From: "Philippe Gramoullé" <philippe.gramoulle@mmania.com>
To: linux-kernel@vger.kernel.org
Cc: Linux IEEE 1394 Devel Mailing List
<linux1394-devel@lists.sourceforge.net>
Subject: 2.6.0-test1-mm1: bad: scheduling while atomic! after removing ohci1394 module
Date: Wed, 16 Jul 2003 18:08:55 +0200 [thread overview]
Message-ID: <20030716180855.22d4a4f4.philippe.gramoulle@mmania.com> (raw)
Hello,
With 2.6.0-test1-mm1, i have the following in my logs after i rmmod'ed the
ohci1394 module:
bad: scheduling while atomic!
Call Trace:
[<c011c958>] schedule+0x578/0x580
[<c0108ff2>] copy_thread+0x32/0x250
[<c011cd0c>] wait_for_completion+0x8c/0xf0
[<c011c9b0>] default_wake_function+0x0/0x30
[<c011c9b0>] default_wake_function+0x0/0x30
[<c012b9e1>] kill_proc_info+0x51/0x80
[<e0b87665>] nodemgr_remove_host+0x55/0xa0 [ieee1394]
[<e0b82fba>] highlevel_remove_host+0x8a/0xa0 [ieee1394]
[<e0b4163d>] ohci1394_pci_remove+0x3d/0x160 [ohci1394]
[<c018c93e>] sysfs_hash_and_remove+0x4e/0x7c
[<c022c75b>] pci_device_remove+0x3b/0x40
[<c0256916>] device_release_driver+0x66/0x70
[<c025694b>] driver_detach+0x2b/0x40
[<c0256bae>] bus_remove_driver+0x3e/0x80
[<c0256fc3>] driver_unregister+0x13/0x2a
[<c022ca56>] pci_unregister_driver+0x16/0x30
[<e0b41adf>] ohci1394_cleanup+0xf/0x11 [ohci1394]
[<c0137d89>] sys_delete_module+0x139/0x170
[<c014c1e5>] sys_munmap+0x45/0x70
[<c010b0ab>] syscall_call+0x7/0xb
Should i worry ?
Besides that, IEE1394 works fine with my DV camcorder.
Thanks,
Philippe
next reply other threads:[~2003-07-16 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 16:08 Philippe Gramoullé [this message]
2003-07-16 16:36 ` 2.6.0-test1-mm1: bad: scheduling while atomic! after removing ohci1394 module Ben Collins
2003-07-16 16:45 ` Jeff Garzik
2003-07-16 16:53 ` Ben Collins
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=20030716180855.22d4a4f4.philippe.gramoulle@mmania.com \
--to=philippe.gramoulle@mmania.com \
--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;
as well as URLs for NNTP newsgroup(s).