linux-kernel - Re: Bluetooth related possible system hard lockups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87twrurisy.fsf@intel.com>
Date:	Wed, 19 Aug 2015 19:54:05 -0300
From:	Vinicius Costa Gomes <vinicius.gomes@...el.com>
To:	Jamin Collins <jamin.collins@...il.com>,
	linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Bluetooth related possible system hard lockups

Hi Jamin,

Jamin Collins <jamin.collins@...il.com> writes:

> I've recently started experiencing what appear to be hard lockups on
> what has otherwise been a very solid system (Lenovo W530 Thinkpad).
> I'm running a fully updated Arch Linux install on it, and have been
> for a few months (since roughly April of this year).  Just before
> experiencing these lockups I started using a bluetooth mouse.
>
> When the apparent lockup occurs:
> - the laptop screen seems to be off (no display)
> - the CPU fan is running at a moderate speed (not the slowest, and not
> the fastest)
> - no apparent disk activity
> - nothing in journalctl (when I hard reset I find only a gap, last
> entry hours before)
> - unresponsive to network requests (ping, etc)
>
> The only way I've found to recover the system thus far is a hard reset
> (hold power for 4+ seconds).
>

Without more information (the backtrace of the crash, from the kernel
logs or even a picture of the screen showing the crash dump), it is hard
to be sure. I can only guess.

This looks like this issue (for one colleague on a very similar setup as
yours, it was the case):

http://thread.gmane.org/gmane.linux.kernel.input/45023

I just checked, that patch is in the stable queue, and for little it
missed the 4.1.6 deadline, but it should appear on 4.1.7 (if it is
released) or 4.2 (for sure).

You can also apply that patch locally and see if solves your problem,
or you can give the input subsystem kernel tree a try:

https://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git


Cheers,
--
Vinicius
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/