[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [buildd] traveling



Hi,

I'm trying to get washi running.

Do you still connect via evil? washi used to have a serial connection to
evil as well, we should be able to log in there.

Yes. I didn't know about the serial connection.

It may not be there anymore ... minicom tries to use ttyUSB0 without having the right permissions for it, maybe Mark used it for something else.

I'll poke around on evil if I can connect...

Thanks. It hasn't been terribly stable, but the buildd configuration
seems to be valid now.

That was another concern of mine - last thing I did was forwarding wanna-build queries to hobbes, but that's offline now, and even q650 hasn't come back up again.

Mark said that washi is up fine, but the network has a bunch of errors
and goes offline. I guess that's an argument for letting it buildd some
big packages next time it comes up.

PING washi (192.168.100.3) 56(84) bytes of data.
64 bytes from washi (192.168.100.3): icmp_seq=1 ttl=64 time=6.77 ms
64 bytes from washi (192.168.100.3): icmp_seq=2 ttl=64 time=0.000 ms
64 bytes from washi (192.168.100.3): icmp_seq=3 ttl=64 time=7.05 ms
64 bytes from washi (192.168.100.3): icmp_seq=4 ttl=64 time=4.48 ms
64 bytes from washi (192.168.100.3): icmp_seq=5 ttl=64 time=6.98 ms
64 bytes from washi (192.168.100.3): icmp_seq=6 ttl=64 time=3.70 ms
64 bytes from washi (192.168.100.3): icmp_seq=7 ttl=64 time=2071992 ms
wrong data byte #29 should be 0x1d but was 0x1f
#8 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1f 1e 1f 20 21 22 23 24 25 26 27
#40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37
64 bytes from washi (192.168.100.3): icmp_seq=8 ttl=64 time=2071990 ms
64 bytes from washi (192.168.100.3): icmp_seq=9 ttl=64 time=2.84 ms
64 bytes from washi (192.168.100.3): icmp_seq=10 ttl=64 time=0.000 ms
64 bytes from washi (192.168.100.3): icmp_seq=11 ttl=64 time=2.70 ms
64 bytes from washi (192.168.100.3): icmp_seq=12 ttl=64 time=5.89 ms
64 bytes from washi (192.168.100.3): icmp_seq=15 ttl=64 time=3.33 ms
64 bytes from washi (192.168.100.3): icmp_seq=14 ttl=64 time=8.11 ms

The ping replies did look a tad strange, yep.

Getting that driver fixed would probably be a good thing. :)

First thing it's ever done that. Maybe Mark has a new network card in the PC that corrupts packets ... or maybe the NE2000 is on its way out.

Maybe he needs to reduce the processor speed or the interrupt timer frequency for the card (though I never saw such behavior when testing the driver).

	Michael



Reply to: