From: Chris Rankin <rankincj@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-stable release plans?
Date: Wed, 24 Jan 2007 15:06:23 +0000 (GMT) [thread overview]
Message-ID: <249539.3227.qm@web52902.mail.yahoo.com> (raw)
> That's surely no reason to dump 2.6.19.x, you'll find the occasional
> such report on every(?) release since page mapcount went into 2.6.7.
This was the only time I've seen it, before or since.
> Oftentimes it's bad RAM (try memtest86)
There is nothing wrong with my RAM. I tested it quite extensively when I upgraded to 2 GB.
> sometimes it's a bad driver (probably the case for the tainted P report appended
> to your untainted one), sometimes it's unidentified memory corruption.
But MY kernel is clearly untainted. So what other explanation is there apart from a kernel bug?
Cheers,
Chris
___________________________________________________________
All New Yahoo! Mail – Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html
next reply other threads:[~2007-01-24 15:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 15:06 Chris Rankin [this message]
2007-01-24 15:40 ` 2.6.18-stable release plans? Hugh Dickins
[not found] <BC3E207A-1A56-4032-9619-910E80281E9C@gmail.com>
2007-01-25 8:51 ` Chris Rankin
-- strict thread matches above, loose matches on Subject: below --
2007-01-24 15:53 Chris Rankin
2007-01-24 16:12 ` Hugh Dickins
2007-01-24 17:33 ` Chris Rankin
2007-01-24 16:28 ` Mark Rustad
2007-01-24 22:37 ` Chris Rankin
2007-01-24 23:11 ` Alan
2007-01-24 23:05 ` Chris Rankin
2007-01-24 23:32 ` Mark Rustad
2007-01-24 23:45 ` Chris Rankin
2007-01-25 1:00 ` Ken Moffat
2007-01-25 9:16 ` Chris Rankin
2007-01-25 19:36 ` Ken Moffat
2007-01-26 13:02 ` Chris Rankin
2007-01-25 23:26 ` Alistair John Strachan
2007-01-25 3:05 ` Mark Rustad
2007-01-25 21:04 ` Matt Mackall
2007-02-02 4:02 ` Valdis.Kletnieks
2007-02-02 6:47 ` Jon Masters
2007-02-02 8:17 ` Valdis.Kletnieks
2007-01-24 13:30 Chris Rankin
2007-01-24 14:37 ` Hugh Dickins
2007-01-22 22:13 Chuck Ebbert
2007-01-23 0:23 ` Jesper Juhl
2007-01-23 20:33 ` Chuck Ebbert
2007-01-23 20:56 ` Adrian Bunk
2007-01-24 4:50 ` Daniel Barkalow
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=249539.3227.qm@web52902.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/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.