Hibernation failed with: failed to set xfermode

[Marc Tardif]

I'm running Ubuntu 6.10 installed from edgy-alternate-i386, built on 20061009. The installation process went well but, when I select System -> Quit... -> Hibernate, then the screen goes blank and I get the following errors:

[17294614.840000] ata1: failed to set xfermode (err_mask=0x4)
[17294644.844000] ata2: failed to set xfermode (err_maks=0x4)
[17294674.844000] ata3: failed to set xfermode (err_maks=0x4)
...
[17294680.136000] Buffer I/O error on device sda1, logical block 28316
[17294680.136000] Aborting journal on device sda1
...

Then, the machine simply doesn't do anything and never shuts down. Since the error messages seemed to indicate a problem with /dev/sda1, I ran fsck but that returned:

/dev/sda1: recovering journal
/dev/sda1: clean, 132436/19152896 files, 1215535/38304976 blocks

So, I am attaching the output of lspci and lshal in the hope this information might prove to be useful.

[Marc Tardif (cr3)]

By the way, hibernation works quite well for the same release on different hardware. So, it would be relevant to specify that I am using a Dell Precision 380:

http://www.dell.com/content/products/productdetails.aspx/precn_380?c=us&l=en&s=biz&cs=555

If you need more hardware details, please don't hesitate to let me know.

[Matt Zimmerman (mdz)]

Marc, this looks like a kernel bug, so I'm reassigning it. In general, if you're uncertain about which package your bug belongs to, you should leave that field blank. 'hibernate' is a random package in universe which has nothing to do with the hibernation support in Ubuntu, and bugs filed against it are unlikely to get attention

[John Vivirito (gnomefreak)]

Matt i think i changed it. I think i got this and another bug mixed up on the packages while i was going through the no package assigned bugs. sorry for the confusion

[Marc Tardif (cr3)]

This bug is still appearing on the same hardware when running Ubuntu 6.10 installed from edgy-alternate-i386, built on 20061024.1.

[sedd (sedillard)]

I get the same errors on an hp nw9440 when resuming from suspend.

[Oleksij Rempel (olerem)]

Is it still reproducible on gutsy?

[wolfger (wolfger)]

5 months without a response. Is anybody working on this?

[Sergio Zanchetta (primes2h)]

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.

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.

[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.

[Ralph Janke (txwikinger)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.