** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+attachment/5370279/+files/journal
** Bug watch added: Red Hat Bugzilla #1506339
https://bugzilla.redhat.com/show_bug.cgi?id=1506339
--
You received this bug notification because you are a member
Possibly related: https://bugzilla.redhat.com/show_bug.cgi?id=1506339
Also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662 which
suggests 5.4.0-rc7-drm-tip-git-g3ff71899c56c works for them
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've had this twice today.
Lost data as a result of walking away for a cup of tea. Came back to a locked
up desktop
May 12 11:18:04 mcp kernel: [drm:pipe_config_mismatch [i915]] *ERROR* mismatch
in pixel_rate (expected 148500, found 296999)
May 12 11:18:04 mcp kernel: [drm:pipe_config_mismatch
I'm running linux-image-5.4.0-30-generic and it happened again last night.
I come back to the machine and see corruption on both external panels, while
internal panel is off. So it does indeed feel like i915 related. Would be happy
to try and get more debug info, but it's hard given the machine
Adding your PPA and getting linux-image-5.4.0-29-generic. Will reboot
and try this over the weekend. I never know how to trigger this, so no
idea if it actually will or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Had this a few more times. Took some time to rummage in the journal and
found this just before it happened.
May 01 10:00:54 mcp kernel: [ cut here ]
May 01 10:00:54 mcp kernel: pipe state doesn't match!
May 01 10:00:54 mcp kernel: WARNING: CPU: 1 PID: 13809 at
This feels very multi-monitor centric.
I have had it numerous times overnight. I have 2 external displays
permanently attached, so 3 displays active in total, at most times. This
is sometimes triggered overnight, probably when a notification comes in
and triggers the displays to wake up.
This
I'm not finding much in the logs. There's some i915 splat which could
possibly be related to the corruption, but nothing to explain the hard
lockup.
The current focal-proposed kernel (5.4.0-24) has some fixes for
races/deadlocks in i915, so it's worth trying that out to see if it
helps. You can
** Attachment added: "bootlog3.log.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+attachment/5349866/+files/bootlog3.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871687
** Attachment added: "bootlog2.log.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+attachment/5349865/+files/bootlog2.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871687
** Attachment added: "bootlog1.log.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+attachment/5349864/+files/bootlog1.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871687
** Attachment added: "bootlog0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+attachment/5349863/+files/bootlog0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871687
12 matches
Mail list logo
