I'm getting a problem in usb-storage (it's loaded as a module towards the end
of the boot sequence). The module locks during initialisation, which doesn't
happen in 2.4.17.
(is it possible to unload a crashed module without rebooting?
This happens so often with SCSI... )
The culprit seems to be my new usb CF reader. Unfortunately it's unbranded
and I can't identify the underlying hardware. None of the specific drivers
(e.g. sandisk, lexar, microtech, freecom) need to be loaded for it to work,
so I guess there's some generic protocol for usb->scsi?
Regardless, unless someone else has an idea, I'm going to try manually
merging the usb-storage changes in from 2.4.17 to 2.4.18-rc2 until it
breaks to try and isolate the problem..
--
JP Morris - aka DOUG the Eagle (Dragon) -=UDIC=- [email protected]
Fun things to do with the Ultima games http://www.it-he.com
Developing a U6/U7 clone http://ire.it-he.org
d+++ e+ N+ T++ Om U1234!56!7'!S'!8!9!KA u++ uC+++ uF+++ uG---- uLB----
uA--- nC+ nR---- nH+++ nP++ nI nPT nS nT wM- wC- y a(YEAR - 1976)
On Wed, Feb 20, 2002 at 06:58:55PM +0000, J.P. Morris wrote:
>
> I'm getting a problem in usb-storage (it's loaded as a module towards the end
> of the boot sequence). The module locks during initialisation, which doesn't
> happen in 2.4.17.
Does the lockup happen without the CF reader plugged in?
If so, and you later plugin the CF reader (after the module is loaded)
does the kernel still lock up?
thanks,
greg k-h
On Wed, 20 Feb 2002 11:05:09 -0800
Greg KH <[email protected]> wrote:
> On Wed, Feb 20, 2002 at 06:58:55PM +0000, J.P. Morris wrote:
> >
> > I'm getting a problem in usb-storage (it's loaded as a module towards the end
> > of the boot sequence). The module locks during initialisation, which doesn't
> > happen in 2.4.17.
>
> Does the lockup happen without the CF reader plugged in?
No.
> If so, and you later plugin the CF reader (after the module is loaded)
> does the kernel still lock up?
No. However, the reader then doesn't work either.
No device entries get created for it (I'm using devfs).
It's a multiformat reader (CF/SM/MMC) so there will be a cluster of
entries when it is working correctly.
Note that the kernel itself doesn't lock, just the module.
That is, the module never completes initialisation and sits there forever.
When it was being loaded by script at boot, I had to use Alt-Sys-K to kill
the process trying to load the module in order to log in.
I have tried upgrading just the usb-storage module from 2.4.17 to 2.4.18
and (unfortunately) it still works.. the cause of the problem is elsewhere.
Any ideas? Thanks.
> thanks,
>
> greg k-h
>
--
JP Morris - aka DOUG the Eagle (Dragon) -=UDIC=- [email protected]
Fun things to do with the Ultima games http://www.it-he.com
Developing a U6/U7 clone http://ire.it-he.org
d+++ e+ N+ T++ Om U1234!56!7'!S'!8!9!KA u++ uC+++ uF+++ uG---- uLB----
uA--- nC+ nR---- nH+++ nP++ nI nPT nS nT wM- wC- y a(YEAR - 1976)
On Thu, Feb 21, 2002 at 08:04:59PM +0000, J.P. Morris wrote:
>
> Note that the kernel itself doesn't lock, just the module.
> That is, the module never completes initialisation and sits there forever.
> When it was being loaded by script at boot, I had to use Alt-Sys-K to kill
> the process trying to load the module in order to log in.
>
> I have tried upgrading just the usb-storage module from 2.4.17 to 2.4.18
> and (unfortunately) it still works.. the cause of the problem is elsewhere.
>
> Any ideas? Thanks.
Enable debugging in the usb-storage driver, and send the kernel debug
output to the usb-storage author and maintainer :)
Good luck,
greg k-h