From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967297Ab3E3ALu (ORCPT ); Wed, 29 May 2013 20:11:50 -0400 Received: from hydra.sisk.pl ([212.160.235.94]:54430 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966530Ab3E3ALr (ORCPT ); Wed, 29 May 2013 20:11:47 -0400 From: "Rafael J. Wysocki" To: Yinghai Lu Cc: Greg Kroah-Hartman , ACPI Devel Maling List , Linux Kernel Mailing List Subject: Re: System slow down from udev Date: Thu, 30 May 2013 02:20:41 +0200 Message-ID: <5422298.byNmKLLQxX@vostro.rjw.lan> User-Agent: KMail/4.9.5 (Linux/3.10.0-rc3+; KDE/4.9.5; x86_64; ; ) In-Reply-To: <19316305.cljVYtP0Hv@vostro.rjw.lan> References: <19316305.cljVYtP0Hv@vostro.rjw.lan> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday, May 30, 2013 01:55:07 AM Rafael J. Wysocki wrote: > On Wednesday, May 29, 2013 03:49:38 PM Yinghai Lu wrote: > > On Wed, May 29, 2013 at 2:34 PM, Rafael J. Wysocki wrote: > > > On Wednesday, May 29, 2013 01:13:46 PM Yinghai Lu wrote: > > >> On Wed, May 29, 2013 at 4:29 AM, Rafael J. Wysocki wrote: > > >> > On your systems the processor driver is built-in. Any chance to build it as > > >> > a module and see if that helps? > > >> > > >> it CONFIG_ACPI_PROCESSOR it not set in the config > > >> the boot get to normal speed. > > > > > > Well, if it is not set at all, there won't be problems with it. :-) > > > > > > I've tested my linux-next branch on OpenSUSE 11.3 both with the processor > > > driver built in and modular and I'm not able to reproduce the issue you're > > > seeing. > > > > > > Moreover, I'm not sure if user space is involved here at all, because the > > > problem triggers for you when all of the relevant kernel code is non-modular. > > > > > > With the processor driver enabled, when the slowdown happens, are the systems > > > usable enough to get some debug info out of them? > > > > please check the bootchart data. > > > > looks like it take 200s if no acpi_processor ... > > otherwise will take 800s or more. > > Well, something's fishy for sure. > > To my eyes it looks like we're getting lots of notifications related to the > processor driver and that generates a lot of workqueue load. > > Can you please get /proc/interrupts from both cases and the output of > "find /sys/firmware/acpi/interrupts/ -print -exec cat {} \;"? > > Also please send the output of "ls -l /sys/devices/system/cpu/cpu*" with the > processor driver present. Well, this is kind of a blind shot, but I'm wondering if the appended patch makes any difference? Rafael --- drivers/acpi/processor_driver.c | 3 --- 1 file changed, 3 deletions(-) Index: linux-pm/drivers/acpi/processor_driver.c =================================================================== --- linux-pm.orig/drivers/acpi/processor_driver.c +++ linux-pm/drivers/acpi/processor_driver.c @@ -87,9 +87,6 @@ static void acpi_processor_notify(acpi_h struct acpi_processor *pr; int saved; - if (device->handle != handle) - return; - pr = acpi_driver_data(device); if (!pr) return;