Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753370Ab2KEIkk (ORCPT ); Mon, 5 Nov 2012 03:40:40 -0500 Received: from mail-ob0-f174.google.com ([209.85.214.174]:61523 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753052Ab2KEIkj (ORCPT ); Mon, 5 Nov 2012 03:40:39 -0500 MIME-Version: 1.0 In-Reply-To: <20121105092904.74d7ff6703f984b0b05f8e16@studenti.unina.it> References: <20121029231624.1476a25a62a0c219cc25627a@studenti.unina.it> <20121105092904.74d7ff6703f984b0b05f8e16@studenti.unina.it> Date: Mon, 5 Nov 2012 08:40:38 +0000 Message-ID: Subject: Re: nouveau, linux3.7-rc3: BUG: unable to handle kernel paging request at fffffffffffffff8 From: Dave Airlie To: Antonio Ospite Cc: dri-devel@lists.freedesktop.org, David Airlie , Ben Skeggs , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1845 Lines: 42 On Mon, Nov 5, 2012 at 8:29 AM, Antonio Ospite wrote: > On Mon, 29 Oct 2012 23:16:24 +0100 > Antonio Ospite wrote: > >> Hi, >> >> I am experiencing a bug with nouveau with linux-3.7-rc3 (and since rc1), >> my video adapter is the one integrated on the MSI M3N78-VM motherboard >> (hence x86_64): >> > [...] >> [ 1943.858601] BUG: unable to handle kernel paging request at fffffffffffffff8 >> [ 1943.858669] IP: [] nouveau_mm_head+0x30/0x127 [nouveau] >> [ 1943.858779] PGD 160d067 PUD 160e067 PMD 0 >> [ 1943.858803] Oops: 0000 [#1] SMP > [..] >> [ 1943.860018] Call Trace: >> [ 1943.860019] [] ? kmem_cache_alloc_trace+0xbf/0xcf >> [ 1943.860019] [] ? should_resched+0x5/0x23 >> [ 1943.860019] [] ? nv50_fb_vram_new+0xc5/0x1f2 [nouveau] > > Ben, I cannot reproduce the crash with 3.7-rc4, I spotted commits > a7dbf00 and 5cad16a which seem to be related to the problem I was > having; would you mind elaborating a bit about what you think was > causing the crash on my side? Maybe the chipset used on this motherboard > doesn't support some feature? And how did you figured out from the logs? > 5cad16acd25b16681a060d28d10eeacf98d07701 is the actual fix The chipset hasn't got Z compression support, and the oops once decoded pointed out the new code was trying to allocate Z tags from a NULL memory block. The old code use to allocate an empty memory block instead of NULL, and it got lost in the rewrite, Ben just fixed it to allow empty memory blocks again. Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/