libGL error: failed to open drm device: Permission denied

2017-08-25 Thread Gabriel Guzman
Hello misc@,

I noticed the following error while running chrome from the shell this
evening: 

libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: i965

Which I think means that I'm not getting accelerated X.

A search of misc archives led me to this:
https://marc.info/?l=openbsd-misc=146159057503035=2 which in turn
led to: https://marc.info/?l=openbsd-misc=145125527304834=2 

Based on the information in those threads, I checked to see what TTY I
was logged in on: 

gabe@xps:~$ env
_=/usr/bin/env
LOGNAME=gabe
WINDOWPATH=ttyC4
WINDOWID=20971533
XTERM_SHELL=/bin/ksh
HOME=/home/gabe
LC_CTYPE=en_US.UTF-8
XTERM_VERSION=XTerm/OpenBSD(330)
DISPLAY=:0
SSH_AGENT_PID=92062
GOPATH=/home/gabe
PATH=/home/gabe/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/games
SSH_AUTH_SOCK=/tmp/ssh-xfkLowrabhm9/agent.77539
PS1=\[\u@\]\[\h\]:\[\w\]\$ 
TERM=screen-256color
SHELL=/bin/ksh
USER=gabe
XTERM_LOCALE=en_US.UTF-8

Seemingly WINDOWPATH=ttyC4 (but I don't really know the right way to
check this) - so I added an entry to my /etc/fbtab: 

/dev/ttyC4  0600 
/dev/console:/dev/wskbd:/dev/wskbd0:/dev/wsmouse:/dev/wsmouse0:/dev/ttyCcfg:/dev/drm0

duplicating what I saw for ttyC0.

I rebotted and confirmed that I was indeed now the owner of /dev/drm0:

gabe@xps:~$ ls -l /dev/drm*
crw---  1 gabe  wheel   87,   0 Aug 25 21:18 /dev/drm0
crw---  1 root  wheel   87,   1 Aug 25 21:18 /dev/drm1
crw---  1 root  wheel   87,   2 Aug 25 21:18 /dev/drm2
crw---  1 root  wheel   87,   3 Aug 25 21:18 /dev/drm3

Then I ran glxgears, and got the permission denied message again: 

gabe@xps:~$ glxgears  
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: i965

And, sure enough when I rechecked /dev/drm: 

gabe@xps:~$ ls -l /dev/drm* 
crw---  1 root  wheel   87,   0 Aug 25 21:18 /dev/drm0
crw---  1 root  wheel   87,   1 Aug 25 21:18 /dev/drm1
crw---  1 root  wheel   87,   2 Aug 25 21:18 /dev/drm2
crw---  1 root  wheel   87,   3 Aug 25 21:18 /dev/drm3

I'm no longer the owner.  I'm not sure when this started, but
I don't have this issue on my 6.1 box, just on the one running current. 

Sometimes, forcing the permissions on /dev/drm0 does work:

gabe@xps:~$ doas chown gabe /dev/drm0 
doas (g...@xps.my.domain) password: 
gabe@xps:~$ glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.

But then, as soon as I exit glxgears, /dev/drm0 goes right back to being
owned by root, and the error message comes back.  

Xorg log, and dmesg below... there are some drm0 errors in the dmesg
that maybe are related?  If anyone has any ideas, I'm open to trying
them out.  If not, I'l probably do a clean install on this machine as it
has been awhile since the last one.  

Also, not sure if it's relevant, but I'm a member of the `staff` login
class on this machine

Thanks,
gabe. 

gabe@xps:~$ cat /var/log/Xorg.0.log
[20.707] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
(Operation not permitted)
Check that you have set 'machdep.allowaperture=1'
in /etc/sysctl.conf and reboot your machine
refer to xf86(4) for details
[20.707]linear framebuffer access unavailable
[20.716] (--) Using wscons driver on /dev/ttyC4
[20.730] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[20.730] X Protocol Version 11, Revision 0
[20.730] Build Operating System: OpenBSD 6.2 amd64 
[20.730] Current Operating System: OpenBSD xps.my.domain 6.2 GENERIC.MP#40 
amd64
[20.730] Build Date: 25 August 2017  11:23:34AM
[20.730]  
[20.730] Current version of pixman: 0.34.0
[20.730]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[20.730] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[20.731] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug 25 22:22:37 
2017
[20.732] (==) Using system config directory 
"/usr/X11R6/share/X11/xorg.conf.d"
[20.733] (==) No Layout section.  Using the first Screen section.
[20.733] (==) No screen section available. Using defaults.
[20.733] (**) |-->Screen "Default Screen Section" (0)
[20.733] (**) |   |-->Monitor ""
[20.734] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[20.734] (==) Disabling SIGIO handlers for input devices
[20.734] (==) Automatically adding devices
[20.734] (==) Automatically enabling devices
[20.734] (==) Not automatically adding GPU devices
[20.734] (==) Max clients allowed: 256, resource mask: 0x1f
[20.740] (==) FontPath set to:
/usr/X11

Re: libGL error: failed to open drm device: Permission denied

2017-03-20 Thread Alessandro DE LAURENZIS
Hello Mihai,

On Tue, 21 Mar 2017 00:07:16 +0200
Mihai Popescu  wrote:

> What version of OpenBSD are you running?

-current, updated to 03/19 snapshot:

[just22@poseidon]-[0]-[✓]-[~]> dmesg | head -2
OpenBSD 6.1-beta (GENERIC.MP) #38: Sun Mar 19 11:09:01 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

> Did you modified /etc/fbtab?

Never touched:

[just22@poseidon]-[0]-[✓]-[~]> cat /etc/fbtab
#  $OpenBSD: fbtab.head,v 1.2 1999/05/05 06:56:34 deraadt Exp $
# login(1) reads this file to determine which devices should be chown'd to
# the new user. Format is:
# login-tty permdevice:[device]:...
/dev/ttyC0  0600
/dev/console:/dev/wskbd:/dev/wskbd0:/dev/wsmouse:/dev/wsmouse0:/dev/ttyCcfg:/
dev/drm0
# samples
#/dev/ttyC0 0600/dev/fd0

> What is 'll' or that command used to show permissions?

Just an alias to 'ls -lh', anyhow:

[just22@poseidon]-[0]-[✓]-[~]> ls -l /dev/drm0
crw---  1 just22  wheel   87,   0 Mar 20 08:17 /dev/drm0

(this is the "normal" condition, of course)

> Is just22 a custom user, i.e. not created at install time?

It was created (a long time ago!) at install time.

> Looking at what I have, I think for a normal install it should show
> you this:
>
> [just22@poseidon]-[~]> ll /dev/drm0
> crw---  1 just22  just22   87,   0 Mar 20 08:17 /dev/drm0

I noticed that the ownership of the device is "just22,just22" when I log in
from ttyC0, reset to "root,wheel" when I logout from there, set to
"just22,wheel" when logging in through xenodm. Does this make sense?

Thanks for your feedback

--
Alessandro DE LAURENZIS
[mailto:jus...@atlantide.t28.net]
LinkedIn: http://it.linkedin.com/in/delaurenzis



Re: libGL error: failed to open drm device: Permission denied

2017-03-20 Thread Mihai Popescu
> in the hope that someone clarify the situation.

What version of OpenBSD are you running?

Did you modified /etc/fbtab?

What is 'll' or that command used to show permissions?

Is just22 a custom user, i.e. not created at install time?


Looking at what I have, I think for a normal install it should show you this:

[just22@poseidon]-[~]> ll /dev/drm0
crw---  1 just22  just22   87,   0 Mar 20 08:17 /dev/drm0
   



libGL error: failed to open drm device: Permission denied

2017-03-20 Thread Alessandro DE LAURENZIS
Dear misc@ readers,

I'd like to make a follow-up of an old thread [0], in the hope that someone
clarify the situation.

I normally log in X through xdm (xenodm from some weeks now) and, once there,
the ownership of /dev/drm0 is changed to my user, as expected:

[just22@poseidon]-[~]> ll /dev/drm0
crw---  1 just22  wheel   87,   0 Mar 20 08:17 /dev/drm0

But, if I switch from X to ttyC0 (Ctrl-Alt-F1), log in there and then log out,
the ownership is reset:

[just22@poseidon]-[~]> ll /dev/drm0
crw---  1 root  wheel   87,   0 Mar 20 08:17 /dev/drm0

(this behavior seems consistent with the content of /etc/fbtab, meaning
that if I do the same sequence of operations from a different virtual
terminal, ttyC1 for example, /dev/drm0 ownership is left untouched).

Of cource, when I switch back in X, I'm no more able to get access to drm
device, losing hardware acceleration for applications using it and continuosly
receiving the following error message:

libGL error: failed to open drm device: Permission denied

The only way to restore the correct condition is to logout/login (or restart
xenodm service).

I temporarely worked around the problem inhibiting the login from ttyC0 (and
so reserving it as a kind of "virtual console" for kernel messages), but I'd
like to hear your thoughts on this: is it the expected/desired behavior
or should it be fixed?

All the best

[0]: http://marc.info/?l=openbsd-misc=145125527304834=2

-- 
Alessandro DE LAURENZIS
[mailto:jus...@atlantide.t28.net]
LinkedIn: http://it.linkedin.com/in/delaurenzis



Re: libGL error: failed to open drm device: Permission denied

2015-12-28 Thread Mihai Popescu
Well, things were sorted out.

Looking at that /etc/fbtab file Jonathan Gray pointed out (and yes,
this is not a typo of /etc/fstab like I thought before) I can spot the
/dev/drm0 in that long list of devices prepared for chown at login.

But, that file is filled in for ttyC0 only, the tty that most users
are using it for login. But, giving the fact that I got some annoying
kernel messages from my connecting/disconnecting USB mouse with
aggresive power management routines, I was using ttyC1 for login. From
that things got another way. I think this clarifies the other issue of
changing tty / ownership change mentioned in this thread by somebody
else.

So the error was not really an error, going back to ttyC0 login I got
the right permission and the messages are no more. Of course I can
edit the /etc/fbtab, too.

One question please: is it right that not getting access to /dev/drm0
is like losing hardware acceleration for applications using it?

Thanks.



Re: libGL error: failed to open drm device: Permission denied

2015-12-28 Thread lists
Mon, 28 Dec 2015 00:25:25 +0200 Mihai Popescu <mih...@gmail.com>
> libGL error: failed to open drm device: Permission denied
> libGL error: failed to load driver: r600
> 
> Is it normal, can it be fixed on my side?

Quick and dirty hack around this (if your user is in group wheel):

$ grep chmod .xinitrc
sudo chmod g+rw /dev/drm0

$ ls -l /dev/drm*

Any other suggestions, and moreover proper way to address this?



Re: libGL error: failed to open drm device: Permission denied

2015-12-28 Thread Mihai Popescu
> Can you include the output of ls -l /dev/drm0 and
> the contents of /var/log/Xorg.0.log ?

$ ls -l /dev/drm0
crw---  1 root  wheel   87,   0 Dec 11 20:39 /dev/drm0

$ more /var/log/Xorg.0.log
[46.215] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
(Operation not permitted)
Check that you have set 'machdep.allowaperture=1'
in /etc/sysctl.conf and reboot your machine
refer to xf86(4) for details
[46.215]linear framebuffer access unavailable
[46.221] (--) Using wscons driver on /dev/ttyC4 in pcvt
compatibility mode (version 3.32)
[47.345]
X.Org X Server 1.17.4
Release Date: 2015-10-28
[47.345] X Protocol Version 11, Revision 0
[47.345] Build Operating System: OpenBSD 5.8 amd64
[47.345] Current Operating System: OpenBSD thinkc.my.domain 5.8
GENERIC.MP#1739 amd64
[47.346] Build Date: 11 December 2015  07:02:02AM
[47.346]
[47.346] Current version of pixman: 0.32.8
[47.346]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[47.346] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[47.346] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 28
17:22:45 2015
[47.376] (==) Using system config directory
"/usr/X11R6/share/X11/xorg.conf.d"
[47.383] (==) No Layout section.  Using the first Screen section.
[47.383] (==) No screen section available. Using defaults.
[47.383] (**) |-->Screen "Default Screen Section" (0)
[47.383] (**) |   |-->Monitor ""
[47.384] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[47.384] (==) Disabling SIGIO handlers for input devices
[47.384] (==) Automatically adding devices
[47.384] (==) Automatically enabling devices
[47.384] (==) Not automatically adding GPU devices
[47.488] (==) FontPath set to:
/usr/X11R6/lib/X11/fonts/misc/,
/usr/X11R6/lib/X11/fonts/TTF/,
/usr/X11R6/lib/X11/fonts/OTF/,
/usr/X11R6/lib/X11/fonts/Type1/,
/usr/X11R6/lib/X11/fonts/100dpi/,
/usr/X11R6/lib/X11/fonts/75dpi/
[47.488] (==) ModulePath set to "/usr/X11R6/lib/modules"
[47.488] (II) The server relies on wscons to provide the list of
input devices.
If no devices become available, reconfigure wscons or disable
AutoAddDevices.
[47.488] (II) Loader magic: 0x10a6b3131ce0
[47.488] (II) Module ABI versions:
[47.488]X.Org ANSI C Emulation: 0.4
[47.488]X.Org Video Driver: 19.0
[47.488]X.Org XInput driver : 21.0
[47.488]X.Org Server Extension : 9.0
[47.489] (--) PCI:*(0:1:5:0) 1002:9715:17aa:3082 rev 0, Mem @
0xd000/268435456, 0xfe90/65536, 0xfe80/1048576, I/O @
0xe000/256
[47.489] (II) LoadModule: "glx"
[47.503] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[47.581] (II) Module glx: vendor="X.Org Foundation"
[47.581]compiled for 1.17.4, module version = 1.0.0
[47.581]ABI class: X.Org Server Extension, version 9.0
[47.581] (==) AIGLX enabled
[47.582] (==) Matched ati as autoconfigured driver 0
[47.582] (==) Matched vesa as autoconfigured driver 1
[47.582] (==) Assigned the driver to the xf86ConfigLayout
[47.582] (II) LoadModule: "ati"
[47.582] (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.so
[47.607] (II) Module ati: vendor="X.Org Foundation"
[47.607]compiled for 1.17.4, module version = 7.5.0
[47.607]Module class: X.Org Video Driver
[47.607]ABI class: X.Org Video Driver, version 19.0
[47.607] (II) LoadModule: "radeon"
[47.608] (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.so
[47.626] (II) Module radeon: vendor="X.Org Foundation"
[47.626]compiled for 1.17.4, module version = 7.5.0
[47.626]Module class: X.Org Video Driver
[47.626]ABI class: X.Org Video Driver, version 19.0
[47.627] (II) LoadModule: "vesa"
[47.627] (II) Loading /usr/X11R6/lib/modules/drivers/vesa_drv.so
[47.636] (II) Module vesa: vendor="X.Org Foundation"
[47.636]compiled for 1.17.4, module version = 2.3.3
[47.636]Module class: X.Org Video Driver
[47.636]ABI class: X.Org Video Driver, version 19.0
[47.636] (II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
ATI Radeon Mobility X300 (M24) 3152 (PCIE),
ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
ATI Radeon X600 (RV380) 3E50 (PCIE),
ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
 

Re: libGL error: failed to open drm device: Permission denied

2015-12-28 Thread lists
Mon, 28 Dec 2015 19:50:42 +0200 Mihai Popescu 
> But, that file is filled in for ttyC0 only, the tty that most users
> are using it for login. But, giving the fact that I got some annoying
> kernel messages from my connecting/disconnecting USB mouse with
> aggresive power management routines, I was using ttyC1 for login.

Similar here, not using anywhere ttyC0, rather tty00 and ttyC1 to
ttyC5.  Confirmed the /etc/fbtab lines for these ttys worked as
expected in these cases.

> So the error was not really an error, going back to ttyC0 login I got
> the right permission and the messages are no more. Of course I can
> edit the /etc/fbtab, too.

Interesting if you ssh log in to startx, e.g. ttyp0, does this work
in /etc/fbtab and is it expected to in this case?

> One question please: is it right that not getting access to /dev/drm0
> is like losing hardware acceleration for applications using it?

Yes, on a drm(4) supported device.  You could confirm this with the
demo glxgears(1).



Re: libGL error: failed to open drm device: Permission denied

2015-12-27 Thread Jonathan Gray
On Mon, Dec 28, 2015 at 12:25:25AM +0200, Mihai Popescu wrote:
> Hello,
> 
> I am running cwm and I had some problems starting chrome from the menu
> - it starts for the very first time when i click on the menu, then i
> have to click 2 or 3 times on menu entry to start chrome again. This
> is not a big deal, maybe a cwm glitch.
> 
> I went to start chrome from xterm, and I got these errors:
> 
> $ chrome
> libGL error: failed to open drm device: Permission denied
> libGL error: failed to load driver: r600
> libGL error: failed to open drm device: Permission denied
> libGL error: failed to load driver: r600
> 
> Is it normal, can it be fixed on my side?

The ownership of /dev/drm0 should be changed according to
/etc/fbtab to your user after logging in.

Can you include the output of ls -l /dev/drm0 and
the contents of /var/log/Xorg.0.log ?

How are you starting X, xdm/startx/?



Re: libGL error: failed to open drm device: Permission denied

2015-12-27 Thread patrick keshishian
On 12/27/15, Jonathan Gray <j...@jsg.id.au> wrote:
> On Mon, Dec 28, 2015 at 12:25:25AM +0200, Mihai Popescu wrote:
>> Hello,
>>
>> I am running cwm and I had some problems starting chrome from the menu
>> - it starts for the very first time when i click on the menu, then i
>> have to click 2 or 3 times on menu entry to start chrome again. This
>> is not a big deal, maybe a cwm glitch.
>>
>> I went to start chrome from xterm, and I got these errors:
>>
>> $ chrome
>> libGL error: failed to open drm device: Permission denied
>> libGL error: failed to load driver: r600
>> libGL error: failed to open drm device: Permission denied
>> libGL error: failed to load driver: r600
>>
>> Is it normal, can it be fixed on my side?
>
> The ownership of /dev/drm0 should be changed according to
> /etc/fbtab to your user after logging in.

I have noticed (in the past), switching from X to virtual term
(Ctrl+Shift+Fx) will override/revert the ownership of /dev/drm0,
resulting in above (or similar) errors when I switch back to X
and run something like xlock.

I say "in the past", as I have avoided above switching since.

Hope this sheds some light onto the problem (or possibly
as-designed behavior).

--patrick


> Can you include the output of ls -l /dev/drm0 and
> the contents of /var/log/Xorg.0.log ?
>
> How are you starting X, xdm/startx/?



libGL error: failed to open drm device: Permission denied

2015-12-27 Thread Mihai Popescu
Hello,

I am running cwm and I had some problems starting chrome from the menu
- it starts for the very first time when i click on the menu, then i
have to click 2 or 3 times on menu entry to start chrome again. This
is not a big deal, maybe a cwm glitch.

I went to start chrome from xterm, and I got these errors:

$ chrome
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: r600
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: r600

Is it normal, can it be fixed on my side?

OpenBSD 5.8-current (GENERIC.MP) #1739: Fri Dec 11 06:16:43 MST 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8029429760 (7657MB)
avail mem = 7781957632 (7421MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xeebc0 (57 entries)
bios0: vendor LENOVO version "9VKT33AUS" date 09/11/2013
bios0: LENOVO 1990RZ2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC TCPA MCFG SLIC MCFG HPET SSDT
acpi0: wakeup devices PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4)
PCE7(S4) PCE9(S4) PCEA(S4) PCEB(S4) PCEC(S4) SBAZ(S4) PS2K(S3)
PS2M(S3) P0PC(S4) PE20(S4) PE21(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Athlon(tm) II X2 B26 Processor, 3194.57 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,NODEID,ITSC
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB
64b/line 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative
cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative
cpu0: AMD erratum 721 detected and fixed
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Athlon(tm) II X2 B26 Processor, 3192.02 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,NODEID,ITSC
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB
64b/line 16-way L2 cache
cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative
cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative
cpu1: AMD erratum 721 detected and fixed
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 3 pa 0xfec0, version 21, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpimcfg1 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318180 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (P0P1)
acpiprt2 at acpi0: bus -1 (PCE2)
acpiprt3 at acpi0: bus -1 (PCE3)
acpiprt4 at acpi0: bus -1 (PCE4)
acpiprt5 at acpi0: bus -1 (PCE5)
acpiprt6 at acpi0: bus -1 (PCE6)
acpiprt7 at acpi0: bus -1 (PCE7)
acpiprt8 at acpi0: bus -1 (PCE9)
acpiprt9 at acpi0: bus -1 (PCEA)
acpiprt10 at acpi0: bus 2 (P0PC)
acpiprt11 at acpi0: bus 3 (PE20)
acpiprt12 at acpi0: bus -1 (PE21)
acpiprt13 at acpi0: bus -1 (PE22)
acpiprt14 at acpi0: bus 4 (PE23)
acpicpu0 at acpi0: C1(@1 halt!), PSS
acpicpu1 at acpi0: C1(@1 halt!), PSS
acpibtn0 at acpi0: PWRB
cpu0: 3194 MHz: speeds: 3200 2500 1900 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "AMD RS880 Host" rev 0x00
ppb0 at pci0 dev 1 function 0 unknown vendor 0x17aa product 0x9602 rev 0x00
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 5 function 0 "ATI Radeon HD 4250" rev 0x00
drm0 at radeondrm0
radeondrm0: apic 3 int 18
ahci0 at pci0 dev 17 function 0 "ATI SBx00 SATA" rev 0x00: apic 3 int
19, AHCI 1.2
ahci0: port 0: 3.0Gb/s
ahci0: port 1: 1.5Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: <ATA, WDC WD3200AAKS-0, 40.0> SCSI3
0/direct fixed naa.50014ee1018094dc
sd0: 305245MB, 512 bytes/sector, 625142448 sectors
cd0 at scsibus1 targ 1 lun 0: <PLDS, DVD-RW DH16ABSH, YL32> ATAPI
5/cdrom removable
ohci0 at pci0 dev 18 function 0 "ATI SB700 USB" rev 0x00: apic 3 int
18, version 1.0, legacy support
ehci0 at pci0 dev 18 function 2 "ATI SB700 USB2" rev 0x00: apic 3 int 17
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "ATI EHCI root hub" rev 2.00/1.00 addr 1
ohci1 at pci0 dev 19 function 0 "ATI SB700 USB" rev 0x00: apic 3 int
18, version 1.0, legacy support
ehci1 at pci0 dev 19 function 2 "ATI SB700 USB2" rev 0x00: apic 3 int 17
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 "ATI EHCI root hub" rev 2.00/1.00 addr 1
piixpm0 at pci0 dev 20 fu