On Mon, Dec 15, 2008 at 11:36:37AM -0700, Aaron D. Johnson wrote: > Package: linux-image-2.6.26-1-mckinley > Version: 2.6.26-11 > Severity: grave > Justification: renders package unusable > > Attempting to boot linux-image-2.6.26-1-mckinley (2.6.26-11) as an HP > Integrity Virtual Machines guest OS results in a panic during network > startup. Console messages leading up to this: > > [...] > [16578579.202741] EXT3 FS on dm-1, internal journal > [16578579.204938] EXT3-fs: mounted filesystem with ordered data mode. > done. > Activating swapfile swap...[16578579.463160] Adding 4194272k swap on > /dev/mapper/vg00-swap. Priority:-1 extents:1 across:4194272k > done. > Setting up networking.... > Configuring network interfaces...[16578581.213754] e1000: eth0: > e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None > [16578582.433694] NET: Registered protocol family 10 > [16578582.437702] lo: Disabled Privacy Extensions > [16578582.580016] Entered OS MCA handler. PSP=fff2e12c cpu=1 monarch=1 > [16578582.580019] All OS MCA slaves have reached rendezvous > [16578582.607085] mlogbuf_finish: printing switched to urgent mode, > MCA/INIT might be dodgy or fail. > [16578582.611888] Delaying for 5 seconds...
I've got a theory - can you search the /var/log/kern.log* files on this guest for any Oops messages? Do you recall experiencing a hang during your kernel upgrade? I'm wondering if there was an oops at the time you upgraded your kernel package. Also, can you mount your efi partition and capture the md5sums of the files under /boot/efi/efi/debian? If my theory is correct, you may be able to get back up and running by booting an older kernel (if you have one), running 'elilo', then booting back into the 2.6.26-11 kernel. -- dann frazier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org