sane-project-website/old-archive/1998-05/0140.html

116 wiersze
5.1 KiB
HTML

<!-- received="Tue May 12 10:58:33 1998 PDT" -->
<!-- sent="Tue, 12 May 1998 19:54:39 +0200 (MET DST)" -->
<!-- name="becka@rz.uni-duesseldorf.de" -->
<!-- email="becka@rz.uni-duesseldorf.de" -->
<!-- subject="Re: whole system locked" -->
<!-- id="m0yZJGB-0000YyC@charon.beck-sw.de" -->
<!-- inreplyto="35586653.7C21D5B2@t-online.de" -->
<title>sane-devel: Re: whole system locked</title>
<h1>Re: whole system locked</h1>
<a href="mailto:becka@rz.uni-duesseldorf.de"><i>becka@rz.uni-duesseldorf.de</i></a><br>
<i>Tue, 12 May 1998 19:54:39 +0200 (MET DST)</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#140">[ date ]</a><a href="index.html#140">[ thread ]</a><a href="subject.html#140">[ subject ]</a><a href="author.html#140">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0141.html">Yuri Dario: "Re: Win32 TWAIN DLL to interface with SANE"</a>
<li> <b>Previous message:</b> <a href="0139.html">Jim Ford: "Re: [umax] Can't use 10-bit scan: "preview cannot handle depth 16""</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Hi !<br>
<p>
<i>&gt; I recently encountered real problems out of nowhere: </i><br>
<i>&gt; the xscanimage-preview crashed the whole system.</i><br>
<i>&gt; </i><br>
<i>&gt; to start from the beginning:</i><br>
<i>&gt; </i><br>
<i>&gt; hardware: Mustek Paragon 1200SP (firmware 1.02)</i><br>
<i>&gt; connected to Tekram DC390 which also runs </i><br>
<i>&gt; IBM SCSI-Harddisk</i><br>
<p>
I am having similar problems with an IDE System with an<br>
MP 12000SP (FW 1.00) connected to the NCR 53c400 SCSI card that came<br>
with it.<br>
<p>
<i>&gt; I put the system from IDE-disk to SCSI some time ago. For some time</i><br>
<i>&gt; everything worked perfect, when suddenly, exactly at the end of a</i><br>
<i>&gt; preview-scan the whole system froze completely (don't laugh at me).</i><br>
<i>&gt; No keybord working.</i><br>
<p>
I have a similar effect sometimes that can cause either the whole system<br>
locking up or the SCSI subsystem going mad in a way that can only be cured <br>
by a reboot.<br>
rmmod, power-cycle scanner, insmod does _not_ help.<br>
<p>
<i>&gt; I had to reset and repair a more or less corrupt filesystem :-(</i><br>
<i>&gt; It happend some more times, but only EXACTLY at the end of previewing,</i><br>
<i>&gt; the normal scanning was fine. </i><br>
<p>
I have seen similar effects. They seem to be connected to the exact amount<br>
of data/the number of lines that have to be transferred.<br>
<p>
I can reproduce the hangup by giving specific parameter sets to the scanner.<br>
<p>
<i>&gt; With option strip-height (1 or 2) enabled previewing works mostly correct, </i><br>
<i>&gt; only one crash since. </i><br>
<p>
At previewing ?<br>
<p>
If you have the same problem that I have, I assume it would be very likely<br>
that it now happened at scan time, because the strip-height option<br>
causes the "breaks" in the transfer at other places, thus changing the<br>
size of the last strip - what seems to be the cause of the problem -<br>
should either always or never affect previewing - right ?<br>
<p>
<i>&gt; smaller strip-heights seem safer and color preview very unsafe </i><br>
<i>&gt; (more data coming?)</i><br>
<p>
Hmm - sounds somewhat familiar. Color mode significantly increased the<br>
probability for hangs here, too.<br>
<p>
<i>&gt; I have no real idea what is going on, to me it seems some kind of</i><br>
<i>&gt; timing problem? </i><br>
<p>
Hmm - My guess was rather a rounding error in number-of-lines calculations,<br>
because at the parameter sets where I could reproduce the hang, I usually<br>
had calculated "fractional part" of the last line number to be near 0.5.<br>
<p>
Could you check further using scanimage, checking, if hangups at given <br>
parameter sets are reproducible and record those parameter sets, so I can cross<br>
check them ?<br>
<p>
If you like, you could also already check my theory by calculating the total<br>
number of requested lines which is simply the product of the scan length in<br>
inch and the resolution.<br>
<p>
<i>&gt; The system tries to write preview-data to disk while the scanner still </i><br>
<i>&gt; locks the SCSI-bus? </i><br>
<p>
I don't think preview data gets written to SCSI. It should end up in RAM - <br>
right ? It should only go to disk via swapping. Is that likely to occur for<br>
your system ?<br>
<p>
CU,Andy<br>
<p>
<pre>
--
= Andreas Beck | Email : &lt;<a href="mailto:andreas.beck@ggi-project.org">andreas.beck@ggi-project.org</a>&gt; =
<p>
<p>
<pre>
--
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0141.html">Yuri Dario: "Re: Win32 TWAIN DLL to interface with SANE"</a>
<li> <b>Previous message:</b> <a href="0139.html">Jim Ford: "Re: [umax] Can't use 10-bit scan: "preview cannot handle depth 16""</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>