[Kernel-packages] [Bug 1825663] [NEW] Regression: With "nomodeset" in grub, very long boot times due to "/usr/bin/nvidia-smi"
Public bug reported: When booting with the Nvidia drivers version 418 with the following GRUB setting: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" Boot process takes a very long time to complete. Output from /var/sys/syslog Apr 20 07:58:28 matt-tower systemd-resolved[1027]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Apr 20 07:58:28 matt-tower systemd-resolved[1027]: message repeated 2 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Apr 20 07:58:29 matt-tower systemd[1]: NetworkManager-dispatcher.service: Succeeded. Apr 20 07:58:30 matt-tower systemd-resolved[1027]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Apr 20 07:58:30 matt-tower systemd-resolved[1027]: message repeated 2 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Apr 20 07:58:43 matt-tower systemd[1]: systemd-fsckd.service: Succeeded. Apr 20 07:58:45 matt-tower systemd-timesyncd[1025]: Synchronized to time server 91.189.91.157:123 (ntp.ubuntu.com). Apr 20 07:58:46 matt-tower systemd[1]: systemd-hostnamed.service: Succeeded. Apr 20 07:59:12 matt-tower systemd-udevd[588]: Spawned process '/usr/bin/nvidia-smi' [657] is taking longer than 59s to complete Apr 20 07:59:12 matt-tower systemd-udevd[548]: nvidia: Worker [588] processing SEQNUM=2799 is taking a long time Apr 20 07:59:13 matt-tower kernel: [ 76.679951] snd_hda_intel :00:1b.0: couldn't bind with audio component Apr 20 07:59:13 matt-tower kernel: [ 76.703584] snd_hda_codec_realtek hdaudioC0D2: autoconfig for ALC892: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line Apr 20 07:59:13 matt-tower kernel: [ 76.703586] snd_hda_codec_realtek hdaudioC0D2:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Apr 20 07:59:13 matt-tower kernel: [ 76.703587] snd_hda_codec_realtek hdaudioC0D2:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) This issue did not happen with the nvidia-driver-390, nor on ubuntu 18.10 with the 418 drivers via the PPA. This is a performance regression. Unfortunately, if I do not set "nomodeset" in GRUB, then the plymouth splash screen and entire boot process is a blank screen, which makes it difficult to enter my LUKS encryption key. (in other words, removing "nomodeset" from GRUB is not an option) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 08:07:55 2019 InstallationDate: Installed on 2019-04-20 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: Upgraded to disco on 2019-04-20 (0 days ago) ** Affects: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1825663 Title: Regression: With "nomodeset" in grub, very long boot times due to "/usr/bin/nvidia-smi" Status in nvidia-graphics-drivers-418 package in Ubuntu: New Bug description: When booting with the Nvidia drivers version 418 with the following GRUB setting: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" Boot process takes a very long time to complete. Output from /var/sys/syslog Apr 20 07:58:28 matt-tower systemd-resolved[1027]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Apr 20 07:58:28 matt-tower systemd-resolved[1027]: message repeated 2 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Apr 20 07:58:29 matt-tower systemd[1]: NetworkManager-dispatcher.service: Succeeded. Apr 20 07:58:30 matt-tower systemd-resolved[1027]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Apr 20 07:58:30 matt-tower systemd-resolved[1027]: message repeated 2 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Apr 20 07:58:43 matt-tower systemd[1]: systemd-fsckd.service: Succeeded. Apr 20 07:58:45 matt-tower systemd-timesyncd[1025]:
[Kernel-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
It's back! Me too on Ubuntu 18.04.2 LTS. Maybe it was package keyboard-configuration_1.178ubuntu2.8_all.deb? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: New Status in linux source package in Bionic: New Status in xorg-server source package in Bionic: New Status in console-setup source package in Cosmic: New Status in linux source package in Cosmic: New Status in xorg-server source package in Cosmic: New Status in console-setup source package in Disco: In Progress Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: New Status in linux source package in Eoan: New Status in xorg-server source package in Eoan: New Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1771764] Re: Add encapsulation support to ip route
Please see my comment on bug 1771783 -- unsubscribing the Ubuntu
Sponsors Team.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1771764
Title:
Add encapsulation support to ip route
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Triaged
Bug description:
The following command does not work:
$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"
In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103
=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4
With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2
At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+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 1691214] Re: Consider enabling --color by default
Bump; was this patch sent upstream? What is the status of it at the moment? The attached patch can't be uploaded as-is to any currently-supported release, unsubscribing sponsors (please resubscribe when more details are given). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1691214 Title: Consider enabling --color by default Status in iproute2 package in Ubuntu: Confirmed Bug description: The output of ip --color a looks a lot nicer to me than ip a If you look in /etc/skel/.bashrc you can see that we already enable color for other commands: alias ls='ls --color=auto' alias grep='grep --color=auto' alias fgrep='fgrep --color=auto' alias egrep='egrep --color=auto' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1691214/+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 1771783] Re: Add support for custom protocols from rt_protos.d
Hello! Thank you for your contribution to Ubuntu.
If you would like this to be sponsored to Xenial, please edit the bug
description to follow the SRU bug template. More information can be
found here:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
Additionally, I see in your debdiff there are multiple areas which still need
to be filled in, or removed. Such lines include:
+## Description: add some description
+## Origin/Author: add some origin or author
+## Bug: bug URL
I recommend you read the DEP-3 standard, which provides a standard way
to fill out such a description: https://dep-
team.pages.debian.net/deps/dep3/
I am unsubscribing the Ubuntu Sponsors Team for now, please resubscribe
us when the changes have been made.
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1771783
Title:
Add support for custom protocols from rt_protos.d
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Triaged
Bug description:
FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20
iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos
A patch has been pushed upstream so that external applications can define
their protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+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 1825554] Re: Ryzen5 2500U Vega 8 raven ridge flickering screen
apport information ** Description changed: Hey, I'm running Ubuntu 18.10 on a Lenovo Yoga 530 14-AHR. My display is flickering, depending on the displayed content in different frequency. Video of the symptom: https://www.dropbox.com/s/ulbqo7taspx60vv/VID_20190123_151449.mp4?dl=0 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-09 (160 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 5.0.0-05-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.2 + Architecture: amd64 + CurrentDesktop: X-Cinnamon + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-11-09 (161 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + Package: linux (not installed) + Tags: cosmic + Uname: Linux 5.0.8-050008-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1825554/+attachment/5257190/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825554 Title: Ryzen5 2500U Vega 8 raven ridge flickering screen Status in linux package in Ubuntu: Confirmed Bug description: Hey, I'm running Ubuntu 18.10 on a Lenovo Yoga 530 14-AHR. My display is flickering, depending on the displayed content in different frequency. Video of the symptom: https://www.dropbox.com/s/ulbqo7taspx60vv/VID_20190123_151449.mp4?dl=0 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-09 (160 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 5.0.0-05-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-09 (161 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 5.0.8-050008-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825554/+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 1825219] Re: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs
Emrah ÖZCAN, thank you for reporting this and helping make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1825219 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825219 Title: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs Status in linux package in Ubuntu: Incomplete Bug description: ubuntu 16.04 i386 32 bit processor On settings "do anything when closing lid" is aplied. Hard reset needs . Tried all other ways. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825219/+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 1825554] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1825554/+attachment/5257191/+files/ProcEnviron.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825554 Title: Ryzen5 2500U Vega 8 raven ridge flickering screen Status in linux package in Ubuntu: Confirmed Bug description: Hey, I'm running Ubuntu 18.10 on a Lenovo Yoga 530 14-AHR. My display is flickering, depending on the displayed content in different frequency. Video of the symptom: https://www.dropbox.com/s/ulbqo7taspx60vv/VID_20190123_151449.mp4?dl=0 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-09 (160 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 5.0.0-05-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-09 (161 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 5.0.8-050008-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825554/+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 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10
** Description changed: [Impact] The integrity subsystem is still reporting error messages like this at boot: - integrity: Unable to open file: /etc/keys/x509_evm.der (-2) + integrity: Unable to open file: /etc/keys/x509_evm.der (-2) - In a previous commit we have downgraded these errors to warnings: + In a previous commit we have downgraded this error to warning: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master- next=58441dc86d7b066a2c02079829a96035587a7066 (this fix is applied everywhere, not only in bionic) But there's another place (security/integrity/digsig.c) that reports the - same error message that should be also downgraded for consistency. + same error message that should be also downgraded to warning for + consistency. [Test Case] No special test case is required, errors are reported at boot if an integrity policy is enabled. [Fix] Downgrade also this error message to a warning. + + [Regression Potential] + + It is a one-liner that changes a printk() error message, regression + potential is minimal. [Original bug report] == Comment: #0 - Application Cdeadmin - 2018-04-20 05:56:03 == == Comment: #1 - Application Cdeadmin - 2018-04-20 05:56:05 == State: Open by: stccdenv on 18 April 2018 06:27:28 This defect was opened automatically using defect_template with only logs. Please refer to 2nd seq for the problem description. ==Automatic entries== Full Log: http://w3.austin.ibm.com/afs/awd.austin.ibm.com/u/stccdenv/logs/devops4fp1_defect_template_20180418060138 Contact: Thirukumaran V T (thirukuma...@in.ibm.com), Tommy Adams(tnad...@us.ibm.com) Backup: Atit Patel (a...@us.ibm.com) System Name: devops4fp1 FSP IP: 9.3.136.192 (devops4fp1.aus.stglabs.ibm.com) System Firmware Level: Current Side Driver:.fips861/b0413a_1816.861 Non-Current Side Driver:.fips861/b0410a_1816.861 Lpar Access: Please refer https://pcajet.aus.stglabs.ibm.com/ for the lab password. (The Lab Test Passwords are now accessible only through the auto or manual install web apps. For example, from the manual install web app, enter your email address, check the Lab Passwords checkbox and then click on Submit.) (To access the Lpars in 10.33.x.x network, login to any LCB or HMC then ssh/telnet to 10.33.x.x lpars) --- HMC IP: 9.3.118.110 (vhmccloudtst100.aus.stglabs.ibm.com) HMC Version: "version= Version: 9 Release: 1 Service Pack: 910 HMC Build level 1803052221 ","base_version=V9R1 " --- =Logs SNAP : devops4p02: /tmp/ibmsupt/snap.pax.Z.devops4p02.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p02.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p02 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p02 devops4p03: /tmp/ibmsupt/snap.pax.Z.devops4p03.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p03.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p03 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p03 devops4p04: /tmp/ibmsupt/snap.pax.Z.devops4p04.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p04.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p04 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p04 devops4p05: /tmp/ibmsupt/snap.pax.Z.devops4p05.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p05.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p05 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p05 devops4p06: /tmp/ctsupt/ctsnap.linux-hjmh.04180701.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.linux-hjmh.04180701.tar.gz /tmp/var_log.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/var_log.180418060149.tar.gz /var/log/nts_linux-hjmh_180418_0703.tbz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/nts_linux-hjmh_180418_0703.tbz /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p06 /tmp/htx.180418060149.tar.gz and also @
[Kernel-packages] [Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10
And about the error "vio vio: uevent:" happening at boot, it could be triggered by something in the initramfs. I think the best thing we can do from a kernel perspective is to add extra information to the error message to figure out exactly which task is triggering this error, and maybe also print the exact data that is received by the kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766201 Title: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The integrity subsystem is still reporting error messages like this at boot: integrity: Unable to open file: /etc/keys/x509_evm.der (-2) In a previous commit we have downgraded this error to warning: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master- next=58441dc86d7b066a2c02079829a96035587a7066 (this fix is applied everywhere, not only in bionic) But there's another place (security/integrity/digsig.c) that reports the same error message that should be also downgraded to warning for consistency. [Test Case] No special test case is required, errors are reported at boot if an integrity policy is enabled. [Fix] Downgrade also this error message to a warning. [Regression Potential] It is a one-liner that changes a printk() error message, regression potential is minimal. [Original bug report] == Comment: #0 - Application Cdeadmin - 2018-04-20 05:56:03 == == Comment: #1 - Application Cdeadmin - 2018-04-20 05:56:05 == State: Open by: stccdenv on 18 April 2018 06:27:28 This defect was opened automatically using defect_template with only logs. Please refer to 2nd seq for the problem description. ==Automatic entries== Full Log: http://w3.austin.ibm.com/afs/awd.austin.ibm.com/u/stccdenv/logs/devops4fp1_defect_template_20180418060138 Contact: Thirukumaran V T (thirukuma...@in.ibm.com), Tommy Adams(tnad...@us.ibm.com) Backup: Atit Patel (a...@us.ibm.com) System Name: devops4fp1 FSP IP: 9.3.136.192 (devops4fp1.aus.stglabs.ibm.com) System Firmware Level: Current Side Driver:.fips861/b0413a_1816.861 Non-Current Side Driver:.fips861/b0410a_1816.861 Lpar Access: Please refer https://pcajet.aus.stglabs.ibm.com/ for the lab password. (The Lab Test Passwords are now accessible only through the auto or manual install web apps. For example, from the manual install web app, enter your email address, check the Lab Passwords checkbox and then click on Submit.) (To access the Lpars in 10.33.x.x network, login to any LCB or HMC then ssh/telnet to 10.33.x.x lpars) --- HMC IP: 9.3.118.110 (vhmccloudtst100.aus.stglabs.ibm.com) HMC Version: "version= Version: 9 Release: 1 Service Pack: 910 HMC Build level 1803052221 ","base_version=V9R1 " --- =Logs SNAP : devops4p02: /tmp/ibmsupt/snap.pax.Z.devops4p02.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p02.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p02 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p02 devops4p03: /tmp/ibmsupt/snap.pax.Z.devops4p03.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p03.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p03 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p03 devops4p04: /tmp/ibmsupt/snap.pax.Z.devops4p04.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p04.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p04 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p04 devops4p05: /tmp/ibmsupt/snap.pax.Z.devops4p05.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p05.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p05 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p05 devops4p06: /tmp/ctsupt/ctsnap.linux-hjmh.04180701.tar.gz and also @
[Kernel-packages] [Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10
@manjo thanks for testing again! Now I see, we need to apply another small patch to security/integrity/digsig.c, that seems to have exactly the same error message that should be considered a warning instead. I'll post a fix soon. -- 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/1766201 Title: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 - Application Cdeadmin - 2018-04-20 05:56:03 == == Comment: #1 - Application Cdeadmin - 2018-04-20 05:56:05 == State: Open by: stccdenv on 18 April 2018 06:27:28 This defect was opened automatically using defect_template with only logs. Please refer to 2nd seq for the problem description. ==Automatic entries== Full Log: http://w3.austin.ibm.com/afs/awd.austin.ibm.com/u/stccdenv/logs/devops4fp1_defect_template_20180418060138 Contact: Thirukumaran V T (thirukuma...@in.ibm.com), Tommy Adams(tnad...@us.ibm.com) Backup: Atit Patel (a...@us.ibm.com) System Name: devops4fp1 FSP IP: 9.3.136.192 (devops4fp1.aus.stglabs.ibm.com) System Firmware Level: Current Side Driver:.fips861/b0413a_1816.861 Non-Current Side Driver:.fips861/b0410a_1816.861 Lpar Access: Please refer https://pcajet.aus.stglabs.ibm.com/ for the lab password. (The Lab Test Passwords are now accessible only through the auto or manual install web apps. For example, from the manual install web app, enter your email address, check the Lab Passwords checkbox and then click on Submit.) (To access the Lpars in 10.33.x.x network, login to any LCB or HMC then ssh/telnet to 10.33.x.x lpars) --- HMC IP: 9.3.118.110 (vhmccloudtst100.aus.stglabs.ibm.com) HMC Version: "version= Version: 9 Release: 1 Service Pack: 910 HMC Build level 1803052221 ","base_version=V9R1 " --- =Logs SNAP : devops4p02: /tmp/ibmsupt/snap.pax.Z.devops4p02.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p02.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p02 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p02 devops4p03: /tmp/ibmsupt/snap.pax.Z.devops4p03.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p03.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p03 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p03 devops4p04: /tmp/ibmsupt/snap.pax.Z.devops4p04.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p04.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p04 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p04 devops4p05: /tmp/ibmsupt/snap.pax.Z.devops4p05.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p05.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p05 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p05 devops4p06: /tmp/ctsupt/ctsnap.linux-hjmh.04180701.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.linux-hjmh.04180701.tar.gz /tmp/var_log.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/var_log.180418060149.tar.gz /var/log/nts_linux-hjmh_180418_0703.tbz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/nts_linux-hjmh_180418_0703.tbz /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p06 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p06 devops4p07: /tmp/ctsupt/ctsnap.devops4p07.04180601.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.devops4p07.04180601.tar.gz /tmp/var_log.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/var_log.180418060149.tar.gz /var/tmp/sosreport-devops4p07.aus.stglabs.ibm.com-20180418060350.tar.xz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/sosreport-devops4p07.aus.stglabs.ibm.com-20180418060350.tar.xz /tmp/IBM.DRM.180418060149.tar.gz and also @
[Kernel-packages] [Bug 982299] Re: [Dell Inspiron 1520] Screen stays black after laptop lid is opened
** This bug is no longer a duplicate of bug 1825219 Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs -- 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/982299 Title: [Dell Inspiron 1520] Screen stays black after laptop lid is opened Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Every time I close my laptop's lid and wait for few minutes -- screen stays black. I can switch to text console (Alt-Ctrl-F1) and back to black X screen (Alt-Ctrl-F7). I can login in console. I don't see mouse cursor on X screen. I'm using free nouveau drivers. This issue appeared just after I've upgraded to 12.04 beta2. I'm running 'sudo restart lightdm' from console to bring X to life. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0-0ubuntu4 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Sun Apr 15 16:35:07 2012 DistUpgraded: 2012-03-30 06:52:10,270 DEBUG got a conffile-prompt from dpkg for file: '/etc/gnome/defaults.list' DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: Dell Inc. Inspiron 1520 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-22-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to precise on 2012-03-30 (16 days ago) dmi.bios.date: 07/11/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0UW306 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0UW306:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.4-0ubuntu3 version.ia32-libs: ia32-libs 20090808ubuntu35 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/982299/+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 1821823] Re: No wireless networks displayed for broadcom BCM43142
This bug was fixed in the package dkms - 2.6.1-4ubuntu2 --- dkms (2.6.1-4ubuntu2) disco; urgency=medium * d/p/revert-removal-of-modules-from-dkms-built-tree.patch: - Revert the upstream change that caused dkms uninstall remove the modules from the built tree, as that seems wrong. The uninstall operation should leave the module in the 'built' state as per design (LP: #1821823). -- Łukasz 'sil2100' Zemczak Wed, 17 Apr 2019 11:30:19 +0100 ** Changed in: dkms (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in dkms package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Invalid Status in dkms source package in Disco: Fix Committed Bug description: [Impact] The dkms version available in disco regressed in behavior in comparison to earlier series, causing `dkms uninstall` removing the module from the built tree instead of only uninstalling it. Per the dkms manpage, an uninstall operation should leave the module in the 'built' state, while currently it ends up only in the 'added' state. This breaks our current shim-signed logic, since on postinst we're uninstalling every dkms module, checking if we uninstalled it correctly by making sure it's in the 'built' state and then signing it if everything is ok. And this is now broken. This seemed to have been introduced unintentionally as the manpage still notes for `dkms uninstall`: "Uninstalls an installed module/module-version combo from the kernel/arch passed in the -k option, or the current kernel if the -k option was not passed upon. After uninstall completion, the driver will be left in the built state. To completely remove a driver, the remove action should be utilized." The bug has been made visible with the bcmwl-kernel-source driver, which, if installed before shim-signed, will then become uninstalled and not reinstalled again (because of the failed status check before signing). [Test Case] An easy way of checking if the uninstall logic has been reverted: 1. On a disco system, install the dkms and bcmwl-kernel-source packages (-proposed disabled). 2. Check the version of the module installed `dkms status`. 3. Once the installation completes, uninstall the bcmwl dkms module from the system: `dkms uninstall bcmwl/` 4. Checks that the status is not reported as 'built' (should be something like 'added' only): `dkms status bcmwl` 5. Enable disco-proposed and upgrade dkms. 6. Re-install the bcmwl-kernel-source package. 7. Once again uninstall the bcmwl dkms module: `dkms uninstall bcmwl/` 8. Check the status and notice that it is now reported as 'built': `dkms status bcmwl` Another way would be checking on a secureboot-enabled system that has Broadcom wireless installing the -proposed dkms, then bcmwl-kernel- source and finally shim-signed (reinstalling if necessary). This operation should result in the broadcom dkms module still being installed and active. But this test should be counted as an optional 'additional test'. [Regression Potential] Since this does change the dkms uninstall behavior, there is always some risk involved. One of the potential regressions could be related to kernel uninstallation, as we are reverting parts of the kernel prerm scripts along with the revert - but the risk should be low as we're actually reverting to the state we had in all series prior to disco. In overall the uninstall command of dkms might have regressed its behavior in case some other place started assuming the removals of modules from the built directory, but seeing the disco diff it's highly improbable. [Original Description] For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha
[Kernel-packages] [Bug 1821027] Re: Boot time increase since 4.15.0-46 on Dell G7 7588
** Attachment added: "systemd-analyze" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+attachment/5257220/+files/systemd-analyze -- 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/1821027 Title: Boot time increase since 4.15.0-46 on Dell G7 7588 Status in linux package in Ubuntu: Confirmed Bug description: Hi Ubuntu Team, My laptop take more than 45 sec to boot up Ubuntu. Here is my kernel log. Feb 5 13:26:57 my-laptop kernel: [2.461535] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 Feb 5 13:26:57 my-laptop kernel: [2.780579] [drm] RC6 on Feb 5 13:26:57 my-laptop kernel: [ 33.565700] SGI XFS with ACLs, security attributes, realtime, no debug enabled Feb 5 13:26:57 my-laptop kernel: [ 33.567361] XFS (nvme0n1p10): Mounting V5 Filesystem Here is the problem. It take more than 30 sec to do load the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+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 1821027] Re: Boot time increase since 4.15.0-46 on Dell G7 7588
** Attachment added: "lspci" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+attachment/5257221/+files/lspci -- 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/1821027 Title: Boot time increase since 4.15.0-46 on Dell G7 7588 Status in linux package in Ubuntu: Confirmed Bug description: Hi Ubuntu Team, My laptop take more than 45 sec to boot up Ubuntu. Here is my kernel log. Feb 5 13:26:57 my-laptop kernel: [2.461535] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 Feb 5 13:26:57 my-laptop kernel: [2.780579] [drm] RC6 on Feb 5 13:26:57 my-laptop kernel: [ 33.565700] SGI XFS with ACLs, security attributes, realtime, no debug enabled Feb 5 13:26:57 my-laptop kernel: [ 33.567361] XFS (nvme0n1p10): Mounting V5 Filesystem Here is the problem. It take more than 30 sec to do load the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+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 1821027] Re: Boot time increase since 4.15.0-46 on Dell G7 7588
** Attachment added: "systemd-analyze-blame" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+attachment/5257219/+files/systemd-analyze-blame -- 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/1821027 Title: Boot time increase since 4.15.0-46 on Dell G7 7588 Status in linux package in Ubuntu: Confirmed Bug description: Hi Ubuntu Team, My laptop take more than 45 sec to boot up Ubuntu. Here is my kernel log. Feb 5 13:26:57 my-laptop kernel: [2.461535] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 Feb 5 13:26:57 my-laptop kernel: [2.780579] [drm] RC6 on Feb 5 13:26:57 my-laptop kernel: [ 33.565700] SGI XFS with ACLs, security attributes, realtime, no debug enabled Feb 5 13:26:57 my-laptop kernel: [ 33.567361] XFS (nvme0n1p10): Mounting V5 Filesystem Here is the problem. It take more than 30 sec to do load the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+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 1821027] Re: Boot time increase since 4.15.0-46 on Dell G7 7588
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+attachment/5257222/+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/1821027 Title: Boot time increase since 4.15.0-46 on Dell G7 7588 Status in linux package in Ubuntu: Confirmed Bug description: Hi Ubuntu Team, My laptop take more than 45 sec to boot up Ubuntu. Here is my kernel log. Feb 5 13:26:57 my-laptop kernel: [2.461535] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 Feb 5 13:26:57 my-laptop kernel: [2.780579] [drm] RC6 on Feb 5 13:26:57 my-laptop kernel: [ 33.565700] SGI XFS with ACLs, security attributes, realtime, no debug enabled Feb 5 13:26:57 my-laptop kernel: [ 33.567361] XFS (nvme0n1p10): Mounting V5 Filesystem Here is the problem. It take more than 30 sec to do load the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+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
Re: [Kernel-packages] [Bug 1799019] Re: Linux crashed so severly that I have to reinstall.
That is not the only bug that has “slip through our radar”. The latest update of Ubuntu MATE lies about the owner of files both in the command line ls -l command and the Caja Properties window. Both claim the owner is root. Since I am logged on a robert not root I would not be able to create, modify, or delete any files in my system (ls always says to owner is root). Since I can make changes then either the file system permissions code is broken or the owner is being incorrectly reported. I reported this problem about 4 weeks ago. It has “slip through our radar”. No response from anybody despite the fact that this is a security problem in the basic kernel. Robert On Fri, Apr 19, 2019 at 7:50 AM Po-Hsu Lin wrote: > Hello, > my apology for this situation, we let this package (linux-signed) slip > through our radar in the old days. The process has been improved now. > > I am gonna close this bug with Invalid, but please feel free to open a > new bug with command "ubuntu-bug linux" base on what you have > encountered recently (preferably one issue in a report, and with a > supported version, as Ubuntu Mate 14.10 has already reaches it End-of- > Life [1]). > > Or ask questions on community forums like https://askubuntu.com > https://ubuntuforums.org/ > > Thank you. > > [1] https://en.wikipedia.org/wiki/Ubuntu_MATE > > ** Changed in: linux-signed (Ubuntu) >Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1799019 > > Title: > Linux crashed so severly that I have to reinstall. > > Status in linux-signed package in Ubuntu: > Invalid > > Bug description: > First Google Chrome and Chromium crashed closing all their windows. > Then most, but not all, of the VisualWorks windows diappeared. > (Unfortunately the System window closed so I could not exit properly). > Then the list of open windows at the bottom of the screen disappeared, > as did the menu bar at the top. With no menu to shutdown, I had to > turn power off. > > When I tried to reboot I got the Ubuntu symbol and the progress dots > underneath. After more than an hour, I got a command line to log in. > (Not a terminal window - Ubuntu never started.) > > I was able to log in but could do nothing since this was a system > without MATE or any window GUI. > > Every time I try to reboot, I get the save progress dots for over an > hour and then the terminal mode login prompt. > > I had to boot from the distribution DVD to make this report before re- > installing the system. > > Please fix your documentation on reporting system crashes. What is > "apport" and how do I run it? > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-20-generic 4.15.0-20.21 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Uname: Linux 4.15.0-20-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CasperVersion: 1.394 > CurrentDesktop: MATE > Date: Sun Oct 21 02:13:33 2018 > LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > ProcEnviron: >TERM=xterm >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=C.UTF-8 >SHELL=/bin/bash > SourcePackage: linux-signed > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1799019/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1799019 Title: Linux crashed so severly that I have to reinstall. Status in linux-signed package in Ubuntu: Invalid Bug description: First Google Chrome and Chromium crashed closing all their windows. Then most, but not all, of the VisualWorks windows diappeared. (Unfortunately the System window closed so I could not exit properly). Then the list of open windows at the bottom of the screen disappeared, as did the menu bar at the top. With no menu to shutdown, I had to turn power off. When I tried to reboot I got the Ubuntu symbol and the progress dots underneath. After more than an hour, I got a command line to log in. (Not a terminal window - Ubuntu never started.) I was able to log in but could do nothing since this was a system without MATE or any window GUI. Every time I try to reboot, I get the save progress dots for over an hour and then the terminal mode login prompt. I had to boot from the distribution DVD to make this report before re- installing the system. Please fix your documentation on reporting system crashes. What is "apport" and how do I run it? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux
[Kernel-packages] [Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10
** Description changed: + [Impact] + + The integrity subsystem is still reporting error messages like this at + boot: + + integrity: Unable to open file: /etc/keys/x509_evm.der (-2) + + In a previous commit we have downgraded these errors to warnings: + + https://git.launchpad.net/~ubuntu- + kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master- + next=58441dc86d7b066a2c02079829a96035587a7066 + + (this fix is applied everywhere, not only in bionic) + + But there's another place (security/integrity/digsig.c) that reports the + same error message that should be also downgraded for consistency. + + [Test Case] + + No special test case is required, errors are reported at boot if an + integrity policy is enabled. + + [Fix] + + Downgrade also this error message to a warning. + + [Original bug report] + == Comment: #0 - Application Cdeadmin - 2018-04-20 05:56:03 == - == Comment: #1 - Application Cdeadmin - 2018-04-20 05:56:05 == State: Open by: stccdenv on 18 April 2018 06:27:28 This defect was opened automatically using defect_template with only logs. Please refer to 2nd seq for the problem description. ==Automatic entries== Full Log: http://w3.austin.ibm.com/afs/awd.austin.ibm.com/u/stccdenv/logs/devops4fp1_defect_template_20180418060138 Contact: Thirukumaran V T (thirukuma...@in.ibm.com), Tommy Adams(tnad...@us.ibm.com) Backup: Atit Patel (a...@us.ibm.com) System Name: devops4fp1 FSP IP: 9.3.136.192 (devops4fp1.aus.stglabs.ibm.com) System Firmware Level: - Current Side Driver:.fips861/b0413a_1816.861 - Non-Current Side Driver:.fips861/b0410a_1816.861 + Current Side Driver:.fips861/b0413a_1816.861 + Non-Current Side Driver:.fips861/b0410a_1816.861 Lpar Access: Please refer https://pcajet.aus.stglabs.ibm.com/ for the lab password. (The Lab Test Passwords are now accessible only through the auto or manual install web apps. For example, from the manual install web app, enter your email address, check the Lab Passwords checkbox and then click on Submit.) (To access the Lpars in 10.33.x.x network, login to any LCB or HMC then ssh/telnet to 10.33.x.x lpars) --- HMC IP: 9.3.118.110 (vhmccloudtst100.aus.stglabs.ibm.com) HMC Version: "version= Version: 9 - Release: 1 - Service Pack: 910 + Release: 1 + Service Pack: 910 HMC Build level 1803052221 ","base_version=V9R1 " --- =Logs - SNAP : - devops4p02: /tmp/ibmsupt/snap.pax.Z.devops4p02.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p02.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p02 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p02 - devops4p03: /tmp/ibmsupt/snap.pax.Z.devops4p03.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p03.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p03 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p03 - devops4p04: /tmp/ibmsupt/snap.pax.Z.devops4p04.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p04.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p04 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p04 - devops4p05: /tmp/ibmsupt/snap.pax.Z.devops4p05.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p05.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p05 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p05 - devops4p06: /tmp/ctsupt/ctsnap.linux-hjmh.04180701.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.linux-hjmh.04180701.tar.gz /tmp/var_log.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/var_log.180418060149.tar.gz /var/log/nts_linux-hjmh_180418_0703.tbz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/nts_linux-hjmh_180418_0703.tbz /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p06 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p06 - devops4p07: /tmp/ctsupt/ctsnap.devops4p07.04180601.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.devops4p07.04180601.tar.gz
[Kernel-packages] [Bug 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR
Do you use the same laptop as the original bug reporter? -- 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/1796582 Title: Internal microphone not working on Lenovo Ideapad 330S-15ARR Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The internal microphone on this troublesome laptop stopped working after upgrading from Bionic to Cosmic. There is no signal from the microphone with kernel 4.18.0-7 or 4.18.0-8. This DOES work correctly with kernel 4.15.0-34 that is still present on Cosmic after the upgrade. I recommend Canonical gets this laptop for testing since a ton of stuff is troublesome on this Raven Ridge laptop. Would be a good specimen to get support for this platform improved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2295 F pulseaudio /dev/snd/controlC0: xorbit 2295 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 7 12:02:45 2018 InstallationDate: Installed on 2018-09-20 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796582/+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 1825632] 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/1825632 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon Status in linux package in Ubuntu: Confirmed Bug description: Problem when i installing the new version. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erwan 3106 F pulseaudio /dev/snd/controlC1: erwan 3106 F pulseaudio Date: Sat Apr 20 12:37:44 2019 ErrorMessage: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon InstallationDate: Installed on 2018-10-07 (194 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=d478b832-a087-4e04-824b-57099769e24e ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 SourcePackage: linux Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) dmi.bios.date: 05/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LB.603 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LB.603:bd05/06/2016:svnASUSTeKCOMPUTERINC.:pnX555LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825632/+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 1785912]
Nothing changed, I assume that work will be done here before the fix is pushed. @Marteen I also tried to build the kernel with "constant_n = true;" and the flickering is still there. I do know that a laptop with the same display panel (Dell xps 9370) works perfectly fine under Linux. The panel is manufactured by AUO and is the B133ZAN01.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/1785912 Title: Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV Status in Linux: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Horrible screen flicker from login screen and after login. 18.04.1 LTS. I have two similar laptops, both Lenovo Ideapad 720s 13IKB, model 81A8 - Core i5 7200U - Intel HD Graphics 620 Rev 02 - works fine. model 81BV - Core i5 8250U - Intel UHD Graphics 620 Rev 07 - awful screen flashing. Neither have the problem in Windows (ie hardware fine) I installed the standard Ubuntu 18.04 on each of them (same USB Key, few weeks apart) but only the 81BV / 8th gen / UHD 620 Rev 07 has the problem. Flickering visible on video here: https://photos.app.goo.gl/HCN73q1nQfgstgVBA I've used ubuntu-bug so I believe you have all the details of the machine. The install came straight from your standard 18.04 download. Any changes are due to me trying to fix this (not much prev exp of kernel params etc) Things tried but which didn't work were: - enable huc/guc (got it to load - it's now visible in the attached dmesg - but didn't help.) - enable_rc6=0 (just stopped sleep / resume working) - edp_vswing=2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Tue Aug 7 23:09:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39af] InstallationDate: Installed on 2018-08-06 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:210d Acer, Inc Bus 001 Device 002: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=10eb4e00-26e4-4f42-b983-9a603a658f89 ro i915.enable_guc=3 i915.enable_guc_loading=1 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6MCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 720S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr6MCN27WW:bd05/02/2018:svnLENOVO:pn81BV:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB: dmi.product.family: ideapad 720S-13IKB dmi.product.name: 81BV dmi.product.version: Lenovo ideapad 720S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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 N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1785912/+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 1825638] 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 1825638 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/1825638 Title: Lenovo Legion Y530-15ICH does not start with live usb Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+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 1825638] [NEW] Lenovo Legion Y530-15ICH does not start with live usb
Public bug reported: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: does legion lenovo not start y530-15ich -- 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/1825638 Title: Lenovo Legion Y530-15ICH does not start with live usb Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+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 1825639] [NEW] Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound.
Public bug reported: This is the same problem in https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem persists (this T430 laptop has inbuilt Bluetooth). This makes listening to music or any audio over Bluetooth almost unbearable - while it is temporarily fixed by running `pactl suspend- sink 1 && pactl suspend-sink 0` it soon returns. I have even updated the BIOS but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 20 13:10:59 2019 InstallationDate: Installed on 2018-11-26 (144 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 2349G4G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB9WW (2.79 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349G4G dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349G4G dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 24:FD:52:8C:5D:82 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:65823 acl:64 sco:0 events:9052 errors:0 TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1825639 Title: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. Status in bluez package in Ubuntu: New Bug description: This is the same problem in https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem persists (this T430 laptop has inbuilt Bluetooth). This makes listening to music or any audio over Bluetooth almost unbearable - while it is temporarily fixed by running `pactl suspend- sink 1 && pactl suspend-sink 0` it soon returns. I have even updated the BIOS but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 20 13:10:59 2019 InstallationDate: Installed on 2018-11-26 (144 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 2349G4G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB9WW (2.79 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349G4G dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349G4G dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 24:FD:52:8C:5D:82 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:65823 acl:64 sco:0 events:9052 errors:0 TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1825639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR
Bug isn't corrected in Kubuntu 19.04 in kernel 5.0.0-13-generic. -- 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/1796582 Title: Internal microphone not working on Lenovo Ideapad 330S-15ARR Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The internal microphone on this troublesome laptop stopped working after upgrading from Bionic to Cosmic. There is no signal from the microphone with kernel 4.18.0-7 or 4.18.0-8. This DOES work correctly with kernel 4.15.0-34 that is still present on Cosmic after the upgrade. I recommend Canonical gets this laptop for testing since a ton of stuff is troublesome on this Raven Ridge laptop. Would be a good specimen to get support for this platform improved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2295 F pulseaudio /dev/snd/controlC0: xorbit 2295 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 7 12:02:45 2018 InstallationDate: Installed on 2018-09-20 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796582/+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 1825638] Re: Lenovo Legion Y530-15ICH does not start with live usb
How to make them when loading live-usb, if you consider that the system does not boot and does not even give the command line interface? ** 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/1825638 Title: Lenovo Legion Y530-15ICH does not start with live usb Status in linux package in Ubuntu: Confirmed Bug description: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+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 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR
No, I have the Ideapad 330 (Not S)-15ARR. But I think the microphone is the same for both. -- 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/1796582 Title: Internal microphone not working on Lenovo Ideapad 330S-15ARR Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The internal microphone on this troublesome laptop stopped working after upgrading from Bionic to Cosmic. There is no signal from the microphone with kernel 4.18.0-7 or 4.18.0-8. This DOES work correctly with kernel 4.15.0-34 that is still present on Cosmic after the upgrade. I recommend Canonical gets this laptop for testing since a ton of stuff is troublesome on this Raven Ridge laptop. Would be a good specimen to get support for this platform improved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2295 F pulseaudio /dev/snd/controlC0: xorbit 2295 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 7 12:02:45 2018 InstallationDate: Installed on 2018-09-20 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796582/+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 1825632] [NEW] package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon
Public bug reported: Problem when i installing the new version. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erwan 3106 F pulseaudio /dev/snd/controlC1: erwan 3106 F pulseaudio Date: Sat Apr 20 12:37:44 2019 ErrorMessage: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon InstallationDate: Installed on 2018-10-07 (194 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=d478b832-a087-4e04-824b-57099769e24e ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 SourcePackage: linux Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) dmi.bios.date: 05/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LB.603 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LB.603:bd05/06/2016:svnASUSTeKCOMPUTERINC.:pnX555LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- 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/1825632 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon Status in linux package in Ubuntu: New Bug description: Problem when i installing the new version. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erwan 3106 F pulseaudio /dev/snd/controlC1: erwan 3106 F pulseaudio Date: Sat Apr 20 12:37:44 2019 ErrorMessage: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon InstallationDate: Installed on 2018-10-07 (194 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=d478b832-a087-4e04-824b-57099769e24e ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 SourcePackage: linux Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) dmi.bios.date:
[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
I think you already have tried to take the fans by fancontrol. I thought
if fancontrol works on this laptop then you just need to add a service
to stop fancontrol service before suspend and start it again after
suspend after small delay.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
New
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+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 1824981] Re: cifs set_oplock buffer overflow in strcat
I tried Ubuntu kernel "4.18.0-17-generic #18~18.04.1-Ubuntu". Crashed the same way on high load as the 4.15.0-47 does. Now testing 4.15.0-48 from Kai-Heng. Still haven't found the trigger for that bug. Seems to be load related - we're having five servers each running many threads reading/writing gigabytes of data to the share. There might be even 100+ processes trying to set a lock one the same file at the same time. Seems to get better if we reduce the number of parallel threads. -- 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/1824981 Title: cifs set_oplock buffer overflow in strcat Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.2 LTS Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM top - 12:39:53 up 3:41, 4 users, load average: 66.19, 64.06, 76.90 Tasks: 1076 total, 1 running, 675 sleeping, 12 stopped, 1 zombie %Cpu(s): 28.2 us, 0.3 sy, 0.0 ni, 71.5 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 39483801+total, 24077185+free, 57428284 used, 96637872 buff/cache KiB Swap: 999420 total, 999420 free,0 used. 33477683+avail Mem We've seen the following bug many times since we introduced new machines running Ubuntu 18. Wasn't an issue older machines running Ubuntu 16. Three different machines are affected, so it's rather not a hardware issue. | detected buffer overflow in strcat | [ cut here ] | kernel BUG at /build/linux-6ZmFRN/linux-4.15.0/lib/string.c:1052! | invalid opcode: [#1] SMP PTI | Modules linked in: [...] | Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 1.6.11 11/20/2018 | RIP: 0010:fortify_panic+0x13/0x22 | [...] | Call Trace: | smb21_set_oplock_level+0x147/0x1a0 [cifs] | smb3_set_oplock_level+0x22/0x90 [cifs] | smb2_set_fid+0x76/0xb0 [cifs] | cifs_new_fileinfo+0x259/0x390 [cifs] | ? smb2_get_lease_key+0x40/0x40 [cifs] | ? cifs_new_fileinfo+0x259/0x390 [cifs] | cifs_open+0x3db/0x8d0 [cifs] | [...] (Full dmesg output attached) After hitting this bug there are many cifs related dmesg entries, processes lock up and eventually the systems freezes. The share is mounted using: //server/share /mnt/server/ cifs defaults,auto,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777,credentials=/root/passwords/share,domain=myDomain,uid=myUser,gid=10513,mfsymlinks Currently we're testing the cifs mount options "cache=none" as the bug seems to be oplock related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824981/+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 1824981] Re: cifs set_oplock buffer overflow in strcat
Here are some details from proc what is happening on our servers. Both running 4.15.0-47-generic. server13 / uptime 2 days # cat /proc/fs/cifs/Stats Resources in use CIFS Session: 1 Share (unique mount targets): 2 SMB Request/Response Buffer: 1 Pool size: 5 SMB Small Req/Resp Buffer: 1 Pool size: 30 Operations (MIDs): 0 7 session 14 share reconnects Total vfs operations: 7223031 maximum at one time: 102 1) \\server\share SMBs: 13497286 Negotiates: 0 sent 0 failed SessionSetups: 0 sent 0 failed Logoffs: 0 sent 0 failed TreeConnects: 502 sent 0 failed TreeDisconnects: 0 sent 0 failed Creates: 0 sent 466291 failed Closes: 0 sent 2 failed Flushes: 0 sent 0 failed Reads: 0 sent 19 failed Writes: 0 sent 0 failed Locks: 0 sent 0 failed IOCTLs: 0 sent 0 failed Cancels: 0 sent 0 failed Echos: 0 sent 0 failed QueryDirectories: 0 sent 14011 failed ChangeNotifies: 0 sent 0 failed QueryInfos: 0 sent 0 failed SetInfos: 0 sent 0 failed OplockBreaks: 0 sent 16 failed server15 / uptime 5 days # cat /proc/fs/cifs/Stats Resources in use CIFS Session: 1 Share (unique mount targets): 2 SMB Request/Response Buffer: 1 Pool size: 5 SMB Small Req/Resp Buffer: 1 Pool size: 30 Operations (MIDs): 0 1 session 2 share reconnects Total vfs operations: 118861442 maximum at one time: 52 1) \\server\share SMBs: 122017565 Negotiates: 0 sent 0 failed SessionSetups: 0 sent 0 failed Logoffs: 0 sent 0 failed TreeConnects: 19970 sent 0 failed TreeDisconnects: 0 sent 0 failed Creates: 0 sent 738187 failed Closes: 0 sent 0 failed Flushes: 0 sent 0 failed Reads: 0 sent 41 failed Writes: 0 sent 0 failed Locks: 0 sent 0 failed IOCTLs: 0 sent 0 failed Cancels: 0 sent 0 failed Echos: 0 sent 0 failed QueryDirectories: 0 sent 9776 failed ChangeNotifies: 0 sent 0 failed QueryInfos: 0 sent 0 failed SetInfos: 0 sent 0 failed OplockBreaks: 0 sent 3301 failed -- 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/1824981 Title: cifs set_oplock buffer overflow in strcat Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.2 LTS Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM top - 12:39:53 up 3:41, 4 users, load average: 66.19, 64.06, 76.90 Tasks: 1076 total, 1 running, 675 sleeping, 12 stopped, 1 zombie %Cpu(s): 28.2 us, 0.3 sy, 0.0 ni, 71.5 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 39483801+total, 24077185+free, 57428284 used, 96637872 buff/cache KiB Swap: 999420 total, 999420 free,0 used. 33477683+avail Mem We've seen the following bug many times since we introduced new machines running Ubuntu 18. Wasn't an issue older machines running Ubuntu 16. Three different machines are affected, so it's rather not a hardware issue. | detected buffer overflow in strcat | [ cut here ] | kernel BUG at /build/linux-6ZmFRN/linux-4.15.0/lib/string.c:1052! | invalid opcode: [#1] SMP PTI | Modules linked in: [...] | Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 1.6.11 11/20/2018 | RIP: 0010:fortify_panic+0x13/0x22 | [...] | Call Trace: | smb21_set_oplock_level+0x147/0x1a0 [cifs] | smb3_set_oplock_level+0x22/0x90 [cifs] | smb2_set_fid+0x76/0xb0 [cifs] | cifs_new_fileinfo+0x259/0x390 [cifs] | ? smb2_get_lease_key+0x40/0x40 [cifs] | ? cifs_new_fileinfo+0x259/0x390 [cifs] | cifs_open+0x3db/0x8d0 [cifs] | [...] (Full dmesg output attached) After hitting this bug there are many cifs related dmesg entries, processes lock up and eventually the systems freezes. The share is mounted using: //server/share /mnt/server/ cifs defaults,auto,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777,credentials=/root/passwords/share,domain=myDomain,uid=myUser,gid=10513,mfsymlinks Currently we're testing the cifs mount options "cache=none" as the bug seems to be oplock related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824981/+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 1756226] Re: nvidia-driver-390 fails to start GUI
...:~$ apt-cache policy nvidia-390 nvidia-390: Installeret: 390.87-0ubuntu0~gpu18.04.2 Kandidat:390.87-0ubuntu0~gpu18.04.2 .:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installeret: 1:0.5.2.3 Kandidat:1:0.5.2.3 I seem be having this issue ? how can i verify? if i nvidia active i get black screen with a cursor indicated in top left, and i hear the ubunti logon sound. and then nothing. i have to do: sudo prime-select intel to get back in to GUI please help -- 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/1756226 Title: nvidia-driver-390 fails to start GUI Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: I was the original person who posted Ubuntu [Bug 1752053] nvidia-390 fails to boot graphical display. I was able to use the fix on my laptop successfully. However, my desktop computer has 2 GTX1080 Ti cards and the fix does not work. After I boot my desktop computer, I do not get a login screen. I get a blank screen with a flickering text cursor in the top left corner. I am running Bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+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 1825678] [NEW] Intel wifi fails to resume after suspend
Public bug reported: Yesterday my WiFi card(Intel Wireless 3165) didn't show up on resuming the laptop from a suspend state. I rebooted a few times and found that the situation hadn't changed. Rebooting and choosing older kernels didn't help. I ran lspci and discovered my WiFi card was missing in the output. I shut down the laptop assuming my WiFi card suffered a hardware failure. In the evening, after starting up from a full shutdown, the WiFi card worked again. Today, the situation happened again, but I approached the debugging more methodically. I looked at nmcli and found it still saw my wifi card but found it unavailable. lspci could still see the Wifi card in the last position. I analyzed dmesg output and discovered an iwlwifi crash(the relevant part of dmesg is provided in wifi_dmesg.txt attachment). Then, I rebooted the laptop. This didn't fix the issue and from a quick look at lspci, the wifi card was missing again. So I repeated the procedure that worked the previous day - full shutdown, wait 10 seconds, then start up. This restored my WiFi card to a working state and allowed me to file this bug report. I will be happy to provide any further information that could read to fixing this issue. Additional information: 1. lsb_release -rd Description:Peppermint 8 Eight Release:8 Yes, that's technically not Ubuntu. However, Peppermint does not modify Ubuntu's kernel, and Peppermint 8 is based on Ubuntu 16.04 Xenial Xerus. 2. apt-cache policy linux-firmware linux-firmware: Installed: 1.157.21 Candidate: 1.157.21 Version table: *** 1.157.21 500 500 http://pl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 1.157 500 500 http://pl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu xenial/main i386 Packages 3. I expected suspend and resume to work like they did for the last two years 4. iwlwifi crashed and dumped its registers. 5. Inxi, in case it's useful(many other bug reporting websites ask for it): inxi -Fz System:Host: PiDell Kernel: 4.15.0-47-generic x86_64 (64 bit) Desktop: N/A Distro: Peppermint Eight Machine: System: Dell (portable) product: Inspiron 15 7000 Gaming Mobo: Dell model: 065C71 v: A00 Bios: Dell v: 1.7.0 date: 05/08/2018 CPU: Quad core Intel Core i7-7700HQ (-HT-MCP-) cache: 6144 KB clock speeds: max: 3800 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz 5: 800 MHz 6: 800 MHz 7: 800 MHz 8: 800 MHz Graphics: Card-1: Intel Device 591b Card-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] Display Server: X.Org 1.19.6 driver: nvidia Resolution: 1920x1080@60.00hz GLX Renderer: GeForce GTX 1050 Ti/PCIe/SSE2 GLX Version: 4.6.0 NVIDIA 396.54 Audio: Card Intel CM238 HD Audio Controller driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k4.15.0-47-generic Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 IF: enp2s0 state: down mac: Card-2: Intel Wireless 3165 driver: iwlwifi IF: wlp3s0 state: up mac: Drives:HDD Total Size: 1256.3GB (27.6% used) ID-1: /dev/sda model: Micron_1100_SATA size: 256.1GB ID-2: /dev/sdb model: TOSHIBA_MQ01ABD1 size: 1000.2GB Partition: ID-1: / size: 46G used: 38G (87%) fs: ext4 dev: /dev/sdb3 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 51.0C mobo: N/A gpu: 48C Fan Speeds (in rpm): cpu: N/A Info: Processes: 258 Uptime: 51 min Memory: 2152.2/15906.5MB Client: Shell (bash) inxi: 2.2.35 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: iwlwifi xenial ** Attachment added: "dmesg log" https://bugs.launchpad.net/bugs/1825678/+attachment/5257399/+files/wifi_dmesg.txt ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** No longer affects: network-manager (Ubuntu) -- 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/1825678 Title: Intel wifi fails to resume after suspend Status in linux-firmware package in Ubuntu: New Bug description: Yesterday my WiFi card(Intel Wireless 3165) didn't show up on resuming the laptop from a suspend state. I rebooted a few times and found that the situation hadn't changed. Rebooting and choosing older kernels didn't help. I ran lspci and discovered my WiFi card was missing in the output. I shut down the
[Kernel-packages] [Bug 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels
Unsubscribing the Ubuntu Sponsors Team as there is nothing to sponsor.
--
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/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile package in Ubuntu:
Opinion
Status in makedumpfile source package in Xenial:
In Progress
Status in makedumpfile source package in Bionic:
In Progress
Status in makedumpfile source package in Cosmic:
In Progress
Status in makedumpfile source package in Disco:
Opinion
Bug description:
[Impact]
Crash kernels include an obsolete "nousb" parameter by default, which can
cause confusion since it's been deprecated in newer kernel versions.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line appears to be saying the
opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is extremely low, since it doesn't need any changes
in makedumpfile code and we're only removing an already ineffective parameter
from the crashkernel cmdline. Nonetheless, patches will be tested with
autopkgtests and normal kdump use-case scenarios.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
Confirmed during upgrade of clean fully-updated Ubuntu MATE 18.10 to Ubuntu MATE 19.04, so I have marked Ubuntu MATE as affected by this bug. ** Also affects: ubuntu-mate 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/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+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 1809934] Re: AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809934 Title: AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot Status in linux package in Ubuntu: Expired Bug description: CPU: AMD Ryzen 5 2400G / AMD Ryzen 3 2200G Version: Ubuntu 18.04.1 Desktop (AMD64) Kernel: 4.15.0-43 generic Mainboard: ASUS Prime X370-Pro (4207), ASRock B450 Pro4 (1.80), MSI B350 Tomahawk (7A34v1K), Gigabyte GA-AB350M-Gaming3 (F24c) Detailed information: AMD AGESA version "PinnaclePI-AM4 1.0.0.6" based firmware is released by many major mainboard manufacturers lately. However, this 1.0.0.6 based firmware with Raven Ridge processors (2200G, 2400G and more) cause system hangs on boot if a system is running 4.15.0 kernel. If install kernel version 4.18.0-13-generic from "linux-image-generic- hwe-18.04-edge" has no issue. Here is boot messages output (dumped via serial port and truncated): [4.385021] [drm] ring test on 5 succeeded in 3 usecs [4.385030] [drm] ring test on 6 succeeded in 2 usecs [4.385035] [drm] ring test on 7 succeeded in 1 usecs [4.385044] [drm] ring test on 8 succeeded in 2 usecs [4.385090] [drm] ring test on 10 succeeded in 2 usecs [5.406001] clocksource: timekeeping watchdog on CPU2: Marking clocksource 'tsc' as unstable because the skew is too large: [5.406002] clocksource: 'hpet' wd_now: 5152d87 wd_last: 40b14df mask: [5.406004] clocksource: 'tsc' cs_now: f4c92bc9d cs_last: ebf5adbce mask: [5.406006] tsc: Marking TSC unstable due to clocksource watchdog [5.406014] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [5.406015] sched_clock: Marking unstable (5406009219, 0)<-(5548358599, -142345214) [7.906021] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [9.156104] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: writing more dwords to the ring than expected! [ 11.656035] ata2.00: ATA-8: TOSHIBA DT01ACA200, MX4OABB0, max UDMA/133 [ 32.204004] watchdog: BUG: soft lockup - CPU#2 stuck for 21s! [kworker/2:1:60] [ 32.204005] Modules linked in: hid_logitech_hidpp hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 amdgpu(+) chash i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect uas sysimgblt fb_sys_fops drm r8169 usb_storage i2c_piix4 mii ahci libahci wmi video gpio_a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809934/+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 1816660] Re: Extremely slow graphical desktop startup process Ubuntu 18.10
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816660 Title: Extremely slow graphical desktop startup process Ubuntu 18.10 Status in linux package in Ubuntu: Expired Bug description: I have experienced a stubborn issue after upgrading my Ubuntu from 18.04 to 18.10. Every time I would like to login into my system via lightdm the login process takes a lot of time (more than 2 minutes). This is definitely an issue because this process took about half minutes in my previous version of Ubuntu. The issues is affected both GNOME and XFCE. I have tried resolve issues provided by journalctl but I did not found solution regarding most of those problem. I am sure this problem affects many users. I have been searching solution and also workaround such as install another desktop environment would be appreciated. I have tried - removing xdg-desktop-portal - removing gnome-keyring Both of them issued error. - reinstall lightdm None of them was successful. critical chain graphical.target @2min 33.766s └─multi-user.target @2min 33.763s └─smbd.service @2min 33.053s +709ms └─winbind.service @2min 28.004s +5.044s └─network.target @38.625s └─NetworkManager.service @24.995s +13.497s └─dbus.service @24.548s └─basic.target @24.409s └─sockets.target @24.407s └─cups.socket @24.404s └─sysinit.target @24.187s └─haveged.service @24.184s └─apparmor.service @16.637s +7.540s └─local-fs.target @16.630s └─local-fs-pre.target @16.628s └─keyboard-setup.service @5.634s +10.986s └─systemd-journald.socket @5.572s └─system.slice @5.483s └─-.slice @5.483s hardware 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Complex 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6/R7 Graphics] 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri HDMI/DP Audio Controller 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1425 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port 00:03.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port 00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40) 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 16) 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11) 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40) 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 5 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Jet PRO [Radeon R5 M230] 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet
[Kernel-packages] [Bug 1776563]
Dear kernel developers, the ACPI seems to be OK from kernel v 5.1 but only with using the ivrs_ioapic kernel parameters. This is almos a constant failure by these notebooks. Couldn't this be hardcoded somehow into the kernel? This bug is almost one year old and we know how it can be fixed but we are not kernel developers to make/create the proper patch. Could you please help us? Thanks, Richard -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
