All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at mm/rmap.c:480 in 2.6.10-rc3-bk7
Date: Tue, 14 Dec 2004 17:11:32 -0800	[thread overview]
Message-ID: <20041215011132.GA16099@kroah.com> (raw)
In-Reply-To: <20041215001912.GA15575@kroah.com>

On Tue, Dec 14, 2004 at 04:19:12PM -0800, Greg KH wrote:
> On Tue, Dec 14, 2004 at 11:26:48PM +0000, Hugh Dickins wrote:
> > One case that's easy to explain: if it was preceded (perhaps hours
> > earlier) by a "Bad page state" message and stacktrace, referring to
> > the same page (in ecx, edx, ebp in your dump), which showed non-zero
> > mapcount, then this is an after-effect of bad_page resetting mapcount.
> > And the real problem was probably a double free, which bad_page noted,
> > but carried on regardless.  Worth checking your logs for, let us know,
> > but there have been several reports where that's definitely not so.
> 
> Nope, nothing like that in my logs, sorry.
> 
> > I presume this was just a one-off?  If you can repeat it from time to
> > time, I'll try to devise some printk'ing to shed more light.
> 
> I'll try to see if I can reproduce it.  If so, I'll let you know.

Yes, I can duplicate it easily now:
	- running X with drm and the radeon driver
	- start a gish game up in 640x480 mode and start the initial
	  level.
	- as the laptop just can't handle the cpu demands of this
	  program, everything runs way too slow.
	- switch back to the console that I started X up on and hit
	  ctrl-C.
	- X dies, and the kernel oops happens.

And yes, it does only show up when I'm using drm/agp for me, as this is
the only way I've ever seen this error.  I can't really even get gish to
start up without drm, but I guess I could try to see if I can do that
later tonight.

Any testing you want me to do?

Oh, and this also happens on 2.6.10-rc3-bk8.

thanks,

greg k-h

  reply	other threads:[~2004-12-15  1:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 16:45 kernel BUG at mm/rmap.c:480 in 2.6.10-rc3-bk7 Greg KH
2004-12-14 23:26 ` Hugh Dickins
2004-12-15  0:10   ` Nick Piggin
2004-12-15  0:19   ` Greg KH
2004-12-15  1:11     ` Greg KH [this message]
2004-12-15 17:23       ` Hugh Dickins
2004-12-15 17:58         ` Greg KH
2004-12-15 18:48           ` Hugh Dickins
2004-12-15 22:22             ` Hugh Dickins
2004-12-15 22:33             ` Dave Airlie
2004-12-15 23:19               ` Greg KH
2004-12-15 19:03           ` Andrea Arcangeli
2004-12-15 22:48             ` Andrea Arcangeli
2004-12-15 23:41               ` Greg KH
2004-12-16  5:18                 ` Hugh Dickins
2004-12-16 14:28                   ` Andrea Arcangeli
2004-12-16 17:03                     ` Hugh Dickins
2004-12-15  0:43   ` Andrea Arcangeli

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=20041215011132.GA16099@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.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.