From: Pierre JUHEN <pierre.juhen@wanadoo.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: PROBLEM : PCI hotplug crashes with 2.4.9
Date: Tue, 21 Aug 2001 18:04:53 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-99841691328306@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99833581003509@msgid-missing>
I was a bit lazy, writing by memory : you are right the system says
"pcimodules is scanning more than 00:00.0"
but onluy this line and crashes. Under 2.4.6, it scans all the pci
adresses.
Renaming pcimodules to pcimodules- leads to " ** can't synthesize pci
hotplug events".
On my system, kudzu is started after hotplug, so the problem seems not
linked with that,
since it crashes even during boot, very early, just after fsck.
David Brownell a écrit :
> > Only the
> > first line "pcimodules scanning 00:00.0" is displayed.
>
> Curious. If anything, I'd expect it to say
> "pcimodules is scanning more than 00:00.0".
> (The last version I saw didn't have a way to
> scan for modules appropriate to a particular
> PCI slot, and the hotplug scripts warn about
> that limitation.)
>
> You might try renaming "pcimodules" to "pcimodules-"
> to see if that changes any interesting behavior. I notice
> you're using RedHat with 7.1 and usb-uhci. I seem to
> recall that Kudzu wanted to do some hotplug-ish things;
> they may not play well together yet.
>
> - Dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-08-21 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-20 19:33 PROBLEM : PCI hotplug crashes with 2.4.9 Pierre JUHEN
2001-08-20 19:36 ` Greg KH
2001-08-20 22:50 ` David Brownell
2001-08-21 18:04 ` Pierre JUHEN [this message]
2001-08-21 18:22 ` David Brownell
2001-08-21 21:09 ` Pierre JUHEN
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=marc-linux-hotplug-99841691328306@msgid-missing \
--to=pierre.juhen@wanadoo.fr \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).