LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-stable release plans?
Date: Wed, 24 Jan 2007 14:37:23 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0701241425170.10956@blonde.wat.veritas.com> (raw)
In-Reply-To: <20070124133037.98357.qmail@web52914.mail.yahoo.com>

On Wed, 24 Jan 2007, Chris Rankin wrote:
> 
> Personally, I dumped 2.6.19.x like a hot coal as soon as I tripped over this bug:
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=7707
> 
> I didn't take much to trigger it, either. But the silence has been deafening.

Oh, the page_remove_rmap BUG, page_mapcount negative.

Sorry for the deafening silence, see I was CC'ed but dropped the ball.

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.

Oftentimes it's bad RAM (try memtest86), 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.  Not once (except
during experimental patch testing) has it been proved due to an actual
VM problem.

Hugh

  reply	other threads:[~2007-01-24 14:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 13:30 Chris Rankin
2007-01-24 14:37 ` Hugh Dickins [this message]
     [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 15:06 Chris Rankin
2007-01-24 15:40 ` 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=Pine.LNX.4.64.0701241425170.10956@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rankincj@yahoo.com \
    --subject='Re: 2.6.18-stable release plans?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).