From: Thierry Vignaud <tvignaud@mandriva.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [Fwd: [BUG] sata_via doesn't detect anymore my disks (broken between rc1 and rc3)]
Date: Fri, 20 Oct 2006 20:59:03 +0200 [thread overview]
Message-ID: <m2u01yddag.fsf@vador.mandriva.com> (raw)
In-Reply-To: <44F30ABE.2050803@gmail.com> (Tejun Heo's message of "Tue, 29 Aug 2006 00:24:46 +0900")
Tejun Heo <htejun@gmail.com> writes:
> >>>>> The second patch is essentially identical to what you did the
> >>>>> one liner. Can you please check it once more? I'll prepare
> >>>>> old-sequence hardreset in the meantime.
> >>>> Okay, here's the old-sequence hardreset patch. This should have
> >>>> the highest chance of working. This patch should be applied on
> >>>> top of the vt6420 patch.
> >>> On top of which patch?
> >>> I just tried to apply it on top of:
> >>> - your last week patch
> >>> - your two patches of this week
> >>> and it does *not* apply on top of anyone...
> >> Arghh... Sorry. I sent the wrong version. This patch is against
> >> #upstream while I should have sent the one against #upstream-fixes.
> >>
> >>> Couldn't you either check first your patch or (better) just send a
> >>> patch against vanilla 2.6.18-rc4-mm2?
> >> I've attached whole sata_via.c to the other mail. I think that should
> >> do the trick.
> > It didn't (tested by overwriting 2.6.18-rc4-mm2's driver).
> > I tried a few reset methods combinations w/os success.
> > Like in other faillure cases, the driver saw the two links but failed
> > to see the hd attached to the second sata link.
>
> Hmmm.. That's very weird. The detection sequence is almost identical
> to the original code. Argh..... Any ideas?
btw, I tried again with rc1 and rc2.
here, the diff on sata-via against 2.6.18 are trivials and irrelevant
so it looks like the issue is introduce by core changes in libata
(that maybe uncover a previously hidded issue in sata-via?)
next prev parent reply other threads:[~2006-10-20 18:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44D98E7E.3060208@pobox.com>
[not found] ` <44E29AEF.8030606@gmail.com>
[not found] ` <20060816051408.GI6371@htj.dyndns.org>
[not found] ` <m2wt98bio1.fsf@vador.mandriva.com>
[not found] ` <m2sljwbil7.fsf@vador.mandriva.com>
[not found] ` <44E37BD4.8010709@pobox.com>
[not found] ` <m23bbva9cs.fsf@vador.mandriva.com>
[not found] ` <44E46E0E.4060703@gmail.com>
[not found] ` <m2fyfv7a8s.fsf@vador.mandriva.com>
2006-08-22 16:37 ` [Fwd: [BUG] sata_via doesn't detect anymore my disks (broken between rc1 and rc3)] Tejun Heo
2006-08-23 20:17 ` Thierry Vignaud
2006-08-25 10:29 ` Thierry Vignaud
2006-08-25 12:16 ` Tejun Heo
2006-08-25 13:55 ` Tejun Heo
2006-08-25 14:09 ` Thierry Vignaud
2006-08-25 15:03 ` Tejun Heo
2006-08-25 15:30 ` Thierry Vignaud
2006-08-28 14:34 ` Thierry Vignaud
2006-08-28 15:24 ` Tejun Heo
2006-08-28 15:43 ` Thierry Vignaud
2006-10-03 15:00 ` Thierry Vignaud
2006-10-20 18:59 ` Thierry Vignaud [this message]
2006-08-25 13:56 ` Thierry Vignaud
2006-08-25 14:02 ` Thierry Vignaud
2006-08-25 15:02 ` Tejun Heo
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=m2u01yddag.fsf@vador.mandriva.com \
--to=tvignaud@mandriva.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).