[linux-dvb] arm crash by disk start

[Rainer Zocholl <UseNet-Posting-Nospam-74308-@zocki.toppoint.de>]

Hello

already posted that to the vdr list but it think this problem
is more driver related.

The questions are:
Can someone reproduce the effect?
Why&what is so sensible if the CPU is a little more busy in
an other driver? (I assume that the powered down disk
lets the IDE driver block)
Why does the DVB driver does not come back on its feet?
(A reboot is required)


Kernel 2.4.27 with VDR 1.3.17 (incl. thread patches)
3 FF DVB-S cards 2.1,2.1,1.3 with the 
newest(?) AV771x firmware (261d) Werner Fink announced.
1 bugdet DVB-T Avermedia 771
DVB: AV7111( ) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261d


----

powering down (sent to sleep) a harddisk leads very reproducible to non 
recoverable arm "cashes" when waken up.
Sending teh disk to "standby" does not show the effect so it's quite
sure that it not caused by the powersupply (anyway: 350W loaded with 100W...
totally 2 IDE disks Samsung 160GB + 60GB should not have such a problem)

To "crash" the arm I did something like:

#tail-f /var/log/yslog /var/loh/messages&
#
#umount /dev/hdc4
##sent to deep sleep
#hdparm -Y  /dev/hdc4
#
#sleep 5
#
##wake the disk
#hdparm -t  /dev/hdc4
## ^ this wakeup last serveral 10 seconds!
#mount /dev/hdc4 /mnt
#df /dev/hdc4
#


Generates this (stripped) tail output (messages did not have 
any other info than syslog)


/dev/hdc4:
 Timing buffered disk reads:
39:17 msi kernel: hdc: dma_timer_expiry: dma status == 0x61

==> /var/log/messages <==
39:17 msi kernel: hdc: dma_timer_expiry: dma status == 0x61

==> /var/log/syslog <==
39:27 msi kernel: hdc: error waiting for DMA
39:27 msi kernel: hdc: dma timeout retry: status=0xd0 { Busy }
39:27 msi kernel:
39:27 msi kernel: hdc: DMA disabled
39:27 msi kernel: ide1: reset: success

==> /var/log/syslog <==
39:50 msi kernel: av7110_fw_request: timeout waiting for COMMAND to complete
39:50 msi kernel: StopHWFilter error

==> /var/log/syslog <==
39:54 msi kernel: av7110_fw_request: timeout waiting for COMMAND to complete
39:54 msi kernel: StartHWFilter error
39:55 msi kernel: av71101: ARM crashed!

==> /var/log/syslog <==
39:55 msi kernel: av7110_fw_cmd error
39:55 msi kernel: av7110_fw_cmd error
39:56 msi kernel: StartHWFilter error


==> /var/log/syslog <==
40:01 msi /USR/SBIN/CRON[4905]: (root) CMD (if [ -x /usr/bin/mrtg ] && [ -r /etc/mrtg.cfg ]; then /usr/bin/m
rtg /etc/mrtg.cfg >> /var/log/mrtg/mrtg.log 2>&1; fi)
40:01 msi /USR/SBIN/CRON[4906]: (root) CMD (/usr/local/sbin/concheck > /tmp/cron.xxx 2&>1)
64 MB in 78.97 seconds =829.88 kB/sec
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hdc4             49604084  40843928   6240364  87% /mount
40:18 msi kernel: kjournald starting.  Commit interval 5 seconds
40:18 msi kernel: EXT3-fs warning: checktime reached, running e2fsck is recommended
40:18 msi kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,4), internal journal
40:18 msi kernel: EXT3-fs: mounted filesystem with ordered data mode.

vdr tries to restart without any success...


The disk is running in DMA. the 900kB/s sems to include the spinuptime.
A second test shows the usual 30MB/s.
But any way: No reason to die for the DVB driver IMHO.


Rainer