Date: Wed, 06 Aug 2014 10:22:47 -0700 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= <royger@FreeBSD.org>, freebsd-current@FreeBSD.org Subject: Re: r259580 breaks radeonkms Message-ID: <53E26467.8020509@freebsd.org> In-Reply-To: <53E25D3E.7000200@FreeBSD.org> References: <53E178BC.4040201@freebsd.org> <53E1F6E3.1040304@FreeBSD.org> <5850878054da9ac1898035b6c5d010e5@sonic.net> <53E25D3E.7000200@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/06/14 09:52, Roger Pau Monné wrote: > On 06/08/14 16:35, Nathan Whitehorn wrote: >> >> On 2014-08-06 02:35, Roger Pau Monné wrote: >>> On 06/08/14 02:37, Nathan Whitehorn wrote: >>>> Kernels with r269580 will panic when loading the radeonkms driver in >>>> pmap_page_set_memattr(). This probably indicates a bug in radeonkms, but >>>> the system is unusable in the meantime. >>>> -Nathan >>> I seem to be able to load radeonkms just fine after r269580: >> It's possible that it is related to actually using it, rather than >> loading the module. I was only testing them together. I'm using vt and >> the panic (page fault in kernel mode) occurs when TTM tries to set >> memory attributes on some page while starting X. Before the panic, I see >> all the normal Radeon module messages as you do, so the module seems to >> have actually loaded correctly. The KMS console also seems to be >> functional enough to display the panic message, so I suspect it's X that >> triggers it. >> -Nathan > Please try the attached patch, it seems to solve the panic for me. It > also includes a fix for Intel i915 gem, which I'm not able to test > because I don't have the hardware. > > Roger. > Works for me on radeon. Thanks! -Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53E26467.8020509>