From: Ben Collins <bcollins@debian.org>
To: Andrew Morton <akpm@digeo.com>
Cc: Philippe Gramoull? <philippe.gramoulle@mmania.com>,
linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: 2.5.67-mm3: Bad: scheduling while atomic with IEEE1394 then hard freeze ( lockup on CPU0)
Date: Tue, 15 Apr 2003 20:49:33 -0400 [thread overview]
Message-ID: <20030416004933.GI16706@phunnypharm.org> (raw)
In-Reply-To: <20030415160530.2520c61c.akpm@digeo.com>
On Tue, Apr 15, 2003 at 04:05:30PM -0700, Andrew Morton wrote:
> Philippe Gramoull? <philippe.gramoulle@mmania.com> wrote:
> >
> >
> > http://www.philou.org/2.5.67-mm3/2.5.67-mm3.log
>
> This is a great bug report. Thanks.
>
> The 1394 warnings are known about and I think Ben is working on it.
Yeah, they are fixed in the linux1394 tree. I'm getting ready to push
them to Linus.
--
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-04-16 0:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 22:05 2.5.67-mm3: Bad: scheduling while atomic with IEEE1394 then hard freeze ( lockup on CPU0) Philippe Gramoullé
2003-04-15 23:05 ` Andrew Morton
2003-04-15 23:17 ` Philippe Gramoullé
2003-04-15 23:34 ` Andrew Morton
2003-04-16 5:54 ` Greg KH
2003-04-16 16:58 ` Patrick Mochel
2003-04-16 23:40 ` Philippe Gramoullé
2003-04-17 3:54 ` Greg KH
2003-04-16 0:49 ` Ben Collins [this message]
2003-04-16 16:45 ` Philippe Gramoullé
2003-04-16 17:32 ` Steve Kinneberg
2003-04-16 22:30 ` Philippe Gramoullé
2003-04-16 23:35 ` Steve Kinneberg
2003-04-16 23:52 ` Philippe Gramoullé
2003-04-17 2:48 ` Dan Maas
2003-04-16 18:09 ` Ben Collins
2003-04-18 18:51 ` Florin Iucha
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=20030416004933.GI16706@phunnypharm.org \
--to=bcollins@debian.org \
--cc=akpm@digeo.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.gramoulle@mmania.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 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.