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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 19 Aug 2015 14:09:01 -0700
From:	Jamin Collins <jamin.collins@...il.com>
To:	linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Bluetooth related possible system hard lockups

Issue Update

I have not been successful in reproducing the issue *without*
connecting a bluetooth device at least once.

I have however actually witnessed the lockup now:
- the screen does *not* turn off as part of the lockup
- initially the keyboard was non-responsive
- after a few seconds of use the jmouse stopped responding
- was able to momentarily reconnect the bluetooth mouse and then it
too stopped responding

On Wed, Aug 19, 2015 at 1:04 PM, Jamin Collins <jamin.collins@...il.com> wrote:
> 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).
>
> I know it involves bluetooth being on, possibly requires having
> connected a device, and then some indeterminate amount of time away
> from the system (lack of user interaction).  I'm currently testing
> with bluetooth on, but no device connected to see if the issue occurs.
>
> The kernel in question:
> Linux version 4.1.5-1-ARCH (builduser@...ias) (gcc version 5.2.0 (GCC)
> ) #1 SMP PREEMPT Tue Aug 11 15:41:14 CEST 2015
>
> Bluetooth:
> Bluetooth daemon 5.33
>
> The bluetooth device I've been using is a Thinkpad Bluetooth Laser Mouse:
> ThinkPad Bluetooth Laser Mouse as
> /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/0005:17EF:6002.0001/input/input19
>
> I'm not subscribed to this list, so please CC me on replies.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ