Arch Linux

ncnd

Member

Registered: 2015-09-09

Posts: 3

Freeze : unable to handle kernel paging request

Hello all !

I'm having trouble with my Arch laptop : it keeps freezing, sometimes after 2 or 3 minutes of running.
Here are the logs :

sept. 09 13:51:50 Salmar kernel: BUG: unable to handle kernel paging request at 0000002d03648323
sept. 09 13:51:50 Salmar kernel: IP: [<ffffffff811c5cae>] __kmalloc_node_track_caller+0x1de/0x320
sept. 09 13:51:50 Salmar kernel: PGD da1b1067 PUD 0 
sept. 09 13:51:50 Salmar kernel: Oops: 0000 [#1] PREEMPT SMP 
sept. 09 13:51:50 Salmar kernel: Modules linked in: hid_generic hidp cmac ecb rfcomm bnep nls_iso8859_1 iTCO_wdt nls_cp437 vfat intel_rapl fat iosf_mbi arc4 iTCO_vendor_support x86_pkg_temp_t
sept. 09 13:51:50 Salmar kernel:  bluetooth snd_pcm tpm wmi thermal nvram iwlwifi drm_kms_helper snd_timer led_class ac video battery drm button mei_me cfg80211 snd rfkill intel_gtt i2c_algo_
sept. 09 13:51:50 Salmar kernel: CPU: 2 PID: 437 Comm: Xorg Not tainted 4.1.6-1-ARCH #1
sept. 09 13:51:50 Salmar kernel: Hardware name: LENOVO 20CDCTO1WW/20CDCTO1WW, BIOS GQET37WW (1.17 ) 06/16/2014
sept. 09 13:51:50 Salmar kernel: task: ffff8800d9bc7010 ti: ffff8800d8840000 task.ti: ffff8800d8840000
sept. 09 13:51:50 Salmar kernel: RIP: 0010:[<ffffffff811c5cae>]  [<ffffffff811c5cae>] __kmalloc_node_track_caller+0x1de/0x320
sept. 09 13:51:50 Salmar kernel: RSP: 0018:ffff8800d8843a38  EFLAGS: 00010246
sept. 09 13:51:50 Salmar kernel: RAX: 0000000000000000 RBX: ffff8800b629d800 RCX: 00000000000a8802
sept. 09 13:51:50 Salmar kernel: RDX: 00000000000a8782 RSI: 00000000000a8782 RDI: 00000000000196c0
sept. 09 13:51:50 Salmar kernel: RBP: ffff8800d8843a98 R08: 0000002d03648323 R09: ffffffff8147396b
sept. 09 13:51:50 Salmar kernel: R10: ffff88011a803500 R11: 0000000000003293 R12: 00000000000106d0
sept. 09 13:51:50 Salmar kernel: R13: 0000000000000240 R14: 00000000ffffffff R15: ffff88011a803500
sept. 09 13:51:50 Salmar kernel: FS:  00007fc5f11c0940(0000) GS:ffff88011f280000(0000) knlGS:0000000000000000
sept. 09 13:51:50 Salmar kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
sept. 09 13:51:50 Salmar kernel: CR2: 0000002d03648323 CR3: 00000000da218000 CR4: 00000000001406e0
sept. 09 13:51:50 Salmar kernel: Stack:
sept. 09 13:51:50 Salmar kernel:  ffff8800d8843a58 ffffffff810a9605 ffff88011f256280 ffff88011f256280
sept. 09 13:51:50 Salmar kernel:  ffff88011f256280 ffffffff81473997 ffff8800d8843a88 ffff8800b629d800
sept. 09 13:51:50 Salmar kernel:  ffff8800d8843b0f 00000000000004d0 0000000000000240 00000000ffffffff
sept. 09 13:51:50 Salmar kernel: Call Trace:
sept. 09 13:51:50 Salmar kernel:  [<ffffffff810a9605>] ? sched_clock_cpu+0xb5/0xe0
sept. 09 13:51:50 Salmar kernel:  [<ffffffff81473997>] ? __alloc_skb+0x87/0x210
sept. 09 13:51:50 Salmar kernel:  [<ffffffff814738b1>] __kmalloc_reserve.isra.5+0x31/0x90
sept. 09 13:51:50 Salmar kernel:  [<ffffffff8147396b>] ? __alloc_skb+0x5b/0x210
sept. 09 13:51:50 Salmar kernel:  [<ffffffff81473997>] __alloc_skb+0x87/0x210
sept. 09 13:51:50 Salmar kernel:  [<ffffffff81473b77>] alloc_skb_with_frags+0x57/0x1d0
sept. 09 13:51:50 Salmar kernel:  [<ffffffff810a5ab0>] ? wake_up_process+0x50/0x50
sept. 09 13:51:50 Salmar kernel:  [<ffffffff8146c65e>] sock_alloc_send_pskb+0x1fe/0x280
sept. 09 13:51:50 Salmar kernel:  [<ffffffff810bc5d4>] ? __wake_up_sync_key+0x54/0x70
sept. 09 13:51:50 Salmar kernel:  [<ffffffff8152d606>] unix_stream_sendmsg+0x286/0x410
sept. 09 13:51:50 Salmar kernel:  [<ffffffff81469387>] sock_sendmsg+0x17/0x30
sept. 09 13:51:50 Salmar kernel:  [<ffffffff81469425>] sock_write_iter+0x85/0xf0
sept. 09 13:51:50 Salmar kernel:  [<ffffffff811e0b18>] do_iter_readv_writev+0x68/0xa0
sept. 09 13:51:50 Salmar kernel:  [<ffffffff811e1326>] do_readv_writev+0x1a6/0x260
sept. 09 13:51:50 Salmar kernel:  [<ffffffff811fee82>] ? __fget+0x72/0xb0
sept. 09 13:51:50 Salmar kernel:  [<ffffffff811e1469>] vfs_writev+0x39/0x50
sept. 09 13:51:50 Salmar kernel:  [<ffffffff811e2259>] SyS_writev+0x59/0x100
sept. 09 13:51:50 Salmar kernel:  [<ffffffff8158bfae>] system_call_fastpath+0x12/0x71
sept. 09 13:51:50 Salmar kernel: Code: 11 5c e4 7e 74 07 e9 17 ff ff ff 66 90 e8 1c 1f 11 00 e9 0b ff ff ff 66 0f 1f 44 00 00 49 63 42 20 49 8b 3a 48 8d 8a 80 00 00 00 <49> 8b 1c 00 4c 89 c0 
sept. 09 13:51:50 Salmar kernel: RIP  [<ffffffff811c5cae>] __kmalloc_node_track_caller+0x1de/0x320

I haven't found any way to reproduce this predictably.

I have ran memtest several times and it says everything is okay.
I have done CPU and hard drive stress test, nothing seems broken on that side...

I have no idea where to look at.
I have switched to debian jessie for some time, I had no problem and it nether froze. But I missed Arch to much so I'm back... and so are the bugs

My computer is a Lenovo Thinkpad Yoga S1, it is 1 year old

If anyone has an idea where to look !

Thanks

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,659

Re: Freeze : unable to handle kernel paging request

Just a guess, but have you installed and configured the Intel Processor Microcode updates?

Also, what are the output of mount and free    ?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

ncnd

Member

Registered: 2015-09-09

Posts: 3

Re: Freeze : unable to handle kernel paging request

I had never heard about that ! I installed it and for now it seems to have fixed the problem... But as it is quite random I am not sure yet, I'll see if it happens again !

Thanks !

ncnd

Member

Registered: 2015-09-09

Posts: 3

Re: Freeze : unable to handle kernel paging request

So, updates : it just froze twice :'(

Mount output :

proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=1975916k,nr_inodes=493979,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/mapper/cryptroot on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=23,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
mqueue on /dev/mqueue type mqueue (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
/dev/sda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=396048k,mode=700,uid=1000,gid=100)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)

(My root - /dev/sda3 -> /dev/mapper/cryptroot - is encrypted using dmcrypt. I totally forgot to mention that, could it change something ?)

Free output :
(hand translated)

            total       used        free      shared       cache   available
Mem:      3960464     787848     2510368      127668      662248     2992072
Swap:      4194300         0     4194300

This time journalctl only had --reboot-- when I manually shut it down, no error message of any kind...

I really have no idea of what is going on, this is quite annoying... HALP ! ><

mich41

Member

Registered: 2012-06-22

Posts: 796

Re: Freeze : unable to handle kernel paging request

This looks like some bug in the kernel memory allocator or maybe a bug somewhere else in the kernel causing random memory corruptions. Downgrading to linux-lts or some older kernel version which worked in the past should help.