public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mikael Wahlberg <mikael.wahlberg@ardendo.se>
To: Seth Mos <knuffie@xs4all.nl>
Cc: "Christoph Hellwig" <hch@infradead.org>,
	linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com,
	"Per Lejontand" <pele@ardendo.se>,
	"Jonas Engström" <jonas@ardendo.se>
Subject: Re: Filesystem kernel hangup, 2.6.3 (bad: scheduling while atomic!)
Date: Mon, 23 Feb 2004 14:50:23 +0100	[thread overview]
Message-ID: <1077544223.1247.23.camel@harrier> (raw)
In-Reply-To: <4.3.2.7.2.20040223144245.01c2e688@pop.xs4all.nl>

On Mon, 2004-02-23 at 14:46, Seth Mos wrote:
> At 14:08 23-2-2004 +0100, Mikael Wahlberg wrote:
> >On Mon, 2004-02-23 at 13:19, Christoph Hellwig wrote:
> > > On Sun, Feb 22, 2004 at 04:49:41PM +0100, Mikael Wahlberg wrote:
> > > did you run memtest86 on the box?  do you some strange patches applied or
> > > external modules loaded?  What's your .config?
> >
> >No strange patches. Pure 2.6.3 dist kernel. We haven't run memtest86,
> >but as I mentioned above, we have 4 equal machines with error correcting
> >memory, so I find it unlikely to be a memory problem.
> 
> The memory might be fine, but the mainboard might still be borked. I have 
> seen this once with Dell kit. Asuming can be dangerous. If you can spare 
> the down time it is always a good idea to make sure.

Yes, but four new identical boxes... seems very unlikely. But sure, we
can try it when I get to the computer room (It is not at our site, but
at a customers)

/Mikael
-- 
-----------------------------------------------------------------------
 Mikael Wahlberg,  M.Sc.                  Ardendo
 Unit Manager Professional Services/      e-mail: mikael@ardendo.se
 Technical Project Manager                GSM:    +46 733 279 274


  reply	other threads:[~2004-02-23 13:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22 15:49 Filesystem kernel hangup, 2.6.3 (bad: scheduling while atomic!) Mikael Wahlberg
2004-02-23 12:19 ` Christoph Hellwig
2004-02-23 13:08   ` Mikael Wahlberg
2004-02-23 13:13     ` Christoph Hellwig
2004-03-04  9:35       ` Mikael Wahlberg
2004-02-23 13:46     ` Seth Mos
2004-02-23 13:50       ` Mikael Wahlberg [this message]
2004-02-23 13:46   ` Mikael Wahlberg
     [not found]   ` <1077543963.1246.20.camel@harrier.lucky.linux.kernel>
2004-04-28  4:39     ` allocation failures with CBQ bandwidth limiting & high net use (was Re: Filesystem kernel hangup, 2.6.3 (bad: scheduling while atomic!)) Brad Allen
2004-04-28  5:42       ` Andrew Morton

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=1077544223.1247.23.camel@harrier \
    --to=mikael.wahlberg@ardendo.se \
    --cc=hch@infradead.org \
    --cc=jonas@ardendo.se \
    --cc=knuffie@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=pele@ardendo.se \
    /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