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 21:09:25 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-99842802808019@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99833581003509@msgid-missing>
The offending command is "/sbin/modprobe ohci1394".
Thank you for your help.
I will dig around ieee1394 tomorrow.
Regards,
Pierre
_________________________________________
David Brownell a écrit :
> > 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.
>
> Then you should be able to try reproducing this by hand,
> without hotplug scripts at all. Is it "pcimodules" that's making
> it crash? Or is it the subsequent "modprobe" commands?
> Neither of those is supposed to be able to crash the kernel.
>
> You should be able to track this down pretty easily. Disable
> the /etc/hotplug/pci.rc script for a moment ("pci.rc-"), boot, then
> run it by hand like "sh -x pci.rc start". That's pretty much the way
> it's done at boot time, except that by passing the "-x" you get
> some nice debug output, and will be able to see what user
> mode command caused the crash.
>
> - 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
prev parent reply other threads:[~2001-08-21 21:09 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
2001-08-21 18:22 ` David Brownell
2001-08-21 21:09 ` Pierre JUHEN [this message]
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-99842802808019@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).