On Thu, Jan 12, 2017 at 08:06:46PM +0100, Christoph Anton Mitterer wrote: > On Thu, 2017-01-12 at 18:24 +0100, Greg KH wrote: > > What kworker process causes this? Does it have a name? > How do I find out? Or do you mean the /0:3 which is contained in the > top output below? Yes, thanks, I saw it later on. > > > # perf top -p 2359 gives something like that: > > > Samples: 64K of event 'cycles:ppp', Event count (approx.): > > > 19127246624 > > > Overhead Shared Object Symbol > > > 19,91% [kernel] [k] acpi_ns_search_one_scope > > > 11,18% [kernel] [k] acpi_os_write_port > > > 8,51% [kernel] [k] pci_conf1_read > > > 7,59% [kernel] [k] acpi_ex_system_memory_space_handler > > > 3,57% [kernel] [k] acpi_os_read_port > > > 2,84% [kernel] [k] kmem_cache_alloc > > > 2,27% [kernel] [k] acpi_ut_get_next_predefined_method > > > 1,96% [kernel] [k] nmi > > > > Looks like acpi is going crazy, maybe lots of different ACPI events? > > Have you asked the ACPI developers about this? > Not yet - for starters didn't want to cross post on too many lists ;-) > Shall I forward it to linux-acpi? Please do. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
