From: Tejun Heo <tj@kernel.org>
To: Alexander Huemer <alexander.huemer@sbg.ac.at>
Cc: Frans Pop <elendil@planet.nl>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: 2.6.{30,31} x86_64 ahci problem - irq 23: nobody cared
Date: Mon, 12 Oct 2009 19:07:03 +0900 [thread overview]
Message-ID: <4AD2FFC7.5010402@kernel.org> (raw)
In-Reply-To: <4AD2FD10.2010800@sbg.ac.at>
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.
--
tejun
next prev parent reply other threads:[~2009-10-12 10:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ABBB8C2.2080901@sbg.ac.at>
2009-09-24 19:24 ` 2.6.{30,31} x86_64 ahci problem - irq 23: nobody cared Frans Pop
2009-09-24 19:30 ` Alexander Huemer
2009-09-24 19:40 ` Frans Pop
2009-09-24 19:43 ` Alexander Huemer
2009-09-25 0:02 ` Alexander Huemer
2009-09-25 11:28 ` Alexander Huemer
2009-09-25 12:24 ` Frans Pop
2009-09-25 12:27 ` Alexander Huemer
2009-09-25 12:48 ` Frans Pop
2009-10-08 12:00 ` Alexander Huemer
2009-10-09 21:30 ` Alexander Huemer
2009-10-10 13:13 ` Frans Pop
2009-10-11 20:57 ` Alexander Huemer
2009-10-12 7:49 ` Tejun Heo
2009-10-12 9:48 ` Frans Pop
2009-10-12 9:52 ` Tejun Heo
2009-10-12 9:55 ` Alexander Huemer
2009-10-12 10:07 ` Tejun Heo [this message]
2009-10-12 10:11 ` Alexander Huemer
2009-10-12 15:03 ` Alexander Huemer
2009-10-12 17:28 ` Robert Hancock
2009-10-13 2:17 ` Tejun Heo
2009-10-13 6:49 ` Alexander Huemer
2009-10-13 12:35 ` Tejun Heo
2009-10-14 11:45 ` Jean Delvare
2009-10-21 8:38 ` Jean Delvare
2009-10-21 10:01 ` Alexander Huemer
2009-10-21 11:28 ` Jean Delvare
2009-10-26 15:01 ` Alexander Huemer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AD2FFC7.5010402@kernel.org \
--to=tj@kernel.org \
--cc=alexander.huemer@sbg.ac.at \
--cc=elendil@planet.nl \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).