All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: linux-kernel@vger.kernel.org
Subject: Problem with IDE harddrive and ATA FLASH on the same IDE channel
Date: Thu, 10 Jan 2002 13:04:40 -0600	[thread overview]
Message-ID: <3C3DE5C8.7060504@acm.org> (raw)

I am working on a board that has both an IDE drive and an ATA flash on 
the same IDE channel.  If I use them independently, they work fine.  If 
I try to use them together (say, copy files from one to the other) I get 
lost interrupts, spurrious interrupts, etc.  Can you have a HDD and 
FLASH on the same IDE channel?  This is on a Serverworks OSB4, I've 
tried various kernels.  One wierd thing, if I compile the Redhat 7.2 
kernel with Redhat's compile, it does seem to work.  If I compile it 
with a 2.95.3 compiler (on SuSE) it doesn't work.  I've tried playing 
with timing, with and without DMA, etc.

Any ideas on this or how to debug this?

Thanks,

-Corey

heres the kernel output on the error:

hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
ide0: unexpected interrupt, status=0x58, count=1
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
ide0: reset: success
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
ide0: reset: success
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
end_request: I/O error, dev 03:41 (hdb), sector 32780
hdb: drive not ready for command
EXT2-fs error (device ide0(3,65)): ext2_write_inode: unable to read 
inode block
- inode=3945, block=16390
hdb: lost interrupt
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
ide0: unexpected interrupt, status=0x58, count=5
ide0: reset: master: error (0x80?); slave: failed
hda: status timeout: status=0x80 { Busy }
hda: drive not ready for command
ide0: reset: success
hdb: lost interrupt
hdb: lost interrupt
hdb: lost interrupt
hdb: lost interrupt
hdb: lost interrupt
hdb: lost interrupt
end_request: I/O error, dev 03:41 (hdb), sector 32780
hdb: drive not ready for command
EXT2-fs error (device ide0(3,65)): ext2_write_inode: unable to read 
inode block
- inode=3945, block=16390
hdb: lost interrupt
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
ide0: unexpected interrupt, status=0x58, count=5
ide0: reset: master: error (0x80?); slave: failed
hda: status timeout: status=0x80 { Busy }
hda: drive not ready for command
ide0: reset: success
hdb: lost interrupt
hdb: lost interrupt
hdb: lost interrupt
hdb: lost interrupt
hdb: lost interrupt
hdb: lost interrupt
hdb: lost interrupt
hdb: lost interrupt
hdb: lost interrupt


                 reply	other threads:[~2002-01-10 19:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3C3DE5C8.7060504@acm.org \
    --to=minyard@acm.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.