On Tuesday, 26 of August 2008, Oliver Neukum wrote: > Am Dienstag 26 August 2008 20:44:53 schrieb Rafael J. Wysocki: > > On Tuesday, 26 of August 2008, Stefan Seyfried wrote: > > > On Tue, Aug 26, 2008 at 12:10:08PM +0200, Rafael J. Wysocki wrote: > > > > > Good. Can you test what happens if you unplug the device while suspended > > > > > and hibernated? > > > > > > > > It's built-in, I can't unplug it. :-) > > > > > > Maybe you can disable it in the BIOS, but this might change the DSDT / other > > > system configuration, so it might break resume in other ways :-( > > > > There is a switch that's supposed to disable the radio (rfkill or something). > > I used it to switch the radio off while the box was waking up from hibernation > > and kbluetooth didn't find the adapter after the resume. After I've pressed > > the "radio off" button again, the bluetooth appears to be functional again. > > > > However, this "radio off" button is shared between bluetooth and wireless > > (b43) and there are some surprising interactions. Nothing seems to be broken, > > though. > > This doesn't explain the original failure. Can you comment out the support > for suspend/resume in the driver and try again? With that commented out, I'm able to reproduce the failure. With the original patch, I'm not. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
