WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: win-pv assertion failed while migrating

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: win-pv assertion failed while migrating
From: alice wan <wanjia19870902@xxxxxxxxx>
Date: Thu, 17 Feb 2011 10:39:05 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 16 Feb 2011 18:40:18 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JGK/51W5BJJ5lVICnn0w0Kj7mJ3sYCN9s5vWsuWrSrw=; b=FqeaydELeMyY6+1g3C0PSqvcgc0NTqMj8f6QZkwPcKqjXPYO3e6wNlNdID2cTaYxdW t1F21XvJwVzD3ZkfGklopfzhUlX54G/w6c7Rkl8l6ti99SYZ4RFJONaXZFQ00HP0E8dK p/ZRrpUOS17NVqv82ssnBziGRzUOPHo2+uxTA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=lH0BuZG2ZkHtvRc4dPcby7jbf9ZD3/vFl4VsryndmH3kjpLeyNXPM8sCmwSpYY6rN0 IbnpPSKs/A6ceFB3XLAJsF0xnt43UUp/3yY0tV9KleZLWNtpd7EjIy16KLm5XpTdEp62 3h7CeAHKgCk702bHx4tKq6GofCr2BNGtqLlk4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01C5563F@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTi=0_Lago4q7vnj67rB_yZLhaJeSKGnL5zSK71iv@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01C55475@trantor> <AANLkTin33XbNLUaJTQBQee+u0w4FOw_aMRRx3o3juDij@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01C554C2@trantor> <AANLkTi=f5T0Qw92dAFoCk3Ywxp+UGXKByVUA-Rb_kqmg@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01C554F0@trantor> <AANLkTikgkHBSxnrUSUKXfTtK2kLuseJKmXPW0MAj9m37@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01C55501@trantor> <AANLkTi=zk0zayUw2+kPtYHyW_ZoL-yKfObxRj1+w3c1U@xxxxxxxxxxxxxx> <AANLkTimO6evTZ+jSD-YizMFk0N7gaqhsDL-2z1rAUUh-@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01C55590@trantor> <AANLkTinU3H45m-P2vTUZWjz1NV9VxF2Nig=UgRDxWcMx@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01C5563F@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
well, Assertion failure appeared again and vm also blue screen of death after migrating 90 times
 
XenPCI <-- hvm_set_parameter
 140 XenPCI     hvm_set_parameter(HVM_PARAM_CALLBACK_IRQ, 28) = 0
 141 XenPCI --> EvtChn_AllocIpi
 142 XenPCI <-- EvtChn_AllocIpi
 143 XenPCI --> EvtChn_BindDpc
 144 XenPCI <-- EvtChn_BindDpc
 145 XenPCI     pdo_event_channel = 5
 146 XenPCI <-- EvtChn_Init
 147 XenPCI <-- XenPci_Suspend0
 148 XenPCI --> XenPci_SuspendN
 149 XenPCI     doing nothing on cpu N
 150 XenPCI <-- XenPci_SuspendN
 151 XenPCI <-- XenPci_HighSyncCallFunctionN
 152 XenPCI <-- XenPci_HighSyncCallFunction0
 153 XenPCI     Waiting for highsync_complete_event
 154 XenVbd --> HwScsiStartIo (Suspending/Resuming)
 155 XenPCI <-- XenPci_HighSync
 156 XenVbd <-- HwScsiStartIo (Suspending/Resuming)
 157 XenPCI --> XenBus_Resume
 158 XenPCI --> hvm_get_parameter
 159 XenPCI HYPERVISOR_hvm_op retval = 0
 160 XenPCI <-- hvm_get_parameter
 161 XenPCI --> hvm_get_parameter
 162 XenPCI HYPERVISOR_hvm_op retval = 0
 163 XenPCI <-- hvm_get_parameter
 164 XenPCI --> EvtChn_BindDpc
 165 XenPCI <-- EvtChn_BindDpc
 166 XenPCI     Adding watch for path = control/sysrq
 167 XenPCI     Adding watch for path = control/shutdown
 168 XenPCI --> XenPci_SysrqHandler
 169 XenPCI     Adding watch for path = device
 170 XenPCI     SysRq Value = (null)
 171 XenPCI <-- XenPci_SysrqHandler
 172 XenPCI     Adding watch for path = memory/target
 173 XenPCI --> XenPci_ShutdownHandler
 174 XenPCI     Adding watch for path = control/shutdown
 175 Error reading shutdown path - ENOENT
 176 XenPCI <-- XenPci_ShutdownHandler
 177 XenPCI <-- XenBus_Resume
 178 XenPCI --> XenPci_DeviceWatchHandler
 179 XenPCI     suspend event channel = 6
 180 XenPCI <-- XenPci_DeviceWatchHandler
 181 XenPCI --> XenPci_BalloonHandler
 182 XenPCI --> EvtChn_BindDpc
 183 XenPCI <-- EvtChn_BindDpc
 184 XenPCI     Resuming child
 185 XenPCI     target memory value = 512 (524288)
 186 XenPCI --> XenPci_Pdo_Resume
 187 XenPCI     path = device/vbd/768
 188 XenPCI <-- XenPci_BalloonHandler
 189 XenPCI --> XenPci_GetBackendAndAddWatch
 190 XenPCI --> XenPci_IoWatch
 191 XenPCI     Got balloon event, current = 512, target = 512
 192 XenPCI     found pending read - MinorFunction = 0, length = 1024
 193 XenPCI     No change to memory
 194 XenPCI <-- XenBus_ProcessReadRequest
 195 XenPCI <-- XenPci_IoWatch
 196 XenPCI --> XenPci_EvtIoDefault
 197 XenPCI --> XenPci_DeviceWatchHandler
 198 XenPCI --> XenBus_EvtIoWrite
 199 XenPCI     33 bytes of write buffer remaining
 200 XenPCI     Rescanning child list
 201 XenPCI --> XenPci_EvtChildListScanForChildren
 202 XenPCI     completing request with length 33
 203 XenPCI <-- XenBus_EvtIoWrite
 204 XenPCI <-- XenPci_EvtIoDefault
 205 XenPCI     Found path = device/vbd/768
 206 XenPCI --> XenPci_EvtIoDefault
 207 XenPCI --> XenBus_EvtIoRead
 208 XenPCI     Found path = device/vif/0
 209 XenPCI     found pending read
 210 XenPCI <-- XenPci_EvtChildListScanForChildren
 211 XenPCI <-- XenBus_ProcessReadRequest
 212 XenPCI <-- XenPci_DeviceWatchHandler
 213 XenPCI <-- XenBus_EvtIoRead
 214 XenPCI <-- XenPci_EvtIoDefault
 215 XenPCI <-- XenPci_GetBackendAndAddWatch
 216 XenPCI --> XenPci_EvtIoDefault
 217 XenPCI --> XenPci_ChangeFrontendState
 218 XenPCI --> XenBus_EvtIoRead
 219 XenPCI --> XenPci_UpdateBackendState
 220 XenPCI <-- XenPci_ChangeFrontendState
 221 XenPCI     no data to read
 222 XenPCI     state unchanged
 223 XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
 224 XenPCI <-- XenBus_EvtIoRead
 225 XenPCI     XEN_INIT_TYPE_RING - ring-ref = 81F28000
 226 XenPCI <-- XenPci_EvtIoDefault
 227 XenPCI     XEN_INIT_TYPE_RING - ring-ref = 15803
 228 XenPCI --> XenPci_DeviceWatchHandler
 229 XenPCI <-- XenPci_DeviceWatchHandler
 230 XenPCI     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
 231 XenPCI --> XenPci_DeviceWatchHandler
 232 XenPCI <-- XenPci_DeviceWatchHandler
 233 XenPCI --> EvtChn_BindIrq
 234 XenPCI --> XenPci_DeviceWatchHandler
 235 XenPCI <-- EvtChn_BindIrq
 236 XenPCI <-- XenPci_DeviceWatchHandler
 237 XenPCI --> XenPci_ChangeFrontendStateMap
 238 XenPCI --> XenPci_ChangeFrontendState
 239 XenPCI --> XenPci_DeviceWatchHandler
 240 XenPCI <-- XenPci_DeviceWatchHandler
 241 XenPCI --> XenPci_UpdateBackendState
 242 XenPCI     Backend State Changed to Connected
 243 XenPCI <-- XenPci_UpdateBackendState
 244 XenPCI <-- XenPci_ChangeFrontendState
 245 XenPCI <-- XenPci_ChangeFrontendStateMap
 246 XenPCI --> XenPci_ChangeFrontendStateMap
 247 XenPCI <-- XenPci_ChangeFrontendStateMap
 248 XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
 249 XenPCI --> XenPci_ChangeFrontendState
 250 XenPCI --> XenPci_DeviceWatchHandler
 251 XenPCI <-- XenPci_ChangeFrontendState
 252 XenPCI <-- XenPci_DeviceWatchHandler
 253 XenPCI --> XenPci_Pdo_ChangeSuspendState
 254 XenPCI     setting pdo state to 2
 255 XenPCI     Notifying event channel 5
 256 XenPCI     EVT_ACTION_TYPE_SUSPEND
 257 XenVbd --> XenVbd_HwScsiInterrupt
 258 XenVbd     New pdo state SR_STATE_RESUMING
 259 XenVbd     XEN_INIT_TYPE_VECTORS
 260 XenVbd     XEN_INIT_TYPE_DEVICE_STATE - 82095B44
 261 XenVbd     XEN_INIT_TYPE_RING - ring-ref = 81F28000
 262 XenVbd     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
 263 XenVbd     XEN_INIT_TYPE_READ_STRING - device-type = disk
 264 XenVbd     device-type = Disk
 265 XenVbd     XEN_INIT_TYPE_READ_STRING - mode = w
 266 XenVbd     mode = w
 267 XenVbd     XEN_INIT_TYPE_READ_STRING - sectors = 104857600
 268 XenVbd     XEN_INIT_TYPE_READ_STRING - sector-size = 512
 269 XenVbd     XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11
 270 XenVbd     qemu_hide_flags_value = 3
 271 XenPCI --> EvtChn_PdoEventChannelDpc
 272 XenPCI     EVT_ACTION_TYPE_SUSPEND
 273 XenPCI <-- EvtChn_PdoEventChannelDpc
 274 XenPCI --> EvtChn_PdoEventChannelDpc
 275 XenPCI     fdo state set to 2
 276 XenPCI <-- EvtChn_PdoEventChannelDpc
 277 XenPCI <-- XenPci_Pdo_ChangeSuspendState
 278 XenPCI --> XenPci_Pdo_ChangeSuspendState
 279 XenPCI     setting pdo state to 0
 280 XenPCI     Notifying event channel 5
 281 XenPCI     EVT_ACTION_TYPE_SUSPEND
 282 XenVbd --> XenVbd_HwScsiInterrupt
 283 XenVbd     New pdo state 0
 284 XenVbd     New pdo state 0
 285 XenPCI --> EvtChn_PdoEventChannelDpc
 286 XenPCI     EVT_ACTION_TYPE_SUSPEND
 287 XenPCI <-- EvtChn_PdoEventChannelDpc
 288 XenPCI --> EvtChn_PdoEventChannelDpc
 289 XenPCI     fdo state set to 0
 290 XenPCI <-- EvtChn_PdoEventChannelDpc
 291 XenPCI <-- XenPci_Pdo_ChangeSuspendState
 292 XenPCI <-- XenPci_Pdo_Resume
 293 XenPCI     Resuming child
 294 XenPCI --> XenPci_Pdo_Resume
 295 XenPCI     path = device/vif/0
 296 XenPCI --> XenPci_GetBackendAndAddWatch
 297 
 298 *** Assertion failed: xpdd->xb_msg_offset + msg_len <= sizeof(xsd_sockmsg_t) + xpdd->xb_msg->len
 299 ***   Source File: e:\win-pvdrivers_852\win-pvdrivers.hg\xenpci\xenbus.c, line 303
 300 
 301 XenVbd --> DriverEntry
 302 XenVbd     IRQL = 31
 303 XenVbd     DriverObject = 00000000, RegistryPath = 00000000
 304 XenVbd --> XenVbd_HwScsiFindAdapter
 305 XenVbd     IRQL = 31
 306 XenVbd     xvdd = 8191C300
 307 XenVbd     BusInterruptLevel = 28
 308 XenVbd     BusInterruptVector = 01c
 309 XenVbd     NumberOfAccessRanges = 1
 310 XenVbd     RangeStart = 1f968000, RangeLength = 00001000
 311 XenVbd     XEN_INIT_TYPE_VECTORS
 312 XenVbd     XEN_INIT_TYPE_DEVICE_STATE - 82095B44
 313 XenVbd     XEN_INIT_TYPE_RING - ring-ref = 81F28000
 314 XenVbd     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
 315 XenVbd     XEN_INIT_TYPE_READ_STRING - device-type = disk
 316 XenVbd     device-type = Disk
 317 XenVbd     XEN_INIT_TYPE_READ_STRING - mode = w
 318 XenVbd     mode = w
 319 XenVbd     XEN_INIT_TYPE_READ_STRING - sectors = 104857600
 320 XenVbd     XEN_INIT_TYPE_READ_STRING - sector-size = 512
 321 XenVbd     XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11
 322 XenVbd     qemu_hide_flags_value = 3
 323 XenVbd     aligned_buffer_data = 8191E274
 324 XenVbd     aligned_buffer = 8191F000
 325 XenVbd     ConfigInfo->MaximumTransferLength = 4096
 326 XenVbd     ConfigInfo->NumberOfPhysicalBreaks = 0
 327 XenVbd     ConfigInfo->CachesData was initialised to 0
 328 XenVbd     Dma64BitAddresses not supported
 329 XenVbd <-- XenVbd_HwScsiFindAdapter
 330 XenVbd --> XenVbd_HwScsiInitialize
 331 XenVbd     IRQL = 31
 332 XenVbd     dump_mode = 1
 333 XenVbd <-- XenVbd_HwScsiInitialize
 334 XenVbd     Command = INQUIRY
 335 XenVbd --> XenVbd_HwScsiResetBus
 336 XenVbd     IRQL = 31
 337 XenVbd <-- XenVbd_HwScsiResetBus
 338 XenVbd     Command = SCSIOP_START_STOP_UNIT
 339 XenVbd     Command = READ_CAPACITY
 340 XenVbd <-- DriverEntry
 341 XenVbd     max_dump_mode_blocks = 8
 342 XenVbd     max_dump_mode_length = 4096
 343 
 344 *** Assertion failed: srb != NULL
 345 ***   Source File: e:\win-pvdrivers_852\win-pvdrivers.hg\xenvbd\xenvbd_scsiport.c, line 988
 346 
 347 XenNet --> XenNet_Shutdown
 348 XenNet <-- XenNet_Shutdown
 349 XenPCI     Bug check 0x0000008E (0x80000003, 0x80878113, 0x80898FB4, 0x00000000)
 350 Log-dirty command enable
 351 Log-dirty command disable
 


 
2011/2/16 James Harper <james.harper@xxxxxxxxxxxxxxxx>
I've just pushed a fix which seems to fix the problem - no leaking at
all so far.

James

> -----Original Message-----
> From: alice wan [mailto:wanjia19870902@xxxxxxxxx]
> Sent: Wednesday, 16 February 2011 13:44
> To: James Harper
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: win-pv assertion failed while migrating
>
> Assertion failure didn't appear, but vm still had problem after
migrating six
> hundred times.
>
> XenPCI <-- XenPci_ShutdownHandler
> XenPCI     Adding watch for path = control/shutdown
> XenPCI --> XenPci_DeviceWatchHandler
> XenPCI <-- XenPci_DeviceWatchHandler
> XenPCI <-- XenBus_Resume
> XenPCI --> XenPci_BalloonHandler
> XenPCI     suspend event channel = 6
> XenPCI --> EvtChn_BindDpc
> XenPCI <-- EvtChn_BindDpc
> XenPCI     target memory value = 512 (524288)
> XenPCI     Resuming child
> XenPCI --> XenPci_Pdo_Resume
> XenPCI <-- XenPci_BalloonHandler
> XenPCI     path = device/vbd/768
> XenPCI --> XenPci_UpdateBackendState
> XenPCI --> XenPci_GetBackendAndAddWatch
> XenPCI     Got balloon event, current = 512, target = 512
> XenPCI     No change to memory
> XenPCI --> XenPci_IoWatch
> XenPCI     found pending read - MinorFunction = 0, length = 1024
> XenPCI <-- XenBus_ProcessReadRequest
> XenPCI <-- XenPci_IoWatch
> XenPCI --> XenPci_EvtIoDefault
> XenPCI --> XenPci_DeviceWatchHandler
> XenPCI --> XenBus_EvtIoWrite
> XenPCI     33 bytes of write buffer remaining
> XenPCI     Rescanning child list
> XenPCI --> XenPci_EvtChildListScanForChildren
> XenPCI     completing request with length 33
> XenPCI <-- XenBus_EvtIoWrite
> XenPCI <-- XenPci_EvtIoDefault
> XenPCI     Found path = device/vbd/768
> XenPCI --> XenPci_EvtIoDefault
> XenPCI --> XenBus_EvtIoRead
> XenPCI     Found path = device/vif/0
> XenPCI     found pending read
> XenPCI <-- XenPci_EvtChildListScanForChildren
> XenPCI <-- XenBus_ProcessReadRequest
> XenPCI <-- XenPci_DeviceWatchHandler
> XenPCI <-- XenBus_EvtIoRead
> XenPCI <-- XenPci_EvtIoDefault
> XenPCI --> XenPci_EvtIoDefault
> XenPCI <-- XenPci_GetBackendAndAddWatch
> XenPCI --> XenBus_EvtIoRead
> XenPCI --> XenPci_ChangeFrontendState
> XenPCI     no data to read
> XenPCI --> XenPci_UpdateBackendState
> XenPCI <-- XenBus_EvtIoRead
> XenPCI <-- XenPci_ChangeFrontendState
> XenPCI <-- XenPci_EvtIoDefault
> XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
> XenPCI     state unchanged
> XenPCI     XEN_INIT_TYPE_RING - ring-ref = FED06000
> XenPCI --> XenPci_DeviceWatchHandler
> XenPCI     No free grant refs
> XenPCI <-- XenPci_DeviceWatchHandler
> XenPCI     Error
> XenPCI --> XenPci_ChangeFrontendState
> XenPCI --> XenPci_DeviceWatchHandler
> XenPCI <-- XenPci_ChangeFrontendState
> XenPCI <-- XenPci_DeviceWatchHandler
> XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers, status = c0000001
> XenPCI --> XenPci_ChangeFrontendState
> XenPCI --> XenPci_DeviceWatchHandler
> XenPCI <-- XenPci_DeviceWatchHandler
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     Backend State Changed to Closing
> XenPCI     Requesting eject
> XenPCI <-- XenPci_UpdateBackendState
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> Log-dirty command enable
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI     Suspend detected via Dpc
> XenPCI --> XenPci_SuspendResume
> XenPCI <-- XenPci_SuspendResume
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Still waiting for 4 (currently 5)...
> XenPCI --> XenPci_UpdateBackendState
> XenPCI     state unchanged
> XenPCI     Timed out waiting for 4!
> XenPCI     Failed to change frontend state to connected
> XenPCI <-- XenPci_Pdo_Resume
> XenPCI     Resuming child
> XenPCI --> XenPci_Pdo_Resume
> XenPCI     path = device/vif/0
> XenPCI <-- XenPci_Pdo_Resume
> XenPCI <-- XenPci_SuspendResume
>
>
> xenstore-ls /local/domain/635/device
> vfb = ""
>  0 = ""
>   state = "1"
>   backend-id = "0"
>   backend = "/local/domain/0/backend/vfb/635/0"
> console = ""
>  0 = ""
>   state = "1"
>   backend-id = "0"
>   backend = "/local/domain/0/backend/console/635/0"
> vbd = ""
>  768 = ""
>   backend-id = "0"
>   virtual-device = "768"
>   device-type = "disk"
>   state = "4"
>   backend = "/local/domain/0/backend/vbd/635/768"
> vif = ""
>  0 = ""
>   backend-id = "0"
>   mac = "00:16:3e:e0:00:13"
>   handle = "0"
>   state = "1"
>   backend = "/local/domain/0/backend/vif/635/0"
> suspend = ""
>  event-channel = "6"
>
>
> 2011/2/15 James Harper <james.harper@xxxxxxxxxxxxxxxx>
>
>
>       I have just pushed a fix. It was a stupid mistake on my part and
I
>       didn't notice it because Windows 2008 doesn't seem to crash on
ASSERT
>       failures.
>
>       Please try it now.
>
>       Thanks
>
>
>       James
>
>       > -----Original Message-----
>       > From: alice wan [mailto:wanjia19870902@xxxxxxxxx]
>
>       > Sent: Tuesday, 15 February 2011 19:20
>       > To: James Harper
>       > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>       > Subject: Re: win-pv assertion failed while migrating
>       >
>       > new problem appeared in the fix and only after migrate once,
it came
>       out.
>       >
>       > XenNet --> XenNet_SuspendResume
>       > XenNet     New state SR_STATE_RESUMING
>       > XenNet <-- XenNet_SuspendResume
>       > XenNet --> XenNet_ResumeWorkItem
>       > XenPCI --> EvtChn_PdoEventChannelDpc
>       >
>       > *** Assertion failed: !xi->resume_work_item
>       > ***   Source File:
e:\win-pvdrivers\win-pvdrivers.hg\xennet\xennet.c,
>       line 248
>       >
>       > XenPCI <-- EvtChn_PdoEventChannelDpc
>       > XenVbd --> DriverEntry
>       > XenVbd     IRQL = 31
>       > XenVbd     DriverObject = 00000000, RegistryPath = 00000000
>       > XenVbd --> XenVbd_HwScsiFindAdapter
>       > XenVbd     IRQL = 31
>       > XenVbd     xvdd = 8196B300
>       > XenVbd     BusInterruptLevel = 28
>       > XenVbd     BusInterruptVector = 01c
>       > XenVbd     NumberOfAccessRanges = 1
>       > XenVbd     RangeStart = 1f9eb000, RangeLength = 00001000
>       > XenVbd     XEN_INIT_TYPE_VECTORS
>       > XenVbd     XEN_INIT_TYPE_DEVICE_STATE - 820E93CC
>       > XenVbd     XEN_INIT_TYPE_RING - ring-ref = 815FC000
>       > XenVbd     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
>       > XenVbd     XEN_INIT_TYPE_READ_STRING - device-type = disk
>       > XenVbd     device-type = Disk
>       > XenVbd     XEN_INIT_TYPE_READ_STRING - mode = w
>       > XenVbd     mode = w
>       > XenVbd     XEN_INIT_TYPE_READ_STRING - sectors = 104857600
>       > XenVbd     XEN_INIT_TYPE_READ_STRING - sector-size = 512
>       > XenVbd     XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11
>       > XenVbd     qemu_hide_flags_value = 3
>       > XenVbd     aligned_buffer_data = 8196D274
>       > XenVbd     aligned_buffer = 8196E000
>       > XenVbd     ConfigInfo->MaximumTransferLength = 4096
>       > XenVbd     ConfigInfo->NumberOfPhysicalBreaks = 0
>       > XenVbd     ConfigInfo->CachesData was initialised to 0
>       > XenVbd     Dma64BitAddresses not supported
>       > XenVbd <-- XenVbd_HwScsiFindAdapter
>       > XenVbd --> XenVbd_HwScsiInitialize
>       > XenVbd     IRQL = 31
>       > XenVbd     dump_mode = 1
>       > XenVbd <-- XenVbd_HwScsiInitialize
>       > XenVbd     Command = INQUIRY
>       > XenVbd --> XenVbd_HwScsiResetBus
>       > XenVbd     IRQL = 31
>       > XenVbd <-- XenVbd_HwScsiResetBus
>       > XenVbd     Command = SCSIOP_START_STOP_UNIT
>       > XenVbd     Command = READ_CAPACITY
>       > XenVbd <-- DriverEntry
>       > XenVbd     max_dump_mode_blocks = 8
>       > XenVbd     max_dump_mode_length = 4096
>       >
>       > *** Assertion failed: srb != NULL
>       > ***   Source File:
>       e:\win-pvdrivers\win-pvdrivers.hg\xenvbd\xenvbd_scsiport.c,
>       > line 988
>       >
>       > XenNet --> XenNet_Shutdown
>       > XenNet <-- XenNet_Shutdown
>       > XenPCI     Bug check 0x0000007E (0x80000003, 0x80878113,
0xF88A566C,
>       > 0xF88A5368)
>       >
>       >
>       > 2011/2/15 alice wan <wanjia19870902@xxxxxxxxx>
>       >
>       >
>       >       I build from source. today, i'll use latest version to
test, if
>       there's
>       > any results, i'll let u know
>       >
>       >
>       >       2011/2/14 James Harper <james.harper@xxxxxxxxxxxxxxxx>
>       >
>       >
>       >               I've found a race in xennet that could cause the
>       problems you are
>       > seeing
>       >               and have pushed a fix, but it's not well tested.
From
>       what you've
>       > said I
>       >               think you can build from source. If not, I
should be
>       able to
>       > upload some
>       >               binaries tomorrow. Please let me know how your
testing
>       goes.
>       >
>       >
>       >               James
>       >
>       >               > -----Original Message-----
>       >               > From: alice wan
[mailto:wanjia19870902@xxxxxxxxx]
>       >
>       >               > Sent: Monday, 14 February 2011 18:01
>       >
>       >               > To: James Harper
>       >               > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>       >
>       >               > Subject: Re: win-pv assertion failed while
migrating
>       >               >
>       >               > serveral hundred times, not regular and vm
blue screen
>       of death
>       >               >
>       >               >
>       >               >
>       >               >
>       >               > 2011/2/14 James Harper
<james.harper@xxxxxxxxxxxxxxxx>
>       >               >
>       >               >
>       >               >       >
>       >               >       > yes, windows 2003-32.
>       >               >       >
>       >               >       > my test is migrate vm between host A
and host
>       B
>       >               >       > continually(xen4.0.0.0+2.6.31.13)
>       >               >       >
>       >               >       > Almost after automatic migrate script
ran for
>       one day,
>       > this
>       >               problem
>       >               >       appeared
>       >               >       >
>       >               >       > maybe i can also do some test on
>       xen4.0.1+2.6.32.x to
>       > check
>       >               whether it
>       >               >       matters
>       >               >       > kernel or pv driver.
>       >               >
>       >               >
>       >               >       So you are saying that it doesn't happen
>       immediately,
>       > only after
>       >               some
>       >               >       time? Do you know how many times?
>       >               >
>       >               >       Maybe I'm leaking a resource somewhere
every
>       time migrate
>       >               happens and
>       >               >       eventually it runs out...
>       >               >
>       >               >       James
>       >               >
>       >               >
>       >
>       >
>       >
>       >
>
>
>


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>