From owner-freebsd-current@FreeBSD.ORG Wed Aug 6 17:22:32 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7D8DE2F7; Wed, 6 Aug 2014 17:22:32 +0000 (UTC) Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4744D2A2D; Wed, 6 Aug 2014 17:22:32 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id hz1so3740579pad.8 for ; Wed, 06 Aug 2014 10:22:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=57ug++P8eGgoh/VUOJEVzyOw9g3/3vZAc3l2nS2W2TY=; b=qBn/HYMBNtZezEZ39DbepAxoy7etamSE5FS/x5rgp7aOXHy2YJMy2yPXCQHGsnf3yu 2U/3AuCxdvUE1H5sd8Q/uyT2BykYFZl1p3UQKjoNxv5d8tcW4PgyGEwCQn3QRa3tGGrG 8PLybfcjXUlhX/yBGovh9KzSf8mU7n0NM67kEZUu1a0fBgvWZaWQGVtbtH9/yeCbspbb SjuD7fslS1r/mFtJiWPW9/YQys5K1lBu3TjtLlHpr8xb3t/SnnBOrC62ur9ASexKdjqY llmLzn6WFgwcs1O5OXLFR27tgruOnSHd82BFfEahFA6OsgrAmFwKCCWrRAK3CcsCgWIk lNoA== X-Received: by 10.68.104.66 with SMTP id gc2mr12609278pbb.17.1407345751784; Wed, 06 Aug 2014 10:22:31 -0700 (PDT) Received: from [192.168.20.11] (c-98-247-240-204.hsd1.wa.comcast.net. [98.247.240.204]) by mx.google.com with ESMTPSA id ni5sm2611540pdb.35.2014.08.06.10.22.30 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 06 Aug 2014 10:22:31 -0700 (PDT) References: <53E178BC.4040201@freebsd.org> <53E1F6E3.1040304@FreeBSD.org> <5850878054da9ac1898035b6c5d010e5@sonic.net> <53E25D3E.7000200@FreeBSD.org> Mime-Version: 1.0 (1.0) In-Reply-To: <53E25D3E.7000200@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPhone Mail (11D257) From: Garrett Cooper Subject: Re: r259580 breaks radeonkms Date: Wed, 6 Aug 2014 10:22:31 -0700 To: =?utf-8?Q?Roger_Pau_Monn=C3=A9?= Cc: David Mackay , "freebsd-current@freebsd.org" , Nathan Whitehorn X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Aug 2014 17:22:32 -0000 > On Aug 6, 2014, at 9:52, Roger Pau Monn=C3=A9 wrote: >=20 >> On 06/08/14 16:35, Nathan Whitehorn wrote: >>=20 >>=20 >>> On 2014-08-06 02:35, Roger Pau Monn=C3=A9 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, bu= t >>>> the system is unusable in the meantime. >>>> -Nathan >>>=20 >>> I seem to be able to load radeonkms just fine after r269580: >>=20 >> 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 >=20 > 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. >=20 > Roger. >=20 > <0001-drm-fix-usage-of-vm_phys_fictitious_to_vm_page.patch> David McKay confirmed that the patch worked for them on an intel GEM compati= ble chipset. Cheers! -Garrett=