From: Meelis Roos <mroos@linux.ee>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Steffen Klassert <klassert@mathematik.tu-chemnitz.de>,
netdev@vger.kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: bisected regression: 3c59x corrupts packets in 3.17-rc5
Date: Tue, 16 Sep 2014 02:14:54 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.11.1409160209280.21050@adalberg.ut.ee> (raw)
Somewhere between 3.17.0-rc3 and 3.17.0-rc5 I started seeing dropped ssh
connections to a couple of test servers with dual AthlonMP (32-bit) and
3C90x family of NICs (3Com Corporation 3c980-C 10/100baseTX NIC
[Python-T] (rev 78) in one server and 3Com Corporation 3c905C-TX/TX-M
[Tornado] (rev 78) in the other server). Bisect leads to the following
commit:
98ea232cf63961fad734cc8c5e07e8915ec73073 is the first bad commit
commit 98ea232cf63961fad734cc8c5e07e8915ec73073
Author: Neil Horman <nhorman@tuxdriver.com>
Date: Thu Sep 4 06:13:38 2014 -0400
3c59x: avoid panic in boomerang_start_xmit when finding page address:
...
--
Meelis Roos (mroos@linux.ee)
next reply other threads:[~2014-09-15 23:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 23:14 Meelis Roos [this message]
2014-09-16 10:17 ` Neil Horman
2014-09-16 10:32 ` Meelis Roos
2014-09-16 14:31 ` Neil Horman
2014-09-16 14:32 ` [RFC PATCH] 3c59x: Add dma error checking and recovery Neil Horman
2014-09-16 20:29 ` bisected regression: 3c59x corrupts packets in 3.17-rc5 David Miller
2014-09-17 10:27 ` Neil Horman
2014-09-17 12:43 ` mroos
2014-09-17 12:56 ` Neil Horman
2014-09-17 13:04 ` [PATCH 1/2] 3c59x: Add dma error checking and recovery Neil Horman
2014-09-17 13:04 ` [PATCH 2/2] 3c59x: Fix bad offset spec in skb_frag_dma_map Neil Horman
2014-09-19 20:29 ` David Miller
2014-09-19 20:29 ` [PATCH 1/2] 3c59x: Add dma error checking and recovery David Miller
2014-09-20 1:19 ` Neil Horman
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=alpine.LRH.2.11.1409160209280.21050@adalberg.ut.ee \
--to=mroos@linux.ee \
--cc=klassert@mathematik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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
all inboxes | Powered by JetHome®