[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <be1b757c0708131027v5c57822as2d9bd3190fd19b71@mail.gmail.com>
Date: Mon, 13 Aug 2007 19:27:12 +0200
From: "Karl Meyer" <adhocrocker@...il.com>
To: "Francois Romieu" <romieu@...zoreil.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
Hi,
dmesg, interrupts and .config are attached. I will have a look at git bisect.
2007/8/13, Francois Romieu <romieu@...zoreil.com>:
> (netdev Cced)
>
> Karl Meyer <adhocrocker@...il.com> :
> [...]
> > I am having trouble with the 2.6.23 kernel. With all versions since
> > 2.6.23-rc1 I have trouble with my network connection. When using the
> > network over a certain level (just browsing the web seems not to be
> > enough) e.g. when installing packages over the nvsv4 share, all
> > network stuff freezes for some time and syslog tells me:
> > Aug 13 13:16:09 frege NETDEV WATCHDOG: eth0: transmit timed out
> > Aug 13 13:16:39 frege NETDEV WATCHDOG: eth0: transmit timed out
> > Aug 13 13:17:09 frege NETDEV WATCHDOG: eth0: transmit timed out
> > Aug 13 13:17:57 frege NETDEV WATCHDOG: eth0: transmit timed out
>
> Can you:
> - send a complete dmesg + /proc/interrupts + .config
> - use git bisect to find a suspect changeset
> I do not expect any change of behavior between 2.6.22 and
> 25805dcf9d83098cf5492117ad2669cd14cc9b24 if it can help you narrow
> things down (assuming it is a r8169 regression).
>
> --
> Ueimor
>
View attachment "2.6.23-rc3.config" of type "text/plain" (38445 bytes)
View attachment "dmesg" of type "text/plain" (23530 bytes)
View attachment "interrupts" of type "text/plain" (776 bytes)
Powered by blists - more mailing lists