From: Ondrej Zary <linux@zary.sk>
To: "Christian König" <christian.koenig@amd.com>
Cc: nouveau@lists.freedesktop.org, Ben Skeggs <bskeggs@redhat.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Nouveau] nouveau broken on Riva TNT2 in 5.13.0-rc4: NULL pointer dereference in nouveau_bo_sync_for_device
Date: Wed, 9 Jun 2021 09:10:51 +0200 [thread overview]
Message-ID: <202106090910.51188.linux@zary.sk> (raw)
In-Reply-To: <1c4a7360-57e3-c75a-c729-1432db5b90b9@amd.com>
On Wednesday 09 June 2021, Christian König wrote:
> Am 09.06.21 um 08:57 schrieb Ondrej Zary:
> > [SNIP]
> >> Thanks for the heads up. So the problem with my patch is already fixed,
> >> isn't it?
> > The NULL pointer dereference in nouveau_bo_wr16 introduced in
> > 141b15e59175aa174ca1f7596188bd15a7ca17ba was fixed by
> > aea656b0d05ec5b8ed5beb2f94c4dd42ea834e9d.
> >
> > That's the bug I hit when bisecting the original problem:
> > NULL pointer dereference in nouveau_bo_sync_for_device
> > It's caused by:
> > # first bad commit: [e34b8feeaa4b65725b25f49c9b08a0f8707e8e86] drm/ttm: merge ttm_dma_tt back into ttm_tt
>
> Good that I've asked :)
>
> Ok that's a bit strange. e34b8feeaa4b65725b25f49c9b08a0f8707e8e86 was
> created mostly automated.
>
> Do you have the original backtrace of that NULL pointer deref once more?
The original backtrace is here: https://lkml.org/lkml/2021/6/5/350
--
Ondrej Zary
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
WARNING: multiple messages have this Message-ID (diff)
From: Ondrej Zary <linux@zary.sk>
To: "Christian König" <christian.koenig@amd.com>
Cc: nouveau@lists.freedesktop.org, Ben Skeggs <bskeggs@redhat.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: nouveau broken on Riva TNT2 in 5.13.0-rc4: NULL pointer dereference in nouveau_bo_sync_for_device
Date: Wed, 9 Jun 2021 09:10:51 +0200 [thread overview]
Message-ID: <202106090910.51188.linux@zary.sk> (raw)
In-Reply-To: <1c4a7360-57e3-c75a-c729-1432db5b90b9@amd.com>
On Wednesday 09 June 2021, Christian König wrote:
> Am 09.06.21 um 08:57 schrieb Ondrej Zary:
> > [SNIP]
> >> Thanks for the heads up. So the problem with my patch is already fixed,
> >> isn't it?
> > The NULL pointer dereference in nouveau_bo_wr16 introduced in
> > 141b15e59175aa174ca1f7596188bd15a7ca17ba was fixed by
> > aea656b0d05ec5b8ed5beb2f94c4dd42ea834e9d.
> >
> > That's the bug I hit when bisecting the original problem:
> > NULL pointer dereference in nouveau_bo_sync_for_device
> > It's caused by:
> > # first bad commit: [e34b8feeaa4b65725b25f49c9b08a0f8707e8e86] drm/ttm: merge ttm_dma_tt back into ttm_tt
>
> Good that I've asked :)
>
> Ok that's a bit strange. e34b8feeaa4b65725b25f49c9b08a0f8707e8e86 was
> created mostly automated.
>
> Do you have the original backtrace of that NULL pointer deref once more?
The original backtrace is here: https://lkml.org/lkml/2021/6/5/350
--
Ondrej Zary
WARNING: multiple messages have this Message-ID (diff)
From: Ondrej Zary <linux@zary.sk>
To: "Christian König" <christian.koenig@amd.com>
Cc: Ben Skeggs <bskeggs@redhat.com>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: nouveau broken on Riva TNT2 in 5.13.0-rc4: NULL pointer dereference in nouveau_bo_sync_for_device
Date: Wed, 9 Jun 2021 09:10:51 +0200 [thread overview]
Message-ID: <202106090910.51188.linux@zary.sk> (raw)
In-Reply-To: <1c4a7360-57e3-c75a-c729-1432db5b90b9@amd.com>
On Wednesday 09 June 2021, Christian König wrote:
> Am 09.06.21 um 08:57 schrieb Ondrej Zary:
> > [SNIP]
> >> Thanks for the heads up. So the problem with my patch is already fixed,
> >> isn't it?
> > The NULL pointer dereference in nouveau_bo_wr16 introduced in
> > 141b15e59175aa174ca1f7596188bd15a7ca17ba was fixed by
> > aea656b0d05ec5b8ed5beb2f94c4dd42ea834e9d.
> >
> > That's the bug I hit when bisecting the original problem:
> > NULL pointer dereference in nouveau_bo_sync_for_device
> > It's caused by:
> > # first bad commit: [e34b8feeaa4b65725b25f49c9b08a0f8707e8e86] drm/ttm: merge ttm_dma_tt back into ttm_tt
>
> Good that I've asked :)
>
> Ok that's a bit strange. e34b8feeaa4b65725b25f49c9b08a0f8707e8e86 was
> created mostly automated.
>
> Do you have the original backtrace of that NULL pointer deref once more?
The original backtrace is here: https://lkml.org/lkml/2021/6/5/350
--
Ondrej Zary
next prev parent reply other threads:[~2021-06-09 7:10 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 19:43 [Nouveau] nouveau broken on Riva TNT2 in 5.13.0-rc4: NULL pointer dereference in nouveau_bo_sync_for_device Ondrej Zary
2021-06-05 19:43 ` Ondrej Zary
2021-06-05 19:43 ` Ondrej Zary
2021-06-05 21:22 ` [Nouveau] " Ilia Mirkin
2021-06-05 21:22 ` Ilia Mirkin
2021-06-05 21:22 ` Ilia Mirkin
2021-06-05 21:34 ` Ondrej Zary
2021-06-05 21:34 ` Ondrej Zary
2021-06-05 21:34 ` Ondrej Zary
2021-06-06 21:16 ` [Nouveau] " Ondrej Zary
2021-06-06 21:16 ` Ondrej Zary
2021-06-06 21:16 ` Ondrej Zary
2021-06-07 20:58 ` [Nouveau] " Ondrej Zary
2021-06-07 20:58 ` Ondrej Zary
2021-06-07 20:58 ` Ondrej Zary
2021-06-08 18:47 ` [Nouveau] " Ondrej Zary
2021-06-08 18:47 ` Ondrej Zary
2021-06-08 18:47 ` Ondrej Zary
2021-06-08 20:01 ` [Nouveau] " Ondrej Zary
2021-06-08 20:01 ` Ondrej Zary
2021-06-08 20:01 ` Ondrej Zary
2021-06-08 21:59 ` [Nouveau] " Ondrej Zary
2021-06-08 21:59 ` Ondrej Zary
2021-06-08 21:59 ` Ondrej Zary
2021-06-09 6:43 ` [Nouveau] " Christian König
2021-06-09 6:43 ` Christian König
2021-06-09 6:43 ` Christian König
2021-06-09 6:57 ` [Nouveau] " Ondrej Zary
2021-06-09 6:57 ` Ondrej Zary
2021-06-09 6:57 ` Ondrej Zary
2021-06-09 7:02 ` [Nouveau] " Christian König
2021-06-09 7:02 ` Christian König
2021-06-09 7:02 ` Christian König
2021-06-09 7:10 ` Ondrej Zary [this message]
2021-06-09 7:10 ` Ondrej Zary
2021-06-09 7:10 ` Ondrej Zary
2021-06-09 9:21 ` [Nouveau] " Christian König
2021-06-09 9:21 ` Christian König
2021-06-09 9:21 ` Christian König
2021-06-09 20:00 ` [Nouveau] " Ondrej Zary
2021-06-09 20:00 ` Ondrej Zary
2021-06-09 20:00 ` Ondrej Zary
2021-06-10 6:43 ` [Nouveau] " Christian König
2021-06-10 6:43 ` Christian König
2021-06-10 6:43 ` Christian König
2021-06-10 17:50 ` [Nouveau] " Ondrej Zary
2021-06-10 17:50 ` Ondrej Zary
2021-06-10 17:50 ` Ondrej Zary
2021-06-10 17:59 ` [Nouveau] " Christian König
2021-06-10 17:59 ` Christian König
2021-06-10 17:59 ` Christian König
2021-06-11 12:38 ` [Nouveau] " Christian König
2021-06-11 12:38 ` Christian König
2021-06-11 12:38 ` Christian König
2021-06-11 18:23 ` [Nouveau] " Ondrej Zary
2021-06-11 18:23 ` Ondrej Zary
2021-06-11 18:23 ` Ondrej Zary
2021-06-14 11:07 ` [Nouveau] " Christian König
2021-06-14 11:07 ` Christian König
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=202106090910.51188.linux@zary.sk \
--to=linux@zary.sk \
--cc=bskeggs@redhat.com \
--cc=christian.koenig@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.