From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: linux-kernel@vger.kernel.org, oprofile-list@lists.sf.net,
Robert Richter <robert.richter@amd.com>
Subject: Re: oprofile: WQ on CPU0, prefer CPU1
Date: Sat, 16 May 2009 22:49:47 -0700 [thread overview]
Message-ID: <20090516224947.05067f96.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090514202214.14243n1debrzobx2@mail.your-server.de>
(cc's added, from MAINTAINERS)
On Thu, 14 May 2009 20:22:14 +0200 Thomas Meyer <thomas@m3y3r.de> wrote:
>
> After suspend and resume to/from S3 I see a lot of these messages in
> the kernel log:
>
> [11750.054031] WQ on CPU0, prefer CPU1
> [11750.154023] WQ on CPU0, prefer CPU1
> [11750.254022] WQ on CPU0, prefer CPU1
> [11750.354022] WQ on CPU0, prefer CPU1
> [11750.454018] WQ on CPU0, prefer CPU1
> [11750.554022] WQ on CPU0, prefer CPU1
> [11750.654022] WQ on CPU0, prefer CPU1
> [11750.754039] WQ on CPU0, prefer CPU1
> [11750.854020] WQ on CPU0, prefer CPU1
> [11750.954024] WQ on CPU0, prefer CPU1
> [11751.054029] WQ on CPU0, prefer CPU1
> [11751.154028] WQ on CPU0, prefer CPU1
> [11751.254026] WQ on CPU0, prefer CPU1
> [11751.354019] WQ on CPU0, prefer CPU1
> [11751.454022] WQ on CPU0, prefer CPU1
> [11751.554032] WQ on CPU0, prefer CPU1
> [11751.654028] WQ on CPU0, prefer CPU1
> [11751.754028] WQ on CPU0, prefer CPU1
> [11751.854033] WQ on CPU0, prefer CPU1
> [11751.954029] WQ on CPU0, prefer CPU1
> [and so on; seems not to stop]
>
> This comes from drivers/oprofile/cpu_buffer.c
>
> Bug or feature?
>
Don't know. It needs fixing though - the kernel shouldn't blurt random
printks like this.
>
> PS: 2.6.30-rc5
Do you know if earlier kernels did the same thing?
next prev parent reply other threads:[~2009-05-17 5:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 18:22 oprofile: WQ on CPU0, prefer CPU1 Thomas Meyer
2009-05-17 5:49 ` Andrew Morton [this message]
2009-05-17 13:03 ` Thomas Meyer
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=20090516224947.05067f96.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sf.net \
--cc=robert.richter@amd.com \
--cc=thomas@m3y3r.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.