2007-06-06 06:33:35

by Dave Jones

[permalink] [raw]
Subject: Bus hidden behind transparent bridge.

We've had this printk in drivers/pci/probe.c asking people
to report it if they see it to linux-kernel for a long time.

google finds hundreds of instances of this being hit.
There are a bunch in bugzilla too..

http://bugzilla.kernel.org/show_bug.cgi?id=6783
http://bugzilla.kernel.org/show_bug.cgi?id=7403
http://bugzilla.kernel.org/show_bug.cgi?id=7575
http://bugzilla.kernel.org/show_bug.cgi?id=7664
http://bugzilla.kernel.org/show_bug.cgi?id=8074
http://bugzilla.kernel.org/show_bug.cgi?id=8480

(possibly others, these are just a quick skim based on summary)

I don't recall ever seeing anything happen any time someone has
reported this. Is it worth keeping the printk there?
It only seems to cause confusion (users think its an error,
especially as we ask them to do something).

Better yet, I don't think I've seen a report of this where
the user is actually experiencing a problem.

Who is the intended recipient of these reports?

Dave

--
http://www.codemonkey.org.uk


2007-06-08 05:40:59

by Greg KH

[permalink] [raw]
Subject: Re: Bus hidden behind transparent bridge.

On Wed, Jun 06, 2007 at 02:33:11AM -0400, Dave Jones wrote:
> We've had this printk in drivers/pci/probe.c asking people
> to report it if they see it to linux-kernel for a long time.
>
> google finds hundreds of instances of this being hit.
> There are a bunch in bugzilla too..
>
> http://bugzilla.kernel.org/show_bug.cgi?id=6783
> http://bugzilla.kernel.org/show_bug.cgi?id=7403
> http://bugzilla.kernel.org/show_bug.cgi?id=7575
> http://bugzilla.kernel.org/show_bug.cgi?id=7664
> http://bugzilla.kernel.org/show_bug.cgi?id=8074
> http://bugzilla.kernel.org/show_bug.cgi?id=8480
>
> (possibly others, these are just a quick skim based on summary)
>
> I don't recall ever seeing anything happen any time someone has
> reported this. Is it worth keeping the printk there?
> It only seems to cause confusion (users think its an error,
> especially as we ask them to do something).
>
> Better yet, I don't think I've seen a report of this where
> the user is actually experiencing a problem.
>
> Who is the intended recipient of these reports?

They should all go to [email protected] as he is the one who added that line.
In fact, if he doesn't fix it up soon, I'm really tempted to just add
his email address there instead, as I'm really tired of getting these
emails and he said it would be fixed up by now...

thanks,

greg k-h