Bug 620312
| Summary: | BSOD during running iometer tool on XP 32bit Guest. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Quan Wenli <wquan> | ||||||||
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 6.1 | CC: | llim, syeghiay, tburke, ykaul | ||||||||
| Target Milestone: | rc | Keywords: | RHELNAK | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | virtio-win 1.1.10 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2010-08-11 02:21:16 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 435956 [details]
blue screen
Created attachment 435957 [details]
complete memory dump analyze
(In reply to comment #2) > Created an attachment (id=435957) [details] > complete memory dump analyze Did you have the viostor symbols? You would have gotten (hopefully) a much clearer stack. This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** Raising needinfo for Comment #4. Microsoft (R) Windows Debugger Version 6.10.0003.233 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\MEMORY.DMP] Kernel Complete Dump File: Full address space is available ************************************************************ WARNING: Dump file has been truncated. Data may be missing. ************************************************************ Symbol search path is: SRV*c:\symbol*http://msdl.mircrosoft.com/download/symbols;SRV*C:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp.080413-2111 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Mon Aug 2 05:14:23.687 2010 (GMT-7) System Uptime: 0 days 0:08:35.359 Loading Kernel Symbols ............................................................... ......................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {160, 7, 0, bacbcdcb} *** ERROR: Module load completed but symbols could not be loaded for viostor.sys Probably caused by : viostor.sys ( viostor+dcb ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 00000160, memory referenced Arg2: 00000007, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: bacbcdcb, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 00000160 CURRENT_IRQL: 7 FAULTING_IP: viostor+dcb bacbcdcb 80bf6001000000 cmp byte ptr [edi+160h],0 DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO BUGCHECK_STR: 0xD1 PROCESS_NAME: Idle TRAP_FRAME: bacd7c00 -- (.trap 0xffffffffbacd7c00) ErrCode = 00000000 eax=89bd7864 ebx=89e4f8dc ecx=00000342 edx=00000000 esi=89bd7864 edi=00000000 eip=bacbcdcb esp=bacd7c74 ebp=bacd7c84 iopl=0 nv up ei ng nz ac pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296 viostor+0xdcb: bacbcdcb 80bf6001000000 cmp byte ptr [edi+160h],0 ds:0023:00000160=?? Resetting default scope LAST_CONTROL_TRANSFER: from bacbcdcb to 805446e0 STACK_TEXT: bacd7c00 bacbcdcb badb0d00 00000000 89e04b70 nt!KiTrap0E+0x238 WARNING: Stack unwind information not available. Following frames may be wrong. bacd7c84 ba6f5dd2 00000401 bacd7d50 89e0ee18 viostor+0xdcb bacd7c9c 80545695 89e0ee18 89e50a30 01010007 SCSIPORT!ScsiPortInterrupt+0x2a bacd7c9c baac9d3e 89e0ee18 89e50a30 01010007 nt!KiInterruptDispatch+0x45 bacd7d50 80545d3c 00000000 0000000e 00000000 processr!AcpiC1Idle+0x12 bacd7d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10 STACK_COMMAND: kb FOLLOWUP_IP: viostor+dcb bacbcdcb 80bf6001000000 cmp byte ptr [edi+160h],0 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: viostor+dcb FOLLOWUP_NAME: MachineOwner MODULE_NAME: viostor IMAGE_NAME: viostor.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c50524c FAILURE_BUCKET_ID: 0xD1_viostor+dcb BUCKET_ID: 0xD1_viostor+dcb Followup: MachineOwner --------- As passed in virtio-win 1.1.10 in comment #12. Close it.Thanks~~~ |
Created attachment 435955 [details] iometer conf file Description of problem: Core dumped during running iometer tool on XP 32bit Guest. Version-Release number of selected component (if applicable): kernel-2.6.32-54.el6.x86_64 qemu-kvm-0.12.1.2-2.104.el6.x86_64 virtio-win-1.1.9-0.vfd How reproducible: always Steps to Reproduce: 1.Boot XP 32bit Guest. CIL: /usr/libexec/qemu-kvm -m 2G -smp 2 -drive file=/home/WindowXp-32-virtio,cache=none,format=raw,boot=on,id=drive-virtio0-0-0,if=none -device virtio-blk-pci,drive=drive-virtio0-0-0,id=virtio0-0-0 -netdev tap,id=hostnet0 -device rtl8139,netdev=hostnet0,mac=00:00:11:12:31:4A,bus=pci.0,addr=0x4 -boot c -uuid `uuidgen` -rtc base=utc -no-kvm-pit-reinjection -cpu qemu64,+sse2,+x2apic -balloon none -monitor stdio -vnc :1 -drive file=/home/vrtio-10G,cache=none,format=raw,if=none,id=drive-virtio0-0-1 -device virtio-blk-pci,drive=drive-virtio0-0-1,id=virtio0-0-1 2.running the iometer tool by using the attached the conf file. iometer version:2006.07.27. 3. Actual results: Expected results: Additional info: