Very Computer

recently busy with taper 6.8.2 and it stopped with the verify action :
kernel v2.0.30. no other related msgs found.

/var/log/messages reported over and over again (and again and...)

Aug 28 16:49:25 grobbebol kernel: [026]     fdc-io.c (fdc_interrupt_wait) -
*** BUG: unexpected schedule exit ***.
Aug 28 16:49:25 grobbebol kernel: [026]     fdc-io.c (fdc_interrupt_wait) -
*** BUG: unexpected schedule exit ***.

which probably triggers :

Aug 28 16:49:25 grobbebol kernel: [027]    ftape-rw.c (wait_segment) -
fdc_interrupt_wait failed.
Aug 28 16:49:25 grobbebol kernel: [027]    ftape-rw.c (wait_segment) -
fdc_interrupt_wait failed.
Aug 28 16:49:25 grobbebol kernel: [028]   ftape-read.c (read_segment) -
wait_segment failed while reading.
Aug 28 16:49:25 grobbebol kernel: [028]   ftape-read.c (read_segment) -
wait_segment failed while reading.
Aug 28 16:49:25 grobbebol kernel: [029]        ftape-io.c
(ftape_report_operation) - No acknowledge after 302 msec. (95 iter).
Aug 28 16:49:25 grobbebol kernel: [029]        ftape-io.c
(ftape_report_operation) - No acknowledge after 302 msec. (95 iter).
Aug 28 16:49:25 grobbebol kernel: [030]        ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
Aug 28 16:49:25 grobbebol kernel: [030]        ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
Aug 28 16:49:26 grobbebol kernel: [031]        ftape-io.c
(ftape_report_operation) - No acknowledge after 302 msec. (95 iter).
Aug 28 16:49:26 grobbebol kernel: [031]        ftape-io.c
(ftape_report_operation) - No acknowledge after 302 msec. (95 iter).
Aug 28 16:49:26 grobbebol kernel: [032]        ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
Aug 28 16:49:26 grobbebol kernel: [032]        ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.

--
Grobbebol's Home                 |      Don't give in to spammers.
http://www.xs4all.nl/~bengel     |     Use your real e-mail address
Linux 2.0.30 on an i586/64 MB    |             on Usenet.