Hi,

Inspired by mails of another curent thread I looked at hdparm
and played around with the options.
To my great surprise a simple 'hdparm -d1 /dev/hda' freezes my
system completely. No keyboard, no mouse. No chance to get to a
second tty to kill or mend something. The only way to get out
was the Windows button aka reset switch.

Details:

-----------------------------------------------------

[root@molch wobo]# hdparm -i /dev/hda

/dev/hda:

 Model=ST320430A, FwRev=3.11, SerialNo=7BX09MRL
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs
RotSpdTol>.5% }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=0(?), BuffSize=512kB, MaxMultSect=16, MultSect=off
 DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=2(fast)
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes,
LBAsects=40079088
 WARNING 23565024 ORPHANED SECTORS :: KERNEL REPORTING ERROR
 tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2 
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3
mode4 
 UDMA modes: mode0 mode1 mode2 mode3 *mode4 
 Drive Supports : ATA-1 ATA-2 ATA-3 ATA-4 
------------------------------------------------------

[root@molch wobo]# hdparm /dev/hda

/dev/hda:
 multcount    =  0 (off)
 I/O support  =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  0 (off)
 keepsettings =  0 (off)
 nowerr       =  0 (off)
 readonly     =  0 (off)
 readahead    =  8 (on)
 geometry     = 2494/255/63, sectors = 40079088, start = 0
------------------------------------------------------

[root@molch wobo]# hdparm -Tt /dev/hda

/dev/hda:
 Timing buffer-cache reads:   128 MB in  2.31 seconds =55.41
MB/sec
 Timing buffered disk reads:  64 MB in 11.08 seconds = 5.78
MB/sec
------------------------------------------------------

'hdparm -c3 /dev/hda' activates 32-bit and makes no problems. It
takes the 'timing buffered disk reads' to 6.2x.

'hdparm -d1' generates the proper output that dma-access is now
activated for hda. As soon as the hd is accessed the whole
system freezes with the red hd-light on.

Any ideas? As for the values of the hd one should assume it
should work with dma-access.

wobo
-- 
GPG-Fingerprint: FE5A 0891 7027 8D1B 4E3F  73C1 AD9B D732 A698 82EE
For Public Key mailto [EMAIL PROTECTED] with Subject: GPG-Request
-------------------------------------------------------------------
ISDN4LINUX-FAQ -- Deutsch: http://www.wolf-b.de/i4l/i4lfaq-de.html

Reply via email to