RE: [hpoj-devel] hpoj-0.6 feedback

[dgun <dg...@ww...>]

HP-Roseville,ex1 wrote:
 > Hi, Daniel.
 > 
 > > It always happens on large scans (> about 2MB)--every time.  
 > > I haven't checked
 > > to see if it always happens at the same byte number or not, 
 > > but it always occurs
 > > on a large scan.  Scanning small images (< about 2MB) seems 
 > > to work fine.  I
 > > haven't tried enough small scans in a row to see if it's only 
 > > a problem with
 > > large scans, or if it's a problem with total data transfer 
 > > since the module was
 > > loaded.
 > In the "large scan" cases where it breaks every time, it would still be
 > helpful for me to know what scan settings you use:
 > - preview or non-preview
 > - lineart, halftone, grayscale, or color
 > - resolution
 > - geometry settings (unless scanning the whole page)
 > If I know exactly what you do I might have a better chance of reproducing
 > the problem.  In some cases different values for the above options can
 > change the timing due to changing whether the scanner or the PC is the
 > bottleneck.

I use xscanimage and have everything set to "auto".  DPI is large enough to make
scan size > 2MB (maybe anywhere from 200-600).  It's frozen when scanning
lineart, color, preview and non-preview.  Previews are full page, and scans have
crashed on both full page and partial page.

 > 
 > > If I get the right debug incantations though, I can log 
 > > everything up to the
 > > point the module hangs and try to backtrack from there.  What 
 > > do you think would
 > > be the appropriate debug parameters so that I don't get too 
 > > much info, but still
 > > get enough?
 > When I turn on debug output for the kernel drivers I generally use
 > "debug=15" for ieee12844.o and/or "debug=1" for ieee12844pp.o".  I would say
 > start with only logging ieee12844.o, and then try logging both.  If you want
 > you could also try only logging ieee12844pp.o.  Note that the output will
 > appear on the console (which can't be redirected to a file), and it should
 > also show up in syslog (possibly /var/log/messages) if syslog is configured
 > correctly.

The log looks the same whether I do ieee12844.o debug=15 or ieee12844pp.o
debug=1.  Anyway, turning on debug causes it to crash repeatably every time! 
The output is very long, but here are the last lines before it freezes:

Sep 15 23:54:54 localhost kernel:
PAR_WAIT_SET_CLEAR(l=c6159160,set=0x0000,clear=0x0040): timed out waiting for
event=9! 
Sep 15 23:54:54 localhost kernel: mlcpp0: mlcpp_intr ERROR -110 
Sep 15 23:54:54 localhost kernel:   state=5 event=9 reset=7 recv=1 rcv=0 send=2 
Sep 15 23:54:54 localhost kernel: mlc: mlcpp0: link error -110 

Then when I kill the xscanimage process, I get a bunch more output with this at
the end:

Sep 15 22:39:16 localhost kernel:
PAR_WAIT_SET_CLEAR(l=c6045160,set=0x0098,clear=0x0040): timed out waiting for
event=23! 
Sep 15 22:39:16 localhost kernel: +mlcpp0: mlcpp_intr ERROR -110 
Sep 15 22:39:16 localhost kernel:   state=7 event=23 reset=7 recv=1 rcv=0 send=2 
Sep 15 22:39:16 localhost kernel: mlc: mlcpp0: link error -110 

Similar, but different.  At this point, the module is unloadable and if I start
another process that tries to access the PSC 500, the process immediately goes
into hardware blocking (D status).

I can send you the entire file (edited for clarity) if it will help you.  Time
permitting, I'll also see if I can figure anything out.

--
Daniel
dg...@xo...

______________________________________________________
Get your free web-based email at http://www.xoom.com
Birthday? Anniversary? Send FREE animated greeting
cards for any occasion at http://greetings.xoom.com