From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: Re: Sparc32 SMP
Date: Thu, 23 Nov 2006 22:29:53 +0000 [thread overview]
Message-ID: <456620E1.5070809@systella.fr> (raw)
In-Reply-To: <Pine.LNX.4.10.10607130208320.4657-300000@coalcreekmill.cm.com>
Hello,
This Oops is reproductible. I have decoded the Oops:
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Nov 23 14:26:47 hilbert kernel: Unable to handle kernel NULL pointer
dereference
Nov 23 14:26:48 hilbert kernel: tsk->{mm,active_mm}->context = 00005058
Nov 23 14:26:48 hilbert kernel: tsk->{mm,active_mm}->pgd = fc12d000
Nov 23 14:26:48 hilbert kernel: \|/ ____ \|/
Nov 23 14:26:48 hilbert kernel: "@'/ ,. \`@"
Nov 23 14:26:48 hilbert kernel: /_| \__/ |_\
Nov 23 14:26:48 hilbert kernel: \__U_/
Nov 23 14:26:48 hilbert kernel: tar(13387): Oops [#1]
Nov 23 14:26:48 hilbert kernel: PSR: 400000c2 PC: f008bd8c NPC: f008bd90
Y: 00000000 Not tainted
Using defaults from ksymoops -t elf32-sparc -a sparc
Nov 23 14:26:48 hilbert kernel: PC: <pipe_readv+0xac/0x440>
Nov 23 14:26:48 hilbert kernel: Caller[f008c140]: pipe_read+0x20/0x28
Nov 23 14:26:48 hilbert kernel: Caller[f007dee8]: vfs_read+0xa0/0x16c
Nov 23 14:26:48 hilbert kernel: Caller[f007eb38]: sys_read+0x38/0x64
Nov 23 14:26:48 hilbert kernel: Caller[f0015a3c]:
syscall_is_too_hard+0x3c/0x40
Nov 23 14:26:48 hilbert kernel: Caller[0003df90]: 0x3df98
Nov 23 14:26:49 hilbert kernel: Instruction DUMP: 1a800003 fa04a00c
a810001b <c207600c> 90100013 9fc04000 92100012 80a22000 128000b9
>>PC; f008bd8c <pipe_readv+2f8/4d4> <==
Trace; f008c140 <do_pipe+158/28c>
Trace; f007dee8 <vfs_readv+6c/70>
Trace; f007eb38 <__fput+8c/1b0>
Trace; f0015a3c <linux_sparc_syscall+0/18>
Trace; 0003df90 Before first symbol
Code; f008bd80 <pipe_readv+2ec/4d4>
00000000 <_PC>:
Code; f008bd80 <pipe_readv+2ec/4d4>
0: 1a 80 00 03 bcc c <_PC+0xc>
Code; f008bd84 <pipe_readv+2f0/4d4>
4: fa 04 a0 0c ld [ %l2 + 0xc ], %i5
Code; f008bd88 <pipe_readv+2f4/4d4>
8: a8 10 00 1b mov %i3, %l4
Code; f008bd8c <pipe_readv+2f8/4d4> <== c: c2 07 60 0c ld [ %i5 + 0xc ], %g1 <==Code; f008bd90 <pipe_readv+2fc/4d4>
10: 90 10 00 13 mov %l3, %o0
Code; f008bd94 <pipe_readv+300/4d4>
14: 9f c0 40 00 call %g1
Code; f008bd98 <pipe_readv+304/4d4>
18: 92 10 00 12 mov %l2, %o1
Code; f008bd9c <pipe_readv+308/4d4>
1c: 80 a2 20 00 cmp %o0, 0
Code; f008bda0 <pipe_readv+30c/4d4>
20: 12 80 00 b9 bne 304 <_PC+0x304>
Code; f008bda4 <pipe_readv+310/4d4>
24: 00 00 00 00 unimp 0
1 error issued. Results may not be reliable.
hilbert:/var/log#
I don't understand the last message... Any idea ?
Regards,
JKB
next prev parent reply other threads:[~2006-11-23 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 10:41 sparc32 smp Raymond Burns
2006-07-18 4:35 ` David Miller
2006-11-23 13:35 ` Sparc32 SMP BERTRAND Joël
2006-11-23 22:29 ` BERTRAND Joël [this message]
2006-11-26 9:22 ` BERTRAND Joël
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=456620E1.5070809@systella.fr \
--to=joel.bertrand@systella.fr \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.