Hi, could this patchset eventually help here: kacpi* eat a lot of cpu after s2disk https://bugzilla.novell.com/show_bug.cgi?id=401740 This seem to happen on all recent Dells. Shaohua Li, Andi: Can you keep me up to date about these patches, pls If Andi thinks they are suitable for mainline, I'd like to add them to our recent codebase. Or is there a chance that these (or some critical ones) go into .27-rcX? Thanks, Thomas On Thursday 28 August 2008 04:02:03 Shaohua Li wrote: > In some BIOSes, every _STA method call will send a notification again, > this cause freeze. And in some BIOSes, it appears _STA should be called > after _DCK. This tries to avoid calls _STA, and still keep the device > present check. > http://bugzilla.kernel.org/show_bug.cgi?id=10431 > > Signed-off-by: Shaohua Li <shaohua.li@xxxxxxxxx> > --- > drivers/acpi/dock.c | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) > > Index: linux/drivers/acpi/dock.c > =================================================================== > --- linux.orig/drivers/acpi/dock.c 2008-08-27 14:38:44.000000000 +0800 > +++ linux/drivers/acpi/dock.c 2008-08-28 09:33:02.000000000 +0800 > @@ -604,14 +604,17 @@ static int handle_eject_request(struct d > static void dock_notify(acpi_handle handle, u32 event, void *data) > { > struct dock_station *ds = data; > + struct acpi_device *tmp; > > switch (event) { > case ACPI_NOTIFY_BUS_CHECK: > - if (!dock_in_progress(ds) && dock_present(ds)) { > + if (!dock_in_progress(ds) && acpi_bus_get_device(ds->handle, > + &tmp)) { > begin_dock(ds); > dock(ds); > if (!dock_present(ds)) { > printk(KERN_ERR PREFIX "Unable to dock!\n"); > + complete_dock(ds); > break; > } > atomic_notifier_call_chain(&dock_notifier_list, > > > -- > 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 -- 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
