On 11/9/2011 9:56 PM, David Howland wrote: > On 11/9/2011 10:17 PM, Stan Hoeppner wrote: >> On 11/9/2011 7:55 PM, David Howland wrote: >>> ========8<================= >>> kernel:[ 1919.981706] general protection fault: 0000 [#1] SMP >>> kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent >>> kernel:[ 1919.981870] Stack: >>> kernel:[ 1919.981893] Call Trace: >>> kernel:[ 1919.982020] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00 >>> 00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db >>> 74 0c 8b 42 14<48> 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44 >>> 89 ee 83 >> >> Where's the call trace? >> > > Here's the full syslog dump:
<snipped log> See if you can fix it by backing these 3 out to the previous version you had installed: [UPGRADE] xen-hypervisor-4.0-amd64 4.0.1-2 -> 4.0.1-4 [UPGRADE] xen-utils-4.0 4.0.1-2 -> 4.0.1-4 [UPGRADE] xenstore-utils 4.0.1-2 -> 4.0.1-4 Post the circumstances/history and a copy of the error log to LKML and the Xen list. In the mean time, check your filesystems to make sure none of your VM image files (or anyhting else) didn't get corrupted when the power died, or as a result of the upgrade. It would probably be a good idea to check out your hardware as well. Power outages often included spikes and surges before it completely goes dark. Assuming you're jacked into a good quality known-to-be-working UPS, damage to the machine, or storage array, is less likely to be a factor here. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ebb50a0.30...@hardwarefreak.com
