Http get commands return a bad results.

[Matthew Dillon]

:Hello,
:
:and good job, Matt.
:
:I report a problem that are caused yesterday cvsup, build and install.
:Following things are just facts on my current system because I can't understand at
:all why the problem occured. The new kernel has the problem that it's http get
:command like wget(1) or fetch(1) sometimes return a bad result.
:
:Bad result example(file was downloaded by a new kernel's wget(1)):
:$ gzip -cd gnotepad+-1.3.3.tar.gz | tar -xvf -

    Could you run an 'md5' checksum on the file when it is found to be
    bad verses when it is found to be good ?  And then put the good and
    the bad file up somewhere where I can fetch them so I can do a 
    byte-by-byte comparison.

    Also, in -CURRENT, try turning off sack and see if the problem still
    occurs.

    sysctl net.inet.tcp.sack=0

:Ah, by the way, I've remembered I had have following messages at log-in after yesterday
:installing.
:
:[diagnostic] cache_lock: blocked on 0xde0600b8 "getty"
:[diagnostic] cache_lock: unblocked getty
:[diagnostic] cache_lock: blocked on 0xde0600b8 "getty"
:[diagnostic] cache_lock: unblocked getty
:Regards.
:-- 
:H.Miyamoto (aka "Yuukis"). <Ys at xxxxxxxxxxxxxx>

    These are not related.

					-Matt
					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>