All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerald Britton <gbritton@mit.edu>
To: Ishan Oshadi Jayawardena <ioshadi@sltnet.lk>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: IDE-DMA woes
Date: Fri, 7 Dec 2001 11:31:10 -0500	[thread overview]
Message-ID: <20011207113110.A3673@light-brigade.mit.edu> (raw)
In-Reply-To: <3C115106.BED6616D@sltnet.lk>
In-Reply-To: <3C115106.BED6616D@sltnet.lk>; from ioshadi@sltnet.lk on Fri, Dec 07, 2001 at 05:30:14PM -0600

On Fri, Dec 07, 2001 at 05:30:14PM -0600, Ishan Oshadi Jayawardena wrote:
> Greetings.
> 	I run Linux on an IBM PC300GL with Intel's
> 82371AB PIIX4 chipset. With DMA enabled (by doing a
> hdparm -d1 /dev/hda) on the hdd, I
> _sometimes_ get the following message from the kernel
> after resuming from APM standby mode:

I have very similar behavior on an IBM Thinkpad T23.  It's got this IDE
controller:

00:1f.1 IDE interface: Intel Corporation: Unknown device 248a (rev 01)
        Subsystem: IBM: Unknown device 0220

And, I also only sometimes get roughly:

ide_dmaproc: chipset supported ide_dma_lostirq func only: 13
hda: lost interrupt
ide_dmaproc: chipset supported ide_dma_timeout func only: 14

> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hda: status error: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hda: status error: error=0x84 { DriveStatusError BadCRC }
> hda: drive not ready for command
> 
> then the drive stalls for a few seconds, and the driver
> disables DMA. This behaviour doesn't seem to depend on the
> kernel version (current: 2.4.14; error seen with 2.2 series also.)
> The weird thing is that this is not reliably reproducable; most of
> the time the system goes to apm standby (not suspend) and resumes fine.

Unfortunately, when mine hits this condition, it seems to never recover
from it.  It also seems to only happen sometimes and I've been unable to
reliably reproduce the problem.  I told Andre about the problem and he
suggested doing a "hdparm -d0 -X08 /dev/hda" prior to suspend and that
seems to work around the problem.  I "hdparm -d1 -X69 /dev/hda" on resume
to get it back to speedy udma5 mode.  I think the problem is the BIOS doing
things to the IDE chipset during the suspend, and the driver not properly
correcting the changes on resume.

				-- Gerald


  reply	other threads:[~2001-12-07 16:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 23:30 IDE-DMA woes Ishan Oshadi Jayawardena
2001-12-07 16:31 ` Gerald Britton [this message]
2001-12-08 19:47   ` Ishan Oshadi Jayawardena
2001-12-08 21:09   ` Andre Hedrick
2001-12-08 21:56     ` Jacob Luna Lundberg
2001-12-08 22:11       ` François Cami
2001-12-08 22:25         ` J Sloan
2001-12-09  1:08           ` Simon Turvey
2001-12-10  8:31             ` Andre Hedrick
     [not found] <Pine.LNX.4.33.0112071247050.6985-100000@coffee.psychology.mcmaster.ca>
2001-12-08 19:47 ` Ishan Oshadi Jayawardena

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=20011207113110.A3673@light-brigade.mit.edu \
    --to=gbritton@mit.edu \
    --cc=ioshadi@sltnet.lk \
    --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.