lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 30 Sep 2011 10:06:25 +0200 From: Arkadiusz Miśkiewicz <a.miskiewicz@...il.com> To: "Matt Carlson" <mcarlson@...adcom.com> Cc: "Michael Chan" <mchan@...adcom.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: Re: tg3: BMC stops responding in 3.0 On Friday 30 of September 2011, Matt Carlson wrote: > On Mon, Sep 26, 2011 at 11:31:33AM -0700, Arkadiusz Mi??kiewicz wrote: > > On Monday 26 of September 2011, Matt Carlson wrote: > > > On Fri, Sep 23, 2011 at 12:45:50PM -0700, Arkadiusz Mi??kiewicz wrote: > > > > Hi, > > > > > > > > I was using 2.6.38.8 and recently tried to switch to 3.0.4 on Tyan > > > > S2891 platform. > > > > > > > > This platform uses tg3: > > > > tg3 0000:0a:09.1: eth1: Tigon3 [partno(BCM95704) rev 2003] > > > > (PCIX:133MHz:64- bit) MAC address 00:e0:81:33:5e:af > > > > tg3 0000:0a:09.1: eth1: attached PHY is 5704 (10/100/1000Base-T > > > > Ethernet) (WireSpeed[1], EEE[0]) > > > > tg3 0000:0a:09.1: eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] > > > > TSOcap[1] tg3 0000:0a:09.1: eth1: dma_rwctrl[769f4000] > > > > dma_mask[64-bit] > > > > > > > > With 2.6.38.8 everything was working fine. With 3.0.4 there is a > > > > problem. As soon as tg3 module is loaded or eth0 configured (can't > > > > tell which one since the machine is 400km away from me and I have no > > > > way to play with it other than ipmi or ssh) BMC stops responding (so > > > > all ipmitool commands over LAN stop working). Normal tg3 activity is > > > > not affected - I can ssh-in without a problem etc but ipmi over lan > > > > doesn't work. > > > > > > > > From ssh console "ipmitool lan print" works, shows data but for > > > > example after "ipmitool mc reset cold" it doesn't recover - ipmitool > > > > returns "Invalid channel: 255". I have to reboot to 2.6.38.8 and > > > > then issue "ipmitool mc reset cold" to recover. > > > > > > > > Any idea which tg3 change could break this? Can't bisect this due > > > > remote access only. > > > > > > > > I was hoping that maybe 9e975cc291d80d5e4562d6bed15ec171e896d69b > > > > "tg3: Fix io failures after chip reset" will fix things for me but no > > > > - this doesn't help. > > > > > > What version of the tg3 driver are you working with? > > > > The one in 3.0.4 kernel. I think it's 3.119 (at least modinfo says so). > > Unfortunately there were a lot of changes between 3.117 and 3.119(+). > Is there any way you can narrow down the gap? The machines are 400km away from me and it's hard to debug that way then ipmi/network conectivity is in stake :-/ I could try some form of bisecting but need to know if all git versions between 3.117 and 3.119 were known to be safe and working? I don't want to loose any conectivity to this machine. I was going to try 2.6.39 but it looks like it also uses 3.117 driver. -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/ -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists