From: Ferenc Wagner <wferi@niif.hu>
To: netdev@vger.kernel.org
Cc: Matt Carlson <mcarlson@broadcom.com>,
Michael Chan <mchan@broadcom.com>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
linux-kernel@vger.kernel.org, wferi@niif.hu
Subject: tg3 driver upgrade (Linux 2.6.32 -> 3.2) breaks IBM Bladecenter SoL
Date: Fri, 28 Sep 2012 22:45:28 +0200 [thread overview]
Message-ID: <87txuhho5z.fsf@lant.ki.iif.hu> (raw)
Hi,
Upgrading the kernel on our HS20 blades resulted in their SoL (serial
over LAN) connection being broken. The disconnection happens when eth0
(the interface involved in SoL) is brought up during the boot sequence.
If I later "ip link set eth0 down", then the connection is restored, but
"ip link set eth0 up" breaks it again on 3.2. ethtool -a, -c, -g, -k
and -u show no difference; ethtool -i on the 2.6.32 kernel reports:
driver: tg3
version: 3.116
firmware-version: 5704s-v3.38, ASFIPMIs v2.47
bus-info: 0000:05:01.0
In the 3.2 kernel the driver version is 3.121. In the output of lspci
-vv only the Interrupt line shows variability. I'd be grateful for any
workaround suggestion; I understand that is't not easy given the lack of
information about the SoL implementation, but maybe somebody can guess
what changed in the driver which could affect it this way.
--
Regards,
Feri.
next reply other threads:[~2012-09-28 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 20:45 Ferenc Wagner [this message]
2012-10-01 9:33 ` Michael Chan
2012-10-02 9:31 ` Ferenc Wagner
2012-10-02 12:07 ` Ferenc Wagner
2012-10-02 15:03 ` Michael Chan
2012-10-02 16:49 ` Ferenc Wagner
2012-10-02 17:06 ` Michael Chan
2012-10-02 18:49 ` Ferenc Wagner
2012-10-02 19:06 ` Michael Tokarev
2012-10-03 0:17 ` Ben Hutchings
2012-10-03 0:47 ` David Miller
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=87txuhho5z.fsf@lant.ki.iif.hu \
--to=wferi@niif.hu \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=rob.herring@calxeda.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®