Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752287AbbHSWyJ (ORCPT ); Wed, 19 Aug 2015 18:54:09 -0400 Received: from mga03.intel.com ([134.134.136.65]:8872 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751199AbbHSWyI (ORCPT ); Wed, 19 Aug 2015 18:54:08 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,712,1432623600"; d="scan'208";a="787369974" From: Vinicius Costa Gomes To: Jamin Collins , linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Bluetooth related possible system hard lockups In-Reply-To: References: User-Agent: Notmuch/0.19 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Wed, 19 Aug 2015 19:54:05 -0300 Message-ID: <87twrurisy.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1805 Lines: 50 Hi Jamin, Jamin Collins 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/