Date: Sun, 26 Jun 2005 12:57:29 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: eta@lclark.edu Cc: cracauer@cons.org, freebsd-current@FreeBSD.ORG Subject: Re: 6.0-current panic: loading radeon module Message-ID: <20050626.125729.127901479.imp@bsdimp.com> In-Reply-To: <1119809673.3817.3.camel@leguin> References: <1119650444.1173.105.camel@leguin> <20050624195906.A5702@cons.org> <1119809673.3817.3.camel@leguin>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <1119809673.3817.3.camel@leguin>
Eric Anholt <eta@lclark.edu> writes:
: 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.
rman_get_start() doesn't do the trick? Or do you need to know what it
is before the bus_alloc_resource? If so, you can call
bus_get_resource(). What is it that you need to know?
Maybe I should look at the drm code :-)
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050626.125729.127901479.imp>