You are not logged in.
Pages: 1
Hi,
my system freezes for unknown reasons. The problem is about 2 or 3 weeks old. It ran stable before.
The crash behavior is really strange:
Complete freeze of X11, a lenghty debug log dump on tty with systemd finally complaining about not being able to kill a process.
SSH login is impossible.
I can connect (Bitwise ssh), but key exchange or (after established key) starting up the shell on the crashed host ends in a network timeout.
The LED on eth-plug shows something still runs.
Soft reset works.
Systemd whines.
trigger:
I have no idea what really triggers the crash but this time I saw
pacman segfaulting when trying to fetch packages.
ping on hostnames segfaulted too, ping on ip address did work.
I then tried to nslookup a host and there it was again - system freeze.
A second way to freeze the system is to use a webbrowser. It works a while, then suddenly, crash.
System load is very low when it happens (cpus, hdd io, network io, mem), the machine is cold.
It's not a graphics problem as I triggered the nslookup crash via ssh and didn't even login in to X on th machine.
Has anybody seen this?
What information do you need?
I made fotos of the stack trace on the tty, because last week the machine wouldn't boot at all anymore after some resets.
(I did check the hardware - everything seems to be fine, I even changed mainboard and cpu since last week.)
UPDATE:
After this reboot nslookup works just fine. And now I'm really finally lost. I'm doing a pacman -Syu just to make sure I don't have a fixed issue hanging around.
But I'm pretty sure, it's going to crash again pretty soon.
UPDATE2:
Found this via journalctl -x
Jul 07 17:07:52 druschba kernel: ffff880212bd4d20 0000000000000004 000000000000JJul 07 17:07:52 druschba kernel: ffff880212bd4d20 0000000000000004 0000000000000Jul 07 17:07:52 druschba kernel:Jul 07 17:07:52 druschba kernel: ffff880212bd4d20 0000000000000004 0000000000000686 f
Jul 07 17:07:52 druschba kernel: ffff880212bd4d20 0000000000000004 0000000000000686 ffff8800dde33c18
Jul 07 17:07:52 druschba kernel: Call Trace:
Jul 07 17:07:52 druschba kernel: ffff880212bd4d20 0000000000000004 0000000000000686 ffff8800dde33c18
Jul 07 17:07:52 druschba kernel: Call Trace:
Jul 07 17:07:52 druschba kernel: [<ffffffff81181ff8>] truncate_inode_page+0x58/0x100
Jul 07 17:07:52 druschba kernel: [<ffffffff81182250>] truncate_inode_pages_range+0x170/0x840
Jul 07 17:07:52 druschba kernel: [<ffffffff81182984>] truncate_inode_pages_final+0x44/0x50
Jul 07 17:07:52 druschba kernel: [<ffffffffa01f6589>] ext4_evict_inode+0x119/0x4b0 [ext4]
Jul 07 17:07:52 druschba kernel: [<ffffffff81211c75>] evict+0xc5/0x190
Jul 07 17:07:52 druschba kernel: [<ffffffff81212419>] iput+0x1d9/0x260
Jul 07 17:07:52 druschba kernel: [<ffffffff8120e2c2>] __dentry_kill+0x172/0x1d0
Jul 07 17:07:52 druschba kernel: [<ffffffff8120e45c>] dput+0x13c/0x230
Jul 07 17:07:52 druschba kernel: [<ffffffff811f91f5>] __fput+0x135/0x1e0
Jul 07 17:07:52 druschba kernel: [<ffffffff811f92de>] ____fput+0xe/0x10
Jul 07 17:07:52 druschba kernel: [<ffffffff81097c04>] task_work_run+0x84/0xa0
Jul 07 17:07:52 druschba kernel: [<ffffffff810036aa>] exit_to_usermode_loop+0xba/0xc0
Jul 07 17:07:52 druschba kernel: [<ffffffff81003bde>] syscall_return_slowpath+0x4e/0x60
Jul 07 17:07:52 druschba kernel: [<ffffffff815c72fa>] entry_SYSCALL_64_fastpath+0xa2/0xa4
Jul 07 17:07:52 druschba kernel: Code: 89 45 b0 31 c0 eb 24 49 8b 0c 24 80 e5 02 74 2d 41 83 c1 01 83 c2 01 f0 41 80 64 24 01 fdJul 07 17:07:52 druschba kernel: RIP [<ffffffffa01efb63>] ext4_da_invalidatepage+0xe3/0x350 [ext4]
Jul 07 17:07:52 druschba kernel: RSP <ffff8800dde33b98>
Jul 07 17:07:52 druschba kernel: CR2: ffff8c01fd07a708
Jul 07 17:07:52 druschba kernel: ---[ end trace fd0fd2856a756738 ]---
Jul 07 17:09:49 druschba kernel: ping[830]: segfault at 44 ip 0000000000409abb sp 00007ffee9741ce0 error 6 in ping[400000+e000]
Jul 07 17:10:02 druschba kernel: ping[831]: segfault at 4a ip 0000000000409abb sp 00007ffc90acead0 error 6 in ping[400000+e000]
Jul 07 17:10:13 druschba kernel: BUG: unable to handle kernel paging request at ffff8c01fd07a548
Jul 07 17:10:13 druschba kernel: IP: [<ffffffff811d4a64>] kmem_cache_alloc+0x74/0x1e0
-- Reboot --
Last edited by Stephan Lahl (2016-07-07 16:28:04)
Offline
Offline
That error seems to be related to the filesystem/disk, maybe a faulty harddisk?
Offline
Pages: 1