kernel panic - not syncing (linux-image-2.6.17-9-generic)

Bug #61877 reported by Niall Creech
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.17-9-generic

kernel panics on boot. last 4 lines seen are

[15.826112] RIP <ffffffff803847247> {agp_generic_create_gatt_table+100} RSP <ffff81003f181df8>
[15.826216] CR2 0000000000000008
[15.826252] <0> kernel panic - not syncing: Attempted to kill init!
[15.826318]

Sorry, no screenshot.
Possible duplicate bug (linux-image-2.6.17-8)
https://launchpad.net/distros/ubuntu/+bug/61848

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

just to add, linux-image-2.6.17-8-generic works fine for me, the breakage only occurs with the -9 kernel

Revision history for this message
tamasrs (tamasrs) wrote :

Same here, 64bit AMD 248 2x VIA Chipset.
No log..
linux-image-2.6.17-8-generic works fine

TRS.

Revision history for this message
tamasrs (tamasrs) wrote :

Screen shot :)

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

just to confirm that the screenshot the exact same panic i get on my amd64-k8 chip

Revision history for this message
Jose Bernardo (bernardo-bandos) wrote :

Seems the same panic I get on my AMD64 (MSI NEO K8T 2 motherboard, VIA K8 chipset).

Revision history for this message
NoWhereMan (e.vacchi) (uncommonnonsense) wrote :

while the problem is probably different (no 64bit processor here) I still get the error reported here https://launchpad.net/distros/ubuntu/+bug/61848 with this -9 update, so this kernel build(s) must be buggy

Revision history for this message
Helmut Duregger (helmutduregger) wrote :

I have the same panic, also on AMD64 (MSI NEO K8T 2 motherboard, VIA K8 chipset, AMI BIOS).

linux-image-2.6.17-7-generic works fine aswell.

Revision history for this message
Quim Calpe (quimcalpe) wrote :

Same here, but with a AMD XP 2200+, so no 64bit processor here. The same happened with 2.6.17-8-generic kernel, I just waited for the new kernel update(2.6.17-9-generic), but it crashes the same way.

Kernel linux-image-2.6.17-7-generic works fine thought...

Revision history for this message
NoWhereMan (e.vacchi) (uncommonnonsense) wrote :

@quim calpe: is the kernel panic you get the one linked here, or the message is more like the one in https://launchpad.net/distros/ubuntu/+bug/61848 ? in this case add a comment there, too

at least i'm not alone...

Revision history for this message
Quim Calpe (quimcalpe) wrote :

@NoWhereMan: You are right, the kernel panic I'm getting is almost the same as you posted in 61848, so I'm Going to comment there also.

Revision history for this message
Derry Geuther (ryther) wrote :

linux-image-2.6.17-9-generic_amd64 on MSI K8TM: same kernel panic. Seems to be another issue with the infamous Via-based-chipset K8T mobo's...?

Revision history for this message
tamasrs (tamasrs) wrote :

linux-image-2.6.17-10-generic is out and working, khmmm, but no fglrx (agp port problem... i guess)

TRS

Revision history for this message
Helmut Duregger (helmutduregger) wrote :

linux-image-2.6.17-10-generic works for me too.

I get this now though:

[ 89.413798] ACPI: Invalid package argument
[ 89.413802] ACPI Exception (acpi_processor-0275): AE_BAD_PARAMETER, Invalid _PSS data [20060707]
[ 89.416526] powernow-k8: 0 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV)
[ 89.416529] powernow-k8: 1 : fid 0xa (1800 MHz), vid 0xa (1300 mV)
[ 89.416531] powernow-k8: 2 : fid 0xc (2000 MHz), vid 0x6 (1400 mV)
[ 89.416534] powernow-k8: 3 : fid 0xe (2200 MHz), vid 0x2 (1500 mV)

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

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!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.