Bug#526983: linux-image-2.6.29-1-amd64: NETDEV WATCHDOG: eth0 (r8169): transmit timed out

2010-08-09 Thread Carlos Fonseca

On Mon, 15 Feb 2010, Moritz Muehlenhoff wrote:


Please report this upstream at http://bugzilla.kernel.org (Product:
Drivers, Component: Network) and send us the bug number.


I have just added some additional info to

http://bugzilla.kernel.org/show_bug.cgi?id=14962

which seems to be the same bug (it refers to debian bug 528362, which has 
been merged with this one). Basically, the problem is still present in 
2.6.35-1~experimental.1.


Sorry to have gone silent...

Regards,

Carlos




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.lnx.4.64.1008091910510.2...@darwin.csi.fct.ualg.pt



Bug#526983: linux-image-2.6.29-1-amd64: NETDEV WATCHDOG: eth0 (r8169): transmit timed out

2010-02-14 Thread Moritz Muehlenhoff
On Sat, Jan 23, 2010 at 05:16:49PM +, Carlos Fonseca wrote:
 On Mon, 18 Jan 2010, Carlos Fonseca wrote:
 
 I have just installed linux-image-2.6.32-trunk-amd64_2.6.32-5, and
 will try to reproduce it with that kernel, as well.
 
 Here it goes.

Please report this upstream at http://bugzilla.kernel.org (Product:
Drivers, Component: Network) and send us the bug number.

Cheers,
Moritz



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100215005315.ga14...@galadriel.inutil.org



Bug#526983: linux-image-2.6.29-1-amd64: NETDEV WATCHDOG: eth0 (r8169): transmit timed out

2010-01-23 Thread Carlos Fonseca

On Mon, 18 Jan 2010, Carlos Fonseca wrote:

I have just installed linux-image-2.6.32-trunk-amd64_2.6.32-5, and will 
try to reproduce it with that kernel, as well.


Here it goes.

Carlos


[  588.804125] [ cut here ]
[  588.804141] WARNING: at 
/build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/net/sched/sch_generic.c:261
 dev_watchdog+0xe2/0x194()
[  588.804148] Hardware name: Satellite A110
[  588.804153] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
[  588.804157] Modules linked in: i915 drm_kms_helper drm i2c_algo_bit bridge 
stp bnep sco rfcomm l2cap crc16 bluetooth xt_multiport xt_state autofs4 
cpufreq_stats cpufreq_userspace cpufreq_powersave cpufreq_conservative ipt_LOG 
iptable_mangle iptable_filter iptable_nat ip_tables nf_nat x_tables 
nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 fuse pcspkr coretemp acpi_cpufreq 
firewire_sbp2 loop snd_hda_codec_realtek snd_hda_intel snd_hda_codec arc4 
snd_hwdep ecb snd_pcm_oss snd_mixer_oss snd_pcm joydev snd_seq_midi snd_rawmidi 
pcmcia snd_seq_midi_event battery container ac snd_seq snd_timer snd_seq_device 
video output iwl3945 iwlcore snd yenta_socket rsrc_nonstatic mac80211 
pcmcia_core i2c_i801 psmouse soundcore rng_core cfg80211 serio_raw evdev 
processor button i2c_core snd_page_alloc intel_agp rfkill agpgart ext3 jbd 
mbcache dm_mirror dm_region_hash dm_log dm_snapshot dm_mod sg sr_mod cdrom 
sd_mod crc_t10dif ide_pci_generic ide_core ata_piix ata_generic sdhci_pci sdhci 
firewire_ohci firewire_core crc_itu_t mmc_core led_class libata scsi_mod r8169 
mii uhci_hcd thermal fan thermal_sys ehci_hcd usbcore nls_base [last unloaded: 
scsi_wait_scan]
[  588.804341] Pid: 0, comm: swapper Not tainted 2.6.32-trunk-amd64 #1
[  588.804345] Call Trace:
[  588.804349]  IRQ  [8124] ? dev_watchdog+0xe2/0x194
[  588.804361]  [8124] ? dev_watchdog+0xe2/0x194
[  588.804369]  [8104dc34] ? warn_slowpath_common+0x77/0xa3
[  588.804375]  [8124ee0c] ? dev_watchdog+0x0/0x194
[  588.804382]  [8104dcbc] ? warn_slowpath_fmt+0x51/0x59
[  588.804390]  [81041bed] ? enqueue_task_fair+0x24/0x69
[  588.804398]  [8103a5fb] ? activate_task+0x20/0x26
[  588.804405]  [8104a1d9] ? try_to_wake_up+0x249/0x259
[  588.804412]  [8124ede0] ? netif_tx_lock+0x3d/0x69
[  588.804419]  [8123a42f] ? netdev_drivername+0x3b/0x40
[  588.804425]  [8124] ? dev_watchdog+0xe2/0x194
[  588.804432]  [8103fb0a] ? __wake_up+0x30/0x44
[  588.804441]  [8105a249] ? run_timer_softirq+0x1c9/0x268
[  588.804449]  [810539ca] ? __do_softirq+0xdd/0x19f
[  588.804457]  [8106fa83] ? tick_dev_program_event+0x2d/0x95
[  588.804465]  [81011c6c] ? call_softirq+0x1c/0x30
[  588.804471]  [810138c3] ? do_softirq+0x3f/0x7c
[  588.804478]  [81053839] ? irq_exit+0x36/0x76
[  588.804486]  [810258d7] ? smp_apic_timer_interrupt+0x87/0x95
[  588.804492]  [81011633] ? apic_timer_interrupt+0x13/0x20
[  588.804496]  EOI  [a009f4ef] ? acpi_idle_enter_bm+0x26a/0x29e 
[processor]
[  588.804520]  [a009f4e8] ? acpi_idle_enter_bm+0x263/0x29e 
[processor]
[  588.804528]  [81226bf3] ? cpuidle_idle_call+0x95/0xee
[  588.804536]  [8100fe6f] ? cpu_idle+0xa2/0xda
[  588.804542] ---[ end trace 84d7d31e6a0b75ae ]---
[  588.820207] r8169: eth0: link up
[  600.820205] r8169: eth0: link up

Bug#526983: linux-image-2.6.29-1-amd64: NETDEV WATCHDOG: eth0 (r8169): transmit timed out

2010-01-18 Thread Carlos Fonseca

On Sun, 17 Jan 2010, Ben Hutchings wrote:


I believe this bug was fixed in upstream version 2.6.32.  This is now
available in sid; please can you test it?

Ben.


I have just tried it with linux-image-2.6.32-trunk-amd64_2.6.32-4, and the 
timeout ocurred shortly after boot while rsyncing a large directory (see 
below). I have just installed linux-image-2.6.32-trunk-amd64_2.6.32-5, and 
will try to reproduce it with that kernel, as well.


Is there anything else I can do to help debug this?

Carlos


[  163.804080] [ cut here ]
[  163.804099] WARNING: at 
/build/buildd-linux-2.6_2.6.32-4-amd64-2Mp3BR/linux-2.6-2.6.32/debian/build/source_amd64_none/net/sched/sch_generic.c:261
 dev_watchdog+0xe2/0x194()
[  163.804106] Hardware name: Satellite A110
[  163.804111] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
[  163.804115] Modules linked in: i915 drm_kms_helper drm i2c_algo_bit bridge 
stp bnep sco rfcomm l2cap crc16 bluetooth xt_multiport xt_state autofs4 
cpufreq_stats cpufreq_userspace cpufreq_powersave cpufreq_conservative ipt_LOG 
iptable_mangle iptable_filter iptable_nat ip_tables nf_nat x_tables 
nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 fuse pcspkr coretemp acpi_cpufreq 
firewire_sbp2 loop snd_hda_codec_realtek snd_hda_intel snd_hda_codec arc4 
snd_hwdep ecb snd_pcm_oss snd_mixer_oss snd_pcm joydev snd_seq_midi battery 
snd_rawmidi pcmcia snd_seq_midi_event snd_seq ac container snd_timer 
snd_seq_device iwl3945 video output iwlcore snd mac80211 yenta_socket 
rsrc_nonstatic pcmcia_core cfg80211 psmouse processor i2c_i801 soundcore 
intel_agp button evdev i2c_core serio_raw rng_core agpgart rfkill 
snd_page_alloc ext3 jbd mbcache dm_mirror dm_region_hash dm_log dm_snapshot 
dm_mod sg sr_mod cdrom sd_mod crc_t10dif ide_pci_generic ide_core ata_piix 
ata_generic sdhci_pci sdhci firewire_ohci firewire_core crc_itu_t mmc_core 
led_class libata scsi_mod r8169 mii uhci_hcd thermal fan thermal_sys ehci_hcd 
usbcore nls_base [last unloaded: scsi_wait_scan]
[  163.804299] Pid: 0, comm: swapper Not tainted 2.6.32-trunk-amd64 #1
[  163.804303] Call Trace:
[  163.804307]  IRQ  [8124d58e] ? dev_watchdog+0xe2/0x194
[  163.804321]  [8124d58e] ? dev_watchdog+0xe2/0x194
[  163.804329]  [8104dc34] ? warn_slowpath_common+0x77/0xa3
[  163.804337]  [8124d4ac] ? dev_watchdog+0x0/0x194
[  163.804343]  [8104dcbc] ? warn_slowpath_fmt+0x51/0x59
[  163.804351]  [81041bed] ? enqueue_task_fair+0x24/0x69
[  163.804359]  [8103a5fb] ? activate_task+0x20/0x26
[  163.804366]  [8104a1da] ? try_to_wake_up+0x249/0x259
[  163.804374]  [8124d480] ? netif_tx_lock+0x3d/0x69
[  163.804381]  [81238acf] ? netdev_drivername+0x3b/0x40
[  163.804388]  [8124d58e] ? dev_watchdog+0xe2/0x194
[  163.804394]  [8103fb0a] ? __wake_up+0x30/0x44
[  163.804403]  [8105a245] ? run_timer_softirq+0x1c9/0x268
[  163.804412]  [810539ca] ? __do_softirq+0xdd/0x19f
[  163.804419]  [8106fa7f] ? tick_dev_program_event+0x2d/0x95
[  163.804427]  [81011c6c] ? call_softirq+0x1c/0x30
[  163.804434]  [810138c3] ? do_softirq+0x3f/0x7c
[  163.804441]  [81053839] ? irq_exit+0x36/0x76
[  163.804449]  [810258d7] ? smp_apic_timer_interrupt+0x87/0x95
[  163.804456]  [81011633] ? apic_timer_interrupt+0x13/0x20
[  163.804460]  EOI  [8102b5b4] ? hpet_legacy_next_event+0x0/0x7
[  163.804480]  [a009f4ef] ? acpi_idle_enter_bm+0x26a/0x29e 
[processor]
[  163.804491]  [a009f4e8] ? acpi_idle_enter_bm+0x263/0x29e 
[processor]
[  163.804501]  [8122529b] ? cpuidle_idle_call+0x95/0xee
[  163.804509]  [8100fe6f] ? cpu_idle+0xa2/0xda
[  163.804514] ---[ end trace 5d93e39c12569cc1 ]---
[  163.820195] r8169: eth0: link up
[  193.820254] r8169: eth0: link up
[  205.820192] r8169: eth0: link up
[  253.820265] r8169: eth0: link up

Bug#526983: linux-image-2.6.29-1-amd64: NETDEV WATCHDOG: eth0 (r8169): transmit timed out

2010-01-17 Thread Ben Hutchings
I believe this bug was fixed in upstream version 2.6.32.  This is now
available in sid; please can you test it?

Ben.

-- 
Ben Hutchings
I'm not a reverse psychological virus.  Please don't copy me into your sig.


signature.asc
Description: This is a digitally signed message part


Bug#526983: linux-image-2.6.29-1-amd64: NETDEV WATCHDOG: eth0 (r8169): transmit timed out

2010-01-17 Thread Ben Hutchings
On Sun, 2010-01-17 at 15:17 +, Ben Hutchings wrote:
 I believe this bug was fixed in upstream version 2.6.32.  This is now
 available in sid; please can you test it?

I now realise that I already wrote to you about bug #528362, where you
originally reported this, and that you said the bug was not fixed in
2.6.32.  I think that #528362 and #526983 may be different bugs.

Ben.

-- 
Ben Hutchings
I'm not a reverse psychological virus.  Please don't copy me into your sig.


signature.asc
Description: This is a digitally signed message part


Bug#526983: linux-image-2.6.29-1-amd64: NETDEV WATCHDOG: eth0 (r8169): transmit timed out

2010-01-17 Thread Victor Pablos Ceruelo

Maybe not so different, behavior is similar and logs too.
In
http://bugzilla.kernel.org/show_bug.cgi?id=14962
they told me to download and try r8168 driver
at www.realtek.com.tw

I'll give it a try and let you know (I'll let them know too, of course),
but I don't like the idea of installing non-debian sw ... ;-)

Regards,

Victor.

Ben Hutchings wrote:

On Sun, 2010-01-17 at 15:17 +, Ben Hutchings wrote:
  

I believe this bug was fixed in upstream version 2.6.32.  This is now
available in sid; please can you test it?



I now realise that I already wrote to you about bug #528362, where you
originally reported this, and that you said the bug was not fixed in
2.6.32.  I think that #528362 and #526983 may be different bugs.

Ben.

  



--
-
-

Víctor Pablos Ceruelo - Software Engineer, Phd student. 


Telephone number: +34 655 53 64 27
Email: vpablos at fi dot upm dot es or
  victorpablosceruelo at gmail dot com
Msn:   victorpablosceruelo at gmail dot com
Skype: victorpablosceruelo
Web page: https://babel.ls.fi.upm.es/~vpablos/
-
-
Si ha recibido este correo electrónico por error, le informamos que 
puede contener información confidencial y que está prohibido su uso.
Le rogamos lo comunique a su remitente y lo elimine. 
Gracias por su colaboración.


If you receive this e-mail by error, please note that it may contain 
confidential information, therefore, the use of this information is
strictly forbidden. Please inform the sender of the error and delete 
the information received. 
Thank you for your collaboration. 
-

-




Bug#526983: linux-image-2.6.29-1-amd64: NETDEV WATCHDOG: eth0 (r8169): transmit timed out

2009-07-25 Thread Moritz Muehlenhoff
On Mon, May 04, 2009 at 10:23:39PM +0300, Carlos Fonseca wrote:
 Package: linux-image-2.6.29-1-amd64
 Version: 2.6.29-4~snapshot.13461
 Severity: important
 
 
 The network card on my laptop will typically hang with a
 
 NETDEV WATCHDOG: eth0 (r8169): transmit timed out
 
 message sometime after the computer is switched on. Once this happens, 
 suspending to ram and resuming
 will bring the network back to life, while preserving connections already 
 established and so on.
 
 Neither unconfiguring the network interface and configuring it again nor 
 removing and reinserting the r8169 module helps.
 
 The problem never seems to happen again after resuming, even under heavy 
 network usage. All previous kernels I have tried
 exhibit the same problem. Please see the two separate traces below.

Looking at the commits for r8169.c, several look like they could've
fixed this. Could you try 2.6.30 from unstable?

Cheers,
Moritz



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#526983: linux-image-2.6.29-1-amd64: NETDEV WATCHDOG: eth0 (r8169): transmit timed out

2009-07-25 Thread Carlos Fonseca

On Sat, 25 Jul 2009, Moritz Muehlenhoff wrote:


Looking at the commits for r8169.c, several look like they could've
fixed this. Could you try 2.6.30 from unstable?

Cheers,
   Moritz


I have been using the kernels from

http://kernel-archive.buildserver.net/debian-kernel

and it continues to happen. I have also upgraded the BIOS in the meantime, 
but the only difference is that now, *sometimes*, the interface comes back 
to life shortly after the oops. Sometimes, it doesn't.


The oops below happened with kernel 2.6.30-4~snapshot.13990. The 
interface did come back afterwards, so I did not have to suspend/resume, 
but this is *not* always the case.


[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.30-1-amd64 (Debian 2.6.30-4~snapshot.13990) 
(wa...@debian.org) (gcc version 4.3.3 (GCC) ) #1 SMP Thu Jul 23 02:29:33 UTC 
2009
...
[   88.642173] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
[  321.366720] ACPI: EC: GPE storm detected, transactions will use polling mode
[  321.865126] ACPI: EC: missing confirmations, switch off interrupt mode.
[  384.804112] [ cut here ]
[  384.804132] WARNING: at 
/build/linux-2.6-2.6.30/debian/build/source_amd64_none/net/sched/sch_generic.c:226
 dev_watchdog+0xc7/0x164()
[  384.804138] Hardware name: Satellite A110
[  384.804141] NETDEV WATCHDOG: eth0 (r8169): transmit timed out
[  384.804145] Modules linked in: i915 drm i2c_algo_bit bridge stp bnep sco 
rfcomm l2cap bluetooth xt_multiport xt_state autofs4 cpufreq_stats 
cpufreq_userspace cpufreq_powersave cpufreq_conservative ipt_LOG iptable_mangle 
iptable_filter iptable_nat ip_tables nf_nat x_tables nf_conntrack_ipv4 
nf_conntrack nf_defrag_ipv4 pcspkr coretemp acpi_cpufreq firewire_sbp2 loop 
snd_hda_codec_realtek snd_hda_intel snd_hda_codec pcmcia arc4 snd_hwdep 
snd_pcm_oss snd_mixer_oss ecb snd_pcm yenta_socket rsrc_nonstatic joydev 
pcmcia_core evdev psmouse snd_seq_midi i2c_i801 serio_raw i2c_core iwl3945 
iwlcore rng_core snd_rawmidi iTCO_wdt rfkill mac80211 snd_seq_midi_event video 
output battery snd_seq snd_timer snd_seq_device cfg80211 container snd ac 
button processor soundcore snd_page_alloc intel_agp ext3 jbd mbcache dm_mirror 
dm_region_hash dm_log dm_snapshot dm_mod sg sr_mod cdrom sd_mod crc_t10dif 
ide_pci_generic ide_core ata_piix ata_generic libata r8169 mii sdhci_pci sdhci 
mmc_core led_class scsi_mod firewire_ohci firewire_core crc_itu_t uhci_hcd 
thermal fan thermal_sys ehci_hcd
[  384.804318] Pid: 0, comm: swapper Not tainted 2.6.30-1-amd64 #1
[  384.804322] Call Trace:
[  384.804326]  IRQ  [8042330e] ? dev_watchdog+0xc7/0x164
[  384.804341]  [8042330e] ? dev_watchdog+0xc7/0x164
[  384.804350]  [8024239f] ? warn_slowpath_common+0x77/0xa3
[  384.804357]  [80423247] ? dev_watchdog+0x0/0x164
[  384.804363]  [80242427] ? warn_slowpath_fmt+0x51/0x59
[  384.804372]  [8023430e] ? enqueue_task+0x5c/0x65
[  384.804380]  [8025474b] ? autoremove_wake_function+0x9/0x2e
[  384.804386]  [8042321b] ? netif_tx_lock+0x3d/0x69
[  384.804394]  [8040fcc0] ? netdev_drivername+0x3b/0x40
[  384.804400]  [8042330e] ? dev_watchdog+0xc7/0x164
[  384.804406]  [80235618] ? __wake_up+0x30/0x44
[  384.804412]  [80423247] ? dev_watchdog+0x0/0x164
[  384.804420]  [8024aa87] ? run_timer_softirq+0x193/0x210
[  384.804428]  [8025b4b9] ? getnstimeofday+0x55/0xaf
[  384.804435]  [80246fa9] ? __do_softirq+0xac/0x173
[  384.804442]  [80210bcc] ? call_softirq+0x1c/0x30
[  384.804448]  [802125fa] ? do_softirq+0x3a/0x7e
[  384.804454]  [80246d26] ? irq_exit+0x3f/0x80
[  384.804461]  [80220e63] ? smp_apic_timer_interrupt+0x87/0x94
[  384.804467]  [802105d3] ? apic_timer_interrupt+0x13/0x20
[  384.804471]  EOI  [a01d85e3] ? acpi_idle_enter_bm+0x274/0x2a8 
[processor]
[  384.804505]  [a01d85dc] ? acpi_idle_enter_bm+0x26d/0x2a8 
[processor]
[  384.804514]  [803fce9c] ? cpuidle_idle_call+0x8b/0xc7
[  384.804522]  [8020edda] ? cpu_idle+0x50/0x91
[  384.804527] ---[ end trace eadd4032f69184bd ]---
[  384.821181] r8169: eth0: link up

Thanks for looking into this.

Cheers,

Carlos