[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A1328D6.5090404@dell.com>
Date: Tue, 19 May 2009 16:47:02 -0500
From: Mario Limonciello <mario_limonciello@...l.com>
To: Oliver Neukum <oliver@...kum.org>
CC: Matthew Garrett <mjg59@...f.ucam.org>,
Marcel Holtmann <marcel@...tmann.org>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Explicitly disable BT radio using rfkill interface on
suspend
Hi Oliver:
Oliver Neukum wrote:
> Am Dienstag, 19. Mai 2009 22:36:40 schrieb Mario Limonciello:
>
>
> This error shouldn't happen. But you do get a disconnection. Please
> recheck you see no udev event and please post "lsusb -v" before and
> after suspension.
>
> Regards
> Oliver
>
Attached are both the lsusb listings. As you can see, the missing
device post-suspend is that Bluetooth radio device (which is why I
proposed this patch in the first place).
There is a udev removal event for this device, but as I said, there are
no add/remove/change events for the keyboard or mouse devices. I'm
attaching udevadm monitor ran from right before the suspend to right after.
Sending the appropriate hid report to the mouse device will re-attach
this Bluetooth radio device to the bus.
--
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@...l.com
View attachment "lsusb_postsuspend.txt" of type "text/plain" (45530 bytes)
View attachment "lsusb_presuspend.txt" of type "text/plain" (56533 bytes)
View attachment "udev.log" of type "text/x-log" (4096 bytes)
Download attachment "signature.asc" of type "application/pgp-signature" (261 bytes)
Powered by blists - more mailing lists