[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AD300B5.6080102@sbg.ac.at>
Date: Mon, 12 Oct 2009 12:11:01 +0200
From: Alexander Huemer <alexander.huemer@....ac.at>
To: Tejun Heo <tj@...nel.org>
CC: Frans Pop <elendil@...net.nl>, linux-kernel@...r.kernel.org,
linux-ide@...r.kernel.org, Jeff Garzik <jgarzik@...ox.com>,
alexander.huemer@....ac.at
Subject: Re: 2.6.{30,31} x86_64 ahci problem - irq 23: nobody cared
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists