Bug 923081
| Summary: | Win8/2012 BSOD 0xc4 when installation | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | CongLi <coli> | ||||||||||
| Component: | kvm | Assignee: | Yvugenfi <yvugenfi> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 5.10 | CC: | chayang, dfleytma, ghammer, juzhang, michen, mkenneth, qzhang, rhod, shuang, virt-maint, vrozenfe, xwei, yvugenfi | ||||||||||
| Target Milestone: | rc | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-03-28 18:13:41 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
CongLi
2013-03-19 07:20:51 UTC
Created attachment 712552 [details]
Debug info about win8-32
Created attachment 712554 [details]
Debug info about win8-64
Created attachment 712555 [details]
Debug info about win2012-64
1. I don't think it is a same bug as Bug #921530 (different BSOD number) 2. The BSOD code is very very suspicious... Is it a clean installation or is it OS upgrade? For some reason driver verifier is turned on (0xc4 - bug check code). Best regards, Yan. Hi, Yan Vugenfirer 1. The phenomenon of Bug #921530 is same, as you say, it's not the same bug. 2. It's a clean installation. I have created new images to reproduce the bug, there is always the same error. 3. The bug reproduced on AMD 100%, as for Intel, the bug just reproduced 1 time, not each time. Best Regards, Cong Li Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. Trying Win2012, met same error, 100% repro on such hw, Changing the summary to include win8/2012 processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 67 model name : Dual-Core AMD Opteron(tm) Processor 1216 stepping : 3 cpu MHz : 2400.000 cache size : 1024 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid : 1 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy bogomips : 4822.45 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc |