On Tue, 22 Feb 2005, Parag Warudkar wrote:
> Alan,
> See below for stack traces and also note that the stack traces are after I
> modified usb_device_read to do down_interruptible instead of down. (kudzu
> gets stuck regardless though.) Let me know if you want me to revert the
>
On Tue, 22 Feb 2005, Parag Warudkar wrote:
Alan,
See below for stack traces and also note that the stack traces are after I
modified usb_device_read to do down_interruptible instead of down. (kudzu
gets stuck regardless though.) Let me know if you want me to revert the
down_interruptible
On Tuesday 22 February 2005 03:41 pm, Alan Stern wrote:
> usb_device_read acquires a couple of locks, one for the USB bus list and
> one for the root hub of the bus it's looking at. I don't know which one
> occurs at offset 229 on your system -- maybe you can tell. Oddly enough,
> neither of
On Tue, 22 Feb 2005, Parag Warudkar wrote:
> > You said that the system hangs during bootup. Where in the log does that
> > hang occur? The log itself looks perfectly normal. The Maxtor drive is
> > scanned, the partitions detected, and then apparently one or two
> > partitions are mounted.
On Monday 07 February 2005 11:18 am, Alan Stern wrote:
> > I am already running 2.6.11-rc3 and the problem has not gone away. Are
> > there any relevant fixes in -bk?
>
> No.
>
> > Attached is the bootup log after enabling CONFIG_USB_STORAGE_DEBUG.
>
> You said that the system hangs during bootup.
On Monday 07 February 2005 11:18 am, Alan Stern wrote:
I am already running 2.6.11-rc3 and the problem has not gone away. Are
there any relevant fixes in -bk?
No.
Attached is the bootup log after enabling CONFIG_USB_STORAGE_DEBUG.
You said that the system hangs during bootup. Where in
On Tue, 22 Feb 2005, Parag Warudkar wrote:
You said that the system hangs during bootup. Where in the log does that
hang occur? The log itself looks perfectly normal. The Maxtor drive is
scanned, the partitions detected, and then apparently one or two
partitions are mounted. There's
On Tuesday 22 February 2005 03:41 pm, Alan Stern wrote:
usb_device_read acquires a couple of locks, one for the USB bus list and
one for the root hub of the bus it's looking at. I don't know which one
occurs at offset 229 on your system -- maybe you can tell. Oddly enough,
neither of those
8 matches
Mail list logo
