netdev - loosing IPMI-card by loading netconsole

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 14 May 2010 15:45:44 +0200
From:	Henning Fehrmann <henning.fehrmann@....mpg.de>
To:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Cc:	Jesse Brandeburg <jesse.brandeburg@...el.com>,
	Bruce Allan <bruce.w.allan@...el.com>,
	PJ Waskiewicz <peter.p.waskiewicz.jr@...el.com>,
	John Ronciak <john.ronciak@...el.com>, netdev@...r.kernel.org,
	Matt Mackall <mpm@...enic.com>,
	Carsten Aulbert <carsten.aulbert@....mpg.de>,
	Tejun Heo <tj@...nel.org>
Subject: loosing IPMI-card by loading netconsole

Hello,

We have SuperMicro PDSM 2+ boards together with 82573E and 82573L Intel NICs.
Additional we have IPMI cards which are tunneled via the 82573E NIC.

We are using the e1000e driver for NICs together with the netconsole driver.
(netconsole netconsole=4444@...ent_IP/eth1,514@...ver_IP/server_MAC). Netconsole
is using the NIC which is NOT used by the IPMI card.

Usually we are able to access the IPMI card remotely with ipmitools.

Having the kernel 2.6.27.39 installed everything worked together, the NICs, remotely 
accessing the IPMI cards and netconsole.

The driver version of e1000e is 0.3.3.3-k6. 

Using a more recent kernel: 2.6.32.7 we lost the ability of remotely accessing the IPMI card
when the netconsole driver is loaded. 
The IPMI card is accessible before the netconsole driver is loaded and disappears 
once we use netconsole. Even unloading netconsole does not help then.

We get the IPMI card back when 'removing' eth0:
echo 1 > /sys/devices/pci0000:00/0000:00:1c.4/0000:0d:00.0/remove

0d:00.0 is eth0.

The version of the e1000e driver is 1.0.2-k2.

I compiled and loaded a later version of this driver (1.1.19) without solving this problem.

For eth0 (82573E) we have a firmware version 0.15-4 installed and for eth1 we use the firmware 
version 0.5-7. But this is the same for both kernel versions. 

Do you have an idea? 

Thank you and cheers,
Henning

--
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