Bug#396469: Installation report: failed install on Toshiba Satellite
Here's the entire screen:
cc8394ed
*pde = 012ef067
*pte = 00000000
Oops: 0000
CPU: 0
EIP: 001:[<cc8394ed>] Not tainted
EFLAGS: 00010046
eax: 00000000 ebx: cc825b50 ecx: 00000000 edx: 00000cfc
esi: 000000ff edi: cbfe3400 ebp: 00000000 esp: cb19e84
ds: 0018 es: 0018 ss: 0018
Process modprobe (pid: 43, stackpage=cbf19000)
Stack: cbfe3400 00000040 cfb19eac cbfe34000
....
cc825aa0 00000001 0000000 cc81c29a cc825aa0
Call Trace: [<cc825b50>] [<cc825aa0>]...
...
[<c010820f>]
Code: 0f b6 9c 36 a1 9e 83 cc ba ff 00 00 00 d3 e2 d3 e3 0f b6 84
Segmentation fault
<6>Journalled Block Device driver loaded
pivot_root: No such file or directory
/sbin/init: 432: cannot open dev/console: No such file
Kernel panic: Attempted to kill init!
I just typed the first and last few numbers of thd Stack and Call Trace. There are more hex numbers where the ellipses are.
I'm not set up to boot over a null modem. Is there any way I can do an interactive boot and step through each piece as it's loading?
On 11/2/06, Frans Pop
<elendil@planet.nl> wrote:On Wednesday 01 November 2006 15:45, Bill McNeill wrote:
> The machine is hard hung, so I'm not in a debug shell and I can't page
> up to see what came before the segment fault. Unfortunately, I can't
> see what was loading before the fault: the very top of the screen is
> filled up with the register dump and whatnot.
OK. But still, the installer worked without problem, so we should be able
to solve this.
> I don't know how to figure out what was running when the seg fault
> occurred. I don't have a working shell so I can't read any log files,
> nor can I cat /proc/modules or ls /dev.
Please give us any information that you _can_ see on the screen. I know
that copying that manually is a pain, but without the info we cannot
help!
Another option, if the laptop has a serial port, you have another box to
connect it to and a null-modem cable, is to boot over serial console.
That should give you the full log of boot messages.
Cheers,
FJP
--
Bill McNeill
http://staff.washington.edu/billmcn/index.shtml
Reply to: