|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
James,
I have tried the latest version (gplpv_chk_wnet_x86_0.10.0.83.msi) on a Xen
3.3.1 system and I am seeing a system crash. I have copied windows debug log
for your reference. I have not seen a crash issue with the previous release of
gplpv driver. Is there a known issue with the latest release? Or any thing
extra I have to do to make it work?
Thanks
Manoj
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \\.\com8
Waiting to reconnect...
Connected to Windows Server 2003 3790 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: C:\WinDDK\6000\share\fw_vmegaraid\win_mfi_client\i386
Executable search path is: C:\WinDDK\6000\share\fw_vmegaraid\win_mfi_client\i386
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrnlpa.exe -
Windows Server 2003 Kernel Version 3790 UP Free x86 compatible
Built by: 3790.srv03_sp2_rtm.070216-1710
Kernel base = 0x80800000 PsLoadedModuleList = 0x8089ffa8
System Uptime: not available
XenPCI --> DriverEntry
XenPCI --> XenPci_FixLoadOrder
XenPCI Current Order:
XenPCI System Reserved
XenPCI Dummy Group
XenPCI WdfLoadGroup
XenPCI XenPCI Group
XenPCI Boot Bus Extender
XenPCI System Bus Extender
XenPCI SCSI miniport
XenPCI Port
XenPCI Primary Disk
XenPCI SCSI Class
XenPCI SCSI CDROM Class
XenPCI FSFilter Infrastructure
XenPCI FSFilter System
XenPCI FSFilter Bottom
XenPCI FSFilter Copy Protection
XenPCI FSFilter Security Enhancer
XenPCI FSFilter Open File
XenPCI FSFilter Physical Quota Management
XenPCI FSFilter Encryption
XenPCI FSFilter Compression
XenPCI FSFilter HSM
XenPCI FSFilter Cluster File System
XenPCI FSFilter System Recovery
XenPCI FSFilter Quota Management
XenPCI FSFilter Content Screener
XenPCI FSFilter Continuous Backup
XenPCI FSFilter Replication
XenPCI FSFilter Anti-Virus
XenPCI FSFilter Undelete
XenPCI FSFilter Activity Monitor
XenPCI FSFilter Top
XenPCI Filter
XenPCI Boot File System
XenPCI Base
XenPCI Pointer Port
XenPCI Keyboard Port
XenPCI Pointer Class
XenPCI Keyboard Class
XenPCI Video Init
XenPCI Video
XenPCI Video Save
XenPCI File System
XenPCI Event Log
XenPCI Streams Drivers
XenPCI NDIS Wrapper
XenPCI COM Infrastructure
XenPCI UIGroup
XenPCI PlugPlay
XenPCI PNP_TDI
XenPCI NDIS
XenPCI TDI
XenPCI NetBIOSGroup
XenPCI ShellSvcGroup
XenPCI SchedulerGroup
XenPCI AudioGroup
XenPCI SmartCardGroup
XenPCI NetworkProvider
XenPCI MS_WindowsRemoteValidation
XenPCI MS_WindowsLocalValidation
XenPCI SpoolerGroup
XenPCI NetDDEGroup
XenPCI Parallel arbitrator
XenPCI Extended Base
XenPCI PCI Configuration
XenPCI MS Transactions
XenPCI dummy_group_index = 1
XenPCI wdf_load_group_index = 2
XenPCI xenpci_group_index = 3
XenPCI boot_bus_extender_index = 4
XenPCI SystemStartOptions = NOEXECUTE=OPTOUT FASTDETECT DEBUG
DEBUGPORT=COM1 BAUDRATE=115200 LASTBOOTSTATUS=2
XenPCI PV Devices Active
XenPCI <-- DriverEntry
XenPCI Xen PCI device found - must be fdo
XenPCI --> XenPci_EvtDeviceAdd_XenPci
XenPCI <-- XenPci_EvtDeviceAdd_XenPci
XenPCI --> XenPci_EvtDevicePrepareHardware
XenPCI IoPort Address(c000) Length: 256
XenPCI Private Data: 0x01 0x00 0x00
XenPCI Memory mapped CSR:(d2000000:0) Length:(16777216)
XenPCI Memory flags = 0004
XenPCI Private Data: 0x01 0x01 0x00
XenPCI irq_number = 01c
XenPCI irq_vector = 1a3
XenPCI irq_level = 009
XenPCI irq_mode = LevelSensitive
XenPCI ShareDisposition = CmResourceShareShared
XenPCI <-- XenPci_EvtDevicePrepareHardware
XenPCI --> XenPci_EvtDeviceD0Entry
XenPCI WdfPowerDeviceD3Final
XenPCI --> XenPci_Init
XenPCI base = 0x40000000, Xen Signature = XenVMMXenVMM, EAX = 0x40000002
XenPCI Hypercall area at 817B3000
XenPCI pfn = 17B3
XenPCI shared_info_area_unmapped.QuadPart = d2000000
XenPCI gpfn = d2000
XenPCI hypervisor memory op (XENMAPSPACE_shared_info) ret = 0
XenPCI <-- XenPci_Init
XenPCI --> GntTbl_Init
XenPCI grant_frames = 32
XenPCI grant_entries = 16384
XenPCI <-- GntTbl_Init
XenPCI --> EvtChn_Init
XenPCI --> hvm_set_parameter
XenPCI HYPERVISOR_hvm_op retval = 0
XenPCI <-- hvm_set_parameter
XenPCI hvm_set_parameter(HVM_PARAM_CALLBACK_IRQ, 28) = 0
XenPCI --> EvtChn_AllocIpi
XenPCI <-- EvtChn_AllocIpi
XenPCI --> EvtChn_BindDpc
XenPCI <-- EvtChn_BindDpc
XenPCI pdo_event_channel = 4
XenPCI <-- EvtChn_Init
XenPCI <-- XenPci_EvtDeviceD0Entry
XenPCI --> EvtChn_EvtInterruptEnable
XenPCI <-- EvtChn_EvtInterruptEnable
XenPCI --> XenPci_EvtDeviceD0EntryPostInterruptsEnabled
XenPCI --> XenBus_Init
XenPCI --> hvm_get_parameter
XenPCI HYPERVISOR_hvm_op retval = 0
XenPCI <-- hvm_get_parameter
XenPCI --> hvm_get_parameter
XenPCI HYPERVISOR_hvm_op retval = 0
XenPCI <-- hvm_get_parameter
XenPCI --> EvtChn_BindDpc
XenPCI <-- EvtChn_BindDpc
XenPCI <-- XenBus_Init
XenPCI --> XenPci_SysrqHandler
XenPCI SysRq Value = (null)
XenPCI <-- XenPci_SysrqHandler
XenPCI --> XenPci_ShutdownHandler
Error reading shutdown path - ENOENT
XenPCI <-- XenPci_ShutdownHandler
XenPCI XENMEM_current_reservation = 67551
XenPCI XENMEM_maximum_reservation = 67584
XenPCI XENMEM_maximum_ram_page = 259897
XenPCI Initial Memory Value = 256 (262144)
XenPCI --> XenPci_BalloonThreadProc
XenPCI <-- XenPci_EvtDeviceD0EntryPostInterruptsEnabled
XenPCI --> XenPci_EvtChildListScanForChildren
XenPCI --> XenPci_BalloonHandler
XenPCI target memory value = 256 (262144)
XenPCI <-- XenPci_EvtChildListScanForChildren
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI device = 'vbd', index = '768', path = 'device/vbd/768'
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI device = 'vif', index = '0', path = 'device/vif/0'
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI device = 'pci', index = '0', path = 'device/pci/0'
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI Xen PCI device not found - must be filter
XenPCI --> XenPci_EvtDeviceAdd_XenHide
XenPCI Installing Filter for Intel(R) 82371SB PCI Bus Master IDE Controller
XenPCI <-- XenPci_EvtDeviceAdd_XenHide
XenPCI --> XenHide_EvtDevicePrepareHardware
XenPCI <-- XenHide_EvtDevicePrepareHardware
XenPCI <-- XenPci_BalloonHandler
*** Fatal System Error: 0x0000007b
(0xF9FDFA98,0xC0000034,0x00000000,0x00000000)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.
A fatal system error has occurred.
Connected to Windows Server 2003 3790 x86 compatible target, ptr64 FALSE
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrnlpa.exe -
Loading Kernel Symbols
............................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7B, {f9fdfa98, c0000034, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntkrnlpa.exe ( nt!KeRegisterBugCheckReasonCallback+b85 )
Followup: MachineOwner
---------
nt!DbgBreakPointWithStatus+0x4:
8086cf18 cc int 3
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INACCESSIBLE_BOOT_DEVICE (7b)
During the initialization of the I/O system, it is possible that the driver
for the boot device failed to initialize the device that the system is
attempting to boot from, or it is possible for the file system that is
supposed to read that device to either fail its initialization or to simply
not recognize the data on the boot device as a file system structure that
it recognizes. In the former case, the argument (#1) is the address of a
Unicode string data structure that is the ARC name of the device from which
the boot was being attempted. In the latter case, the argument (#1) is the
address of the device object that could not be mounted.
If this is the initial setup of the system, then this error can occur if
the system was installed on an unsupported disk or SCSI controller. Note
that some controllers are supported only by drivers which are in the Windows
Driver Library (WDL) which requires the user to do a custom install. See
the Windows Driver Library for more information.
This error can also be caused by the installation of a new SCSI adapter or
disk controller or repartitioning the disk with the system partition. If
this is the case, on x86 systems the boot.ini file must be edited or on ARC
systems setup must be run. See the "Advanced Server System Administrator's
User Guide" for information on changing boot.ini.
If the argument is a pointer to an ARC name string, then the format of the
first two (and in this case only) longwords will be:
USHORT Length;
USHORT MaximumLength;
PWSTR Buffer;
That is, the first longword will contain something like 00800020 where 20
is the actual length of the Unicode string, and the next longword will
contain the address of buffer. This address will be in system space, so
the high order bit will be set.
If the argument is a pointer to a device object, then the format of the first
word will be:
USHORT Type;
That is, the first word will contain a 0003, where the Type code will ALWAYS
be 0003.
Note that this makes it immediately obvious whether the argument is a pointer
to an ARC name string or a device object, since a Unicode string can never
have an odd number of bytes, and a device object will always have a Type
code of 3.
Arguments:
Arg1: f9fdfa98, Pointer to the device object or Unicode string of ARC name
Arg2: c0000034
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
MODULE_NAME: nt
FAULTING_MODULE: 80800000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 45d69710
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x7B
LAST_CONTROL_TRANSFER: from 80826a2f to 8086cf18
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f9fdf694 80826a2f 00000003 00000000 80087000 nt!DbgBreakPointWithStatus+0x4
f9fdfa2c 80826dc7 0000007b f9fdfa98 c0000034
nt!KeRegisterBugCheckReasonCallback+0xb85
f9fdfa4c 809fe64f 0000007b f9fdfa98 c0000034 nt!KeBugCheckEx+0x1b
f9fdfbb4 80a00b25 80087000 00000000 80087000 nt!NlsOemLeadByteInfo+0x22ce3
f9fdfc04 809fd3e3 80087000 f9fdfc48 00000000 nt!IoReportHalResourceUsage+0x201f
f9fdfc74 809fb5bb 80087000 00000000 817a95a8 nt!NlsOemLeadByteInfo+0x21a77
f9fdfda0 808e098f 80087000 f9fdfddc 809418f4 nt!NlsOemLeadByteInfo+0x1fc4f
f9fdfdac 809418f4 80087000 00000000 00000000
nt!IoSetPartitionInformationEx+0x24b
f9fdfddc 80887f4a 808e0982 80087000 00000000
nt!PsRemoveCreateThreadNotifyRoutine+0x21e
00000000 00000000 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x44a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeRegisterBugCheckReasonCallback+b85
80826a2f e8907c0000 call nt!ZwYieldExecution+0x994 (8082e6c4)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KeRegisterBugCheckReasonCallback+b85
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlpa.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of James Harper
Sent: Friday, July 10, 2009 10:04 PM
To: Velayudhan, Vinu; Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
>
> Looks like I am missing something in my test setup.
>
> I have tried gplpv_fre_wnet_x86_0.10.0.69.msi. But with these drivers
I am not
> even seeing a hot plug event in Windows GOS when I run the xm
scsi-attach in
> Dom0. With the WinGPLPV-0.9.x, I used to get a hot plug event in
Windows.
>
> Do I need start any specific component/module in Xen, before hot
plugging? I
> tried this with a Xen 3.3.1 and with fresh Windows GOS image which
didn't had
> any preinstalled GPL drivers.
>
I'll have an update ready soon that should fix this problem for you.
James
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |