From: Andreas Mohr <andi@lisas.de>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>,
Prarit Bhargava <prarit@redhat.com>,
Don Zickus <dzickus@redhat.com>, Don Dutile <ddutile@redhat.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Asit Mallick <asit.k.mallick@intel.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] irq: add quirk for broken interrupt remapping on 55XX chipsets
Date: Sat, 2 Mar 2013 16:59:42 +0100 [thread overview]
Message-ID: <20130302155942.GA353@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <1362158276-4901-1-git-send-email-nhorman@tuxdriver.com>
Hi,
> if ((revision == 0x13) && irq_remapping_enabled) {
> + pr_warn("WARNING WARNING WARNING WARNING WARNING
> WARNING\n"
> + "This system BIOS has enabled interrupt
> remapping\n"
> + "on a chipset that contains an errata making
> that\n"
> + "feature unstable. Please reboot with
> nointremap\n"
> + "added to the kernel command line and contact\n"
> + "your BIOS vendor for an update");
> + }
Forgive me, but ISTR that there's a special BIOS firmware quirk bug annotating
logger warning message mechanism (have I managed to hit all keywords yet? ;)
in the kernel which might be useful in this case.
OK, found something (but I don't think it was the mechanism
that ISTR - perhaps it got modernized?):
include/linux/printk.h:
/*
* FW_BUG
* Add this to a message where you are sure the firmware is buggy or
* behaves
* really stupid or out of spec. Be aware that the responsible BIOS
* developer
* should be able to fix this issue or at least get a concrete idea of
* the
* problem by reading your message without the need of looking at the
* kernel
* code.
*
* Use it for definite and high priority BIOS bugs.
*
* FW_WARN
* Use it for not that clear (e.g. could the kernel messed up things
* already?)
* and medium priority BIOS bugs.
*
* FW_INFO
* Use this one if you want to tell the user or vendor about something
* suspicious, but generally harmless related to the firmware.
*
* Use it for information or very low priority BIOS bugs.
*/
So perhaps it is appropriate to be used here.
HTH,
Andreas Mohr
next prev parent reply other threads:[~2013-03-02 15:59 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 17:17 Neil Horman
2013-03-01 18:20 ` Yinghai Lu
2013-03-01 19:29 ` Neil Horman
2013-03-02 2:28 ` Jiang Liu
2013-03-02 15:59 ` Andreas Mohr [this message]
2013-03-04 13:24 ` Don Dutile
2013-03-10 1:11 ` Prarit Bhargava
2013-03-02 16:21 ` Prarit Bhargava
2013-03-02 20:13 ` Neil Horman
2013-03-04 19:04 ` [PATCH v2] " Neil Horman
2013-03-09 20:49 ` Neil Horman
2013-03-09 22:20 ` Myron Stowe
2013-03-11 1:31 ` Don Dutile
2013-03-11 11:25 ` Neil Horman
2013-03-11 12:17 ` Prarit Bhargava
2013-04-03 23:53 ` Bjorn Helgaas
2013-04-04 11:17 ` Neil Horman
2013-04-04 14:27 ` David Woodhouse
2013-04-04 14:50 ` Neil Horman
2013-04-04 14:57 ` Bjorn Helgaas
2013-04-04 15:39 ` Neil Horman
2013-04-04 17:14 ` Bjorn Helgaas
2013-04-04 17:51 ` Neil Horman
2013-04-04 18:41 ` Bjorn Helgaas
2013-04-04 20:02 ` Neil Horman
2013-04-04 13:54 ` [PATCH v3] " Neil Horman
2013-04-04 15:08 ` [PATCH v4] " Neil Horman
2013-04-04 16:16 ` Yinghai Lu
2013-04-04 17:27 ` Don Dutile
2013-04-04 17:40 ` Yinghai Lu
2013-04-04 20:04 ` Neil Horman
2013-04-04 20:33 ` Bjorn Helgaas
2013-04-04 21:11 ` Yinghai Lu
2013-04-05 0:24 ` Neil Horman
2013-04-05 19:25 ` [PATCH v5] " Neil Horman
2013-04-05 19:29 ` Neil Horman
2013-04-05 19:31 ` [PATCH v6] " Neil Horman
2013-04-05 23:37 ` Yinghai Lu
2013-04-06 1:55 ` Bjorn Helgaas
2013-04-08 15:29 ` Don Dutile
2013-04-08 17:17 ` Bjorn Helgaas
2013-04-08 17:42 ` Neil Horman
2013-04-09 10:08 ` Joerg Roedel
2013-04-15 11:18 ` [PATCH v7] " Neil Horman
2013-04-15 15:30 ` Bjorn Helgaas
2013-04-15 16:28 ` Neil Horman
2013-04-15 16:28 ` [PATCH v8] " Neil Horman
2013-04-15 22:41 ` [PATCH v9] " Neil Horman
2013-04-15 23:02 ` Yinghai Lu
2013-04-16 0:43 ` Neil Horman
2013-04-16 6:20 ` Arkadiusz Miskiewicz
2013-04-16 10:24 ` Joerg Roedel
2013-04-16 13:07 ` Neil Horman
2013-04-16 13:35 ` Neil Horman
2013-04-16 16:37 ` Joerg Roedel
2013-04-16 17:25 ` Neil Horman
2013-04-16 20:38 ` [PATCH v10] " Neil Horman
2013-04-16 22:08 ` Don Dutile
2013-04-18 15:02 ` Joerg Roedel
2013-04-18 17:00 ` Neil Horman
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=20130302155942.GA353@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=asit.k.mallick@intel.com \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=prarit@redhat.com \
/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®