|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] GPLPV under NetBSD dom0
The NetBSD guys finally fixed the bug w/ pty='serial' so now I can
debug why the GPLPV drivers are BSODing. WOOHOO!
dom0
====
OS: NetBSD 5.0.1/amd64
Xen Kernel: 3.3.2
Xen Userland: 3.3.2nb1
CPU: AMD Phenom II X3
domU
====
OS: Windows Server 2003 EE R2 SP2 x64
CPUs: 2 Virtual
Xen Config
========
serial = 'pty'
kernel = '/usr/pkg/lib/xen/boot/hvmloader'
builder = 'hvm'
memory = '3072'
device_model='/usr/pkg/libexec/qemu-dm'
name = "win2k3"
vcpus = 2
cpus="1-2"
cpu_cap=200
cpu_weight=128
disk = [ 'file:/usr/local/xen/win2k3.img,ioemu:hda,w',
'file:/usr/local/xen/win2k3.iso,ioemu:hdb:cdrom,r' ]
vif = [ 'mac=00:16:3e:50:02:f4, bridge=bridge0, type=ioemu,
model=e1000', 'mac=00:16:3e:50:02:f5, bridge=bridge1, type=ioemu,
model=e1000', 'mac=00:16:3e:50:02:f6, bridge=bridge2, type=ioemu,
model=e1000' ]
boot = 'd'
vnc = 1
usb = 1
usbdevice = 'tablet'
acpi = 1
apic = 1
acpio = 1
shadow_memory = 12
pae = 1
sdl = 0
stdvga = 0
on_reboot = 'restart'
on_shutdown = 'destroy'
on_crash = 'restart'
localtime = 1
timer_mode = 1
xen_platform_pci=0
WinDbg Output
===========
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \\.\com8
Waiting to reconnect...
Connected to Windows Server 2003 3790 x64 target at (Thu Oct 29
16:51:09.060 2009 (GMT-5)), ptr64 TRUE
Kernel Debugger connection established.
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for ntkrnlmp.exe -
Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
Built by: 3790.srv03_sp2_qfe.090319-1204
Machine Name:
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d8280
System Uptime: not available
XenPCI GPLPV 0.10.0.130XenPCI --> 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 = FASTDETECT NOEXECUTE=ALWAYSOFF
NOGUIBOOT BOOTLOGO DEBUG
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:(f2000000:0) Length:(16777216)
XenPCI Memory flags = 0004
XenPCI Private Data: 0x01 0x01 0x00
XenPCI irq_number = 01c
XenPCI irq_vector = 1a1
XenPCI irq_level = 00a
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 FFFFFADFB578C000
XenPCI shared_info_area_unmapped.QuadPart = f2000000
XenPCI gpfn = f2000
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 = 2
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 suspend event channel = 6
XenPCI --> EvtChn_BindDpc
XenPCI <-- EvtChn_BindDpc
XenPCI --> XenPci_SysrqHandler
XenPCI SysRq Value = (null)
XenPCI <-- XenPci_SysrqHandler
XenPCI --> XenPci_ShutdownHandler
XenPCI XENMEM_current_reservation = 788447
XenPCI XENMEM_maximum_reservation = 788480
Error reading shutdown path - ENOENT
XenPCI <-- XenPci_ShutdownHandler
XenPCI XENMEM_maximum_ram_page = 1245184
XenPCI --> XenPci_DeviceWatchHandler
XenPCI Initial Memory Value = 3072 (3145728)
XenPCI --> XenPci_BalloonThreadProc
XenPCI <-- XenPci_DeviceWatchHandler
XenPCI <-- XenPci_EvtDeviceD0EntryPostInterruptsEnabled
XenPCI --> XenPci_BalloonHandler
XenPCI --> XenPci_EvtChildListScanForChildren
XenPCI target memory value = 3072 (3145728)
XenPCI Found path = device/vbd/768
XenPCI <-- XenPci_BalloonHandler
XenPCI Found path = device/vbd/832
XenPCI Got balloon event, current = 3072, target = 3072
XenPCI No change to memory
XenPCI Found path = device/vif/0
XenPCI Found path = device/vif/1
XenPCI Found path = device/vif/2
XenPCI <-- XenPci_EvtChildListScanForChildren
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI device = 'vbd', index = '768', path = 'device/vbd/768'
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI device = 'vbd', index = '832', path = 'device/vbd/832'
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI device = 'vif', index = '0', path = 'device/vif/0'
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI device = 'vif', index = '1', path = 'device/vif/1'
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI device = 'vif', index = '2', path = 'device/vif/2'
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
XenVbd --> DriverEntry
XenVbd IRQL = 0
XenVbd DriverObject = FFFFFADFB5737830, RegistryPath = FFFFF80000095160
XenVbd <-- DriverEntry
XenPCI Xen PCI device not found - must be filter
XenPCI --> XenPci_EvtDeviceAdd_XenHide
XenPCI <-- XenPci_EvtDeviceAdd_XenHide (filter not required for Xen
Block Device Driver)
XenPCI Xen PCI device not found - must be filter
XenPCI --> XenPci_EvtDeviceAdd_XenHide
XenPCI <-- XenPci_EvtDeviceAdd_XenHide (filter not required for Xen
Block Device Driver)
XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
XenPCI device/vbd/768
XenPCI CmResourceTypeMemory (0)
XenPCI Start = f2000000, Length = 0
XenPCI pfn[0] = 000be604
XenPCI New Start = 00000000be604000, Length = 4096
XenPCI CmResourceTypeMemory (1)
XenPCI Start = f2000001, Length = 0
XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
XenPCI --> XenPciPdo_EvtDevicePrepareHardware
XenPCI <-- XenPciPdo_EvtDevicePrepareHardware
XenPCI --> XenPciPdo_EvtDeviceD0Entry
XenPCI WdfPowerDeviceD3Final
XenPCI --> XenConfig_InitConfigPage
XenPCI fdo_driver_object = FFFFFADFB5737830
XenPCI fdo_driver_extension = FFFFFADFB5706010
XenPCI <-- XenConfig_InitConfigPage
XenPCI --> XenPci_GetBackendAndAddWatch
XenPCI --> XenPci_UpdateBackendState
XenPCI <-- XenPci_GetBackendAndAddWatch
XenPCI Backend State Changed to Connected
XenPCI <-- XenPci_UpdateBackendState
XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
XenPCI testing path = device/vbd/768/device-type
XenPCI testing disk vs disk
XenPCI condition = 0
XenPCI --> XenPci_ChangeFrontendState
XenPCI --> XenPci_DeviceWatchHandler
XenPCI <-- XenPci_DeviceWatchHandler
XenPCI --> XenPci_UpdateBackendState
XenPCI state unchanged
XenPCI Still waiting for 2 (currently 4)...
XenPCI --> XenPci_UpdateBackendState
XenPCI state unchanged
XenPCI Timed out waiting for 2!
XenPCI --> XenPci_ChangeFrontendState
XenPCI --> XenPci_DeviceWatchHandler
XenPCI <-- XenPci_DeviceWatchHandler
XenPCI --> XenPci_UpdateBackendState
XenPCI state unchanged
XenPCI Still waiting for 2 (currently 4)...
XenPCI --> XenPci_UpdateBackendState
XenPCI state unchanged
XenPCI Timed out waiting for 2!
XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers, status = c0000001
XenPCI Match
XenPCI <-- XenPciPdo_EvtDeviceD0Entry (error path)
XenPCI --> XenPciPdo_EvtDeviceReleaseHardware
XenPCI <-- XenPciPdo_EvtDeviceReleaseHardware
XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
XenPCI device/vbd/832
XenPCI CmResourceTypeMemory (0)
XenPCI Start = f2000000, Length = 0
XenPCI pfn[0] = 000be5fc
XenPCI New Start = 00000000be5fc000, Length = 4096
XenPCI CmResourceTypeMemory (1)
XenPCI Start = f2000001, Length = 0
XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
XenPCI --> XenPciPdo_EvtDevicePrepareHardware
XenPCI <-- XenPciPdo_EvtDevicePrepareHardware
XenPCI --> XenPciPdo_EvtDeviceD0Entry
XenPCI WdfPowerDeviceD3Final
XenPCI --> XenConfig_InitConfigPage
XenPCI fdo_driver_object = FFFFFADFB5737830
XenPCI fdo_driver_extension = FFFFFADFB5706010
XenPCI <-- XenConfig_InitConfigPage
XenPCI --> XenPci_GetBackendAndAddWatch
XenPCI --> XenPci_UpdateBackendState
XenPCI <-- XenPci_GetBackendAndAddWatch
XenPCI Backend State Changed to Connected
XenPCI <-- XenPci_UpdateBackendState
XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
XenPCI testing path = device/vbd/832/device-type
XenPCI testing cdrom vs disk
XenPCI condition = 1
XenPCI set inactive
XenPCI set inactive with dont config
XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
XenPCI <-- XenPciPdo_EvtDeviceD0Entry
XenVbd --> XenVbd_HwScsiFindAdapter
XenVbd IRQL = 0
XenVbd xvdd = FFFFFADFB5783008
XenVbd BusInterruptLevel = 28
XenVbd BusInterruptVector = 01c
XenVbd NumberOfAccessRanges = 1
XenVbd RangeStart = be5fc000, RangeLength = 00001000
XenVbd XEN_INIT_TYPE_VECTORS
XenVbd XEN_INIT_TYPE_DEVICE_STATE - 00000000B55C85D0
XenVbd Device is inactive
XenVbd Dma64BitAddresses supported
XenVbd <-- XenVbd_HwScsiFindAdapter
XenPCI --> XenPci_BIS_GetDmaAdapter
XenPCI IRQL = 0
XenPCI Device Description = FFFFFADFAD207D80:
XenPCI Version = 0
XenPCI Master = 1
XenPCI ScatterGather = 1
XenPCI DemandMode = 0
XenPCI AutoInitialize = 0
XenPCI Dma32BitAddresses = 0
XenPCI IgnoreCount = 0
XenPCI Dma64BitAddresses = 1
XenPCI BusNumber = 0
XenPCI DmaChannel = -1
XenPCI InterfaceType = 15
XenPCI DmaWidth = 0
XenPCI DmaSpeed = 0
XenPCI MaximumLength = 45056
XenPCI DmaPort = -1
XenPCI About to call IoGetAttachedDeviceReference
XenPCI Before start of loop - curr = FFFFFADFB55C4060
XenPCI End of loop
XenPCI <-- XenPci_BIS_GetDmaAdapter
XenVbd --> XenVbd_HwScsiInitialize
XenVbd IRQL = 10
XenVbd dump_mode = 0
XenVbd <-- XenVbd_HwScsiInitialize
XenVbd --> XenVbd_HwScsiAdapterControl
XenVbd IRQL = 0
XenVbd xvdd = FFFFFADFB5783008
XenVbd ScsiQuerySupportedControlTypes (Max = 5)
XenVbd <-- XenVbd_HwScsiAdapterControl
XenVbd Inactive Srb->Function = 00000000
*** Fatal System Error: 0x0000007b
(0xFFFFFADFAD2083C0,0xFFFFFFFFC0000034,0x0000000000000000,0x0000000000000000)
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.
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for ntkrnlmp.exe -
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7B, {fffffadfad2083c0, ffffffffc0000034, 0, 0}
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntkrnlmp.exe ( nt!KeDisconnectInterrupt+48e )
Followup: MachineOwner
---------
nt!DbgBreakPointWithStatus:
fffff800`01026c00 cc int 3
Thanks!
-Dustin
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |