http://bugzilla.novell.com/show_bug.cgi?id=566288
http://bugzilla.novell.com/show_bug.cgi?id=566288#c41
--- Comment #41 from Robert Schweikert
No traceback, but the system hung over night. At some point after my backup process started the system dropped into never never land. Here is a snippet from the syslog:
May 15 00:45:33 triumph rsyslogd: -- MARK -- May 15 01:05:33 triumph rsyslogd: -- MARK -- May 15 01:12:01 triumph /usr/sbin/cron[10659]: (root) CMD (/usr/local/bin/simBackup --verbose) May 15 06:07:40 triumph kernel: imklog 4.4.1, log source = /proc/kmsg started. May 15 06:07:40 triumph rsyslogd: [origin software="rsyslogd" swVersion="4.4.1" x-pid="1917" x-info="http://www.rsyslog.com"] (re)start
At 1:12 my backup script started and then at some point the system hung. At 6:07 is the reboot.
I take it that instead of a corruption and traceback the protection of memory in this kernel now triggers a hang.
What else can I do?
And some additional information that might be useful. The backup is just a tar command, which did get issued according to my log file. Judging by the size of the tarball created and previous backups the hang occurred while the tar command was running. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.