From: "Thomas Hellström" <thomas@tungstengraphics.com>
To: Marcus Better <marcus@better.se>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
Dave Airlie <airlied@linux.ie>,
netdev@vger.kernel.org, dri-devel@lists.sourceforge.net,
Alan Hourihane <alanh@tungstengraphics.com>
Subject: Re: rtl8139: NETDEV WATCHDOG: eth0: transmit timed out
Date: Sat, 08 Jul 2006 18:15:55 +0200 [thread overview]
Message-ID: <44AFDA3B.6020904@tungstengraphics.com> (raw)
In-Reply-To: <44AE8CBB.4070409@better.se>
Hi!
Marcus Better wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>(For those haven't followed, this is about
> http://permalink.gmane.org/gmane.linux.network/38493
>)
>
>Francois Romieu wrote:
>
>
>>Marcus Better <marcus@better.se> :
>>
>>
>>>I'm seeing this problem on my Acer Travelmate 223X laptop with built-in
>>>Realtek 8139: The ethernet stops working, usually after at most a few
>>>minutes operation.
>>>
>>>
>
>
>
>>In a better world, you would narrow the suspect with a git bissect [1]
>>between v2.6.15 and v2.6.16.
>>
>>
>
>I did, and the winner after 13 reboots is...
>
>commit de227f5f32775d86e5c780a7cffdd2e08574f7fb
>Author: Dave Airlie <airlied@starflyer.(none)>
>Date: Wed Jan 25 15:31:43 2006 +1100
>
> drm: i915 patches from Tungsten Graphics
>
> Fix CMDBUFFER path, add heap destroy and flesh out sarea for rotation
> (Tungsten Graphics)
>
> From: Alan Hourihane <alanh@tungstengraphics.com>
> Signed-off-by: Dave Airlie <airlied@linux.ie>
>
>
>I didn't believe it at first either, but blacklisting the i915 module
>actually fixes the problem. Now that I know what to look for, I notice
>that the network errors always started cropping up after X11 started.
>
>Wonder what's going on here. Why is the graphics driver killing my network?
>
>
I guess you got the wrong commit, and the correct one should be the one
where Dave adds vblank interrupts. It should be close to the one you listed.
Some i915 chips have buggy interrupts. What happens is that the display
interrupts are duplicated on the sound interrupt channel. Usually
there's no interrupt handler there that recognizes them, and after a
while, the kernel detects too many spurious interrupts and disables the
sound IRQ line. If the network sits on the same IRQ line, it will be
disabled as well. If you check your kernel logs, you will probably have
messages about disabled IRQs.
A workaround is to add the "noirqdebug" (I hope I remember the spelling
correctly) kernel option at boot time.
/Thomas
>Marcus
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.3 (GNU/Linux)
>
>iD8DBQFEroy7XjXn6TzcAQkRAp7bAJ9F7HgWg+VsvQ0fwkK3+b4Ne+tASwCg8+m3
>8i5BoW+ujUjoX3DLW0QKAPQ=
>=MDAc
>-----END PGP SIGNATURE-----
>
>Using Tomcat but need to do more? Need to support web services, security?
>Get stuff done quickly with pre-integrated technology to make your job easier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>--
>_______________________________________________
>Dri-devel mailing list
>Dri-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/dri-devel
>
>
next prev parent reply other threads:[~2006-07-08 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 9:23 rtl8139: NETDEV WATCHDOG: eth0: transmit timed out Marcus Better
2006-06-30 21:16 ` Francois Romieu
2006-07-04 19:38 ` Marcus Better
2006-07-07 16:32 ` Marcus Better
2006-07-08 16:15 ` Thomas Hellström [this message]
2006-07-09 7:23 ` Marcus Better
2006-07-09 7:34 ` Thomas Hellström
2006-07-09 16:34 ` Marcus Better
2006-07-10 13:02 ` Marcus Better
2006-07-10 13:10 ` Thomas Hellström
2006-07-10 13:17 ` Marcus Better
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44AFDA3B.6020904@tungstengraphics.com \
--to=thomas@tungstengraphics.com \
--cc=airlied@linux.ie \
--cc=alanh@tungstengraphics.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=marcus@better.se \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).