From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Xen-devel <Xen-devel@lists.xensource.com>,
Carsten Schiers <carsten@schiers.de>
Subject: Re: Kernel Warning
Date: Thu, 25 Aug 2011 15:37:30 -0700 [thread overview]
Message-ID: <4E56CEAA.8060907@goop.org> (raw)
In-Reply-To: <1314301188.31709.1.camel@dagon.hellion.org.uk>
On 08/25/2011 12:39 PM, Ian Campbell wrote:
> On Thu, 2011-08-25 at 20:31 +0100, Carsten Schiers wrote:
>> Is that a Xen thing that anybody's interested in?
> It's a harmless warning but it gets reported a lot and it taints the
> kernel which causes some confusion is there is subsequently another
> error. I proposed toning it down a bit a couple of days ago:
> http://marc.info/?l=xen-devel&m=131400621622691
I'd tend towards just silently eating APIC writes, unless we want to go
through and try to silence each one at the source.
J
next prev parent reply other threads:[~2011-08-25 22:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 4:24 linux-next: manual merge of the xen tree with the tip tree Stephen Rothwell
2011-08-25 18:13 ` Jeremy Fitzhardinge
2011-08-25 18:26 ` H. Peter Anvin
2011-08-25 18:26 ` H. Peter Anvin
2011-08-25 19:31 ` Kernel Warning Carsten Schiers
2011-08-25 19:39 ` Ian Campbell
2011-08-25 22:37 ` Jeremy Fitzhardinge [this message]
2011-08-25 23:06 ` linux-next: manual merge of the xen tree with the tip tree Stephen Rothwell
2011-08-25 23:12 ` H. Peter Anvin
2011-08-26 2:54 ` Stephen Rothwell
2011-09-13 11:11 ` Stephen Rothwell
2011-09-13 15:07 ` Thomas Gleixner
2011-09-13 20:53 ` Jeremy Fitzhardinge
2011-09-13 20:56 ` Thomas Gleixner
2011-09-13 21:00 ` Jeremy Fitzhardinge
2011-09-14 0:32 ` Stephen Rothwell
2011-09-14 0:41 ` Jeremy Fitzhardinge
2011-09-14 0:48 ` Stephen Rothwell
[not found] <Pine.GSO.4.33.0210301642520.22794-100000@raven>
2002-10-30 21:56 ` kernel warning Russell Coker
-- strict thread matches above, loose matches on Subject: below --
2002-10-27 4:23 Brian May
2002-10-28 12:57 ` Stephen Smalley
2002-10-28 22:53 ` Brian May
2002-10-28 23:00 ` Russell Coker
2002-10-29 23:07 ` Brian May
2002-10-30 13:23 ` Stephen Smalley
2002-10-30 15:13 ` Russell Coker
2002-10-30 19:48 ` Stephen Smalley
2002-10-30 22:08 ` Brian May
2002-10-30 22:21 ` Stephen Smalley
2002-10-30 22:22 ` Russell Coker
2002-10-30 22:49 ` Stephen Smalley
2002-10-30 22:03 ` Brian May
2002-10-30 19:43 ` Kerry Thompson
2002-10-30 19:54 ` Stephen Smalley
2002-05-09 15:29 Robert Singleton
2002-05-09 17:24 ` Vladimir G. Ivanovic
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=4E56CEAA.8060907@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=carsten@schiers.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.