Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "James Braid" <james.braid@peace.com>
To: "'Grant Grundler'" <grundler@dsl2.external.hp.com>
Cc: <parisc-linux@lists.parisc-linux.org>
Subject: RE: [parisc-linux] Re: Dodgy SCSI in L2000
Date: Fri, 10 May 2002 10:46:17 +1200	[thread overview]
Message-ID: <00b001c1f7ab$571903d0$5e01000a@bongo> (raw)
In-Reply-To: <20020509165445.7A515482A@dsl2.external.hp.com>

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> The fault was caused at 0x0000000010108fe0 - I need to see the
> matching vmlinux and System.map to determine where this is in
> the code.
> 

Ah, mind if send you the vmlinux and System.map off-list?


> When the box freezes, do "tc" from GSP. On reboot, at PDC prompt
> type "ser pim" to get the state of the machine when it was TC'd.
> Once you've saved the PIM dump, it's good to clear PIM.
> (iirc, "ser clearpim")
> Again, save matching Sysytem.map and vmlinux.
> 

> IIRC, setting _SYNC parameter to 10 is equivalent to "fast".

Okay, I will try that and put a new kernel in.
 
> oic. In cases like this, we have to disable Stack Dumping since
> it data page faults. I suspect that's what's happened in the
> previous dumps too. You can disable stack dumps by changing "#if 1"
> to "#if 0" on line 149 (show_stack()) in
> arch/parisc/kernel/traps.c.  

I will disable that as well and put a new kernel in.

> BTW, typically this msg means a kernel driver is attempting 
> to directly
> access user space data instead of copying the data into kernel
> space.  

That sounds nasty...

> > so I cranked it up to dbench 100. That crashed nicely with 
> this panic:
> > 
> > Dumping Stack from 0x0000000056390000 to 0x0000000056390000:
> > 
> > Kernel Fault: Code=15 regs=0000000046390000
> > (Addr=0000000056388018) 
> 
> did you get the "Stack pointer and cr30 do not correspond!" 
> msg before this?

Yep, I did get the "Stack pointer..." stuff before this, I left it
off the email though.

> Me either since I've not seen this problem. This does sound like
> the SCSI interface driver is hitting a corner case and dying there.
> But that's just a SWAG.
> 
> I'll have to get dbench and try it on the a500 when that's
> available.  

Cool.

Thanks, James.

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1.1

iQA/AwUBPNr8OFW+bhIOiSqWEQLoTwCeOG3NSZzK01Aq1w+tz7R421fs9xgAoPbb
9VCHtaEiG6tTKElsrWsPMiad
=6qMg
-----END PGP SIGNATURE-----

  reply	other threads:[~2002-05-09 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jbraid@gmx.net>
     [not found] ` <000001c1f741$846d8730$0500a8c0@oscar>
2002-05-09 16:54   ` [parisc-linux] Re: Dodgy SCSI in L2000 Grant Grundler
2002-05-09 22:46     ` James Braid [this message]
2002-05-11 21:14       ` Grant Grundler
2002-05-16  5:00         ` James Braid

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='00b001c1f7ab$571903d0$5e01000a@bongo' \
    --to=james.braid@peace.com \
    --cc=grundler@dsl2.external.hp.com \
    --cc=parisc-linux@lists.parisc-linux.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