From: Plamen Petrov <pvp-lsts@fs.uni-ruse.bg>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Jarek Poplawski <jarkao2@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 16626] New: Machine hangs with EIP at skb_copy_and_csum_dev
Date: Tue, 24 Aug 2010 16:27:59 +0300 [thread overview]
Message-ID: <4C73C8DF.4060601@fs.uni-ruse.bg> (raw)
In-Reply-To: <4C738636.4000107@fs.uni-ruse.bg>
На 24.8.2010 г. 11:43, Plamen Petrov написа:
> На 24.8.2010 г. 08:01, Eric Dumazet написа:
>> Le mardi 24 août 2010 à 07:51 +0300, Plamen Petrov a écrit :
>>> So far - not so good. :(
...
>>
> Here is what I've got while running the kernel with the patch
> I attached earlier plus the above one, after turning GRO on for
> my tg3 nic:
>
> [picture 10]
> http://picpaste.com/37e37f9ff9504e3a003f49092f9b1be6.jpg
>
> [picture 11]
> http://picpaste.com/5663ca7c5041c0ed7a1f3e6a9aa17a9e.jpg
>
> [picture 12]
> http://picpaste.com/17f2ecaa409a1ebbf835a2e0519d3099.jpg
>
> Now moving on to the second proposed patch from Jarek.
>
> Thanks,
> Plamen
The current status: if I enable GRO on the tg3 - the kernel oopses.
It just takes a different amount of time to trigger: somewhere from
30 seconds to 30 minutes.
The oopses looks the same, and here are the latest:
[picture 13]
http://picpaste.com/c8dbda8f5c15d9ce3e050dd7f245f5d0.jpg
[picture 14]
http://picpaste.com/646cca586b704c5b72d3cf9fa54c7344.jpg
I was wondering which debug options could help us track this down?
Thanks,
Plamen
next prev parent reply other threads:[~2010-08-24 13:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16626-10286@https.bugzilla.kernel.org/>
2010-08-19 22:21 ` [Bugme-new] [Bug 16626] New: Machine hangs with EIP at skb_copy_and_csum_dev Andrew Morton
2010-08-20 5:03 ` Plamen Petrov
2010-08-20 5:11 ` Andrew Morton
2010-08-20 6:12 ` Plamen Petrov
2010-08-20 6:20 ` Andrew Morton
2010-08-20 6:26 ` Plamen Petrov
2010-08-20 6:34 ` Eric Dumazet
2010-08-20 6:57 ` Plamen Petrov
2010-08-20 7:38 ` Plamen Petrov
2010-08-20 8:31 ` Plamen Petrov
2010-08-20 9:19 ` Plamen Petrov
2010-08-20 10:26 ` Eric Dumazet
2010-08-20 10:53 ` Plamen Petrov
2010-08-20 19:38 ` Jarek Poplawski
2010-08-21 7:47 ` Jarek Poplawski
2010-08-21 7:50 ` Eric Dumazet
2010-08-21 8:07 ` Jarek Poplawski
2010-08-23 11:47 ` Plamen Petrov
2010-08-23 12:35 ` Eric Dumazet
2010-08-23 12:47 ` Jarek Poplawski
2010-08-23 13:00 ` Eric Dumazet
2010-08-23 13:10 ` Jarek Poplawski
2010-08-23 13:43 ` Plamen Petrov
2010-08-23 14:05 ` Plamen Petrov
2010-08-23 14:14 ` Jarek Poplawski
2010-08-24 4:51 ` Plamen Petrov
2010-08-24 5:01 ` Eric Dumazet
2010-08-24 8:43 ` Plamen Petrov
2010-08-24 13:27 ` Plamen Petrov [this message]
2010-08-24 15:08 ` Eric Dumazet
2010-08-24 17:25 ` Plamen Petrov
2010-08-24 18:22 ` Jarek Poplawski
2010-08-24 19:19 ` Eric Dumazet
2010-08-25 7:05 ` Plamen Petrov
2010-08-29 7:48 ` [PATCH] net: reset ip_summed in skb_tunnel_rx() Eric Dumazet
2010-08-29 15:35 ` Jesse Gross
2010-08-27 8:44 ` [Bugme-new] [Bug 16626] New: Machine hangs with EIP at skb_copy_and_csum_dev Plamen Petrov
2010-08-24 5:19 ` Plamen Petrov
2010-08-24 6:18 ` Jarek Poplawski
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=4C73C8DF.4060601@fs.uni-ruse.bg \
--to=pvp-lsts@fs.uni-ruse.bg \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=eric.dumazet@gmail.com \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
/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).