From: Chris Ruvolo <chris+lkml@ruvolo.net>
To: Ben Collins <bcollins@debian.org>
Cc: gaxt <gaxt@rogers.com>,
linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: Re: Firewire
Date: Thu, 24 Jul 2003 17:07:03 -0700 [thread overview]
Message-ID: <20030725000703.GD23196@ruvolo.net> (raw)
In-Reply-To: <20030724234503.GR1512@phunnypharm.org>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
On Thu, Jul 24, 2003 at 07:45:03PM -0400, Ben Collins wrote:
> If it wasn't being updated, I would see the problem too, and I'm not.
On another note, I just got this output when doing a 'rmmod' ohci1394:
bad: scheduling while atomic!
Call Trace:
[<c01159c7>] schedule+0x3b7/0x3c0
[<c0115d28>] wait_for_completion+0x78/0xd0
[<c0115a20>] default_wake_function+0x0/0x30
[<c0115a20>] default_wake_function+0x0/0x30
[<c01226c0>] kill_proc_info+0x40/0x60
[<c89ddff5>] nodemgr_remove_host+0x55/0xa0 [ieee1394]
[<c89d9b66>] highlevel_remove_host+0x76/0x90 [ieee1394]
[<c89c56ee>] ohci1394_pci_remove+0x3e/0x160 [ohci1394]
[<c01a44eb>] pci_device_remove+0x3b/0x40
[<c01c4efe>] device_release_driver+0x5e/0x60
[<c01c4f2b>] driver_detach+0x2b/0x40
[<c01c518b>] bus_remove_driver+0x3b/0x70
[<c01c55b4>] driver_unregister+0x14/0x28
[<c01a47a7>] pci_unregister_driver+0x17/0x30
[<c89c5ad2>] ohci1394_cleanup+0x12/0x16 [ohci1394]
[<c012cdc5>] sys_delete_module+0x125/0x190
[<c013fcb3>] sys_munmap+0x43/0x70
[<c010940b>] syscall_call+0x7/0xb
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2003-07-24 23:51 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 13:34 Firewire gaxt
2003-07-24 22:35 ` Firewire Chris Ruvolo
2003-07-24 22:36 ` Firewire Ben Collins
2003-07-24 23:09 ` Firewire Chris Ruvolo
2003-07-24 23:14 ` Firewire Ben Collins
2003-07-24 23:48 ` Firewire Chris Ruvolo
2003-07-24 23:45 ` Firewire Ben Collins
2003-07-25 0:07 ` Chris Ruvolo [this message]
2003-07-25 0:14 ` Firewire Chris Ruvolo
2003-07-25 1:13 ` Firewire Torrey Hoffman
2003-07-25 1:27 ` Firewire Chris Ruvolo
2003-07-25 1:29 ` Firewire Ben Collins
2003-07-25 2:00 ` Firewire Chris Ruvolo
2003-07-25 2:19 ` Firewire Ben Collins
2003-07-25 3:23 ` Firewire Sam Bromley
2003-07-25 4:12 ` Firewire Ben Collins
2003-07-25 5:39 ` Firewire Chris Ruvolo
2003-07-25 13:34 ` Firewire Ben Collins
2003-07-25 14:06 ` Firewire gaxt
2003-07-25 13:47 ` Firewire Ben Collins
2003-07-25 14:23 ` Firewire gaxt
2003-07-25 15:28 ` Firewire gaxt
2003-07-25 14:29 ` Firewire Chris Ruvolo
2003-07-25 14:29 ` Firewire Ben Collins
2003-07-25 15:40 ` Firewire Ben Collins
2003-07-25 16:07 ` Firewire Chris Ruvolo
2003-07-25 16:18 ` Firewire Ben Collins
2003-07-25 17:02 ` Firewire Chris Ruvolo
2003-07-25 17:07 ` Firewire Ben Collins
2003-07-25 17:51 ` Firewire Torrey Hoffman
2003-07-25 18:13 ` Firewire Chris Ruvolo
2003-07-25 18:12 ` Firewire Ben Collins
2003-07-25 18:43 ` Firewire gaxt
2003-07-25 18:26 ` Firewire Ben Collins
2003-07-25 18:45 ` Firewire Ben Collins
2003-07-25 19:16 ` Firewire gaxt
2003-07-25 19:35 ` Firewire Chris Ruvolo
2003-07-25 20:11 ` Firewire Ben Collins
2003-07-25 21:48 ` Firewire gaxt
2003-07-26 4:41 ` Firewire (One fix worked, now getting oops) Sam Bromley
2003-07-26 15:12 ` Ben Collins
2003-07-26 17:41 ` Sam Bromley
2003-07-26 17:45 ` Ben Collins
2003-07-26 16:52 ` Firewire Chris Ruvolo
2003-07-26 17:45 ` Firewire Ben Collins
2003-07-25 20:48 ` Firewire Torrey Hoffman
2003-07-25 20:44 ` Firewire Ben Collins
2003-07-25 18:18 ` Firewire Torrey Hoffman
2003-07-25 18:33 ` Firewire gaxt
2003-07-25 16:28 ` Firewire gaxt
2003-07-25 15:53 ` Firewire Chris Ruvolo
2003-07-25 15:47 ` Firewire Ben Collins
2003-07-25 16:14 ` Firewire Chris Ruvolo
2003-07-25 13:34 ` Firewire 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=20030725000703.GD23196@ruvolo.net \
--to=chris+lkml@ruvolo.net \
--cc=bcollins@debian.org \
--cc=gaxt@rogers.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.