From: Alberto Bertogli <albertogli@telpin.com.ar>
To: linux-kernel@vger.kernel.org
Subject: Oops again
Date: Tue, 20 Feb 2001 09:29:51 -0300 (ARST) [thread overview]
Message-ID: <982672191.3a92633f35b87@webmail.telpin.com.ar> (raw)
Yesterday I posted an oops report. Today I've just arrived and the machine got
an oops once again (at about 2am). It was almost unreadable because this time
minicom was running and the output is a real mess, the only things clear were:
Unable to handle kernel NULL pointer dereference at virtual address 00000004
*pde: 00000000
And below
process swapper (pid: 0
Then at the end the same kernel panic posted previously:
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
It ran 2.2 before, and the only difference is that now mailsnarf is running.
If you need any other info, please just ask.
Thanks,
Alberto
reply other threads:[~2001-02-20 12:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=982672191.3a92633f35b87@webmail.telpin.com.ar \
--to=albertogli@telpin.com.ar \
--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