From: "Elliot Mackenzie" <macka@adixein.com>
To: "'Randy.Dunlap'" <rddunlap@osdl.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: PROBLEM: Panic booting from USB disk in ioremap.c (line 81)
Date: Sat, 21 Feb 2004 10:11:24 +1000 [thread overview]
Message-ID: <001301c3f80f$3ebbf890$4301a8c0@waverunner> (raw)
In-Reply-To: <20040220113031.0414ff65.rddunlap@osdl.org>
OK, I have done that, and I recompiled an identical kernel with spinlock
support (first incarnation did not have it).
Files on syslinux USB disk include vmlinuz (2.6.3), initrd and syslinux
config.
Cheers,
Elliot.
Now we get this:
==========================
Calling initcall 0xc03f7e19
Calling initcall 0xc03f819c
Calling initcall 0xc03f1e7c
Calling initcall 0xc03e7084
Calling initcall 0xc03e7101
Calling initcall 0xc03e90e2
remap_area_pages BUG: address=0xce800000, size=0xedeb0000,
end=0xbc6b0000
Call Trace:
[<c0119318>] remap_area_pges+0x210/0x21d
[<c0149169>] get_vm_area+0x32/0x36
[<c01193ff>] __ioremap+0xda/0x104
[<c03e9249>] sbf_init+0x167/0x180
[<c03e46f1>] do_init_calls+0x28/0x93
[<c03e90e2>] sbf_init+0x0/0x180
[<c012ca54>] init_workqueues+0xf/0x27
[<c01050bc>] init+0x30/0x134
[<c010508c>] init+0x0/0x134
[<c0109255>] kernel_thread_helper+0x5/0xb
------------[ cut here ]------------
kernel BUG at arch/i386/mm/ioremap.c:84!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c0119318>] Not tainted
EFLAGS: 00010292
EIP is at remap_area_pages+0x210/0x21d
eax: c0000001 ebx: edeb0000 ecx: c0369a50 edx: 00000282
esi: 0dffc0000 edi: ce800000 ebp: 00000000 esp: cde55f3c
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, theadinfo=cde54000 task=cdfb3900)
Stack: c03250e0 ce800000 edeb0000 bc6b0000 cdffb100 000000d0 c0101cec
edeb0000 0dffc000 bc6b0000 c0101ce8 c0149169 edeb0000 0dffc000 ce800000
00000000 c01193ff ce800000 3f7fc000 edeb0000 00000000 00000000 00000024
ce800000
Call Trace:
[<c0149169>] get_vm_area+0x32/0x36
[<c01193ff>] __ioremap+0xda/0x104
[<c03e9249>] sbf_init+0x167/0x180
[<c03e46f1>] do_init_calls+0x28/0x93
[<c03e90e2>] sbf_init+0x0/0x180
[<c012ca54>] init_workqueues+0xf/0x27
[<c01050bc>] init+0x30/0x134
[<c010508c>] init+0x0/0x134
[<c0109255>] kernel_thread_helper+0x5/0xb
Code: 0f 0b 54 00 ab 4d 32 c0 e9 1d fe ff ff 83 ec 20 89 5c 24 10
<0>Kernel panic: Attempted to kill init!
==========================
<snip>
|
| The call trace must be missing some helpful info, then.
| I say that only because the data supplied does not look usb-device
| specific.
| Please apply the patch below (for 2.6.3) and reboot that kernel
| with "initcall_debug" added to the kernel boot command line,
| and send the resulting (failing) output back to us.
|
| --
| ~Randy
<snip>
next prev parent reply other threads:[~2004-02-21 0:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 15:37 PROBLEM: Panic booting from USB disk in ioremap.c (line 81) Elliot Mackenzie
2004-02-20 19:30 ` Randy.Dunlap
2004-02-21 0:11 ` Elliot Mackenzie [this message]
2004-02-21 0:11 ` Randy.Dunlap
2004-02-21 0:25 ` Elliot Mackenzie
2004-02-21 0:19 ` Randy.Dunlap
2004-02-21 0:36 ` Elliot Mackenzie
-- strict thread matches above, loose matches on Subject: below --
2004-02-21 5:31 Randy.Dunlap
2004-02-22 12:02 ` Elliot Mackenzie
2004-02-26 0:03 ` Randy.Dunlap
[not found] <A6974D8E5F98D511BB910002A50A6647615F32F8@hdsmsx402.hd.intel.com>
2004-02-26 8:11 ` Len Brown
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='001301c3f80f$3ebbf890$4301a8c0@waverunner' \
--to=macka@adixein.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox