Resume fails when using NoDRI

Bug #235278 reported by Pirouette Cacahuète
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Setting the NoDRI option in xorg.conf makes resuming from disk failing.

This was verified in 2.6.24-16-generic and 2.6.24-17-generic. Both ends up with a marroon-like screen (instead of the blue-one from Blubuntu), and machine seems to be frezeed. Trying to use a virtual console to login and reboot, I end up getting the caps lock's LED to blink, which means kernel panic (but no video to confirm).

I can't check if it's related to i915 driver, but I'm using this one (on an Intel 945GM chipset). Laptop model is Toshiba Satellite Pro A100-PSAAA. Resume works like a charm in 2.6.24-16-generic (not -17-generic, due to general resume regression :) as reported in bug 226279), when using the DRI.

This is not really grave, but it's strange.

Tags: cft-2.6.27
Revision history for this message
Nick Ellery (nick.ellery) wrote :

Hi, and thanks for reporting this bug. Please see the ACPI debugging page here, and post your results in seperate attachments.
https://wiki.ubuntu.com/DebuggingACPI

Revision history for this message
Nick Ellery (nick.ellery) wrote :

Note: scroll down to the 'Filing a bug report' section, and post those results.

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

Correct package

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

Here is the informations needed from ACPI, according to the wiki's page you pointed.

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

And now, ACPI !

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

Here is the full kern.log. Contains both failed and successfull resume.

You can see failure on May 26th, around 5pm (17:49-17:51)

Revision history for this message
Nick Ellery (nick.ellery) wrote :

Thanks for your report.

Revision history for this message
Nick Ellery (nick.ellery) wrote :

Bug confirmed and assigned to Kernel ACPI team.

Changed in linux:
assignee: nobody → ubuntu-kernel-acpi
status: Incomplete → Confirmed
Changed in linux:
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Ralph Janke (txwikinger) wrote :

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

Changed in linux:
status: Triaged → Incomplete
Revision history for this message
Javier Jardón (jjardon) wrote :

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:
status: Incomplete → Invalid
Curtis Hovey (sinzui)
Changed in linux (Ubuntu):
assignee: Registry Administrators (registry) → nobody
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.