From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755370Ab1DRP7h (ORCPT ); Mon, 18 Apr 2011 11:59:37 -0400 Received: from mail-iw0-f174.google.com ([209.85.214.174]:37666 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754029Ab1DRP7b convert rfc822-to-8bit (ORCPT ); Mon, 18 Apr 2011 11:59:31 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=c2e9TvfwbI09ZgBElr7U+fH+giVrVOlD8ju5UJ2nec0iYPzNMlAFJ8QB2XwWTcfilI NCvnvCRxNshIMVBoFbxgcHQCHDMjKc1dOw9qJtB/RNGtKIJBAcY1uzHG3kPZeRUkA/09 Vn6Y2BEACinlWR1EjQCXmmARK9PePzpCkBT0c= MIME-Version: 1.0 In-Reply-To: References: <4DA655E7.3000904@zytor.com> <20110415131152.GJ18463@8bytes.org> <20110415131650.GB18660@elte.hu> <20110415154604.GN18463@8bytes.org> <20110416163509.GS18463@8bytes.org> <20110417140924.GU18463@8bytes.org> Date: Mon, 18 Apr 2011 11:59:25 -0400 Message-ID: Subject: Re: Linux 2.6.39-rc3 From: Jerome Glisse To: Alex Deucher Cc: Joerg Roedel , Yinghai Lu , Linux Kernel Mailing List , "dri-devel@lists.freedesktop.org" , "H. Peter Anvin" , Tejun Heo , Linus Torvalds , Thomas Gleixner , alexandre.f.demers@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 18, 2011 at 11:33 AM, Alex Deucher wrote: > On Mon, Apr 18, 2011 at 11:29 AM, Jerome Glisse wrote: >> On Mon, Apr 18, 2011 at 11:23 AM, Alex Deucher wrote: >>> On Sun, Apr 17, 2011 at 10:09 AM, Joerg Roedel wrote: >>>> On Sat, Apr 16, 2011 at 02:54:04PM -0400, Jerome Glisse wrote: >>>> >>>>> If you want to go the printk way you can add printk before each test >>>>> ring_test, ib_test in r600.c this 2 functions are the own that might >>>>> trigger the first GPU gart activities. >>>> >>>> Okay, I found the place in source that triggers this. It happens in the >>>> function r600_ib_test. The interesting thing is that not the ib-command >>>> itself is responsible but the fence that is emitted afterwards (proved >>>> by removing the fence command, where the problem went away). >>>> I don't know enough about the command semantics to make a guess what >>>> goes wrong there. But maybe you GPU folks have an idea? >>>> >>> >>> I can't think of anything off hand.  It might be worth disabling the >>> call to r600_ib_test() in r600_init() and then seeing if you get any >>> errors when the fences are used later on when X starts or just at that >>> point in the module load sequence.  What's odd is that when you tested >>> radeon.no_wb=1 you got the same behavior as that disables shadowing of >>> fence writes to gpu gart mem, so it wouldn't be writing to memory in >>> that case. >>> >>> Alex >>> >> >> It might be the irq ring write that is faulty. > > That's disabled with no_wb=1 as well. > > Alex > I mean the irq interrupt ring, i don't see this being disabled when no_wb=1 Cheers, Jerome