Date: Sun, 26 Jun 2005 11:14:33 -0700 From: Eric Anholt <eta@lclark.edu> To: Martin Cracauer <cracauer@cons.org> Cc: freebsd-current@freebsd.org, Warner Losh <imp@bsdimp.com> Subject: Re: 6.0-current panic: loading radeon module Message-ID: <1119809673.3817.3.camel@leguin> In-Reply-To: <20050624195906.A5702@cons.org> References: <20050617173008.A11142@cons.org> <20050617194638.A13394@cons.org> <20050617.233055.41723867.imp@bsdimp.com> <200506241641.25433.jhb@FreeBSD.org> <1119650444.1173.105.camel@leguin> <20050624195906.A5702@cons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2005-06-24 at 19:59 -0400, Martin Cracauer wrote: > > I'd forgotten about this thread. I've got a proposed fix for this at: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/80718 > > I get the same panic and backtrace with that patch (on a 32 MB moobile > Radeon 7500). > > I will annotate the sourcecode now to verify (or not) the NULLs in the > arguments for the bus argument. Thanks for showing that that patch didn't work. I should have remembered why it wouldn't. The next step would be to try a workaround: Comment out the two calls to drm_initmap() in radeon_cp.c. We really need a nice call to grab the start/offset of a pci resource given the rid. We can avoid it now, but we might not be able to given where the DRM is headed. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1119809673.3817.3.camel>