Hibernation on Gutsy Tribe-2 hangs on "Power down" on D3C5105 motherboard

Bug #123071 reported by Marc Tardif
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.22 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I'm running Gutsy Tribe-2 on an Intel D3C5105 motherboard. When selecting the Hibernation button from the Quit menu, I get several usb related messages on the console and the last line says:

  [76959.181279] Power down.

The expected behavior is for the machine to power down by itself.

Tags: hwct
Revision history for this message
Marc Tardif (cr3) wrote :

Apologies, the bug is actually for an Intel D3C5105 motherboard.

Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Marc Tardif (cr3) wrote :
Marc Tardif (cr3)
description: updated
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

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!

Changed in linux-source-2.6.22:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote :

The output of 'sudo dmidecode' would be helpful also.

Changed in linux-source-2.6.22:
assignee: nobody → brian-murray
Changed in linux-source-2.6.22:
assignee: brian-murray → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-source-2.6.22 (Ubuntu) because there has been no activity for 60 days.]

Revision history for this message
Marc Tardif (cr3) wrote :

Apologies for the very late response. I have tested again with beta and I am still experiencing the same problem. I suspect this might be a limitation of the BIOS.

Please find the requested files attached below.

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
Marc Tardif (cr3) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

I'm not positive but it looks like there may be a newer version of the BIOS available for this system at:

http://downloadcenter.intel.com/Filter_Results.aspx?strTypes=all&ProductID=2373&OSFullname=OS+Independent&strOSs=38

If that is in fact a newer BIOS could please up date to it and report back?

Changed in linux-source-2.6.22:
status: Invalid → Incomplete
Revision history for this message
wolfger (wolfger) wrote :

5 months with no response. 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!

Changed in linux-source-2.6.22:
status: Incomplete → Invalid
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.