[PATH 1/1] Kexec jump - v2 - kexec jump

Lombard, David N dnlombar at ichips.intel.com
Wed Aug 15 14:44:41 EDT 2007


Are you still having problem w/ kexec and the Intel NIC?  What kernel
are you trying to kexec?  There's a problem when placing the e1000
into D3hot when an older kernel is the target of the kexec.  The problem
is manifested by the BARs being 0 in the kexec'd kernel.  We've checked
the PCI specs and believe the e1000 is behaving in a compliant way.  
We've seen this when trying to use kexec to boot any RHEL4 (2.6.9-basis)
kernel; I've not seen it when trying to kexec 2.6.14 or later kernels.

We see work was done in later kernels to properly handle the D3hot to D0
transition that's so problematic to 2.6.9.  And ugly hack that works
around this problem is to not put the NIC in D3hot if we know we're going
to kexec an older kernel--fortunately, this appears to be safe even when a
newer kernel, that doesn't have that problem, is to be started.  I
published that ugly nasty patch to the kboot list as that's the
environment whence we ran into the problem and it only affects older

I'll be happy to provide more detail if needed.

David N. Lombard, Intel, Irvine, CA
I do not speak for Intel Corporation; all comments are strictly my own.

More information about the kexec mailing list