lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 15 Sep 2007 09:56:28 -0700
From:	Pete Zaitcev <zaitcev@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Christian Volkmann <haveaniceday@...sv.de>,
	linux-kernel@...r.kernel.org,
	linux-usb-devel@...ts.sourceforge.net,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	zaitcev@...hat.com
Subject: Re: 2.6.23-rc6: usb 1-1: device not accepting address 2, error -62

On Sat, 15 Sep 2007 03:48:19 -0700, Andrew Morton <akpm@...ux-foundation.org> wrote:

> > I have an error message with 2.6.23-rc6.
> > This did not happen with 2.6.22.
> 
> Another one for Michal's dirt file.

No, I think it's the module ordering again.

> > 2.6.23-rc6 boot.msg extract ( hub/usb )

I wish users stopped this filtering, it's a very bad idea.

As it is, there's no message showing when ehci_hcd was loaded.
We can try piece together the picture:

> > <6>usb usb1: configuration #1 chosen from 1 choice
> > <6>hub 1-0:1.0: USB hub found
> > <6>hub 1-0:1.0: 2 ports detected
> > <6>usb usb2: configuration #1 chosen from 1 choice
> > <6>hub 2-0:1.0: USB hub found
> > <6>hub 2-0:1.0: 2 ports detected
> > <6>usb 1-1: new low speed USB device using ohci_hcd and address 2

ok this was ohci_hcd

> > <3>usb 1-1: device not accepting address 2, error -62
> > <6>usb 5-2: new full speed USB device using uhci_hcd and address 2

was ehci here? We don't know but I bet it was, because:

> > <6>usb 6-2: new high speed USB device using ehci_hcd and address 2

> > 2.6.22 boot.msg extract ( hub/usb )

This one seems far shorter. The EHCI comes online late here as well,
but not as late as in the "regression" case. I am wondering if we
have some kind of "parallel PCI probing" option in action here.

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ