From: Divy Le Ray <divy@chelsio.com>
To: Ben Greear <greearb@candelatech.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: reproducible cxgb kernel panic in FC8 kernel 2.6.23.1-49
Date: Thu, 15 Nov 2007 03:46:55 -0800 [thread overview]
Message-ID: <473C31AF.9030300@chelsio.com> (raw)
In-Reply-To: <473A67CA.8030007@candelatech.com>
Ben Greear wrote:
> This panic happens (almost?) immediately after starting TCP traffic
> between
> the cxgb nic on this system and another. We also got at least one crash
> on a custom/tainted 2.6.20.12 kernel, but it would run for at least
> a few minutes at ~1Gbps first.
>
> I think my serial console chomped some of this..but it's very
> reproducible,
> so if you need more info I can make the terminal wider and do it again.
>
Hi Ben,
I just posted a patch fixing this T2 crash. It appeared in 2.6.22, when
eth_type_trans()
was modified to set skb->dev. cxgb3 got fixed at the time, but I
obviously forgot the
chelsio driver. I'm a bit behind on T2 updates. I will get to it in a
few days.
Cheers,
Divy
next prev parent reply other threads:[~2007-11-15 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 3:13 reproducible cxgb kernel panic in FC8 kernel 2.6.23.1-49 Ben Greear
2007-11-15 11:46 ` Divy Le Ray [this message]
2007-11-20 2:22 ` Ben Greear
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=473C31AF.9030300@chelsio.com \
--to=divy@chelsio.com \
--cc=greearb@candelatech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.