From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Martin Rogge <marogge@onlinehome.de>
Cc: bzolnier@gmail.com, linux-ide@vger.kernel.org
Subject: Re: Fwd: CMD 64x regression from 2.6.21 to 2.6.22 and 2.6.23?
Date: Tue, 16 Oct 2007 15:53:09 +0400 [thread overview]
Message-ID: <4714A625.8040306@ru.mvista.com> (raw)
In-Reply-To: <200710152339.33718.marogge@onlinehome.de>
Martin Rogge wrote:
>> Could you git-bisect this?
>> Although I have a couple of patch suspects (dealing with interrupts),
>>all worked fine with PCI-649 just fine. PCI-648 is not really much
>>different from 649 according to specs...
> Yes, I found the same when I managed to send the CMD 648 into UDMA-100 mode years ago (by treating it like a 649).
> Anyway, I found the git patches on kernel.org and bisected away. For completeness, this is the table containing all my results.
> Kernel System reaction
> ============================================================================
> 2.6.21 CMD 648 working fine
> 2.6.21-git4 CMD 648 working fine
> 2.6.21-git5 CMD 648 working fine
> 2.6.21-git6 irg 15: nobody cared [...] Disabling IRQ #15 etc.
> 2.6.21-git8 irg 15: nobody cared [...] Disabling IRQ #15 etc.
> 2.6.22-rc1 irg 15: nobody cared [...] Disabling IRQ #15 etc.
> 2.6.22 irg 15: nobody cared [...] Disabling IRQ #15 etc.
> 2.6.23 irg 15: nobody cared [...] Disabling IRQ #15 etc.
> Well, most likely the CMD related patches in git6 are the culprit.
Erm... usually bisection leaves you with one patch startting from which
kernel was broken. It seems you've done sort iof manual bisecting. Thanks
anyway. :-)
> Regards,
> cu Martin
MBR, Sergei
next prev parent reply other threads:[~2007-10-16 11:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710142211.03382.marogge@onlinehome.de>
2007-10-15 17:14 ` Fwd: CMD 64x regression from 2.6.21 to 2.6.22 and 2.6.23? Sergei Shtylyov
[not found] ` <200710152339.33718.marogge@onlinehome.de>
2007-10-16 11:53 ` Sergei Shtylyov [this message]
2007-10-16 12:43 ` Mark Lord
2007-10-16 12:59 ` Sergei Shtylyov
2007-10-16 22:14 ` Bartlomiej Zolnierkiewicz
2007-10-17 19:15 ` Martin Rogge
2007-10-17 20:40 ` Sergei Shtylyov
2007-10-19 19:58 ` Martin Rogge
2007-10-19 20:26 ` Sergei Shtylyov
2007-10-19 23:09 ` Martin Rogge
2007-10-20 14:55 ` Sergei Shtylyov
2007-10-20 17:11 ` Sergei Shtylyov
2007-10-21 20:55 ` Martin Rogge
2007-10-26 15:38 ` Sergei Shtylyov
2007-10-18 22:39 ` Martin Rogge
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=4714A625.8040306@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=marogge@onlinehome.de \
/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).