[Kernel-packages] [Bug 1727136] Re: [GLIBC] Fix glibc AVX frequency problems

2020-05-18 Thread roots
Addendum to the previous comment: glibc version is 2.31-0ubuntu9. -- 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/1727136 Title: [GLIBC] Fix glibc AVX frequency problems Status in

[Kernel-packages] [Bug 1727136] Re: [GLIBC] Fix glibc AVX frequency problems

2020-05-18 Thread roots
I'm having the same issue with Ubuntu 20.04, linux 5.4.0-31-generic: user@linux:~$ sudo perf stat -e cpu/event=0x28,umask=0x18,name=core_power_lvl1_turbo_license/,cpu/event=0x28,umask=0x20,name=core_power_lvl2_turbo_license/,cpu/event=0x28,umask=0x40,name=core_power_throttle/,cycles -a -I 1000

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

2017-01-19 Thread roots
Maybe some symptoms with my old mainboard will be helpful for general debugging this issue: -The drive was *sometimes* recognised fine at boot in first place, showed with "lspci" and "nvme list" would give me correct output -After boot, the drive would go "missing" after a duration of approx. 5

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

2017-01-19 Thread roots
Dan, unfortunately I can't, as the bug won't show up with my new mainboard anymore, that's why I suspected it to be chipset-specific (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/comments/36). roots. -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

2017-01-15 Thread roots
@All: In the meantime, I've switched to a different motherboard, where the issue does not occur _within linux_ anymore (with none of the default Ubuntu Kernels (4.4.0-53, -57, -59, 4.8.0-32 and 4.9.0 from the mainline ppa). This applies for both the NVME SSD being hooked to a PCIe-Slot (via

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

2017-01-15 Thread roots
@Wayne Scott: I succeeded in catching some of those scrolling screen messages (for another issue) by filming the screen output with my mobile phone. However, I had to set a high recording framerate (50 or 60Hz). -- You received this bug notification because you are a member of Kernel Packages,

[Kernel-packages] [Bug 1641322] Re: frequently lost connection to nvme

2016-12-24 Thread roots
Hmmm...unfortunately there's no such thing for my mainboard :-| However, thanks and please keep us posted! Happy holidays for you, too! r. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1641322] Re: frequently lost connection to nvme

2016-12-24 Thread roots
Hi, I'm having the same issue with Xenial and various kernels I've tested. Did you find any solution or workaround to this issue yet? Thanks, r. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

2016-12-24 Thread roots
Hi, I second Stephanes post: Please set this bug to NOT FIXED - I'm having this issue with Ubuntu 16.04, Kernels 4.4.0-53, -57, -58 and 4.9.0. Drive is a Samsung 960 Pro M2 SSD on a PCIe-M2 - Adapter hooked to a PCIe16x slot, Gigabyte GA-Z77X-UD3H mobo. [0.715691] nvme0n1: p1 [ 171.849770]

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

2016-12-24 Thread roots
Please mark as OPEN, see my post below. Thanks. -- 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/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Fix Released

[Kernel-packages] [Bug 1315669] Re: Kernel Panic caused by pulseaudio

2014-05-30 Thread roots
Thanks for your answer and sorry for the late feedback. This weird bug/panic disappeared after switching from nonfree Catalyst to free radeon driver. Even when using Catalyst again, the bug does not reappear. So Dave seems to be right, thanks for the pointers. However I still don't understand the