On Wednesday, 27 of August 2008, Oliver Neukum wrote: > Am Mittwoch 27 August 2008 01:28:15 schrieb Rafael J. Wysocki: > > > 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. > > Now we know a driver without support for suspend/resume breaks suspend and > hibernate. We need to find out whether this is limited to btusb or everything. I'm quite confident it's specific to bluetooth, because I only need to turn the bluetooth user space off, most importantly hcid, to make the problem go away even without the patch (that is, without the patch I don't even have to uload btusb before suspend if the bluetoot user land is not running). > Can you test with anotherrrrr driver, like a mouse and remove suspend/resume > from usbhid? If this is specific to btusb we have a fix, if not, I am afraid > this has to be bisected. Is that really necessary? I can do that, but first I'll check if 2.6.26 is fine. 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
