> Don’t miss this step! dmesg is always worth checking.
Best advice given in the whole article. Many times I go to check something that "can't figure out what is wrong." dmseg | tail and then the swearing begins on their end.
Best advice given in the whole article. Many times I go to check something that "can't figure out what is wrong." dmseg | tail and then the swearing begins on their end.
It's amazing how much time one useful error message can save.
Also, I'm a little disappointed that the author didn't drill down into what the actual problem was in his example. That java process is of course suspicious, but that might just be the video server and expected behavior.
And a likely source of misgivings regarding recent developments in the ecosystem...
dmesg -T
Has been available for years to print out human-readable timestamps. Check to see if dmesg is an alias to that on your system. Also, -IIRC- dmesg has printed system-uptime timestamps with every line since at least the early 2000's.One caveat: the times printed by dmesg -T will be incorrect if the system has suspended to RAM or disk.
Check dmesg(1) for more info! :D