https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #23 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
(In reply to Paul Menzel from comment #22)
> Bernd, what triggers this on your system? What is your test case? Start some
> program?
basically start the system, log in,
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #22 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
Ok, being back at the system after some days, I see the kmemleaks are still
present with Linux 5.0-rc6+.
Bernd, what triggers this on your system? What is your test
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #21 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
Created attachment 281201
--> https://bugzilla.kernel.org/attachment.cgi?id=281201=edit
kmemleak output with 4.19.0-rc1 5d35ed4832da
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #20 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
(In reply to Christian König from comment #17)
> We completely disabled the feature added in "5d35ed4832d" for upstreaming
> later on.
>
> Can you guys please test
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #19 from Christian König (christian.koe...@amd.com) ---
(In reply to Paul Menzel from comment #18)
> (In reply to Christian König from comment #17)
> > We completely disabled the feature added in "5d35ed4832d" for upstreaming
> >
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #18 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
(In reply to Christian König from comment #17)
> We completely disabled the feature added in "5d35ed4832d" for upstreaming
> later on.
Sorry, I do not understand
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #17 from Christian König (christian.koe...@amd.com) ---
We completely disabled the feature added in "5d35ed4832d" for upstreaming later
on.
Can you guys please test amd-staging-drm-next as well and check if the problem
occurs there
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #16 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
Created attachment 281177
--> https://bugzilla.kernel.org/attachment.cgi?id=281177=edit
kmemleak output with 5.0-rc6
Nope sorry, I see the same with kernel 5.0-rc6.
btw,
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #15 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
Sure, can test that one.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #14 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
Hi. Testing Linux 5.0-rc6 for some minutes, I am not seeing these kmemleak
messages anymore on the MSI Mortar B350M. Bernd, could you test this?
Unfortunately, the
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #13 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
meh …
well, I just tested 4.20.10 and I do still see a lot of memory leaks there.
kmemleak: 93 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
And it looks an
https://bugzilla.kernel.org/show_bug.cgi?id=202537
Christian König (christian.koe...@amd.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #11 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
Ok, so finally I think I've been able to track this down.
Not 100% sure, because for the final test versions I had to apply a few patches
to fix bugs that otherwise would've
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #10 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
Unfortunately this turns out to be much harder than expected, because about 1/3
of the revs to test just won't boot at all (like instant kernel panic and not
responding).
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #9 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
(In reply to Michel Dänzer from comment #7)
> kmemleak is claiming there are leaks all over the place. That's weird, since
> other people (including myself) aren't seeing any
https://bugzilla.kernel.org/show_bug.cgi?id=202537
Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #7 from Michel Dänzer (mic...@daenzer.net) ---
kmemleak is claiming there are leaks all over the place. That's weird, since
other people (including myself) aren't seeing any such leaks, also with 4.20
based kernels.
So, I'm afraid
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #5 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
I'll have a look at kmemleak, but I've never worked with it, so it would be
nice to have a backup in case I don't get along with it. ;)
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #6 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
Created attachment 281105
--> https://bugzilla.kernel.org/attachment.cgi?id=281105=edit
kmemleak output with 4.20.6
So I let kmemleak do a scan and this is the output.
In
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #4 from Michel Dänzer (mic...@daenzer.net) ---
drivers/gpu/drm/amd/display/ seems likely. Even if the result from that doesn't
make sense, it should at least narrow down the other commits you need to test.
Or maybe just start with
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #3 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
Sure, I can try to bisect it, but it would help if I could narrow the amount of
commits down, because usually the problem doesn't come right away, so it would
take some time
https://bugzilla.kernel.org/show_bug.cgi?id=202537
Michel Dänzer (mic...@daenzer.net) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #1 from Bernd Steinhauser (li...@bernd-steinhauser.de) ---
Created attachment 281077
--> https://bugzilla.kernel.org/attachment.cgi?id=281077=edit
kernel messages
--
You are receiving this mail because:
You are watching the
23 matches
Mail list logo
