linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* IDE, putting HD to sleep causes "lost interrupt"
@ 2002-07-31  7:57 Mukesh Rajan
  2002-07-31 12:18 ` Mark Lord
  2002-07-31 17:08 ` Andre Hedrick
  0 siblings, 2 replies; 5+ messages in thread
From: Mukesh Rajan @ 2002-07-31  7:57 UTC (permalink / raw)
  To: linux-kernel; +Cc: mlord

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: IDE, putting HD to sleep causes "lost interrupt"
  2002-07-31  7:57 IDE, putting HD to sleep causes "lost interrupt" Mukesh Rajan
@ 2002-07-31 12:18 ` Mark Lord
  2002-07-31 18:52   ` Bill Davidsen
  2002-07-31 17:08 ` Andre Hedrick
  1 sibling, 1 reply; 5+ messages in thread
From: Mark Lord @ 2002-07-31 12:18 UTC (permalink / raw)
  To: Mukesh Rajan; +Cc: linux-kernel

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: IDE, putting HD to sleep causes "lost interrupt"
  2002-07-31  7:57 IDE, putting HD to sleep causes "lost interrupt" Mukesh Rajan
  2002-07-31 12:18 ` Mark Lord
@ 2002-07-31 17:08 ` Andre Hedrick
  2002-08-01 19:49   ` Thunder from the hill
  1 sibling, 1 reply; 5+ messages in thread
From: Andre Hedrick @ 2002-07-31 17:08 UTC (permalink / raw)
  To: Mukesh Rajan; +Cc: linux-kernel, mlord

Because you need to call

hdparm -w /dev/hda		<--- Reset Device
hdparm -C /dev/hda		<--- query status, repeat until good.
hdparm -X** /dev/hda		<--- transfer rate mode set
hdparm -m** /dev/hda		<--- set multiple
hdparm -d* /dev/hda		<--- set DMA

You effectively kill (disable command mode) the drive has to be kick
started.

Cheers,

On Wed, 31 Jul 2002, 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
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Andre Hedrick
LAD Storage Consulting Group


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: IDE, putting HD to sleep causes "lost interrupt"
  2002-07-31 12:18 ` Mark Lord
@ 2002-07-31 18:52   ` Bill Davidsen
  0 siblings, 0 replies; 5+ messages in thread
From: Bill Davidsen @ 2002-07-31 18:52 UTC (permalink / raw)
  To: Mark Lord; +Cc: Mukesh Rajan, linux-kernel

On Wed, 31 Jul 2002, Mark Lord wrote:

> 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.

Would it be a reasonable thing to include the -Y information in the device
status so that the driver could know a reset was required? Since the
driver sends the command it has the chance to notice there, or might read
a status, or ??? Or is this undesirable for some other reason?

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: IDE, putting HD to sleep causes "lost interrupt"
  2002-07-31 17:08 ` Andre Hedrick
@ 2002-08-01 19:49   ` Thunder from the hill
  0 siblings, 0 replies; 5+ messages in thread
From: Thunder from the hill @ 2002-08-01 19:49 UTC (permalink / raw)
  To: Andre Hedrick; +Cc: Mukesh Rajan, linux-kernel, mlord

Hi,

On Wed, 31 Jul 2002, Andre Hedrick wrote:
> Because you need to call
> 
> hdparm -w /dev/hda		<--- Reset Device
> hdparm -C /dev/hda		<--- query status, repeat until good.
> hdparm -X** /dev/hda		<--- transfer rate mode set
> hdparm -m** /dev/hda		<--- set multiple
> hdparm -d* /dev/hda		<--- set DMA
> 
> You effectively kill (disable command mode) the drive has to be kick
> started.

Well, mind how horribly that sucks if your hdparm is on the disk you've 
sent to sleep. Thus, never send your disk containing /sbin to sleep...

			Thunder
-- 
.-../../-./..-/-..- .-./..-/.-.././.../.-.-.-


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2002-08-01 19:46 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-07-31  7:57 IDE, putting HD to sleep causes "lost interrupt" Mukesh Rajan
2002-07-31 12:18 ` Mark Lord
2002-07-31 18:52   ` Bill Davidsen
2002-07-31 17:08 ` Andre Hedrick
2002-08-01 19:49   ` Thunder from the hill

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).