J. Scott Heppler <shepper <at> earthlink.net> writes: > > My dmesg show a new mem address conflict error that has persisted > through 3 upgrades. I am currently at > > 5.2 GENERIC.MP#20 amd64 > > The message shows up in the standard dmesg > acpicpu0 at acpi0: PSS > acpicpu1 at acpi0: PSS > acpitz0 at acpi0: critical temperature is 65 degC > acpibtn0 at acpi0: PWRB > cpu0: PowerNow! K8 2500 MHz: speeds: 2500 2400 2200 2000 1800 1000 MHz > pci0 at mainbus0 bus 0 > 0:0:0: mem address conflict 0xe0000000/0x20000000 >... The message is produced by src/sys/dev/pci/pci.c -- it is not amd64 specific.
>... I booted a Jggimi amd64 live cd and did not get the error message.... That doesn't tell the mailing list very much. As that's *my* live media build, I can at least let them know that this means a 5.0-release GENERIC.MP kernel. (I'm a bit behind on live media updates.) I note that pci.c has had 4 patches since 5.0-release, the last in October. As you're running -current, you have them all. It's possible that patch 1.96 is the reason you see the messages, since that patch did touch that section of pci.c. You might consider building a kernel from source without that patch. You'll need to review FAQ 5 and the man page for cvs(1). Just as an FYI: A full dmesg is always recommended when posting to misc@. Fragments are not always helpful.
