Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Sep 2010 09:19:22 -0700
From:      Mark Atkinson <atkin901@gmail.com>
To:        freebsd-stable@freebsd.org
Subject:   Re: Freebsd 8.1 + xorg + radeonhd hang
Message-ID:  <i6qrma$lau$1@dough.gmane.org>
In-Reply-To: <AANLkTinR0OPp_t1iFkmbgZe0vSM_F_vYcNPS28mfFDHZ@mail.gmail.com>
References:  <201009132016.o8DKGmw5053180@lurza.secnetix.de>	<20100913234355.I96626@rumrunner.mine.nu>	<alpine.BSF.2.00.1009141512120.54615@wonkity.com>	<20100914231728.D5192@rumrunner.mine.nu>	<alpine.BSF.2.00.1009141545420.54725@wonkity.com> <AANLkTinR0OPp_t1iFkmbgZe0vSM_F_vYcNPS28mfFDHZ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/14/2010 15:39, Oliver Pinter wrote:
> Hi all!
> 
> it's an old problem:
> http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009372.html
> 
> And still exist... with or without dri/3d, it's a bug between freebsd
> agp and xorg-server.
> 
> When you use vesa, than this problem is elliminated. With radeon or
> radeon-hd driver, the problem come back, and the machine locked up.
> When you killed the xserver, end kldunloaded the radeon modul, then
> presented a small memory leak, and the radeon kernek modul is not
> reloadable.
> The DRI/DRM/3D is completly independent from this bug. The bug is in
> libpciaccess or xorg-server. The old xserver (<=1.4.X) is bugfree....

Yep this issue has been around since the Xorg upgrade -- note that
changes were made to drm and radeon kernel modules around the same time.
  I used to be able to drop in and out of X before then as well.  Now if
I exit X, I have to reboot.   This is an r600 card and radeon or
radeonhd both behave the same.

I reported it here:

http://article.gmane.org/gmane.os.freebsd.devel.x11/9508

the report was largely ignored.

> On 9/15/10, Warren Block <wblock@wonkity.com> wrote:
>> On Tue, 14 Sep 2010, Eivind E wrote:
>>>
>>
>> First, the intermittent nature of the problem sounds like it might be
>> hardware failure.  The only easy way to test that would be to swap in
>> another video board, but people rarely have extras.
>>
>> You also mentioned upgrading from 7.x to 8.1.  It's worth running
>> pkg_libchk from sysutils/bsdadminscripts to make sure nothing was
>> missed.
>>
>> Back to the xorg.conf...
>>
>> Adding Option "Log" "Sync" to ServerLayout may help preserve the
>> Xorg.0.log file.  Untested by me so far, but shouldn't hurt.
>>
>>> I'll repost the xorg.conf here
>>>
>>> Section "ServerLayout"
>>> 	Identifier     "Layout0"
>>> 	Screen      0  "Screen0" 0 0
>>> 	InputDevice    "Tastatur" "CoreKeyboard"
>>> 	InputDevice    "Mus" "CorePointer"
>>> 	Option	"AllowEmptyInput" "off"
>>> EndSection
>>
>> AllowEmptyInput (and fire) bad!  Use AutoAddDevices Off instead.
>> (http://www.wonkity.com/~wblock/docs/html/aei.html)
>>
>>> Section "Files"
>>> EndSection
>>
>> Looks wrong, but works here.  I'd suggest leaving out the section
>> entirely rather than leaving it empty, though.
>>
>>> Section "Module"
>>> 	# Load "freetype"
>>> 	# Load "xtt"
>>> 	Load  "extmod"
>>> 	Load  "glx"
>>> 	Load  "dri"
>>> 	Load  "dbe"
>>> 	Load  "record"
>>> 	Load  "xtrap"
>>> 	Load  "type1"
>>> 	Load  "speedo"
>>> EndSection
>>
>> All but the commented first two and last three are default.  Worth
>> commenting out the last three and testing, too.
>>
>>> Section "Monitor"
>>> 	Identifier   "Skjerm"
>>> 	HorizSync    31.5 - 48.5
>>> 	VertRefresh  50.0 - 70.0
>>> EndSection
>>>
>>> Section "Device"
>>> 	Identifier  "Grafikkort"
>>> 	Driver      "radeonhd"
>>> 	Option	"HPD" "off"
>>> EndSection
>>
>> My success rate with the radeonhd driver is pretty much nonexistent.
>>
>>> Section "Screen"
>>> 	Identifier "Screen0"
>>> 	Device     "Grafikkort"
>>> 	Monitor    "Skjerm"
>>> 	DefaultDepth     16
>>> 	SubSection "Display"
>>> 		Depth     16
>>> 		Modes    "1280x1024" "1280x960" "1152x864" "1024x768" "800x600"
>>> "640x480"
>>> 	EndSubSection
>>> EndSection
>>
>> 16-bit?  That may actually be slower than 24, depending on how the card
>> is built.  Should still work, though it's worth commenting out in both
>> places for testing.
>>
>>> Section "DRI"
>>> 	Mode 0666
>>> EndSection
>>
>> Should not cause a problem, although I use 0660.
>>
>> My full xorg.conf for the X1650 is here:
>> http://wonkity.com/~wblock/radeon/x1650/xorg.conf
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyQ8goACgkQrDN5kXnx8yZD5QCgiQE9YLU2Vy/jCC56e7s28kkS
74IAn2oi3jHXfXDgblwpLM982wWAqyyD
=kuqx
-----END PGP SIGNATURE-----




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?i6qrma$lau$1>