From: Mark Lord <mlord@pobox.com>
To: Mukesh Rajan <mrajan@ics.uci.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE, putting HD to sleep causes "lost interrupt"
Date: Wed, 31 Jul 2002 08:18:35 -0400 [thread overview]
Message-ID: <3D47D59B.6B8CFED7@pobox.com> (raw)
In-Reply-To: <Pine.SOL.4.20.0207310013490.15380-100000@hobbit.ics.uci.edu>
Well, the answer is very simple, then: DON'T DO THAT.
When an ATA (IDE) drive is put to sleep (-Y),
it *requires* a reset to revive it for any future commands.
The IDE driver doesn't know about the -Y, so it just attempts
I/O a few times before digging out the BIG hammer and doing a reset.
All is well.
--
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com
Mukesh Rajan wrote:
>
> hi,
>
> things work perfectly fine on my desktop. but on my laptop (toshiba
> satellite) if i try,
>
> %hdparm -Y /dev/hda <--- put to sleep followed by
> %hdparm -C /dev/hda <--- query status
>
> gives me
>
> hda: lost interrupt
> hda: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hda: irq timeout: status=0x50 { DriveReady SeekComplete }
> hda: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hda: irq timeout: status=0x50 { DriveReady SeekComplete }
> hda: lost interrupt
> hda: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hda: irq timeout: status=0x50 { DriveReady SeekComplete }
> hda: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hda: irq timeout: status=0x50 { DriveReady SeekComplete }
> hda: DMA disabled
> ide0: reset: success
>
> if i try the above from X, the machine freezes and i need to do hard
> reboot.
>
> the boot message regarding ide are as follows
>
> boot messages
> -------------
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> ALI15X3: IDE controller on PCI bus 00 dev 20
> PCI: No IRQ known for interrupt pin A of device 00:04.0. Please try using
> pci=biosirq.
> ALI15X3: chipset revision 195
> ALI15X3: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xeff0-0xeff7, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xeff8-0xefff, BIOS settings: hdc:DMA, hdd:pio
> hda: TOSHIBA MK2018GAP, ATA DISK drive
>
> the closest i think i got to on google is the following but there are no
> answers
>
> http://mail.nl.linux.org/kernelnewbies/2001-01/msg00064.html
>
> please help.
>
> - mukesh
next prev parent reply other threads:[~2002-07-31 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 7:57 Mukesh Rajan
2002-07-31 12:18 ` Mark Lord [this message]
2002-07-31 18:52 ` Bill Davidsen
2002-07-31 17:08 ` Andre Hedrick
2002-08-01 19:49 ` Thunder from the hill
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=3D47D59B.6B8CFED7@pobox.com \
--to=mlord@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrajan@ics.uci.edu \
/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
all inboxes | Powered by JetHome®