Date: Wed, 10 Feb 2010 11:37:52 -0800 From: David Wolfskill <david@catwhisker.org> To: Robert Noland <rnoland@FreeBSD.org> Cc: x11@FreeBSD.org Subject: Re: DRI problems with ati/radeon on stable/7 r203425 Message-ID: <20100210193752.GE391@bunrab.catwhisker.org> In-Reply-To: <1265814875.8609.61.camel@balrog.2hip.net> References: <20100208172654.GA391@bunrab.catwhisker.org> <1265764746.8609.18.camel@balrog.2hip.net> <20100210023558.GV391@bunrab.catwhisker.org> <1265802517.8609.25.camel@balrog.2hip.net> <20100210130642.GA391@bunrab.catwhisker.org> <1265813805.8609.52.camel@balrog.2hip.net> <20100210150604.GC391@bunrab.catwhisker.org> <1265814875.8609.61.camel@balrog.2hip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--9A1A73/U17WN0PFw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 10, 2010 at 09:14:35AM -0600, Robert Noland wrote: > On Wed, 2010-02-10 at 07:06 -0800, David Wolfskill wrote: > > On Wed, Feb 10, 2010 at 08:56:45AM -0600, Robert Noland wrote: > > > ... > > > Right, it sounds like the other person is having interrupt issues. D= oes > > > moving the mouse / touchpad have any impact? > >=20 > > Well, trying to doesn't appear to have any effect; it doesn't move, > > regardless. > >=20 > > > Or, possibly disabling msi? (adding hw.drm.msi=3D0 to loader.conf) > > > .... > >=20 > > Well, I don't know what msi is, so I hadn't tried that. I will try it > > after the daily builds are finished -- probably 3 - 4 hours from now. >=20 > MSI is "Message Signaled Interrupt" and is enabled by default for any > card that reports that it is capable (except for intel 945, which is > borked). When drm loads it will tell you if it is using msi or not. > ... OK. I re-enabled DRI in xorg.conf & disabled hw.drm.msi; the result appeared to work, though the screen didn't always clear all of images (e.g., the "swarm" screen saver left little white bits lying around; when the (2-D) juggler was tossing scarves, huge vertical swaths of color were left behind). I re-enabled hw.drm.msi & rebooted; got the lockup. Noticed that sending a BREAK on serial console does get me into DDB. Rebooted; fsck; disabled hw.drm.msi again; rebooted (there's a lot of that...). xdm came up OK. I logged in via ssh, the started killing off the xdm process. It would terminate, then init(8) would fire it back up again (courtesy of the entry in /etc/ttys), as expected. About the 5th time around, xdm didn't come back. Couldn't switch to a vty (via Ctl+Alt+Fx). No "login: " prompt at serial console. Sent a BREAK to the latter; backtrace shows: agp0: Setting AGP v2 mode 4 info: [drm] Setting GART location based on new memory map info: [drm] Loading R200 Microcode info: [drm] writeback test succeeded in 2 usecs drm0: [MPSAFE] drm0: [ITHREAD] agp0: Setting AGP v2 mode 4 info: [drm] Setting GART location based on new memory map info: [drm] Loading R200 Microcode info: [drm] writeback test succeeded in 2 usecs drm0: [MPSAFE] drm0: [ITHREAD] ~KDB: enter: Line break on console [thread pid 13 tid 100005 ] Stopped at 0xc081c68a =3D kdb_enter_why+0x3a: movl $0,0xc0cd= 1338 =3D kdb_why db> bt Tracing pid 13 tid 100005 td 0xc54e36c0 kdb_enter_why(c0b63ea1,c0b9492d,c0cd0480,b,c5c0c48c,...) at 0xc081c68a =3D = kdb_enter_why+0x3a siointr1(c07f7526,c54e36c0,0,6,c3feb7f8,...) at 0xc0ad07c3 =3D siointr1+0x1= 33 siointr(c5c0c400,c54e36c0,c0ca1830,c552a700,4,...) at 0xc0ad2140 =3D sioint= r+0x70 intr_event_handle(c552a700,c51b1c78,c58768cc,c54e36c0,4,...) at 0xc07ca25c = =3D intr_event_handle+0x5c intr_execute_handlers(c0ca1830,c51b1c78,c0811a2f,c54e36c0,c58766c0,...) at = 0xc0ae5e2f =3D intr_execute_handlers+0x4f atpic_handle_intr(4,c51b1c78) at 0xc0b019f7 =3D atpic_handle_intr+0xf7 Xatpic_intr4() at 0xc0ae1171 =3D Xatpic_intr4+0x21 --- interrupt, eip =3D 0xc0aeb07b, esp =3D 0xc51b1cb8, ebp =3D 0xc51b1cbc -= -- spinlock_exit(1,0,c0b9ea17,4fc,0,...) at 0xc0aeb07b =3D spinlock_exit+0x2b ithread_loop(c54db880,c51b1d38,0,0,0,...) at 0xc07caea8 =3D ithread_loop+0x= 338 fork_exit(c07cab70,c54db880,c51b1d38) at 0xc07c7089 =3D fork_exit+0x99 fork_trampoline() at 0xc0ae1080 =3D fork_trampoline+0x8 --- trap 0, eip =3D 0, esp =3D 0xc51b1d70, ebp =3D 0 --- db> show lock=20 db> show sleepqueue db> show lockchain=20 thread 100005 (pid 13, swi4: clock sio) running on CPU 0 db> show sleepchain thread 100005 (pid 13, swi4: clock sio) running on CPU 0 Please let me know if there's any other information I could provide; I'd like to help get this resolved. Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --9A1A73/U17WN0PFw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAktzCw8ACgkQmprOCmdXAD0R6ACfV036VkZsy9Rzjb074NG3HYdZ ZYcAn1oNBXny+Ib0sjrkuNCOvco+lszo =avOO -----END PGP SIGNATURE----- --9A1A73/U17WN0PFw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100210193752.GE391>