2011/2/24 Michael Biebl :
> Has anyone investigated, why the lockup occurs and if this can be fixed in the
> driver/kernel. Has this problem been reported upstream to the Linux kernel
> guys
> resp. the bluetooth maintainers?
>
> I would very much prefer this instead over working around the proble
2011/2/24 Martin Pitt :
> Hello Lin,
>
> Keng-Yu Lin [2011-02-24 14:49 +0800]:
>> +btusbget() {
>> + local dev usb
>> + usb="/sys/bus/usb/devices"
>> + for dev in "$usb"/*; do
>> + [[ -f "${dev}/bDeviceClass" ]] || continue
>> + [[ "$(cat "${dev}/bDeviceClass")" = "e0" ]] || contin
Am 24.02.2011 10:34, schrieb Martin Pitt:
> program call. Can you please confirm that this still works on your
> system? This should also be forwarded upstream, but Michael and I can
> also take care of that.
Has anyone investigated, why the lockup occurs and if this can be fixed in the
driver/ker
Hello Lin,
Keng-Yu Lin [2011-02-24 14:49 +0800]:
> +btusbget() {
> +local dev usb
> +usb="/sys/bus/usb/devices"
> +for dev in "$usb"/*; do
> + [[ -f "${dev}/bDeviceClass" ]] || continue
> + [[ "$(cat "${dev}/bDeviceClass")" = "e0" ]] || continue # Wireless
> + [[ -f "${dev}
For those who are interested, the bug is also tracked at
http://launchpad.net/bugs/715643 for Ubuntu.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
From 8dd91340660a14c55d12372a3e9a767863b7f316 Mon Sep 17 00:00:00 2001
From: Keng-Yu Lin
Date: Thu, 24 Feb 2011 13:59:14 +0800
Subject: [PATCH] Add the quirk support for stoping/restarting bluetooth service
It is found that the bluetooth modules with USB VID/PIDs [0a5c:219c]
[0a5c:21bc] and [413
It is found that the bluetooth modules with USB VID/PIDs [0a5c:219c]
[0a5c:21bc] and [413c:8187] is causing random S4 hangs on various
laptops with SandyBridge chipset.
The hans can be observed by repeating hibernate/resume in a 250
iterations with fwft. The successful cycles number before the han
7 matches
Mail list logo
