From: "J.P. Morris" <jpm@it-he.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18-rc2 problem..
Date: Thu, 21 Feb 2002 20:04:59 +0000 [thread overview]
Message-ID: <20020221200459.642e3bb3.jpm@it-he.org> (raw)
In-Reply-To: <20020220190509.GA30784@kroah.com>
In-Reply-To: <20020220185855.2bcecc24.jpm@it-he.org> <20020220190509.GA30784@kroah.com>
On Wed, 20 Feb 2002 11:05:09 -0800
Greg KH <greg@kroah.com> 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=- doug@it-he.org
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)
next prev parent reply other threads:[~2002-02-21 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 18:58 2.4.18-rc2 problem J.P. Morris
2002-02-20 19:05 ` Greg KH
2002-02-21 20:04 ` J.P. Morris [this message]
2002-02-21 22:07 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020221200459.642e3bb3.jpm@it-he.org \
--to=jpm@it-he.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox