mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: False positive "do_IRQ: #.55 No irq handler for vector" messages on AMD ryzen based laptops
Date: Wed, 6 Mar 2019 09:41:23 +0100	[thread overview]
Message-ID: <e8d1128f-ff81-3dc9-90ae-86ce5d8f69b2@redhat.com> (raw)
In-Reply-To: <20190305195432.GI8256@zn.tnic>

Hi,

On 05-03-19 20:54, Borislav Petkov wrote:
> On Tue, Mar 05, 2019 at 08:40:02PM +0100, Hans de Goede wrote:
>> Finger pointing at the firmware if there are multiple vendors involved
>> is really not going to help here. Esp. since most OEMs will just respond
>> with "the machine works fine with Windows"
> 
> Yes, because windoze simply doesn't report that spurious IRQ, most
> likely.

So maybe we need to lower the priority of the do_IRQ error from pr_emerg
to pr_err then ?  That will stop throwing the errors in the users face each
boot on distros which have chosen to set the quiet loglevel to such a level
that pr_err messages are not shown on the console (*).

Regards,

Hans


*) Since there are simply too much false-positive pr_err messages in the kernel,
try e.g. plugging in a usb-stick and then do "dmesg -level=err"
Note the messages will still be in dmesg and in the system logs


  reply	other threads:[~2019-03-06  8:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 15:53 Hans de Goede
2019-02-19 21:01 ` Thomas Gleixner
2019-02-19 21:47   ` Lendacky, Thomas
2019-02-21 12:30     ` Hans de Goede
2019-03-03 10:57       ` Hans de Goede
2019-03-05 14:06         ` Lendacky, Thomas
2019-03-05 16:02           ` Hans de Goede
2019-03-05 19:19             ` Hans de Goede
2019-03-05 19:31               ` Lendacky, Thomas
2019-03-05 19:40                 ` Hans de Goede
2019-03-05 19:54                   ` Borislav Petkov
2019-03-06  8:41                     ` Hans de Goede [this message]
2019-03-06 10:14                       ` Thomas Gleixner
2019-03-07 11:20                         ` Hans de Goede
2019-02-21 12:28   ` Hans de Goede
2021-01-09  5:50 Christopher William Snowhill

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=e8d1128f-ff81-3dc9-90ae-86ce5d8f69b2@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tglx@linutronix.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 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®