Date: Sun, 24 Aug 2008 11:55:47 -0400 From: Robert Noland <rnoland@FreeBSD.org> To: "Paul B. Mahol" <onemda@gmail.com> Cc: freebsd-x11 <freebsd-x11@freebsd.org> Subject: Re: [CFT] drm updates Message-ID: <1219593348.3430.64.camel@wombat.2hip.net> In-Reply-To: <3a142e750808240812q50c1237as8c391dc35fc98ac0@mail.gmail.com> References: <20080821120021.90B5610656E5@hub.freebsd.org> <200808211456.01947.matt@chronos.org.uk> <1219544221.3430.37.camel@wombat.2hip.net> <3a142e750808240329n55d1b95bnd701dde4892c6c14@mail.gmail.com> <3a142e750808240812q50c1237as8c391dc35fc98ac0@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-IXzAnxALTp0mqK54DGiF Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2008-08-24 at 17:12 +0200, Paul B. Mahol wrote: > On 8/24/08, Paul B. Mahol <onemda@gmail.com> wrote: > > On 8/24/08, Robert Noland <rnoland@freebsd.org> wrote: > >> I've uploaded a final patch set to: > >> > >> http://people.freebsd.org/~rnoland > >> > >> I have committed this version to -CURRENT, but patches are available f= or > >> RELENG_7 as well. > >> > >> This version mostly just fixes a long standing memory leak. > >> > >> All of the reports for radeon have been good. I'm still seeing a few > >> odd things with Intel though. The most severe issue is on my 965gm. > >> After restarting X, it will hang in a way that I have never seen > >> before... The small amount of evidence that I have been able to colle= ct > >> suggests that this may be due to mesa trashing the hardware. I've spe= nt > >> a couple of days trying to figure out exactly what could be wrong. Th= is > >> morning I rebuilt my kernel with a stock drm from src and I got exactl= y > >> the same hang. Since this update does help lots of people and doesn't > >> seem to make things worse than they were to begin with, I went ahead a= nd > >> committed it. > >> > >> I was incorrect about the patch to libdrm... It isn't needed in 2.3.1 > >> and it is already committed upstream. I'll commit that update to port= s > >> soon also. It, along with a recent xf86-video-* are needed to enable > >> the new vblank behavior, which will disable vblank interrupts if there > >> are no active consumers. > >> > >> robert. > >> > > > > Do I need to update some ports? because with kernel from HEAD I have > > encountered problems when drm is loaded (agp + drm + i915) > > astro/stellarium caused deadlock, only mouse pointer could move, if I d= id > > not > > started it, system will panic anyway after some time. I did not yet tes= ted > > vty switching,.... > > > > related hardware: > > > > hostb0@pci0:0:0:0: class=3D0x060000 card=3D0x30a2103c chip=3D0x27a= 08086 > > rev=3D0x03 > > hdr=3D0x00 > > vendor =3D 'Intel Corporation' > > device =3D '955XM/945GM/PM/GMS/940GML Express Processor to DRAM > > Controller' > > class =3D bridge > > subclass =3D HOST-PCI > > vgapci0@pci0:0:2:0: class=3D0x030000 card=3D0x30a2103c chip=3D0x27a= 28086 > > rev=3D0x03 hdr=3D0x00 > > vendor =3D 'Intel Corporation' > > device =3D 'Mobile 945GM/GU Express Integrated Graphics Control= ler' > > class =3D display > > subclass =3D VGA > > vgapci1@pci0:0:2:1: class=3D0x038000 card=3D0x30a2103c chip=3D0x27a= 68086 > > rev=3D0x03 hdr=3D0x00 > > vendor =3D 'Intel Corporation' > > device =3D 'Mobile 945GM/GU Express Integrated Graphics Control= ler' > > class =3D display > > > > also if Xorg is never started, trying to unload agp.ko > > (after unloading i915.ko and drm.ko) module will cause panic. > > >=20 > Comparing to xf86-video-i815, xf86-video-intel is more stable (it doesnt = panic, crash, hardlocks, ...), but still locks display when starting astro/= stellarium. Oh, yes you should be using xf86-video-intel. robert. --=-IXzAnxALTp0mqK54DGiF Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEABECAAYFAkixhIMACgkQM4TrQ4qfROOKwwCfT2JlVmqKcJZSnMQwQ2WggJQJ 0ugAnivPBmK/jMo3NpHdCIOrl74fauEz =fIdX -----END PGP SIGNATURE----- --=-IXzAnxALTp0mqK54DGiF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1219593348.3430.64.camel>