Attach log captured with v5.6-rc7. However, without hardware console,
there is no any information dumped when system is trying suspend. This
is quite critical for debugging suspend/resume problems.
** Attachment added: "dmesg.5.6.0-050600rc7-generic.drm-debug"
https://bugs.launchpad.net/oem-pr
Attach log captured with v5.6-rc7. However, without hardware console,
there is no any information dumped when system is trying suspend. This
is quite critical for debugging suspend/resume problems.
** Attachment added: "dmesg.5.6.0-050600rc7-generic.drm-debug"
https://bugs.launchpad.net/oem-pr
cpu family : 6
model : 142
model name : Intel(R) Core(TM) i3-8130U CPU @ 2.20GHz
stepping: 10
microcode : 0xca
** Attachment added: "cpuinfo"
https://bugs.launchpad.net/oem-priority/+bug/1857883/+attachment/5340834/+files/cpuinfo
--
You received this bug not
> Is there any comment on why this issue only happened on the config
from customer, but not on our configs.
I would recommend to compare CPU stepping, perhaps a regression only
present in later CPU stepping after pre-production samples.
--
You received this bug notification because you are a mem
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2020-01-07/
** Attachment added: "drm-tip kernel 2020-01-07 dmesg with drm.debug=0xe"
https://bugs.launchpad.net/oem-priority/+bug/1857883/+attachment/5318763/+files/dmesg.5.5.0-994-generic.drm-debug
--
You received this bug notification
** Summary changed:
- system failed to suspend
+ i915 DMS firmware kbl_dmc_ver1_{01,04}.bin hang system during suspend
** Attachment added: "mainline kernel v5.5-rc5 dmesg with drm.debug=0xe"
https://bugs.launchpad.net/oem-priority/+bug/1857883/+attachment/5318762/+files/dmesg.5.5.0-050500rc5
