From: Martin Michlmayr <tbm@cyrius.com>
To: linux-mips@linux-mips.org
Cc: manoj.ekbote@broadcom.com, mark.e.mason@broadcom.com
Subject: BigSur: oops loading ramdisk
Date: Sun, 25 Nov 2007 13:52:29 +0100 [thread overview]
Message-ID: <20071125125229.GJ20922@deprecation.cyrius.com> (raw)
With a 32 bit kernel (current git) on BigSur, I get an oops while
trying to load the ramdisk:
Linux version 2.6.24-rc3-g2ffbb837-dirty (tbm@em64t) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #4 Sun Nov 25 12:44:26 UTC 2007
...
RPC: Registered tcp transport module.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (cramfs filesystem) readonly.
Freeing unused kernel memory: 132k freed
CPU 0 Unable to handle kernel paging request at virtual address 00000000, epc == 802931b8, ra == 802965f4
Oops[#1]:
Cpu 0
$ 0 : 00000000 10001f00 00000000 00000000
$ 4 : 8ed01000 00000000 8f421df8 00000000
$ 8 : 80430000 8f472a6c 00000000 0000000e
$12 : 8f00603c ffffffff 00000000 00000084
$16 : 8f4a22c0 80440000 00500001 8ed01000
$20 : 00000002 8f0147a0 00000000 00000000
$24 : 00000003 000000cd
$28 : 8f420000 8f421da8 00000000 802965f4
Hi : 00000002
Lo : 82828285
epc : 802931b8 init_dev+0x8c/0x56c Not tainted
ra : 802965f4 tty_open+0x148/0x330
Status: 10001f03 KERNEL EXL IE
Cause : 00808008
BadVA : 00000000
PrId : 01041100 (SiByte SB1A)
Modules linked in:
Process swapper (pid: 1, threadinfo=8f420000, task=8f41f928)
Stack : 80178a60 00000003 804487e4 8ed01000 8f421dfc 00000000 8f4a22c0 80440000
00500001 00000001 00000002 8f0147a0 00000000 00000000 00000000 802965f4
8f006d28 00000000 8f421df8 00000000 8f006d28 00000000 00000000 8048ff20
8f006d28 8f4a22c0 8f4032a0 80173018 00000000 8f413000 ffffff9c 8017bb74
00000000 80435ba0 8f4a22c0 8f006d28 00000000 80172ef8 8016df8c 80430000
...
Call Trace:
[<802931b8>] init_dev+0x8c/0x56c
[<802965f4>] tty_open+0x148/0x330
[<80173018>] chrdev_open+0x120/0x178
[<8016df8c>] __dentry_open+0x104/0x210
[<8016e144>] nameidata_to_filp+0x30/0x54
[<8016e1a8>] do_filp_open+0x40/0x54
[<8016e220>] do_sys_open+0x64/0x114
[<80100448>] init_post+0x30/0xe8
[<80450874>] kernel_init+0x2e4/0x314
Code: 8c8200a0 00051880 00431021 <8c510000> 162000e2 00000000 8e64003c 10800009 24020002
Kernel panic - not syncing: Attempted to kill init!
Rebooting in 5 seconds..Passing control back to CFE...
--
Martin Michlmayr
http://www.cyrius.com/
next reply other threads:[~2007-11-25 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 12:52 Martin Michlmayr [this message]
2007-11-25 13:01 ` BigSur: oops loading ramdisk Martin Michlmayr
2007-11-26 14:45 ` Ralf Baechle
2007-11-26 16:17 ` Martin Michlmayr
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=20071125125229.GJ20922@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=linux-mips@linux-mips.org \
--cc=manoj.ekbote@broadcom.com \
--cc=mark.e.mason@broadcom.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