From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: "Ismail Dönmez" <ismail@pardus.org.tr>,
linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, "Greg KH" <greg@kroah.com>
Subject: Re: oops in __nodemgr_remove_host_dev (was Re: Ooops with suspend to RAM)
Date: Thu, 15 Mar 2007 01:14:00 +0100 [thread overview]
Message-ID: <45F88FC8.10202@s5r6.in-berlin.de> (raw)
In-Reply-To: <45F88E8B.90403@s5r6.in-berlin.de>
I wrote:
> according to a quick test I made right now it is a regression post 2.6.20.
> # modprobe ohci1394 # wait a bit, eth1394 is auto-loaded
> # modprobe -r eth1394
> # modprobe -r ohci1394
> works.
> # modprobe ohci1394 # wait a bit, eth1394 is auto-loaded
> # modprobe -r ohci1394
> oopses with the same trace as Ismael posted. And indeed, looking at his
> trace once more I now also spot eth1394 among his linked-in modules.
To avoid any misunderstandings: Both the former and the latter sequence
work under 2.6.20 and earlier.
--
Stefan Richter
-=====-=-=== --== -====
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-03-15 0:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 4:42 Ooops with suspend to RAM Ismail Dönmez
2007-03-14 11:14 ` oops in __nodemgr_remove_host_dev (was Re: Ooops with suspend to RAM) Stefan Richter
2007-03-14 11:45 ` oops in __nodemgr_remove_host_dev Stefan Richter
2007-03-14 16:58 ` oops in __nodemgr_remove_host_dev (was Re: Ooops with suspend to RAM) Ismail Dönmez
2007-03-14 18:25 ` Stefan Richter
2007-03-14 22:51 ` Ismail Dönmez
2007-03-15 0:08 ` Stefan Richter
2007-03-15 0:14 ` Stefan Richter [this message]
2007-03-15 0:45 ` Ismail Dönmez
2007-03-15 0:49 ` Ismail Dönmez
2007-03-16 19:46 ` Stefan Richter
2007-03-20 21:43 ` [PATCH 2.6.21-rc4] ieee1394: fix oops on "modprobe -r ohci1394" after network class_device conversion Stefan Richter
2007-03-20 22:26 ` Ismail Dönmez
2007-03-21 18:11 ` Stefan Richter
2007-03-20 23:34 ` Greg KH
2007-03-21 0:16 ` Stefan Richter
2007-05-13 11:43 ` Stefan Richter
2007-05-20 20:21 ` Stefan Richter
2007-03-14 11:50 ` Ooops with suspend to RAM Adrian Bunk
2007-03-14 16:59 ` Ismail Dönmez
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=45F88FC8.10202@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=ismail@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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