Http get commands return a bad results.

H.Miyamoto Ys at PixyGarden.net
Tue Nov 16 06:57:11 PST 2004


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.


Here's a old kernel uname output:
DragonFly humming.pixygarden.net 1.1-UNKNOWN DragonFly 1.1-UNKNOWN #0: Mon Oct 25 16:32:55 JST 2004 (snip)

And new kernel uname output:
DragonFly humming.pixygarden.net 1.1-CURRENT DragonFly 1.1-CURRENT #0: Mon Nov 15 19:28:28 JST 2004 (snip)

Bad result example(file was downloaded by a new kernel's wget(1)):
$ gzip -cd gnotepad+-1.3.3.tar.gz | tar -xvf -
gnotepad+-1.3.3/
gnotepad+-1.3.3/po/
gnotepad+-1.3.3/po/strings_glade.c
gnotepad+-1.3.3/po/ChangeLog
gnotepad+-1.3.3/po/Makefile.in.in
gnotepad+-1.3.3/po/POTFILES.in
gnotepad+-1.3.3/po/gnotepad+.pot
gnotepad+-1.3.3/po/stamp-cat-id
gnotepad+-1.3.3/po/da.po
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
gzip: invalid compressed data--crc error
gzip: gnotepad+-1.3.3.tar.gz: uncompress failed
tar: Error exit delayed from previous errors


This problem occured either a file on NFS or a file on direct attached scsi strage.
The old kernel's http get commands work fine and new kernel can uncompress a file that
was fetched by old kernel. New kernel's commands can work to a small size file. Addition,
new kernel's general commands like cp, mv and rm are working fine.
Well, I fully recognize that hints and informations too few so I hope to know what I
should tell, check and test.

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
[diagnostic] cache_lock: blocked on 0xde0600b8 "getty"
[diagnostic] cache_lock: unblocked getty
[diagnostic] cache_lock: blocked on 0xde0600b8 "getty"
[diagnostic] cache_lock: unblocked getty
[diagnostic] cache_lock: blocked on 0xde0600b8 "getty"
[diagnostic] cache_lock: unblocked getty

Are these messages relate to the problem?


Regards.
-- 
H.Miyamoto (aka "Yuukis"). <Ys at xxxxxxxxxxxxxx>
           http://wids.net/ - Enjoy Your Computing ?





More information about the Bugs mailing list