[Hewlett-Packard HP EliteBook 6930p] suspend/resume failure

Bug #420424 reported by Severin H
150
This bug affects 31 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
Nominated for Jaunty by tpkuester
Nominated for Karmic by TestDriveLinux

Bug Description

I use Karmic with the latest updates applied. I'll follow the steps described by Andres Mujica in https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/361988/comments/2 as soon as possible.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lantash 3480 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd4420000 irq 17'
   Mixer name : 'Analog Devices AD1984A'
   Components : 'HDA:11d4194a,103c30dc,00100400'
   Controls : 22
   Simple ctrls : 14
Date: Fri Aug 28 11:06:54 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=9327249a-231b-4d15-a232-fa320270e566
InterpreterPath: /usr/bin/python2.6
MachineType: Hewlett-Packard HP EliteBook 6930p
Package: linux-image-2.6.31-8-generic 2.6.31-8.28
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-8-generic root=UUID=fbab4c4c-8eee-4edd-ac28-678e8e8df3ce ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
RelatedPackageVersions: linux-firmware 1.16
SourcePackage: linux
Tags: resume suspend
Title: [Hewlett-Packard HP EliteBook 6930p] suspend/resume failure
Uname: Linux 2.6.31-8-generic x86_64
UserGroups:

dmi.bios.date: 07/15/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PCD Ver. F.05
dmi.board.name: 30DC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 87.21
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCDVer.F.05:bd07/15/2008:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.05:rvnHewlett-Packard:rn30DC:rvrKBCVersion87.21:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 6930p
dmi.product.version: F.05
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Severin H (severinh) wrote :
Revision history for this message
Jaap Haitsma (jaap) wrote :

Still happening with linux-image-2.6.31-14-generic

Revision history for this message
TestDriveLinux (testdrivelinux) wrote :

This bug is reproducible and affects me too (updated to latest version on 18th Oct 2009). Suggest this is a regression as suspend/resume worked correctly on same hardware using Jaunty.

The laptop appears to suspend okay but on resume the screen is on but apart from the mouse cursor which moves and is controllable by the trackpad the screen is blank. Have to turn off laptop by holding power key as no other key combination has any effect.

uname -a
Linux ubuntu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Jaap Haitsma (jaap) wrote : Re: [Bug 420424] Re: [Hewlett-Packard HP EliteBook 6930p] suspend/resume failure
Download full text (3.6 KiB)

NOTE it worked a while ago in Karmic. It worked on the 27th of
September because then I blogged about faster resume from suspend

On Sun, Oct 18, 2009 at 16:13, TestDriveLinux
<email address hidden> wrote:
> This bug is reproducible and affects me too (updated to latest version
> on 18th Oct 2009). Suggest this is a regression as suspend/resume worked
> correctly on same hardware using Jaunty.
>
> The laptop appears to suspend okay but on resume the screen is on but
> apart from the mouse cursor which moves and is controllable by the
> trackpad the screen is blank. Have to turn off laptop by holding power
> key as no other key combination has any effect.
>
> uname -a
> Linux ubuntu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux
>
>
> ** Changed in: linux (Ubuntu)
>       Status: New => Confirmed
>
> --
> [Hewlett-Packard HP EliteBook 6930p] suspend/resume failure
> https://bugs.launchpad.net/bugs/420424
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Confirmed
>
> Bug description:
> I use Karmic with the latest updates applied. I'll follow the steps described by Andres Mujica in https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/361988/comments/2 as soon as possible.
>
> ProblemType: KernelOops
> Annotation: This occured during a previous suspend and prevented it from resuming properly.
> AplayDevices:
>  **** List of PLAYBACK Hardware Devices ****
>  card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> Architecture: amd64
> ArecordDevices:
>  **** List of CAPTURE Hardware Devices ****
>  card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
>   Subdevices: 2/2
>   Subdevice #0: subdevice #0
>   Subdevice #1: subdevice #1
> AudioDevicesInUse:
>  USER        PID ACCESS COMMAND
>  /dev/snd/controlC0:  lantash    3480 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
>  Card hw:0 'Intel'/'HDA Intel at 0xd4420000 irq 17'
>   Mixer name   : 'Analog Devices AD1984A'
>   Components   : 'HDA:11d4194a,103c30dc,00100400'
>   Controls      : 22
>   Simple ctrls  : 14
> Date: Fri Aug 28 11:06:54 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/share/apport/apportcheckresume
> Failure: suspend/resume
> HibernationDevice: RESUME=UUID=9327249a-231b-4d15-a232-fa320270e566
> InterpreterPath: /usr/bin/python2.6
> MachineType: Hewlett-Packard HP EliteBook 6930p
> Package: linux-image-2.6.31-8-generic 2.6.31-8.28
> PccardctlIdent:
>
> PccardctlStatus:
>
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-8-generic root=UUID=fbab4c4c-8eee-4edd-ac28-678e8e8df3ce ro quiet splash
> ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
> ProcEnviron: PATH=(custom, no user)
> ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
> RelatedPackageVersions: linux-firmware 1.16
> SourcePackage: linux
> Tags: resume suspend
> Title: [Hewlett-Packard HP EliteBook 6930p] suspend/resume failure
> Uname: Linux 2.6.31-8-generic x86_64
> UserGroups:
>
> dmi.bios.date: 07/15/2008
> dmi.bios.vendor: Hewlett-Packard
> dmi.bios.versi...

Read more...

Revision history for this message
Severin H (severinh) wrote :

Am I right that following the instructions at https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/361988/comments/2 (installing the latest upstream mainline kernel and gathering information) would still be helpful for tracking this bug down?

If so, I'll try to do my best - now that my HP 6930p laptop has finally been repaired.

Revision history for this message
Yossi Ovadia (jabadia) wrote :

Still occurs on 23'rd update as well ( should match the RC release ).
:(

Revision history for this message
Jaap Haitsma (jaap) wrote :

Still happening 3 days before the release of Karmic. Hopefully we get
a kernel update before release, because this is a serious regression
compared to jaunty and it worked in Karmic several kernel releases ago

Revision history for this message
tpkuester (tpkuester) wrote :

Currently using Ubuntu 9.10 RC on a HP 6930p with up to date everything, no ATI drivers.

I also had this problem.

Reading around, I found someone who had the same problem, and noted about memory cards in the MMC slot.

After removing my MMC, the computer suspended successfully, but would not resume.

After blacklisting the ricoh_mmc mod the resume works (to some extent.)

Googling "ricoh_mmc suspend" shows that there are apparently some problems with this... It may be in the fixes.

This bug may also be related to #454831.

Hope this all helps.

Revision history for this message
Sasha Levin (sasha-comsleep) wrote :

Confirming that blacklisting 'ricoh_mmc' has fixed the sleep/resume bug, tested on several 6930p laptops.

Thanks tpkuester!

Revision history for this message
TestDriveLinux (testdrivelinux) wrote :

I'd be grateful if you provide some instructions on how to blacklist 'ricoh_mmc'.

Thanks

Revision history for this message
tpkuester (tpkuester) wrote :

First, open a terminal as root and type "rmmod ricoh_mmc". Try suspending your computer to see if it resumes ok. If it does, make the change permanent.

Run this command:
gksu gedit /etc/modprobe.d/blacklist.conf

Add this at the end of the file:

# Blacklisting until a bugfix comes out that
# lets me suspend my laptop
blacklist ricoh_mmc

Revision history for this message
TestDriveLinux (testdrivelinux) wrote :

Thanks for the instructions.

On the first go (sudo rmmod ricoh_mmc) it went into suspend and resumed fine. However the system became unstable and I could not launch any applications. I had to forcibly power off the laptop.

Trying the same thing again on the next boot, it unfortunately returned to the previous behavior (suspends fine but on resume the screen is blank apart from the mouse cursor). I'll try a few more times to see if there is any pattern and report back.

Revision history for this message
Falk (gammalget) wrote :

Confirming that blacklisting 'ricoh_mmc' has fixed the sleep/resume bug for me.
I have tried it a few times at it looks like it works.

Revision history for this message
cob (cobbjbc) wrote :

Seems to be working for me as well, since blacklisting ricoh_mmc.

Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote :

Blacklist ricoh_mmc had no effect for me and I made sure I rebooted and did `lsmod' to verify it was not loaded. No effect :-(

I'm using the ATI driver as I'm using an external monitor and when I upgraded to 9.04 the default driver was too slow. I tried to revert back to see if the driver could have an effect on the suspend/resume issue but I must have a wrong xorg.conf file because ubuntu would crash on startup.

Anything I could do for helping diagnose the issue?

Revision history for this message
msphix (msphix) wrote :

Backlisting ricoh_mmc worked for me.

Suspend and hibernation are working again which stopped after upgrade to Karmic.

Revision history for this message
tpkuester (tpkuester) wrote :

To those who have noted that blacklisting the driver helped fix the problem, are you currently on an EliteBook 6930p? Or are you using another operating system?

I'm trying to decide if this needs to be made into a more meaningful bug -- ie: "ricoh_mmc driver breaks suspend / resume"

Revision history for this message
Sasha Levin (sasha-comsleep) wrote :

Blacklisting ricoh_mmc solved the problem for me.

I'm on an EliteBook 6930p with Ubuntu 9.10.

Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : apport-collect data

AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: manus 3728 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd8420000 irq 17'
   Mixer name : 'Analog Devices AD1984A'
   Components : 'HDA:11d4194a,103c30dc,00100400 HDA:11c11040,103c1378,00100200'
   Controls : 22
   Simple ctrls : 14
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=02dde8ff-284d-41aa-9d96-645e80d8b2f7
MachineType: Hewlett-Packard HP EliteBook 6930p
NonfreeKernelModules: fglrx
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   product info: "RICOH", "Bay8Controller", "", ""
   manfid: 0x0000, 0x0000
   function: 254 (unknown)
PccardctlStatus:
 Socket 0:
   3.3V 16-bit PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcCmdLine: root=UUID=2097c4ff-b668-458d-a2ef-553f3c86cda1 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 SHELL=/usr/bin/tcsh
 LANG=C
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WpaSupplicantLog:

XsessionErrors:
 (gnome-panel:3783): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x1f1ac00
 (gnome-panel:3783): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x1f1ac00
 (polkit-gnome-authentication-agent-1:3809): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:3784): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:3783): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
dmi.bios.date: 07/15/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PCD Ver. F.05
dmi.board.name: 30DC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 87.21
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCDVer.F.05:bd07/15/2008:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.05:rvnHewlett-Packard:rn30DC:rvrKBCVersion87.21:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 6930p
dmi.product.version: F.05
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : AlsaDevices.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : BootDmesg.gz
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : Card0.Amixer.values.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : Card0.Codecs.codec.0.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : Card0.Codecs.codec.1.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : CurrentDmesg.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : IwConfig.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : Lspci.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : Lsusb.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : PciMultimedia.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : ProcCpuinfo.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : ProcInterrupts.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : ProcModules.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : UdevDb.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : UdevLog.txt
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote : WifiSyslog.gz
tags: added: apport-collected
Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote :

Just to say that disabling ricoh_mmc has no effect for me.

Revision history for this message
cob (cobbjbc) wrote :

tpkuester: I am using an EliteBook 6930p with Karmic installed. It was upgraded from Jaunty using the Update Manager.

Revision history for this message
Sasha Levin (sasha-comsleep) wrote :

Emmanuel, the ricoh_mmc module is showing up as a loaded module in the data you provided.

Are you sure it was properly disabled?

Revision history for this message
SteveLoughran (steve-loughran) wrote :

1. I am experiencing the same problem, again elitebook 6930p upgraded from Jaunty with 32-bit OS.
2. blacklisting ricoh_mmc did not make this problem go away; checked in proc/modules
3. disabling the slot in the BIOS doesn't help either
4. I do have the WWAN device in, and some other devices.

I'm going to drop to BIOS and disable the various peripherals I don't need. Failing that, try a clean install rather than an upgrade, and roll back to jaunty if that fails.

Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote :

I did have it disabled, but when it did not do anything I've restored it.

Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote :

some findings today. The original poster and myself are using 68PCD F.05 version of the bios. I've decided to upgrade to the latest version which is 68PCD F.13. After doing that it still failed. However after disabling ricoh_mmc suspend/resume seems to work (modulo the brightness that was set to the lowest value on resume). I'll have to try a few reboot suspend resume sequence to see if this works 100% of the time.

So for those for which disabling ricoh_mmc did not work, you may want to try the BIOS upgrade.

Revision history for this message
Simon N. (simon-ubuntu-sngs) wrote :

I can confirm this.
With old bios resume didn't work at all.
After upgrading to newest bios resume works with blacklisted ricoh_mmc.
After loading ricoh_mmc resume doesn't work any more.

Thanks Emmanuel, now suspend/resume is usable again.

Revision history for this message
snowlord (register-jaric) wrote :

I can confirm that removing ricoh_mmc solved this issue for me.

----
As an aside, note that in Jaunty resuming worked for me, but the X server always crashed when resuming after the laptop had slept for more than a short while, so it was useless anyway. There's a bug about that somewhere, and as far as I understood it, it was related to the Intel graphics driver.

(HP 6930p with Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07))

Revision history for this message
SteveLoughran (steve-loughran) wrote :

I'm doing the BIOS upgrade and will then try a clean OS install.

For people who dont have a copy of windows around to run the SP.exe that contains an installer exe that sticks a .ISO image into your filesystem, I have that .ISO safely extracted for reuse. I will not comment on the irony of needing a copy of a windows to get the "non windows" BIOS updater onto a CD, except to say that I am aware of the irony and cherish XP under VirtualBox for just such events.

Revision history for this message
SteveLoughran (steve-loughran) wrote :

-I can confirm, BIOS upgrade followed by clean install with mmc disabled means that laptop now suspends and resumes/. This implies two problems. Something in the BIOS that upgrading the BIOS fixes, something in the mmc controller. Both need to be fixed for your laptop to resume reliably.

Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote :

For the BIOS upgrade, you can get the FreeDOS bios update and stick it on a USB key. From the key it will do the upgrade without the need for Windows.

Revision history for this message
Vikas BN (vikas-bn) wrote :

suspend/resume works for me too after i remove ricoh_mmc module. It didn't work earlier.
System details:
HP Elitebook 6930p
Ubuntu 9.10
uname -r => 2.6.31-15-generic
latest updates installed.

Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

Blacklisting mmc_ricoh helped me too.

Revision history for this message
goto (gotolaunchpad) wrote :

Slightly off topic:

If I upgrade to a newer BIOS than my original (F.0B), the BIOS will stop seeing my HDD. I can still boot off a Gentoo Live CD and mount my HDD from it, but the BIOS can't directly boot from it. I wasted four hours trying to figure out what was wrong (switching between SATA and IDE compatibility, changing the BIOS boot order, disabling everything except the HDD in the BIOS, reinstalling grub, trying lilo instead of grub, running fsck, etc) before I finally downgraded to my original F.0B BIOS, which allowed the BIOS to see my HDD again.

Be grateful you can upgrade your BIOS. I wish I could go back to Thinkpads.

Revision history for this message
techman (lj-ekman) wrote :

If you do not want to blacklist the ricoh_mmc driver then you can use SUSPEND_MODULES.

Add SUSPEND_MODULES="ricoh_mmc" into /etc/pm/config.d/suspend_modules (create the file it if it does not exist)

Then the kernel will unload the module before suspending and reload the module when resuming.

tried it on ubuntu 9.10 with 2.6.31-14-generic i686.

Revision history for this message
Emmanuel Stapf [ES] (xumoqkn5d6or9iyw) wrote :

I've upgraded to an even more recent version of the BIOS (version F.18) in which HP stated having fixed a suspend issue for Fedora and found out that it also solves that issue too without having to suspend or disable the ricoh_mmc driver. I believe that the issue can now be closed if it works for others too.

Revision history for this message
Frantique (undernetangel) wrote :

Solution found:
Upgrade to latest BIOS, after add to /etc/default/acpi-support the ricoh_mmc module to MODULES="". It will look like this:
MODULES="ricoh_mmc"

That is all.

Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

The fix with /etc/default/acpi-support helps for latest F.18 firmware.
Though there is still problem suspending (laptop just hangs) if card is inserted when suspending, even with this workaround.

Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

Tested on Ubuntu 10.10 - works flawless without any need to use suspend_modules file or unloading ricoh_mmc kernel module for successful suspend.

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
Anton (feenstra) wrote :

Well, I've been having this very same problem for a long while (I don't remember when - but I just came across a post http://ubuntuforums.org/archive/index.php/t-1604695.html where they describe it first appearing in lucid - that sounds about right for me). So it was in lucid, maverick, natty, and now oneiric. Seems that at least one of those must be supported!

I'm habitually using dual screen and compositing windows manager (compiz), but turning that off (only for a little while) didn't seem to fix it.

As per the suggestion in #56, I've opened a new bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887171

To post a comment you must log in.