[Bug 211277] sometimes crash at s2ram-wake (Ryzen 3500U): amdgpu, drm, commit_tail, amdgpu_dm_atomic_commit_tail

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=211277

--- Comment #65 from youling257@xxxxxxxxx ---
(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 attachment 298889 [details]
> > > > dmesg5.15.txt
> > > > 
> > > > (In reply to James Zhu from comment #59)
> > > > > (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! James
> > > > 
> > > > when resume failed have to force shutdown, how to output dmesg?
> > > > only has boot log dmesg.
> > > 
> > > after reboot, you can find under /var/log/kern.log and /var/log/syslog
> > based
> > > on timestamp. you can just attach kern.log
> > 
> > my userspace is androidx86, running androidx86 with linux 5.15 and mesa21
> on
> > amdgpu, no /var/log.
> > git bisect linux kernel 5.15rc1 and rc2, bad commit is drm/amdgpu: move
> > iommu_resume before ip init/resume.
> 
> Can you check CONFIG_HSA_AMD setting in .config? By the way , see if the
> below link help you dump the  error message during resume.
> https://stackoverflow.com/questions/9682306/android-how-to-get-kernel-logs-
> after-kernel-panic

do you see my dmesg kernel command line "memmap=1M!5M ramoops.mem_size=1048576
ramoops.ecc=1 ramoops.mem_address=0x00500000 ramoops.console_size=16384
ramoops.ftrace_size=16384 ramoops.pmsg_size=16384 ramoops.record_size=32768".

if kernel panic reboot, can get /sys/fs/pstore/console-ramoops-0 and
/sys/fs/pstore/pmsg-ramoops-0.
but when resume failed, have to press power button force shutdown, no anything.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.



[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux