[arch-general] system crashes when starting network connection
Hello, recently I have come across a weird problem regarding full system crashes under certain conditions. It seems somewhat random but the trigger always includes starting a network connection after sometime with no network connectivity. The only applications that have triggered the issue until now are firefox (after starting normaly) which triggers the second I click on a bookmark to open a website (no network conenction until that second). The other application was mutt, which triggered the moment when I fetched mails and the status bar said "looking up mbox" or something of the like. The result of the trigger is a full system crash, showing the current screen. Using Ctrl+Alt+F1/7 does not work. There is no trace in the logs, neither in the journal nor did I find anything with dmseg. The only way to get out of this is by hard reset. I have tried to replicate the bug but so far I was not succesful. I have no idea how to analyse the issue further. Do you have any hints on how to produce continious detailed logfiles or something of that sort to find what is wrong? Thanks
On Mon, 17 Oct 2016 23:50:14 +0200, sivmu wrote:
The result of the trigger is a full system crash, showing the current screen.
I have no idea how to analyse the issue further.
You didn't mention what WM or DE, what kind of network, what tool to access the network and what graphics is used. A wild guess, since the GUI does freeze, it might be related to the used DE and/or the graphics. Regards, Ralf
Am 18.10.2016 um 00:53 schrieb Ralf Mardorf:
On Mon, 17 Oct 2016 23:50:14 +0200, sivmu wrote:
The result of the trigger is a full system crash, showing the current screen.
I have no idea how to analyse the issue further.
You didn't mention what WM or DE, what kind of network, what tool to access the network and what graphics is used.
Sorry for that. I'm using the awesome WM, there are basically no other userspace processes running besides teh xserver, dbus and systemd. First I suspected the recent upgrade to gtk 3.22 might be the culprit, but after mutt caused the same issue (used in xterm) I think that can be ruled out. The amdgpu driver was also a suspect but I have not found anything to support that idea. Since This only happens after the network has been inactive for some time, I highly suspect the issue lies there. The network adapter is an intel gigabit ethernet adapter, I will try to find out the exact specification. up till now there was never a problem with it anyway. I have been running this szstem for mounth without issues. The only suspect software that was updated recently was gtk and the upgrade to linux 4.7.7
Did this problem started after an upgrade? Can you check if it is hardware failure? Any memtest?
Am 18.10.2016 um 21:33 schrieb Alex Theotokatos via arch-general:
Did this problem started after an upgrade? Can you check if it is hardware failure? Any memtest?
it did staret after upgrading the kernel to 4.7.7 Hardware seems ok. After upgrading the kernel to 4.7.8 today the issue did not occur again. So I assume the error was in the kernel, although I would still very much like to know a way to analyse this kind of problem. I imaging there must be some kind of continious loggin tool that shows when exactly the error triggers.
On Tue, Oct 18, 2016 at 10:16:26PM +0200, sivmu wrote:
After upgrading the kernel to 4.7.8 today the issue did not occur again.
What repo did you find that kernel in?
participants (4)
-
Alex Theotokatos
-
Dutch Ingraham
-
Ralf Mardorf
-
sivmu