jdd wrote:
Hello,
I have a serious problem with my 13.2 install.
In short it crashes approx twice a day. Hardcrash. Suddenly no more keyboard nor mouse. sometime, after a long wait (very long, it happenned twice and I was no more in front of the computer, it reboots or unconnect, anyway I find the computer sitting on the login prompt.
I don't see anything in the system logs
I have this from the beginning (a week or more), never had it with 13.1.
What's new apart the 13.2 is the use of a new 256Gb Kingston ssd devoted at the 13.2 install and sitted on an external esata dock (I have the dock since more than two years with no problem).
What can I do to track the problem? it do not come at any special time, but randomly.
Can you try loading an alternate kernel? Ideally -- for testing, if you can substitute in a "vanilla" kernel with as few "patch addons" as necessary for things to work, that could help. Do you run with any sort of HANGCHECK timer
zgrep HANG /proc/config.gz CONFIG_HANGCHECK_TIMER=m <- (m or y)
or a Watchdog timer that can yell if a process hangs?...
zgrep WATCH /proc/config.gz CONFIG_AUDIT_WATCH=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_IPMI_WATCHDOG=m CONFIG_WATCHDOG=y CONFIG_WATCHDOG_CORE=y
Nov 12 04:41:46 Ishtar kernel: [ 5766.362637] INFO: task sendmail:38508 blocked for more than 120 seconds. Nov 12 04:41:46 Ishtar kernel: [ 5766.369362] Not tainted 3.17.2-Isht-Van #1 Nov 12 04:41:46 Ishtar kernel: [ 5766.373984] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 12 04:41:46 Ishtar kernel: [ 5766.381842] ffff880f221d7700 0000000000000046 ffff880a8f16a510 ffff880f221d7fd8 Nov 12 04:41:46 Ishtar kernel: [ 5766.381844] 00000000001d3b40 00000000001d3b40 ffff8817fbca4a20 ffff880a8f16a510 Nov 12 04:41:46 Ishtar kernel: [ 5766.381847] 7fffffffffffffff ffff880bf796d370 0000000000000002 0000000000000000 Nov 12 04:41:46 Ishtar kernel: [ 5766.381848] Call Trace: Nov 12 04:41:46 Ishtar kernel: [ 5766.381856] [<ffffffff8160cea4>] schedule+0x24/0x70 [.....] Nov 12 04:41:46 Ishtar kernel: [ 5766.382027] [<ffffffff81613352>] system_call_fastpath+0x16/0x1b Nov 12 04:41:46 Ishtar kernel: [ 5766.382029] 4 locks held by sendmail/38508: Nov 12 04:41:46 Ishtar kernel: [ 5766.382029] #0: (sb_writers#3){......}, at: [<ffffffff811c62bf>] mnt_want_write+0x1f/0x50 ... --------------- Had a few of those in my log w/the 3.17.2 kernel due to a regression, moving back to 3.16.x & waiting for 3.17.3 got around the problem. In my case, the hangs were xfs related, so I posted a Q on the xfs list and found out about the regression (that only appeared during "xfsdump"s (backups)), but having a good amount of system logs around so you can know what is "normal" and what is not, helps when "abnormal" pops up. FWIW, I also *try* to keep my system-boot messages:
unzip -l boot.msg.zip Archive: boot.msg.zip Length Date Time Name 190342 2011-12-24 00:56 boot-111224.0057 ... 120345 2014-11-17 09:29 boot-141117.0933
17410349 120 files ---- Doesn't always help, but keeping logs can let you look for anomalies that can point to problems. Other than that, there are too many causes of the symptoms you describe -- maybe googling for your problem? "how to track suse 13.2 hang" brings up a bunch of places to look... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org