From: borenius@shuttle.de (Raoul Borenius)
To: Florian Lohoff <flo@rfc822.org>
Cc: Ralf Baechle <ralf@oss.sgi.com>, linux-mips@oss.sgi.com
Subject: Re: Kernel crash on boot with current cvs (todays)
Date: Wed, 13 Jun 2001 13:37:51 +0200 [thread overview]
Message-ID: <20010613133751.A18749@bunny.shuttle.de> (raw)
In-Reply-To: <20010613125610.A18235@paradigm.rfc822.org>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Wed, Jun 13, 2001 at 12:56:10PM +0200, Florian Lohoff wrote:
> >
> > Using ksymoops gave a lot of warnings this time. Don't know why, the
> > System.map should be the right one (it's out of
> > kernel-image-2.4.3-ip22-r4k.tgz).
>
> This is because the system map has been generated with newer binutils
> which always dump the addresses as 64Bit addresses. Load the system
> map into an text editor and delete the first ffffffff from the
> addresses 1,$ s/^ffffffff//
Should have looked closer, sorry...
I've attached the output of ksymoops.
Regrds
Raoul
---------------------------------------------------------------------
Raoul Gunnar Borenius Deutsches Forschungsnetz e.V.
WiNShuttle Lindenspürstr.32, 70176 Stuttgart
Phone : +49 711 63314-206 FAX: +49 711 63314-133
E-Mail : borenius@shuttle.de http://www.shuttle.de
---------------------------------------------------------------------
[-- Attachment #2: trace.txt --]
[-- Type: text/plain, Size: 3321 bytes --]
ksymoops 2.4.1 on mips 2.4.3. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.3/ (default)
-m /boot/System.map-2.4.3 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
Starting periodic command scheduler: cronkernel BUG at semaphore.c:235!
Unable to handle kernel paging request at virtual address 00000000, epc == 8800e e5c, ra == 8800ee5c
$0 : 00000000 1000fc00 0000001f 8f63a000
$4 : 00000017 00000000 00000001 8877a3a0
$8 : 0000000a 88171cc0 00000000 00000000
$12: 00000000 881718e0 fffffff9 0000000a
$16: 8877a59c 00000000 8f63a000 8877a5a4
$20: 8f63bf04 8f63bf00 8f63bea0 00000009
$24: 8f63bcf2 ffffffff
$28: 8f63a000 8f63bdd8 7fff7bb0 8800ee5c
epc : 8800ee5c
Using defaults from ksymoops -t elf32-tradbigmips -a mips:3000
Status: 1000fc03
Cause : 0000000c
Process start-stop-daem (pid: 129, stackpage=8f63a000)
Stack: 88124dc0 88124dd8 000000eb 00000000 8877a59c 8877a580 8800eb84 10011f10
00000000 8ffa02c0 88063810 880647f4 00000000 8f63a000 8877a5a4 8877a5a4
fffffffe 8877a580 8fac4840 8877a59c 8f63bf04 88063670 8fac4660 8f8cec20
8f63bf00 8f63bf00 8fac4840 8f63bf00 8fac4840 8814b00d 8f63bf00 8f63bf04
880640f0 880640b8 8fac4840 8805f7f4 8fac4660 8814b00d 8f8ceca0 8f8ceca0
88052a88 ...
Call Trace: [<88124dc0>] [<88124dd8>] [<8800eb84>] [<88063810>] [<880647f4>] [<8 8063670>] [<880640f0>] [<880640b8>] [<8805f7f4>] [<88052a88>] [<88052b74>] [<880
537c0>] [<88053768>] [<88052294>] [<8804ef14>] [<8800fc28>] [<8800c638>] [<c013d 686>]
Code: 240600eb 0e007859 00000000 <ae200000> 26040010 24050003 0e006b45 2406
>>RA; 8800ee5c <__rwsem_wake+b8/dc>
>>PC; 8800ee5c <__rwsem_wake+b8/dc> <=====
Trace; 88124dc0 <prom_getsysid+cc8/106c>
Trace; 88124dd8 <prom_getsysid+ce0/106c>
Trace; 8800eb84 <__down_read+1dc/1e4>
Trace; 88063810 <proc_root_link+b4/e4>
Trace; 880647f4 <proc_pid_make_inode+24/10c>
Code; 8800ee50 <__rwsem_wake+ac/dc>
0000000000000000 <_PC>:
Code; 8800ee50 <__rwsem_wake+ac/dc>
0: 240600eb li $a2,235
Code; 8800ee54 <__rwsem_wake+b0/dc>
4: 0e007859 jal 801e164 <_PC+0x801e164> 9002cfb4 <END_OF_CODE+7e98120/????>
Code; 8800ee58 <__rwsem_wake+b4/dc>
8: 00000000 nop
Code; 8800ee5c <__rwsem_wake+b8/dc> <=====
c: ae200000 sw $zero,0($s1) <=====
Code; 8800ee60 <__rwsem_wake+bc/dc>
10: 26040010 addiu $a0,$s0,16
Code; 8800ee64 <__rwsem_wake+c0/dc>
14: 24050003 li $a1,3
Code; 8800ee68 <__rwsem_wake+c4/dc>
18: 0e006b45 jal 801ad14 <_PC+0x801ad14> 90029b64 <END_OF_CODE+7e94cd0/????>
Code; 8800ee6c <__rwsem_wake+c8/dc>
1c: 24060000 li $a2,0
0001 0a003b85
2 warnings issued. Results may not be reliable.
next prev parent reply other threads:[~2001-06-13 11:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-10 22:03 Kernel crash on boot with current cvs (todays) Florian Lohoff
2001-06-11 3:53 ` Keith Owens
2001-06-11 19:12 ` Florian Lohoff
2001-06-12 1:01 ` Maciej W. Rozycki
2001-06-12 1:01 ` Keith M Wesolowski
2001-06-12 1:22 ` Maciej W. Rozycki
2001-06-12 2:05 ` Keith Owens
2001-06-11 4:42 ` Ralf Baechle
2001-06-11 14:50 ` Raoul Borenius
2001-06-12 10:09 ` Florian Lohoff
2001-06-12 11:53 ` Ralf Baechle
2001-06-12 16:37 ` H . J . Lu
[not found] ` <20010613100602.A17124@bunny.shuttle.de>
2001-06-13 10:56 ` Florian Lohoff
2001-06-13 11:34 ` Keith Owens
2001-06-13 12:05 ` Ralf Baechle
2001-06-13 12:19 ` ksymoops changes for mips (was Kernel crash on boot with current cvs) Keith Owens
2001-06-16 9:22 ` Ralf Baechle
2001-06-27 2:21 ` ksymoops changes for mips Keith Owens
2001-06-28 14:32 ` Thiemo Seufer
2001-07-31 3:57 ` Keith Owens
2001-07-31 4:30 ` Keith Owens
2001-08-03 6:10 ` Keith Owens
2001-08-03 10:07 ` Thiemo Seufer
2001-06-13 13:44 ` Kernel crash on boot with current cvs (todays) Maciej W. Rozycki
2001-06-13 14:07 ` Keith Owens
2001-06-13 15:08 ` Maciej W. Rozycki
2001-06-16 9:24 ` Ralf Baechle
2001-06-13 11:37 ` Raoul Borenius [this message]
2001-06-13 11:46 ` Keith Owens
2001-06-13 11:46 ` Keith Owens
2001-06-13 13:16 ` Raoul Borenius
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=20010613133751.A18749@bunny.shuttle.de \
--to=borenius@shuttle.de \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.com \
/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