From: Ben Collins <bcollins@debian.org>
To: Torrey Hoffman <thoffman@arnor.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Oops in firewire (2.4.21-pre5 with 2.4.21-pre4 firewire driver)
Date: Thu, 13 Mar 2003 01:11:44 -0500 [thread overview]
Message-ID: <20030313061144.GV563@phunnypharm.org> (raw)
In-Reply-To: <1047517628.1172.8.camel@rohan.arnor.net>
On Wed, Mar 12, 2003 at 05:06:23PM -0800, Torrey Hoffman wrote:
> I heard that the firewire merge in 2.4.21-pre5 was messed up, so I
> replaced the -pre5 drivers/ieee1394 with the one from -pre4.
I'd suggest with trying the latest BK cset patch (which fixes -pre5 and
also fixes some things in general).
> I got an oops while loading the driver. I will continue to experiment
> with recent kernels, and try to find a bitkeeper snapshot with the
> latest firewire fixes. Any suggestions are welcome.
> >>EIP; c016e639 <__journal_remove_checkpoint+39/90> <=====
This happened in the kjournald thread context. I'm not sure it is
ieee1394 related, but it is suspect that it happened in the middle of
handling an ieee1394 bus reset.
Is this reproducible when loading the ohci1394 driver? If so, does it
occur when you turn off hotplug (IOW, don't load sbp2 driver) or if the
sbp2 device is not attached?
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2003-03-13 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 1:06 Torrey Hoffman
2003-03-13 6:11 ` Ben Collins [this message]
2003-03-13 18:00 ` Torrey Hoffman
2003-03-14 3:42 ` Torrey Hoffman
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=20030313061144.GV563@phunnypharm.org \
--to=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thoffman@arnor.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
all inboxes | Powered by JetHome®