DRM/DRI in STABLE
Charles P. Schaum
verbo.solo at sbcglobal.net
Sun Oct 1 21:37:38 PDT 2006
Hi,
Just had a question about DRI/DRM using the Intel i915 module on an
845G. Using fullscreen modes that have a resolution different from the
display at startup can cause the xserver to halt and restart. This
actually happened more under 6.1 STABLE than 6.2-PRE.
After building world I can usually go for about a day or so without this
behavior appearing. Then it will occur and, after the first occurrance,
it will generally have that behavior until a subsequent rebuilding of
world.
I usually avoid this by modifying games so that they either run in a
window or use the default resolution, so there's an easy workaround. I
was just curious if I were doing something dumb or if that's just life
right now.
Charles
See below:
I had been getting messages under 6.1-STABLE like:
Sep 21 05:09:07 elbereth kernel: Warning: pid 3307 used static ldt
allocation.
Sep 21 05:09:07 elbereth kernel: See the i386_set_ldt man page for more
info
Sep 21 05:11:52 elbereth kernel: error: [drm:pid3311:drm_close] *ERROR*
can't find authenticator...
But after rebuilding world/kernel to 6.2-PRE (STABLE) these have largely
disappeared - and I still am using the same apps. About the only thing I
see currently are some errors generated when recording a CD via GNOME
(atapicam) which have no effect on my getting a good CD and therefore
which I ignore.
Today's messages were:
Oct 1 07:47:59 elbereth kernel: pid 59648 (typesconfig), uid 0: exited
on signal 11 (core dumped)
Oct 1 07:47:59 elbereth kernel: pid 59649 (typesconfig), uid 0: exited
on signal 11 (core dumped)
Oct 1 20:39:16 elbereth kernel: pid 811 (Xorg), uid 0: exited on signal
6 (core dumped)
Oct 1 20:39:22 elbereth gdm[804]: Error reinitilizing server
Oct 1 20:39:55 elbereth login: ROOT LOGIN (root) ON ttyv0
Oct 1 21:16:24 elbereth cupsd: Unable to read configuration file
'/usr/local/etc/cups/cupsd.conf' - exiting!
Oct 1 21:16:24 elbereth syslogd: /dev/:0: No such file or directory
Oct 1 21:17:40 elbereth sudo: charles : TTY=ttyp2 ;
PWD=/home/charles ; USER=root ; COMMAND=/usr/local/sbin/cupsd
Oct 1 22:48:42 elbereth kernel: pid 23581 (typesconfig), uid 0: exited
on signal 11 (core dumped)
Oct 1 22:48:42 elbereth kernel: pid 23582 (typesconfig), uid 0: exited
on signal 11 (core dumped)
The X log really did not indicate anything unusual, save that the server
crashed:
(II) 3rd Button detected: disabling emulate3Button
(II) I810(0): Setting refresh with VBE 3 method.
(II) I810(0): Display plane A is enabled and connected to Pipe A.
(II) I810(0): Enabling plane A.
(II) I810(0): Display plane A is now enabled and connected to Pipe A.
(II) I810(0): PIPEACONF is 0x80000000
(II) I810(0): Mode bandwidth is 47 Mpixel/s
(II) I810(0): maxBandwidth is 640 Mbyte/s, pipe bandwidths are 252
Mbyte/s, 0 Mbyte/s
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Fatal server error:
Caught signal 11. Server aborting
Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional
information.
(WW) I810(0): Successfully set original devices
(WW) I810(0): Setting the original video mode instead of restoring
the saved state
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(II) I810(0): BIOS call 0x5f05 not supported, setting refresh with VBE 3
method.
(II) I810(0): xf86UnbindGARTMemory: unbind key 9
(II) I810(0): xf86UnbindGARTMemory: unbind key 1
(II) I810(0): xf86UnbindGARTMemory: unbind key 2
(II) I810(0): xf86UnbindGARTMemory: unbind key 4
(II) I810(0): xf86UnbindGARTMemory: unbind key 3
(II) I810(0): xf86UnbindGARTMemory: unbind key 5
(II) I810(0): xf86UnbindGARTMemory: unbind key 6
(II) I810(0): xf86UnbindGARTMemory: unbind key 7
(II) I810(0): xf86UnbindGARTMemory: unbind key 8
(WW) I810(0): Successfully set original devices (2)
More information about the freebsd-stable
mailing list