View Single Post
  #2   (View Single Post)  
Old 23rd January 2013
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,977
Default

Good day, shep. I responded to your post on misc@ about this, since you mentioned my live media but did not explain which kernel it used.

To follow up to my comments there, I believe patch 1.96 to src/sys/dev/pci.c is a likely root cause for the message. You could prove this by building a test kernel without the patch. The remaining subsequent patch, 1.97, may or may not have a conflict if 1.96 is removed. I haven't checked this.

Patch 1.96 caught my eye first because of the log message for the patch:
Code:
Add resource tracking for PCI bus numbers.  This will allow us to prevent
attaching the same PCI bus twice and in the long run this will allown us
to hot plug PCI busses and support CardBus on machines where the firmware
doesn't assign a bus number to CardBus devices.

While there, print a bit more information for memory and io conflicts.
And then looking at the code, it touches the logic which produces the message.

Whether the message is correct, in that your hardware has a memory addressing conflict in how the PCI buses interconnect ... I wouldn't know.

Here's a link to the Web interface to the OpenBSD CVS repository for pci.c. From there, you can look at the patch in unified diff form ("preferred") or even in multiple colors, showing the lines of code added, edited, or removed.
Reply With Quote