Date: Thu, 04 Sep 2008 15:28:30 -0400 From: Robert Noland <rnoland@FreeBSD.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@FreeBSD.org Subject: Re: drm causes kernel panic Message-ID: <1220556510.54710.49.camel@squirrel.corp.cox.com> In-Reply-To: <20080904185205.GA2699@troutmask.apl.washington.edu> References: <20080903011612.GA1242@troutmask.apl.washington.edu> <1220416793.1848.1.camel@wombat.2hip.net> <20080903051228.GA2475@troutmask.apl.washington.edu> <1220471512.11763.9.camel@squirrel.corp.cox.com> <20080903195845.GA1370@troutmask.apl.washington.edu> <1220493627.2467.6.camel@wombat.2hip.net> <20080904170208.GA1463@troutmask.apl.washington.edu> <1220550785.54710.33.camel@squirrel.corp.cox.com> <20080904185205.GA2699@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-NE/jSCzcGR/H2beSbO7k Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2008-09-04 at 11:52 -0700, Steve Kargl wrote: > On Thu, Sep 04, 2008 at 01:53:05PM -0400, Robert Noland wrote: > > On Thu, 2008-09-04 at 10:02 -0700, Steve Kargl wrote: > > >=20 > > > Your patch fixes the problem. With a new kernel and Xorg's dri > > > module loaded, I now see in /var/log/Xorg.0.log > > >=20 > > > (II) MACH64(0): [drm] SAREA 2200+1208: 3408 > > > drmOpenDevice: node name is /dev/dri/card0 > > > drmOpenDevice: open result is 9, (OK) > > > drmOpenDevice: node name is /dev/dri/card0 > > > drmOpenDevice: open result is 9, (OK) > > > drmOpenByBusid: Searching for BusID pci:0000:03:06.0 > > > drmOpenDevice: node name is /dev/dri/card0 > > > drmOpenDevice: open result is 9, (OK) > > > drmOpenByBusid: drmOpenMinor returns 9 > > > drmOpenByBusid: drmGetBusid reports pci:0000:03:06.0 > > > (II) [drm] DRM interface version 1.2 > > > (II) [drm] DRM open master succeeded. > > > (II) MACH64(0): [drm] Using the DRM lock SAREA also for drawables. > > > (II) MACH64(0): [drm] framebuffer handle =3D 0xfd000000 > > > (II) MACH64(0): [drm] added 1 reserved context for kernel > > > (II) MACH64(0): X context handle =3D 0x1 > > > (II) MACH64(0): [drm] installed DRM signal handler > > > (II) MACH64(0): [drm] Will request asynchronous DMA mode > > > (=3D=3D) MACH64(0): [drm] Using 2 MB for DMA buffers > > > (II) MACH64(0): [pci] ring handle =3D 0x64a34000 > > > (II) MACH64(0): [pci] Ring mapped at 0x2006d4000 > > > (II) MACH64(0): [drm] register handle =3D 0xfeaff000 > > > (II) MACH64(0): [dri] Visual configs initialized > > > (II) MACH64(0): [dri] Block 0 base at 0xfeaff400 > > > (WW) MACH64(0): Not enough memory for local textures, disabling DRI > > > (II) MACH64(0): [drm] removed 1 reserved context for kernel > > > (II) MACH64(0): [drm] unmapping 8192 bytes of SAREA 0xfffffffe4096200= 0 at 0x2006d2000 > > > (II) MACH64(0): [drm] Closed DRM master. > >=20 > > I'm guessing that this is a pci based card like mine? So, I assume thi= s > > is the same case as before the updates? > >=20 >=20 > Yes, it is pci based. It's actually an integrate ATI Rage XL on > the Tyan motherboard. I updated my Xorg installation, so the > previous behavior isn't relevant. Prior to the Xorg update,=20 > Xorg's dri module refused to load because the drm version is > 1.2, which was previously unsupported. Ok, I have one system like that. So this seems good on mach64 and intel... Now, if I can just get a report on radeon... robert. >=20 --=-NE/jSCzcGR/H2beSbO7k 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) iEYEABECAAYFAkjANt4ACgkQM4TrQ4qfROP6BQCeJdz4+WlKuURExSFBi7aItkLE 84cAn3ND8GEPU22CkpZij3gR34L32SsQ =cagv -----END PGP SIGNATURE----- --=-NE/jSCzcGR/H2beSbO7k--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1220556510.54710.49.camel>