Bug 89608 - USB device not accepting new address on A7V333-X
Summary: USB device not accepting new address on A7V333-X
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 9
Hardware: athlon Linux
Target Milestone: ---
Assignee: Pete Zaitcev
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-24 22:41 UTC by Stephen Lewis
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-18 22:19:45 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Kernel messages, interrupt and PCI config data (9.27 KB, text/plain)
2003-04-24 22:43 UTC, Stephen Lewis
no flags Details
Kernel 2.4.22-pre6-ac1 log with verbose USB error reporting (24.08 KB, text/plain)
2003-07-18 21:54 UTC, Stephen Lewis
no flags Details

Description Stephen Lewis 2003-04-24 22:41:55 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
Using RH9 clean install on Asus A7V333-X mobo with Athlon XP2600+ processor.

The motherboard  has three USB 2.0 hubs on it. All three appear to be
initialised correctly, but only one appears to work at any time. After
rebooting, the working hub will not necessarily be the same one. the other two
hubs give "USB device not accepting new address" errors.

The same problem occurs on the 3 USB devices I have: a 128MB USB memory stick,
an HP 315 camera, and a Trust Micro Mouse.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Connect USB device to one of the 3 on-board hubs


Actual Results:  Only one hub works - it appears to be random on each boot.

Expected Results:  All three should work.

Additional info:

Comment 1 Stephen Lewis 2003-04-24 22:43:16 UTC
Created attachment 91285 [details]
Kernel messages, interrupt and PCI config data

Comment 2 Stephen Lewis 2003-04-28 21:34:05 UTC
Just tried home-compiled kernel-2.4.21-rc1-ac3. The "usb_control/bulk_msg:
timeout" errors in the earlier attachment do not appear to be present from
limited testing, but the main problem is still there. 

Comment 3 Pete Zaitcev 2003-06-03 03:13:54 UTC
Try to remove ehci-hcd from /etc/modules.conf.

Comment 4 Pete Zaitcev 2003-06-03 20:31:41 UTC
The "kill ehci-hcd" suggestion still stands, plus I'd like a report on
the 2.4.20-18. Thanks.

Comment 5 Stephen Lewis 2003-06-09 22:19:59 UTC
Using kernel 2.4.20-18.9, only the hub connected to the front USB ports appears
to have this problem; the other 2 hubs work OK. On investigating, this is also
true of 2.4.20-13.9.

IIRC, the front hub used to work intermittently with the earlier kernels, so I
don't believe it's a hardware problem.

Removing the ehci-hcd line from modules.conf makes no difference.

Comment 6 Stephen Lewis 2003-07-18 21:54:22 UTC
Created attachment 93012 [details]
Kernel 2.4.22-pre6-ac1 log with verbose USB error reporting

I have just repeated this test with kernel 2.4.22-pre6-ac1, having set verbose
USB error reporting at compile time. Results attached. It now appears to be the
same (front panel) hub reporting this problem at all times, so earlier comment
about random hub may be unrelated.

Comment 7 Stephen Lewis 2003-07-18 22:19:45 UTC
Bug closed. Signal wires to header on motherboard transposed - a hardware problem.

Note You need to log in before you can comment on or make changes to this bug.