[Kernel-packages] [Bug 1878918] Re: Button power don’t shutdown
[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/1878918 Title: Button power don’t shutdown Status in linux package in Ubuntu: Expired Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 I realized that since I updated the system to version 20.04 it is not responding when I press the shutdown button on my notebook, even though in the power management in the settings it is to shut down when I press it. When I put it to suspend, he responds, but when I put it off he does nothing 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: neto 1092 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 15 10:19:38 2020 InstallationDate: Installed on 2020-02-28 (76 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7949306b-901a-4602-8b3f-ce5078d80526 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: Upgraded to focal on 2020-05-09 (5 days ago) dmi.bios.date: 07/22/2015 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P13ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-AD5BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP13ABH:bd07/22/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-AD5BR:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C/532U3C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878918/+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 1888461] Re: After upgrade, Linux will not boot
Log mentions it - ** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888461/+attachment/5395066/+files/journal.log -- 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/1888461 Title: After upgrade, Linux will not boot Status in linux package in Ubuntu: Incomplete Bug description: I have been running 18.04 upgraded on my laptop and today after a restart-to-upgrade... starting up with Ubuntu 4.15.0-112, the latest update, it blinks, shows Superblock last write time is in the future... messages in the top left of the screen, then blanks black screen and shows the error again. This is super confusing as I checked the time in BIOS, "date" on terminal and they were correct. Adjtime hasn't been changed since 2018 and contains: $ cat /etc/adjtime 0.0 0 0.0 0 LOCAL When I go to advanced options I chose the last kernel and now it boots ok. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-112-generic 4.15.0-112.113 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 5569 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jul 21 23:38:35 2020 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=136d3aa0-26df-4f6e-8eb2-9ade44134645 InstallationDate: Installed on 2013-11-23 (2432 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS L521X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic root=UUID=8e997c12-0ee0-422b-a7e4-a7cb0a74f38f ro quiet splash noresume vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-111-generic N/A linux-backports-modules-4.15.0-111-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2020-07-20 (2 days ago) dmi.bios.date: 02/12/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0C5Y96 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A17 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd02/12/2018:svnDellInc.:pnXPSL521X:pvrA17:rvnDellInc.:rn0C5Y96:rvrA00:cvnDellInc.:ct8:cvrA17: dmi.product.family: 103C_5335KV dmi.product.name: XPS L521X dmi.product.version: A17 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888461/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Touchpad MSFT0001:00 04F3:3140 is dead on 5.8 rc5 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. 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/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 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/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on
[Kernel-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
@Seb, for the pulseaudio bionic, I remember you already pushed a build for this SRU to the queue, so @foundation team, could you please build it since our oem project is waiting for this fix. thx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+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 1729145] Re: /dev/bcache/by-uuid links not created after reboot
Anyone interested in this bug, please take a look at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941 Good summary of the issue: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941/comments/27 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941/comments/47 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941/comments/56 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941/comments/62 And the fix made at bcache-tools for that bug (kernel patch made to fix this bug will asked to be removed soon, as that fix solves this issue). -- 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/1729145 Title: /dev/bcache/by-uuid links not created after reboot Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Bug description: 1. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 2. $ apt-cache policy linux-image-`uname -r` linux-image-4.13.0-16-generic: Installed: 4.13.0-16.19 Candidate: 4.13.0-16.19 Version table: *** 4.13.0-16.19 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3. After creating some bcache devices and rebooting /dev/bcache/by-uuid/ -> ../../bcacheN symlinks point to the current bcache device which is caching the dev.uuid found after creating a backing device. 4. /dev/bcache/by-uuid does not exist and there are not symlinks underneath It appears that since the initramfs loads the bcache module which probes and finds all of the cache devices and backing devices then once the rootfs is mounted and udev gets to run, the bcache kernel module does not emit the CACHED_UUID value into the environment if the underlying devices are already registered. In dmesg, one can see that prior to mounting the rootfs, we see bcache register events: [5.333973] bcache: register_bdev() registered backing device vdb2 [5.354138] bcache: register_bdev() registered backing device vdb4 [5.365665] bcache: register_bdev() registered backing device vdb3 [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 entries, seq 1 [5.428683] bcache: register_cache() registered cache device vdb1 then rootfs ismounted and systemd starts systemd-udev [9.350889] systemd[1]: Listening on udev Kernel Socket. And then the coldplug replay of kernel events triggers /lib/udev/rules.d/69-bcache.rules which invokes /lib/udev/bcache-register which writes the device name (/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the bcache kernel driver attempting to register the block device. However, there is already a bcache device associated already and registration fails [ 11.173141] bcache: register_bcache() error opening /dev/vdb2: device already registered [ 11.184617] bcache: register_bcache() error opening /dev/vdb3: device already registered [ 11.199130] bcache: register_bcache() error opening /dev/vdb1: device already registered [ 11.271694] bcache: register_bcache() error opening /dev/vdb4: device already registered The problem then is that only a kernel call to bch_cached_dev_run() which happens like this: bcache_register() register_bdev() bch_cached_dev_run() kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env); where env includes: "DRIVER=bcache", kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid), NULL, NULL, }; Since that event is not emitted for any previously registered device, then the symlink will not be created. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 31 22:09 seq crw-rw 1 root audio 116, 33 Oct 31 22:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 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: CRDA: N/A Date: Wed Nov 1 01:39:01 2017 Ec2AMI: ami-030b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus
[Kernel-packages] [Bug 1888571] Re: Screen flickering and glitching after install
> Intel integrated driver causes screen flickering with Ubuntu install. I think you mean the generic 'modeset' driver, which is the correct driver to use and the one shown in your XorgLog attachments. If you were using 'xserver-xorg-video-intel' then please just uninstall that package. It should not be used and commonly causes problems (bug 1867668). Most likely I think this is a kernel bug relating to: [ 117.852074] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 117.944970] sof-audio-pci :00:1f.3: firmware boot complete [ 170.252664] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 170.347691] sof-audio-pci :00:1f.3: firmware boot complete [ 235.442471] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 235.537670] sof-audio-pci :00:1f.3: firmware boot complete ... ** Tags added: ice-lake-flicker ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Screen flickering and glitching after install + [Ice Lake] Screen flickering and glitching after 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/1888571 Title: [Ice Lake] Screen flickering and glitching after install Status in linux package in Ubuntu: Confirmed Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/1888571/+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 1888571] 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/1888571 Title: [Ice Lake] Screen flickering and glitching after install Status in linux package in Ubuntu: Confirmed Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/1888571/+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 1888571] [NEW] Screen flickering and glitching after install
You have been subscribed to a public bug: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ice-lake-flicker ubuntu -- Screen flickering and glitching after install https://bugs.launchpad.net/bugs/1888571 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 1888442] Re: upgrade did not go well
These cryptsetup warnings and errors are indeed due to my zfs use, I see them several times a month for the life of the machine, roughly the last ten months. Don't let the 'error' there scare you, as it did me. I don't understand them, but they also don't appear to have any consequences. The problem is visible well before the cryptsetup is run: Fetched 110 MB in 15s (7,164 kB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 214052 files and directories currently installed.) Preparing to unpack .../base-files_11ubuntu5.1_amd64.deb ... Warning: Stopping motd-news.service, but it can still be activated by: motd-news.timer Unpacking base-files (11ubuntu5.1) over (11ubuntu5) ... Failed to reload daemon: Connection timed out Failed to reload daemon: Connection timed out Setting up base-files (11ubuntu5.1) ... It's entirely possible systemctl daemon-reload commands were failing because I undocked my laptop. (The dmesg buffer did have some ugly stuff in it.) But I've heard more than one person complain about apt upgrades including systemd packages leading to system instability, and that feels more like what I saw. Thanks ** Package changed: zfs-linux (Ubuntu) => systemd (Ubuntu) -- 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/1888442 Title: upgrade did not go well Status in systemd package in Ubuntu: New Bug description: Hello, I had some problems during my most recent apt upgrade. A confounding factor to these problems was removing my laptop from its docking station a few minutes earlier. $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic linux-image-5.4.0-42-generic linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic python3-click python3-colorama The following packages will be upgraded: base-files libnss-mymachines libnss-systemd libpam-systemd libpulse-mainloop-glib0 libpulse0 libpulsedsp libseccomp2 libsystemd0 libudev1 libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 linux-firmware linux-generic linux-headers-generic linux-image-generic pulseaudio pulseaudio-utils python3-distupgrade sudo systemd systemd-container systemd-journal-remote systemd-sysv systemd-timesyncd ubuntu-drivers-common ubuntu-release-upgrader-core udev 34 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 110 MB/184 MB of archives. After this operation, 360 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://wopr.domain/ubuntu focal-proposed/main amd64 base-files amd64 11ubuntu5.1 [60.1 kB] Get:2 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-systemd amd64 245.4-4ubuntu3.2 [95.6 kB] Get:3 http://wopr.domain/ubuntu focal-proposed/universe amd64 systemd-journal-remote amd64 245.4-4ubuntu3.2 [61.9 kB] Get:4 http://wopr.domain/ubuntu focal-proposed/main amd64 udev amd64 245.4-4ubuntu3.2 [1,363 kB] Get:5 http://wopr.domain/ubuntu focal-proposed/main amd64 libudev1 amd64 245.4-4ubuntu3.2 [78.9 kB] Get:6 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system amd64 6.0.0-0ubuntu8.2 [67.5 kB] Get:7 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-clients amd64 6.0.0-0ubuntu8.2 [343 kB] Get:8 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.2 [605 kB] Get:9 http://wopr.domain/ubuntu focal-proposed/universe amd64 libvirt-daemon-driver-storage-zfs amd64 6.0.0-0ubuntu8.2 [21.4 kB] Get:10 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-storage-rbd amd64 6.0.0-0ubuntu8.2 [28.3 kB] Get:11 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt0 amd64 6.0.0-0ubuntu8.2 [1,444 kB] Get:12 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon amd64 6.0.0-0ubuntu8.2 [404 kB] Get:13 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-mymachines amd64 245.4-4ubuntu3.2 [131 kB] Get:14 http://wopr.domain/ubuntu focal-proposed/main amd64 libseccomp2 amd64 2.4.3-1ubuntu3.20.04.3 [42.4 kB] Get:15 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-container amd64 245.4-4ubuntu3.2 [317 kB] Get:16 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.2 [12.3 kB] Get:17 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-sysv amd64 245.4-4ubuntu3.2 [10.3 kB] Get:18 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.2 [28.0 kB] Get:19
[Kernel-packages] [Bug 1888584] 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 1888584 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/1888584 Title: 5.4.0-42 Monitor not recognized after kernel upgrade Status in linux package in Ubuntu: Incomplete Bug description: 5.3.0-62 recognized my monitor. Upgraded and Samsung S32F351FUK monitor not recognized in 5.4.0-42 LinuxMint 19.3 OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888584/+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 1888584] [NEW] 5.4.0-42 Monitor not recognized after kernel upgrade
Public bug reported: 5.3.0-62 recognized my monitor. Upgraded and Samsung S32F351FUK monitor not recognized in 5.4.0-42 LinuxMint 19.3 OS ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1888584 Title: 5.4.0-42 Monitor not recognized after kernel upgrade Status in linux package in Ubuntu: New Bug description: 5.3.0-62 recognized my monitor. Upgraded and Samsung S32F351FUK monitor not recognized in 5.4.0-42 LinuxMint 19.3 OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888584/+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 1884232] Re: touchpad doesn't work at all on ACER Spin 5
I'm also affected by this. Ping me if I can help move this along in any way, I'm happy to test. -- 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/1884232 Title: touchpad doesn't work at all on ACER Spin 5 Status in linux package in Ubuntu: Confirmed Bug description: Touchpad is not working at all on ACER Spin 5 SP513-54N. According to https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 I am creating this kernel bug issue. There are more issues, too, like touchscreen not working and Ubuntu not installable - see here if interrested https://askubuntu.com/questions/1251719/ I would like to run Ubuntu on this machine and I am willing to help with any debug or kernel tweaking... Please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4195 F pulseaudio CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 10:44:58 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.00 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+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'
Any luck with saving the world? But more importantly is there any progress in finding a fix for this problem, I feel that it's kind of ridiculous that the issue is not fixed for 8 months now. Would love to get and update -- 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 1822937] Re: NVIDIA settings won't write to /etc/xorg
I'm seeing what i think is a related problem using Ubuntu 20.04 and nvidia driver 440. IE default ubuntu 20.04 install from the ISO (and then updated). My settings do not persist across reboots. (which is really annoying since I have a secondary display rotated. Tried running as sudo - it seems to persist, but doesn't take) ``` $sudo nvidia-settings [sudo] password for haydon: (nvidia-settings:51977): GLib-GObject-CRITICAL **: 15:53:13.651: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** Message: 15:53:13.925: PRIME: No offloading required. Abort ** Message: 15:53:13.925: PRIME: is it supported? no Package xorg-server was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-server.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-server' found ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-settings source package in Disco: Won't Fix Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+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 1888556] Re: Kernel linux-image-4.4.0-186-generic and nvidia drivers
Ok, I found the cause: I had the meta package linux-image-generic installed, but not the metapackage linux-generic. For that reason, when kernel was upgraded the package with the kernel headers wasn't upgraded, and that caused the issue (that of course disappeared reverting to the previous kernel version) After installing the metapackage linux-generic I managed to update to the new kernel and the nvidia drivers worked as supposed. So, this bug report can be closed, sorry for wasting your time ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Invalid Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1886860] Re: cgroup refcount is bogus when cgroup_sk_alloc is disabled
Reproducer is here. https://launchpad.net/~cascardo/+archive/ubuntu/ppa/+sourcepub/11445138 /+listing-archive-extra -- 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/1886860 Title: cgroup refcount is bogus when cgroup_sk_alloc is disabled Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete Bug description: When net_prio and net_cls cgroups are used, cgroup refcount is bogus, as it's not incremented anymore, but decremented when sockets are closed. This might lead to crashes possibly because of use-after-free when packets are received as shown in LP #1886668. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886860/+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 1888567] 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/1888567 Title: Touchpad do not recognized Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have recently installed Kubuntu 20.04 (dual boot with Windows 10) and the touchpad is not recognized. I typed: cat /proc/bus/input/devices but it doesn't show nothing related to the touchpad. Besides, in "System preferences" a message is shown "Touchpad not found". I checked in the Driver Manager for updates but I can't found any drivers. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1038 F pulseaudio /dev/snd/controlC0: daniel 1038 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Jul 22 13:41:43 2020 InstallationDate: Installed on 2020-07-20 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire ES1-521 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=447c90a4-cd39-4e03-b354-6a3366c13f50 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BELLEMERE_BE dmi.board.vendor: Acer dmi.board.version: V1.06 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-521:pvrV1.06:rvnAcer:rnBELLEMERE_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion: dmi.product.family: BE dmi.product.name: Aspire ES1-521 dmi.product.sku: Aspire ES1-521_104B_V1.06 dmi.product.version: V1.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888567/+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 1888567] [NEW] Touchpad do not recognized
Public bug reported: Hello, I have recently installed Kubuntu 20.04 (dual boot with Windows 10) and the touchpad is not recognized. I typed: cat /proc/bus/input/devices but it doesn't show nothing related to the touchpad. Besides, in "System preferences" a message is shown "Touchpad not found". I checked in the Driver Manager for updates but I can't found any drivers. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1038 F pulseaudio /dev/snd/controlC0: daniel 1038 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Jul 22 13:41:43 2020 InstallationDate: Installed on 2020-07-20 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire ES1-521 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=447c90a4-cd39-4e03-b354-6a3366c13f50 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BELLEMERE_BE dmi.board.vendor: Acer dmi.board.version: V1.06 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-521:pvrV1.06:rvnAcer:rnBELLEMERE_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion: dmi.product.family: BE dmi.product.name: Aspire ES1-521 dmi.product.sku: Aspire ES1-521_104B_V1.06 dmi.product.version: V1.06 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1888567 Title: Touchpad do not recognized Status in linux package in Ubuntu: New Bug description: Hello, I have recently installed Kubuntu 20.04 (dual boot with Windows 10) and the touchpad is not recognized. I typed: cat /proc/bus/input/devices but it doesn't show nothing related to the touchpad. Besides, in "System preferences" a message is shown "Touchpad not found". I checked in the Driver Manager for updates but I can't found any drivers. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1038 F pulseaudio /dev/snd/controlC0: daniel 1038 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Jul 22 13:41:43 2020 InstallationDate: Installed on 2020-07-20 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire ES1-521 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=447c90a4-cd39-4e03-b354-6a3366c13f50 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BELLEMERE_BE dmi.board.vendor: Acer dmi.board.version: V1.06 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-521:pvrV1.06:rvnAcer:rnBELLEMERE_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion: dmi.product.family: BE dmi.product.name: Aspire ES1-521 dmi.product.sku: Aspire ES1-521_104B_V1.06 dmi.product.version: V1.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888567/+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 1888202] Re: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Won't Fix -- 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/1888202 Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Won't Fix Bug description: the upgrade process assumes ZFS-utils is not configured and has exit code 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 20 10:22:00 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-05-15 (1526 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888202/+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 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54
Hi, has any progress been made in reversing/fixing the change that caused this bug? 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/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 Status in linux package in Ubuntu: Confirmed Bug description: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic. This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX and so on. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+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 1888556] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394989/+files/PulseList.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394990/+files/UdevDb.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394980/+files/CurrentDmesg.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394986/+files/ProcEnviron.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394988/+files/ProcModules.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394987/+files/ProcInterrupts.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394979/+files/CRDA.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394981/+files/IwConfig.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394985/+files/ProcCpuinfoMinimal.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394982/+files/Lspci.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394983/+files/Lsusb.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394991/+files/WifiSyslog.txt ** 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394984/+files/ProcCpuinfo.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name 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/1888556/+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 1888556] Re: Kernel linux-image-4.4.0-186-generic and nvidia drivers
apport information ** Tags added: apport-collected ** Description changed: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. - After reverting back to linux-image-4.4.0-185-generic all got back to - normality. + After reverting back to linux-image-4.4.0-185-generic all got back to normality. + --- + ApportVersion: 2.20.1-0ubuntu2.23 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: angelo 2223 F pulseaudio + /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio + /dev/snd/controlC0: angelo 2223 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 + InstallationDate: Installed on 2010-11-24 (3528 days ago) + InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) + MachineType: System manufacturer System Product Name + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash + ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-185-generic N/A + linux-backports-modules-4.4.0-185-generic N/A + linux-firmware 1.157.23 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: xenial + Uname: Linux 4.4.0-185-generic i686 + UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare + _MarkForUpload: True + dmi.bios.date: 07/20/2009 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0408 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: P5QL/EPU + 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.:bvr0408:bd07/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1888556/+attachment/5394978/+files/AlsaInfo.txt -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Confirmed Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: angelo 2223 F pulseaudio /dev/snd/pcmC0D0p: angelo 2223 F...m pulseaudio /dev/snd/controlC0: angelo 2223 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6f07501c-b65b-4e0b-afaf-52715c09d9d5 InstallationDate: Installed on 2010-11-24 (3528 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-185-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-185.215-generic 4.4.224 RelatedPackageVersions: linux-restricted-modules-4.4.0-185-generic N/A linux-backports-modules-4.4.0-185-generic N/A linux-firmware 1.157.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-185-generic i686 UpgradeStatus: Upgraded to xenial on 2020-07-15 (7 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU 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:
[Kernel-packages] [Bug 1888523] Re: PCIe Bus Error device 8086:a298 spam
When a PCIe AER error is captured, an error message will be output to console. If it's a correctable error, it is output as a warning. Otherwise, it is printed as an error. So users could choose different log level to filter out correctable error messages. === More information @ https://www.kernel.org/doc/Documentation/PCI/pcieaer- howto.rst -- 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/1888523 Title: PCIe Bus Error device 8086:a298 spam Status in linux package in Ubuntu: Incomplete Bug description: Kubuntu 20.04 i7-8700k Gigabyte Aorus Gaming 7 16GB Corsair Dominator RAM I noticed this non-stop spam occurring every second or 2 in my syslog. What is it and is it bad? Here is a bit of the spam: Jul 22 11:04:21 PC034 kernel: [78364.160774] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:21 PC034 kernel: [78364.160785] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:21 PC034 kernel: [78364.160791] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:21 PC034 kernel: [78364.160795] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:25 PC034 kernel: [78367.840037] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:25 PC034 kernel: [78367.840042] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:25 PC034 kernel: [78367.840044] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:25 PC034 kernel: [78367.840046] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.222986] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.222997] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.223003] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.223007] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.280463] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.280473] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.280481] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.280486] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.515980] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.515991] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.515999] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.516004] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.842283] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.842293] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.842301] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.842306] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:37 PC034 kernel: [78380.104714] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:37 PC034 kernel: [78380.104725] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:37 PC034 kernel: [78380.104733] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:37 PC034 kernel: [78380.104739] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:39 PC034 kernel: [78382.170309] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:39 PC034 kernel: [78382.170320] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:39 PC034 kernel: [78382.170328] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:39 PC034 kernel: [78382.170333] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:44 PC034 kernel: [78387.413811] pcieport :00:1d.0: AER: Corrected error
[Kernel-packages] [Bug 1888523] Re: PCIe Bus Error device 8086:a298 spam
PCI(e) is capable of correcting errors whenever possible. From your logs all of the errors are corrected and therefore nothing to worry about. If you see incorrectable errors you may observed device failures, or system failures in some cases. -- 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/1888523 Title: PCIe Bus Error device 8086:a298 spam Status in linux package in Ubuntu: Incomplete Bug description: Kubuntu 20.04 i7-8700k Gigabyte Aorus Gaming 7 16GB Corsair Dominator RAM I noticed this non-stop spam occurring every second or 2 in my syslog. What is it and is it bad? Here is a bit of the spam: Jul 22 11:04:21 PC034 kernel: [78364.160774] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:21 PC034 kernel: [78364.160785] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:21 PC034 kernel: [78364.160791] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:21 PC034 kernel: [78364.160795] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:25 PC034 kernel: [78367.840037] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:25 PC034 kernel: [78367.840042] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:25 PC034 kernel: [78367.840044] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:25 PC034 kernel: [78367.840046] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.222986] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.222997] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.223003] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.223007] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.280463] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.280473] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.280481] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.280486] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.515980] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.515991] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.515999] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.516004] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.842283] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.842293] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.842301] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.842306] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:37 PC034 kernel: [78380.104714] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:37 PC034 kernel: [78380.104725] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:37 PC034 kernel: [78380.104733] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:37 PC034 kernel: [78380.104739] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:39 PC034 kernel: [78382.170309] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:39 PC034 kernel: [78382.170320] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:39 PC034 kernel: [78382.170328] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:39 PC034 kernel: [78382.170333] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:44 PC034 kernel: [78387.413811] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:44 PC034 kernel: [78387.413827] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical
[Kernel-packages] [Bug 1888560] [NEW] Focal update: v5.4.53 upstream stable release
Public bug reported:
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:
v5.4.53 upstream stable release
from git://git.kernel.org/
crypto: atmel - Fix selection of CRYPTO_AUTHENC
crypto: atmel - Fix build error of CRYPTO_AUTHENC
net: atlantic: fix ip dst and ipv6 address filters
net: rmnet: fix lower interface leak
bridge: mcast: Fix MLD2 Report IPv6 payload length check
genetlink: remove genl_bind
ipv4: fill fl4_icmp_{type,code} in ping_v4_sendmsg
ipv6: fib6_select_path can not use out path for nexthop objects
ipv6: Fix use of anycast address with loopback
l2tp: remove skb_dst_set() from l2tp_xmit_skb()
llc: make sure applications use ARPHRD_ETHER
net: Added pointer check for dst->ops->neigh_lookup in dst_neigh_lookup_skb
net_sched: fix a memory leak in atm_tc_init()
sched: consistently handle layer3 header accesses in the presence of VLANs
tcp: fix SO_RCVLOWAT possible hangs under high mem pressure
tcp: make sure listeners don't initialize congestion-control state
tcp: md5: add missing memory barriers in tcp_md5_do_add()/tcp_md5_hash_key()
tcp: md5: do not send silly options in SYNCOOKIES
vlan: consolidate VLAN parsing code and limit max parsing depth
tcp: md5: refine tcp_md5_do_add()/tcp_md5_hash_key() barriers
tcp: md5: allow changing MD5 keys in all socket states
cgroup: fix cgroup_sk_alloc() for sk_clone_lock()
cgroup: Fix sock_cgroup_data on big-endian.
ip: Fix SO_MARK in RST, ACK and ICMP packets
arm64: Introduce a way to disable the 32bit vdso
arm64: arch_timer: Allow an workaround descriptor to disable compat vdso
arm64: arch_timer: Disable the compat vdso for cores affected by
ARM64_WORKAROUND_1418040
drm/msm: fix potential memleak in error branch
drm/msm/dpu: allow initialization of encoder locks during encoder init
drm/exynos: Properly propagate return value in drm_iommu_attach_device()
drm/exynos: fix ref count leak in mic_pre_enable
x86/fpu: Reset MXCSR to default in kernel_fpu_begin()
thermal/drivers: imx: Fix missing of_node_put() at probe time
blk-mq-debugfs: update blk_queue_flag_name[] accordingly for new flags
m68k: nommu: register start of the memory with memblock
m68k: mm: fix node memblock init
dt-bindings: mailbox: zynqmp_ipi: fix unit address
cifs: prevent truncation from long to int in wait_for_free_credits
arm64/alternatives: use subsections for replacement sequences
tpm_tis: extra chip->ops check on error path in tpm_tis_core_init
gfs2: read-only mounts should grab the sd_freeze_gl glock
i2c: eg20t: Load module automatically if ID matches
arm64/alternatives: don't patch up internal branches
iio:magnetometer:ak8974: Fix alignment and data leak issues
iio:humidity:hdc100x Fix alignment and data leak issues
iio: magnetometer: ak8974: Fix runtime PM imbalance on error
iio: core: add missing IIO_MOD_H2/ETHANOL string identifiers
iio: mma8452: Add missed iio_device_unregister() call in mma8452_probe()
iio: pressure: zpa2326: handle pm_runtime_get_sync failure
iio:humidity:hts221 Fix alignment and data leak issues
iio:pressure:ms5611 Fix buffer element alignment
iio:health:afe4403 Fix timestamp alignment and prevent data leak.
spi: spi-fsl-dspi: Fix lockup if device is shutdown during SPI transfer
net: dsa: bcm_sf2: Fix node reference count
of: of_mdio: Correct loop scanning logic
net: macb: call pm_runtime_put_sync on failure path
net: ethernet: mvneta: Do not error out in non serdes modes
net: ethernet: mvneta: Add back interface mode validation
Revert "usb/ohci-platform: Fix a warning when hibernating"
Revert "usb/ehci-platform: Set PM runtime as active on resume"
Revert "usb/xhci-plat: Set PM runtime as active on resume"
net: sfp: add support for module quirks
net: sfp: add some quirks for GPON modules
ARM: OMAP4+: remove pdata quirks for omap4+ iommus
ARM: OMAP2+: Add workaround for DRA7 DSP MStandby errata i879
ARM: OMAP2+: use separate IOMMU pdata to fix DRA7 IPU1 boot
mmc: mmci: Support any block sizes for ux500v2 and qcom variant
HID: quirks: Remove ITE 8595 entry from hid_have_special_driver
ARM: at91: pm: add quirk for sam9x60's ulp1
drm/sun4i: tcon: Separate quirks for tcon0 and tcon1 on A20
scsi: sr: remove references to BLK_DEV_SR_VENDOR, leave it enabled
UBUNTU: [Config] updateconfigs for BLK_DEV_SR_VENDOR
bus: ti-sysc: Rename clk related quirks to pre_reset and post_reset quirks
bus: ti-sysc: Consider non-existing registers too when matching quirks
bus: ti-sysc: Handle module unlock quirk needed for some RTC
bus: ti-sysc: Detect display subsystem related devices
arm64: dts: g12-common: add parkmode_disable_ss_quirk on DWC3 controller
bus: ti-sysc: Detect EDMA and
[Kernel-packages] [Bug 1888202] Re: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
I cannot reproduce this bug anymore. i propose to close it -- 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/1888202 Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Incomplete Bug description: the upgrade process assumes ZFS-utils is not configured and has exit code 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 20 10:22:00 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-05-15 (1526 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888202/+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 1887206] Re: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
Maybe i have selected the wrong kernel entry when booting : it was a fresh 20.04 install over an existing 18.04 one (update was not working). ** Attachment added: "apt_list_output.txt" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1887206/+attachment/5394966/+files/apt_list_output.txt -- 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/1887206 Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Incomplete Bug description: _ ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log uas usb_storage hid_generic radeon mxm_wmi i2c_algo_bit ttm drm_kms_helper firewire_ohci syscopyarea sysfillrect firewire_core usbhid i2c_i801 sysimgblt fb_sys_fops pata_acpi crc_itu_t hid r8169 drm mii pata_jmicron ahci libahci wmi ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jul 11 02:47:30 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1887206/+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 1888556] 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 1888556 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 ** Tags added: xenial -- 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: Incomplete Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888556/+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 1879707] Re: [UBUNTU 20.04] mke2fs dasd(fba), Failing CCW, default ERP has run out of retries and failed
I just wanted to try the kernel that I've build yesterday (see comment #6) and as a first step I wanted to recreate re-create the described error situation on an up to date 20.04 system: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal $ uname -a Linux zlin42 5.4.0-40-generic #44-Ubuntu SMP Mon Jun 22 23:57:33 UTC 2020 s390x s390x s390x GNU/Linux $ apt-cache policy linux-generic linux-generic: Installed: 5.4.0.40.43 Candidate: 5.4.0.40.43 Version table: *** 5.4.0.40.43 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main s390x Packages 500 http://ports.ubuntu.com/ubuntu-ports focal-security/main s390x Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages $ But by surprise I didn't ran into any problems! I was able to flawlessly make use of FBA devices in the following three different way: 1) (re-)used a FBA device that was previously in use, without wiping out any data 2) used a FBA device that I wiped out using wipefs 3) used a FBA device that I entirely wiped out (and zeroed) using dd (see the attached doc for more details) Looks like a fix for this problem came in with the kernels that were rolled out in between 5.4.0-29-generic and 5.4.0-40-generic. (Again I didn't installed the patched kernel, I just used the latest official one.) Message to the initial bug reporter: Please can you retry on an up-to-date 20.04 system (or after having updated your existing one, like for example with "sudo apt -y -q update && sudo apt -y -q full-upgrade" plus reboot in case the kernel got update, what I assume will happen)? ** Attachment added: "cmdline.txt" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879707/+attachment/5394964/+files/cmdline.txt ** Changed in: ubuntu-z-systems Status: In Progress => 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/1879707 Title: [UBUNTU 20.04] mke2fs dasd(fba),Failing CCW,default ERP has run out of retries and failed Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: mke2fs,dasd(fba) guest edevices FBA,default ERP has run out of retries and failed,Failing CCW ---uname output--- xx - 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:27:18 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- mke2fs to dasd(fba) devices Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. dasd(fba),Failing CCW,default ERP has run out of retries and failed between the following syslog events, mke2fs running, before mounting and starting IO to dasd(fba) devices May 14 14:33:32 ilabg13 root: ILAB_IO_FROM_MSDI_START May 14 14:48:34 ilabg13 root: ILAB_IO_FROM_MSDI_RUNNING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879707/+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 1888556] [NEW] Kernel linux-image-4.4.0-186-generic and nvidia drivers
Public bug reported: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1888556 Title: Kernel linux-image-4.4.0-186-generic and nvidia drivers Status in linux package in Ubuntu: New Bug description: After updating my kernel to linux-image-4.4.0-186-generic yesterday in Ubuntu 16.04, the screen resolution dropped, because it stopped using the nvidia drivers. After reverting back to linux-image-4.4.0-185-generic all got back to normality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888556/+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 1888523] Re: PCIe Bus Error device 8086:a298 spam
Unfortunately I can't share the apport-collect log because I am uncomfortable with the amount of data it collects about my system. My threat model doesn't allow for such disclosure of data. I could share relevant parts of the log if I review it 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/1888523 Title: PCIe Bus Error device 8086:a298 spam Status in linux package in Ubuntu: Incomplete Bug description: Kubuntu 20.04 i7-8700k Gigabyte Aorus Gaming 7 16GB Corsair Dominator RAM I noticed this non-stop spam occurring every second or 2 in my syslog. What is it and is it bad? Here is a bit of the spam: Jul 22 11:04:21 PC034 kernel: [78364.160774] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:21 PC034 kernel: [78364.160785] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:21 PC034 kernel: [78364.160791] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:21 PC034 kernel: [78364.160795] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:25 PC034 kernel: [78367.840037] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:25 PC034 kernel: [78367.840042] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:25 PC034 kernel: [78367.840044] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:25 PC034 kernel: [78367.840046] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.222986] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.222997] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.223003] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.223007] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.280463] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.280473] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.280481] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.280486] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.515980] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.515991] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.515999] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.516004] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.842283] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.842293] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.842301] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.842306] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:37 PC034 kernel: [78380.104714] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:37 PC034 kernel: [78380.104725] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:37 PC034 kernel: [78380.104733] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:37 PC034 kernel: [78380.104739] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:39 PC034 kernel: [78382.170309] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:39 PC034 kernel: [78382.170320] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:39 PC034 kernel: [78382.170328] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:39 PC034 kernel: [78382.170333] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:44 PC034 kernel: [78387.413811] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:44 PC034 kernel: [78387.413827] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected,
[Kernel-packages] [Bug 1849981] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10
Hi, can you attach to the bug report the output from the following command: sudo apt list --installed ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1849981 Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 Status in zfs-linux package in Ubuntu: Confirmed Bug description: Was upgrading to 19.10 and encountered this ProblemType: Package DistroRelease: Ubuntu 19.10 Package: zfs-dkms 0.8.1-1ubuntu14 ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 10:28:20 2019 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2013-06-08 (2331 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: zfs-linux Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849981/+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 1813749] Re: zfs-linux 0.6.5.6-0ubuntu26 ADT test failure with linux-snapdragon 4.4.0-1107.112
** Changed in: zfs-linux (Ubuntu) Status: New => Fix Released -- 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/1813749 Title: zfs-linux 0.6.5.6-0ubuntu26 ADT test failure with linux-snapdragon 4.4.0-1107.112 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Bug description: [Impact] ADT Testing failed with xenial/linux-snapdragon on: arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/z/zfs-linux/20190125_170958_97a22@/log.gz The debian test script (debian/tests/kernel-smoke-test) doesn't load the zfs module causing the tests to fail. [Test Case] Run autopkgtest of zfs-linux package with xenial/linux-snapdragon kernel. Alternatively one can install the zfs-dkms package, download the zfs-linux source from version 0.6.5.6-0ubuntu26 and run: $ sudo ./debian/tests/kernel-smoke-test Making sure the modules are not loaded before running the test manually. [Fix] The solution is to load the zfs module before starting the tests, as done by the test script shipped by the packages for Bionic and later series. [Regression Potential] Low. The fix changes only the debian test script, so no impact on regular users. [Other Info] The tests were not failing before. I suspect that's being caused by a change in the order that the packages are installed before the tests start. With previous ADT runs, the zfsutils-linux package was installed after zfs-dkms, so that caused systemd to start the zfs-import-scan service, which loaded the modules. On these later ADT failed runs, zfs-dkms is installed last, so the service is not reloaded and the modules stay unloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1813749/+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 1887206] Re: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
Hi, can you attach to the bug report the output from the following command: sudo apt list --installed ** Changed in: zfs-linux (Ubuntu) Status: New => Incomplete ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1887206 Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Incomplete Bug description: _ ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log uas usb_storage hid_generic radeon mxm_wmi i2c_algo_bit ttm drm_kms_helper firewire_ohci syscopyarea sysfillrect firewire_core usbhid i2c_i801 sysimgblt fb_sys_fops pata_acpi crc_itu_t hid r8169 drm mii pata_jmicron ahci libahci wmi ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jul 11 02:47:30 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1887206/+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 1888551] Re: perf vendor events s390: Add new deflate counters for IBM z15
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => In Progress -- 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/1888551 Title: perf vendor events s390: Add new deflate counters for IBM z15 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 Bug description: SRU Justification: == [Impact] * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters reported with lscpumf are not usable with 'perf stat -e'. * 'lscpumf -c' provides a list of available counters, but the following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR * 'perf list' is also not offering these counters. * On the kernel side this is fixed with the following upstream accepted commit: [Fix] * e7950166e40271c025e0eec348cdf5c63ac734fa "perf vendor events s390: Add new deflate counters for IBM z15" [Test Case] * Requires the fix/patch of the kernel (d68d5d51dc898895b4e15bea52e5668ca9e76180 "s390/cpum_cf: Add new extended counters for IBM z15") * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in LPAR is needed where the counters are enabled in the activation profile. * Use 'perf list' to determine if the counters DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed * Use 'perf stat -e' to enable amd make use of these counters. [Regression Potential] * The regression can be considered as low, since: * it's architecture specific (s390x) * limited to IBM z15 hardware * and only additional (s390x) hardware counters are defined and added. [Other] * Since these patches are upstream in kernel 5.7 they will automatically land in groovy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888551/+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 1888551] [NEW] perf vendor events s390: Add new deflate counters for IBM z15
Public bug reported: SRU Justification: == [Impact] * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters reported with lscpumf are not usable with 'perf stat -e'. * 'lscpumf -c' provides a list of available counters, but the following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR * 'perf list' is also not offering these counters. * On the kernel side this is fixed with the following upstream accepted commit: [Fix] * e7950166e40271c025e0eec348cdf5c63ac734fa "perf vendor events s390: Add new deflate counters for IBM z15" [Test Case] * Requires the fix/patch of the kernel (d68d5d51dc898895b4e15bea52e5668ca9e76180 "s390/cpum_cf: Add new extended counters for IBM z15") * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in LPAR is needed where the counters are enabled in the activation profile. * Use 'perf list' to determine if the counters DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed * Use 'perf stat -e' to enable amd make use of these counters. [Regression Potential] * The regression can be considered as low, since: * it's architecture specific (s390x) * limited to IBM z15 hardware * and only additional (s390x) hardware counters are defined and added. [Other] * Since these patches are upstream in kernel 5.7 they will automatically land in groovy. ** Affects: ubuntu-z-systems Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- 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/1888551 Title: perf vendor events s390: Add new deflate counters for IBM z15 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 Bug description: SRU Justification: == [Impact] * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters reported with lscpumf are not usable with 'perf stat -e'. * 'lscpumf -c' provides a list of available counters, but the following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR * 'perf list' is also not offering these counters. * On the kernel side this is fixed with the following upstream accepted commit: [Fix] * e7950166e40271c025e0eec348cdf5c63ac734fa "perf vendor events s390: Add new deflate counters for IBM z15" [Test Case] * Requires the fix/patch of the kernel (d68d5d51dc898895b4e15bea52e5668ca9e76180 "s390/cpum_cf: Add new extended counters for IBM z15") * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in LPAR is needed where the counters are enabled in the activation profile. * Use 'perf list' to determine if the counters DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed * Use 'perf stat -e' to enable amd make use of these counters. [Regression Potential] * The regression can be considered as low, since: * it's architecture specific (s390x) * limited to IBM z15 hardware * and only additional (s390x) hardware counters are defined and added. [Other] * Since these patches are upstream in kernel 5.7 they will automatically land in groovy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888551/+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 1888523] 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 1888523 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/1888523 Title: PCIe Bus Error device 8086:a298 spam Status in linux package in Ubuntu: Incomplete Bug description: Kubuntu 20.04 i7-8700k Gigabyte Aorus Gaming 7 16GB Corsair Dominator RAM I noticed this non-stop spam occurring every second or 2 in my syslog. What is it and is it bad? Here is a bit of the spam: Jul 22 11:04:21 PC034 kernel: [78364.160774] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:21 PC034 kernel: [78364.160785] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:21 PC034 kernel: [78364.160791] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:21 PC034 kernel: [78364.160795] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:25 PC034 kernel: [78367.840037] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:25 PC034 kernel: [78367.840042] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:25 PC034 kernel: [78367.840044] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:25 PC034 kernel: [78367.840046] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.222986] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.222997] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.223003] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.223007] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.280463] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.280473] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.280481] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.280486] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.515980] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.515991] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.515999] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.516004] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.842283] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.842293] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.842301] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.842306] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:37 PC034 kernel: [78380.104714] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:37 PC034 kernel: [78380.104725] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:37 PC034 kernel: [78380.104733] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:37 PC034 kernel: [78380.104739] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:39 PC034 kernel: [78382.170309] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:39 PC034 kernel: [78382.170320] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:39 PC034 kernel: [78382.170328] pcieport :00:1d.0: AER: device [8086:a298] error
[Kernel-packages] [Bug 1849823] Re: zfs usb hdd: i/o is currently suspended after laptop wakeup from suspend
This bug was filed for a Pop!_OS installation. Won't Fix. ** Changed in: zfs-linux (Ubuntu) Status: In Progress => Won't Fix -- 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/1849823 Title: zfs usb hdd: i/o is currently suspended after laptop wakeup from suspend Status in zfs-linux package in Ubuntu: Won't Fix Bug description: Hey, I have an external usb hdd, which is formatted with zfs. When I suspend my laptop, and wake it up, the state of the pool is normal, if I try to ls the pool, I get the list of files on it one time, then the pool freeze here is the status: pool: your-pool state: ONLINE status: One or more devices are faulted in response to IO failures. action: Make sure the affected devices are connected, then run 'zpool clear'. see: http://zfsonlinux.org/msg/ZFS-8000-HC scan: none requested config: NAMESTATE READ WRITE CKSUM your-pool ONLINE 0 5 0 sda1 ONLINE 012 0 errors: List of errors unavailable: pool I/O is currently suspended errors: 5 data errors, use '-v' for a list If I try: zpool clear your-pool I get: cannot clear errors for your-pool: I/O error and the state change to UNAVIAL like this: pool: your-pool state: UNAVAIL status: One or more devices are faulted in response to IO failures. action: Make sure the affected devices are connected, then run 'zpool clear'. see: http://zfsonlinux.org/msg/ZFS-8000-HC scan: none requested config: NAMESTATE READ WRITE CKSUM your-pool UNAVAIL 0 0 0 insufficient replicas sda1 UNAVAIL 0 0 0 errors: List of errors unavailable: pool I/O is currently suspended errors: 5 data errors, use '-v' for a list Any one experienced this ? Description: Pop!_OS 18.04 LTS Release: 18.04 zfsutils-linux: Installed: 0.7.5-1ubuntu16.6 Candidate: 0.7.5-1ubuntu16.6 Version table: *** 0.7.5-1ubuntu16.6 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.7.5-1ubuntu15 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849823/+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 1874519] Re: ZFS installation on Raspberry Pi is problematic
Thanks Juerg. Can you close this bug once it lands? -- 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/1874519 Title: ZFS installation on Raspberry Pi is problematic Status in zfs-linux package in Ubuntu: Triaged Bug description: Version: Ubuntu Server 20.04 - preinstalled 64-bit image for Raspberry Pi. ZFS on the Pi under 20.04 is currently a bit problematic. Upon issuing the command 'zpool status', I'm helpfully directed to install zfsutils-linux. When I do this, it complains that it cannot find the ZFS module, then errors out. Worse than that, the zfsutils-linux package does not depend on the zfs-dkms package, so it doesn't attempt to build the ZFS kernel modules automatically. The workaround is to install zfs-dkms, which builds the required kernel modules. (Once this has been done, the usual errors when installing the zfsutils-linux package, caused by there being no ZFS pools on the system, can be worked around by creating a zpool, then rerunning 'sudo apt install zfsutils-linux', as with previous versions of Ubuntu and Debian). I have not tested on other hardware platforms - this problem may also exist on other platforms where the user has not selected to install to ZFS. I have selected 'zfsutils' as the affected package, which is not the name of an actual current package, since launchpad won't let me submit the bug without selecting a package, however it's not clear to me that the problem is caused by that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1874519/+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 1888202] Re: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
Can you attach the output from running the command journalctl -xe thanks. ** Changed in: zfs-linux (Ubuntu) Status: New => Incomplete ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1888202 Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Incomplete Bug description: the upgrade process assumes ZFS-utils is not configured and has exit code 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 20 10:22:00 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-05-15 (1526 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888202/+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 1888523] Re: PCIe Bus Error device 8086:a298 spam
** Package changed: ubuntu => linux (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/1888523 Title: PCIe Bus Error device 8086:a298 spam Status in linux package in Ubuntu: New Bug description: Kubuntu 20.04 i7-8700k Gigabyte Aorus Gaming 7 16GB Corsair Dominator RAM I noticed this non-stop spam occurring every second or 2 in my syslog. What is it and is it bad? Here is a bit of the spam: Jul 22 11:04:21 PC034 kernel: [78364.160774] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:21 PC034 kernel: [78364.160785] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:21 PC034 kernel: [78364.160791] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:21 PC034 kernel: [78364.160795] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:25 PC034 kernel: [78367.840037] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:25 PC034 kernel: [78367.840042] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:25 PC034 kernel: [78367.840044] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:25 PC034 kernel: [78367.840046] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.222986] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.222997] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.223003] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.223007] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.280463] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.280473] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.280481] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.280486] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.515980] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.515991] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.515999] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.516004] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.842283] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.842293] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.842301] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.842306] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:37 PC034 kernel: [78380.104714] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:37 PC034 kernel: [78380.104725] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:37 PC034 kernel: [78380.104733] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:37 PC034 kernel: [78380.104739] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:39 PC034 kernel: [78382.170309] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:39 PC034 kernel: [78382.170320] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:39 PC034 kernel: [78382.170328] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:39 PC034 kernel: [78382.170333] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:44 PC034 kernel: [78387.413811] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:44 PC034 kernel: [78387.413827] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:44 PC034 kernel: [78387.413838] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:44 PC034 kernel: [78387.413846] pcieport
[Kernel-packages] [Bug 1865295] Re: dangling documentation symlinks
This was fixed in bug 1768777 ** Changed in: zfs-linux (Ubuntu) Status: New => Fix Released ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Low ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1865295 Title: dangling documentation symlinks Status in zfs-linux package in Ubuntu: Fix Released Bug description: Hello, there's dangling symlinks in the zfsutils-linux binary packages on a bionic system: lrwxrwxrwx 1 root root7 Apr 13 2016 libnvpair1linux -> zfs-doc lrwxrwxrwx 1 root root7 Apr 13 2016 libuutil1linux -> zfs-doc lrwxrwxrwx 1 root root7 Apr 13 2016 libzfs2linux -> zfs-doc lrwxrwxrwx 1 root root7 Apr 13 2016 libzpool2linux -> zfs-doc lrwxrwxrwx 1 root root7 Apr 13 2016 zfsutils-linux -> zfs-doc lrwxrwxrwx 1 root root7 Apr 13 2016 zfs-zed -> zfs-doc zfs-doc: total 68 lrwxrwxrwx 1 root root38 Dec 17 06:15 changelog.Debian.gz -> ../libnvpair1linux/changelog.Debian.gz -rw-r--r-- 1 root root 53854 Oct 6 2017 copyright lrwxrwxrwx 1 root root28 Dec 17 06:15 COPYRIGHT -> ../libnvpair1linux/COPYRIGHT drwxr-xr-x 2 root root 4096 Feb 29 09:37 examples lrwxrwxrwx 1 root root41 Dec 17 06:15 OPENSOLARIS.LICENSE.gz -> ../libnvpair1linux/OPENSOLARIS.LICENSE.gz -rw-r--r-- 1 root root 684 Oct 6 2017 README.Debian apt-get install --reinstall zfs-doc fixed it. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfs-doc (not installed) ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 Date: Sat Feb 29 09:44:37 2020 InstallationDate: Installed on 2012-10-18 (2690 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: Upgraded to bionic on 2018-05-02 (668 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1865295/+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 1888523] [NEW] PCIe Bus Error device 8086:a298 spam
You have been subscribed to a public bug: Kubuntu 20.04 i7-8700k Gigabyte Aorus Gaming 7 16GB Corsair Dominator RAM I noticed this non-stop spam occurring every second or 2 in my syslog. What is it and is it bad? Here is a bit of the spam: Jul 22 11:04:21 PC034 kernel: [78364.160774] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:21 PC034 kernel: [78364.160785] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:21 PC034 kernel: [78364.160791] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:21 PC034 kernel: [78364.160795] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:25 PC034 kernel: [78367.840037] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:25 PC034 kernel: [78367.840042] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:25 PC034 kernel: [78367.840044] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:25 PC034 kernel: [78367.840046] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.222986] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.222997] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.223003] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.223007] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.280463] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.280473] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.280481] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.280486] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.515980] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.515991] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.515999] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.516004] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.842283] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.842293] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.842301] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.842306] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:37 PC034 kernel: [78380.104714] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:37 PC034 kernel: [78380.104725] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:37 PC034 kernel: [78380.104733] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:37 PC034 kernel: [78380.104739] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:39 PC034 kernel: [78382.170309] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:39 PC034 kernel: [78382.170320] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:39 PC034 kernel: [78382.170328] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:39 PC034 kernel: [78382.170333] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:44 PC034 kernel: [78387.413811] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:44 PC034 kernel: [78387.413827] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:44 PC034 kernel: [78387.413838] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:44 PC034 kernel: [78387.413846] pcieport :00:1d.0: AER:[ 0] RxErr ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- PCIe Bus Error device 8086:a298 spam https://bugs.launchpad.net/bugs/1888523 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list:
[Kernel-packages] [Bug 1838141] Re: intel_pstate not working. CPU frequency fixed at 800MHz. No cpu frequency scaling.
XPS 13 (Core i5-10210U) with performance governor idles (0.2% usage) at 4 GHz instead of 900 MHz. -- 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/1838141 Title: intel_pstate not working. CPU frequency fixed at 800MHz. No cpu frequency scaling. Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: intel_pstate not working. CPU frequency fixed at 800MHz. I've tried to modify frequency using "cpufreq-set" and also by directly writing to files in "/sys/devices/system/cpu/cpu0/cpufreq/*" to no success. I tried different versions of kernel, it started working on 4.17.0 but stopped working soon. These are the versions I tested. 5.2.3 - Not Working 5.1.0 - Not Working 4.19.60 - Not Working 4.18.20 - Not Working 4.17.19 - Not Working 4.17.10 - Not Working 4.17.5 - Not Working 4.17.3 - Not Working 4.17.2 - Working 4.17.1 - Working 4.17.0 - Working 4.16.18 - Not Working 4.15.0 - Not Working Please let me know if anything else is needed. thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-55-generic 4.15.0-55.60 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: srijan 2219 F pulseaudio CurrentDesktop: KDE Date: Sat Jul 27 11:34:10 2019 InstallationDate: Installed on 2018-11-25 (243 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5621 Realtek Semiconductor Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator PH315-51 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=a76bd009-8058-4e96-a8b5-a82b7fbe1ede ro acpi_backlight=vendor i915.modeset=1 i915.enable_guc=3 i915.enable_dc=2 i915.enable_fbc=1 nvme_core.default_ps_max_latency_us=1800 pcie_aspm=force i915.enable_psr=2 i915.disable_power_well=1 nmi_watchdog=0 RelatedPackageVersions: linux-restricted-modules-4.15.0-55-generic N/A linux-backports-modules-4.15.0-55-generic N/A linux-firmware 1.173.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.24 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienta_CFS dmi.board.vendor: CFL dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.24 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.24:bd12/05/2018:svnAcer:pnPredatorPH315-51:pvrV1.24:rvnCFL:rnSienta_CFS:rvrV1.24:cvnAcer:ct10:cvrV1.24: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH315-51 dmi.product.version: V1.24 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838141/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
passing intel_pstate=disable_hwp on the kernel commandline causes the kernel to scale the Core i5-8250U down to 1.6 GHz in performance mode, but that's still a bit off from the 900 MHz it scales down to in powersave mode. I believe Windows also does not run the CPUs in performance mode by default on mobile devices (but in balanced or balanced performance), I don't know about stationary ones. Performance governor on laptops should be restricted to gamemode. -- 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
The performance governor is the right choice for servers, but it's not the right choice on non-server platforms, it's also not the default kernel setting, it was set because we have the ondemand.service in userspace that can change it back to ondemand (or well we have the service because of that change in the kernel :D). Fans do not necessarily spin, and you might not actually notice any significant changes in power usage, but the expectation of a desktop user is that the CPU scales its frequencies down, which recent-ish Intel CPUs (Skylake+) on like a ThinkPad T480s - which manage the pstates in hardware instead of software like the old MacBook does - don't do. If we compare this to Red Hat, what they do is CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y in RHEL and CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y in fedora. Power usage, at 3-6% CPU usage: Powersave: I see 0.9-1.4W power usage on the cores Performance, I see 1.6-2.5W -- 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1888461] Re: After upgrade, Linux will not boot
Ok but now it's looping a different error message, maybe just whatever the last message was? And again using the previous kernel works. See attached. ** Attachment added: "Video of startup" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888461/+attachment/5394915/+files/boot.mp4 -- 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/1888461 Title: After upgrade, Linux will not boot Status in linux package in Ubuntu: Incomplete Bug description: I have been running 18.04 upgraded on my laptop and today after a restart-to-upgrade... starting up with Ubuntu 4.15.0-112, the latest update, it blinks, shows Superblock last write time is in the future... messages in the top left of the screen, then blanks black screen and shows the error again. This is super confusing as I checked the time in BIOS, "date" on terminal and they were correct. Adjtime hasn't been changed since 2018 and contains: $ cat /etc/adjtime 0.0 0 0.0 0 LOCAL When I go to advanced options I chose the last kernel and now it boots ok. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-112-generic 4.15.0-112.113 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 5569 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jul 21 23:38:35 2020 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=136d3aa0-26df-4f6e-8eb2-9ade44134645 InstallationDate: Installed on 2013-11-23 (2432 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS L521X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic root=UUID=8e997c12-0ee0-422b-a7e4-a7cb0a74f38f ro quiet splash noresume vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-111-generic N/A linux-backports-modules-4.15.0-111-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2020-07-20 (2 days ago) dmi.bios.date: 02/12/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0C5Y96 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A17 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd02/12/2018:svnDellInc.:pnXPSL521X:pvrA17:rvnDellInc.:rn0C5Y96:rvrA00:cvnDellInc.:ct8:cvrA17: dmi.product.family: 103C_5335KV dmi.product.name: XPS L521X dmi.product.version: A17 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888461/+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 1874874] Re: Focal detects wrong driver version 440 for NVIDIA GTX 550
nvidia-driver-440: Instalados: (ninguno) Candidato: 440.100-0ubuntu0.20.04.1 Tabla de versión: 440.100-0ubuntu0.20.04.1 500 500 http://ar.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 440.82+really.440.64-0ubuntu6 500 500 http://ar.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages -- 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/1874874 Title: Focal detects wrong driver version 440 for NVIDIA GTX 550 Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: My desktop PC has an NVIDIA GeForce GTX 550 Ti. Just installed Focal selecting the option to install 3rd-party drivers during setup process, and after the first boot screen resolution is 800x600. I verified the detected version of NVIDIA driver and I realized it was 440, although correct version is 390. Finally I manually installed proper version (390) and now the graphics are working OK. This is the output for the command "$ lspci -nn": 01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 Ti] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1) This is the output for the command "# ubuntu-drivers devices": == /sys/devices/pci:00/:00:02.0/:01:00.0 == modalias : pci:v10DEd1244sv1043sd83BEbc03sc00i00 vendor : NVIDIA Corporation model: GF116 [GeForce GTX 550 Ti] driver : nvidia-driver-435 - distro non-free driver : nvidia-driver-390 - distro non-free driver : nvidia-driver-440 - distro non-free recommended driver : nvidia-340 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin The version 440 is recommended, but it's not correct for this model (390 should be recommended instead) The issue was not present in previous versions (in both 19.10 and 18.04 driver 390 was recommended correctly) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1874874/+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 1873961] Comment bridged from LTC Bugzilla
--- Comment From z...@us.ibm.com 2020-07-22 10:07 EDT--- Download "iproute2_4.15.0-2ubuntu1.2_ppc64el.deb" from: https://launchpad.net/~smb/+archive/ubuntu/bionic/+packages Installed it on Genesis OS (4.15.0-1039-ibm-gt). New "tc" command sum value: root@ltcgen4:~# sum /sbin/tc 45845 729 I am able to see the correct tcp_flags mask with this new /sbin/tc". The new package works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: In Progress Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: In Progress Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1873074] Re: kernel panic hit by kube-proxy iptables-save/restore caused by aufs
Marking as fix released for X/B/F on kernel packages versions: - Xenial: 4.4.0-186.216 - Bionic: 4.15.0-112.113 - Focal: 5.4.0-42.46 Covered in USNs: https://usn.ubuntu.com/4425-1 https://usn.ubuntu.com/4426-1 https://usn.ubuntu.com/4427-1 ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- 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/1873074 Title: kernel panic hit by kube-proxy iptables-save/restore caused by aufs Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released 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 Released Status in linux source package in Groovy: Won't Fix Bug description: [Impact] * Systems with aufs mounts are vulnerable to a kernel BUG(), which can turn into a panic/crash if panic_on_oops is set. * It is exploitable by unprivileged local users; and also remote access operations (e.g., web server) potentially. * This issue has also manifested in Kubernetes deployments with a kernel panic in iptables-save or iptables-restore after a few weeks of uptime, without user interaction. * Usually all Kubernetes worker nodes hit the issue around the same time. [Fix] * The issue is fixed with 2 patches in aufs4-linux.git: - 515a586eeef3 aufs: do not call i_readcount_inc() - f10aea57d39d aufs: bugfix, IMA i_readcount * The first addresses the issue, and the second addresses a regression in the aufs feature to change RW branches to RO. * The kernel v5.3 aufs patches had an equivalent fix to the second patch, which is present in the Focal aufs patchset (and on ubuntu-unstable/master & /master-5.8 on 20200629) - 1d26f910c53f aufs: for v5.3-rc1, maintain i_readcount (in aufs5-linux.git) [Test Case] * Repeatedly open/close the same file in read-only mode in aufs (UINT_MAX times, to overflow a signed int back to 0.) * Alternatively, monitor the underlying filesystems's file inode.i_readcount over several open/close system calls. (should not monotonically increase; rather, return to 0.) [Regression Potential] * This changes the core path that aufs opens files, so there is a risk of regression; however, the fix changes aufs for how other filesystems work, so this generally is OK to do. In any case, most regressions would manifest in open() or close() (where the VFS handles/checks inode.i_readcount.) * The aufs maintainer has access to an internal test-suite used to validate aufs changes, used to identify the first regression (in the branch RW/RO mode change), and then to validate/publish the patches upstream; should be good now. * This has also been tested with 'stress-ng --class filesystem' and with 'xfstests -overlay' (patch to use aufs vs overlayfs) on Xenial/Bionic/Focal (-proposed vs. -proposed + patches). No regressions observed in stress-ng/xfstests log or dmesg. [Other Info] * Applied on Unstable (branches master and master-5.8) * Not required on Groovy (still 5.4; should sync from Unstable) * Required on LTS releases: Bionic and Focal and Xenial. * Required on other releases: Disco and Eoan (for custom kernels) [Original Bug Description] Problem Report: -- An user reported several nodes in their Kubernetes clusters hit a kernel panic at about the same time, and periodically (usually 35 days of uptime, and in same order nodes booted.) The kernel panics message/stack trace are consistent across nodes, in __fput() by iptables-save/restore from kube-proxy. Example: """ [3016161.866702] kernel BUG at .../include/linux/fs.h:2583! [3016161.866704] invalid opcode: [#1] SMP ... [3016161.866780] CPU: 40 PID: 33068 Comm: iptables-restor Tainted: P OE 4.4.0-133-generic #159-Ubuntu ... [3016161.866786] RIP: 0010:[...] [...] __fput+0x223/0x230 ... [3016161.866818] Call Trace: [3016161.866823] [...] fput+0xe/0x10 [3016161.866827] [...] task_work_run+0x86/0xb0 [3016161.866831] [...] exit_to_usermode_loop+0xc2/0xd0 [3016161.866833] [...] syscall_return_slowpath+0x4e/0x60 [3016161.866839] [...] int_ret_from_sys_call+0x25/0x9f """ (uptime: 3016161
[Kernel-packages] [Bug 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x
** Changed in: ubuntu-z-systems Status: New => In Progress -- 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/1888507 Title: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: New Status in linux source package in Bionic: In Progress Bug description: We need to run BPF filters to analyse and monitor network traffic. The BPF filters are created by skydive (http://skydive.network). Currently skydive fails to install BPF filters on s390x (using Ubuntu 18.04 currently, soon moving to Ubuntu 20.04). Because of these failures, we decided to try the BPF samples that come with the kernel first. These samples also fail on s390x while they work fine on Intel. shense@boe-build:~/bionic/samples/bpf$ uname -a Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC 2020 s390x s390x s390x GNU/Linux Example instructions: sudo apt install -y dpkg-dev clang llvm libelf-dev sudo apt-get source linux-image-unsigned-$(uname -r) cd linux-4.15.0/ make headers_install make samples/bpf/ Errors: shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map [sudo] password for shense: invalid relo for insn[4].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test invalid relo for insn[22].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+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 1888510] [NEW] xen-netfront: potential deadlock in xennet_remove()
Public bug reported: [Impact] During our AWS testing we were experiencing deadlocks on hibernate across all Xen instance types. The trace was showing that the system was stuck in xennet_remove(): [ 358.109087] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): [ 358.115102] modprobeD0 4892 4833 0x4004 [ 358.115104] Call Trace: [ 358.115112] __schedule+0x2a8/0x670 [ 358.115115] schedule+0x33/0xa0 [ 358.115118] xennet_remove+0x1f0/0x230 [xen_netfront] [ 358.115121] ? wait_woken+0x80/0x80 [ 358.115124] xenbus_dev_remove+0x51/0xa0 [ 358.115126] device_release_driver_internal+0xe0/0x1b0 [ 358.115127] driver_detach+0x49/0x90 [ 358.115129] bus_remove_driver+0x59/0xd0 [ 358.115131] driver_unregister+0x2c/0x40 [ 358.115132] xenbus_unregister_driver+0x12/0x20 [ 358.115134] netif_exit+0x10/0x7aa [xen_netfront] [ 358.115137] __x64_sys_delete_module+0x146/0x290 [ 358.115140] do_syscall_64+0x5a/0x130 [ 358.115142] entry_SYSCALL_64_after_hwframe+0x44/0xa9 This prevented hibernation to complete. The reason of this problem is a race condition in xennet_remove(): the system is reading the current state of the bus, it's requesting to change the state to "Closing", and it's waiting for the state to be changed to "Closing". However, if the state becomes "Closed" between reading the state and requesting the state change, we are stuck forever, because the state will never change from "Closed" back to "Closing". [Test case] Create any Xen-based instance in AWS, hibernate/resume multiple times. Some times the system gets stuck (hung task timeout). [Fix] Prevent the deadlock by changing the wait condition to check also for state == Closed. [Regression potential] Minimal, this change affects only Xen, more exactly only the xen- netfront driver. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1888510 Title: xen-netfront: potential deadlock in xennet_remove() Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Eoan: New Status in linux-aws source package in Focal: New Bug description: [Impact] During our AWS testing we were experiencing deadlocks on hibernate across all Xen instance types. The trace was showing that the system was stuck in xennet_remove(): [ 358.109087] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): [ 358.115102] modprobeD0 4892 4833 0x4004 [ 358.115104] Call Trace: [ 358.115112] __schedule+0x2a8/0x670 [ 358.115115] schedule+0x33/0xa0 [ 358.115118] xennet_remove+0x1f0/0x230 [xen_netfront] [ 358.115121] ? wait_woken+0x80/0x80 [ 358.115124] xenbus_dev_remove+0x51/0xa0 [ 358.115126] device_release_driver_internal+0xe0/0x1b0 [ 358.115127] driver_detach+0x49/0x90 [ 358.115129] bus_remove_driver+0x59/0xd0 [ 358.115131] driver_unregister+0x2c/0x40 [ 358.115132] xenbus_unregister_driver+0x12/0x20 [ 358.115134] netif_exit+0x10/0x7aa [xen_netfront] [ 358.115137] __x64_sys_delete_module+0x146/0x290 [ 358.115140] do_syscall_64+0x5a/0x130 [ 358.115142] entry_SYSCALL_64_after_hwframe+0x44/0xa9 This prevented hibernation to complete. The reason of this problem is a race condition in xennet_remove(): the system is reading the current state of the bus, it's requesting to change the state to "Closing", and it's waiting for the state to be changed to "Closing". However, if the state becomes "Closed" between reading the state and requesting the state change, we are stuck forever, because the state will never change from "Closed" back to "Closing". [Test case] Create any Xen-based instance in AWS, hibernate/resume multiple times. Some times the system gets stuck (hung task timeout). [Fix] Prevent the deadlock by changing the wait condition to check also for state == Closed. [Regression potential] Minimal, this change affects only Xen, more exactly only the xen- netfront driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1888510/+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 1849567] Re: zfs-linux 0.7.5-1ubuntu16.6 ADT test failure with linux-hwe-edge 5.3.0-19.20~18.04.2
Tested with HWE 5.3.0-19-generic and 5.4.0-42-generic, not an issue now. Marking as fixed released. ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu) Status: New => Fix Released ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1849567 Title: zfs-linux 0.7.5-1ubuntu16.6 ADT test failure with linux-hwe-edge 5.3.0-19.20~18.04.2 Status in zfs-linux package in Ubuntu: Fix Released Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20191023_190127_604c5@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20191023_194206_604c5@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20191023_190644_604c5@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849567/+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 1873961] Re: tc filter show tcp_flags wrong mask value
Test build of proposed change at: https://launchpad.net/~smb/+archive/ubuntu/bionic ** Merge proposal linked: https://code.launchpad.net/~smb/ubuntu/+source/iproute2/+git/iproute2/+merge/387837 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: In Progress Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: In Progress Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress -- 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/1888507 Title: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: In Progress Bug description: We need to run BPF filters to analyse and monitor network traffic. The BPF filters are created by skydive (http://skydive.network). Currently skydive fails to install BPF filters on s390x (using Ubuntu 18.04 currently, soon moving to Ubuntu 20.04). Because of these failures, we decided to try the BPF samples that come with the kernel first. These samples also fail on s390x while they work fine on Intel. shense@boe-build:~/bionic/samples/bpf$ uname -a Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC 2020 s390x s390x s390x GNU/Linux Example instructions: sudo apt install -y dpkg-dev clang llvm libelf-dev sudo apt-get source linux-image-unsigned-$(uname -r) cd linux-4.15.0/ make headers_install make samples/bpf/ Errors: shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map [sudo] password for shense: invalid relo for insn[4].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test invalid relo for insn[22].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+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 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- 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/1888507 Title: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: We need to run BPF filters to analyse and monitor network traffic. The BPF filters are created by skydive (http://skydive.network). Currently skydive fails to install BPF filters on s390x (using Ubuntu 18.04 currently, soon moving to Ubuntu 20.04). Because of these failures, we decided to try the BPF samples that come with the kernel first. These samples also fail on s390x while they work fine on Intel. shense@boe-build:~/bionic/samples/bpf$ uname -a Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC 2020 s390x s390x s390x GNU/Linux Example instructions: sudo apt install -y dpkg-dev clang llvm libelf-dev sudo apt-get source linux-image-unsigned-$(uname -r) cd linux-4.15.0/ make headers_install make samples/bpf/ Errors: shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map [sudo] password for shense: invalid relo for insn[4].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test invalid relo for insn[22].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
I made this video after the last updates, which include: pulseaudio-libraries and linux-firmwares. I created a new user, to see if it was a desktop problem or user settings, but the problem remained. We are available. Hugs. Thanks. ** Attachment added: "sem título.webm" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1884255/+attachment/5394894/+files/sem%20t%C3%ADtulo.webm -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id :
[Kernel-packages] [Bug 1888507] [NEW] [UBUNTU 18.04] BPF programs fail on Ubuntu s390x
Public bug reported: We need to run BPF filters to analyse and monitor network traffic. The BPF filters are created by skydive (http://skydive.network). Currently skydive fails to install BPF filters on s390x (using Ubuntu 18.04 currently, soon moving to Ubuntu 20.04). Because of these failures, we decided to try the BPF samples that come with the kernel first. These samples also fail on s390x while they work fine on Intel. shense@boe-build:~/bionic/samples/bpf$ uname -a Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC 2020 s390x s390x s390x GNU/Linux Example instructions: sudo apt install -y dpkg-dev clang llvm libelf-dev sudo apt-get source linux-image-unsigned-$(uname -r) cd linux-4.15.0/ make headers_install make samples/bpf/ Errors: shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map [sudo] password for shense: invalid relo for insn[4].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test invalid relo for insn[22].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields ** Affects: ubuntu-z-systems Importance: Medium Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-187029 severity-medium targetmilestone-inin1804 ** Tags added: architecture-s39064 bugnameltc-187029 severity-medium targetmilestone-inin1804 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (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/1888507 Title: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: We need to run BPF filters to analyse and monitor network traffic. The BPF filters are created by skydive (http://skydive.network). Currently skydive fails to install BPF filters on s390x (using Ubuntu 18.04 currently, soon moving to Ubuntu 20.04). Because of these failures, we decided to try the BPF samples that come with the kernel first. These samples also fail on s390x while they work fine on Intel. shense@boe-build:~/bionic/samples/bpf$ uname -a Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC 2020 s390x s390x s390x GNU/Linux Example instructions: sudo apt install -y dpkg-dev clang llvm libelf-dev sudo apt-get source linux-image-unsigned-$(uname -r) cd linux-4.15.0/ make headers_install make samples/bpf/ Errors: shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map [sudo] password for shense: invalid relo for insn[4].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test invalid relo for insn[22].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 =
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
The new kernel 5.7.10 has the ACPI ID for this touchpad added to the elan-i2c-ids.h. See kernel.org: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/include/linux/input /elan-i2c-ids.h?h=v5.7.10 Just adding the device ID did not fix this problem for me but perhaps more changes were made for this kernel. I will give it a try. -- 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/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+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 1888405] Re: zfsutils-linux: zfs-volume-wait.service fails with locked encrypted zvols
This bug was fixed in the package zfs-linux - 0.8.4-1ubuntu10 --- zfs-linux (0.8.4-1ubuntu10) groovy; urgency=medium * Fix volume wait on locked encrypted zvols (LP: #1888405) [ James Dingwall ] - 4620-zfs-vol-wait-fix-locked-encrypted-vols.patch zfs-volume-wait.service systemd unit does not start if the encrypted zvol is locked. The /sbin/zvol_wait should not wait for links when the volume has property keystatus=unavailable. Add a check for this. -- Colin Ian King Wed, 22 Jul 2020 09:58:22 +0100 ** Changed in: zfs-linux (Ubuntu Groovy) Status: In Progress => Fix Released -- 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/1888405 Title: zfsutils-linux: zfs-volume-wait.service fails with locked encrypted zvols Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification Focal == When an encrypted zvol is locked the zfs-volume-wait service does not start. The /sbin/zvol_wait should not wait for links when the volume has property keystatus=unavailable. == Fix == The attached patch in comment #1. == Test == lock an encrypted zvol. without the fix the volume wait will block the boot. with the fix it is not blocked. == Regression Potential == Limited to zvol wait - this change affects just the encrypted vols checking. - I was doing some experimentation with encrypted zvols and observed that the zfs-volume-wait.service systemd unit does not start if the encrypted zvol is locked. The /sbin/zvol_wait should not wait for links when the volume has property keystatus=unavailable. The attached patch seems to resolve the issue for me. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.1 Candidate: 0.8.3-1ubuntu12.2 Version table: 0.8.3-1ubuntu12.2 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 0.8.3-1ubuntu12.1 100 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405/+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 1888507] [NEW] [UBUNTU 18.04] BPF programs fail on Ubuntu s390x
You have been subscribed to a public bug: We need to run BPF filters to analyse and monitor network traffic. The BPF filters are created by skydive (http://skydive.network). Currently skydive fails to install BPF filters on s390x (using Ubuntu 18.04 currently, soon moving to Ubuntu 20.04). Because of these failures, we decided to try the BPF samples that come with the kernel first. These samples also fail on s390x while they work fine on Intel. shense@boe-build:~/bionic/samples/bpf$ uname -a Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC 2020 s390x s390x s390x GNU/Linux Example instructions: sudo apt install -y dpkg-dev clang llvm libelf-dev sudo apt-get source linux-image-unsigned-$(uname -r) cd linux-4.15.0/ make headers_install make samples/bpf/ Errors: shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map [sudo] password for shense: invalid relo for insn[4].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (b7) r1 = 0 2: (63) *(u32 *)(r10 -32) = r1 3: (bf) r1 = r7 4: (85) call unknown#-1 BPF_CALL uses reserved fields shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test invalid relo for insn[22].code 0x85 bpf_load_program() err=22 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields 0: (bf) r7 = r1 1: (18) r1 = 0x207265743a25646e 3: (7b) *(u64 *)(r10 -16) = r1 4: (18) r1 = 0x705f616c6c6f632e 6: (7b) *(u64 *)(r10 -24) = r1 7: (18) r1 = 0x5f6c72755f686d61 9: (7b) *(u64 *)(r10 -32) = r1 10: (18) r1 = 0x7420737472657373 12: (7b) *(u64 *)(r10 -40) = r1 13: (18) r1 = 0x4661696c65642061 15: (7b) *(u64 *)(r10 -48) = r1 16: (b7) r1 = 0 17: (73) *(u8 *)(r10 -8) = r1 18: (b7) r2 = 1 19: (7b) *(u64 *)(r10 -72) = r2 20: (63) *(u32 *)(r10 -76) = r1 21: (bf) r1 = r7 22: (85) call unknown#-1 BPF_CALL uses reserved fields ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-187029 severity-medium targetmilestone-inin1804 -- [UBUNTU 18.04] BPF programs fail on Ubuntu s390x https://bugs.launchpad.net/bugs/1888507 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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-xenial
--
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/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
In Progress
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users of bcache who manually specified a block size
greater than the page size when creating the device
with 'make-bcache' started to hit a kernel BUG/oops
after kernel upgrades. (This is not widely used.)
* The issue has been exposed with commit ad6bf88a6c19
("block: fix an integer overflow in logical block size")
because it increased the range of values accepted as
logical block size, which used to overflow to zero,
and thus receive a default of 512 via block layer.
* The issue existed previously, but with fewer values
exposed (e.g. 8k, 16k, 32k); the regression reports
happened with larger values (512k) for RAID stripes.
[Fix]
* The upstream commit dcacbc1242c7 ("bcache: check and
adjust logical block size for backing devices") checks
the block size and adjusts it if needed, to the value
of the underlying device's logical block size.
* It is merged as of v5.8-rcN, and sent to v5.7 stable.
[Test Case]
* Run make-bcache with block size greater than page size.
$ sudo make-bcache --bdev $DEV --block 8k
* Expected results: bcache device registered; no BUG/oops.
* Details steps on comment #43.
[Regression Potential]
* Restricted to users who specify a bcache block size
greater than page size.
* Regressions could theoretically manifest on bcache
device probe/register, if the underlying device's
logical block size for whatever triggers issues not
seen previously with the overflow/default 512 bytes.
[Other Info]
* Unstable has the patch on both master/master-5.7.
* Groovy should get it on rebase.
[Original Bug Description]
After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does
not boot any longer. It always crashes during boot with a kernel panic.
I suspect that this crash might be related to Bcache because this is
the only one of our systems where we use Bcache and the kernel panic
appears right after Bcache initialization.
I already checked that this bug still exists in the 4.15.0-92.93
kernel from proposed.
Unfortunately, I cannot do a bisect because this is a critical
production system and we do not have any other system with a similar
configuration.
I attached a screenshot with the trace of the kernel panic.
The last message that appears before the kernel panic (or rather the
last one that I can see - there is a rather long pause between that
message and the panic and I cannot scroll up far enough to ensure that
there are no other messages in between) is:
bcache: register_bcache() error /dev/dm-0: device already registered
When booting with kernel 4.15.0-88 that does not have this problem,
the next message is
bcache: register_bcache() error /dev/dm-12: device already registered
(emitting change event)
After that the next message is:
Begin: Loading essential drivers ... done
This message also appears after the kernel panic, but the boot process
stalls and the system can only be recovered by doing a hardware reset.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-88-generic 4.15.0-88.88
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 17 21:08 seq
crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
[Kernel-packages] [Bug 1867983] Re: Computer is frozen after suspend
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1867983 Title: Computer is frozen after suspend Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Confirmed Bug description: === SRU Justification === [Impact] Some systems with ATA drives freeze during suspend [Fix] Avoid circular sync dependency by using async cookie. [Test] User reports positive feedback. [Regression Potential] Low. This patch makes synchronize more targeted, prevents many potential freeze. === Original Bug Report === I am using an old HP EliteBook 6930p with current Ubuntu. When the computer is suspended, even after a fresh boot, it does not wake up: the power comes back, but the laptop is frozen, and does not respond to ping. It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42. I am holding kernel purge for now, but this is annoying. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isabelle 1010 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 20:46:35 2020 HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c InstallationDate: Installed on 2015-03-15 (1830 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago) dmi.bios.date: 07/31/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PCU Ver. F.12 dmi.board.name: 30DB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 87.27 dmi.chassis.asset.tag: CZC939161W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 6930p dmi.product.sku: J1610781 dmi.product.version: F.12 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867983/+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 1888494] [NEW] ss outputs lots of trailing spaces
Public bug reported: $ ss -atn | head -n 5 | tr ' ' '_' State__Recv-Q_Send-Q___Local_Address:Port_Peer_Address:Port_Process_ LISTEN_0__4096_127.0.0.53%lo:530.0.0.0:* LISTEN_0__224__127.0.0.1:5430__0.0.0.0:* LISTEN_0__1280.0.0.0:220.0.0.0:* LISTEN_0__5127.0.0.1:631___0.0.0.0:* These trailing spaces cause problems when piping ss output through grep or anything else unless the terminal window is very wide. The spaces are present even when stdout is a terminal, indeed if I maximize my terminal window (its width becomes a very reasonable 172 characters) and run ss without arguments, the output is interleaved with blank lines. env -i changes nothing. The spaces should be trimmed before output regardless of whether stdout is a terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: iproute2 5.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Jul 22 14:05:53 2020 SourcePackage: iproute2 UpgradeStatus: Upgraded to focal on 2020-04-26 (86 days ago) ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1888494 Title: ss outputs lots of trailing spaces Status in iproute2 package in Ubuntu: New Bug description: $ ss -atn | head -n 5 | tr ' ' '_' State__Recv-Q_Send-Q___Local_Address:Port_Peer_Address:Port_Process_ LISTEN_0__4096_127.0.0.53%lo:530.0.0.0:* LISTEN_0__224__127.0.0.1:5430__0.0.0.0:* LISTEN_0__1280.0.0.0:220.0.0.0:* LISTEN_0__5127.0.0.1:631___0.0.0.0:* These trailing spaces cause problems when piping ss output through grep or anything else unless the terminal window is very wide. The spaces are present even when stdout is a terminal, indeed if I maximize my terminal window (its width becomes a very reasonable 172 characters) and run ss without arguments, the output is interleaved with blank lines. env -i changes nothing. The spaces should be trimmed before output regardless of whether stdout is a terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: iproute2 5.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Jul 22 14:05:53 2020 SourcePackage: iproute2 UpgradeStatus: Upgraded to focal on 2020-04-26 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1888494/+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 1812978] Re: rtnetlink.sh in net from ubuntu_kernel_selftests fails
Issue found on 4.15.0-2006.7-azure-fips ** Tags added: sru-20200629 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1812978 Title: rtnetlink.sh in net from ubuntu_kernel_selftests fails Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Won't Fix Status in linux-aws source package in Cosmic: Won't Fix Bug description: There are several failures in this test: * ipv6 addrlabel * macsec * ipsec $ sudo ./rtnetlink.sh PASS: policy routing PASS: route get PASS: tc htb hierarchy PASS: gre tunnel endpoint PASS: gretap PASS: ip6gretap PASS: erspan PASS: ip6erspan PASS: bridge setup FAIL: ipv6 addrlabel PASS: set ifalias 485dc5aa-b024-4952-88a7-414355fc2bdc for test-dummy0 PASS: vrf PASS: vxlan FAIL: can't add fou port , skipping test *** stack smashing detected ***: terminated ./rtnetlink.sh: line 468: 5132 Aborted (core dumped) ip macsec show > /dev/null FAIL: macsec ./rtnetlink.sh: line 527: 5146 Terminated ip x m > $tmpfile FAIL: ipsec ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-14-generic 4.18.0-14.15 ProcVersionSignature: User Name 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 23 09:53 seq crw-rw 1 root audio 116, 33 Jan 23 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 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: Date: Wed Jan 23 10:01:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-14-generic N/A linux-backports-modules-4.18.0-14-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812978/+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 1873961] Re: tc filter show tcp_flags wrong mask value
** Changed in: ubuntu-power-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: In Progress Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: In Progress Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+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 1708049] Re: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur
Did the suggestion in comment #2 help? ** Changed in: zfs-linux (Ubuntu) Status: Triaged => 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/1708049 Title: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in zfs-linux package in Ubuntu: Incomplete Bug description: Ubuntu 16.04 . When it trys to update ZFS it fails and then several hours later the computer crashes.Reboot still crashes. Have to go back several updates to stop crashing. thanks R ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu17 Uname: Linux 4.9.24-040924-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 2 00:34:53 2017 DuplicateSignature: package:zfsutils-linux:0.6.5.6-0ubuntu17 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package zfsutils-linux (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-14 (109 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: zfs-linux Title: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1708049/+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 1887914] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394869/+files/ProcCpuinfoMinimal.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394870/+files/ProcInterrupts.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394873/+files/RfKill.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394874/+files/UdevDb.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394871/+files/ProcModules.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394875/+files/WifiSyslog.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394872/+files/PulseList.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394861/+files/CurrentDmesg.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394866/+files/Lsusb-t.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394864/+files/Lspci-vt.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394865/+files/Lsusb.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] Re: Partial freeze if booting with USB-C dock attached
apport information ** Description changed: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: leo1928 F pulseaudio + /dev/snd/controlC1: leo1928 F pulseaudio + /dev/snd/controlC0: leo1928 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-03-25 (484 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + MachineType: LENOVO 20N8CTO1WW + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal + Uname: Linux 5.4.0-40-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 06/15/2020 + dmi.bios.vendor: LENOVO + dmi.bios.version: R0YET44P (1.27 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20N8CTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40709 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad E490 + dmi.product.name: 20N8CTO1WW + dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 + dmi.product.version: ThinkPad E490 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394859/+files/AlsaInfo.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
[Kernel-packages] [Bug 1887914] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394860/+files/CRDA.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394863/+files/Lspci.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394867/+files/Lsusb-v.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394868/+files/ProcCpuinfo.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1887914] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1887914/+attachment/5394862/+files/IwConfig.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: leo1928 F pulseaudio /dev/snd/controlC1: leo1928 F pulseaudio /dev/snd/controlC0: leo1928 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (484 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20N8CTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@focal/boot/vmlinuz-5.4.0-40-generic root=UUID=cbee37f5-8d6e-4d54-a71d-cd0f24de1427 ro rootflags=subvol=@focal 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: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET44P (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET44P(1.27):bd06/15/2020:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+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 1873961] Re: tc filter show tcp_flags wrong mask value
** Description changed: + [SRU Justification] + + Impact: The tc command does not show the correct values for tcp_flags + (and ip_tos) on filter rules. This might break other scripts parsing + that output but at least confuses users. + + Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" + from upstream iproute2. + + Testcase: + tc qdisc add dev lo ingress + tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 + tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ + tcp_flags 0x909/f00 + + tc filter show dev lo parent : + + filter protocol ip pref 3 flower chain 0 + filter protocol ip pref 3 flower chain 0 handle 0x1 + eth_type ipv4 + ip_tos a9606c10 <-- bad, should be 0x8/32 + not_in_hw + filter protocol ip pref 5 flower chain 0 + filter protocol ip pref 5 flower chain 0 handle 0x1 + eth_type ipv4 + ip_proto tcp + tcp_flags 909909 <-- bad, should be ßx0ß0/f00 + not_in_hw + + Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is + is incorrect in both cases. + + Risk of Regression: + Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. + + + === Original description === + ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools - - + ---Steps to Reproduce--- - Steps to reproduce the problem: + Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r - + 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 - src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff - eth_type ipv4 - ip_proto tcp - tcp_flags 22 /* <--- Wrong */ - skip_sw - in_hw - action order 1: mirred (Egress Redirect to device p0v0_r) stolen - + src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff + eth_type ipv4 + ip_proto tcp + tcp_flags 22 /* <--- Wrong */ + skip_sw + in_hw + action order 1: mirred (Egress Redirect to device p0v0_r) stolen + 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r - - After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. - - Userspace tool common name: tc - - The userspace tool has the following bit modes: 64-bit + + After that, using "tc filter show dev p0v2_r root" to verify, we still + see the same output (tcp_flags 22) as shown in 2) above, which is wrong. + + Userspace tool common name: tc + + The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 - lib: introduce print_nl - Common pattern in iproute commands is to print a line seperator - in non-json mode. Make that a simple function. + lib: introduce print_nl + Common pattern in iproute commands is to print a line seperator + in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ - + patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 - tc: fix bugs for tcp_flags and ip_attr hex output - Fix hex output for both the ip_attr and tcp_flags print functions. - + tc: fix bugs for tcp_flags and ip_attr hex output + Fix hex output for both the ip_attr and tcp_flags print functions. + With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 - src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff - eth_type ipv4 - ip_proto tcp - tcp_flags 0x2/7 /* <--- Correct */ - skip_sw - in_hw - action order 1: mirred (Egress Redirect to device p0v0_r) stolen + src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff + eth_type ipv4 + ip_proto
[Kernel-packages] [Bug 1886390] Re: Fix an issue that HID devices are not scanned by Realtek 8822C
Verified that the new firmware fixes HID, Eddystone and OBEX issues. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1886390 Title: Fix an issue that HID devices are not scanned by Realtek 8822C Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] HID devices are not scanned by Realtek 8822C Bluetooth, so keyboard or mouse cannot connect to the host. [Fix] New firmware release for 8822C. [Test] HID devices can be scanned now. Pairing and connecting also work. [Regression Potential] Low. It's an upstream firmware release. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1886390/+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 1888442] Re: upgrade did not go well
You seem to be using ZFS on root (which is EXPERIMENTAL AFAIK). ... update-initramfs: Generating /boot/initrd.img-5.4.0-41-generic cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu cryptsetup: WARNING: Couldn't determine root device ... ** Package changed: systemd (Ubuntu) => zfs-linux (Ubuntu) -- 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/1888442 Title: upgrade did not go well Status in zfs-linux package in Ubuntu: New Bug description: Hello, I had some problems during my most recent apt upgrade. A confounding factor to these problems was removing my laptop from its docking station a few minutes earlier. $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic linux-image-5.4.0-42-generic linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic python3-click python3-colorama The following packages will be upgraded: base-files libnss-mymachines libnss-systemd libpam-systemd libpulse-mainloop-glib0 libpulse0 libpulsedsp libseccomp2 libsystemd0 libudev1 libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 linux-firmware linux-generic linux-headers-generic linux-image-generic pulseaudio pulseaudio-utils python3-distupgrade sudo systemd systemd-container systemd-journal-remote systemd-sysv systemd-timesyncd ubuntu-drivers-common ubuntu-release-upgrader-core udev 34 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 110 MB/184 MB of archives. After this operation, 360 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://wopr.domain/ubuntu focal-proposed/main amd64 base-files amd64 11ubuntu5.1 [60.1 kB] Get:2 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-systemd amd64 245.4-4ubuntu3.2 [95.6 kB] Get:3 http://wopr.domain/ubuntu focal-proposed/universe amd64 systemd-journal-remote amd64 245.4-4ubuntu3.2 [61.9 kB] Get:4 http://wopr.domain/ubuntu focal-proposed/main amd64 udev amd64 245.4-4ubuntu3.2 [1,363 kB] Get:5 http://wopr.domain/ubuntu focal-proposed/main amd64 libudev1 amd64 245.4-4ubuntu3.2 [78.9 kB] Get:6 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system amd64 6.0.0-0ubuntu8.2 [67.5 kB] Get:7 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-clients amd64 6.0.0-0ubuntu8.2 [343 kB] Get:8 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.2 [605 kB] Get:9 http://wopr.domain/ubuntu focal-proposed/universe amd64 libvirt-daemon-driver-storage-zfs amd64 6.0.0-0ubuntu8.2 [21.4 kB] Get:10 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-storage-rbd amd64 6.0.0-0ubuntu8.2 [28.3 kB] Get:11 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt0 amd64 6.0.0-0ubuntu8.2 [1,444 kB] Get:12 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon amd64 6.0.0-0ubuntu8.2 [404 kB] Get:13 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-mymachines amd64 245.4-4ubuntu3.2 [131 kB] Get:14 http://wopr.domain/ubuntu focal-proposed/main amd64 libseccomp2 amd64 2.4.3-1ubuntu3.20.04.3 [42.4 kB] Get:15 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-container amd64 245.4-4ubuntu3.2 [317 kB] Get:16 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.2 [12.3 kB] Get:17 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-sysv amd64 245.4-4ubuntu3.2 [10.3 kB] Get:18 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.2 [28.0 kB] Get:19 http://wopr.domain/ubuntu focal-proposed/main amd64 libpam-systemd amd64 245.4-4ubuntu3.2 [186 kB] Get:20 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd amd64 245.4-4ubuntu3.2 [3,796 kB] Get:21 http://wopr.domain/ubuntu focal-proposed/main amd64 libsystemd0 amd64 245.4-4ubuntu3.2 [271 kB] Get:22 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse-mainloop-glib0 amd64 1:13.99.1-1ubuntu3.5 [11.7 kB] Get:23 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulsedsp amd64 1:13.99.1-1ubuntu3.5 [21.7 kB] Get:24 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio-utils amd64 1:13.99.1-1ubuntu3.5 [55.0 kB] Get:25 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio amd64 1:13.99.1-1ubuntu3.5 [815 kB] Get:26 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse0 amd64 1:13.99.1-1ubuntu3.5 [263 kB] Get:27 http://wopr.domain/ubuntu focal/main amd64
[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
Oh, so the upstream patch had the test case all the time and I just blanked it, looking at the content there and visible comments in this bug report only. :/ Thanks for the pointer. That should be all needed and I can go on with the SRU process. ** Changed in: iproute2 (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Triaged Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: In Progress Bug description: ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+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
