linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Michael Bakos <bakhos@msi.umn.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "Badness in pci_find_subsys"
Date: Thu, 31 Jul 2003 09:36:39 -0700	[thread overview]
Message-ID: <20030731163639.GA3555@kroah.com> (raw)
In-Reply-To: <Pine.SGI.4.33.0307311059540.17528-300000@ir12.msi.umn.edu>

On Thu, Jul 31, 2003 at 11:05:13AM -0500, Michael Bakos wrote:
> Kernel version: 2.6.0-test1
> CPU type: x86-64 (Opteron)
> PCI information attached.
> 
> I get: Badness in pci_find_subsys at drivers/pci/search.c:132 comming from
> 2 different things(one seems to be from the tg3 ethernet driver and the
> other from the ide driver), I also attached the exact call trace (before
> the pci information).

Known issue, it's fixed in the x86_64 tree and hopefully will make it to
Linus's tree sometime soon.

thanks,

greg k-h

      reply	other threads:[~2003-07-31 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31 16:05 "Badness in pci_find_subsys" Michael Bakos
2003-07-31 16:36 ` Greg KH [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=20030731163639.GA3555@kroah.com \
    --to=greg@kroah.com \
    --cc=bakhos@msi.umn.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).