https://bugzilla.novell.com/show_bug.cgi?id=803702 https://bugzilla.novell.com/show_bug.cgi?id=803702#c2 --- Comment #2 from Elmar Stellnberger 2013-02-14 09:45:09 UTC --- Created an attachment (id=524649) --> (http://bugzilla.novell.com/attachment.cgi?id=524649) backtrace -- 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=803702 https://bugzilla.novell.com/show_bug.cgi?id=803702#c3 Robert Milasan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |estellnb@elstel.org --- Comment #3 from Robert Milasan 2013-02-14 10:02:53 UTC --- Enable sysrq in Yast -> Kernel settings and then reboot. Then please run the following commands as root on the non-crashed system: ulimit -c unlimited mkdir -p /root/cores chmod 1777 /root/cores echo "/root/cores/core.%e.%p.%h.%t" > /proc/sys/kernel/core_pattern echo 2 > /proc/sys/kernel/suid_dumpable udevadm trigger; udevadm settle --timeout=30 (repeat this command a couple of times, hopefully it will crash). This also can be added to /lib/mkinitrd/boot/04-udev.sh, but you will need the sysrq enabled and when the system crash to push the respective coredump to a file system, non-tmpfs. If you wanna add the upper command in the initrd, where the crash happens, add to /lib/mkinitrd/boot/04-udev.sh the following (before wait_for_events function): ulimit -c unlimited mkdir -p /run/cores chmod 1777 /run/cores echo "/run/cores/core.%e.%p.%h.%t" > /proc/sys/kernel/core_pattern echo 2 > /proc/sys/kernel/suid_dumpable and then rebuild initrd image using 'mkinitrd'. NOTE: please read about the usage of sysrq keys so you can copy the coredump from /run/cores, as /run is a tmpfs. http://en.wikipedia.org/wiki/Magic_SysRq_key -- 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=803702 https://bugzilla.novell.com/show_bug.cgi?id=803702#c5 Elmar Stellnberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|estellnb@elstel.org | --- Comment #5 from Elmar Stellnberger 2013-02-14 11:10:28 UTC --- Sorry, have tried to reproduce it but could not. Neither running udevadm trigger; udevadm settle --timeout=30 nor rebooting several times with different devices plugged in or not could re-evoke the crash. Nonetheless my system should be configured now to get a kdump as well as a (oops) /root/cores/*.core. I have used /root/cores instead because I could not imagine a kernel dump on ramfs to be useful if the only escape is a hard power off. I hope if installed in initrd that will refer to the real system root rather than the initrd system root buffered on ram. -- 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=803702 https://bugzilla.novell.com/show_bug.cgi?id=803702#c7 --- Comment #7 from Elmar Stellnberger 2013-02-14 11:52:19 UTC --- Created an attachment (id=524675) --> (http://bugzilla.novell.com/attachment.cgi?id=524675) dmesg with udev-dbg on Sorry; still nothing in /run/cores though my X server has terminated and /var/log/messages is of zero size. -- 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=803702 https://bugzilla.novell.com/show_bug.cgi?id=803702#c9 Elmar Stellnberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|estellnb@elstel.org | --- Comment #9 from Elmar Stellnberger 2013-02-14 11:53:33 UTC --- Created an attachment (id=524677) --> (http://bugzilla.novell.com/attachment.cgi?id=524677) Xorg.0.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=803702 https://bugzilla.novell.com/show_bug.cgi?id=803702#c11 Robert Milasan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |estellnb@elstel.org --- Comment #11 from Robert Milasan 2013-03-14 09:49:43 UTC --- Elmar, any news on this. Did the panic happen again? -- 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.