[Kernel-packages] [Bug 2043320] [NEW] perf top error: "The cycles:P event is not supported" on 13th gen / raptor lake

Public bug reported: `perf top` immediately fails to start for me, 6.5 on i9-13900kf, with the error: The cycles:P event is not supported. `perf record` and `perf stat` appear to work fine, including `perf stat` showing the two different sets of counters for cpu_core and cpu_atom. Looking at

[Kernel-packages] [Bug 1718897] Re: perf broken on 4.13.0-11-generic (artful): libbfd-2.29-system.so: cannot open shared object file: No such file or directory

Yes, symlinking: ln -s libbfd-2.29.1-system.so libbfd-2.29-system.so .. does fix the problem. -- 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/1718897 Title: perf broken on

[Kernel-packages] [Bug 1702056] Re: perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open share

I have "reopened" this bug as: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718897 , as it still fails for me (a month later). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1718897] [NEW] perf broken on 4.13.0-11-generic (artful): libbfd-2.29-system.so: cannot open shared object file: No such file or directory

Public bug reported: perf fails to start on my Artful install. This bug is very similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702056 ... which was marked "fix released" a month ago. I do not have "-proposed" enabled. Full error: faux@astoria:~% perf

[Kernel-packages] [Bug 1696665] Re: Boot wedges on 4.10.0-22 but not on -21

It's somewhere in: * e8f09b159634 - (refs/bisect/bad) drm/fb-helper: Allow var->x/yres(_virtual) < fb->width/height again (3 weeks ago) * 62dd80f54582 - drm/etnaviv: fix missing unlock on error in etnaviv_gpu_submit() (3 weeks ago) * 1611347ef50a - (HEAD) drm/nouveau: initial support

[Kernel-packages] [Bug 1696665] Re: Boot wedges on 4.10.0-22 but not on -21

Bisecting. Trying a single boot only because it appears 100% reproducible. Famous last words. # bad: [0077e0558cc53950b2d5cd9458641443161ca7db] x86/signals: Fix lower/upper bound reporting in compat siginfo # good: [c0cf63ef356bab81f71fd9e3a00a9c731f9ec680] UBUNTU: SAUCE: PCI: Apply the new

[Kernel-packages] [Bug 1696665] Re: Boot wedges on 4.10.0-22 but not on -21

I tried the Ubuntu mainline builds. The bug happens on mainline 4.10.12 (and 13, and 15, and 17..), but not on 4.10.11. This tallies well with the Ubuntu versions, where 11 is before -22, and 12 is after. The failure on 4.10.12-mainline is attached. Linux version 4.10.12-041012-generic

[Kernel-packages] [Bug 1696665] [NEW] Boot wedges on 4.10.0-22 but not on -21

Public bug reported: After a kernel update, the machine wedges during late boot. Symptoms: * lightdm never gets a chance to start because things like gpu-manager are wedged, and must start before it * gpu-manager uses 100% cpu * sudo / ip / anything that uses netlink hangs forever and can't

[Kernel-packages] [Bug 1462432] [NEW] 100% reproducible segfault clicking detect displays

Public bug reported: When I click Detect displays, nvidia-settings segfaults. The nvidia driver doesn't seem particularly happy with having more than one monitor attached anyway (weird flashing during boot), but it does work if configured manually with xrandr. i3wm without gnome-session or any

[Kernel-packages] [Bug 1270818] [NEW] nouveau(?) breaks or hangs in 3.13.0-4, -2, but not -1 on GK107GLM [Quadro K2000M]

Public bug reported: HP EliteBook 8570w with an NVIDIA GK107GLM [Quadro K2000M]. 3.13.0-4: hardlock late in the boot process (no sysrq or hardware button responses). 3.13.0-2: Gets into X / lightdm / Gnome 3, but only supported resolutions are 800x600 and 1024x768, no multi-mon support etc.; I