Comme=
nt # 34
on bug 10542=
5
from MirceaKitsune
(In reply to iive from comment #33)
Ahhh... you've reminded me of a detail that I have in fact noticed but forg=
ot
to mention: After the machine freezes and becomes completely unresponsive, =
some
keyboard leds will indeed turn off after roughly 10 seconds. I only noticed
this because I currently have a backlit keyboard that has the lighting
controlled by the Scroll Lock LED... I saw that a few seconds after the cra=
sh,
the keyboard lighting always turns itself off.
I cannot connect the computers with a serial cable: I think the motherboards
are too modern to have a serial port, and they're at a far distance in oppo=
site
rooms. Both computers are connected to the same home router via LAN cables
though, and can communicate through local IP... so net console sounds like a
good idea, but I've never heard of it before so I'll have to look this up.
Your sysrq suggestion seems to have worked! I first did this:
echo 1 > /proc/sys/kernel/sysrq
Then I pressed 'Alt + PrintScreen + H'. Now dmesg shows me:
[265102.938475] sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c)
terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i)
thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l)
show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p)
show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb=
(V)
show-blocked-tasks(w) dump-ftrace-buffer(z)
I assume that after the crash, I should first use it to test REISUB?
And here is the output of the kernel features you said to check. If they're=
not
there, I'm out of luck on this one, as I don't know how to compile my own
kernel and can't risk breaking my machine with dangerous tests.
mircea@linux-qz0r:~> zgrep CONFIG_NETCONSOLE /proc/config.gz
CONFIG_NETCONSOLE=3Dm
CONFIG_NETCONSOLE_DYNAMIC=3Dy
mircea@linux-qz0r:~> zgrep SERIAL_8250_CONSOLE /proc/config.gz
CONFIG_SERIAL_8250_CONSOLE=3Dy
Lastly I'll try glxgears without vsync for a few hours in the next days: I =
have
to leave my computer locked while I'm away from home or sleeping, but can l=
eave
it on for roughly 3 hours of the day while I'm around but AFK. I should note
that I tried running Xonotic without vsync, and that seems to have made
absolutely no difference. Also this likely isn't network related, I always =
test
in a local match with bots and not online multiplayer.