kernel panic linux-image-2.6.17-12-server

Bug #129196 reported by Jean Dumont
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.17-12-server

Dell Poweredge 2850
Intel Xeon 2.8GHz
RAM 2Gb
3 Disk (SCSI 70 Gb) RAID5 on Dell MegaRaid.
Distribution Ubuntu Edgy (Dapper would not install)

It works fine with linux-image-2.6.17-11-server, but with linux-image-2.6.17-12-server I got a kernel panic
I tried it with

Kernel command line: root=UUID=c8614365-abfd-4115-8e19-fa261ff91c4c ro (this is the default)

then with
Kernel command line: root=UUID=c8614365-abfd-4115-8e19-fa261ff91c4c ro noapic nolapic aic7xxx=no_reset

but no luck

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are currently reviewing bug reports regarding older kernels. Did this issue ever resolve itself after an update? Please let us know.

However, now that the 7.10 Gutsy Gibbon release of Ubuntu is out, we were wondering if you can still reproduce this issue. Could you please download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download and report back your results? If the issue is still present in the new release, please attach the following information:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Please be sure to attach each file as a separate attachment. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux-source-2.6.17:
status: New → Incomplete
Revision history for this message
Jean Dumont (jean-dumont) wrote :

I'll do that tonight on one of the server and see what happens (upgrading to gutsy), but I already have three Dell 2950 (it's not the same model) running gutsy(64) quite happily, so I'm quite confident that it will work.

For the rest the servers are up-to-date except for the kernel which is still 2.6.17-11, would it be usefull to boot 2.6.17-12 and try to send you the informations (but it is a kernel panic quite early in the boot process so I don't think anything is mounted yet)

Sorry for the broken report, I had not read the KernelTeamBugPolicies page up till now (oops)

Regards

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

It is most helpful to us if you are able to capture the kernel panic. Even a digital photo of the information you see would suffice. Thanks!

Revision history for this message
Jean Dumont (jean-dumont) wrote :

Sorry for taking so long, but I'm quite busy :-)

So I attach a file with the relevant portion of the logs
there are two files for each logfile one labelled 2.6.17-11.log and the other 2.6.17-12.log

In fact after much trying (which is why it took me so long) I finally succeded in getting to the boot prompt with 2.6.17-12 where the kernel panicked with something along the lines of "Aiie no syncing disabling interrupt"

In reviewing the logs I see that modules loading seems to be impossible with 2.6.17-12 can this be the cause of all that ?

If there is still something I can do to help, don't hesitate to ask, I wont upgrade this particular server to gutsy for at least a week (the other ones have been upgraded without a glitch and are perfectly fonctionnal (even with the Open Manager from Dell at least after you realised that you have to replace the sh link to point to bash rather than dash) )

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Changed in linux-source-2.6.17:
status: Incomplete → Invalid
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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