Rebooting DG965MQ after installing Feisty herd 3 from alternate stalls

Bug #82892 reported by Marc Tardif
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

After installing Feisty herd 3 from alternate on DG965MQ, the shutdown process stalls with the following error message:

Sending SIGKILL to all processes
Please stand by while rebooting the system.
[ 7673.970819] Synchronizing SCSI cache for disk sda:
[ 7674.066593] ACPI: PCI interrupt for device 0000:00:19.0 disabled
[ 7674.083237] Restarting system

Pressing ctrl-c doesn't have any effect, the machine needs to be reset.

Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Ben Collins (ben-collins) wrote :

Please make sure you have the latest BIOS. I know I saw issues on my 965 mobo before updating the BIOS.

Also, provide dmidecode.

Does this only happen after install, or is it any reboot? Can you try adding each of these to the kernel command line, then reboot, and try the next till one works:

reboot=h
reboot=s
reboot=b

Let me know which ones work, if any. The dmidecode will allow us to add a special entry for this specific motherboard to force the reboot mode that does work.

THanks

Changed in linux-source-2.6.20:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Marc Tardif (cr3) wrote :

Updating the BIOS to MQ1618P fixed the shutdown problem.

Revision history for this message
Kyle McMartin (kyle) wrote :

Rejecting since this isn't a kernel bug. Thanks for testing the BIOS update.

Changed in linux-source-2.6.20:
status: Needs Info → Rejected
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

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.