kvm-amd causing kernel panic

[Dulmandakh Sukhbaatar]

when I try to load kvm-amd module, it causes kernel panic on Opteron 2214 using Ubuntu feisty amd64 version. Contact me if any further information needed.

[Chris Halse Rogers (raof)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

[Dulmandakh Sukhbaatar (dulmandakh)]

Thanks. I've attached file required to fix kernel bug.

[Dulmandakh Sukhbaatar (dulmandakh)]

Sorry, I've looked how to attach more file at once, but no luck.

[Chris Halse Rogers (raof)]

Can you attach the log generated by "dmesg > dmesg-after.log" after attempting to modprobe the kvm-amd module? If you can, that should contain useful information.

[Dulmandakh Sukhbaatar (dulmandakh)]

kernel panic prevents me doing anything on a server. How I can get dmesg log after kernel panic? If it is possible tell me how, and I'll send you info.

[Chris Halse Rogers (raof)]

You might want to try https://help.ubuntu.com/community/DebuggingSystemCrash , but don't worry if you can't get anything.

[Chris Halse Rogers (raof)]

As a last resort, if you have local access to the server you can attach a digital photograph of the terminal output spewed by the OOPS. You would need to modprobe kvm-amd at one of the VTs (Ctrl+Alt+F1). That should output the relevant oops data to the screen, which you can take a photo of.

Also if possible, it would be nice (but not essential) if you could try to reproduce the kernel oops with a Gutsy livecd (tribe 3 should be released soon). If that works, it should be simpler to backport the fix from the Gutsy kernel.

[Dulmandakh Sukhbaatar (dulmandakh)]

Now I'm attending GUADEC in Birmingham. When I'm back home I can try either photo or gutsy. Few days ago I visited Canonical office in London. Did you were there?

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. 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!

[Leann Ogasawara (leannogasawara)]

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.

[Michele Mangili (mangilimic)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!