From: Tomas Szepe <szepe@pinerecords.com>
To: linux-ia64@vger.kernel.org
Subject: Re: 2.4.25 + 040218.diff OOPS
Date: Wed, 24 Mar 2004 10:54:19 +0000 [thread overview]
Message-ID: <20040324105419.GA20174@louise.pinerecords.com> (raw)
In-Reply-To: <20040320115002.GF21377@louise.pinerecords.com>
On Mar-23 2004, Tue, 10:12 -0700
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> Can you look up these IPs by hand, since ksymoops doesn't work?
> (I always use gdb: "info line *0xe00000000447cfe2").
Ok, I'll try to when (if) the OOPS reappears.
> > Mar 20 11:46:07 columbia kernel: bash[15068]: NaT consumption 2216203124768
> > Mar 20 11:46:07 columbia kernel:
> > Mar 20 11:46:07 columbia kernel: Pid: 15068, CPU 0, comm: bash
> > Mar 20 11:46:07 columbia kernel: psr : 0000121008022038 ifs : 800000000000070f ip : [<e000000004449e71>] Not tainted
>
> > Mar 20 11:47:51 columbia kernel: <1>Unable to handle kernel NULL pointer dereferencemc[15066]: Oops 11012296146944
> > Mar 20 11:47:51 columbia kernel:
> > Mar 20 11:47:51 columbia kernel: Pid: 15066, CPU 0, comm: mc
> > Mar 20 11:47:51 columbia kernel: psr : 0000121008026018 ifs : 800000000000038c ip : [<e0000000045a7be1>] Not tainted
>
> If these are reproducible, it would be useful to figure out how,
> so I could try it here.
No "luck" so far, the machine has been running solid these days
(except I'm getting occassional segfaults in userland, mainly from
make and bash).
Thanks!
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2004-03-24 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 11:50 2.4.25 + 040218.diff OOPS Tomas Szepe
2004-03-23 17:12 ` Bjorn Helgaas
2004-03-24 10:54 ` Tomas Szepe [this message]
2004-03-24 13:00 ` Tomas Szepe
2004-03-24 14:34 ` Keith Owens
2004-03-24 15:29 ` Andreas Schwab
2004-03-24 15:53 ` Bjorn Helgaas
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=20040324105419.GA20174@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=linux-ia64@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