A quirk with CONFIG_PREEMPT=y ?
by Petri Kaukasoina from LinuxQuestions.org on (#5SGHF)
I have seen this only twice and I am not sure it has anything to do with PREEMPT...
I don't remember seeing this before the change from CONFIG_PREEMPT_VOLUNTARY to CONFIG_PREEMPT. With CONFIG_PREEMPT and preempt=full, I used vlc to watch a video from local disk, and the video once stopped. A mouse click to the screen made it continue. Then I changed to CONFIG_PREEMPT with preempt=voluntary, and the same happened. Then I moved from CONFIG_PREEMPT back to CONFIG_PREEMPT_VOLUNTARY and have not seen it since.
It is not easy to reproduce: it took several hours to happen.
Has anyone else seen this?
(This is a sandy bridge with integrated graphics controller and I use the intel x.org driver running in slackware64-current.)
I don't remember seeing this before the change from CONFIG_PREEMPT_VOLUNTARY to CONFIG_PREEMPT. With CONFIG_PREEMPT and preempt=full, I used vlc to watch a video from local disk, and the video once stopped. A mouse click to the screen made it continue. Then I changed to CONFIG_PREEMPT with preempt=voluntary, and the same happened. Then I moved from CONFIG_PREEMPT back to CONFIG_PREEMPT_VOLUNTARY and have not seen it since.
It is not easy to reproduce: it took several hours to happen.
Has anyone else seen this?
(This is a sandy bridge with integrated graphics controller and I use the intel x.org driver running in slackware64-current.)