[BUG] e1000 on reboot/boot path.

[ebiederm@xmission.com (Eric W. Biederman)]

Mike Snitzer <snitzer@gmail.com> writes:

So you have a problem that the e1000 driver does not properly
shutdown the e1000 in the reboot path (no code).  But it does properly
cleanup when you remove the module.

>  I've been bitten by this issue
> with the e1000 (<= 5.2.52-k4) driver.  With an "Ethernet controller:
> Intel Corp. 82546EB Gigabit Ethernet Controller", device id# 1010, I
> get:
> 
> Intel(R) PRO/1000 Network Driver - version 5.2.30.1-k1
> Copyright (c) 1999-2004 Intel Corporation.
> PCI: Enabling device 04:05.0 (0000 -> 0003)
> Uhhuh. NMI received for unknown reason 31.
> Dazed and confused, but trying to continue
> Do you have a strange power saving mode enabled?
> The EEPROM Checksum Is Not Valid
> PCI: Enabling device 04:05.1 (0000 -> 0003)
> The EEPROM Checksum Is Not Valid
> 
> The 5.2.52-k4 has toned down, yet basically the same, errors.  This
> message results when kexec'ing from a 2.6.7 kernel with the e1000
> builtin; once I made the e1000 a module and unloaded it prior to
> kexec'ing all was fine.
> 
> Looking at the e1000 source it is clear that removing the e1000 module
> triggers e1000_remove() via module_exit()'s pci_unregister_driver(). 
> Once the e1000 let go of the PCI resources the kexec'd kernel's e1000
> driver was happy.  Kexec looks to call all loaded modules' shutdown()
> routine.  The e1000 doesn't have shutdown(); but it does have a
> remove().
> 

Eric