Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758977AbZJMGuI (ORCPT ); Tue, 13 Oct 2009 02:50:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758967AbZJMGuG (ORCPT ); Tue, 13 Oct 2009 02:50:06 -0400 Received: from mx06.lb01.inode.at ([62.99.145.6]:5985 "EHLO mx.inode.at" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758947AbZJMGuF (ORCPT ); Tue, 13 Oct 2009 02:50:05 -0400 Message-ID: <4AD422F2.4080308@sbg.ac.at> Date: Tue, 13 Oct 2009 08:49:22 +0200 From: Alexander Huemer User-Agent: Thunderbird 2.0.0.23 (X11/20090826) MIME-Version: 1.0 To: Tejun Heo CC: Jean Delvare , Frans Pop , linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org, Jeff Garzik , alexander.huemer@sbg.ac.at Subject: Re: 2.6.{30,31} x86_64 ahci problem - irq 23: nobody cared References: <4ABBB8C2.2080901@sbg.ac.at> <200910101513.51320.elendil@planet.nl> <4AD2DFA4.9000602@kernel.org> <200910121148.16439.elendil@planet.nl> <4AD2FC60.8080705@kernel.org> <4AD2FD10.2010800@sbg.ac.at> <4AD2FFC7.5010402@kernel.org> <4AD300B5.6080102@sbg.ac.at> <4AD34554.3050701@sbg.ac.at> <4AD3E348.5030508@kernel.org> In-Reply-To: <4AD3E348.5030508@kernel.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2974 Lines: 101 Tejun Heo wrote: > [cc'ing Jean and quoting whole body] > > Hello, Jean. > > It seems i2c_i801 is triggering IRQ storm on Alexander's machine. The > original thread is > > http://thread.gmane.org/gmane.linux.kernel/894187 > > Any ideas? > > Thanks. > > Alexander Huemer wrote: > >> Alexander Huemer wrote: >> >>> Tejun Heo wrote: >>> >>>> Alexander Huemer wrote: >>>> >>>> >>>>> Tejun Heo wrote: >>>>> >>>>> >>>>>> Frans Pop wrote: >>>>>> >>>>>> >>>>>> >>>>>>> On Monday 12 October 2009, Tejun Heo wrote: >>>>>>> >>>>>>> >>>>>>>> Alexander, can you please attach full boot log and the output of >>>>>>>> "lspci -nn"? Also, how reproducible is the problem? You already >>>>>>>> answered to Frans' question but can you be more specific? >>>>>>>> >>>>>>>> >>>>>>> Full dmesg was made available earlier at: >>>>>>> http://xx.vu/~ahuemer/dmesg_ahuemer_20090923 >>>>>>> >>>>>>> >>>>>> Does blacklisting i801_smbus make any difference? >>>>>> >>>>>> >>>>>> >>>>> lspci -nn: >>>>> http://xx.vu/~ahuemer/lspci_nn_ahuemer_20091012 >>>>> >>>>> what do you mean with "blacklisting i801_smbus" ? >>>>> >>>>> >>>> [ 3.872387] i2c /dev entries driver >>>> [ 3.873943] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 23 (level, >>>> low) -> IRQ 23 >>>> [ 3.875580] w83627hf: Found W83627HF chip at 0x290 >>>> >>>> IRQ23 is also used by i801_smbus and it would be nice to confirm >>>> whether the problem can still be triggered with that driver not >>>> loaded. Adding "blacklist i2c_i801" to /etc/modprobe.d/blacklist >>>> should probabaly do the trick. >>>> >>>> Thanks. >>>> >>>> >>>> >>> okay, i think you assume that i2c_i801 is a module. >>> it is indeed built into the kernel. >>> i'll rebuild the kernel without that component and run a test again. >>> >>> regards >>> -alex >>> >> tejun, it seems you hit an interesting point. >> i compiled kernel-2.6.31.3 with my ususal config _without_ i2c_i801. >> my usual test (compilation of gcc-4.3.2) finished 5 times without the >> error. >> i'll let it run some more times over night. >> does anybody have an idea how i can trace what exactly causes the error >> during the compilation run so that i can create a short test program ? >> >> regards >> -alex >> > > hi, i compiled gcc in a loop over night, 14 times. no error. it really seams i2c_i801 was the cause... unfortunately i still don't know how i can extract the part of the gcc compilation process that causes the error on an affected kernel. that would enable me to create a simple test program. regards -alex -- 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/