[Kernel-packages] [Bug 1887397] Re: perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1
The same thing happens to me when I'm trying to rebuild Linux 5.7 kernel on debian testing. gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf -I/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf -isystem /home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/include -Wbad-function-cast -Wdeclaration-after-statement -Wformat-security -Wformat-y2k -Winit-self -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wno-system-headers -Wold-style-definition -Wpacked -Wredundant-decls -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wwrite-strings -Wformat -Wstrict-aliasing=3 -Wshadow -DHAVE_ARCH_X86_64_SUPPORT -I/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/arch/x86/include/generated -DHAVE_SYSCALL_TABLE_SUPPORT -DHAVE_PERF_REGS_SUPPORT -DHAVE_ARCH_REGS_QUERY_REGISTER_OFFSET -O6 -fno-omit-frame-pointer -ggdb3 -funwind-tables -Wall -Wextra -std=gnu99 -fstack-protector-all -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/lib/perf/include -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf/util/include -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf/arch/x86/include -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/include/ -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/arch/x86/include/uapi -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/include/uapi -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/arch/x86/include/ -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/arch/x86/ -I/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf//util -I/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/ -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf/util -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf -I/home/zanyrain/r7000-dev/linux-5.7.6/tools/lib/ -DHAVE_SYNC_COMPARE_AND_SWAP_SUPPORT -DHAVE_PTHREAD_ATTR_SETAFFINITY_NP -DHAVE_PTHREAD_BARRIER -DHAVE_EVENTFD -DHAVE_GET_CURRENT_DIR_NAME -DHAVE_GETTID -DHAVE_FILE_HANDLE -DHAVE_DWARF_GETLOCATIONS_SUPPORT -DHAVE_GLIBC_SUPPORT -DHAVE_AIO_SUPPORT -DHAVE_SCHED_GETCPU_SUPPORT -DHAVE_SETNS_SUPPORT -DHAVE_CSTRACE_SUPPORT -DHAVE_LIBELF_SUPPORT -DHAVE_LIBELF_MMAP_SUPPORT -DHAVE_ELF_GETPHDRNUM_SUPPORT -DHAVE_GELF_GETNOTE_SUPPORT -DHAVE_ELF_GETSHDRSTRNDX_SUPPORT -DHAVE_DWARF_SUPPORT -DHAVE_LIBBPF_SUPPORT -DHAVE_BPF_PROLOGUE -DHAVE_JITDUMP -DHAVE_DWARF_UNWIND_SUPPORT -DNO_LIBUNWIND_DEBUG_FRAME -DHAVE_LIBUNWIND_SUPPORT -DHAVE_SLANG_SUPPORT -DHAVE_LIBPERL_SUPPORT -DHAVE_TIMERFD_SUPPORT -DHAVE_LIBPYTHON_SUPPORT -DHAVE_CPLUS_DEMANGLE_SUPPORT -DHAVE_ZLIB_SUPPORT -DHAVE_LZMA_SUPPORT -DHAVE_LIBCAP_SUPPORT -DHAVE_BACKTRACE_SUPPORT -DHAVE_LIBNUMA_SUPPORT -DHAVE_KVM_STAT_SUPPORT -DHAVE_PERF_READ_VDSO32 -DHAVE_PERF_READ_VDSOX32 -DHAVE_LIBBABELTRACE_SUPPORT -DHAVE_AUXTRACE_SUPPORT -I/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/ -Wl,-z,relro -Xlinker --dynamic-list=/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/plugins/libtraceevent-dynamic-list \ /home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/perf-in.o /home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/pmu-events/pmu-events-in.o -Wl,--whole-archive /home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/libapi.a /home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/libtraceevent.a /home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/libsubcmd.a /home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/libperf.a /home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/libbpf.a -Wl,--no-whole-archive -Wl,--start-group -lpthread -lrt -lm -ldl -lopencsd_c_api -lopencsd -lelf -ldw -lunwind-x86_64 -lunwind -llzma -lslang -lperl -ldl -lm -lpthread -lc -lcrypt -lpython3.8 -lcrypt -lpthread -ldl -lutil -lm -lm -lutil -liberty -lz -llzma -lcap -lnuma -lbabeltrace-ctf -Wl,--end-group -o /home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/perf /usr/bin/ld:/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/plugins/libtraceevent-dynamic-list:2: ignoring invalid character `@' in script /usr/bin/ld:/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/plugins/libtraceevent-dynamic-list:2: ignoring invalid character `@' in script /usr/bin/ld:/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/plugins/libtraceevent-dynamic-list:2: syntax error in dynamic list collect2: error: ld returned 1 exit status make[5]: *** [Makefile.perf:629: /home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/perf] Error 1 make[5]: Leaving directory '/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf' make[4]: *** [Makefile.perf:225: sub-make] Error
[Kernel-packages] [Bug 1881996] Re: Enable e1000e S0ix on Tiger Lake
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1881996
Title:
Enable e1000e S0ix on Tiger Lake
Status in HWE Next:
New
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux-oem-5.6 source package in Focal:
Fix Released
Bug description:
[SRU Justfication]
[Impact]
Enable e1000e S0ix on Tiger Lake for OEM-5.6.
[Fix]
Following fixes, currently landed in linux-next, are necessary for
Tiger Lake e1000e S0ix.
* commit 632fbd5eb5b0 ("e1000e: fix S0ix flows for cable connected case")
* commit e086ba2fccda ("e1000e: disable s0ix entry and exit flows for ME
systems")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1881996/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886736] Re: My PC froze, got a black screen multiple times, and locked me out 3 times before I could log back in and use my PC again
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Package changed: linux (Ubuntu) => ubuntu -- 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/1886736 Title: My PC froze, got a black screen multiple times, and locked me out 3 times before I could log back in and use my PC again Status in Ubuntu: Incomplete Bug description: The issue occurred when I was browsing firefox while listening to youtube. The screen froze and stuttered, and then it turned black. Three seconds later, I was thrown back to the login screen. When I logged back in, the mouse was unresponsive and the screen turned black again. This happened 3 times until I was about to "sudo reboot" the machine as I lost control. However, I managed to pull up a terminal and type in ubuntu-bug linux. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 7 21:22:01 2020 InstallationDate: Installed on 2020-07-06 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-06 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions:
[Kernel-packages] [Bug 1878544] Re: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub)
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: Fix Committed => In Progress ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Assignee: koba (kobako) => (unassigned) -- 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/1878544 Title: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub) Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Released Bug description: Asus Zenbook Flip S (UX-370UAR). Intel Core i7-8550U CPU). The X freezes and doesnt even allow to start a console session. Only happening on Ubuntu 18.04 and 20.04. Does not happen in the same computer under Ubuntu 16.04 or Windows 10. Can be replicated easily. Every time I plug/unplug the power USB-C or the USB-c hub. Mostly, on any interaction with the USB-c or I/O ports. If I plug/unplug the USB-c without X in a console session (CTRL+ALT+F3) I get the following: BUG: kernel NULL point dereference, address: 0080 ... Workqueue: events ucsi_connector_change [typec_usci] RIP: 0010:ucsi_displayport_remove_partner+0xe/0x30 [typec_usci] ... Find a picture of the full error attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vks20 1808 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 23:46:49 2020 InstallationDate: Installed on 2020-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. UX370UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=acc6d87c-574b-4c1e-8e8f-e75c1e9ff1fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX370UAR.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX370UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.311:bd10/15/2019:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX370UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886269] Re: ps/2 mouse not working
@Jatinderpal, couldn't get you. So you've reinstalled your system, get upgraded, then is your PS/2 mouse working as expected now? If not, and yet the kernel parameter still works for you, then you may choose not to fix it and carry it forever. Leave this bug in INCOMPLETE state and it will expire after 60 days. -- 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/1886269 Title: ps/2 mouse not working Status in linux package in Ubuntu: Incomplete Bug description: ps/2 mouse not working , gave some command in terminal , this bug came out. See https://ark.intel.com/content/www/us/en/ark/products/39683/intel- desktop-board-dg41rq.html ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 19:25:07 2020 DistUpgraded: 2020-07-03 12:12:10,464 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:d613] InstallationDate: Installed on 2020-06-30 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=7093ceae-5eb7-497e-8809-023c282ce7a1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-07-03 (1 days ago) dmi.bios.date: 01/08/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41RQ dmi.board.vendor: Intel Corporation dmi.board.version: AAE54511-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jul 3 08:17:23 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
** Tags added: hwe-touchpad -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN54WW:bd06/13/2017:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80NV
[Kernel-packages] [Bug 1873594] Re: sporadic black screen freeze on lenovo e595 Ryzen 3700U
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1873594 Title: sporadic black screen freeze on lenovo e595 Ryzen 3700U Status in linux package in Ubuntu: Expired Bug description: Hi, i have sporadic black screen freeze on my lenovo e595 3700U during reboot. The only workaround till now is add "nomodeset" to GRUB_CMDLINE_LINUX_DEFAULT Problem occure also on linux-image-unsigned-5.6.5-050605-generic_5.6.5-050605.202004171629_amd64 and linux-image-unsigned-5.4.28-050428-generic_5.4.28-050428.202003250833_amd64 19.10 was working with 5.0 kernel regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gizzmo 1345 F pulseaudio /dev/snd/controlC1: gizzmo 1345 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Apr 18 21:28:37 2020 InstallationDate: Installed on 2020-04-18 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0bda:b023 Realtek Semiconductor Corp. Bluetooth Radio Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NFCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic root=/dev/mapper/vgkubuntu-root ro nomodeset ip=dhcp RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
Yes, linux-module-extra is needed since all audio driver kernel modules are in this deb. -- 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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05) Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: wayland-session focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
It actually didn't work for me, but that is likely because i did not load linux-modules-extra. THe download link for the deb keeps failing, but I'll try again tomorrow. So please disregard until then. -- 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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05) Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: wayland-session focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN
[Kernel-packages] [Bug 1887473] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Eoan) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed -- 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/1887473 Title: timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. <<>> tag=timer_settime02 stime=1594698491 cmdline="timer_settime02" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s timer_settime02.c:78: INFO: Testing variant: syscall with old kernel spec timer_settime02.c:89: INFO: Testing for setting new_set pointer to NULL: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:89: INFO: Testing for setting tv_nsec to a negative value: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:89: INFO: Testing for setting tv_nsec value too high: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:89: INFO: Testing for passing pointer to invalid timer_id: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
Re: [Kernel-packages] [Bug 1886269] Re: ps/2 mouse not working
Yes please, I tried as you suggested to install new kernel, but the problem was that my system was hacked by some other bug with the name 'kluser', I tried everything but in vain, so I reinstalled system and then kept on upgrading because updating was still hacked by the bug as it was indeed imbedded in the hard drive, then I gave command to reinstall original sound and graphic drivers and the mouse started working. Now I don't know how that happened but I still believe that reminiscence of old bug is there and computer sometimes misbehave. As I have fully upgraded the system with 20FF and keeping that misbehaving also now suggest please should I do it again or not, as my professional work also suffers being my only computer. Thanks a lot. On Mon, 13 Jul, 2020, 13:01 You-Sheng Yang, <1886...@bugs.launchpad.net> wrote: > Please test kernels from > https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1886269 . Before we > may continue to send a fix to upsteam kernel mailing list for review, so > that you don't have to carry that boot parameter, we will need your > confirmation that this fix actually works. > > The PPA may take up to 10 hours from now to complete, but when it's done > please test one of the kernels with: > > 1. remove that grub boot parameter. If you etched that into > /etc/default/grub directly before, please temporarily remove that > parameter and run `sudo update-grub` to sync the generated config. > > 2. Run `sudo add-apt-repository ppa:vicamo/ppa-1886269` to add the > repository. > > 3. Run following command to install ppa kernel: > >$ sudo apt install \ >linux-modules-extra-4.15.0-112-generic=4.15.0-112.113+lp1886269 \ >linux-image-unsigned-4.15.0-112-generic=4.15.0-112.113+lp1886269 \ >linux-headers-4.15.0-112-generic=4.15.0-112.113+lp1886269 \ >linux-headers-4.15.0-112=4.15.0-112.113+lp1886269 > > 4. Reboot and select kernel "4.15.0-112-generic". > > 5. Attach dmesg log here. > > Thank you. > > ** Description changed: > > ps/2 mouse not working , gave some command in terminal , this bug came > out. > + > + See https://ark.intel.com/content/www/us/en/ark/products/39683/intel- > + desktop-board-dg41rq.html > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 > Uname: Linux 4.15.0-109-generic x86_64 > .tmp.unity_support_test.0: > - > + > ApportVersion: 2.20.9-0ubuntu7.15 > Architecture: amd64 > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat Jul 4 19:25:07 2020 > DistUpgraded: 2020-07-03 12:12:10,464 DEBUG Running PostInstallScript: > './xorg_fix_proprietary.py' > DistroCodename: bionic > DistroVariant: ubuntu > GraphicsCard: > - Intel Corporation 4 Series Chipset Integrated Graphics Controller > [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) > -Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics > Controller [8086:d613] > + Intel Corporation 4 Series Chipset Integrated Graphics Controller > [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) > +Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics > Controller [8086:d613] > InstallationDate: Installed on 2020-06-30 (4 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic > root=UUID=7093ceae-5eb7-497e-8809-023c282ce7a1 ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: Upgraded to bionic on 2020-07-03 (1 days ago) > dmi.bios.date: 01/08/2009 > dmi.bios.vendor: Intel Corp. > dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: DG41RQ > dmi.board.vendor: Intel Corporation > dmi.board.version: AAE54511-203 > dmi.chassis.type: 3 > dmi.modalias: > dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr: > version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 > version.libdrm2: libdrm2 2.4.101-2~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.5-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > xserver.bootTime: Fri Jul 3 08:17:23 2020 > xserver.configfile: default > xserver.errors: > - > + > xserver.logfile: /var/log/Xorg.0.log > xserver.outputs: > - > + > xserver.version: 2:1.18.4-0ubuntu0.8 > > -- > You received this bug notification because you are subscribed to the bug > report. >
[Kernel-packages] [Bug 1887469] Re: timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
It looks like a test case issue after commit:
50a2cb874188c ("syscalls: Fix issues around calling syscalls with old timespec")
https://github.com/linux-test-project/ltp/commit/50a2cb874188c89e03501f9d68585d3e256f3fc7
--
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/1887469
Title:
timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other
arches)
And B/E/F s390x as well.
<<>>
tag=timer_settime01 stime=1594697076
cmdline="timer_settime01"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
timer_settime01.c:142: INFO: Testing variant: syscall with old kernel spec
timer_settime01.c:70: INFO: Testing for general initialization:
timer_settime01.c:125: PASS: CLOCK_REALTIME was successful
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:70: INFO: Testing for setting old_value:
timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:70: INFO: Testing for using periodic timer:
timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:70: INFO: Testing for using absolute time:
timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported:
[Kernel-packages] [Bug 1887473] [NEW] timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
Public bug reported: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. <<>> tag=timer_settime02 stime=1594698491 cmdline="timer_settime02" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s timer_settime02.c:78: INFO: Testing variant: syscall with old kernel spec timer_settime02.c:89: INFO: Testing for setting new_set pointer to NULL: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:89: INFO: Testing for setting tv_nsec to a negative value: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:89: INFO: Testing for setting tv_nsec value too high: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:89: INFO: Testing for passing pointer to invalid timer_id: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:89: INFO: Testing for passing invalid address for new_value: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EFAULT (14) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EFAULT (14)
[Kernel-packages] [Bug 1887473] Re: timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
This issue can be found on 4.4.0-185-generic as well.
It looks like a test case issue after commit:
50a2cb874188c ("syscalls: Fix issues around calling syscalls with old timespec")
https://github.com/linux-test-project/ltp/commit/50a2cb874188c89e03501f9d68585d3e256f3fc7
The test will pass after revert to
50a2cb874188c89e03501f9d68585d3e256f3fc7^
--
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/1887473
Title:
timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Eoan:
New
Status in linux source package in Focal:
New
Bug description:
Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other
arches)
And B/E/F s390x as well.
<<>>
tag=timer_settime02 stime=1594698491
cmdline="timer_settime02"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
timer_settime02.c:78: INFO: Testing variant: syscall with old kernel spec
timer_settime02.c:89: INFO: Testing for setting new_set pointer to NULL:
timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected:
EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected:
EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:89: INFO: Testing for setting tv_nsec to a negative value:
timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected:
EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected:
EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:89: INFO: Testing for setting tv_nsec value too high:
timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected:
EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected:
EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:89: INFO: Testing for passing pointer to invalid timer_id:
timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as
[Kernel-packages] [Bug 1887469] Re: timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
This issue can be found on 4.4.0-185-generic as well. -- 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/1887469 Title: timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. <<>> tag=timer_settime01 stime=1594697076 cmdline="timer_settime01" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s timer_settime01.c:142: INFO: Testing variant: syscall with old kernel spec timer_settime01.c:70: INFO: Testing for general initialization: timer_settime01.c:125: PASS: CLOCK_REALTIME was successful timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for setting old_value: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for using periodic timer: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for using absolute time: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
[Kernel-packages] [Bug 1887469] [NEW] timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
Public bug reported: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. <<>> tag=timer_settime01 stime=1594697076 cmdline="timer_settime01" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s timer_settime01.c:142: INFO: Testing variant: syscall with old kernel spec timer_settime01.c:70: INFO: Testing for general initialization: timer_settime01.c:125: PASS: CLOCK_REALTIME was successful timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for setting old_value: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for using periodic timer: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for using absolute time: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f18ddc13af98 Summary: passed 1 failed 46 skipped 8 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-186-generic 4.4.0-186.216 ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 Uname: Linux 4.4.0-186-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access
[Kernel-packages] [Bug 1887469] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Eoan) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed -- 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/1887469 Title: timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. <<>> tag=timer_settime01 stime=1594697076 cmdline="timer_settime01" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s timer_settime01.c:142: INFO: Testing variant: syscall with old kernel spec timer_settime01.c:70: INFO: Testing for general initialization: timer_settime01.c:125: PASS: CLOCK_REALTIME was successful timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for setting old_value: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for using periodic timer: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for using absolute time: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL:
[Kernel-packages] [Bug 1690085]
(In reply to Ashesh Ambasta from comment #699) > Created attachment 290243 [details] > attachment-20700-0.html I am getting: > Sorry, you are not authorized to access attachment #290243. […] > AMD did publish an errata in which they claim an issue like this exists; > but a solution is ruled out. Which is further bad news. There was some > discussion on a fix being at the kernel level, but that isn't anywhere > in sight either. I believe these CPU's are plagued by several issues, > which probably makes a fix for this at the kernel level hard. However, > Windows seems to have managed to fix it. That’s interesting. Could you please share the URL to these statements? […] raulvior.bcn, Asheesh: Please always remove the cited parts, as otherwise the Web issue page gets even more convoluted. Thanks. > Anyway; rants aside, this is my current take on the CPU. > > On 7/12/20 3:58 PM, bugzilla-dae...@bugzilla.kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=196683 > > > > --- Comment #698 from raulvior@gmail.com --- > > Did you ask for an RMA? Did it work? > > (In reply to Ashesh Ambasta from comment #692) > >> As a last resort, I've tried `idle=halt` on this machine. And yet my > >> system just crashed after 3 weeks of uptime. > >> > >> I'm done with AMD. I will RMA this processor to try things out, but > >> overall, if that doesn't work, this thing is headed to the junkyard and > >> I'm going to live with Intel. > >> > >> At least in the 13 or so odd Intel systems I've tried, I've not had > >> exhasperating issues like these where the company is positively trying > >> to ignore this ongoing issue. > >> > >> This is disgusting from AMD. > >> > >> On 6/11/20 6:03 PM, bugzilla-dae...@bugzilla.kernel.org wrote: > >>> https://bugzilla.kernel.org/show_bug.cgi?id=196683 > >>> > >>> --- Comment #689 from raulvior@gmail.com --- > >>> (In reply to raulvior.bcn from comment #653) > (In reply to txrx from comment #651) > > Typical Current Idle might not be working. Read the sensor output. If > voltage is not higher than without enabling it, try to increase the core > voltage. > > My Ryzen 7 1800X seems to not produce hangs since I upgraded to 1003ABB > >> with > an ASUS Crosshair VI Hero and enabled Typical current idle. > > > > I was able to update my BIOS to version 18, but my system still locks > up. > > I tried the following with the new BIOS: > >- use factory defaults > >- disable SMT > >- disable SMT with Typical Current Idle > >- all of the above with SVM disabled/enabled > > Right now I set the power supply idle control to "Low ..." and will > >> report > > back. > > > >>> The motherboard kept hanging. I had to remove the Vitals GNOME Extension. > >> It > >>> seems that polling voltage values hangs the motherboard... Still, there > are > >>> times that the computer does not come back from suspend. There's > something > >>> wrong with the BIOS/UEFI. > >>> -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ?
[Kernel-packages] [Bug 1690085]
It amazing tho, but most of all thanks for this.i would like to visit here https://vibenext.com/ https://massivebaze.xyz -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to:
[Kernel-packages] [Bug 1887459] Re: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
** Description changed: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. + + This is a new test case added between this and the last cycle. <<>> tag=clock_gettime04 stime=1594692118 cmdline="clock_gettime04" contacts="" analysis=exit <<>> tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s tst_test.c:1292: BROK: Test killed by SIGFPE! Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Error message can be found in syslog: report_user_fault: 159 callbacks suppressed User process fault: interruption code 0009 ilc:2 in clock_gettime04[113b0+22000] CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P O 4.4.0-186-generic #216-Ubuntu task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000 User PSW : 070510018000 000113b18878 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3 User GPRS: 0b0cd725 000113b1d026 000113b1d00e 0b0cd725 000113b19bc4 03ffe687e770 000113b28f38 03ff941fe128 000113b28ec8 075fcbb9 03ff941a5000 000113b1d098 000113b1843e 03ffe687e1f8 User Code: 000113b1886a: e300a0380016 llgf%r0,56(%r10) 000113b18870: a749 lghi%r4,0 #000113b18874: b9870040 dlgr%r4,%r0 >000113b18878: c0508328 larl%r5,113b28ec8 000113b1887e: eb140002000d sllg%r1,%r4,2 000113b18884: e3119012 lt %r1,0(%r1,%r9) 000113b1888a: a784009a brc 8,113b189be 000113b1888e: e3405044 lg %r4,64(%r5) Last Breaking-Event-Address: [<000113b18860>] 0x113b18860 Kernel tainted flag is 4097 after a clean boot, it won't be changed after the test: $ cat /proc/sys/kernel/tainted 4097 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-186-generic 4.4.0-186.216 ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 Uname: Linux 4.4.0-186-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jul 13 22:02:08 2020 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1887459 Title: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. This is a new test case added between this and the last cycle. <<>> tag=clock_gettime04 stime=1594692118 cmdline="clock_gettime04" contacts="" analysis=exit <<>> tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s tst_test.c:1292: BROK: Test killed by SIGFPE! Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Error message can be found in syslog: report_user_fault: 159 callbacks suppressed User process fault: interruption code 0009 ilc:2 in clock_gettime04[113b0+22000] CPU: 0 PID: 4222 Comm:
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
the origin change was in ''' commit 9dadfd82504afa114b39e508e4580cb0212468ea (tag: pkg/import/2.00-20) Author: Colin Watson Date: Thu Nov 14 10:49:31 2013 + + Set vt.handoff=7 for smooth handoff to kernel graphical mode. ''' https://git.launchpad.net/~hugh712/ubuntu/+source/grub2/commit/?h=ubuntu/devel=9dadfd82504afa114b39e508e4580cb0212468ea then it's been changed in bionic as: ''' commit db84c3cc6faa4750d12c451f7a0c20560d0893bd Author: Mathieu Trudel-Lapierre Date: Fri Feb 9 16:30:45 2018 -0500 Add configure option to use vt.handoff=1 ''' https://git.launchpad.net/~hugh712/ubuntu/+source/grub2/commit/?h=bionic=c9b225dd94935e17dc8196dcaea524d4897bef4d -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.9 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Precise: Fix Committed Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: New Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826848] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.9 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1826848 Title: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] Failure to run ip_defrag deterministically. [Fix] Use smaller packets and ignore EPERM. [Test case] Run the test multiple times without observing failures. [Regression potential] If the test fix is incorrect, it will cause us to miss real kernel bugs. But as it is now, we are already ignoring its results. == Test failed becuase: ./ip_defrag: sendto overlap: 1400: Operation not permitted selftests: net: ip_defrag.sh ipv6 tx:17 gso:1 (fail) OK ipv4 defrag PASS seed = 1556203721 ipv4 defrag with overlaps PASS seed = 1556203722 ipv6 defrag seed = 1556203756 PASS ipv6 defrag with overlaps seed = 1556203756 ./ip_defrag: sendto overlap: 1400: Operation not permitted not ok 1..17 selftests: net: ip_defrag.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884159] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.9 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1884159 Title: Update lockdown patches Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: Impact: The lockdown patches have evolved over time, and part of this was restricting more areas of the kernel. Not all of these additions were backported, and some can lead to lockdown bypasses, see [1] and [2]. Fix: Backport newer lockdown restrictions to older releases. Test Case: Test cases for most of the backports can be found at [3], and [4] is another test case. Some which need e.g. specific hardware to test have not been tested. Regression Potential: Most of these are small, simple fixes with low potential for regression. Users may also lose access to some functionality previously accissible under secure boot. Some changes are more substantial, especially the hw_param and debugfs changes for xenial, but they are based on well-tested upstream code. The xmon backports also carry a more moderate risk of regression. [1] https://lists.ubuntu.com/archives/kernel-team/2020-June/111050.html [2] https://lore.kernel.org/lkml/20200615104332.901519-1-ja...@zx2c4.com/ [3] https://git.launchpad.net/~sforshee/+git/lockdown-tests [4] https://git.zx2c4.com/american-unsigned-language/tree/american-unsigned-language.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881137] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.9 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1881137 Title: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers Status in linux package in Ubuntu: Incomplete Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-418-server package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: In Progress Status in nvidia-graphics-drivers-440-server source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-440 source package in Focal: In Progress Status in nvidia-graphics-drivers-440-server source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.82: * New upstream release: - Added a workaround for Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory. - Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces. - Fixed a bug that caused render-offloaded applications to crash on exit. - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getnstimeofday'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "dereferencing pointer to incomplete type 'struct timeval'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration
[Kernel-packages] [Bug 1885757] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.9 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1885757 Title: seccomp_bpf fails on powerpc Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] seccomp_bpf test fails on powerpc and ends up being disabled on some series, or causing engineers to waste their time verifying the same failures are the only ones we see every kernel release. [Test case] Run the test and notice there are no more failures. [Regression potential] We may break the test on different architectures. That doesn't break users, though, as the changes are only on tests. It has been tested at least on ppc64el and amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1885757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886668] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.9 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1886668 Title: linux 4.15.0-109-generic network DoS regression vs -108 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] On systems using cgroups and sockets extensively, like docker, kubernetes, lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic. [Fix] Revert the patch that disables sk_alloc cgroup refcounting when tasks are added to net_prio cgroup. [Test case] Test that such environments where the issue is reproduced survive some hours of uptime. A different bug was reproduced with a work-in-progress code and was not reproduced with the culprit reverted. [Regression potential] The reverted commit fix a memory leak on similar scenarios. But a leak is better than a crash. Two other bugs have been opened to track a real fix for this issue and the leak. -- Reported from a user: Several of our infrastructure VMs recently started crashing (oops attached), after they upgraded to -109. -108 appears to be stable. Analysing the crash, it appears to be a wild pointer access in a BPF filter, which makes this (probably) a network-traffic triggered crash. [ 696.396831] general protection fault: [#1] SMP PTI [ 696.396843] Modules linked in: iscsi_target_mod target_core_mod ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse i2c_piix4 pata_acpi floppy [ 696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic #110-Ubuntu [ 696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018 [ 696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0 [ 696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292 [ 696.397015] RAX: 6d69546e6f697469 RBX: RCX: 0014 [ 696.397028] RDX: RSI: 893fd036 RDI: 893fb5154800 [ 696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: [ 696.397058] R10: R11: 0003 R12: 0014 [ 696.397075] R13: 893fb5154800 R14: 0020 R15: 893fc6ba4d00 [ 696.397091] FS: () GS:893fdcb8() knlGS: [ 696.397107] CS: 0010 DS: ES: CR0: 80050033 [ 696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 003606e0 [ 696.397135] DR0: DR1: DR2: [ 696.397152] DR3: DR6: fffe0ff0 DR7: 0400 [ 696.397169] Call Trace: [ 696.397175] [ 696.397183] sk_filter_trim_cap+0xd0/0x1b0 [ 696.397191] tcp_v4_rcv+0x8b7/0xa80 [ 696.397199] ip_local_deliver_finish+0x66/0x210 [ 696.397208] ip_local_deliver+0x7e/0xe0 [ 696.397215] ? ip_rcv_finish+0x430/0x430 [ 696.397223] ip_rcv_finish+0x129/0x430 [ 696.397230] ip_rcv+0x296/0x360 [ 696.397238] ? inet_del_offload+0x40/0x40 [ 696.397249] __netif_receive_skb_core+0x432/0xb80 [ 696.397261] ? skb_send_sock+0x50/0x50 [ 696.397271] ? tcp4_gro_receive+0x137/0x1a0 [ 696.397280] __netif_receive_skb+0x18/0x60 [ 696.397290] ? __netif_receive_skb+0x18/0x60 [ 696.397300] netif_receive_skb_internal+0x45/0xe0 [ 696.397309] napi_gro_receive+0xc5/0xf0 [ 696.397317] xennet_poll+0x9ca/0xbc0 [ 696.397325]
[Kernel-packages] [Bug 1886247] Re: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
Verified 5.6.0-1020-oem: $ modinfo ./lib/modules/5.6.0-1020-oem/kernel/drivers/net/wireless/realtek/rtw88/rtwpci.ko | grep ^alias: alias: pci:v10ECdD723sv*sd*bc*sc*i* alias: pci:v10ECdC82Fsv*sd*bc*sc*i* alias: pci:v10ECdC822sv*sd*bc*sc*i* alias: pci:v10ECdB822sv*sd*bc*sc*i* ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1886247 Title: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: SRU justification: [Impact] New realtek wifi card ID found on ThinkCentre. No driver is loaded to support it. [Fix] This wifi card is very similar as 0xc822 in rtw88. [Test] Verified on hardware, link status is OK, iperf test result is good. [Regression Potential] Low. Add new ID to supported driver. Test on hw, double confirmed by LP bugs. This patch is backported from original link due to the 5.8-rc1 driver file path changed, no function changed. Maintainer had merged: https://github.com/lwfinger/rtlwifi_new/commit/b76b895a90f1168c5223849562fd6e1196b2c351 This git repo is moving by maintainer, not availible by now. = 01:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device c82f Looking for a working solution on a fresh install (USB BOOT) of Ubuntu. A work-around helped, for a while, but I would really like to disconnect my Wifi Dongel and use my brand new laptop! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1277 F pulseaudio /dev/snd/pcmC0D0c: christian 1277 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 07:58:06 2020 InstallationDate: Installed on 2020-06-28 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f610713f-73ad-468c-8a69-9a47b385acab ro quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux StagingDrivers: r8712u UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887459] Re: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
This issue can be reproduced on 4.4.0-185-generic s390x ** Tags added: kqa-blocker sru-20200629 ubuntu-ltp-syscalls -- 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/1887459 Title: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. <<>> tag=clock_gettime04 stime=1594692118 cmdline="clock_gettime04" contacts="" analysis=exit <<>> tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s tst_test.c:1292: BROK: Test killed by SIGFPE! Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Error message can be found in syslog: report_user_fault: 159 callbacks suppressed User process fault: interruption code 0009 ilc:2 in clock_gettime04[113b0+22000] CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P O 4.4.0-186-generic #216-Ubuntu task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000 User PSW : 070510018000 000113b18878 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3 User GPRS: 0b0cd725 000113b1d026 000113b1d00e 0b0cd725 000113b19bc4 03ffe687e770 000113b28f38 03ff941fe128 000113b28ec8 075fcbb9 03ff941a5000 000113b1d098 000113b1843e 03ffe687e1f8 User Code: 000113b1886a: e300a0380016 llgf%r0,56(%r10) 000113b18870: a749 lghi%r4,0 #000113b18874: b9870040 dlgr%r4,%r0 >000113b18878: c0508328 larl%r5,113b28ec8 000113b1887e: eb140002000d sllg%r1,%r4,2 000113b18884: e3119012 lt %r1,0(%r1,%r9) 000113b1888a: a784009a brc 8,113b189be 000113b1888e: e3405044 lg %r4,64(%r5) Last Breaking-Event-Address: [<000113b18860>] 0x113b18860 Kernel tainted flag is 4097 after a clean boot, it won't be changed after the test: $ cat /proc/sys/kernel/tainted 4097 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-186-generic 4.4.0-186.216 ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 Uname: Linux 4.4.0-186-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jul 13 22:02:08 2020 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1887459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887459] Re: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
** Description changed: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. <<>> tag=clock_gettime04 stime=1594692118 cmdline="clock_gettime04" contacts="" analysis=exit <<>> tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s tst_test.c:1292: BROK: Test killed by SIGFPE! Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Error message can be found in syslog: report_user_fault: 159 callbacks suppressed User process fault: interruption code 0009 ilc:2 in clock_gettime04[113b0+22000] CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P O 4.4.0-186-generic #216-Ubuntu task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000 User PSW : 070510018000 000113b18878 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3 User GPRS: 0b0cd725 000113b1d026 000113b1d00e 0b0cd725 000113b19bc4 03ffe687e770 000113b28f38 03ff941fe128 000113b28ec8 075fcbb9 03ff941a5000 000113b1d098 000113b1843e 03ffe687e1f8 User Code: 000113b1886a: e300a0380016 llgf%r0,56(%r10) 000113b18870: a749 lghi%r4,0 #000113b18874: b9870040 dlgr%r4,%r0 >000113b18878: c0508328 larl%r5,113b28ec8 000113b1887e: eb140002000d sllg%r1,%r4,2 000113b18884: e3119012 lt %r1,0(%r1,%r9) 000113b1888a: a784009a brc 8,113b189be 000113b1888e: e3405044 lg %r4,64(%r5) Last Breaking-Event-Address: [<000113b18860>] 0x113b18860 - Kernel tainted flag: + Kernel tainted flag is 4097 after a clean boot, it won't be changed after the test: $ cat /proc/sys/kernel/tainted 4097 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-186-generic 4.4.0-186.216 ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 Uname: Linux 4.4.0-186-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jul 13 22:02:08 2020 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1887459 Title: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. <<>> tag=clock_gettime04 stime=1594692118 cmdline="clock_gettime04" contacts="" analysis=exit <<>> tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s tst_test.c:1292: BROK: Test killed by SIGFPE! Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Error message can be found in syslog: report_user_fault: 159 callbacks suppressed User process fault: interruption code 0009 ilc:2 in clock_gettime04[113b0+22000] CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P O 4.4.0-186-generic #216-Ubuntu task: 0007aa6de348 ti:
[Kernel-packages] [Bug 1887461] [NEW] nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu 14.04
Public bug reported: when I did apt-get update && apt-get dist-upgrade, I saw that nvidia-430 package had the version 64 update that was just released a few days ago. After installing it, my system wouldn't boot to xwindows. Failsafe boot to gui wouldn't work either The error messages looked similar to this bug report for nvidia drivers: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053 Here's what my xorg.[0,failsafe].log showed: [43.645] (++) Log file: "/var/log/Xorg.failsafe.log", Time: Mon Jul 13 18:41:16 2020 [43.645] (++) Using config file: "/etc/X11/xorg.conf.failsafe" [43.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [43.645] Parse error on line 7 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass.conf "OutputClass" is not a valid section name. [43.645] (EE) Problem parsing the config file [43.645] (EE) Error parsing the config file [43.645] (EE) Fatal server error: [43.645] (EE) no screens found(EE) I have a *directory* named what the file is looking for (at least now after I downgraded nvidia...) here is the contents: /usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf# cat nvidia-drm-outputclass.conf # This xorg.conf.d configuration snippet configures the X server to # automatically load the nvidia X driver when it detects a device driven by the # nvidia-drm.ko kernel module. Please note that this only works on Linux kernels # version 3.9 or higher with CONFIG_DRM enabled, and only if the nvidia-drm.ko # kernel module is loaded before the X server is started. Section "OutputClass" Identifier "nvidia" MatchDriver"nvidia-drm" Driver "nvidia" EndSection basically, in the progress of filing this bug report, I downgraded to nvidia-418 and my system was about to boot again. To me, that says that nvidia-430.64 at least on Ubuntu 14.04 has a regression ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1887461 Title: nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu 14.04 Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: when I did apt-get update && apt-get dist-upgrade, I saw that nvidia-430 package had the version 64 update that was just released a few days ago. After installing it, my system wouldn't boot to xwindows. Failsafe boot to gui wouldn't work either The error messages looked similar to this bug report for nvidia drivers: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053 Here's what my xorg.[0,failsafe].log showed: [43.645] (++) Log file: "/var/log/Xorg.failsafe.log", Time: Mon Jul 13 18:41:16 2020 [43.645] (++) Using config file: "/etc/X11/xorg.conf.failsafe" [43.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [43.645] Parse error on line 7 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass.conf "OutputClass" is not a valid section name. [43.645] (EE) Problem parsing the config file [43.645] (EE) Error parsing the config file [43.645] (EE) Fatal server error: [43.645] (EE) no screens found(EE) I have a *directory* named what the file is looking for (at least now after I downgraded nvidia...) here is the contents: /usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf# cat nvidia-drm-outputclass.conf # This xorg.conf.d configuration snippet configures the X server to # automatically load the nvidia X driver when it detects a device driven by the # nvidia-drm.ko kernel module. Please note that this only works on Linux kernels # version 3.9 or higher with CONFIG_DRM enabled, and only if the nvidia-drm.ko # kernel module is loaded before the X server is started. Section "OutputClass" Identifier "nvidia" MatchDriver"nvidia-drm" Driver "nvidia" EndSection basically, in the progress of filing this bug report, I downgraded to nvidia-418 and my system was about to boot again. To me, that says that nvidia-430.64 at least on Ubuntu 14.04 has a regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1887461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887459] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Eoan) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed -- 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/1887459 Title: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. <<>> tag=clock_gettime04 stime=1594692118 cmdline="clock_gettime04" contacts="" analysis=exit <<>> tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s tst_test.c:1292: BROK: Test killed by SIGFPE! Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Error message can be found in syslog: report_user_fault: 159 callbacks suppressed User process fault: interruption code 0009 ilc:2 in clock_gettime04[113b0+22000] CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P O 4.4.0-186-generic #216-Ubuntu task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000 User PSW : 070510018000 000113b18878 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3 User GPRS: 0b0cd725 000113b1d026 000113b1d00e 0b0cd725 000113b19bc4 03ffe687e770 000113b28f38 03ff941fe128 000113b28ec8 075fcbb9 03ff941a5000 000113b1d098 000113b1843e 03ffe687e1f8 User Code: 000113b1886a: e300a0380016 llgf%r0,56(%r10) 000113b18870: a749 lghi%r4,0 #000113b18874: b9870040 dlgr%r4,%r0 >000113b18878: c0508328 larl%r5,113b28ec8 000113b1887e: eb140002000d sllg%r1,%r4,2 000113b18884: e3119012 lt %r1,0(%r1,%r9) 000113b1888a: a784009a brc 8,113b189be 000113b1888e: e3405044 lg %r4,64(%r5) Last Breaking-Event-Address: [<000113b18860>] 0x113b18860 Kernel tainted flag: $ cat /proc/sys/kernel/tainted 4097 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-186-generic 4.4.0-186.216 ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 Uname: Linux 4.4.0-186-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jul 13 22:02:08 2020 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1887459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887459] Re: clock_gettime04 from ubuntu_ltp_syscalls failed on X s390x
** Description changed: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) <<>> tag=clock_gettime04 stime=1594692118 cmdline="clock_gettime04" contacts="" analysis=exit <<>> tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s tst_test.c:1292: BROK: Test killed by SIGFPE! Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Error message can be found in syslog: - report_user_fault: 159 callbacks suppressed - User process fault: interruption code 0009 ilc:2 in clock_gettime04[113b0+22000] - CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P O 4.4.0-186-generic #216-Ubuntu - task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000 - User PSW : 070510018000 000113b18878 - R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3 - User GPRS: 0b0cd725 000113b1d026 000113b1d00e - 0b0cd725 000113b19bc4 03ffe687e770 - 000113b28f38 03ff941fe128 000113b28ec8 075fcbb9 - 03ff941a5000 000113b1d098 000113b1843e 03ffe687e1f8 - User Code: 000113b1886a: e300a0380016 llgf%r0,56(%r10) -000113b18870: a749 lghi%r4,0 - #000113b18874: b9870040 dlgr%r4,%r0 - >000113b18878: c0508328 larl%r5,113b28ec8 -000113b1887e: eb140002000d sllg%r1,%r4,2 -000113b18884: e3119012 lt %r1,0(%r1,%r9) -000113b1888a: a784009a brc 8,113b189be -000113b1888e: e3405044 lg %r4,64(%r5) - Last Breaking-Event-Address: - [<000113b18860>] 0x113b18860 + report_user_fault: 159 callbacks suppressed + User process fault: interruption code 0009 ilc:2 in clock_gettime04[113b0+22000] + CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P O 4.4.0-186-generic #216-Ubuntu + task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000 + User PSW : 070510018000 000113b18878 + R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3 + User GPRS: 0b0cd725 000113b1d026 000113b1d00e + 0b0cd725 000113b19bc4 03ffe687e770 + 000113b28f38 03ff941fe128 000113b28ec8 075fcbb9 + 03ff941a5000 000113b1d098 000113b1843e 03ffe687e1f8 + User Code: 000113b1886a: e300a0380016 llgf%r0,56(%r10) + 000113b18870: a749 lghi%r4,0 + #000113b18874: b9870040 dlgr%r4,%r0 + >000113b18878: c0508328 larl%r5,113b28ec8 + 000113b1887e: eb140002000d sllg%r1,%r4,2 + 000113b18884: e3119012 lt %r1,0(%r1,%r9) + 000113b1888a: a784009a brc 8,113b189be + 000113b1888e: e3405044 lg %r4,64(%r5) + Last Breaking-Event-Address: + [<000113b18860>] 0x113b18860 + + Kernel tainted flag: + $ cat /proc/sys/kernel/tainted + 4097 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-186-generic 4.4.0-186.216 ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 Uname: Linux 4.4.0-186-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jul 13 22:02:08 2020 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Description
[Kernel-packages] [Bug 1887459] [NEW] clock_gettime04 from ubuntu_ltp_syscalls failed on X s390x
Public bug reported: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) <<>> tag=clock_gettime04 stime=1594692118 cmdline="clock_gettime04" contacts="" analysis=exit <<>> tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s tst_test.c:1292: BROK: Test killed by SIGFPE! Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Error message can be found in syslog: report_user_fault: 159 callbacks suppressed User process fault: interruption code 0009 ilc:2 in clock_gettime04[113b0+22000] CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P O 4.4.0-186-generic #216-Ubuntu task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000 User PSW : 070510018000 000113b18878 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3 User GPRS: 0b0cd725 000113b1d026 000113b1d00e 0b0cd725 000113b19bc4 03ffe687e770 000113b28f38 03ff941fe128 000113b28ec8 075fcbb9 03ff941a5000 000113b1d098 000113b1843e 03ffe687e1f8 User Code: 000113b1886a: e300a0380016 llgf%r0,56(%r10) 000113b18870: a749 lghi%r4,0 #000113b18874: b9870040 dlgr%r4,%r0 >000113b18878: c0508328 larl%r5,113b28ec8 000113b1887e: eb140002000d sllg%r1,%r4,2 000113b18884: e3119012 lt %r1,0(%r1,%r9) 000113b1888a: a784009a brc 8,113b189be 000113b1888e: e3405044 lg %r4,64(%r5) Last Breaking-Event-Address: [<000113b18860>] 0x113b18860 Kernel tainted flag: $ cat /proc/sys/kernel/tainted 4097 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-186-generic 4.4.0-186.216 ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 Uname: Linux 4.4.0-186-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jul 13 22:02:08 2020 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: apport-bug package-from-proposed s390x third-party-packages xenial ** Description changed: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) <<>> tag=clock_gettime04 stime=1594692118 cmdline="clock_gettime04" contacts="" analysis=exit <<>> tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s tst_test.c:1292: BROK: Test killed by SIGFPE! Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> + Error message can be found in syslog: + report_user_fault: 159 callbacks suppressed + User process fault: interruption code 0009 ilc:2 in clock_gettime04[113b0+22000] + CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P O 4.4.0-186-generic #216-Ubuntu + task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000 + User PSW : 070510018000 000113b18878 + R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3 + User GPRS: 0b0cd725 000113b1d026 000113b1d00e + 0b0cd725 000113b19bc4 03ffe687e770 + 000113b28f38 03ff941fe128 000113b28ec8 075fcbb9 + 03ff941a5000 000113b1d098 000113b1843e 03ffe687e1f8 + User Code:
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
OK, thx. I will SRU the patches in the testing kernel first. -- 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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05) Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: wayland-session focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias:
[Kernel-packages] [Bug 1882623] Re: VM enter into hung status after triggering a crash
Last time I did verification against gallery image, the default kernel version is 4.4.0-148-generic. And I tried below kernel, found the kernel linux-image-4.15.0-1042-azure is the first one which we hit this bug, it is not specific for the esm kernel. # Kernel Version/Package Result 0 Default kernel 4.4.0-148-generic => Good 1 linux-image-4.15.0-1023-azure => Good 2 linux-image-4.15.0-1030-azure 3 linux-image-4.15.0-1031-azure 4 linux-image-4.15.0-1032-azure 5 linux-image-4.15.0-1035-azure 6 linux-image-4.15.0-1036-azure => Good 7 linux-image-4.15.0-1037-azure 8 linux-image-4.15.0-1039-azure 9 linux-image-4.15.0-1040-azure => Good 10 linux-image-4.15.0-1041-azure => Good 11 linux-image-4.15.0-1042-azure => Bad 12 linux-image-4.15.0-1045-azure => Bad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1882623 Title: VM enter into hung status after triggering a crash Status in linux-azure package in Ubuntu: New Bug description: Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest using size Standard DS2 v2 Install kexec-tools kdump-tools makedumpfile, configure boot kernel parameter crashkernel=512M Run sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools and sed -i 's/LOAD_KEXEC=true/LOAD_KEXEC=false/g' /etc/default/kexec Reboot VM, make sure crash kernel memory reserved successfully Trigger a crash by run echo 1 > /proc/sys/kernel/sysrq, then echo c > /proc/sysrq-trigger, VM will reboot automatically and after reboot, check crash dump is generated under /var/crash Install linux-azure kernel Enable private-ppa canonical-kernel-esm Install kernel linux-azure, reboot VM, kernel version 4.15.0-1084-azure Trigger a crash by run echo 1 > /proc/sys/kernel/sysrq, then echo c > /proc/sysrq-trigger, VM entered into a hung status. Attach whole serial console [ 65.452007] INFO: rcu_sched detected stalls on CPUs/tasks: [ 65.456004] 1-...!: (0 ticks this GP) idle=488/0/0 softirq=1/1 fqs=0 [ 65.456004] (detected by 0, t=15002 jiffies, g=707, c=706, q=8457) [ 65.456004] rcu_sched kthread starved for 15002 jiffies! g707 c706 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1 [ 360.020026] INFO: rcu_sched detected stalls on CPUs/tasks: [ 360.024015] 1-...!: (10 GPs behind) idle=b34/0/0 softirq=1/1 fqs=1 [ 360.024015] (detected by 0, t=15002 jiffies, g=717, c=716, q=6429) [ 360.024015] rcu_sched kthread starved for 15000 jiffies! g717 c716 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1 [ 420.048010] INFO: rcu_sched detected stalls on CPUs/tasks: [ 420.052006] 1-...!: (0 ticks this GP) idle=f94/0/0 softirq=1/1 fqs=0 [ 420.052006] (detected by 0, t=15002 jiffies, g=718, c=717, q=6429) [ 420.052006] rcu_sched kthread starved for 15002 jiffies! g718 c717 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1882623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
I will have to read up on this, and I am in a situation where I have to rely on this as my only computer for a while. -- 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/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager Status in linux package in Ubuntu: Incomplete Status in linux package in Fedora: Unknown Bug description: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not on the internal monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887445] [NEW] libnvidia-gl-440 does not specify exact dependencies on libnvidia-compute-440 or libnvidia-common-440
Public bug reported: Inspecting the package: $ dpkg --info libnvidia-gl-440_440.100-0ubuntu0.18.04.1_amd64.deb new Debian package, version 2.0. size 62889184 bytes: control archive=2352 bytes. 729 bytes,17 lines control 1531 bytes,18 lines md5sums 2554 bytes, 106 lines * preinst #!/bin/sh 461 bytes,12 lines shlibs 74 bytes, 2 lines triggers Package: libnvidia-gl-440 Source: nvidia-graphics-drivers-440 Version: 440.100-0ubuntu0.18.04.1 Architecture: amd64 Maintainer: Ubuntu Core Developers Installed-Size: 206436 Depends: libnvidia-common-440, libc6 (>= 2.2.5), libgcc1 (>= 1:4.2), libnvidia-compute-440, libx11-6, libxext6 Conflicts: libnvidia-gl Replaces: libnvidia-gl, nvidia-384 (<< 390.25), nvidia-390 (<< 390.25-0ubuntu1) Provides: libegl-vendor, libglx-vendor, libnvidia-gl Section: non-free/libs Priority: optional Multi-Arch: same Homepage: http://www.nvidia.com Description: NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD This package provides the NVIDIA OpenGL/GLX/EGL/GLES libraries and the Vulkan ICD. when attempting to pin libnvidia-gl-440 to version 440.59-0ubuntu0.18.04.1, I discovered that version 440.100 gets installed for libnvidia-compute-440 and libnvidia-common-440. This causes applications to break, because NVRM expects exact matches between the kernel driver version (440.59) and the libraries: [ 720.451125] NVRM: API mismatch: the client has the version 440.100, but NVRM: this kernel module has the version 440.59. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. I've worked around this locally by looking up the dependencies of libnvidia-gl-440, and pinning those with exact-matches as well. This could be resolved by specifying these dependencies inside the package as exact matches. ** Affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1887445 Title: libnvidia-gl-440 does not specify exact dependencies on libnvidia- compute-440 or libnvidia-common-440 Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: Inspecting the package: $ dpkg --info libnvidia-gl-440_440.100-0ubuntu0.18.04.1_amd64.deb new Debian package, version 2.0. size 62889184 bytes: control archive=2352 bytes. 729 bytes,17 lines control 1531 bytes,18 lines md5sums 2554 bytes, 106 lines * preinst #!/bin/sh 461 bytes,12 lines shlibs 74 bytes, 2 lines triggers Package: libnvidia-gl-440 Source: nvidia-graphics-drivers-440 Version: 440.100-0ubuntu0.18.04.1 Architecture: amd64 Maintainer: Ubuntu Core Developers Installed-Size: 206436 Depends: libnvidia-common-440, libc6 (>= 2.2.5), libgcc1 (>= 1:4.2), libnvidia-compute-440, libx11-6, libxext6 Conflicts: libnvidia-gl Replaces: libnvidia-gl, nvidia-384 (<< 390.25), nvidia-390 (<< 390.25-0ubuntu1) Provides: libegl-vendor, libglx-vendor, libnvidia-gl Section: non-free/libs Priority: optional Multi-Arch: same Homepage: http://www.nvidia.com Description: NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD This package provides the NVIDIA OpenGL/GLX/EGL/GLES libraries and the Vulkan ICD. when attempting to pin libnvidia-gl-440 to version 440.59-0ubuntu0.18.04.1, I discovered that version 440.100 gets installed for libnvidia-compute-440 and libnvidia-common-440. This causes applications to break, because NVRM expects exact matches between the kernel driver version (440.59) and the libraries: [ 720.451125] NVRM: API mismatch: the client has the version 440.100, but NVRM: this kernel module has the version 440.59. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. I've worked around this locally by looking up the dependencies of libnvidia-gl-440, and pinning those with exact-matches as well. This could be resolved by specifying these dependencies inside the package as exact matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718761] Re: It's not possible to use OverlayFS (mount -t overlay) to stack directories on a ZFS volume
I am arriving here as I would also like to run containers (docker) over
a zpool as the storage backend. In my case, I am running Ubuntu Server
(Focal) on a Pi 3B, I would ideally have root on zfs but with it being a
Pi, I have not done this yet. I have an externally attached USB pool for
real data and have left the OS as it is on the SD card, however, as the
above says, I would like to move more of my systems towards ZFS with
time and use Ubuntu-based distros and containers on a lot of them, where
these can't be run under illumos as VMs.
I have installed docker-rootless on this system, however due to kernel
limitations, it is impossible to mount datasets as non-root on linux
(long-standing issue, I am working on a bug report with details of
options for a workaround and will attach), and using a noverlay over the
top of zfs would be fine for me, as I can snapshot and work with the
higher-level system and back up easily, even if not as fast as native
zfs performance, however, the daemon will not start, and I have fallen
back to the "vfs" driver on my data-root filesystem.
Some googling hasn't indicated what feature(s) would be required in zfs for
overlay to be used on top, docker's documentation doesn't seem to clarify
anything, and searching for the "fstype=1" requirement in xfs, I find from the
manual page for `mkfs.xfs`:
```
ftype=value
This feature allows the inode type to be stored in
the directory structure so that the readdir(3) and
getdents(2) do not need to look up the inode to
determine the inode type.
```
which perhaps is not the issue at hand.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1718761
Title:
It's not possible to use OverlayFS (mount -t overlay) to stack
directories on a ZFS volume
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
-- Configuration
# echo -e $(grep VERSION= /etc/os-release)\\nSIGNATURE=\"$(cat
/proc/version_signature)\"
VERSION="16.04.3 LTS (Xenial Xerus)"
SIGNATURE="Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17"
# dpkg --list | grep zfs
ii libzfs2linux0.6.5.6-0ubuntu18
ii zfs-doc 0.6.5.6-0ubuntu18
ii zfs-initramfs 0.6.5.6-0ubuntu18
ii zfs-zed 0.6.5.6-0ubuntu18
ii zfsutils-linux 0.6.5.6-0ubuntu18
-- Fault: Creating an overlay of multiple directories on a ZFS volume
does not work
# df /var/tmp
Filesystem Type 1K-blocks Used Available Use% Mounted on
tank07/var/tmp zfs 129916288 128 129916160 1% /var/tmp
# mkdir /var/tmp/{lower,middle,upper,workdir,overlay}
# mount -t overlay overlay
-olowerdir=/var/tmp/middle:/var/tmp/lower,upperdir=/var/tmp/upper,workdir=/var/tmp/workdir
/var/tmp/overlay
mount: wrong fs type, bad option, bad superblock on overlay,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
# dmesg|tail -1
[276328.438284] overlayfs: filesystem on '/var/tmp/upper' not supported as
upperdir
-- Control test 1: Creating an overlay of multiple directories on
another filesystem works
# df /tmp
Filesystem Type 1K-blocks Used Available Use% Mounted on
tmpfs tmpfs 1048576 133492915084 13% /tmp
# mkdir /tmp/{lower,middle,upper,workdir,overlay}
# mount -t overlay overlay
-olowerdir=/tmp/middle:/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/workdir
/tmp/overlay
# mount | grep overlay
overlay on /tmp/overlay type overlay
(rw,relatime,lowerdir=/tmp/middle:/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/workdir)
-- Control test 2: Creating an overlay using AuFS works on ZFS volume
and elsewhere
# mount -t aufs -obr=/tmp/lower:/tmp/middle:/tmp/upper:/tmp/workdir none
/tmp/overlay
# mount -t aufs
-obr=/var/tmp/lower:/var/tmp/middle:/var/tmp/upper:/var/tmp/workdir none
/var/tmp/overlay
# mount | grep aufs
none on /var/tmp/overlay type aufs (rw,relatime,si=9ead1ecae778b250)
none on /tmp/overlay type aufs (rw,relatime,si=9ead1ec9257d1250)
-- Remark
While the use of AuFS can be used as a workaround in the above scenario, AuFS
in turn will not work with [fuse.]glusterfs mounts (this has been documented
elsewhere). Given that OverlayFS is part of the (upstream) kernel and Ubuntu
now officially supports ZFS, the above should be fixed.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 18 16:12 seq
crw-rw 1 root audio 116, 33 Sep 18 16:12 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with
[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
The script responsible for updating the /boot/initrd.img symlink is called `linux-update-symlinks`. If a kernel is installed without that script being run, the symlink will not be updated. The only place where `linux-update-symlinks` is run is inside each of our kernels, in `debian/templates/image.postinst.in`. This means that when our kernels are built as .deb packages, the appropriate machinery will be placed inside the .deb to thus update the /boot/initrd.img symlink. I checked the change history to `installkernel` and could not find any point in time in which it ran `linux-update-symlinks`. Furthermore, the help info inside `linux-update-symlinks` contains the following note: "This command is intended to be called from the postinst and postrm maintainer scripts of Linux kernel packages." It looks like `linux- update-symlinks` was only ever intended to be used in postinst/postrm hooks for .deb packages (and not called by `installkernel`). There are a few remedies to this problem I can see, but I'm not sure which is the correct solution: 1. Add a call to `linux-update-symlinks` into `installkernel` or 2. Add a script into /etc/kernel/postinst.d to run `linux-update-symlinks` or 3. Run `linux-update-symlinks` manually after installing a kernel directly via `installkernel` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Triaged Status in debianutils package in Ubuntu: New Status in linux-base package in Ubuntu: New Bug description: When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1677230] Re: vfat: missing iso8859-1 charset
this problem seems to be back in 5.3.61, 5.3.62 with bionic -- 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/1677230 Title: vfat: missing iso8859-1 charset Status in linux package in Ubuntu: Fix Released Bug description: The vfat kernel code has two dependencies: the code page (437) and the iocharset (iso8859-1), and while the former is built-in (like the vfat code itself), the latter is built as an external module, making vfat unusable unless the nsl_iso8859-1 ko is available at the moment a vfat filesystem is mounted. What is just a discrepancy in the config that we never hit (since we are shipping the nsl_iso8859-1 .ko in our initrd), became a problem in kernel derivatives of our -generic kernel (e.g. snappy) where we don't have any control on the modules people pack in their initrd, and in case the boot partition is a vfat partition that is being mounted during the boot. For this reason, i propose to fix the root problem and turn CONFIG_NLS_ISO8859_1=y to make the vfat code completely independent on any external factor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886234] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1886234 Title: libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1 with -EEXIST, don't try to register things with the same name in the same directory. Status in linux package in Ubuntu: Confirmed Bug description: After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and turning the VM off, I see this in dmesg: [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, widening DMA allocations [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config. [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6 [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1 [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1 [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1 [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config. [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on [ 4680.392669] sysfs: cannot create duplicate filename '/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1' [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G OE 5.4.0-40-generic #44-Ubuntu [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG STRIX X570-E GAMING, BIOS 1409 05/12/2020 [ 4680.392674] Call Trace: [ 4680.392681] dump_stack+0x6d/0x9a [ 4680.392684] sysfs_warn_dup.cold+0x17/0x35 [ 4680.392685] sysfs_create_dir_ns+0xb8/0xd0 [ 4680.392687] kobject_add_internal+0xbd/0x2b0 [ 4680.392688] kobject_add+0x7e/0xb0 [ 4680.392692] device_add+0x132/0x6b0 [ 4680.392696] snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device] [ 4680.392702] __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392706] snd_device_register_all+0x33/0x50 [snd] [ 4680.392709] snd_card_register+0x62/0x1b0 [snd] [ 4680.392712] ? snd_hwdep_new+0xfe/0x146 [snd_hwdep] [ 4680.392715] snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth] [ 4680.392717] snd_emux_register+0x11a/0x190 [snd_emux_synth] [ 4680.392719] ? 0xc1065000 [ 4680.392721] ? sf_sample_new+0x20/0x20 [snd_emux_synth] [ 4680.392723] snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth] [ 4680.392725] really_probe+0x2b3/0x3e0 [ 4680.392726] driver_probe_device+0xbc/0x100 [ 4680.392728] __device_attach_driver+0x71/0xd0 [ 4680.392729] ? driver_allows_async_probing+0x50/0x50 [ 4680.392731] bus_for_each_drv+0x84/0xd0 [ 4680.392732] __device_attach+0xe1/0x160 [ 4680.392734] device_initial_probe+0x13/0x20 [ 4680.392735] bus_probe_device+0x8f/0xa0 [ 4680.392737] device_add+0x3c7/0x6b0 [ 4680.392740] ? __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392742] snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device] [ 4680.392745] __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392748] snd_device_register_all+0x33/0x50 [snd] [ 4680.392751] snd_card_register+0x62/0x1b0 [snd] [ 4680.392753] ? snd_seq_device_new+0xd0/0x126 [snd_seq_device] [ 4680.392758] snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1] [ 4680.392761] local_pci_probe+0x48/0x80 [ 4680.392763] pci_device_probe+0x10f/0x1b0 [ 4680.392765] really_probe+0x159/0x3e0 [ 4680.392766] driver_probe_device+0xbc/0x100 [ 4680.392767] __device_attach_driver+0x71/0xd0 [ 4680.392769] ? driver_allows_async_probing+0x50/0x50 [ 4680.392770] bus_for_each_drv+0x84/0xd0 [ 4680.392771] __device_attach+0xe1/0x160 [ 4680.392773] device_attach+0x10/0x20 [ 4680.392775] bus_rescan_devices_helper+0x39/0x80 [ 4680.392777] drivers_probe_store+0x36/0x60 [ 4680.392778] bus_attr_store+0x27/0x30 [ 4680.392780] sysfs_kf_write+0x3e/0x50 [ 4680.392782] kernfs_fop_write+0xda/0x1b0 [ 4680.392784] __vfs_write+0x1b/0x40 [ 4680.392785] vfs_write+0xb9/0x1a0 [ 4680.392786] ksys_write+0x67/0xe0 [ 4680.392788] __x64_sys_write+0x1a/0x20 [ 4680.392790] do_syscall_64+0x57/0x190 [ 4680.392793] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 4680.392794] RIP: 0033:0x7f52456222cf [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48 [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 0001 [ 4680.392798] RAX: ffda RBX: 000c RCX: 7f52456222cf [ 4680.392799] RDX: 000c RSI: 7f5230062f50 RDI:
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
Actually, the use of built-in speaker and headphones at the same time happens only if I boot with headphones plugged in; and the way to mute the speakers but not the headphones is simply to unplug and reinsert the headphones. So that's fine. (It's different from what I'm used to, but acceptable behavior IMO). And 5.6.0 is no different from the new testing kernel in that regard. -- 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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05) Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: wayland-session focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/18/2020
Re: [Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
@Hui Wang The new testing kernel -- 5.4.0-42.46 -- does work on my machine! Sound works, mic works. One odd thing: with headphones plugged in, sound is output at both headphones and internal speakers. And it's not immediately obvious to me how to mute the speakers but leave the headphones on. Volume Control lists four output devices: Smart Sound Technology Audio Controller HDMI3/DP3 Output Smart Sound Technology Audio Controller HDMI2/DP2 Output Smart Sound Technology Audio Controller HDMI1/DP1 Output Smart Sound Technology Audio Controller Speaker + Headphones I'm attaching dmesg output. On Mon, Jul 13, 2020 at 10:20 AM Hui Wang <1886...@bugs.launchpad.net> wrote: > @gogolink, > > I built a new testing kernel, if you have time, please help test it. If > it still can't work, we have to bisect if we want to fix it in the 5.4 > kernel. > > https://people.canonical.com/~hwang4/lp1886341/v2/ > > thx. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1886341 > > Title: > Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal > audio devices to fail to load w/o unacceptable workaround (Lenovo > IdeaPad 5 15IIL05) > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal > speakers, headphone jack, and mic do not work at all. No audio devices > appear in the Sound settings or in pavucontrol. By appending options > snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can > get audio working, but the microphone (unsuprisingly) does not work. > Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as > the same effect as dmic_detect=0. Attempts to fix with option > snd_hda_intel device=generic or deveice=auto have had no effect. This > bug does NOT manifest on 5.4.0-26-generic, the kernel version featured > on the 20.04 live media. After installation, and updating to > 5.4.0-40-generic, the bug manifests on the next boot. > > Note that the audio hardware seems to work properly w/o workaround on > a small (< 5%) percentage of boots, but I have been unable to > reproduce this. With the workaround enabled, inxi -A gives > > Audio: > Device-1: Intel Smart Sound Audio driver: snd_hda_intel > Sound Server: ALSA v: k5.4.0-40-generic > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-40-generic 5.4.0-40.44 > ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 > Uname: Linux 5.4.0-40-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.3 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: jill 1374 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sun Jul 5 13:32:58 2020 > InstallationDate: Installed on 2020-07-03 (2 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: LENOVO 81YK > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic > root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-40-generic N/A >linux-backports-modules-5.4.0-40-generic N/A >linux-firmware1.187.1 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/18/2020 > dmi.bios.vendor: LENOVO > dmi.bios.version: DPCN40WW > dmi.board.asset.tag: NO Asset Tag > dmi.board.name: LNVNB161216 > dmi.board.vendor: LENOVO > dmi.board.version: SDK0J40709 WIN > dmi.chassis.asset.tag: NO Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: IdeaPad 5 15IIL05 > dmi.modalias: > dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: > dmi.product.family: IdeaPad 5 15IIL05 > dmi.product.name: 81YK > dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 > dmi.product.version: IdeaPad 5 15IIL05 > dmi.sys.vendor: LENOVO > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu27.3 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 20.04 > InstallationDate: Installed on 2020-07-03 (5 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: LENOVO 81YK > Package: linux (not installed) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >
[Kernel-packages] [Bug 1886234] Re: libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1 with -EEXIST, don't try to register things with the same name in the same directory.
Tested with 5.8.0-050800-generic downloaded from kernel ppa. Got exactly the same error as above, except this time the whole system froze and became unusable, so I had to kill the power to the PC. Additionally I got a whole bunch of new errors in dmesg like [ 31.072963] SQUASHFS error: Unable to read metadata cache entry [31b7fff] [ 31.072964] SQUASHFS error: Unable to read directory block [31b7fff:13ee] which seem to be unrelated. ** Changed in: linux (Ubuntu) Status: Incomplete => New -- 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/1886234 Title: libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1 with -EEXIST, don't try to register things with the same name in the same directory. Status in linux package in Ubuntu: New Bug description: After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and turning the VM off, I see this in dmesg: [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, widening DMA allocations [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config. [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6 [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1 [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1 [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1 [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config. [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on [ 4680.392669] sysfs: cannot create duplicate filename '/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1' [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G OE 5.4.0-40-generic #44-Ubuntu [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG STRIX X570-E GAMING, BIOS 1409 05/12/2020 [ 4680.392674] Call Trace: [ 4680.392681] dump_stack+0x6d/0x9a [ 4680.392684] sysfs_warn_dup.cold+0x17/0x35 [ 4680.392685] sysfs_create_dir_ns+0xb8/0xd0 [ 4680.392687] kobject_add_internal+0xbd/0x2b0 [ 4680.392688] kobject_add+0x7e/0xb0 [ 4680.392692] device_add+0x132/0x6b0 [ 4680.392696] snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device] [ 4680.392702] __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392706] snd_device_register_all+0x33/0x50 [snd] [ 4680.392709] snd_card_register+0x62/0x1b0 [snd] [ 4680.392712] ? snd_hwdep_new+0xfe/0x146 [snd_hwdep] [ 4680.392715] snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth] [ 4680.392717] snd_emux_register+0x11a/0x190 [snd_emux_synth] [ 4680.392719] ? 0xc1065000 [ 4680.392721] ? sf_sample_new+0x20/0x20 [snd_emux_synth] [ 4680.392723] snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth] [ 4680.392725] really_probe+0x2b3/0x3e0 [ 4680.392726] driver_probe_device+0xbc/0x100 [ 4680.392728] __device_attach_driver+0x71/0xd0 [ 4680.392729] ? driver_allows_async_probing+0x50/0x50 [ 4680.392731] bus_for_each_drv+0x84/0xd0 [ 4680.392732] __device_attach+0xe1/0x160 [ 4680.392734] device_initial_probe+0x13/0x20 [ 4680.392735] bus_probe_device+0x8f/0xa0 [ 4680.392737] device_add+0x3c7/0x6b0 [ 4680.392740] ? __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392742] snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device] [ 4680.392745] __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392748] snd_device_register_all+0x33/0x50 [snd] [ 4680.392751] snd_card_register+0x62/0x1b0 [snd] [ 4680.392753] ? snd_seq_device_new+0xd0/0x126 [snd_seq_device] [ 4680.392758] snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1] [ 4680.392761] local_pci_probe+0x48/0x80 [ 4680.392763] pci_device_probe+0x10f/0x1b0 [ 4680.392765] really_probe+0x159/0x3e0 [ 4680.392766] driver_probe_device+0xbc/0x100 [ 4680.392767] __device_attach_driver+0x71/0xd0 [ 4680.392769] ? driver_allows_async_probing+0x50/0x50 [ 4680.392770] bus_for_each_drv+0x84/0xd0 [ 4680.392771] __device_attach+0xe1/0x160 [ 4680.392773] device_attach+0x10/0x20 [ 4680.392775] bus_rescan_devices_helper+0x39/0x80 [ 4680.392777] drivers_probe_store+0x36/0x60 [ 4680.392778] bus_attr_store+0x27/0x30 [ 4680.392780] sysfs_kf_write+0x3e/0x50 [ 4680.392782] kernfs_fop_write+0xda/0x1b0 [ 4680.392784] __vfs_write+0x1b/0x40 [ 4680.392785] vfs_write+0xb9/0x1a0 [ 4680.392786] ksys_write+0x67/0xe0 [ 4680.392788] __x64_sys_write+0x1a/0x20 [ 4680.392790] do_syscall_64+0x57/0x190 [ 4680.392793] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 4680.392794] RIP: 0033:0x7f52456222cf [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
So, with my usual kernel version, 5.4.0.40-generic, adding that line
(exactly as it was written, including spaces, " and ' ) during boot ('e'
-editing the grub), the touchpad works, but after the laptop goes idle
or the screen is locked, it goes back as a generic mouse.
The trick of disconnecting and connecting it back with ```modprobe
psmouse``` keeps working though...
I am trying it now with the latest version of the kernel
5.8.0-050800-generic.
The touchpad works from start. I have locked the screen and it keeps
working after logging in.
Even better, all the multi-finger movements work as well ( I had fusuma,
but 4 finger vertical swipe never worked; now, it is working).
I can't say yet that it has been fixed, but definitely we're on the
right track!
Please let me know if I can do anything else to help you debug this
thing.
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/1882388
Title:
Touchpad recognised as generic mouse
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo
ideapadY700. My laptop recognises touchpad as mouse. I have no other
mouse plugged.
Touchpad firmware: 2ul001af
Lenovo ideapad700-15ISK BIOS version: CDCN54WW
I'm new in Ubuntu and I don't know much...
```$ uname -a```
```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21
12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux```
```$ dmesg | grep psmouse```
```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01
failed.
[ 30.218879] psmouse serio1: elantech: failed to query firmware version.
[ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost
synchronization, throwing 2 bytes away.
[ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost
synchronization, throwing 2 bytes away.
[ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost
synchronization, throwing 2 bytes away.
[ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost
synchronization, throwing 2 bytes away.
```
```$ xinput```
```⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ Sleep Buttonid=10 [slave
keyboard (3)]
↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave
keyboard (3)]
↳ Ideapad extra buttons id=12 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=13 [slave
keyboard (3)]
```
```$ cat /proc/bus/input/devices```
```I: Bus=0011 Vendor=0002 Product=0001 Version=0063
N: Name="PS/2 Logitech Wheel Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input19
U: Uniq=
H: Handlers=mouse0 event16
B: PROP=1
B: EV=7
B: KEY=7 0 0 0 0
B: REL=3
```
I have read a lot of solutions; I tried to use xorg, but it didn't work.
When I removed it, it worked for a day (only) and I decided erase and
re-install Ubuntu.
Please help!
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-33-generic 5.4.0-33.37
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nando 1137 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 6 20:24:24 2020
InstallationDate: Installed on 2020-06-06 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera
Bus 001 Device 003: ID 8087:0a2a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80NV
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic
root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7
RelatedPackageVersions:
[Kernel-packages] [Bug 1870140] Re: Laptop freeze after unplug power-AC (USB-C)
Hi @mxmaster, i'm also subscribed on Fedora bug tracking to receive more information about this issue. As usual Fedora's users more active =) I found the message from 2020-04-30 about fix for 5.6.8 kernels https://bugzilla.redhat.com/show_bug.cgi?id=1785972#c48 I'm not checked this information, because i'm not Fedora user, but it sounds good ) -- 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/1870140 Title: Laptop freeze after unplug power-AC (USB-C) Status in linux package in Ubuntu: Confirmed Bug description: ## Power adapter plugged in, charging goes well [ 1018.621820] asus_wmi: Unknown key cf pressed ## Power adapter unplugged, after few moments system freeze [ 567.444810] BUG: kernel NULL pointer dereference, address: 0080 [ 567.444819] #PF: supervisor read access in kernel mode [ 567.444823] #PF: error_code(0x) - not-present page [ 567.444827] PGD 0 P4D 0 [ 567.444834] Oops: [#1] PREEMPT SMP PTI [ 567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 5.5.11-151.current #1 [ 567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS UX370UAR.310 04/17/2019 [ 567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi] [ 567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi] [ 567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00 [ 567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202 [ 567.444883] RAX: 0008 RBX: 88844685c418 RCX: 000efd00 [ 567.444886] RDX: RSI: 0001 RDI: 0008 [ 567.444889] RBP: R08: R09: c9477ce0 [ 567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 88844685c418 [ 567.444895] R13: 0001 R14: 88844685c2a8 R15: [ 567.444900] FS: () GS:88844ec0() knlGS: [ 567.444903] CS: 0010 DS: ES: CR0: 80050033 [ 567.444906] CR2: 0080 CR3: 0240a006 CR4: 003606f0 [ 567.444909] Call Trace: [ 567.444921] ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi] [ 567.444930] ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi] [ 567.444938] ucsi_handle_connector_change+0x231/0x310 [typec_ucsi] [ 567.444949] ? kmem_cache_free+0x22a/0x290 [ 567.444960] process_one_work+0x1e1/0x3d0 [ 567.444968] worker_thread+0x4a/0x3d0 [ 567.444976] kthread+0xfb/0x130 [ 567.444983] ? process_one_work+0x3d0/0x3d0 [ 567.444988] ? kthread_park+0x90/0x90 [ 567.444998] ret_from_fork+0x35/0x40 [ 567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm fb_sys_fops i2c_i801 ucsi_acpi snd_timer [ 567.445072] typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp usb_common wmi i2c_hid hid battery video [ 567.445112] CR2: 0080 [ 567.445117] ---[ end trace a50cf550f0b4969a ]--- [ 567.445126] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi] [ 567.445132] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00 [ 567.445136] RSP: 0018:c9477df0 EFLAGS: 00010202 [ 567.445140] RAX: 0008 RBX: 88844685c418 RCX: 000efd00 [ 567.445143] RDX: RSI: 0001 RDI: 0008 [
[Kernel-packages] [Bug 1776563]
How is it? -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
https://github.com/torvalds/linux/commit/89a3c9f5b9f0bcaa9aea3e8b2a616fcaea9aad78 SUNRPC: Properly set the @Subbuf parameter of xdr_buf_subsegment() When I apply that patch to 5.4.0-40-generic the original bug disappears, however I sometimes still get: [Mo Jul 13 20:22:53 2020] BUG: unable to handle page fault for address: 98fd15cd [Mo Jul 13 20:22:53 2020] #PF: supervisor write access in kernel mode [Mo Jul 13 20:22:53 2020] #PF: error_code(0x0003) - permissions violation [Mo Jul 13 20:22:53 2020] PGD 214c01067 P4D 214c01067 PUD 214c05067 PMD 455d94063 PTE 800455cd0061 [Mo Jul 13 20:22:53 2020] Oops: 0003 [#1] SMP PTI [Mo Jul 13 20:22:53 2020] CPU: 0 PID: 1428 Comm: update-desktop- Tainted: G OE 5.4.0-40-generic #44 [Mo Jul 13 20:22:53 2020] Hardware name: XXX [Mo Jul 13 20:22:53 2020] RIP: 0010:memcpy_erms+0x6/0x10 [Mo Jul 13 20:22:53 2020] Code: ff 90 90 90 eb 1e 0f 1f 00 48 89 f8 48 89 d1 48 c1 e9 03 83 e2 07 f3 48 a5 89 d1 f3 a4 c3 66 0f 1f 44 00 00 48 89 f8 48 89 d1 a4 c3 0f 1f 80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38 fe [Mo Jul 13 20:22:53 2020] RSP: 0018:b4f780bdb610 EFLAGS: 00010286 [Mo Jul 13 20:22:53 2020] RAX: 98fd15ccffc4 RBX: b4f780bdba08 RCX: 0004 [Mo Jul 13 20:22:53 2020] RDX: 0040 RSI: 98fd132eb064 RDI: 98fd15cd [Mo Jul 13 20:22:53 2020] RBP: b4f780bdb640 R08: R09: 015b [Mo Jul 13 20:22:53 2020] R10: b4f780bdb5e0 R11: 98fd10f14850 R12: 0028 [Mo Jul 13 20:22:53 2020] R13: 0040 R14: 98fd188be280 R15: 0040 [Mo Jul 13 20:22:53 2020] FS: 7fea854dcb80() GS:98fd1da0() knlGS: [Mo Jul 13 20:22:53 2020] CS: 0010 DS: ES: CR0: 80050033 [Mo Jul 13 20:22:53 2020] CR2: 98fd15cd CR3: 0004532e0003 CR4: 003606f0 [Mo Jul 13 20:22:53 2020] Call Trace: [Mo Jul 13 20:22:53 2020] ? _copy_from_pages+0x6f/0xa0 [sunrpc] [Mo Jul 13 20:22:53 2020] xdr_shrink_pagelen+0x83/0xb0 [sunrpc] [Mo Jul 13 20:22:53 2020] xdr_align_pages+0x8e/0x1c0 [sunrpc] [Mo Jul 13 20:22:53 2020] xdr_read_pages+0x18/0x80 [sunrpc] [Mo Jul 13 20:22:53 2020] nfs4_xdr_dec_readlink+0xea/0x140 [nfsv4] [Mo Jul 13 20:22:53 2020] rpcauth_unwrap_resp_decode+0x27/0x30 [sunrpc] [Mo Jul 13 20:22:53 2020] gss_unwrap_resp+0x358/0x5a0 [auth_rpcgss] [Mo Jul 13 20:22:53 2020] ? call_bind_status+0x290/0x290 [sunrpc] [Mo Jul 13 20:22:53 2020] rpcauth_unwrap_resp+0x24/0x30 [sunrpc] [Mo Jul 13 20:22:53 2020] call_decode+0x158/0x1d0 [sunrpc] [Mo Jul 13 20:22:53 2020] __rpc_execute+0x8c/0x3a0 [sunrpc] [Mo Jul 13 20:22:53 2020] rpc_execute+0xa0/0xb0 [sunrpc] [Mo Jul 13 20:22:53 2020] rpc_run_task+0x120/0x150 [sunrpc] [Mo Jul 13 20:22:53 2020] nfs4_call_sync_custom+0x10/0x30 [nfsv4] [Mo Jul 13 20:22:53 2020] nfs4_call_sync_sequence+0x65/0x80 [nfsv4] [Mo Jul 13 20:22:53 2020] _nfs4_proc_readlink+0xa3/0xc0 [nfsv4] [Mo Jul 13 20:22:53 2020] nfs4_proc_readlink+0x6e/0x100 [nfsv4] [Mo Jul 13 20:22:53 2020] nfs_symlink_filler+0x33/0x70 [nfs] [Mo Jul 13 20:22:53 2020] do_read_cache_page+0x2f6/0x830 [Mo Jul 13 20:22:53 2020] ? nfs_get_link+0x120/0x120 [nfs] [Mo Jul 13 20:22:53 2020] ? xas_load+0xd/0x80 [Mo Jul 13 20:22:53 2020] ? find_get_entry+0x5e/0x170 [Mo Jul 13 20:22:53 2020] ? nfs4_do_check_delegation+0x1d/0x40 [nfsv4] [Mo Jul 13 20:22:53 2020] ? nfs4_have_delegation+0x13/0x20 [nfsv4] [Mo Jul 13 20:22:53 2020] ? nfs_check_cache_invalid+0x38/0xa0 [nfs] [Mo Jul 13 20:22:53 2020] read_cache_page+0x12/0x20 [Mo Jul 13 20:22:53 2020] nfs_get_link+0x47/0x120 [nfs] [Mo Jul 13 20:22:53 2020] trailing_symlink+0x21d/0x280 [Mo Jul 13 20:22:53 2020] ? nfs_destroy_readpagecache+0x20/0x20 [nfs] [Mo Jul 13 20:22:53 2020] path_lookupat.isra.0+0x8c/0x230 [Mo Jul 13 20:22:53 2020] ? rpc_free_task+0x64/0x70 [sunrpc] [Mo Jul 13 20:22:53 2020] ? rpc_do_put_task+0x6a/0x70 [sunrpc] [Mo Jul 13 20:22:53 2020] filename_lookup+0xae/0x170 [Mo Jul 13 20:22:53 2020] ? strncpy_from_user+0x4c/0x150 [Mo Jul 13 20:22:53 2020] user_path_at_empty+0x3a/0x50 [Mo Jul 13 20:22:53 2020] vfs_statx+0x7d/0xe0 [Mo Jul 13 20:22:53 2020] __do_sys_newstat+0x3e/0x80 [Mo Jul 13 20:22:53 2020] ? _cond_resched+0x19/0x30 [Mo Jul 13 20:22:53 2020] ? exit_to_usermode_loop+0xea/0x160 [Mo Jul 13 20:22:53 2020] __x64_sys_newstat+0x16/0x20 [Mo Jul 13 20:22:53 2020] do_syscall_64+0x57/0x190 [Mo Jul 13 20:22:53 2020] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Mo Jul 13 20:22:53 2020] RIP: 0033:0x7fea8568449a -- 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/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Confirmed Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
It was working for a while, but after the laptop goes idle or the screen is locked, the touchpad goes back as a generic mouse; the trick of disconnecting and connecting it back with ```modprobe psmouse``` keeps working though... -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias:
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Ubuntu no longer uses vt.handover and it should not be specified at all anymore. We boot directly to tty1, always and everywhere, and we should not be setting that at all. Thus a patch changing that from 7 to 1 is not a good idea for focal+. And I can't quite remember which releases we have changed to booting to tty1 by default. Maybe it was bionic, or between xenial and bionic? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
hugh, you will need to coordinate this with the Foundations Team, as there are a number of grub changes currently queued for SRU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
On W10 it's setted as 1920x1080 - 59Hz. It works perfectly. I tried with this resolution on Ubuntu 20.04. Still doesn't works. ** Attachment added: "Resolution and refresh second monitor on W10.PNG" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1871721/+attachment/5392357/+files/Resolution%20and%20refresh%20second%20monitor%20on%20W10.PNG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0:
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
I can confirm that 5.8.0-050800-generic does fix the bug. I also tested https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.51/ and the problem is still present in that version. -- 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/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Confirmed Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10:
[Kernel-packages] [Bug 1887397] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1887397
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1887397
Title:
perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Groovy:
Incomplete
Bug description:
After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
is failing with the following error:
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
syntax error in dynamic list
collect2: error: ld returned 1 exit status
The file mentioned in the error (libtraceevent-dynamic-list) contains
some '@' that ld doesn't seem to like:
$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail@@GLIBC_2.4;
free@@GLIBC_2.2.5;
memset@@GLIBC_2.2.5;
realloc@@GLIBC_2.2.5;
sprintf@@GLIBC_2.2.5;
strcmp@@GLIBC_2.2.5;
strdup@@GLIBC_2.2.5;
strncmp@@GLIBC_2.2.5;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};
The same file generated in a Focal environment (w/ binutils
2.34-6ubuntu1) looks as following:
$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail;
free;
memset;
realloc;
sprintf;
strcmp;
strdup;
strncmp;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};
And here is the chunk of Makefile that is generating this file:
define do_generate_dynamic_list_file
symbol_type=`$(NM) -u -D $1 | awk 'NF>1 {print $$1}' | \
xargs echo "U w W" | tr 'w ' 'W\n' | sort -u | xargs echo`;\
if [ "$$symbol_type" = "U W" ];then \
(echo '{'; \
$(NM) -u -D $1 | awk 'NF>1 {print "\t"$$2";"}' | sort -u;\
echo '};'; \
) > $2; \
else\
(echo Either missing one of [$1] or bad version of $(NM))
1>&2;\
fi
My guess is that something changed in the output of `nm` to show the @
charaters that ld does not like.
This problem is currently breaking all kernel builds in Groovy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887397/+subscriptions
--
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
I will investigate when I have some time, hopefully later today. -- 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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05) Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: wayland-session focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias:
[Kernel-packages] [Bug 1887397] Re: perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1
see https://sourceware.org/bugzilla/show_bug.cgi?id=25708
this seems to be an intended change.
** Bug watch added: Sourceware.org Bugzilla #25708
https://sourceware.org/bugzilla/show_bug.cgi?id=25708
** Package changed: binutils (Ubuntu Groovy) => linux (Ubuntu Groovy)
--
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/1887397
Title:
perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1
Status in linux package in Ubuntu:
New
Status in linux source package in Groovy:
New
Bug description:
After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
is failing with the following error:
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
syntax error in dynamic list
collect2: error: ld returned 1 exit status
The file mentioned in the error (libtraceevent-dynamic-list) contains
some '@' that ld doesn't seem to like:
$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail@@GLIBC_2.4;
free@@GLIBC_2.2.5;
memset@@GLIBC_2.2.5;
realloc@@GLIBC_2.2.5;
sprintf@@GLIBC_2.2.5;
strcmp@@GLIBC_2.2.5;
strdup@@GLIBC_2.2.5;
strncmp@@GLIBC_2.2.5;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};
The same file generated in a Focal environment (w/ binutils
2.34-6ubuntu1) looks as following:
$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail;
free;
memset;
realloc;
sprintf;
strcmp;
strdup;
strncmp;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};
And here is the chunk of Makefile that is generating this file:
define do_generate_dynamic_list_file
symbol_type=`$(NM) -u -D $1 | awk 'NF>1 {print $$1}' | \
xargs echo "U w W" | tr 'w ' 'W\n' | sort -u | xargs echo`;\
if [ "$$symbol_type" = "U W" ];then \
(echo '{'; \
$(NM) -u -D $1 | awk 'NF>1 {print "\t"$$2";"}' | sort -u;\
echo '};'; \
) > $2; \
else\
(echo Either missing one of [$1] or bad version of $(NM))
1>&2;\
fi
My guess is that something changed in the output of `nm` to show the @
charaters that ld does not like.
This problem is currently breaking all kernel builds in Groovy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887397/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887397] [NEW] perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1
You have been subscribed to a public bug:
After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
is failing with the following error:
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
syntax error in dynamic list
collect2: error: ld returned 1 exit status
The file mentioned in the error (libtraceevent-dynamic-list) contains
some '@' that ld doesn't seem to like:
$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail@@GLIBC_2.4;
free@@GLIBC_2.2.5;
memset@@GLIBC_2.2.5;
realloc@@GLIBC_2.2.5;
sprintf@@GLIBC_2.2.5;
strcmp@@GLIBC_2.2.5;
strdup@@GLIBC_2.2.5;
strncmp@@GLIBC_2.2.5;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};
The same file generated in a Focal environment (w/ binutils
2.34-6ubuntu1) looks as following:
$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail;
free;
memset;
realloc;
sprintf;
strcmp;
strdup;
strncmp;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};
And here is the chunk of Makefile that is generating this file:
define do_generate_dynamic_list_file
symbol_type=`$(NM) -u -D $1 | awk 'NF>1 {print $$1}' | \
xargs echo "U w W" | tr 'w ' 'W\n' | sort -u | xargs echo`;\
if [ "$$symbol_type" = "U W" ];then \
(echo '{'; \
$(NM) -u -D $1 | awk 'NF>1 {print "\t"$$2";"}' | sort -u;\
echo '};'; \
) > $2; \
else\
(echo Either missing one of [$1] or bad version of $(NM)) 1>&2;\
fi
My guess is that something changed in the output of `nm` to show the @
charaters that ld does not like.
This problem is currently breaking all kernel builds in Groovy.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
--
perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1
https://bugs.launchpad.net/bugs/1887397
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886827] Re: Machine hangs when doing a normal reboot
It's for 5.8-rc4. -- 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/1886827 Title: Machine hangs when doing a normal reboot Status in linux package in Ubuntu: Incomplete Bug description: Hi, When booting into kernel 4.15.0-99-generic or higher and also kernel 5.3.0-53-generic or higher, the system hangs when issuing the reboot command or CTRL-ALT-DEL from console with the following console messages: -- snip Reached target Final Step. Starting Reboot... < following message repeats indefinetely every 120 seconds > INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.15.0-99-generic #100 " echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. -- snip I did a git bisect procedure between kernels 4.15.0-96-generic and 4.15.0-99 and it reported the following: -- snip b52be79f3c6cc89bb3834c5174843e34f945f386 is the first bad commit commit b52be79f3c6cc89bb3834c5174843e34f945f386 -- snip Ubuntu version affected: Ubuntu 4.15.0-99.100-generic 4.15.18 First kernel package affected: linux-image-4.15.0-99-generic Necessary debug files will be attached as soon as possible. Quinn --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 9 09:55 seq crw-rw 1 root audio 116, 33 Jul 9 09:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/system-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-99-generic root=/dev/mapper/system-root ro rootflags=subvol=@ biosdevname=0 net.ifnames=0 nomodeset "dyndbg=file drivers/base/* +p" ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.18 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk plugdev sudo _MarkForUpload: True dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd05/05/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
What's the resolution and refresh rate picked under Windows? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
Can you please also test upstream 5.4: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.51/ Hopefully we don't need to do any backport, there are a hundred commits... -- 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/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Confirmed Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10:
[Kernel-packages] [Bug 1877461] Re: Bionic update: upstream stable patchset 2020-05-07
This bug was fixed in the package linux - 4.15.0-111.112
---
linux (4.15.0-111.112) bionic; urgency=medium
* bionic/linux: 4.15.0-111.112 -proposed tracker (LP: #1886999)
* Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461)
- SAUCE: mlxsw: Add missmerged ERR_PTR hunk
* linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"
-- Khalid Elmously Thu, 09 Jul 2020
16:03:14 -0400
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
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/1877461
Title:
Bionic update: upstream stable patchset 2020-05-07
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2020-05-07
Ported from the following upstream stable releases:
v4.14.178, v4.19.119
from git://git.kernel.org/
ext4: fix extent_status fragmentation for plain files
net: ipv4: avoid unused variable warning for sysctl
drm/msm: Use the correct dma_sync calls harder
crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static
vti4: removed duplicate log message.
watchdog: reset last_hw_keepalive time at start
scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
ceph: return ceph_mdsc_do_request() errors from __get_parent()
ceph: don't skip updating wanted caps when cap is stale
pwm: rcar: Fix late Runtime PM enablement
scsi: iscsi: Report unbind session event when the target has been removed
ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map()
kernel/gcov/fs.c: gcov_seq_next() should increase position index
selftests: kmod: fix handling test numbers above 9
ipc/util.c: sysvipc_find_ipc() should increase position index
s390/cio: avoid duplicated 'ADD' uevents
pwm: renesas-tpu: Fix late Runtime PM enablement
pwm: bcm2835: Dynamically allocate base
perf/core: Disable page faults when getting phys address
PCI/ASPM: Allow re-enabling Clock PM
mm, slub: restore the original intention of prefetch_freepointer()
cxgb4: fix large delays in PTP synchronization
ipv6: fix restrict IPV6_ADDRFORM operation
macsec: avoid to set wrong mtu
macvlan: fix null dereference in macvlan_device_event()
net: bcmgenet: correct per TX/RX ring statistics
net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
net/x25: Fix x25_neigh refcnt leak when receiving frame
tcp: cache line align MAX_TCP_HEADER
team: fix hang in team_mode_get()
net: dsa: b53: Fix ARL register definitions
xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
vrf: Check skb for XFRM_TRANSFORMED flag
KEYS: Avoid false positive ENOMEM error on key read
ALSA: hda: Remove ASUS ROG Zenith from the blacklist
iio: adc: stm32-adc: fix sleep in atomic context
iio: xilinx-xadc: Fix ADC-B powerdown
iio: xilinx-xadc: Fix clearing interrupt when enabling trigger
iio: xilinx-xadc: Fix sequencer configuration for aux channels in
simultaneous mode
fs/namespace.c: fix mountpoint reference counter race
USB: sisusbvga: Change port variable from signed to unsigned
USB: Add USB_QUIRK_DELAY_CTRL_MSG and USB_QUIRK_DELAY_INIT for Corsair K70
RGB RAPIDFIRE
USB: early: Handle AMD's spec-compliant identifiers, too
USB: core: Fix free-while-in-use bug in the USB S-Glibrary
USB: hub: Fix handling of connect changes during sleep
overflow.h: Add arithmetic shift helper
vmalloc: fix remap_vmalloc_range() bounds checks
mm/hugetlb: fix a addressing exception caused by huge_pte_offset
mm/ksm: fix NULL pointer dereference when KSM zero page is enabled
tools/vm: fix cross-compile build
ALSA: usx2y: Fix potential NULL dereference
ALSA: hda/realtek - Add new codec supported for ALC245
ALSA: usb-audio: Fix usb audio refcnt leak when getting spdif
ALSA: usb-audio: Filter out unsupported sample rates on Focusrite devices
tpm/tpm_tis: Free IRQ if probing fails
tpm: ibmvtpm: retry on H_CLOSED in tpm_ibmvtpm_send()
KVM: Check validity of resolved slot when searching memslots
KVM: VMX: Enable machine check support for 32bit targets
tty: hvc: fix buffer overflow during hvc_alloc().
tty: rocket, avoid OOB access
usb-storage: Add unusual_devs entry for
[Kernel-packages] [Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108
This bug was fixed in the package linux - 4.15.0-111.112 --- linux (4.15.0-111.112) bionic; urgency=medium * bionic/linux: 4.15.0-111.112 -proposed tracker (LP: #1886999) * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - SAUCE: mlxsw: Add missmerged ERR_PTR hunk * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668) - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups" -- Khalid Elmously Thu, 09 Jul 2020 16:03:14 -0400 ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1886668 Title: linux 4.15.0-109-generic network DoS regression vs -108 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] On systems using cgroups and sockets extensively, like docker, kubernetes, lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic. [Fix] Revert the patch that disables sk_alloc cgroup refcounting when tasks are added to net_prio cgroup. [Test case] Test that such environments where the issue is reproduced survive some hours of uptime. A different bug was reproduced with a work-in-progress code and was not reproduced with the culprit reverted. [Regression potential] The reverted commit fix a memory leak on similar scenarios. But a leak is better than a crash. Two other bugs have been opened to track a real fix for this issue and the leak. -- Reported from a user: Several of our infrastructure VMs recently started crashing (oops attached), after they upgraded to -109. -108 appears to be stable. Analysing the crash, it appears to be a wild pointer access in a BPF filter, which makes this (probably) a network-traffic triggered crash. [ 696.396831] general protection fault: [#1] SMP PTI [ 696.396843] Modules linked in: iscsi_target_mod target_core_mod ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse i2c_piix4 pata_acpi floppy [ 696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic #110-Ubuntu [ 696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018 [ 696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0 [ 696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292 [ 696.397015] RAX: 6d69546e6f697469 RBX: RCX: 0014 [ 696.397028] RDX: RSI: 893fd036 RDI: 893fb5154800 [ 696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: [ 696.397058] R10: R11: 0003 R12: 0014 [ 696.397075] R13: 893fb5154800 R14: 0020 R15: 893fc6ba4d00 [ 696.397091] FS: () GS:893fdcb8() knlGS: [ 696.397107] CS: 0010 DS: ES: CR0: 80050033 [ 696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 003606e0 [ 696.397135] DR0: DR1: DR2: [ 696.397152] DR3: DR6: fffe0ff0 DR7: 0400 [ 696.397169] Call Trace: [ 696.397175] [ 696.397183] sk_filter_trim_cap+0xd0/0x1b0 [ 696.397191] tcp_v4_rcv+0x8b7/0xa80 [ 696.397199] ip_local_deliver_finish+0x66/0x210 [ 696.397208] ip_local_deliver+0x7e/0xe0 [ 696.397215] ? ip_rcv_finish+0x430/0x430 [ 696.397223] ip_rcv_finish+0x129/0x430 [ 696.397230] ip_rcv+0x296/0x360 [ 696.397238] ? inet_del_offload+0x40/0x40 [ 696.397249] __netif_receive_skb_core+0x432/0xb80 [ 696.397261] ? skb_send_sock+0x50/0x50 [ 696.397271] ? tcp4_gro_receive+0x137/0x1a0 [ 696.397280] __netif_receive_skb+0x18/0x60 [ 696.397290] ? __netif_receive_skb+0x18/0x60 [ 696.397300] netif_receive_skb_internal+0x45/0xe0 [ 696.397309] napi_gro_receive+0xc5/0xf0 [ 696.397317] xennet_poll+0x9ca/0xbc0 [ 696.397325]
[Kernel-packages] [Bug 1883498] Re: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic
I can confirm that since booting on 4.4.0-185 (~24h ago), we have not experienced any panics on our systems; while we had 4 panics in less than 24h on 4.4.0-184. -- 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/1883498 Title: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: I happened to do an upgrade on a number of servers last week. Some of them got 4.4.0-179-generic and the ones upgraded a bit later during the week got 4.4.0-184-generic as it was just released. The ones with 4.4.0-184-generic started getting stuck. With linux-crashdump installed I obtained the dmesgs and crash dumps. The backtrace appears somewhat similar to #202669 but that one only happened on bare hardware for us - this one is on KVM virtual instances. #202669 paniced in icmpv6_route_lookup and this one dies already in icmpv6_send. Between 2020-06-11 and 2020-06-15, on a set of 12 VMs running 4.4.0-184-generic, there were 85 crashes like this, on servers with noticeable IPv6 traffic. All of the 12 VMs with 4.4.0-184-generic crashed at least once. (There are more than 12 VMs experiencing this, this is just the set I had linux-crashdump on.) [57063.487084] BUG: unable to handle kernel NULL pointer dereference at 0018 [57063.487184] IP: [] icmp6_send+0x1fb/0x970 [57063.487218] PGD 0 [57063.487231] Oops: [#1] SMP [57063.488665] Call Trace: [57063.488679] [57063.488705] [] ? __netif_receive_skb+0x18/0x60 [57063.488739] [] ? task_tick_fair+0x4c8/0x8e0 [57063.488771] [] ? _raw_spin_unlock_bh+0x20/0x50 [57063.488802] [] icmpv6_send+0x21/0x30 [57063.488829] [] ip6_expire_frag_queue+0x115/0x1b0 [57063.488862] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [57063.488897] [] nf_ct_frag6_expire+0x1f/0x30 [nf_defrag_ipv6] [57063.488937] [] call_timer_fn+0x37/0x140 [57063.488965] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [57063.489002] [] run_timer_softirq+0x234/0x330 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Can you please explain how to apply the patch in #9. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883676] Re: ZFS performance drops suddenly
It would be interesting in knowing the following data:
1. How much memory does the machine have when booted?
run: free
2. What the arcstats look like when it goes slowly
use: cat /proc/spl/kstat/zfs/arcstats
thanks
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1883676
Title:
ZFS performance drops suddenly
Status in zfs-linux package in Ubuntu:
Incomplete
Bug description:
Run Phoronix Flexible IO / Random write benchmark.
After running the benchmark repeatedly multiple times (occasionally it can be
30 minutes or 8 hours), the performance drops suddenly. The only way (I know
of) to get back to high performance is reboot.
---
$ for i in $(seq 1 1000); do printf "2\n4\n2\n1\n1\n1\nn\n" |
phoronix-test-suite run fio | awk '/Average.*IOPS/ {print $2}' >> /tmp/iops;
done
$ less /tmp/iops
...
2095
2095
2093
783
388
389
...
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zfsutils-linux 0.7.5-1ubuntu16.9
ProcVersionSignature: User Name 5.3.0-1023.25~18.04.1-aws 5.3.18
Uname: Linux 5.3.0-1023-aws x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
Date: Tue Jun 16 08:55:01 2020
Ec2AMI: ami-06fd83ae47b05282f
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1f
Ec2InstanceType: c4.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.sudoers.d.zfs: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1883676/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
@gogolink, I built a new testing kernel, if you have time, please help test it. If it still can't work, we have to bisect if we want to fix it in the 5.4 kernel. https://people.canonical.com/~hwang4/lp1886341/v2/ thx. -- 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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05) Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: wayland-session focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu) Status: New => Confirmed ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions --
[Kernel-packages] [Bug 1887391] [NEW] groovy/linux-raspi: Upstream raspberrypi patchset 2020-07-07
Public bug reported: Upstream raspberrypi patchset 2020-07-07 Ported from the following raspberrypi branch: rpi-5.7.y from https://github.com/raspberrypi/linux.git ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed ** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1887391 Title: groovy/linux-raspi: Upstream raspberrypi patchset 2020-07-07 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: Confirmed Bug description: Upstream raspberrypi patchset 2020-07-07 Ported from the following raspberrypi branch: rpi-5.7.y from https://github.com/raspberrypi/linux.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1887391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108
Concur. Previously in bionic 4.15.0-109 I would get this within 5 or 6 hours *max* (often much less) with 4.15.0-111 I'm at about 24 hours so far and no sign. Looks good. -- 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/1886668 Title: linux 4.15.0-109-generic network DoS regression vs -108 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] On systems using cgroups and sockets extensively, like docker, kubernetes, lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic. [Fix] Revert the patch that disables sk_alloc cgroup refcounting when tasks are added to net_prio cgroup. [Test case] Test that such environments where the issue is reproduced survive some hours of uptime. A different bug was reproduced with a work-in-progress code and was not reproduced with the culprit reverted. [Regression potential] The reverted commit fix a memory leak on similar scenarios. But a leak is better than a crash. Two other bugs have been opened to track a real fix for this issue and the leak. -- Reported from a user: Several of our infrastructure VMs recently started crashing (oops attached), after they upgraded to -109. -108 appears to be stable. Analysing the crash, it appears to be a wild pointer access in a BPF filter, which makes this (probably) a network-traffic triggered crash. [ 696.396831] general protection fault: [#1] SMP PTI [ 696.396843] Modules linked in: iscsi_target_mod target_core_mod ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse i2c_piix4 pata_acpi floppy [ 696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic #110-Ubuntu [ 696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018 [ 696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0 [ 696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292 [ 696.397015] RAX: 6d69546e6f697469 RBX: RCX: 0014 [ 696.397028] RDX: RSI: 893fd036 RDI: 893fb5154800 [ 696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: [ 696.397058] R10: R11: 0003 R12: 0014 [ 696.397075] R13: 893fb5154800 R14: 0020 R15: 893fc6ba4d00 [ 696.397091] FS: () GS:893fdcb8() knlGS: [ 696.397107] CS: 0010 DS: ES: CR0: 80050033 [ 696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 003606e0 [ 696.397135] DR0: DR1: DR2: [ 696.397152] DR3: DR6: fffe0ff0 DR7: 0400 [ 696.397169] Call Trace: [ 696.397175] [ 696.397183] sk_filter_trim_cap+0xd0/0x1b0 [ 696.397191] tcp_v4_rcv+0x8b7/0xa80 [ 696.397199] ip_local_deliver_finish+0x66/0x210 [ 696.397208] ip_local_deliver+0x7e/0xe0 [ 696.397215] ? ip_rcv_finish+0x430/0x430 [ 696.397223] ip_rcv_finish+0x129/0x430 [ 696.397230] ip_rcv+0x296/0x360 [ 696.397238] ? inet_del_offload+0x40/0x40 [ 696.397249] __netif_receive_skb_core+0x432/0xb80 [ 696.397261] ? skb_send_sock+0x50/0x50 [ 696.397271] ? tcp4_gro_receive+0x137/0x1a0 [ 696.397280] __netif_receive_skb+0x18/0x60 [ 696.397290] ? __netif_receive_skb+0x18/0x60 [ 696.397300] netif_receive_skb_internal+0x45/0xe0 [ 696.397309] napi_gro_receive+0xc5/0xf0 [ 696.397317] xennet_poll+0x9ca/0xbc0 [ 696.397325] net_rx_action+0x140/0x3a0 [ 696.397334] __do_softirq+0xe4/0x2d4 [ 696.397344] irq_exit+0xc5/0xd0 [ 696.397352] xen_evtchn_do_upcall+0x30/0x50 [ 696.397361] xen_hvm_callback_vector+0x90/0xa0 [ 696.397371] [ 696.397378] RIP: 0010:native_safe_halt+0x12/0x20 [ 696.397390] RSP: 0018:94c4862cbe80 EFLAGS: 0246 ORIG_RAX: ff0c [ 696.397405] RAX: 8efc1800 RBX: 0006 RCX:
[Kernel-packages] [Bug 1887386] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1887386 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1887386 Title: Kernel 5.4.0.-40 Cinamon: screen not enabled after boot Status in linux package in Ubuntu: Incomplete Bug description: No button nor touch is active, yet you can move the pointer. Description: Linux Mint 20 Release: 20 System infos: https://termbin.com/o0o6 But it does work with Mint 20.04 and kernel 4.15.0-109 thank's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887156] Re: USB ports not working on the Pi 4 rev 1.4 board
** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1887156 Title: USB ports not working on the Pi 4 rev 1.4 board Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Bionic: Confirmed Status in linux-raspi2 source package in Eoan: Confirmed Bug description: [Impact] USB on the Pi 4B rev 1.4 running the raspi 5.3 kernel is non- functional. [Test Case] See original description below. [Regression Potential] Low. The changes are isolated to the PCIe driver used for the Raspberry Pi. The commit is a clean cherry-pick from the raspi 5.4 kernel. [Original Description] On the Pi 4 board revision 1.4 (of which the 8Gb model is currently the main example), the VL805 USB controller doesn't appear to be recognized by the 5.3 kernel. To reproduce: * Flash a current bionic image (e.g. http://cdimage.ubuntu.com/releases/bionic/release/ubuntu-18.04.4-preinstalled-server-arm64+raspi4.img.xz) * Boot the card on an older Pi model (3, 4 rev 1.2, etc.) * sudo add-apt-repository ppa:waveform/firmware * sudo apt install linux-firmware-raspi2 (the rev 1.4 requires a newer firmware package to boot; this PPA contains a test package with a back-ported firmware) * Boot the card on a Pi 4 rev 1.4 * Observe USB2 and USB3 ports do not work * Boot the card on an older Pi 4 rev 1.2 * Observe USB2 and USB3 ports do work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1887156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887386] [NEW] Kernel 5.4.0.-40 Cinamon: screen not enabled after boot
Public bug reported: No button nor touch is active, yet you can move the pointer. Description:Linux Mint 20 Release:20 System infos: https://termbin.com/o0o6 But it does work with Mint 20.04 and kernel 4.15.0-109 thank's ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "journal" https://bugs.launchpad.net/bugs/1887386/+attachment/5392311/+files/journal -- 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/1887386 Title: Kernel 5.4.0.-40 Cinamon: screen not enabled after boot Status in linux package in Ubuntu: Incomplete Bug description: No button nor touch is active, yet you can move the pointer. Description: Linux Mint 20 Release: 20 System infos: https://termbin.com/o0o6 But it does work with Mint 20.04 and kernel 4.15.0-109 thank's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877270] Re: Devlink - add RoCE disable kernel support
Waiting on Mellanox to report back on test kernels. ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Jeff Lane (bladernr) -- 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/1877270 Title: Devlink - add RoCE disable kernel support Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] RoCE disable feature was added to the kernel v5.5. This feature was requested by Mellanox customers that use Ubuntu 20.04, and it's a very high important to deliver this feature to the customers in one of ubuntu 20.04 SRU. [SHORT DESCRIPTION] RoCE enablement state controls driver support for RoCE traffic. When RoCE is disabled, there is no gid table, only raw ethernet QPs are supported and traffic on the well known UDP RoCE port is handled as raw ethernet traffic. [Test Case] To change RoCE enablement state a user must change the driverinit cmode value and run devlink reload. User command examples: - Disable RoCE:: $ devlink dev param set pci/:06:00.0 name enable_roce value false cmode driverinit $ devlink dev reload pci/:06:00.0 - Read RoCE enablement state:: $ devlink dev param show pci/:06:00.0 name enable_roce pci/:06:00.0: name enable_roce type generic values: cmode driverinit value true [Regression Potential] This feature shouldn't affect the regression because it's only adding support for RoCE enable/disable. Also, This feature was tested internally by Mellanox QA teams those tests logs/results are private unfortunately i can't share it here [Other Info] Feature patchset: 4383cfcc65e7 net/mlx5: Add devlink reload 32680da71034 net/mlx5: Remove unneeded variable in mlx5_unload_one 94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state b5a498baf929 IB/mlx5: Rename profile and init methods cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param 6c7295e13ffd devlink: Add new "enable_roce" generic device param All are in upstream in 5.5, so no pick into Groovy necessary userspace: No userspace dependency on this. the feature uses the devlink param functionality which already exists in UB20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
@Corbin, You set "regression" in the bug title, suppose the audio in the 5.4.0-26 kernel works, what version of kernel is the 1st can't work -28, -33, -39 or -40? After I get the 1st failure kernel, I could check what patch introduced the regression. thx. -- 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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05) Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: wayland-session focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor:
[Kernel-packages] [Bug 1886937] Re: limited hardware support AMD 4700u HP Envy x360 13-ay003nd
https://wiki.archlinux.org/index.php/Power_management/Suspend_and_hibernate#Required_kernel_parameters -- 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/1886937 Title: limited hardware support AMD 4700u HP Envy x360 13-ay003nd Status in linux package in Ubuntu: Confirmed Bug description: Suspend/Hibernate: screen goes off, nothing else happens. After user interaction, screen turns on. Login screen is shown. Sometimes screen does not turn on: physical reboot required. kernel upgrade to 5.8rc3 or 5.8rc4 has no effect. Brightness: Adjusting brightness has no effect, nightmode has no effect. Partial solution: kernel upgrade 5.8rc3 or 5.8rc4 solves this partially, brightness can be adjusted and nightmode works But after a reboot brightness is always at max. Also brightness cannot be lowered as much as normally expected. CPU & fan: CPU is always high, 5.8rc3 solves this partially, fan is still always on and quite high (after clean Ubuntu install, nothing configured or installed). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: asterix 881 F pulseaudio /dev/snd/controlC1: asterix 881 F pulseaudio /dev/snd/controlC0: asterix 881 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Jul 9 12:21:02 2020 InstallationDate: Installed on 2020-07-09 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ay0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=e2b48a5b-5ae8-41c4-a6d0-7eb17bb02dd3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876E dmi.board.vendor: HP dmi.board.version: 12.30 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd05/07/2020:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:rvnHP:rn876E:rvr12.30:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx dmi.product.sku: 1D5H9EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I'll start the SRU for this issue soon -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
It is using oem2.inf I add the line at boot, by editing the grub and adding it at the end of the line which starts with 'linux', and I don't want to get to excited, but so far, so good... ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392309/+files/dmesg -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
Sorry, I uninstalled the updated kernel; should I install it again? Where do I configure that line? during boot? -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias:
[Kernel-packages] [Bug 1875200] Re: [amdgpu] Entire computer freezes shortly after bootup
Can you please follow [1]? Hopefully we can collect more info if the freeze is caused by a kernel panic... [1] https://wiki.ubuntu.com/Kernel/CrashdumpRecipe -- 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/1875200 Title: [amdgpu] Entire computer freezes shortly after bootup Status in linux package in Ubuntu: Incomplete Bug description: I'm not sure if this bug was filed completely; I used the "ubuntu-bug" command which gathered a lot of information and files, but then the bugs.launchpad.net site timeouted and I'm not sure if the information I entered before and the files that were gathered have actually been submitted. Summary: after an upgrade to Ubuntu 20.04 my entire computer freezes some seconds after bootup. It does not even reply to pings anymore and remote logins stop working as well. When booting it in recovery mode and then immediately using the menu option to continue booting, it appears to work reliably, but it only detects one monitor and there is no 3d acceleration. I've seen freezes happening at the following points: a) at the stage of a black screnen saying "lenovo" in the middle and "ubuntu" at the bottom (of both monitors) b) when asking for username and password to login c) after login When I was using the same computer with Ubuntu 19.10, there was no such problem. The computer is a Lenovo ThinkCentre M920x, the graphics card used is 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] (rev ef) with two monitors (3840x2160) connected via MiniDisplayPort ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 14:29:19 2020 DistUpgraded: 2020-04-25 14:33:16,904 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop 9 Series) [17aa:3135] Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] [1002:67ff] (rev ef) (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Baffin [Radeon RX 550 640SP / RX 560/560X] [1642:1725] InstallationDate: Installed on 2020-03-29 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 10S1002NMZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ff61fce1-cc83-4bbe-bc88-09cdd2ac7471 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) XorgLogOld: dmi.bios.date: 02/17/2020 dmi.bios.vendor: LENOVO dmi.bios.version: M1UKT50A dmi.board.name: 3135 dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN 3305220985042 dmi.chassis.type: 35 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1UKT50A:bd02/17/2020:svnLENOVO:pn10S1002NMZ:pvrThinkCentreM920x:rvnLENOVO:rn3135:rvrSDK0T08861WIN3305220985042:cvnLENOVO:ct35:cvrNone: dmi.product.family: ThinkCentre M920x dmi.product.name: 10S1002NMZ dmi.product.sku: LENOVO_MT_10S1_BU_Think_FM_ThinkCentre M920x dmi.product.version: ThinkCentre M920x dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877871] Re: [radeon] X windows hangs following upgrade from 18.04 to 20.04
Thanks. The next step is to bisect the kernel. First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the working version you found) $ git bisect bad $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it still have the same issue, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. -- 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/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885270] Re: Touchpad stopped working after upgrading to Ubuntu 20.04
Though different vendor, seems to be similar to lp: #1882388. -- 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/1885270 Title: Touchpad stopped working after upgrading to Ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Bug description: When I upgraded to Ubuntu 20.04 my touchpad stopped working. When I used the command xinput to list the input devices there was a PS/2 Generic Mouse registered instead of my Lenovo Yoga 13 touchpad. I tried to search for the same on the askubuntu forum. I got the answer that to try and remove psmouse and then again add it using the command sudo modprobe -r psmouse; sudo modprobe psmouse This initially solved my problem but later on the same issue arose after restarting the machine. The touchpad also is again reported as a generic mouse if the system is suspended. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lokesh 1790 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 26 16:45:45 2020 InstallationDate: Installed on 2019-08-15 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO Mocca 2.0 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=a610e76e-890e-442a-b764-c81d6becd466 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-15 (42 days ago) dmi.bios.date: 02/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN55WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3196Win8 STD MBR IPG dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pnMocca2.0:pvrYoga13:rvnLENOVO:rnINVALID:rvr3196Win8STDMBRIPG:cvnLENOVO:ct10:cvrYoga13: dmi.product.family: IDEAPAD dmi.product.name: Mocca 2.0 dmi.product.sku: LENOVO_BI_IDEAPAD66 dmi.product.version: Yoga 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887340] Re: system freezes including keyboard and mouse whenever a CD is played
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/ If latest kernel doesn't fix it then we need to bisect kernel. -- 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/1887340 Title: system freezes including keyboard and mouse whenever a CD is played Status in linux package in Ubuntu: Incomplete Bug description: Consistently, whenever a CD is played, the system freezes including keyboard and mouse. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pks1207 F pulseaudio /dev/snd/controlC2: pks1207 F pulseaudio /dev/snd/controlC0: pks1207 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 11:42:33 2020 InstallationDate: Installed on 2020-01-06 (188 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=ff43ab9d-9612-4215-8f0c-d11964542c44 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-16 (57 days ago) dmi.bios.date: 05/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A88-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1702:bd05/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
Ok, this mean it uses PS/2 mouse. Can you please boot to mainline kernel with kernel parameter "dyndbg='file drivers/input/mouse/* +p'", and attach dmesg here? -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias:
[Kernel-packages] [Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108
I confirm that I can't reproduce the bug with the reproducer from comment #7 with bionic/linux 4.15.0-111. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1886668 Title: linux 4.15.0-109-generic network DoS regression vs -108 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] On systems using cgroups and sockets extensively, like docker, kubernetes, lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic. [Fix] Revert the patch that disables sk_alloc cgroup refcounting when tasks are added to net_prio cgroup. [Test case] Test that such environments where the issue is reproduced survive some hours of uptime. A different bug was reproduced with a work-in-progress code and was not reproduced with the culprit reverted. [Regression potential] The reverted commit fix a memory leak on similar scenarios. But a leak is better than a crash. Two other bugs have been opened to track a real fix for this issue and the leak. -- Reported from a user: Several of our infrastructure VMs recently started crashing (oops attached), after they upgraded to -109. -108 appears to be stable. Analysing the crash, it appears to be a wild pointer access in a BPF filter, which makes this (probably) a network-traffic triggered crash. [ 696.396831] general protection fault: [#1] SMP PTI [ 696.396843] Modules linked in: iscsi_target_mod target_core_mod ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse i2c_piix4 pata_acpi floppy [ 696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic #110-Ubuntu [ 696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018 [ 696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0 [ 696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292 [ 696.397015] RAX: 6d69546e6f697469 RBX: RCX: 0014 [ 696.397028] RDX: RSI: 893fd036 RDI: 893fb5154800 [ 696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: [ 696.397058] R10: R11: 0003 R12: 0014 [ 696.397075] R13: 893fb5154800 R14: 0020 R15: 893fc6ba4d00 [ 696.397091] FS: () GS:893fdcb8() knlGS: [ 696.397107] CS: 0010 DS: ES: CR0: 80050033 [ 696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 003606e0 [ 696.397135] DR0: DR1: DR2: [ 696.397152] DR3: DR6: fffe0ff0 DR7: 0400 [ 696.397169] Call Trace: [ 696.397175] [ 696.397183] sk_filter_trim_cap+0xd0/0x1b0 [ 696.397191] tcp_v4_rcv+0x8b7/0xa80 [ 696.397199] ip_local_deliver_finish+0x66/0x210 [ 696.397208] ip_local_deliver+0x7e/0xe0 [ 696.397215] ? ip_rcv_finish+0x430/0x430 [ 696.397223] ip_rcv_finish+0x129/0x430 [ 696.397230] ip_rcv+0x296/0x360 [ 696.397238] ? inet_del_offload+0x40/0x40 [ 696.397249] __netif_receive_skb_core+0x432/0xb80 [ 696.397261] ? skb_send_sock+0x50/0x50 [ 696.397271] ? tcp4_gro_receive+0x137/0x1a0 [ 696.397280] __netif_receive_skb+0x18/0x60 [ 696.397290] ? __netif_receive_skb+0x18/0x60 [ 696.397300] netif_receive_skb_internal+0x45/0xe0 [ 696.397309] napi_gro_receive+0xc5/0xf0 [ 696.397317] xennet_poll+0x9ca/0xbc0 [ 696.397325] net_rx_action+0x140/0x3a0 [ 696.397334] __do_softirq+0xe4/0x2d4 [ 696.397344] irq_exit+0xc5/0xd0 [ 696.397352] xen_evtchn_do_upcall+0x30/0x50 [ 696.397361] xen_hvm_callback_vector+0x90/0xa0 [ 696.397371] [ 696.397378] RIP: 0010:native_safe_halt+0x12/0x20 [ 696.397390] RSP: 0018:94c4862cbe80 EFLAGS: 0246 ORIG_RAX: ff0c [ 696.397405] RAX: 8efc1800 RBX:
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
Can you please also find out which .inf it uses? -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN54WW:bd06/13/2017:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK: dmi.product.family: IDEAPAD
Re: [Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
Sound does *not* work for me on testing kernel 5.4.0-42 I'm attaching the dmseg output. On Mon, Jul 13, 2020 at 12:20 AM Hui Wang <1886...@bugs.launchpad.net> wrote: > We also want to fix this issue in the ubuntu 5.4 kernel, so I built a > testing kernel, could you please test if that testing kernel work or > not, if it doesn't work, please upload a complete dmesg. > > thx. > > https://people.canonical.com/~hwang4/lp1886341/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1886341 > > Title: > Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal > audio devices to fail to load w/o unacceptable workaround (Lenovo > IdeaPad 5 15IIL05) > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal > speakers, headphone jack, and mic do not work at all. No audio devices > appear in the Sound settings or in pavucontrol. By appending options > snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can > get audio working, but the microphone (unsuprisingly) does not work. > Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as > the same effect as dmic_detect=0. Attempts to fix with option > snd_hda_intel device=generic or deveice=auto have had no effect. This > bug does NOT manifest on 5.4.0-26-generic, the kernel version featured > on the 20.04 live media. After installation, and updating to > 5.4.0-40-generic, the bug manifests on the next boot. > > Note that the audio hardware seems to work properly w/o workaround on > a small (< 5%) percentage of boots, but I have been unable to > reproduce this. With the workaround enabled, inxi -A gives > > Audio: > Device-1: Intel Smart Sound Audio driver: snd_hda_intel > Sound Server: ALSA v: k5.4.0-40-generic > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-40-generic 5.4.0-40.44 > ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 > Uname: Linux 5.4.0-40-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.3 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: jill 1374 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sun Jul 5 13:32:58 2020 > InstallationDate: Installed on 2020-07-03 (2 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: LENOVO 81YK > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic > root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-40-generic N/A >linux-backports-modules-5.4.0-40-generic N/A >linux-firmware1.187.1 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/18/2020 > dmi.bios.vendor: LENOVO > dmi.bios.version: DPCN40WW > dmi.board.asset.tag: NO Asset Tag > dmi.board.name: LNVNB161216 > dmi.board.vendor: LENOVO > dmi.board.version: SDK0J40709 WIN > dmi.chassis.asset.tag: NO Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: IdeaPad 5 15IIL05 > dmi.modalias: > dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: > dmi.product.family: IdeaPad 5 15IIL05 > dmi.product.name: 81YK > dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 > dmi.product.version: IdeaPad 5 15IIL05 > dmi.sys.vendor: LENOVO > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu27.3 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 20.04 > InstallationDate: Installed on 2020-07-03 (5 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: LENOVO 81YK > Package: linux (not installed) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic > root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-40-generic N/A >linux-backports-modules-5.4.0-40-generic N/A >linux-firmware1.187.1 > Tags: wayland-session focal > Uname:
[Kernel-packages] [Bug 1886890] Re: sched_rr_get_interval01 from ubuntu_ltp_syscalls failed on 4.4
This issue can be found on X-4.4 P8 / s390x as well (skipped on arm64).
** Tags added: ppc64el s390x
--
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/1886890
Title:
sched_rr_get_interval01 from ubuntu_ltp_syscalls failed on 4.4
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Bug description:
== SRU Justification ==
A new regression test case "sched_rr_get_interval01" for commit 975e155ed873
("sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice tuning knob in
milliseconds"). Has been added to the LTP syscalls test suite.
On Xenial 4.4.0-186.216, this test is failing with:
startup='Wed Jul 8 10:36:58 2020'
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
sched_rr_get_interval01.c:43: INFO: Testing variant: vDSO or syscall with
libc spec
sched_rr_get_interval01.c:60: PASS: sched_rr_get_interval() passed
sched_rr_get_interval01.c:68: PASS: Time quantum 0s 1ns
sched_rr_get_interval01.c:75: FAIL: /proc/sys/kernel/sched_rr_timeslice_ms
!= 100 got 25
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
sched_rr_get_interval01.c:43: INFO: Testing variant: syscall with old kernel
spec
sched_rr_get_interval01.c:60: PASS: sched_rr_get_interval() passed
sched_rr_get_interval01.c:68: PASS: Time quantum 0s 1ns
sched_rr_get_interval01.c:75: FAIL: /proc/sys/kernel/sched_rr_timeslice_ms
!= 100 got 25
HINT: You _MAY_ be missing kernel fixes, see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=975e155ed873
Summary:
passed 4
failed 2
skipped 0
warnings 0
tag=sched_rr_get_interval01 stime=1594204618 dur=0 exit=exited stat=1
core=no cu=0 cs=0
== Fixes ==
975e155ed873 ("sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice
tuning knob in milliseconds")
This patch can be cherry-picked in to the affected Xenial kernel. It's
already been applied in newer kernels.
== Test ==
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1886890-sched_rr_get_interval01/
With the patch applied, this test will pass without any issue.
And it can be simply tested with:
# echo 100 > /proc/sys/kernel/sched_rr_timeslice_ms
# cat /proc/sys/kernel/sched_rr_timeslice_ms
100
(was 25 before the patch)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886890/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Note: the patch (if #101 is the "right" solution) applies to the package "grub-common" that contains /etc/grub.d/10_linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
Re: [Kernel-packages] [Bug 1887340] Re: system freezes including keyboard and mouse whenever a CD is played
No. 20.04 On Mon, Jul 13, 2020 at 2:41 PM Kai-Heng Feng <1887...@bugs.launchpad.net> wrote: > Did the issue happen on 19.10? > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1887340 > > Title: > system freezes including keyboard and mouse whenever a CD is played > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887340/+subscriptions > -- 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/1887340 Title: system freezes including keyboard and mouse whenever a CD is played Status in linux package in Ubuntu: Incomplete Bug description: Consistently, whenever a CD is played, the system freezes including keyboard and mouse. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pks1207 F pulseaudio /dev/snd/controlC2: pks1207 F pulseaudio /dev/snd/controlC0: pks1207 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 11:42:33 2020 InstallationDate: Installed on 2020-01-06 (188 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=ff43ab9d-9612-4215-8f0c-d11964542c44 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-16 (57 days ago) dmi.bios.date: 05/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A88-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1702:bd05/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881214] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel switch, iwlwifi Microcode SW Error: FW error in SYNC CMD CHANNEL_SWITCH_TIME_EVENT_CMD
Same issue here. Ubuntu 20.04 fully updated running on a Dell Latitude 5590. Started after VPN connection over wifi. It works ok sometime and then VPN and network stopped working in this case. Changing to cabled connection just in case meanwhile the issue gets solved. Pasting repeated log just in case (few lines): Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989816] wlp2s0: Failed check-sdata-in-driver check, flags: 0x0 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989848] WARNING: CPU: 3 PID: 21572 at net/mac80211/driver-ops.h:17 drv_sta_state+0x254/0x3 f0 [mac80211] Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989848] Modules linked in: rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlin k xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter bridge stp llc ccm ip 6table_filter ip6_tables iptable_filter bpfilter cmac algif_hash algif_skcipher af_alg aufs bnep overlay snd_hda_codec_hdmi mei_hdcp intel_r apl_msr dell_rbtn snd_hda_codec_realtek snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp nls_iso8859_1 snd_hda_intel coretemp snd _intel_dspcfg kvm_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi crct10dif_pclmul ghash_ clmulni_intel uvcvideo dell_laptop ledtrig_audio dell_smm_hwmon videobuf2_vmalloc snd_seq aesni_intel joydev dell_wmi crypto_simd dell_smbio s dcdbas snd_seq_device iwlmvm cryptd videobuf2_memops glue_helper mac80211 intel_cstate snd_timer intel_rapl_perf videobuf2_v4l2 libarc4 bt usb videobuf2_common input_leds btrtl btbcm i915 iwlwifi btintel Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989879] videodev bluetooth snd serio_raw intel_wmi_thunderbolt mc dell_wmi_descriptor wmi _bmof ecdh_generic rtsx_pci_ms soundcore cfg80211 hid_multitouch ecc memstick mei_me drm_kms_helper mei processor_thermal_device i2c_algo_bi t intel_rapl_common ucsi_acpi fb_sys_fops intel_xhci_usb_role_switch typec_ucsi syscopyarea sysfillrect intel_soc_dts_iosf roles sysimgblt i ntel_pch_thermal typec int3400_thermal acpi_thermal_rel mac_hid dell_smo8800 int3403_thermal int340x_thermal_zone intel_hid acpi_pad sparse_ keymap sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic rtsx_pci_sdmmc crc32_pclmul nvme intel_lpss_pci i ntel_lpss e1000e i2c_i801 ahci idma64 i2c_hid nvme_core rtsx_pci libahci virt_dma wmi hid video Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989908] CPU: 3 PID: 21572 Comm: kworker/u8:3 Tainted: GW 5.4.0-40-generic #44-Ubuntu Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989908] Hardware name: Dell Inc. Latitude 5590/0PF5TR, BIOS 1.12.1 11/08/2019 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989917] Workqueue: phy0 ieee80211_csa_connection_drop_work [mac80211] Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989926] RIP: 0010:drv_sta_state+0x254/0x3f0 [mac80211] Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989927] Code: 00 45 31 ed e9 66 fe ff ff 48 8b 83 78 04 00 00 48 8d b3 98 04 00 00 48 c7 c 7 c8 b8 b7 c0 48 85 c0 48 0f 45 f0 e8 57 71 ba f3 <0f> 0b 41 bd fb ff ff ff e9 3d fe ff ff 65 8b 05 e8 5c 51 3f 89 c0 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989927] RSP: 0018:a8344385fc98 EFLAGS: 00010282 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989928] RAX: RBX: 9c3c93d348c0 RCX: 0006 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989928] RDX: 0007 RSI: 0082 RDI: 9c3c9e3978c0 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989929] RBP: a8344385fcd0 R08: 040d87ca R09: 0004 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989929] R10: R11: 0001 R12: 9c3c99ba07a0 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989930] R13: 9c3c99ba07a0 R14: 0004 R15: 9c3c99ba0d68 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989930] FS: () GS:9c3c9e38() knlGS: Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989931] CS: 0010 DS: ES: CR0: 80050033 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989931] CR2: 7f217f6163c0 CR3: 0001ba00a002 CR4: 003606e0 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989932] DR0: DR1: DR2: Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989932] DR3: DR6: fffe0ff0 DR7: 0400 Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989933] Call Trace: Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989942] sta_info_move_state+0x276/0x370 [mac80211] Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989950] __sta_info_destroy_part2+0x2f/0x180 [mac80211] Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [ 9218.989961] __sta_info_flush+0x128/0x180 [mac80211] Jul 13 12:02:15 ipaz-Latitude-5590 kernel: [
[Kernel-packages] [Bug 1887362] Re: CPU can't reach full speed after resuming from sleep
Dmesg above has such a faulty resume. Laptop went to sleep `Jul 12 19:56:05` and awoke to a faulty cpu state at `Jul 13 09:17:14` -- 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/1887362 Title: CPU can't reach full speed after resuming from sleep Status in linux package in Ubuntu: Confirmed Bug description: This happens very sporadically after upgrading to 20.04 (not an issue before focal). Sometimes, after resuming from sleep, the CPU won't go over 1.23GHz. It will scale up and down between this and the min speed (800MHz) but go no higher. Putting the laptop to sleep and resuming brings it back to normal. I can't find a reliable way of reproducing it as it seems to happen at random. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.40.43 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luis 1013521 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: sway Date: Mon Jul 13 09:27:33 2020 InstallationDate: Installed on 2019-08-17 (330 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a0 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vglinux-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-31 (103 days ago) dmi.bios.date: 05/22/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.2 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887362] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1887362 Title: CPU can't reach full speed after resuming from sleep Status in linux package in Ubuntu: Confirmed Bug description: This happens very sporadically after upgrading to 20.04 (not an issue before focal). Sometimes, after resuming from sleep, the CPU won't go over 1.23GHz. It will scale up and down between this and the min speed (800MHz) but go no higher. Putting the laptop to sleep and resuming brings it back to normal. I can't find a reliable way of reproducing it as it seems to happen at random. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.40.43 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luis 1013521 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: sway Date: Mon Jul 13 09:27:33 2020 InstallationDate: Installed on 2019-08-17 (330 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a0 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vglinux-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-31 (103 days ago) dmi.bios.date: 05/22/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.2 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
** Attachment added: "deviceManager_1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392299/+files/deviceManager_1.png -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias:
[Kernel-packages] [Bug 1882088] Re: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations
A patched kernel (that I created during the SRU preparation and test compile) is available here: https://people.canonical.com/~fheimes/lp1882088/ for further testing. -- 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/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * Connections from later-level SMC (protocol) versions to an SMC- enabled server on Linux hang. * Later-level versions of SMC (although backwards-compatible) present a higher version number and use larger messages during the CLC handshake. * The solution to avoid such hangs is to introduce toleration for later version numbers, and support CLC messages of arbitrary length. [Fix] * fb4f79264c0fc6fd5a68ffe3e31bfff97311e1f1 fb4f79264c0f "net/smc: tolerate future SMCD versions" [Test Case] * Requires two IBM z13/z13s GA2 or LinuxONE Rockhopper/Emperor systems with RoCE Express adapter v2(.1) for SMC-D usage. * One system needs to run the initial SMC-D version, the other a newer version. * Establish a connection between both system and monitor/verify if it's reliable or if it hangs. [Regression Potential] * The regression can be considered as medium to low: * Since SMC-D is a pretty special way of doing shared memory communications and not that wide-spread. * However, the code that is changed is common code. * But the patch is straight forward and only modifies /net/smc/smc_clc.c and /net/smc/smc_clc.h * It largely bumps limits (allows larger messages), adds a check and introduces toleration, rather than changing control or flow. [Other] * The above fix is currently in 'linux-next' and tagged with next-20200709. * It is still assumed that it gets accepted for 5.8. * However, since this is not guaranteed this SRU request is for focal and groovy - to make sure that no potential regressions are introduced in case the patch will not end up in 5.8. __ Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
** Attachment added: "deviceManager_3.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392301/+files/deviceManager_3.png ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias:
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
** Attachment added: "deviceManager_2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392300/+files/deviceManager_2.png -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias:
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
** Attachment added: "deviceManager" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392298/+files/deviceManager_0.png -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias:
[Kernel-packages] [Bug 1886234] Re: libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1 with -EEXIST, don't try to register things with the same name in the same directory.
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1886234 Title: libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1 with -EEXIST, don't try to register things with the same name in the same directory. Status in linux package in Ubuntu: Incomplete Bug description: After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and turning the VM off, I see this in dmesg: [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, widening DMA allocations [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config. [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6 [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1 [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1 [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1 [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config. [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on [ 4680.392669] sysfs: cannot create duplicate filename '/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1' [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G OE 5.4.0-40-generic #44-Ubuntu [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG STRIX X570-E GAMING, BIOS 1409 05/12/2020 [ 4680.392674] Call Trace: [ 4680.392681] dump_stack+0x6d/0x9a [ 4680.392684] sysfs_warn_dup.cold+0x17/0x35 [ 4680.392685] sysfs_create_dir_ns+0xb8/0xd0 [ 4680.392687] kobject_add_internal+0xbd/0x2b0 [ 4680.392688] kobject_add+0x7e/0xb0 [ 4680.392692] device_add+0x132/0x6b0 [ 4680.392696] snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device] [ 4680.392702] __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392706] snd_device_register_all+0x33/0x50 [snd] [ 4680.392709] snd_card_register+0x62/0x1b0 [snd] [ 4680.392712] ? snd_hwdep_new+0xfe/0x146 [snd_hwdep] [ 4680.392715] snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth] [ 4680.392717] snd_emux_register+0x11a/0x190 [snd_emux_synth] [ 4680.392719] ? 0xc1065000 [ 4680.392721] ? sf_sample_new+0x20/0x20 [snd_emux_synth] [ 4680.392723] snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth] [ 4680.392725] really_probe+0x2b3/0x3e0 [ 4680.392726] driver_probe_device+0xbc/0x100 [ 4680.392728] __device_attach_driver+0x71/0xd0 [ 4680.392729] ? driver_allows_async_probing+0x50/0x50 [ 4680.392731] bus_for_each_drv+0x84/0xd0 [ 4680.392732] __device_attach+0xe1/0x160 [ 4680.392734] device_initial_probe+0x13/0x20 [ 4680.392735] bus_probe_device+0x8f/0xa0 [ 4680.392737] device_add+0x3c7/0x6b0 [ 4680.392740] ? __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392742] snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device] [ 4680.392745] __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392748] snd_device_register_all+0x33/0x50 [snd] [ 4680.392751] snd_card_register+0x62/0x1b0 [snd] [ 4680.392753] ? snd_seq_device_new+0xd0/0x126 [snd_seq_device] [ 4680.392758] snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1] [ 4680.392761] local_pci_probe+0x48/0x80 [ 4680.392763] pci_device_probe+0x10f/0x1b0 [ 4680.392765] really_probe+0x159/0x3e0 [ 4680.392766] driver_probe_device+0xbc/0x100 [ 4680.392767] __device_attach_driver+0x71/0xd0 [ 4680.392769] ? driver_allows_async_probing+0x50/0x50 [ 4680.392770] bus_for_each_drv+0x84/0xd0 [ 4680.392771] __device_attach+0xe1/0x160 [ 4680.392773] device_attach+0x10/0x20 [ 4680.392775] bus_rescan_devices_helper+0x39/0x80 [ 4680.392777] drivers_probe_store+0x36/0x60 [ 4680.392778] bus_attr_store+0x27/0x30 [ 4680.392780] sysfs_kf_write+0x3e/0x50 [ 4680.392782] kernfs_fop_write+0xda/0x1b0 [ 4680.392784] __vfs_write+0x1b/0x40 [ 4680.392785] vfs_write+0xb9/0x1a0 [ 4680.392786] ksys_write+0x67/0xe0 [ 4680.392788] __x64_sys_write+0x1a/0x20 [ 4680.392790] do_syscall_64+0x57/0x190 [ 4680.392793] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 4680.392794] RIP: 0033:0x7f52456222cf [ 4680.392795] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 fd ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 5c fd ff ff 48 [ 4680.392796] RSP: 002b:7f52023615a0 EFLAGS: 0293 ORIG_RAX: 0001 [ 4680.392798] RAX: ffda RBX: 000c RCX: 7f52456222cf
[Kernel-packages] [Bug 1886977] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1886977 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1886977 Title: [Toshiba Portege R830] Grid-like cursor movement on touchpad Status in linux package in Ubuntu: Incomplete Bug description: Moving cursor using touchpad goes in zigzag pattern, when moving diagonally. The laptop is Toshiba Portege R830 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libinput10 1.10.4-1ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jul 9 17:35:34 2020 SourcePackage: libinput UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
