Another test. Different approach, different behavior. To try and support my thesis about "starvation", I ran the test on vmware and left the computer, while usually I used to use it regurarly while running the test, so this time teorically all CPU would have been reserved to Haiku, and thus the low memory thread should have been able to free the vnode in 10 seconds. The test this time in fact, last 3 hours before crashing (nice nap by the way :-) ), with the same error, but the output of tar was quite different. See screenshot attached. Any comments? Anyway, I wanted to test with condition variable, but I'm not sure on how to proceed, despite of that though, I think we should hanle the error E_BUSY differently, because 10 seconds with our current scheduler, and with not I/O scheduler doesn't seem to be a good choice on slow system like running on vmware is. Anyway, is Marcus subscribed to this mailing list? What does he think about the possibility of being a scsi problem? Regards, -- Salvatore Benedetto (a.k.a. emitrax) Student of Computer Engineer University of Pisa www.haiku-os.it
Attachment:
crash1-bt.jpg
Description: JPEG image
