http://bugzilla.suse.com/show_bug.cgi?id=977932
http://bugzilla.suse.com/show_bug.cgi?id=977932#c1
Michal Kubeček changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mkubecek@suse.com,
| |peter@peterchambers.me.uk
Assignee|kernel-maintainers@forge.pr |mkubecek@suse.com
|ovo.novell.com |
Flags| |needinfo?(peter@peterchambe
| |rs.me.uk)
--- Comment #1 from Michal Kubeček ---
First, please check if the issue persists with 3.12.57-44 kernel update
released earlier this week. If it does, I have some questions:
1. Do I understand correctly that this happens after suspending to memory
(not disk)?
2. How long is the delay between resume and system reboot? Do you have
a non-zero value in /proc/sys/kernel/panic ?
3. Try setting "echo 8 >/proc/sys/kernel/printk", switching to a text console
(Ctrl-Alt-F1), logging as root and suspending manually by running
"echo mem >/sys/power/state". If the resume is broken, you might see some
error messages on the terminal, these might give us some clue.
--
You are receiving this mail because:
You are on the CC list for the bug.