From: grundler@dsl2.external.hp.com (Grant Grundler)
To: jsoe0708@tiscali.be
Cc: "Vlad D. Markov" <markov@monmouth.com>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] kernel panic when extracting large tar files
Date: Tue, 7 Jan 2003 02:17:04 -0700 [thread overview]
Message-ID: <20030107091704.GC4093@dsl2.external.hp.com> (raw)
In-Reply-To: <3DED9A660000447F@ocpmta3.freegates.net>
On Tue, Jan 07, 2003 at 08:23:37AM +0100, jsoe0708@tiscali.be wrote:
...
> >Did not want to send the file to the whole group.
> >
> You would :-)
joel is right. See FAQ #17.
http://www.parisc-linux.org/faq/index.html
> Trap 5 on CPU 0
> IIR: 6ab60038 ISR: 00000000 IOR: 1d7dcf3c
> Trap 5 on CPU 0
> IIR: 22643206 ISR: 00000000 IOR: 10309800
> Trap 5 on CPU 0
> IIR: 22643206 ISR: 00000000 IOR: 10309800
> Trap 5 on CPU 0
>
> which say that is a trap 5 (ie a LPMC). So, may me am i wrong, but it seems
> that there is a hardware problem on this machine?
yes. LPMC is usually a recoverable memory parity error.
ISR/IOR is the virtual address that was accessed.
Since this is kernel space (ISR==0), I think you can just
drop the leading 1 for the physical address.
Try pulling half the memory and see if the trap goes away.
Or replace all the memory if you have spares.
grant
next prev parent reply other threads:[~2003-01-07 9:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200301070054.h070rc5k047346@smtp.monmouth.com>
2003-01-07 7:23 ` [parisc-linux] kernel panic when extracting large tar files jsoe0708
2003-01-07 9:17 ` Grant Grundler [this message]
2003-01-07 12:39 ` Thibaut VARENE
2003-01-07 20:13 ` Carlos O'Donell
2003-01-07 23:25 ` Thibaut VARENE
2003-01-08 1:34 ` Carlos O'Donell
2003-01-08 3:20 ` Carlos O'Donell
2003-01-06 2:31 Vlad D. Markov
2003-01-06 9:02 ` jsoe0708
2003-01-06 13:15 ` Matthew Wilcox
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=20030107091704.GC4093@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=jsoe0708@tiscali.be \
--cc=markov@monmouth.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