public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Alexander Nyberg <alexn@telia.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Simple question re: oops
Date: Sat, 30 Jul 2005 20:46:17 -0400	[thread overview]
Message-ID: <1122770777.5473.1.camel@mindpipe> (raw)
In-Reply-To: <21d7e997050730174034a68f4@mail.gmail.com>

On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote:
> > panic_on_oops has no effect, a bunch of stuff flies past and the last
> > thing I see is "gam_server: scheduling while atomic" then a stack trace
> > of the core dump path then "Aiee, killing interrupt handler".
> > 
> > I am starting to suspect the hard drive, does that sound plausible?
> > It's as if it locks up when it hits a certain disk block.
> 
> run memtest on it... you might have bad RAM..
> 

Already swapped it out, but I'll try memtest.

Any idea why printk_ratelimit does not work?  I set it to 1000 (per the
docs this should limit to 1 printk per second) and burst to 1 but I
still get screenfuls of text flying by.

Lee



  reply	other threads:[~2005-07-31  0:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-30 23:48 Simple question re: oops Lee Revell
2005-07-31  0:10 ` Lee Revell
2005-07-31  0:11 ` Alexander Nyberg
2005-07-31  0:15   ` Lee Revell
2005-07-31  0:21   ` Lee Revell
2005-07-31  0:40     ` Dave Airlie
2005-07-31  0:46       ` Lee Revell [this message]
2005-08-01 18:03         ` ECC Support in Linux Roger Heflin
2005-08-02  1:22           ` Wang, Zhenyu
2005-07-31  2:50       ` SOLVED - Re: Simple question re: oops Lee Revell

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=1122770777.5473.1.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=airlied@gmail.com \
    --cc=alexn@telia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox