DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD General

OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below.

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #1   (View Single Post)  
Old 22nd January 2013
shep shep is offline
ISO Quartermaster
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 546
Thanked 9 Times in 9 Posts
Default mem address conflict in amd64 current

In
Code:
OpenBSD 5.2-current (GENERIC.MP) #17: Fri Jan 18 17:50:43 MST 2013
    todd@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
and the prior version I am getting warning in
dmesg:
Code:
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
pchb0 at pci0 dev 0 function 0 "ATI RX780 Host" rev 0x00
I do not see this in my other Intel Atom motherboard running amd64 current.
Is any one else getting this? Does it represent failing memory?

My pcidump -v | grep 0x200:
Code:
0x001c: BAR mem 64bit addr: 0x00000000e0000000/0x20000000
and pcidump -v | grep 0x001c
Code:
	0x001c: BAR mem 64bit addr: 0x00000000e0000000/0x20000000
	0x001c: I/O Base: d1 I/O Limit: d1 Secondary Status: 2000
	0x001c: I/O Base: e1 I/O Limit: e1 Secondary Status: 0000
	0x001c: BAR io addr: 0x0000fc00/0x0004
	0x001c: BAR empty (00000000)
	0x001c: BAR empty (00000000)
	0x001c: BAR empty (00000000)
	0x001c: BAR empty (00000000)
	0x001c: BAR empty (00000000)
	0x001c: BAR empty (00000000)
	0x001c: BAR empty (00000000)
	0x001c: BAR io addr: 0x00000000/0x0004
	0x001c: BAR empty (00000000)
	0x001c: BAR empty (00000000)
	0x001c: I/O Base: c0 I/O Limit: c0 Secondary Status: 2280
	0x001c: BAR empty (00000000)
	0x001c: BAR empty (00000000)
	0x001c: BAR empty (00000000)
	0x001c: BAR empty (00000000)
	0x001c: BAR empty (00000000)
It seems to be running fine but this is new in the dmesg.

Added: Just to be sure that I was not having a hardware issue , I booted Jggimi's live fluxbox amd64 cd and the memory conflict did not show up in the 5.0 dmesg

Last edited by shep; 23rd January 2013 at 03:00 AM. Reason: added live cd
Reply With Quote
 

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Can't find packages for amd64 -current Daffy OpenBSD Packages and Ports 6 8th June 2011 02:44 PM
Does pf conflict with OpenVPN? Emile OpenBSD Packages and Ports 37 2nd February 2011 11:03 PM
Status of Current amd64 shep OpenBSD General 3 24th August 2010 02:14 PM
Current Missing some amd64 Packages shep OpenBSD Packages and Ports 3 5th March 2010 03:50 PM
FreeBSD 8.0-CURRENT (amd64 & i386) VMware Virtual Appliances Available glarkin_at_FreeBSD FreeBSD Installation and Upgrading 1 3rd December 2008 08:49 AM


All times are GMT. The time now is 01:08 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick