From: Karol Herbst <kherbst@redhat.com>
To: Ondrej Zary <linux@zary.sk>
Cc: "Christian König" <christian.koenig@amd.com>,
nouveau <nouveau@lists.freedesktop.org>,
"Ben Skeggs" <bskeggs@redhat.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: nouveau broken again on Riva TNT2 in 5.14.0-rc2
Date: Thu, 22 Jul 2021 21:51:18 +0200 [thread overview]
Message-ID: <CACO55tvq0Ksm6x_L3r6B8KhYR6dTqb=xzPaRzAeQgaBnff_sYA@mail.gmail.com> (raw)
In-Reply-To: <202107222122.05546.linux@zary.sk>
hey thanks for the report.
This is a known issue and the fix is pending in drm-mist-fixes and
should land in 5.14 soonish.
On Thu, Jul 22, 2021 at 9:29 PM Ondrej Zary <linux@zary.sk> wrote:
>
> Hello,
> nouveau is broken again:
>
> [ 58.795794] BUG: kernel NULL pointer dereference, address: 0000017c
> [ 58.795835] #PF: supervisor read access in kernel mode
> [ 58.795844] #PF: error_code(0x0000) - not-present page
> [ 58.795851] *pde = 00000000
> [ 58.795862] Oops: 0000 [#1] SMP
> [ 58.795875] CPU: 0 PID: 1730 Comm: Xorg Not tainted 5.14.0-rc2+ #391
> [ 58.795886] Hardware name: VIA Technologies, Inc. VT82C694X/694X, BIOS 6.00 PG 02/19/2002
> [ 58.795894] EIP: nouveau_bo_wr16+0x8/0x27 [nouveau]
> [ 58.796716] Code: 85 ff 74 0d 80 7d f3 00 74 07 80 a6 c0 01 00 00 fe 89 f0 e8 e5 ee ff ff 8d 65 f4 89 f8 5b 5e 5f 5d c3 55 01 d2 89 e5 53 89 c3 <03> 93 7c 01 00 00 0f b7 c1 f6 83 84 01 00 00 80 74 07 e8 8a bc 72
> [ 58.796728] EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000
> [ 58.796736] ESI: 00000020 EDI: c18bc600 EBP: c7c49d88 ESP: c7c49d84
> [ 58.796744] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 EFLAGS: 00210246
> [ 58.796754] CR0: 80050033 CR2: 0000017c CR3: 07e12000 CR4: 00000690
> [ 58.796762] Call Trace:
> [ 58.796774] nv04_crtc_cursor_set+0x148/0x1d8 [nouveau]
> [ 58.796952] ? ttm_bo_reserve.constprop.16+0x1c/0x1c [nouveau]
> [ 58.797122] drm_mode_cursor_common+0x13b/0x1ad
> [ 58.797150] ? ttm_bo_reserve.constprop.16+0x1c/0x1c [nouveau]
> [ 58.797322] drm_mode_cursor_ioctl+0x2e/0x36
> [ 58.797335] ? drm_mode_setplane+0x203/0x203
> [ 58.797346] drm_ioctl_kernel+0x66/0x99
> [ 58.797366] drm_ioctl+0x211/0x2d8
> [ 58.797377] ? drm_mode_setplane+0x203/0x203
> [ 58.797389] ? __cond_resched+0x1e/0x22
> [ 58.797409] ? mutex_lock+0xb/0x24
> [ 58.797422] ? rpm_resume.part.14+0x6f/0x362
> [ 58.797447] ? ktime_get_mono_fast_ns+0x5e/0xf2
> [ 58.797469] ? __pm_runtime_resume+0x5b/0x63
> [ 58.797480] nouveau_drm_ioctl+0x65/0x81 [nouveau]
> [ 58.797662] ? nouveau_cli_work+0xc3/0xc3 [nouveau]
> [ 58.797838] vfs_ioctl+0x1a/0x24
> [ 58.797850] __ia32_sys_ioctl+0x6ea/0x704
> [ 58.797861] ? doublefault_shim+0x120/0x120
> [ 58.797872] ? exit_to_user_mode_prepare+0x9e/0x10c
> [ 58.797900] do_int80_syscall_32+0x53/0x6e
> [ 58.797910] entry_INT80_32+0xf0/0xf0
> [ 58.797923] EIP: 0xb7f04092
> [ 58.797932] Code: 00 00 00 e9 90 ff ff ff ff a3 24 00 00 00 68 30 00 00 00 e9 80 ff ff ff ff a3 e8 ff ff ff 66 90 00 00 00 00 00 00 00 00 cd 80 <c3> 8d b4 26 00 00 00 00 8d b6 00 00 00 00 8b 1c 24 c3 8d b4 26 00
> [ 58.797943] EAX: ffffffda EBX: 0000000e ECX: c01c64a3 EDX: bf9a15c0
> [ 58.797952] ESI: 00997850 EDI: c01c64a3 EBP: 0000000e ESP: bf9a1574
> [ 58.797959] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00200292
> [ 58.797972] Modules linked in: i2c_dev nouveau wmi hwmon drm_ttm_helper psmouse serio_raw via_agp sg parport_pc 8139cp parport
> [ 58.798016] CR2: 000000000000017c
> [ 58.798147] ---[ end trace 732829d39ed65de9 ]---
>
>
> d02117f8efaa5fbc37437df1ae955a147a2a424a is the first bad commit
>
> --
> Ondrej Zary
>
next prev parent reply other threads:[~2021-07-22 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 19:22 nouveau broken again on Riva TNT2 in 5.14.0-rc2 Ondrej Zary
2021-07-22 19:51 ` Karol Herbst [this message]
2021-07-23 7:26 ` [Nouveau] " Daniel Vetter
2021-07-23 15:52 ` Ondrej Zary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACO55tvq0Ksm6x_L3r6B8KhYR6dTqb=xzPaRzAeQgaBnff_sYA@mail.gmail.com' \
--to=kherbst@redhat.com \
--cc=bskeggs@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@zary.sk \
--cc=nouveau@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).