Bug 6101 - kernel oops when suspending with swsusp
Summary: kernel oops when suspending with swsusp
Status: REJECTED INVALID
Alias: None
Product: Power Management
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: power-management_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-18 13:20 UTC by Robert
Modified: 2007-04-28 12:49 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.15.2
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Robert 2006-02-18 13:20:41 UTC
Distribution: Debian
Hardware Environment: acer travelmate 800 (intel centrino laptop)

Problem Description: Unloading all unloadable modules and then suspending to 
disk using swsusp results in a kernel oops ("Unable to handle kernel paging 
request at address..."). The only modules that are loaded at this point are: 
usbcore, yenta_socket, rsrc_nonstatic, pcmcia_core, intel_agp, agpgart (see 
also the screenshot).
Strangely, if I don't unload all modules, swsusp works *sometimes*. It *always* 
reproducibly oopses if I unload all modules before calling suspend.

Steps to reproduce: I unloaded all unloadable modules and then called 
echo -n disk > /sys/power/state

Here is the log, config, lspci, and a digicam screenshot of the oops:

http://rffr.de/configs/dmesg-2006-02-05.txt
http://rffr.de/configs/lspci-2006-02-05.txt
http://rffr.de/configs/config-2.6.15.2.txt
http://rffr.de/screens/oops-2006-02-05.jpg
Comment 1 Robert 2006-02-18 13:59:04 UTC
I just noticed that using suspend-to-RAM (echo -n mem > /sys/power/state) leads 
to exactly the same result.

(Unload all modules, suspend -> oops)
Comment 2 Pavel Machek 2006-02-18 14:09:11 UTC
Can you try not loading those modules at all? I guess some module have problem
in unload routine...

Comment 3 Pavel Machek 2006-09-27 01:42:32 UTC
If it still happens in 2.6.18, please reopen.

Note You need to log in before you can comment on or make changes to this bug.