kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #28370
[Bug 1250488] Re: USB hub stopped working on a given USB port (would work on any other port). Reboot fixed the issue
Here's the output of lsusb now, though now everything works fine so I
guess it won't be of much help.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 015: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120
Bus 003 Device 011: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 010: ID 0489:e04e Foxconn / Hon Hai
Bus 001 Device 004: ID 04f2:b374 Chicony Electronics Co., Ltd
Bus 003 Device 012: ID 03f0:1604 Hewlett-Packard DeskJet 940c
Bus 003 Device 013: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 003 Device 014: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1250488
Title:
USB hub stopped working on a given USB port (would work on any other
port). Reboot fixed the issue
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
I have two USB ports that I usually use interchangeably: to port A I
connect the mouse, to port B I connect a USB hub (to which I connect a
keyboard, printer and other devices).
Suddenly (probably after resuming from a suspend), the USB hub stopped working when connected to port A.
It would work fine, however, if connected to port B. When I say the hub stopped working I mean that any device (even a keyboard) wouldn't work if connected through the hub.
I exchanged ports dozens of times and 100% checked that:
- mouse and keyboard would systematically work fine if connected directly to any of the ports A or B
- the USB hub would systematically work fine only if connected to port B
- the USB hub would systematically fail (i.e. no device connected through it would ever work) if connected to port A
Now I've rebooted, and everything works as expected again: the USB
hub always works fine whether I connect it to port A or B.
I thought this was something physical until I rebooted and found out
that everything works again.
This is absolutely ridiculous.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-33-generic 3.8.0-33.48
ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11
Uname: Linux 3.8.0-33-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: teo 2229 F.... pulseaudio
Date: Tue Nov 12 15:13:49 2013
HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3
InstallationDate: Installed on 2013-10-11 (31 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.8.0-33-generic N/A
linux-backports-modules-3.8.0-33-generic N/A
linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.07
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250488/+subscriptions
References