From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: Sparc32 SMP
Date: Thu, 23 Nov 2006 13:35:11 +0000 [thread overview]
Message-ID: <4565A38F.10101@systella.fr> (raw)
In-Reply-To: <Pine.LNX.4.10.10607130208320.4657-300000@coalcreekmill.cm.com>
Hello Bob,
I'm testing some configurations with 2.6.18.2 linux kernel. This kernel
boots wihtout any trouble and I believe that all troubles we have seen
are fixed.
With SuperSparc-II, kernel seems to be stable, but I'm not able to
untar a linux kernel without receive "tâche interrompue" (unterrupted
task) or an Oops :
Unable to handle kernel NULL pointer dereference
tsk->{mm,active_mm}->context = 00005058
tsk->{mm,active_mm}->pgd = fc12d000
\|/ ____ \|/
"@'/ ,. \`@"
/_| \__/ |_\
\__U_/
tar(13387): Oops [#1]
PSR: 400000c2 PC: f008bd8c NPC: f008bd90 Y: 00000000 Not tainted
PC: <pipe_readv+0xac/0x440>
%G: 00001000 fbbfea14 0000003c 00000030 fbbfea00 73635f6c f93be000
00000000
%O: f0a0d900 f0a0d900 fcffb000 63616368 6536345f 70616765 f93bfd88
f008c030
RPC: <pipe_readv+0x350/0x440>
%L: 00000000 00000000 fbbfea50 fbbfea00 00000000 fcffc000 00000001
00000001
%I: f93bfe60 00000003 f93bfe60 00001800 fcffb000 00000000 f93bfe00
f008c140
Caller[f008c140]: pipe_read+0x20/0x28
Caller[f007dee8]: vfs_read+0xa0/0x16c
Caller[f007eb38]: sys_read+0x38/0x64
Caller[f0015a3c]: syscall_is_too_hard+0x3c/0x40
Caller[0003df90]: 0x3df98
Instruction DUMP: 1a800003 fa04a00c a810001b <c207600c> 90100013
9fc04000 92
100012 80a22000 128000b9
Unable to handle kernel NULL pointer dereference
tsk->{mm,active_mm}->context = 0000506a
tsk->{mm,active_mm}->pgd = fc13c800
\|/ ____ \|/
"@'/ ,. \`@"
/_| \__/ |_\
\__U_/
tar(13402): Oops [#2]
PSR: 400000c6 PC: f008bd8c NPC: f008bd90 Y: 00000000 Not tainted
PC: <pipe_readv+0xac/0x440>
%G: 00002800 fb478e14 00000104 000000d0 fb478e00 09307866 f882c000
00000000
%O: f0a4bf00 f0a4bf00 fcfe1000 30306632 30312c30 78613830 f882dd88
f008c030
RPC: <pipe_readv+0x350/0x440>
%L: 00000000 00000000 fb478f18 fb478e00 00000000 fcfe2000 00000001
00000001
%I: f882de60 0000000d f882de60 00002000 fcfe1000 00000000 f882de00
f008c140
Caller[f008c140]: pipe_read+0x20/0x28
Caller[f007dee8]: vfs_read+0xa0/0x16c
Caller[f007eb38]: sys_read+0x38/0x64
Caller[f0015a3c]: syscall_is_too_hard+0x3c/0x40
Caller[0003df90]: 0x3df98
Instruction DUMP: 1a800003 fa04a00c a810001b <c207600c> 90100013
9fc04000 92
100012 80a22000 128000b9
I think that the trouble I have seen with HyperSPARC comes from the
same mistake. Any idea ?
Regards,
JKB
next prev parent reply other threads:[~2006-11-23 13:35 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 ` BERTRAND Joël [this message]
2006-11-23 22:29 ` Sparc32 SMP BERTRAND Joël
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=4565A38F.10101@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.