[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <67b279c7-1b65-46be-baa2-06794b47b9d1@leemhuis.info>
Date: Wed, 12 Jun 2024 14:41:04 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: "tzimmermann@...e.de" <tzimmermann@...e.de>
Cc: "Petkov, Borislav" <Borislav.Petkov@....com>,
"regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
"zack.rusin@...adcom.com" <zack.rusin@...adcom.com>,
"dmitry.osipenko@...labora.com" <dmitry.osipenko@...labora.com>,
"Kaplan, David" <David.Kaplan@....com>,
"Koenig, Christian" <Christian.Koenig@....com>,
Dave Airlie <airlied@...hat.com>, Dave Airlie <airlied@...hat.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
ML dri-devel <dri-devel@...ts.freedesktop.org>,
spice-devel@...ts.freedesktop.org, virtualization@...ts.linux.dev
Subject: Re: [REGRESSION] QXL display malfunction
[CCing a few more people and lists that get_maintainers pointed out for qxl]
Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
for once, to make this easily accessible to everyone.
Thomas, from here it looks like this report that apparently is caused by
a change of yours that went into 6.10-rc1 (b33651a5c98dbd ("drm/qxl: Do
not pin buffer objects for vmap")) fell through the cracks. Or was
progress made to resolve this and I just missed this?
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
#regzbot poke
On 03.06.24 04:29, Kaplan, David wrote:
>> -----Original Message-----
>> From: Kaplan, David
>> Sent: Sunday, June 2, 2024 9:25 PM
>> To: tzimmermann@...e.de; dmitry.osipenko@...labora.com; Koenig,
>> Christian <Christian.Koenig@....com>; zach.rusin@...adcom.com
>> Cc: Petkov, Borislav <Borislav.Petkov@....com>; regressions@...t.linux.dev
>> Subject: [REGRESSION] QXL display malfunction
>>
>> Hi,
>>
>> I am running an Ubuntu 19.10 VM with a tip kernel using QXL video and I've
>> observed the VM graphics often malfunction after boot, sometimes failing to
>> load the Ubuntu desktop or even immediately shutting the guest down.
>> When it does load, the guest dmesg log often contains errors like
>>
>> [ 4.303586] [drm:drm_atomic_helper_commit_planes] *ERROR* head 1
>> wrong: 65376256x16777216+0+0
>> [ 4.586883] [drm:drm_atomic_helper_commit_planes] *ERROR* head 1
>> wrong: 65376256x16777216+0+0
>> [ 4.904036] [drm:drm_atomic_helper_commit_planes] *ERROR* head 1
>> wrong: 65335296x16777216+0+0
>> [ 5.374347] [drm:qxl_release_from_id_locked] *ERROR* failed to find id in
>> release_idr
>>
>> I bisected the issue down to "drm/qxl: Do not pin buffer objects for vmap"
>> (b33651a5c98dbd5a919219d8c129d0674ef74299).
>>
>> The full guest .config and guest XML can be provided if desired. The guest
>> kernel has QXL support compiled in and the VM has
>>
>> <video>
>> <model type="qxl" ram="65536" vram="65536" vgamem="16384"
>> heads="1" primary="yes"/>
>> <address type="pci" domain="0x0000" bus="0x00" slot="0x01"
>> function="0x0"/> </video>
>>
>> The host is Ubuntu 24.04 (stock) running QEMU version 8.2.2. The VM is run
>> under virt-manager 4.1.0. If other information would be helpful, just let me
>> know.
>>
>> Thanks --David Kaplan
>
> Fixing emails...sorry
>
> --David Kaplan
>
>
Powered by blists - more mailing lists