From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Brandon Low <lostlogic@lostlogicx.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.20: libata PATA ATAPI CDROM weirdness on ALI
Date: Sun, 18 Feb 2007 08:54:39 +0300 [thread overview]
Message-ID: <20070218055440.AF4D839BCA7@muan.mtu.ru> (raw)
In-Reply-To: <20070218045625.GE19788@lostlogicx.com>
Brandon Low wrote:
> I'm having some weirdness during boot with my optical drives on 2.6.20.
>
> ata2.00: ATAPI, max UDMA/33
> ata2.01: ATAPI, max UDMA/33
> ata2.00: qc timeout (cmd 0xef)
> ata2.00: failed to set xfermode (err_mask=0x4)
> ata2.00: limiting speed to UDMA/25
> ata2: failed to recover some devices, retrying in 5 secs
> ata2.00: configured for UDMA/25
> ata2.01: configured for UDMA/33
>
> the 4 lines starting with qc timeout _would_ repeat with lower speeds
> until the drive was finally disabled and then do the same for 2.01,
> except that on this particular attempt, I had the thought to eject both
> optical drives while it sat there. Boot then proceeded normally and the
> drives appear to work.
>
> Intuitively this seems to indicate that the drives aren't being sent
> some kind of wake-up call before their transfer modes are set.
>
> The motherboard is an ASRock 939 Dual SATA II.
>
In my case of relatively old ALi chipset CD-ROM was never detected if DMA is
allowed. Unfortunately this remained mystery for quite some time. Legacy
IDE drivers are working just fine; it is only pata_ali that failes :(
See e.g. http://marc.theaimsgroup.com/?l=linux-kernel&m=116500554505311&w=2
(2.6.19: ALi M5229 - CD-ROM not found with pata_ali)
if you have any idea how to debug it ...
-andrey
> Let me know if there is any more information that I can provide.
>
> Thanks,
>
> Brandon Low
prev parent reply other threads:[~2007-02-18 5:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 4:56 Brandon Low
2007-02-18 5:54 ` Andrey Borzenkov [this message]
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=20070218055440.AF4D839BCA7@muan.mtu.ru \
--to=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lostlogic@lostlogicx.com \
/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
all inboxes | Powered by JetHome®