public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux-ACPI <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Lance Ortiz <lance.ortiz@hp.com>, Tony Luck <tony.luck@intel.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: WARNING at drivers/pci/search.c:214 for 3.9
Date: Tue, 7 May 2013 22:49:58 +0200	[thread overview]
Message-ID: <20130507204958.GF7633@pd.tnic> (raw)
In-Reply-To: <20130507153349.4d03040a@pluto.restena.lu>

On Tue, May 07, 2013 at 03:33:49PM +0200, Bruno Prémont wrote:
> With the BIOS updated, the error message is gone (both the Hardware
> error, and the WARNINGs triggered by attempting to lookup the source
> PCIe device) Not sure which of the two public updates did the fix...

Yeah, who knows. At least it got fixed.

> > I don't understand: are you saying this patch breaks detection of your
> > keyboard and touchpad and if you revert it, it works again? But 3.9 works?
> 
> No, that was the commit message of the SUSE guy who performed
> the revert for SUSE kernel!

Oh ok, I see. SP2 was probably missing some other commits from upstream.
Ok, good, so it was a BIOS issue and it got fixed by a BIOS update.
Seldom do I see bugs resolved that way :-).

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

      reply	other threads:[~2013-05-07 20:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 14:21 WARNING at drivers/pci/search.c:214 for 3.9 Bruno Prémont
2013-05-06 15:07 ` Borislav Petkov
2013-05-06 21:20   ` Ortiz, Lance E
2013-05-06 21:49     ` Borislav Petkov
2013-05-06 22:40       ` Ortiz, Lance E
2013-05-08 17:22       ` Ortiz, Lance E
2013-05-07  6:52   ` Bruno Prémont
2013-05-07 10:38     ` Borislav Petkov
2013-05-07 13:33       ` Bruno Prémont
2013-05-07 20:49         ` Borislav Petkov [this message]

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=20130507204958.GF7633@pd.tnic \
    --to=bp@alien8.de \
    --cc=bonbons@linux-vserver.org \
    --cc=lance.ortiz@hp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    --cc=tony.luck@intel.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