From: Ian Kumlien <pomac@vapor.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Linux-kernel@vger.kernel.org
Subject: Re: [OOPS] related to swap?
Date: Sun, 09 Apr 2006 21:31:58 +0200 [thread overview]
Message-ID: <1144611118.7535.5.camel@localhost> (raw)
In-Reply-To: <44339031.4040307@yahoo.com.au>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
On Wed, 2006-04-05 at 19:38 +1000, Nick Piggin wrote:
> Ian Kumlien wrote:
> > As i said, i really doubt that the memory is at fault here, it has done
> > several passes over the memory but not all tests. I can give it a go
> > though, but i really doubt it'll find anything.
>
> If it doesn't cost you much time (ie. do it overnight) it could save some
> developers a lot of time.
Well, the memory passes test 1-5 and 8. The 32 bit thingies all fail on
4 dimms, so either 4 dimms are broken or the test is broken for amd64.
Anyways, i noticed that the memory clocking got skewed when all the
memory was in the machine, so i've removed 1gb of memory.
> > The kernel i run is a plain 2.6.16.1 from kernel.org (i have heard that
> > you can actually compile gentoos own these days)
>
> OK, good.
2.6.16.2 now... And a new nvidia driver...
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 200 bytes --]
next prev parent reply other threads:[~2006-04-09 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 8:22 [OOPS] related to swap? Ian Kumlien
2006-04-05 9:38 ` Nick Piggin
2006-04-06 21:28 ` Ian Kumlien
2006-04-09 19:31 ` Ian Kumlien [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 22:49 Ian Kumlien
2006-04-04 12:31 ` Nick Piggin
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=1144611118.7535.5.camel@localhost \
--to=pomac@vapor.com \
--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.