Bug 1972487
| Summary: | [virtio-win][whql test] Win10-64 & Win2019 & Win2022(vhost=on) hit BSOD when run '2c_Mini6RSSSendRecv (Multi-Group Win8+)' | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | leidwang <leidwang> | ||||||
| Component: | virtio-win | Assignee: | ybendito | ||||||
| virtio-win sub component: | virtio-win-prewhql | QA Contact: | Ke Ma <mama> | ||||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||||
| Severity: | high | ||||||||
| Priority: | high | CC: | ailan, lijin, mdean, qizhu, ybendito, yvugenfi | ||||||
| Version: | 9.0 | Keywords: | Triaged | ||||||
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
||||||
| Target Release: | 9.0 | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Windows | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2022-05-17 15:35:26 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1968315, 2057757 | ||||||||
| Attachments: |
|
||||||||
|
Description
leidwang@redhat.com
2021-06-16 03:51:24 UTC
Created attachment 1791437 [details]
screenshot
Win10-64 also hit BSOD when run "Run RSC Tests". Stop code same as comment1. (In reply to leidwang from comment #3) > Win10-64 also hit BSOD when run "Run RSC Tests". Stop code same as comment1. Sorry,Win10-64 hit BSOD when run "2c_Mini6RSSSendRecv (Multi-Group Win8+)". Stop code same as comment1. Win2022(vhost=on) hit BSOD when run "2c_Mini6RSSSendRecv (Multi-Group Win8+)".Stop code same as comment1. The fix merged upstream. Test this job(2c_Mini6RSSSendRecv (Multi-Group Win8+)) with virtio-win-prewhql-0.1-206(win2022,win2019), but still hit BSOD. Stop code is the same as before. Can we move this BZ to 8.6? This BZ will not block our testing. (In reply to leidwang from comment #32) > Test this job(2c_Mini6RSSSendRecv (Multi-Group Win8+)) with > virtio-win-prewhql-0.1-206(win2022,win2019), > but still hit BSOD. Stop code is the same as before. > > Can we move this BZ to 8.6? This BZ will not block our testing. If it is not a blocker, let's move it to RHEL8.6 Please upload the new dump as well. Thanks. (In reply to leidwang from comment #32) > Test this job(2c_Mini6RSSSendRecv (Multi-Group Win8+)) with > virtio-win-prewhql-0.1-206(win2022,win2019), > but still hit BSOD. Stop code is the same as before. > > Can we move this BZ to 8.6? This BZ will not block our testing. Moving to RHEL8.6 based on comment#32 Hit this issue when run the job "2c_Mini6RSSSendRecv (Multi-Group Win8+)" int win11 whql testing, stop code is same as comment1, pkg: qemu-kvm-6.0.0-28.module+el8.5.0+12271+fffa967b.x86_64 kernel-4.18.0-330.el8.x86_64 seabios-1.14.0-1.module+el8.4.0+8855+a9e237a9.x86_64 virtio-win-prewhql-0.1-207.iso Please run this specific test ( '2c_Mini6RSSSendRecv (Multi-Group Win8+)') at least 5 times if not crashes earlier: 1. on virtio-win build 162 2. on virtio-win build 171 Please use Server2022 release (build 20348) with respective HCK (do not use the evaluation build 20344). In case of crashes please share the dump files. Thanks in advance. Created attachment 1829162 [details]
Build 21050 for test
Please try the fix candidate build 21050 (comment #40) at least 5 times. In case of crash please collect the memory dumps. Merged upstream: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/659 Waiting for downstream build. Tested the job with 216 build on Win2022,Win2019,Win10-64. 1.Not hit BSOD on Win2022 2.Hit BSOD at the fourth test on Win2019 stop code:SYSTEM THREAD EXCEPTION NOT HANDLED 2.Hit BSOD at the fourth test on Win10-64 stop code:SYSTEM THREAD EXCEPTION NOT HANDLED Hi Yan,I will upload dump files later,could you please help to check if the crash is related to the RSS test?Thanks! (In reply to leidwang from comment #61) > Tested the job with 216 build on Win2022,Win2019,Win10-64. > > 1.Not hit BSOD on Win2022 > > 2.Hit BSOD at the fourth test on Win2019 > stop code:SYSTEM THREAD EXCEPTION NOT HANDLED > > 2.Hit BSOD at the fourth test on Win10-64 Sorry,hit BSOD at the first test on Win10-64 > stop code:SYSTEM THREAD EXCEPTION NOT HANDLED > > Hi Yan,I will upload dump files later,could you please help to check if the > crash is related to the RSS test?Thanks! (In reply to leidwang from comment #64) > (In reply to leidwang from comment #61) > > Tested the job with 216 build on Win2022,Win2019,Win10-64. > > > > 1.Not hit BSOD on Win2022 > > > > 2.Hit BSOD at the fourth test on Win2019 > > stop code:SYSTEM THREAD EXCEPTION NOT HANDLED > > > > 2.Hit BSOD at the fourth test on Win10-64 > Sorry,hit BSOD at the first test on Win10-64 > > stop code:SYSTEM THREAD EXCEPTION NOT HANDLED > > > > Hi Yan,I will upload dump files later,could you please help to check if the > > crash is related to the RSS test?Thanks! Hi Leidwang, Can you please provide exact qemu and kernel versions when you reproduce the problem. In both dumps the problem is different that initial one and we want to try reproducing it. Thanks (In reply to ybendito from comment #66) > (In reply to leidwang from comment #64) > > (In reply to leidwang from comment #61) > > > Tested the job with 216 build on Win2022,Win2019,Win10-64. > > > > > > 1.Not hit BSOD on Win2022 > > > > > > 2.Hit BSOD at the fourth test on Win2019 > > > stop code:SYSTEM THREAD EXCEPTION NOT HANDLED > > > > > > 2.Hit BSOD at the fourth test on Win10-64 > > Sorry,hit BSOD at the first test on Win10-64 > > > stop code:SYSTEM THREAD EXCEPTION NOT HANDLED > > > > > > Hi Yan,I will upload dump files later,could you please help to check if the > > > crash is related to the RSS test?Thanks! > > Hi Leidwang, > Can you please provide exact qemu and kernel versions when you reproduce the > problem. > In both dumps the problem is different that initial one and we want to try > reproducing it. > Thanks qemu:qemu-kvm-6.2.0-7.el9.x86_64 kernel:kernel-5.14.0-57.kpq0.el9.x86_64 Based on our discussions at the Windows team meeting, the BSOD we encountered this time was a completely different problem. So we'll close this bz and open a new bug to track new issues. Thanks! (In reply to leidwang from comment #68) > Based on our discussions at the Windows team meeting, the BSOD we > encountered this time was a completely different problem. > So we'll close this bz and open a new bug to track new issues. Thanks! Do you have a new BZ number? (In reply to Yvugenfi from comment #69) > (In reply to leidwang from comment #68) > > Based on our discussions at the Windows team meeting, the BSOD we > > encountered this time was a completely different problem. > > So we'll close this bz and open a new bug to track new issues. Thanks! > > Do you have a new BZ number? https://bugzilla.redhat.com/show_bug.cgi?id=2059569 Reopened as the fix was reverted. Under investigation again. *** Bug 2059569 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (new packages: virtio-win), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:3890 |