From: Burkhard K. <bu...@bu...> - 2000-09-28 23:37:22
|
DG > >BTW, there is still another problem with the kernel drivers which causes > >more-or-less random lockups of the client process, for example, when doing > >a large scan. If you're able to do anything about that or even just have > >any ideas on what could be causing it, it would be much appreciated too. > :-) > > I've spent a little time reaquainting myself with the code, and I think I > can take a shot at this. Fortunately (maybe), it hangs reliably with > debugging turned on, suggesting a timing issue (interrupt scheduling > conflicts maybe?). Are we talking about the driver compiled under 2.2 or 2.4? I know we have a timing issue under 2.4 and I hope it is related to changes in the underlying parport layer. Under 2.4 the driver becomes somehow sluggish without debugging turned on (sic!) - which means that the overall reaction becomes faster if some loops slow down. -- Burkhard Kohl buk at/auf buks.ipn.de |