The upstream bug tracker says "Please use your distribution's bug
tracking tools. This bugzilla is for reporting bugs against upstream
Linux kernels. If you did not compile your own kernel from scratch, you
are probably in the wrong place."
Since I'm not using an upstream kernel, I'm not planning
Public bug reported:
With package linux-tools-6.5.0-45-generic, perf will reproducibly
segfault on startup:
$ SYSFS_PATH=/nonexistent perf record /bin/echo
Failed to read max cpus, using default of 4096
libperf: Miscounted nr_mmaps 0 vs 1
WARNING: No sample_id_all support, falling back to unorder
This is sporadically reproducible for me. It's probably a hardware
quirk. I have Ubuntu 20.04 with Linux 5.4.0-37-generic. I'm using a
"Microsoft Mobile Mouse 4000" which presents itself as 045e:07b2
"Microsoft Corp. 2.4GHz Transceiver v8.0 used by mouse Wireless Desktop
900". The issue only occurs
Sorry about not finishing the bisection. I was dubious about the
prospect of finding a nice clean patch to cherry pick in that drm-intel
branch. But this is superseded now by the upgrade of linux-generic-
hwe-16.04 to 4.15, which does not have the same issue.
I recommend closing this bug as fixed,
In other words, I'd like packaged kernels for
2d62c799f8ffac4f7ffba6a4e7f148827dfc24c7 and
5771a8c08880cdca3bfb4a3fc6d309d6bba20877 . The expectation is that that
will confirm that the fix came from drm-intel. Assuming that's confirmed
then we would have to do a bisection of the drm-intel-next bran
b9c55b6e2cc4369b0688961fa5de0e057f3ec0c4: fixed
I noticed that in the broken kernel, plymouth does not switch on the
external monitor. Normally plymouth shows a cloned display.
Looking at the remaining commits, there was a merge of tag "drm-intel-
next-2017-07-17" which had a very large number of
e5fa05b96b02f45a91a364d2121451a4da05cd84: fixed
I discovered that the issue is not reproducible with the external
monitor unplugged, i.e. the trigger seems to be lightdm starting in dual
monitor mode. That invalidates the test I did at
bf1d6b2c76eda86159519bf5c427b1fa8f51f733 , which I think was w
e5fa05b96b02f45a91a364d2121451a4da05cd84: fixed
I discovered that the issue is not reproducible with the external
monitor unplugged, i.e. the trigger seems to be lightdm starting in dual
monitor mode. That invalidates the test I did at
bf1d6b2c76eda86159519bf5c427b1fa8f51f733 , which I think was w
edc2988c548db05e33b921fed15821010bc74895: fixed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1742602
Title:
Blank screen when starting X after upgrading from 4.10 to 4.13.0-26
Status
bf1d6b2c76eda86159519bf5c427b1fa8f51f733: fixed
Curiously, there was a kernel error with this kernel which I don't think
was there before:
[5.505217] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR*
uncleared fifo underrun on pipe A
[5.505308] [drm:intel_cpu_fifo_underrun_irq_h
aae3dbb4776e7916b6cd442d00159bea27a695c1: fixed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1742602
Title:
Blank screen when starting X after upgrading from 4.10 to 4.13.0-26
Status
aae3dbb4776e7916b6cd442d00159bea27a695c1: fixed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1742602
Title:
Blank screen when starting X after upgrading from 4.10 to 4.13.0-26
Status
4.13.0-041300 (4.13 final): broken
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1742602
Title:
Blank screen when starting X after upgrading from 4.10 to 4.13.0-26
Status in linux pack
4.14-rc1 does fix the issue. So that just leaves 12600 commits to choose
from, according to git log v4.13-rc7..v4.14-rc1. I guess I would need to
recompile the kernel for each bisection iteration? Are we looking for a
drm/i915 commit? There's not quite so many of those (281).
--
You received this
I booted various mainline kernels from http://kernel.ubuntu.com/~kernel-
ppa/mainline/?C=N;O=D
* 4.11.12: works
* 4.12.14: fails
* 4.13.16: fails
* 4.14.2: works
* 4.14.13: works
* 4.15-rc7: works
So it would seem that the issue was introduced upstream in 4.12 and
fixed in 4.14.
--
You received
Here's the packed apport file.
** Attachment added: "apport.linux.2.apport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742602/+attachment/5034906/+files/apport.linux.2.apport
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I ran apport-collect, selected "keep", and edited the resulting file to
remove private information. But I couldn't find any way to upload such a
file to an existing bug report.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Attachment removed: "dmesg"
https://bugs.lau
Public bug reported:
I'm following the HWE kernels in Ubuntu 16.04, so my kernel was upgraded
today from 4.10.0-42 to 4.13.0-26. After rebooting, the splash screen
and disk encryption passphrase prompt showed correctly, but when X
started, the screen went blank. Logs showed everything running as n
18 matches
Mail list logo
