Crash during boot @ networking ...

[dominique]

I upgraded my kernel through kynaptic to k7 smp.

When I boot on this kernel, ubuntu crashes during the boot process at "Networking devices configuration". I have to hard reboot.

ASUS AV8 Deluxe
AMD x2 3800+
Wifi pci card : asus wl-130g

[Sitsofe Wheeler (sitsofe)]

Does caps lock continue to work?

Is there anything logs (e.g. /var/log/messages ) around the time the network card is loaded?

Could also see if it is possible to boot to runlevel 2 and then try starting the network initscript by hand?

If you know which modules are loaded, what happens if you try modprobing them by hand?

[dominique (1212dl)]

.yes, caps lock continues to work

I don't what means "to boot to runlevel 2", but I tried to boot in safe mod with the same result. I did it again to get the /var/log/messages :

Mar 5 21:57:46 localhost syslogd 1.4.1#17ubuntu3: restart.
Mar 5 21:57:47 localhost kernel: Inspecting /boot/System.map-2.6.12-10-386
Mar 5 21:57:47 localhost kernel: Loaded 29010 symbols from /boot/System.map-2.6.12-10-386.
Mar 5 21:57:47 localhost kernel: Symbols match kernel version 2.6.12.
Mar 5 21:57:47 localhost kernel: No module symbols loaded - kernel modules not enabled.
Mar 5 21:57:47 localhost kernel: 35.935101] Checking for popad bug... OK.
Mar 5 21:57:47 localhost kernel: [ 35.935237] checking if image is initramfs... it is
Mar 5 21:57:47 localhost kernel: [ 36.324833] Freeing initrd memory: 5171k freed
Mar 5 21:57:47 localhost kernel: [ 36.325424] ACPI: Looking for DSDT in initrd... not found!
Mar 5 21:57:47 localhost kernel: [ 36.368222] not found!
Mar 5 21:57:47 localhost kernel: [ 36.374919] ENABLING IO-APIC IRQs
Mar 5 21:57:47 localhost kernel: [ 36.375235] ..TIMER: vector=0x31 pin1=2 pin2=-1
Mar 5 21:57:47 localhost kernel: [ 36.486825] NET: Registered protocol family 16
Mar 5 21:57:47 localhost kernel: [ 36.486843] EISA bus registered
Mar 5 21:57:47 localhost kernel: [ 36.486846] ACPI: bus type pci registered
Mar 5 21:57:47 localhost kernel: [ 36.487187] PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
Mar 5 21:57:47 localhost kernel: [ 36.487193] PCI: Using configuration type 1
Mar 5 21:57:47 localhost kernel: [ 36.487196] mtrr: v2.0 (20020519)
Mar 5 21:57:47 localhost kernel: [ 36.487432] ACPI: Subsystem revision 20050729
Mar 5 21:57:47 localhost kernel: [ 36.493265] ACPI: Interpreter enabled
Mar 5 21:57:47 localhost kernel: [ 36.493268] ACPI: Using IOAPIC for interrupt routing
Mar 5 21:57:47 localhost kernel: [ 36.494128] ACPI: PCI Root Bridge [PCI0] (0000:00)
Mar 5 21:57:47 localhost kernel: [ 36.494131] PCI: Probing PCI hardware (bus 00)
Mar 5 21:57:47 localhost kernel: [ 36.494145] ACPI: Assume root bridge [\_SB_.PCI0] segment is 0
Mar 5 21:57:47 localhost kernel: [ 36.512262] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 14 15)
Mar 5 21:57:47 localhost kernel: [ 36.512455] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *10 11 14 15)
Mar 5 21:57:47 localhost kernel: [ 36.512664] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 10 11 14 15)
Mar 5 21:57:47 localhost kernel: [ 36.512856] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
Mar 5 21:57:47 localhost kernel: [ 36.513048] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
Mar 5 21:57:47 localhost kernel: [ 36.513240] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
Mar 5 21:57:47 localhost kernel: [ 36.513434] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
Mar 5 21:57:47 localhost kernel: [ 36.513642] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
Mar 5 21:57:47 localhost kernel: [ 36.513727] Linux Plug and Play Support v0.97 (c) Adam Belay
Mar 5 21:57:47 localh...

[dominique (1212dl)]

Hi,

Does the /var/log/messages that Isent help?

Would like me to do anything else that could help?

Thanks,

[dominique (1212dl)]

1) I recently used a wired connection, and once missed the grub selection, so thtat the computer booted by default on the smp kernel...and it didn't crash...nice surprise when I came back in my desk and saw that!
I tested further, and, amazingly enough, just the fact of being wired to the modem-router allows to boot without crash.

2) The bad news is that the behaviour of the system makes it unsuable :
- the system monitor shows that one of the core is always sollicitated very eraticly from 20 to 90% in kind of pics every second or so
- when trying to type in any apps, like gedit, it is impossible to set the keyboard to respnd normally; when typing a letter, one has 5 or more in a row, a kind of -aaaaaaa ddddd...- and it is linked to the sollicitation of the dual core by the system; each time the system goes through a pic of processing, this frantic keyboard behaviour appears.
- same black screen as when one don't use the computer for a while, but every few seconds when it starts!

3) I thought that if I unsintall the pci card for wireless connection , these weird behaviours would stop (and that I would finally be able to use the dual core processor). It didn't have any effects. I don't have any wireless card installed on this computer, but it still goes mad if I boot on smp kernel.

4) I tested a live cd of Dapper 64bits on my dual core computer, and everything works fine

5) I installed the wireless pci card on another single core processor desktop with Ubuntu dapper, and everything works fine.

I hope it helps!

[Sitsofe Wheeler (sitsofe)]

Hmm from that log report it looks like something keeps poking your DVD drive and is causing trouble. Along with the other things you have mentioned this does not sound a network/wifi problem at all (perhaps it's an interrupt problem?). Does booting with the noacpi or noapic options help?

[dominique (1212dl)]

I found the solution in this thread :

http://ubuntuforums.org/showthread.php?p=893372#post893372

Actually the noacpi or noapic wouldn't help, but "clock=pmtmr notsc" did the trick.

Hope all will go well on the upgrade to Dapper :)

Thanks,

[Matt Zimmerman (mdz)]

https://wiki.ubuntu.com/DebuggingSystemCrash

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

This bug has had no activity for a considerable period. This is a check to see if there is still interest in investigating this bug report.
Looks like a solution was found for this.

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Closing.