Bug 108658

Summary: gt215 scheduling while atomic warning
Product: xorg Reporter: Ard Biesheuvel <ard.biesheuvel>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: medium    
Version: git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Ard Biesheuvel 2018-11-05 11:51:08 UTC
Booting v4.20-rc1 on a arm64 with a Geforce 210 card inserted produces the following splat:

nouveau 0000:02:00.0: NVIDIA GT218 (0a8280b1)
hub 2-0:1.0: 4 ports detected
nouveau 0000:02:00.0: bios: version 70.18.8a.00.06
nouveau 0000:02:00.0: fb: 1024 MiB DDR3
BUG: scheduling while atomic: kworker/0:1/12/0x00000002
Modules linked in: hid_apple hid_generic usbhid hid sd_mod nouveau(+) xhci_pci i2c_algo_bit xhci_hcd ttm ahci_platform libahci_platform drm_kms_helper libahci libata drm usbcore amd_xgbe scsi_mod libphy
CPU: 0 PID: 12 Comm: kworker/0:1 Not tainted 4.20.0-rc1+ #5
Hardware name: AMD Seattle/Seattle, BIOS 20:07:19 Oct  2 2018
Workqueue: events nvkm_pstate_work [nouveau]
Call trace:
 dump_backtrace+0x0/0x1d0
 show_stack+0x24/0x30
 dump_stack+0x98/0xbc
 __schedule_bug+0x64/0x80
 __schedule+0x818/0x9b8
 schedule+0x40/0xa8
 gt215_pmu_send+0x274/0x2a8 [nouveau]
 nvkm_pmu_send+0x60/0x80 [nouveau]
 nvkm_memx_init+0x5c/0x120 [nouveau]
 gt215_ram_calc+0x12f8/0x4d58 [nouveau]
 gt215_ram_calc+0x2a0/0x4d58 [nouveau]
 nvkm_pstate_work+0x18c/0x6b0 [nouveau]
 process_one_work+0x1a8/0x438
 worker_thread+0x54/0x3f8
 kthread+0x104/0x130
 ret_from_fork+0x10/0x18
[TTM] Zone  kernel: Available graphics memory: 16460910 kiB
[TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[TTM] Initializing pool allocator
[TTM] Initializing DMA pool allocator
nouveau 0000:02:00.0: DRM: VRAM: 1024 MiB
nouveau 0000:02:00.0: DRM: GART: 1048576 MiB
nouveau 0000:02:00.0: DRM: TMDS table version 2.0
nouveau 0000:02:00.0: DRM: DCB version 4.0
nouveau 0000:02:00.0: DRM: DCB outp 00: 02000300 00000000
nouveau 0000:02:00.0: DRM: DCB outp 01: 01000302 00020030
nouveau 0000:02:00.0: DRM: DCB outp 02: 02021362 00020010
nouveau 0000:02:00.0: DRM: DCB outp 04: 01032310 00000000
nouveau 0000:02:00.0: DRM: DCB conn 00: 00001030
nouveau 0000:02:00.0: DRM: DCB conn 01: 00002161
nouveau 0000:02:00.0: DRM: DCB conn 02: 00000200
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
BUG: scheduling while atomic: kworker/0:1/12/0x00000000
Modules linked in: hid_apple hid_generic usbhid hid sd_mod nouveau(+) xhci_pci i2c_algo_bit xhci_hcd ttm ahci_platform libahci_platform drm_kms_helper libahci libata drm usbcore amd_xgbe scsi_mod libphy
CPU: 0 PID: 12 Comm: kworker/0:1 Tainted: G        W         4.20.0-rc1+ #5
Hardware name: AMD Seattle/Seattle, BIOS 20:07:19 Oct  2 2018
Workqueue: events nvkm_pstate_work [nouveau]
Call trace:
 dump_backtrace+0x0/0x1d0
 show_stack+0x24/0x30
 dump_stack+0x98/0xbc
 __schedule_bug+0x64/0x80
 __schedule+0x818/0x9b8
 schedule+0x40/0xa8
 gt215_pmu_send+0x274/0x2a8 [nouveau]
 nvkm_pmu_send+0x60/0x80 [nouveau]
 nvkm_memx_train_result+0x5c/0xe8 [nouveau]
 gt215_ram_calc+0xbd8/0x4d58 [nouveau]
 nvkm_pstate_work+0x18c/0x6b0 [nouveau]
 process_one_work+0x1a8/0x438
 worker_thread+0x54/0x3f8
 kthread+0x104/0x130
 ret_from_fork+0x10/0x18
nouveau 0000:02:00.0: DRM: MM: using COPY for buffer copies
nouveau 0000:02:00.0: DRM: allocated 1920x1200 fb: 0x70000, bo (____ptrval____)
Console: switching to colour frame buffer device 240x75
nouveau 0000:02:00.0: fb0: nouveaufb frame buffer device
Comment 1 Martin Peres 2019-12-04 09:46:44 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/465.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.