Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Ralph Spitzner Newsgroups: comp.os.linux.networking Subject: e1000 driver Date: Fri, 09 Mar 2012 10:15:36 +0100 Organization: Hanswurst & Kaspar Hauser Ltd. Lines: 60 Message-ID: <4cuo29-7j7.ln1@spitzner.org> NNTP-Posting-Host: hHjA4DcVYoA8Gqbq3XyaYQ.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Firefox/10.0.2 SeaMonkey/2.7.2 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.os.linux.networking:1153 This may be the wrong group, feel free to shove me to another :-) Since the latest 2.6.x and with the new 3.x.x Kernels I get some really strange behaviour on an 82547EI card using the e1000 driver. Gateway has two cards one Realtek pointing at the cable-modem and the gig pointing at the lan via a dlink Giga switch connected to the Desktop (gigabit) and the printer (100mb) and sometimes friends computers, all good so far. (nice throughput, no errors) Then, when I connect the Targa (el Cheapo) wifi router (100m) for the netbook and phone it will take anywhere between 1 and 6 _Days_ until the connection to the gateway locks up producing _this_ on the routers screen: [16281.008328] ------------[ cut here ]------------ [16281.009020] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xb9/0x110() [16281.009020] Hardware name: To Be Filled By O.E.M. [16281.009020] NETDEV WATCHDOG: eth1 (e1000): transmit queue 0 timed out [16281.009020] Modules linked in: p4_clockmod freq_table speedstep_lib dvb_ttpci budget_av tda10023 stv0297 budget_core dvb_core i915 drm_kms_helper saa7146_vv saa7146 cfbcopyarea video ttpci_eeprom e1000 snd_intel8x0 8139too snd_ac97_codec ac97_bus backlight cfbimgblt cfbfillrect intel_agp intel_gtt [last unloaded: dvb_ttpci] [16281.009020] Pid: 0, comm: swapper/0 Tainted: G W 3.2.2-spitzner.org #3 [16281.009020] Call Trace: [16281.009020] [] warn_slowpath_common+0x65/0x7a [16281.009020] [] ? dev_watchdog+0xb9/0x110 [16281.009020] [] warn_slowpath_fmt+0x26/0x2a [16281.009020] [] dev_watchdog+0xb9/0x110 [16281.009020] [] run_timer_softirq+0x156/0x1f9 [16281.009020] [] ? netif_tx_unlock+0x3e/0x3e [16281.009020] [] __do_softirq+0x93/0x130 [16281.009020] [] ? local_bh_enable+0xa/0xa [16281.009020] [] ? irq_exit+0x35/0x84 [16281.009020] [] ? smp_apic_timer_interrupt+0x5e/0x6c [16281.009459] [] ? apic_timer_interrupt+0x2a/0x30 [16281.009879] [] ? videobuf_read_stream+0xe7/0x238 [16281.010040] [] ? default_idle+0x52/0x81 [16281.010040] [] ? cpu_idle+0x52/0x73 [16281.010040] [] ? rest_init+0x58/0x5a [16281.010040] [] ? start_kernel+0x2b8/0x2bd [16281.010040] [] ? i386_start_kernel+0xb0/0xb7 [16281.010040] ---[ end trace 4eaa2a86a8e2da24 ]--- Any idea WTF is going on there, anyone ? (and why the swapper is tainted all of a sudden) Ok, it might just be hardware going bad, but it coincides with newer kernels.... regards -rasp -- RTMPDump & ffmpeg are your friends.. -icke