Skip to contentSkip to conversation

hdparm -Y hangup

DISCUSSION Padraig Brady 3 participants 6 messages Sep 20, 2002 – Sep 25, 2002

lore
Share & tools
lore
#0 lore raw

This seems like a bug in the ide driver not issuing a reset?

On RH7.3 (2.4.18-3) if I do:

$ hdparm -Y /dev/hda
$ do stuff and disk spins up
$ hdparm -Y /dev/hda
$ everything hangs waiting for disk

cheers,
Pádraig.

Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev f9
PIIX4: chipset revision 2
PIIX4: not 100% native mode: will probe irqs later

    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio

hda: Maxtor 4D040H2, ATA DISK drive
hdc: SAMSUNG CD-ROM SC-148C, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
blk: queue c035e6a4, I/O limit 4095Mb (mask 0xffffffff)
hda: 78125000 sectors (40000 MB) w/2048KiB Cache, CHS=4863/255/63, UDMA(66) ide-floppy driver 0.99.newide
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 hda6 >

#1 lore raw
Quoted 7 lines

This seems like a bug in the ide driver not issuing a reset?

On RH7.3 (2.4.18-3) if I do:

$ hdparm -Y /dev/hda
$ do stuff and disk spins up
$ hdparm -Y /dev/hda
$ everything hangs waiting for disk

It *IS* a bug, but only Mark Lord, (the hdparm maintainer), and I seem to care about it - everybody else says, "just do hdparm -y instead", which is missing the point.

Incidently, I think you mean:

On RH7.3 (2.4.18-3) if I do:

$ hdparm -y /dev/hda
$ do stuff and disk spins up
$ hdparm -Y /dev/hda
$ everything hangs waiting for disk

with a lower case y for the first example.

So, unless you, I, or Mark Lord fixes it, it stays broken :-).

John.

#2 lore raw
Quoted 9 lines · [email protected] wrote:
Quoted 7 lines

This seems like a bug in the ide driver not issuing a reset?

On RH7.3 (2.4.18-3) if I do:

$ hdparm -Y /dev/hda
$ do stuff and disk spins up
$ hdparm -Y /dev/hda
$ everything hangs waiting for disk

It *IS* a bug, but only Mark Lord, (the hdparm maintainer), and I seem to care about it - everybody else says, "just do hdparm -y instead", which is missing the point.

Hrm, OK thanks for the info. Perhaps it should be removed from hdparm or a (DANGEROUS) put beside the description until it's fixed.

Quoted 10 lines

Incidently, I think you mean:

On RH7.3 (2.4.18-3) if I do:

$ hdparm -y /dev/hda
$ do stuff and disk spins up
$ hdparm -Y /dev/hda
$ everything hangs waiting for disk

with a lower case y for the first example.

No it seemed to wake up correctly the first time with -Y. As you say -y works always.

Quoted 1 line

So, unless you, I, or Mark Lord fixes it, it stays broken :-).

cheers,
Pádraig.

#3 lore raw
Quoted 3 lines

Hrm, OK thanks for the info. Perhaps it should be removed from hdparm or a (DANGEROUS) put beside the description until it's fixed.

The person to contact would be Mark Lord, the hdparm maintainer, (see the hdparm manual page for his E-Mail address).

Quoted 11 lines
Quoted 9 lines

Incidently, I think you mean:

On RH7.3 (2.4.18-3) if I do:

$ hdparm -y /dev/hda
$ do stuff and disk spins up
$ hdparm -Y /dev/hda
$ everything hangs waiting for disk

with a lower case y for the first example.

No it seemed to wake up correctly the first time with -Y.

That *is* strange.

Quoted 1 line

As you say -y works always.

On the systems I have tried it, yes - I'm not saying it always works.

John.

#4 lore raw
Quoted 5 lines · On Mon, 23 Sep 2002 [email protected] wrote:
Quoted 3 lines

Hrm, OK thanks for the info. Perhaps it should be removed from hdparm or a (DANGEROUS) put beside the description until it's fixed.

The person to contact would be Mark Lord, the hdparm maintainer, (see the hdparm manual page for his E-Mail address).

Rather than have Mark Lord set the option DANGEROUS (it shouldn't be) perhaps it could be made to work more than once... Odd problem, is something not getting set or cleared when the drive is spun up the first time?

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#5 lore raw
Quoted 11 lines
Quoted 6 lines
Quoted 3 lines

Hrm, OK thanks for the info. Perhaps it should be removed from hdparm or a (DANGEROUS) put beside the description until it's fixed.

The person to contact would be Mark Lord, the hdparm maintainer, (see the hdparm manual page for his E-Mail address).

Rather than have Mark Lord set the option DANGEROUS (it shouldn't be) perhaps it could be made to work more than once... Odd problem, is something not getting set or cleared when the drive is spun up the first time?

With my Maxtor disk connected to a PIIX3 IDE interface and stock kernel 2.4.19, I get this behavior:

# hdparm -Y /dev/hda

Disk sleeps

# find

No disk activity - it doesn't wake up. It doesn't work once for me, it always hangs on the first attempt.

So, I try dmesg on another console - no new output.

# hdparm -w /dev/hda

Performs a device reset, and the disk spins up.

# dmesg

hda: ide_set_handler: handler not null; c0181050
hda: dma_intr: status=0xd0 { Busy }
hda: DMA disabled
hda: ide_set_handler: handler not null; old=c0181050, new=c017b160
bug: kernel timer added twice at c017afe1.
hda: ide_set_handler: handler not null; old=c017b160, new=c017b160
ide0: reset: success

Obviously, if you're going to try to repeat this, sync the disk beforehand, because I assume that a device reset will loose data in the disk's write cache.

John.