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-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 7 Jun 2007 12:12:54 +0200
From:	Kacper Bielecki <kazjote@...d.ics.p.lodz.pl>
To:	Francois Romieu <romieu@...zoreil.com>
Cc:	netdev@...r.kernel.org
Subject: Re: PROBLEM: network interface regularly stops working

First of all I managed to reproduce this bug with Gentoo LiveCD 2007.0 amd64 
so now Im sure it is not Ubuntu specific. 2007.0 comes with kernel 
2.6.19-gentoo-...

On Tuesday 05 of June 2007 22:37:09 you wrote:
> Can you reproduce the problem if this module is not loaded at all ?
>
> Please understand "loaded" as "it's loaded but it is not used" as well
> as "it was loaded but I unloaded it before testing".

Fglrx was not loaded just because it fails to build with 2.6.22-r4 patched 
kernel. What I noticed is that when the interface fails during the system 
startup, xorg wont start complaining about fglrx. If networking is working 
xorg will simply load xorg (ati) module. 

>
> > Restarting interface doesn't solve the problem.
>
> Neither do an 'ifconfig down/rmmod/modprobe/ifconfig up' cycle ?
>
When I do this cycle before the network fail I get normally eth0 interface 
working with the dmesg output shown in dmesg_cycle_good attached file.

After the fail eth0 will not start anymore, instead eth1 will start with the 
huge number of dropped packets. Dmesg output from this operation is in 
attachmet named modprobe_dmesg. Ifconfig status after operation is in 
ifconfig_after_dmesg.

To generate this files I used dmesg | tail command so it is not full output.
>
> > I don't know what else can help so I attach some information about
> > system.
>
> A 'cat /proc/interrupts', a few seconds of 'vmstat 1' a
> 'for i in $(seq 1 5); do ethtool -S eth0; sleep 1; done' after the watchdog
> event and a good bunch of patience.

I attach interrupts and vmstat. ethtool -S eth0 won't generate any output 
after network fail. It freezes and can be exited with CTRL+C. I attach also 
normal output from your script  before the fail in ethtool_good file.

View attachment "dmesg_cycle_good" of type "text/plain" (651 bytes)

View attachment "modprobe_dmesg" of type "text/plain" (601 bytes)

View attachment "ifconfig_after_dmesg" of type "text/plain" (1026 bytes)

View attachment "interrupts" of type "text/plain" (863 bytes)

View attachment "vmstat" of type "text/plain" (1498 bytes)

View attachment "ethtool_good" of type "text/plain" (1456 bytes)

Powered by blists - more mailing lists