[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#600281: marked as done (linux-image-2.6.26-2-sparc64: networks halt after a few weeks on TULIP DAVICOM DM9102, NETDEV WATCHDOG: eth0: transmit timed out)

Your message dated Fri, 23 Apr 2021 10:16:07 +0200
with message-id <[🔎] YIKCR5VxXUv6oNuf@eldamar.lan>
and subject line Re: Bug#600281: linux-image-2.6.26-2-sparc64: networks halt after a few weeks on TULIP DAVICOM DM9102, NETDEV WATCHDOG: eth0: transmit timed out
has caused the Debian Bug report #600281,
regarding linux-image-2.6.26-2-sparc64: networks halt after a few weeks on TULIP DAVICOM DM9102, NETDEV WATCHDOG: eth0: transmit timed out
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
600281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600281
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.26-2-sparc64
Version: 2.6.26-22lenny1
Severity: important


I am using a Sun Fire V100 with Debian Lenny. It was OK for a few weeks, then suddenly it was not possible to access it from SSH: connexion timed 
out. The only thing I could get from network was the "index of" apache default index page. No way to download a file. All looked like if the 
network was over logging.

I couldn't get physical access, so asked someone to reboot it. After that I had a look to syslog, there are many lines like this:
[...]
Oct 14 15:02:11 titine kernel: [7088458.574525] NETDEV WATCHDOG: eth0: transmit timed out
Oct 14 15:02:27 titine kernel: [7088474.574528] NETDEV WATCHDOG: eth0: transmit timed out
Oct 14 15:02:47 titine kernel: [7088494.574530] NETDEV WATCHDOG: eth0: transmit timed out
Oct 14 15:03:03 titine kernel: [7088510.574533] NETDEV WATCHDOG: eth0: transmit timed out
Oct 14 15:03:19 titine kernel: [7088526.574532] NETDEV WATCHDOG: eth0: transmit timed out
Oct 14 15:03:39 titine kernel: [7088546.574534] NETDEV WATCHDOG: eth0: transmit timed out
Oct 14 15:03:55 titine kernel: [7088562.574532] NETDEV WATCHDOG: eth0: transmit timed out
Oct 14 15:04:11 titine kernel: [7088578.574537] NETDEV WATCHDOG: eth0: transmit timed out
Oct 14 15:04:23 titine kernel: [7088590.574540] NETDEV WATCHDOG: eth0: transmit timed out
Oct 14 15:04:47 titine kernel: [7088614.574541] NETDEV WATCHDOG: eth0: transmit timed out
Oct 14 15:05:27 titine kernel: [7088654.574546] NETDEV WATCHDOG: eth0: transmit timed out
Oct 14 15:06:03 titine kernel: [7088690.574542] NETDEV WATCHDOG: eth0: transmit timed out
[...]

Saw a similar bug, number 522592. It's closed now, with no solution or fix.

Network settings:

mii-tool eth0 -vv
Using SIOCGMIIPHY=0x8947
eth0: negotiated 100baseTx-FD, link ok
  registers for MII PHY 1: 
    1000 782d 0181 b840 01e1 41e1 0001 0000
    0000 0000 0000 0000 0000 0000 0000 0000
    0000 8018 7800 1000 0001 0000 0000 0000
    0000 0000 0000 0000 0000 0000 0000 0000
  product info: vendor 00:60:6e, model 4 rev 0
  basic mode:   autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD

Module info:

modinfo tulip
filename:       /lib/modules/2.6.26-2-sparc64/kernel/drivers/net/tulip/tulip.ko
version:        1.1.15-NAPI
license:        GPL
description:    Digital 21*4* Tulip ethernet driver
author:         The Linux Kernel Team
srcversion:     A033E0667282FCC8CABF3C6
alias:          pci:v00001414d00000002sv*sd*bc*sc*i*
alias:          pci:v000014EAd0000AB08sv*sd*bc*sc*i*
alias:          pci:v000010B7d00009300sv*sd*bc*sc*i*
alias:          pci:v000017B3d0000AB08sv*sd*bc*sc*i*
alias:          pci:v00001737d0000AB08sv*sd*bc*sc*i*
alias:          pci:v00001737d0000AB09sv*sd*bc*sc*i*
alias:          pci:v00001626d00008410sv*sd*bc*sc*i*
alias:          pci:v000014F1d00001803sv*sd*bc*sc*i*
alias:          pci:v00001186d00001591sv*sd*bc*sc*i*
alias:          pci:v00001186d00001561sv*sd*bc*sc*i*
alias:          pci:v00001186d00001541sv*sd*bc*sc*i*
alias:          pci:v00001113d00009511sv*sd*bc*sc*i*
alias:          pci:v00001113d00001217sv*sd*bc*sc*i*
alias:          pci:v00001113d00001216sv*sd*bc*sc*i*
alias:          pci:v00001282d00009102sv*sd*bc*sc*i*
alias:          pci:v00001282d00009100sv*sd*bc*sc*i*
alias:          pci:v00008086d00000039sv*sd*bc*sc*i*
alias:          pci:v000011F6d00009881sv*sd*bc*sc*i*
alias:          pci:v00001259d0000A120sv*sd*bc*sc*i*
alias:          pci:v0000104Ad00002774sv*sd*bc*sc*i*
alias:          pci:v0000104Ad00000981sv*sd*bc*sc*i*
alias:          pci:v000013D1d0000AB08sv*sd*bc*sc*i*
alias:          pci:v000013D1d0000AB03sv*sd*bc*sc*i*
alias:          pci:v000013D1d0000AB02sv*sd*bc*sc*i*
alias:          pci:v00001317d00009511sv*sd*bc*sc*i*
alias:          pci:v00001317d00001985sv*sd*bc*sc*i*
alias:          pci:v00001317d00000985sv*sd*bc*sc*i*
alias:          pci:v00001317d00000981sv*sd*bc*sc*i*
alias:          pci:v000011ADd0000C115sv*sd*bc*sc*i*
alias:          pci:v0000125Bd00001400sv*sd*bc*sc*i*
alias:          pci:v000010D9d00000531sv*sd*bc*sc*i*
alias:          pci:v000010D9d00000512sv*sd*bc*sc*i*
alias:          pci:v000011ADd00000002sv*sd*bc*sc*i*
alias:          pci:v00001011d00000019sv*sd*bc*sc*i*
alias:          pci:v00001011d00000009sv*sd*bc*sc*i*
depends:        
vermagic:       2.6.26-2-sparc64 mod_unload modversions 
parm:           tulip_debug:int
parm:           max_interrupt_work:int
parm:           rx_copybreak:int
parm:           csr0:int
parm:           options:array of int
parm:           full_duplex:array of int

Are there any tools or options I could put on so as to get more information on the next time this bug appears (if it does)?

Remi.

-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: sparc (sparc64)

Kernel: Linux 2.6.26-2-sparc64
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-2-sparc64 depends on:
ii  debconf [debconf-2.0]         1.5.24     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92o      tools for generating an initramfs
ii  module-init-tools             3.4-1      tools for managing Linux kernel mo

linux-image-2.6.26-2-sparc64 recommends no packages.

Versions of packages linux-image-2.6.26-2-sparc64 suggests:
pn  fdutils            <none>                (no description available)
pn  linux-doc-2.6.26   <none>                (no description available)
ii  silo               1.4.13a+git20070930-3 Sparc Improved LOader

-- debconf information:
  linux-image-2.6.26-2-sparc64/postinst/old-system-map-link-2.6.26-2-sparc64: true
  linux-image-2.6.26-2-sparc64/preinst/abort-install-2.6.26-2-sparc64:
  linux-image-2.6.26-2-sparc64/postinst/bootloader-test-error-2.6.26-2-sparc64:
  linux-image-2.6.26-2-sparc64/prerm/removing-running-kernel-2.6.26-2-sparc64: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.26-2-sparc64/preinst/initrd-2.6.26-2-sparc64:
  linux-image-2.6.26-2-sparc64/preinst/lilo-initrd-2.6.26-2-sparc64: true
  linux-image-2.6.26-2-sparc64/preinst/abort-overwrite-2.6.26-2-sparc64:
  linux-image-2.6.26-2-sparc64/postinst/depmod-error-2.6.26-2-sparc64: false
  linux-image-2.6.26-2-sparc64/postinst/old-initrd-link-2.6.26-2-sparc64: true
  linux-image-2.6.26-2-sparc64/preinst/failed-to-move-modules-2.6.26-2-sparc64:
* linux-image-2.6.26-2-sparc64/preinst/already-running-this-2.6.26-2-sparc64:
  linux-image-2.6.26-2-sparc64/preinst/elilo-initrd-2.6.26-2-sparc64: true
  linux-image-2.6.26-2-sparc64/postinst/depmod-error-initrd-2.6.26-2-sparc64: false
  linux-image-2.6.26-2-sparc64/postinst/old-dir-initrd-link-2.6.26-2-sparc64: true
  linux-image-2.6.26-2-sparc64/preinst/overwriting-modules-2.6.26-2-sparc64: true
  linux-image-2.6.26-2-sparc64/preinst/bootloader-initrd-2.6.26-2-sparc64: true
  linux-image-2.6.26-2-sparc64/postinst/bootloader-error-2.6.26-2-sparc64:
  linux-image-2.6.26-2-sparc64/postinst/kimage-is-a-directory:
  linux-image-2.6.26-2-sparc64/prerm/would-invalidate-boot-loader-2.6.26-2-sparc64: true
  linux-image-2.6.26-2-sparc64/postinst/create-kimage-link-2.6.26-2-sparc64: true
  linux-image-2.6.26-2-sparc64/preinst/lilo-has-ramdisk:

--- End Message ---
--- Begin Message --- 
Control: tags -1 + moreinfo

Hi,

On Tue, Aug 20, 2013 at 06:08:41PM +0200, Moritz Muehlenhoff wrote:
> reassign 600281 src:linux
> thanks
> 
> On Thu, Oct 21, 2010 at 03:27:37AM +0200, Rémi Bouhl wrote:
> > 2010/10/18, dann frazier <dannf@debian.org>:
> > >
> > > Does /var/log/kern.log contain anything interesting before these
> > > messages? (oops message, tulip driver messages, etc)?
> > 
> > Ah, yes. Here it is:
> > 
> > Oct 13 06:25:02 titine kernel: imklog 3.18.6, log source = /proc/kmsg started.
> > Oct 13 18:38:17 titine kernel: [7015022.568660] NETDEV WATCHDOG: eth0:
> > transmit timed out
> > Oct 13 18:38:17 titine kernel: [7015022.637393] ------------[ cut here
> > ]------------
> > Oct 13 18:38:17 titine kernel: [7015022.700285] WARNING: at
> > net/sched/sch_generic.c:222 dev_watchdog+0xb4/0x118()
> > Oct 13 18:38:17 titine kernel: [7015022.796421] Modules linked in:
> > nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc tun xt_multiport
> > xt_tcpudp xt_state iptable_filter ipt_MASQUERADE iptable_nat nf_nat
> > nf_conntrack_ipv4 nf_conntrack ip_tables x_tables ipv6 ext3 jbd raid1
> > raid0 md_mod ide_cd_mod cdrom ide_disk alim15x3 ide_pci_generic tulip
> > ata_generic libata scsi_mod ohci_hcd dmfe [last unloaded:
> > scsi_wait_scan]
> > Oct 13 18:38:17 titine kernel: [7015023.238823] Call Trace:
> > Oct 13 18:38:17 titine kernel: [7015023.273110]  [00000000006235fc]
> > dev_watchdog+0xbc/0x118
> > Oct 13 18:38:17 titine kernel: [7015023.343979]  [000000000045f924]
> > run_timer_softirq+0x178/0x1e8
> > Oct 13 18:38:17 titine kernel: [7015023.421699]  [000000000045bc48]
> > __do_softirq+0x48/0xb8
> > Oct 13 18:38:17 titine kernel: [7015023.491422]  [000000000042d2b4]
> > do_softirq+0x58/0x7c
> > Oct 13 18:38:17 titine kernel: [7015023.558858]  [000000000045b8a4]
> > irq_exit+0x40/0x8c
> > Oct 13 18:38:17 titine kernel: [7015023.624004]  [00000000004319a4]
> > timer_interrupt+0x74/0x84
> > Oct 13 18:38:17 titine kernel: [7015023.697155]  [00000000004209d4]
> > tl0_irq14+0x1c/0x20
> > Oct 13 18:38:17 titine kernel: [7015023.763447]  [0000000000427674]
> > cpu_idle+0x9c/0xc4
> > Oct 13 18:38:17 titine kernel: [7015023.828599]  [000000000078296c]
> > start_kernel+0x318/0x324
> > Oct 13 18:38:17 titine kernel: [7015023.900605]  [000000000067d260]
> > auxio_probe+0x0/0xd0
> > Oct 13 18:38:17 titine kernel: [7015023.968039]  [0000000000000000] 0x8
> > Oct 13 18:38:17 titine kernel: [7015024.016044] ---[ end trace
> > 8945f4f399a29df3 ]---
> > Oct 13 18:38:51 titine kernel: [7015058.568656] NETDEV WATCHDOG: eth0:
> > transmit timed out
> > 
> > Then it repeats "NETDEV WATCHDOG" message.
> > 
> > >
> > >> Saw a similar bug, number 522592. It's closed now, with no solution or
> > >> fix.
> > >
> > > As suggested in that bug report, can you try the 2.6.32 kernel from
> > > squeeze and see if it has better results?
> > >
> > I can do this, but would not that be usefull to help finding the bug
> > on stable version?
> > This server is not critical, I don't mind if 2.6.26 or 2.6.32 is
> > running on it. Just tell me the one it's better to use for debug
> > purposes, and I'll use it.
> 
> Does this work with current kernels, e.g. Wheezy?

I'm going to assume we can close this bug, as there was no followup,
and possibly not anymore easy to reproduce.

In case this is still the case please feel free to reopen the bug.

Regards,
Salvatore

--- End Message ---
Reply to: