From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CBBFFC43457 for ; Tue, 13 Oct 2020 23:54:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 85F1C206D5 for ; Tue, 13 Oct 2020 23:54:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730360AbgJMXyU (ORCPT ); Tue, 13 Oct 2020 19:54:20 -0400 Received: from winds.org ([68.75.195.9]:45042 "EHLO winds.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726953AbgJMXyT (ORCPT ); Tue, 13 Oct 2020 19:54:19 -0400 Received: by winds.org (Postfix, from userid 100) id 9B0A113F97CD; Tue, 13 Oct 2020 19:54:18 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by winds.org (Postfix) with ESMTP id 97C9913F9795; Tue, 13 Oct 2020 19:54:18 -0400 (EDT) Date: Tue, 13 Oct 2020 19:54:18 -0400 (EDT) From: Byron Stanoszek To: Ben Skeggs cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org Subject: Re: Nouveau DRM failure on 5120x1440 screen with 5.8/5.9 kernel In-Reply-To: Message-ID: References: User-Agent: Alpine 2.23 (LNX 451 2020-06-18) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 13 Oct 2020, Byron Stanoszek wrote: > I'm having a problem with both the 5.8 and 5.9 kernels using the nouveau DRM > driver. I have a laptop with a VGA card (specs below) connected to a > 5120x1440 screen. At boot time, the card correctly detects the screen, tries > to allocate fbdev fb0, then the video hangs completely for 15-30 seconds > until it goes blank. This message eventually displays after a while: Workqueue: nvkm-disp nv50_disp_super RIP: 0010:nv50_disp_super_2_2+0x1b0/0x470 Code: 69 00 00 48 69 c0 d3 4d 62 10 48 c1 e8 26 49 89 c5 0f b7 43 40 44 89 e9 8d 44 02 f9 0f b7 53 46 29 d0 31 d2 48 98 49 0f af c4 <48> f7 f1 48 89 c6 0f b7 43 4e 0f b7 53 4c 83 e8 19 29 d0 31 d2 48 RSP: 0018:ffffc900005e3e08 EFLAGS: 00010206 RAX: 0000000000000000 RBX: ffff88841b08ed20 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffc90003614200 RDI: ffffffff820c1140 RBP: ffff88841b202060 R08: 0000000000000000 R09: 00000000000061ce R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000 R13: 0000000000000000 R14: ffff88841b96b800 R15: ffff88841b975000 FS: 0000000000000000(0000) GS:ffff88841dc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f922e61e000 CR3: 000000000240a004 CR4: 00000000001706b0 Call Trace: ? nvkm_dp_disable+0x5d/0x70 ? nv50_disp_super+0x137/0x220 ? process_one_work+0x19c/0x2c0 ? worker_thread+0x48/0x350 ? process_one_work+0x2c0/0x2c0 ? kthread+0x129/0x150 ? __kthread_create_worker+0x100/0x100 ? ret_from_fork+0x22/0x30 ---[ end trace dbb0d14fd1ddb445 ]--- nouveau 0000:01:00.0: DRM: core notifier timeout Thanks, -Byron