From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: System slow down from udev
Date: Thu, 30 May 2013 01:55:07 +0200 [thread overview]
Message-ID: <19316305.cljVYtP0Hv@vostro.rjw.lan> (raw)
In-Reply-To: <CAE9FiQV8CZN+mQvZScr16y9R1y6Tyx7uQg_DbNwE5KkHdi5H1w@mail.gmail.com>
On Wednesday, May 29, 2013 03:49:38 PM Yinghai Lu wrote:
> On Wed, May 29, 2013 at 2:34 PM, Rafael J. Wysocki <rjw@sisk.pl> 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 <rjw@sisk.pl> 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.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-05-29 23:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 23:39 Yinghai Lu
2013-05-28 23:50 ` Rafael J. Wysocki
2013-05-28 23:46 ` Yinghai Lu
2013-05-28 23:57 ` Rafael J. Wysocki
2013-05-29 0:01 ` Yinghai Lu
2013-05-29 0:30 ` Rafael J. Wysocki
2013-05-29 1:07 ` Greg Kroah-Hartman
2013-05-29 3:46 ` Yinghai Lu
2013-05-29 11:29 ` Rafael J. Wysocki
2013-05-29 20:13 ` Yinghai Lu
2013-05-29 21:34 ` Rafael J. Wysocki
[not found] ` <CAE9FiQV8CZN+mQvZScr16y9R1y6Tyx7uQg_DbNwE5KkHdi5H1w@mail.gmail.com>
2013-05-29 23:55 ` Rafael J. Wysocki [this message]
2013-05-30 0:20 ` Rafael J. Wysocki
2013-05-30 2:12 ` Yinghai Lu
2013-05-30 1:55 ` Yinghai Lu
2013-05-30 14:34 ` Rafael J. Wysocki
2013-05-30 14:45 ` Rafael J. Wysocki
2013-05-30 16:36 ` Rafael J. Wysocki
2013-05-30 17:42 ` Yinghai Lu
2013-05-30 17:49 ` Yinghai Lu
2013-05-30 19:48 ` Rafael J. Wysocki
2013-05-30 18:12 ` Yinghai Lu
2013-05-30 19:49 ` [PATCH] ACPI / processor: Initialize per_cpu(processors, pr->id) properly (Re: System slow down from udev) Rafael J. Wysocki
2013-05-30 19:46 ` System slow down from udev Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19316305.cljVYtP0Hv@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®