[Bug 814126] New: System instable after resume from disk
https://bugzilla.novell.com/show_bug.cgi?id=814126 https://bugzilla.novell.com/show_bug.cgi?id=814126#c0 Summary: System instable after resume from disk Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: vbargsten@freenet.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=534059) --> (http://bugzilla.novell.com/attachment.cgi?id=534059) Screenshot of lock-up User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 When resuming from disk the system is instable, often leading to a lock-up (see screenshot). Occured using the 12.3 default kernel version and 3.8.4 from kernel-stable repository. I then tried suspend to disk with the debug kernel and saw the journal being filled up quite fast with messages such as Mar 26 22:10:42 vbmobil2.site systemd-journal[370]: Missed 14 kernel messages Mar 26 22:10:42 vbmobil2.site kernel: power_supply BAT1: prop CHARGE_NOW=3885000 Mar 26 22:10:42 vbmobil2.site systemd-journal[370]: Missed 14 kernel messages Mar 26 22:10:42 vbmobil2.site kernel: power_supply BAT1: prop CHARGE_NOW=3885000 Mar 26 22:10:42 vbmobil2.site systemd-journal[370]: Missed 14 kernel messages Mar 26 22:10:42 vbmobil2.site kernel: power_supply BAT1: prop CHARGE_NOW=3885000 I suspect that these messages somehow spam the system and e.g. trigger led events. Since the wireless device ath9k-phy0 is the only one underneath /sys/class/leds/, this may establish the connection to the previous observations (https://bugzilla.novell.com/show_bug.cgi?id=738586). I then tried suspend to disk and resume with the battery removed. This seemed stable (tested for about 10 suspend-resume cycles). Reproducible: Always Steps to Reproduce: 1. Suspend to disk 2. Resume Actual Results: System is instable, often leading to lockup after short time. Expected Results: Successful resume -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=814126 https://bugzilla.novell.com/show_bug.cgi?id=814126#c1 --- Comment #1 from Vinzenz Bargsten <vbargsten@freenet.de> 2013-04-08 21:35:30 UTC --- Created an attachment (id=534062) --> (http://bugzilla.novell.com/attachment.cgi?id=534062) journalctl output from suspend-resume with debug kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=814126 https://bugzilla.novell.com/show_bug.cgi?id=814126#c2 --- Comment #2 from Vinzenz Bargsten <vbargsten@freenet.de> 2013-04-08 21:36:47 UTC --- Created an attachment (id=534063) --> (http://bugzilla.novell.com/attachment.cgi?id=534063) syslog according to journal log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=814126 https://bugzilla.novell.com/show_bug.cgi?id=814126#c3 --- Comment #3 from Vinzenz Bargsten <vbargsten@freenet.de> 2013-04-08 21:37:13 UTC --- Created an attachment (id=534064) --> (http://bugzilla.novell.com/attachment.cgi?id=534064) output of lspci -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=814126 https://bugzilla.novell.com/show_bug.cgi?id=814126#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trenn@suse.com AssignedTo|kernel-maintainers@forge.pr |jlee@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=814126 https://bugzilla.novell.com/show_bug.cgi?id=814126#c4 Vinzenz Bargsten <vbargsten@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #4 from Vinzenz Bargsten <vbargsten@freenet.de> 2013-07-15 18:41:18 UTC --- Kernel parameter "acpi=copy_dsdt" seems to fix the problem. With full acip debug output (acpi.debug_level=0x2 acpi.debug_layer=0xFFFFFFFF, tried a custom dsdt), I once noticed messages indicating that battery related acpi functions could not be found after one resume (instead of just weird behaviour). Then added the copy_dsdt option. Since this worked, I gradually removed all other special kernel parameters I have also tried (such as acpi_os_name="Windows 2009" acpi_enforce_resources=strict or acpi_osi=Linux). Seems that the copy_dsdt function is sufficient. In effect I use "acpi=copy_dsdt pcie_aspm=force i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.lvds_downclock=1" now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com