crash while booting (4.4.10)


Forum: User Feedback
Topic: crash while booting (4.4.10)
started by: macias

Posted by macias on Jan. 31 2009,09:14
Dell Latitude D610, DSL 4.4.10, booted from CD or USB, does not matter, failsafe, no failsafe, also does not matter. Just after booting DSL crashes with message:

Unable to handle kernel null pointer reference at virtual address 000000 kernel panic: attempted to kill init!

Computer is OK, opensuse 10.1, 10.2, 10.3, 11.1, Kubuntu, windows, and some other live distros work just fine.

Posted by WDef on Jan. 31 2009,10:13
Please post lines of the screen output immediately before this error to improve the chances that someone might work out what is happening.

All this says by itself that there is an invalid pointer in kernel space somewhere.  Need to know during exactly what part of the boot this occurs.

Posted by macias on Jan. 31 2009,12:42
It happens almost immediately after pressing enter after seeing
boot:
prompt.

Ok, the visible lines before crash:
PCI: PCI BIOS revision 2.10 entry at 0xfb5be, last bus=10
PCI: Using configuration type 1
schedule_task(): keventd not started

and next is the mini-crash log with CPU registers, call trace, stack. Last line before kernel panic is:
Code: Bad EIP value.

Posted by WDef on Jan. 31 2009,14:11
Did you try booting with

>dsl acpi=off

It may be that your BIOS  is breaking acpi.

The standard advice is to start switching off as many things as possible using boot codes (eg nousb see wiki). (Though I thought if you were trying failsafe that already did that - are you sure you are entering boot codes correctly? There is no error message for an incorrect bootcode - I've long thought there should be).

You could try upgrading your BIOS as well if there is a new version.

Posted by macias on Feb. 01 2009,08:52
Quote (WDef @ Jan. 31 2009,14:11)
Did you try booting with

>dsl acpi=off

It may be that your BIOS  is breaking acpi.

The standard advice is to start switching off as many things as possible using boot codes (eg nousb see wiki). (Though I thought if you were trying failsafe that already did that - are you sure you are entering boot codes correctly? There is no error message for an incorrect bootcode - I've long thought there should be).

You could try upgrading your BIOS as well if there is a new version.

> Did you try booting with
> >dsl acpi=off

Indeed, this one works, i.e. does not crash. I don't know if it works fully because I am new to DSL, system booted up and fsck failed to run. I was able to run "dir" :-) for example.

> Though I thought if you were trying failsafe that already did that - > are you sure you are entering boot codes correctly?

I think so, bootscreen says to type
failsafe
so I did. This one crashes the computer as well, but at least the monitor is not black so I can read the messages. Without failsafe computer crashes with black screen.

> You could try upgrading your BIOS as well if there is a new
> version.

It is the newest :-)

So thank you for the help, however it would be great to fix this bug, as I said, DSL is the only one distro which crashes in such way. For example for slax all I do, is insert CD or USB, and after few seconds I have X running. In normal mode, not failsafe, or with acpi off.

Posted by WDef on Feb. 01 2009,10:41
This issue is likely to be a result somehow of the interaction between your BIOS, hardware and dsl's kernel.  Your other distros most likely have much more recent kernels that are playing better with your BIOS and hardware.
Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.