Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #1160
| From | Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: e1000 driver |
| Date | 2012-03-10 10:16 +0100 |
| Organization | Plouf ! |
| Message-ID | <jjf65b$1lll$1@saria.nerim.net> (permalink) |
| References | <4cuo29-7j7.ln1@spitzner.org> <4f5a867b$0$18682$91cee783@newsreader03.highway.telekom.at> |
Hello,
Johann Klammer a écrit :
>
> Happens here too from time to time. Different hardware, but same symptoms.
I had a similar message twice recently :
------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xc8/0x13b()
NETDEV WATCHDOG: eth1 (ne2k-pci): transmit timed out
Modules linked in: ipt_ULOG act_police cls_u32 sch_ingress ppp_deflate
zlib_defl
ate zlib_inflate bsd_comp ppp_async crc_ccitt ppp_generic
slhc ip6t_REJECT ip6ta
ble_filter ip6_tables xt_state ipt_REDIRECT
xt_multiport ipt_REJECT xt_limit xt_
tcpudp iptable_mangle
iptable_nat iptable_filter ip_tables x_tables psmouse apm
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack_ipv6 nf_conntrack_ipv4
nf_conntr
ack ipv6 ne2k_pci 8390 3c59x mii
Pid: 0, comm: swapper Not tainted 2.6.27.61-p3 #1
[<c0115fa1>] warn_slowpath+0x5a/0x7b
[<c0112bd3>] enqueue_task_fair+0x19/0x41
[<c0112070>] enqueue_task+0x3f/0x4a
[<c0112160>] activate_task+0x1c/0x20
[<c01122ff>] __wake_up_common+0x2d/0x52
[<c0111bd9>] place_entity+0x7c/0xca
[<c0112bd3>] enqueue_task_fair+0x19/0x41
[<c0112070>] enqueue_task+0x3f/0x4a
[<c01ca038>] strlcpy+0x11/0x3d
[<c02463c7>] dev_watchdog+0xc8/0x13b
[<c01262a4>] ktime_get_ts+0x1d/0x3f
[<c011c508>] run_timer_softirq+0x124/0x16c
[<c02462ff>] dev_watchdog+0x0/0x13b
[<c01199a1>] __do_softirq+0x38/0x78
[<c0119a03>] do_softirq+0x22/0x26
[<c0119ab9>] irq_exit+0x25/0x55
[<c0104de2>] do_IRQ+0x4d/0x5f
[<c010385f>] common_interrupt+0x23/0x28
[<c0107377>] default_idle+0x25/0x38
[<c01028d8>] cpu_idle+0x41/0x5d
=======================
---[ end trace 0901e6cba4f12be8 ]---
eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=819.
eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=424.
(and so on, until I unplugged and re-plugged the ethernet cable)
eth1 is a Realtek RTL8029 PCI connected to a DSL modem with a 10Mbit/s
half duplex interface.
Weirdly, after unplugging and re-plugging the ethernet cable, the
interface was operational again.
The first time happened 54 days after moving the system to a new
hardware but keeping the same 2.6.27.49 kernel which had run fine for 7
months on the old hardware. The previous card was a 3Com 3C509 ISA. The
second time happened 4 days after upgrading the kernel to 2.6.27.51.
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
e1000 driver Ralph Spitzner <rasp@spitzner.org> - 2012-03-09 10:15 +0100
Re: e1000 driver Richard Kettlewell <rjk@greenend.org.uk> - 2012-03-09 10:07 +0000
Re: e1000 driver Johann Klammer <klammerj@NOSPAM.a1.net> - 2012-03-09 23:39 +0100
Re: e1000 driver GangGreene <GangGreene@invalid.com> - 2012-03-09 20:01 -0500
Re: e1000 driver Johann Klammer <klammerj@NOSPAM.a1.net> - 2012-03-10 07:13 +0100
Re: e1000 driver Ralph Spitzner <rasp@spitzner.org> - 2012-03-10 09:30 +0100
Re: e1000 driver Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-03-10 15:02 +0000
Re: e1000 driver Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2012-03-10 10:16 +0100
Re: e1000 driver Ralph Spitzner <rasp@spitzner.org> - 2012-03-13 07:52 +0100
Re: e1000 driver unruh <unruh@invalid.ca> - 2012-03-14 01:59 +0000
Re: e1000 driver Ralph Spitzner <rasp@spitzner.org> - 2012-03-14 09:33 +0100
Re: e1000 driver "J.B. Wood" <john.wood@nrl.navy.mil> - 2012-03-13 05:36 -0400
Re: e1000 driver Rick Jones <rick.jones2@hp.com> - 2012-03-13 21:36 +0000
csiph-web