Re: Recent update of Xen packages causes kernel panic with HVM domU
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: [#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: 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
Re: Recent update of Xen packages causes kernel panic with HVM domU
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: [#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: Nov 9 16:45:32 rackable kernel: [ 1919.981706] general protection fault: [#1] SMP Nov 9 16:45:32 rackable kernel: [ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent Nov 9 16:45:32 rackable kernel: [ 1919.981717] CPU 2 Nov 9 16:45:32 rackable kernel: [ 1919.981720] Modules linked in: tun nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_physdev ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative parport_pc ppdev lp parport nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs xen_evtchn xenfs binfmt_misc bridge stp fuse loop ioatdma radeon ttm drm_kms_helper i2c_i801 drm i2c_algo_bit rng_core pcspkr dca evdev i2c_core i5000_edac edac_core i5k_amb psmouse serio_raw processor button acpi_processor shpchp pci_hotplug ext3 jbd mbcache dm_mod sd_mod crc_t10dif uhci_hcd ata_generic ata_piix ehci_hcd libata scsi_mod usbcore nls_base e1000e thermal thermal_sys [last unloaded: scsi_wait_scan] Nov 9 16:45:32 rackable kernel: [ 1919.981816] Pid: 24, comm: xenwatch Not tainted 2.6.32-5-xen-amd64 #1 S5000PSL Nov 9 16:45:32 rackable kernel: [ 1919.981819] RIP: e030:[] [] __kmalloc_track_caller+0xcd/0x13c Nov 9 16:45:32 rackable kernel: [ 1919.981829] RSP: e02b:8803ea52bb10 EFLAGS: 00010002 Nov 9 16:45:32 rackable kernel: [ 1919.981832] RAX: RBX: 331474c384d0f7d9 RCX: 0008 Nov 9 16:45:32 rackable kernel: [ 1919.981835] RDX: 880013216090 RSI: 00d0 RDI: 0003 Nov 9 16:45:32 rackable kernel: [ 1919.981838] RBP: 0200 R08: 80d0 R09: 8803ea52bdd7 Nov 9 16:45:32 rackable kernel: [ 1919.981841] R10: R11: 000186a0 R12: 8146bf10 Nov 9 16:45:32 rackable kernel: [ 1919.981843] R13: 00d0 R14: 00d0 R15: 0008 Nov 9 16:45:32 rackable kernel: [ 1919.981851] FS: 7fbc8fe9d700() GS:880013204000() knlGS: Nov 9 16:45:32 rackable kernel: [ 1919.981854] CS: e033 DS: ES: CR0: 8005003b Nov 9 16:45:32 rackable kernel: [ 1919.981857] CR2: 7fbc8f747000 CR3: 00030f11a000 CR4: 2660 Nov 9 16:45:32 rackable kernel: [ 1919.981861] DR0: DR1: DR2: Nov 9 16:45:32 rackable kernel: [ 1919.981864] DR3: DR6: 0ff0 DR7: 0400 Nov 9 16:45:32 rackable kernel: [ 1919.981868] Process xenwatch (pid: 24, threadinfo 8803ea52a000, task 8803ea4f3880) Nov 9 16:45:32 rackable kernel: [ 1919.981870] Stack: Nov 9 16:45:32 rackable kernel: [ 1919.981872] 8803ea4f3880 81141305 000881044ced 0008 Nov 9 16:45:32 rackable kernel: [ 1919.981878] <0> 8803 8803 0001 8803ea52bc28 Nov 9 16:45:32 rackable kernel: [ 1919.981885] <0> 41ed 810c846f 0004 Nov 9 16:45:32 rackable kernel: [ 1919.981893] Call Trace: Nov 9 16:45:32 rackable kernel: [ 1919.981900] [] ? sysfs_new_dirent+0x2a/0xf7 Nov 9 16:45:32 rackable kernel: [ 1919.981906] [] ? kstrdup+0x2b/0x40 Nov 9 16:45:32 rackable kernel: [ 1919.981910] [] ? sysfs_new_dirent+0x2a/0xf7 Nov 9 16:45:32 rackable kernel: [ 1919.981914] [] ? create_dir+0x2d/0x7c Nov 9 16:45:32 rackable kernel: [ 1919.981918] [] ? sysfs_create_dir+0x35/0x4a Nov 9 16:45:32 rackable kernel: [ 1919.981924] [] ? kobject_get+0x12/0x17 Nov 9 16:45:32 rackable kernel: [ 1919.981928] [] ? kobject_add_internal+0xcb/0x181 Nov 9 16:45:32 rackable kernel: [ 1919.981932] [] ? kobject_add+0x74/0x7c Nov 9 16:45:32 rackable kernel: [ 1919.981943] [] ? xen_force_evtchn_callback+0x9/0xa Nov 9 16:45:32 rackable kernel: [ 1919.981948] [] ? check_events+0x12/0x20 Nov 9 16:45:32 rackable kernel: [ 1919.981952] [] ? __kmalloc+0x12f/0x141 Nov 9 16:45:32 rackable kernel: [ 1919.981958] [] ? device_private_init+0x13/0x45 Nov 9 16:45:32 rackable kernel: [ 1919.981963] [] ? device_add+0xce/0x537 Nov 9 16:45:32 rackable kernel: [ 1919.981969] [] ? backend_bus_id+0x10f/0x132 Nov 9 16:45:32 rackable kernel: [ 1919.981973] [] ? xenbus_probe_node+0x13b/0x1d4 Nov 9 16:45:32 rackable kernel: [ 1919.981977] [] ? cmp_dev+0x0/0x39 Nov 9 16:45:32 rackabl
Re: Recent update of Xen packages causes kernel panic with HVM domU
On 11/9/2011 7:55 PM, David Howland wrote: > Recently I lost power (along with much of New England) for eight days. > When the juice started flowing again, I restarted my Xen server (Debian > Squeeze, dual Xeon (8 cores), 16GB RAM), which came up fine but had a > pile of package updates pending... > 8<= > kernel:[ 1919.981706] general protection fault: [#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? -- 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/4ebb4248.9010...@hardwarefreak.com
Recent update of Xen packages causes kernel panic with HVM domU
Recently I lost power (along with much of New England) for eight days. When the juice started flowing again, I restarted my Xen server (Debian Squeeze, dual Xeon (8 cores), 16GB RAM), which came up fine but had a pile of package updates pending... === [UPGRADE] libavcodec52 4:0.5.4-1 -> 4:0.5.5-1 [UPGRADE] libavformat52 4:0.5.4-1 -> 4:0.5.5-1 [UPGRADE] libavutil49 4:0.5.4-1 -> 4:0.5.5-1 [UPGRADE] libnss3-1d 3.12.8-1+squeeze3 -> 3.12.8-1+squeeze4 [UPGRADE] libpostproc51 4:0.5.4-1 -> 4:0.5.5-1 [UPGRADE] libpq5 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1 [UPGRADE] libswscale0 4:0.5.4-1 -> 4:0.5.5-1 [UPGRADE] libxenstore3.0 4.0.1-2 -> 4.0.1-4 [UPGRADE] postgresql 8.4.8-0squeeze2 -> 8.4.9-0squeeze1 [UPGRADE] postgresql-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1 [UPGRADE] postgresql-client 8.4.8-0squeeze2 -> 8.4.9-0squeeze1 [UPGRADE] postgresql-client-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1 [UPGRADE] postgresql-contrib 8.4.8-0squeeze2 -> 8.4.9-0squeeze1 [UPGRADE] postgresql-contrib-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1 [UPGRADE] postgresql-doc 8.4.8-0squeeze2 -> 8.4.9-0squeeze1 [UPGRADE] postgresql-doc-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1 [UPGRADE] tzdata 2011m-0squeeze1 -> 2011n-0squeeze1 [UPGRADE] tzdata-java 2011m-0squeeze1 -> 2011n-0squeeze1 [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 === I did an "aptitude safe-upgrade" without even really looking at it. At the time, I had an HVM domU running. The upgrade crashed the system. I'm pretty sure it crashed while configuring the xen-hypervisor-4.0-amd64 package. When I brought it back up, I ran a "dpkg --configure -a" to finish the job. However, now, when I try to use my Windows HVM, I always get a kernel panic dealing with the vbd. For example... 8<= kernel:[ 1919.981706] general protection fault: [#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 kernel:[ 1920.014542] general protection fault: [#2] SMP kernel:[ 1920.014550] last sysfs file: /sys/devices/vbd-3-832/uevent kernel:[ 1920.014729] Stack: kernel:[ 1920.014752] Call Trace: kernel:[ 1920.014836] 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 8<= Then the system destabilizes. I have a pretty common setup. I can't be the only one! What the heck happened with those updates?!? Please help me out! thanks, -d -- 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/4ebb2f08.4060...@fastmail.fm
