VIA VL812 hub stops working with 4.4.0-40.60

Bug #1628363 reported by Dave Chiluk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
Xenial
Invalid
Undecided
Dave Chiluk

Bug Description

VIA VL812 hub stops working with 4.4.0-40.60. Works fine with 4.4.0-39.59.

Logs include both boot with 4.4.0-39 *(most recent) and 4.4.0-40 (previous boot).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.40.42
ProcVersionSignature: Ubuntu 4.4.0-39.59-generic 4.4.21
Uname: Linux 4.4.0-39-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep 27 22:48:35 2016
HibernationDevice: RESUME=UUID=1cb62c08-3564-4d8a-846c-696369aaaa0d
InstallationDate: Installed on 2016-01-15 (256 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-39-generic root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-39-generic N/A
 linux-backports-modules-4.4.0-39-generic N/A
 linux-firmware 1.157.4
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2013
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DX79SI
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG28808-500
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
klp-taint: 12289

Revision history for this message
Dave Chiluk (chiluk) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Tim Gardner (timg-tpi)
Changed in linux (Ubuntu Xenial):
assignee: nobody → Dave Chiluk (chiluk)
status: New → In Progress
Revision history for this message
Dave Chiluk (chiluk) wrote :

So I just rebooted 4 times with the -40 kernel, and everything seems to be going well. I'm going to chalk this one up to hardware misbehaving. At least until someone else hits this as well.

Keep in mind the hub, does not work in usb 3.0 mode. That is not what this bug is about.

Dave Chiluk (chiluk)
Changed in linux (Ubuntu):
status: Confirmed → Invalid
Changed in linux (Ubuntu Xenial):
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.