From: Matthew Stapleton <matthew4196@gmail.com>
To: linux-ide@vger.kernel.org
Subject: Re: ICH7m problem using libata
Date: Tue, 19 Dec 2006 10:40:15 +1000 [thread overview]
Message-ID: <200612191040.16608.matthew4196@gmail.com> (raw)
Jan Gutter wrote:
> and the hard drive just uses PIO. With libata, it hangs up randomly,
> causing the driver to eventually clock down to PIO mode too.
I have a new Acer 5614WSMi with similar timeouts, and although it has a
different model PATA hard drive, the PATA cdrom is the same model and
firmware version, and it seems to be the cdrom that is timing out.
When I migrated my gentoo install over, the first kernel I tried was 2.6.18
with both the IDE PIIX driver (manually added the ICH7M pci id to get DMA)
and libata and I got timeouts on both drivers. I'm now using libata on
kernel: 2.6.19-gentoo-r2 which is based on mainline 2.6.19.1 and am still
getting timeouts.
At first I noticed that the timeouts stop if I don't have any programs running
(like hald) that regularly query the cdrom. Then I had a look at the hald
source code to find out which commands might be causing the timeouts. I
wrote a simple test program that just opens the cdrom with "O_RDONLY |
O_NONBLOCK" then immediately closes it and loops every second and it
triggered a timeout after a few hours. Then I changed the delay to 4 seconds
and still got a timeout after a while. If I change the test program to only
open the cdrom once then continously execute a status command such as the
CDROM_DRIVE_STATUS ioctl every second, the timeouts don't seem to occur.
Hopefully this should help with finding the source of the problem.
--
Matthew Stapleton
next reply other threads:[~2006-12-19 0:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 0:40 Matthew Stapleton [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-16 14:11 ICH7m problem using libata Mikael Pettersson
2007-01-16 14:51 ` Jan Gutter
2006-12-04 17:36 Jan Gutter
2006-12-20 0:18 ` Tejun Heo
2007-01-03 3:07 ` Matthew Stapleton
2007-01-03 3:44 ` Tejun Heo
2007-01-09 22:17 ` Matthew Stapleton
2007-01-15 5:20 ` Tejun Heo
2007-01-15 23:58 ` Matthew Stapleton
2007-01-16 8:56 ` Tejun Heo
2007-01-16 11:31 ` Jan Gutter
2007-01-16 11:42 ` Tejun Heo
2007-01-16 13:53 ` Jan Gutter
2007-01-17 5:11 ` Tejun Heo
2007-01-17 13:25 ` Jan Gutter
2007-01-17 13:41 ` Tejun Heo
2007-01-18 2:13 ` Matthew Stapleton
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=200612191040.16608.matthew4196@gmail.com \
--to=matthew4196@gmail.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).