From: Chris Rankin <rankincj@yahoo.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: Alan <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-stable release plans?
Date: Thu, 25 Jan 2007 09:16:04 +0000 (GMT) [thread overview]
Message-ID: <486377.64357.qm@web52903.mail.yahoo.com> (raw)
In-Reply-To: <20070125010020.GB26654@deepthought>
--- Ken Moffat <zarniwhoop@ntlworld.com> wrote:
> At the moment, you have a problem that nobody recognises. If you're not
> willing to test if the problem happens repeatably, (you appear to
> have had one failure and immediately reverted to an old kernel), who
> do you think will be able to fix it?
This bug seems to be in the kernel's "memory management", and the last memory-related bug I had
(caused by a bad DIMM on another machine) caused creeping filesystem corruption. However, this
machine is my main desktop, and so I am keen to keep the filesystems intact. So yes, that involves
not running a kernel that has shown itself to be unreliable.
I was hoping that someone with a deeper knowledge of the differences between 2.6.18 and 2.6.19
would have an idea of what might have triggered this problem, and yes, I was also thinking that
some more people would trip over it and help debug it.
But anyway - can someone please tell me what "Eeek! page_mapcount(page) went negative! (-1)" is
*really* saying/implying? Because I am currently translating this as "I WANT TO EAT YOUR
FILESYSTEMS".
Cheers,
Chris
___________________________________________________________
New Yahoo! Mail is the ultimate force in competitive emailing. Find out more at the Yahoo! Mail Championships. Plus: play games and win prizes.
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk
next prev parent reply other threads:[~2007-01-25 9:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 15:53 2.6.18-stable release plans? 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 [this message]
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
[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:06 Chris Rankin
2007-01-24 15:40 ` Hugh Dickins
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=486377.64357.qm@web52903.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zarniwhoop@ntlworld.com \
/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