Skip to contentSkip to conversation

Bus hidden behind transparent bridge.

DISCUSSION Dave Jones 2 participants 2 messages Jun 6, 2007 – Jun 8, 2007

lore
Share & tools
lore

Dave Jones

author
#0 lore raw

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

Signature · 1 line
http://www.codemonkey.org.uk
#1 lore raw
Quoted 20 lines · Dave Jones

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).

Quoted 4 lines

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