All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Matthew Stapleton <matthew4196@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: ICH7m problem using libata
Date: Tue, 16 Jan 2007 17:56:27 +0900	[thread overview]
Message-ID: <45AC933B.1000201@gmail.com> (raw)
In-Reply-To: <200701160958.33561.matthew4196@gmail.com>

Matthew Stapleton wrote:
> Tejun Heo wrote:
>> Does the problem still persist?
>>
> With that kernel and the previous patches it does.  I'll try kernel 2.6.20-rc5 
> and the which-cocktail-2.6.19.patch

I got confused between your report and Jan's.  Yours (not so sure about
Jan's) seems to be drive firmware bug which hald was successful to
undiscover.  Does hald clear CDO_USE_FFLAGS using ioctl
CDROM_CLEAR_OPTIONS?  The failed commands seem to be from cdrom
open_for_data().  Considering general quality of ATAPI devices, I
wouldn't be too surprised if some device fails after hours of repeated
poll sequence containing READ_TOC and ALLOW_MEDIUM_REMOVAL.

I think it's best to contact hal people about your issue.  If/when you
contact hal people, please cc me.

Thanks.

-- 
tejun

  reply	other threads:[~2007-01-16  8:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 17:36 ICH7m problem using libata 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2006-12-19  0:40 Matthew Stapleton
2007-01-16 14:11 Mikael Pettersson
2007-01-16 14:51 ` Jan Gutter

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=45AC933B.1000201@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=matthew4196@gmail.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 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.