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 12:31:29 +0200 [thread overview]
Message-ID: <018401c67e54$1043cfb0$1800a8c0@dcccs> (raw)
In-Reply-To: 4472E2E0.4000201@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:24 PM
Subject: Re: swapper: page allocation failure. - random reboot problem
> Haar János wrote:
>
> > Sorry, i have allready did these things.
> >
> > The motherboard + CPU + RAM successed the overnight memtest, but anyway
i
> > have replaced this group with another pre-tested ones, but no change!
> > (Additionally, i replaced the NIC [e1000 to e1000, and e1000 to
realtek],
> > the sata cards [promise to promise], the sata and ide cables, mb, cpu,
ram,
> > ps, and the power cable too.
> > Only the 12hdd is the same, but smart reports no errors at all!)
> > The power supply is the 3rd. and the problem is the same.
>
> 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....
Cheers,
Janos
>
> >
> > This is really a software bug, but i dont know exactly where.
>
> Could be. memtest doesn't guarantee anything though...
>
> --
> SUSE Labs, Novell Inc.
> Send instant messages to your online friends http://au.messenger.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2006-05-23 10:32 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 [this message]
2006-05-23 10:45 ` Nick Piggin
2006-05-23 11:01 ` Haar János
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='018401c67e54$1043cfb0$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox