Bug 858531
| Summary: | guest fail to s3/s4 with virtio-rng driver if the /dev/hwrng open for reading | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | juzhang <juzhang> | ||||||||
| Component: | kernel | Assignee: | Neil Horman <nhorman> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 6.4 | CC: | amit.shah, flang, juzhang, mdeng, michen, nhorman, qzhang, virt-maint, xfu | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | |||||||||||
| : | 917960 (view as bug list) | Environment: | |||||||||
| Last Closed: | 2014-08-12 11:27:47 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: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 912287, 917960 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
juzhang
2012-09-19 03:14:15 UTC
Created attachment 614190 [details]
the guest full dmesg
test this as follow version: host: #rpm -q qemu-kvm qemu-kvm-0.12.1.2-2.299.el6.bz786407.x86_64 #uname -r 2.6.32-305.el6.x86_64 guest: 2.6.32-303.el6.x86_64 steps as same as Discription results: not hit call trace,but when after first time do S3/S4 successfully ,can not do S3/S4 second time ,third time . guest : [root@localhost ~]# echo mem >/sys/power/state---->first time s3 successfully [root@localhost ~]# echo disk >/sys/power/state--->first time s4 successfully [root@localhost ~]# echo disk >/sys/power/state---->second time S4 bash: echo: write error: Device or resource busy [root@localhost ~]# echo disk >/sys/power/state---->third time s4 bash: echo: write error: Device or resource busy [root@localhost ~]# echo disk >/sys/power/state Message from syslogd@localhost at Sep 18 07:58:08 ... kernel:BUG: soft lockup - CPU#1 stuck for 64s! [bash:2507] bash: echo: write error: Device or resource busy [root@localhost ~]# bash: echo: write error: Device or resource busy bash: bash:: command not found [root@localhost ~]# echo mem >/sys/power/state---->second time s3 bash: echo: write error: Device or resource busy addinfo attachment is when can not do S3/s4,the guest show Created attachment 614195 [details]
after second time S3/S4 ,guest show
Created attachment 614196 [details]
after second time S3/S4 ,guest show
Screenshots say rngd refuses to freeze. reassigning to rng-tools, please check why rngd doesn't freeze. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux. This really has nothing to do with rng-tools, it appears that rngd isn't freezing because its stuck in a state where we're getting woken up from a wait_for_completion_killable call in virtio_data_present, but the return code isn't ERESTARTSYS in wait_for_common, so the virtio code falls through its return check, then looks to see how much more data it needs to pull from the random device. Since this test puts such a drain on the entropy pools we just go straight back to waiting on the completion event. juzhang, do you have this set up somewhere where I can try to do some more investigation on it already, or do I need to set something up? Hi Qzhang, Could you give a help for handling this issue? Best Regards, Junyi (In reply to Neil Horman from comment #8) > This really has nothing to do with rng-tools, it appears that rngd isn't > freezing because its stuck in a state where we're getting woken up from a > wait_for_completion_killable call in virtio_data_present, but the return > code isn't ERESTARTSYS in wait_for_common, so the virtio code falls through > its return check, then looks to see how much more data it needs to pull from > the random device. Since this test puts such a drain on the entropy pools > we just go straight back to waiting on the completion event. juzhang, do > you have this set up somewhere where I can try to do some more investigation > on it already, or do I need to set something up? Hi, Neil We could setup the environment for you to debug, but I would like to confirm with you first, do we need to fix such issue in RHEL6? Since RHEL6 s3/s4 will not be official supported any more and Ademar closed most of the s3/s4 bug (refer to Bug 912287). We will only keep some basic S3/S4 case in our test plan. If you think we need to fix this bug or at least need to investigate first, then I will prepare the setup. :) Thanks, Qunfang Oh, thats a good point, I had not realized that we don't support s3/s4 in virt environments. If thats the case, then no, we probably don't need to fix this in RHEL6. That said, you do probably want to test it on RHEL7 where we do support it, as this is still likely a bug. (In reply to Neil Horman from comment #11) > Oh, thats a good point, I had not realized that we don't support s3/s4 in > virt environments. If thats the case, then no, we probably don't need to > fix this in RHEL6. That said, you do probably want to test it on RHEL7 > where we do support it, as this is still likely a bug. Hi, Junyi Could you help let someone to try it on RHEL7 host to see whether the problem exists on RHEL7 host? Thanks, Qunfang (In reply to Qunfang Zhang from comment #12) > (In reply to Neil Horman from comment #11) > > Oh, thats a good point, I had not realized that we don't support s3/s4 in > > virt environments. If thats the case, then no, we probably don't need to > > fix this in RHEL6. That said, you do probably want to test it on RHEL7 > > where we do support it, as this is still likely a bug. > > Hi, Junyi > > Could you help let someone to try it on RHEL7 host to see whether the > problem exists on RHEL7 host? > > Thanks, > Qunfang Sure. Hi Xiangchun, Could you have a try then update the result in the bz? Best Regards, Junyi |