On 2015-06-12 16:13, Qu Wenruo wrote:
Remote syslog does not capture anything.
No backtrace?
No (nothing saved on disk, don't have VNC access).
The only way to capture anything is:
while true; do dmesg -c ; done
but that's usually incomplete.
Without backtrace, it's much harder to debug for us.
It's quite possible that some codes go mad and pass a NULL pointer,
and then wait_event() is called on the NULL->some_member.
Anyway, backtrace is needed to debug this.
If syslog can't help, what about kdump + crash to get the backtrace?
I'll try to get a kdump + crash.
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
