Re: PROBLEM: network interface regularly stops working

2007-07-03 Thread Kacper Bielecki
New kernel patch didn't solve my problem. 

I noticed also that number of packets dropped which is shown in ifconfig 
output increases always by 4294967295 no mather what time elapsed between two 
runs.
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: PROBLEM: network interface regularly stops working

2007-06-24 Thread Kacper Bielecki
It looks like the problem doesnt exist in the new ubuntu kernel version 
2.6.20-16.29. I have been testing it for few days and network works fine.

The problem still exists for the 2.6.22-rc4 patched version which I compiled 
before.

-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: PROBLEM: network interface regularly stops working

2007-06-07 Thread Kacper Bielecki
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.
[  326.605896] ACPI: PCI interrupt for device :01:00.0 disabled
[  334.383427] r8169 Gigabit Ethernet driver 2.2LK loaded
[  334.383549] ACPI: PCI Interrupt :01:00.0[A] - GSI 17 (level, low) - 
IRQ 17
[  334.383646] PCI: Setting latency timer of device :01:00.0 to 64
[  334.383889] PM: Adding info for No Bus:eth0
[  334.384761] eth0: RTL8168b/8111b at 0xc21e, 00:19:66:02:75:9f, 
IRQ 17
[  334.400904] r8169: eth0: link down
[  334.400915] r8169: eth0: link down
[  334.402389] ADDRCONF(NETDEV_UP): eth0: link is not ready
[  336.067849] r8169: eth0: link up
[  336.069313] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready 
[  254.015732] eth0: no IPv6 routers present
[ 1277.154147] PM: Removing info for No Bus:eth0
[ 1277.168553] ACPI: PCI interrupt for device :01:00.0 disabled
[ 1345.343644] r8169 Gigabit Ethernet driver 2.2LK loaded
[ 1345.343751] PCI: Enabling device :01:00.0 ( - 0003)
[ 1345.343759] ACPI: PCI Interrupt :01:00.0[A] - GSI 17 (level, low) - 
IRQ 17
[ 1345.343916] PCI: Setting latency timer of device :01:00.0 to 64
[ 1346.141898] PM: Adding info for No Bus:eth0
[ 1346.141991] eth0: RTL8100e at 0xc21e2000, ff:ff:ff:ff:ff:ff, IRQ 17
[ 1346.961209] r8169: eth1: link up
eth1  Link encap:Ethernet  HWaddr FF:FF:FF:FF:FF:FF  
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:60129542130 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
  Interrupt:17 Base address:0x2000 

eth1:avah Link encap:Ethernet  HWaddr FF:FF:FF:FF:FF:FF  
  inet addr:169.254.14.242  Bcast:169.254.255.255  Mask:255.255.0.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  Interrupt:17 Base address:0x2000 

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:13 errors:0 dropped:0 overruns:0 frame:0
  TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:1192 (1.1 KiB)  TX bytes:1192 (1.1 KiB)

   CPU0   CPU1   
  0: 139995  0   IO-APIC-edge  timer
  1:   1842  0   IO-APIC-edge  i8042
  7:  0  0   IO-APIC-edge  parport0
  8:  0  0   IO-APIC-edge  rtc
  9:  0  0   IO-APIC-fasteoi   acpi
 12:113  0   IO-APIC-edge  i8042
 14:  70624  0   IO-APIC-edge  libata
 15:  0  0   IO-APIC-edge  libata
 16:  0  0   IO-APIC-fasteoi   uhci_hcd:usb4
 17: 47  0   IO-APIC-fasteoi   eth0
 18:  0  0   IO-APIC-fasteoi   uhci_hcd:usb3
 19: 72  0   IO-APIC-fasteoi   uhci_hcd:usb2, libata
 23:   1063  0   IO-APIC-fasteoi   uhci_hcd:usb1, ehci_hcd:usb5, 
snd_ca0106
NMI:  0  0 
LOC: 139966 139944 
ERR:  0
procs ---memory-- ---swap-- -io -system-- cpu
 r  b   swpd   free   buff  cache   si   so  

Re: PROBLEM: network interface regularly stops working

2007-06-05 Thread Kacper Bielecki
 Can you try 2.6.22-rc3 (or -rc4) + patches ..0013 from
 http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.22-rc3/r8169-20070527

 Which motherboard is it ?

 Please Cc: netdev@vger.kernel.org

The motherboadr is ASRock ConRoe945G-DVI
I will get you know when I try new kernel.
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: PROBLEM: network interface regularly stops working

2007-06-05 Thread Kacper Bielecki

 Can you try 2.6.22-rc3 (or -rc4) + patches ..0013 from
 http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.22-rc3/r8169-20070527

After installing kernel 2.6.22-rc4 with patches 0001..0013 (there wasn't  
patch) the problem is not solved. I still get the same behaviour.


-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: PROBLEM: network interface regularly stops working

2007-06-05 Thread Francois Romieu
Kacper Bielecki [EMAIL PROTECTED] :
[...]
 The motherboadr is ASRock ConRoe945G-DVI

Same model as my current test machine.

It uses a boring el-cheapo PIV though.

 After installing kernel 2.6.22-rc4 with patches 0001..0013 (there wasn't  
 patch) the problem is not solved. I still get the same behaviour.

I did not look too closely at your report first, but:

 [   61.374301] fglrx: module license 'Proprietary. (C) 2002 - ATI 
 Technologies, Starnberg, GERMANY' taints kernel.
 [   61.375872] [fglrx] Maximum main memory to use for locked dma buffers: 921 
 MBytes.
 [   61.376132] [fglrx] module loaded - fglrx 8.37.6 [May 25 2007] on minor 0
 [   61.413699] ACPI: PCI Interrupt :03:00.0[A] - GSI 16 (level, low) - 
 IRQ 16
 [   63.283042] [fglrx] total  GART = 130023424
 [   63.283047] [fglrx] free   GART = 114032640
 [   63.283049] [fglrx] max single GART = 114032640
 [   63.283051] [fglrx] total  LFB  = 268304384
 [   63.283053] [fglrx] free   LFB  = 256765952
 [   63.283055] [fglrx] max single LFB  = 256765952
 [   63.283057] [fglrx] total  Inv  = 0
 [   63.283059] [fglrx] free   Inv  = 0
 [   63.283061] [fglrx] max single Inv  = 0
 [   63.283063] [fglrx] total  TIM  = 0

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.

 Restarting interface doesn't solve the problem.

Neither do an 'ifconfig down/rmmod/modprobe/ifconfig up' cycle ?

[...]
 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.

-- 
Ueimor
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html