linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Tejun Heo <tj@kernel.org>
Cc: Alexander Huemer <alexander.huemer@sbg.ac.at>,
	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: Wed, 14 Oct 2009 13:45:29 +0200	[thread overview]
Message-ID: <200910141345.30177.jdelvare@suse.de> (raw)
In-Reply-To: <4AD473F9.7090606@kernel.org>

Le mardi 13 octobre 2009, Tejun Heo a écrit :
> Alexander Huemer wrote:
> > 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.
> 
> Given that i2c is used for temperature monitoring, I think it is not
> triggered by any single step of the compiling but rather by the
> accumulated heat load during compilation.  Let's wait for Jean to
> chime in.  :-)

Sorry, I'm somewhat busy at the moment, I'll give it a look as soon
as I get a moment.

-- 
Jean Delvare
Suse L3

  reply	other threads:[~2009-10-14 11:46 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
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 [this message]
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=200910141345.30177.jdelvare@suse.de \
    --to=jdelvare@suse.de \
    --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 \
    --cc=tj@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).