Frans Pop wrote: > On Wednesday 29 July 2009, Rafael J. Wysocki wrote: > >> On Wednesday 29 July 2009, you wrote: >> >>> Just for testing I enabled HP_WMI. But from then, I could not resume >>> anymore. I just reverted the last git commit on the >>> 'drivers/platform/x86/hp-wmi.c' code >>> (4c395bdd3f2ca8f7e8efad881e16071182c3b8ca) and now I can resume. The >>> problem still persists on .31-rc serie >>> >> Frans, that's something for you to take care of. >> > > I'll at least give it a try. > > Cedric, as a start, can you please provide the output of the following > commands after the system is booted and with hp-wmi loaded: > $ grep . /sys/devices/platform/hp-wmi/* > $ ls -l /dev/input/* > $ cat /proc/bus/input/devices > > Does an unload and reload of the module work correctly? What gets output > in dmesg by that? > > The strange thing is that the resume function does not do anything that's > not also done in hp_wmi_input_setup(). The only thing I can think of is > that we might need to test for wmi_has_guid(HPWMI_EVENT_GUID) because > that model simply does not support input events. > > Cheers, > FJP > I tested your patch (from buzilla) and now I can resume. Thanks ! You have my tested-by ;-) PS: I suppose you don't need this infos anymore ? -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
