From: "David J. M. Karlsen" <david@davidkarlsen.com>
To: linux-kernel@vger.kernel.org
Subject: OOPS report
Date: Tue, 27 Sep 2005 21:09:21 +0200 [thread overview]
Message-ID: <433998E1.7080609@davidkarlsen.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2515 bytes --]
I get this OOPS every time I go to runlevel S or 6 from 2:
INIT: Going single user
INIT: Sending processes the TERM signal
INUnable to handle kernel NULL pointer dereference
tsk->{mm,active_mm}->context = 0000000000000001
tsk->{mm,active_mm}->pgd = fffff800303a6000
\|/ ____ \|/
"@'/ .. \`@"
/_| \__/ |_\
\__U_/
swapper(0): Oops [#1]
TSTATE: 0000000080009600 TPC: 0000000000571084 TNPC: 0000000000571088 Y:
0000000
0 Not tainted
TPC: <tty_wakeup+0x4/0x80>
g0: 0000000000001018 g1: 000000000045572c g2: 0000000000000001 g3:
0000000000000
000
g4: 00000000006d6fc0 g5: fffff80000000000 g6: 00000000006d2fc0 g7:
0000000000000
003
o0: 0000000000000000 o1: 0000000000000aab o2: 0000000000000001 o3:
fffffffffffff
ef0
o4: fffff80037f07d20 o5: fffff800007b3e78 sp: 00000000006d6051 ret_pc:
000000000
0455588
RPC: <__tasklet_schedule+0x28/0xa0>
l0: 00000000007dc0c0 l1: 000000000000000f l2: 00000000006d8000 l3:
00000000ef9fd
588
l4: 00000000ef9fd538 l5: 0000000000000001 l6: 000000000000000a l7:
00000000007dc
000
i0: 0000000000000000 i1: fffff80037f02a68 i2: 0000000000000001 i3:
fffff80037f09
af0
i4: fffff80037f02a48 i5: fffff80037f02a40 i6: 00000000006d6111 i7:
0000000000455
72c
I7: <tasklet_action+0x8c/0x120>
Caller[000000000045572c]: tasklet_action+0x8c/0x120
Caller[00000000004552d0]: __do_softirq+0xf0/0x120
Caller[0000000000455354]: do_softirq+0x54/0x80
Caller[0000000000455494]: irq_exit+0x54/0x80
Caller[0000000000408994]: tl0_irq11+0x34/0x40
Caller[00000000004149dc]: cpu_idle+0x3c/0xe0
Caller[000000000078884c]: start_kernel+0x22c/0x240
Caller[00000000004046c4]: tlb_fixup_done+0x5c/0x64
Caller[0000000000000000]: _start+0xffffffffffbfc000/0x12
Instruction DUMP: 01000000 01000000 9de3bf40 <c25e2120> b2102001
b4102001 b6
102000 83307005 82086001
Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Rebooting in 60 seconds..
uname -a
Linux sunshine 2.6.13 #1 SMP Sun Sep 4 23:37:10 CEST 2005 sparc64 GNU/Linux
cat /proc/cpuinfo
cpu : TI UltraSparc I (SpitFire)
fpu : UltraSparc I integrated FPU
promlib : Version 3 Revision 1
prom : 3.1.1
type : sun4u
ncpus probed : 1
ncpus active : 1
Cpu0Bogo : 284.67
Cpu0ClkTck : 00000000088601c0
MMU Type : Spitfire
State:
CPU0: online
/proc/config.gz attached.
Is it well nown?
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 7452 bytes --]
next reply other threads:[~2005-09-27 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 19:09 David J. M. Karlsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-02 8:42 OOPS report Daryl Radivojevic
2009-01-05 10:04 ` Oliver Neukum
2003-05-28 15:16 OOPs report Lawrence Walton
2003-05-28 22:53 ` Andrew Morton
2003-05-28 23:05 ` Dave Jones
2003-05-28 23:55 ` Andrew Morton
2003-05-26 18:35 Oops report Petro
2003-01-25 17:05 Asher Yanich
2001-12-27 20:51 Mark Hindley
2000-12-22 10:48 Bill K.
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=433998E1.7080609@davidkarlsen.com \
--to=david@davidkarlsen.com \
--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