Re: [BISECTED] 5.14.0-rc4 broke drm/ttm when !CONFIG_DEBUG_FS

On Mon, Aug 2, 2021 at 8:29 PM Duncan wrote: > > [Not subscribed so please CC me. Manual quoting after using lore's > in-reply-to functionality. First time doing that so hope I got it > right.] > > Mikael Pettersson wrote... > > Booting 5.14.0-rc4 on my box wit

[BISECTED] 5.14.0-rc4 broke drm/ttm when !CONFIG_DEBUG_FS

Booting 5.14.0-rc4 on my box with Radeon graphics breaks with [drm:radeon_ttm_init [radeon]] *ERROR* failed initializing buffer object driver(-19). radeon :01:00.0: Fatal error during GPU init after which the screen goes black for the rest of kernel boot and early user-space init. Once the

[BISECTED] 3.17-rc1 radeon screen corruption due to "Always flush the HDP cache before submitting a CS to the GPU"

Michel D?nzer writes: > On 06.09.2014 01:49, Mikael Pettersson wrote: > > Michel D?nzer writes: > > > On 30.08.2014 22:59, Mikael Pettersson wrote: > > > > Since 3.17-rc1 my radeon card (RV370 / X1050 card) causes screen > > corruption > > >

[BISECTED] 3.17-rc1 radeon screen corruption due to "Always flush the HDP cache before submitting a CS to the GPU"

Michel D?nzer writes: > On 06.09.2014 01:49, Mikael Pettersson wrote: > > Michel D?nzer writes: > > > On 30.08.2014 22:59, Mikael Pettersson wrote: > > > > Since 3.17-rc1 my radeon card (RV370 / X1050 card) causes screen > > corruption > > >

[BISECTED] 3.17-rc1 radeon screen corruption due to "Always flush the HDP cache before submitting a CS to the GPU"

Michel D?nzer writes: > On 30.08.2014 22:59, Mikael Pettersson wrote: > > Since 3.17-rc1 my radeon card (RV370 / X1050 card) causes screen corruption > > after a while in X + firefox. This still occurs with yesterday's HEAD > > of Linus' repo. 3.16 and ealier kernels a

[BISECTED] 3.17-rc1 radeon screen corruption due to "Always flush the HDP cache before submitting a CS to the GPU"

Michel D?nzer writes: > On 30.08.2014 22:59, Mikael Pettersson wrote: > > Since 3.17-rc1 my radeon card (RV370 / X1050 card) causes screen corruption > > after a while in X + firefox. This still occurs with yesterday's HEAD > > of Linus' repo. 3.16 and ealier kernels a

[BISECTED] 3.17-rc1 radeon screen corruption due to "Always flush the HDP cache before submitting a CS to the GPU"

Since 3.17-rc1 my radeon card (RV370 / X1050 card) causes screen corruption after a while in X + firefox. This still occurs with yesterday's HEAD of Linus' repo. 3.16 and ealier kernels are fine. I ran a bisect, which identified: commit 72a9987edcedb89db988079a03c9b9c65b6ec9ac Author: Michel

Re: [3.12-rc1 regression] [BISECTED] X fails to start on Latitude E6510 w/ NOUVEAU DRM driver

I wrote: Dell Latitude E6510, CONFIG_DRM_NOUVEAU, 64-bit Fedora 17 user-space, Xorg drivers, and 01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2). With 3.11 X starts fine, with 3.12-rc1 it fails with the following in Xorg.0.log: ... [

[3.12-rc1 regression] X fails to start on Latitude E6510 w/ NOUVEAU DRM driver

Dell Latitude E6510, CONFIG_DRM_NOUVEAU, 64-bit Fedora 17 user-space, Xorg drivers, and 01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2). With 3.11 X starts fine, with 3.12-rc1 it fails with the following in Xorg.0.log: ... [56.819] (II) Loading

[3.11-rc4] Possible problem with nouveau drm driver and interrupts on Dell Latitude E6510

My Latitude E6510 has the following graphics HW: 01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude E6510 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at e200 (32-bit,

[3.11-rc4] Possible problem with nouveau drm driver and interrupts on Dell Latitude E6510

My Latitude E6510 has the following graphics HW: 01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude E6510 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at e200 (32-bit,