public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Thomas Molina <tmolina@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide-cd still borken for me in 2.5.45
Date: Fri, 1 Nov 2002 13:06:18 +0100	[thread overview]
Message-ID: <20021101120618.GJ8428@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0211010537410.917-100000@dad.molina>

On Fri, Nov 01 2002, Thomas Molina wrote:
> I have been building my system to use ide-scsi for ages now because of 
> reqiurements for cdrecord.  With the announced intention to get rid of 
> ide-scsi in 2.5.44 I have started trying ide-cd with no success.  I 
> previously reported this problem for 2.5.44 and 2.5.45 continues the 
> issue.  My system is based on RedHat 7.3, with an A7V133 motherboard and 
> an Athlon 1.3GHz processor.  
> 
> Building ide-cd monolithic (or modular and attempting a modprobe) gives me 
> endless streams of the following error messages (hand-copied from 
> console):
> 
> hdc: irq timeout: status=0x90 {Busy}
> hdc: irq timeout: error=0x01IllegalLengthIndication
> hdc: drive not ready for command
> hdc: ATAPI reset timed-out, status=0x80
> ide1: reset: success

Interesting. Please send me a detailed list of your hardware, boot
messages should suffice. Does 2.5.43 work correctly?

-- 
Jens Axboe


  reply	other threads:[~2002-11-01 12:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01 11:55 ide-cd still borken for me in 2.5.45 Thomas Molina
2002-11-01 12:06 ` Jens Axboe [this message]
2002-11-01 13:09   ` Thomas Molina
2002-11-02  1:49   ` Thomas Molina
2002-11-02  2:24     ` Thomas Molina
2002-11-02  9:18       ` Jens Axboe
2002-11-02 14:48         ` Thomas Molina
2002-11-02 14:54           ` Jens Axboe
2002-11-02 15:43             ` Jens Axboe
2002-11-02 18:39               ` Thomas Molina

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=20021101120618.GJ8428@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmolina@cox.net \
    /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