You are not logged in.
I've finally been able to induce a kernel panic on demand (Go on omegle.com, open the chat, open a new tab and load a bunch of pages). I've been having issues with the LTS kernel and my machine for a while, even after freshly reinstalling Arch. Now that I'm able to induce the panic, I can hopefully capture the output to the console. The only problem is, the panic is very unpredictable and I can't switch over to tty2 in time to capture the output. I know that there is a way to use a separate computer to capture output but It's very hard for me to get another machine and it's a bit complicated to set up. How can I better predict when the panic will happen? Is there another method to capture output?
Offline
Offline
Before you induce a kernel panic, run "while [ 1 -eq 1 ]; do sleep 1 && dmesg > outfile && journalctl -b > outfile2; done"
Afterwards look in the files for errors / panic messages.
You also can filter the journalctl output as described here: https://wiki.archlinux.org/index.php/Systemd#Journal or run "cat outfile | grep panic"
Offline
I have both files and I see some telling errors (ones that occur at the end of file). I don't know how to read them or how to fix it. I'll upload the files so you can help me.
Offline
Offline
I do not see any errors, can you send me the output of "sudo journalctl -k" maybe? Or tell me what errors you see in the files.
Last edited by mhoogland (2015-12-01 10:29:06)
Offline
It's been a while since I induced the panic, so I don't know what journalctl -k would reveal, considering when it happened.
Here are the errors that I see:
[ 0.730468] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM (Happened a few seconds after boot)
[ 3.162024] usb 1-1.4.1: string descriptor 0 read error: -22 (A bunch of errors like this)
All of these errors happened just before the panic and are the last lines of outfile:
[ 417.498051] fuse init (API version 7.23)
[ 795.937788] traps: nacl_helper[1457] general protection ip:7f45f3006b76 sp:7ffdb680e3f0 error:0 in libc-2.22.so[7f45f2fd2000+19b000]
[ 814.260723] traps: nacl_helper[1466] general protection ip:7f00fb5b5b76 sp:7fff955377f0 error:0 in libc-2.22.so[7f00fb581000+19b000]
[ 840.286859] traps: nacl_helper[1504] general protection ip:7fc5553abb76 sp:7fffe6d4bf20 error:0 in libc-2.22.so[7fc555377000+19b000]
Outfile2 contains whole dumps, so I'm not even going to bother posting it...
Offline
Since chromium is involved, my best guess would be that something went wrong in the browser and brought down your system, the most probable culprit might be gpu related.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Please clarify: Are you still on the LTS kernel and does the problem also come up with the default kernel? Why do you need the LTS kernel?
Offline
I'm still on the LTS kernel. I think it does but It's been a while since I've used it. I use the LTS kernel just because of the fact that it's LTS, I'd imagine it would be more stable. I'll switch back to the default and see if it panics...
Offline
You need to read more about the Arch LTS kernel then :-)
Offline
Okay, thanks.
Offline
It still happens even when I use the regular kernel. It's actually worse. I can't watch youtube and use the terminal at the same time without a panic. Also, ROOKIE, you mentioned that the issue may be GPU related? I'm using an Acer AXC-603-EB11. I haven't installed drivers for it and I know it has a GPU inside. Is there any way to test if it's GPU related?
Last edited by HappyClown (2015-12-06 19:25:08)
Offline
Well, by default chromium does rely on the gpu for a good number of things, I'd say try with a different browser, same tasks only change the browser. If it works then you can try to disable all hardware acceleration features on chromium and then enable them one by one until things crash. After that I suppose you can go upstream and report it, maybe someone will be able to pinpoint what is wrong and fix it.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Okay, but I think firefox has the same issue to a lesser degree, so it may use hardware acceleration as well (actually, I just checked. It does.). I don't know of any browsers that don't use hardware acceleration. I think I'm going to skip to disabling hardware acceleration in chromium and seeing what happens.
Offline
Okay, after disabling hardware acceleration, it's been a few days without the default kernel panicking. I'm going to try it with the LTS kernel and see if it panics. I've never reported to upstream before, any recommendations on what should be included? (assuming you're a dev)
Last edited by HappyClown (2015-12-09 23:47:21)
Offline