https://bugzilla.kernel.org/show_bug.cgi?id=211277
kolAflash (kolafl...@kolahilft.de) changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #87 from kolAflash (kolafl...@kolahilft.de) ---
(In reply to James Zhu from comment #86)
> Hi @kolAflash, thanks so much for your effort on this verification!
> Would you mind help apply those patches on 5.12 stable to check also?
>
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #86 from James Zhu (jam...@amd.com) ---
Hi @kolAflash, thanks so much for your effort on this verification!
Would you mind help apply those patches on 5.12 stable to check also?
it should be automatically merged. Thanks! James
--
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #85 from kolAflash (kolafl...@kolahilft.de) ---
(In reply to James Zhu from comment #77)
> Created attachment 299697 [details]
> backport patch for 5.10 stable.
>
> Hi @kolAflash, before I send out them to public for review,. could
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #84 from kolAflash (kolafl...@kolahilft.de) ---
@James
I was able to compile!
Looks like this was some fault of mine.
(I'm usually building out of source directory and did something wrong...)
Now I'm testing the current v5.10.82
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #83 from kolAflash (kolafl...@kolahilft.de) ---
Hi James,
(In reply to James Zhu from comment #82)
> [...]
> $ grep -rn "amdgpu_amdkfd.h\|kgd2kfd_resume_iommu"
> drivers/gpu/drm/amd/amdkfd/kfd_device.c
> 31:#include
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #82 from James Zhu (jam...@amd.com) ---
Hi @kolAflash,
I don't have issue with your .config. on ubuntu 20.04
>From source code, it should be fine.
$ grep -rn "kgd2kfd_resume_iommu" drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #81 from kolAflash (kolafl...@kolahilft.de) ---
Created attachment 299721
--> https://bugzilla.kernel.org/attachment.cgi?id=299721=edit
Linux kernel make .config
@James
Compiling v5.10.80 (f884bb85b8d877d4e0c670403754813a7901705b)
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #80 from James Zhu (jam...@amd.com) ---
Hi @kolAflash,
I applied those patches on
(https://github.com/gregkh/linux.git linux-5.10.y
f884bb85b8d877d4e0c670403754813a7901705b)
(https://github.com/gregkh/linux.git linux-5.12.y
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #79 from kolAflash (kolafl...@kolahilft.de) ---
@James
Got this when compiling with Linux-5.10.81:
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device.c: In function
‘kgd2kfd_device_init’:
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #78 from kolAflash (kolafl...@kolahilft.de) ---
(In reply to James Zhu from comment #77)
> Created attachment 299697 [details]
> backport patch for 5.10 stable.
>
> Hi @kolAflash, before I send out them to public for review,. could
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #77 from James Zhu (jam...@amd.com) ---
Created attachment 299697
--> https://bugzilla.kernel.org/attachment.cgi?id=299697=edit
backport patch for 5.10 stable.
Hi @kolAflash, before I send out them to public for review,. could you
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #76 from Alex Deucher (alexdeuc...@gmail.com) ---
(In reply to James Zhu from comment #75)
> (In reply to kolAflash from comment #74)
> > @James Zhu
> >
> > Tested 5.15.2 for over a week and more than 50 standby-wakeups.
> > No
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #75 from James Zhu (jam...@amd.com) ---
(In reply to kolAflash from comment #74)
> @James Zhu
>
> Tested 5.15.2 for over a week and more than 50 standby-wakeups.
> No problems!
> Thanks :-)
>
> I would be happy about a patch for the
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #74 from kolAflash (kolafl...@kolahilft.de) ---
@James Zhu
Tested 5.15.2 for over a week and more than 50 standby-wakeups.
No problems!
Thanks :-)
I would be happy about a patch for the 5.10 longterm kernel.
The bug became a problem
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #73 from kolAflash (kolafl...@kolahilft.de) ---
(In reply to Jerome C from comment #72)
> Hi James,
>
> I noticed the patch that you asked us to try from comment 52 were also
> submitted to kernel 5.14.7
>
> tested it, all is good
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #72 from Jerome C (m...@jeromec.com) ---
Hi James,
I noticed the patch that you asked us to try from comment 52 were also
submitted to kernel 5.14.7
tested it, all is good for now
Thanks
Jerome
--
You may reply to this email to
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #71 from youling...@gmail.com ---
(In reply to James Zhu from comment #70)
> My mistaake. Can you try add pci=noats in boot parameters?
no help, still resume failed.
--
You may reply to this email to add a comment.
You are
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #70 from James Zhu (jam...@amd.com) ---
My mistaake. Can you try add pci=noats in boot parameters?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #69 from youling...@gmail.com ---
(In reply to James Zhu from comment #67)
> (In reply to youling257 from comment #66)
> > resume failed record video,
> > https://drive.google.com/drive/folders/1bWMC4ByGvudC9zBk-9Xgamz-
> >
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #68 from youling...@gmail.com ---
(In reply to James Zhu from comment #67)
> (In reply to youling257 from comment #66)
> > resume failed record video,
> > https://drive.google.com/drive/folders/1bWMC4ByGvudC9zBk-9Xgamz-
> >
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #67 from James Zhu (jam...@amd.com) ---
(In reply to youling257 from comment #66)
> resume failed record video,
> https://drive.google.com/drive/folders/1bWMC4ByGvudC9zBk-9Xgamz-
> shir0pqX?usp=sharing
Can you try apply this patch:
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #66 from youling...@gmail.com ---
resume failed record video,
https://drive.google.com/drive/folders/1bWMC4ByGvudC9zBk-9Xgamz-shir0pqX?usp=sharing
--
You may reply to this email to add a comment.
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #65 from youling...@gmail.com ---
(In reply to James Zhu from comment #63)
> (In reply to youling257 from comment #62)
> > (In reply to James Zhu from comment #61)
> > > (In reply to youling257 from comment #60)
> > > > Created
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #64 from youling...@gmail.com ---
Created attachment 298899
--> https://bugzilla.kernel.org/attachment.cgi?id=298899=edit
config-5.15.0-rc2-android-x86_64+
CONFIG_HSA_AMD=y
--
You may reply to this email to add a comment.
You
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #63 from James Zhu (jam...@amd.com) ---
(In reply to youling257 from comment #62)
> (In reply to James Zhu from comment #61)
> > (In reply to youling257 from comment #60)
> > > Created attachment 298889 [details]
> > > dmesg5.15.txt
>
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #62 from youling...@gmail.com ---
(In reply to James Zhu from comment #61)
> (In reply to youling257 from comment #60)
> > Created attachment 298889 [details]
> > dmesg5.15.txt
> >
> > (In reply to James Zhu from comment #59)
> > >
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #61 from James Zhu (jam...@amd.com) ---
(In reply to youling257 from comment #60)
> Created attachment 298889 [details]
> dmesg5.15.txt
>
> (In reply to James Zhu from comment #59)
> > (In reply to youling257 from comment #58)
> > >
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #60 from youling...@gmail.com ---
Created attachment 298889
--> https://bugzilla.kernel.org/attachment.cgi?id=298889=edit
dmesg5.15.txt
(In reply to James Zhu from comment #59)
> (In reply to youling257 from comment #58)
> >
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #59 from James Zhu (jam...@amd.com) ---
(In reply to youling257 from comment #58)
> drm/amdgpu: move iommu_resume before ip init/resume cause suspend to disk
> resume failed on my amdgpu 3400g.
Can you share whole demsg log? Regards!
https://bugzilla.kernel.org/show_bug.cgi?id=211277
youling...@gmail.com changed:
What|Removed |Added
CC||youling...@gmail.com
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #57 from James Zhu (jam...@amd.com) ---
(In reply to Anthony Rabbito from comment #53)
> Thanks for chiming in James! Few things I've observed since adding
> 'pci=noats' the graphic artifacts seem to happen way less. I did observe one
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #56 from Jerome C (m...@jeromec.com) ---
damn, sorry for the ugly message layout replies
I didn't realize my e-mail provider was doing that
--
You may reply to this email to add a comment.
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #54 from Jerome C (m...@jeromec.com) ---
Hi James,
After 900 ( 600 on LLVM, 300 on GCC ) susp/resu using kernel 5.14.1 compiled by
LLVM 12.0.1 ( LLVM\_IAS is unset during compiling ) and again by GCC 11.1.0,
there no crash on resume,
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #55 from Jerome C (m...@jeromec.com) ---
Created attachment 298695
--> https://bugzilla.kernel.org/attachment.cgi?id=298695=edit
signature.asc
--
You may reply to this email to add a comment.
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #53 from Anthony Rabbito (ted...@gmail.com) ---
Thanks for chiming in James! Few things I've observed since adding 'pci=noats'
the graphic artifacts seem to happen way less. I did observe one lockup which
required me to hard shut down
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #52 from James Zhu (jam...@amd.com) ---
Created attachment 298691
--> https://bugzilla.kernel.org/attachment.cgi?id=298691=edit
Fix for S3 hung issue
Hi Jerome and kolAflash,
I think iommu device init is put at wrong place during
https://bugzilla.kernel.org/show_bug.cgi?id=211277
Arham Jain (arhamj...@gmail.com) changed:
What|Removed |Added
CC||arhamj...@gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #50 from James Zhu (jam...@amd.com) ---
Hi Anthony,
Can you try if Comment #37? see if it helps. But from the log that you
attached, it is a different issue that GFX hw has lots of ECC error, which
cause gfx ring time out. after
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #49 from Anthony Rabbito (ted...@gmail.com) ---
Created attachment 298661
--> https://bugzilla.kernel.org/attachment.cgi?id=298661=edit
journalctl of amdgpu trace
(In reply to Anthony Rabbito from comment #48)
--
You may reply to
https://bugzilla.kernel.org/show_bug.cgi?id=211277
Anthony Rabbito (ted...@gmail.com) changed:
What|Removed |Added
CC||ted...@gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #47 from James Zhu (jam...@amd.com) ---
Hi Jerome,
Thanks! I knew this issue is not easy to judge if it is fixed. Since it
occurred quite randomly. On my setup, this WA passed 5 times up to 300
suspend/resume cycles, 1 time up to 3800
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #45 from Jerome C (m...@jeromec.com) ---
Unfortunately this failed after 138 susp/resu
Thanks
Jerome
On 02/09/2021 22:24, bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=211277
>
> ---
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #44 from James Zhu (jam...@amd.com) ---
Created attachment 298651
--> https://bugzilla.kernel.org/attachment.cgi?id=298651=edit
A workaround for suspend/resume hung issue
The VCN block passed all ring tests, usually the vcn will
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #43 from kolAflash (kolafl...@kolahilft.de) ---
(In reply to James Zhu from comment #42)
> Hi Jerome and kolAflash,
>
> Thanks for confirmation. I have a workaround for this issue. But I wish I
> can find the root cause or better
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #42 from James Zhu (jam...@amd.com) ---
Hi Jerome and kolAflash,
Thanks for confirmation. I have a workaround for this issue. But I wish I can
find the root cause or better workaround.
James
--
You may reply to this email to add a
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #41 from kolAflash (kolafl...@kolahilft.de) ---
I can confirm Jeromes result.
Bug is gone with pci=noats.
(Debian-11 kernel 5.10.0-8-amd64)
I ran 50 suspend/standby rounds.
Also I used the notebook for 2 days and suspended it
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #40 from James Zhu (jam...@amd.com) ---
Hi Jerome,
Yes, you are right.Turning off ats will affect iommu. KFD needs iommu enable.
KFD supports computing engine. It won't affect 3D and video acceleration. After
I confirm if ats/iommu
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #38 from Jerome C (m...@jeromec.com) ---
Hi James,
With "pci=noats" set the suspension and resume works fine
I did see some errors ( something about device not added ) in the kernel
log from "kfd" but I guess that's related to PCIe
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #37 from James Zhu (jam...@amd.com) ---
HiJerome and kolAflash,
would you mind base on your original test configuration,and add pci=noats in
boot parameter? for example:
linux /boot/vmlinuz-5.4.0-54-generic
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #36 from Jerome C (m...@jeromec.com) ---
I've been watching linux-next and noticed that this commit
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #35 from kolAflash (kolafl...@kolahilft.de) ---
Created attachment 298193
--> https://bugzilla.kernel.org/attachment.cgi?id=298193=edit
/var/log/kern.log running amd-drm-next-5.14-2021-05-12 (ae30d41eb) with Xorg
Sorry for the long
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #34 from Jerome C (m...@jeromec.com) ---
Using 5.13.0 now and the issue is still here
(In reply to kolAflash from comment #32)
> Created attachment 296901 [details]
> dmesg via SSH, running amd-drm-next-5.14-2021-05-12 without
>
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #33 from Jerome C (m...@jeromec.com) ---
(In reply to kolAflash from comment #32)
> In the meanwhile I performed test number 2.
>
> > 2. amd-drm-next-5.14-2021-05-12* without ip_block_mask=0x0ff, with Xorg
> [...]
>
> This time the
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #32 from kolAflash (kolafl...@kolahilft.de) ---
Created attachment 296901
--> https://bugzilla.kernel.org/attachment.cgi?id=296901=edit
dmesg via SSH, running amd-drm-next-5.14-2021-05-12 without ip_block_mask=0x0ff
and with Xorg
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #31 from Jerome C (m...@jeromec.com) ---
(In reply to kolAflash from comment #30)
> Created attachment 296891 [details]
> all kernel messages with ip_block_mask=0x0ff (Debian kernel 5.10.0-6)
>
> Also crashes with ip_block_mask=0x0ff
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #30 from kolAflash (kolafl...@kolahilft.de) ---
Created attachment 296891
--> https://bugzilla.kernel.org/attachment.cgi?id=296891=edit
all kernel messages with ip_block_mask=0x0ff (Debian kernel 5.10.0-6)
Also crashes with
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #29 from James Zhu (jam...@amd.com) ---
Hi Jeromec,I think debug turn-on changes a little bit timing. log without debug
info can't give me any help. The amdgpu_fence_info looks good for all cases.
this issue is possible device
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #28 from Jerome C (m...@jeromec.com) ---
Created attachment 296877
--> https://bugzilla.kernel.org/attachment.cgi?id=296877=edit
AMDGPU fence info
(In reply to James Zhu from comment #27)
> Hi Jeromec, thanks for your feedback, can
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #27 from James Zhu (jam...@amd.com) ---
Hi Jeromec, thanks for your feedback, can you also add drm.debug=0x1ff
modprobe? I need log: case 1 dmesg and
/sys/kernel/debug/dri/0/amdgpu_fence_info (if you can). James.
--
You may reply to
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #26 from Jerome C (m...@jeromec.com) ---
(In reply to Jerome C from comment #25)
> I forgot to mention... I'm on kernel 5.13.4
5.12.4 I mean
--
You may reply to this email to add a comment.
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #25 from Jerome C (m...@jeromec.com) ---
I forgot to mention... I'm on kernel 5.13.4
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #24 from Jerome C (m...@jeromec.com) ---
(In reply to James Zhu from comment #21)
> Hi Jeromec, to isolate the cause, can you help run two experiments
> separately?
> 1. To run suspend/resume without launching Xorg, just on text mode.
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #23 from James Zhu (jam...@amd.com) ---
Hi kolAflash,
VCN IP is for video acceleration(for video playback), if vcn ip didn't handle
suspend/resume process properly, we do observe other IP blocks be affected. For
your case it is
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #22 from kolAflash (kolafl...@kolahilft.de) ---
@James
What do you mean by video acceleration?
Is this about 3D / DRI acceleration like in video games?
Or do you mean just "video" playback (movie, mp4, webm, h264, vp8, ...)
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #21 from James Zhu (jam...@amd.com) ---
Hi Jeromec, to isolate the cause, can you help run two experiments separately?
1. To run suspend/resume without launching Xorg, just on text mode.
2. To disable video acceleration (VCN IP). I
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #20 from Jerome C (m...@jeromec.com) ---
(In reply to James Zhu from comment #19)
> Created attachment 296841 [details]
> to fix suspend/resume hung issue
>
> Hi @kolAflash and @jeromec, Can you help check if this patch can fix the
>
https://bugzilla.kernel.org/show_bug.cgi?id=211277
jam...@amd.com (jam...@amd.com) changed:
What|Removed |Added
CC||jam...@amd.com
---
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #18 from Jerome C (m...@jeromec.com) ---
(In reply to Alex Deucher from comment #17)
> I don't think we've been able to reproduce it. That said, we did double
> check the programmign sequences and I believe it may be fixed with these
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #17 from Alex Deucher (alexdeuc...@gmail.com) ---
I don't think we've been able to reproduce it. That said, we did double check
the programmign sequences and I believe it may be fixed with these patches:
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #16 from kolAflash (kolafl...@kolahilft.de) ---
@Alex
Any progress on this?
If there's no perfect way to fix this, what about an option to turn on/off this
behaviour?
A module option that can be changed at runtime would be ideal.
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #15 from kolAflash (kolafl...@kolahilft.de) ---
(In reply to Alex Deucher from comment #10)
> Can you bisect?
> https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html
I've done several s2ram-wakeup cycles (100 automatic
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #14 from kolAflash (kolafl...@kolahilft.de) ---
(In reply to Jerome C from comment #13)
I don't get how you got to your results.
There's no straight path from 5.10.4 to 5.11-rc5, as they are on different
branches (5.10.y and master).
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #13 from Jerome C (m...@jeromec.com) ---
(In reply to kolAflash from comment #12)
> I've tried doing a bisect using this script. Unfortunately I couldn't
> reproduce the bug this way. So I bisecting will take a lot longer.
>
> for i
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #12 from kolAflash (kolafl...@kolahilft.de) ---
I've tried doing a bisect using this script. Unfortunately I couldn't reproduce
the bug this way. So I bisecting will take a lot longer.
for i in {0..19}; do
echo -e "\n${i}"
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #11 from kolAflash (kolafl...@kolahilft.de) ---
(In reply to Alex Deucher from comment #10)
> Can you bisect?
> https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html
I will try to.
But it will definitely need some time
https://bugzilla.kernel.org/show_bug.cgi?id=211277
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #9 from kolAflash (kolafl...@kolahilft.de) ---
I'm on Linux-5.7 now since 2021-01-26.
And I woke up the notebook at least once a day since then.
So it's clearly a regression in the kernel somewhere between 5.7 and 5.10 and
probably
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #8 from Jerome C (m...@jeromec.com) ---
I've tried kernel 5.11-rc5 and same issue occurs there.
For now I've downgraded kernel to 5.9.14 ( will update it to 5.9.16 ) until
this issue is fixed
What I've mentioned in comment 4 isn't
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #7 from Jerome C (m...@jeromec.com) ---
ok, you have it turned off already
Weird thing happened this morning... I woke my laptop up and it was slow screen
updates... I just closed my laptop lid, frustrated... I noticed it suspended
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #6 from kolAflash (kolafl...@kolahilft.de) ---
(In reply to Jerome C from comment #4)
> [...]
> Do you have kernel parameter set "init_on_free=1" or in your kernel config
> "CONFIG_INIT_ON_FREE_DEFAULT_ON=y", [...]
I'm using the
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #5 from Jerome C (m...@jeromec.com) ---
Created attachment 294879
--> https://bugzilla.kernel.org/attachment.cgi?id=294879=edit
Kernel log
Unfortunately it crashed again although I've noticed it's been crashing a lot
less (4-5
https://bugzilla.kernel.org/show_bug.cgi?id=211277
Jerome C (m...@jeromec.com) changed:
What|Removed |Added
CC||m...@jeromec.com
---
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #3 from kolAflash (kolafl...@kolahilft.de) ---
I searched through my journalctl log.
I set up the whole system in May 2020 with Linux-5.6.7.
(journalctl has everything back to that date)
The bug appeared as following since October
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #2 from kolAflash (kolafl...@kolahilft.de) ---
Created attachment 294749
--> https://bugzilla.kernel.org/attachment.cgi?id=294749=edit
BIOS update history (just in case someone has a clue if something looks
suspicios and this might
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #1 from kolAflash (kolafl...@kolahilft.de) ---
Created attachment 294747
--> https://bugzilla.kernel.org/attachment.cgi?id=294747=edit
kern.log
--
You may reply to this email to add a comment.
You are receiving this mail because:
86 matches
Mail list logo
