dri-devel December 2020

dri-devel@lists.freedesktop.org

278 participants
659 discussions

[Bug 209457] New: AMDGPU resume fail with RX 580 GPU
by bugzilla-daemon＠bugzilla.kernel.org 15 Jul '21

15 Jul '21

https://bugzilla.kernel.org/show_bug.cgi?id=209457 Bug ID: 209457 Summary: AMDGPU resume fail with RX 580 GPU Product: Drivers Version: 2.5 Kernel Version: 5.8.12 to 5.9-rc6 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: rmuncrief(a)humanavance.com Regression: No Created attachment 292739 --> https://bugzilla.kernel.org/attachment.cgi?id=292739&action=edit dmesg resume fail output with kernel 5.9.0-rc6 I've been having random resume problems from around kernel 5.5, and it persists even up to 5.9-rc6. When this occurs I can still login to SSH and give a reboot command, but though SSH disconnects my computer doesn't reboot and I have to press the reset button. I have an ASUS Gaming TUF X570 motherboard, R7 3700X CPU, RX 580 GPU, and 16GB of RAM. The primary error recorded over and over in dmesg is: [xxxxx.xxxxxx] amdgpu: failed to send message 201 ret is 65535 [xxxxx.xxxxxx] amdgpu: last message was failed ret is 65535 I've included the part of dmesg beginning with suspend event through the resume failure for kernel 5.9-rc6. -- You are receiving this mail because: You are watching the assignee of the bug.

1 40

[Bug 207383] New: [Regression] 5.7-rc: amdgpu/polaris11 gpf: amdgpu_atomic_commit_tail
by bugzilla-daemon＠bugzilla.kernel.org 06 Jul '21

06 Jul '21

https://bugzilla.kernel.org/show_bug.cgi?id=207383 Bug ID: 207383 Summary: [Regression] 5.7-rc: amdgpu/polaris11 gpf: amdgpu_atomic_commit_tail Product: Drivers Version: 2.5 Kernel Version: 5.7-rc1, 5.7-rc2 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: 1i5t5.duncan(a)cox.net Regression: No Created attachment 288649 --> https://bugzilla.kernel.org/attachment.cgi?id=288649&action=edit kernel config 5.7-rc1 and rc2 regression from kernel 5.6.0 After starting X/plasma on 5.7-rc1 and rc2, system runs for a few seconds to a few hours, then display freezes. The pointer continues to be movable and audio will continue to play for some seconds but they eventually stop as well. The kernel remains alive at least enough to reboot with SRQ-b, not sure if previous SRQs have any effect or not. Sometimes but not always there's a gpf left in the log, appearing to confirm it's amdgpu (the -dirty is simply a patch making mounts noatime by default): Apr 20 03:25:55 h2 kernel: general protection fault, probably for non-canonical address 0xc1316515e40a92f6: 0000 [#1] SMP Apr 20 03:25:55 h2 kernel: CPU: 3 PID: 3921 Comm: kworker/u16:5 Tainted: G T 5.7.0-rc2-dirty #194 Apr 20 03:25:55 h2 kernel: Hardware name: Gigabyte Technology Co., Ltd. GA-990FXA-UD3/GA-990FXA-UD3, BIOS F6 03/30/2012 Apr 20 03:25:55 h2 kernel: Workqueue: events_unbound commit_work Apr 20 03:25:55 h2 kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x102d/0x1fd8 Apr 20 03:25:55 h2 kernel: Code: 48 89 9d a0 fc ff ff 8b 90 e0 02 00 00 85 d2 0f 85 26 f1 ff ff 48 8b 85 e0 fc ff ff 48 89 85 a0 fc ff ff 48 8b b5 e0 fc ff ff <80> be b0 01 00 00 01 0f 86 b4 00 00 00 31 c0 48 b9 00 00 00 00 01 Apr 20 03:25:55 h2 kernel: RSP: 0018:ffffc9000216bad0 EFLAGS: 00010286 Apr 20 03:25:55 h2 kernel: RAX: ffff88842a6e1000 RBX: ffff8883d1d5b800 RCX: ffff8884283db200 Apr 20 03:25:55 h2 kernel: RDX: ffff8884283db2e0 RSI: c1316515e40a92f6 RDI: 0000000000000002 Apr 20 03:25:55 h2 kernel: RBP: ffffc9000216be50 R08: 0000000000000001 R09: 0000000000000001 Apr 20 03:25:55 h2 kernel: R10: 0000000000030000 R11: 0000000000000000 R12: 0000000000000000 Apr 20 03:25:55 h2 kernel: R13: 0000000000000005 R14: ffff88842bb76000 R15: ffff88841c08cc00 Apr 20 03:25:55 h2 kernel: FS: 0000000000000000(0000) GS:ffff88842ecc0000(0000) knlGS:0000000000000000 Apr 20 03:25:55 h2 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 20 03:25:55 h2 kernel: CR2: 000078617de4fffc CR3: 000000040ca0e000 CR4: 00000000000406e0 Apr 20 03:25:55 h2 kernel: Call Trace: Apr 20 03:25:55 h2 kernel: ? 0xffffffff81000000 Apr 20 03:25:55 h2 kernel: ? __switch_to_asm+0x34/0x70 Apr 20 03:25:55 h2 kernel: ? __switch_to_asm+0x40/0x70 Apr 20 03:25:55 h2 kernel: ? __switch_to_asm+0x34/0x70 Apr 20 03:25:55 h2 kernel: ? __switch_to_asm+0x40/0x70 Apr 20 03:25:55 h2 kernel: ? commit_tail+0x8e/0x120 Apr 20 03:25:55 h2 kernel: ? process_one_work+0x1a9/0x300 Apr 20 03:25:55 h2 kernel: ? worker_thread+0x45/0x3b8 Apr 20 03:25:55 h2 kernel: ? kthread+0xf3/0x130 Apr 20 03:25:55 h2 kernel: ? process_one_work+0x300/0x300 Apr 20 03:25:55 h2 kernel: ? __kthread_create_on_node+0x180/0x180 Apr 20 03:25:55 h2 kernel: ? ret_from_fork+0x22/0x40 Apr 20 03:25:55 h2 kernel: ---[ end trace 33869116def8e8ad ]--- Apr 20 03:25:55 h2 kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x102d/0x1fd8 Apr 20 03:25:55 h2 kernel: Code: 48 89 9d a0 fc ff ff 8b 90 e0 02 00 00 85 d2 0f 85 26 f1 ff ff 48 8b 85 e0 fc ff ff 48 89 85 a0 fc ff ff 48 89 85 a0 fc ff ff 48 8b b5 e0 fc ff ff <80> be b0 01 00 00 01 0f 86 b4 00 00 00 31 c0 48 b9 00 00 00 00 01 Apr 20 03:25:55 h2 kernel: RSP: 0018:ffffc9000216bad0 EFLAGS: 00010286 Apr 20 03:25:55 h2 kernel: RAX: ffff88842a6e1000 RBX: ffff8883d1d5b800 RCX: ffff8884283db200 Apr 20 03:25:55 h2 kernel: RDX: ffff8884283db2e0 RSI: c1316515e40a92f6 RDI: 0000000000000002 Apr 20 03:25:55 h2 kernel: RBP: ffffc9000216be50 R08: 0000000000000001 R09: 0000000000000001 Apr 20 03:25:55 h2 kernel: R10: 0000000000030000 R11: 0000000000000000 R12: 0000000000000000 Apr 20 03:25:55 h2 kernel: R13: 0000000000000005 R14: ffff88842bb76000 R15: ffff88841c08cc00 Apr 20 03:25:55 h2 kernel: FS: 0000000000000000(0000) GS:ffff88842ecc0000(0000) knlGS:0000000000000000 Apr 20 03:25:55 h2 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 20 03:25:55 h2 kernel: CR2: 000078617de4fffc CR3: 000000040ca0e000 CR4: 00000000000406e0 That's it. Nothing in the log since boot before, and the next entry is after reboot. gcc version 9.3.0 on Gentoo. AMD fx6100 on the Gigabyte board in the log above. xorg-server 1.20.8, mesa 20.0.4, xf86-video-amdgpu 19.1.0, linux-firmware 20200413 kernel config attached -- You are receiving this mail because: You are watching the assignee of the bug.

1 121

[PATCH] drm/vc4: dsi: Only register our component once a DSI device is attached
by Maxime Ripard 05 Jul '21

05 Jul '21

If the DSI driver is the last to probe, component_add will try to run all the bind callbacks straight away and return the error code. However, since we depend on a power domain, we're pretty much guaranteed to be in that case on the BCM2711, and are just lucky on the previous SoCs since the v3d also depends on that power domain and is further in the probe order. In that case, the DSI host will not stick around in the system: the DSI bind callback will be executed, will not find any DSI device attached and will return EPROBE_DEFER, and we will then remove the DSI host and ask to be probed later on. But since that host doesn't stick around, DSI devices like the RaspberryPi touchscreen whose probe is not linked to the DSI host (unlike the usual DSI devices that will be probed through the call to mipi_dsi_host_register) cannot attach to the DSI host, and we thus end up in a situation where the DSI host cannot probe because the panel hasn't probed yet, and the panel cannot probe because the DSI host hasn't yet. In order to break this cycle, let's wait until there's a DSI device that attaches to the DSI host to register the component and allow to progress further. Suggested-by: Andrzej Hajda <a.hajda(a)samsung.com> Signed-off-by: Maxime Ripard <maxime(a)cerno.tech> --- drivers/gpu/drm/vc4/vc4_dsi.c | 25 ++++++++----------------- 1 file changed, 8 insertions(+), 17 deletions(-) diff --git a/drivers/gpu/drm/vc4/vc4_dsi.c b/drivers/gpu/drm/vc4/vc4_dsi.c index eaf276978ee7..19aab4e7e209 100644 --- a/drivers/gpu/drm/vc4/vc4_dsi.c +++ b/drivers/gpu/drm/vc4/vc4_dsi.c @@ -1246,10 +1246,12 @@ static ssize_t vc4_dsi_host_transfer(struct mipi_dsi_host *host, return ret; } +static const struct component_ops vc4_dsi_ops; static int vc4_dsi_host_attach(struct mipi_dsi_host *host, struct mipi_dsi_device *device) { struct vc4_dsi *dsi = host_to_dsi(host); + int ret; dsi->lanes = device->lanes; dsi->channel = device->channel; @@ -1284,6 +1286,12 @@ static int vc4_dsi_host_attach(struct mipi_dsi_host *host, return 0; } + ret = component_add(&dsi->pdev->dev, &vc4_dsi_ops); + if (ret) { + mipi_dsi_host_unregister(&dsi->dsi_host); + return ret; + } + return 0; } @@ -1662,7 +1670,6 @@ static int vc4_dsi_dev_probe(struct platform_device *pdev) { struct device *dev = &pdev->dev; struct vc4_dsi *dsi; - int ret; dsi = devm_kzalloc(dev, sizeof(*dsi), GFP_KERNEL); if (!dsi) @@ -1670,26 +1677,10 @@ static int vc4_dsi_dev_probe(struct platform_device *pdev) dev_set_drvdata(dev, dsi); dsi->pdev = pdev; - - /* Note, the initialization sequence for DSI and panels is - * tricky. The component bind above won't get past its - * -EPROBE_DEFER until the panel/bridge probes. The - * panel/bridge will return -EPROBE_DEFER until it has a - * mipi_dsi_host to register its device to. So, we register - * the host during pdev probe time, so vc4 as a whole can then - * -EPROBE_DEFER its component bind process until the panel - * successfully attaches. - */ dsi->dsi_host.ops = &vc4_dsi_host_ops; dsi->dsi_host.dev = dev; mipi_dsi_host_register(&dsi->dsi_host); - ret = component_add(&pdev->dev, &vc4_dsi_ops); - if (ret) { - mipi_dsi_host_unregister(&dsi->dsi_host); - return ret; - } - return 0; } -- 2.26.2

5 21

[Bug 210005] New: Kernel stacktrace, Xorg freezes
by bugzilla-daemon＠bugzilla.kernel.org 22 Jun '21

22 Jun '21

https://bugzilla.kernel.org/show_bug.cgi?id=210005 Bug ID: 210005 Summary: Kernel stacktrace, Xorg freezes Product: Drivers Version: 2.5 Kernel Version: 5.8.0-26-generic Hardware: Intel OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: amarandi(a)dshort.biz Regression: No Created attachment 293391 --> https://bugzilla.kernel.org/attachment.cgi?id=293391&action=edit syslog Hello guys, this is my first kernel bug report, so I hope I am doing it right. One line summary of the problem: At any unspecific point my whole system freezes and I cant recover it without an RESIUB / hard restart. Full description of the problem/report: This does not happen before I upgraded to Ubuntu 20.10. Before i had Ubuntu 20.04 (linux-image-5.4.0-52-generic) Distribution specific informations: Ubuntu 20.10 Kernel version: Linux version 5.8.0-26-generic (buildd@lcy01-amd64-025) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #27-Ubuntu SMP Wed Oct 21 22:29:16 UTC 2020 Hardware: Dell XPS 15 9560 Syslog message / kernel log in attachments. If you need additional informations please ask and I will provide them. Thank you! :) -- You are receiving this mail because: You are watching the assignee of the bug.

1 2

[PATCH] intel: Do not assert on unknown chips in drm_intel_decode_context_alloc
by Tvrtko Ursulin 17 Jun '21

17 Jun '21

From: Tvrtko Ursulin <tvrtko.ursulin(a)intel.com> There is this long standing nit of igt/tools/intel_error_decode asserting when you feed it an error state from a GPU the local libdrm does not know of. To fix this I need a tweak in drm_intel_decode_context_alloc to make it not assert but just return NULL (which seems an already possible return value). Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin(a)intel.com> --- intel/intel_decode.c | 39 +++++++++++++++++++++------------------ 1 file changed, 21 insertions(+), 18 deletions(-) diff --git a/intel/intel_decode.c b/intel/intel_decode.c index e0a516644314..be6f77984d65 100644 --- a/intel/intel_decode.c +++ b/intel/intel_decode.c @@ -3815,32 +3815,35 @@ drm_public struct drm_intel_decode * drm_intel_decode_context_alloc(uint32_t devid) { struct drm_intel_decode *ctx; + int gen = 0; - ctx = calloc(1, sizeof(struct drm_intel_decode)); - if (!ctx) - return NULL; - - ctx->devid = devid; - ctx->out = stdout; - - if (intel_get_genx(devid, &ctx->gen)) + if (intel_get_genx(devid, &gen)) ; else if (IS_GEN8(devid)) - ctx->gen = 8; + gen = 8; else if (IS_GEN7(devid)) - ctx->gen = 7; + gen = 7; else if (IS_GEN6(devid)) - ctx->gen = 6; + gen = 6; else if (IS_GEN5(devid)) - ctx->gen = 5; + gen = 5; else if (IS_GEN4(devid)) - ctx->gen = 4; + gen = 4; else if (IS_9XX(devid)) - ctx->gen = 3; - else { - assert(IS_GEN2(devid)); - ctx->gen = 2; - } + gen = 3; + else if (IS_GEN2(devid)) + gen = 2; + + if (!gen) + return NULL; + + ctx = calloc(1, sizeof(struct drm_intel_decode)); + if (!ctx) + return NULL; + + ctx->devid = devid; + ctx->gen = gen; + ctx->out = stdout; return ctx; } -- 2.25.1

2 5

[Bug 205517] New: nouveau MMIO read of 00000000 FAULT at 619444
by bugzilla-daemon＠bugzilla.kernel.org 16 Jun '21

16 Jun '21

https://bugzilla.kernel.org/show_bug.cgi?id=205517 Bug ID: 205517 Summary: nouveau MMIO read of 00000000 FAULT at 619444 Product: Drivers Version: 2.5 Kernel Version: 5.3.0 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: todd.e.brandt(a)linux.intel.com Regression: No Created attachment 285893 --> https://bugzilla.kernel.org/attachment.cgi?id=285893&action=edit issue.def NVidia GPU driver fault on Dell systems during resume. [33133.398092] nouveau 0000:01:00.0: calling nv_msi_ht_cap_quirk_leaf+0x0/0x30 @ 27 [33133.398102] nouveau 0000:01:00.0: nv_msi_ht_cap_quirk_leaf+0x0/0x30 took 5 usecs [33133.398104] nouveau 0000:01:00.0: calling quirk_nvidia_hda+0x0/0xc0 @ 27 [33133.398107] nouveau 0000:01:00.0: Enabling HDA controller [33133.398110] nouveau 0000:01:00.0: quirk_nvidia_hda+0x0/0xc0 took 3 usecs [33133.399220] done. [33133.540201] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ] [33133.556094] PM: suspend exit -- You are receiving this mail because: You are watching the assignee of the bug.

1 3

[PATCH] drm/rockchip: cdn-dp: fix sign extension on an int multiply for a u64 result
by Colin King 28 May '21

28 May '21

From: Colin Ian King <colin.king(a)canonical.com> The variable bit_per_pix is a u8 and is promoted in the multiplication to an int type and then sign extended to a u64. If the result of the int multiplication is greater than 0x7fffffff then the upper 32 bits will be set to 1 as a result of the sign extension. Avoid this by casting tu_size_reg to u64 to avoid sign extension and also a potential overflow. Addresses-Coverity: ("Unintended sign extension") Fixes: 1a0f7ed3abe2 ("drm/rockchip: cdn-dp: add cdn DP support for rk3399") Signed-off-by: Colin Ian King <colin.king(a)canonical.com> --- drivers/gpu/drm/rockchip/cdn-dp-reg.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/rockchip/cdn-dp-reg.c b/drivers/gpu/drm/rockchip/cdn-dp-reg.c index 9d2163ef4d6e..33fb4d05c506 100644 --- a/drivers/gpu/drm/rockchip/cdn-dp-reg.c +++ b/drivers/gpu/drm/rockchip/cdn-dp-reg.c @@ -658,7 +658,7 @@ int cdn_dp_config_video(struct cdn_dp_device *dp) */ do { tu_size_reg += 2; - symbol = tu_size_reg * mode->clock * bit_per_pix; + symbol = (u64)tu_size_reg * mode->clock * bit_per_pix; do_div(symbol, dp->max_lanes * link_rate * 8); rem = do_div(symbol, 1000); if (tu_size_reg > 64) { -- 2.27.0

3 2

[Bug 208573] New: Black screen on boot if two displays plugged in with NAVI 10
by bugzilla-daemon＠bugzilla.kernel.org 24 May '21

24 May '21

https://bugzilla.kernel.org/show_bug.cgi?id=208573 Bug ID: 208573 Summary: Black screen on boot if two displays plugged in with NAVI 10 Product: Drivers Version: 2.5 Kernel Version: 5.7.8-6-MANJARO Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: thomas.langkamp(a)medicalschool-hamburg.de Regression: No With Radeon R9 Fury X and 2 4k displays @60hz, one LG TV@HDMI, one iiyama@DP => everything fine With new Radeon 5700 from Asus => black screen after grub menu and after some time the gpu-fans spin up a bit and the mainboard debug LED starts flashing. Then reset-button is the only option. With new Radeon 5700 XT from Gigabyte => same So I can already rule out a hardware fault. What helps: - Starting a recovery boot entry in grub - OR disconecting one display before reboot Both 5700 cards work always fine with only one display connected. If I connect the second display later, when I am already on desktop environment - also everything works. Other things I tried - changing to 30 hz then reboot - kernels from 5.4 onwards - different ports on the gpu - DP to HDMI-adapter sudo dmesg | grep amdgpu [sudo] Passwort für tom: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.7-x86_64 root=UUID=74886ca0-4a71-4692-aa0c-b2a539ec6b48 rw quiet loglevel=3 rd.systemd.show_status=auto rd.udev.log_priority=3 amdgpu.ppfeaturemask=0xfffd7fff resume=LABEL=swap libahci.ignore_sss=1 [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.7-x86_64 root=UUID=74886ca0-4a71-4692-aa0c-b2a539ec6b48 rw quiet loglevel=3 rd.systemd.show_status=auto rd.udev.log_priority=3 amdgpu.ppfeaturemask=0xfffd7fff resume=LABEL=swap libahci.ignore_sss=1 [ 2.597324] [drm] amdgpu kernel modesetting enabled. [ 2.597526] fb0: switching to amdgpudrmfb from EFI VGA [ 2.597631] amdgpu 0000:0d:00.0: vgaarb: deactivate vga console [ 2.597664] amdgpu 0000:0d:00.0: enabling device (0006 -> 0007) [ 2.615476] amdgpu 0000:0d:00.0: VRAM: 8176M 0x0000008000000000 - 0x00000081FEFFFFFF (8176M used) [ 2.615477] amdgpu 0000:0d:00.0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF [ 2.615580] [drm] amdgpu: 8176M of VRAM memory ready [ 2.615583] [drm] amdgpu: 8176M of GTT memory ready. [ 3.433349] amdgpu 0000:0d:00.0: RAS: optional ras ta ucode is not available [ 3.528083] snd_hda_intel 0000:0d:00.1: bound 0000:0d:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [ 3.628396] fbcon: amdgpudrmfb (fb0) is primary device [ 3.739398] amdgpu 0000:0d:00.0: fb0: amdgpudrmfb frame buffer device [ 3.783482] amdgpu 0000:0d:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 3.783485] amdgpu 0000:0d:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 3.783487] amdgpu 0000:0d:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 3.783489] amdgpu 0000:0d:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 3.783491] amdgpu 0000:0d:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 3.783492] amdgpu 0000:0d:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 3.783494] amdgpu 0000:0d:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 3.783496] amdgpu 0000:0d:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 3.783498] amdgpu 0000:0d:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 3.783499] amdgpu 0000:0d:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 3.783501] amdgpu 0000:0d:00.0: ring sdma0 uses VM inv eng 12 on hub 0 [ 3.783503] amdgpu 0000:0d:00.0: ring sdma1 uses VM inv eng 13 on hub 0 [ 3.783505] amdgpu 0000:0d:00.0: ring vcn_dec uses VM inv eng 0 on hub 1 [ 3.783506] amdgpu 0000:0d:00.0: ring vcn_enc0 uses VM inv eng 1 on hub 1 [ 3.783508] amdgpu 0000:0d:00.0: ring vcn_enc1 uses VM inv eng 4 on hub 1 [ 3.783510] amdgpu 0000:0d:00.0: ring jpeg_dec uses VM inv eng 5 on hub 1 [ 3.784426] [drm] Initialized amdgpu 3.37.0 20150101 for 0000:0d:00.0 on minor 0 [ 2050.217010] amdgpu 0000:0d:00.0: RAS: optional ras ta ucode is not available [ 2050.416499] [drm:dpcd_set_source_specific_data [amdgpu]] *ERROR* Error in DP aux read transaction, not writing source specific data [ 2050.925049] [drm:retrieve_link_cap [amdgpu]] *ERROR* retrieve_link_cap: Read dpcd data failed. [ 2050.934845] amdgpu 0000:0d:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 2050.934846] amdgpu 0000:0d:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 2050.934846] amdgpu 0000:0d:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 2050.934847] amdgpu 0000:0d:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 2050.934847] amdgpu 0000:0d:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 2050.934848] amdgpu 0000:0d:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 2050.934849] amdgpu 0000:0d:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 2050.934849] amdgpu 0000:0d:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 2050.934850] amdgpu 0000:0d:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 2050.934850] amdgpu 0000:0d:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 2050.934851] amdgpu 0000:0d:00.0: ring sdma0 uses VM inv eng 12 on hub 0 [ 2050.934851] amdgpu 0000:0d:00.0: ring sdma1 uses VM inv eng 13 on hub 0 [ 2050.934852] amdgpu 0000:0d:00.0: ring vcn_dec uses VM inv eng 0 on hub 1 [ 2050.934852] amdgpu 0000:0d:00.0: ring vcn_enc0 uses VM inv eng 1 on hub 1 [ 2050.934853] amdgpu 0000:0d:00.0: ring vcn_enc1 uses VM inv eng 4 on hub 1 [ 2050.934853] amdgpu 0000:0d:00.0: ring jpeg_dec uses VM inv eng 5 on hub 1 lspci -v 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex Subsystem: ASRock Incorporation Device 1450 Flags: fast devsel 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge Flags: fast devsel 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 25 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fcf00000-fcffffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 26 Bus: primary=00, secondary=02, subordinate=0a, sec-latency=0 I/O behind bridge: 0000f000-0000ffff [size=4K] Memory behind bridge: fcc00000-fcdfffff [size=2M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge Flags: fast devsel 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge Flags: fast devsel 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 27 Bus: primary=00, secondary=0b, subordinate=0d, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: fca00000-fcbfffff [size=2M] Prefetchable memory behind bridge: 00000000e0000000-00000000f01fffff [size=258M] Capabilities: <access denied> Kernel driver in use: pcieport 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge Flags: fast devsel 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge Flags: fast devsel 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 28 Bus: primary=00, secondary=0e, subordinate=0e, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fc700000-fc9fffff [size=3M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge Flags: fast devsel 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 30 Bus: primary=00, secondary=0f, subordinate=0f, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fce00000-fcefffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) Subsystem: ASRock Incorporation Device 790b Flags: 66MHz, medium devsel Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) Subsystem: ASRock Incorporation Device 790e Flags: bus master, 66MHz, medium devsel, latency 0 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 Flags: fast devsel 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 Flags: fast devsel 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 Flags: fast devsel 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 Flags: fast devsel Kernel driver in use: k10temp Kernel modules: k10temp 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 Flags: fast devsel 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 Flags: fast devsel 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 Flags: fast devsel 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 Flags: fast devsel 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 (prog-if 02 [NVM Express]) Subsystem: Samsung Electronics Co Ltd Device a801 Flags: bus master, fast devsel, latency 0, IRQ 45, NUMA node 0 Memory at fcf00000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: nvme 02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43d0 (rev 01) (prog-if 30 [XHCI]) Subsystem: ASRock Incorporation Device 43d0 Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at fcda0000 (64-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01) (prog-if 01 [AHCI 1.0]) Subsystem: ASRock Incorporation Device 43c8 Flags: bus master, fast devsel, latency 0, IRQ 47 Memory at fcd80000 (32-bit, non-prefetchable) [size=128K] Expansion ROM at fcd00000 [disabled] [size=512K] Capabilities: <access denied> Kernel driver in use: ahci 02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 32 Bus: primary=02, secondary=03, subordinate=0a, sec-latency=0 I/O behind bridge: 0000f000-0000ffff [size=4K] Memory behind bridge: fcc00000-fccfffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 33 Bus: primary=03, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 03:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 35 Bus: primary=03, secondary=05, subordinate=05, sec-latency=0 I/O behind bridge: 0000f000-0000ffff [size=4K] Memory behind bridge: fcc00000-fccfffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 03:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 36 Bus: primary=03, secondary=06, subordinate=06, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 38 Bus: primary=03, secondary=07, subordinate=07, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 39 Bus: primary=03, secondary=08, subordinate=08, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 03:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 40 Bus: primary=03, secondary=09, subordinate=09, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 03:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 41 Bus: primary=03, secondary=0a, subordinate=0a, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) Subsystem: ASRock Incorporation Device 1539 Flags: bus master, fast devsel, latency 0, IRQ 34 Memory at fcc00000 (32-bit, non-prefetchable) [size=128K] I/O ports at f000 [size=32] Memory at fcc20000 (32-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: igb Kernel modules: igb 0b:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 43 Memory at fcb00000 (32-bit, non-prefetchable) [size=16K] Bus: primary=0b, secondary=0c, subordinate=0d, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: fca00000-fcafffff [size=1M] Prefetchable memory behind bridge: 00000000e0000000-00000000f01fffff [size=258M] Capabilities: <access denied> Kernel driver in use: pcieport 0c:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 44 Bus: primary=0c, secondary=0d, subordinate=0d, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: fca00000-fcafffff [size=1M] Prefetchable memory behind bridge: 00000000e0000000-00000000f01fffff [size=258M] Capabilities: <access denied> Kernel driver in use: pcieport 0d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device 2316 Flags: bus master, fast devsel, latency 0, IRQ 111 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f0000000 (64-bit, prefetchable) [size=2M] I/O ports at e000 [size=256] Memory at fca00000 (32-bit, non-prefetchable) [size=512K] Expansion ROM at fca80000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: amdgpu Kernel modules: amdgpu 0d:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio Flags: bus master, fast devsel, latency 0, IRQ 110 Memory at fcaa0000 (32-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function Flags: fast devsel Capabilities: <access denied> 0e:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor Flags: bus master, fast devsel, latency 0, IRQ 99 Memory at fc800000 (32-bit, non-prefetchable) [size=1M] Memory at fc900000 (32-bit, non-prefetchable) [size=8K] Capabilities: <access denied> Kernel driver in use: ccp Kernel modules: ccp 0e:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller (prog-if 30 [XHCI]) Subsystem: ASRock Incorporation Device 7914 Flags: bus master, fast devsel, latency 0, IRQ 90 Memory at fc700000 (64-bit, non-prefetchable) [size=1M] Capabilities: <access denied> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 0f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function Flags: fast devsel Capabilities: <access denied> 0f:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) (prog-if 01 [AHCI 1.0]) Subsystem: ASRock Incorporation Device 7901 Flags: bus master, fast devsel, latency 0, IRQ 49 Memory at fce08000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: ahci 0f:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller Subsystem: ASRock Incorporation Device 2220 Flags: bus master, fast devsel, latency 0, IRQ 46 Memory at fce00000 (32-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- You are receiving this mail because: You are watching the assignee of the bug.

1 15

[PATCH v5 0/7] dma-buf: Performance improvements for system heap & a system-uncached implementation
by John Stultz 21 May '21

21 May '21

Hey All, So just wanted to send my last revision of my patch series of performance optimizations to the dma-buf system heap. This series reworks the system heap to use sgtables, and then consolidates the pagelist method from the heap-helpers into the CMA heap. After which the heap-helpers logic is removed (as it is unused). I'd still like to find a better way to avoid some of the logic duplication in implementing the entire dma_buf_ops handlers per heap. But unfortunately that code is tied somewhat to how the buffer's memory is tracked. As more heaps show up I think we'll have a better idea how to best share code, so for now I think this is ok. After this, the series introduces an optimization that Ørjan Eide implemented for ION that avoids calling sync on attachments that don't have a mapping. Next, an optimization to use larger order pages for the system heap. This change brings us closer to the current performance of the ION allocation code (though there still is a gap due to ION using a mix of deferred-freeing and page pools, I'll be looking at integrating those eventually). Finally, a reworked version of my uncached system heap implementation I was submitting a few weeks back. Since it duplicated a lot of the now reworked system heap code, I realized it would be much simpler to add the functionality to the system_heap implementation itself. While not improving the core allocation performance, the uncached heap allocations do result in *much* improved performance on HiKey960 as it avoids a lot of flushing and invalidating buffers that the cpu doesn't touch often. Feedback on these would be great! thanks -john New in v5: * Added a comment explaining why the order sizes are chosen as they are Cc: Sumit Semwal <sumit.semwal(a)linaro.org> Cc: Liam Mark <lmark(a)codeaurora.org> Cc: Laura Abbott <labbott(a)kernel.org> Cc: Brian Starkey <Brian.Starkey(a)arm.com> Cc: Hridya Valsaraju <hridya(a)google.com> Cc: Suren Baghdasaryan <surenb(a)google.com> Cc: Sandeep Patil <sspatil(a)google.com> Cc: Daniel Mentz <danielmentz(a)google.com> Cc: Chris Goldsworthy <cgoldswo(a)codeaurora.org> Cc: Ørjan Eide <orjan.eide(a)arm.com> Cc: Robin Murphy <robin.murphy(a)arm.com> Cc: Ezequiel Garcia <ezequiel(a)collabora.com> Cc: Simon Ser <contact(a)emersion.fr> Cc: James Jones <jajones(a)nvidia.com> Cc: linux-media(a)vger.kernel.org Cc: dri-devel(a)lists.freedesktop.org John Stultz (7): dma-buf: system_heap: Rework system heap to use sgtables instead of pagelists dma-buf: heaps: Move heap-helper logic into the cma_heap implementation dma-buf: heaps: Remove heap-helpers code dma-buf: heaps: Skip sync if not mapped dma-buf: system_heap: Allocate higher order pages if available dma-buf: dma-heap: Keep track of the heap device struct dma-buf: system_heap: Add a system-uncached heap re-using the system heap drivers/dma-buf/dma-heap.c | 33 +- drivers/dma-buf/heaps/Makefile | 1 - drivers/dma-buf/heaps/cma_heap.c | 324 +++++++++++++++--- drivers/dma-buf/heaps/heap-helpers.c | 270 --------------- drivers/dma-buf/heaps/heap-helpers.h | 53 --- drivers/dma-buf/heaps/system_heap.c | 494 ++++++++++++++++++++++++--- include/linux/dma-heap.h | 9 + 7 files changed, 753 insertions(+), 431 deletions(-) delete mode 100644 drivers/dma-buf/heaps/heap-helpers.c delete mode 100644 drivers/dma-buf/heaps/heap-helpers.h -- 2.17.1

5 18

BUG: unable to handle kernel paging request in vga16fb_imageblit (2)
by syzbot 17 May '21

17 May '21

Hello, syzbot found the following crash on: HEAD commit: 262f7a6b Merge tag 'for-5.7-rc3-tag' of git://git.kernel.o.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12786888100000 kernel config: https://syzkaller.appspot.com/x/.config?x=5b075813ec8b93cd dashboard link: https://syzkaller.appspot.com/bug?extid=1f29e126cf461c4de3b3 compiler: gcc (GCC) 9.0.0 20181231 (experimental) Unfortunately, I don't have any reproducer for this crash yet. IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+1f29e126cf461c4de3b3(a)syzkaller.appspotmail.com BUG: unable to handle page fault for address: ffff8880ffca0e80 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD d401067 P4D d401067 PUD 0 Oops: 0002 [#1] PREEMPT SMP KASAN CPU: 0 PID: 710 Comm: syz-executor.5 Not tainted 5.7.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:writeb arch/x86/include/asm/io.h:65 [inline] RIP: 0010:vga_imageblit_expand drivers/video/fbdev/vga16fb.c:1168 [inline] RIP: 0010:vga16fb_imageblit+0xa5b/0x2210 drivers/video/fbdev/vga16fb.c:1260 Code: 48 89 fa 48 c1 ea 03 0f b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 09 84 d2 74 05 e8 ee 59 ed fd 41 8b 47 14 48 8b 74 24 08 <88> 06 0f ae e8 8a 06 b8 05 00 00 00 ba ce 03 00 00 ee 48 c7 c2 18 RSP: 0000:ffffc90002ea71f0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000007 RCX: ffffc90014391000 RDX: 0000000000000000 RSI: ffff8880ffca0e80 RDI: ffffc90002ea739c RBP: ffffc90002ea738c R08: ffff8880922ac200 R09: 0000000000000000 R10: ffffffff8a895007 R11: fffffbfff1512a00 R12: 0000000000000000 R13: ffff888218de5140 R14: 0000000000000001 R15: ffffc90002ea7388 FS: 00007fbeeb282700(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff8880ffca0e80 CR3: 000000008e9c5000 CR4: 00000000001406f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: bit_putcs_unaligned drivers/video/fbdev/core/bitblit.c:139 [inline] bit_putcs+0x910/0xe10 drivers/video/fbdev/core/bitblit.c:188 fbcon_putcs+0x345/0x3f0 drivers/video/fbdev/core/fbcon.c:1362 con_flush drivers/tty/vt/vt.c:2569 [inline] do_con_write.part.0+0x7d1/0x1dc0 drivers/tty/vt/vt.c:2772 do_con_write drivers/tty/vt/vt.c:2588 [inline] con_write+0x41/0xe0 drivers/tty/vt/vt.c:3154 process_output_block drivers/tty/n_tty.c:595 [inline] n_tty_write+0x3f0/0xf90 drivers/tty/n_tty.c:2333 do_tty_write drivers/tty/tty_io.c:962 [inline] tty_write+0x495/0x800 drivers/tty/tty_io.c:1046 __vfs_write+0x76/0x100 fs/read_write.c:495 __kernel_write+0x11c/0x3a0 fs/read_write.c:516 write_pipe_buf+0x153/0x1e0 fs/splice.c:809 splice_from_pipe_feed fs/splice.c:512 [inline] __splice_from_pipe+0x3e6/0x7b0 fs/splice.c:636 splice_from_pipe+0xd9/0x140 fs/splice.c:671 default_file_splice_write+0x37/0x90 fs/splice.c:821 do_splice_from fs/splice.c:863 [inline] direct_splice_actor+0x115/0x160 fs/splice.c:1037 splice_direct_to_actor+0x38c/0x980 fs/splice.c:992 do_splice_direct+0x1b4/0x280 fs/splice.c:1080 do_sendfile+0x555/0xc50 fs/read_write.c:1521 __do_sys_sendfile64 fs/read_write.c:1582 [inline] __se_sys_sendfile64 fs/read_write.c:1568 [inline] __x64_sys_sendfile64+0x1cc/0x210 fs/read_write.c:1568 do_syscall_64+0xf6/0x7d0 arch/x86/entry/common.c:295 entry_SYSCALL_64_after_hwframe+0x49/0xb3 RIP: 0033:0x45c829 Code: 0d b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007fbeeb281c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000028 RAX: ffffffffffffffda RBX: 00000000004fc0c0 RCX: 000000000045c829 RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000003 RBP: 000000000078bf00 R08: 0000000000000000 R09: 0000000000000000 R10: 0800000080004103 R11: 0000000000000246 R12: 00000000ffffffff R13: 00000000000008d6 R14: 00000000004cb7a1 R15: 00007fbeeb2826d4 Modules linked in: CR2: ffff8880ffca0e80 ---[ end trace 5bb103c4fc7bf525 ]--- RIP: 0010:writeb arch/x86/include/asm/io.h:65 [inline] RIP: 0010:vga_imageblit_expand drivers/video/fbdev/vga16fb.c:1168 [inline] RIP: 0010:vga16fb_imageblit+0xa5b/0x2210 drivers/video/fbdev/vga16fb.c:1260 Code: 48 89 fa 48 c1 ea 03 0f b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 09 84 d2 74 05 e8 ee 59 ed fd 41 8b 47 14 48 8b 74 24 08 <88> 06 0f ae e8 8a 06 b8 05 00 00 00 ba ce 03 00 00 ee 48 c7 c2 18 RSP: 0000:ffffc90002ea71f0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000007 RCX: ffffc90014391000 RDX: 0000000000000000 RSI: ffff8880ffca0e80 RDI: ffffc90002ea739c RBP: ffffc90002ea738c R08: ffff8880922ac200 R09: 0000000000000000 R10: ffffffff8a895007 R11: fffffbfff1512a00 R12: 0000000000000000 R13: ffff888218de5140 R14: 0000000000000001 R15: ffffc90002ea7388 FS: 00007fbeeb282700(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff8880ffca0e80 CR3: 000000008e9c5000 CR4: 00000000001406f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 --- This bug is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller(a)googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

5 20

← Newer
1
2
3
4
5
6
7
8
9
...
66
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel December 2020