FS#45784 - [linux] Computer freezes since upgrade to 4.1.X kernel

Attached to Project: Arch Linux
Opened by Matt Leach (hexsun) - Sunday, 26 July 2015, 13:54 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 18 October 2017, 09:36 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Hello,

Since the 4.1.X kernel has been released my laptop (a thinkpad T440) has started to crash. The crash can occur from anytime within five minutes to a couple of hours of uptime. I can't seem to find anything specific that triggers the freeze. There is a kernel oops on line 448 of the boot log that I suspect is the problem as when I downgrade to the 4.0.7 kernel, this oops doesn't occur and the laptop doesn't freeze.

After a freeze, I can't see anything in the logs about a kernel panic which is making me think this is some kind of serious fault as the kernel doesn't even have chance to log any output.

I have attached a boot log, as well as the output from /proc/cpuinfo.

If anymore info is needed, please let me know.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 18 October 2017, 09:36 GMT
Reason for closing:  No response
Comment by Nicholas Yim (nyim) - Wednesday, 29 July 2015, 10:08 GMT
everytime, I try lspci, my computer(thinkpad t440p) freeze.
even boot from archlinux-2015.07.01-dual.iso usb disk
Comment by AJ (aminjam) - Thursday, 30 July 2015, 23:39 GMT
`lspci` doesn't seem to the the cause of my issue, but I am experiencing random freezes on my Thinkpad T450s quite often as well.
Comment by Matt Leach (hexsun) - Friday, 31 July 2015, 07:22 GMT
Agreed, lspci doesn't cause me any issues. I'm still experiencing random freezing still.
Comment by Markus Gabsdiel (dagget86) - Thursday, 06 August 2015, 16:25 GMT
Same Problem with my Thinkpad T420.
Kernel panic after random uptime, sometimes with blinking CapsLock, but nothing in the log.

Since now, kernel panic showed to me 2 times.

http://s25.postimg.org/97c7htsbz/20150729_213751.jpg and
http://s25.postimg.org/dp16o2l67/20150803_205522.jpg
   journal.txt (108.4 KiB)
Comment by Matt Leach (hexsun) - Thursday, 06 August 2015, 17:25 GMT
I've been doing some rebasing and after reverting commit 15c1247953e8a45232ed5a5540f291d2d0a77665 I see no warning on my boot log. I'm hoping that this will also fix the freezing issue, but I'll need to work on my laptop for a while until I'm sure.

I've notified the kernel folks about this,linux-kernel@vger.kernel.org/msg949949.html"> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg949949.html
Comment by Adriano M (Adry88) - Thursday, 06 August 2015, 21:47 GMT
Same problem on my Samsung np900x3c, since kernel 4.1.x, the freeze occurs only when there are bluetooth devices connected after some time (maybe when devices go in sleep mode)
Downgraded to 4.0.7 without any freeze.

Journal:

ago 04 09:26:13 arch-book kernel: general protection fault: 0000 [#1] PREEMPT SMP
ago 04 09:26:13 arch-book kernel: Modules linked in: tun hidp rfcomm cmac ecb bnep joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core btusb v4l2_common btbcm btintel videodev bluetooth media crc16 zram lz4_compress tpm_inf
ago 04 09:26:13 arch-book kernel: tpm_tis snd_pcm snd_timer intel_gtt snd mei_me battery soundcore i2c_algo_bit mei i2c_core tpm video wmi button ac processor sch_fq_codel ip_tables x_tables btrfs xor raid6_pq sd_mod atkbd libps2 crc32c
ago 04 09:26:13 arch-book kernel: CPU: 0 PID: 1929 Comm: konsole Not tainted 4.1.4-1-ARCH #1
ago 04 09:26:13 arch-book kernel: Hardware name: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D/SAMSUNG_NP1234567890, BIOS P07AAC 11/18/2013
ago 04 09:26:13 arch-book kernel: task: ffff88006a0dbd20 ti: ffff8800097a0000 task.ti: ffff8800097a0000
ago 04 09:26:13 arch-book kernel: RIP: 0010:[<ffffffff810ab37e>] [<ffffffff810ab37e>] effective_load.isra.8+0xe/0xa0
ago 04 09:26:13 arch-book kernel: RSP: 0018:ffff8800097a3b80 EFLAGS: 00010046
ago 04 09:26:13 arch-book kernel: RAX: 0000000000000400 RBX: 0000000000000002 RCX: 0000000000000400
ago 04 09:26:13 arch-book kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 7774654e2e706f74
ago 04 09:26:13 arch-book kernel: RBP: ffff8800097a3c38 R08: 0000000000000400 R09: 000000000000f87c
ago 04 09:26:13 arch-book kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000010
ago 04 09:26:13 arch-book kernel: R13: ffff88011a88b600 R14: 0000000000000000 R15: ffff88004bf45400
ago 04 09:26:13 arch-book kernel: FS: 00007f8d75f75840(0000) GS:ffff88011f200000(0000) knlGS:0000000000000000
ago 04 09:26:13 arch-book kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
ago 04 09:26:13 arch-book kernel: CR2: 0000000002488e78 CR3: 00000000096cb000 CR4: 00000000001407f0
ago 04 09:26:13 arch-book kernel: Stack:
ago 04 09:26:13 arch-book kernel: ffffffff810aca0a ffff880000000001 ffffffff810bbfc5 ffff88006a0df010
ago 04 09:26:13 arch-book kernel: 00000000000000c3 ffff8800097a3c38 ffff880009670a80 0000000000000001
ago 04 09:26:13 arch-book kernel: 0000000000000010 0000000000000000 000000000000f87c 0000000000000400
ago 04 09:26:13 arch-book kernel: Call Trace:
ago 04 09:26:13 arch-book kernel: [<ffffffff810aca0a>] ? select_task_rq_fair+0x5fa/0x740
ago 04 09:26:13 arch-book kernel: [<ffffffff810bbfc5>] ? __wake_up_common+0x55/0x90
ago 04 09:26:13 arch-book kernel: [<ffffffff810a57e9>] try_to_wake_up+0x129/0x350
ago 04 09:26:13 arch-book kernel: [<ffffffff810a5a90>] wake_up_state+0x10/0x20
ago 04 09:26:13 arch-book kernel: [<ffffffff81085182>] signal_wake_up_state+0x22/0x40
ago 04 09:26:13 arch-book kernel: [<ffffffff81085790>] complete_signal+0x110/0x260
ago 04 09:26:13 arch-book kernel: [<ffffffff81085a91>] __send_signal+0x1b1/0x410
ago 04 09:26:13 arch-book kernel: [<ffffffff81085d2e>] send_signal+0x3e/0x80
ago 04 09:26:13 arch-book kernel: [<ffffffff810869b2>] do_send_sig_info+0x52/0xa0
ago 04 09:26:13 arch-book kernel: [<ffffffff81086caf>] group_send_sig_info+0x4f/0x60
ago 04 09:26:13 arch-book kernel: [<ffffffff81086deb>] kill_pid_info+0x3b/0x70
ago 04 09:26:13 arch-book kernel: [<ffffffff8108878a>] SyS_kill+0xaa/0x200
ago 04 09:26:13 arch-book kernel: [<ffffffff81066bef>] ? __do_page_fault+0x18f/0x4b0
ago 04 09:26:13 arch-book kernel: [<ffffffff8158beae>] system_call_fastpath+0x12/0x71
ago 04 09:26:13 arch-book kernel: Code: ff 48 c7 41 48 00 00 00 00 48 8b 90 48 01 00 00 48 85 d2 75 d8 e9 09 ff ff ff 0f 1f 00 0f 1f 44 00 00 48 63 d2 48 85 f6 48 89 c8 <48> 8b 3c d7 0f 84 82 00 00 00 48 85 ff 74 7d 55 41 bb 02 00 00
ago 04 09:26:13 arch-book kernel: RIP [<ffffffff810ab37e>] effective_load.isra.8+0xe/0xa0
-- Reboot --
Comment by Matt Leach (hexsun) - Thursday, 06 August 2015, 22:08 GMT
The boot warning has been fixed with a patch (see above thread). However, I'm still experiencing bad crashes, I've noticed that they tend to happen after coming out of RAM suspend, but can occur at other times too. I've tried using kdump and magic sysrq to get some kind of info about why the crash occurred but the system has totally locked up. Any ideas of how to debug this, folks?

The bluetooth connection that Adriano mentions is interesting, as I have a bluetooth mouse that I use. I will try disabling the bluetooth controller and see if that prevents the crash.
Comment by Matt Leach (hexsun) - Friday, 07 August 2015, 16:47 GMT
It's looking like this is a duplicate of bug #45787. I've narrowed the issue down to when I disconnect my bluetooth mouse, as stated in the bug report.
Comment by cirrus (cirrus) - Monday, 24 August 2015, 13:14 GMT
same same today on two archlinux x64 installs when updated to 4.1.6-1 , downgrading to 4.1.5-1 brought both installs back up, sorry didnt read #46092
Comment by mattia (nTia89) - Monday, 02 October 2017, 20:19 GMT
is this issue still valid?

Loading...