From: Ondrej Zary <linux@zary.sk>
To: Ben Skeggs <bskeggs@redhat.com>
Cc: nouveau@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: nouveau broken on Riva TNT2 in 5.13.0-rc4: NULL pointer dereference in nouveau_bo_sync_for_device
Date: Sun, 6 Jun 2021 23:16:03 +0200 [thread overview]
Message-ID: <202106062316.03369.linux@zary.sk> (raw)
In-Reply-To: <202106052334.23943.linux@zary.sk>
On Saturday 05 June 2021 23:34:23 Ondrej Zary wrote:
> On Saturday 05 June 2021 21:43:52 Ondrej Zary wrote:
> > Hello,
> > I'm testing 5.13.0-rc4 and nouveau crashes with NULL pointer dereference in nouveau_bo_sync_for_device.
> > Found various reports like this but that was back in februaryso that should be fixed now.
>
> So it is the same bug. Broken since 5.11. This revert fixes it in 5.11:
> https://lists.freedesktop.org/archives/dri-devel/2021-February/298531.html
>
> Added some debug printks to nouveau_bo_sync_for_device:
> [ 22.225048] ttm_dma=fc33b500
> [ 22.225066] ttm_dma->num_pages=18
> [ 22.225071] i=0 num_pages=16
> [ 22.225077] ttm_dma->dma_address=00000000
> [ 22.225094] BUG: kernel NULL pointer dereference, address: 00000000
>
> So ttm->dma_address is NULL.
>
Tested reverting f295c8cfec833c2707ff1512da10d65386dde7af again and it does not work...
Not sure what I did before.
Bisecting between 5.10 and 5.11 is impossible - I keep hitting neverending stream of bugs.
As always with nouveau...
--
Ondrej Zary
next prev parent reply other threads:[~2021-06-07 7:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 19:43 nouveau broken on Riva TNT2 in 5.13.0-rc4: NULL pointer dereference in nouveau_bo_sync_for_device Ondrej Zary
2021-06-05 21:22 ` [Nouveau] " Ilia Mirkin
2021-06-05 21:34 ` Ondrej Zary
2021-06-06 21:16 ` Ondrej Zary [this message]
2021-06-07 20:58 ` Ondrej Zary
2021-06-08 18:47 ` Ondrej Zary
2021-06-08 20:01 ` Ondrej Zary
2021-06-08 21:59 ` Ondrej Zary
2021-06-09 6:43 ` Christian König
2021-06-09 6:57 ` Ondrej Zary
2021-06-09 7:02 ` Christian König
2021-06-09 7:10 ` Ondrej Zary
2021-06-09 9:21 ` Christian König
2021-06-09 20:00 ` Ondrej Zary
2021-06-10 6:43 ` Christian König
2021-06-10 17:50 ` Ondrej Zary
2021-06-10 17:59 ` Christian König
2021-06-11 12:38 ` Christian König
2021-06-11 18:23 ` Ondrej Zary
2021-06-14 11:07 ` Christian König
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=202106062316.03369.linux@zary.sk \
--to=linux@zary.sk \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).