From: "Haar János" <djani22@netcenter.hu>
To: "Nick Piggin" <nickpiggin@yahoo.com.au>
Cc: <kernel@kolivas.org>, <cw@f00f.org>, <linux-kernel@vger.kernel.org>
Subject: Re: swapper: page allocation failure. - random reboot problem
Date: Tue, 23 May 2006 13:01:07 +0200 [thread overview]
Message-ID: <01a101c67e58$38cdc8b0$1800a8c0@dcccs> (raw)
In-Reply-To: 4472E7E4.6060403@yahoo.com.au
----- Original Message -----
From: "Nick Piggin" <nickpiggin@yahoo.com.au>
To: "Haar János" <djani22@netcenter.hu>
Cc: <kernel@kolivas.org>; <cw@f00f.org>; <linux-kernel@vger.kernel.org>
Sent: Tuesday, May 23, 2006 12:45 PM
Subject: Re: swapper: page allocation failure. - random reboot problem
> Haar János wrote:
> > ----- Original Message -----
>
> >>But is the power supply rated enough to support all the drives?
> >>I have seen random reboots where the power supply wasn't good
> >>enough.
> >
> >
> > This is the 3rd modell, currently 550W.
> > The system is P4 3G.
> >
> > The another 2 stable node uses only 460W, and all hardware is equal.
> > But i tried to swap ps between the stable and unstabe nodes, but nothing
is
> > changed....
>
> Not sure then, sorry.
OK, what do you recommend? :-)
>
> If it is a software problem, then if you can narrow it down further
> (eg. kernel 2.6.15 worked, 2.6.16 did not), or find a reproducable
> test case for it, then some more progress might be made.
Yes, you have right!
I try it allready, but i cannot step back enough, because my sata card works
only on 2.6.16+
Before i use the promise sata cards, and the sata 300G hdds, i use 2.6.15
kernel, and all my 4 nodes was really stable.
But this is not enough to exactly find the problem. :-(
Anyway, Hetbert Xu helps me a lot to track down the problem, but we only can
close out some thing.
If i have right, the problem is about libata, promise driver,
sata-error-handling or similar, but not so sure.
If there is no way to software debug, i will swap all the 12 hdd between 2
disk nodes, and this can show i have right, or not.
Cheers,
Janos
>
> --
> SUSE Labs, Novell Inc.
> Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-05-23 11:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 8:10 swapper: page allocation failure Haar János
2006-05-21 8:16 ` Chris Wedgwood
2006-05-21 8:37 ` Haar János
2006-05-21 8:47 ` Chris Wedgwood
2006-05-21 9:03 ` Haar János
2006-05-21 9:10 ` Chris Wedgwood
2006-05-21 9:31 ` Haar János
2006-05-21 10:24 ` Chris Wedgwood
2006-05-21 10:42 ` Haar János
2006-05-21 10:26 ` Chris Wedgwood
2006-05-21 10:45 ` Haar János
2006-05-21 12:01 ` Nick Piggin
2006-05-21 13:58 ` Haar János
2006-05-22 0:09 ` Nick Piggin
2006-05-22 7:41 ` Haar János
2006-05-22 11:17 ` Con Kolivas
2006-05-22 15:08 ` Haar János
2006-05-22 15:12 ` Con Kolivas
2006-05-22 21:06 ` swapper: page allocation failure. - random reboot problem Haar János
2006-05-23 9:17 ` Nick Piggin
2006-05-23 10:16 ` Haar János
2006-05-23 10:24 ` Nick Piggin
2006-05-23 10:31 ` Haar János
2006-05-23 10:45 ` Nick Piggin
2006-05-23 11:01 ` Haar János [this message]
2006-05-21 9:23 ` swapper: page allocation failure Haar János
2006-05-21 12:03 ` Andrew Morton
2006-05-21 14:01 ` Haar János
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='01a101c67e58$38cdc8b0$1800a8c0@dcccs' \
--to=djani22@netcenter.hu \
--cc=cw@f00f.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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.