On Feb 21, 2007, at 9:41 AM, David N. Lombard wrote:
> Greg Kurtzer wrote:
>> I am seeing an issue where a network device (e1000) won't come up
>> after a kexec.
>> Booted into newly kexec'ed OS I am get the following error when I
>> `modprobe e1000`:
>> e1000: EEPROM initialization failed
>> e1000: probe of 000:07:07.0 failed with error -5
>> My kexec line looks like:
>> kexec --initrd=/vnfs.img --force --append="masterip=${MASTERIP}
>> noapic" /vmlinuz
>
> I've been using kexec on 2.6.14 (patched for later--but not latest--
> e1000 drivers) and 2.6.18 as-is; have not had any problems w/ e1000
> devices coming up.
>
> In any event, patch in the latest e1000 driver from http://
> e1000.sourceforge.net on your kernel or try a 2.6.18 kernel.
>
> The only kexec kernel patches used were some fairly old (like over
> a year ago) from Vivek
Ahh, great idea!
BTW, are you referring to the kernel that is running the kexec or the
kexec'ed kernel (in this case /vmlinuz)? I won't have control over
the secondary kernel because people tend to throw all sorts of
distributions and kernels onto Perceus, but the "host" kernel I can
update. Presently, the kexec kernel is 2.6.19.3, and have been
meaning to update to 2.6.19.4. I will look into the e1000 update then
and see if it is applicable. :)
note, I didn't have this problem with the 2.6.16 kernel that I ran
previously, but I required the newer drivers in 2.6.19 for some of
the newest cluster/node hardware.
I probably should have mentioned the kernel versions that I was
using... ;)
Many thanks!
Greg
--
Greg Kurtzer
I believe the world would be a better place if people didn't
believe in their beliefs. -- gmk
_______________________________________________
fastboot mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/fastboot
