From: Jarek Poplawski <jarkao2@o2.pl>
To: Karl Meyer <adhocrocker@gmail.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
Date: Mon, 27 Aug 2007 14:50:36 +0200 [thread overview]
Message-ID: <20070827125035.GB2854@ff.dom.local> (raw)
In-Reply-To: <be1b757c0708210356s633db6c0m67601b250121ea0d@mail.gmail.com>
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.
next prev parent reply other threads:[~2007-08-27 12:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <be1b757c0708130435y689b9dd8raf9ac9f9c0fcc976@mail.gmail.com>
2007-08-13 16:58 ` PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out" Francois Romieu
[not found] ` <be1b757c0708131027v5c57822as2d9bd3190fd19b71@mail.gmail.com>
[not found] ` <20070814070901.GA14693@electric-eye.fr.zoreil.com>
[not found] ` <be1b757c0708141425qd887581n3922702b84a21758@mail.gmail.com>
[not found] ` <20070814224629.GB3495@electric-eye.fr.zoreil.com>
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 [this message]
2007-09-01 19:24 ` Karl Meyer
2007-09-02 22:15 ` Michal Piotrowski
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
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=20070827125035.GB2854@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=adhocrocker@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).