From: Dan Maas <dmaas@maasdigital.com>
To: Philippe Gramoull? <philippe.gramoulle@mmania.com>
Cc: Steve Kinneberg <kinnebergsteve@acmsystems.com>,
Ben Collins <bcollins@debian.org>, Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
Linux1394dev <linux1394-devel@lists.sourceforge.net>
Subject: Re: 2.5.67-mm3: Bad: scheduling while atomic with IEEE1394 then hard freeze ( lockup on CPU0)
Date: Wed, 16 Apr 2003 22:48:00 -0400 [thread overview]
Message-ID: <20030416224800.A706@morpheus> (raw)
In-Reply-To: <20030417003031.2b603167.philippe.gramoulle@mmania.com>; from philippe.gramoulle@mmania.com on Thu, Apr 17, 2003 at 12:30:31AM +0200
> Since then, i only got these "reset storms" versions over versions.
Jim Radford's nodemgr back-off patch fixes the reset storms, for me at
least. (check the list archives, he posted it a few weeks ago).
It should definitely be applied, but I would hold off until we fix the
nodemgr crash bug, since Jim's patch masks (but does not eliminate) it.
I'd rather force people to deal with the nodemgr crash :)
(if nobody picks up the torch on nodemgr, I'll try myself in a few
days - I'm too busy now but boy I want it FIXED! :)
Regards,
Dan
next prev parent reply other threads:[~2003-04-17 2:36 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
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 [this message]
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=20030416224800.A706@morpheus \
--to=dmaas@maasdigital.com \
--cc=akpm@digeo.com \
--cc=bcollins@debian.org \
--cc=greg@kroah.com \
--cc=kinnebergsteve@acmsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox