Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752841Ab2JAJdL (ORCPT ); Mon, 1 Oct 2012 05:33:11 -0400 Received: from mms2.broadcom.com ([216.31.210.18]:4453 "EHLO mms2.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752487Ab2JAJdJ (ORCPT ); Mon, 1 Oct 2012 05:33:09 -0400 X-Server-Uuid: 4500596E-606A-40F9-852D-14843D8201B2 Subject: Re: tg3 driver upgrade (Linux 2.6.32 -> 3.2) breaks IBM Bladecenter SoL From: "Michael Chan" To: "Ferenc Wagner" cc: netdev@vger.kernel.org, "Matt Carlson" , "Grant Likely" , "Rob Herring" , linux-kernel@vger.kernel.org In-Reply-To: <87txuhho5z.fsf@lant.ki.iif.hu> References: <87txuhho5z.fsf@lant.ki.iif.hu> Date: Mon, 1 Oct 2012 02:33:02 -0700 Message-ID: <1349083982.5420.16.camel@LTIRV-MCHAN1.corp.ad.broadcom.com> MIME-Version: 1.0 X-WSS-ID: 7C77BD7B3OW601841-01-01 Content-Type: text/plain; charset=cp1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1046 Lines: 26 On Fri, 2012-09-28 at 22:45 +0200, Ferenc Wagner wrote: > 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. 2.6.32 to 3.2 is a big jump. Can you narrow this down further? It will be hard for us to find a HS20 with 5704 to test this. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/