[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
I just pushed a firmware that should fix this. Please try our latest version from https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git/plain/iwlwifi-8265-36.ucode This firmware is not upstream yet. I sent the pull request today. -- 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/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 Status in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. Firmware: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.840159] wlp2s0: send auth to 60:38:e0:70:a2:11 (try 1/3) Dec 13 11:53:36 james-x1 kernel: [ 856.844875] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Dec 13 11:53:36 james-x1 kernel: [ 856.845015] iwlwifi :02:00.0: Start IWL Error Log Dump: Dec 13 11:53:36 james-x1 kernel: [ 856.845018] iwlwifi :02:00.0: Status: 0x0100, count: 6 Dec 13 11:53:36 james-x1 kernel: [ 856.845021] iwlwifi :02:00.0: Loaded firmware version: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.845024] iwlwifi :02:00.0: 0x1006 | ADVANCED_SYSASSERT Dec 13 11:53:36 james-x1 kernel: [ 856.845026] iwlwifi :02:00.0: 0x02F0 | trm_hw_status0 Dec 13 11:53:36 james-x1 kernel: [ 856.845029] iwlwifi :02:00.0: 0x | trm_hw_status1 Dec 13 11:53:36 james-x1 kernel: [ 856.845031] iwlwifi :02:00.0: 0x000248DC | branchlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845034] iwlwifi :02:00.0: 0x0003A7DA | interruptlink1 Dec 13 11:53:36 james-x1 kernel: [ 856.845036] iwlwifi :02:00.0: 0x | interruptlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845039] iwlwifi :02:00.0: 0xFEDA | data1 Dec 13 11:53:36 james-x1 kernel: [ 856.845041] iwlwifi :02:00.0: 0xDEADBEEF | data2 Dec 13 11:53:36 james-x1 kernel: [ 856.845044] iwlwifi :02:00.0: 0xDEADBEEF | data3 Dec 13 11:53:36 james-x1 kernel: [ 856.845046] iwlwifi :02:00.0: 0x0007E1DC | beacon time Dec 13 11:53:36 james-x1 kernel: [ 856.845048] iwlwifi :02:00.0: 0x003B0850 | tsf low Dec 13 11:53:36 james-x1 kernel: [ 856.845051] iwlwifi :02:00.0: 0x | tsf hi Dec 13 11:53:36 james-x1 kernel: [ 856.845053] iwlwifi :02:00.0: 0x | time gp1 Dec 13 11:53:36 james-x1 kernel: [ 856.845055] iwlwifi :02:00.0: 0x003B0852 | time gp2 Dec 13 11:53:36 james-x1 kernel: [ 856.845058] iwlwifi :02:00.0: 0x0001 | uCode revision type Dec 13 11:53:36 james-x1 kernel: [ 856.845060] iwlwifi :02:00.0: 0x0024 | uCode version major Dec 13 11:53:36 james-x1 kernel: [ 856.845063] iwlwifi :02:00.0: 0x7596AFD4 | uCode version minor Dec 13 11:53:36 james-x1 kernel: [ 856.845065] iwlwifi :02:00.0: 0x0230 | hw version Dec 13 11:53:36 james-x1 kernel: [ 856.845068] iwlwifi :02:00.0: 0x18489000 | board version Dec 13 11:53:36 james-x1 kernel: [ 856.845070] iwlwifi :02:00.0: 0x0501001C | hcmd Dec 13 11:53:36 james-x1 kernel: [ 856.845072] iwlwifi :02:00.0: 0x00023008 | isr0 Dec 13 11:53:36 james-x1 kernel: [ 856.845075] iwlwifi :02:00.0: 0x000D | isr1 Dec 13 11:53:36 james-x1 kernel: [ 856.845077] iwlwifi :02:00.0: 0x08001802 | isr2 Dec 13 11:53:36 james-x1 kernel: [ 856.845080] iwlwifi :02:00.0: 0x0041FDC0 | isr3 Dec 13 11:53:36 james-x1 kernel: [ 856.845082] iwlwifi :02:00.0: 0x | isr4 Dec 13 11:53:36 james-x1 kernel: [ 856.845084] iwlwifi :02:00.0: 0x00580118 | last cmd Id Dec 13 11:53:36 james-x1 kernel: [ 856.845087] iwlwifi :02:00.0: 0x | wait_event Dec 13 11:53:36 james-x1 kernel: [ 856.845089] iwlwifi :02:00.0: 0x76DD | l2p_control Dec 13 11:53:36 james-x1 kernel: [ 856.845091] iwlwifi :02:00.0: 0x0020 | l2p_duration Dec 13 11:53:36 james-x1 kernel: [ 856.845094] iwlwifi :02:00.0: 0x | l2p_mhvalid Dec 13 11:53:36 james-x1 kernel: [ 856.845096] iwlwifi :02:00.0: 0x00A0 | l2p_addr_match Dec 13 11:53:36 james-x1 kernel: [ 856.845099] iwlwifi :02:00.0: 0x000D | lmpm_pmg_sel Dec 13 11:53:36 james-x1 kernel: [ 856.845101] iwlwifi :02:00.0: 0x22040707 | timestamp Dec 13 11:53:36 james-x1 kernel: [ 856.845103] iwlwifi :02:00.0: 0x6070 | flow_handler Dec 13 11:53:36 james-x1 kernel: [ 856.845170] iwlwifi :02:00.0: Start IWL Error Log Dump: Dec 13 11:53:36 james-x1 kernel: [ 856.845173] iwlwifi :02:00.0: Status: 0x0100, count: 7 Dec 13 11:53:36 james-x1 kernel: [ 856.845176] iwlwifi :02:00.0: 0x0070 | ADVANCED_SYSASSERT Dec 13 11:53:36 james-x1 kernel: [ 856.845178] iwlwifi :02:00.0: 0x | umac branchlink1 Dec 13 11:53:36 james-x1 kernel: [ 856.845181] iw
[Kernel-packages] [Bug 1808609] Re: None of my external drives appear after Linux crash.
The last time I tried the "upstream kernel" the bug (different bug) was still there. And I had to reinstall Linux afterwards just to get a working system. After having to reinstall Linux six times I'm getting tired of it. Finding the bug does not help if the crash corrupted the drive superblocks. I need a tool to recover from the damage the crash did to my drives. My data is more important to me than trying to find the memory lead in Caja that caused the crash in the first place. Surely I am not the only one suffering from corruption of external hard drives. Unfortunately I am on a fixed income and cannot afford the $500+ that a recovery service charges to recover my data (x 7 drives all corrupted by the same crash). -- 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/1808609 Title: None of my external drives appear after Linux crash. Status in linux package in Ubuntu: Incomplete Bug description: First my system became incredibly slow (consistent with the memory leak in Caja). I xKill Caja and then tried to restart it. I then closed every app and tried to do a shutdown. I got a warning that Caja still had processes running preventing shutdown. I chose shut down anyway. I eventually got the progress screen showing that Linux was trying to shut down. After 1 1/2 hours of the progress screen, I manually turned off power. I was able to reboot but all of my external drives are missing. I tried turning off and then back on one drive with no result. When I plug a drive back in I do not feel the vibration caused by the drive spinning up. Nor do I feel the drive do the initial seek. This indicated that Linux is not even attempting to access the drives. Do I have to reinstall Ubuntu MATE 18.10 (again) in order to use external USB drives? The attached screen shots shows only partitions on my two internal hard drives. Gparted does not show the disks. Disks from the Control Center shows only internal devices. Without access to my external drives I am stalled. I can't even do backups. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2606 F pulseaudio /dev/snd/controlC0: robert 2606 F pulseaudio CurrentDesktop: MATE Date: Fri Dec 14 22:38:44 2018 InstallationDate: Installed on 2018-11-30 (14 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A 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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1808609/+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 1808677] [NEW] apt hangs when updating to inux-headers-4.18.0-12-generic
Public bug reported: When updating only the kernel it hangs: apt install --only-upgrade linux-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-headers-4.18.0-12 linux-headers-4.18.0-12-generic linux-headers-generic linux-image-4.18.0-12-generic linux-image-generic linux-modules-4.18.0-12-generic linux-modules-extra-4.18.0-12-generic Suggested packages: fdutils linux-doc-4.18.0 | linux-source-4.18.0 linux-tools The following NEW packages will be installed: linux-headers-4.18.0-12 linux-headers-4.18.0-12-generic linux-image-4.18.0-12-generic linux-modules-4.18.0-12-generic linux-modules-extra-4.18.0-12-generic The following packages will be upgraded: linux-generic linux-headers-generic linux-image-generic 3 upgraded, 5 newly installed, 0 to remove and 148 not upgraded. Need to get 0 B/66,0 MB of archives. After this operation, 330 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Reading changelogs... Done Selecting previously unselected package linux-modules-4.18.0-12-generic. (Reading database ... 269826 files and directories currently installed.) Preparing to unpack .../0-linux-modules-4.18.0-12-generic_4.18.0-12.13_amd64.deb ... Unpacking linux-modules-4.18.0-12-generic (4.18.0-12.13) ... Selecting previously unselected package linux-image-4.18.0-12-generic. Preparing to unpack .../1-linux-image-4.18.0-12-generic_4.18.0-12.13_amd64.deb ... Unpacking linux-image-4.18.0-12-generic (4.18.0-12.13) ... Selecting previously unselected package linux-modules-extra-4.18.0-12-generic. Preparing to unpack .../2-linux-modules-extra-4.18.0-12-generic_4.18.0-12.13_amd64.deb ... Unpacking linux-modules-extra-4.18.0-12-generic (4.18.0-12.13) ... Preparing to unpack .../3-linux-generic_4.18.0.12.13_amd64.deb ... Unpacking linux-generic (4.18.0.12.13) over (4.18.0.11.12) ... Preparing to unpack .../4-linux-image-generic_4.18.0.12.13_amd64.deb ... Unpacking linux-image-generic (4.18.0.12.13) over (4.18.0.11.12) ... Selecting previously unselected package linux-headers-4.18.0-12. Preparing to unpack .../5-linux-headers-4.18.0-12_4.18.0-12.13_all.deb ... Unpacking linux-headers-4.18.0-12 (4.18.0-12.13) ... Selecting previously unselected package linux-headers-4.18.0-12-generic. Preparing to unpack .../6-linux-headers-4.18.0-12-generic_4.18.0-12.13_amd64.deb ... Unpacking linux-headers-4.18.0-12-generic (4.18.0-12.13) ... Preparing to unpack .../7-linux-headers-generic_4.18.0.12.13_amd64.deb ... Unpacking linux-headers-generic (4.18.0.12.13) over (4.18.0.11.12) ... Setting up linux-headers-4.18.0-12 (4.18.0-12.13) ... Setting up linux-modules-4.18.0-12-generic (4.18.0-12.13) ... Setting up linux-headers-4.18.0-12-generic (4.18.0-12.13) ... ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: cosmic -- 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/1808677 Title: apt hangs when updating to inux-headers-4.18.0-12-generic Status in linux package in Ubuntu: Incomplete Bug description: When updating only the kernel it hangs: apt install --only-upgrade linux-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-headers-4.18.0-12 linux-headers-4.18.0-12-generic linux-headers-generic linux-image-4.18.0-12-generic linux-image-generic linux-modules-4.18.0-12-generic linux-modules-extra-4.18.0-12-generic Suggested packages: fdutils linux-doc-4.18.0 | linux-source-4.18.0 linux-tools The following NEW packages will be installed: linux-headers-4.18.0-12 linux-headers-4.18.0-12-generic linux-image-4.18.0-12-generic linux-modules-4.18.0-12-generic linux-modules-extra-4.18.0-12-generic The following packages will be upgraded: linux-generic linux-headers-generic linux-image-generic 3 upgraded, 5 newly installed, 0 to remove and 148 not upgraded. Need to get 0 B/66,0 MB of archives. After this operation, 330 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Reading changelogs... Done Selecting previously unselected package linux-modules-4.18.0-12-generic. (Reading database ... 269826 files and directories currently installed.) Preparing to unpack .../0-linux-modules-4.18.0-12-generic_4.18.0-12.13_amd64.deb ... Unpacking linux-modules-4.18.0-12-generic (4.18.0-12.13) ... Selecting previously unselected package linux-image-4.18.0-12-generic. Preparing to unpack .../1-linux-image-4.18.0-12-generic_4.18.0-12.13_amd64.deb ... Unpacking linux-image-4.18.0-12-generic (4.18.0-12.13) ... Selecting previously unselected package linux-modules-extra-4.18.0-12-generic. Preparing to unpack .../2-linux-modules-extra-4.18.0-12-generic_4.18.0-12.13_
[Kernel-packages] [Bug 1808677] 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 1808677 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: cosmic -- 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/1808677 Title: apt hangs when updating to inux-headers-4.18.0-12-generic Status in linux package in Ubuntu: Incomplete Bug description: When updating only the kernel it hangs: apt install --only-upgrade linux-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-headers-4.18.0-12 linux-headers-4.18.0-12-generic linux-headers-generic linux-image-4.18.0-12-generic linux-image-generic linux-modules-4.18.0-12-generic linux-modules-extra-4.18.0-12-generic Suggested packages: fdutils linux-doc-4.18.0 | linux-source-4.18.0 linux-tools The following NEW packages will be installed: linux-headers-4.18.0-12 linux-headers-4.18.0-12-generic linux-image-4.18.0-12-generic linux-modules-4.18.0-12-generic linux-modules-extra-4.18.0-12-generic The following packages will be upgraded: linux-generic linux-headers-generic linux-image-generic 3 upgraded, 5 newly installed, 0 to remove and 148 not upgraded. Need to get 0 B/66,0 MB of archives. After this operation, 330 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Reading changelogs... Done Selecting previously unselected package linux-modules-4.18.0-12-generic. (Reading database ... 269826 files and directories currently installed.) Preparing to unpack .../0-linux-modules-4.18.0-12-generic_4.18.0-12.13_amd64.deb ... Unpacking linux-modules-4.18.0-12-generic (4.18.0-12.13) ... Selecting previously unselected package linux-image-4.18.0-12-generic. Preparing to unpack .../1-linux-image-4.18.0-12-generic_4.18.0-12.13_amd64.deb ... Unpacking linux-image-4.18.0-12-generic (4.18.0-12.13) ... Selecting previously unselected package linux-modules-extra-4.18.0-12-generic. Preparing to unpack .../2-linux-modules-extra-4.18.0-12-generic_4.18.0-12.13_amd64.deb ... Unpacking linux-modules-extra-4.18.0-12-generic (4.18.0-12.13) ... Preparing to unpack .../3-linux-generic_4.18.0.12.13_amd64.deb ... Unpacking linux-generic (4.18.0.12.13) over (4.18.0.11.12) ... Preparing to unpack .../4-linux-image-generic_4.18.0.12.13_amd64.deb ... Unpacking linux-image-generic (4.18.0.12.13) over (4.18.0.11.12) ... Selecting previously unselected package linux-headers-4.18.0-12. Preparing to unpack .../5-linux-headers-4.18.0-12_4.18.0-12.13_all.deb ... Unpacking linux-headers-4.18.0-12 (4.18.0-12.13) ... Selecting previously unselected package linux-headers-4.18.0-12-generic. Preparing to unpack .../6-linux-headers-4.18.0-12-generic_4.18.0-12.13_amd64.deb ... Unpacking linux-headers-4.18.0-12-generic (4.18.0-12.13) ... Preparing to unpack .../7-linux-headers-generic_4.18.0.12.13_amd64.deb ... Unpacking linux-headers-generic (4.18.0.12.13) over (4.18.0.11.12) ... Setting up linux-headers-4.18.0-12 (4.18.0-12.13) ... Setting up linux-modules-4.18.0-12-generic (4.18.0-12.13) ... Setting up linux-headers-4.18.0-12-generic (4.18.0-12.13) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808677/+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 1808528] Re: Update linux-firmware in bionic for 18.10 hwe kernel
Hello Seth, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Description changed: SRU Justification Impact: A 4.18-based hwe kernel has been introduced into bionic. However some of the firmware files it requires are missing from bionic's linux- firmware, rendering the relevant hardware inoperable. Fix: Add the missing firmware files. Regression Potential: Most of these files will not be used by the - existing kernels in xenial. A few may be, and while regressions are not + existing kernels in bionic. A few may be, and while regressions are not expected it's possible that new firmware versions might introduce regressions. -- 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/1808528 Title: Update linux-firmware in bionic for 18.10 hwe kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Fix Committed Bug description: SRU Justification Impact: A 4.18-based hwe kernel has been introduced into bionic. However some of the firmware files it requires are missing from bionic's linux-firmware, rendering the relevant hardware inoperable. Fix: Add the missing firmware files. Regression Potential: Most of these files will not be used by the existing kernels in bionic. A few may be, and while regressions are not expected it's possible that new firmware versions might introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1808528/+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 1806914] Re: [18.04] update-initramfs fails to generate correct initrd
This trouble arises when trying to update initramfs from the isofile (ubuntu-18.04.1-desktop-amd64.iso) as soon as ubiquity terminates the installation. update-initramfs succeeds when run from an installed instance of Ubuntu and after a chroot command, or, afterwards, from a running 18.04 system. This seems to point the bug to the isofile. -- 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/1806914 Title: [18.04] update-initramfs fails to generate correct initrd Status in linux package in Ubuntu: Confirmed Bug description: Hi I get many trouble in trying to generate a correct initrd.img for the following configuration clear lvm on /dev/sd4 partition (msdos) several logical volumes, some clear and some luks-encrypted / et /home on encrypted logical volumes, each with its own 512 byte binary key-file on removable device (USB stick) /boot et /usr on clear logical volumes I am still running 14.04 due to trouble with 16.04, maybe because I missed the introduction of the "initramfs" crypttab option. I dropped any investigation hoping for the trouble being solved with 18.04. This is not the case. I run into trouble as soon as I tried to update initrd.img with update-initramfs. victor-odos goes to /, victor-oikia goes to /home I rewrote passdev and stored it in /lib/cryptsetup/bash/passdev 1/ with crypttab referencing my binary key-files victor-odos /dev/mapper/victor-odos_l /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-odos:1 luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs victor-oikia /dev/mapper/victor-oikia_l /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-oikia:1 luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs I join two files : /dev/stdout sent to .log and /dev/stderr to .err 2/ with no key-files victor-odos /dev/mapper/victor-odos_l none luks,initramfs victor-oikia /dev/mapper/victor-oikia_l none luks,initramfs I don't know how to bypass this issue When this has been solved, I intend to detach luks headers. How to code crypttab as I don't know the operational file hierarchy inside initrd ? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2114 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3550 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper iso-scan/filename=/amorces/username-18.04.1-desktop-amd64.iso quiet splash --- ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3550 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+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 1503695] Re: nft nat not working
Please try on a newer Ubuntu, 18.04 or later, that ships updated linux
kernel and nftables.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: nftables (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1503695
Title:
nft nat not working
Status in linux package in Ubuntu:
Incomplete
Status in nftables package in Ubuntu:
Incomplete
Bug description:
Hi ,
I have installed an ubuntu 15.10 beta machine and configured nftables
firewalling.
While the regular firewalling works (using the default settings that
come with the package), I found that nat rules are silently ignored.
I've added this to the /etc/nftables.conf and read it:
table ip nat {
chain prerouting {
type nat hook prerouting priority 0;
ip daddr 1.2.3.4 tcp dport 80 redirect to 1234
tcp dport 80 redirect to 1235
}
chain postrouting {
type nat hook postrouting priority 0;
}
}
following the example from
http://wiki.nftables.org/wiki-
nftables/index.php/Performing_Network_Address_Translation_%28NAT%29#Redirect
(1.2.3.4 is just a placeholder for the address actually used here, i
do not want to reveal the address to the bug report). nft reads this
without complaining, and
nft list table ip nat
gives exactly that output (except for replacing 80 with "http"), so
the configuration is read correctly.
But it simply does not work. Without having any daemon listening on
ports 1234, 1235 , traffic to port 80 works as usual. As long as there
is not process waiting on 1234/1235, connection should be refused.
Which is dangerous and a security flaw, since this was meant (and used
in a similar way with iptables and Ubuntu 14.04) to avoid revealing
sensitive data over the internet (an application that is not able to
use https should be tunneled). When firewall rules have been loaded
and accepted without any warning, one would expect them to run.
Ive tried to unload all iptables-related kernel packages and to load
packages like nft_nat, nft_redir, nft_redir_ipv4, but the direct
connection to port 80 still works although it shouldn't.
No error warning, no message. It just allows outgoing port 80 although
it shouldn't.
Which is a problem, since this is security-relevant. If it doesn't
work, it should spit out some error message.
(FYI: It was implemented under Ubuntu 14.04 with
iptables -t nat -I OUTPUT -d 1.2.3.4 -p tcp --dport 80 -j REDIRECT --to-port
1234
)
My current guess: On that wiki page's bottem there's a hint that iptables and
nft nat cannot be used at the same time. Unfortunately Ubuntu 15.10 still loads
plenty of iptables stuff. Although I've tried to remove it all and it's kernel
modules, I guess this could be a problem.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: nftables 0.4-7
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Oct 7 15:21:36 2015
InstallationDate: Installed on 2015-09-03 (33 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
SourcePackage: nftables
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503695/+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 1699772]
*** Bug 122062 has been marked as a duplicate of this bug. *** -- 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/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Incomplete Status in linux package in Debian: Fix Released Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+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 1699772]
xubuntu 18.04.1 32-bit (4.15.0-42-generic #45-Ubuntu) My experience was rather different. LibreOffice would always crash at a point about 35% through the splash screen, so I couldn't use the UI to disable the use of Java. I checked with sysctl -a and also by dumping all strings in the kernel, and "stack_guard_gap" isn't a valid kernel parameter. If I edited the LibreOffice config file "javasettings_Linux_x86.xml" to look like this: http://openoffice.org/2004/java/framework/1.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> LibreOffice 6.0.6.2 00m0(Build:2) would find the java virtual machine, update the config file, and then crash as before. The (partial) solution was to rename /usr/bin/java and /usr/lib/jvm/ AND code the javasettings file as above. With these steps taken I can at least edit documents in --writer and spreadsheets with --calc. Creating a native database requires Java, so that doesn't work, but I was able to attach to a spreadsheet and treat it like a database. Not sure about Access/Jet or SqLite databases yet. Of course, anything else that requires Java is now broken. Java version is OpenJDK Runtime Environment (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.4) OpenJDK Server VM (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.4, mixed mode) I tried creating a "Hello World" Java program and it worked as expected. Hmmm... "Mixed Mode?" Also, this version of was intended for Ubuntu 18.04.**4**, whereas I have 18.04.**1**. -- 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/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Incomplete Status in linux package in Debian: Fix Released Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the probl
[Kernel-packages] [Bug 1805433] Re: Call trace in dmesg (need to specify later what this is)
Ok i have the new kernel loaded now. The new dmesg output still has 9 call traces in it. ** Attachment added: "dmesg_patch1.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805433/+attachment/5222693/+files/dmesg_patch1.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/1805433 Title: Call trace in dmesg (need to specify later what this is) Status in linux package in Ubuntu: Confirmed Bug description: Hello, I get a few call traces in my dmesg log which seems to indicate some problem. I'm trying to get my hardware better compatible with Ubuntu 18.10 therefor i report this bug. Actually i have no idea what this is about so i'll be happy to provide more information on request. There are actually a few call traces so i will upload the entire output from dmesg together with information on my system. Possibly the issues should be separated into several bug reports. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: philippe 4375 F pulseaudio /dev/snd/controlC0: philippe 4375 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-05-14 (198 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=5ef6da7b-eb86-45bd-ad30-df7141164c79 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-16 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: AB350 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd07/23/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805433/+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 1787775] Re: touchpad not working on lenovo yoga 530
As I said, I can't boot without recovery mode. ** Attachment added: "dmesg with modified kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+attachment/5222694/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1799064] Re: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward)
Apologies for the belated response. Unfortunately that does not seem to work around the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1799064 Title: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from bionic to cosmic, Bluetooth has stopped working. It has worked fine for several versions before. Error message from syslog is: Failed to set mode: Failed (0x03) Which according to various random forum posts seems to suggest the device is not powering on. Powering on manually also does not work: % bluetoothctl Agent registered [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed And results in the same set mode failure getting logged again in syslog. hciconfig reports the device as down: % sudo hciconfig hci0: Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:101 acl:0 sco:0 commands:24 errors:0 And, again, it refuses to power on: % sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) rfkill does not appear to be blocking it: % rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no And systemd-rfkill.service is masked: ~ % sudo systemctl status systemd-rfkill.service ● systemd-rfkill.service Loaded: masked (Reason: Unit systemd-rfkill.service is masked.) [..] The system does not have tlp installed. I have tried numerous reboots, power offs, and moving the USB Bluetooth adapter to different ports, with no change in result. I have also tried unloading and loading btusb. The adapter is a cheap noname thing off of eBay, I trust the system report will provide every possibly interesting detail about it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sun Oct 21 17:22:28 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer INC. EB1501P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet username=autostart,nodiskmount loglevel=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EB1501P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Eee Family dmi.product.name: EB1501P dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:95 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1799064/+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 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10
I think I just found a solution! I just saw the following bug report over at Redhat (https://bugzilla.redhat.com/show_bug.cgi?id=1597481) and this kernel.org report (https://bugzilla.kernel.org/show_bug.cgi?id=200455). The bug seems to be related to recent changes in the module related to the Intel Management Engine: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=257355a44b9929e55d6fd47bfff66971dc4de948 I can confirm that blacklisting the mei_me module seems to resolve the issue for my part! ** Bug watch added: Red Hat Bugzilla #1597481 https://bugzilla.redhat.com/show_bug.cgi?id=1597481 ** Bug watch added: Linux Kernel Bug Tracker #200455 https://bugzilla.kernel.org/show_bug.cgi?id=200455 -- 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/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to kubuntu 18.04 resuming from suspend fails in most cases on my laptop. When trying to resume the power LED is turned on, but the screen stays black and the system does not respond at all. Switching to another virtual terminal is not possible and closing the lid again does not show any effect. The hardware is a Dell Latitude e7440 with core i7 4600U and intel graphics only. The only way to change the status is a hard shut-down by long pressing the power button. The last message in kern.log is: PM: suspend entry (deep) The described problem is similar to bug #1774950. However, the latter is considered to be fixed with kernel 4.15.0-38 while my problem persists with this kernel. Output of 'sudo lspci -vnvn' is attached, the result of 'cat /proc/version_signature' is: Ubuntu 4.15.0-38.41-generic 4.15.18 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: graeser2116 F pulseaudio /dev/snd/controlC0: graeser2116 F pulseaudio CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=none InstallationDate: Installed on 2014-03-20 (1690 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Latitude E7440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+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 1787775] Re: touchpad not working on lenovo yoga 530
@hookedbehemoth: Not 100% sure but it looks like you booted the old kernel (where the driver was builtin) with the new modules. [3.303452] Modules linked in: hid_sensor_custom(E) hid_sensor_hub(E) wacom(E+) chash(E) i2c_algo_bit(E) ttm(E) drm_kms_helper(E) syscopyarea(E) hid_roccat_savu(E) sysfillrect(E) hid_roccat(E) hid_roccat_common(E) sysimgblt(E) fb_sys_fops(E) nvme(E) usbhid(E) drm(E) nvme_core(E) wmi(E) i2c_hid(E) video(E) hid(E) [3.321326] Call Trace: [3.322515] amd_mp2_pci_work+0xa1/0x110 amd_mp2_pci_work doesn't exist anymore in the latest versions of the driver, and i2c_amd_mp2 isn't listed in the list of modules linked in. But the module containing the newer driver doesn't get loaded either because of symbols missing in kernels older than 4.19: [6.263647] i2c_amd_mp2: Unknown symbol i2c_get_dma_safe_msg_buf (err 0) [6.292760] i2c_amd_mp2: Unknown symbol i2c_put_dma_safe_msg_buf (err 0) I'm surprised that it worked at all for Kai and Stephan. The patch needs a few changes in order to be applied to older kernels, I forgot to mention it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1787775] Re: touchpad not working on lenovo yoga 530
I tried installing the kernel with a fresh install of ubuntu-16.04.4 because it was the only version with a kernel lower then 4.15xx that I had on my system. I tried installing over the ubuntu GUI but that was very strange. As I wrote it will not boot at all. If I boot recovery It will work and that's where the dmesg comes from. -- 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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1787775] Re: touchpad not working on lenovo yoga 530
That's strange then, maybe the old driver is still builtin in https://people.canonical.com/~khfeng/lp1787775/. Kai is waiting for the driver to be accepted by Linux's maintainers before applying it to Ubuntu's kernel. If you want to get the touchpad working beforehand on your Yoga 530-14ARR, I suggest installing Ubuntu 18.04, this kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.9/ Then the i2c-amd-mp2 driver in DKMS version with the following commands: sudo apt install build-essential dkms git clone https://github.com/Syniurge/i2c-amd-mp2.git cd i2c-amd-mp2 sudo ./dkms-install.sh Reboot and the touchpad and touchscreen should work. -- 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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1787775] Re: touchpad not working on lenovo yoga 530
> Kai is waiting for the driver to be accepted by Linux's maintainers before applying it to Ubuntu's kernel. (I meant the new driver, which works with the Yoga 530. And it should be soon, the maintainer is waiting for someone from AMD to acknowledge or review the submitted patch.) -- 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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1784152] Re: i2c_hid_get_input floods system logs
Same bug on an Acer Aspire ES 15. I found a solution by changing the touchpad BIOS value from "advanced" to "standard". -- 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/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+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 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04
I have installed the kernel and rebooted the server 3 times. All reboots were as fast as the previous ubuntu 16.04. So I think your fix has solved the problem. Thanks a lot. I did get a warning during the update of the initramfs though W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast But it may be that this has been already there before and I just didn't see it. The whole issue leaves 2 open question to me: 1. Has there been a change in the VESA/AST mechanism from 16.04 to 18.04 ? 2. Or is there another explanation for the different behavior after the upgrade to 18.04? -- 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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+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 1714178]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/45. -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
** Changed in: xorg-server Status: Confirmed => Unknown -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1787775] Re: touchpad not working on lenovo yoga 530
Thanks a lot. Works like a charm. -- 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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1806343] Re: FN+F3/F4 does not modify keyboard backlight brightness.
Finally figured out to load module: asus_nb_wmi Keyboard and screen back light all respond now. -- 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/1806343 Title: FN+F3/F4 does not modify keyboard backlight brightness. Status in linux package in Ubuntu: Confirmed Bug description: acpi_listen does not output anything to terminal when pressing key combination. Keyboard backlight has worked on older versions (I believe 18.04 or earlier.) I can manually toggle with: echo 0 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness echo 1 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness echo 2 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness echo 3 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness for varying degrees of brightness. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: disco Uname: Linux 4.19.6-041906-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I performed a full 18.10 install and my A315-41 with Ryzen 3 2200U performed flawlessly. Everything works out of the box, except for graphical performance. Everything I am doing on the desktop has a little lag and it seems to me that CPU load is rising quickly already with simple tasks on the desktop. Is it possible that there is software rendering taking place? How would I find out? According to glxinfo, direct rendering is in effect. Would it be the right action to install AMDGPU Pro driver? Or is there any other chance to make this piece of hardware sprint away? -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
disable amd DC with kernel parameter amdgpu.dc=0 -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
on my polaris desktop i had low 2d performance and screen flickering the above parameter solved it,amdgpu dc is still under heavy development. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805849] Re: apt repository in proposed packages availability issue
** Changed in: linux-azure (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu)
Status: Triaged => 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/1805849
Title:
apt repository in proposed packages availability issue
Status in linux package in Ubuntu:
Invalid
Status in linux-azure package in Ubuntu:
Invalid
Bug description:
We have a watcher that does the following:
- verifies if any linux-azure kernels have been published in proposed repo.
- if it detects one, it will install.
The problem we have is that even though we detect a new kernel in proposed,
the installation of it will fail as there are unmet package dependencies not
being available.
This does resolve after several hours, but the way it works is not reliable
that we see the main package being available, but the packages in the repo are
not ready yet.
So it seems to be a timing issue from the time the kernel is released, and
the time the packages actual get on the repo.
Can you please suggest on some methods to better handle the detect &
install for these, or some suggestions to how we do this from below.
How we search for new kernel availability from proposed:
#apt-cache madison linux-azure | grep ${release}-proposed
But doing an install right after that will fail most of the times if the
kernel was just published:
#apt clean all
#apt -y update
#apt install linux-azure/$release
^ this is after we add the proposed repo in sources.list.
Actual error in the end:
linux-azure : Depends: linux-image-azure (= 4.15.0.1034.34) but 4.15.0.1030.30
E: Unable to correct problems, you have held broken packages.
This is observed on all LTS versions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805849/+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 1117804] Re: ausearch doesn't show AppArmor denial messages
Meta: I've re-read the discussion from December 2017. If there were messages later than this on the thread, I missed them due to suboptimal mailing list archive presentation. Sorry if this leads me to wrong conclusions! I lack the skills to do the actual work I think should be done. The only way I can help here is by facilitating the conversation, so I'll do that: I'd like to make sure there's no misunderstanding about the various opinions that were expressed, the current state of the discussion, and what the next steps should be (e.g. who's waiting for whom). My understanding is that [my personal opinion in square brackets]: 0. Upstream acknowledges that there is a problem and that it would be nice to solve it. 1. There's indeed desire upstream for finding a good balance between sharing (via generic infrastructure and possibly message types) and taking into account that each LSM has different needs. [This makes sense to me: there are probably bits worth sharing instead of every LSM doing their own thing 100% in their dark corner. Now, obviously finding a good balance requires discussion between LSMs to identify what can be shared and what is specific to each, which has its costs (and may require different skills than writing kernel code).] 2. There's a consensus about the fact we need _some_ way to tell which LSM has sent the message. Several options have been mentioned, including adding a new lsm= identifier and using different allocated blocks (be it in the 1400 range or elsewhere). [I'm glad that the door remains open for the option we had in mind initially.] 3. The ball is in our court: upstream proposed several options and I don't see them reach actionable conclusions without our input. At this point, it seems that the next step is: AppArmor developers express their needs. For example: * Are there existing messages formats supported by the auditd suite that would work for us and we'd be happy to share with other LSMs? If yes, great: if we start using them our users will benefit from it without having to adapt existing tools. * What are our needs that we think are specific to AppArmor? (It might be that once we state them, another LSM developer will say "actually, this could be useful for us too", who knows :) * Once we have the answers to the above questions, we can start checking many AppArmor-specific identifiers we need today and how many extra spare ones we want allocated. (Without this info, nobody can decide whether we can fit in the 1400 range.) John, are we on the same page? If not, I'd love to know what we understood differently :) -- 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/1117804 Title: ausearch doesn't show AppArmor denial messages Status in AppArmor: Confirmed Status in audit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: The following command should display all AVC denials: ausearch -m avc However, it doesn't work with AppArmor denials. Here's a quick test case to generate a denial, search for it with ausearch, and see that no messages are displayed: $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current cat: /proc/self/attr/current: Permission denied $ sudo ausearch -m avc -c cat ausearch claims that there are no matches, but there's a matching audit message if you look in audit.log: type=AVC msg=audit(1360193426.539:64): apparmor="DENIED" operation="open" parent=8253 profile="/usr/sbin/tcpdump" name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1117804/+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 1807513] Re: problem loading UEFI certificate
** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807513/+attachment/5220407/+files/PulseList.txt ** Description changed: dmesg reports the following warnings: [1.466047] Problem loading UEFI:db X.509 certificate (-65) [1.466051] Problem loading UEFI:db X.509 certificate (-65) Ubuntu 18.10 (64bit) linux-image-4.18.0-12-generic --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND - /dev/snd/controlC1: wouterd4213 F pulseaudio - /dev/snd/controlC0: wouterd4213 F pulseaudio + /dev/snd/controlC1: whoop4213 F pulseaudio + /dev/snd/controlC0: whoop4213 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-01 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Aspire A515-41G Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=UUID=a16675f6-b0e4-4e39-875e-b5edf3661e9e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/27/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Wartortle_BS dmi.board.vendor: BR dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/27/2017:svnAcer:pnAspireA515-41G:pvrV1.06:rvnBR:rnWartortle_BS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-41G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer -- 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/1807513 Title: problem loading UEFI certificate Status in linux package in Ubuntu: Confirmed Bug description: dmesg reports the following warnings: [1.466047] Problem loading UEFI:db X.509 certificate (-65) [1.466051] Problem loading UEFI:db X.509 certificate (-65) Ubuntu 18.10 (64bit) linux-image-4.18.0-12-generic --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: whoop4213 F pulseaudio /dev/snd/controlC0: whoop4213 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-01 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Aspire A515-41G Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=UUID=a16675f6-b0e4-4e39-875e-b5edf3661e9e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/27/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Wartortle_BS dmi.board.vendor: BR dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/27/2017:svnAcer:pnAspireA515-41G:pvrV1.06:rvnBR:rnWartortle_BS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-41G dmi.product.sku: 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/1807513/+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 1807511] Re: AMDGPU Radeon RX540 system freezes poor performance with ac adapter plugged in
https://bugs.freedesktop.org/show_bug.cgi?id=109073 ** Bug watch added: freedesktop.org Bugzilla #109073 https://bugs.freedesktop.org/show_bug.cgi?id=109073 ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807511/+attachment/5220610/+files/PulseList.txt ** Description changed: Various temporary UI freezes when booting Ubuntu 18.10. dmesg reports various amdgpu warnings and errors. Some examples (please read dmesg attachment for complete overview): [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched [drm:dc_create [amdgpu]] *ERROR* DC: Number of connectors is zero! t is 0 [drm:amdgpu_uvd_ring_test_ib [amdgpu]] *ERROR* amdgpu: (0)IB test timed out. [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed testing IB on ring 12 (-110). [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring test failed (-110). [powerplay] [drm:uvd_v6_0_enc_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 13 test failed [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=1853, last emitted seq=1853 [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, last signaled seq=3110, last emitted seq=3110 [drm] No hardware hang detected. Did some blocks stall? [drm] No hardware hang detected. Did some blocks stall? [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, last signaled seq=2249, last emitted seq=2249 amdgpu: [powerplay] failed to send message 261 ret is 0 amdgpu :03:00.0: GPU pci config reset Ubuntu 18.10 (64 bit) 4.18.0-12-generic --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND - /dev/snd/controlC1: wouterd2696 F pulseaudio - /dev/snd/controlC0: wouterd2696 F pulseaudio + /dev/snd/controlC1: whoop2696 F pulseaudio + /dev/snd/controlC0: whoop2696 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-01 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Aspire A515-41G Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=UUID=a16675f6-b0e4-4e39-875e-b5edf3661e9e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/27/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Wartortle_BS dmi.board.vendor: BR dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/27/2017:svnAcer:pnAspireA515-41G:pvrV1.06:rvnBR:rnWartortle_BS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-41G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer -- 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/1807511 Title: AMDGPU Radeon RX540 system freezes poor performance with ac adapter plugged in Status in linux package in Ubuntu: Confirmed Bug description: Various temporary UI freezes when booting Ubuntu 18.10. dmesg reports various amdgpu warnings and errors. Some examples (please read dmesg attachment for complete overview): [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched [drm:dc_create [amdgpu]] *ERROR* DC: Number of connectors is zero! t is 0 [drm:amdgpu_uvd_ring_test_ib [amdgpu]] *ERROR* amdgpu: (0)IB test timed out. [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed testing IB on ring 12 (-110). [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring test failed (-110). [powerplay] [drm:uvd_v6_0_enc_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 13 test failed [drm:amdgpu_device_ip_resume_phas
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
This bug was fixed in the package alsa-lib - 1.1.7-2ubuntu0.1 --- alsa-lib (1.1.7-2ubuntu0.1) disco; urgency=medium * Cherry picked 0009-conf-ucm-Dell-WD15-Dock-Fix-incorrect-device-names.patch * Cherry picked 0010-conf-USB-Audio-Add-Dell-WD19-Dock-in-the-IEC958-blac.patch * (LP: #1806532) -- Hui Wang Tue, 11 Dec 2018 11:20:38 + ** Changed in: alsa-lib (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1574196] Re: Card with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz networks with high channel number.
same here, GNU/Gentoo Linux with broadcom-sta driver package. 5 Ghz band works only if a lower channel is configured on the AP. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1574196 Title: Card with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz networks with high channel number. Status in bcmwl package in Ubuntu: Confirmed Bug description: The card Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) doesn't see 5Ghz networks with an high channel number, if you change the channel back to a lower one the network will be found again. In my case with channel 104 the network wasn't seen by the card, with channel 40 it works fine wireless-info script result: ## wireless info START ## Report from: 22 Apr 2016 19:23 CEST +0200 Booted last: 22 Apr 2016 18:51 CEST +0200 Script from: 27 Sep 2015 00:34 UTC + # release ### Distributor ID: Ubuntu Description: Ubuntu 14.04.4 LTS Release: 14.04 Codename: trusty # kernel Linux 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Parameters: ro, quiet, splash, vt.handoff=7 # desktop ### Ubuntu # lspci # 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7758] Kernel driver in use: r8169 04:00.0 Network controller [0280]: Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) Subsystem: Broadcom Corporation Device [14e4:0619] Kernel driver in use: wl # lsusb # Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 004: ID 1532:0016 Razer USA, Ltd DeathAdder Mouse Bus 001 Device 003: ID 258a:0001 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # PCMCIA card info ## # rfkill 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no # lsmod # wl 6367819 0 mxm_wmi13021 1 nouveau wmi19177 2 mxm_wmi,nouveau cfg80211 496328 1 wl # interfaces auto lo iface lo inet loopback # ifconfig ## eth0 Link encap:Ethernet HWaddr UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) virbr0Link encap:Ethernet HWaddr inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan2 Link encap:Ethernet HWaddr inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:45040 errors:0 dropped:0 overruns:0 frame:7469 TX packets:33232 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:33581962 (33.5 MB) TX bytes:6334838 (6.3 MB) Interrupt:18 # iwconfig ## eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. wlan2 IEEE 802.11abg ESSID:"LamerTexWiFi" Mode:Managed Frequency:2.437 GHz Access Point: Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off # route # Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 00 wlan2 192.168.1.0 0.0.0.0 255.255.255.0 U 9 0
[Kernel-packages] [Bug 1805248] Re: Regression: hinic performance degrades over time
Testing shows performance inline with the 4.18.0-11-generic kernel. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1805248 Title: Regression: hinic performance degrades over time Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] Bug 1800664 introduced checksum offload and TSO support for HiNIC adapters. While that did improve performance in short iperf runs, longer runs were later found to show a significant regression in performance: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800664/comments/3 [Test Case] iperf -c 192.168.99.1 -P5 [Fix] Revert the offending patch. [Regression Risk] This is reverting a patch, returning the driver to 18.10 GA behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805248/+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 1799064] Re: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward)
** No longer affects: bluez (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1799064 Title: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from bionic to cosmic, Bluetooth has stopped working. It has worked fine for several versions before. Error message from syslog is: Failed to set mode: Failed (0x03) Which according to various random forum posts seems to suggest the device is not powering on. Powering on manually also does not work: % bluetoothctl Agent registered [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed And results in the same set mode failure getting logged again in syslog. hciconfig reports the device as down: % sudo hciconfig hci0: Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:101 acl:0 sco:0 commands:24 errors:0 And, again, it refuses to power on: % sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) rfkill does not appear to be blocking it: % rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no And systemd-rfkill.service is masked: ~ % sudo systemctl status systemd-rfkill.service ● systemd-rfkill.service Loaded: masked (Reason: Unit systemd-rfkill.service is masked.) [..] The system does not have tlp installed. I have tried numerous reboots, power offs, and moving the USB Bluetooth adapter to different ports, with no change in result. I have also tried unloading and loading btusb. The adapter is a cheap noname thing off of eBay, I trust the system report will provide every possibly interesting detail about it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sun Oct 21 17:22:28 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer INC. EB1501P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet username=autostart,nodiskmount loglevel=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EB1501P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Eee Family dmi.product.name: EB1501P dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:95 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799064/+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 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04
> Has there been a change in the VESA/AST mechanism from 16.04 to 18.04 ? I think the answer is "yes" there must have been a kernel change that caused the regression. It's not yet clear where the regression occurred between 16.04 and 18.04 (there's at least two years work between them) but at least we seem to have a fix for it. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- 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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Triaged Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+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 1808625] [NEW] Lenovo Ideapad 330 touchpad isn't being recognised by Ubuntu. To work I have to use an external one.
You have been subscribed to a public bug: My laptop is Lenovo Ideapad 330. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.29 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Dec 15 17:13:44 2018 InstallationDate: Installed on 2018-12-11 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- Lenovo Ideapad 330 touchpad isn't being recognised by Ubuntu. To work I have to use an external one. https://bugs.launchpad.net/bugs/1808625 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 1808193] Re: Battery percentage changes suddenly depending on whether AC is plugged in
** 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/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in upower package in Ubuntu: New Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: upower PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808193/+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 1808635] [NEW] [nouveau] [Quadro FX 3800] no boot just red square on screen
You have been subscribed to a public bug: no boot just red squar on screan ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Sat Dec 15 10:16:34 2018 DistUpgraded: 2018-08-28 08:03:16,046 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GT200GL [Quadro FX 3800] [10de:05ff] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GT200GL [Quadro FX 3800] [10de:0661] InstallationDate: Installed on 2016-09-30 (806 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Z400 Workstation ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=2aeb5d71-8879-4ee6-8084-763dda365c5a ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-28 (109 days ago) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G3 v03.57 dmi.board.asset.tag: 2UA935021D dmi.board.name: 0AE4h dmi.board.vendor: Hewlett-Packard dmi.board.version: C dmi.chassis.asset.tag: 2UA935021D dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G3v03.57:bd07/15/2013:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0AE4h:rvrC:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z400 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Aug 28 22:26:33 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic nouveau ubuntu -- [nouveau] [Quadro FX 3800] no boot just red square on screen https://bugs.launchpad.net/bugs/1808635 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 1808625] Re: Lenovo Ideapad 330 touchpad isn't being recognised by Ubuntu. To work I have to use an external one.
** Summary changed: - Mouse pad of laptop isn't being recognised by Ubuntu. To work I have to use an external one. + Lenovo Ideapad 330 touchpad isn't being recognised by Ubuntu. To work I have to use an external one. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Lenovo Ideapad 330 touchpad isn't being recognised by Ubuntu. To work I have to use an external one. + Lenovo Ideapad 330 touchpad isn't being recognised by Ubuntu. To work I have to use an external mouse. -- 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/1808625 Title: Lenovo Ideapad 330 touchpad isn't being recognised by Ubuntu. To work I have to use an external mouse. Status in linux package in Ubuntu: Incomplete Bug description: My laptop is Lenovo Ideapad 330. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.29 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Dec 15 17:13:44 2018 InstallationDate: Installed on 2018-12-11 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808625/+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 1808625] 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 1808625 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/1808625 Title: Lenovo Ideapad 330 touchpad isn't being recognised by Ubuntu. To work I have to use an external mouse. Status in linux package in Ubuntu: Incomplete Bug description: My laptop is Lenovo Ideapad 330. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.29 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Dec 15 17:13:44 2018 InstallationDate: Installed on 2018-12-11 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808625/+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 1808729] [NEW] MAC address pass through on RTL8153-BND for docking station
Public bug reported: [Impact] A new chip RTL8153-BND on docks require to be added to the whitelist to support MAC address pass through. [Fix] This commit adds check for RTL8153-BND chip. https://lkml.org/lkml/2018/12/11/500 [Regression Potential] Low. It doesn't change the code flow for the old RTL8153-AD chip, so it won't lead to regression. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Tags: originate-from-1806322 somerville ** Tags added: originate-from-1806322 somerville -- 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/1808729 Title: MAC address pass through on RTL8153-BND for docking station Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: [Impact] A new chip RTL8153-BND on docks require to be added to the whitelist to support MAC address pass through. [Fix] This commit adds check for RTL8153-BND chip. https://lkml.org/lkml/2018/12/11/500 [Regression Potential] Low. It doesn't change the code flow for the old RTL8153-AD chip, so it won't lead to regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1808729/+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 1808635] Re: [nouveau] no boot just red square on screen
Can you please take a photo of the screen when the red square is displayed? ** Summary changed: - revert to older software + [nouveau] no boot just red square on screen ** Tags added: nouveau ** Summary changed: - [nouveau] no boot just red square on screen + [nouveau] [Quadro FX 3800] no boot just red square on screen ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** 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/1808635 Title: [nouveau] [Quadro FX 3800] no boot just red square on screen Status in linux package in Ubuntu: Incomplete Bug description: no boot just red squar on screan ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Sat Dec 15 10:16:34 2018 DistUpgraded: 2018-08-28 08:03:16,046 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GT200GL [Quadro FX 3800] [10de:05ff] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GT200GL [Quadro FX 3800] [10de:0661] InstallationDate: Installed on 2016-09-30 (806 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Z400 Workstation ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=2aeb5d71-8879-4ee6-8084-763dda365c5a ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-28 (109 days ago) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G3 v03.57 dmi.board.asset.tag: 2UA935021D dmi.board.name: 0AE4h dmi.board.vendor: Hewlett-Packard dmi.board.version: C dmi.chassis.asset.tag: 2UA935021D dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G3v03.57:bd07/15/2013:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0AE4h:rvrC:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z400 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Aug 28 22:26:33 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808635/+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 1808736] [NEW] Saving crash report failed
Public bug reported: In response to a error window stating that there is a problem with Caja (other than the memory leak that eats up move than 8GB of RAM). I clicked report to developers. See additional screen shot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2807 F pulseaudio /dev/snd/controlC0: robert 2807 F pulseaudio CurrentDesktop: MATE Date: Sun Dec 16 22:06:41 2018 InstallationDate: Installed on 2018-12-16 (0 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A 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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "Screenshot at 2018-12-16 22-01-51.png" https://bugs.launchpad.net/bugs/1808736/+attachment/5222800/+files/Screenshot%20at%202018-12-16%2022-01-51.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808736 Title: Saving crash report failed Status in linux package in Ubuntu: New Bug description: In response to a error window stating that there is a problem with Caja (other than the memory leak that eats up move than 8GB of RAM). I clicked report to developers. See additional screen shot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2807 F pulseaudio /dev/snd/controlC0: robert 2807 F pulseaudio CurrentDesktop: MATE Date: Sun Dec 16 22:06:41 2018 InstallationDate: Installed on 2018-12-16 (0 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A 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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1808736/+subscriptions -
[Kernel-packages] [Bug 1808609] Re: None of my external drives appear after Linux crash.
Tracked down problem. Hardware problem with power going to external drives. Fixed power problem and (some) drives mount. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1808609 Title: None of my external drives appear after Linux crash. Status in linux package in Ubuntu: Fix Committed Bug description: First my system became incredibly slow (consistent with the memory leak in Caja). I xKill Caja and then tried to restart it. I then closed every app and tried to do a shutdown. I got a warning that Caja still had processes running preventing shutdown. I chose shut down anyway. I eventually got the progress screen showing that Linux was trying to shut down. After 1 1/2 hours of the progress screen, I manually turned off power. I was able to reboot but all of my external drives are missing. I tried turning off and then back on one drive with no result. When I plug a drive back in I do not feel the vibration caused by the drive spinning up. Nor do I feel the drive do the initial seek. This indicated that Linux is not even attempting to access the drives. Do I have to reinstall Ubuntu MATE 18.10 (again) in order to use external USB drives? The attached screen shots shows only partitions on my two internal hard drives. Gparted does not show the disks. Disks from the Control Center shows only internal devices. Without access to my external drives I am stalled. I can't even do backups. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2606 F pulseaudio /dev/snd/controlC0: robert 2606 F pulseaudio CurrentDesktop: MATE Date: Fri Dec 14 22:38:44 2018 InstallationDate: Installed on 2018-11-30 (14 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A 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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1808609/+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 1808736] 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/1808736 Title: Saving crash report failed Status in linux package in Ubuntu: Confirmed Bug description: In response to a error window stating that there is a problem with Caja (other than the memory leak that eats up move than 8GB of RAM). I clicked report to developers. See additional screen shot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2807 F pulseaudio /dev/snd/controlC0: robert 2807 F pulseaudio CurrentDesktop: MATE Date: Sun Dec 16 22:06:41 2018 InstallationDate: Installed on 2018-12-16 (0 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A 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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1808736/+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 1752437]
Hi all, I have been following this bug and patch for a while for my bq-100, it's exhilarating to know that you guys solved the touch/flip issue and I can go back as running my laptop vm host on linux again. I've been refreshing this daily to see when the RESOLVED changes into VERIFIED so I can DL a stable kernel, but I think it doesn't work this way. Therefore, can someone please point to how do I get Hans de Goede's patch into an ubuntu 18.10 install? Is it the patch command, or ukuu, or a clean compile of the kernel (and if so, any howto for ubuntu for required extras?). I usually don't poke into my daily driver computer if it's not required, but this Windows as host OS was supposed to only be till October, it unbalances my zen :-) So, wait till official patched Kernel (any time estimate)? Or patch the kernel? Cheers all. -- 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the following patch with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git2
[Kernel-packages] [Bug 1752437]
(In reply to m.kolesinski from comment #104) > (In reply to Robert Munn from comment #103) > > I can confirm the patch is included in 4.19.7 as well. > > AFAIK, patches aren't normally part of a kernel release...those are up to > your distro. > Right, let me be more specific. I'm on Ubuntu 18.10, I downloaded the latest kernel debs from: https://kernel.ubuntu.com/~kernel-ppa/mainline/ which at the time was 4.19.7. These are not the official kernels in the Ubuntu repo, but they are builds from the Ubuntu team. You have to download and install them yourself. I did that with 4.19.7. I was not expecting the patch to be included, but a couple of days later I touched the screen to wipe off a speck of dust and the page scrolled. Still takes some work and I would not recommend it to a novice, but it's quite a bit easier (and far less time consuming) than compiling from source. -- 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the following patch with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel:
[Kernel-packages] [Bug 1752437]
(In reply to Eran Benjamin from comment #101) > Hi all, > > I have been following this bug and patch for a while for my bq-100, it's > exhilarating to know that you guys solved the touch/flip issue and I can go > back as running my laptop vm host on linux again. > > I've been refreshing this daily to see when the RESOLVED changes into > VERIFIED so I can DL a stable kernel, but I think it doesn't work this way. > > Therefore, can someone please point to how do I get Hans de Goede's patch > into an ubuntu 18.10 install? > Is it the patch command, or ukuu, or a clean compile of the kernel (and if > so, any howto for ubuntu for required extras?). > > I usually don't poke into my daily driver computer if it's not required, but > this Windows as host OS was supposed to only be till October, it unbalances > my zen :-) > > So, wait till official patched Kernel (any time estimate)? > Or patch the kernel? > > Cheers all. As far as I can tell, the patch is already included since the 4.19.8 -- 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the following patch with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-inp
[Kernel-packages] [Bug 1752437]
(In reply to Robert Munn from comment #103) > I can confirm the patch is included in 4.19.7 as well. AFAIK, patches aren't normally part of a kernel release...those are up to your distro. So, it sounds like some distros are including this in their patchsets they apply, but I see no mention of this issue in any of the changelogs yet for mainline kernel releases. This is one aspect of this bug tracking system I find frustrating...I don't see a link from the bug pointing to the release it is fixed in, and vice versa. The bug tracking and release systems are not tied together as best I can tell. In order to patch my distro, I had to recompile from source, and hand- create a patch using the edits in the last attachment in this thread. My biggest hassle was the fact that I have a slow and flaky internet connection, and git is just a pile o' crap when it comes to dealing with that (no download resume support...). I opted to download the source manually, then hack the MAKEPKG for Arch to skip the whole process. I could have just directly hand-edited the source at that point, but still opted to just create a patch file, and edited MAKEPKG to pull in my custom file. You then have to add it to your boot loader, etc., just like any other kernel build. -- 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the following patch with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2
[Kernel-packages] [Bug 1752437]
(In reply to Seth Shelnutt from comment #106) > I've just updated to 4.19.9, verified the patch was included, and I'm now > getting: > > cmi: probe of SMB0001:00 failed with error -5 That error can be safely ignored, the CMI device is not used on your laptop, 4.20 will have a patch silencing this error. -- 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the following patch with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1752437/+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 1752437]
I've just updated to 4.19.9, verified the patch was included, and I'm now getting: cmi: probe of SMB0001:00 failed with error -5 I'm running the latest bios, F.31 Rev.A for my hp envy x360 15z. Has anyone else encountered this? I'm wondering if I'm missing some kernel config setting or if this latest bios has changed the ACPI table? -- 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the following patch with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1752437/+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 1752437]
I can confirm the patch is included in 4.19.7 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the following patch with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1752437/+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 1808743] [NEW] [Ubuntu 1810] Kdump fails to dump vmcore and enters initramfs inside Power9 KVM guest
You have been subscribed to a public bug: Kdump fails to dump vmcore even with workaround suggested This issue is submitted to track on Power9 Guest where it uses file type qcow2 disk (virtio-scsi) Boot Log: (Attached full console log) [3.754031]32regs: 19616.000 MB/sec [3.794031]32regs_prefetch: 17280.000 MB/sec [3.834030]altivec : 22480.000 MB/sec [3.834063] xor: using function: altivec (22480.000 MB/sec) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=5e1fe9e9-cf03-4c73-adce-0e57676f98e0 does not exist. Dropping to a shell! BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Contact Information = Balamuruhan S / balamuruh...@in.ibm.com ---uname output--- Guest Kernel: 4.18.0-11-generic Host Kernel: 4.18.0-11-generic Machine Type = Boston ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Have a healthy KVM guest with Ubuntu 1810 with kernel 4.18.0-11-generic 2. Install kdump, kexec and crash tools in the guest, # dpkg -l | grep crash ii apport2.20.10-0ubuntu13.1 all automatically generate crash reports for debugging ii crash 7.2.3+real-1 ppc64el kernel debugging utility, allowing gdb like syntax ii kdump-tools 1:1.6.4-2ubuntu1 ppc64el scripts and tools for automating kdump (Linux crash dumps) ii linux-crashdump 4.18.0.11.12 ppc64el Linux kernel crashdump setup for the latest generic kernel ii python3-apport2.20.10-0ubuntu13.1 all Python 3 library for Apport crash report handling 3. Ensure workaround suggested in Bug 172389 is followed by uncomment the `KDUMP_CMDLINE_APPEND` and change nr_cpus to maxcpus in /etc/default/kdump-tools config file, # cat /etc/default/kdump-tools | grep -i cmdline # KDUMP_CMDLINE - The default is to use the contents of /proc/cmdline. # Set this variable to override /proc/cmdline. # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line #KDUMP_CMDLINE="" KDUMP_CMDLINE_APPEND="1 maxcpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb reset_devices" 4. restart the kdump tools service, # service kdump-tools restart # service kdump-tools status ? kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres Active: active (exited) since Mon 2018-12-03 02:34:03 CST; 1 weeks 3 days ago Process: 1560 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/S Main PID: 1560 (code=exited, status=0/SUCCESS) Dec 03 02:34:02 ubuntu1810 systemd[1]: Starting Kernel crash dump capture servic Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]: Starting kdump-tools: * Creating Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]: * Creating symlink /var/lib/kdump Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]: Modified cmdline:BOOT_IMAGE=/boot/ Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]: * loaded kdump kernel Dec 03 02:34:03 ubuntu1810 kdump-tools[1678]: /sbin/kexec -p --command-line="BOO Dec 03 02:34:03 ubuntu1810 kdump-tools[1679]: loaded kdump kernel Dec 03 02:34:03 ubuntu1810 systemd[1]: Started Kernel crash dump capture service 5. check kdump-config is state is ready to dump, # kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.18.0-11-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-11-generic current state:ready to kdump 6. Reboot the guest and check for kernel cmdline whether crashkernel is included, # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.18.0-11-generic root=UUID=5e1fe9e9-cf03-4c73-adce-0e57676f98e0 ro net.ifnames=0 biosdevname=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M 7. enable sysrq and trigger the crash, # echo 1 > /proc/sys/kernel/sysrq # cat /proc/sys/kernel/sysrq 1 # echo c > /proc/sysrq-trigger kdump fails to generate vmcore after c
[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Please note this bug is closed, so generally will be ignored by developers. If you have any ongoing problems please consider joining one of these open bugs instead: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bugs?field.tag=nvidia or log a new bug by running the command: ubuntu-bug gdm3 Only if the original reporter would like this bug reopened should it be reopened. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1808743] [NEW] [Ubuntu 1810] Kdump fails to dump vmcore and enters initramfs inside Power9 KVM guest
Public bug reported: Kdump fails to dump vmcore even with workaround suggested This issue is submitted to track on Power9 Guest where it uses file type qcow2 disk (virtio-scsi) Boot Log: (Attached full console log) [3.754031]32regs: 19616.000 MB/sec [3.794031]32regs_prefetch: 17280.000 MB/sec [3.834030]altivec : 22480.000 MB/sec [3.834063] xor: using function: altivec (22480.000 MB/sec) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=5e1fe9e9-cf03-4c73-adce-0e57676f98e0 does not exist. Dropping to a shell! BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Contact Information = Balamuruhan S / balamuruh...@in.ibm.com ---uname output--- Guest Kernel: 4.18.0-11-generic Host Kernel: 4.18.0-11-generic Machine Type = Boston ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Have a healthy KVM guest with Ubuntu 1810 with kernel 4.18.0-11-generic 2. Install kdump, kexec and crash tools in the guest, # dpkg -l | grep crash ii apport2.20.10-0ubuntu13.1 all automatically generate crash reports for debugging ii crash 7.2.3+real-1 ppc64el kernel debugging utility, allowing gdb like syntax ii kdump-tools 1:1.6.4-2ubuntu1 ppc64el scripts and tools for automating kdump (Linux crash dumps) ii linux-crashdump 4.18.0.11.12 ppc64el Linux kernel crashdump setup for the latest generic kernel ii python3-apport2.20.10-0ubuntu13.1 all Python 3 library for Apport crash report handling 3. Ensure workaround suggested in Bug 172389 is followed by uncomment the `KDUMP_CMDLINE_APPEND` and change nr_cpus to maxcpus in /etc/default/kdump-tools config file, # cat /etc/default/kdump-tools | grep -i cmdline # KDUMP_CMDLINE - The default is to use the contents of /proc/cmdline. # Set this variable to override /proc/cmdline. # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line #KDUMP_CMDLINE="" KDUMP_CMDLINE_APPEND="1 maxcpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb reset_devices" 4. restart the kdump tools service, # service kdump-tools restart # service kdump-tools status ? kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres Active: active (exited) since Mon 2018-12-03 02:34:03 CST; 1 weeks 3 days ago Process: 1560 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/S Main PID: 1560 (code=exited, status=0/SUCCESS) Dec 03 02:34:02 ubuntu1810 systemd[1]: Starting Kernel crash dump capture servic Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]: Starting kdump-tools: * Creating Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]: * Creating symlink /var/lib/kdump Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]: Modified cmdline:BOOT_IMAGE=/boot/ Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]: * loaded kdump kernel Dec 03 02:34:03 ubuntu1810 kdump-tools[1678]: /sbin/kexec -p --command-line="BOO Dec 03 02:34:03 ubuntu1810 kdump-tools[1679]: loaded kdump kernel Dec 03 02:34:03 ubuntu1810 systemd[1]: Started Kernel crash dump capture service 5. check kdump-config is state is ready to dump, # kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.18.0-11-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-11-generic current state:ready to kdump 6. Reboot the guest and check for kernel cmdline whether crashkernel is included, # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.18.0-11-generic root=UUID=5e1fe9e9-cf03-4c73-adce-0e57676f98e0 ro net.ifnames=0 biosdevname=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M 7. enable sysrq and trigger the crash, # echo 1 > /proc/sys/kernel/sysrq # cat /proc/sys/kernel/sysrq 1 # echo c > /proc/sysrq-trigger kdump fails to generate vmcore after crash instead reboots
[Kernel-packages] [Bug 1806343] Re: FN+F3/F4 does not modify keyboard backlight brightness.
So asus_nb_wmi isn't automatically loaded on the system? -- 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/1806343 Title: FN+F3/F4 does not modify keyboard backlight brightness. Status in linux package in Ubuntu: Confirmed Bug description: acpi_listen does not output anything to terminal when pressing key combination. Keyboard backlight has worked on older versions (I believe 18.04 or earlier.) I can manually toggle with: echo 0 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness echo 1 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness echo 2 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness echo 3 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness for varying degrees of brightness. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: disco Uname: Linux 4.19.6-041906-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343/+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 1787775] Re: touchpad not working on lenovo yoga 530
[0.00] Linux version 4.15.0-42-generic (buildd@lgw01-amd64-023) This mean the kernel is built by Ubuntu's official builder, so it's expected not to work. -- 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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1808743] Re: [Ubuntu 1810] Kdump fails to dump vmcore and enters initramfs inside Power9 KVM guest
** Package changed: linux (Ubuntu) => makedumpfile (Ubuntu) ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1808743 Title: [Ubuntu 1810] Kdump fails to dump vmcore and enters initramfs inside Power9 KVM guest Status in The Ubuntu-power-systems project: Triaged Status in makedumpfile package in Ubuntu: New Bug description: Kdump fails to dump vmcore even with workaround suggested This issue is submitted to track on Power9 Guest where it uses file type qcow2 disk (virtio-scsi) Boot Log: (Attached full console log) [3.754031]32regs: 19616.000 MB/sec [3.794031]32regs_prefetch: 17280.000 MB/sec [3.834030]altivec : 22480.000 MB/sec [3.834063] xor: using function: altivec (22480.000 MB/sec) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. mdadm: No devices listed in conf file were found. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=5e1fe9e9-cf03-4c73-adce-0e57676f98e0 does not exist. Dropping to a shell! BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Contact Information = Balamuruhan S / balamuruh...@in.ibm.com ---uname output--- Guest Kernel: 4.18.0-11-generic Host Kernel: 4.18.0-11-generic Machine Type = Boston ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Have a healthy KVM guest with Ubuntu 1810 with kernel 4.18.0-11-generic 2. Install kdump, kexec and crash tools in the guest, # dpkg -l | grep crash ii apport2.20.10-0ubuntu13.1 all automatically generate crash reports for debugging ii crash 7.2.3+real-1 ppc64el kernel debugging utility, allowing gdb like syntax ii kdump-tools 1:1.6.4-2ubuntu1 ppc64el scripts and tools for automating kdump (Linux crash dumps) ii linux-crashdump 4.18.0.11.12 ppc64el Linux kernel crashdump setup for the latest generic kernel ii python3-apport2.20.10-0ubuntu13.1 all Python 3 library for Apport crash report handling 3. Ensure workaround suggested in Bug 172389 is followed by uncomment the `KDUMP_CMDLINE_APPEND` and change nr_cpus to maxcpus in /etc/default/kdump-tools config file, # cat /etc/default/kdump-tools | grep -i cmdline # KDUMP_CMDLINE - The default is to use the contents of /proc/cmdline. # Set this variable to override /proc/cmdline. # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line #KDUMP_CMDLINE="" KDUMP_CMDLINE_APPEND="1 maxcpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb reset_devices" 4. restart the kdump tools service, # service kdump-tools restart # service kdump-tools status ? kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres Active: active (exited) since Mon 2018-12-03 02:34:03 CST; 1 weeks 3 days ago Process: 1560 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/S Main PID: 1560 (code=exited, status=0/SUCCESS) Dec 03 02:34:02 ubuntu1810 systemd[1]: Starting Kernel crash dump capture servic Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]: Starting kdump-tools: * Creating Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]: * Creating symlink /var/lib/kdump Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]: Modified cmdline:BOOT_IMAGE=/boot/ Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]: * loaded kdump kernel Dec 03 02:34:03 ubuntu1810 kdump-tools[1678]: /sbin/kexec -p --command-line="BOO Dec 03 02:34:03 ubuntu1810 kdump-tools[1679]: loaded kdump kernel Dec 03 02:34:03 ubuntu1810 systemd[1]: Started Kernel crash dump capture service 5. c
[Kernel-packages] [Bug 1806659] Re: linux: 4.15.0-43.46 -proposed tracker
4.15.0-43.46 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kvm_unit_tests - 29 failed on amaura, 25 failed on pepe, 29 failed on KVM nodes ubuntu_ltp - timed out on timeleap test ubuntu_ltp_syscalls - getrandom02 timed out (bug 1797327) inotify08 (bug 1775784) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) ubuntu_lxc - package from -proposed and from -update casuing apt issue (bug 1805978) xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kvm_smoke_test - Unable to boot Xenial cloud image on Bionic ARM64 ThunderX / Azure (bug 1765668) ubuntu_kvm_unit_tests - gicv3-ipi and gicv3-active failed on Moonshot (bug 1790825) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) ubuntu_lxc - package from -proposed and from -update casuing apt issue (bug 1805978) xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in i386: ubuntu_bpf - Some test in test_verifier failed on i386 Bionic (bug 1788578) ubuntu_kvm_unit_tests - 29 failed on pepe ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) ubuntu_lxc - package from -proposed and from -update casuing apt issue (bug 1805978) ubuntu_qrt_apparmor - mmap timed out on onibi (bug 1783922) manually verified xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in ppc64le (P8): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kvm_smoke_test - test case issue, KVM works fine ubuntu_kvm_unit_tests - sprs timed out (bug 1740017) ubuntu_ltp_syscalls - fallocate05 (bug 1783880) inotify08 (bug 1775784) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) ubuntu_lxc - package from -proposed and from -update casuing apt issue (bug 1805978) xfstests - timed out on ext4 generic/430 test (bug 1755999) 46 / 47 tests were run, missing: xfstests Issue to note in ppc64le (P9): hwclock - hwclock test failed on PowerPC due to 0.x sec difference (bug 1802233) ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kvm_unit_tests - sprs timed out (bug 1740017) ubuntu_ltp_syscalls - fallocate05 (bug 1783880) inotify08 (bug 1775784) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) ubuntu_lxc - package from -proposed and from -update casuing apt issue (bug 1805978) Issue to note in s390x (KVM): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) ubuntu_lxc - Container "reboot" is defined (bug 1788574) Issue to note in s390x (Ubuntu on LPAR): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) ubuntu_lxc - lxc-test-api-reboot failed (bug 1776381) Container "reboot" is defined (bug 1788574) Issue to note in s390x (zVM): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kvm_unit_tests - skey failed (bug 1778705) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) ubuntu_lxc - Container "reboot" is defined (bug 1788574) Note: No xfstests for P9 as it does not have a scratch drive -- 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/1806659 Title: linux: 4.15.0-43.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an expla
[Kernel-packages] [Bug 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04
** Description changed: + ===SRU Justification=== + [Impact] + Server console is extremely slow on ast, after the upgrade from 16.04 to + 18.04. + + [Fix] + Remove firmware/bootloader configured framebuffer device before probing. + + [Test] + User confirmed the patch fixes the issue. + + [Regression Potential] + Low. The fix is in stable tree, limits to one specific device, and other + DRM drivers already do this for a while. + + ===Original Bug Report=== After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) - --- + --- ProblemType: Bug AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Dec 15 07:22 seq - crw-rw 1 root audio 116, 33 Dec 15 07:22 timer + total 0 + crw-rw 1 root audio 116, 1 Dec 15 07:22 seq + crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: - eth0 no wireless extensions. - - eth1 no wireless extensions. - - lono wireless extensions. + eth0 no wireless extensions. + + eth1 no wireless extensions. + + lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: - + ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: - linux-restricted-modules-4.15.0-42-generic N/A - linux-backports-modules-4.15.0-42-generic N/A - linux-firmware 1.173.2 + linux-restricted-modules-4.15.0-42-generic N/A + linux-backports-modules-4.15.0-42-generic N/A + linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: - + _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Triaged Bug description: ===SRU Justification=== [Impact] Server console is extremely slow on ast, after the upgrade from 16.04 to 18.04. [Fix] Remove firmware/bootloader configured framebuffer device before probing. [Test] User confirmed the patch fixes the issue. [Regression Potential] Low. The fix is in stable tree, limits to one specific device, and other DRM drivers already do this for a while. ===Original Bug Report=== After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2
[Kernel-packages] [Bug 1799064] Re: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward)
And apology from my side, it should be "btusb.enable_autosuspend=0" instead. -- 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/1799064 Title: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from bionic to cosmic, Bluetooth has stopped working. It has worked fine for several versions before. Error message from syslog is: Failed to set mode: Failed (0x03) Which according to various random forum posts seems to suggest the device is not powering on. Powering on manually also does not work: % bluetoothctl Agent registered [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed And results in the same set mode failure getting logged again in syslog. hciconfig reports the device as down: % sudo hciconfig hci0: Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:101 acl:0 sco:0 commands:24 errors:0 And, again, it refuses to power on: % sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) rfkill does not appear to be blocking it: % rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no And systemd-rfkill.service is masked: ~ % sudo systemctl status systemd-rfkill.service ● systemd-rfkill.service Loaded: masked (Reason: Unit systemd-rfkill.service is masked.) [..] The system does not have tlp installed. I have tried numerous reboots, power offs, and moving the USB Bluetooth adapter to different ports, with no change in result. I have also tried unloading and loading btusb. The adapter is a cheap noname thing off of eBay, I trust the system report will provide every possibly interesting detail about it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sun Oct 21 17:22:28 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer INC. EB1501P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet username=autostart,nodiskmount loglevel=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EB1501P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Eee Family dmi.product.name: EB1501P dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:95 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799064/+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 1735062] [NEW] Xorg freeze
You have been subscribed to a public bug: The problem is a very short graphics freeze. I believe the issue is related to the i915 driver:;; [ 1103.153702] [ cut here ] [ 1103.153759] WARNING: CPU: 2 PID: 5425 at /build/linux-KM2a5S/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:12848 intel_atomic_commit_tail+0xf7d/0xf90 [i915] [ 1103.153760] Modules linked in: msr rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm bnep binfmt_misc intel_rapl dell_laptop x86_pkg_temp_thermal intel_powerclamp dell_smm_hwmon coretemp kvm_intel uvcvideo kvm videobuf2_vmalloc btusb irqbypass snd_hda_codec_hdmi videobuf2_memops videobuf2_v4l2 snd_hda_codec_conexant btrtl snd_hda_codec_generic videobuf2_core crct10dif_pclmul crc32_pclmul btbcm btintel ghash_clmulni_intel cryptd intel_cstate snd_hda_intel intel_rapl_perf bluetooth videodev snd_hda_codec snd_hda_core media ecdh_generic snd_hwdep dell_wmi dell_smbios arc4 snd_pcm input_leds dcdbas joydev sparse_keymap serio_raw wmi_bmof snd_seq_midi snd_seq_midi_event snd_rawmidi iwldvm mac80211 snd_seq snd_seq_device snd_timer iwlwifi snd cfg80211 lpc_ich soundcore mei_me mei [ 1103.153800] shpchp dell_smo8800 mac_hid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci drm libahci atl1c wmi video [ 1103.153820] CPU: 2 PID: 5425 Comm: kworker/u16:2 Tainted: G OE 4.13.0-17-generic #20-Ubuntu [ 1103.153821] Hardware name: Dell Inc. Dell System Inspiron N411Z/0YWNPW, BIOS A00 06/24/2011 [ 1103.153860] Workqueue: events_unbound intel_atomic_commit_work [i915] [ 1103.153862] task: 90c28720c5c0 task.stack: a496c3ee [ 1103.153898] RIP: 0010:intel_atomic_commit_tail+0xf7d/0xf90 [i915] [ 1103.153899] RSP: 0018:a496c3ee3d88 EFLAGS: 00010282 [ 1103.153900] RAX: 001c RBX: 0001 RCX: [ 1103.153901] RDX: RSI: 90c39fa8dc78 RDI: 90c39fa8dc78 [ 1103.153902] RBP: a496c3ee3e40 R08: 0001 R09: 0323 [ 1103.153903] R10: a496c3ee3d88 R11: R12: fe3e [ 1103.153904] R13: 90c38d06 R14: 90c38e3db000 R15: 0002 [ 1103.153906] FS: () GS:90c39fa8() knlGS: [ 1103.153907] CS: 0010 DS: ES: CR0: 80050033 [ 1103.153908] CR2: 7f2139afa000 CR3: 0001949eb000 CR4: 000406e0 [ 1103.153910] Call Trace: [ 1103.153917] ? wait_woken+0x80/0x80 [ 1103.153955] intel_atomic_commit_work+0x12/0x20 [i915] [ 1103.153960] process_one_work+0x1e7/0x410 [ 1103.153962] worker_thread+0x4a/0x410 [ 1103.153965] kthread+0x125/0x140 [ 1103.153967] ? process_one_work+0x410/0x410 [ 1103.153969] ? kthread_create_on_node+0x70/0x70 [ 1103.153972] ret_from_fork+0x25/0x30 [ 1103.153974] Code: ff ff ff 48 83 c7 08 e8 42 a1 32 e0 4c 8b 85 70 ff ff ff 4d 85 c0 0f 85 7b fa ff ff 8d 73 41 48 c7 c7 60 c4 66 c0 e8 d4 53 34 e0 <0f> ff e9 65 fa ff ff 66 90 66 2e 0f 1f 84 00 00 00 00 00 66 66 [ 1103.154006] ---[ end trace 3e9edf28140fd63f ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 22:09:19 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.10.0-40-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:051b] InstallationDate: Installed on 2016-01-02 (696 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: Dell Inc. Dell System Inspiron N411Z ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=ca80c0e0-465a-47b9-8a50-2ff12698bdfe ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0YWNPW dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chass
[Kernel-packages] [Bug 1808752] [NEW] Regression: Screen orientation does no longer change
Public bug reported: I don't know if I filed the bug against the right package. Since last upgrades the screen orientation of the internal monitor of my Thinkpad X1 Yoga does no longer change even if I turn the laptop around. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-firmware 1.175.1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 08:23:35 2018 Dependencies: InstallationDate: Installed on 2018-11-30 (16 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1808752 Title: Regression: Screen orientation does no longer change Status in gnome-shell package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: I don't know if I filed the bug against the right package. Since last upgrades the screen orientation of the internal monitor of my Thinkpad X1 Yoga does no longer change even if I turn the laptop around. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-firmware 1.175.1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 08:23:35 2018 Dependencies: InstallationDate: Installed on 2018-11-30 (16 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808752/+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 1735062] Re: Xorg freeze
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- 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/1735062 Title: Xorg freeze Status in linux package in Ubuntu: Won't Fix Bug description: The problem is a very short graphics freeze. I believe the issue is related to the i915 driver:;; [ 1103.153702] [ cut here ] [ 1103.153759] WARNING: CPU: 2 PID: 5425 at /build/linux-KM2a5S/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:12848 intel_atomic_commit_tail+0xf7d/0xf90 [i915] [ 1103.153760] Modules linked in: msr rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm bnep binfmt_misc intel_rapl dell_laptop x86_pkg_temp_thermal intel_powerclamp dell_smm_hwmon coretemp kvm_intel uvcvideo kvm videobuf2_vmalloc btusb irqbypass snd_hda_codec_hdmi videobuf2_memops videobuf2_v4l2 snd_hda_codec_conexant btrtl snd_hda_codec_generic videobuf2_core crct10dif_pclmul crc32_pclmul btbcm btintel ghash_clmulni_intel cryptd intel_cstate snd_hda_intel intel_rapl_perf bluetooth videodev snd_hda_codec snd_hda_core media ecdh_generic snd_hwdep dell_wmi dell_smbios arc4 snd_pcm input_leds dcdbas joydev sparse_keymap serio_raw wmi_bmof snd_seq_midi snd_seq_midi_event snd_rawmidi iwldvm mac80211 snd_seq snd_seq_device snd_timer iwlwifi snd cfg80211 lpc_ich soundcore mei_me mei [ 1103.153800] shpchp dell_smo8800 mac_hid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci drm libahci atl1c wmi video [ 1103.153820] CPU: 2 PID: 5425 Comm: kworker/u16:2 Tainted: G OE 4.13.0-17-generic #20-Ubuntu [ 1103.153821] Hardware name: Dell Inc. Dell System Inspiron N411Z/0YWNPW, BIOS A00 06/24/2011 [ 1103.153860] Workqueue: events_unbound intel_atomic_commit_work [i915] [ 1103.153862] task: 90c28720c5c0 task.stack: a496c3ee [ 1103.153898] RIP: 0010:intel_atomic_commit_tail+0xf7d/0xf90 [i915] [ 1103.153899] RSP: 0018:a496c3ee3d88 EFLAGS: 00010282 [ 1103.153900] RAX: 001c RBX: 0001 RCX: [ 1103.153901] RDX: RSI: 90c39fa8dc78 RDI: 90c39fa8dc78 [ 1103.153902] RBP: a496c3ee3e40 R08: 0001 R09: 0323 [ 1103.153903] R10: a496c3ee3d88 R11: R12: fe3e [ 1103.153904] R13: 90c38d06 R14: 90c38e3db000 R15: 0002 [ 1103.153906] FS: () GS:90c39fa8() knlGS: [ 1103.153907] CS: 0010 DS: ES: CR0: 80050033 [ 1103.153908] CR2: 7f2139afa000 CR3: 0001949eb000 CR4: 000406e0 [ 1103.153910] Call Trace: [ 1103.153917] ? wait_woken+0x80/0x80 [ 1103.153955] intel_atomic_commit_work+0x12/0x20 [i915] [ 1103.153960] process_one_work+0x1e7/0x410 [ 1103.153962] worker_thread+0x4a/0x410 [ 1103.153965] kthread+0x125/0x140 [ 1103.153967] ? process_one_work+0x410/0x410 [ 1103.153969] ? kthread_create_on_node+0x70/0x70 [ 1103.153972] ret_from_fork+0x25/0x30 [ 1103.153974] Code: ff ff ff 48 83 c7 08 e8 42 a1 32 e0 4c 8b 85 70 ff ff ff 4d 85 c0 0f 85 7b fa ff ff 8d 73 41 48 c7 c7 60 c4 66 c0 e8 d4 53 34 e0 <0f> ff e9 65 fa ff ff 66 90 66 2e 0f 1f 84 00 00 00 00 00 66 66 [ 1103.154006] ---[ end trace 3e9edf28140fd63f ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 22:09:19 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.10.0-40-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphic
[Kernel-packages] [Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint
Same as LP: #1803600? Try boot with kernel parameter "psmouse.elantech_smbus=0". -- 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/1808588 Title: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint Status in linux package in Ubuntu: Confirmed Bug description: I upgraded my Ubuntu from Bionic Beaver to Cosmic Cuttlefish on my laptop. The installation process seemed to go well, but on reboot my trackpad and trackpoint no longer move the pointer, register taps or click buttons, and are seemingly unrecognized by the system. General information: Laptop make/model: Lenovo Thinkpad P72 TYPE 20MB-CT01WW 18/11 (that might be a 'O' rather than an '0' on the sticker) Touchpad maufacturer: (Lenovo?) UltraNav TrackPoint When symptoms first appeared: On first reboot after the change to Cosmic. Also on subsequent reboots and waking from sleep and suspend. No trackpad device is listed in /proc/bus/input/devices. The trackpad and trackpoint and buttons work if I boot into another OS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+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
