Bug 6101
| Summary: | kernel oops when suspending with swsusp | ||
|---|---|---|---|
| Product: | Power Management | Reporter: | Robert (spinningteacup) |
| Component: | Other | Assignee: | power-management_other |
| Status: | REJECTED INVALID | ||
| Severity: | normal | CC: | rjwysocki |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.15.2 | Tree: | Mainline |
| Subsystem: | Regression: | --- | |
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) Can you try not loading those modules at all? I guess some module have problem in unload routine... If it still happens in 2.6.18, please reopen. |
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