From: Florian Lohoff <flo@rfc822.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@linux-mips.org
Subject: Re: sudo oops on mips64 linux_2_4
Date: Wed, 16 Jul 2003 16:21:36 +0200 [thread overview]
Message-ID: <20030716142136.GA13810@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1030716150225.25959B-100000@delta.ds2.pg.gda.pl>
[-- Attachment #1: Type: text/plain, Size: 3795 bytes --]
On Wed, Jul 16, 2003 at 03:05:05PM +0200, Maciej W. Rozycki wrote:
> Please pass it through ksymoops for more details. Version 2.4.9 should
> work just fine for mips64.
This looks still broken - Giving the vmlinux file to ksymoops makes it
even worse - tons or errors.
ksymoops 2.4.8 on mips 2.4.19-r5k-ip22. Options used
-v /dev/null (specified)
-k /dev/null (specified)
-l /dev/null (specified)
-o /dev/null (specified)
-m /home/flo/System.map (specified)
Error (regular_file): read_nm_symbols /dev/null is not a regular file, ignored
Warning (read_vmlinux): no kernel symbols in vmlinux, is /dev/null a valid vmlinux file?
Error (regular_file): read_ksyms /dev/null is not a regular file, ignored
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Cpu 0 Unable to handle kernel paging request at address 0000000000000000, epc == ffffffff88171104, ra == ffffffff880159f0
Cpu 0
$0 : 0000000000000000 ffffffff881e0000 0000000000000020 0000000000000000
$4 : 0000000000000000 ffffffff881dffff ffffffff881e0000 0000000000000020
$8 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000
$12 : 0000000000000000 0000000000000001 0000000000000028 0000000000000003
$16 : ffffffffffffffff 000000007fff7a20 0000000000000000 000000007fff7a28
$20 : 0000000000000004 000000007fff7aa0 000000007fff7b60 000000007fff7bf0
$24 : 0000000000000000 000000002ad0d6f0
$28 : ffffffff8a188000 ffffffff8a18be30 000000007fff7c80 ffffffff880159f0
epc : ffffffff88171104 Not tainted
Using defaults from ksymoops -t elf32-tradbigmips -a mips:3000
Process sudo (pid: 225, stackpage=ffffffff8a188000)
Stack: 0000004000000000 000000050000013a 000000505d00f61c 0000000000000000
ffffffff881cdd08 0000000000008912 ffffffff8a231a80 000000007fff7a20
ffffffff880157dc 0000000000000002 000000007fff7e34 0000000000000004
0000000000000004 000000007fff7a64 000000007fff7a60 ffffffff8801aeec
0000000000000000 00000000100006c0 0000000000000fd6 0000000000000000
0000000000000004 0000000000008912 000000007fff7a20 0000000000000000
0000000000000000 0000000000000000 0000000010003ec0 0000000000000010
000000002adc3f44 000000002adc3f44 0000000020666f72 0000000020256820
000000007fff7e34 0000000000000001 0000000000000001 0000000000000002
0000000000000000 000000007fff7aa0 000000007fff7b60 000000007fff7bf0
0000000000000006 ...
Call Trace: [<ffffffff880157dc>] [<ffffffff8801aeec>]
Code: 0085202f 10c0fff2 64c5ffff <a0800000> 64840001 14a0fffd 64a5ffff 03e00008 00000000
>>PC; ffffffff88171104 <END_OF_CODE+fffffffeffe868fc/????> <=====
Trace; ffffffff880157dc <END_OF_CODE+fffffffeffd2afd4/????>
Trace; ffffffff8801aeec <END_OF_CODE+fffffffeffd306e4/????>
Code; 881710f8 <fbmem_read_proc+d8/100>
00000000 <_PC>:
Code; 881710f8 <fbmem_read_proc+d8/100>
0: 0085202f 0x85202f
Code; 881710fc <fbmem_read_proc+dc/100>
4: 10c0fff2 beqz a2,ffffffd0 <_PC+0xffffffd0>
Code; 88171100 <fbmem_read_proc+e0/100>
8: 64c5ffff 0x64c5ffff
Code; 88171104 <fbmem_read_proc+e4/100>
c: a0800000 sb zero,0(a0)
Code; 88171108 <fbmem_read_proc+e8/100>
10: 64840001 0x64840001
Code; 8817110c <fbmem_read_proc+ec/100>
14: 14a0fffd bnez a1,c <_PC+0xc>
Code; 88171110 <fbmem_read_proc+f0/100>
18: 64a5ffff 0x64a5ffff
Code; 88171114 <fbmem_read_proc+f4/100>
1c: 03e00008 jr ra
Code; 88171118 <fbmem_read_proc+f8/100>
20: 00000000 nop
1 warning and 2 errors issued. Results may not be reliable.
Flo
--
Florian Lohoff flo@rfc822.org +49-171-2280134
Heisenberg may have been here.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-16 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 11:07 sudo oops on mips64 linux_2_4 Florian Lohoff
2003-07-16 13:05 ` Maciej W. Rozycki
2003-07-16 14:21 ` Florian Lohoff [this message]
2003-07-16 15:21 ` Maciej W. Rozycki
2003-07-16 18:45 ` Ladislav Michl
2003-07-16 19:01 ` Maciej W. Rozycki
2003-07-16 19:05 ` Geert Uytterhoeven
2003-07-16 19:54 ` Maciej W. Rozycki
2003-07-16 19:57 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2003-07-16 15:05 Chris Fouts
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=20030716142136.GA13810@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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