All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: "Fortier,Vincent [Montreal]" <Vincent.Fortier1@EC.GC.CA>
Cc: Andi Kleen <ak@suse.de>, Marko Macek <Marko.Macek@gmx.net>,
	Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: ASUS A8V Deluxe, x86_64
Date: Tue, 16 May 2006 21:05:56 +0900	[thread overview]
Message-ID: <4469C024.3030506@gmail.com> (raw)
In-Reply-To: <8E8F647D7835334B985D069AE964A4F702463F@ECQCMTLMAIL1.quebec.int.ec.gc.ca>

Fortier,Vincent [Montreal] wrote:
>>> Now I'm having an ASUS A8V Deluxe.... and sadly a lot of problems:
>>>
>>> - My SATA Controller make my Linux crash when connecting a 
>>> Plextor 716SA CD-DVD-R 
>>> (http://bugzilla.kernel.org/show_bug.cgi?id=5533)
> 
>> Patch:
>>
> http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.17-rc4-
> git2-libata1.patch.bz2
>> (diff'd against 2.6.17-rc4-git2, but should apply to most recent
> 2.6.17-rcX[-gitY] kernels)
> 
> I gave a try at the latest ata patches announced yesterday by Jeff and
> it completelly solved my SATA ATAPI bug.. I even been able to burn my
> first DVD using my Plextor 716SA on my Linux!!!  Really nice and much
> anticipated work!  Thnx a lot!
> 
> I have already marked bug 5533 as resolved and I'll wait until inclusion
> into 2.6.18 to close it.  I've also marked bug 6317 has closed since
> that did not occur since around rc2 or rc3 of 2.6.17.
> 

Jeff, do you know what fixed this one?  I've been following the bug and 
thought it was one of those via-ATAPI-have-no-idea bugs.  How come the 
update fix this one?  Have I missed something?

-- 
tejun

  reply	other threads:[~2006-05-16 12:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 11:45 ASUS A8V Deluxe, x86_64 Fortier,Vincent [Montreal]
2006-05-16 11:45 ` Fortier,Vincent [Montreal]
2006-05-16 12:05 ` Tejun Heo [this message]
2006-05-16 12:57   ` Albert Lee
2006-05-16 13:11     ` Tejun Heo
2006-08-10  6:46     ` Reinhard Brandstädter
2006-08-10  7:37       ` Albert Lee
2006-08-10  8:56         ` Reinhard Brandstädter
2006-08-14  6:31           ` Albert Lee
2006-05-16 14:32   ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2006-08-10 14:03 Fortier,Vincent [Montreal]
2006-05-18 10:57 Fortier,Vincent [Montreal]
2006-05-18 10:57 ` Fortier,Vincent [Montreal]
2006-05-18 11:25 ` Albert Lee
2006-05-17 11:02 Fortier,Vincent [Montreal]
2006-05-18  3:29 ` Tejun Heo
2006-05-18  5:28   ` Albert Lee
2006-05-16 14:43 Fortier,Vincent [Montreal]
2006-05-16 14:43 ` Fortier,Vincent [Montreal]
2006-05-16 15:40 ` Tejun Heo
2006-05-16 14:40 Fortier,Vincent [Montreal]
2006-05-16 14:40 ` Fortier,Vincent [Montreal]
2006-05-15 18:23 Fortier,Vincent [Montreal]
2006-05-15 19:08 ` Andi Kleen
2006-05-15 19:23   ` Marko Macek
2006-05-15 19:41     ` Andi Kleen
2006-05-15 17:12 Fortier,Vincent [Montreal]
2006-05-15 12:05 Fortier,Vincent [Montreal]
2006-05-15 17:02 ` Greg KH
2006-05-23  6:10 ` Aaron Gyes

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=4469C024.3030506@gmail.com \
    --to=htejun@gmail.com \
    --cc=Marko.Macek@gmx.net \
    --cc=Vincent.Fortier1@EC.GC.CA \
    --cc=ak@suse.de \
    --cc=jeff@garzik.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.