Kernel panic on boot if SMP (ASUS M3A-H/HDMI)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
High
|
|||
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Hardy |
Fix Released
|
Medium
|
Stefan Bader | ||
Intrepid |
Fix Released
|
Medium
|
Stefan Bader |
Bug Description
SRU Justification:
Impact: The BIOS is expected to clear the SYSCFG[
after fixed MTRRs are configured. Some BIOSes do not clear SYSCFG[
Fix: Attached patch from upstream which is included in Jaunty and has been verified to help on Intrepid too.
Testcase: see bug report.
---
Binary package hint: linux-image-
Latest working kernel version: Doesn't work with any ubuntu versions of the kernel that I know of. Latest tried is 2.6.26-7-server. Does apparently work with the latest official stable 2.6.24.7 linux mainline kernel on a down-cored Phenom CPU according to http://
Earliest failing kernel version: The earliest failing version that I know about is 2.6.24-19-server. Have also tried a linux-image-generic kernel.
Distribution: Ubuntu 8.10
Hardware Environment: ASUS M3A-H/HDMI, 4GB RAM, AMD PHENOM X3 8750, 4xSATA, 256MB Radeon 2400 PRO PCI Express.
Software Environment: Ubuntu 64bit server edition. Using the latest available bios update (Version 1001)
Problem Description: When not using acpi=off or acpi=ht, the system goes straight into kernel panic. This occurs on or after installation.
Steps to reproduce: Use the same hardware set-up as me. Boot into ubuntu.
Note: I have also reported this as a mainline linux bug and the full history and a lot of information (dmesg output, acpidump output, kernel panic screen shots etc.) can be found here: http://
Related branches
description: | updated |
Changed in linux: | |
status: | Unknown → Incomplete |
Changed in linux: | |
status: | Incomplete → Confirmed |
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux: | |
status: | Confirmed → Invalid |
Changed in linux: | |
status: | Unknown → In Progress |
Changed in linux: | |
status: | In Progress → Confirmed |
Changed in linux: | |
status: | Confirmed → Fix Released |
Changed in linux (Ubuntu Hardy): | |
assignee: | nobody → stefan-bader-canonical |
status: | New → In Progress |
Changed in linux (Ubuntu Intrepid): | |
assignee: | nobody → stefan-bader-canonical |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
assignee: | intuitivenipple → nobody |
Changed in linux: | |
importance: | Undecided → Medium |
importance: | Undecided → Medium |
tags: | added: hw-specific |
Changed in linux: | |
importance: | Unknown → High |
Hi Paul,
Thanks for the report. Ubuntu tries to keep their kernel as close to what the upstream kernel has as possible. So a bug in the upstream kernel is a bug in our kernel. It'd be great if you'd be willing to continue to work with the upstream developers if possible. In the near future we're hoping to try to provide an upstream vanilla kernel package for our users to help with reporting bugs upstream but for now you will have to build the upstream kernel manually. It hopefully is a simple process which we have documented - https:/ /wiki.ubuntu. com/KernelTeam/ GitKernelBuild . If you wouldn't mind building the upstream kernel and testing that would be great.