From: Chris Wright <chrisw@osdl.org>
To: Eric Cooper <ecc@cmu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: repeatable mm/rmap.c crash in 2.6.11.*
Date: Wed, 4 May 2005 15:11:22 -0700 [thread overview]
Message-ID: <20050504221122.GU23013@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050504215311.GA28900@localhost>
* Eric Cooper (ecc@cmu.edu) wrote:
> I first noticed this in 2.6.11, and it has been present in each point
> release since then. This is on a machine that runs 2.6.10 with no
> problems. I finally got around to capturing the output over a serial
> console, using 2.6.11.8. It happens on every boot, almost always
> before the init scripts are finished. Here's one example. I can
> provide others, or more info, as needed. Thanks.
This one's been a bit elusive. If you could apply the patch in the mail
(link) below and let me (or Hugh) know what you find that'd be quite
helpful.
http://marc.theaimsgroup.com/?l=linux-kernel&m=111101533309675&w=2
thanks,
-chris
prev parent reply other threads:[~2005-05-04 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 21:53 repeatable mm/rmap.c crash in 2.6.11.* Eric Cooper
2005-05-04 22:11 ` Chris Wright [this message]
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=20050504221122.GU23013@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=ecc@cmu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox