linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Kernel oops while duming user core.
Date: Thu, 31 Jan 2008 14:41:58 -0600	[thread overview]
Message-ID: <20080131204158.GV14201@localdomain> (raw)
In-Reply-To: <20080131201601.GA10501@loki.buserror.net>

Scott Wood wrote:
> On Thu, Jan 31, 2008 at 11:40:04AM -0600, Rune Torgersen wrote:
> > Unable to handle kernel paging request for data at address 0x48024000
> > Faulting instruction address: 0xc000f0a0
> > Oops: Kernel access of bad area, sig: 11 [#1]
> > PREEMPT Innovative Systems ApMax
> 
> Does it happen without preempt?
> 
> > Modules linked in: drv_wd(P) drv_scc devcom drv_pcir tipc drv_ss7
> > drv_auxcpu drv_leds(P) drv_ethsw proc_sysinfo(P) i2c_8266(P)
> > NIP: c000f0a0 LR: c0011fec CTR: 00000080
> > REGS: eebe9b70 TRAP: 0300   Tainted: P         (2.6.24-test)
> 
> Does it happen without the modules?

I doubt the modules are the problem; there was a practically identical
report from someone with an untainted 2.6.24-rc kernel a few weeks ago
(see my first reply to Rune).

> 
> > MSR: 00009032 <EE,ME,IR,DR>  CR: 24004442  XER: 00000000
> > DAR: 48024000, DSISR: 20000000
> 
> Hmm, this doesn't look like a valid DSISR, so I'm guessing this was a TLB
> miss that got redirected to DataAccess (or is there something that causes
> DSRISR[2] to be set on 8280?  I didn't see anything in the manual...). 
> However, SRR1 in that case seems to indicate a store, which dcbst shouldn't
> generate (except on 8xx, according to the comment in update_mmu_cache).
> 
> Do you have a simple test case that we could try to reproduce?  I tried a
> simple core dump on an 8280, and it worked.

Is the crashing program multithreaded?  The first report had firefox
triggering the oops.

  parent reply	other threads:[~2008-01-31 20:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 13:45 Kernel oops while duming user core Rune Torgersen
2008-01-31 16:15 ` Nathan Lynch
2008-01-31 16:26   ` Rune Torgersen
2008-01-31 17:40     ` Rune Torgersen
2008-01-31 19:15       ` Kumar Gala
2008-01-31 19:18         ` Rune Torgersen
2008-01-31 20:16       ` Scott Wood
2008-01-31 20:19         ` Rune Torgersen
2008-01-31 20:38         ` Rune Torgersen
2008-01-31 20:41         ` Nathan Lynch [this message]
2008-01-31 20:45           ` Rune Torgersen
2008-01-31 20:55           ` Scott Wood
2008-01-31 21:58             ` Scott Wood
2008-01-31 22:10               ` Rune Torgersen
2008-02-03  7:34                 ` Benjamin Herrenschmidt
2008-02-04 18:23                   ` Kernel oops while dumping " Scott Wood
2008-01-31 19:15     ` Kernel oops while duming " Kumar Gala
2008-01-31 19:23       ` Rune Torgersen
2008-01-31 19:54         ` Nathan Lynch
2008-02-01 17:38   ` Scott Wood
2008-02-02 12:05     ` Clemens Koller

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=20080131204158.GV14201@localdomain \
    --to=ntl@pobox.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).