Bug 147273

Summary: kernel BUG in swsusp.c
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Juergen Christ <christ.juergen>
Component: KernelAssignee: Pavel Machek <pavel>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Minor    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: SuSE Linux 10.0   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: BUG message displayed by the kernel

Description Juergen Christ 2006-02-01 15:46:08 UTC 
Hi,

sometimes when I try to suspend my Laptop, I get a kernel BUG messages (attached as a photo). I cannot reproduce it every time, but it occurs regularly one time per month (about 1 time per 25 suspends).

This is my system:
Intel Centrino Processor with 1400 MHz,
256 MB DDR-Ram
Intel Extreme Graphics 2 graphic card.

With kind regards,

Jürgen
Comment 1 Juergen Christ 2006-02-01 15:48:02 UTC 
Created attachment 66048 [details]
BUG message displayed by the kernel
Comment 3 Pavel Machek 2006-02-09 09:09:15 UTC 
Yes, "famous" swsusp.c:905. It should be fixed in suse10.1 beta. (Code was totally rewritten at that part).

Unfortunately noone really knows how to reproduce this one, and I do not understand why it is happening :-(.
Comment 4 Stephan Kulow 2008-06-25 09:35:09 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:37:11 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:42:02 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 7 Stephan Kulow 2008-06-25 09:53:26 UTC 
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(