public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: walt <wa1ter@myrealbox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.3-rc2 bk]  ieee1394 oops on bootup
Date: Thu, 12 Feb 2004 09:47:34 -0500	[thread overview]
Message-ID: <20040212144734.GA639@phunnypharm.org> (raw)
In-Reply-To: <402B92A4.7040703@myrealbox.com>

On Thu, Feb 12, 2004 at 06:50:12AM -0800, walt wrote:
> walt wrote:
> >This problem started with the bk changesets from Linus yesterday (11Feb).
> >
> >I get the oops below if Firewire is compiled into the kernel or if the
> >modules are loaded at bootime (I'm using hotplug+udev).  The strange
> >thing is that if I load the Firewire modules by hand after bootup then
> >everything is okay....
> 
> Sorry, I just discovered that this is wrong.  I can load the ieee1394
> module with no errors.  It is only when I load the ohci1394 module
> that the oops occurs -- even after booting.

I've already got a fix for this. Getting ready to post it to the list.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/

  reply	other threads:[~2004-02-12 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.fjveksa.v44uhu@ifi.uio.no>
2004-02-12 14:50 ` [2.6.3-rc2 bk] ieee1394 oops on bootup walt
2004-02-12 14:47   ` Ben Collins [this message]
2004-02-12  6:58 Bob Gill
  -- strict thread matches above, loose matches on Subject: below --
2004-02-12  5:04 walt

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=20040212144734.GA639@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wa1ter@myrealbox.com \
    /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