June 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sb56637(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(sb56637(a)gmail.com | |) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- You can try to build the kernel based on the config of Clear Linux manually on TW and see whether you get the given performance boost. If not, it's a user-space problem. Install linux git repo on the running Clear Linux system, set up the compiler and other tool chains, and run "make localmodconfig". You might need to catch up more via "make oldconfig". Change the CONFIG_LOCAL_VERSION string not to conflict with the existing one, make, and install the kernel, and confirm that the system works. Then you can copy the .config file from there to TW, and build again there in a similar step. -- You are receiving this mail because: You are the assignee for the bug.

2 years, 1 month

1
0
0 0

[kernel-bugs] [Bug 1172901] Kernel - AMD-Vi: Unable to read/write to IOMMU perf counter.

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1172901 https://bugzilla.suse.com/show_bug.cgi?id=1172901#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Assignee|kernel-bugs(a)opensuse.org |jroedel(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Joerg, could you take a look? -- You are receiving this mail because: You are the assignee for the bug.

2 years, 1 month

1
0
0 0

[kernel-bugs] [Bug 1172905] Kernel 5.7.1 does not boot

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1172905 https://bugzilla.suse.com/show_bug.cgi?id=1172905#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |p.stolz77(a)googlemail.com, | |tiwai(a)suse.com Flags| |needinfo?(p.stolz77@googlem | |ail.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Do you get any crash trace or such if you boot without quiet option? Also try to remove splash=silent, too. And, please boot with the old working kernel, and get hwinfo output from there, and attach to Bugzilla. Give the dmesg output from the working kernel, too. -- You are receiving this mail because: You are the assignee for the bug.

2 years, 1 month

1
0
0 0

[kernel-bugs] [Bug 1172901] New: Kernel

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1172901 Bug ID: 1172901 Summary: Kernel Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rahmspinat(a)gmx.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0 Build Identifier: On Lenovo Laptop with Ryzen APU I get the message during boot: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter. (dmsg | grep IOMMU) Reproducible: Always Steps to Reproduce: Hardware for reproducing is needed. Actual Results: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter. Expected Results: pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40 perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank). The expected result I got when booting Ubuntu 20.04. Seems to be that a certain parameter in kernel config needs to be set. -- You are receiving this mail because: You are the assignee for the bug.

2 years, 1 month

1
1
0 0

[kernel-bugs] [Bug 1172900] New: Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1172900 Bug ID: 1172900 Summary: Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838777 --> http://bugzilla.opensuse.org/attachment.cgi?id=838777&action=edit lots of screenshots and terminal outputs Hi there, the pandemic has forced a lot of users to spend much more time in videoconferencing apps, which in turn has given more exposure to some of the inefficiencies in the Linux graphics stack. I've been fighting with Jitsi Meet via Firefox and Zoom making my laptop so hot that the fans go full speed, and it smells and feels hot. It's an all-Intel components Thinkpad T530. I also observe even higher CPU loads but slightly less palpable heat on my secondary Thinkpad T440s, also with all-Intel components. And of course, with the addtional CPU load comes much shorter battery life. I've also extensively tested other mainstream distros like the most recent Ubuntu, Fedora, and Manjaro releases with similar results, but since Tumbleweed is the one I actually want to use on this laptop I'm reporting this bug here. As a last resort, I tried Clear Linux on the Thinkpad T530, since I heard Clear was optimized for Intel hardware. Surprisingly, it reported drastically lower CPU load and generally lower heat readings. And to the touch/smell the machine was obviously cooler and less stressed. The Firefox CPU load with Jitsi under Clear Linux was similar to what I have observed under Windows 8 on my Thinkpad T440s laptop. I retested several times in Clear under Gnome (Xorg session), and then several times more on my daily driver installed openSUSE Tumbleweed system with KDE Plasma (Xorg) and Openbox, and then I confirmed the excess CPU usage with a Tumbleweed live USB running Gnome on Xorg and Wayland. I'm attaching a tarball of all my findings, since there are a lot of files. The filenames describe what OS and what applications are running. The Zoom test was with a simple 2 user meeting with first video and then screensharing. The Jitsi test was performed with just 2 users with video enabled on a fresh Firefox profile. I'm attaching Firefox's support output and Zoom's terminal output, as well as the loaded kernel modules. I'm also attaching the hwinfo for my Thinkpad T530, but I don't think it's particularly relevant because I have observed the same CPU loads with the same apps on all the other laptops I own running Linux. Please let me know if you need any other information, I'd be glad to help troubleshoot. I'm not really an expert on the graphics stack in Linux, but I have tried to follow the Arch Wiki guidelines for enabling VA-API, and I've tried tons of options in about:config for Firefox on my installed openSUSE TW system. I'm sure it has packages installed that aren't present on the TW live Gnome system I booted, which is probably the reason for the differences in CPU load and temperature between the two systems. But both are drastically worse than Clear Linux straight out-of-the-box. Any ideas on what Clear Linux is doing differently? Is it just the result of thousands of little tweaks and optimizations, or is there some major configuration or compile flag in the graphics stack that Clear is using that could be applied to Tumbleweed? Thanks a lot for the help. -- You are receiving this mail because: You are the assignee for the bug.

2 years, 1 month

1
0
0 0

[kernel-bugs] Your Bugzilla bug list needs attention.

by bugzilla_noreply＠suse.com

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! Harmonize kernel modules in JeOS leap 15.1 with TW and leap 15.2 -> http://bugzilla.suse.com/show_bug.cgi?id=1166342 test bug for assignee change -> http://bugzilla.suse.com/show_bug.cgi?id=1172181 Support for 64-bot processors on motherboards with 32-bit UEFI -> http://bugzilla.suse.com/show_bug.cgi?id=1172292 usb message shown on console even with "quiet splash=silent" -> http://bugzilla.suse.com/show_bug.cgi?id=1172322 -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

2 years, 1 month

1
0
0 0

[kernel-bugs] [Bug 1172886] New: Kernel 4.12.14-lp151.28.52-default is unable to start on some hardware

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1172886 Bug ID: 1172886 Summary: Kernel 4.12.14-lp151.28.52-default is unable to start on some hardware Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ae(a)ae-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838763 --> http://bugzilla.opensuse.org/attachment.cgi?id=838763&action=edit Screenshot of Kernelpanic Kernelpanic with Linux mail 4.12.14-lp151.28.52-default #1 SMP Wed Jun 10 15:32:08 UTC 2020 (464fb5f) x86_64 x86_64 x86_64 GNU/Linux Kernel Linux mail 4.12.14-lp151.28.48-default #1 SMP Fri Apr 17 05:38:36 UTC 2020 (18849d1) x86_64 x86_64 x86_64 GNU/Linux works fine. I can only add a picture from the root server. -- You are receiving this mail because: You are the assignee for the bug.

2 years, 1 month

1
6
0 0

[kernel-bugs] [Bug 1172741] perf fails to build on aarch64 and armv7/6

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1172741 Tony Jones <tonyj(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |tonyj(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

2 years, 1 month

1
0
0 0

[kernel-bugs] [Bug 1172741] perf fails to build on aarch64 and armv7/6

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1172741 https://bugzilla.suse.com/show_bug.cgi?id=1172741#c3 --- Comment #3 from Tony Jones <tonyj(a)suse.com> --- (In reply to Takashi Iwai from comment #2) > Pushed the fix to master/for-next branch. Wrong. We don't collect perf patches in the kernel tree. Please revert and leave perf stuff to me. Thanks! -- You are receiving this mail because: You are the assignee for the bug.

2 years, 1 month

1
0
0 0

[kernel-bugs] [Bug 1172741] perf fails to build on aarch64 and armv7/6

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1172741 https://bugzilla.suse.com/show_bug.cgi?id=1172741#c2 --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Pushed the fix to master/for-next branch. -- You are receiving this mail because: You are the assignee for the bug.

2 years, 1 month

1
0
0 0

2022

2021

2020

openSUSE Kernel Bugs June 2020