kernel panic

[Chak]

Ordinateur Fixe UNIKA. Lors du boot sur le CD d'Install Edgy Eft et/ou de la Mise à Jour de Dapper Drake vers Edgy Eft par Internet (FTP), ecran noir avec message suivant: "[88.253534] <0> kernel panic - not syncing : attempted to kill init!"

VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChr ome] Integrated Video;

Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8 237 AC97 Audio Controller

Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host B ridge

PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge

Communication controller: Agere Systems V.92 56K WinModem

IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT82 3x/A/C PIPC Bus Master IDE

Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II]

[Daniel T Chen (crimsun)]

It's doubtful this panic is caused by audio drivers. Can you attach the contents of /var/log/dmesg (if it was synced prior)?

[Chak (chakorama)]

I attach the contents of /var/log/dmesg =

[17179569.184000] Linux version 2.6.15-27-386 (buildd@terranova) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 PREEMPT Sat Sep 16 01:51:59 UTC 2006
[17179569.184000] BIOS-provided physical RAM map:
[17179569.184000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[17179569.184000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[17179569.184000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[17179569.184000] BIOS-e820: 0000000000100000 - 000000003f000000 (usable)
[17179569.184000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[17179569.184000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[17179569.184000] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
[17179569.184000] 112MB HIGHMEM available.
[17179569.184000] 896MB LOWMEM available.
[17179569.184000] On node 0 totalpages: 258048
[17179569.184000] DMA zone: 4096 pages, LIFO batch:0
[17179569.184000] DMA32 zone: 0 pages, LIFO batch:0
[17179569.184000] Normal zone: 225280 pages, LIFO batch:31
[17179569.184000] HighMem zone: 28672 pages, LIFO batch:7
[17179569.184000] DMI 2.3 present.
[17179569.184000] ACPI: Unable to locate RSDP
[17179569.184000] Allocating PCI resources starting at 40000000 (gap: 3f000000:bfc00000)
[17179569.184000] Built 1 zonelists
[17179569.184000] Kernel command line: root=/dev/hda1 ro quiet splash
[17179569.184000] Found and enabled local APIC!
[17179569.184000] mapped APIC to ffffd000 (fee00000)
[17179569.184000] Initializing CPU#0
[17179569.184000] PID hash table entries: 4096 (order: 12, 65536 bytes)
[ 0.000000] Detected 1992.286 MHz processor.
[ 14.188673] Using tsc for high-res timesource
[ 14.189876] Console: colour VGA+ 80x25
[ 14.191001] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 14.192699] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 14.227243] Memory: 1012648k/1032192k available (1976k kernel code, 18804k reserved, 606k data, 288k init, 114688k highmem)
[ 14.227248] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[ 14.303258] Calibrating delay using timer specific routine.. 3993.28 BogoMIPS (lpj=7986563)
[ 14.303298] Security Framework v1.0.0 initialized
[ 14.303310] SELinux: Disabled at boot.
[ 14.303325] Mount-cache hash table entries: 512
[ 14.303463] CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000
[ 14.303470] CPU: After vendor identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000
[ 14.303477] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[ 14.303480] CPU: L2 Cache: 256K (64 bytes/line)
[ 14.303482] CPU: After all inits, caps: 0383fbff c1cbfbff 00000000 00000420 00000000 00000000 00000000
[ 14.303502] mtrr: v2.0 (20020519)
[ 14.303506] CPU: AMD Sempron(tm) 2800+ stepping 00
[ 14.303510] Enabling fast FPU save and restore... done.
[ 14.303512] Enabling unmasked SIMD FPU exception support... done.
[ 14.303516] Checking 'hlt' instruction... OK.
[ 14.319520] checking if image is initramfs... it is
[ 14.850675] Freeing initrd...

[Jussi Kukkonen (jku)]

I suspect this may really be a duplicate of bug 63134 based on the panic and the hardware you have (although my french is pretty rusty). Can you check if the kernel panic screen mentions "quirk_via_abnormal_poweroff" like the screenshot in http://librarian.launchpad.net/4557331/DSC01924.JPG?

Using "acpi=force" as a boot option should also work as a work-around, if my hunch is correct.

Please mark this as duplicate (or comment here) if it looks like I'm right.

[Chak (chakorama)]

2007/1/5, Jussi Kukkonen <email address hidden>:
>
> I suspect this may really be a duplicate of bug 63134 based on the panic
> and the hardware you have (although my french is pretty rusty). Can you
> check if the kernel panic screen mentions "quirk_via_abnormal_poweroff"
> like the screenshot in
> http://librarian.launchpad.net/4557331/DSC01924.JPG?
>
> Using "acpi=force" as a boot option should also work as a work-around,
> if my hunch is correct.
>
> Please mark this as duplicate (or comment here) if it looks like I'm
> right.
>
> --
> kernel panic
> https://launchpad.net/bugs/69790
>

I don't have a good english and I don't understand very much your message
but I can tell you that the screenshot in
http://librarian.launchpad.net/4557331/DSC01924.JPG is the same than I had
on my screen of computer and I think than the error comes of the bad
assumption of responsibility of my materiel

<email address hidden>

[Jussi Kukkonen (jku)]

Hi chak, thanks for the comment

I'm going to mark this a duplicate of the other bug based on your message. I hope it gets fixed soon.

[Launchpad Janitor (janitor)]

The 18 month support period for Edgy Eft 6.10 has reached its end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!