resume from suspend does not initialize the display on 2.6.35 kernel

[doesntcount]

Since upgrading to maverick, many people have reported being unable to resume from a suspended state.

Steps to reproduce:

Install Maverick.
Suspend.
Resume.
Notice that the resume worked except that video fails to initialize. Key strokes still work. You can CTRL-ALT-DELETE, for example.

See more details in this thread:

http://ubuntuforums.org/showthread.php?p=9929232&posted=1#post9929232

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic-pae 2.6.35-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nkaun 1580 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6fdc000 irq 46'
   Mixer name : 'IDT 92HD71B7X'
   Components : 'HDA:111d76b2,10280233,00100302'
   Controls : 20
   Simple ctrls : 14
Date: Thu Oct 7 22:05:18 2010
HibernationDevice: RESUME=UUID=8bde75bb-54d1-412f-a479-790d7ddb8d52
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Dell Inc. Latitude E6400
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=010a55ae-9aaa-440e-bf4a-243a37105193 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 05/06/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A24
dmi.board.name: 0X574R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA24:bd05/06/2010:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0X574R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.

[madbiologist (me-again)]

Try updating your BIOS to the A27 version available at http://supportapj.dell.com/support/downloads/driverslist.aspx?c=au&cs=audhs1&l=en&s=dhs&ServiceTag=&SystemID=LAT_E6400&os=WLH&osl=en&catid=&impid=

[madbiologist (me-again)]

Please also attach /var/log/pm-suspend.log.

[Greg (cebif)]

I have a very similar bug from upgrading 10.04-10.10 except the reporters result "Notice that the resume worked except that video fails to initialize. Key strokes still work. You can CTRL-ALT-DELETE" does not apply with me. None of the keys work. I have to press the reset button. Also the caps-lock and scroll-lock are flashing.
My mainboard is a: Abit KN7 SLI PCIE
Video card: Nvidia 7950 GT only single card
Was working perfectly on 10.04 lucid.

[Greg (cebif)]

Here is the pm-suspend.log for my case

[Greg (cebif)]

The attachment I just uploaded probably manly applies from Oct 14 today when I tried pm-suspend. There are other dates in it before I upgraded to 10.10 maverick. I also tried pm-suspend with the older kernel 2.6.32-25 in unbuntu 10.10 and it has same problem but worked alright in ubuntu 10.04 lucid.
Here is my hardware:
cebif@cebif-desktop:~$ lspci
00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:0a.0 Serial controller: Timedia Technology Co Ltd PCI2S550 (Dual 16550 UART) (rev 01)
05:00.0 VGA compatible controller: nVidia Corporation G71 [GeForce 7950 GT] (rev a1)
cebif@cebif-desktop:~$

[William Davis (hotshotdj)]

I just retested suspend on my system, and it works now. There was a kernel upgrade from 2.6.35-33 to 2.6.35-34 (currently using 2.6.35-22-generic #34-Ubuntu). Of course cpufreq is still stuck at the lowest step (800 Mhz) upon resume... but that is another bug.

@doesntcount - have you upgraded to the 2.6.35-34 kernel? Did it fix your problem?

@Greg - your problem sounds quite different from what doesntcount reported and I also experienced. It might warrant a separate bug report if one has not already been open.

[simcha (jtopinski)]

Changing:
GRUB_CMDLINE_LINUX=”"
to
GRUB_CMDLINE_LINUX=”acpi_sleep=nonvs"
in /etc/default/grub
and runing:
sudo update-grub

Has solved problem form me on Lenovo x200

[doesntcount (doesntcount)]

Attaching my pm-suspend.log. This log is for a suspend that was done immediately after upgrading to:

Linux <hostname> 2.6.35-22-generic-pae #34-Ubuntu SMP Sun Oct 10 11:03:48 UTC 2010 i686 GNU/Linux

I'm now running the latest bios for my dell latitude 6400. That didn't help.

I'll try the grub idea next.

[doesntcount (doesntcount)]

Nope, the GRUB_CMDLINE_LINUX change didn't solve anything.

Is there anything else I can provide?

[Jamie Krug (jamie-thekrugs)]

I have a System76 Serval Pro (SerP6) laptop running the latest Ubuntu 10.10 Maverick 64-bit.

Suspend/resume works fine most of the time, but occasionally I see the blank screen upon resume, while all other expected lights are on--it's as if it has resumed, but I can see nothing and no key strokes seem to do anything.

I'm trying the GRUB_CMDLINE_LINUX="acpi_sleep=nonvs" change to /etc/default/grub (and have run `sudo update-grub`) and will report back any news.

[FreeMinded (pascal-planetmages)]

I have a Lenovo S10 with Kubuntu 10.10 and I'm having this suspend issue. Computer goes to sleep as you would expect, but doesn't wake up from it. Screen stays black (the other light go on as if everything went well). No reaction to key strokes any more.
The GRUB_CMDLINE_LINUX="acpi_sleep=nonvs" didn't fix it.
Is there another workaround or fix?

BTW: This issue started after some Kernel update while still on Kubuntu 10.04. Before suspend was working flawlessly.

[Jamie Krug (jamie-thekrugs)]

I'm pretty sure this problem only manifests itself if I suspend or resume while my SerP6 laptop is running on battery power. I'm fairly certain that I've never had a problem on suspend or resume if I'm always connected to AC power, but that's obviously hardly ideal with a laptop.

That said, I can't immediately reproduce the problem--it seems to be just every 3 or 4 times, at suspend or resume, on battery power (or switching from on or off battery power), that I get power but a blank screen and must hard reboot.

If anyone can suggest what logs or other reporting I can provide to try to get some movement around this bug, I'm very eager to see it go away.

[doesntcount (doesntcount)]

My problem had nothing to do with battery power. It would fail to resume
100% of the time, regardless of battery power (even with AC power).

On Sun, Nov 7, 2010 at 10:24 PM, Jamie Krug <email address hidden>wrote:

> I'm pretty sure this problem only manifests itself if I suspend or
> resume while my SerP6 laptop is running on battery power. I'm fairly
> certain that I've never had a problem on suspend or resume if I'm always
> connected to AC power, but that's obviously hardly ideal with a laptop.
>
> That said, I can't immediately reproduce the problem--it seems to be
> just every 3 or 4 times, at suspend or resume, on battery power (or
> switching from on or off battery power), that I get power but a blank
> screen and must hard reboot.
>
> If anyone can suggest what logs or other reporting I can provide to try
> to get some movement around this bug, I'm very eager to see it go away.
>
> --
> resume from suspend does not initialize the display on 2.6.35 kernel
> https://bugs.launchpad.net/bugs/656631
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: New
>
> Bug description:
> Since upgrading to maverick, many people have reported being unable to
> resume from a suspended state.
>
> Steps to reproduce:
>
> Install Maverick.
> Suspend.
> Resume.
> Notice that the resume worked except that video fails to initialize. Key
> strokes still work. You can CTRL-ALT-DELETE, for example.
>
> See more details in this thread:
>
> http://ubuntuforums.org/showthread.php?p=9929232&posted=1#post9929232
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: linux-image-2.6.35-22-generic-pae 2.6.35-22.33
> Regression: Yes
> Reproducible: Yes
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4
> Uname: Linux 2.6.35-22-generic-pae i686
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> AplayDevices:
> **** List of PLAYBACK Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> Architecture: i386
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
> Subdevices: 2/2
> Subdevice #0: subdevice #0
> Subdevice #1: subdevice #1
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: nkaun 1580 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xf6fdc000 irq 46'
> Mixer name : 'IDT 92HD71B7X'
> Components : 'HDA:111d76b2,10280233,00100302'
> Controls : 20
> Simple ctrls : 14
> Date: Thu Oct 7 22:05:18 2010
> HibernationDevice: RESUME=UUID=8bde75bb-54d1-412f-a479-790d7ddb8d52
> InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
> MachineType: Dell Inc. Latitude E6400
> PccardctlIdent:
> Socket 0:
> no product info available
> PccardctlStatus:
> Socket 0:
> no card
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae
> root=UUID=010a55ae-9aaa-440e-bf4a-243a37105193 ro quiet splash
> ProcEnviron:
> LANG=en_...

[Michal (mikeos)]

Jame Krug: i bet you must have a Dell Latitude E6410 with nVidia and Intel Core i7 2.66GHz. Maybe the GPU does not matter. I spend over 3 weeks analysing the problem. The result is evident: it's not about Ubuntu (in Windows, yes being desperate I installed Win7 on a different HDD to test out, the problem is the same), it's not about Mainboard (Dell replaced my MB), it's not about RAM type (I tested with different modules of different sizes), not even about HDD (i tested with SSD and classical HDD), not about PCI peripherals (i removed all removable PCI peripherals), not about batttery model (I tried with a different models - 6cell and 9cell). It's most probably about the BIOS bug affecting Latitude E6410 with Core i7 620M 2.66Ghz (Dell replaced my CPU for the same model with no improvement); probably a race condition during frequency scaling (SpeedStep) on resume on batteries. Try disabling SpeedStep in BIOS and the problem does not appear; however it is a very unlucky solution. I'm trying to persuade Dell to give me a different nearest model of Core i7 CPU, even though I should pay for the difference in price. I expect that a different resulting CPU frequency helps to avoid the problem. BIOS should resolve it, but who knows when A06 comes out an if it would contain the fix. If one follows the history of E6400 latop overheating issues, it took one year and 10 BIOS revisions to mitigate the problem. I'm not sure whether the GPU is involved in this strange race condition when resuming on batteries. Please paste here your system specifications, especially CPU and GPU specs.

[Michal (mikeos)]

Oh, SerP6? I just thougt it's kind of typo, when I realized it is a laptop model, sorry. Anyway it still may be interesting, especially knowing what kind of CPU and GPU you have. Anyway it's not Dell or Serval who "manufactures BIOSes"; they assemble and package them based on components from their vendors.

[Jamie Krug (jamie-thekrugs)]

mikeos, my laptop specs:
System76 Serval Professional
- Graphics Nvidia GeForce GTX 285M Graphics with 1GB GDDR3 Video Memory
- Processor Core i7-840QM Processor ( 45nm, 8MB L3 Cache, 1.86GHz )
- Memory 8 GB - DDR3 1333 MHz - 2 DIMMs
- Hard Drive 160 GB Intel X25-M Solid State Drive

[Jamie Krug (jamie-thekrugs)]

It looks like I may have a fix/workaround that works for me, from this forum thread:
http://ubuntuforums.org/showpost.php?p=10100625&postcount=75

Basically, I add my wireless module ID to SUSPEND_MODULES in /etc/pm/config.d/unload_module. Not only does this seemed to have made my suspend/resume blank screen hangs disappear, but I've also noticed reconnecting to wifi networks, or connecting to a new one upon resume to be much faster (read above forum post for more details).

I should state that I barely understand what this is doing or why I'm doing it, but it was a suggestion that I've tried and it seems to work! I hope this somehow moves this issue along to a more final resolution.

Here's the basic commands I've used to apply this workaround...

$ lspci | grep Wireless
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller (rev 10)

$ lsmod | grep r8192
r8192se_pci 507324 0

# edit this file...
gksu gedit /etc/pm/config.d/unload_module &
# ...paste this line and save:
SUSPEND_MODULES="r8192se_pci"

[Jamie Krug (jamie-thekrugs)]

Unfortunately, the SUSPEND_MODULES workaround did not work for me after all. I went almost a week without suspend/resume problems, but the problems have appeared again. A few days ago I had a new one, where trying to suspend did not fully suspend--yet I was able to get the login screen, so no freeze-up. But the same old failure to resume occurred again as well. In this case, I opened my laptop lid to resume, power and lights came on, but nothing else happened--blank screen, and unable to anything but force a hard power-off. That said, as I've stated above, the attempted SUSPEND_MODULES workaround does still improve the way my network reconnects upon resume.

I looked through all sorts of log files after the failed resume, and there's absolutely *nothing* recorded in *any* log at that time. This suggests that the kernel never gets any sort of message to begin a resume, or if it does, whatever this problem is, it's rendering the system completely frozen and unable to log a single message :(

[Giuseppe Santillo (santillogiuseppe)]

Same problem here(2.6.35-22-generic, Ubuntu 10.10 32bit)
$ lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge Alternate
00:01.0 PCI bridge: Device 010a:0312
00:04.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 0)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [IDE mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3c)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Link Control
01:05.0 VGA compatible controller: ATI Technologies Inc RS880 [Radeon HD 4200]
01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200]
02:00.0 Ethernet controller: Atheros Communications AR8131 Gigabit Ethernet (rev c0)

[Latham Loop (lathamloop)]

My Dell Inspiron Mini 1012 (BIOS version A07) has this problem.
I tried adding the

GRUB_CMDLINE_LINUX="acpi_sleep=nonvs"
to /etc/default/grub and rebooted but that had no effect (maybe made it worse?).
I'm not confident configuring GRUB though.

[Michal (mikeos)]

Remember to call "sudo update-grub" after making modifications in /etc/default/grub. The update-grub script assures that /boot/grub/grub.cfg is updated with the new information. I assume you're using GRUB2.

[Latham Loop (lathamloop)]

Negative results :(
I tried again, making sure to run "sudo update-grub", after adding
GRUB_CMDLINE_LINUX="acpi_sleep=nonvs"
to /etc/default/grub.
Screen still does not turn on after suspending my Dell Inspiron Mini 1012 (BIOS version A07)

[dirkd (dirk-dierickx)]

since the latest updated kernel (2.6.35-23) i haven't had a resume failure, i suspend/resume several times a day and previously it failed at least once a day. not anymore, for me the problem seems to be fixed.

[Latham Loop (lathamloop)]

Kernel update = Negative results again :(

I ran the update manager, which updated my Dell Insipiron Mini 1012 (BIOS version A07),
from Kernel version 2.6.35-22 to 2.6.35-23
Sadly, the screen persists in staying off when I resume from a suspend.

[Michal (mikeos)]

Latham:
Do you really have an nVidia NVS GPU in your machine? If not, don't read further and "acpi_sleep=nonvs" is not for you anyway. Also don't continue reading unless you're familiar with GRUB boot menu and reverting to stock kernel if something bad happens.
For Linux kernels above 2.6.35 this acpi_sleep=nonvs tweak is no longer necessary. You may try it with 2.6.36 kernel downloadable e.g. from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-maverick/
You would need to download 3 files into a new empty directory:
1) linux-headers-2.6.36-020636_2.6.36-020636.201010210905_all.deb
2) linux-headers-2.6.36-020636-generic_2.6.36-020636.201010210905_ARCH.deb
3) linux-image-2.6.36-020636-generic_2.6.36-020636.201010210905_ARCH.deb
where ARCH stands for your OS architecture, either i386 or amd64.
Once you have the corresponding 3 files downloaded, run "sudo dpkg -i linux*" (without quotes) from this directory. Thanks to linux-headers and DKMS support the nVidia kernel module should be compiled and inserted to kernel automatically. If everything installs successfully you may try to reboot into your new kernel and see if it helped.

Dirkd:
You say it failed at least once a day. Didn't you just change recently your daily habits using your laptop? It took me quite a long time to realize the resume failure occurs only on resume from battery power, so sometimes it made me feel it fails more often than the other day. Usually users don't realize if they're performing resume on batteries or on AC which makes them feel that sometimes it fails and sometimes it works.

[dirkd (dirk-dierickx)]

no change in habbits here, i resume a lot on battery.
my machine is an acer travelmate 7730, i've attached my lspci output as well.

[Latham Loop (lathamloop)]

I installed the 2.6.36 Kernel, as mikeos instructed, and it is working much better :)
although I have observed two instances where the screen did not power up on resume ?? 2 of about 15 tries in my testing.

This may have no basis in reality, but since the 2.6.36 kernel update, the screen power always seems to resume if I have a USB mouse plugged in. When I am just using the track pad, the screen has failed to power up twice upon resume.

Dell Insipiron Mini 1012 (BIOS version A07),
Intel(R) Graphics Media Accelerator 3150 (resolution 1366 x 768)
Generic PnP Monitor
Intel(R) Atom(TM) CPU N450 @ 1.66GHz, 1 Core(s), 2 Logic Processors
2 GB RAM
Suspending & Resuming on battery power.

[penalvch (penalvch)]

doesntcount, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command in the development release from a Terminal (Applications->Accessories->Terminal) as it will automatically gather and attach updated debug information to this report.

apport-collect -p linux <BUGNUMBER>

Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[Launchpad Janitor (janitor)]

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