[Kernel-packages] [Bug 1739300] Re: The header files fcntl.h and linux/fcntl.h are incompatible
Setting the status to Confirmed, though i am the reporter.
This is slightly inconsistent. Brain hurts.
--
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/1739300
Title:
The header files fcntl.h and linux/fcntl.h are incompatible
Status in glibc package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The program try.c, below, does not compile.
Though with HAVE_ARCH_STRUCT_FLOCK and HAVE_ARCH_STRUCT_FLOCK64 defined, it
compiles.
But then fails again to compile, when _GNU_SOURCE is also defined.
I expect this to compile in all three cases.
$ cat try.c
//#define _GNU_SOURCE
//#define HAVE_ARCH_STRUCT_FLOCK
//#define HAVE_ARCH_STRUCT_FLOCK64
#include
#include
int main(int argc, char *argv[]){}
$ gcc try.c
In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0,
from /usr/include/linux/fcntl.h:4,
from try.c:5:
/usr/include/asm-generic/fcntl.h:195:8: error: redefinition of ‘struct flock’
struct flock {
^
In file included from /usr/include/fcntl.h:35:0,
from try.c:4:
/usr/include/x86_64-linux-gnu/bits/fcntl.h:35:8: note: originally defined here
struct flock
^
$ gcc -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c ## this is ok
$ gcc -D_GNU_SOURCE -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c
In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0,
from /usr/include/linux/fcntl.h:4,
from try.c:5:
/usr/include/asm-generic/fcntl.h:155:8: error: redefinition of ‘struct
f_owner_ex’
struct f_owner_ex {
^~
In file included from /usr/include/x86_64-linux-gnu/bits/fcntl.h:61:0,
from /usr/include/fcntl.h:35,
from try.c:4:
/usr/include/x86_64-linux-gnu/bits/fcntl-linux.h:267:8: note: originally
defined here
struct f_owner_ex
^~
$ gcc --version | head -1
gcc (Ubuntu 7.2.0-8ubuntu3) 7.2.0
$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
$ dpkg -S /usr/include/x86_64-linux-gnu/bits/fcntl.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/bits/fcntl.h
# Package: libc6-dev
# Version: 2.26-0ubuntu2
$ dpkg -S /usr/include/x86_64-linux-gnu/asm/fcntl.h
linux-libc-dev:amd64: /usr/include/x86_64-linux-gnu/asm/fcntl.h
# Package: linux-libc-dev
# Version: 4.13.0-19.22
Regards, Mike
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739300/+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 1739300] Re: The header files fcntl.h and linux/fcntl.h are incompatible
due to the nature of the issue i have encountered, i am unable to run
apport-collect 1739300
and have changed the bug status to 'Confirmed' (for the second time).
** Changed in: glibc (Ubuntu)
Status: New => Confirmed
** 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/1739300
Title:
The header files fcntl.h and linux/fcntl.h are incompatible
Status in glibc package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The program try.c, below, does not compile.
Though with HAVE_ARCH_STRUCT_FLOCK and HAVE_ARCH_STRUCT_FLOCK64 defined, it
compiles.
But then fails again to compile, when _GNU_SOURCE is also defined.
I expect this to compile in all three cases.
$ cat try.c
//#define _GNU_SOURCE
//#define HAVE_ARCH_STRUCT_FLOCK
//#define HAVE_ARCH_STRUCT_FLOCK64
#include
#include
int main(int argc, char *argv[]){}
$ gcc try.c
In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0,
from /usr/include/linux/fcntl.h:4,
from try.c:5:
/usr/include/asm-generic/fcntl.h:195:8: error: redefinition of ‘struct flock’
struct flock {
^
In file included from /usr/include/fcntl.h:35:0,
from try.c:4:
/usr/include/x86_64-linux-gnu/bits/fcntl.h:35:8: note: originally defined here
struct flock
^
$ gcc -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c ## this is ok
$ gcc -D_GNU_SOURCE -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c
In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0,
from /usr/include/linux/fcntl.h:4,
from try.c:5:
/usr/include/asm-generic/fcntl.h:155:8: error: redefinition of ‘struct
f_owner_ex’
struct f_owner_ex {
^~
In file included from /usr/include/x86_64-linux-gnu/bits/fcntl.h:61:0,
from /usr/include/fcntl.h:35,
from try.c:4:
/usr/include/x86_64-linux-gnu/bits/fcntl-linux.h:267:8: note: originally
defined here
struct f_owner_ex
^~
$ gcc --version | head -1
gcc (Ubuntu 7.2.0-8ubuntu3) 7.2.0
$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
$ dpkg -S /usr/include/x86_64-linux-gnu/bits/fcntl.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/bits/fcntl.h
# Package: libc6-dev
# Version: 2.26-0ubuntu2
$ dpkg -S /usr/include/x86_64-linux-gnu/asm/fcntl.h
linux-libc-dev:amd64: /usr/include/x86_64-linux-gnu/asm/fcntl.h
# Package: linux-libc-dev
# Version: 4.13.0-19.22
Regards, Mike
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739300/+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 1770178] Re: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Yes, sorry. I just hit send on the bug report tool without noticing /boot was full. On Thu, May 10, 2018, 10:11 AM Joseph Salisbury, < joseph.salisb...@canonical.com> wrote: > You may need to run the following from a terminal: > > sudo apt-get install -f > sudo apt-get clean > sudo apt-get update > > Then re-install the package or updates. > > If that does not resolve your issue, please mark the bug as "Confirmed" > > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Low > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1770178 > > Title: > package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to > install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools > exited with return code 1 > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I came in this morning, and the bug reporter tool was complaining > about this. > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: linux-image-extra-4.4.0-124-generic 4.4.0-124.148 > ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 > Uname: Linux 4.4.0-122-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.1-0ubuntu2.16 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: u388mw 2403 F pulseaudio >/dev/snd/controlC0: u388mw 2403 F pulseaudio > Date: Wed May 9 06:30:24 2018 > ErrorMessage: subprocess installed post-installation script returned > error exit status 1 > HibernationDevice: RESUME=UUID=2cfbf33c-ccf2-4fa0-95fd-c3242e7ca36a > InstallationDate: Installed on 2018-02-12 (85 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: Synergio System Product Name > ProcFB: 0 EFI VGA > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-122-generic.efi.signed > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17 > RfKill: > > SourcePackage: linux > Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed > to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools > exited with return code 1 > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/23/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 0805 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: P8H61-M LE/CSM > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev x.0x > dmi.chassis.asset.tag: Asset-1234567890 > dmi.chassis.type: 3 > dmi.chassis.vendor: Chassis Manufacture > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr0805:bd12/23/2011:svnSynergio:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLE/CSM:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: > dmi.product.name: System Product Name > dmi.product.version: System Version > dmi.sys.vendor: Synergio > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770178/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770178 Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Incomplete Bug description: I came in this morning, and the bug reporter tool was complaining about this. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u388mw 2403 F pulseaudio /dev/snd/controlC0: u388mw 2403 F pulseaudio Date: Wed May 9 06:30:24 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=2cfbf33c-ccf2-4fa0-95fd-c3242e7ca36a InstallationDate: Installed on 2018-02-12 (85 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Synergio System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-122-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet
[Kernel-packages] [Bug 1770178] Re: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770178/+attachment/5136746/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770178 Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Confirmed Bug description: I came in this morning, and the bug reporter tool was complaining about this. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u388mw 2403 F pulseaudio /dev/snd/controlC0: u388mw 2403 F pulseaudio Date: Wed May 9 06:30:24 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=2cfbf33c-ccf2-4fa0-95fd-c3242e7ca36a InstallationDate: Installed on 2018-02-12 (85 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Synergio System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-122-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LE/CSM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd12/23/2011:svnSynergio:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLE/CSM:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: Synergio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770178/+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 1770178] [NEW] package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: I came in this morning, and the bug reporter tool was complaining about this. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u388mw 2403 F pulseaudio /dev/snd/controlC0: u388mw 2403 F pulseaudio Date: Wed May 9 06:30:24 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=2cfbf33c-ccf2-4fa0-95fd-c3242e7ca36a InstallationDate: Installed on 2018-02-12 (85 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Synergio System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-122-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LE/CSM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd12/23/2011:svnSynergio:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLE/CSM:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: Synergio ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package xenial ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1770178/+attachment/5136726/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770178 Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Confirmed Bug description: I came in this morning, and the bug reporter tool was complaining about this. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u388mw 2403 F pulseaudio /dev/snd/controlC0: u388mw 2403 F pulseaudio Date: Wed May 9 06:30:24 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=2cfbf33c-ccf2-4fa0-95fd-c3242e7ca36a InstallationDate: Installed on 2018-02-12 (85 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Synergio System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-122-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LE/CSM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1768211] [NEW] norton setup
Public bug reported: Online Norton Help and Support by PC Planet PCPlanet's Certified Technicians can help you scan, detect, and remove all types of viruses and malware in your computer. Our techies have years of experience and the expertise in providing support for antivirus and fixing computer virus problems online through remote connection. Our support services are available through phone, chat and email. Just call us at 1-888-406-4114 to chat with a certified expert and get instant support for Norton Antivirus to make your computer virus free.http://pcplanet247.com/www-norton-com-setup//;>Norton Support Get Started http://pcplanet247.com/www-norton-com-setup//;>Norton Support http://pcplanet247.com/www-norton-com-setup//;>Norton Support 2016 is a version of Norton Setup productivity suite came after Norton 2013. This version is available for PCs (such as Norton Security & 360 2016) and Macs (such as Norton Delux & Premier Edition 2016 for Mac). Along with all the features of previous versions, Norton includes additional ribbon buttons, enhanced collaboration, mentions, new & improved connection options, publish to docs.com, publish to power BI, researcher, suggest a feature, text highlighter, zoom for Norton and staying in the loop. To get Norton 2016, you need to buy, download, install and then activate it. To perform these processes, there is a series of steps that needs to be followed. You can purchase Norton Antivirus setup offline or online. Upon online purchase via norton.com/setup, you will receive a 25-digit product key on your registered email ID. Upon offline purchase, you will receive an Norton retail card, on the back of which this 25-digit key is mentioned. Keep this key secure with you, as you will need it later at the time of Norton subscription activation or while logging in to your account. http://pcplanet247.com/www-norton-com-setup//;>Norton Support http://pcplanet247.com/www-norton-com-setup//;>Norton Support Norton Support NORTON SETUP Visithttp://pcplanet247.com/www-norton-com-setup//;>Norton Support and sign in to your Norton account or create a new account (new users) Enter Norton product key Select your subscription and click download button to begin the downloading process There, you will get the choice to choose from different versions and languages Depending upon your browser, run the downloaded setup Click Run (in Edge or Internet Explorer), Setup (in Chrome), or Save File (in Firefox) After installation, open any of the application of MS Office 2016 Here, you will be see a Norton Antivirus activation wizard Click activate and enter the same product key, if asked Follow the on-screen instructions to complete activation NORTON SETUP FOR MAC First two steps as same with those listed in PC Now, log in to your Norton account and install Norton setup 2016 For this, you have to open My Account and under the name of your subscription, choose Install On the next window, select install under Install information This will begin downloading the installation package Once the download completes, open Finder and go to Downloads Double-click Norton_Setup_2016_Installer.pkg Click continue Review the software license agreement Choose agree to the terms of the software license agreement Select how you want to install the Norton2016 and click continue Change your install location, if you want and then click Install Enter your Mac login password and click Install software Click the Launchpad icon in the dock to display all your applications Click the Norton icon and then click Get Started followed by What’s new This will begin activation process Enter the product key, if asked Follow the on-screen instructions to finish activation It’s good to go! Norton Setup 2016 for Business NORTON SETUP FOR PC Sign in with your work or school account by visiting http://pcplanet247.com/www-norton-com-setup//;>Norton Support >From the drop-down list, choose your preferred language and accept the default >to install 32-bit or select Advanced and choose 4-bit Choose Install Click Run, Setup or Save file option, depending upon your browser You will be prompted “Do you want to allow this app to make changes to your device?” Click Yes This will begin the installation You’re all set! Activate it and you will be able to access all its applications For Mac Log in with your School or work account at norton setup On the Norton page, select Install option available under Install Norton 2016 for Mac This will begin downloading the installer package Open Finder, go to Downloads, and double-click Norton_Setup_2016_Installer.pkg Rest of the steps are same as those listed above in Norton 2016 for home (Mac) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: norton setup -- 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/1768211 Title: norton setup
[Kernel-packages] [Bug 1768162] [NEW] kernel crashes during boot unless IOMMU is disabled on AMD Cpu
Public bug reported: Previous - IOMMU was enabled under Ubuntu 16.04 LTS Kernel 4.4 - No Issues Current - After upgrading to 18.04 with kernel 4.15 systems crashes with IOMMU enabled - Disabling IOMMU within the BIOS allow booting with 4.15 kernel - Enabling IOMMU and switching to 4.4 boots fine as well under 18.04 Not Sure if this is the same as bug 1747463 Version Log Ubuntu 4.15.0-20.21-generic 4.15.17 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 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 20:05:32 2018 InstallationDate: Installed on 2015-06-11 (1054 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Patch added: "bug.log" https://bugs.launchpad.net/bugs/1768162/+attachment/5131102/+files/bug.log -- 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/1768162 Title: kernel crashes during boot unless IOMMU is disabled on AMD Cpu Status in linux-signed package in Ubuntu: New Bug description: Previous - IOMMU was enabled under Ubuntu 16.04 LTS Kernel 4.4 - No Issues Current - After upgrading to 18.04 with kernel 4.15 systems crashes with IOMMU enabled - Disabling IOMMU within the BIOS allow booting with 4.15 kernel - Enabling IOMMU and switching to 4.4 boots fine as well under 18.04 Not Sure if this is the same as bug 1747463 Version Log Ubuntu 4.15.0-20.21-generic 4.15.17 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 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 20:05:32 2018 InstallationDate: Installed on 2015-06-11 (1054 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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/1768162/+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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
I've just rebooted five times without any lock ups. I'll leave it running, and see what happens. -- 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/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+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 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)
@tyhicks, I don't have an Artful test system, but I confirmed on Xenial (4.4.0-116-generic) that `apparmor=0` is a workaround, without the `noibpb` option and with intel-microcode version 3.20180312.0~ubuntu16.04.1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Xenial: Confirmed Status in linux source package in Xenial: Confirmed Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. ## Workaround ## 1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary avoid the problem: https://wiki.ubuntu.com/Kernel/KernelBootParameters 2. Install the previous version of package from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb 3. (Optional) Hold the package so that it won't be upgraded accidentally sudo apt-mark hold intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Still not working on 4.16.0-rc6. Is there actually development going on concering this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
I'm afraid that 4.4.0-117-generic #141 - Ubuntu SMP Tue Mar 13 11:58:07 doesn't cure the problem for me. I still get the Watchdog Hard Lockups. -- 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/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
That one, 47a0... , failed. Unfortunately, that is the last one that I can test for you until next week, as I have to go away for a few days. I hope that someone else can help. -- 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/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
Linux golf 4.4.0-110-generic #133~lp1745349Commit49bb7a3cbf5 SMP Tue Mar 6 16:37:00 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux doesn't seem to have the problem,. -- 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/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
That one (e233e...) 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/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
That one, Linux golf 4.4.0-110-generic #133~lp1745349Commit7de295e2a47849 SMP Tue Mar 6 13:00:57 UTC 20 x86_64 x86_64 x86_64 GNU/Linux doesn't appear to have the problem. It has been running for a lot longer than it usually does. -- 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/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
I'm definitely running from your 110 kernel, and it exhibits the Watchdog Hard Lockup problem, when running without noipbp. -- 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/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
uname -a shows:- Linux golf 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux so I obviously haven't implemented your kernel correctly. -- 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/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+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 1627474] Re: ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)
I hope this is helpful additional data. I run Ubuntu 16.04 on a Dell XPS 15 9560. I've been using a bluetooth mouse almost daily for over a month with no problems. I left the computer on, but didn't use it for several days. I then closed the lid (causing a suspend state), later opened the lid to a frozen OS (the clock in the system tray was frozen to about the time I closed the lid). I had to hard-power-off, and have since rebooted, installed updates, rebooted again, and the network seems to work fine, but the bluetooth is no longer recognized at all. I got the same errors reported above after powering up post-freeze. The syslog with the errors is attached. It is possible that my problem my have arisen from corruption to something when the machine froze, and is not the same consistent kernel bug described above. In either case, I'm hopeful the information posted here and attached provides value. ** Attachment added: "syslog.1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627474/+attachment/5070022/+files/syslog.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/1627474 Title: ath10k_pci :03:00.0: firmware crashed! (uuid n/a) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: The wireless card in my Acer V3-372-587T suffers from firmware crashes regularly (every 5-10mins approx). $ lsb_release -rd Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Checking dmesg I see: $ dmesg | grep ath10k [91/214] [7.773800] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [8.123875] request_firmware: ath10k/pre-cal-pci-:03:00.0.bin [8.126477] ath10k_pci :03:00.0: Direct firmware load for ath10k/pre-cal-pci-:03:00.0.bin fa$ led with error -2 [8.126481] request_firmware: ath10k/cal-pci-:03:00.0.bin [8.126492] ath10k_pci :03:00.0: Direct firmware load for ath10k/cal-pci-:03:00.0.bin failed with error -2 [8.126493] request_firmware: ath10k/QCA6174/hw3.0/firmware-5.bin [8.127095] ath10k_pci :03:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin fa$ led with error -2 [8.127098] ath10k_pci :03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.$ in': -2 [8.127101] request_firmware: ath10k/QCA6174/hw3.0/firmware-4.bin [8.129458] ath10k_pci :03:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 105b:e09$ [8.129460] ath10k_pci :03:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 [8.129954] ath10k_pci :03:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowla$ ,ignore-otp,no-4addr-pad crc32 75dee6c5 [8.195123] request_firmware: ath10k/QCA6174/hw3.0/board-2.bin [8.198141] ath10k_pci :03:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 [ 10.338326] ath10k_pci :03:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypt$ 1 [ 10.436186] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0 [ 319.064117] ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [ 319.064164] ath10k_pci :03:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 105b:e09$ [ 319.064174] ath10k_pci :03:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 [ 319.066828] ath10k_pci :03:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowla$ ,ignore-otp,no-4addr-pad crc32 75dee6c5 [ 319.068042] ath10k_pci :03:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 [ 319.068055] ath10k_pci :03:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypt$ 1 [ 319.070104] ath10k_pci :03:00.0: firmware register dump: [ 319.070127] ath10k_pci :03:00.0: [00]: 0x0503 0x15B3 0x009860FA 0x00955B31 [ 319.070139] ath10k_pci :03:00.0: [04]: 0x009860FA 0x00060730 0x0004 0x0040E8A0 [ 319.070148] ath10k_pci :03:00.0: [08]: 0x00498110 0x00955A00 0x000B 0x0040 [ 319.070158] ath10k_pci :03:00.0: [12]: 0x0009 0x 0x00952CD0 0x00952CE6 [ 319.070167] ath10k_pci :03:00.0: [16]: 0x00952CC4 0x0091080D 0x 0x0091080D [ 319.070176] ath10k_pci :03:00.0: [20]: 0x409860FA 0x0040E7E8 0x 0x0041E0DC [ 319.070195] ath10k_pci :03:00.0: [24]: 0x800B5A1D 0x0040E848 0x000F 0xC09860FA [ 319.070214] ath10k_pci :03:00.0: [28]: 0x809B3230 0x0040E948 0x0018 0x004313DC [ 319.070231] ath10k_pci :03:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9BC 0x00429548 [ 319.070246] ath10k_pci :03:00.0: [36]: 0x8091D252 0x0040E9B8 0x 0x0001 [ 319.070255] ath10k_pci :03:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 0x00429C10 [ 319.070264]
[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
I'm afraid that I am not an expert at Ubuntu. I think that I have installed your test kernel correctly, but I don't know how to prove it. I used sudo dpkg -i *.deb . If I have installed it correctly, then it doesn't cure the problem. It runs fine with noibpb, but fails in the same way if I try to run without it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+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 1739300] Re: The header files fcntl.h and linux/fcntl.h are incompatible
** Changed in: linux (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739300
Title:
The header files fcntl.h and linux/fcntl.h are incompatible
Status in glibc package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Bug description:
The program try.c, below, does not compile.
Though with HAVE_ARCH_STRUCT_FLOCK and HAVE_ARCH_STRUCT_FLOCK64 defined, it
compiles.
But then fails again to compile, when _GNU_SOURCE is also defined.
I expect this to compile in all three cases.
$ cat try.c
//#define _GNU_SOURCE
//#define HAVE_ARCH_STRUCT_FLOCK
//#define HAVE_ARCH_STRUCT_FLOCK64
#include
#include
int main(int argc, char *argv[]){}
$ gcc try.c
In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0,
from /usr/include/linux/fcntl.h:4,
from try.c:5:
/usr/include/asm-generic/fcntl.h:195:8: error: redefinition of ‘struct flock’
struct flock {
^
In file included from /usr/include/fcntl.h:35:0,
from try.c:4:
/usr/include/x86_64-linux-gnu/bits/fcntl.h:35:8: note: originally defined here
struct flock
^
$ gcc -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c ## this is ok
$ gcc -D_GNU_SOURCE -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c
In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0,
from /usr/include/linux/fcntl.h:4,
from try.c:5:
/usr/include/asm-generic/fcntl.h:155:8: error: redefinition of ‘struct
f_owner_ex’
struct f_owner_ex {
^~
In file included from /usr/include/x86_64-linux-gnu/bits/fcntl.h:61:0,
from /usr/include/fcntl.h:35,
from try.c:4:
/usr/include/x86_64-linux-gnu/bits/fcntl-linux.h:267:8: note: originally
defined here
struct f_owner_ex
^~
$ gcc --version | head -1
gcc (Ubuntu 7.2.0-8ubuntu3) 7.2.0
$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
$ dpkg -S /usr/include/x86_64-linux-gnu/bits/fcntl.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/bits/fcntl.h
# Package: libc6-dev
# Version: 2.26-0ubuntu2
$ dpkg -S /usr/include/x86_64-linux-gnu/asm/fcntl.h
linux-libc-dev:amd64: /usr/include/x86_64-linux-gnu/asm/fcntl.h
# Package: linux-libc-dev
# Version: 4.13.0-19.22
Regards, Mike
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739300/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Does not work on 4.16.0-041600rc1-lowlatency on my YEPO 737S. I never had it working a bit, whichever kernel i booted. `dmesg` output is attached. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244/+attachment/5062564/+files/dmesg.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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
Correction - 4.4.0-116-generic does not solve the problem. The server was up for over an hour before hanging. As it doesn't usually have a console, I can't be certain of the cause of the hang. However, a subsequent reboot, with a console, involving rebuilding a 10TB RAID 5 array, showed exactly the same Watchdog Hard Lockup for each core during the boot process. Now running with noibpb again. -- 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/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
4.4.0-116-generic does appear to solve the problem on my Asus Prime Z270K. -- 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/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+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 1743041] Re: Updating Lubuntu on netbook corrupts screen
** Tags removed: kernel-bug-exists-upstream ** Tags added: kernel-fixed-upstream -- 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/1743041 Title: Updating Lubuntu on netbook corrupts screen Status in linux package in Ubuntu: Confirmed Bug description: Updating Lubuntu 16.04-3 LTS on Asus 1000HE netbook corrupts screen as shown at https://i.imgur.com/bTw9t4Z.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743041/+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 1743041] Re: Updating Lubuntu on netbook corrupts screen
I've just tested 4.15-rc9 generic from http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.15-rc9/. It works now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743041 Title: Updating Lubuntu on netbook corrupts screen Status in linux package in Ubuntu: Confirmed Bug description: Updating Lubuntu 16.04-3 LTS on Asus 1000HE netbook corrupts screen as shown at https://i.imgur.com/bTw9t4Z.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743041/+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 1743041] Re: Updating Lubuntu on netbook corrupts screen
I tested the latest upstream kernel (v4.15-rc8) and the bug still exists. ** Tags removed: bot-comment ** Tags added: kernel-bug-exists-upstream ** 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/1743041 Title: Updating Lubuntu on netbook corrupts screen Status in linux package in Ubuntu: Confirmed Bug description: Updating Lubuntu 16.04-3 LTS on Asus 1000HE netbook corrupts screen as shown at https://i.imgur.com/bTw9t4Z.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743041/+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 1743041] Re: Updating Lubuntu on netbook corrupts screen
OK, I'll do that. -- 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/1743041 Title: Updating Lubuntu on netbook corrupts screen Status in linux package in Ubuntu: Incomplete Bug description: Updating Lubuntu 16.04-3 LTS on Asus 1000HE netbook corrupts screen as shown at https://i.imgur.com/bTw9t4Z.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743041/+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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
@tomreyn My corrent config to get stability C6 disabled in BIOS ALSR disabled kernel >= 4.14.4 with CONFIG_RCU_NOCB_CPU rcu_nocbs=0-15 processor.max_cstate=1 in GRUB_CMDLINE_LINUX I got lockups still with ASLR disabled and rcu_nocbs with the custom built kernel, once I added C6 disabled in bios and processor.max_cstate=1 I've gotten 6 weeks of uptime -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The
[Kernel-packages] [Bug 1743041] Re: Updating Lubuntu on netbook corrupts screen
Can't run apport-collect as bug renders system inoperable. ** 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/1743041 Title: Updating Lubuntu on netbook corrupts screen Status in linux package in Ubuntu: Confirmed Bug description: Updating Lubuntu 16.04-3 LTS on Asus 1000HE netbook corrupts screen as shown at https://i.imgur.com/bTw9t4Z.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743041/+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 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Out of curiosity, can you link me to the upstream git repo for http://kernsec.org/pipermail/linux-security-module- archive/2017-December/004638.html? I want to be sure I'm looking at the right place. Interestingly, it looks like someone replied to your patch saying they would incorporate it in early December, so it seems this bug fell through the cracks more than once. Joseph Salisbury is subscribed to this bug and has commented on it above, so hopefully he will update regarding this when he gets a chance. This seems like a really simple fix, so I'm actually going to see if I can recompile 4.13.0-25-generic with this patch added to make it work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+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 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Thanks! Should I mark this bug as a duplicate then? Also, what is the process/timeline for that patch you linked being applied downstream into Artful? -- 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/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+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 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Okay, the bug still exists in 4.13.0-21-generic, but went away in 4.13.0-25-generic once I removed 'apparmor=0'. So I think Tetsuo may be on to something. Could this be a duplicate of this[0] bug? This would make sense considering the message of one the problematic commits is "add stacking support to apparmor network hooks". I'm not well versed enough in the kernel internals to say for sure, so I'm deferring to someone who knows better. Also, I'm not sure if I'm missing something, but while that bug is marked as "Fix Committed" in Launchpad[0], and a request was made to revert the pair of commits[1], I neither see a reply to that email saying the commits were indeed reverted nor subsequent commits to the Artful repo reverting the files affected by these commits. Is it possible that email got lost? [0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734327 [1] https://lists.ubuntu.com/archives/kernel-team/2017-December/088715.html [2] http://kernel.ubuntu.com/git/ubuntu/ubuntu-artful.git/log/security/apparmor/lsm.c and http://kernel.ubuntu.com/git/ubuntu/ubuntu-artful.git/log/security/selinux/netlabel.c -- 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/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lo no wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+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 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Okay, I tested it with 4.15.0-041500rc7-generic and the issue disappeared. Thanks! Does that provide any insight into what exactly the error is and/or a possible workaround? Unfortunately I'm unable to use this kernel in the interim as I rely on the Nvidia kernel modules, which aren't compiling in DKMS. ** Tags added: kernel-fixed-upstream -- 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/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+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 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Please note that I ran 'ubuntu-bug' from my most recent working kernel (from Zesty): 4.10.0-42-generic, so some of this log output may be inaccurate as a result. -- 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/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: New Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+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 1742572] [NEW] System Hangs and General Protection Fault Occurs following NFS Access
Public bug reported: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1742572/+attachment/5034766/+files/dmesg.log ** Description changed: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. - Attached is the console log (obtained via netconsole), lspci (with - -vnvn), and the output from lsb_release -a. + Attached is the console log (obtained via netconsole) which includes the + kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: mvastola 4661 F pulseaudio - /dev/snd/controlC1: mvastola 4661 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: mvastola 4661 F pulseaudio + /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot&q
[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)
Workaround: grep -q 'LLMNR=no' /etc/systemd/resolved.conf || \ echo 'LLMNR=no' | sudo tee -a /etc/systemd/resolved.conf sudo service systemd-networkd restart -- 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/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial) Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: When testing MAAS on Bionic, we noticed sluggish performance that we could not immediately explain. After comparing the results from a run of the test suite on Xenial to a run on Bionic, we determined that the slowdowns had to do with DNS lookups. In particular, if MAAS attempts to resolve a hostname using getaddrinfo() and the call fails, on Xenial the negative result is returned in a fraction of a second. On Bionic, the negative result is returned in ~1.6 seconds, according to some measures. ### To run the test ### git clone https://github.com/mpontillo/test-getaddrinfo cd test-getaddrinfo make ### Results on Xenial ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Success getaddrinfo() return value: -2 (Name or service not known) real 0m0.015s user 0m0.000s sys 0m0.000s ### Results on Bionic ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Resource temporarily unavailable getaddrinfo() return value: -3 (Temporary failure in name resolution) real 0m1.609s user 0m0.004s sys 0m0.000s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)
Interesting; the first thing I tried when triaging this was to edit /etc/nsswitch.conf as follows: # hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname hosts: files dns ... to eliminate the possibility that it was multicast DNS causing the slowdown. But it appears I'm behind the times. ;-) (And didn't this only affect the .local domain?) Does this mean there are now two subsystems responsible for link-local address resolution? (avahi and systemd-resolved?) -- 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/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial) Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: When testing MAAS on Bionic, we noticed sluggish performance that we could not immediately explain. After comparing the results from a run of the test suite on Xenial to a run on Bionic, we determined that the slowdowns had to do with DNS lookups. In particular, if MAAS attempts to resolve a hostname using getaddrinfo() and the call fails, on Xenial the negative result is returned in a fraction of a second. On Bionic, the negative result is returned in ~1.6 seconds, according to some measures. ### To run the test ### git clone https://github.com/mpontillo/test-getaddrinfo cd test-getaddrinfo make ### Results on Xenial ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Success getaddrinfo() return value: -2 (Name or service not known) real 0m0.015s user 0m0.000s sys 0m0.000s ### Results on Bionic ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Resource temporarily unavailable getaddrinfo() return value: -3 (Temporary failure in name resolution) real 0m1.609s user 0m0.004s sys 0m0.000s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Just to be clear my mainline kernel is configured with CONFIG_RCU_NOCB_CPU to yes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Well I've now hit 3 weeks of uptime with C6 disabled in the BIOS and GRUB_CMDLINE_LINUX_DEFAULT="rcu_nocbs=0-15 processor.max_cstate=1" and 4.14.6 built from the mainline kernel repo. At this point I'm satisfied that for me at least my Ryzen is now stable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I can confirm that #294 works on a Lenovo G50-80. However I did have some hiccups. Basically the I did the 4 steps, but the first time did not work. It didn't update the boot entries, neither installed the new kernel. What I did was to boot in the oldest kernel that I had installed: Linux 4.13.0-12-generic Then redo the steps from #294: https://askubuntu.com/a/989771 1. Install Ukuu 2. Update the kernel Select the kernel 4.14.9 and select Install. 3. Restart the system with the latest kernel From GRUB select the option which starts with "Advanced options". Select Ubuntu GNU/Linux, with Linux 4.14.9-generic 4. Restart again and go into the BIOS At this point I'm able to boot into another USB disk that was not able to boot after I hit this bug, hope this help. -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (22/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software. Insyde is responding to emails acknowledging that they are aware of issue but are not providing details. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to:
[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)
** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial) Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: When testing MAAS on Bionic, we noticed sluggish performance that we could not immediately explain. After comparing the results from a run of the test suite on Xenial to a run on Bionic, we determined that the slowdowns had to do with DNS lookups. In particular, if MAAS attempts to resolve a hostname using getaddrinfo() and the call fails, on Xenial the negative result is returned in a fraction of a second. On Bionic, the negative result is returned in ~1.6 seconds, according to some measures. ### To run the test ### git clone https://github.com/mpontillo/test-getaddrinfo cd test-getaddrinfo make ### Results on Xenial ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Success getaddrinfo() return value: -2 (Name or service not known) real 0m0.015s user 0m0.000s sys 0m0.000s ### Results on Bionic ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Resource temporarily unavailable getaddrinfo() return value: -3 (Temporary failure in name resolution) real 0m1.609s user 0m0.004s sys 0m0.000s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)
** Description changed: When testing MAAS on Bionic, we noticed sluggish performance that we could not immediately explain. After comparing the results from a run of the test suite on Xenial to a run on Bionic, we determined that the slowdowns had to do with DNS lookups. In particular, if MAAS attempts to resolve a hostname using getaddrinfo() and the call fails, on Xenial the negative result is returned in a fraction of a second. On Bionic, the negative result is returned in ~1.6 seconds, according to some measures. ### To run the test ### git clone https://github.com/mpontillo/test-getaddrinfo cd test-getaddrinfo make - ### Results on Xenial ### - time ./test not-a-real-hostname + $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname - getaddrinfo errno: Success - getaddrinfo() return value: -2 (Name or service not known) + getaddrinfo errno: Success + getaddrinfo() return value: -2 (Name or service not known) real 0m0.015s user 0m0.000s sys 0m0.000s - ### Results on Bionic ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname - getaddrinfo errno: Resource temporarily unavailable - getaddrinfo() return value: -3 (Temporary failure in name resolution) + getaddrinfo errno: Resource temporarily unavailable + getaddrinfo() return value: -3 (Temporary failure in name resolution) real 0m1.609s user 0m0.004s sys 0m0.000s -- 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/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial) Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: When testing MAAS on Bionic, we noticed sluggish performance that we could not immediately explain. After comparing the results from a run of the test suite on Xenial to a run on Bionic, we determined that the slowdowns had to do with DNS lookups. In particular, if MAAS attempts to resolve a hostname using getaddrinfo() and the call fails, on Xenial the negative result is returned in a fraction of a second. On Bionic, the negative result is returned in ~1.6 seconds, according to some measures. ### To run the test ### git clone https://github.com/mpontillo/test-getaddrinfo cd test-getaddrinfo make ### Results on Xenial ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Success getaddrinfo() return value: -2 (Name or service not known) real 0m0.015s user 0m0.000s sys 0m0.000s ### Results on Bionic ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Resource temporarily unavailable getaddrinfo() return value: -3 (Temporary failure in name resolution) real 0m1.609s user 0m0.004s sys 0m0.000s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)
I just tested with the Xenial kernel and Bionic userspace and observed that the bug still occurs, so marked Invalid for 'linux'. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial) Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: When testing MAAS on Bionic, we noticed sluggish performance that we could not immediately explain. After comparing the results from a run of the test suite on Xenial to a run on Bionic, we determined that the slowdowns had to do with DNS lookups. In particular, if MAAS attempts to resolve a hostname using getaddrinfo() and the call fails, on Xenial the negative result is returned in a fraction of a second. On Bionic, the negative result is returned in ~1.6 seconds, according to some measures. ### To run the test ### git clone https://github.com/mpontillo/test-getaddrinfo cd test-getaddrinfo make ### Results on Xenial ### time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Success getaddrinfo() return value: -2 (Name or service not known) real 0m0.015s user 0m0.000s sys 0m0.000s ### Results on Bionic ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Resource temporarily unavailable getaddrinfo() return value: -3 (Temporary failure in name resolution) real 0m1.609s user 0m0.004s sys 0m0.000s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)
Note: I doubt this bug is in the kernel itself; I initially attempted to file it under glibc at first, but for some reason the `linux` package was selected. I also added `systemd` in case the difference in behavior can be explained by the addition of resolved. Note that these tests were run on Bionic Desktop, so it's using network- manager, not networkd. -- 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/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial) Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When testing MAAS on Bionic, we noticed sluggish performance that we could not immediately explain. After comparing the results from a run of the test suite on Xenial to a run on Bionic, we determined that the slowdowns had to do with DNS lookups. In particular, if MAAS attempts to resolve a hostname using getaddrinfo() and the call fails, on Xenial the negative result is returned in a fraction of a second. On Bionic, the negative result is returned in ~1.6 seconds, according to some measures. ### To run the test ### git clone https://github.com/mpontillo/test-getaddrinfo cd test-getaddrinfo make ### Results on Xenial ### time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Success getaddrinfo() return value: -2 (Name or service not known) real 0m0.015s user 0m0.000s sys 0m0.000s ### Results on Bionic ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Resource temporarily unavailable getaddrinfo() return value: -3 (Temporary failure in name resolution) real 0m1.609s user 0m0.004s sys 0m0.000s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1739672] [NEW] Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)
Public bug reported: When testing MAAS on Bionic, we noticed sluggish performance that we could not immediately explain. After comparing the results from a run of the test suite on Xenial to a run on Bionic, we determined that the slowdowns had to do with DNS lookups. In particular, if MAAS attempts to resolve a hostname using getaddrinfo() and the call fails, on Xenial the negative result is returned in a fraction of a second. On Bionic, the negative result is returned in ~1.6 seconds, according to some measures. ### To run the test ### git clone https://github.com/mpontillo/test-getaddrinfo cd test-getaddrinfo make ### Results on Xenial ### time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Success getaddrinfo() return value: -2 (Name or service not known) real0m0.015s user0m0.000s sys 0m0.000s ### Results on Bionic ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Resource temporarily unavailable getaddrinfo() return value: -3 (Temporary failure in name resolution) real0m1.609s user0m0.004s sys 0m0.000s ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: xenial ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial) Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When testing MAAS on Bionic, we noticed sluggish performance that we could not immediately explain. After comparing the results from a run of the test suite on Xenial to a run on Bionic, we determined that the slowdowns had to do with DNS lookups. In particular, if MAAS attempts to resolve a hostname using getaddrinfo() and the call fails, on Xenial the negative result is returned in a fraction of a second. On Bionic, the negative result is returned in ~1.6 seconds, according to some measures. ### To run the test ### git clone https://github.com/mpontillo/test-getaddrinfo cd test-getaddrinfo make ### Results on Xenial ### time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Success getaddrinfo() return value: -2 (Name or service not known) real 0m0.015s user 0m0.000s sys 0m0.000s ### Results on Bionic ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Resource temporarily unavailable getaddrinfo() return value: -3 (Temporary failure in name resolution) real 0m1.609s user 0m0.004s sys 0m0.000s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1739300] Re: The header files fcntl.h and linux/fcntl.h are incompatible
Thx, Hans Joachim.
Problem with ubuntu-bug was, that i did not know the package to put this on.
apport-collect 1739300 freezes on my system.
But there are no logs needed in this case, i presume.
So status => Confirmed
** 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/1739300
Title:
The header files fcntl.h and linux/fcntl.h are incompatible
Status in glibc package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
The program try.c, below, does not compile.
Though with HAVE_ARCH_STRUCT_FLOCK and HAVE_ARCH_STRUCT_FLOCK64 defined, it
compiles.
But then fails again to compile, when _GNU_SOURCE is also defined.
I expect this to compile in all three cases.
$ cat try.c
//#define _GNU_SOURCE
//#define HAVE_ARCH_STRUCT_FLOCK
//#define HAVE_ARCH_STRUCT_FLOCK64
#include
#include
int main(int argc, char *argv[]){}
$ gcc try.c
In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0,
from /usr/include/linux/fcntl.h:4,
from try.c:5:
/usr/include/asm-generic/fcntl.h:195:8: error: redefinition of ‘struct flock’
struct flock {
^
In file included from /usr/include/fcntl.h:35:0,
from try.c:4:
/usr/include/x86_64-linux-gnu/bits/fcntl.h:35:8: note: originally defined here
struct flock
^
$ gcc -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c ## this is ok
$ gcc -D_GNU_SOURCE -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c
In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0,
from /usr/include/linux/fcntl.h:4,
from try.c:5:
/usr/include/asm-generic/fcntl.h:155:8: error: redefinition of ‘struct
f_owner_ex’
struct f_owner_ex {
^~
In file included from /usr/include/x86_64-linux-gnu/bits/fcntl.h:61:0,
from /usr/include/fcntl.h:35,
from try.c:4:
/usr/include/x86_64-linux-gnu/bits/fcntl-linux.h:267:8: note: originally
defined here
struct f_owner_ex
^~
$ gcc --version | head -1
gcc (Ubuntu 7.2.0-8ubuntu3) 7.2.0
$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
$ dpkg -S /usr/include/x86_64-linux-gnu/bits/fcntl.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/bits/fcntl.h
# Package: libc6-dev
# Version: 2.26-0ubuntu2
$ dpkg -S /usr/include/x86_64-linux-gnu/asm/fcntl.h
linux-libc-dev:amd64: /usr/include/x86_64-linux-gnu/asm/fcntl.h
# Package: linux-libc-dev
# Version: 4.13.0-19.22
Regards, Mike
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739300/+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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
well another lock up. I've now disabled C6 in the bios and added max_cstates=1 to the boot parameters -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Well another watchdog failure with 4.14.5 I also updated to AGESA 1.0.0.6B when I rebooted to 4.14.5. Just building a 4.14.6 to try again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to:
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
After 5 days uptime with my custom ubuntu kernel build I got a different crash with a reboot vs the watchdog error. I'm now running a mainline kernel 4.14.3 with ASLR disabled and rcu_nocbs=0-15 and have restarted my no crash counter. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups:
[Kernel-packages] [Bug 1736794] [NEW] iwlwifi driver for Intel 7260 crashing
Public bug reported: Intel NUC's from Axiomtek with Intel Corporation Wireless 7260 (rev bb) chipsets. We have this running on almost 200 of these devices. Ubuntu 16.04.3 as well as Ubuntu 14.04.5 "loaded firmware version 17.608620.0 op_mode iwlmvm" linux-firmware trusty: 1.127.24 linux-firmware xenial: 1.157.14 The wireless driver will crash at least daily, if not multiple times in a day depending on the machine. Swapping the chipset out for an Atheros works just fine. I have followed the many other bug reports related to this same chipset and they are either marked incomplete, refer to hardware we aren't running or have been marked as fix released. The latest linux-firmware did not resolve or change the behavior of the issue. Output from dmesg when the crash occurs: [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: Queue 16 stuck for 1 ms. [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: Current SW read_ptr 236 write_ptr 88 [Wed Dec 6 18:56:38 2017] [ cut here ] [Wed Dec 6 18:56:38 2017] WARNING: CPU: 3 PID: 0 at /build/linux-lts-xenial-CtFtiH/linux-lts-xenial-4.4.0/drivers/net/wireless/iwlwifi/pcie/trans.c:1552 iwl_trans_pcie_grab_nic_access+0xf5/0x100 [iwlwifi]() [Wed Dec 6 18:56:38 2017] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) [Wed Dec 6 18:56:38 2017] Modules linked in: drbg ansi_cprng ctr ccm uvcvideo videobuf2_vmalloc btusb videobuf2_memops btrtl videobuf2_v4l2 btbcm btintel videobuf2_core hid_generic bluetooth v4l2_common videodev usbhid media arc4 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iwlmvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass iwlwifi crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cfg80211 aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_soc_rt5640 snd_soc_rl6231 snd_soc_ssm4567 serio_raw lpc_ich i915 shpchp binfmt_misc snd_hda_intel snd_soc_core snd_compress snd_hda_codec ac97_bus snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm_dmaengine snd_hda_core snd_hwdep snd_pcm 8250_fintek snd_seq video snd_seq_device snd_timer drm_kms_helper snd elan_i2c 8250_dw drm dw_dmac i2c_hid hid dw_dmac_core mei_me fb_sys_fops syscopyarea snd_soc_sst_acpi i2c_designware_platform mac_hid sysfillrect spi_pxa2xx_platform mei i2c_designware_core soundcore acpi_pad sysimgblt acpi_als kfifo_buf industrialio lp parport igb psmouse ahci e1000e i2c_algo_bit libahci dca ptp pps_core fjes sdhci_acpi sdhci [Wed Dec 6 18:56:38 2017] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.4.0-101-generic #124~14.04.1-Ubuntu [Wed Dec 6 18:56:38 2017] Hardware name: To be filled by O.E.M. To be filled by O.E.M./CRESCENTBAY, BIOS 5.6.5 12/14/2016 [Wed Dec 6 18:56:38 2017] 88012dd83d00 813dfc6c 88012dd83d48 [Wed Dec 6 18:56:38 2017] c07ca6e0 88012dd83d38 8107ea26 8800ca47 [Wed Dec 6 18:56:38 2017] 8800ca4735f0 88012dd83dd8 880128108bc0 [Wed Dec 6 18:56:38 2017] Call Trace: [Wed Dec 6 18:56:38 2017][] dump_stack+0x63/0x87 [Wed Dec 6 18:56:38 2017] [] warn_slowpath_common+0x86/0xc0 [Wed Dec 6 18:56:38 2017] [] warn_slowpath_fmt+0x4c/0x50 [Wed Dec 6 18:56:38 2017] [] ? iwl_read32+0x1f/0x90 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] iwl_trans_pcie_grab_nic_access+0xf5/0x100 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] iwl_trans_pcie_read_mem+0x2f/0xa0 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] iwl_pcie_txq_stuck_timer+0xd8/0x390 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] ? intel_pstate_timer_func+0x2db/0x3a0 [Wed Dec 6 18:56:38 2017] [] ? iwl_pcie_enqueue_hcmd+0xa90/0xa90 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] call_timer_fn+0x35/0x130 [Wed Dec 6 18:56:38 2017] [] ? iwl_pcie_enqueue_hcmd+0xa90/0xa90 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] run_timer_softirq+0x20e/0x2c0 [Wed Dec 6 18:56:38 2017] [] __do_softirq+0xdd/0x290 [Wed Dec 6 18:56:38 2017] [] irq_exit+0x95/0xa0 [Wed Dec 6 18:56:38 2017] [] smp_apic_timer_interrupt+0x42/0x50 [Wed Dec 6 18:56:38 2017] [] apic_timer_interrupt+0x82/0x90 [Wed Dec 6 18:56:38 2017][] ? cpuidle_enter_state+0xd8/0x250 [Wed Dec 6 18:56:38 2017] [] ? cpuidle_enter_state+0xb4/0x250 [Wed Dec 6 18:56:38 2017] [] cpuidle_enter+0x17/0x20 [Wed Dec 6 18:56:38 2017] [] call_cpuidle+0x32/0x60 [Wed Dec 6 18:56:38 2017] [] ? cpuidle_select+0x13/0x20 [Wed Dec 6 18:56:38 2017] [] cpu_startup_entry+0x289/0x350 [Wed Dec 6 18:56:38 2017] [] start_secondary+0x149/0x170 [Wed Dec 6 18:56:38 2017] ---[ end trace ad9659e8d87e5230 ]--- [Wed Dec 6 18:56:38 2017] iwl data: : b0 68 00 00 14 00 00 00 b8 8a 5c 00 00 00 00 00 .h\. [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(0) = 0x5a5a5a5a [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(1) = 0x5a5a5a5a [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(2) = 0x5a5a5a5a [Wed Dec 6 18:56:38 2017] iwlwifi
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Well I've hit 48 hours uptime since booting to my custom build kernel (Linux ganymede 4.13.0-17-generic #20+ryzen SMP Sun Dec 3 20:18:51 MST 2017 x86_64 x86_64 x86_64 GNU/Linux) with rcu_nocbs=0-15 in my boot command and disabled ASLR. That's about double my previous uptime record, I'll report back again if I hit 1 week -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Yep I did :) thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Cool Thanks for the confirmation Franck I've rebuilt 4.13.0-17 with instructions from here https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel (Probably similarly to Mario). I'm going to test it with this first (since don't really want to reboot again). But might get stuff ready with a 4.14.3 (which is current latest). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
@franckc did you have to rebuild your kernel? I tried the kernel options without that and still had failures. I've just rebuilt with CONFIG_RCU_NOCB_CPU to see if now the rcu_nocbs=0-15 resolves my lockups -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True
[Kernel-packages] [Bug 1726612] [NEW] PUD 18e40d063
Public bug reported: System froze and needed to be power-cycled. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikebw 5765 F pulseaudio /dev/snd/controlC0: mikebw 5765 F pulseaudio Date: Mon Oct 23 17:06:41 2017 Failure: oops InstallationDate: Installed on 2016-09-20 (398 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire V3-574 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=d6148b34-f87c-495e-aee7-9ab86a72efef ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: PUD 18e40d063 UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago) dmi.bios.date: 11/30/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: USOPP_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.35:bd11/30/2015:svnAcer:pnAspireV3-574:pvrV3.72:rvnAcer:rnUSOPP_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire V3-574 dmi.product.version: V3.72 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops artful kernel-oops -- 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/1726612 Title: PUD 18e40d063 Status in linux package in Ubuntu: Confirmed Bug description: System froze and needed to be power-cycled. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikebw 5765 F pulseaudio /dev/snd/controlC0: mikebw 5765 F pulseaudio Date: Mon Oct 23 17:06:41 2017 Failure: oops InstallationDate: Installed on 2016-09-20 (398 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire V3-574 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=d6148b34-f87c-495e-aee7-9ab86a72efef ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: PUD 18e40d063 UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago) dmi.bios.date: 11/30/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: USOPP_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.35:bd11/30/2015:svnAcer:pnAspireV3-574:pvrV3.72:rvnAcer:rnUSOPP_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire V3-574 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726612/+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 1572698] Re: [patch included]Slow speed and dropped connections with Realtek RTL8192CU-based wifi
i'm using the fix from git hub on 16.04 all up to date. https://github.com/pvaret/rtl8192cu-fixes Tried and work on kernels 4.4 , 4.8 and 4.11 . I haven't tested it on 4.9 and 4.14 It's ALREADY fixed, some one just needs to review it's not malware and then do a copy paste -_- Why it's not integrated alredy in the kernel after all this time -- 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/1572698 Title: [patch included]Slow speed and dropped connections with Realtek RTL8192CU-based wifi Status in linux package in Ubuntu: Confirmed Bug description: EDIT(other user): Some one fixed it in github, still works in at least in linux 4.4-4.11 https://github.com/pvaret/rtl8192cu-fixes EDIT: I am using a D-Link DWA-131 USB wlan adapter to connect to my private wlan. The adapter works fine under Windows and I have no problems connecting to my wlan with other devices (e.g. my laptop running Linux Mint). However, the adapter, which is based on the Realtek rtl8192cu chipset, won't work correctly on any current Ubuntu machine (in my case Kubuntu 15.10 64bit): As also showcased by a myriad of other bug reports (most of which have expired by now), wlan-adapters based on the Realtek rtl8192cu chipset exhibit very slow connection speeds and frequently dropped connections with current Linux kernels. I have noticed this originally in Linux Mint 17 running kernel 3.19.x, in Kubuntu 15.10 up to 4.2.0.35 and can confirm that it is still present in a live session of Xenial Xerus (16.04). I have tried commonly mentioned "fixes" such as deactivating hardware encryption without success. The drivers available on the Realtek homepage are apparently intended for older kernels and won't install. There is, however, a fixed driver available via github (https://github.com/pvaret/rtl8192cu-fixes). I have followed the instructions found there and finally my wlan-adapter is working correctly. Apparently the issues caused by the broken driver in the linux kernels might be connected to power management. I am posting this bug here in the hope that some developer finally manages to incorporate the (obviously available) fixes found in the github-drivers into the drivers already included in the kernel. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick2300 F pulseaudio /dev/snd/controlC1: patrick2300 F pulseaudio DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=28c49a78-8b93-495e-bc1b-22c87db4734c InstallationDate: Installed on 2015-10-22 (181 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. GA-870A-UD3 NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=1016b861-fa27-4990-bac9-58a3ab27ff5b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 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. RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.149.3 RfKill: Tags: wily UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' Uname: Linux 4.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/01/2011 dmi.bios.vendor: AwardAward (授与する, じゅよする, juyosuru) Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-870A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd08/01/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-870A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-870A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-870A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572698/+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 1572698] Re: [patch included]Slow speed and dropped connections with Realtek RTL8192CU-based wifi
** Description changed: + EDIT: Some one fixed it in github, still works in at least in linux 4.4-4.11 + https://github.com/pvaret/rtl8192cu-fixes + EDIT: + I am using a D-Link DWA-131 USB wlan adapter to connect to my private wlan. The adapter works fine under Windows and I have no problems connecting to my wlan with other devices (e.g. my laptop running Linux Mint). However, the adapter, which is based on the Realtek rtl8192cu chipset, won't work correctly on any current Ubuntu machine (in my case Kubuntu 15.10 64bit): As also showcased by a myriad of other bug reports (most of which have expired by now), wlan-adapters based on the Realtek rtl8192cu chipset exhibit very slow connection speeds and frequently dropped connections with current Linux kernels. I have noticed this originally in Linux Mint 17 running kernel 3.19.x, in Kubuntu 15.10 up to 4.2.0.35 and can confirm that it is still present in a live session of Xenial Xerus (16.04). I have tried commonly mentioned "fixes" such as deactivating hardware encryption without success. The drivers available on the Realtek homepage are apparently intended for older kernels and won't install. There is, however, a fixed driver available via github (https://github.com/pvaret/rtl8192cu-fixes). I have followed the instructions found there and finally my wlan-adapter is working correctly. Apparently the issues caused by the broken driver in the linux kernels might be connected to power management. I am posting this bug here in the hope that some developer finally manages to incorporate the (obviously available) fixes found in the github-drivers into the drivers already included in the kernel. - --- + --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: patrick2300 F pulseaudio - /dev/snd/controlC1: patrick2300 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: patrick2300 F pulseaudio + /dev/snd/controlC1: patrick2300 F pulseaudio DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=28c49a78-8b93-495e-bc1b-22c87db4734c InstallationDate: Installed on 2015-10-22 (181 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. GA-870A-UD3 NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=1016b861-fa27-4990-bac9-58a3ab27ff5b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 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. + 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. RelatedPackageVersions: - linux-restricted-modules-4.2.0-35-generic N/A - linux-backports-modules-4.2.0-35-generic N/A - linux-firmware1.149.3 + linux-restricted-modules-4.2.0-35-generic N/A + linux-backports-modules-4.2.0-35-generic N/A + linux-firmware1.149.3 RfKill: - + Tags: wily UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' Uname: Linux 4.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: - + _MarkForUpload: True dmi.bios.date: 08/01/2011 - dmi.bios.vendor: Award Software International, Inc. + dmi.bios.vendor: AwardAward (授与する, じゅよする, juyosuru) Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-870A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd08/01/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-870A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-870A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-870A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Description changed: - EDIT: Some one fixed it in github, still works in at least in linux 4.4-4.11 + EDIT(other user): Some one fixed it in github, still works in at least in linux 4.4-4.11 https://github.com/pvaret/rtl8192cu-fixes EDIT: I am using a D-Link DWA-131 USB wlan adapter to connect to my private wlan. The adapter works fine under Windows and I have no problems connecting to my wlan with other devices (e.g. my laptop running Linux Mint). However, the adapter, which is based on the Realtek rtl8192cu chipset, won't work correctly on any current Ubuntu machine (in my case Kubuntu 15.10 64bit): As also showcased by a myriad of other bug reports (most of
[Kernel-packages] [Bug 1572698] Re: Slow speed and dropped connections with Realtek RTL8192CU-based wifi
** Changed in: linux (Ubuntu) Status: Expired => Confirmed ** Summary changed: - Slow speed and dropped connections with Realtek RTL8192CU-based wifi + [patch included]Slow speed and dropped connections with Realtek RTL8192CU-based wifi -- 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/1572698 Title: [patch included]Slow speed and dropped connections with Realtek RTL8192CU-based wifi Status in linux package in Ubuntu: Confirmed Bug description: EDIT(other user): Some one fixed it in github, still works in at least in linux 4.4-4.11 https://github.com/pvaret/rtl8192cu-fixes EDIT: I am using a D-Link DWA-131 USB wlan adapter to connect to my private wlan. The adapter works fine under Windows and I have no problems connecting to my wlan with other devices (e.g. my laptop running Linux Mint). However, the adapter, which is based on the Realtek rtl8192cu chipset, won't work correctly on any current Ubuntu machine (in my case Kubuntu 15.10 64bit): As also showcased by a myriad of other bug reports (most of which have expired by now), wlan-adapters based on the Realtek rtl8192cu chipset exhibit very slow connection speeds and frequently dropped connections with current Linux kernels. I have noticed this originally in Linux Mint 17 running kernel 3.19.x, in Kubuntu 15.10 up to 4.2.0.35 and can confirm that it is still present in a live session of Xenial Xerus (16.04). I have tried commonly mentioned "fixes" such as deactivating hardware encryption without success. The drivers available on the Realtek homepage are apparently intended for older kernels and won't install. There is, however, a fixed driver available via github (https://github.com/pvaret/rtl8192cu-fixes). I have followed the instructions found there and finally my wlan-adapter is working correctly. Apparently the issues caused by the broken driver in the linux kernels might be connected to power management. I am posting this bug here in the hope that some developer finally manages to incorporate the (obviously available) fixes found in the github-drivers into the drivers already included in the kernel. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick2300 F pulseaudio /dev/snd/controlC1: patrick2300 F pulseaudio DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=28c49a78-8b93-495e-bc1b-22c87db4734c InstallationDate: Installed on 2015-10-22 (181 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. GA-870A-UD3 NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=1016b861-fa27-4990-bac9-58a3ab27ff5b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 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. RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.149.3 RfKill: Tags: wily UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' Uname: Linux 4.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/01/2011 dmi.bios.vendor: AwardAward (授与する, じゅよする, juyosuru) Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-870A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd08/01/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-870A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-870A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-870A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572698/+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 1716457] [NEW] Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning
Public bug reported: I've had this happen twice on kernel upgrades, most recently when linux- image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware 1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1716457 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic
[Kernel-packages] [Bug 1716438] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948119/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948115/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948120/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716304] Re: Environmental Variables Have Improper Values
I used this command in a terminal as directed: apport-collect 1716304 and now the post seems to be corrupted. This is a new install so I have no prior history with the problem. And, I am not able to test a different kernel on that computer. Mike On 09/11/2017 07:14 AM, Joseph Salisbury wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.13 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13 > > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Medium > -- Not Proofed for Spelling or Content ** 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/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Confirmed Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716438] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948121/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948111/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948109/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948117/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948113/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948118/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948112/+files/JournalErrors.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/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948114/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948116/+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/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948110/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikebw 2674 F pulseaudio /dev/snd/controlC1: mikebw 2674 F pulseaudio DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-01-21 (1329 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-94-generic N/A linux-backports-modules-4.4.0-94-generic N/A linux-firmware1.157.12 Tags: xenial Uname: Linux 4.4.0-94-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716438] Re: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning
apport information ** Tags added: apport-collected ** Description changed: I've had this happen twice on kernel upgrades, most recently when linux- image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial + --- + ApportVersion: 2.20.1-0ubuntu2.10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: mikebw 2674 F pulseaudio + /dev/snd/controlC1: mikebw 2674 F pulseaudio + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2014-01-21 (1329 days ago) + InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_US + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=8f5d219a-699a-42fc-a668-7c78fbab134a ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.4.0-94-generic N/A + linux-backports-modules-4.4.0-94-generic N/A + linux-firmware1.157.12 + Tags: xenial + Uname: Linux 4.4.0-94-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2017-07-29 (43 days ago) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 08/13/2010 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2104 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: M4A785TD-M EVO + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1716438/+attachment/4948108/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: Confirmed Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an
[Kernel-packages] [Bug 1716304] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948090/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716304] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948088/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716304] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948091/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716304] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948085/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716304] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948089/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716304] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948086/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716304] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948087/+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/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716304] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948084/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716304] Re: Environmental Variables Have Improper Values
apport information ** Tags added: apport-collected xenial ** Description changed: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. - Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE - (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial + Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial + --- + ApportVersion: 2.20.1-0ubuntu2.10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: mike 1919 F pulseaudio + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf + InstallationDate: Installed on 2017-08-10 (32 days ago) + InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + IwConfig: + enp0s25 no wireless extensions. + + lono wireless extensions. + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_US + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash + ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 + 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. + RelatedPackageVersions: + linux-restricted-modules-4.10.0-33-generic N/A + linux-backports-modules-4.10.0-33-generic N/A + linux-firmware 1.157.12 + RfKill: + + Tags: xenial + Uname: Linux 4.10.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 01/20/2010 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0301 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: 111-CD-E630 + dmi.board.vendor: EVGA + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.name: To Be Filled By O.E.M. + dmi.product.version: Rev 1.xx + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948080/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: Tr
[Kernel-packages] [Bug 1716304] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948082/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716304] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948083/+files/JournalErrors.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/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716304] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1716304/+attachment/4948081/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: Incomplete Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1919 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf InstallationDate: Installed on 2017-08-10 (32 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=50fe2f63-75ab-4a84-824a-86259bd5c3d3 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 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. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.157.12 RfKill: Tags: xenial Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 111-CD-E630 dmi.board.vendor: EVGA dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd01/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn111-CD-E630:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: Rev 1.xx dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716438] [NEW] Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning
Public bug reported: I've had this happen twice on kernel upgrades, most recently when linux- image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1716438 Title: Failure to download linux-image-extra-*-generic causes initrd to be built incorrectly with no warning Status in linux package in Ubuntu: New Bug description: I've had this happen twice on kernel upgrades, most recently when linux-image-extra-4.4.0-95-generic failed to download due to an iffy connection. Because linux-image-4.4.0-95-generic did successfully download, its setup (run-parts: executing /etc/kernel/postinst.d/zz- update-grub 4.4.0-95-generic /boot/vmlinuz-4.4.0-95-generic) was run and an initrd file built. The problem is that the resulting initrd file is less than half the size it should be, lacking all of the drivers that would have come in from the "extra" package: -rw-r--r-- 1 root root 38288353 Aug 22 10:09 initrd.img-4.4.0-89-generic -rw-r--r-- 1 root root 38289328 Aug 22 10:11 initrd.img-4.4.0-93-generic -rw-r--r-- 1 root root 38371214 Sep 2 06:00 initrd.img-4.4.0-94-generic -rw-r--r-- 1 root root 16899714 Sep 11 12:15 initrd.img-4.4.0-95-generic The result is a system that upon reboot cannot access important things such as the network. Recovery involves putting hands on the console and using GRUB to manually select a prior kernel with a good initrd. Recommendation: Do not allow the build of initrd and consequent activation of the new kernel as default without making sure the extra package has been or can be installed if selected. At the very minimum, issue a warning that the system may not be properly rebootable. Note that the following information is compiled while booted from kernel 94 rather than the kernel 95 with the faulty initrd. # uname -a Linux xena 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-94.117-generic 4.4.83 # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716438/+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 1716304] [NEW] Environmental Variables Have Improper Values
Public bug reported: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1716304 Title: Environmental Variables Have Improper Values Status in linux package in Ubuntu: New Bug description: With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP, and GDMSESSION are set to Lubuntu. A more appropriate and useful value would be LXDE. This is not a problem with Lubuntu-Openbox. Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
Looks to me like the patch is in Ubuntu kernel. http://kernel.ubuntu.com/git/kernel- ppa/mirror/linux.git/tree/drivers/mfd/intel-lpss-pci.c -- 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/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)]↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]↳ Power Button id=6[slave keyboard (3)]↳ Video Bus id=7[slave keyboard (3)]↳ Video Bus id=8[slave keyboard (3)]↳ Power Button id=9[slave keyboard (3)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1710392] Re: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop
http://kernel.ubuntu.com/git/kernel- ppa/mirror/linux.git/tree/drivers/mfd/intel-lpss-pci.c Looks like the source is now fixed. -- 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/1710392 Title: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop Status in linux package in Ubuntu: Confirmed Bug description: There's just a 1 line patch required, to add an initializer to array of structs scanned to match up the device ID with driver. The PR is here: https://github.com/torvalds/linux/pull/444#discussion_r131229815 I've applied the patch and created and booted from a custom kernel and it works great. The laptop is wonderful running Ubuntu: I7 7700HQ, 16G RAM, 500G SSD, 4K touch screen, decent I/O ports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710392/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
The title of the email might be better to include the directory path to the file, and a brief description. Use the body of the email to mention Lenovo. I assume you already got that feedback... -- 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/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)]↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]↳ Power Button id=6[slave keyboard (3)]↳ Video Bus id=7[slave keyboard (3)]↳ Video Bus id=8[slave keyboard (3)]↳ Power Button id=9[slave keyboard (3)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
Please do use my email or name, etc. B -- 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/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)]↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]↳ Power Button id=6[slave keyboard (3)]↳ Video Bus id=7[slave keyboard (3)]↳ Video Bus id=8[slave keyboard (3)]↳ Power Button id=9[slave keyboard (3)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1710392] Re: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop
I changed it to confirmed, although I am the reporter. I found the patch is missing in the ubuntu kernel source: https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git /mainline-crack/tree/drivers/mfd/intel-lpss-pci.c -- 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/1710392 Title: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop Status in linux package in Ubuntu: Confirmed Bug description: There's just a 1 line patch required, to add an initializer to array of structs scanned to match up the device ID with driver. The PR is here: https://github.com/torvalds/linux/pull/444#discussion_r131229815 I've applied the patch and created and booted from a custom kernel and it works great. The laptop is wonderful running Ubuntu: I7 7700HQ, 16G RAM, 500G SSD, 4K touch screen, decent I/O ports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710392/+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 1710392] Re: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop
The bug exists upstream in 4.13-rc4 ** Tags added: kernel-bug-exists-upstream ** 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/1710392 Title: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop Status in linux package in Ubuntu: Confirmed Bug description: There's just a 1 line patch required, to add an initializer to array of structs scanned to match up the device ID with driver. The PR is here: https://github.com/torvalds/linux/pull/444#discussion_r131229815 I've applied the patch and created and booted from a custom kernel and it works great. The laptop is wonderful running Ubuntu: I7 7700HQ, 16G RAM, 500G SSD, 4K touch screen, decent I/O ports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710392/+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 1710392] Re: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop
Sorry, to answer the first question, the latest kernels do boot on the machine, the trackpad isn't recognized and doesn't respond to anything at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710392 Title: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop Status in linux package in Ubuntu: Incomplete Bug description: There's just a 1 line patch required, to add an initializer to array of structs scanned to match up the device ID with driver. The PR is here: https://github.com/torvalds/linux/pull/444#discussion_r131229815 I've applied the patch and created and booted from a custom kernel and it works great. The laptop is wonderful running Ubuntu: I7 7700HQ, 16G RAM, 500G SSD, 4K touch screen, decent I/O ports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710392/+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 1710392] Re: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop
No. The laptop is a 2017 model. The source file in question simply doesn't have an array element that describes/identifies the trackpad. My assumption is that the driver maintainer simply hasn't seen a device with this ID before. I would be happy to test the latest kernel, but I don;'t see the required fix in the source code. https://github.com/torvalds/linux/blob/master/drivers/mfd/intel-lpss- pci.c#L223 (the missing line is after that one) If this is not the correct kernel source, please let me know. This is master/4.13-rc3 branch. -- 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/1710392 Title: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop Status in linux package in Ubuntu: Incomplete Bug description: There's just a 1 line patch required, to add an initializer to array of structs scanned to match up the device ID with driver. The PR is here: https://github.com/torvalds/linux/pull/444#discussion_r131229815 I've applied the patch and created and booted from a custom kernel and it works great. The laptop is wonderful running Ubuntu: I7 7700HQ, 16G RAM, 500G SSD, 4K touch screen, decent I/O ports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710392/+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 1710392] Re: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop
I searched the WWW for any kind of solution to the trackpad not being recognized. There are several months of similar questions, but no resolution. Until this patch was made public/known. Further discussion here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700657 -- 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/1710392 Title: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop Status in linux package in Ubuntu: Confirmed Bug description: There's just a 1 line patch required, to add an initializer to array of structs scanned to match up the device ID with driver. The PR is here: https://github.com/torvalds/linux/pull/444#discussion_r131229815 I've applied the patch and created and booted from a custom kernel and it works great. The laptop is wonderful running Ubuntu: I7 7700HQ, 16G RAM, 500G SSD, 4K touch screen, decent I/O ports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710392/+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 1710392] [NEW] Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop
Public bug reported: There's just a 1 line patch required, to add an initializer to array of structs scanned to match up the device ID with driver. The PR is here: https://github.com/torvalds/linux/pull/444#discussion_r131229815 I've applied the patch and created and booted from a custom kernel and it works great. The laptop is wonderful running Ubuntu: I7 7700HQ, 16G RAM, 500G SSD, 4K touch screen, decent I/O ports. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1710392 Title: Additional initializer needed to recognize trackpad on Lenovo Yoga 720 laptop Status in linux package in Ubuntu: Confirmed Bug description: There's just a 1 line patch required, to add an initializer to array of structs scanned to match up the device ID with driver. The PR is here: https://github.com/torvalds/linux/pull/444#discussion_r131229815 I've applied the patch and created and booted from a custom kernel and it works great. The laptop is wonderful running Ubuntu: I7 7700HQ, 16G RAM, 500G SSD, 4K touch screen, decent I/O ports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710392/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
@kaihengfeng Can you please assure this gets in the queue to get merged into master? The file in question hasn't been changed since early July, so not merged. It would be awesome to not have to build custom kernels all the time the kernel needs to be updated. -- 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/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)]↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]↳ Power Button id=6[slave keyboard (3)]↳ Video Bus id=7[slave keyboard (3)]↳ Video Bus id=8[slave keyboard (3)]↳ Power Button id=9[slave keyboard (3)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
@CoolStar nothing to do. https://github.com/torvalds/linux/pull/444 @Hoeze made the PR already. -- 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/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)]↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]↳ Power Button id=6[slave keyboard (3)]↳ Video Bus id=7[slave keyboard (3)]↳ Video Bus id=8[slave keyboard (3)]↳ Power Button id=9[slave keyboard (3)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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
