[Bug 1863023] Re: Deadlock in QXL

2021-07-04 Thread Launchpad Bug Tracker
[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1863023 Title: Deadlock in

[Bug 1863023] Re: Deadlock in QXL

2021-05-05 Thread Thomas Huth
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now. If you still think this bug report here is valid, then please switch the

[Bug 1863023] Re: Deadlock in QXL

2020-03-06 Thread Alex Bennée
I can't see where the do_run_on_cpu is called in memory.c at 4.2. Is it reproducible on the latest state of master. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1863023 Title: Deadlock in QXL Sta

[Bug 1863023] Re: Deadlock in QXL

2020-03-06 Thread Gerd Hoffmann
Any change if you remove the graphic_hw_update() call in qxl_enter_vga_mode()? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1863023 Title: Deadlock in QXL Status in QEMU: New Bug description: