* [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2022-12-28 14:49 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2022-12-28 14:49 UTC (permalink / raw)
To: diogo.ivo; +Cc: nouveau, airlied, regressions, dri-devel, bskeggs
Hello,
Commit 2541626cfb79 breaks GM20B probe with
the following kernel log:
[ 2.153892] ------------[ cut here ]------------
[ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
[ 2.153916] Modules linked in:
[ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
[ 2.153929] Hardware name: Google Pixel C (DT)
[ 2.153933] Workqueue: events_unbound deferred_probe_work_func
[ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
[ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
[ 2.153966] sp : ffffffc009e134b0
[ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
[ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
[ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
[ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
[ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
[ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
[ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
[ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
[ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
[ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
[ 2.154050] Call trace:
[ 2.154053] gf100_vmm_valid+0x2c4/0x390
[ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
[ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
[ 2.154076] nvkm_vmm_map+0x50/0x84
[ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
[ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
[ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
[ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
[ 2.154114] nvkm_subdev_init_+0x3c/0x12c
[ 2.154119] nvkm_subdev_init+0x60/0xa0
[ 2.154125] nvkm_device_init+0x14c/0x2a0
[ 2.154133] nvkm_udevice_init+0x60/0x9c
[ 2.154140] nvkm_object_init+0x48/0x1b0
[ 2.154144] nvkm_ioctl_new+0x168/0x254
[ 2.154149] nvkm_ioctl+0xd0/0x220
[ 2.154153] nvkm_client_ioctl+0x10/0x1c
[ 2.154162] nvif_object_ctor+0xf4/0x22c
[ 2.154168] nvif_device_ctor+0x28/0x70
[ 2.154174] nouveau_cli_init+0x150/0x590
[ 2.154180] nouveau_drm_device_init+0x60/0x2a0
[ 2.154187] nouveau_platform_device_create+0x90/0xd0
[ 2.154193] nouveau_platform_probe+0x3c/0x9c
[ 2.154200] platform_probe+0x68/0xc0
[ 2.154207] really_probe+0xbc/0x2dc
[ 2.154211] __driver_probe_device+0x78/0xe0
[ 2.154216] driver_probe_device+0xd8/0x160
[ 2.154221] __device_attach_driver+0xb8/0x134
[ 2.154226] bus_for_each_drv+0x78/0xd0
[ 2.154230] __device_attach+0x9c/0x1a0
[ 2.154234] device_initial_probe+0x14/0x20
[ 2.154239] bus_probe_device+0x98/0xa0
[ 2.154243] deferred_probe_work_func+0x88/0xc0
[ 2.154247] process_one_work+0x204/0x40c
[ 2.154256] worker_thread+0x230/0x450
[ 2.154261] kthread+0xc8/0xcc
[ 2.154266] ret_from_fork+0x10/0x20
[ 2.154273] ---[ end trace 0000000000000000 ]---
[ 2.154278] nouveau 57000000.gpu: pmu: map -22
[ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
[ 2.154559] nouveau 57000000.gpu: init failed with -22
[ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
[ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
[ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
#regzbot introduced: 2541626cfb79
Thanks,
Diogo Ivo
^ permalink raw reply [flat|nested] 60+ messages in thread
* [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2022-12-28 14:49 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2022-12-28 14:49 UTC (permalink / raw)
To: diogo.ivo; +Cc: regressions, bskeggs, dri-devel, nouveau, airlied
Hello,
Commit 2541626cfb79 breaks GM20B probe with
the following kernel log:
[ 2.153892] ------------[ cut here ]------------
[ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
[ 2.153916] Modules linked in:
[ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
[ 2.153929] Hardware name: Google Pixel C (DT)
[ 2.153933] Workqueue: events_unbound deferred_probe_work_func
[ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
[ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
[ 2.153966] sp : ffffffc009e134b0
[ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
[ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
[ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
[ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
[ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
[ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
[ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
[ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
[ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
[ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
[ 2.154050] Call trace:
[ 2.154053] gf100_vmm_valid+0x2c4/0x390
[ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
[ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
[ 2.154076] nvkm_vmm_map+0x50/0x84
[ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
[ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
[ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
[ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
[ 2.154114] nvkm_subdev_init_+0x3c/0x12c
[ 2.154119] nvkm_subdev_init+0x60/0xa0
[ 2.154125] nvkm_device_init+0x14c/0x2a0
[ 2.154133] nvkm_udevice_init+0x60/0x9c
[ 2.154140] nvkm_object_init+0x48/0x1b0
[ 2.154144] nvkm_ioctl_new+0x168/0x254
[ 2.154149] nvkm_ioctl+0xd0/0x220
[ 2.154153] nvkm_client_ioctl+0x10/0x1c
[ 2.154162] nvif_object_ctor+0xf4/0x22c
[ 2.154168] nvif_device_ctor+0x28/0x70
[ 2.154174] nouveau_cli_init+0x150/0x590
[ 2.154180] nouveau_drm_device_init+0x60/0x2a0
[ 2.154187] nouveau_platform_device_create+0x90/0xd0
[ 2.154193] nouveau_platform_probe+0x3c/0x9c
[ 2.154200] platform_probe+0x68/0xc0
[ 2.154207] really_probe+0xbc/0x2dc
[ 2.154211] __driver_probe_device+0x78/0xe0
[ 2.154216] driver_probe_device+0xd8/0x160
[ 2.154221] __device_attach_driver+0xb8/0x134
[ 2.154226] bus_for_each_drv+0x78/0xd0
[ 2.154230] __device_attach+0x9c/0x1a0
[ 2.154234] device_initial_probe+0x14/0x20
[ 2.154239] bus_probe_device+0x98/0xa0
[ 2.154243] deferred_probe_work_func+0x88/0xc0
[ 2.154247] process_one_work+0x204/0x40c
[ 2.154256] worker_thread+0x230/0x450
[ 2.154261] kthread+0xc8/0xcc
[ 2.154266] ret_from_fork+0x10/0x20
[ 2.154273] ---[ end trace 0000000000000000 ]---
[ 2.154278] nouveau 57000000.gpu: pmu: map -22
[ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
[ 2.154559] nouveau 57000000.gpu: init failed with -22
[ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
[ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
[ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
#regzbot introduced: 2541626cfb79
Thanks,
Diogo Ivo
^ permalink raw reply [flat|nested] 60+ messages in thread
* [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2022-12-28 14:49 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2022-12-28 14:49 UTC (permalink / raw)
To: diogo.ivo; +Cc: nouveau, airlied, regressions, dri-devel, bskeggs
Hello,
Commit 2541626cfb79 breaks GM20B probe with
the following kernel log:
[ 2.153892] ------------[ cut here ]------------
[ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
[ 2.153916] Modules linked in:
[ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
[ 2.153929] Hardware name: Google Pixel C (DT)
[ 2.153933] Workqueue: events_unbound deferred_probe_work_func
[ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
[ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
[ 2.153966] sp : ffffffc009e134b0
[ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
[ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
[ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
[ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
[ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
[ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
[ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
[ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
[ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
[ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
[ 2.154050] Call trace:
[ 2.154053] gf100_vmm_valid+0x2c4/0x390
[ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
[ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
[ 2.154076] nvkm_vmm_map+0x50/0x84
[ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
[ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
[ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
[ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
[ 2.154114] nvkm_subdev_init_+0x3c/0x12c
[ 2.154119] nvkm_subdev_init+0x60/0xa0
[ 2.154125] nvkm_device_init+0x14c/0x2a0
[ 2.154133] nvkm_udevice_init+0x60/0x9c
[ 2.154140] nvkm_object_init+0x48/0x1b0
[ 2.154144] nvkm_ioctl_new+0x168/0x254
[ 2.154149] nvkm_ioctl+0xd0/0x220
[ 2.154153] nvkm_client_ioctl+0x10/0x1c
[ 2.154162] nvif_object_ctor+0xf4/0x22c
[ 2.154168] nvif_device_ctor+0x28/0x70
[ 2.154174] nouveau_cli_init+0x150/0x590
[ 2.154180] nouveau_drm_device_init+0x60/0x2a0
[ 2.154187] nouveau_platform_device_create+0x90/0xd0
[ 2.154193] nouveau_platform_probe+0x3c/0x9c
[ 2.154200] platform_probe+0x68/0xc0
[ 2.154207] really_probe+0xbc/0x2dc
[ 2.154211] __driver_probe_device+0x78/0xe0
[ 2.154216] driver_probe_device+0xd8/0x160
[ 2.154221] __device_attach_driver+0xb8/0x134
[ 2.154226] bus_for_each_drv+0x78/0xd0
[ 2.154230] __device_attach+0x9c/0x1a0
[ 2.154234] device_initial_probe+0x14/0x20
[ 2.154239] bus_probe_device+0x98/0xa0
[ 2.154243] deferred_probe_work_func+0x88/0xc0
[ 2.154247] process_one_work+0x204/0x40c
[ 2.154256] worker_thread+0x230/0x450
[ 2.154261] kthread+0xc8/0xcc
[ 2.154266] ret_from_fork+0x10/0x20
[ 2.154273] ---[ end trace 0000000000000000 ]---
[ 2.154278] nouveau 57000000.gpu: pmu: map -22
[ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
[ 2.154559] nouveau 57000000.gpu: init failed with -22
[ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
[ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
[ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
#regzbot introduced: 2541626cfb79
Thanks,
Diogo Ivo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2022-12-28 14:49 ` Diogo Ivo
(?)
@ 2023-01-05 12:28 ` Thorsten Leemhuis
-1 siblings, 0 replies; 60+ messages in thread
From: Thorsten Leemhuis @ 2023-01-05 12:28 UTC (permalink / raw)
To: bskeggs, Karol Herbst, Lyude Paul
Cc: regressions, dri-devel, nouveau, airlied, Diogo Ivo
[adding Karol and Lyude to the list of recipients]
Hi, this is your Linux kernel regression tracker. Top-posting for once,
to make this easily accessible to everyone.
On 28.12.22 15:49, Diogo Ivo wrote:
> Hello,
>
> Commit 2541626cfb79 breaks GM20B probe with
> the following kernel log:
Just wondering: is anyone looking on this? The report was posted more
than a week ago and didn't even get a single reply yet afaics. This of
course can happen at this time of the year, but I nevertheless thought a
quick status inquiry might be a good idea at this point.
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.
> [ 2.153892] ------------[ cut here ]------------
> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> [ 2.153916] Modules linked in:
> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> [ 2.153929] Hardware name: Google Pixel C (DT)
> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
> [ 2.153966] sp : ffffffc009e134b0
> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> [ 2.154050] Call trace:
> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
> [ 2.154076] nvkm_vmm_map+0x50/0x84
> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
> [ 2.154119] nvkm_subdev_init+0x60/0xa0
> [ 2.154125] nvkm_device_init+0x14c/0x2a0
> [ 2.154133] nvkm_udevice_init+0x60/0x9c
> [ 2.154140] nvkm_object_init+0x48/0x1b0
> [ 2.154144] nvkm_ioctl_new+0x168/0x254
> [ 2.154149] nvkm_ioctl+0xd0/0x220
> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
> [ 2.154162] nvif_object_ctor+0xf4/0x22c
> [ 2.154168] nvif_device_ctor+0x28/0x70
> [ 2.154174] nouveau_cli_init+0x150/0x590
> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
> [ 2.154200] platform_probe+0x68/0xc0
> [ 2.154207] really_probe+0xbc/0x2dc
> [ 2.154211] __driver_probe_device+0x78/0xe0
> [ 2.154216] driver_probe_device+0xd8/0x160
> [ 2.154221] __device_attach_driver+0xb8/0x134
> [ 2.154226] bus_for_each_drv+0x78/0xd0
> [ 2.154230] __device_attach+0x9c/0x1a0
> [ 2.154234] device_initial_probe+0x14/0x20
> [ 2.154239] bus_probe_device+0x98/0xa0
> [ 2.154243] deferred_probe_work_func+0x88/0xc0
> [ 2.154247] process_one_work+0x204/0x40c
> [ 2.154256] worker_thread+0x230/0x450
> [ 2.154261] kthread+0xc8/0xcc
> [ 2.154266] ret_from_fork+0x10/0x20
> [ 2.154273] ---[ end trace 0000000000000000 ]---
> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> [ 2.154559] nouveau 57000000.gpu: init failed with -22
> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
>
> #regzbot introduced: 2541626cfb79
>
> Thanks,
>
> Diogo Ivo
>
>
#regzbot poke
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-05 12:28 ` Thorsten Leemhuis
0 siblings, 0 replies; 60+ messages in thread
From: Thorsten Leemhuis @ 2023-01-05 12:28 UTC (permalink / raw)
To: bskeggs, Karol Herbst, Lyude Paul
Cc: nouveau, Diogo Ivo, regressions, dri-devel, airlied
[adding Karol and Lyude to the list of recipients]
Hi, this is your Linux kernel regression tracker. Top-posting for once,
to make this easily accessible to everyone.
On 28.12.22 15:49, Diogo Ivo wrote:
> Hello,
>
> Commit 2541626cfb79 breaks GM20B probe with
> the following kernel log:
Just wondering: is anyone looking on this? The report was posted more
than a week ago and didn't even get a single reply yet afaics. This of
course can happen at this time of the year, but I nevertheless thought a
quick status inquiry might be a good idea at this point.
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.
> [ 2.153892] ------------[ cut here ]------------
> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> [ 2.153916] Modules linked in:
> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> [ 2.153929] Hardware name: Google Pixel C (DT)
> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
> [ 2.153966] sp : ffffffc009e134b0
> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> [ 2.154050] Call trace:
> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
> [ 2.154076] nvkm_vmm_map+0x50/0x84
> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
> [ 2.154119] nvkm_subdev_init+0x60/0xa0
> [ 2.154125] nvkm_device_init+0x14c/0x2a0
> [ 2.154133] nvkm_udevice_init+0x60/0x9c
> [ 2.154140] nvkm_object_init+0x48/0x1b0
> [ 2.154144] nvkm_ioctl_new+0x168/0x254
> [ 2.154149] nvkm_ioctl+0xd0/0x220
> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
> [ 2.154162] nvif_object_ctor+0xf4/0x22c
> [ 2.154168] nvif_device_ctor+0x28/0x70
> [ 2.154174] nouveau_cli_init+0x150/0x590
> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
> [ 2.154200] platform_probe+0x68/0xc0
> [ 2.154207] really_probe+0xbc/0x2dc
> [ 2.154211] __driver_probe_device+0x78/0xe0
> [ 2.154216] driver_probe_device+0xd8/0x160
> [ 2.154221] __device_attach_driver+0xb8/0x134
> [ 2.154226] bus_for_each_drv+0x78/0xd0
> [ 2.154230] __device_attach+0x9c/0x1a0
> [ 2.154234] device_initial_probe+0x14/0x20
> [ 2.154239] bus_probe_device+0x98/0xa0
> [ 2.154243] deferred_probe_work_func+0x88/0xc0
> [ 2.154247] process_one_work+0x204/0x40c
> [ 2.154256] worker_thread+0x230/0x450
> [ 2.154261] kthread+0xc8/0xcc
> [ 2.154266] ret_from_fork+0x10/0x20
> [ 2.154273] ---[ end trace 0000000000000000 ]---
> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> [ 2.154559] nouveau 57000000.gpu: init failed with -22
> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
>
> #regzbot introduced: 2541626cfb79
>
> Thanks,
>
> Diogo Ivo
>
>
#regzbot poke
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-05 12:28 ` Thorsten Leemhuis
0 siblings, 0 replies; 60+ messages in thread
From: Thorsten Leemhuis @ 2023-01-05 12:28 UTC (permalink / raw)
To: bskeggs, Karol Herbst, Lyude Paul
Cc: nouveau, Diogo Ivo, regressions, dri-devel, airlied
[adding Karol and Lyude to the list of recipients]
Hi, this is your Linux kernel regression tracker. Top-posting for once,
to make this easily accessible to everyone.
On 28.12.22 15:49, Diogo Ivo wrote:
> Hello,
>
> Commit 2541626cfb79 breaks GM20B probe with
> the following kernel log:
Just wondering: is anyone looking on this? The report was posted more
than a week ago and didn't even get a single reply yet afaics. This of
course can happen at this time of the year, but I nevertheless thought a
quick status inquiry might be a good idea at this point.
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.
> [ 2.153892] ------------[ cut here ]------------
> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> [ 2.153916] Modules linked in:
> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> [ 2.153929] Hardware name: Google Pixel C (DT)
> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
> [ 2.153966] sp : ffffffc009e134b0
> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> [ 2.154050] Call trace:
> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
> [ 2.154076] nvkm_vmm_map+0x50/0x84
> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
> [ 2.154119] nvkm_subdev_init+0x60/0xa0
> [ 2.154125] nvkm_device_init+0x14c/0x2a0
> [ 2.154133] nvkm_udevice_init+0x60/0x9c
> [ 2.154140] nvkm_object_init+0x48/0x1b0
> [ 2.154144] nvkm_ioctl_new+0x168/0x254
> [ 2.154149] nvkm_ioctl+0xd0/0x220
> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
> [ 2.154162] nvif_object_ctor+0xf4/0x22c
> [ 2.154168] nvif_device_ctor+0x28/0x70
> [ 2.154174] nouveau_cli_init+0x150/0x590
> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
> [ 2.154200] platform_probe+0x68/0xc0
> [ 2.154207] really_probe+0xbc/0x2dc
> [ 2.154211] __driver_probe_device+0x78/0xe0
> [ 2.154216] driver_probe_device+0xd8/0x160
> [ 2.154221] __device_attach_driver+0xb8/0x134
> [ 2.154226] bus_for_each_drv+0x78/0xd0
> [ 2.154230] __device_attach+0x9c/0x1a0
> [ 2.154234] device_initial_probe+0x14/0x20
> [ 2.154239] bus_probe_device+0x98/0xa0
> [ 2.154243] deferred_probe_work_func+0x88/0xc0
> [ 2.154247] process_one_work+0x204/0x40c
> [ 2.154256] worker_thread+0x230/0x450
> [ 2.154261] kthread+0xc8/0xcc
> [ 2.154266] ret_from_fork+0x10/0x20
> [ 2.154273] ---[ end trace 0000000000000000 ]---
> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> [ 2.154559] nouveau 57000000.gpu: init failed with -22
> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
>
> #regzbot introduced: 2541626cfb79
>
> Thanks,
>
> Diogo Ivo
>
>
#regzbot poke
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-05 12:28 ` Thorsten Leemhuis
(?)
@ 2023-01-13 13:19 ` Linux kernel regression tracking (Thorsten Leemhuis)
-1 siblings, 0 replies; 60+ messages in thread
From: Linux kernel regression tracking (Thorsten Leemhuis) @ 2023-01-13 13:19 UTC (permalink / raw)
To: bskeggs, Karol Herbst, Lyude Paul
Cc: regressions, dri-devel, nouveau, airlied, Diogo Ivo, Daniel Vetter
[CCing Daniel]
On 05.01.23 13:28, Thorsten Leemhuis wrote:
> [adding Karol and Lyude to the list of recipients]
>
> On 28.12.22 15:49, Diogo Ivo wrote:
>> Hello,
>>
>> Commit 2541626cfb79 breaks GM20B probe with
>> the following kernel log:
> Just wondering: is anyone looking on this? The report was posted more
> than a week ago and didn't even get a single reply yet afaics. This of
> course can happen at this time of the year, but I nevertheless thought a
> quick status inquiry might be a good idea at this point.
Hmmm, the report is now more that two weeks old and didn't get a single
reply. My prodding about a week ago also didn't help. Then I guess I
have to bring this to Linus attention, unless something happens in the
next 2 days.
Diogo, for that it would be really helpful to known: is the issue still
happening with latest mainline? Is it possible to revert 2541626cfb79
easily? And if so: do things work afterwards again?
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
>> [ 2.153892] ------------[ cut here ]------------
>> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
>> [ 2.153916] Modules linked in:
>> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
>> [ 2.153929] Hardware name: Google Pixel C (DT)
>> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
>> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
>> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
>> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
>> [ 2.153966] sp : ffffffc009e134b0
>> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
>> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
>> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
>> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
>> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
>> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
>> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
>> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
>> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
>> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
>> [ 2.154050] Call trace:
>> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
>> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
>> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
>> [ 2.154076] nvkm_vmm_map+0x50/0x84
>> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
>> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
>> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
>> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
>> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
>> [ 2.154119] nvkm_subdev_init+0x60/0xa0
>> [ 2.154125] nvkm_device_init+0x14c/0x2a0
>> [ 2.154133] nvkm_udevice_init+0x60/0x9c
>> [ 2.154140] nvkm_object_init+0x48/0x1b0
>> [ 2.154144] nvkm_ioctl_new+0x168/0x254
>> [ 2.154149] nvkm_ioctl+0xd0/0x220
>> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
>> [ 2.154162] nvif_object_ctor+0xf4/0x22c
>> [ 2.154168] nvif_device_ctor+0x28/0x70
>> [ 2.154174] nouveau_cli_init+0x150/0x590
>> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
>> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
>> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
>> [ 2.154200] platform_probe+0x68/0xc0
>> [ 2.154207] really_probe+0xbc/0x2dc
>> [ 2.154211] __driver_probe_device+0x78/0xe0
>> [ 2.154216] driver_probe_device+0xd8/0x160
>> [ 2.154221] __device_attach_driver+0xb8/0x134
>> [ 2.154226] bus_for_each_drv+0x78/0xd0
>> [ 2.154230] __device_attach+0x9c/0x1a0
>> [ 2.154234] device_initial_probe+0x14/0x20
>> [ 2.154239] bus_probe_device+0x98/0xa0
>> [ 2.154243] deferred_probe_work_func+0x88/0xc0
>> [ 2.154247] process_one_work+0x204/0x40c
>> [ 2.154256] worker_thread+0x230/0x450
>> [ 2.154261] kthread+0xc8/0xcc
>> [ 2.154266] ret_from_fork+0x10/0x20
>> [ 2.154273] ---[ end trace 0000000000000000 ]---
>> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
>> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
>> [ 2.154559] nouveau 57000000.gpu: init failed with -22
>> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
>> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
>> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
>>
>> #regzbot introduced: 2541626cfb79
>>
>> Thanks,
>>
>> Diogo Ivo
>>
>>
>
> #regzbot poke
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-13 13:19 ` Linux kernel regression tracking (Thorsten Leemhuis)
0 siblings, 0 replies; 60+ messages in thread
From: Linux kernel regression tracking (Thorsten Leemhuis) @ 2023-01-13 13:19 UTC (permalink / raw)
To: bskeggs, Karol Herbst, Lyude Paul
Cc: regressions, nouveau, dri-devel, Diogo Ivo, Daniel Vetter, airlied
[CCing Daniel]
On 05.01.23 13:28, Thorsten Leemhuis wrote:
> [adding Karol and Lyude to the list of recipients]
>
> On 28.12.22 15:49, Diogo Ivo wrote:
>> Hello,
>>
>> Commit 2541626cfb79 breaks GM20B probe with
>> the following kernel log:
> Just wondering: is anyone looking on this? The report was posted more
> than a week ago and didn't even get a single reply yet afaics. This of
> course can happen at this time of the year, but I nevertheless thought a
> quick status inquiry might be a good idea at this point.
Hmmm, the report is now more that two weeks old and didn't get a single
reply. My prodding about a week ago also didn't help. Then I guess I
have to bring this to Linus attention, unless something happens in the
next 2 days.
Diogo, for that it would be really helpful to known: is the issue still
happening with latest mainline? Is it possible to revert 2541626cfb79
easily? And if so: do things work afterwards again?
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
>> [ 2.153892] ------------[ cut here ]------------
>> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
>> [ 2.153916] Modules linked in:
>> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
>> [ 2.153929] Hardware name: Google Pixel C (DT)
>> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
>> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
>> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
>> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
>> [ 2.153966] sp : ffffffc009e134b0
>> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
>> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
>> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
>> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
>> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
>> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
>> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
>> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
>> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
>> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
>> [ 2.154050] Call trace:
>> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
>> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
>> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
>> [ 2.154076] nvkm_vmm_map+0x50/0x84
>> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
>> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
>> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
>> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
>> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
>> [ 2.154119] nvkm_subdev_init+0x60/0xa0
>> [ 2.154125] nvkm_device_init+0x14c/0x2a0
>> [ 2.154133] nvkm_udevice_init+0x60/0x9c
>> [ 2.154140] nvkm_object_init+0x48/0x1b0
>> [ 2.154144] nvkm_ioctl_new+0x168/0x254
>> [ 2.154149] nvkm_ioctl+0xd0/0x220
>> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
>> [ 2.154162] nvif_object_ctor+0xf4/0x22c
>> [ 2.154168] nvif_device_ctor+0x28/0x70
>> [ 2.154174] nouveau_cli_init+0x150/0x590
>> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
>> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
>> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
>> [ 2.154200] platform_probe+0x68/0xc0
>> [ 2.154207] really_probe+0xbc/0x2dc
>> [ 2.154211] __driver_probe_device+0x78/0xe0
>> [ 2.154216] driver_probe_device+0xd8/0x160
>> [ 2.154221] __device_attach_driver+0xb8/0x134
>> [ 2.154226] bus_for_each_drv+0x78/0xd0
>> [ 2.154230] __device_attach+0x9c/0x1a0
>> [ 2.154234] device_initial_probe+0x14/0x20
>> [ 2.154239] bus_probe_device+0x98/0xa0
>> [ 2.154243] deferred_probe_work_func+0x88/0xc0
>> [ 2.154247] process_one_work+0x204/0x40c
>> [ 2.154256] worker_thread+0x230/0x450
>> [ 2.154261] kthread+0xc8/0xcc
>> [ 2.154266] ret_from_fork+0x10/0x20
>> [ 2.154273] ---[ end trace 0000000000000000 ]---
>> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
>> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
>> [ 2.154559] nouveau 57000000.gpu: init failed with -22
>> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
>> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
>> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
>>
>> #regzbot introduced: 2541626cfb79
>>
>> Thanks,
>>
>> Diogo Ivo
>>
>>
>
> #regzbot poke
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-13 13:19 ` Linux kernel regression tracking (Thorsten Leemhuis)
0 siblings, 0 replies; 60+ messages in thread
From: Linux kernel regression tracking (Thorsten Leemhuis) @ 2023-01-13 13:19 UTC (permalink / raw)
To: bskeggs, Karol Herbst, Lyude Paul
Cc: regressions, nouveau, dri-devel, Diogo Ivo, airlied
[CCing Daniel]
On 05.01.23 13:28, Thorsten Leemhuis wrote:
> [adding Karol and Lyude to the list of recipients]
>
> On 28.12.22 15:49, Diogo Ivo wrote:
>> Hello,
>>
>> Commit 2541626cfb79 breaks GM20B probe with
>> the following kernel log:
> Just wondering: is anyone looking on this? The report was posted more
> than a week ago and didn't even get a single reply yet afaics. This of
> course can happen at this time of the year, but I nevertheless thought a
> quick status inquiry might be a good idea at this point.
Hmmm, the report is now more that two weeks old and didn't get a single
reply. My prodding about a week ago also didn't help. Then I guess I
have to bring this to Linus attention, unless something happens in the
next 2 days.
Diogo, for that it would be really helpful to known: is the issue still
happening with latest mainline? Is it possible to revert 2541626cfb79
easily? And if so: do things work afterwards again?
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
>> [ 2.153892] ------------[ cut here ]------------
>> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
>> [ 2.153916] Modules linked in:
>> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
>> [ 2.153929] Hardware name: Google Pixel C (DT)
>> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
>> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
>> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
>> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
>> [ 2.153966] sp : ffffffc009e134b0
>> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
>> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
>> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
>> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
>> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
>> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
>> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
>> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
>> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
>> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
>> [ 2.154050] Call trace:
>> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
>> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
>> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
>> [ 2.154076] nvkm_vmm_map+0x50/0x84
>> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
>> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
>> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
>> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
>> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
>> [ 2.154119] nvkm_subdev_init+0x60/0xa0
>> [ 2.154125] nvkm_device_init+0x14c/0x2a0
>> [ 2.154133] nvkm_udevice_init+0x60/0x9c
>> [ 2.154140] nvkm_object_init+0x48/0x1b0
>> [ 2.154144] nvkm_ioctl_new+0x168/0x254
>> [ 2.154149] nvkm_ioctl+0xd0/0x220
>> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
>> [ 2.154162] nvif_object_ctor+0xf4/0x22c
>> [ 2.154168] nvif_device_ctor+0x28/0x70
>> [ 2.154174] nouveau_cli_init+0x150/0x590
>> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
>> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
>> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
>> [ 2.154200] platform_probe+0x68/0xc0
>> [ 2.154207] really_probe+0xbc/0x2dc
>> [ 2.154211] __driver_probe_device+0x78/0xe0
>> [ 2.154216] driver_probe_device+0xd8/0x160
>> [ 2.154221] __device_attach_driver+0xb8/0x134
>> [ 2.154226] bus_for_each_drv+0x78/0xd0
>> [ 2.154230] __device_attach+0x9c/0x1a0
>> [ 2.154234] device_initial_probe+0x14/0x20
>> [ 2.154239] bus_probe_device+0x98/0xa0
>> [ 2.154243] deferred_probe_work_func+0x88/0xc0
>> [ 2.154247] process_one_work+0x204/0x40c
>> [ 2.154256] worker_thread+0x230/0x450
>> [ 2.154261] kthread+0xc8/0xcc
>> [ 2.154266] ret_from_fork+0x10/0x20
>> [ 2.154273] ---[ end trace 0000000000000000 ]---
>> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
>> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
>> [ 2.154559] nouveau 57000000.gpu: init failed with -22
>> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
>> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
>> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
>>
>> #regzbot introduced: 2541626cfb79
>>
>> Thanks,
>>
>> Diogo Ivo
>>
>>
>
> #regzbot poke
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-13 13:19 ` [Nouveau] " Linux kernel regression tracking (Thorsten Leemhuis)
(?)
@ 2023-01-14 3:27 ` Karol Herbst
-1 siblings, 0 replies; 60+ messages in thread
From: Karol Herbst @ 2023-01-14 3:27 UTC (permalink / raw)
To: Linux regressions mailing list
Cc: nouveau, dri-devel, Diogo Ivo, bskeggs, Daniel Vetter, airlied
[-- Attachment #1: Type: text/plain, Size: 6916 bytes --]
On Fri, Jan 13, 2023 at 2:19 PM Linux kernel regression tracking
(Thorsten Leemhuis) <regressions@leemhuis.info> wrote:
>
> [CCing Daniel]
>
> On 05.01.23 13:28, Thorsten Leemhuis wrote:
> > [adding Karol and Lyude to the list of recipients]
> >
> > On 28.12.22 15:49, Diogo Ivo wrote:
> >> Hello,
> >>
> >> Commit 2541626cfb79 breaks GM20B probe with
> >> the following kernel log:
> > Just wondering: is anyone looking on this? The report was posted more
> > than a week ago and didn't even get a single reply yet afaics. This of
> > course can happen at this time of the year, but I nevertheless thought a
> > quick status inquiry might be a good idea at this point.
>
> Hmmm, the report is now more that two weeks old and didn't get a single
> reply. My prodding about a week ago also didn't help. Then I guess I
> have to bring this to Linus attention, unless something happens in the
> next 2 days.
>
I tried to look into it, but my jetson nano, just constantly behaves
in very strange ways. I tried to compile and install a 6.1 kernel onto
it, but any kernel just refuses to boot and I have no idea what's up
with that device. The kernel starts to boot and it just stops in the
middle. From what I can tell is that most of the tegra devices never
worked reliably in the first place and there are a couple of random
and strange bugs around. I've attached my dmesg, so if anybody has any
clues why the kernel just stops doing anything, it would really help
me.
But maybe it would be for the best to just pull tegra support out of
nouveau, because in the current situation we really can't spare much
time dealing with them and we are already busy enough just dealing
with the desktop GPUs. And the firmware we got from Nvidia is so
ancient and different from the desktop GPU ones, that without actually
having all those boards available and properly tested, we can't be
sure to not break them.
And afaik there are almost no _actual_ users, just distribution folks
wanting to claim "support" for those devices, but then ending up using
Nvidia's out of tree Tegra driver in deployments anyway.
If there are actual users using them for their daily life, I'd like to
know, because I'm aware of none.
If there are companies/entities actually caring about those devices
running _nouveau_, I'd be happy to keep supporting them, but then only
with proper kernel CI, because the current situation is just not
sustainable.
Ben, Lyude, Dave, Daniel, any thoughts on that?
> Diogo, for that it would be really helpful to known: is the issue still
> happening with latest mainline? Is it possible to revert 2541626cfb79
> easily? And if so: do things work afterwards again?
>
> 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
>
> >> [ 2.153892] ------------[ cut here ]------------
> >> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> >> [ 2.153916] Modules linked in:
> >> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> >> [ 2.153929] Hardware name: Google Pixel C (DT)
> >> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> >> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> >> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> >> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
> >> [ 2.153966] sp : ffffffc009e134b0
> >> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> >> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> >> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> >> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> >> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> >> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> >> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> >> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> >> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> >> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> >> [ 2.154050] Call trace:
> >> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
> >> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
> >> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
> >> [ 2.154076] nvkm_vmm_map+0x50/0x84
> >> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
> >> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
> >> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
> >> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
> >> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
> >> [ 2.154119] nvkm_subdev_init+0x60/0xa0
> >> [ 2.154125] nvkm_device_init+0x14c/0x2a0
> >> [ 2.154133] nvkm_udevice_init+0x60/0x9c
> >> [ 2.154140] nvkm_object_init+0x48/0x1b0
> >> [ 2.154144] nvkm_ioctl_new+0x168/0x254
> >> [ 2.154149] nvkm_ioctl+0xd0/0x220
> >> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
> >> [ 2.154162] nvif_object_ctor+0xf4/0x22c
> >> [ 2.154168] nvif_device_ctor+0x28/0x70
> >> [ 2.154174] nouveau_cli_init+0x150/0x590
> >> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
> >> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
> >> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
> >> [ 2.154200] platform_probe+0x68/0xc0
> >> [ 2.154207] really_probe+0xbc/0x2dc
> >> [ 2.154211] __driver_probe_device+0x78/0xe0
> >> [ 2.154216] driver_probe_device+0xd8/0x160
> >> [ 2.154221] __device_attach_driver+0xb8/0x134
> >> [ 2.154226] bus_for_each_drv+0x78/0xd0
> >> [ 2.154230] __device_attach+0x9c/0x1a0
> >> [ 2.154234] device_initial_probe+0x14/0x20
> >> [ 2.154239] bus_probe_device+0x98/0xa0
> >> [ 2.154243] deferred_probe_work_func+0x88/0xc0
> >> [ 2.154247] process_one_work+0x204/0x40c
> >> [ 2.154256] worker_thread+0x230/0x450
> >> [ 2.154261] kthread+0xc8/0xcc
> >> [ 2.154266] ret_from_fork+0x10/0x20
> >> [ 2.154273] ---[ end trace 0000000000000000 ]---
> >> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
> >> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> >> [ 2.154559] nouveau 57000000.gpu: init failed with -22
> >> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> >> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> >> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
> >>
> >> #regzbot introduced: 2541626cfb79
> >>
> >> Thanks,
> >>
> >> Diogo Ivo
> >>
> >>
> >
> > #regzbot poke
>
[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 18397 bytes --]
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd071]
[ 0.000000] Linux version 6.1.5 (root@fedora) (gcc (GCC) 12.2.1 20221121 (Red Hat 12.2.1-4), GNU ld version 2.38-25.fc37) #3 SMP PREEMPT_DYNAMIC Fri Jan 13 20:33:37 EST 2023
[ 0.000000] Machine model: NVIDIA Jetson Nano Developer Kit
[ 0.000000] earlycon: uart8250 at MMIO32 0x0000000070006000 (options '')
[ 0.000000] printk: bootconsole [uart8250] enabled
[ 0.000000] efi: EFI v2.90 by Das U-Boot
[ 0.000000] efi: RTPROP=0xfb5e5040 SMBIOS=0xfb5e4000 MOKvar=0xfb4b5000 MEMRESERVE=0xfb4ac040
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb0_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb0_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb1_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb1_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] NUMA: No NUMA configuration found
[ 0.000000] NUMA: Faking a node at [mem 0x0000000040001000-0x000000017f1fffff]
[ 0.000000] NUMA: NODE_DATA [mem 0x17e8c9a40-0x17e8dffff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000040001000-0x00000000ffffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal [mem 0x0000000100000000-0x000000017f1fffff]
[ 0.000000] Device empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000040001000-0x000000004003ffff]
[ 0.000000] node 0: [mem 0x0000000080000000-0x000000008001ffff]
[ 0.000000] node 0: [mem 0x0000000080020000-0x00000000afffffff]
[ 0.000000] node 0: [mem 0x00000000b0000000-0x00000000b01fffff]
[ 0.000000] node 0: [mem 0x00000000b0200000-0x00000000fb4b4fff]
[ 0.000000] node 0: [mem 0x00000000fb4b5000-0x00000000fb4b5fff]
[ 0.000000] node 0: [mem 0x00000000fb4b6000-0x00000000fb4fcfff]
[ 0.000000] node 0: [mem 0x00000000fb4fd000-0x00000000fb4fdfff]
[ 0.000000] node 0: [mem 0x00000000fb4fe000-0x00000000fb5e3fff]
[ 0.000000] node 0: [mem 0x00000000fb5e4000-0x00000000fb5e7fff]
[ 0.000000] node 0: [mem 0x00000000fb5e8000-0x00000000fb5e8fff]
[ 0.000000] node 0: [mem 0x00000000fb5e9000-0x00000000fb5ecfff]
[ 0.000000] node 0: [mem 0x00000000fb5ed000-0x00000000fed2ffff]
[ 0.000000] node 0: [mem 0x00000000fed30000-0x00000000fed3ffff]
[ 0.000000] node 0: [mem 0x00000000fed40000-0x00000000fedfffff]
[ 0.000000] node 0: [mem 0x0000000100000000-0x000000017f1fffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000040001000-0x000000017f1fffff]
[ 0.000000] On node 0, zone DMA: 1 pages in unavailable ranges
[ 0.000000] On node 0, zone DMA: 32704 pages in unavailable ranges
[ 0.000000] On node 0, zone Normal: 4608 pages in unavailable ranges
[ 0.000000] On node 0, zone Normal: 3584 pages in unavailable ranges
[ 0.000000] cma: Reserved 64 MiB at 0x00000000f7200000
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.0 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] psci: SMC Calling Convention v1.1
[ 0.000000] percpu: Embedded 31 pages/cpu s88616 r8192 d30168 u126976
[ 0.000000] pcpu-alloc: s88616 r8192 d30168 u126976 alloc=31*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Detected PIPT I-cache on CPU0
[ 0.000000] CPU features: detected: Spectre-v2
[ 0.000000] CPU features: detected: Spectre-v3a
[ 0.000000] CPU features: detected: Spectre-BHB
[ 0.000000] CPU features: kernel page table isolation forced ON by KASLR
[ 0.000000] CPU features: detected: Kernel page table isolation (KPTI)
[ 0.000000] CPU features: detected: ARM erratum 834220
[ 0.000000] CPU features: detected: ARM erratum 1742098
[ 0.000000] CPU features: detected: ARM erratum 832075
[ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[ 0.000000] alternatives: applying boot alternatives
[ 0.000000] Fallback order for Node 0: 0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1024190
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=(hd0,msdos2)/vmlinuz-6.1.5 root=UUID=8ade1e40-a2ab-48ac-aa5d-182a8cb026c0 ro rootflags=subvol=root loglevel=8 earlycon=uart8250,mmio32,0x70006000 console=ttyS0,115200n8
[ 0.000000] Unknown kernel command line parameters "BOOT_IMAGE=(hd0,msdos2)/vmlinuz-6.1.5", will be passed to user space.
[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[ 0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
[ 0.000000] software IO TLB: area num 4.
[ 0.000000] software IO TLB: mapped [mem 0x00000000cd400000-0x00000000d1400000] (64MB)
[ 0.000000] Memory: 3344928K/4161788K available (16576K kernel code, 4204K rwdata, 13972K rodata, 9216K init, 10651K bss, 751324K reserved, 65536K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] ftrace: allocating 57252 entries in 224 pages
[ 0.000000] ftrace: allocated 224 pages with 3 groups
[ 0.000000] trace event string verifier disabled
[ 0.000000] Dynamic Preempt: voluntary
[ 0.000000] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4096 to nr_cpu_ids=4.
[ 0.000000] Trampoline variant of Tasks RCU enabled.
[ 0.000000] Rude variant of Tasks RCU enabled.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] GIC: GICv2 detected, but range too small and irqchip.gicv2_force_probe not set
[ 0.000000] Root IRQ handler: gic_handle_irq
[ 0.000000] /interrupt-controller@60004000: 192 interrupts forwarded to /interrupt-controller
[ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[ 0.000001] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[ 0.008345] tegra-timer: failed to map irq for cpu0
[ 0.013398] Failed to initialize '/timer@60005000': -22
[ 0.020674] kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval____)-0x(____ptrval____)
[ 0.031299] Console: colour dummy device 80x25
[ 0.036104] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[ 0.046826] pid_max: default: 32768 minimum: 301
[ 0.051841] LSM: Security Framework initializing
[ 0.056682] Yama: becoming mindful.
[ 0.060342] SELinux: Initializing.
[ 0.064163] LSM support for eBPF active
[ 0.068125] landlock: Up and running.
[ 0.072118] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.079791] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.090951] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.098490] cblist_init_generic: Setting shift to 2 and lim to 1.
[ 0.104973] cblist_init_generic: Setting shift to 2 and lim to 1.
[ 0.111419] cblist_init_generic: Setting shift to 2 and lim to 1.
[ 0.118000] rcu: Hierarchical SRCU implementation.
[ 0.122964] rcu: Max phase no-delay instances is 1000.
[ 0.134829] Speedo Revision 4
[ 0.137913] Tegra210: unknown SKU 0x8f
[ 0.141799] Tegra Revision: A02 SKU: 143 CPU Process: 0 SoC Process: 0
[ 0.149507] tegra-pmc: access to PMC is restricted to TZ
[ 0.155038] Remapping and enabling EFI services.
[ 0.160719] smp: Bringing up secondary CPUs ...
[ 0.166356] Detected PIPT I-cache on CPU1
[ 0.166573] CPU1: Booted secondary processor 0x0000000001 [0x411fd071]
[ 0.167684] Detected PIPT I-cache on CPU2
[ 0.167817] CPU2: Booted secondary processor 0x0000000002 [0x411fd071]
[ 0.168741] Detected PIPT I-cache on CPU3
[ 0.168861] CPU3: Booted secondary processor 0x0000000003 [0x411fd071]
[ 0.168980] smp: Brought up 1 node, 4 CPUs
[ 0.205882] SMP: Total of 4 processors activated.
[ 0.210738] CPU features: detected: 32-bit EL0 Support
[ 0.216061] CPU features: detected: 32-bit EL1 Support
[ 0.221370] CPU features: detected: CRC32 instructions
[ 0.226816] CPU features: emulated: Privileged Access Never (PAN) using TTBR0_EL1 switching
[ 0.235450] CPU: All CPU(s) started at EL2
[ 0.239721] alternatives: applying system-wide alternatives
[ 0.251737] devtmpfs: initialized
[ 0.294478] Registered cp15_barrier emulation handler
[ 0.299740] Registered setend emulation handler
[ 0.304762] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.314967] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.324669] pinctrl core: initialized pinctrl subsystem
[ 0.331375] SMBIOS 3.0 present.
[ 0.334635] DMI: Unknown Unknown Product/Unknown Product, BIOS 2022.04 04/01/2022
[ 0.343286] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.350808] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations
[ 0.358403] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.366657] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.374990] audit: initializing netlink subsys (disabled)
[ 0.380915] audit: type=2000 audit(0.290:1): state=initialized audit_enabled=0 res=1
[ 0.384079] thermal_sys: Registered thermal governor 'fair_share'
[ 0.388975] thermal_sys: Registered thermal governor 'step_wise'
[ 0.395279] thermal_sys: Registered thermal governor 'user_space'
[ 0.401589] cpuidle: using governor menu
[ 0.412234] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.419417] ASID allocator initialised with 32768 entries
[ 0.426035] Serial: AMBA PL011 UART driver
[ 0.446128] tegra210-pinctrl 700008d4.pinmux: there is not valid maps for state drive
[ 0.481462] tegra-mc 70019000.memory-controller: no memory timings for RAM code 0 registered
[ 0.509090] KASLR enabled
[ 0.522092] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.529124] HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page
[ 0.535984] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[ 0.543002] HugeTLB: 508 KiB vmemmap can be freed for a 32.0 MiB page
[ 0.549670] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.556689] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page
[ 0.563272] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[ 0.570289] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[ 0.578205] cryptd: max_cpu_qlen set to 1000
[ 0.583875] raid6: skipped pq benchmark and selected neonx8
[ 0.589685] raid6: using neon recovery algorithm
[ 0.595632] ACPI: Interpreter disabled.
[ 0.603308] iommu: Default domain type: Translated
[ 0.608357] iommu: DMA domain TLB invalidation policy: lazy mode
[ 0.615363] SCSI subsystem initialized
[ 0.619478] libata version 3.00 loaded.
[ 0.623697] usbcore: registered new interface driver usbfs
[ 0.629434] usbcore: registered new interface driver hub
[ 0.634955] usbcore: registered new device driver usb
[ 0.640650] pps_core: LinuxPPS API ver. 1 registered
[ 0.645784] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.655249] PTP clock support registered
[ 0.659539] EDAC MC: Ver: 3.0.0
[ 0.664242] Registered efivars operations
[ 0.669853] NetLabel: Initializing
[ 0.673374] NetLabel: domain hash size = 128
[ 0.677873] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.683811] NetLabel: unlabeled traffic allowed by default
[ 0.689582] mctp: management component transport protocol core
[ 0.695623] NET: Registered PF_MCTP protocol family
[ 0.701073] vgaarb: loaded
[ 0.704468] clocksource: Switched to clocksource arch_sys_counter
[ 0.823127] VFS: Disk quotas dquot_6.6.0
[ 0.827367] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.835017] pnp: PnP ACPI: disabled
[ 0.848393] NET: Registered PF_INET protocol family
[ 0.853889] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
[ 0.865308] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[ 0.874180] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.882314] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[ 0.890779] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes, linear)
[ 0.899367] TCP: Hash tables configured (established 32768 bind 32768)
[ 0.906664] MPTCP token hash table entries: 4096 (order: 4, 98304 bytes, linear)
[ 0.914563] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[ 0.921576] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
[ 0.929342] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.935288] NET: Registered PF_XDP protocol family
[ 0.940250] PCI: CLS 0 bytes, default 64
[ 0.944723] Trying to unpack rootfs image as initramfs...
[ 0.951701] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[ 0.961025] kvm [1]: Guests without required CPU erratum workarounds can deadlock system!
[ 0.961025] Only trusted guests should be used on this system.
[ 0.975538] kvm [1]: IPA Size Limit: 44 bits
[ 0.983862] kvm [1]: Hyp mode initialized successfully
[ 0.992472] Initialise system trusted keyrings
[ 0.997203] Key type blacklist registered
[ 1.001784] workingset: timestamp_bits=37 max_order=20 bucket_order=0
[ 1.019514] zbud: loaded
[ 1.027162] integrity: Platform Keyring initialized
[ 1.032268] integrity: Machine keyring initialized
[ 1.075202] NET: Registered PF_ALG protocol family
[ 1.080193] xor: measuring software checksum speed
[ 1.087180] 8regs : 4889 MB/sec
[ 1.093570] 32regs : 5211 MB/sec
[ 1.100678] arm64_neon : 3793 MB/sec
[ 1.105192] xor: using function: 32regs (5211 MB/sec)
[ 1.110425] Key type asymmetric registered
[ 1.114660] Asymmetric key parser 'x509' registered
[ 8.298270] Freeing initrd memory: 131308K
[ 8.329463] alg: self-tests for CTR-KDF (hmac(sha256)) passed
[ 8.335660] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[ 8.343538] io scheduler mq-deadline registered
[ 8.348245] io scheduler kyber registered
[ 8.352681] io scheduler bfq registered
[ 8.363489] atomic64_test: passed
[ 8.401688] tegra-apbdma 60020000.dma: Tegra20 APB DMA driver registered 32 channels
[ 8.417141] tegra-pmc 7000e400.pmc: i2c-thermtrip node not found, emergency thermal reset disabled.
[ 8.430604] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 8.448097] msm_serial: driver initialized
[ 8.462926] usbcore: registered new interface driver usbserial_generic
[ 8.469744] usbserial: USB Serial support registered for generic
[ 8.476215] mousedev: PS/2 mouse device common for all mice
[ 8.485840] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[ 8.498577] device-mapper: uevent: version 1.0.3
[ 8.503760] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
[ 8.515847] ledtrig-cpu: registered to indicate activity on CPUs
[ 8.524282] hid: raw HID events driver (C) Jiri Kosina
[ 8.529853] usbcore: registered new interface driver usbhid
[ 8.535628] usbhid: USB HID core driver
[ 8.546967] drop_monitor: Initializing network drop monitor service
[ 8.615329] Initializing XFRM netlink socket
[ 8.620692] NET: Registered PF_INET6 protocol family
[ 8.653474] Segment Routing with IPv6
[ 8.657316] RPL Segment Routing with IPv6
[ 8.661563] In-situ OAM (IOAM) with IPv6
[ 8.665780] mip6: Mobile IPv6
[ 8.668879] NET: Registered PF_PACKET protocol family
[ 8.676227] registered taskstats version 1
[ 8.681725] Loading compiled-in X.509 certificates
[ 8.718979] Loaded X.509 cert 'Build time autogenerated kernel key: 0f87d8bf07ebde2f3dffab5a01f044e6c3e615b7'
[ 8.730513] zswap: loaded using pool lzo/zbud
[ 8.735436] page_owner is disabled
[ 8.739238] Key type .fscrypt registered
[ 8.743297] Key type fscrypt-provisioning registered
[ 8.750791] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity=yes
[ 8.757870] Key type big_key registered
[ 8.762536] Key type encrypted registered
[ 8.766932] ima: secureboot mode disabled
[ 8.771087] ima: No TPM chip found, activating TPM-bypass!
[ 8.776779] Loading compiled-in module X.509 certificates
[ 8.784253] Loaded X.509 cert 'Build time autogenerated kernel key: 0f87d8bf07ebde2f3dffab5a01f044e6c3e615b7'
[ 8.794520] ima: Allocated hash algorithm: sha256
[ 8.799445] ima: No architecture policies found
[ 8.804213] evm: Initialising EVM extended attributes:
[ 8.809526] evm: security.selinux
[ 8.812948] evm: security.SMACK64 (disabled)
[ 8.817357] evm: security.SMACK64EXEC (disabled)
[ 8.822124] evm: security.SMACK64TRANSMUTE (disabled)
[ 8.827343] evm: security.SMACK64MMAP (disabled)
[ 8.832114] evm: security.apparmor (disabled)
[ 8.836613] evm: security.ima
[ 8.839672] evm: security.capability
[ 8.843363] evm: HMAC attrs: 0x1
[ 8.946174] alg: No test for 842 (842-scomp)
[ 8.950792] alg: No test for 842 (842-generic)
[ 9.391834] gpio-6 (system-suspend-gpio): hogged as output/high
[ 9.398001] gpio-151 (camera-control-output-low): hogged as output/low
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-14 3:27 ` Karol Herbst
0 siblings, 0 replies; 60+ messages in thread
From: Karol Herbst @ 2023-01-14 3:27 UTC (permalink / raw)
To: Linux regressions mailing list
Cc: nouveau, dri-devel, Diogo Ivo, bskeggs, airlied
[-- Attachment #1: Type: text/plain, Size: 6916 bytes --]
On Fri, Jan 13, 2023 at 2:19 PM Linux kernel regression tracking
(Thorsten Leemhuis) <regressions@leemhuis.info> wrote:
>
> [CCing Daniel]
>
> On 05.01.23 13:28, Thorsten Leemhuis wrote:
> > [adding Karol and Lyude to the list of recipients]
> >
> > On 28.12.22 15:49, Diogo Ivo wrote:
> >> Hello,
> >>
> >> Commit 2541626cfb79 breaks GM20B probe with
> >> the following kernel log:
> > Just wondering: is anyone looking on this? The report was posted more
> > than a week ago and didn't even get a single reply yet afaics. This of
> > course can happen at this time of the year, but I nevertheless thought a
> > quick status inquiry might be a good idea at this point.
>
> Hmmm, the report is now more that two weeks old and didn't get a single
> reply. My prodding about a week ago also didn't help. Then I guess I
> have to bring this to Linus attention, unless something happens in the
> next 2 days.
>
I tried to look into it, but my jetson nano, just constantly behaves
in very strange ways. I tried to compile and install a 6.1 kernel onto
it, but any kernel just refuses to boot and I have no idea what's up
with that device. The kernel starts to boot and it just stops in the
middle. From what I can tell is that most of the tegra devices never
worked reliably in the first place and there are a couple of random
and strange bugs around. I've attached my dmesg, so if anybody has any
clues why the kernel just stops doing anything, it would really help
me.
But maybe it would be for the best to just pull tegra support out of
nouveau, because in the current situation we really can't spare much
time dealing with them and we are already busy enough just dealing
with the desktop GPUs. And the firmware we got from Nvidia is so
ancient and different from the desktop GPU ones, that without actually
having all those boards available and properly tested, we can't be
sure to not break them.
And afaik there are almost no _actual_ users, just distribution folks
wanting to claim "support" for those devices, but then ending up using
Nvidia's out of tree Tegra driver in deployments anyway.
If there are actual users using them for their daily life, I'd like to
know, because I'm aware of none.
If there are companies/entities actually caring about those devices
running _nouveau_, I'd be happy to keep supporting them, but then only
with proper kernel CI, because the current situation is just not
sustainable.
Ben, Lyude, Dave, Daniel, any thoughts on that?
> Diogo, for that it would be really helpful to known: is the issue still
> happening with latest mainline? Is it possible to revert 2541626cfb79
> easily? And if so: do things work afterwards again?
>
> 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
>
> >> [ 2.153892] ------------[ cut here ]------------
> >> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> >> [ 2.153916] Modules linked in:
> >> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> >> [ 2.153929] Hardware name: Google Pixel C (DT)
> >> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> >> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> >> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> >> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
> >> [ 2.153966] sp : ffffffc009e134b0
> >> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> >> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> >> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> >> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> >> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> >> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> >> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> >> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> >> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> >> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> >> [ 2.154050] Call trace:
> >> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
> >> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
> >> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
> >> [ 2.154076] nvkm_vmm_map+0x50/0x84
> >> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
> >> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
> >> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
> >> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
> >> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
> >> [ 2.154119] nvkm_subdev_init+0x60/0xa0
> >> [ 2.154125] nvkm_device_init+0x14c/0x2a0
> >> [ 2.154133] nvkm_udevice_init+0x60/0x9c
> >> [ 2.154140] nvkm_object_init+0x48/0x1b0
> >> [ 2.154144] nvkm_ioctl_new+0x168/0x254
> >> [ 2.154149] nvkm_ioctl+0xd0/0x220
> >> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
> >> [ 2.154162] nvif_object_ctor+0xf4/0x22c
> >> [ 2.154168] nvif_device_ctor+0x28/0x70
> >> [ 2.154174] nouveau_cli_init+0x150/0x590
> >> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
> >> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
> >> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
> >> [ 2.154200] platform_probe+0x68/0xc0
> >> [ 2.154207] really_probe+0xbc/0x2dc
> >> [ 2.154211] __driver_probe_device+0x78/0xe0
> >> [ 2.154216] driver_probe_device+0xd8/0x160
> >> [ 2.154221] __device_attach_driver+0xb8/0x134
> >> [ 2.154226] bus_for_each_drv+0x78/0xd0
> >> [ 2.154230] __device_attach+0x9c/0x1a0
> >> [ 2.154234] device_initial_probe+0x14/0x20
> >> [ 2.154239] bus_probe_device+0x98/0xa0
> >> [ 2.154243] deferred_probe_work_func+0x88/0xc0
> >> [ 2.154247] process_one_work+0x204/0x40c
> >> [ 2.154256] worker_thread+0x230/0x450
> >> [ 2.154261] kthread+0xc8/0xcc
> >> [ 2.154266] ret_from_fork+0x10/0x20
> >> [ 2.154273] ---[ end trace 0000000000000000 ]---
> >> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
> >> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> >> [ 2.154559] nouveau 57000000.gpu: init failed with -22
> >> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> >> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> >> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
> >>
> >> #regzbot introduced: 2541626cfb79
> >>
> >> Thanks,
> >>
> >> Diogo Ivo
> >>
> >>
> >
> > #regzbot poke
>
[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 18397 bytes --]
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd071]
[ 0.000000] Linux version 6.1.5 (root@fedora) (gcc (GCC) 12.2.1 20221121 (Red Hat 12.2.1-4), GNU ld version 2.38-25.fc37) #3 SMP PREEMPT_DYNAMIC Fri Jan 13 20:33:37 EST 2023
[ 0.000000] Machine model: NVIDIA Jetson Nano Developer Kit
[ 0.000000] earlycon: uart8250 at MMIO32 0x0000000070006000 (options '')
[ 0.000000] printk: bootconsole [uart8250] enabled
[ 0.000000] efi: EFI v2.90 by Das U-Boot
[ 0.000000] efi: RTPROP=0xfb5e5040 SMBIOS=0xfb5e4000 MOKvar=0xfb4b5000 MEMRESERVE=0xfb4ac040
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb0_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb0_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb1_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb1_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] NUMA: No NUMA configuration found
[ 0.000000] NUMA: Faking a node at [mem 0x0000000040001000-0x000000017f1fffff]
[ 0.000000] NUMA: NODE_DATA [mem 0x17e8c9a40-0x17e8dffff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000040001000-0x00000000ffffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal [mem 0x0000000100000000-0x000000017f1fffff]
[ 0.000000] Device empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000040001000-0x000000004003ffff]
[ 0.000000] node 0: [mem 0x0000000080000000-0x000000008001ffff]
[ 0.000000] node 0: [mem 0x0000000080020000-0x00000000afffffff]
[ 0.000000] node 0: [mem 0x00000000b0000000-0x00000000b01fffff]
[ 0.000000] node 0: [mem 0x00000000b0200000-0x00000000fb4b4fff]
[ 0.000000] node 0: [mem 0x00000000fb4b5000-0x00000000fb4b5fff]
[ 0.000000] node 0: [mem 0x00000000fb4b6000-0x00000000fb4fcfff]
[ 0.000000] node 0: [mem 0x00000000fb4fd000-0x00000000fb4fdfff]
[ 0.000000] node 0: [mem 0x00000000fb4fe000-0x00000000fb5e3fff]
[ 0.000000] node 0: [mem 0x00000000fb5e4000-0x00000000fb5e7fff]
[ 0.000000] node 0: [mem 0x00000000fb5e8000-0x00000000fb5e8fff]
[ 0.000000] node 0: [mem 0x00000000fb5e9000-0x00000000fb5ecfff]
[ 0.000000] node 0: [mem 0x00000000fb5ed000-0x00000000fed2ffff]
[ 0.000000] node 0: [mem 0x00000000fed30000-0x00000000fed3ffff]
[ 0.000000] node 0: [mem 0x00000000fed40000-0x00000000fedfffff]
[ 0.000000] node 0: [mem 0x0000000100000000-0x000000017f1fffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000040001000-0x000000017f1fffff]
[ 0.000000] On node 0, zone DMA: 1 pages in unavailable ranges
[ 0.000000] On node 0, zone DMA: 32704 pages in unavailable ranges
[ 0.000000] On node 0, zone Normal: 4608 pages in unavailable ranges
[ 0.000000] On node 0, zone Normal: 3584 pages in unavailable ranges
[ 0.000000] cma: Reserved 64 MiB at 0x00000000f7200000
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.0 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] psci: SMC Calling Convention v1.1
[ 0.000000] percpu: Embedded 31 pages/cpu s88616 r8192 d30168 u126976
[ 0.000000] pcpu-alloc: s88616 r8192 d30168 u126976 alloc=31*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Detected PIPT I-cache on CPU0
[ 0.000000] CPU features: detected: Spectre-v2
[ 0.000000] CPU features: detected: Spectre-v3a
[ 0.000000] CPU features: detected: Spectre-BHB
[ 0.000000] CPU features: kernel page table isolation forced ON by KASLR
[ 0.000000] CPU features: detected: Kernel page table isolation (KPTI)
[ 0.000000] CPU features: detected: ARM erratum 834220
[ 0.000000] CPU features: detected: ARM erratum 1742098
[ 0.000000] CPU features: detected: ARM erratum 832075
[ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[ 0.000000] alternatives: applying boot alternatives
[ 0.000000] Fallback order for Node 0: 0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1024190
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=(hd0,msdos2)/vmlinuz-6.1.5 root=UUID=8ade1e40-a2ab-48ac-aa5d-182a8cb026c0 ro rootflags=subvol=root loglevel=8 earlycon=uart8250,mmio32,0x70006000 console=ttyS0,115200n8
[ 0.000000] Unknown kernel command line parameters "BOOT_IMAGE=(hd0,msdos2)/vmlinuz-6.1.5", will be passed to user space.
[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[ 0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
[ 0.000000] software IO TLB: area num 4.
[ 0.000000] software IO TLB: mapped [mem 0x00000000cd400000-0x00000000d1400000] (64MB)
[ 0.000000] Memory: 3344928K/4161788K available (16576K kernel code, 4204K rwdata, 13972K rodata, 9216K init, 10651K bss, 751324K reserved, 65536K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] ftrace: allocating 57252 entries in 224 pages
[ 0.000000] ftrace: allocated 224 pages with 3 groups
[ 0.000000] trace event string verifier disabled
[ 0.000000] Dynamic Preempt: voluntary
[ 0.000000] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4096 to nr_cpu_ids=4.
[ 0.000000] Trampoline variant of Tasks RCU enabled.
[ 0.000000] Rude variant of Tasks RCU enabled.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] GIC: GICv2 detected, but range too small and irqchip.gicv2_force_probe not set
[ 0.000000] Root IRQ handler: gic_handle_irq
[ 0.000000] /interrupt-controller@60004000: 192 interrupts forwarded to /interrupt-controller
[ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[ 0.000001] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[ 0.008345] tegra-timer: failed to map irq for cpu0
[ 0.013398] Failed to initialize '/timer@60005000': -22
[ 0.020674] kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval____)-0x(____ptrval____)
[ 0.031299] Console: colour dummy device 80x25
[ 0.036104] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[ 0.046826] pid_max: default: 32768 minimum: 301
[ 0.051841] LSM: Security Framework initializing
[ 0.056682] Yama: becoming mindful.
[ 0.060342] SELinux: Initializing.
[ 0.064163] LSM support for eBPF active
[ 0.068125] landlock: Up and running.
[ 0.072118] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.079791] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.090951] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.098490] cblist_init_generic: Setting shift to 2 and lim to 1.
[ 0.104973] cblist_init_generic: Setting shift to 2 and lim to 1.
[ 0.111419] cblist_init_generic: Setting shift to 2 and lim to 1.
[ 0.118000] rcu: Hierarchical SRCU implementation.
[ 0.122964] rcu: Max phase no-delay instances is 1000.
[ 0.134829] Speedo Revision 4
[ 0.137913] Tegra210: unknown SKU 0x8f
[ 0.141799] Tegra Revision: A02 SKU: 143 CPU Process: 0 SoC Process: 0
[ 0.149507] tegra-pmc: access to PMC is restricted to TZ
[ 0.155038] Remapping and enabling EFI services.
[ 0.160719] smp: Bringing up secondary CPUs ...
[ 0.166356] Detected PIPT I-cache on CPU1
[ 0.166573] CPU1: Booted secondary processor 0x0000000001 [0x411fd071]
[ 0.167684] Detected PIPT I-cache on CPU2
[ 0.167817] CPU2: Booted secondary processor 0x0000000002 [0x411fd071]
[ 0.168741] Detected PIPT I-cache on CPU3
[ 0.168861] CPU3: Booted secondary processor 0x0000000003 [0x411fd071]
[ 0.168980] smp: Brought up 1 node, 4 CPUs
[ 0.205882] SMP: Total of 4 processors activated.
[ 0.210738] CPU features: detected: 32-bit EL0 Support
[ 0.216061] CPU features: detected: 32-bit EL1 Support
[ 0.221370] CPU features: detected: CRC32 instructions
[ 0.226816] CPU features: emulated: Privileged Access Never (PAN) using TTBR0_EL1 switching
[ 0.235450] CPU: All CPU(s) started at EL2
[ 0.239721] alternatives: applying system-wide alternatives
[ 0.251737] devtmpfs: initialized
[ 0.294478] Registered cp15_barrier emulation handler
[ 0.299740] Registered setend emulation handler
[ 0.304762] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.314967] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.324669] pinctrl core: initialized pinctrl subsystem
[ 0.331375] SMBIOS 3.0 present.
[ 0.334635] DMI: Unknown Unknown Product/Unknown Product, BIOS 2022.04 04/01/2022
[ 0.343286] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.350808] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations
[ 0.358403] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.366657] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.374990] audit: initializing netlink subsys (disabled)
[ 0.380915] audit: type=2000 audit(0.290:1): state=initialized audit_enabled=0 res=1
[ 0.384079] thermal_sys: Registered thermal governor 'fair_share'
[ 0.388975] thermal_sys: Registered thermal governor 'step_wise'
[ 0.395279] thermal_sys: Registered thermal governor 'user_space'
[ 0.401589] cpuidle: using governor menu
[ 0.412234] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.419417] ASID allocator initialised with 32768 entries
[ 0.426035] Serial: AMBA PL011 UART driver
[ 0.446128] tegra210-pinctrl 700008d4.pinmux: there is not valid maps for state drive
[ 0.481462] tegra-mc 70019000.memory-controller: no memory timings for RAM code 0 registered
[ 0.509090] KASLR enabled
[ 0.522092] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.529124] HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page
[ 0.535984] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[ 0.543002] HugeTLB: 508 KiB vmemmap can be freed for a 32.0 MiB page
[ 0.549670] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.556689] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page
[ 0.563272] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[ 0.570289] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[ 0.578205] cryptd: max_cpu_qlen set to 1000
[ 0.583875] raid6: skipped pq benchmark and selected neonx8
[ 0.589685] raid6: using neon recovery algorithm
[ 0.595632] ACPI: Interpreter disabled.
[ 0.603308] iommu: Default domain type: Translated
[ 0.608357] iommu: DMA domain TLB invalidation policy: lazy mode
[ 0.615363] SCSI subsystem initialized
[ 0.619478] libata version 3.00 loaded.
[ 0.623697] usbcore: registered new interface driver usbfs
[ 0.629434] usbcore: registered new interface driver hub
[ 0.634955] usbcore: registered new device driver usb
[ 0.640650] pps_core: LinuxPPS API ver. 1 registered
[ 0.645784] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.655249] PTP clock support registered
[ 0.659539] EDAC MC: Ver: 3.0.0
[ 0.664242] Registered efivars operations
[ 0.669853] NetLabel: Initializing
[ 0.673374] NetLabel: domain hash size = 128
[ 0.677873] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.683811] NetLabel: unlabeled traffic allowed by default
[ 0.689582] mctp: management component transport protocol core
[ 0.695623] NET: Registered PF_MCTP protocol family
[ 0.701073] vgaarb: loaded
[ 0.704468] clocksource: Switched to clocksource arch_sys_counter
[ 0.823127] VFS: Disk quotas dquot_6.6.0
[ 0.827367] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.835017] pnp: PnP ACPI: disabled
[ 0.848393] NET: Registered PF_INET protocol family
[ 0.853889] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
[ 0.865308] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[ 0.874180] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.882314] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[ 0.890779] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes, linear)
[ 0.899367] TCP: Hash tables configured (established 32768 bind 32768)
[ 0.906664] MPTCP token hash table entries: 4096 (order: 4, 98304 bytes, linear)
[ 0.914563] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[ 0.921576] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
[ 0.929342] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.935288] NET: Registered PF_XDP protocol family
[ 0.940250] PCI: CLS 0 bytes, default 64
[ 0.944723] Trying to unpack rootfs image as initramfs...
[ 0.951701] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[ 0.961025] kvm [1]: Guests without required CPU erratum workarounds can deadlock system!
[ 0.961025] Only trusted guests should be used on this system.
[ 0.975538] kvm [1]: IPA Size Limit: 44 bits
[ 0.983862] kvm [1]: Hyp mode initialized successfully
[ 0.992472] Initialise system trusted keyrings
[ 0.997203] Key type blacklist registered
[ 1.001784] workingset: timestamp_bits=37 max_order=20 bucket_order=0
[ 1.019514] zbud: loaded
[ 1.027162] integrity: Platform Keyring initialized
[ 1.032268] integrity: Machine keyring initialized
[ 1.075202] NET: Registered PF_ALG protocol family
[ 1.080193] xor: measuring software checksum speed
[ 1.087180] 8regs : 4889 MB/sec
[ 1.093570] 32regs : 5211 MB/sec
[ 1.100678] arm64_neon : 3793 MB/sec
[ 1.105192] xor: using function: 32regs (5211 MB/sec)
[ 1.110425] Key type asymmetric registered
[ 1.114660] Asymmetric key parser 'x509' registered
[ 8.298270] Freeing initrd memory: 131308K
[ 8.329463] alg: self-tests for CTR-KDF (hmac(sha256)) passed
[ 8.335660] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[ 8.343538] io scheduler mq-deadline registered
[ 8.348245] io scheduler kyber registered
[ 8.352681] io scheduler bfq registered
[ 8.363489] atomic64_test: passed
[ 8.401688] tegra-apbdma 60020000.dma: Tegra20 APB DMA driver registered 32 channels
[ 8.417141] tegra-pmc 7000e400.pmc: i2c-thermtrip node not found, emergency thermal reset disabled.
[ 8.430604] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 8.448097] msm_serial: driver initialized
[ 8.462926] usbcore: registered new interface driver usbserial_generic
[ 8.469744] usbserial: USB Serial support registered for generic
[ 8.476215] mousedev: PS/2 mouse device common for all mice
[ 8.485840] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[ 8.498577] device-mapper: uevent: version 1.0.3
[ 8.503760] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
[ 8.515847] ledtrig-cpu: registered to indicate activity on CPUs
[ 8.524282] hid: raw HID events driver (C) Jiri Kosina
[ 8.529853] usbcore: registered new interface driver usbhid
[ 8.535628] usbhid: USB HID core driver
[ 8.546967] drop_monitor: Initializing network drop monitor service
[ 8.615329] Initializing XFRM netlink socket
[ 8.620692] NET: Registered PF_INET6 protocol family
[ 8.653474] Segment Routing with IPv6
[ 8.657316] RPL Segment Routing with IPv6
[ 8.661563] In-situ OAM (IOAM) with IPv6
[ 8.665780] mip6: Mobile IPv6
[ 8.668879] NET: Registered PF_PACKET protocol family
[ 8.676227] registered taskstats version 1
[ 8.681725] Loading compiled-in X.509 certificates
[ 8.718979] Loaded X.509 cert 'Build time autogenerated kernel key: 0f87d8bf07ebde2f3dffab5a01f044e6c3e615b7'
[ 8.730513] zswap: loaded using pool lzo/zbud
[ 8.735436] page_owner is disabled
[ 8.739238] Key type .fscrypt registered
[ 8.743297] Key type fscrypt-provisioning registered
[ 8.750791] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity=yes
[ 8.757870] Key type big_key registered
[ 8.762536] Key type encrypted registered
[ 8.766932] ima: secureboot mode disabled
[ 8.771087] ima: No TPM chip found, activating TPM-bypass!
[ 8.776779] Loading compiled-in module X.509 certificates
[ 8.784253] Loaded X.509 cert 'Build time autogenerated kernel key: 0f87d8bf07ebde2f3dffab5a01f044e6c3e615b7'
[ 8.794520] ima: Allocated hash algorithm: sha256
[ 8.799445] ima: No architecture policies found
[ 8.804213] evm: Initialising EVM extended attributes:
[ 8.809526] evm: security.selinux
[ 8.812948] evm: security.SMACK64 (disabled)
[ 8.817357] evm: security.SMACK64EXEC (disabled)
[ 8.822124] evm: security.SMACK64TRANSMUTE (disabled)
[ 8.827343] evm: security.SMACK64MMAP (disabled)
[ 8.832114] evm: security.apparmor (disabled)
[ 8.836613] evm: security.ima
[ 8.839672] evm: security.capability
[ 8.843363] evm: HMAC attrs: 0x1
[ 8.946174] alg: No test for 842 (842-scomp)
[ 8.950792] alg: No test for 842 (842-generic)
[ 9.391834] gpio-6 (system-suspend-gpio): hogged as output/high
[ 9.398001] gpio-151 (camera-control-output-low): hogged as output/low
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-14 3:27 ` Karol Herbst
0 siblings, 0 replies; 60+ messages in thread
From: Karol Herbst @ 2023-01-14 3:27 UTC (permalink / raw)
To: Linux regressions mailing list
Cc: bskeggs, Lyude Paul, dri-devel, nouveau, airlied, Diogo Ivo,
Daniel Vetter
[-- Attachment #1: Type: text/plain, Size: 6916 bytes --]
On Fri, Jan 13, 2023 at 2:19 PM Linux kernel regression tracking
(Thorsten Leemhuis) <regressions@leemhuis.info> wrote:
>
> [CCing Daniel]
>
> On 05.01.23 13:28, Thorsten Leemhuis wrote:
> > [adding Karol and Lyude to the list of recipients]
> >
> > On 28.12.22 15:49, Diogo Ivo wrote:
> >> Hello,
> >>
> >> Commit 2541626cfb79 breaks GM20B probe with
> >> the following kernel log:
> > Just wondering: is anyone looking on this? The report was posted more
> > than a week ago and didn't even get a single reply yet afaics. This of
> > course can happen at this time of the year, but I nevertheless thought a
> > quick status inquiry might be a good idea at this point.
>
> Hmmm, the report is now more that two weeks old and didn't get a single
> reply. My prodding about a week ago also didn't help. Then I guess I
> have to bring this to Linus attention, unless something happens in the
> next 2 days.
>
I tried to look into it, but my jetson nano, just constantly behaves
in very strange ways. I tried to compile and install a 6.1 kernel onto
it, but any kernel just refuses to boot and I have no idea what's up
with that device. The kernel starts to boot and it just stops in the
middle. From what I can tell is that most of the tegra devices never
worked reliably in the first place and there are a couple of random
and strange bugs around. I've attached my dmesg, so if anybody has any
clues why the kernel just stops doing anything, it would really help
me.
But maybe it would be for the best to just pull tegra support out of
nouveau, because in the current situation we really can't spare much
time dealing with them and we are already busy enough just dealing
with the desktop GPUs. And the firmware we got from Nvidia is so
ancient and different from the desktop GPU ones, that without actually
having all those boards available and properly tested, we can't be
sure to not break them.
And afaik there are almost no _actual_ users, just distribution folks
wanting to claim "support" for those devices, but then ending up using
Nvidia's out of tree Tegra driver in deployments anyway.
If there are actual users using them for their daily life, I'd like to
know, because I'm aware of none.
If there are companies/entities actually caring about those devices
running _nouveau_, I'd be happy to keep supporting them, but then only
with proper kernel CI, because the current situation is just not
sustainable.
Ben, Lyude, Dave, Daniel, any thoughts on that?
> Diogo, for that it would be really helpful to known: is the issue still
> happening with latest mainline? Is it possible to revert 2541626cfb79
> easily? And if so: do things work afterwards again?
>
> 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
>
> >> [ 2.153892] ------------[ cut here ]------------
> >> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> >> [ 2.153916] Modules linked in:
> >> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> >> [ 2.153929] Hardware name: Google Pixel C (DT)
> >> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> >> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> >> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> >> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
> >> [ 2.153966] sp : ffffffc009e134b0
> >> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> >> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> >> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> >> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> >> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> >> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> >> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> >> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> >> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> >> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> >> [ 2.154050] Call trace:
> >> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
> >> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
> >> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
> >> [ 2.154076] nvkm_vmm_map+0x50/0x84
> >> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
> >> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
> >> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
> >> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
> >> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
> >> [ 2.154119] nvkm_subdev_init+0x60/0xa0
> >> [ 2.154125] nvkm_device_init+0x14c/0x2a0
> >> [ 2.154133] nvkm_udevice_init+0x60/0x9c
> >> [ 2.154140] nvkm_object_init+0x48/0x1b0
> >> [ 2.154144] nvkm_ioctl_new+0x168/0x254
> >> [ 2.154149] nvkm_ioctl+0xd0/0x220
> >> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
> >> [ 2.154162] nvif_object_ctor+0xf4/0x22c
> >> [ 2.154168] nvif_device_ctor+0x28/0x70
> >> [ 2.154174] nouveau_cli_init+0x150/0x590
> >> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
> >> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
> >> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
> >> [ 2.154200] platform_probe+0x68/0xc0
> >> [ 2.154207] really_probe+0xbc/0x2dc
> >> [ 2.154211] __driver_probe_device+0x78/0xe0
> >> [ 2.154216] driver_probe_device+0xd8/0x160
> >> [ 2.154221] __device_attach_driver+0xb8/0x134
> >> [ 2.154226] bus_for_each_drv+0x78/0xd0
> >> [ 2.154230] __device_attach+0x9c/0x1a0
> >> [ 2.154234] device_initial_probe+0x14/0x20
> >> [ 2.154239] bus_probe_device+0x98/0xa0
> >> [ 2.154243] deferred_probe_work_func+0x88/0xc0
> >> [ 2.154247] process_one_work+0x204/0x40c
> >> [ 2.154256] worker_thread+0x230/0x450
> >> [ 2.154261] kthread+0xc8/0xcc
> >> [ 2.154266] ret_from_fork+0x10/0x20
> >> [ 2.154273] ---[ end trace 0000000000000000 ]---
> >> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
> >> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> >> [ 2.154559] nouveau 57000000.gpu: init failed with -22
> >> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> >> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> >> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
> >>
> >> #regzbot introduced: 2541626cfb79
> >>
> >> Thanks,
> >>
> >> Diogo Ivo
> >>
> >>
> >
> > #regzbot poke
>
[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 18397 bytes --]
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd071]
[ 0.000000] Linux version 6.1.5 (root@fedora) (gcc (GCC) 12.2.1 20221121 (Red Hat 12.2.1-4), GNU ld version 2.38-25.fc37) #3 SMP PREEMPT_DYNAMIC Fri Jan 13 20:33:37 EST 2023
[ 0.000000] Machine model: NVIDIA Jetson Nano Developer Kit
[ 0.000000] earlycon: uart8250 at MMIO32 0x0000000070006000 (options '')
[ 0.000000] printk: bootconsole [uart8250] enabled
[ 0.000000] efi: EFI v2.90 by Das U-Boot
[ 0.000000] efi: RTPROP=0xfb5e5040 SMBIOS=0xfb5e4000 MOKvar=0xfb4b5000 MEMRESERVE=0xfb4ac040
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb0_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb0_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb1_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'fb1_carveout': base 0x0000000000000000, size 0 MiB
[ 0.000000] NUMA: No NUMA configuration found
[ 0.000000] NUMA: Faking a node at [mem 0x0000000040001000-0x000000017f1fffff]
[ 0.000000] NUMA: NODE_DATA [mem 0x17e8c9a40-0x17e8dffff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000040001000-0x00000000ffffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal [mem 0x0000000100000000-0x000000017f1fffff]
[ 0.000000] Device empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000040001000-0x000000004003ffff]
[ 0.000000] node 0: [mem 0x0000000080000000-0x000000008001ffff]
[ 0.000000] node 0: [mem 0x0000000080020000-0x00000000afffffff]
[ 0.000000] node 0: [mem 0x00000000b0000000-0x00000000b01fffff]
[ 0.000000] node 0: [mem 0x00000000b0200000-0x00000000fb4b4fff]
[ 0.000000] node 0: [mem 0x00000000fb4b5000-0x00000000fb4b5fff]
[ 0.000000] node 0: [mem 0x00000000fb4b6000-0x00000000fb4fcfff]
[ 0.000000] node 0: [mem 0x00000000fb4fd000-0x00000000fb4fdfff]
[ 0.000000] node 0: [mem 0x00000000fb4fe000-0x00000000fb5e3fff]
[ 0.000000] node 0: [mem 0x00000000fb5e4000-0x00000000fb5e7fff]
[ 0.000000] node 0: [mem 0x00000000fb5e8000-0x00000000fb5e8fff]
[ 0.000000] node 0: [mem 0x00000000fb5e9000-0x00000000fb5ecfff]
[ 0.000000] node 0: [mem 0x00000000fb5ed000-0x00000000fed2ffff]
[ 0.000000] node 0: [mem 0x00000000fed30000-0x00000000fed3ffff]
[ 0.000000] node 0: [mem 0x00000000fed40000-0x00000000fedfffff]
[ 0.000000] node 0: [mem 0x0000000100000000-0x000000017f1fffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000040001000-0x000000017f1fffff]
[ 0.000000] On node 0, zone DMA: 1 pages in unavailable ranges
[ 0.000000] On node 0, zone DMA: 32704 pages in unavailable ranges
[ 0.000000] On node 0, zone Normal: 4608 pages in unavailable ranges
[ 0.000000] On node 0, zone Normal: 3584 pages in unavailable ranges
[ 0.000000] cma: Reserved 64 MiB at 0x00000000f7200000
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.0 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] psci: SMC Calling Convention v1.1
[ 0.000000] percpu: Embedded 31 pages/cpu s88616 r8192 d30168 u126976
[ 0.000000] pcpu-alloc: s88616 r8192 d30168 u126976 alloc=31*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Detected PIPT I-cache on CPU0
[ 0.000000] CPU features: detected: Spectre-v2
[ 0.000000] CPU features: detected: Spectre-v3a
[ 0.000000] CPU features: detected: Spectre-BHB
[ 0.000000] CPU features: kernel page table isolation forced ON by KASLR
[ 0.000000] CPU features: detected: Kernel page table isolation (KPTI)
[ 0.000000] CPU features: detected: ARM erratum 834220
[ 0.000000] CPU features: detected: ARM erratum 1742098
[ 0.000000] CPU features: detected: ARM erratum 832075
[ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[ 0.000000] alternatives: applying boot alternatives
[ 0.000000] Fallback order for Node 0: 0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1024190
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=(hd0,msdos2)/vmlinuz-6.1.5 root=UUID=8ade1e40-a2ab-48ac-aa5d-182a8cb026c0 ro rootflags=subvol=root loglevel=8 earlycon=uart8250,mmio32,0x70006000 console=ttyS0,115200n8
[ 0.000000] Unknown kernel command line parameters "BOOT_IMAGE=(hd0,msdos2)/vmlinuz-6.1.5", will be passed to user space.
[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[ 0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
[ 0.000000] software IO TLB: area num 4.
[ 0.000000] software IO TLB: mapped [mem 0x00000000cd400000-0x00000000d1400000] (64MB)
[ 0.000000] Memory: 3344928K/4161788K available (16576K kernel code, 4204K rwdata, 13972K rodata, 9216K init, 10651K bss, 751324K reserved, 65536K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] ftrace: allocating 57252 entries in 224 pages
[ 0.000000] ftrace: allocated 224 pages with 3 groups
[ 0.000000] trace event string verifier disabled
[ 0.000000] Dynamic Preempt: voluntary
[ 0.000000] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4096 to nr_cpu_ids=4.
[ 0.000000] Trampoline variant of Tasks RCU enabled.
[ 0.000000] Rude variant of Tasks RCU enabled.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] GIC: GICv2 detected, but range too small and irqchip.gicv2_force_probe not set
[ 0.000000] Root IRQ handler: gic_handle_irq
[ 0.000000] /interrupt-controller@60004000: 192 interrupts forwarded to /interrupt-controller
[ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[ 0.000001] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[ 0.008345] tegra-timer: failed to map irq for cpu0
[ 0.013398] Failed to initialize '/timer@60005000': -22
[ 0.020674] kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval____)-0x(____ptrval____)
[ 0.031299] Console: colour dummy device 80x25
[ 0.036104] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[ 0.046826] pid_max: default: 32768 minimum: 301
[ 0.051841] LSM: Security Framework initializing
[ 0.056682] Yama: becoming mindful.
[ 0.060342] SELinux: Initializing.
[ 0.064163] LSM support for eBPF active
[ 0.068125] landlock: Up and running.
[ 0.072118] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.079791] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.090951] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.098490] cblist_init_generic: Setting shift to 2 and lim to 1.
[ 0.104973] cblist_init_generic: Setting shift to 2 and lim to 1.
[ 0.111419] cblist_init_generic: Setting shift to 2 and lim to 1.
[ 0.118000] rcu: Hierarchical SRCU implementation.
[ 0.122964] rcu: Max phase no-delay instances is 1000.
[ 0.134829] Speedo Revision 4
[ 0.137913] Tegra210: unknown SKU 0x8f
[ 0.141799] Tegra Revision: A02 SKU: 143 CPU Process: 0 SoC Process: 0
[ 0.149507] tegra-pmc: access to PMC is restricted to TZ
[ 0.155038] Remapping and enabling EFI services.
[ 0.160719] smp: Bringing up secondary CPUs ...
[ 0.166356] Detected PIPT I-cache on CPU1
[ 0.166573] CPU1: Booted secondary processor 0x0000000001 [0x411fd071]
[ 0.167684] Detected PIPT I-cache on CPU2
[ 0.167817] CPU2: Booted secondary processor 0x0000000002 [0x411fd071]
[ 0.168741] Detected PIPT I-cache on CPU3
[ 0.168861] CPU3: Booted secondary processor 0x0000000003 [0x411fd071]
[ 0.168980] smp: Brought up 1 node, 4 CPUs
[ 0.205882] SMP: Total of 4 processors activated.
[ 0.210738] CPU features: detected: 32-bit EL0 Support
[ 0.216061] CPU features: detected: 32-bit EL1 Support
[ 0.221370] CPU features: detected: CRC32 instructions
[ 0.226816] CPU features: emulated: Privileged Access Never (PAN) using TTBR0_EL1 switching
[ 0.235450] CPU: All CPU(s) started at EL2
[ 0.239721] alternatives: applying system-wide alternatives
[ 0.251737] devtmpfs: initialized
[ 0.294478] Registered cp15_barrier emulation handler
[ 0.299740] Registered setend emulation handler
[ 0.304762] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.314967] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.324669] pinctrl core: initialized pinctrl subsystem
[ 0.331375] SMBIOS 3.0 present.
[ 0.334635] DMI: Unknown Unknown Product/Unknown Product, BIOS 2022.04 04/01/2022
[ 0.343286] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.350808] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations
[ 0.358403] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.366657] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.374990] audit: initializing netlink subsys (disabled)
[ 0.380915] audit: type=2000 audit(0.290:1): state=initialized audit_enabled=0 res=1
[ 0.384079] thermal_sys: Registered thermal governor 'fair_share'
[ 0.388975] thermal_sys: Registered thermal governor 'step_wise'
[ 0.395279] thermal_sys: Registered thermal governor 'user_space'
[ 0.401589] cpuidle: using governor menu
[ 0.412234] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.419417] ASID allocator initialised with 32768 entries
[ 0.426035] Serial: AMBA PL011 UART driver
[ 0.446128] tegra210-pinctrl 700008d4.pinmux: there is not valid maps for state drive
[ 0.481462] tegra-mc 70019000.memory-controller: no memory timings for RAM code 0 registered
[ 0.509090] KASLR enabled
[ 0.522092] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.529124] HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page
[ 0.535984] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[ 0.543002] HugeTLB: 508 KiB vmemmap can be freed for a 32.0 MiB page
[ 0.549670] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.556689] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page
[ 0.563272] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[ 0.570289] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[ 0.578205] cryptd: max_cpu_qlen set to 1000
[ 0.583875] raid6: skipped pq benchmark and selected neonx8
[ 0.589685] raid6: using neon recovery algorithm
[ 0.595632] ACPI: Interpreter disabled.
[ 0.603308] iommu: Default domain type: Translated
[ 0.608357] iommu: DMA domain TLB invalidation policy: lazy mode
[ 0.615363] SCSI subsystem initialized
[ 0.619478] libata version 3.00 loaded.
[ 0.623697] usbcore: registered new interface driver usbfs
[ 0.629434] usbcore: registered new interface driver hub
[ 0.634955] usbcore: registered new device driver usb
[ 0.640650] pps_core: LinuxPPS API ver. 1 registered
[ 0.645784] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.655249] PTP clock support registered
[ 0.659539] EDAC MC: Ver: 3.0.0
[ 0.664242] Registered efivars operations
[ 0.669853] NetLabel: Initializing
[ 0.673374] NetLabel: domain hash size = 128
[ 0.677873] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.683811] NetLabel: unlabeled traffic allowed by default
[ 0.689582] mctp: management component transport protocol core
[ 0.695623] NET: Registered PF_MCTP protocol family
[ 0.701073] vgaarb: loaded
[ 0.704468] clocksource: Switched to clocksource arch_sys_counter
[ 0.823127] VFS: Disk quotas dquot_6.6.0
[ 0.827367] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.835017] pnp: PnP ACPI: disabled
[ 0.848393] NET: Registered PF_INET protocol family
[ 0.853889] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
[ 0.865308] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[ 0.874180] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.882314] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[ 0.890779] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes, linear)
[ 0.899367] TCP: Hash tables configured (established 32768 bind 32768)
[ 0.906664] MPTCP token hash table entries: 4096 (order: 4, 98304 bytes, linear)
[ 0.914563] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[ 0.921576] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
[ 0.929342] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.935288] NET: Registered PF_XDP protocol family
[ 0.940250] PCI: CLS 0 bytes, default 64
[ 0.944723] Trying to unpack rootfs image as initramfs...
[ 0.951701] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[ 0.961025] kvm [1]: Guests without required CPU erratum workarounds can deadlock system!
[ 0.961025] Only trusted guests should be used on this system.
[ 0.975538] kvm [1]: IPA Size Limit: 44 bits
[ 0.983862] kvm [1]: Hyp mode initialized successfully
[ 0.992472] Initialise system trusted keyrings
[ 0.997203] Key type blacklist registered
[ 1.001784] workingset: timestamp_bits=37 max_order=20 bucket_order=0
[ 1.019514] zbud: loaded
[ 1.027162] integrity: Platform Keyring initialized
[ 1.032268] integrity: Machine keyring initialized
[ 1.075202] NET: Registered PF_ALG protocol family
[ 1.080193] xor: measuring software checksum speed
[ 1.087180] 8regs : 4889 MB/sec
[ 1.093570] 32regs : 5211 MB/sec
[ 1.100678] arm64_neon : 3793 MB/sec
[ 1.105192] xor: using function: 32regs (5211 MB/sec)
[ 1.110425] Key type asymmetric registered
[ 1.114660] Asymmetric key parser 'x509' registered
[ 8.298270] Freeing initrd memory: 131308K
[ 8.329463] alg: self-tests for CTR-KDF (hmac(sha256)) passed
[ 8.335660] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[ 8.343538] io scheduler mq-deadline registered
[ 8.348245] io scheduler kyber registered
[ 8.352681] io scheduler bfq registered
[ 8.363489] atomic64_test: passed
[ 8.401688] tegra-apbdma 60020000.dma: Tegra20 APB DMA driver registered 32 channels
[ 8.417141] tegra-pmc 7000e400.pmc: i2c-thermtrip node not found, emergency thermal reset disabled.
[ 8.430604] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 8.448097] msm_serial: driver initialized
[ 8.462926] usbcore: registered new interface driver usbserial_generic
[ 8.469744] usbserial: USB Serial support registered for generic
[ 8.476215] mousedev: PS/2 mouse device common for all mice
[ 8.485840] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[ 8.498577] device-mapper: uevent: version 1.0.3
[ 8.503760] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
[ 8.515847] ledtrig-cpu: registered to indicate activity on CPUs
[ 8.524282] hid: raw HID events driver (C) Jiri Kosina
[ 8.529853] usbcore: registered new interface driver usbhid
[ 8.535628] usbhid: USB HID core driver
[ 8.546967] drop_monitor: Initializing network drop monitor service
[ 8.615329] Initializing XFRM netlink socket
[ 8.620692] NET: Registered PF_INET6 protocol family
[ 8.653474] Segment Routing with IPv6
[ 8.657316] RPL Segment Routing with IPv6
[ 8.661563] In-situ OAM (IOAM) with IPv6
[ 8.665780] mip6: Mobile IPv6
[ 8.668879] NET: Registered PF_PACKET protocol family
[ 8.676227] registered taskstats version 1
[ 8.681725] Loading compiled-in X.509 certificates
[ 8.718979] Loaded X.509 cert 'Build time autogenerated kernel key: 0f87d8bf07ebde2f3dffab5a01f044e6c3e615b7'
[ 8.730513] zswap: loaded using pool lzo/zbud
[ 8.735436] page_owner is disabled
[ 8.739238] Key type .fscrypt registered
[ 8.743297] Key type fscrypt-provisioning registered
[ 8.750791] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity=yes
[ 8.757870] Key type big_key registered
[ 8.762536] Key type encrypted registered
[ 8.766932] ima: secureboot mode disabled
[ 8.771087] ima: No TPM chip found, activating TPM-bypass!
[ 8.776779] Loading compiled-in module X.509 certificates
[ 8.784253] Loaded X.509 cert 'Build time autogenerated kernel key: 0f87d8bf07ebde2f3dffab5a01f044e6c3e615b7'
[ 8.794520] ima: Allocated hash algorithm: sha256
[ 8.799445] ima: No architecture policies found
[ 8.804213] evm: Initialising EVM extended attributes:
[ 8.809526] evm: security.selinux
[ 8.812948] evm: security.SMACK64 (disabled)
[ 8.817357] evm: security.SMACK64EXEC (disabled)
[ 8.822124] evm: security.SMACK64TRANSMUTE (disabled)
[ 8.827343] evm: security.SMACK64MMAP (disabled)
[ 8.832114] evm: security.apparmor (disabled)
[ 8.836613] evm: security.ima
[ 8.839672] evm: security.capability
[ 8.843363] evm: HMAC attrs: 0x1
[ 8.946174] alg: No test for 842 (842-scomp)
[ 8.950792] alg: No test for 842 (842-generic)
[ 9.391834] gpio-6 (system-suspend-gpio): hogged as output/high
[ 9.398001] gpio-151 (camera-control-output-low): hogged as output/low
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-13 13:19 ` [Nouveau] " Linux kernel regression tracking (Thorsten Leemhuis)
(?)
@ 2023-01-14 15:58 ` Diogo Ivo
-1 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-14 15:58 UTC (permalink / raw)
To: Linux regressions mailing list
Cc: Karol Herbst, nouveau, dri-devel, bskeggs, airlied
On Fri, Jan 13, 2023 at 02:19:06PM +0100, Linux kernel regression tracking (Thorsten Leemhuis) wrote:
> Diogo, for that it would be really helpful to known: is the issue still
> happening with latest mainline? Is it possible to revert 2541626cfb79
> easily? And if so: do things work afterwards again?
Hello,
Thank you for your attention to this! I have checked the latest mainline and
it still occurs. As for reverting, I think it is complicated to do,
since this commit is a part of a larger rework, but I'm afraid I don't know
enough about the code to give a proper answer.
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-14 15:58 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-14 15:58 UTC (permalink / raw)
To: Linux regressions mailing list
Cc: bskeggs, Karol Herbst, Lyude Paul, dri-devel, nouveau, airlied,
Daniel Vetter
On Fri, Jan 13, 2023 at 02:19:06PM +0100, Linux kernel regression tracking (Thorsten Leemhuis) wrote:
> Diogo, for that it would be really helpful to known: is the issue still
> happening with latest mainline? Is it possible to revert 2541626cfb79
> easily? And if so: do things work afterwards again?
Hello,
Thank you for your attention to this! I have checked the latest mainline and
it still occurs. As for reverting, I think it is complicated to do,
since this commit is a part of a larger rework, but I'm afraid I don't know
enough about the code to give a proper answer.
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-14 15:58 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-14 15:58 UTC (permalink / raw)
To: Linux regressions mailing list
Cc: nouveau, dri-devel, bskeggs, Daniel Vetter, airlied
On Fri, Jan 13, 2023 at 02:19:06PM +0100, Linux kernel regression tracking (Thorsten Leemhuis) wrote:
> Diogo, for that it would be really helpful to known: is the issue still
> happening with latest mainline? Is it possible to revert 2541626cfb79
> easily? And if so: do things work afterwards again?
Hello,
Thank you for your attention to this! I have checked the latest mainline and
it still occurs. As for reverting, I think it is complicated to do,
since this commit is a part of a larger rework, but I'm afraid I don't know
enough about the code to give a proper answer.
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-14 3:27 ` Karol Herbst
(?)
@ 2023-01-14 16:03 ` Diogo Ivo
-1 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-14 16:03 UTC (permalink / raw)
To: Karol Herbst
Cc: Linux regressions mailing list, nouveau, dri-devel, bskeggs, airlied
On Sat, Jan 14, 2023 at 04:27:38AM +0100, Karol Herbst wrote:
> I tried to look into it, but my jetson nano, just constantly behaves
> in very strange ways. I tried to compile and install a 6.1 kernel onto
> it, but any kernel just refuses to boot and I have no idea what's up
> with that device. The kernel starts to boot and it just stops in the
> middle. From what I can tell is that most of the tegra devices never
> worked reliably in the first place and there are a couple of random
> and strange bugs around. I've attached my dmesg, so if anybody has any
> clues why the kernel just stops doing anything, it would really help
> me.
Hello,
Thank you for looking into this! I have seen this type of hang in
mainline on this SoC, and it was due to a reset not being deasserted.
Would you mind getting a log with initcall_debug enabled to pinpoint
where the hang occurs? I would be happy to help if I can.
> But maybe it would be for the best to just pull tegra support out of
> nouveau, because in the current situation we really can't spare much
> time dealing with them and we are already busy enough just dealing
> with the desktop GPUs. And the firmware we got from Nvidia is so
> ancient and different from the desktop GPU ones, that without actually
> having all those boards available and properly tested, we can't be
> sure to not break them.
>
> And afaik there are almost no _actual_ users, just distribution folks
> wanting to claim "support" for those devices, but then ending up using
> Nvidia's out of tree Tegra driver in deployments anyway.
> If there are actual users using them for their daily life, I'd like to
> know, because I'm aware of none.
For what it's worth, I consider myself a user of nouveau. Granted, I'm
using it as a hobby project, but in its current state it is not far from
a usable desktop experience on the Pixel C.
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-14 16:03 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-14 16:03 UTC (permalink / raw)
To: Karol Herbst
Cc: Linux regressions mailing list, bskeggs, Lyude Paul, dri-devel,
nouveau, airlied, Daniel Vetter
On Sat, Jan 14, 2023 at 04:27:38AM +0100, Karol Herbst wrote:
> I tried to look into it, but my jetson nano, just constantly behaves
> in very strange ways. I tried to compile and install a 6.1 kernel onto
> it, but any kernel just refuses to boot and I have no idea what's up
> with that device. The kernel starts to boot and it just stops in the
> middle. From what I can tell is that most of the tegra devices never
> worked reliably in the first place and there are a couple of random
> and strange bugs around. I've attached my dmesg, so if anybody has any
> clues why the kernel just stops doing anything, it would really help
> me.
Hello,
Thank you for looking into this! I have seen this type of hang in
mainline on this SoC, and it was due to a reset not being deasserted.
Would you mind getting a log with initcall_debug enabled to pinpoint
where the hang occurs? I would be happy to help if I can.
> But maybe it would be for the best to just pull tegra support out of
> nouveau, because in the current situation we really can't spare much
> time dealing with them and we are already busy enough just dealing
> with the desktop GPUs. And the firmware we got from Nvidia is so
> ancient and different from the desktop GPU ones, that without actually
> having all those boards available and properly tested, we can't be
> sure to not break them.
>
> And afaik there are almost no _actual_ users, just distribution folks
> wanting to claim "support" for those devices, but then ending up using
> Nvidia's out of tree Tegra driver in deployments anyway.
> If there are actual users using them for their daily life, I'd like to
> know, because I'm aware of none.
For what it's worth, I consider myself a user of nouveau. Granted, I'm
using it as a hobby project, but in its current state it is not far from
a usable desktop experience on the Pixel C.
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-14 16:03 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-14 16:03 UTC (permalink / raw)
To: Karol Herbst
Cc: Linux regressions mailing list, nouveau, dri-devel, bskeggs,
Daniel Vetter, airlied
On Sat, Jan 14, 2023 at 04:27:38AM +0100, Karol Herbst wrote:
> I tried to look into it, but my jetson nano, just constantly behaves
> in very strange ways. I tried to compile and install a 6.1 kernel onto
> it, but any kernel just refuses to boot and I have no idea what's up
> with that device. The kernel starts to boot and it just stops in the
> middle. From what I can tell is that most of the tegra devices never
> worked reliably in the first place and there are a couple of random
> and strange bugs around. I've attached my dmesg, so if anybody has any
> clues why the kernel just stops doing anything, it would really help
> me.
Hello,
Thank you for looking into this! I have seen this type of hang in
mainline on this SoC, and it was due to a reset not being deasserted.
Would you mind getting a log with initcall_debug enabled to pinpoint
where the hang occurs? I would be happy to help if I can.
> But maybe it would be for the best to just pull tegra support out of
> nouveau, because in the current situation we really can't spare much
> time dealing with them and we are already busy enough just dealing
> with the desktop GPUs. And the firmware we got from Nvidia is so
> ancient and different from the desktop GPU ones, that without actually
> having all those boards available and properly tested, we can't be
> sure to not break them.
>
> And afaik there are almost no _actual_ users, just distribution folks
> wanting to claim "support" for those devices, but then ending up using
> Nvidia's out of tree Tegra driver in deployments anyway.
> If there are actual users using them for their daily life, I'd like to
> know, because I'm aware of none.
For what it's worth, I consider myself a user of nouveau. Granted, I'm
using it as a hobby project, but in its current state it is not far from
a usable desktop experience on the Pixel C.
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-14 16:03 ` Diogo Ivo
(?)
@ 2023-01-14 18:56 ` Karol Herbst
-1 siblings, 0 replies; 60+ messages in thread
From: Karol Herbst @ 2023-01-14 18:56 UTC (permalink / raw)
To: Diogo Ivo
Cc: Linux regressions mailing list, bskeggs, Lyude Paul, dri-devel,
nouveau, airlied, Daniel Vetter
On Sat, Jan 14, 2023 at 5:07 PM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Sat, Jan 14, 2023 at 04:27:38AM +0100, Karol Herbst wrote:
> > I tried to look into it, but my jetson nano, just constantly behaves
> > in very strange ways. I tried to compile and install a 6.1 kernel onto
> > it, but any kernel just refuses to boot and I have no idea what's up
> > with that device. The kernel starts to boot and it just stops in the
> > middle. From what I can tell is that most of the tegra devices never
> > worked reliably in the first place and there are a couple of random
> > and strange bugs around. I've attached my dmesg, so if anybody has any
> > clues why the kernel just stops doing anything, it would really help
> > me.
>
> Hello,
>
> Thank you for looking into this! I have seen this type of hang in
> mainline on this SoC, and it was due to a reset not being deasserted.
> Would you mind getting a log with initcall_debug enabled to pinpoint
> where the hang occurs? I would be happy to help if I can.
>
the last thing printed is:
[ 20.517642] calling clk_disable_unused+0x0/0xe0 @ 1
> > But maybe it would be for the best to just pull tegra support out of
> > nouveau, because in the current situation we really can't spare much
> > time dealing with them and we are already busy enough just dealing
> > with the desktop GPUs. And the firmware we got from Nvidia is so
> > ancient and different from the desktop GPU ones, that without actually
> > having all those boards available and properly tested, we can't be
> > sure to not break them.
> >
> > And afaik there are almost no _actual_ users, just distribution folks
> > wanting to claim "support" for those devices, but then ending up using
> > Nvidia's out of tree Tegra driver in deployments anyway.
>
> > If there are actual users using them for their daily life, I'd like to
> > know, because I'm aware of none.
>
> For what it's worth, I consider myself a user of nouveau. Granted, I'm
> using it as a hobby project, but in its current state it is not far from
> a usable desktop experience on the Pixel C.
>
okay. I mean, I'm happy to keep fixing regressions and figuring out
what's wrong with booting the devices and such if regular users come
around and file bugs. And until today I wasn't really aware of anybody
:)
It's just not worth my time, if there are no users using them at all.
Or rather.. if there would only be commercial users (like.. companies
deploying those for money), then they could get involved and help us
out, because I wouldn't be willing to spend my time on this, if that
would be the case.
> Diogo
>
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-14 18:56 ` Karol Herbst
0 siblings, 0 replies; 60+ messages in thread
From: Karol Herbst @ 2023-01-14 18:56 UTC (permalink / raw)
To: Diogo Ivo
Cc: Linux regressions mailing list, nouveau, dri-devel, bskeggs,
Daniel Vetter, airlied
On Sat, Jan 14, 2023 at 5:07 PM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Sat, Jan 14, 2023 at 04:27:38AM +0100, Karol Herbst wrote:
> > I tried to look into it, but my jetson nano, just constantly behaves
> > in very strange ways. I tried to compile and install a 6.1 kernel onto
> > it, but any kernel just refuses to boot and I have no idea what's up
> > with that device. The kernel starts to boot and it just stops in the
> > middle. From what I can tell is that most of the tegra devices never
> > worked reliably in the first place and there are a couple of random
> > and strange bugs around. I've attached my dmesg, so if anybody has any
> > clues why the kernel just stops doing anything, it would really help
> > me.
>
> Hello,
>
> Thank you for looking into this! I have seen this type of hang in
> mainline on this SoC, and it was due to a reset not being deasserted.
> Would you mind getting a log with initcall_debug enabled to pinpoint
> where the hang occurs? I would be happy to help if I can.
>
the last thing printed is:
[ 20.517642] calling clk_disable_unused+0x0/0xe0 @ 1
> > But maybe it would be for the best to just pull tegra support out of
> > nouveau, because in the current situation we really can't spare much
> > time dealing with them and we are already busy enough just dealing
> > with the desktop GPUs. And the firmware we got from Nvidia is so
> > ancient and different from the desktop GPU ones, that without actually
> > having all those boards available and properly tested, we can't be
> > sure to not break them.
> >
> > And afaik there are almost no _actual_ users, just distribution folks
> > wanting to claim "support" for those devices, but then ending up using
> > Nvidia's out of tree Tegra driver in deployments anyway.
>
> > If there are actual users using them for their daily life, I'd like to
> > know, because I'm aware of none.
>
> For what it's worth, I consider myself a user of nouveau. Granted, I'm
> using it as a hobby project, but in its current state it is not far from
> a usable desktop experience on the Pixel C.
>
okay. I mean, I'm happy to keep fixing regressions and figuring out
what's wrong with booting the devices and such if regular users come
around and file bugs. And until today I wasn't really aware of anybody
:)
It's just not worth my time, if there are no users using them at all.
Or rather.. if there would only be commercial users (like.. companies
deploying those for money), then they could get involved and help us
out, because I wouldn't be willing to spend my time on this, if that
would be the case.
> Diogo
>
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-14 18:56 ` Karol Herbst
0 siblings, 0 replies; 60+ messages in thread
From: Karol Herbst @ 2023-01-14 18:56 UTC (permalink / raw)
To: Diogo Ivo
Cc: Linux regressions mailing list, nouveau, dri-devel, bskeggs, airlied
On Sat, Jan 14, 2023 at 5:07 PM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Sat, Jan 14, 2023 at 04:27:38AM +0100, Karol Herbst wrote:
> > I tried to look into it, but my jetson nano, just constantly behaves
> > in very strange ways. I tried to compile and install a 6.1 kernel onto
> > it, but any kernel just refuses to boot and I have no idea what's up
> > with that device. The kernel starts to boot and it just stops in the
> > middle. From what I can tell is that most of the tegra devices never
> > worked reliably in the first place and there are a couple of random
> > and strange bugs around. I've attached my dmesg, so if anybody has any
> > clues why the kernel just stops doing anything, it would really help
> > me.
>
> Hello,
>
> Thank you for looking into this! I have seen this type of hang in
> mainline on this SoC, and it was due to a reset not being deasserted.
> Would you mind getting a log with initcall_debug enabled to pinpoint
> where the hang occurs? I would be happy to help if I can.
>
the last thing printed is:
[ 20.517642] calling clk_disable_unused+0x0/0xe0 @ 1
> > But maybe it would be for the best to just pull tegra support out of
> > nouveau, because in the current situation we really can't spare much
> > time dealing with them and we are already busy enough just dealing
> > with the desktop GPUs. And the firmware we got from Nvidia is so
> > ancient and different from the desktop GPU ones, that without actually
> > having all those boards available and properly tested, we can't be
> > sure to not break them.
> >
> > And afaik there are almost no _actual_ users, just distribution folks
> > wanting to claim "support" for those devices, but then ending up using
> > Nvidia's out of tree Tegra driver in deployments anyway.
>
> > If there are actual users using them for their daily life, I'd like to
> > know, because I'm aware of none.
>
> For what it's worth, I consider myself a user of nouveau. Granted, I'm
> using it as a hobby project, but in its current state it is not far from
> a usable desktop experience on the Pixel C.
>
okay. I mean, I'm happy to keep fixing regressions and figuring out
what's wrong with booting the devices and such if regular users come
around and file bugs. And until today I wasn't really aware of anybody
:)
It's just not worth my time, if there are no users using them at all.
Or rather.. if there would only be commercial users (like.. companies
deploying those for money), then they could get involved and help us
out, because I wouldn't be willing to spend my time on this, if that
would be the case.
> Diogo
>
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2022-12-28 14:49 ` Diogo Ivo
(?)
@ 2023-01-15 21:45 ` David Airlie
-1 siblings, 0 replies; 60+ messages in thread
From: David Airlie @ 2023-01-15 21:45 UTC (permalink / raw)
To: Diogo Ivo; +Cc: regressions, bskeggs, dri-devel, nouveau
On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> Hello,
>
> Commit 2541626cfb79 breaks GM20B probe with
> the following kernel log:
>
> [ 2.153892] ------------[ cut here ]------------
> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> [ 2.153916] Modules linked in:
> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> [ 2.153929] Hardware name: Google Pixel C (DT)
> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
> [ 2.153966] sp : ffffffc009e134b0
> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> [ 2.154050] Call trace:
> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
> [ 2.154076] nvkm_vmm_map+0x50/0x84
> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
> [ 2.154119] nvkm_subdev_init+0x60/0xa0
> [ 2.154125] nvkm_device_init+0x14c/0x2a0
> [ 2.154133] nvkm_udevice_init+0x60/0x9c
> [ 2.154140] nvkm_object_init+0x48/0x1b0
> [ 2.154144] nvkm_ioctl_new+0x168/0x254
> [ 2.154149] nvkm_ioctl+0xd0/0x220
> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
> [ 2.154162] nvif_object_ctor+0xf4/0x22c
> [ 2.154168] nvif_device_ctor+0x28/0x70
> [ 2.154174] nouveau_cli_init+0x150/0x590
> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
> [ 2.154200] platform_probe+0x68/0xc0
> [ 2.154207] really_probe+0xbc/0x2dc
> [ 2.154211] __driver_probe_device+0x78/0xe0
> [ 2.154216] driver_probe_device+0xd8/0x160
> [ 2.154221] __device_attach_driver+0xb8/0x134
> [ 2.154226] bus_for_each_drv+0x78/0xd0
> [ 2.154230] __device_attach+0x9c/0x1a0
> [ 2.154234] device_initial_probe+0x14/0x20
> [ 2.154239] bus_probe_device+0x98/0xa0
> [ 2.154243] deferred_probe_work_func+0x88/0xc0
> [ 2.154247] process_one_work+0x204/0x40c
> [ 2.154256] worker_thread+0x230/0x450
> [ 2.154261] kthread+0xc8/0xcc
> [ 2.154266] ret_from_fork+0x10/0x20
> [ 2.154273] ---[ end trace 0000000000000000 ]---
> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> [ 2.154559] nouveau 57000000.gpu: init failed with -22
> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
>
> #regzbot introduced: 2541626cfb79
As a quick check can you try changing
drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
Dave.
>
> Thanks,
>
> Diogo Ivo
>
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-15 21:45 ` David Airlie
0 siblings, 0 replies; 60+ messages in thread
From: David Airlie @ 2023-01-15 21:45 UTC (permalink / raw)
To: Diogo Ivo; +Cc: nouveau, regressions, dri-devel, bskeggs
On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> Hello,
>
> Commit 2541626cfb79 breaks GM20B probe with
> the following kernel log:
>
> [ 2.153892] ------------[ cut here ]------------
> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> [ 2.153916] Modules linked in:
> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> [ 2.153929] Hardware name: Google Pixel C (DT)
> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
> [ 2.153966] sp : ffffffc009e134b0
> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> [ 2.154050] Call trace:
> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
> [ 2.154076] nvkm_vmm_map+0x50/0x84
> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
> [ 2.154119] nvkm_subdev_init+0x60/0xa0
> [ 2.154125] nvkm_device_init+0x14c/0x2a0
> [ 2.154133] nvkm_udevice_init+0x60/0x9c
> [ 2.154140] nvkm_object_init+0x48/0x1b0
> [ 2.154144] nvkm_ioctl_new+0x168/0x254
> [ 2.154149] nvkm_ioctl+0xd0/0x220
> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
> [ 2.154162] nvif_object_ctor+0xf4/0x22c
> [ 2.154168] nvif_device_ctor+0x28/0x70
> [ 2.154174] nouveau_cli_init+0x150/0x590
> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
> [ 2.154200] platform_probe+0x68/0xc0
> [ 2.154207] really_probe+0xbc/0x2dc
> [ 2.154211] __driver_probe_device+0x78/0xe0
> [ 2.154216] driver_probe_device+0xd8/0x160
> [ 2.154221] __device_attach_driver+0xb8/0x134
> [ 2.154226] bus_for_each_drv+0x78/0xd0
> [ 2.154230] __device_attach+0x9c/0x1a0
> [ 2.154234] device_initial_probe+0x14/0x20
> [ 2.154239] bus_probe_device+0x98/0xa0
> [ 2.154243] deferred_probe_work_func+0x88/0xc0
> [ 2.154247] process_one_work+0x204/0x40c
> [ 2.154256] worker_thread+0x230/0x450
> [ 2.154261] kthread+0xc8/0xcc
> [ 2.154266] ret_from_fork+0x10/0x20
> [ 2.154273] ---[ end trace 0000000000000000 ]---
> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> [ 2.154559] nouveau 57000000.gpu: init failed with -22
> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
>
> #regzbot introduced: 2541626cfb79
As a quick check can you try changing
drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
Dave.
>
> Thanks,
>
> Diogo Ivo
>
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-15 21:45 ` David Airlie
0 siblings, 0 replies; 60+ messages in thread
From: David Airlie @ 2023-01-15 21:45 UTC (permalink / raw)
To: Diogo Ivo; +Cc: nouveau, regressions, dri-devel, bskeggs
On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> Hello,
>
> Commit 2541626cfb79 breaks GM20B probe with
> the following kernel log:
>
> [ 2.153892] ------------[ cut here ]------------
> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> [ 2.153916] Modules linked in:
> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> [ 2.153929] Hardware name: Google Pixel C (DT)
> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
> [ 2.153966] sp : ffffffc009e134b0
> [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> [ 2.154050] Call trace:
> [ 2.154053] gf100_vmm_valid+0x2c4/0x390
> [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
> [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
> [ 2.154076] nvkm_vmm_map+0x50/0x84
> [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
> [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
> [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
> [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
> [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
> [ 2.154119] nvkm_subdev_init+0x60/0xa0
> [ 2.154125] nvkm_device_init+0x14c/0x2a0
> [ 2.154133] nvkm_udevice_init+0x60/0x9c
> [ 2.154140] nvkm_object_init+0x48/0x1b0
> [ 2.154144] nvkm_ioctl_new+0x168/0x254
> [ 2.154149] nvkm_ioctl+0xd0/0x220
> [ 2.154153] nvkm_client_ioctl+0x10/0x1c
> [ 2.154162] nvif_object_ctor+0xf4/0x22c
> [ 2.154168] nvif_device_ctor+0x28/0x70
> [ 2.154174] nouveau_cli_init+0x150/0x590
> [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
> [ 2.154187] nouveau_platform_device_create+0x90/0xd0
> [ 2.154193] nouveau_platform_probe+0x3c/0x9c
> [ 2.154200] platform_probe+0x68/0xc0
> [ 2.154207] really_probe+0xbc/0x2dc
> [ 2.154211] __driver_probe_device+0x78/0xe0
> [ 2.154216] driver_probe_device+0xd8/0x160
> [ 2.154221] __device_attach_driver+0xb8/0x134
> [ 2.154226] bus_for_each_drv+0x78/0xd0
> [ 2.154230] __device_attach+0x9c/0x1a0
> [ 2.154234] device_initial_probe+0x14/0x20
> [ 2.154239] bus_probe_device+0x98/0xa0
> [ 2.154243] deferred_probe_work_func+0x88/0xc0
> [ 2.154247] process_one_work+0x204/0x40c
> [ 2.154256] worker_thread+0x230/0x450
> [ 2.154261] kthread+0xc8/0xcc
> [ 2.154266] ret_from_fork+0x10/0x20
> [ 2.154273] ---[ end trace 0000000000000000 ]---
> [ 2.154278] nouveau 57000000.gpu: pmu: map -22
> [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> [ 2.154559] nouveau 57000000.gpu: init failed with -22
> [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
>
> #regzbot introduced: 2541626cfb79
As a quick check can you try changing
drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
Dave.
>
> Thanks,
>
> Diogo Ivo
>
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-15 21:45 ` [Nouveau] " David Airlie
(?)
@ 2023-01-16 12:24 ` Diogo Ivo
-1 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-16 12:24 UTC (permalink / raw)
To: David Airlie; +Cc: regressions, bskeggs, dri-devel, nouveau
On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> As a quick check can you try changing
>
> drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
Hello!
Applying this change breaks probing in a different way, with a
bad PC=0x0. From a quick look at nvkm_falcon_load_dmem it looks like this
could happen due to the .load_dmem() callback not being properly
initialized. This is the kernel log I got:
[ 2.010601] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[ 2.019436] Mem abort info:
[ 2.022273] ESR = 0x0000000086000005
[ 2.026066] EC = 0x21: IABT (current EL), IL = 32 bits
[ 2.031429] SET = 0, FnV = 0
[ 2.034528] EA = 0, S1PTW = 0
[ 2.037694] FSC = 0x05: level 1 translation fault
[ 2.042572] [0000000000000000] user address but active_mm is swapper
[ 2.048961] Internal error: Oops: 0000000086000005 [#1] SMP
[ 2.054529] Modules linked in:
[ 2.057582] CPU: 0 PID: 36 Comm: kworker/u8:1 Not tainted 6.2.0-rc3+ #2
[ 2.064190] Hardware name: Google Pixel C (DT)
[ 2.068628] Workqueue: events_unbound deferred_probe_work_func
[ 2.074463] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2.081417] pc : 0x0
[ 2.083600] lr : nvkm_falcon_load_dmem+0x58/0x80
[ 2.088218] sp : ffffffc009ddb6f0
[ 2.091526] x29: ffffffc009ddb6f0 x28: ffffff808028a008 x27: ffffff8081e43c38
[ 2.098658] x26: 00000000000000ff x25: ffffff808028a0a0 x24: 0000000000000000
[ 2.105788] x23: ffffff8080c328f8 x22: 000000000000002c x21: 0000000000005fd4
[ 2.112917] x20: ffffffc009ddb76c x19: ffffff8080c328b8 x18: 0000000000000000
[ 2.120047] x17: 2e74696e695f646f x16: 6874656d5f77732f x15: 0000000000000000
[ 2.127176] x14: 0000000002f546c2 x13: 0000000000000000 x12: 00000000000001ce
[ 2.134306] x11: 0000000000000001 x10: 0000000000000a90 x9 : ffffffc009ddb600
[ 2.141436] x8 : ffffff80803d19f0 x7 : ffffff80bf971180 x6 : 00000000000001b9
[ 2.148565] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 000000000000002c
[ 2.155693] x2 : 0000000000005fd4 x1 : ffffffc009ddb76c x0 : ffffff8080c328b8
[ 2.162822] Call trace:
[ 2.165264] 0x0
[ 2.167099] gm20b_pmu_init+0x78/0xb4
[ 2.170762] nvkm_pmu_init+0x20/0x34
[ 2.174334] nvkm_subdev_init_+0x60/0x12c
[ 2.178339] nvkm_subdev_init+0x60/0xa0
[ 2.182171] nvkm_device_init+0x14c/0x2a0
[ 2.186178] nvkm_udevice_init+0x60/0x9c
[ 2.190097] nvkm_object_init+0x48/0x1b0
[ 2.194013] nvkm_ioctl_new+0x168/0x254
[ 2.197843] nvkm_ioctl+0xd0/0x220
[ 2.201239] nvkm_client_ioctl+0x10/0x1c
[ 2.205160] nvif_object_ctor+0xf4/0x22c
[ 2.209079] nvif_device_ctor+0x28/0x70
[ 2.212910] nouveau_cli_init+0x150/0x590
[ 2.216916] nouveau_drm_device_init+0x60/0x2a0
[ 2.221442] nouveau_platform_device_create+0x90/0xd0
[ 2.226489] nouveau_platform_probe+0x3c/0x9c
[ 2.230841] platform_probe+0x68/0xc0
[ 2.234500] really_probe+0xbc/0x2dc
[ 2.238070] __driver_probe_device+0x78/0xe0
[ 2.242334] driver_probe_device+0xd8/0x160
[ 2.246511] __device_attach_driver+0xb8/0x134
[ 2.250948] bus_for_each_drv+0x78/0xd0
[ 2.254782] __device_attach+0x9c/0x1a0
[ 2.258612] device_initial_probe+0x14/0x20
[ 2.262789] bus_probe_device+0x98/0xa0
[ 2.266619] deferred_probe_work_func+0x88/0xc0
[ 2.271142] process_one_work+0x204/0x40c
[ 2.275150] worker_thread+0x230/0x450
[ 2.278894] kthread+0xc8/0xcc
[ 2.281946] ret_from_fork+0x10/0x20
[ 2.285525] Code: bad PC value
[ 2.288576] ---[ end trace 0000000000000000 ]---
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-16 12:24 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-16 12:24 UTC (permalink / raw)
To: David Airlie; +Cc: nouveau, regressions, dri-devel, bskeggs
On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> As a quick check can you try changing
>
> drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
Hello!
Applying this change breaks probing in a different way, with a
bad PC=0x0. From a quick look at nvkm_falcon_load_dmem it looks like this
could happen due to the .load_dmem() callback not being properly
initialized. This is the kernel log I got:
[ 2.010601] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[ 2.019436] Mem abort info:
[ 2.022273] ESR = 0x0000000086000005
[ 2.026066] EC = 0x21: IABT (current EL), IL = 32 bits
[ 2.031429] SET = 0, FnV = 0
[ 2.034528] EA = 0, S1PTW = 0
[ 2.037694] FSC = 0x05: level 1 translation fault
[ 2.042572] [0000000000000000] user address but active_mm is swapper
[ 2.048961] Internal error: Oops: 0000000086000005 [#1] SMP
[ 2.054529] Modules linked in:
[ 2.057582] CPU: 0 PID: 36 Comm: kworker/u8:1 Not tainted 6.2.0-rc3+ #2
[ 2.064190] Hardware name: Google Pixel C (DT)
[ 2.068628] Workqueue: events_unbound deferred_probe_work_func
[ 2.074463] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2.081417] pc : 0x0
[ 2.083600] lr : nvkm_falcon_load_dmem+0x58/0x80
[ 2.088218] sp : ffffffc009ddb6f0
[ 2.091526] x29: ffffffc009ddb6f0 x28: ffffff808028a008 x27: ffffff8081e43c38
[ 2.098658] x26: 00000000000000ff x25: ffffff808028a0a0 x24: 0000000000000000
[ 2.105788] x23: ffffff8080c328f8 x22: 000000000000002c x21: 0000000000005fd4
[ 2.112917] x20: ffffffc009ddb76c x19: ffffff8080c328b8 x18: 0000000000000000
[ 2.120047] x17: 2e74696e695f646f x16: 6874656d5f77732f x15: 0000000000000000
[ 2.127176] x14: 0000000002f546c2 x13: 0000000000000000 x12: 00000000000001ce
[ 2.134306] x11: 0000000000000001 x10: 0000000000000a90 x9 : ffffffc009ddb600
[ 2.141436] x8 : ffffff80803d19f0 x7 : ffffff80bf971180 x6 : 00000000000001b9
[ 2.148565] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 000000000000002c
[ 2.155693] x2 : 0000000000005fd4 x1 : ffffffc009ddb76c x0 : ffffff8080c328b8
[ 2.162822] Call trace:
[ 2.165264] 0x0
[ 2.167099] gm20b_pmu_init+0x78/0xb4
[ 2.170762] nvkm_pmu_init+0x20/0x34
[ 2.174334] nvkm_subdev_init_+0x60/0x12c
[ 2.178339] nvkm_subdev_init+0x60/0xa0
[ 2.182171] nvkm_device_init+0x14c/0x2a0
[ 2.186178] nvkm_udevice_init+0x60/0x9c
[ 2.190097] nvkm_object_init+0x48/0x1b0
[ 2.194013] nvkm_ioctl_new+0x168/0x254
[ 2.197843] nvkm_ioctl+0xd0/0x220
[ 2.201239] nvkm_client_ioctl+0x10/0x1c
[ 2.205160] nvif_object_ctor+0xf4/0x22c
[ 2.209079] nvif_device_ctor+0x28/0x70
[ 2.212910] nouveau_cli_init+0x150/0x590
[ 2.216916] nouveau_drm_device_init+0x60/0x2a0
[ 2.221442] nouveau_platform_device_create+0x90/0xd0
[ 2.226489] nouveau_platform_probe+0x3c/0x9c
[ 2.230841] platform_probe+0x68/0xc0
[ 2.234500] really_probe+0xbc/0x2dc
[ 2.238070] __driver_probe_device+0x78/0xe0
[ 2.242334] driver_probe_device+0xd8/0x160
[ 2.246511] __device_attach_driver+0xb8/0x134
[ 2.250948] bus_for_each_drv+0x78/0xd0
[ 2.254782] __device_attach+0x9c/0x1a0
[ 2.258612] device_initial_probe+0x14/0x20
[ 2.262789] bus_probe_device+0x98/0xa0
[ 2.266619] deferred_probe_work_func+0x88/0xc0
[ 2.271142] process_one_work+0x204/0x40c
[ 2.275150] worker_thread+0x230/0x450
[ 2.278894] kthread+0xc8/0xcc
[ 2.281946] ret_from_fork+0x10/0x20
[ 2.285525] Code: bad PC value
[ 2.288576] ---[ end trace 0000000000000000 ]---
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-16 12:24 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-16 12:24 UTC (permalink / raw)
To: David Airlie; +Cc: nouveau, regressions, dri-devel, bskeggs
On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> As a quick check can you try changing
>
> drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
Hello!
Applying this change breaks probing in a different way, with a
bad PC=0x0. From a quick look at nvkm_falcon_load_dmem it looks like this
could happen due to the .load_dmem() callback not being properly
initialized. This is the kernel log I got:
[ 2.010601] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[ 2.019436] Mem abort info:
[ 2.022273] ESR = 0x0000000086000005
[ 2.026066] EC = 0x21: IABT (current EL), IL = 32 bits
[ 2.031429] SET = 0, FnV = 0
[ 2.034528] EA = 0, S1PTW = 0
[ 2.037694] FSC = 0x05: level 1 translation fault
[ 2.042572] [0000000000000000] user address but active_mm is swapper
[ 2.048961] Internal error: Oops: 0000000086000005 [#1] SMP
[ 2.054529] Modules linked in:
[ 2.057582] CPU: 0 PID: 36 Comm: kworker/u8:1 Not tainted 6.2.0-rc3+ #2
[ 2.064190] Hardware name: Google Pixel C (DT)
[ 2.068628] Workqueue: events_unbound deferred_probe_work_func
[ 2.074463] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2.081417] pc : 0x0
[ 2.083600] lr : nvkm_falcon_load_dmem+0x58/0x80
[ 2.088218] sp : ffffffc009ddb6f0
[ 2.091526] x29: ffffffc009ddb6f0 x28: ffffff808028a008 x27: ffffff8081e43c38
[ 2.098658] x26: 00000000000000ff x25: ffffff808028a0a0 x24: 0000000000000000
[ 2.105788] x23: ffffff8080c328f8 x22: 000000000000002c x21: 0000000000005fd4
[ 2.112917] x20: ffffffc009ddb76c x19: ffffff8080c328b8 x18: 0000000000000000
[ 2.120047] x17: 2e74696e695f646f x16: 6874656d5f77732f x15: 0000000000000000
[ 2.127176] x14: 0000000002f546c2 x13: 0000000000000000 x12: 00000000000001ce
[ 2.134306] x11: 0000000000000001 x10: 0000000000000a90 x9 : ffffffc009ddb600
[ 2.141436] x8 : ffffff80803d19f0 x7 : ffffff80bf971180 x6 : 00000000000001b9
[ 2.148565] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 000000000000002c
[ 2.155693] x2 : 0000000000005fd4 x1 : ffffffc009ddb76c x0 : ffffff8080c328b8
[ 2.162822] Call trace:
[ 2.165264] 0x0
[ 2.167099] gm20b_pmu_init+0x78/0xb4
[ 2.170762] nvkm_pmu_init+0x20/0x34
[ 2.174334] nvkm_subdev_init_+0x60/0x12c
[ 2.178339] nvkm_subdev_init+0x60/0xa0
[ 2.182171] nvkm_device_init+0x14c/0x2a0
[ 2.186178] nvkm_udevice_init+0x60/0x9c
[ 2.190097] nvkm_object_init+0x48/0x1b0
[ 2.194013] nvkm_ioctl_new+0x168/0x254
[ 2.197843] nvkm_ioctl+0xd0/0x220
[ 2.201239] nvkm_client_ioctl+0x10/0x1c
[ 2.205160] nvif_object_ctor+0xf4/0x22c
[ 2.209079] nvif_device_ctor+0x28/0x70
[ 2.212910] nouveau_cli_init+0x150/0x590
[ 2.216916] nouveau_drm_device_init+0x60/0x2a0
[ 2.221442] nouveau_platform_device_create+0x90/0xd0
[ 2.226489] nouveau_platform_probe+0x3c/0x9c
[ 2.230841] platform_probe+0x68/0xc0
[ 2.234500] really_probe+0xbc/0x2dc
[ 2.238070] __driver_probe_device+0x78/0xe0
[ 2.242334] driver_probe_device+0xd8/0x160
[ 2.246511] __device_attach_driver+0xb8/0x134
[ 2.250948] bus_for_each_drv+0x78/0xd0
[ 2.254782] __device_attach+0x9c/0x1a0
[ 2.258612] device_initial_probe+0x14/0x20
[ 2.262789] bus_probe_device+0x98/0xa0
[ 2.266619] deferred_probe_work_func+0x88/0xc0
[ 2.271142] process_one_work+0x204/0x40c
[ 2.275150] worker_thread+0x230/0x450
[ 2.278894] kthread+0xc8/0xcc
[ 2.281946] ret_from_fork+0x10/0x20
[ 2.285525] Code: bad PC value
[ 2.288576] ---[ end trace 0000000000000000 ]---
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-15 21:45 ` [Nouveau] " David Airlie
@ 2023-01-17 15:55 ` Nicolas Chauvet
-1 siblings, 0 replies; 60+ messages in thread
From: Nicolas Chauvet @ 2023-01-17 15:55 UTC (permalink / raw)
To: David Airlie; +Cc: nouveau, Diogo Ivo, regressions, dri-devel, bskeggs
Le dim. 15 janv. 2023 à 22:45, David Airlie <airlied@redhat.com> a écrit :
>
> On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > Hello,
> >
> > Commit 2541626cfb79 breaks GM20B probe with
> > the following kernel log:
> >
> > [ 2.153892] ------------[ cut here ]------------
> > [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> > [ 2.153916] Modules linked in:
> > [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> > [ 2.153929] Hardware name: Google Pixel C (DT)
> > [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> > [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> > [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> > [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
> > [ 2.153966] sp : ffffffc009e134b0
> > [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> > [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> > [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> > [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> > [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> > [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> > [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> > [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> > [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> > [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> > [ 2.154050] Call trace:
> > [ 2.154053] gf100_vmm_valid+0x2c4/0x390
> > [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
> > [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
> > [ 2.154076] nvkm_vmm_map+0x50/0x84
> > [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
> > [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
> > [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
> > [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
> > [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
> > [ 2.154119] nvkm_subdev_init+0x60/0xa0
> > [ 2.154125] nvkm_device_init+0x14c/0x2a0
> > [ 2.154133] nvkm_udevice_init+0x60/0x9c
> > [ 2.154140] nvkm_object_init+0x48/0x1b0
> > [ 2.154144] nvkm_ioctl_new+0x168/0x254
> > [ 2.154149] nvkm_ioctl+0xd0/0x220
> > [ 2.154153] nvkm_client_ioctl+0x10/0x1c
> > [ 2.154162] nvif_object_ctor+0xf4/0x22c
> > [ 2.154168] nvif_device_ctor+0x28/0x70
> > [ 2.154174] nouveau_cli_init+0x150/0x590
> > [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
> > [ 2.154187] nouveau_platform_device_create+0x90/0xd0
> > [ 2.154193] nouveau_platform_probe+0x3c/0x9c
> > [ 2.154200] platform_probe+0x68/0xc0
> > [ 2.154207] really_probe+0xbc/0x2dc
> > [ 2.154211] __driver_probe_device+0x78/0xe0
> > [ 2.154216] driver_probe_device+0xd8/0x160
> > [ 2.154221] __device_attach_driver+0xb8/0x134
> > [ 2.154226] bus_for_each_drv+0x78/0xd0
> > [ 2.154230] __device_attach+0x9c/0x1a0
> > [ 2.154234] device_initial_probe+0x14/0x20
> > [ 2.154239] bus_probe_device+0x98/0xa0
> > [ 2.154243] deferred_probe_work_func+0x88/0xc0
> > [ 2.154247] process_one_work+0x204/0x40c
> > [ 2.154256] worker_thread+0x230/0x450
> > [ 2.154261] kthread+0xc8/0xcc
> > [ 2.154266] ret_from_fork+0x10/0x20
> > [ 2.154273] ---[ end trace 0000000000000000 ]---
> > [ 2.154278] nouveau 57000000.gpu: pmu: map -22
> > [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> > [ 2.154559] nouveau 57000000.gpu: init failed with -22
> > [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> > [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> > [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
> >
> > #regzbot introduced: 2541626cfb79
>
> As a quick check can you try changing
>
> drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
>
> Dave.
I'm also reproducing the error on jetson-tx1 running 6.2-rc4 (rawhide
nodebug kernel) on Fedora 37 userspace.
With this change, the error is different:
nouveau: loading out-of-tree module taints kernel.
nouveau: module verification failed: signature and/or required key
missing - tainting kernel
Failed to set up IOMMU for device 57000000.gpu; retaining platform DMA ops
nouveau 57000000.gpu: NVIDIA GM20B (12b000a1)
nouveau 57000000.gpu: imem: using IOMMU
Unable to handle kernel execution of user memory at virtual address
0000000000000000
Mem abort info:
ESR = 0x0000000086000004
EC = 0x21: IABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x04: level 0 translation fault
user pgtable: 4k pages, 48-bit VAs, pgdp=000000013e136000
[0000000000000000] pgd=0000000000000000, p4d=0000000000000000
Internal error: Oops: 0000000086000004 [#1] SMP
Modules linked in: nouveau(OE+) drm_ttm_helper ttm snd_seq_dummy
snd_hrtimer nf_conntrack_netbios_ns nf_conntrack_broadcast
nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet
nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 rfkill ip_set nf_tables
nfnetlink qrtr sunrpc snd_soc_tegra_audio_graph_card
snd_soc_audio_graph_card snd_soc_simple_card_utils snd_soc_core
snd_compress snd_hda_codec_hdmi ac97_bus snd_hda_tegra
snd_pcm_dmaengine snd_hda_codec max77620_thermal vfat snd_hda_core fat
snd_hwdep snd_seq cpufreq_dt tegra_xudc snd_seq_device usb_conn_gpio
tegra_soctherm snd_pcm udc_core snd_timer snd at24 soundcore zram
r8152 mii panel_simple mmc_block tegra_drm drm_dp_aux_bus rtc_max77686
drm_display_helper lp855x_bl cec crct10dif_ce polyval_ce
polyval_generic xhci_tegra sdhci_tegra ghash_ce sdhci_pltfm
phy_tegra_xusb sdhci host1x ahci_tegra gpio_keys tegra210_emc cqhci
rtc_tegra i2c_tegra ip6_tables
abrt-dump-journal-oops: Found oopses: 1
abrt-dump-journal-oops: Creating problem directories
Can't find a meaningful backtrace for hashing in '.'
Preserving oops '.' because DropNotReportableOopses is 'no'
Reported 1 kernel oopses to Abrt
System encountered a non-fatal error in ??()
ip_tables fuse
CPU: 3 PID: 15789 Comm: insmod Tainted: G OE -------
--- 6.2.0-0.rc4.31.fc38.aarch64 #1
Hardware name: nvidia,p2371-2180 NVIDIA P2371-2180/NVIDIA P2371-2180,
BIOS 2022.10 10/01/2022
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : 0x0
lr : nvkm_falcon_load_dmem+0x60/0x80 [nouveau]
sp : ffff8000141034c0
x29: ffff8000141034c0 x28: ffff0000865d2008 x27: ffff0000c87b8638
x26: 00000000000000ff x25: ffff0000865d20a0 x24: 0000000000000000
x23: ffff0000f4ef34f8 x22: 000000000000002c x21: 0000000000005fd4
x20: ffff800014103534 x19: ffff0000f4ef34b8 x18: ffffffffffffffff
x17: 000000040044ffff x16: 00500074b5503510 x15: ffff8000141035d8
x14: ffff0000c87b8506 x13: 0000000000000001 x12: 0000000000000018
x11: 0000000000000001 x10: fffffffffffffec0 x9 : ffff8000091efa90
x8 : ffff800014103560 x7 : 0000000000000000 x6 : 0000000434da8f65
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 000000000000002c
x2 : 0000000000005fd4 x1 : ffff800014103534 x0 : ffff0000f4ef34b8
Call trace:
0x0
gm20b_pmu_init+0x70/0x90 [nouveau]
nvkm_pmu_init+0x28/0x40 [nouveau]
nvkm_subdev_init_+0x68/0x134 [nouveau]
nvkm_subdev_init+0x68/0xb0 [nouveau]
nvkm_device_init+0x154/0x2ac [nouveau]
nvkm_udevice_init+0x68/0xa0 [nouveau]
nvkm_object_init+0x50/0x1b4 [nouveau]
nvkm_ioctl_new+0x154/0x280 [nouveau]
nvkm_ioctl+0xd8/0x230 [nouveau]
nvkm_client_ioctl+0x18/0x24 [nouveau]
nvif_object_ctor+0xec/0x1a0 [nouveau]
nvif_device_ctor+0x30/0x7c [nouveau]
nouveau_cli_init+0x144/0x574 [nouveau]
nouveau_drm_device_init+0x68/0x2b0 [nouveau]
nouveau_platform_device_create+0x98/0xd0 [nouveau]
nouveau_platform_probe+0x34/0x90 [nouveau]
platform_probe+0x70/0xd0
really_probe+0xc8/0x3e4
__driver_probe_device+0x84/0x190
driver_probe_device+0x44/0x11c
__driver_attach+0xf8/0x200
bus_for_each_dev+0x6c/0xac
driver_attach+0x2c/0x40
bus_add_driver+0x188/0x250
driver_register+0x80/0x13c
__platform_driver_register+0x30/0x3c
nouveau_drm_init+0x9c/0x1000 [nouveau]
do_one_initcall+0x4c/0x2a0
do_init_module+0x50/0x200
load_module+0x9b0/0xb10
__do_sys_finit_module+0x98/0x100
__arm64_sys_finit_module+0x28/0x34
invoke_syscall+0x78/0x100
el0_svc_common.constprop.0+0x4c/0xf4
do_el0_svc+0x34/0x4c
el0_svc+0x34/0x10c
el0t_64_sync_handler+0x114/0x120
el0t_64_sync+0x194/0x198
Code: bad PC value
---[ end trace 0000000000000000 ]---
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-17 15:55 ` Nicolas Chauvet
0 siblings, 0 replies; 60+ messages in thread
From: Nicolas Chauvet @ 2023-01-17 15:55 UTC (permalink / raw)
To: David Airlie; +Cc: Diogo Ivo, nouveau, regressions, dri-devel, bskeggs
Le dim. 15 janv. 2023 à 22:45, David Airlie <airlied@redhat.com> a écrit :
>
> On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > Hello,
> >
> > Commit 2541626cfb79 breaks GM20B probe with
> > the following kernel log:
> >
> > [ 2.153892] ------------[ cut here ]------------
> > [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> > [ 2.153916] Modules linked in:
> > [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> > [ 2.153929] Hardware name: Google Pixel C (DT)
> > [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> > [ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> > [ 2.153950] pc : gf100_vmm_valid+0x2c4/0x390
> > [ 2.153959] lr : gf100_vmm_valid+0xb4/0x390
> > [ 2.153966] sp : ffffffc009e134b0
> > [ 2.153969] x29: ffffffc009e134b0 x28: 0000000000000000 x27: ffffffc008fd44c8
> > [ 2.153979] x26: 00000000ffffffea x25: ffffffc0087b98d0 x24: ffffff8080f89038
> > [ 2.153987] x23: ffffff8081fadc08 x22: 0000000000000000 x21: 0000000000000000
> > [ 2.153995] x20: ffffff8080f8a000 x19: ffffffc009e13678 x18: 0000000000000000
> > [ 2.154003] x17: f37a8b93418958e6 x16: ffffffc009f0d000 x15: 0000000000000000
> > [ 2.154011] x14: 0000000000000002 x13: 000000000003a020 x12: ffffffc008000000
> > [ 2.154019] x11: 0000000102913000 x10: 0000000000000000 x9 : 0000000000000000
> > [ 2.154026] x8 : ffffffc009e136d8 x7 : ffffffc008fd44c8 x6 : ffffff80803d0f00
> > [ 2.154034] x5 : 0000000000000000 x4 : ffffff8080f88c00 x3 : 0000000000000010
> > [ 2.154041] x2 : 000000000000000c x1 : 00000000ffffffea x0 : 00000000ffffffea
> > [ 2.154050] Call trace:
> > [ 2.154053] gf100_vmm_valid+0x2c4/0x390
> > [ 2.154061] nvkm_vmm_map_valid+0xd4/0x204
> > [ 2.154069] nvkm_vmm_map_locked+0xa4/0x344
> > [ 2.154076] nvkm_vmm_map+0x50/0x84
> > [ 2.154083] nvkm_firmware_mem_map+0x84/0xc4
> > [ 2.154094] nvkm_falcon_fw_oneinit+0xc8/0x320
> > [ 2.154101] nvkm_acr_oneinit+0x428/0x5b0
> > [ 2.154109] nvkm_subdev_oneinit_+0x50/0x104
> > [ 2.154114] nvkm_subdev_init_+0x3c/0x12c
> > [ 2.154119] nvkm_subdev_init+0x60/0xa0
> > [ 2.154125] nvkm_device_init+0x14c/0x2a0
> > [ 2.154133] nvkm_udevice_init+0x60/0x9c
> > [ 2.154140] nvkm_object_init+0x48/0x1b0
> > [ 2.154144] nvkm_ioctl_new+0x168/0x254
> > [ 2.154149] nvkm_ioctl+0xd0/0x220
> > [ 2.154153] nvkm_client_ioctl+0x10/0x1c
> > [ 2.154162] nvif_object_ctor+0xf4/0x22c
> > [ 2.154168] nvif_device_ctor+0x28/0x70
> > [ 2.154174] nouveau_cli_init+0x150/0x590
> > [ 2.154180] nouveau_drm_device_init+0x60/0x2a0
> > [ 2.154187] nouveau_platform_device_create+0x90/0xd0
> > [ 2.154193] nouveau_platform_probe+0x3c/0x9c
> > [ 2.154200] platform_probe+0x68/0xc0
> > [ 2.154207] really_probe+0xbc/0x2dc
> > [ 2.154211] __driver_probe_device+0x78/0xe0
> > [ 2.154216] driver_probe_device+0xd8/0x160
> > [ 2.154221] __device_attach_driver+0xb8/0x134
> > [ 2.154226] bus_for_each_drv+0x78/0xd0
> > [ 2.154230] __device_attach+0x9c/0x1a0
> > [ 2.154234] device_initial_probe+0x14/0x20
> > [ 2.154239] bus_probe_device+0x98/0xa0
> > [ 2.154243] deferred_probe_work_func+0x88/0xc0
> > [ 2.154247] process_one_work+0x204/0x40c
> > [ 2.154256] worker_thread+0x230/0x450
> > [ 2.154261] kthread+0xc8/0xcc
> > [ 2.154266] ret_from_fork+0x10/0x20
> > [ 2.154273] ---[ end trace 0000000000000000 ]---
> > [ 2.154278] nouveau 57000000.gpu: pmu: map -22
> > [ 2.154285] nouveau 57000000.gpu: acr: one-time init failed, -22
> > [ 2.154559] nouveau 57000000.gpu: init failed with -22
> > [ 2.154564] nouveau: DRM-master:00000000:00000080: init failed with -22
> > [ 2.154574] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22
> > [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22
> >
> > #regzbot introduced: 2541626cfb79
>
> As a quick check can you try changing
>
> drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
>
> Dave.
I'm also reproducing the error on jetson-tx1 running 6.2-rc4 (rawhide
nodebug kernel) on Fedora 37 userspace.
With this change, the error is different:
nouveau: loading out-of-tree module taints kernel.
nouveau: module verification failed: signature and/or required key
missing - tainting kernel
Failed to set up IOMMU for device 57000000.gpu; retaining platform DMA ops
nouveau 57000000.gpu: NVIDIA GM20B (12b000a1)
nouveau 57000000.gpu: imem: using IOMMU
Unable to handle kernel execution of user memory at virtual address
0000000000000000
Mem abort info:
ESR = 0x0000000086000004
EC = 0x21: IABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x04: level 0 translation fault
user pgtable: 4k pages, 48-bit VAs, pgdp=000000013e136000
[0000000000000000] pgd=0000000000000000, p4d=0000000000000000
Internal error: Oops: 0000000086000004 [#1] SMP
Modules linked in: nouveau(OE+) drm_ttm_helper ttm snd_seq_dummy
snd_hrtimer nf_conntrack_netbios_ns nf_conntrack_broadcast
nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet
nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 rfkill ip_set nf_tables
nfnetlink qrtr sunrpc snd_soc_tegra_audio_graph_card
snd_soc_audio_graph_card snd_soc_simple_card_utils snd_soc_core
snd_compress snd_hda_codec_hdmi ac97_bus snd_hda_tegra
snd_pcm_dmaengine snd_hda_codec max77620_thermal vfat snd_hda_core fat
snd_hwdep snd_seq cpufreq_dt tegra_xudc snd_seq_device usb_conn_gpio
tegra_soctherm snd_pcm udc_core snd_timer snd at24 soundcore zram
r8152 mii panel_simple mmc_block tegra_drm drm_dp_aux_bus rtc_max77686
drm_display_helper lp855x_bl cec crct10dif_ce polyval_ce
polyval_generic xhci_tegra sdhci_tegra ghash_ce sdhci_pltfm
phy_tegra_xusb sdhci host1x ahci_tegra gpio_keys tegra210_emc cqhci
rtc_tegra i2c_tegra ip6_tables
abrt-dump-journal-oops: Found oopses: 1
abrt-dump-journal-oops: Creating problem directories
Can't find a meaningful backtrace for hashing in '.'
Preserving oops '.' because DropNotReportableOopses is 'no'
Reported 1 kernel oopses to Abrt
System encountered a non-fatal error in ??()
ip_tables fuse
CPU: 3 PID: 15789 Comm: insmod Tainted: G OE -------
--- 6.2.0-0.rc4.31.fc38.aarch64 #1
Hardware name: nvidia,p2371-2180 NVIDIA P2371-2180/NVIDIA P2371-2180,
BIOS 2022.10 10/01/2022
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : 0x0
lr : nvkm_falcon_load_dmem+0x60/0x80 [nouveau]
sp : ffff8000141034c0
x29: ffff8000141034c0 x28: ffff0000865d2008 x27: ffff0000c87b8638
x26: 00000000000000ff x25: ffff0000865d20a0 x24: 0000000000000000
x23: ffff0000f4ef34f8 x22: 000000000000002c x21: 0000000000005fd4
x20: ffff800014103534 x19: ffff0000f4ef34b8 x18: ffffffffffffffff
x17: 000000040044ffff x16: 00500074b5503510 x15: ffff8000141035d8
x14: ffff0000c87b8506 x13: 0000000000000001 x12: 0000000000000018
x11: 0000000000000001 x10: fffffffffffffec0 x9 : ffff8000091efa90
x8 : ffff800014103560 x7 : 0000000000000000 x6 : 0000000434da8f65
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 000000000000002c
x2 : 0000000000005fd4 x1 : ffff800014103534 x0 : ffff0000f4ef34b8
Call trace:
0x0
gm20b_pmu_init+0x70/0x90 [nouveau]
nvkm_pmu_init+0x28/0x40 [nouveau]
nvkm_subdev_init_+0x68/0x134 [nouveau]
nvkm_subdev_init+0x68/0xb0 [nouveau]
nvkm_device_init+0x154/0x2ac [nouveau]
nvkm_udevice_init+0x68/0xa0 [nouveau]
nvkm_object_init+0x50/0x1b4 [nouveau]
nvkm_ioctl_new+0x154/0x280 [nouveau]
nvkm_ioctl+0xd8/0x230 [nouveau]
nvkm_client_ioctl+0x18/0x24 [nouveau]
nvif_object_ctor+0xec/0x1a0 [nouveau]
nvif_device_ctor+0x30/0x7c [nouveau]
nouveau_cli_init+0x144/0x574 [nouveau]
nouveau_drm_device_init+0x68/0x2b0 [nouveau]
nouveau_platform_device_create+0x98/0xd0 [nouveau]
nouveau_platform_probe+0x34/0x90 [nouveau]
platform_probe+0x70/0xd0
really_probe+0xc8/0x3e4
__driver_probe_device+0x84/0x190
driver_probe_device+0x44/0x11c
__driver_attach+0xf8/0x200
bus_for_each_dev+0x6c/0xac
driver_attach+0x2c/0x40
bus_add_driver+0x188/0x250
driver_register+0x80/0x13c
__platform_driver_register+0x30/0x3c
nouveau_drm_init+0x9c/0x1000 [nouveau]
do_one_initcall+0x4c/0x2a0
do_init_module+0x50/0x200
load_module+0x9b0/0xb10
__do_sys_finit_module+0x98/0x100
__arm64_sys_finit_module+0x28/0x34
invoke_syscall+0x78/0x100
el0_svc_common.constprop.0+0x4c/0xf4
do_el0_svc+0x34/0x4c
el0_svc+0x34/0x10c
el0t_64_sync_handler+0x114/0x120
el0t_64_sync+0x194/0x198
Code: bad PC value
---[ end trace 0000000000000000 ]---
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-16 12:24 ` Diogo Ivo
(?)
@ 2023-01-18 1:28 ` Ben Skeggs
-1 siblings, 0 replies; 60+ messages in thread
From: Ben Skeggs @ 2023-01-18 1:28 UTC (permalink / raw)
To: Diogo Ivo; +Cc: David Airlie, bskeggs, regressions, dri-devel, nouveau
On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > As a quick check can you try changing
> >
> > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
>
> Hello!
>
> Applying this change breaks probing in a different way, with a
> bad PC=0x0. From a quick look at nvkm_falcon_load_dmem it looks like this
> could happen due to the .load_dmem() callback not being properly
> initialized. This is the kernel log I got:
In addition to Dave's change, can you try changing the
nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
sizeof(args), 0, false);
Ben.
>
> [ 2.010601] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
> [ 2.019436] Mem abort info:
> [ 2.022273] ESR = 0x0000000086000005
> [ 2.026066] EC = 0x21: IABT (current EL), IL = 32 bits
> [ 2.031429] SET = 0, FnV = 0
> [ 2.034528] EA = 0, S1PTW = 0
> [ 2.037694] FSC = 0x05: level 1 translation fault
> [ 2.042572] [0000000000000000] user address but active_mm is swapper
> [ 2.048961] Internal error: Oops: 0000000086000005 [#1] SMP
> [ 2.054529] Modules linked in:
> [ 2.057582] CPU: 0 PID: 36 Comm: kworker/u8:1 Not tainted 6.2.0-rc3+ #2
> [ 2.064190] Hardware name: Google Pixel C (DT)
> [ 2.068628] Workqueue: events_unbound deferred_probe_work_func
> [ 2.074463] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 2.081417] pc : 0x0
> [ 2.083600] lr : nvkm_falcon_load_dmem+0x58/0x80
> [ 2.088218] sp : ffffffc009ddb6f0
> [ 2.091526] x29: ffffffc009ddb6f0 x28: ffffff808028a008 x27: ffffff8081e43c38
> [ 2.098658] x26: 00000000000000ff x25: ffffff808028a0a0 x24: 0000000000000000
> [ 2.105788] x23: ffffff8080c328f8 x22: 000000000000002c x21: 0000000000005fd4
> [ 2.112917] x20: ffffffc009ddb76c x19: ffffff8080c328b8 x18: 0000000000000000
> [ 2.120047] x17: 2e74696e695f646f x16: 6874656d5f77732f x15: 0000000000000000
> [ 2.127176] x14: 0000000002f546c2 x13: 0000000000000000 x12: 00000000000001ce
> [ 2.134306] x11: 0000000000000001 x10: 0000000000000a90 x9 : ffffffc009ddb600
> [ 2.141436] x8 : ffffff80803d19f0 x7 : ffffff80bf971180 x6 : 00000000000001b9
> [ 2.148565] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 000000000000002c
> [ 2.155693] x2 : 0000000000005fd4 x1 : ffffffc009ddb76c x0 : ffffff8080c328b8
> [ 2.162822] Call trace:
> [ 2.165264] 0x0
> [ 2.167099] gm20b_pmu_init+0x78/0xb4
> [ 2.170762] nvkm_pmu_init+0x20/0x34
> [ 2.174334] nvkm_subdev_init_+0x60/0x12c
> [ 2.178339] nvkm_subdev_init+0x60/0xa0
> [ 2.182171] nvkm_device_init+0x14c/0x2a0
> [ 2.186178] nvkm_udevice_init+0x60/0x9c
> [ 2.190097] nvkm_object_init+0x48/0x1b0
> [ 2.194013] nvkm_ioctl_new+0x168/0x254
> [ 2.197843] nvkm_ioctl+0xd0/0x220
> [ 2.201239] nvkm_client_ioctl+0x10/0x1c
> [ 2.205160] nvif_object_ctor+0xf4/0x22c
> [ 2.209079] nvif_device_ctor+0x28/0x70
> [ 2.212910] nouveau_cli_init+0x150/0x590
> [ 2.216916] nouveau_drm_device_init+0x60/0x2a0
> [ 2.221442] nouveau_platform_device_create+0x90/0xd0
> [ 2.226489] nouveau_platform_probe+0x3c/0x9c
> [ 2.230841] platform_probe+0x68/0xc0
> [ 2.234500] really_probe+0xbc/0x2dc
> [ 2.238070] __driver_probe_device+0x78/0xe0
> [ 2.242334] driver_probe_device+0xd8/0x160
> [ 2.246511] __device_attach_driver+0xb8/0x134
> [ 2.250948] bus_for_each_drv+0x78/0xd0
> [ 2.254782] __device_attach+0x9c/0x1a0
> [ 2.258612] device_initial_probe+0x14/0x20
> [ 2.262789] bus_probe_device+0x98/0xa0
> [ 2.266619] deferred_probe_work_func+0x88/0xc0
> [ 2.271142] process_one_work+0x204/0x40c
> [ 2.275150] worker_thread+0x230/0x450
> [ 2.278894] kthread+0xc8/0xcc
> [ 2.281946] ret_from_fork+0x10/0x20
> [ 2.285525] Code: bad PC value
> [ 2.288576] ---[ end trace 0000000000000000 ]---
>
> Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-18 1:28 ` Ben Skeggs
0 siblings, 0 replies; 60+ messages in thread
From: Ben Skeggs @ 2023-01-18 1:28 UTC (permalink / raw)
To: Diogo Ivo; +Cc: David Airlie, bskeggs, regressions, dri-devel, nouveau
On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > As a quick check can you try changing
> >
> > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
>
> Hello!
>
> Applying this change breaks probing in a different way, with a
> bad PC=0x0. From a quick look at nvkm_falcon_load_dmem it looks like this
> could happen due to the .load_dmem() callback not being properly
> initialized. This is the kernel log I got:
In addition to Dave's change, can you try changing the
nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
sizeof(args), 0, false);
Ben.
>
> [ 2.010601] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
> [ 2.019436] Mem abort info:
> [ 2.022273] ESR = 0x0000000086000005
> [ 2.026066] EC = 0x21: IABT (current EL), IL = 32 bits
> [ 2.031429] SET = 0, FnV = 0
> [ 2.034528] EA = 0, S1PTW = 0
> [ 2.037694] FSC = 0x05: level 1 translation fault
> [ 2.042572] [0000000000000000] user address but active_mm is swapper
> [ 2.048961] Internal error: Oops: 0000000086000005 [#1] SMP
> [ 2.054529] Modules linked in:
> [ 2.057582] CPU: 0 PID: 36 Comm: kworker/u8:1 Not tainted 6.2.0-rc3+ #2
> [ 2.064190] Hardware name: Google Pixel C (DT)
> [ 2.068628] Workqueue: events_unbound deferred_probe_work_func
> [ 2.074463] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 2.081417] pc : 0x0
> [ 2.083600] lr : nvkm_falcon_load_dmem+0x58/0x80
> [ 2.088218] sp : ffffffc009ddb6f0
> [ 2.091526] x29: ffffffc009ddb6f0 x28: ffffff808028a008 x27: ffffff8081e43c38
> [ 2.098658] x26: 00000000000000ff x25: ffffff808028a0a0 x24: 0000000000000000
> [ 2.105788] x23: ffffff8080c328f8 x22: 000000000000002c x21: 0000000000005fd4
> [ 2.112917] x20: ffffffc009ddb76c x19: ffffff8080c328b8 x18: 0000000000000000
> [ 2.120047] x17: 2e74696e695f646f x16: 6874656d5f77732f x15: 0000000000000000
> [ 2.127176] x14: 0000000002f546c2 x13: 0000000000000000 x12: 00000000000001ce
> [ 2.134306] x11: 0000000000000001 x10: 0000000000000a90 x9 : ffffffc009ddb600
> [ 2.141436] x8 : ffffff80803d19f0 x7 : ffffff80bf971180 x6 : 00000000000001b9
> [ 2.148565] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 000000000000002c
> [ 2.155693] x2 : 0000000000005fd4 x1 : ffffffc009ddb76c x0 : ffffff8080c328b8
> [ 2.162822] Call trace:
> [ 2.165264] 0x0
> [ 2.167099] gm20b_pmu_init+0x78/0xb4
> [ 2.170762] nvkm_pmu_init+0x20/0x34
> [ 2.174334] nvkm_subdev_init_+0x60/0x12c
> [ 2.178339] nvkm_subdev_init+0x60/0xa0
> [ 2.182171] nvkm_device_init+0x14c/0x2a0
> [ 2.186178] nvkm_udevice_init+0x60/0x9c
> [ 2.190097] nvkm_object_init+0x48/0x1b0
> [ 2.194013] nvkm_ioctl_new+0x168/0x254
> [ 2.197843] nvkm_ioctl+0xd0/0x220
> [ 2.201239] nvkm_client_ioctl+0x10/0x1c
> [ 2.205160] nvif_object_ctor+0xf4/0x22c
> [ 2.209079] nvif_device_ctor+0x28/0x70
> [ 2.212910] nouveau_cli_init+0x150/0x590
> [ 2.216916] nouveau_drm_device_init+0x60/0x2a0
> [ 2.221442] nouveau_platform_device_create+0x90/0xd0
> [ 2.226489] nouveau_platform_probe+0x3c/0x9c
> [ 2.230841] platform_probe+0x68/0xc0
> [ 2.234500] really_probe+0xbc/0x2dc
> [ 2.238070] __driver_probe_device+0x78/0xe0
> [ 2.242334] driver_probe_device+0xd8/0x160
> [ 2.246511] __device_attach_driver+0xb8/0x134
> [ 2.250948] bus_for_each_drv+0x78/0xd0
> [ 2.254782] __device_attach+0x9c/0x1a0
> [ 2.258612] device_initial_probe+0x14/0x20
> [ 2.262789] bus_probe_device+0x98/0xa0
> [ 2.266619] deferred_probe_work_func+0x88/0xc0
> [ 2.271142] process_one_work+0x204/0x40c
> [ 2.275150] worker_thread+0x230/0x450
> [ 2.278894] kthread+0xc8/0xcc
> [ 2.281946] ret_from_fork+0x10/0x20
> [ 2.285525] Code: bad PC value
> [ 2.288576] ---[ end trace 0000000000000000 ]---
>
> Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-18 1:28 ` Ben Skeggs
0 siblings, 0 replies; 60+ messages in thread
From: Ben Skeggs @ 2023-01-18 1:28 UTC (permalink / raw)
To: Diogo Ivo; +Cc: David Airlie, nouveau, regressions, dri-devel, bskeggs
On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > As a quick check can you try changing
> >
> > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
>
> Hello!
>
> Applying this change breaks probing in a different way, with a
> bad PC=0x0. From a quick look at nvkm_falcon_load_dmem it looks like this
> could happen due to the .load_dmem() callback not being properly
> initialized. This is the kernel log I got:
In addition to Dave's change, can you try changing the
nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
sizeof(args), 0, false);
Ben.
>
> [ 2.010601] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
> [ 2.019436] Mem abort info:
> [ 2.022273] ESR = 0x0000000086000005
> [ 2.026066] EC = 0x21: IABT (current EL), IL = 32 bits
> [ 2.031429] SET = 0, FnV = 0
> [ 2.034528] EA = 0, S1PTW = 0
> [ 2.037694] FSC = 0x05: level 1 translation fault
> [ 2.042572] [0000000000000000] user address but active_mm is swapper
> [ 2.048961] Internal error: Oops: 0000000086000005 [#1] SMP
> [ 2.054529] Modules linked in:
> [ 2.057582] CPU: 0 PID: 36 Comm: kworker/u8:1 Not tainted 6.2.0-rc3+ #2
> [ 2.064190] Hardware name: Google Pixel C (DT)
> [ 2.068628] Workqueue: events_unbound deferred_probe_work_func
> [ 2.074463] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 2.081417] pc : 0x0
> [ 2.083600] lr : nvkm_falcon_load_dmem+0x58/0x80
> [ 2.088218] sp : ffffffc009ddb6f0
> [ 2.091526] x29: ffffffc009ddb6f0 x28: ffffff808028a008 x27: ffffff8081e43c38
> [ 2.098658] x26: 00000000000000ff x25: ffffff808028a0a0 x24: 0000000000000000
> [ 2.105788] x23: ffffff8080c328f8 x22: 000000000000002c x21: 0000000000005fd4
> [ 2.112917] x20: ffffffc009ddb76c x19: ffffff8080c328b8 x18: 0000000000000000
> [ 2.120047] x17: 2e74696e695f646f x16: 6874656d5f77732f x15: 0000000000000000
> [ 2.127176] x14: 0000000002f546c2 x13: 0000000000000000 x12: 00000000000001ce
> [ 2.134306] x11: 0000000000000001 x10: 0000000000000a90 x9 : ffffffc009ddb600
> [ 2.141436] x8 : ffffff80803d19f0 x7 : ffffff80bf971180 x6 : 00000000000001b9
> [ 2.148565] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 000000000000002c
> [ 2.155693] x2 : 0000000000005fd4 x1 : ffffffc009ddb76c x0 : ffffff8080c328b8
> [ 2.162822] Call trace:
> [ 2.165264] 0x0
> [ 2.167099] gm20b_pmu_init+0x78/0xb4
> [ 2.170762] nvkm_pmu_init+0x20/0x34
> [ 2.174334] nvkm_subdev_init_+0x60/0x12c
> [ 2.178339] nvkm_subdev_init+0x60/0xa0
> [ 2.182171] nvkm_device_init+0x14c/0x2a0
> [ 2.186178] nvkm_udevice_init+0x60/0x9c
> [ 2.190097] nvkm_object_init+0x48/0x1b0
> [ 2.194013] nvkm_ioctl_new+0x168/0x254
> [ 2.197843] nvkm_ioctl+0xd0/0x220
> [ 2.201239] nvkm_client_ioctl+0x10/0x1c
> [ 2.205160] nvif_object_ctor+0xf4/0x22c
> [ 2.209079] nvif_device_ctor+0x28/0x70
> [ 2.212910] nouveau_cli_init+0x150/0x590
> [ 2.216916] nouveau_drm_device_init+0x60/0x2a0
> [ 2.221442] nouveau_platform_device_create+0x90/0xd0
> [ 2.226489] nouveau_platform_probe+0x3c/0x9c
> [ 2.230841] platform_probe+0x68/0xc0
> [ 2.234500] really_probe+0xbc/0x2dc
> [ 2.238070] __driver_probe_device+0x78/0xe0
> [ 2.242334] driver_probe_device+0xd8/0x160
> [ 2.246511] __device_attach_driver+0xb8/0x134
> [ 2.250948] bus_for_each_drv+0x78/0xd0
> [ 2.254782] __device_attach+0x9c/0x1a0
> [ 2.258612] device_initial_probe+0x14/0x20
> [ 2.262789] bus_probe_device+0x98/0xa0
> [ 2.266619] deferred_probe_work_func+0x88/0xc0
> [ 2.271142] process_one_work+0x204/0x40c
> [ 2.275150] worker_thread+0x230/0x450
> [ 2.278894] kthread+0xc8/0xcc
> [ 2.281946] ret_from_fork+0x10/0x20
> [ 2.285525] Code: bad PC value
> [ 2.288576] ---[ end trace 0000000000000000 ]---
>
> Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-18 1:28 ` Ben Skeggs
@ 2023-01-18 8:42 ` Nicolas Chauvet
-1 siblings, 0 replies; 60+ messages in thread
From: Nicolas Chauvet @ 2023-01-18 8:42 UTC (permalink / raw)
To: Ben Skeggs
Cc: Diogo Ivo, David Airlie, bskeggs, regressions, dri-devel, nouveau
Le mer. 18 janv. 2023 à 02:29, Ben Skeggs <skeggsb@gmail.com> a écrit :
>
> On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > As a quick check can you try changing
> > >
> > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> >
> > Hello!
> >
> > Applying this change breaks probing in a different way, with a
> > bad PC=0x0. From a quick look at nvkm_falcon_load_dmem it looks like this
> > could happen due to the .load_dmem() callback not being properly
> > initialized. This is the kernel log I got:
> In addition to Dave's change, can you try changing the
> nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
>
> nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> sizeof(args), 0, false);
Here is the new stack trace:
[ 1112.488211] nouveau: loading out-of-tree module taints kernel.
[ 1112.494763] nouveau: module verification failed: signature and/or
required key missing - tainting kernel
[ 1112.534035] Failed to set up IOMMU for device 57000000.gpu;
retaining platform DMA ops
[ 1112.537536] nouveau 57000000.gpu: NVIDIA GM20B (12b000a1)
[ 1112.537587] nouveau 57000000.gpu: imem: using IOMMU
[ 1112.616677] ------------[ cut here ]------------
[ 1112.616820] nouveau 57000000.gpu: DRM: VRAM: 0 MiB
[ 1112.616830] nouveau 57000000.gpu: DRM: GART: 1048576 MiB
[ 1112.616688] WARNING: CPU: 0 PID: 388 at
/var/tmp/linux/drivers/gpu/drm/nouveau/nvkm/falcon/base.c:135
nvkm_falcon_pio_rd+0x150/0x2bc [nouveau]
[ 1112.617272] Modules linked in: nouveau(OE+) drm_ttm_helper ttm
snd_seq_dummy snd_hrtimer nf_conntrack_netbios_ns
nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib
nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct
nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 rfkill
ip_set nf_tables nfnetlink qrtr snd_soc_tegra_audio_graph_card
snd_soc_audio_graph_card snd_soc_simple_card_utils snd_soc_core
snd_hda_codec_hdmi snd_hda_tegra snd_compress snd_hda_codec ac97_bus
snd_hda_core snd_pcm_dmaengine snd_hwdep snd_seq snd_seq_device sunrpc
snd_pcm usb_conn_gpio snd_timer snd max77620_thermal tegra_xudc
tegra_soctherm udc_core soundcore cpufreq_dt at24 vfat fat zram r8152
mii panel_simple mmc_block tegra_drm drm_dp_aux_bus drm_display_helper
rtc_max77686 lp855x_bl crct10dif_ce cec polyval_ce polyval_generic
ghash_ce gpio_keys sdhci_tegra xhci_tegra sdhci_pltfm sdhci
phy_tegra_xusb rtc_tegra cqhci ahci_tegra host1x tegra210_emc
i2c_tegra ip6_tables
[ 1112.617430] ip_tables fuse
[ 1112.617440] CPU: 0 PID: 388 Comm: kworker/0:4 Tainted: G
OE ------- --- 6.2.0-0.rc4.31.fc38.aarch64 #1
[ 1112.617446] Hardware name: nvidia,p2371-2180 NVIDIA
P2371-2180/NVIDIA P2371-2180, BIOS 2022.10 10/01/2022
[ 1112.617452] Workqueue: events nvkm_pmu_recv [nouveau]
[ 1112.617934] pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 1112.617940] pc : nvkm_falcon_pio_rd+0x150/0x2bc [nouveau]
[ 1112.618418] nouveau 57000000.gpu: DRM: MM: using COPY for buffer copies
[ 1112.618525] lr : nvkm_falcon_pio_rd+0x50/0x2bc [nouveau]
[ 1112.619057] sp : ffff80000bf13c40
[ 1112.619060] x29: ffff80000bf13c50 x28: 0000000000000000 x27: 0000000000000000
[ 1112.619070] x26: ffff8000553f3d70 x25: ffff0000b04704b8 x24: 0000000000000000
[ 1112.619079] x23: ffff8000554800a0 x22: 0000000000000000 x21: ffff80000bf13d56
[ 1112.619086] x20: 000000000000002a x19: 0000000000000001 x18: 0000000000000000
[ 1112.619093] x17: 000000040044ffff x16: ffff8000091f53b0 x15: 0000000000000000
[ 1112.619100] x14: 0000000000000000 x13: 0000000000000030 x12: 0101010101010101
[ 1112.619108] x11: 7f7f7f7f7f7f7f7f x10: fefefefefefefeff x9 : ffff8000552cc224
[ 1112.619115] x8 : ffff0000b0470420 x7 : 0000000000000000 x6 : 000000000000002a
[ 1112.619123] x5 : 0000000000000000 x4 : ffff80005540b7c8 x3 : ffff0000b0470408
[ 1112.619130] x2 : ffff0000b0470420 x1 : ffff0000b0470408 x0 : 0000000000000003
[ 1112.619138] Call trace:
[ 1112.619141] nvkm_falcon_pio_rd+0x150/0x2bc [nouveau]
[ 1112.619756] nvkm_falcon_msgq_pop+0x90/0x1c0 [nouveau]
[ 1112.620313] nvkm_falcon_msgq_recv_initmsg+0xd4/0x1f4 [nouveau]
[ 1112.620877] gm20b_pmu_initmsg+0x3c/0xd4 [nouveau]
[ 1112.621418] gm20b_pmu_recv+0x30/0x80 [nouveau]
[ 1112.622004] nvkm_pmu_recv+0x24/0x30 [nouveau]
[ 1112.622547] process_one_work+0x1e8/0x480
[ 1112.622559] worker_thread+0x74/0x410
[ 1112.622564] kthread+0xe8/0xf4
[ 1112.622568] ret_from_fork+0x10/0x20
[ 1112.622577] ---[ end trace 0000000000000000 ]---
[ 1112.622696] nouveau 57000000.gpu: pmu: unexpected init message size 0 vs 42
[ 1112.622708] nouveau 57000000.gpu: pmu: error parsing init message: -22
[ 1112.623365] [drm] Initialized nouveau 1.3.1 20120801 for
57000000.gpu on minor 1
[ 1113.688183] nouveau 57000000.gpu: pmu:hpq: timeout waiting for queue ready
[ 1113.688246] nouveau 57000000.gpu: gr: init failed, -110
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-18 8:42 ` Nicolas Chauvet
0 siblings, 0 replies; 60+ messages in thread
From: Nicolas Chauvet @ 2023-01-18 8:42 UTC (permalink / raw)
To: Ben Skeggs
Cc: regressions, nouveau, dri-devel, Diogo Ivo, bskeggs, David Airlie
Le mer. 18 janv. 2023 à 02:29, Ben Skeggs <skeggsb@gmail.com> a écrit :
>
> On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > As a quick check can you try changing
> > >
> > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> >
> > Hello!
> >
> > Applying this change breaks probing in a different way, with a
> > bad PC=0x0. From a quick look at nvkm_falcon_load_dmem it looks like this
> > could happen due to the .load_dmem() callback not being properly
> > initialized. This is the kernel log I got:
> In addition to Dave's change, can you try changing the
> nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
>
> nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> sizeof(args), 0, false);
Here is the new stack trace:
[ 1112.488211] nouveau: loading out-of-tree module taints kernel.
[ 1112.494763] nouveau: module verification failed: signature and/or
required key missing - tainting kernel
[ 1112.534035] Failed to set up IOMMU for device 57000000.gpu;
retaining platform DMA ops
[ 1112.537536] nouveau 57000000.gpu: NVIDIA GM20B (12b000a1)
[ 1112.537587] nouveau 57000000.gpu: imem: using IOMMU
[ 1112.616677] ------------[ cut here ]------------
[ 1112.616820] nouveau 57000000.gpu: DRM: VRAM: 0 MiB
[ 1112.616830] nouveau 57000000.gpu: DRM: GART: 1048576 MiB
[ 1112.616688] WARNING: CPU: 0 PID: 388 at
/var/tmp/linux/drivers/gpu/drm/nouveau/nvkm/falcon/base.c:135
nvkm_falcon_pio_rd+0x150/0x2bc [nouveau]
[ 1112.617272] Modules linked in: nouveau(OE+) drm_ttm_helper ttm
snd_seq_dummy snd_hrtimer nf_conntrack_netbios_ns
nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib
nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct
nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 rfkill
ip_set nf_tables nfnetlink qrtr snd_soc_tegra_audio_graph_card
snd_soc_audio_graph_card snd_soc_simple_card_utils snd_soc_core
snd_hda_codec_hdmi snd_hda_tegra snd_compress snd_hda_codec ac97_bus
snd_hda_core snd_pcm_dmaengine snd_hwdep snd_seq snd_seq_device sunrpc
snd_pcm usb_conn_gpio snd_timer snd max77620_thermal tegra_xudc
tegra_soctherm udc_core soundcore cpufreq_dt at24 vfat fat zram r8152
mii panel_simple mmc_block tegra_drm drm_dp_aux_bus drm_display_helper
rtc_max77686 lp855x_bl crct10dif_ce cec polyval_ce polyval_generic
ghash_ce gpio_keys sdhci_tegra xhci_tegra sdhci_pltfm sdhci
phy_tegra_xusb rtc_tegra cqhci ahci_tegra host1x tegra210_emc
i2c_tegra ip6_tables
[ 1112.617430] ip_tables fuse
[ 1112.617440] CPU: 0 PID: 388 Comm: kworker/0:4 Tainted: G
OE ------- --- 6.2.0-0.rc4.31.fc38.aarch64 #1
[ 1112.617446] Hardware name: nvidia,p2371-2180 NVIDIA
P2371-2180/NVIDIA P2371-2180, BIOS 2022.10 10/01/2022
[ 1112.617452] Workqueue: events nvkm_pmu_recv [nouveau]
[ 1112.617934] pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 1112.617940] pc : nvkm_falcon_pio_rd+0x150/0x2bc [nouveau]
[ 1112.618418] nouveau 57000000.gpu: DRM: MM: using COPY for buffer copies
[ 1112.618525] lr : nvkm_falcon_pio_rd+0x50/0x2bc [nouveau]
[ 1112.619057] sp : ffff80000bf13c40
[ 1112.619060] x29: ffff80000bf13c50 x28: 0000000000000000 x27: 0000000000000000
[ 1112.619070] x26: ffff8000553f3d70 x25: ffff0000b04704b8 x24: 0000000000000000
[ 1112.619079] x23: ffff8000554800a0 x22: 0000000000000000 x21: ffff80000bf13d56
[ 1112.619086] x20: 000000000000002a x19: 0000000000000001 x18: 0000000000000000
[ 1112.619093] x17: 000000040044ffff x16: ffff8000091f53b0 x15: 0000000000000000
[ 1112.619100] x14: 0000000000000000 x13: 0000000000000030 x12: 0101010101010101
[ 1112.619108] x11: 7f7f7f7f7f7f7f7f x10: fefefefefefefeff x9 : ffff8000552cc224
[ 1112.619115] x8 : ffff0000b0470420 x7 : 0000000000000000 x6 : 000000000000002a
[ 1112.619123] x5 : 0000000000000000 x4 : ffff80005540b7c8 x3 : ffff0000b0470408
[ 1112.619130] x2 : ffff0000b0470420 x1 : ffff0000b0470408 x0 : 0000000000000003
[ 1112.619138] Call trace:
[ 1112.619141] nvkm_falcon_pio_rd+0x150/0x2bc [nouveau]
[ 1112.619756] nvkm_falcon_msgq_pop+0x90/0x1c0 [nouveau]
[ 1112.620313] nvkm_falcon_msgq_recv_initmsg+0xd4/0x1f4 [nouveau]
[ 1112.620877] gm20b_pmu_initmsg+0x3c/0xd4 [nouveau]
[ 1112.621418] gm20b_pmu_recv+0x30/0x80 [nouveau]
[ 1112.622004] nvkm_pmu_recv+0x24/0x30 [nouveau]
[ 1112.622547] process_one_work+0x1e8/0x480
[ 1112.622559] worker_thread+0x74/0x410
[ 1112.622564] kthread+0xe8/0xf4
[ 1112.622568] ret_from_fork+0x10/0x20
[ 1112.622577] ---[ end trace 0000000000000000 ]---
[ 1112.622696] nouveau 57000000.gpu: pmu: unexpected init message size 0 vs 42
[ 1112.622708] nouveau 57000000.gpu: pmu: error parsing init message: -22
[ 1112.623365] [drm] Initialized nouveau 1.3.1 20120801 for
57000000.gpu on minor 1
[ 1113.688183] nouveau 57000000.gpu: pmu:hpq: timeout waiting for queue ready
[ 1113.688246] nouveau 57000000.gpu: gr: init failed, -110
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-18 1:28 ` Ben Skeggs
(?)
@ 2023-01-20 11:34 ` Diogo Ivo
-1 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-20 11:34 UTC (permalink / raw)
To: Ben Skeggs
Cc: regressions, kherbst, kwizart, nouveau, dri-devel, bskeggs, David Airlie
On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > As a quick check can you try changing
> > >
> > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> In addition to Dave's change, can you try changing the
> nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
>
> nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> sizeof(args), 0, false);
Hello!
Chiming in just to say that with this change I see the same as Nicolas
except that the init message size is 255 instead of 0:
[ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-20 11:34 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-20 11:34 UTC (permalink / raw)
To: Ben Skeggs
Cc: David Airlie, nouveau, regressions, dri-devel, bskeggs, kwizart, kherbst
On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > As a quick check can you try changing
> > >
> > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> In addition to Dave's change, can you try changing the
> nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
>
> nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> sizeof(args), 0, false);
Hello!
Chiming in just to say that with this change I see the same as Nicolas
except that the init message size is 255 instead of 0:
[ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-20 11:34 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-20 11:34 UTC (permalink / raw)
To: Ben Skeggs; +Cc: regressions, nouveau, dri-devel, bskeggs, David Airlie
On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > As a quick check can you try changing
> > >
> > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> In addition to Dave's change, can you try changing the
> nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
>
> nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> sizeof(args), 0, false);
Hello!
Chiming in just to say that with this change I see the same as Nicolas
except that the init message size is 255 instead of 0:
[ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-20 11:34 ` Diogo Ivo
(?)
@ 2023-01-27 6:00 ` Ben Skeggs
-1 siblings, 0 replies; 60+ messages in thread
From: Ben Skeggs @ 2023-01-27 6:00 UTC (permalink / raw)
To: Diogo Ivo
Cc: David Airlie, nouveau, regressions, dri-devel, bskeggs, kwizart, kherbst
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > As a quick check can you try changing
> > > >
> > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
>
> > In addition to Dave's change, can you try changing the
> > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> >
> > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > sizeof(args), 0, false);
>
> Hello!
>
> Chiming in just to say that with this change I see the same as Nicolas
> except that the init message size is 255 instead of 0:
>
> [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
I've attached an entirely untested patch (to go on top of the other
hacks/fixes so far), that will hopefully get us a little further.
Would be great if you guys could test it out for me.
Thanks,
Ben.
[-- Attachment #2: gm20b.diff --]
[-- Type: text/x-patch, Size: 1030 bytes --]
diff --git a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
index 393ade9f7e6c..b7da3ab44c27 100644
--- a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
+++ b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
@@ -48,6 +48,16 @@ gm200_flcn_pio_dmem_rd(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ /* Sigh. Tegra PMU FW's init message... */
+ if (len) {
+ u32 data = nvkm_falcon_rd32(falcon, 0x1c4 + (port * 8));
+
+ while (len--) {
+ *(u8 *)img++ = data & 0xff;
+ data >>= 8;
+ }
+ }
}
static void
@@ -64,6 +74,8 @@ gm200_flcn_pio_dmem_wr(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ WARN_ON(len);
}
static void
@@ -74,7 +86,7 @@ gm200_flcn_pio_dmem_wr_init(struct nvkm_falcon *falcon, u8 port, bool sec, u32 d
const struct nvkm_falcon_func_pio
gm200_flcn_dmem_pio = {
- .min = 4,
+ .min = 1,
.max = 0x100,
.wr_init = gm200_flcn_pio_dmem_wr_init,
.wr = gm200_flcn_pio_dmem_wr,
^ permalink raw reply related [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-27 6:00 ` Ben Skeggs
0 siblings, 0 replies; 60+ messages in thread
From: Ben Skeggs @ 2023-01-27 6:00 UTC (permalink / raw)
To: Diogo Ivo; +Cc: regressions, nouveau, dri-devel, bskeggs, David Airlie
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > As a quick check can you try changing
> > > >
> > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
>
> > In addition to Dave's change, can you try changing the
> > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> >
> > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > sizeof(args), 0, false);
>
> Hello!
>
> Chiming in just to say that with this change I see the same as Nicolas
> except that the init message size is 255 instead of 0:
>
> [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
I've attached an entirely untested patch (to go on top of the other
hacks/fixes so far), that will hopefully get us a little further.
Would be great if you guys could test it out for me.
Thanks,
Ben.
[-- Attachment #2: gm20b.diff --]
[-- Type: text/x-patch, Size: 1030 bytes --]
diff --git a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
index 393ade9f7e6c..b7da3ab44c27 100644
--- a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
+++ b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
@@ -48,6 +48,16 @@ gm200_flcn_pio_dmem_rd(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ /* Sigh. Tegra PMU FW's init message... */
+ if (len) {
+ u32 data = nvkm_falcon_rd32(falcon, 0x1c4 + (port * 8));
+
+ while (len--) {
+ *(u8 *)img++ = data & 0xff;
+ data >>= 8;
+ }
+ }
}
static void
@@ -64,6 +74,8 @@ gm200_flcn_pio_dmem_wr(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ WARN_ON(len);
}
static void
@@ -74,7 +86,7 @@ gm200_flcn_pio_dmem_wr_init(struct nvkm_falcon *falcon, u8 port, bool sec, u32 d
const struct nvkm_falcon_func_pio
gm200_flcn_dmem_pio = {
- .min = 4,
+ .min = 1,
.max = 0x100,
.wr_init = gm200_flcn_pio_dmem_wr_init,
.wr = gm200_flcn_pio_dmem_wr,
^ permalink raw reply related [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-27 6:00 ` Ben Skeggs
0 siblings, 0 replies; 60+ messages in thread
From: Ben Skeggs @ 2023-01-27 6:00 UTC (permalink / raw)
To: Diogo Ivo
Cc: regressions, kherbst, kwizart, nouveau, dri-devel, bskeggs, David Airlie
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > As a quick check can you try changing
> > > >
> > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
>
> > In addition to Dave's change, can you try changing the
> > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> >
> > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > sizeof(args), 0, false);
>
> Hello!
>
> Chiming in just to say that with this change I see the same as Nicolas
> except that the init message size is 255 instead of 0:
>
> [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
I've attached an entirely untested patch (to go on top of the other
hacks/fixes so far), that will hopefully get us a little further.
Would be great if you guys could test it out for me.
Thanks,
Ben.
[-- Attachment #2: gm20b.diff --]
[-- Type: text/x-patch, Size: 1030 bytes --]
diff --git a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
index 393ade9f7e6c..b7da3ab44c27 100644
--- a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
+++ b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
@@ -48,6 +48,16 @@ gm200_flcn_pio_dmem_rd(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ /* Sigh. Tegra PMU FW's init message... */
+ if (len) {
+ u32 data = nvkm_falcon_rd32(falcon, 0x1c4 + (port * 8));
+
+ while (len--) {
+ *(u8 *)img++ = data & 0xff;
+ data >>= 8;
+ }
+ }
}
static void
@@ -64,6 +74,8 @@ gm200_flcn_pio_dmem_wr(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ WARN_ON(len);
}
static void
@@ -74,7 +86,7 @@ gm200_flcn_pio_dmem_wr_init(struct nvkm_falcon *falcon, u8 port, bool sec, u32 d
const struct nvkm_falcon_func_pio
gm200_flcn_dmem_pio = {
- .min = 4,
+ .min = 1,
.max = 0x100,
.wr_init = gm200_flcn_pio_dmem_wr_init,
.wr = gm200_flcn_pio_dmem_wr,
^ permalink raw reply related [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-27 6:00 ` [Nouveau] " Ben Skeggs
(?)
@ 2023-01-27 9:03 ` Nicolas Chauvet
-1 siblings, 0 replies; 60+ messages in thread
From: Nicolas Chauvet @ 2023-01-27 9:03 UTC (permalink / raw)
To: Ben Skeggs
Cc: Diogo Ivo, David Airlie, nouveau, regressions, dri-devel,
bskeggs, kherbst
Le ven. 27 janv. 2023 à 07:01, Ben Skeggs <skeggsb@gmail.com> a écrit :
>
> On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > As a quick check can you try changing
> > > > >
> > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> >
> > > In addition to Dave's change, can you try changing the
> > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > >
> > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > sizeof(args), 0, false);
> >
> > Hello!
> >
> > Chiming in just to say that with this change I see the same as Nicolas
> > except that the init message size is 255 instead of 0:
> >
> > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> I've attached an entirely untested patch (to go on top of the other
> hacks/fixes so far), that will hopefully get us a little further.
>
> Would be great if you guys could test it out for me.
Hello,
Thanks for the patch. It works for me on: jetson-tx1:
---
[ 1022.814699] nouveau 57000000.gpu: NVIDIA GM20B (12b000a1)
[ 1022.814750] nouveau 57000000.gpu: imem: using IOMMU
[ 1022.893976] nouveau 57000000.gpu: DRM: VRAM: 0 MiB
[ 1022.893988] nouveau 57000000.gpu: DRM: GART: 1048576 MiB
[ 1022.895356] nouveau 57000000.gpu: DRM: MM: using COPY for buffer copies
[ 1022.897046] [drm] Initialized nouveau 1.3.1 20120801 for
57000000.gpu on minor 1
---
I've tried to run glmark2-wayland under weston with DRI_PRIME=1, it
seems to work at the beginning, but then I have the following error:
[ 1510.861730] nouveau 57000000.gpu: gr: DATA_ERROR 00000003
[INVALID_OPERATION] ch 3 [04002a2000 glmark2-wayland[2753]] subc 0
class b197 mthd 19d0 data 0000003d
[ 1510.952000] nouveau 57000000.gpu: gr: DATA_ERROR 00000003
[INVALID_OPERATION] ch 3 [04002a2000 glmark2-wayland[2753]] subc 0
class b197 mthd 19d0 data 0000003d
[ 1510.952060] nouveau 57000000.gpu: gr: DATA_ERROR 0000009c [] ch 3
[04002a2000 glmark2-wayland[2753]] subc 0 class b197 mthd 0d78 data
00000006
I think it's a separate error as I think I can reproduce on kernel
6.1x (I will open a separate thread).
So you can add my
Tested-By: Nicolas Chauvet <kwizart@gmail.com>
Thanks
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-27 9:03 ` Nicolas Chauvet
0 siblings, 0 replies; 60+ messages in thread
From: Nicolas Chauvet @ 2023-01-27 9:03 UTC (permalink / raw)
To: Ben Skeggs
Cc: regressions, nouveau, dri-devel, Diogo Ivo, bskeggs, David Airlie
Le ven. 27 janv. 2023 à 07:01, Ben Skeggs <skeggsb@gmail.com> a écrit :
>
> On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > As a quick check can you try changing
> > > > >
> > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> >
> > > In addition to Dave's change, can you try changing the
> > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > >
> > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > sizeof(args), 0, false);
> >
> > Hello!
> >
> > Chiming in just to say that with this change I see the same as Nicolas
> > except that the init message size is 255 instead of 0:
> >
> > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> I've attached an entirely untested patch (to go on top of the other
> hacks/fixes so far), that will hopefully get us a little further.
>
> Would be great if you guys could test it out for me.
Hello,
Thanks for the patch. It works for me on: jetson-tx1:
---
[ 1022.814699] nouveau 57000000.gpu: NVIDIA GM20B (12b000a1)
[ 1022.814750] nouveau 57000000.gpu: imem: using IOMMU
[ 1022.893976] nouveau 57000000.gpu: DRM: VRAM: 0 MiB
[ 1022.893988] nouveau 57000000.gpu: DRM: GART: 1048576 MiB
[ 1022.895356] nouveau 57000000.gpu: DRM: MM: using COPY for buffer copies
[ 1022.897046] [drm] Initialized nouveau 1.3.1 20120801 for
57000000.gpu on minor 1
---
I've tried to run glmark2-wayland under weston with DRI_PRIME=1, it
seems to work at the beginning, but then I have the following error:
[ 1510.861730] nouveau 57000000.gpu: gr: DATA_ERROR 00000003
[INVALID_OPERATION] ch 3 [04002a2000 glmark2-wayland[2753]] subc 0
class b197 mthd 19d0 data 0000003d
[ 1510.952000] nouveau 57000000.gpu: gr: DATA_ERROR 00000003
[INVALID_OPERATION] ch 3 [04002a2000 glmark2-wayland[2753]] subc 0
class b197 mthd 19d0 data 0000003d
[ 1510.952060] nouveau 57000000.gpu: gr: DATA_ERROR 0000009c [] ch 3
[04002a2000 glmark2-wayland[2753]] subc 0 class b197 mthd 0d78 data
00000006
I think it's a separate error as I think I can reproduce on kernel
6.1x (I will open a separate thread).
So you can add my
Tested-By: Nicolas Chauvet <kwizart@gmail.com>
Thanks
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-27 9:03 ` Nicolas Chauvet
0 siblings, 0 replies; 60+ messages in thread
From: Nicolas Chauvet @ 2023-01-27 9:03 UTC (permalink / raw)
To: Ben Skeggs
Cc: regressions, kherbst, nouveau, dri-devel, Diogo Ivo, bskeggs,
David Airlie
Le ven. 27 janv. 2023 à 07:01, Ben Skeggs <skeggsb@gmail.com> a écrit :
>
> On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > As a quick check can you try changing
> > > > >
> > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> >
> > > In addition to Dave's change, can you try changing the
> > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > >
> > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > sizeof(args), 0, false);
> >
> > Hello!
> >
> > Chiming in just to say that with this change I see the same as Nicolas
> > except that the init message size is 255 instead of 0:
> >
> > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> I've attached an entirely untested patch (to go on top of the other
> hacks/fixes so far), that will hopefully get us a little further.
>
> Would be great if you guys could test it out for me.
Hello,
Thanks for the patch. It works for me on: jetson-tx1:
---
[ 1022.814699] nouveau 57000000.gpu: NVIDIA GM20B (12b000a1)
[ 1022.814750] nouveau 57000000.gpu: imem: using IOMMU
[ 1022.893976] nouveau 57000000.gpu: DRM: VRAM: 0 MiB
[ 1022.893988] nouveau 57000000.gpu: DRM: GART: 1048576 MiB
[ 1022.895356] nouveau 57000000.gpu: DRM: MM: using COPY for buffer copies
[ 1022.897046] [drm] Initialized nouveau 1.3.1 20120801 for
57000000.gpu on minor 1
---
I've tried to run glmark2-wayland under weston with DRI_PRIME=1, it
seems to work at the beginning, but then I have the following error:
[ 1510.861730] nouveau 57000000.gpu: gr: DATA_ERROR 00000003
[INVALID_OPERATION] ch 3 [04002a2000 glmark2-wayland[2753]] subc 0
class b197 mthd 19d0 data 0000003d
[ 1510.952000] nouveau 57000000.gpu: gr: DATA_ERROR 00000003
[INVALID_OPERATION] ch 3 [04002a2000 glmark2-wayland[2753]] subc 0
class b197 mthd 19d0 data 0000003d
[ 1510.952060] nouveau 57000000.gpu: gr: DATA_ERROR 0000009c [] ch 3
[04002a2000 glmark2-wayland[2753]] subc 0 class b197 mthd 0d78 data
00000006
I think it's a separate error as I think I can reproduce on kernel
6.1x (I will open a separate thread).
So you can add my
Tested-By: Nicolas Chauvet <kwizart@gmail.com>
Thanks
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-27 6:00 ` [Nouveau] " Ben Skeggs
(?)
@ 2023-01-27 10:39 ` Diogo Ivo
-1 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-27 10:39 UTC (permalink / raw)
To: Ben Skeggs; +Cc: regressions, kherbst, kwizart, nouveau, dri-devel, airlied
On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > As a quick check can you try changing
> > > > >
> > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> >
> > > In addition to Dave's change, can you try changing the
> > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > >
> > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > sizeof(args), 0, false);
> >
> > Chiming in just to say that with this change I see the same as Nicolas
> > except that the init message size is 255 instead of 0:
> >
> > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> I've attached an entirely untested patch (to go on top of the other
> hacks/fixes so far), that will hopefully get us a little further.
Hello,
Thank you for the patch! I can confirm that it fixes the problem
on the Pixel C, and everything works as before the regression.
With this, for the combination of patches
Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
which I can resend after testing the final patch version.
Thanks,
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-27 10:39 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-27 10:39 UTC (permalink / raw)
To: Ben Skeggs; +Cc: airlied, nouveau, regressions, dri-devel, kwizart, kherbst
On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > As a quick check can you try changing
> > > > >
> > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> >
> > > In addition to Dave's change, can you try changing the
> > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > >
> > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > sizeof(args), 0, false);
> >
> > Chiming in just to say that with this change I see the same as Nicolas
> > except that the init message size is 255 instead of 0:
> >
> > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> I've attached an entirely untested patch (to go on top of the other
> hacks/fixes so far), that will hopefully get us a little further.
Hello,
Thank you for the patch! I can confirm that it fixes the problem
on the Pixel C, and everything works as before the regression.
With this, for the combination of patches
Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
which I can resend after testing the final patch version.
Thanks,
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-27 10:39 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-27 10:39 UTC (permalink / raw)
To: Ben Skeggs; +Cc: regressions, nouveau, dri-devel, airlied
On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > As a quick check can you try changing
> > > > >
> > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> >
> > > In addition to Dave's change, can you try changing the
> > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > >
> > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > sizeof(args), 0, false);
> >
> > Chiming in just to say that with this change I see the same as Nicolas
> > except that the init message size is 255 instead of 0:
> >
> > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> I've attached an entirely untested patch (to go on top of the other
> hacks/fixes so far), that will hopefully get us a little further.
Hello,
Thank you for the patch! I can confirm that it fixes the problem
on the Pixel C, and everything works as before the regression.
With this, for the combination of patches
Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
which I can resend after testing the final patch version.
Thanks,
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-27 9:03 ` [Nouveau] " Nicolas Chauvet
@ 2023-01-27 10:48 ` Diogo Ivo
-1 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-27 10:48 UTC (permalink / raw)
To: Nicolas Chauvet; +Cc: David Airlie, Ben Skeggs, kherbst, dri-devel, nouveau
On Fri, Jan 27, 2023 at 10:03:17AM +0100, Nicolas Chauvet wrote:
> I've tried to run glmark2-wayland under weston with DRI_PRIME=1, it
> seems to work at the beginning, but then I have the following error:
>
> [ 1510.861730] nouveau 57000000.gpu: gr: DATA_ERROR 00000003
> [INVALID_OPERATION] ch 3 [04002a2000 glmark2-wayland[2753]] subc 0
> class b197 mthd 19d0 data 0000003d
> [ 1510.952000] nouveau 57000000.gpu: gr: DATA_ERROR 00000003
> [INVALID_OPERATION] ch 3 [04002a2000 glmark2-wayland[2753]] subc 0
> class b197 mthd 19d0 data 0000003d
> [ 1510.952060] nouveau 57000000.gpu: gr: DATA_ERROR 0000009c [] ch 3
> [04002a2000 glmark2-wayland[2753]] subc 0 class b197 mthd 0d78 data
> 00000006
> I think it's a separate error as I think I can reproduce on kernel
> 6.1x (I will open a separate thread).
Hello,
Would you mind testing this Mesa merge request (and the kernel patches
mentioned there) to see if it fixes this error:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20811
Thanks,
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-27 10:48 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-27 10:48 UTC (permalink / raw)
To: Nicolas Chauvet; +Cc: David Airlie, dri-devel, nouveau
On Fri, Jan 27, 2023 at 10:03:17AM +0100, Nicolas Chauvet wrote:
> I've tried to run glmark2-wayland under weston with DRI_PRIME=1, it
> seems to work at the beginning, but then I have the following error:
>
> [ 1510.861730] nouveau 57000000.gpu: gr: DATA_ERROR 00000003
> [INVALID_OPERATION] ch 3 [04002a2000 glmark2-wayland[2753]] subc 0
> class b197 mthd 19d0 data 0000003d
> [ 1510.952000] nouveau 57000000.gpu: gr: DATA_ERROR 00000003
> [INVALID_OPERATION] ch 3 [04002a2000 glmark2-wayland[2753]] subc 0
> class b197 mthd 19d0 data 0000003d
> [ 1510.952060] nouveau 57000000.gpu: gr: DATA_ERROR 0000009c [] ch 3
> [04002a2000 glmark2-wayland[2753]] subc 0 class b197 mthd 0d78 data
> 00000006
> I think it's a separate error as I think I can reproduce on kernel
> 6.1x (I will open a separate thread).
Hello,
Would you mind testing this Mesa merge request (and the kernel patches
mentioned there) to see if it fixes this error:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20811
Thanks,
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-27 10:39 ` Diogo Ivo
(?)
@ 2023-01-29 22:36 ` Ben Skeggs
-1 siblings, 0 replies; 60+ messages in thread
From: Ben Skeggs @ 2023-01-29 22:36 UTC (permalink / raw)
To: Diogo Ivo; +Cc: airlied, nouveau, regressions, dri-devel, kwizart, kherbst
[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]
On Fri, 27 Jan 2023 at 20:42, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > >
> > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > > As a quick check can you try changing
> > > > > >
> > > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> > >
> > > > In addition to Dave's change, can you try changing the
> > > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > > >
> > > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > > sizeof(args), 0, false);
> > >
> > > Chiming in just to say that with this change I see the same as Nicolas
> > > except that the init message size is 255 instead of 0:
> > >
> > > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> > I've attached an entirely untested patch (to go on top of the other
> > hacks/fixes so far), that will hopefully get us a little further.
>
> Hello,
>
> Thank you for the patch! I can confirm that it fixes the problem
> on the Pixel C, and everything works as before the regression.
> With this, for the combination of patches
>
> Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
>
> which I can resend after testing the final patch version.
Thank you (both!) for testing!
I've attached a "final" version of a patch that I'll send (assuming it
still works ;)) after re-testing. There's only a minor change to
avoid breaking the non-Tegra path, so I expect it should be fine.
Ben.
>
> Thanks,
> Diogo
[-- Attachment #2: 0001-drm-nouveau-acr-gm20b-regression-fixes.patch --]
[-- Type: text/x-patch, Size: 2775 bytes --]
From bfc1b84d26ca28f78a07d494b0813fe642e80bbe Mon Sep 17 00:00:00 2001
From: Ben Skeggs <bskeggs@redhat.com>
Date: Fri, 27 Jan 2023 15:42:27 +1000
Subject: [PATCH] drm/nouveau/acr/gm20b: regression fixes
Missed some Tegra-specific quirks when reworking ACR to support Ampere.
Fixes: 2541626cfb79 ("drm/nouveau/acr: use common falcon HS FW code for ACR FWs")
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
---
drivers/gpu/drm/nouveau/nvkm/core/firmware.c | 3 +++
drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c | 14 +++++++++++++-
drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c | 2 +-
3 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nvkm/core/firmware.c b/drivers/gpu/drm/nouveau/nvkm/core/firmware.c
index fcf2a002f6cb..91fb494d4009 100644
--- a/drivers/gpu/drm/nouveau/nvkm/core/firmware.c
+++ b/drivers/gpu/drm/nouveau/nvkm/core/firmware.c
@@ -151,6 +151,9 @@ nvkm_firmware_mem_page(struct nvkm_memory *memory)
static enum nvkm_memory_target
nvkm_firmware_mem_target(struct nvkm_memory *memory)
{
+ if (nvkm_firmware_mem(memory)->device->func->tegra)
+ return NVKM_MEM_TARGET_NCOH;
+
return NVKM_MEM_TARGET_HOST;
}
diff --git a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
index 393ade9f7e6c..b7da3ab44c27 100644
--- a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
+++ b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
@@ -48,6 +48,16 @@ gm200_flcn_pio_dmem_rd(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ /* Sigh. Tegra PMU FW's init message... */
+ if (len) {
+ u32 data = nvkm_falcon_rd32(falcon, 0x1c4 + (port * 8));
+
+ while (len--) {
+ *(u8 *)img++ = data & 0xff;
+ data >>= 8;
+ }
+ }
}
static void
@@ -64,6 +74,8 @@ gm200_flcn_pio_dmem_wr(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ WARN_ON(len);
}
static void
@@ -74,7 +86,7 @@ gm200_flcn_pio_dmem_wr_init(struct nvkm_falcon *falcon, u8 port, bool sec, u32 d
const struct nvkm_falcon_func_pio
gm200_flcn_dmem_pio = {
- .min = 4,
+ .min = 1,
.max = 0x100,
.wr_init = gm200_flcn_pio_dmem_wr_init,
.wr = gm200_flcn_pio_dmem_wr,
diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c b/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c
index a72403777329..2ed04da3621d 100644
--- a/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c
+++ b/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c
@@ -225,7 +225,7 @@ gm20b_pmu_init(struct nvkm_pmu *pmu)
pmu->initmsg_received = false;
- nvkm_falcon_load_dmem(falcon, &args, addr_args, sizeof(args), 0);
+ nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args, sizeof(args), 0, false);
nvkm_falcon_start(falcon);
return 0;
}
--
2.35.1
^ permalink raw reply related [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-29 22:36 ` Ben Skeggs
0 siblings, 0 replies; 60+ messages in thread
From: Ben Skeggs @ 2023-01-29 22:36 UTC (permalink / raw)
To: Diogo Ivo; +Cc: regressions, nouveau, dri-devel, airlied
[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]
On Fri, 27 Jan 2023 at 20:42, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > >
> > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > > As a quick check can you try changing
> > > > > >
> > > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> > >
> > > > In addition to Dave's change, can you try changing the
> > > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > > >
> > > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > > sizeof(args), 0, false);
> > >
> > > Chiming in just to say that with this change I see the same as Nicolas
> > > except that the init message size is 255 instead of 0:
> > >
> > > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> > I've attached an entirely untested patch (to go on top of the other
> > hacks/fixes so far), that will hopefully get us a little further.
>
> Hello,
>
> Thank you for the patch! I can confirm that it fixes the problem
> on the Pixel C, and everything works as before the regression.
> With this, for the combination of patches
>
> Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
>
> which I can resend after testing the final patch version.
Thank you (both!) for testing!
I've attached a "final" version of a patch that I'll send (assuming it
still works ;)) after re-testing. There's only a minor change to
avoid breaking the non-Tegra path, so I expect it should be fine.
Ben.
>
> Thanks,
> Diogo
[-- Attachment #2: 0001-drm-nouveau-acr-gm20b-regression-fixes.patch --]
[-- Type: text/x-patch, Size: 2775 bytes --]
From bfc1b84d26ca28f78a07d494b0813fe642e80bbe Mon Sep 17 00:00:00 2001
From: Ben Skeggs <bskeggs@redhat.com>
Date: Fri, 27 Jan 2023 15:42:27 +1000
Subject: [PATCH] drm/nouveau/acr/gm20b: regression fixes
Missed some Tegra-specific quirks when reworking ACR to support Ampere.
Fixes: 2541626cfb79 ("drm/nouveau/acr: use common falcon HS FW code for ACR FWs")
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
---
drivers/gpu/drm/nouveau/nvkm/core/firmware.c | 3 +++
drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c | 14 +++++++++++++-
drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c | 2 +-
3 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nvkm/core/firmware.c b/drivers/gpu/drm/nouveau/nvkm/core/firmware.c
index fcf2a002f6cb..91fb494d4009 100644
--- a/drivers/gpu/drm/nouveau/nvkm/core/firmware.c
+++ b/drivers/gpu/drm/nouveau/nvkm/core/firmware.c
@@ -151,6 +151,9 @@ nvkm_firmware_mem_page(struct nvkm_memory *memory)
static enum nvkm_memory_target
nvkm_firmware_mem_target(struct nvkm_memory *memory)
{
+ if (nvkm_firmware_mem(memory)->device->func->tegra)
+ return NVKM_MEM_TARGET_NCOH;
+
return NVKM_MEM_TARGET_HOST;
}
diff --git a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
index 393ade9f7e6c..b7da3ab44c27 100644
--- a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
+++ b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
@@ -48,6 +48,16 @@ gm200_flcn_pio_dmem_rd(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ /* Sigh. Tegra PMU FW's init message... */
+ if (len) {
+ u32 data = nvkm_falcon_rd32(falcon, 0x1c4 + (port * 8));
+
+ while (len--) {
+ *(u8 *)img++ = data & 0xff;
+ data >>= 8;
+ }
+ }
}
static void
@@ -64,6 +74,8 @@ gm200_flcn_pio_dmem_wr(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ WARN_ON(len);
}
static void
@@ -74,7 +86,7 @@ gm200_flcn_pio_dmem_wr_init(struct nvkm_falcon *falcon, u8 port, bool sec, u32 d
const struct nvkm_falcon_func_pio
gm200_flcn_dmem_pio = {
- .min = 4,
+ .min = 1,
.max = 0x100,
.wr_init = gm200_flcn_pio_dmem_wr_init,
.wr = gm200_flcn_pio_dmem_wr,
diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c b/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c
index a72403777329..2ed04da3621d 100644
--- a/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c
+++ b/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c
@@ -225,7 +225,7 @@ gm20b_pmu_init(struct nvkm_pmu *pmu)
pmu->initmsg_received = false;
- nvkm_falcon_load_dmem(falcon, &args, addr_args, sizeof(args), 0);
+ nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args, sizeof(args), 0, false);
nvkm_falcon_start(falcon);
return 0;
}
--
2.35.1
^ permalink raw reply related [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-29 22:36 ` Ben Skeggs
0 siblings, 0 replies; 60+ messages in thread
From: Ben Skeggs @ 2023-01-29 22:36 UTC (permalink / raw)
To: Diogo Ivo; +Cc: regressions, kherbst, kwizart, nouveau, dri-devel, airlied
[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]
On Fri, 27 Jan 2023 at 20:42, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > >
> > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > > As a quick check can you try changing
> > > > > >
> > > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> > >
> > > > In addition to Dave's change, can you try changing the
> > > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > > >
> > > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > > sizeof(args), 0, false);
> > >
> > > Chiming in just to say that with this change I see the same as Nicolas
> > > except that the init message size is 255 instead of 0:
> > >
> > > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> > I've attached an entirely untested patch (to go on top of the other
> > hacks/fixes so far), that will hopefully get us a little further.
>
> Hello,
>
> Thank you for the patch! I can confirm that it fixes the problem
> on the Pixel C, and everything works as before the regression.
> With this, for the combination of patches
>
> Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
>
> which I can resend after testing the final patch version.
Thank you (both!) for testing!
I've attached a "final" version of a patch that I'll send (assuming it
still works ;)) after re-testing. There's only a minor change to
avoid breaking the non-Tegra path, so I expect it should be fine.
Ben.
>
> Thanks,
> Diogo
[-- Attachment #2: 0001-drm-nouveau-acr-gm20b-regression-fixes.patch --]
[-- Type: text/x-patch, Size: 2775 bytes --]
From bfc1b84d26ca28f78a07d494b0813fe642e80bbe Mon Sep 17 00:00:00 2001
From: Ben Skeggs <bskeggs@redhat.com>
Date: Fri, 27 Jan 2023 15:42:27 +1000
Subject: [PATCH] drm/nouveau/acr/gm20b: regression fixes
Missed some Tegra-specific quirks when reworking ACR to support Ampere.
Fixes: 2541626cfb79 ("drm/nouveau/acr: use common falcon HS FW code for ACR FWs")
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
---
drivers/gpu/drm/nouveau/nvkm/core/firmware.c | 3 +++
drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c | 14 +++++++++++++-
drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c | 2 +-
3 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nvkm/core/firmware.c b/drivers/gpu/drm/nouveau/nvkm/core/firmware.c
index fcf2a002f6cb..91fb494d4009 100644
--- a/drivers/gpu/drm/nouveau/nvkm/core/firmware.c
+++ b/drivers/gpu/drm/nouveau/nvkm/core/firmware.c
@@ -151,6 +151,9 @@ nvkm_firmware_mem_page(struct nvkm_memory *memory)
static enum nvkm_memory_target
nvkm_firmware_mem_target(struct nvkm_memory *memory)
{
+ if (nvkm_firmware_mem(memory)->device->func->tegra)
+ return NVKM_MEM_TARGET_NCOH;
+
return NVKM_MEM_TARGET_HOST;
}
diff --git a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
index 393ade9f7e6c..b7da3ab44c27 100644
--- a/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
+++ b/drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c
@@ -48,6 +48,16 @@ gm200_flcn_pio_dmem_rd(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ /* Sigh. Tegra PMU FW's init message... */
+ if (len) {
+ u32 data = nvkm_falcon_rd32(falcon, 0x1c4 + (port * 8));
+
+ while (len--) {
+ *(u8 *)img++ = data & 0xff;
+ data >>= 8;
+ }
+ }
}
static void
@@ -64,6 +74,8 @@ gm200_flcn_pio_dmem_wr(struct nvkm_falcon *falcon, u8 port, const u8 *img, int l
img += 4;
len -= 4;
}
+
+ WARN_ON(len);
}
static void
@@ -74,7 +86,7 @@ gm200_flcn_pio_dmem_wr_init(struct nvkm_falcon *falcon, u8 port, bool sec, u32 d
const struct nvkm_falcon_func_pio
gm200_flcn_dmem_pio = {
- .min = 4,
+ .min = 1,
.max = 0x100,
.wr_init = gm200_flcn_pio_dmem_wr_init,
.wr = gm200_flcn_pio_dmem_wr,
diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c b/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c
index a72403777329..2ed04da3621d 100644
--- a/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c
+++ b/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c
@@ -225,7 +225,7 @@ gm20b_pmu_init(struct nvkm_pmu *pmu)
pmu->initmsg_received = false;
- nvkm_falcon_load_dmem(falcon, &args, addr_args, sizeof(args), 0);
+ nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args, sizeof(args), 0, false);
nvkm_falcon_start(falcon);
return 0;
}
--
2.35.1
^ permalink raw reply related [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-29 22:36 ` [Nouveau] " Ben Skeggs
(?)
@ 2023-01-30 13:54 ` Diogo Ivo
-1 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-30 13:54 UTC (permalink / raw)
To: Ben Skeggs; +Cc: regressions, kherbst, kwizart, nouveau, dri-devel, airlied
On Mon, Jan 30, 2023 at 08:36:06AM +1000, Ben Skeggs wrote:
> On Fri, 27 Jan 2023 at 20:42, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > >
> > > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > > > As a quick check can you try changing
> > > > > > >
> > > > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> > > >
> > > > > In addition to Dave's change, can you try changing the
> > > > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > > > >
> > > > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > > > sizeof(args), 0, false);
> > > >
> > > > Chiming in just to say that with this change I see the same as Nicolas
> > > > except that the init message size is 255 instead of 0:
> > > >
> > > > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> > > I've attached an entirely untested patch (to go on top of the other
> > > hacks/fixes so far), that will hopefully get us a little further.
> >
> > Hello,
> >
> > Thank you for the patch! I can confirm that it fixes the problem
> > on the Pixel C, and everything works as before the regression.
> > With this, for the combination of patches
> >
> > Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
> >
> > which I can resend after testing the final patch version.
> Thank you (both!) for testing!
>
> I've attached a "final" version of a patch that I'll send (assuming it
> still works ;)) after re-testing. There's only a minor change to
> avoid breaking the non-Tegra path, so I expect it should be fine.
Hello!
I have tested this new version and everything is working as before, so
Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Thank you,
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-30 13:54 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-30 13:54 UTC (permalink / raw)
To: Ben Skeggs; +Cc: airlied, nouveau, regressions, dri-devel, kwizart, kherbst
On Mon, Jan 30, 2023 at 08:36:06AM +1000, Ben Skeggs wrote:
> On Fri, 27 Jan 2023 at 20:42, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > >
> > > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > > > As a quick check can you try changing
> > > > > > >
> > > > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> > > >
> > > > > In addition to Dave's change, can you try changing the
> > > > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > > > >
> > > > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > > > sizeof(args), 0, false);
> > > >
> > > > Chiming in just to say that with this change I see the same as Nicolas
> > > > except that the init message size is 255 instead of 0:
> > > >
> > > > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> > > I've attached an entirely untested patch (to go on top of the other
> > > hacks/fixes so far), that will hopefully get us a little further.
> >
> > Hello,
> >
> > Thank you for the patch! I can confirm that it fixes the problem
> > on the Pixel C, and everything works as before the regression.
> > With this, for the combination of patches
> >
> > Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
> >
> > which I can resend after testing the final patch version.
> Thank you (both!) for testing!
>
> I've attached a "final" version of a patch that I'll send (assuming it
> still works ;)) after re-testing. There's only a minor change to
> avoid breaking the non-Tegra path, so I expect it should be fine.
Hello!
I have tested this new version and everything is working as before, so
Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Thank you,
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-30 13:54 ` Diogo Ivo
0 siblings, 0 replies; 60+ messages in thread
From: Diogo Ivo @ 2023-01-30 13:54 UTC (permalink / raw)
To: Ben Skeggs; +Cc: regressions, nouveau, dri-devel, airlied
On Mon, Jan 30, 2023 at 08:36:06AM +1000, Ben Skeggs wrote:
> On Fri, 27 Jan 2023 at 20:42, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > >
> > > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > > > As a quick check can you try changing
> > > > > > >
> > > > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> > > >
> > > > > In addition to Dave's change, can you try changing the
> > > > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > > > >
> > > > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > > > sizeof(args), 0, false);
> > > >
> > > > Chiming in just to say that with this change I see the same as Nicolas
> > > > except that the init message size is 255 instead of 0:
> > > >
> > > > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> > > I've attached an entirely untested patch (to go on top of the other
> > > hacks/fixes so far), that will hopefully get us a little further.
> >
> > Hello,
> >
> > Thank you for the patch! I can confirm that it fixes the problem
> > on the Pixel C, and everything works as before the regression.
> > With this, for the combination of patches
> >
> > Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
> >
> > which I can resend after testing the final patch version.
> Thank you (both!) for testing!
>
> I've attached a "final" version of a patch that I'll send (assuming it
> still works ;)) after re-testing. There's only a minor change to
> avoid breaking the non-Tegra path, so I expect it should be fine.
Hello!
I have tested this new version and everything is working as before, so
Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Thank you,
Diogo
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-29 22:36 ` [Nouveau] " Ben Skeggs
(?)
@ 2023-01-30 16:05 ` Nicolas Chauvet
-1 siblings, 0 replies; 60+ messages in thread
From: Nicolas Chauvet @ 2023-01-30 16:05 UTC (permalink / raw)
To: Ben Skeggs; +Cc: Diogo Ivo, airlied, nouveau, regressions, dri-devel, kherbst
Le dim. 29 janv. 2023 à 23:36, Ben Skeggs <skeggsb@gmail.com> a écrit :
>
> On Fri, 27 Jan 2023 at 20:42, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > >
> > > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > > > As a quick check can you try changing
> > > > > > >
> > > > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> > > >
> > > > > In addition to Dave's change, can you try changing the
> > > > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > > > >
> > > > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > > > sizeof(args), 0, false);
> > > >
> > > > Chiming in just to say that with this change I see the same as Nicolas
> > > > except that the init message size is 255 instead of 0:
> > > >
> > > > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> > > I've attached an entirely untested patch (to go on top of the other
> > > hacks/fixes so far), that will hopefully get us a little further.
> >
> > Hello,
> >
> > Thank you for the patch! I can confirm that it fixes the problem
> > on the Pixel C, and everything works as before the regression.
> > With this, for the combination of patches
> >
> > Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
> >
> > which I can resend after testing the final patch version.
> Thank you (both!) for testing!
>
> I've attached a "final" version of a patch that I'll send (assuming it
> still works ;)) after re-testing. There's only a minor change to
> avoid breaking the non-Tegra path, so I expect it should be fine.
Fine with me.
Tested-By: Nicolas Chauvet <kwizart@gmail.com>
Thanks.
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-30 16:05 ` Nicolas Chauvet
0 siblings, 0 replies; 60+ messages in thread
From: Nicolas Chauvet @ 2023-01-30 16:05 UTC (permalink / raw)
To: Ben Skeggs; +Cc: regressions, nouveau, dri-devel, Diogo Ivo, airlied
Le dim. 29 janv. 2023 à 23:36, Ben Skeggs <skeggsb@gmail.com> a écrit :
>
> On Fri, 27 Jan 2023 at 20:42, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > >
> > > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > > > As a quick check can you try changing
> > > > > > >
> > > > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> > > >
> > > > > In addition to Dave's change, can you try changing the
> > > > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > > > >
> > > > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > > > sizeof(args), 0, false);
> > > >
> > > > Chiming in just to say that with this change I see the same as Nicolas
> > > > except that the init message size is 255 instead of 0:
> > > >
> > > > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> > > I've attached an entirely untested patch (to go on top of the other
> > > hacks/fixes so far), that will hopefully get us a little further.
> >
> > Hello,
> >
> > Thank you for the patch! I can confirm that it fixes the problem
> > on the Pixel C, and everything works as before the regression.
> > With this, for the combination of patches
> >
> > Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
> >
> > which I can resend after testing the final patch version.
> Thank you (both!) for testing!
>
> I've attached a "final" version of a patch that I'll send (assuming it
> still works ;)) after re-testing. There's only a minor change to
> avoid breaking the non-Tegra path, so I expect it should be fine.
Fine with me.
Tested-By: Nicolas Chauvet <kwizart@gmail.com>
Thanks.
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-01-30 16:05 ` Nicolas Chauvet
0 siblings, 0 replies; 60+ messages in thread
From: Nicolas Chauvet @ 2023-01-30 16:05 UTC (permalink / raw)
To: Ben Skeggs; +Cc: regressions, kherbst, nouveau, dri-devel, Diogo Ivo, airlied
Le dim. 29 janv. 2023 à 23:36, Ben Skeggs <skeggsb@gmail.com> a écrit :
>
> On Fri, 27 Jan 2023 at 20:42, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> >
> > On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > >
> > > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > > > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > > > > As a quick check can you try changing
> > > > > > >
> > > > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> > > >
> > > > > In addition to Dave's change, can you try changing the
> > > > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
> > > > >
> > > > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> > > > > sizeof(args), 0, false);
> > > >
> > > > Chiming in just to say that with this change I see the same as Nicolas
> > > > except that the init message size is 255 instead of 0:
> > > >
> > > > [ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
> > > I've attached an entirely untested patch (to go on top of the other
> > > hacks/fixes so far), that will hopefully get us a little further.
> >
> > Hello,
> >
> > Thank you for the patch! I can confirm that it fixes the problem
> > on the Pixel C, and everything works as before the regression.
> > With this, for the combination of patches
> >
> > Tested-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
> >
> > which I can resend after testing the final patch version.
> Thank you (both!) for testing!
>
> I've attached a "final" version of a patch that I'll send (assuming it
> still works ;)) after re-testing. There's only a minor change to
> avoid breaking the non-Tegra path, so I expect it should be fine.
Fine with me.
Tested-By: Nicolas Chauvet <kwizart@gmail.com>
Thanks.
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
2023-01-05 12:28 ` Thorsten Leemhuis
(?)
@ 2023-02-03 9:13 ` Linux kernel regression tracking (#update)
-1 siblings, 0 replies; 60+ messages in thread
From: Linux kernel regression tracking (#update) @ 2023-02-03 9:13 UTC (permalink / raw)
To: bskeggs, Karol Herbst, Lyude Paul
Cc: regressions, dri-devel, nouveau, airlied, Diogo Ivo
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 05.01.23 13:28, Thorsten Leemhuis wrote:
> On 28.12.22 15:49, Diogo Ivo wrote:
>> Hello,
>>
>> Commit 2541626cfb79 breaks GM20B probe with
>> the following kernel log:
> Just wondering: is anyone looking on this? The report was posted more
> than a week ago and didn't even get a single reply yet afaics. This of
> course can happen at this time of the year, but I nevertheless thought a
> quick status inquiry might be a good idea at this point.
#regzbot fix: drm/nouveau/acr/gm20b: regression fixes
#regzbot ignore-activity
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
That page also explains what to do if mails like this annoy you.
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-02-03 9:13 ` Linux kernel regression tracking (#update)
0 siblings, 0 replies; 60+ messages in thread
From: Linux kernel regression tracking (#update) @ 2023-02-03 9:13 UTC (permalink / raw)
To: bskeggs, Karol Herbst, Lyude Paul
Cc: nouveau, Diogo Ivo, regressions, dri-devel, airlied
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 05.01.23 13:28, Thorsten Leemhuis wrote:
> On 28.12.22 15:49, Diogo Ivo wrote:
>> Hello,
>>
>> Commit 2541626cfb79 breaks GM20B probe with
>> the following kernel log:
> Just wondering: is anyone looking on this? The report was posted more
> than a week ago and didn't even get a single reply yet afaics. This of
> course can happen at this time of the year, but I nevertheless thought a
> quick status inquiry might be a good idea at this point.
#regzbot fix: drm/nouveau/acr/gm20b: regression fixes
#regzbot ignore-activity
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
That page also explains what to do if mails like this annoy you.
^ permalink raw reply [flat|nested] 60+ messages in thread
* Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
@ 2023-02-03 9:13 ` Linux kernel regression tracking (#update)
0 siblings, 0 replies; 60+ messages in thread
From: Linux kernel regression tracking (#update) @ 2023-02-03 9:13 UTC (permalink / raw)
To: bskeggs, Karol Herbst, Lyude Paul
Cc: nouveau, Diogo Ivo, regressions, dri-devel, airlied
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 05.01.23 13:28, Thorsten Leemhuis wrote:
> On 28.12.22 15:49, Diogo Ivo wrote:
>> Hello,
>>
>> Commit 2541626cfb79 breaks GM20B probe with
>> the following kernel log:
> Just wondering: is anyone looking on this? The report was posted more
> than a week ago and didn't even get a single reply yet afaics. This of
> course can happen at this time of the year, but I nevertheless thought a
> quick status inquiry might be a good idea at this point.
#regzbot fix: drm/nouveau/acr/gm20b: regression fixes
#regzbot ignore-activity
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
That page also explains what to do if mails like this annoy you.
^ permalink raw reply [flat|nested] 60+ messages in thread
end of thread, other threads:[~2023-05-04 12:34 UTC | newest]
Thread overview: 60+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-28 14:49 [REGRESSION] GM20B probe fails after commit 2541626cfb79 Diogo Ivo
2022-12-28 14:49 ` [Nouveau] " Diogo Ivo
2022-12-28 14:49 ` Diogo Ivo
2023-01-05 12:28 ` Thorsten Leemhuis
2023-01-05 12:28 ` [Nouveau] " Thorsten Leemhuis
2023-01-05 12:28 ` Thorsten Leemhuis
2023-01-13 13:19 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-13 13:19 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-13 13:19 ` [Nouveau] " Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-14 3:27 ` Karol Herbst
2023-01-14 3:27 ` Karol Herbst
2023-01-14 3:27 ` Karol Herbst
2023-01-14 16:03 ` Diogo Ivo
2023-01-14 16:03 ` [Nouveau] " Diogo Ivo
2023-01-14 16:03 ` Diogo Ivo
2023-01-14 18:56 ` Karol Herbst
2023-01-14 18:56 ` Karol Herbst
2023-01-14 18:56 ` [Nouveau] " Karol Herbst
2023-01-14 15:58 ` Diogo Ivo
2023-01-14 15:58 ` [Nouveau] " Diogo Ivo
2023-01-14 15:58 ` Diogo Ivo
2023-02-03 9:13 ` Linux kernel regression tracking (#update)
2023-02-03 9:13 ` Linux kernel regression tracking (#update)
2023-02-03 9:13 ` [Nouveau] " Linux kernel regression tracking (#update)
2023-01-15 21:45 ` David Airlie
2023-01-15 21:45 ` David Airlie
2023-01-15 21:45 ` [Nouveau] " David Airlie
2023-01-16 12:24 ` Diogo Ivo
2023-01-16 12:24 ` [Nouveau] " Diogo Ivo
2023-01-16 12:24 ` Diogo Ivo
2023-01-18 1:28 ` [Nouveau] " Ben Skeggs
2023-01-18 1:28 ` Ben Skeggs
2023-01-18 1:28 ` Ben Skeggs
2023-01-18 8:42 ` [Nouveau] " Nicolas Chauvet
2023-01-18 8:42 ` Nicolas Chauvet
2023-01-20 11:34 ` Diogo Ivo
2023-01-20 11:34 ` [Nouveau] " Diogo Ivo
2023-01-20 11:34 ` Diogo Ivo
2023-01-27 6:00 ` Ben Skeggs
2023-01-27 6:00 ` Ben Skeggs
2023-01-27 6:00 ` [Nouveau] " Ben Skeggs
2023-01-27 9:03 ` Nicolas Chauvet
2023-01-27 9:03 ` Nicolas Chauvet
2023-01-27 9:03 ` [Nouveau] " Nicolas Chauvet
2023-01-27 10:48 ` Diogo Ivo
2023-01-27 10:48 ` [Nouveau] " Diogo Ivo
2023-01-27 10:39 ` Diogo Ivo
2023-01-27 10:39 ` [Nouveau] " Diogo Ivo
2023-01-27 10:39 ` Diogo Ivo
2023-01-29 22:36 ` Ben Skeggs
2023-01-29 22:36 ` Ben Skeggs
2023-01-29 22:36 ` [Nouveau] " Ben Skeggs
2023-01-30 13:54 ` Diogo Ivo
2023-01-30 13:54 ` [Nouveau] " Diogo Ivo
2023-01-30 13:54 ` Diogo Ivo
2023-01-30 16:05 ` Nicolas Chauvet
2023-01-30 16:05 ` Nicolas Chauvet
2023-01-30 16:05 ` [Nouveau] " Nicolas Chauvet
2023-01-17 15:55 ` Nicolas Chauvet
2023-01-17 15:55 ` Nicolas Chauvet
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.