trouble resuming from hibernation on -current
Douglas Mayne
deserved its own subject line. I am curious if anyone else is having
trouble when resuming from a hibernation state.
Hardware:
Samsung NC10 netbook (Atom N270 CPU with 2G RAM)
Intel i9xx graphics
500G SATA HD (magnetic RW)
After upgrading to -current, this computer does not resume correctly from
hibernation. The resume process gets 100% done, but on the final step to
return control to a graphics or text console, the display is corrupted
beyond repair. The keyboard is working and you can do <ctl>-<alt>-<fx> to
switch to another text terminal; the display is still corrupted, but you
can at least enter a <ctl>-<alt>-<del> sequence.
Hibernation is an important feature, and it had been implemented and
working great after years of not really working at all.
TIA
p.s. Running on device mapper based encrypted filesystems and swap
partitions. The disk subsystem seems to be working as intended and I don't
think that is the source of the trouble.
--
Douglas Mayne
Robby Workman
No, that's not the problem at all. This is likely some sort of
regression in the kernel, but the good news is that a new one just
hit the -current tree today :-) Try it, and if the resume problem
is still present, we'll go from there.
-RW
Douglas Mayne
> regression in the kernel, but the good neLinux version 2.6.37.3-smp (root@midas) (gcc version 4.5.2 (GCC) ) #1 SMP Mon Mar 7 20:30:02 CST 2011
ws is that a new one just hit
> the -current tree today :-) Try it, and if the resume problem is still
> present, we'll go from there.
>
> -RW
>
Thanks,
I have just upgraded my Samsung NC10 to 13.37 RC1 and booted with the kernel:
Linux version 2.6.37.3-smp
(root@midas) (gcc version 4.5.2 (GCC) ) #1 SMP
Mon Mar 7 20:30:02 CST 2011
Unfortunately, the same flaw is still present (identical to as before)-
it does not resume correctly from hibernation. The display is corrupted,
but the keyboard works. The display looks there is an unchangable box
superimposed over the screen.
Here is the output from lspci (please pardon long lines):
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
02:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)
This tidbit from dmesg looks interesting:
[ 9.343140] usb 1-8: New USB device found, idVendor=0ac8, idProduct=c326
[ 9.351301] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9.359501] usb 1-8: Product: Namuga 1.3M Webcam
[ 9.367728] usb 1-8: Manufacturer: Vimicro Corp.
[ 9.439819] Linux video capture interface: v2.00
[ 9.462735] uvcvideo: Found UVC 1.00 device Namuga 1.3M Webcam (0ac8:c326)
[ 9.474609] input: Namuga 1.3M Webcam as /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/input/input1
[ 9.492111] usbcore: registered new interface driver uvcvideo
[ 9.500875] USB Video Class driver (v1.0.0)
[ 9.539553] irq 16: nobody cared (try booting with the "irqpoll" option)
[ 9.540014] Pid: 982, comm: udevd Not tainted 2.6.37.3-smp #1
[ 9.540014] Call Trace:
[ 9.540014] [<c14393ab>] ? printk+0x1d/0x22
[ 9.540014] [<c109614c>] __report_bad_irq.clone.2+0x2c/0x90
[ 9.540014] [<c1094c94>] ? handle_IRQ_event+0x44/0x150
[ 9.540014] [<c109630a>] note_interrupt+0x15a/0x1a0
[ 9.540014] [<c101f9d3>] ? ack_apic_level+0x63/0x1b0
[ 9.540014] [<c1096f1b>] handle_fasteoi_irq+0x9b/0xc0
[ 9.540014] [<c1096e80>] ? handle_fasteoi_irq+0x0/0xc0
[ 9.540014] <IRQ> [<c143c779>] ? do_IRQ+0x49/0xc0
[ 9.540014] [<c104930c>] ? irq_exit+0x3c/0x80
[ 9.540014] [<c143c782>] ? do_IRQ+0x52/0xc0
[ 9.540014] [<c1003670>] ? common_interrupt+0x30/0x38
[ 9.540014] [<c110a681>] ? d_alloc+0x21/0x180
[ 9.540014] [<c1439f13>] ? _cond_resched+0x13/0x30
[ 9.540014] [<c10ef9be>] ? kmem_cache_alloc+0x2e/0xf0
[ 9.540014] [<c110a681>] ? d_alloc+0x21/0x180
[ 9.540014] [<c1003670>] ? common_interrupt+0x30/0x38
[ 9.540014] [<c110a681>] ? d_alloc+0x21/0x180
[ 9.540014] [<c1101fb8>] ? d_alloc_and_lookup+0x28/0x70
[ 9.540014] [<c1102d8a>] ? do_lookup+0xda/0x120
[ 9.540014] [<c114bb88>] ? sysfs_permission+0x48/0x60
[ 9.540014] [<c1103437>] ? link_path_walk+0x297/0x8b0
[ 9.540014] [<c1103b49>] ? path_walk+0x49/0xa0
[ 9.540014] [<c102935d>] ? ptep_set_access_flags+0x4d/0x60
[ 9.540014] [<c1103ca9>] ? do_path_lookup+0x59/0x90
[ 9.540014] [<c1103ed1>] ? user_path_at+0x41/0x80
[ 9.540014] [<c110250b>] ? putname+0x2b/0x40
[ 9.540014] [<c1103eda>] ? user_path_at+0x4a/0x80
[ 9.540014] [<c10fd22a>] ? vfs_fstatat+0x3a/0x80
[ 9.540014] [<c10fd290>] ? vfs_lstat+0x20/0x30
[ 9.540014] [<c10fd559>] ? sys_lstat64+0x19/0x30
[ 9.540014] [<c10057ad>] ? handle_irq+0x1d/0xa0
[ 9.540014] [<c104930c>] ? irq_exit+0x3c/0x80
[ 9.540014] [<c143c782>] ? do_IRQ+0x52/0xc0
[ 9.540014] [<c104930c>] ? irq_exit+0x3c/0x80
[ 9.540014] [<c143c782>] ? do_IRQ+0x52/0xc0
[ 9.540014] [<c1003670>] ? common_interrupt+0x30/0x38
[ 9.540014] [<c143bebc>] ? syscall_call+0x7/0xb
[ 9.540014] [<c1430000>] ? rdc_init_one+0x5e/0xf0
[ 9.540014] handlers:
[ 9.540014] [<c1305070>] (usb_hcd_irq+0x0/0x70)
[ 9.540014] Disabling IRQ #16
[ 9.885997] scsi 2:0:0:0: CD-ROM TOSHIBA DVD-ROM SD-R2412 1015 PQ: 0 ANSI: 0
[ 9.903055] usb 3-2: new full speed USB device using uhci_hcd and address 2
[ 9.910115] sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
[ 9.911727] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 9.922395] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 9.929256] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 9.929820] sr 2:0:0:0: Attached scsi generic sg1 type 5
[ 10.085351] usb 3-2: New USB device found, idVendor=0a5c, idProduct=2101
[ 10.091854] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 10.098406] usb 3-2: Product: BCM92045NMD
[ 10.104916] usb 3-2: Manufacturer: Broadcom Corp
[ 10.111527] usb 3-2: SerialNumber: 00242CC379C2
[ 10.118443] scsi 3:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS
[ 10.128183] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 10.136218] sd 3:0:0:0: [sdb] 8060928 512-byte logical blocks: (4.12 GB/3.84 GiB)
[ 10.148342] sd 3:0:0:0: [sdb] Write Protect is off
[ 10.156295] sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 10.156305] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 10.172674] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 10.184088] sdb: sdb1
[ 10.195045] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 10.202849] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[ 10.203200] Bluetooth: Core ver 2.15
[ 10.213383] NET: Registered protocol family 31
[ 10.213390] Bluetooth: HCI device and connection manager initialized
[ 10.213398] Bluetooth: HCI socket layer initialized
[ 10.254407] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 10.263930] usbcore: registered new interface driver btusb
[ 22.105628] PM: Starting manual resume from disk
[ 22.212603] SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
[ 22.226614] SGI XFS Quota Management subsystem
[ 22.253233] XFS mounting filesystem dm-0
[ 24.128598] Ending clean XFS mount for filesystem: dm-0
BTW, I am using my own startup environment because to mount encrypted filesystems
at boot. My startup environment is similar to, but not identical to the
official initrd environment. I may be able to test using the official
environment if necessary.
Douglas Mayne
Douglas Mayne
<snip>
I have just upgraded to 13.37 RC2 and booted with the kernel:
Linux version 2.6.37.4-smp (root@midas) (gcc version 4.5.2 (GCC) )
#1 SMP Tue Mar 15 00:05:58 CDT 2011
root@darkstar:~# cat /etc/slackware-version
Slackware 13.37.0
This upgrade hasn't fixed the problem with hibernation. The same flaw is
still present- the restore from hibernation gets to 100% done, but then
it does not properly restore the display.
--
Douglas Mayne
Douglas Mayne
I have just upgraded to 13.37 RC3 and booted with the kernel:
Linux version 2.6.37.4-smp (root@midas)
(gcc version 4.5.2 (GCC) )
#1 SMP Thu Mar 17 15:45:19 CDT 2011
This upgrade hasn't fixed the problem with hibernation. pm-suspend works.
pm-hibernate does not.
# lspci | grep 945
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controller (rev 03)
Also, other Linux distributions are reporting similar problems with the
Intel X driver. I found this problem which is very similar to what I am
seeing:
https://bbs.archlinux.org/viewtopic.php?id=113523
BTW, I may be able to test more hardware (i.e. other laptops that I have
access to.) They all use a similar Intel graphics chipset which appears
to be the cause of the problem.
--
Douglas Mayne
Douglas Mayne
I have just upgraded to 13.37 RC pi. I also applied the patches in the
changelog to the mark: Tue Mar 29 05:46:13 UTC 2011
I also assumed this comment from the changelog,
"Very close now! But we'll likely hold out for 2.6.37.6."
means that the later kernel is preferred. I checked at kernel.org and I
see that kernel patch is now available. I compiled that version (with
some minor differences from the default generic-smp kernel.)
$ cat /proc/version
Linux version 2.6.37.6-smp (root@darkstar)
(gcc version 4.5.2 (GCC) ) #1 SMP
Tue Mar 29 12:13:02 MDT 2011
Unfortunately, this does not fix the problem. Hibernation is still broken
on the Samsung NC10. The failure (video only) is the same as before. pm-
suspend works. pm-hibernate does not.
If I were to make a WAG, I am still not convinced the problems introduced
with udev-165 have been fully addressed. I wouldn't be at all surprised
if there is a very bad assumption introduced there. I am considering
rolling udev back to the last version which worked reliably for me, (i.e.
udev-164), just to see if that makes any difference.
I wrote about the trouble with udev here:
http://groups.google.com/group/alt.os.linux.slackware/msg/000b8f1017a409ba
I could certainly be wrong, and these problems are totally unrelated.
Just a very WAG.
--
Douglas Mayne
Robby Workman
I think they're unrelated, and I think you have a kernel bug that you
should report on the kernel bugzilla. Obviously they either don't
know about it or some such, and perhaps that will help get it fixed later.
-RW
Grant
I read something crazy with driver firmware loading before userspace alive
on resume... So yes, there's a kernel bug involved, the example was r8169
(Realtek 1Gbps NIC chip), you could try telling kernel to keep firmware in
the kernel, to avoid a call out to user-space for firmware load (the default).
Grant.
Douglas Mayne
I have upgraded the Samsung NC10 to Slackware -current to this mark in
the ChangeLog: Mon Apr 18 19:13:18 UTC 2011
I tested hibernation with the official modular kernel:
kernel-generic-smp-2.6.37.6_smp-i686-2
This didn't appear to resolve the problem, so I moved on to test with the
official kernel in "testing":
kernel-generic-smp-2.6.38.3_smp-i686-1
That appears to fix the hibernation problem. The dmesg boot log is also
quite a bit different, and perhaps is doing a better job of initializing
the hardware. I guess, time will tell.
--
Douglas Mayne