Finally was able to reproduce with your commit too
(a79a94c676e5b06d43b7b236dbf22b70d2b11b39).
It's definitely not 100% triggerable hence my bisect missing it.
Tom
On 07/16/2018 01:14 PM, Tom St Denis wrote:
With the tip of drm-next I get this KASAN immediately.
Tom
On 07/16/2018 12:40 PM,
With the tip of drm-next I get this KASAN immediately.
Tom
On 07/16/2018 12:40 PM, Michel Dänzer wrote:
On 2018-07-16 06:36 PM, Tom St Denis wrote:
Will in a bit. I'm tracking down a KASAN oops that the tip of drm-next
causes with unigine-heaven.
Is it different from the one I reported an
Might be though it's definitely a heisenbug since I zeroed in on that
commit easily but now I can't reproduce it with 10+ cycles of
loading/killing unigine-heaven
On 07/16/2018 12:54 PM, Tom St Denis wrote:
On 07/16/2018 12:40 PM, Michel Dänzer wrote:
On 2018-07-16 06:36 PM, Tom St Denis
On 07/16/2018 12:40 PM, Michel Dänzer wrote:
On 2018-07-16 06:36 PM, Tom St Denis wrote:
Will in a bit. I'm tracking down a KASAN oops that the tip of drm-next
causes with unigine-heaven.
Is it different from the one I reported an hour ago?
On 2018-07-16 06:36 PM, Tom St Denis wrote:
> Will in a bit. I'm tracking down a KASAN oops that the tip of drm-next
> causes with unigine-heaven.
Is it different from the one I reported an hour ago?
https://lists.freedesktop.org/archives/amd-gfx/2018-July/024207.html
--
Earthling Michel
Will in a bit. I'm tracking down a KASAN oops that the tip of drm-next
causes with unigine-heaven. (geez, on vacation for a week and my Raven
is suffering hehehehehe)
Tom
On 07/16/2018 12:35 PM, Michel Dänzer wrote:
On 2018-07-16 05:55 PM, Tom St Denis wrote:
I have the same now and get
On 2018-07-16 05:55 PM, Tom St Denis wrote:
> I have the same now and get the attached dmesg.
Still all question marks. :( Anyway, looks like it's probably from
ttm_bo_delayed_delete, but that still doesn't tell us where the BO is
really freed from.
Can you try the attached patch and see if the
I have the same now and get the attached dmesg.
Tom
On 07/16/2018 10:25 AM, Michel Dänzer wrote:
On 2018-07-16 02:10 PM, Tom St Denis wrote:
Hi all,
Back from vacation, booting up the latest drm-next kernel and noticed
this warning on boot. Attached.
I like the comment in the commit
Am 16.07.2018 um 16:25 schrieb Michel Dänzer:
On 2018-07-16 02:10 PM, Tom St Denis wrote:
Hi all,
Back from vacation, booting up the latest drm-next kernel and noticed
this warning on boot. Attached.
I like the comment in the commit 5c200f56506a142451f17dbea7befa76dd74a942:
"This shouldn't
On 2018-07-16 02:10 PM, Tom St Denis wrote:
> Hi all,
>
> Back from vacation, booting up the latest drm-next kernel and noticed
> this warning on boot. Attached.
>
> I like the comment in the commit 5c200f56506a142451f17dbea7befa76dd74a942:
>
> "This shouldn't happen, but if it does, we'll get
Hi all,
Back from vacation, booting up the latest drm-next kernel and noticed
this warning on boot. Attached.
I like the comment in the commit 5c200f56506a142451f17dbea7befa76dd74a942:
"This shouldn't happen, but if it does, we'll get a backtrace of the
caller, and update the pin_size values
11 matches
Mail list logo