* Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
2007-08-16 14:11 ` Francois Romieu
@ 2007-08-16 21:03 ` Karl Meyer
2007-08-20 9:25 ` Karl Meyer
` (2 subsequent siblings)
3 siblings, 0 replies; 12+ messages in thread
From: Karl Meyer @ 2007-08-16 21:03 UTC (permalink / raw)
To: Francois Romieu; +Cc: linux-kernel, netdev
I did some testing today and found that the error occurs after
applying some of the patches. However I did not figure out the exact
patch in which the error "starts" since it sometimes occurs immediatly
when moving some data over the net and sometimes it takes 30 min till
I get the transmit timeout. I will be away till sunday and do some
more testing then.
2007/8/16, Francois Romieu <romieu@fr.zoreil.com>:
> (please do not remove the netdev Cc:)
>
> Francois Romieu <romieu@fr.zoreil.com> :
> [...]
> > If it does not work I'll dissect 0e4851502f846b13b29b7f88f1250c980d57e944
> > tomorrow.
>
> You will find a tgz archive in attachment which contains a serie of patches
> (0001-... to 0005-...) to walk from 6dccd16b7c2703e8bbf8bca62b5cf248332afbe2
> to 0e4851502f846b13b29b7f88f1250c980d57e944 in smaller steps.
>
> Please apply 0001 on top of 6dccd16b7c2703e8bbf8bca62b5cf248332afbe2. If it
> still works, apply 0002 on top of 0001, etc.
>
> --
> Ueimor
>
>
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
2007-08-16 14:11 ` Francois Romieu
2007-08-16 21:03 ` Karl Meyer
@ 2007-08-20 9:25 ` Karl Meyer
2007-08-21 10:56 ` Karl Meyer
2007-09-01 19:24 ` Karl Meyer
3 siblings, 0 replies; 12+ messages in thread
From: Karl Meyer @ 2007-08-20 9:25 UTC (permalink / raw)
To: Francois Romieu; +Cc: linux-kernel, netdev
The error exists from patch 2 on. I did some network testing with
patch 1 and currently use it and have no errors so far.
>From my experiences up to now patch 1 should be error free.
2007/8/16, Francois Romieu <romieu@fr.zoreil.com>:
> (please do not remove the netdev Cc:)
>
> Francois Romieu <romieu@fr.zoreil.com> :
> [...]
> > If it does not work I'll dissect 0e4851502f846b13b29b7f88f1250c980d57e944
> > tomorrow.
>
> You will find a tgz archive in attachment which contains a serie of patches
> (0001-... to 0005-...) to walk from 6dccd16b7c2703e8bbf8bca62b5cf248332afbe2
> to 0e4851502f846b13b29b7f88f1250c980d57e944 in smaller steps.
>
> Please apply 0001 on top of 6dccd16b7c2703e8bbf8bca62b5cf248332afbe2. If it
> still works, apply 0002 on top of 0001, etc.
>
> --
> Ueimor
>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
2007-08-16 14:11 ` Francois Romieu
2007-08-16 21:03 ` Karl Meyer
2007-08-20 9:25 ` Karl Meyer
@ 2007-08-21 10:56 ` Karl Meyer
2007-08-27 12:50 ` Jarek Poplawski
2007-09-01 19:24 ` Karl Meyer
3 siblings, 1 reply; 12+ messages in thread
From: Karl Meyer @ 2007-08-21 10:56 UTC (permalink / raw)
To: Francois Romieu; +Cc: linux-kernel, netdev
fyi:
I do not know whether it is related to the problem, but since using
the version you told me there are these entries is my log:
frege Hangcheck: hangcheck value past margin!
frege Hangcheck: hangcheck value past margin!
frege Hangcheck: hangcheck value past margin!
2007/8/16, Francois Romieu <romieu@fr.zoreil.com>:
> (please do not remove the netdev Cc:)
>
> Francois Romieu <romieu@fr.zoreil.com> :
> [...]
> > If it does not work I'll dissect 0e4851502f846b13b29b7f88f1250c980d57e944
> > tomorrow.
>
> You will find a tgz archive in attachment which contains a serie of patches
> (0001-... to 0005-...) to walk from 6dccd16b7c2703e8bbf8bca62b5cf248332afbe2
> to 0e4851502f846b13b29b7f88f1250c980d57e944 in smaller steps.
>
> Please apply 0001 on top of 6dccd16b7c2703e8bbf8bca62b5cf248332afbe2. If it
> still works, apply 0002 on top of 0001, etc.
>
> --
> Ueimor
>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
2007-08-21 10:56 ` Karl Meyer
@ 2007-08-27 12:50 ` Jarek Poplawski
0 siblings, 0 replies; 12+ messages in thread
From: Jarek Poplawski @ 2007-08-27 12:50 UTC (permalink / raw)
To: Karl Meyer; +Cc: Francois Romieu, linux-kernel, netdev
On 21-08-2007 12:56, Karl Meyer wrote:
> fyi:
> I do not know whether it is related to the problem, but since using
> the version you told me there are these entries is my log:
> frege Hangcheck: hangcheck value past margin!
...
BTW, I don't know wheter it's related too, but I think you should try
first to get rid of these errors:
> Freeing unused kernel memory: 220k freed
> usb_id[1320]: segfault at 00000000 eip b7e25db2 esp bfd1d734 error 4
> usb_id[1329]: segfault at 00000000 eip b7e1bdb2 esp bf9c9224 error 4
> usb_id[1322]: segfault at 00000000 eip b7df3db2 esp bfcb66c4 error 4
> usb_id[1321]: segfault at 00000000 eip b7e11db2 esp bf8f4b04 error 4
Regards,
Jarek P.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
2007-08-16 14:11 ` Francois Romieu
` (2 preceding siblings ...)
2007-08-21 10:56 ` Karl Meyer
@ 2007-09-01 19:24 ` Karl Meyer
2007-09-02 22:15 ` Michal Piotrowski
3 siblings, 1 reply; 12+ messages in thread
From: Karl Meyer @ 2007-09-01 19:24 UTC (permalink / raw)
To: Francois Romieu; +Cc: linux-kernel, netdev
This is what happened today:
Sep 1 21:08:01 frege NETDEV WATCHDOG: eth0: transmit timed out
frege ~ # uname -r
2.6.22.5-cfs-v20.5
2007/8/16, Francois Romieu <romieu@fr.zoreil.com>:
> (please do not remove the netdev Cc:)
>
> Francois Romieu <romieu@fr.zoreil.com> :
> [...]
> > If it does not work I'll dissect 0e4851502f846b13b29b7f88f1250c980d57e944
> > tomorrow.
>
> You will find a tgz archive in attachment which contains a serie of patches
> (0001-... to 0005-...) to walk from 6dccd16b7c2703e8bbf8bca62b5cf248332afbe2
> to 0e4851502f846b13b29b7f88f1250c980d57e944 in smaller steps.
>
> Please apply 0001 on top of 6dccd16b7c2703e8bbf8bca62b5cf248332afbe2. If it
> still works, apply 0002 on top of 0001, etc.
>
> --
> Ueimor
>
>
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
2007-09-01 19:24 ` Karl Meyer
@ 2007-09-02 22:15 ` Michal Piotrowski
2007-09-02 22:21 ` Karl Meyer
0 siblings, 1 reply; 12+ messages in thread
From: Michal Piotrowski @ 2007-09-02 22:15 UTC (permalink / raw)
To: Karl Meyer; +Cc: Francois Romieu, linux-kernel, netdev
Hi,
On 01/09/07, Karl Meyer <adhocrocker@gmail.com> wrote:
> This is what happened today:
>
> Sep 1 21:08:01 frege NETDEV WATCHDOG: eth0: transmit timed out
> frege ~ # uname -r
> 2.6.22.5-cfs-v20.5
Can you reproduce this on 2.6.22 (not 2.6.22.x - it might be a -stable
regression)?
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
2007-09-02 22:15 ` Michal Piotrowski
@ 2007-09-02 22:21 ` Karl Meyer
2007-09-12 20:50 ` Francois Romieu
0 siblings, 1 reply; 12+ messages in thread
From: Karl Meyer @ 2007-09-02 22:21 UTC (permalink / raw)
To: Michal Piotrowski; +Cc: Francois Romieu, linux-kernel, netdev
Hi,
am am looking for this issue for some time now, but there where no
errors in 2.6.22-r2 (gentoo speak, I guess this is 2.6.22.2
officially), I also ran git-bisect (for more information see the older
messages in this thread).
2007/9/3, Michal Piotrowski <michal.k.k.piotrowski@gmail.com>:
> Hi,
>
> On 01/09/07, Karl Meyer <adhocrocker@gmail.com> wrote:
> > This is what happened today:
> >
> > Sep 1 21:08:01 frege NETDEV WATCHDOG: eth0: transmit timed out
> > frege ~ # uname -r
> > 2.6.22.5-cfs-v20.5
>
> Can you reproduce this on 2.6.22 (not 2.6.22.x - it might be a -stable
> regression)?
>
> Regards,
> Michal
>
> --
> LOG
> http://www.stardust.webpages.pl/log/
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
2007-09-02 22:21 ` Karl Meyer
@ 2007-09-12 20:50 ` Francois Romieu
2007-09-26 9:07 ` Karl Meyer
2007-10-01 11:42 ` Karl Meyer
0 siblings, 2 replies; 12+ messages in thread
From: Francois Romieu @ 2007-09-12 20:50 UTC (permalink / raw)
To: Karl Meyer; +Cc: Michal Piotrowski, linux-kernel, netdev
Karl Meyer <adhocrocker@gmail.com> :
[...]
> am am looking for this issue for some time now, but there where no
> errors in 2.6.22-r2 (gentoo speak, I guess this is 2.6.22.2
> officially), I also ran git-bisect (for more information see the older
> messages in this thread).
2.6.22-r2 in gentoo is based on 2.6.22.1. It is way before
0e4851502f846b13b29b7f88f1250c980d57e944 that you reported to work.
Thus it is not surprizing that it works.
Any update regarding the patchkit that I sent on 2007/08/16 ?
It would help to narrow the culprit.
--
Ueimor
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
2007-09-12 20:50 ` Francois Romieu
@ 2007-09-26 9:07 ` Karl Meyer
2007-10-01 11:42 ` Karl Meyer
1 sibling, 0 replies; 12+ messages in thread
From: Karl Meyer @ 2007-09-26 9:07 UTC (permalink / raw)
To: Francois Romieu; +Cc: Michal Piotrowski, linux-kernel, netdev
Hi Francois,
this is what I found and sent:
The error exists from patch 2 on. I did some network testing with
patch 1 and currently use it and have no errors so far.
>From my experiences up to now patch 1 should be error free.
Do you need additional info?
2007/9/12, Francois Romieu <romieu@fr.zoreil.com>:
> Karl Meyer <adhocrocker@gmail.com> :
> [...]
> > am am looking for this issue for some time now, but there where no
> > errors in 2.6.22-r2 (gentoo speak, I guess this is 2.6.22.2
> > officially), I also ran git-bisect (for more information see the older
> > messages in this thread).
>
> 2.6.22-r2 in gentoo is based on 2.6.22.1. It is way before
> 0e4851502f846b13b29b7f88f1250c980d57e944 that you reported to work.
> Thus it is not surprizing that it works.
>
> Any update regarding the patchkit that I sent on 2007/08/16 ?
>
> It would help to narrow the culprit.
>
> --
> Ueimor
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
2007-09-12 20:50 ` Francois Romieu
2007-09-26 9:07 ` Karl Meyer
@ 2007-10-01 11:42 ` Karl Meyer
1 sibling, 0 replies; 12+ messages in thread
From: Karl Meyer @ 2007-10-01 11:42 UTC (permalink / raw)
To: Francois Romieu; +Cc: Michal Piotrowski, linux-kernel, netdev
Hi,
after reading about issues with the nics on kontron boards I did a
bios upgrade,
but this did not change anything.
However, yesterday the nic (onboard) I used died. No link at all,
after switching to
the next onboard nic I got a NETDEV transmit timeout with that one on
kernel 2.6.22-r2.
It seems the whole thing is a hardware issue. I will try to figure out
with kontron.
Sorry :(
Karl
2007/9/12, Francois Romieu <romieu@fr.zoreil.com>:
> Karl Meyer <adhocrocker@gmail.com> :
> [...]
> > am am looking for this issue for some time now, but there where no
> > errors in 2.6.22-r2 (gentoo speak, I guess this is 2.6.22.2
> > officially), I also ran git-bisect (for more information see the older
> > messages in this thread).
>
> 2.6.22-r2 in gentoo is based on 2.6.22.1. It is way before
> 0e4851502f846b13b29b7f88f1250c980d57e944 that you reported to work.
> Thus it is not surprizing that it works.
>
> Any update regarding the patchkit that I sent on 2007/08/16 ?
>
> It would help to narrow the culprit.
>
> --
> Ueimor
>
^ permalink raw reply [flat|nested] 12+ messages in thread