Bug 432913
| Summary: | CPU can not do hotplug when one task set affinity to it. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Song, Youquan <youquan.song> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 9 | CC: | grgustaf | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-07-14 15:42:07 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: |
|
||||||||
Does this happen on the upstream kernel as well? Yes. the kernel 2.6.24 to 2.6.25-rc2 also exit the bug. But the bug is not exit at kernel 2.6.18. Does the CPU mask of the running process get changed when the processor is offlined? And can you get a system state (alt-sysrq-t) when the script hangs? Yes, after I set offline the CPU, I use commands "taskset -p $PID and ps -- pid=$PID -o psr" to find that process CPU mask is change and process migrate to other CPU correctly. Attachment is the Screenshot.png Created attachment 296037 [details]
CPU can not do hotplug when one task set affinity to it.
Created attachment 296040 [details]
Alt-Sysrq-t log after run the script
This bug is still exits on FC9 Beta. Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: Install Fedora 9 (sorry, I can not find the entry for F9 bug report). Set one task affinity to one CPU core, then set offline the CPU core. After that we can not set online the CPU core again. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. run the test.sh script: test.sh 1 ( 1 is the logical CPU ) test.sh script: #!/bin/bash main(){ typeset -i CPU=$1 ./task.sh > /dev/null& PID=$! if [ `cat /sys/devices/system/cpu/cpu${CPU}/online` = "0" ]; then echo "1" > /sys/devices/system/cpu/cpu${CPU}/online fi MASK=$((1<<${CPU})) `taskset -p ${MASK} ${PID} > /dev/null 2>&1` echo "0" > /sys/devices/system/cpu/cpu${CPU}/online echo "1" > /sys/devices/system/cpu/cpu${CPU}/online disown $PID kill -9 $PID > /dev/null 2>&1 echo "PASS\n" } typeset -i TEST_CPU=$1 main $TEST_CPU 2. task.sh script as following #!/bin/bash while : do NOOP=1 done 3. Actual results: The test.sh will block at set online the CPU ( echo "1" > /sys/devices/system/cpu/cpu${CPU}/online ). Expected results: Additional info: Happened in Intel Bensley platform (2xXeon 2.83G Harpertown C0, chipset Blackford G1, 160 SATA)