From: Alexander Huemer <alexander.huemer@sbg.ac.at>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Tejun Heo <tj@kernel.org>, Jeff Garzik <jgarzik@pobox.com>,
alexander.huemer@sbg.ac.at
Subject: Re: 2.6.{30,31} x86_64 ahci problem - irq 23: nobody cared
Date: Sun, 11 Oct 2009 22:57:07 +0200 [thread overview]
Message-ID: <4AD246A3.5000700@sbg.ac.at> (raw)
In-Reply-To: <200910101513.51320.elendil@planet.nl>
I don't know what vanilla-2.6.31-r2 is, but I assume it's based on
either 2.6.31.3 or 2.6.31.2.
vanilla just means the unpatched kernel from kernel.org.
The most likely explanation is that your earlier test from which you
concluded that the revert did fix the problem was incorrect. It seems
unlikely that some other stable commit interferes here.
So basically we're back where we started.
unfortunately you seem to be right.
How reproducible is the error for you? Do you see it every time or not?
If it is reliably reproducible, can you think of any explanation why your
earlier test was a success while we now see that the revert does not help?
the error is reproducible. i'll try to pin it down to certain kernel
versions in the next days.
Does the error *only* occur during gcc compilation, or was that just the
simplest way to reproduce it? Does it always occur at the same point during
the compilation or does it vary?
it was the simplest way.
i don't know how i could find out if the error actually always
happens exactly the same time.
i'll think about that.
Can you create a test case that does not require doing the whole
compilation, but only executes the step that triggers the error?
surely, if i know what happens when the error occurs.
If you can find a reliable and fairly quick way to reproduce the error, I
would suggest doing a bisection.
i would be happy to do that.
thanks for now.
next prev parent reply other threads:[~2009-10-11 20:57 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 [this message]
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
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=4AD246A3.5000700@sbg.ac.at \
--to=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).