After last security updates, hibernation doesn't work

Bug #50646 reported by Juan Jose Amor Iglesias
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Hibernation does not work now in my laptop (Dell D600). After working for months
(using 6.06 beta releases, etc), and after last security updates (those that affect to kernel (2.6.15-25-386) and acpi-support (0.85), I guess).

When trying to recover from a hibernation, a oops occurs in kernel (below, related kern.log dump):

[17179577.664000] Stopping tasks: ==========|
[17179577.664000] Shrinking memory... done (0 pages freed)
[17179577.708000] Loading image metadata ... done (95 pages loaded)
[17179579.028000] busybox: page allocation failure. order:0, mode:0x8020
[17179579.028000] [<c0144aae>] __alloc_pages+0x1ee/0x2e0
[17179579.028000] [<c0144c02>] get_zeroed_page+0x22/0x50
[17179579.028000] [<c013c1b7>] alloc_data_pages+0x37/0xe0
[17179579.028000] [<c013b127>] swsusp_read+0x1a7/0x1f0
[17179579.028000] [<c013b42c>] software_resume+0x7c/0xf0
[17179579.028000] [<c013b646>] resume_store+0x86/0x90
[17179579.028000] [<c01a2327>] flush_write_buffer+0x27/0x30
[17179579.028000] [<c01a236f>] sysfs_write_file+0x3f/0x60
[17179579.028000] [<c015ff06>] vfs_write+0x96/0x150
[17179579.028000] [<c0160078>] sys_write+0x38/0x80
[17179579.028000] [<c01030a9>] syscall_call+0x7/0xb
[17179579.028000] Mem-info:
[17179579.028000] DMA per-cpu:
[17179579.028000] cpu 0 hot: low 0, high 0, batch 1 used:0
[17179579.028000] cpu 0 cold: low 0, high 0, batch 1 used:0
[17179579.028000] DMA32 per-cpu: empty
[17179579.028000] Normal per-cpu:
[17179579.028000] cpu 0 hot: low 0, high 186, batch 31 used:30
[17179579.028000] cpu 0 cold: low 0, high 62, batch 15 used:6
[17179579.028000] HighMem per-cpu: empty
[17179579.028000] Free pages: 4300kB (0kB HighMem)
[17179579.028000] Active:1908 inactive:2333 dirty:0 writeback:0 unstable:0 free:1075 slab:1430 mapped:325 pagetables:13
[17179579.028000] DMA free:3032kB min:72kB low:36kB high:72kB active:0kB inactive:0kB present:16384kB pages_scanned:0 all_unreclaimable? no
[17179579.028000] lowmem_reserve[]: 0 0 751 751
[17179579.028000] DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
[17179579.028000] lowmem_reserve[]: 0 0 751 751
[17179579.028000] Normal free:1268kB min:3468kB low:1732kB high:3468kB active:7632kB inactive:9332kB present:769720kB pages_scanned:0 all_unreclaimable? no
[17179579.028000] lowmem_reserve[]: 0 0 0 0
[17179579.028000] HighMem free:0kB min:128kB low:32kB high:64kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
[17179579.028000] lowmem_reserve[]: 0 0 0 0
[17179579.028000] DMA: 0*4kB 1*8kB 1*16kB 0*32kB 1*64kB 1*128kB 1*256kB 1*512kB 0*1024kB 1*2048kB 0*4096kB = 3032kB
[17179579.028000] DMA32: empty
[17179579.028000] Normal: 1*4kB 0*8kB 1*16kB 1*32kB 1*64kB 1*128kB 0*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 1268kB
[17179579.028000] HighMem: empty
[17179579.028000] Swap cache: add 0, delete 0, find 0/0, race 0+0
[17179579.028000] Free swap = 0kB
[17179579.028000] Total swap = 0kB
[17179579.028000] Free swap: 0kB
[17179579.036000] 196526 pages of RAM
[17179579.036000] 0 pages of HIGHMEM
[17179579.036000] 2592 reserved pages
[17179579.036000] 363 pages shared
[17179579.036000] 0 pages swap cached
[17179579.036000] 0 pages dirty
[17179579.036000] 0 pages writeback
[17179579.036000] 325 pages mapped
[17179579.036000] 1430 pages slab
[17179579.036000] 13 pages pagetables
[17179579.080000] Restarting tasks... done

And after that, a normal boot occurs.

Revision history for this message
Juan Jose Amor Iglesias (jjamor) wrote :

Still unresolved after last kernel updates :-(

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Thanks for reporting this bug. Is it still a problem? To make any progress with it, some more information will be needed. Please attach (by commenting on the bug) to the bug report the output of the following commands:

      uname -a
      sudo lspci -vv
      sudo lspci -vvn
      sudo dmidecode

Thanks again for your contribution.

Revision history for this message
Ben Collins (ben-collins) wrote :

Does this occur everytime, or just the first time you tried it? If you tried suspending after updating the kernel, before an actual reboot, then I can see how that would occur.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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.