linux-kernel - Mass udp flow reboot linux with RealTek RTL-8169 Gigabit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTin7GBSTcfZgr_9sNZ8CPMkW7Vstni+fs2v1-ink@mail.gmail.com>
Date:	Sun, 13 Feb 2011 02:35:44 +0100
From:	Seblu <seblu@...lu.net>
To:	lkml <linux-kernel@...r.kernel.org>
Subject: Mass udp flow reboot linux with RealTek RTL-8169 Gigabit

Hi,

Some days ago, one of my computer poweroff without any warning during
a long rsync. Every time i run this long rsync, my computer power off
after a random time.
Firstly i suspected a  heat stroke. But it resisted all my heat tests
(cpuburn,ffmpeg,etc).
Secondly i suposed a power issue. But after some tests, it does not
seem to be kind of problem.
Thirdly, i trying to load disk by a lot of read. But system is stable.

Which is not practical, is that there is no message or trace in logs
file. And why power off? BIOS is configured to restart after a
powerloss.

So, maybe a network issue? From one another 1Gbit/s wired linux
computer i tryed an udp iperf at full speed (got ~950mbps) and after
some time, host reboot. o0
I tryed again, and host reboot again. I tryed with "ping -s 65000 -f"
and my host reboot again. I've tryed this with a 2.6.32 (debian
squeeze) and a 2.6.37 (debian experimental) kernel, in both case
host reboot.

This doesn't explain why my host power off when rsync, but it seems to
have a big issue with kernel driver r8169.

After starting my flood ping or udp iperf, dmesg show a lot of line:
[  254.896055] r8169 0000:04:00.0: eth0: link up
[  254.919976] r8169 0000:04:00.0: eth0: link up
[  254.943916] r8169 0000:04:00.0: eth0: link up
[  254.983784] r8169 0000:04:00.0: eth0: link up
[  255.007710] r8169 0000:04:00.0: eth0: link up
[  255.031657] r8169 0000:04:00.0: eth0: link up
[  255.103444] r8169 0000:04:00.0: eth0: link up

Reboot is curious because it doesnt look like a kernel panic and print
there is no kernel trace.

My OS is a debian squeeze amd64. My hardware is a intel core i3 +
gigabyte H55N-UBS3 with 4G DDR3.

Do you need more trace / test? Do you think power off and reboot is linked?

Regards,

-- 
Sébastien Luttringer
www.seblu.net

Download attachment "kern.log.xz" of type "application/x-xz" (39104 bytes)