[3.3.0] Packet corruption

[Thomas Cort]

I'm getting corrupt packets when I try to rebuild the system over ssh.
Is anyone else experiencing this?

I installed Minix on VirtualBox 4.1.18 (debian wheezy) from the latest
dev snapshot ISO. I'm using the NAT port forwarding option in
VirtualBox for networking. In Minix, I installed git-base, clang,
binutils, and openssh. I set a root password, started sshd, ssh'd in
from the host OS, cloned the Minix mainline git repository, and ran
`make build`.

I kept getting disconnected during the build...

1st attempt:

all ===> tools
Bad packet length 1905149740.
Disconnecting: Packet corrupt

2nd attempt:

cleandir ===> lib/../minix/lib/libasyn
Corrupted MAC on input.
Disconnecting: Packet corrupt

Tried rebooting, 3rd attempt:

cleandir ===> lib/../minix/lib/libcompat_minix/include
Bad packet length 1823939731.
Disconnecting: Packet corrupt

4th attempt:

create liblua/ldump.d
Bad packet length 2667068010.
Disconnecting: Packet corrupt

There were no messages on the console, but /var/log/messages had logs like this:

sshd 4225 - - error: Received disconnect from 10.0.2.2: 2: Packet corrupt

If there is anything I can do to help narrow this down, like enabling
debug/verbose output somewhere, let me know.

Thomas

[Lionel Sambuc]

Hello tcort,


Good to hear from you!

Would it be possible for you to try using qemu, and/or while selecting another network card emulation under VirtualBox?

if it works then we should be able to assume this is a specific network driver issue. This would help reduce the scope to explore nicely.


Regards,

Lionel

> --
> You received this message because you are subscribed to the Google Groups "minix3" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to minix3+un...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Thomas Cort]

> Would it be possible for you to try using qemu

I tried kvm/qemu and I was able to rebuild the whole system over ssh
without any issues. It was emulating the rtl8139.

> selecting another network card emulation under VirtualBox?

I'll try this next and report back.

Thomas

[Thomas Cort]

> selecting another network card emulation under VirtualBox?

I tried selecting the "Intel PRO/1000 MT Server (82545EM)" driver in
virtual box and using the e1000 driver in Minix. It still gives me
issues...

Hunk #1 succeeded at 923.
Hmm...Corrupted MAC on input.
Disconnecting: Packet corrupt

usb.c:61:33: warning: passing 'const char [16]' to parameter
ofCorrupted MAC on input.
Disconnecting: Packet corrupt

compile cli/cmd_debug_test.o
Bad packet length 2162215020.
Disconnecting: Packet corrupt

[Ben Gras]

Update - could not reproduce this in vbox 4.3.10 on ubuntu. Completed a build (took 45 min) over ssh. With your selected Intel driver.

I could try rebuilding your vbox version from src.

[Thomas Cort]

> Update - could not reproduce this in vbox 4.3.10 on ubuntu

Thanks for looking into this. I'll try building and running vbox
4.3.10 to see if the problem persists. I report back with my findings.

> I could try rebuilding your vbox version from src.

According to dpkg, the version I have installed is 4.1.18-dfsg-2+deb7u3

[Ben Gras]

Perhaps you could make available your full VM config & image somewhere? If possible.

Just in case it's only triggered under certain conditions such as a certain memory size.

[Thomas Cort]

Hi Ben,

> Perhaps you could make available your full VM config & image somewhere?

Here's the config: http://tomcort.com/minix/Minix%203.3.0.vbox

The image is kind of big (over 400MB when compressed with xz), so
it'll take a while to upload. I'll upload it while I sleep and send
you a link tomorrow.

> Just in case it's only triggered under certain conditions such as a certain memory size.

During the setup, I mostly chose defaults. I set the disk size to 12
GB and RAM to 2 GB.

TC

[Ben Gras]

Perfect, thank you.

With your config (complete with port fwding indeed) and your disk image I could quickly start your VM in my vbox and try to reproduce the problem again. It's going now.

[Ben Gras]

With some patience (a lot of building) I could reproduce the problem.

I won't promise I can fix it before release as there are other problems that are higher on the [impact/time to fix] score chart, but this is a start, thank you.