[Kernel-packages] [Bug 1778534] Re: Touchpad not working (Elantech ELAN0618)
Thank you too for following up the reports here.
Sadly I currently have no access to the system, it was my friend's
laptop.
I think it is not yet merged since he said after a kernel update two
days ago (proposed by the Software Updater), the touchpad stopped
working and he had to install the manually built kernel again using
dpkg.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1778534
Title:
Touchpad not working (Elantech ELAN0618)
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Xenial:
Triaged
Status in linux source package in Bionic:
Triaged
Status in linux source package in Cosmic:
Triaged
Bug description:
For a fresh installed Ubuntu 16 (and 18), touchpad doesn't work for
Elantech ELAN0618.
We have modified the struct elan_acpi_id, by adding ELAN0618 to the
list of the supported models (in the file
drivers/input/mouse/elan_i2c_core.c from the kernel source)
static const struct acpi_device_id elan_acpi_id[] = {
{ "ELAN", 0 },
{ "ELAN0100", 0 },
{ "ELAN0600", 0 },
{ "ELAN0602", 0 },
{ "ELAN0605", 0 },
{ "ELAN0608", 0 },
{ "ELAN0605", 0 },
{ "ELAN0609", 0 },
{ "ELAN060B", 0 },
{ "ELAN060C", 0 },
{ "ELAN0611", 0 },
{ "ELAN0618", 0 },
{ "ELAN1000", 0 },
{ }
};
and then built the kernel, and our problem solved.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778534/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160693/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160692/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160687/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160680/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160686/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160690/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160684/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160691/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160685/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] Re: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
apport information ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: apport-collected tara ** Description changed: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: hp 1852 F pulseaudio + /dev/snd/controlC0: hp 1852 F pulseaudio + CurrentDesktop: MATE + DistroRelease: Linux Mint 19 + HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 + InstallationDate: Installed on 2018-07-06 (0 days ago) + InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 + MachineType: Hewlett-Packard HP EliteBook 8570w + Package: linux (not installed) + ProcFB: 0 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-24-generic N/A + linux-backports-modules-4.15.0-24-generic N/A + linux-firmware 1.173.1 + Tags: tara + Uname: Linux 4.15.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/13/2018 + dmi.bios.vendor: Hewlett-Packard + dmi.bios.version: 68IAV Ver. F.68 + dmi.board.name: 176B + dmi.board.vendor: Hewlett-Packard + dmi.board.version: KBC Version 50.1F + dmi.chassis.type: 10 + dmi.chassis.vendor: Hewlett-Packard + dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: + dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI + dmi.product.name: HP EliteBook 8570w + dmi.product.version: A1029D1102 + dmi.sys.vendor: Hewlett-Packard ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160679/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family:
[Kernel-packages] [Bug 1780519] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160682/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160689/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160688/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160683/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1780519/+attachment/5160681/+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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Confirmed Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1852 F pulseaudio /dev/snd/controlC0: hp 1852 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=ea79abf5-9b30-4a54-95e1-07c5996d9074 InstallationDate: Installed on 2018-07-06 (0 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Hewlett-Packard HP EliteBook 8570w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=5065bb0f-c85b-46cf-a505-ff5d25a9746d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768381] Re: package linux-image-4.15.0-20-generic (not installed) failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess retur
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768381 Title: package linux-image-4.15.0-20-generic (not installed) failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Expired Bug description: running on asus c300m chromebook, installed Gallium-OS kernel for full hardware support. error seems to relate to removal of the generic kernel used by ubuntu. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic (not installed) Uname: Linux 4.8.17-galliumos x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 18:55:53 2018 ErrorMessage: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-04-27 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-20-generic (not installed) failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769265] Re: kernel-oops unable to handle kernel NULL pointer in page_idle_get_page
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769265 Title: kernel-oops unable to handle kernel NULL pointer in page_idle_get_page Status in linux package in Ubuntu: Expired Bug description: Using the bionic-4.15.0-15.16-generic-amd64, the command "timeout 1 cat /sys/kernel/mm/page_idle/bitmap" will generate an oops. Other information cat /proc/version_signature: Ubuntu 4.15.0-15.16-generic 4.15.15 (No lspci available, can get if needed). Full oops: [ 76.783820] BUG: unable to handle kernel NULL pointer dereference at 06d0 [ 76.785349] IP: page_idle_get_page+0xcb/0x1a0 [ 76.786079] PGD 0 P4D 0 [ 76.786523] Oops: [#1] SMP PTI [ 76.787136] Modules linked in: kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd input_leds joydev serio_raw mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq psmouse floppy e1000 i2c_piix4 pata_acpi [ 76.791780] CPU: 0 PID: 605 Comm: cat Not tainted 4.15.0-15-generic #16-Ubuntu [ 76.792997] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007 [ 76.793987] RIP: 0010:page_idle_get_page+0xcb/0x1a0 [ 76.794775] RSP: 0018:a5b680473df0 EFLAGS: 00010202 [ 76.795694] RAX: 0001 RBX: ce7dc080 RCX: 0003 [ 76.796908] RDX: 01c9 RSI: 98cbbe384200 RDI: 0080 [ 76.798471] RBP: a5b680473e08 R08: 7000 R09: 1000 [ 76.799680] R10: 98cbb9d0a700 R11: 7000 R12: 0680 [ 76.800892] R13: ce7dc080 R14: 0004 R15: 98cbbd175000 [ 76.802111] FS: 7fcb03cff540() GS:98cbbfc0() knlGS: [ 76.803512] CS: 0010 DS: ES: CR0: 80050033 [ 76.804505] CR2: 06d0 CR3: 3927e000 CR4: 000406f0 [ 76.805766] Call Trace: [ 76.806208] page_idle_bitmap_read+0xdf/0x170 [ 76.806966] sysfs_kf_bin_read+0x4d/0x80 [ 76.807637] kernfs_fop_read+0xad/0x180 [ 76.808324] __vfs_read+0x1b/0x40 [ 76.808907] vfs_read+0x8e/0x130 [ 76.809473] SyS_read+0x55/0xc0 [ 76.810026] do_syscall_64+0x73/0x130 [ 76.810668] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 76.811532] RIP: 0033:0x7fcb03800081 [ 76.812171] RSP: 002b:7fff25fa65c8 EFLAGS: 0246 ORIG_RAX: [ 76.813456] RAX: ffda RBX: 0002 RCX: 7fcb03800081 [ 76.814683] RDX: 0002 RSI: 7fcb03b42000 RDI: 0003 [ 76.816183] RBP: 0002 R08: R09: [ 76.817408] R10: 0022 R11: 0246 R12: 7fcb03b42000 [ 76.818594] R13: 0003 R14: 1000 R15: 0002 [ 76.819816] Code: f0 0f b1 0a 75 7d 48 8b 03 48 89 c2 48 c1 e8 33 83 e0 07 48 c1 ea 36 48 8d 0c 40 4c 8d 24 88 49 c1 e4 07 4c 03 24 d5 c0 b5 05 ae <49> 8b 44 24 50 48 8d b8 80 a1 02 00 e8 04 26 73 00 48 8b 53 20 [ 76.823041] RIP: page_idle_get_page+0xcb/0x1a0 RSP: a5b680473df0 [ 76.824117] CR2: 06d0 [ 76.824720] ---[ end trace 414e619d6174dd72 ]--- Can get full dmesg output if desired. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769265/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767832] Re: ASUS touchpad right button not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767832 Title: ASUS touchpad right button not working Status in Ubuntu-Certification: Invalid Status in linux package in Ubuntu: Expired Bug description: On my ASUS T304UA, the right button of the trackpad generates no input event whereas the left button and the left half part of the middle button works (checked with libinput-debug-events). I checked with the latest available kernel: 4.17.0-041700rc2-generic Needless to say that the trackpad perfectly works under Windows. The device is: Bus 001 Device 005: ID 0b05:184a ASUSTek Computer, Inc. I guess that the corresponding kernel driver is: hid_multitouch Example of libinput-debug-events : left click then right click : -event17 POINTER_BUTTON+1.11sBTN_LEFT (272) pressed, seat count: 1 event17 POINTER_BUTTON+1.23sBTN_LEFT (272) released, seat count: 0 It seems that there is a bug in the trackpad driver... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/1767832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769217] Re: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: package linux-image-extra-4.4.0-98-generic is not ready for configuration cannot
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769217 Title: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: package linux-image-extra-4.4.0-98-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Expired Bug description: I am using Ubuntu 16.04.LTS on my computer. When I updated Ubuntu recently, I realized after restart, that the Image on screen was much too large in order to work further. I suspect that the graphic card is not addressed correctly when starting the operating system. Please, what can I do (press any keys ?) to get the right size on screen? (Momentarily I have to start Ubuntu in the recovery mode in order to get a proper picture on screen.) Moreover I realized that actualization is not working properly (it stops after some time and is only partially finished). Can you help me? Thanks Stefan ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lietz 1845 F pulseaudio Date: Fri May 4 18:55:33 2018 DuplicateSignature: package:linux-image-extra-4.4.0-98-generic:4.4.0-98.121 Processing triggers for libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) ... dpkg: error processing package linux-image-extra-4.4.0-98-generic (--configure): package linux-image-extra-4.4.0-98-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.4.0-98-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=7a220dfb-d9a0-440a-a129-b99139c74029 InstallationDate: Installed on 2016-06-05 (698 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: FUJITSU SIEMENS ESPRIMO E5730 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic root=UUID=f8fc32b7-529a-4437-8494-73287200062d ro recovery nomodeset 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-98-generic 4.4.0-98.121 failed to install/upgrade: package linux-image-extra-4.4.0-98-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2009 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.15.2824.A1 dmi.board.name: D2824-A1 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2824-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.15.2824.A1:bd06/03/2009:svnFUJITSUSIEMENS:pnESPRIMOE5730:pvr:rvnFUJITSUSIEMENS:rnD2824-A1:rvrS26361-D2824-A1:cvnFUJITSUSIEMENS:ct3:cvr: dmi.product.name: ESPRIMO E5730 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768583] Re: Touchpad is not detected in 'Asus GM501GS'
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768583 Title: Touchpad is not detected in 'Asus GM501GS' Status in linux package in Ubuntu: Expired Bug description: I bought a new laptop Asus GM501GS, and the touch-pad is not working. I tried adding i8042.reset, i8042.nohup, etc. And nothing worked. Besides, when installed Ubuntu, the touch-pad also stopped working in BIOS and Windows. When I delete Ubuntu partition and fresh install Windows again. Touch- pad starts working properly. 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: Wed May 2 19:48:44 2018 InstallationDate: Installed on 2018-05-01 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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/+bug/1768583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769423] Re: Xbox One S Bluetooth Controller Won't Connect
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769423 Title: Xbox One S Bluetooth Controller Won't Connect Status in linux package in Ubuntu: Expired Bug description: When attempting to connect a bluetooth xbox controller the controller would fail to connect. Either, an error message saying "This device could not be connected" or the controller would connect, then disconnect constantly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-21-lowlatency 4.15.0-21.22 ProcVersionSignature: Ubuntu 4.15.0-21.22-lowlatency 4.15.17 Uname: Linux 4.15.0-21-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun May 6 13:52:05 2018 InstallationDate: Installed on 2018-04-17 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) 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/+bug/1769423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769655] Re: package linux-image-4.4.0-101-generic 4.4.0-101.124 failed to install/upgrade: package linux-image-4.4.0-101-generic is not ready for configuration cannot configure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769655 Title: package linux-image-4.4.0-101-generic 4.4.0-101.124 failed to install/upgrade: package linux-image-4.4.0-101-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Expired Bug description: ao baixar atu8alizações ele reporta que ha problemas. muito boa a versaO uBUNTU 16.04 , INFORME WENO EMAIL jesus.alci...@hotmail.com ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-101-generic 4.4.0-101.124 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jesus 1760 F pulseaudio Date: Sun May 6 18:47:49 2018 DuplicateSignature: package:linux-image-4.4.0-101-generic:4.4.0-101.124 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package linux-image-4.4.0-101-generic (--configure): package linux-image-4.4.0-101-generic is not ready for configuration ErrorMessage: package linux-image-4.4.0-101-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=7b9708f2-55b7-4e3b-96e9-09c745d1965c InstallationDate: Installed on 2016-12-16 (506 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: POSITIVO POS-AG31AP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=8a77ee4c-e429-4fcf-9294-8cdc7c4f3d7c ro quiet splash 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.18 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.4.0-101-generic 4.4.0-101.124 failed to install/upgrade: package linux-image-4.4.0-101-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2009 dmi.bios.vendor: Desenvolvida para Positivo Informatica SA dmi.bios.version: 0203 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: POS-AG31AP dmi.board.vendor: Positivo Informatica SA dmi.board.version: x.xx dmi.chassis.asset.tag: dmi.chassis.type: 3 dmi.chassis.vendor: POSITIVO dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDesenvolvidaparaPositivoInformaticaSA:bvr0203:bd07/06/2009:svnPOSITIVO:pnPOS-AG31AP:pvrSystemVersion:rvnPositivoInformaticaSA:rnPOS-AG31AP:rvrx.xx:cvnPOSITIVO:ct3:cvrChassisVersion: dmi.product.name: POS-AG31AP dmi.product.version: System Version dmi.sys.vendor: POSITIVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1780519 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: Incomplete Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] Re: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Kernel logs ** Attachment added: "kernel_log_4_15_lm19_nvidia_propret.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+attachment/5160646/+files/kernel_log_4_15_lm19_nvidia_propret.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/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: New Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780519] [NEW] Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Public bug reported: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780519 Title: Laptop HP 8570w : ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Status in linux package in Ubuntu: New Bug description: dmesg | grep ASPM [0.053218] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [2.129058] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [2.131852] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [3.144009] pci :00:01.0: ASPM: Could not configure common clock [9.675052] iwlwifi :25:00.0: can't disable ASPM; OS doesn't have ASPM control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779817] Re: no internet after suspending
search for "r8168 for 4.15 kernel" and you will see problem from across many linux distributions. I am trying to follow https://www.unixblogger.com/2016/08/11/how-to-get-your-realtek- rtl8111rtl8168-working-updated-guide/ and change the "more stable" r8168. Neither the Ubuntu repo of r8168 nor the realtek download of r8168 are compiling cleanly however. Seems like kernel 4.15 included changes to an interface previously "setup_timer" is now "timer_setup" but it might not be as simple as a name change. I'm looking at this patch for a different project (not r8168) : http://patchwork.dpdk.org/patch/31739/ . You will see more logic there than a simple name change. (It could be an unrelated change, I can't tell.) So maybe the 4.15 update for the r8169 driver didn't get the necessary logic changes and that is why there is a bug (?) I'm trying to compile the Realtek r8168 version now, just using pointer casts to get it to compile. Does @kaihengfeng have information about changes to r8169? Ubuntu has a repo r8168-dkms but (in my setup) it has many more compile errors than realtek's r8168 :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: no internet after suspending Status in linux package in Ubuntu: Confirmed Bug description: When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T 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.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. 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/1779817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780470] Re: BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late)
I built a test kernel[1] (3.13.0-153.203+hf185584v20180706b4)on my PPA containing the 3 fixes as suggested by the VMware author[2]. If you are affected by this problem, feel free to use it for testing and update this bug with any feedbacks. [1] - PPA sudo add-apt-repository ppa:slashd/sf185584 sudo apt-get update [2] - https://patchwork.kernel.org/patch/9948741/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780470 Title: BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Bug description: [Impact] It has been brought to my attention that VMware Guest[1] randomly crashes after moving the VMs from a VMware "5.5" env to VMware 6.5 env. The crashes started after the above move (5.5->6.5). Notes: * The crashes wasn't present in VMware 5.5 (with the same VMs). Only started to happens with Vmware 6.5 * The Trusty HWE kernel (Ubuntu-4.4.0-X) doesn't exhibit the situation on VMware 6.5. Here's the stack trace took from the .vmss converted to be readable by Linux debugger: [17007961.187411] BUG: scheduling while atomic: swapper/3/0/0x0100 [17007961.189794] Modules linked in: arc4 md4 nls_utf8 cifs nfsv3 nfs_acl nfsv4 nfs lockd sunrpc fscache veth ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack bridge stp llc aufs vmw_vsock_vmci_transport vsock ppdev vmwgfx serio_raw coretemp ttm drm vmw_balloon vmw_vmci shpchp i2c_piix4 parport_pc mac_hid xfs lp libcrc32c parport psmouse floppy vmw_pvscsi vmxnet3 pata_acpi [17007961.189856] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.13.0-135-generic #184-Ubuntu [17007961.189862] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 10/22/2013 [17007961.189867] 88042f263b90 8172d959 88042f263d30 [17007961.189874] 88042f273180 88042f263ba0 81726d8c 88042f263c00 [17007961.189879] 81731c8f 880428c29800 00013180 880428c25fd8 [17007961.189885] Call Trace: [17007961.189889] [] dump_stack+0x64/0x82 [17007961.189913] [] __schedule_bug+0x4c/0x5a [17007961.189922] [] __schedule+0x6af/0x7f0 [17007961.189929] [] schedule+0x29/0x70 [17007961.189935] [] schedule_timeout+0x279/0x310 [17007961.189947] [] ? select_task_rq_fair+0x56b/0x6f0 [17007961.189955] [] ? enqueue_task_fair+0x422/0x6d0 [17007961.189962] [] ? sched_clock_cpu+0xb5/0x100 [17007961.189971] [] wait_for_completion+0xa6/0x150 [17007961.189977] [] ? wake_up_state+0x20/0x20 [17007961.189987] [] ? __call_rcu+0x2d0/0x2d0 [17007961.189993] [] wait_rcu_gp+0x4b/0x60 [17007961.18] [] ? ftrace_raw_output_rcu_utilization+0x50/0x50 [17007961.190006] [] synchronize_sched+0x3a/0x50 [17007961.190047] [] vmci_event_unsubscribe+0x76/0xb0 [vmw_vmci] [17007961.190063] [] vmci_transport_destruct+0x21/0xe0 [vmw_vsock_vmci_transport] [17007961.190078] [] vsock_sk_destruct+0x17/0x60 [vsock] [17007961.190087] [] __sk_free+0x1f/0x180 [17007961.190092] [] sk_free+0x19/0x20 [17007961.190102] [] vmci_transport_recv_stream_cb+0x200/0x2f0 [vmw_vsock_vmci_transport] [17007961.190114] [] vmci_datagram_invoke_guest_handler+0xbc/0xf0 [vmw_vmci] [17007961.190126] [] vmci_dispatch_dgs+0xcf/0x230 [vmw_vmci] [17007961.190138] [] tasklet_action+0x11e/0x130 [17007961.190145] [] __do_softirq+0xfc/0x310 [17007961.190153] [] irq_exit+0x105/0x110 [17007961.190161] [] do_IRQ+0x56/0xc0 [17007961.190170] [] common_interrupt+0x6d/0x6d [17007961.190173] [] ? native_safe_halt+0x6/0x10 [17007961.190190] [] default_idle+0x1f/0x100 [17007961.190197] [] arch_cpu_idle+0x26/0x30 [17007961.190205] [] cpu_startup_entry+0xc1/0x2b0 [17007961.190214] [] start_secondary+0x21d/0x2d0 [17007961.190221] bad: scheduling from the idle thread! [Other infos] I have identified a patch series[2] which seems to fix the exact same situation. A full discussion can be found on patchworks[3], suggesting a certain patch series[2] authored by Vmware. [1] - VM details : Release: Trusty Kernel: Ubuntu-3.13.0-135 [2] Upstream patch series 8ab18d7 VSOCK: Detach QP check should filter out non matching QPs. 8566b86 VSOCK: Fix lockdep issue. 4ef7ea9 VSOCK: sock_put wasn't safe to call in interrupt context commit 4ef7ea9 Author: Jorgen Hansen Date: Wed Oct 21 04:53:56 2015 -0700 VSOCK: sock_put wasn't safe to call in interrupt context ... Multiple customers have been hitting this issue when using VMware tools on vSphere 2015. ... VSphere 2015 == VMware 6.0 (release
[Kernel-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
You are correct that the kernel reports a supported abi, and currently the abi does not export that it is supporting link mediation for sockets. However the kernel is currently enforcing link mediation on sockets and there are reasons to want to continue to do so. The plan would be to let the parser know that existing kernel abis have a quirk where they are not correctly advertising the abi. The parser would then correctly generate policy for both old and new kernels. The patch would be rolled out in upstream apparmor point releases 2.10.4, 2.11.2, 2.12.1, and 2.13.1, as well as being dropped into supported ubuntu releases. Suse and Debian will pickup the bug fixes from upstream, they are fairly good about picking up point release bug fixes. Updating the userspace probably provides us the widest roll out of the fix possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776155] Re: Touchpad detected as SYNA3602, does not work at all.
How do you check 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/1776155 Title: Touchpad detected as SYNA3602, does not work at all. Status in linux package in Ubuntu: Confirmed Bug description: On my cheaper-end slimline laptop/netbook the touchpad is (I think wrongly) detected by Linux to be the SYNA 3602. Anyway it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. External mouse works fine. It seems that there is a bug reported on a similar issue, although I can not confirm that my touchpad hardware is exactly the same: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625 If so, there may be a whole new generation of slimline Windows 10 netbooks that have this problem. martin@alanah:~$ cat /proc/bus/input/devices I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0018 Vendor=0911 Product=5288 Version=0100 N: Name="SYNA3602:00 0911:5288 Touchpad" P: Phys=i2c-SYNA3602:00 S: Sysfs=/devices/pci:00/:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15 U: Uniq= H: Handlers=mouse0 event14 B: PROP=5 B: EV=1b B: KEY=e420 3 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=045e Product=00b9 Version=0111 N: Name="Microsoft Microsoft USB Wireless Mouse" P: Phys=usb-:00:15.0-1/input0 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-1/1-1:1.0/0003:045E:00B9.0002/input/input16 U: Uniq= H: Handlers=mouse1 event15 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1c3 B: MSC=10 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: MATE Date: Mon Jun 11 07:57:56 2018 InstallationDate: Installed on 2018-04-25 (46 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1536 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-25 (48 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: Multicom Multicom U230 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c7a82fee-6e9d-491d-a38d-f5d6bdb4a930 ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ORO10x.WP313P.NHNAUHL01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrORO10x.WP313P.NHNAUHL01:bd09/15/2017:svnMulticom:pnMulticomU230:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: U-series dmi.product.name: Multicom U230 dmi.product.version: Default string dmi.sys.vendor: Multicom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678213] Re: linux-aws does not provide linux-image-extra-$(uname -r)
The point of this bug report is that the fix to LP#1672464 removed a binary package name from xenial - this is like changing an API contract. But xenial has long since shipped with this breakage, so this report can be ignored. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1678213 Title: linux-aws does not provide linux-image-extra-$(uname -r) Status in linux-aws package in Ubuntu: Incomplete Bug description: I have a large number of image builds based on xenial that automatically install linux-image-extra-$(uname -r) to ensure aufs is available. The recent fix to https://bugs.launchpad.net/ubuntu/+source/linux- aws/+bug/1672464 ensures aufs is available, but it breaks a lot of automation. Is it possible for linux-aws to Provide linux-image-extra-$(uname -r) to prevent breaking existing automation? Ross To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1678213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438510]
Just want to confirm this bug with SONY MDR-XB650BT on Kernel 4.14.52-1-MANJARO. The script from Comment 38 helped me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Status in pulseaudio source package in Xenial: Fix Released Bug description: [Impact] Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and check the device's current "Mode". 3. If the current Mode is not yet A2DP then try to set it to A2DP Expected: The mode is either A2DP by default or can be set to it. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780499] [NEW] Bionic update: upstream stable patchset 2018-07-06
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2018-07-06 (ported from v4.14.41 and v4.16.9) from git://git.kernel.org/ sched/core: Fix possible Spectre-v1 indexing for sched_prio_to_weight[] drm/nouveau/ttm: don't dereference nvbo::cli, it can outlive client drm/i915: Adjust eDP's logical vco in a reliable place. drm/ttm: Use GFP_TRANSHUGE_LIGHT for allocating huge pages bdi: Fix use after free bug in debugfs_remove() i2c: dev: prevent ZERO_SIZE_PTR deref in i2cdev_ioctl_rdwr() perf/x86: Fix possible Spectre-v1 indexing for x86_pmu::event_map() perf/core: Fix possible Spectre-v1 indexing for ->aux_pages[] perf/x86/msr: Fix possible Spectre-v1 indexing in the MSR driver perf/x86/cstate: Fix possible Spectre-v1 indexing for pkg_msr perf/x86: Fix possible Spectre-v1 indexing for hw_perf_event cache_* tracing/uprobe_event: Fix strncpy corner case sched/autogroup: Fix possible Spectre-v1 indexing for sched_prio_to_weight[] smb3: directory sync should not return an error nvme: add quirk to force medium priority for SQ creation thermal: exynos: Propagate error value from tmu_read() thermal: exynos: Reading temperature makes sense only when TMU is turned on Bluetooth: btusb: Only check needs_reset_resume DMI table for QCA rome chipsets Revert "Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174" cpufreq: schedutil: Avoid using invalid next_freq atm: zatm: Fix potential Spectre v1 net: atm: Fix potential Spectre v1 drm/atomic: Clean private obj old_state/new_state in drm_atomic_state_default_clear() drm/atomic: Clean old_state/new_state in drm_atomic_state_default_clear() drm/i915: Fix drm:intel_enable_lvds ERROR message in kernel log drm/vc4: Fix scaling of uni-planar formats can: hi311x: Work around TX complete interrupt erratum can: hi311x: Acquire SPI lock on ->do_get_berr_counter can: kvaser_usb: Increase correct stats counter in kvaser_usb_rx_can_msg() ceph: fix rsize/wsize capping in ceph_direct_read_write() mm, oom: fix concurrent munlock and oom reaper unmap, v3 mm: sections are not offlined during memory hotremove z3fold: fix reclaim lock-ups tracing: Fix regex_match_front() to not over compare the test string dm integrity: use kvfree for kvmalloc'd memory libata: Apply NOLPM quirk for SanDisk SD7UB3Q*G1001 SSDs rfkill: gpio: fix memory leak in probe error path gpio: fix error path in lineevent_create gpio: fix aspeed_gpio unmask irq gpioib: do not free unrequested descriptors bdi: Fix oops in wb_workfn() bdi: wake up concurrent wb_shutdown() callers. tcp: fix TCP_REPAIR_QUEUE bound checking perf: Remove superfluous allocation error check memcg: fix per_node_info cleanup inetpeer: fix uninit-value in inet_getpeer soreuseport: initialise timewait reuseport field ipv4: fix uninit-value in ip_route_output_key_hash_rcu() dccp: initialize ireq->ir_mark net: fix uninit-value in __hw_addr_add_ex() net: initialize skb->peeked when cloning net: fix rtnh_ok() netlink: fix uninit-value in netlink_sendmsg crypto: af_alg - fix possible uninit-value in alg_bind() kcm: Call strp_stop before strp_done in kcm_attach netfilter: ebtables: don't attempt to allocate 0-sized compat array ipvs: fix rtnl_lock lockups caused by start_sync_thread ext4: prevent right-shifting extents beyond EXT_MAX_BLOCKS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches
[Kernel-packages] [Bug 1780137] Re: [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap
I would be useful to see if a non-SMP boot will cause the same issue; if it only occurs in SMP boots then we know it's a lower level locking/race style of 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/1780137 Title: [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: We're seeing a very reproducible regression in the bionic kernel triggered by the stress-ng chdir test performed by the Ubuntu certification suite. We see this on both the HiSilicon D05 arm64 server and the HiSilicon D06 arm64 server. We have been unable to reproduce on other servers so far. [Test Case] $ sudo apt-add-repository -y ppa:hardware-certification/public $ sudo apt install -y canonical-certification-server $ sudo mkfs.ext4 /dev/sda1 (Obviously, this should not be your root disk!!) $ sudo /usr/lib/plainbox-provider-checkbox/bin/disk_stress_ng sda --base-time 240 --really-run This test runs a series of stress-ng tests against /dev/sda, and fails on the "chdir" test. To speed up reproduction, reduce the test list to just "chdir" in the disk_stress_ng script. Attempts to reproduce this directly with stress-ng have failed - presumably because of other environment setup that this script performs (e.g. setting aio-max-nr to 524288). Our reproduction test is to use a non-root disk because it can lead to corruption, and mkfs.ext4'ing the partition just before running the test, to get to a pristine fs state. I bisected this down to the following commit: commit 555bc9b1421f10d94a1192c7eea4a59faca3e711 Author: Theodore Ts'o Date: Mon Feb 19 14:16:47 2018 -0500 ext4: don't update checksum of new initialized bitmaps BugLink: http://bugs.launchpad.net/bugs/1773233 commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
409acdd does NOT have the bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779357] Re: linux-oem: 4.15.0-1010.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1779357 Title: linux-oem: 4.15.0-1010.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780115] Re: linux-aws: 4.15.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1780115 Title: linux-aws: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780119] Re: linux-kvm: 4.15.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1780119 Title: linux-kvm: 4.15.0-1014.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
#43 worked for me. Thanks for the 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/1764645
Title:
Bluetooth not working
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was discovered in Bionic. The regression was introduced by
mainline commit f44cb4b19ed4, which then made it's way into Bionic in
4.15.0-14 as commit c91729972ac6 via stable updates.
This regression is fixed by mainline commit 803cdb8ce584. Commit
803cdb8ce584 was also cc'd to stable. However, it has not landed in
upstream stable 4.15 or Bionic.
== Fix ==
803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012
models")
== Regression Potential ==
Low. This fix has also been cc'd to upstream stable, so it has had
additonal upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I've installed the Ubuntu Bionic Beta 2 and everything works fine but
the bluetooth (perfectly working with Xenial). In bluetooth control
panel the slider is impossible to move to "on".
1) Ubuntu Release (via 'lsb_release -rd')
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) Version of package (apt-cache policy gnome-bluetooth)
gnome-bluetooth:
Installato: 3.28.0-2
Candidato: 3.28.0-2
Tabella versione:
*** 3.28.0-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
I expected to switch on the bluetooth.
4) What happened instead
Bluetooth won't switch on.
5) Output of rfkill list is:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
Network Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
size Mini PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
Ethernet [1969:10a1] (rev 10)
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 17.715399] Bluetooth: Core ver 2.22
[ 17.715414] Bluetooth: HCI device and connection manager initialized
[ 17.715416] Bluetooth: HCI socket layer initialized
[ 17.715418] Bluetooth: L2CAP socket layer initialized
[ 17.715422] Bluetooth: SCO socket layer initialized
[ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
[ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.600649] Bluetooth: BNEP filters: protocol multicast
[ 18.600651] Bluetooth: BNEP socket layer initialized
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stormy 1484 F pulseaudio
/dev/snd/controlC0: stormy 1484 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 17 08:46:30 2018
HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: ASUSTeK COMPUTER INC. G750JH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-15-generic N/A
linux-backports-modules-4.15.0-15-generic N/A
linux-firmware 1.173
SourcePackage: linux
[Kernel-packages] [Bug 1780309] Re: [Hyper-V] Please set CONFIG_BLK_DEV_DRBD to "m"
https://lists.ubuntu.com/archives/kernel-team/2018-July/093725.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1780309 Title: [Hyper-V] Please set CONFIG_BLK_DEV_DRBD to "m" Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Bionic: In Progress Bug description: DRBD modules are not loadable nor are they in extras. Please set CONFIG_BLK_DEV_DRBD to "m" in the linux-azure kernel config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1780309/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779242] Re: package linux-headers-3.13.0-143 3.13.0-143.192 failed to install/upgrade: não pode copiar dados extráidos para './usr/src/linux-headers-3.13.0-143/include/media/s5
*** This bug is a duplicate of bug 1779241 *** https://bugs.launchpad.net/bugs/1779241 ** This bug has been marked a duplicate of bug 1779241 package linux-headers-3.13.0-143 3.13.0-143.192 failed to install/upgrade: não pode copiar dados extráidos para './usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para '/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de ficheiro ou stream inesperado ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779242 Title: package linux-headers-3.13.0-143 3.13.0-143.192 failed to install/upgrade: não pode copiar dados extráidos para './usr/src /linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para '/usr/src /linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de ficheiro ou stream inesperado Status in linux package in Ubuntu: New Bug description: my update gave error in several packages, and I can not and can not update my ubunt 12.4 to the 16 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-headers-3.13.0-143 3.13.0-143.192 ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39 Uname: Linux 3.13.0-143-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 AptOrdering: linux-headers-3.13.0-143: Install linux-headers-3.13.0-143: Configure linux-headers-3.13.0-143-generic: Configure linux-headers-generic: Configure linux-generic: Configure Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anderson 1875 F pulseaudio Date: Thu Jun 28 11:51:14 2018 DpkgHistoryLog: Start-Date: 2018-06-28 11:50:57 Commandline: apt-get install -f Install: linux-headers-3.13.0-143:i386 (3.13.0-143.192, automatic) DuplicateSignature: package:linux-headers-3.13.0-143:3.13.0-143.192:não pode copiar dados extráidos para './usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para '/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de ficheiro ou stream inesperado ErrorMessage: não pode copiar dados extráidos para './usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para '/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de ficheiro ou stream inesperado HibernationDevice: RESUME=UUID=c88c53c8-7acf-443f-852d-b95b388a9d0e InstallationDate: Installed on 2017-10-27 (244 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Acer Aspire 4739Z PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-143-generic root=UUID=e90c1af9-730a-46ca-9a75-08496280e0f2 ro locale=pt_BR 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-9ubuntu1.14 SourcePackage: linux Title: package linux-headers-3.13.0-143 3.13.0-143.192 failed to install/upgrade: não pode copiar dados extráidos para './usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para '/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: HMA_CP dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.05:bd05/30/2011:svnAcer:pnAspire4739Z:pvrV1.05:rvnAcer:rnHMA_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 4739Z dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777696] Re: hisi_sas: Failures during host reset
I ran the test case on a D06 system w/ the 4.15.0-26.28 kernel and it survived. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777696 Title: hisi_sas: Failures during host reset Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] When error handling progresses to host reset, several issues may prevent the system from recovering, therefore requiring a system power cycle. [Test Case] $ iozone -a & $ while :; do sudo sg_reset --device /dev/sda; sleep 5; done [Fix] There is a race between device removal and host reset which can cause the driver to hang, preventing the user from accessing attached devices until a reboot. Fix this by adding locking around the critical path. After a soft host reset, commands maybe sent to the device before the hardware is ready to receive them. This can result in additional errors when the user access the device. Fix this by blocking commands until the hardware has been reinitialized. Stale PHY events may still get processed by the driver after reset. This can cause e.g. ports to be detached because an old pre-reset "phy down" event gets processed, causing the user to lose access to attached devices. Fix this by filtering out pre-reset PHY events. Resource starvation can occur after a "clear nexus ha" reset. Fix this by releasing those resources during the reset. [Regression Risk] The required fixes are localized to the hisi_sas driver. This driver is only used by two platforms supported by Ubuntu: HiSilicon D05 and HiSilicon D06. We will directly verify these fixes on those platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777734] Re: hisi_sas: Add missing PHY spinlock init
Smoke tested on D05 and D06 systems. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/134 Title: hisi_sas: Add missing PHY spinlock init Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] This is a code correctness issue found during code review. From my reading of the code, the spin_lock will always happen to have just been devm_kcalloc'd, which uses GFP_ZERO, before spin_lock_init() needs to be called. That may make the current code safe, but relying on that coincidence seems dangerous. There's also various debugging facilities in the kernel that appear to rely on proper spinlock initialization, and those may currently be broken. [Test Case] Boot test to look for regressions. [Fix] Backport a fix from the scsi maintainer's 4.19 queue which adds a spin_lock_init() call. [Regression Risk] The fix is limited to the hisi_sas driver and is obviously correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777736] Re: hisi_sas_v3_hw: internal task abort: timeout and not done.
Smoke tested on D06 system. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/136 Title: hisi_sas_v3_hw: internal task abort: timeout and not done. Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] On deployments with lots of disks, timeouts can occur that escalate into nexus resets. This can cause disk devices to disappear from the system, possibly requiring a reboot to recover: [18324.951189] cq: iptt:892, task:8026fbde5000, cmp_st:3, err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:16,io_cfg_err_code:0,err_code:0, ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0 [18324.951190] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0 [18324.951191] cmd table: 0x0,0x0,0x0,0x0,0x0 [18324.951192] itct: 0x12fa0345,0x5000cca25d31dac1,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0 [18324.951334] hisi_sas_v3_hw :74:02.0: slot complete: task(8026fbde5000) ignored [18325.039774] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0 [18325.044467] cmd table: 0x0,0x0,0x0,0x0,0x0 [18325.048553] itct: 0x12fa0345,0x5000c50094c65c55,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0 [18325.057058] hisi_sas_v3_hw :74:02.0: slot complete: task(8027dc8e7500) ignored [18326.951312] cq: iptt:1705, task:8027820d0200, cmp_st:3, err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:18,io_cfg_err_code:0,err_code:0, ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0 [18326.968247] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0 [18326.972938] cmd table: 0x0,0x0,0x0,0x0,0x0 [18326.977023] itct: 0x12fa0345,0x5000cca0803e9c1d,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0 [18326.985496] hisi_sas_v3_hw :74:02.0: slot complete: task(8027820d0200) ignored [18329.384695] hisi_sas_v3_hw :74:02.0: internal task abort: timeout and not done. [18329.392344] hisi_sas_v3_hw :74:02.0: start dump all regs,reason:abort timeout! [18329.399904] ***DUMP IS DISABLED*** [18329.405467] dump reg fail. [18329.408162] hisi_sas_v3_hw :74:02.0: I_T nexus reset: internal abort (-5) [18329.936017] cq: iptt:649, task:8027981f8500, cmp_st:3, err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:19,io_cfg_err_code:0,err_code:0, ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0 [18329.936154] cq: iptt:1091, task:8026ff666d00, cmp_st:3, err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:49,io_cfg_err_code:0,err_code:0, ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0 [18329.936155] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0 [18329.936156] cmd table: 0x0,0x0,0x0,0x0,0x0 [18329.936158] itct: 0x12fa0345,0x5000cca2552b2855,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0 [18329.936301] hisi_sas_v3_hw :74:02.0: slot complete: task(8026ff666d00) ignored [Test Case] This was seen on a system with 100s of disks, something I don't have access to, so verification testing will be regression-only. [Fix] A fix queued in the scsi maintainer's tree adjusts some magic registers in the controller, and that somehow fixes the problem (I don't have programming docs for this controller, so I can only hand-wave here). [Regression Risk] The fix is localized to the hisi_sas_v3_hw driver, which is only used in Ubuntu for the D06 platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779357] Re: linux-oem: 4.15.0-1010.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Uploaded + kernel-stable-phase-changed:Friday, 06. July 2018 20:32 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 - phase: Uploaded - kernel-stable-phase-changed:Friday, 06. July 2018 20:32 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1779357 Title: linux-oem: 4.15.0-1010.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766857] Re: [Hyper-V] KVP daemon fails to start
Did you notice any other issues that occur when testing the test kernel posted in comment #12. The second issue posted in the bug is resolved by changing the definition of KVP_CONFIG_LOC in hv_kvp_daemon.c: --- tools/hv/hv_kvp_daemon.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/hv/hv_kvp_daemon.c b/tools/hv/hv_kvp_daemon.c index 4c99c57..e969057 100644 --- a/tools/hv/hv_kvp_daemon.c +++ b/tools/hv/hv_kvp_daemon.c @@ -95,7 +95,7 @@ static struct utsname uts_buf; #define KVP_CONFIG_LOC "/var/lib/hyperv" #ifndef KVP_SCRIPTS_PATH -#define KVP_SCRIPTS_PATH "/usr/libexec/hypervkvpd/" +#define KVP_SCRIPTS_PATH "/usr/sbin/" #endif #define KVP_NET_DIR "/sys/class/net/" -- 2.7.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766857 Title: [Hyper-V] KVP daemon fails to start Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-azure source package in Bionic: Invalid Bug description: While testing Bionic daily build with kernel 4.15.0-20-generic we saw that there are 2 issues with the KVP daemon: 1. KVP daemon crash after boot. Opened a different bug for this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640 2. After the KVP daemon is being started the following messages appear: Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found The above binaries are present on the system, but the their actual path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info. Either the hv_get_dhcp_info and hv_get_dns_info binaries should be placed in the location where the daemon is looking for (/usr/libexec/hypervkvpd/), or the daemon should be set to search for the binaries in the /usr/sbin directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776155] Re: Touchpad detected as SYNA3602, does not work at all.
Which protocol does the touchpad use, PS/2 or HID protocol? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776155 Title: Touchpad detected as SYNA3602, does not work at all. Status in linux package in Ubuntu: Confirmed Bug description: On my cheaper-end slimline laptop/netbook the touchpad is (I think wrongly) detected by Linux to be the SYNA 3602. Anyway it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. External mouse works fine. It seems that there is a bug reported on a similar issue, although I can not confirm that my touchpad hardware is exactly the same: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625 If so, there may be a whole new generation of slimline Windows 10 netbooks that have this problem. martin@alanah:~$ cat /proc/bus/input/devices I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0018 Vendor=0911 Product=5288 Version=0100 N: Name="SYNA3602:00 0911:5288 Touchpad" P: Phys=i2c-SYNA3602:00 S: Sysfs=/devices/pci:00/:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15 U: Uniq= H: Handlers=mouse0 event14 B: PROP=5 B: EV=1b B: KEY=e420 3 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=045e Product=00b9 Version=0111 N: Name="Microsoft Microsoft USB Wireless Mouse" P: Phys=usb-:00:15.0-1/input0 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-1/1-1:1.0/0003:045E:00B9.0002/input/input16 U: Uniq= H: Handlers=mouse1 event15 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1c3 B: MSC=10 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: MATE Date: Mon Jun 11 07:57:56 2018 InstallationDate: Installed on 2018-04-25 (46 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1536 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-25 (48 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: Multicom Multicom U230 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c7a82fee-6e9d-491d-a38d-f5d6bdb4a930 ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ORO10x.WP313P.NHNAUHL01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrORO10x.WP313P.NHNAUHL01:bd09/15/2017:svnMulticom:pnMulticomU230:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: U-series dmi.product.name: Multicom U230 dmi.product.version: Default string dmi.sys.vendor: Multicom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779830] Re: vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
Xenial SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-July/093718.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1779830
Title:
vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The following upstream patch (v4.7) is missing in xenial:
450744051d20 ("vfio/pci: Hide broken INTx support from user")
http://scm/kernels/linux-upstream/commit/?id=450744051d20
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779830/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Yep, that's the same version that is installed in my VM. So it looks like the new -26 kernel does not fix the problem for everybody. It worked for me, but doesn't seem to work for you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780137] Re: [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap
Upstream thread: https://lkml.org/lkml/2018/7/6/763 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780137 Title: [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: We're seeing a very reproducible regression in the bionic kernel triggered by the stress-ng chdir test performed by the Ubuntu certification suite. We see this on both the HiSilicon D05 arm64 server and the HiSilicon D06 arm64 server. We have been unable to reproduce on other servers so far. [Test Case] $ sudo apt-add-repository -y ppa:hardware-certification/public $ sudo apt install -y canonical-certification-server $ sudo mkfs.ext4 /dev/sda1 (Obviously, this should not be your root disk!!) $ sudo /usr/lib/plainbox-provider-checkbox/bin/disk_stress_ng sda --base-time 240 --really-run This test runs a series of stress-ng tests against /dev/sda, and fails on the "chdir" test. To speed up reproduction, reduce the test list to just "chdir" in the disk_stress_ng script. Attempts to reproduce this directly with stress-ng have failed - presumably because of other environment setup that this script performs (e.g. setting aio-max-nr to 524288). Our reproduction test is to use a non-root disk because it can lead to corruption, and mkfs.ext4'ing the partition just before running the test, to get to a pristine fs state. I bisected this down to the following commit: commit 555bc9b1421f10d94a1192c7eea4a59faca3e711 Author: Theodore Ts'o Date: Mon Feb 19 14:16:47 2018 -0500 ext4: don't update checksum of new initialized bitmaps BugLink: http://bugs.launchpad.net/bugs/1773233 commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769792] Re: Keyboard and Touchpad do not work after suspend/resume
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-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/1769792 Title: Keyboard and Touchpad do not work after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: My laptop is a Toshiba Satellite C850D with updated 18.04 installed. When resuming from suspend, I have no keyboard and touchpad. dmesg shows "i8042: Can't reactivate KBD port" This looks like a recurring problem, and is just like these: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1142118 Here's the dmesg output from before and after suspending. https://paste.ubuntu.com/p/rsFX9Yw7Xh/ This post also talks about this bit failing for a lot of people! http://lightrush.ndoytchev.com/random-1/i8042quirkoptions Some of the function keys work, such as changing the screen brightness, but the key (fn+F5) does not turn the touchpad back on. I have not yet tried any of the suggested options, as results have been mixed, but I will. 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 May 7 22:01:26 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.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/+bug/1769792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780470] Re: BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late)
** Description changed: [Impact] It has been brought to my attention that VMware Guest[1] randomly crashes after moving the VMs from a VMware "5.5" env to VMware 6.5 env. The crashes started after the above move (5.5->6.5). Notes: * The crashes wasn't present in VMware 5.5 (with the same VMs). Only started to happens with Vmware 6.5 * The Trusty HWE kernel (Ubuntu-4.4.0-X) doesn't exhibit the situation on VMware 6.5. Here's the stack trace took from the .vmss converted to be readable by Linux debugger: [17007961.187411] BUG: scheduling while atomic: swapper/3/0/0x0100 [17007961.189794] Modules linked in: arc4 md4 nls_utf8 cifs nfsv3 nfs_acl nfsv4 nfs lockd sunrpc fscache veth ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack bridge stp llc aufs vmw_vsock_vmci_transport vsock ppdev vmwgfx serio_raw coretemp ttm drm vmw_balloon vmw_vmci shpchp i2c_piix4 parport_pc mac_hid xfs lp libcrc32c parport psmouse floppy vmw_pvscsi vmxnet3 pata_acpi [17007961.189856] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.13.0-135-generic #184-Ubuntu [17007961.189862] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 10/22/2013 [17007961.189867] 88042f263b90 8172d959 88042f263d30 [17007961.189874] 88042f273180 88042f263ba0 81726d8c 88042f263c00 [17007961.189879] 81731c8f 880428c29800 00013180 880428c25fd8 [17007961.189885] Call Trace: [17007961.189889] [] dump_stack+0x64/0x82 [17007961.189913] [] __schedule_bug+0x4c/0x5a [17007961.189922] [] __schedule+0x6af/0x7f0 [17007961.189929] [] schedule+0x29/0x70 [17007961.189935] [] schedule_timeout+0x279/0x310 [17007961.189947] [] ? select_task_rq_fair+0x56b/0x6f0 [17007961.189955] [] ? enqueue_task_fair+0x422/0x6d0 [17007961.189962] [] ? sched_clock_cpu+0xb5/0x100 [17007961.189971] [] wait_for_completion+0xa6/0x150 [17007961.189977] [] ? wake_up_state+0x20/0x20 [17007961.189987] [] ? __call_rcu+0x2d0/0x2d0 [17007961.189993] [] wait_rcu_gp+0x4b/0x60 [17007961.18] [] ? ftrace_raw_output_rcu_utilization+0x50/0x50 [17007961.190006] [] synchronize_sched+0x3a/0x50 [17007961.190047] [] vmci_event_unsubscribe+0x76/0xb0 [vmw_vmci] [17007961.190063] [] vmci_transport_destruct+0x21/0xe0 [vmw_vsock_vmci_transport] [17007961.190078] [] vsock_sk_destruct+0x17/0x60 [vsock] [17007961.190087] [] __sk_free+0x1f/0x180 [17007961.190092] [] sk_free+0x19/0x20 [17007961.190102] [] vmci_transport_recv_stream_cb+0x200/0x2f0 [vmw_vsock_vmci_transport] [17007961.190114] [] vmci_datagram_invoke_guest_handler+0xbc/0xf0 [vmw_vmci] [17007961.190126] [] vmci_dispatch_dgs+0xcf/0x230 [vmw_vmci] [17007961.190138] [] tasklet_action+0x11e/0x130 [17007961.190145] [] __do_softirq+0xfc/0x310 [17007961.190153] [] irq_exit+0x105/0x110 [17007961.190161] [] do_IRQ+0x56/0xc0 [17007961.190170] [] common_interrupt+0x6d/0x6d [17007961.190173] [] ? native_safe_halt+0x6/0x10 [17007961.190190] [] default_idle+0x1f/0x100 [17007961.190197] [] arch_cpu_idle+0x26/0x30 [17007961.190205] [] cpu_startup_entry+0xc1/0x2b0 [17007961.190214] [] start_secondary+0x21d/0x2d0 [17007961.190221] bad: scheduling from the idle thread! [Other infos] I have identified a patch series[2] which seems to fix the exact same situation. A full discussion can be found on patchworks[3], suggesting a certain patch series[2] authored by Vmware. [1] - VM details : Release: Trusty Kernel: Ubuntu-3.13.0-135 [2] Upstream patch series 8ab18d7 VSOCK: Detach QP check should filter out non matching QPs. 8566b86 VSOCK: Fix lockdep issue. 4ef7ea9 VSOCK: sock_put wasn't safe to call in interrupt context + + + commit 586fbeba3fa97614d9124f8d56b4000c81368ff4 + Author: Jorgen Hansen + Date: Wed Oct 21 04:53:56 2015 -0700 + + VSOCK: sock_put wasn't safe to call in interrupt context + + ... + Multiple customers have been hitting this issue when using + VMware tools on vSphere 2015. + ... + + + VSphere 2015 == VMware 6.0 (release in 2015) and late. + + [3] - https://patchwork.kernel.org/patch/9948741/ ** Description changed: [Impact] It has been brought to my attention that VMware Guest[1] randomly crashes after moving the VMs from a VMware "5.5" env to VMware 6.5 env. The crashes started after the above move (5.5->6.5). Notes: * The crashes wasn't present in VMware 5.5 (with the same VMs). Only started to happens with Vmware 6.5 * The Trusty HWE kernel (Ubuntu-4.4.0-X) doesn't exhibit the situation on VMware 6.5. Here's the stack trace took from the .vmss converted to be readable by Linux debugger: [17007961.187411] BUG: scheduling while
[Kernel-packages] [Bug 1690085]
I have the ASUS B350M board and I updated to latest BIOS 4014 but my lock ups started with the latest kernel 4.17 in Arch where the lock up bug reappeared. I have set the idle current setting to typical and so far no lock up in two days, lets see what happens in few days. Keeping my fingers crossed. -- You 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: Confirmed 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
[Kernel-packages] [Bug 1690085]
idle=nomwait fixed all hangs (from https://community.amd.com/thread/224000 -- You 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: Confirmed 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 1780470] Re: BUG: scheduling while atomic (v3.13 + VMware 6.0 and late)
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Summary changed: - BUG: scheduling while atomic (v3.13 + VMware 6.0 and late) + BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780470 Title: BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Bug description: [Impact] It has been brought to my attention that VMware Guest[1] randomly crashes after moving the VMs from a VMware "5.5" env to VMware 6.5 env. The crashes started after the above move (5.5->6.5). Notes: * The crashes wasn't present in VMware 5.5 (with the same VMs). Only started to happens with Vmware 6.5 * The Trusty HWE kernel (Ubuntu-4.4.0-X) doesn't exhibit the situation on VMware 6.5. Here's the stack trace took from the .vmss converted to be readable by Linux debugger: [17007961.187411] BUG: scheduling while atomic: swapper/3/0/0x0100 [17007961.189794] Modules linked in: arc4 md4 nls_utf8 cifs nfsv3 nfs_acl nfsv4 nfs lockd sunrpc fscache veth ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack bridge stp llc aufs vmw_vsock_vmci_transport vsock ppdev vmwgfx serio_raw coretemp ttm drm vmw_balloon vmw_vmci shpchp i2c_piix4 parport_pc mac_hid xfs lp libcrc32c parport psmouse floppy vmw_pvscsi vmxnet3 pata_acpi [17007961.189856] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.13.0-135-generic #184-Ubuntu [17007961.189862] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 10/22/2013 [17007961.189867] 88042f263b90 8172d959 88042f263d30 [17007961.189874] 88042f273180 88042f263ba0 81726d8c 88042f263c00 [17007961.189879] 81731c8f 880428c29800 00013180 880428c25fd8 [17007961.189885] Call Trace: [17007961.189889] [] dump_stack+0x64/0x82 [17007961.189913] [] __schedule_bug+0x4c/0x5a [17007961.189922] [] __schedule+0x6af/0x7f0 [17007961.189929] [] schedule+0x29/0x70 [17007961.189935] [] schedule_timeout+0x279/0x310 [17007961.189947] [] ? select_task_rq_fair+0x56b/0x6f0 [17007961.189955] [] ? enqueue_task_fair+0x422/0x6d0 [17007961.189962] [] ? sched_clock_cpu+0xb5/0x100 [17007961.189971] [] wait_for_completion+0xa6/0x150 [17007961.189977] [] ? wake_up_state+0x20/0x20 [17007961.189987] [] ? __call_rcu+0x2d0/0x2d0 [17007961.189993] [] wait_rcu_gp+0x4b/0x60 [17007961.18] [] ? ftrace_raw_output_rcu_utilization+0x50/0x50 [17007961.190006] [] synchronize_sched+0x3a/0x50 [17007961.190047] [] vmci_event_unsubscribe+0x76/0xb0 [vmw_vmci] [17007961.190063] [] vmci_transport_destruct+0x21/0xe0 [vmw_vsock_vmci_transport] [17007961.190078] [] vsock_sk_destruct+0x17/0x60 [vsock] [17007961.190087] [] __sk_free+0x1f/0x180 [17007961.190092] [] sk_free+0x19/0x20 [17007961.190102] [] vmci_transport_recv_stream_cb+0x200/0x2f0 [vmw_vsock_vmci_transport] [17007961.190114] [] vmci_datagram_invoke_guest_handler+0xbc/0xf0 [vmw_vmci] [17007961.190126] [] vmci_dispatch_dgs+0xcf/0x230 [vmw_vmci] [17007961.190138] [] tasklet_action+0x11e/0x130 [17007961.190145] [] __do_softirq+0xfc/0x310 [17007961.190153] [] irq_exit+0x105/0x110 [17007961.190161] [] do_IRQ+0x56/0xc0 [17007961.190170] [] common_interrupt+0x6d/0x6d [17007961.190173] [] ? native_safe_halt+0x6/0x10 [17007961.190190] [] default_idle+0x1f/0x100 [17007961.190197] [] arch_cpu_idle+0x26/0x30 [17007961.190205] [] cpu_startup_entry+0xc1/0x2b0 [17007961.190214] [] start_secondary+0x21d/0x2d0 [17007961.190221] bad: scheduling from the idle thread! [Other infos] I have identified a patch series[2] which seems to fix the exact same situation. A full discussion can be found on patchworks[3], suggesting a certain patch series[2] authored by Vmware. [1] - VM details : Release: Trusty Kernel: Ubuntu-3.13.0-135 [2] Upstream patch series 8ab18d7 VSOCK: Detach QP check should filter out non matching QPs. 8566b86 VSOCK: Fix lockdep issue. 4ef7ea9 VSOCK: sock_put wasn't safe to call in interrupt context [3] - https://patchwork.kernel.org/patch/9948741/ To manage notifications about this bug go to:
[Kernel-packages] [Bug 1780470] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1780470 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780470 Title: BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Bug description: [Impact] It has been brought to my attention that VMware Guest[1] randomly crashes after moving the VMs from a VMware "5.5" env to VMware 6.5 env. The crashes started after the above move (5.5->6.5). Notes: * The crashes wasn't present in VMware 5.5 (with the same VMs). Only started to happens with Vmware 6.5 * The Trusty HWE kernel (Ubuntu-4.4.0-X) doesn't exhibit the situation on VMware 6.5. Here's the stack trace took from the .vmss converted to be readable by Linux debugger: [17007961.187411] BUG: scheduling while atomic: swapper/3/0/0x0100 [17007961.189794] Modules linked in: arc4 md4 nls_utf8 cifs nfsv3 nfs_acl nfsv4 nfs lockd sunrpc fscache veth ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack bridge stp llc aufs vmw_vsock_vmci_transport vsock ppdev vmwgfx serio_raw coretemp ttm drm vmw_balloon vmw_vmci shpchp i2c_piix4 parport_pc mac_hid xfs lp libcrc32c parport psmouse floppy vmw_pvscsi vmxnet3 pata_acpi [17007961.189856] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.13.0-135-generic #184-Ubuntu [17007961.189862] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 10/22/2013 [17007961.189867] 88042f263b90 8172d959 88042f263d30 [17007961.189874] 88042f273180 88042f263ba0 81726d8c 88042f263c00 [17007961.189879] 81731c8f 880428c29800 00013180 880428c25fd8 [17007961.189885] Call Trace: [17007961.189889] [] dump_stack+0x64/0x82 [17007961.189913] [] __schedule_bug+0x4c/0x5a [17007961.189922] [] __schedule+0x6af/0x7f0 [17007961.189929] [] schedule+0x29/0x70 [17007961.189935] [] schedule_timeout+0x279/0x310 [17007961.189947] [] ? select_task_rq_fair+0x56b/0x6f0 [17007961.189955] [] ? enqueue_task_fair+0x422/0x6d0 [17007961.189962] [] ? sched_clock_cpu+0xb5/0x100 [17007961.189971] [] wait_for_completion+0xa6/0x150 [17007961.189977] [] ? wake_up_state+0x20/0x20 [17007961.189987] [] ? __call_rcu+0x2d0/0x2d0 [17007961.189993] [] wait_rcu_gp+0x4b/0x60 [17007961.18] [] ? ftrace_raw_output_rcu_utilization+0x50/0x50 [17007961.190006] [] synchronize_sched+0x3a/0x50 [17007961.190047] [] vmci_event_unsubscribe+0x76/0xb0 [vmw_vmci] [17007961.190063] [] vmci_transport_destruct+0x21/0xe0 [vmw_vsock_vmci_transport] [17007961.190078] [] vsock_sk_destruct+0x17/0x60 [vsock] [17007961.190087] [] __sk_free+0x1f/0x180 [17007961.190092] [] sk_free+0x19/0x20 [17007961.190102] [] vmci_transport_recv_stream_cb+0x200/0x2f0 [vmw_vsock_vmci_transport] [17007961.190114] [] vmci_datagram_invoke_guest_handler+0xbc/0xf0 [vmw_vmci] [17007961.190126] [] vmci_dispatch_dgs+0xcf/0x230 [vmw_vmci] [17007961.190138] [] tasklet_action+0x11e/0x130 [17007961.190145] [] __do_softirq+0xfc/0x310 [17007961.190153] [] irq_exit+0x105/0x110 [17007961.190161] [] do_IRQ+0x56/0xc0 [17007961.190170] [] common_interrupt+0x6d/0x6d [17007961.190173] [] ? native_safe_halt+0x6/0x10 [17007961.190190] [] default_idle+0x1f/0x100 [17007961.190197] [] arch_cpu_idle+0x26/0x30 [17007961.190205] [] cpu_startup_entry+0xc1/0x2b0 [17007961.190214] [] start_secondary+0x21d/0x2d0 [17007961.190221] bad: scheduling from the idle thread! [Other infos] I have identified a patch series[2] which seems to fix the exact same situation. A full discussion can be found on patchworks[3], suggesting a certain patch series[2] authored by Vmware. [1] - VM details : Release: Trusty Kernel: Ubuntu-3.13.0-135 [2] Upstream patch series 8ab18d7 VSOCK: Detach QP check should filter out non matching QPs. 8566b86 VSOCK: Fix lockdep issue. 4ef7ea9 VSOCK: sock_put wasn't safe to call in interrupt context [3] - https://patchwork.kernel.org/patch/9948741/ To manage notifications about this
Re: [Kernel-packages] [Bug 1776155] Re: Touchpad detected as SYNA3602, does not work at all.
Kai-Heng: No, the touch pad still doesn't work even after I suspend/resume. I've attached the dmesg output. also this part of that output seems relevant: dmesg | grep -i i2c-syna [5.756115] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, using dummy regulator [5.760556] i2c_hid i2c-SYNA3602:00: unexpected HID descriptor bcdVersion (0x00ff) Thanks for asking. Jeff On Fri, Jul 6, 2018 at 1:19 PM, Kai-Heng Feng wrote: > Does the touchpad start to work after suspend/resume? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1776155 > > Title: > Touchpad detected as SYNA3602, does not work at all. > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > On my cheaper-end slimline laptop/netbook the touchpad is (I think > wrongly) detected by Linux to be the SYNA 3602. Anyway it does not > work at all, neither touchpad nor buttons. Freshly installed Ubuntu > 18.04 system. External mouse works fine. > > It seems that there is a bug reported on a similar issue, although I > can not confirm that my touchpad hardware is exactly the same: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625 > > If so, there may be a whole new generation of slimline Windows 10 > netbooks that have this problem. > > martin@alanah:~$ cat /proc/bus/input/devices > > I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 > N: Name="AT Translated Set 2 keyboard" > P: Phys=isa0060/serio0/input0 > S: Sysfs=/devices/platform/i8042/serio0/input/input2 > U: Uniq= > H: Handlers=sysrq kbd event2 leds > B: PROP=0 > B: EV=120013 > B: KEY=40200 3803078f800d001 fedfffef fffe > B: MSC=10 > B: LED=7 > > I: Bus=0018 Vendor=0911 Product=5288 Version=0100 > N: Name="SYNA3602:00 0911:5288 Touchpad" > P: Phys=i2c-SYNA3602:00 > S: Sysfs=/devices/pci:00/:00:16.1/i2c_designware.1/ > i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15 > U: Uniq= > H: Handlers=mouse0 event14 > B: PROP=5 > B: EV=1b > B: KEY=e420 3 0 0 0 0 > B: ABS=2608003 > B: MSC=20 > > I: Bus=0003 Vendor=045e Product=00b9 Version=0111 > N: Name="Microsoft Microsoft USB Wireless Mouse" > P: Phys=usb-:00:15.0-1/input0 > S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-1/1-1:1.0/ > 0003:045E:00B9.0002/input/input16 > U: Uniq= > H: Handlers=mouse1 event15 > B: PROP=0 > B: EV=17 > B: KEY=1f 0 0 0 0 > B: REL=1c3 > B: MSC=10 > > 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: MATE > Date: Mon Jun 11 07:57:56 2018 > InstallationDate: Installed on 2018-04-25 (46 days ago) > InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 > (20180404) > SourcePackage: linux-signed > UpgradeStatus: No upgrade log present (probably fresh install) > --- > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: martin 1536 F pulseaudio > CurrentDesktop: MATE > DistroRelease: Ubuntu 18.04 > InstallationDate: Installed on 2018-04-25 (48 days ago) > InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 > (20180404) > MachineType: Multicom Multicom U230 > Package: linux (not installed) > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic > root=UUID=c7a82fee-6e9d-491d-a38d-f5d6bdb4a930 ro > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > RelatedPackageVersions: >linux-restricted-modules-4.15.0-20-generic N/A >linux-backports-modules-4.15.0-20-generic N/A >linux-firmware 1.173 > Tags: bionic > Uname: Linux 4.15.0-20-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 09/15/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: ORO10x.WP313P.NHNAUHL01 > dmi.board.asset.tag: Default string > dmi.board.name: Default string > dmi.board.vendor: Default string > dmi.board.version: Default string > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 10 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrORO10x.WP313P.NHNAUHL01: > bd09/15/2017:svnMulticom:pnMulticomU230:pvrDefaultstring:rvnDefaultstring: > rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: > dmi.product.family: U-series > dmi.product.name: Multicom U230 > dmi.product.version: Default string > dmi.sys.vendor: Multicom > > To manage
[Kernel-packages] [Bug 1780470] [NEW] BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late)
Public bug reported: [Impact] It has been brought to my attention that VMware Guest[1] randomly crashes after moving the VMs from a VMware "5.5" env to VMware 6.5 env. The crashes started after the above move (5.5->6.5). Notes: * The crashes wasn't present in VMware 5.5 (with the same VMs). Only started to happens with Vmware 6.5 * The Trusty HWE kernel (Ubuntu-4.4.0-X) doesn't exhibit the situation on VMware 6.5. Here's the stack trace took from the .vmss converted to be readable by Linux debugger: [17007961.187411] BUG: scheduling while atomic: swapper/3/0/0x0100 [17007961.189794] Modules linked in: arc4 md4 nls_utf8 cifs nfsv3 nfs_acl nfsv4 nfs lockd sunrpc fscache veth ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack bridge stp llc aufs vmw_vsock_vmci_transport vsock ppdev vmwgfx serio_raw coretemp ttm drm vmw_balloon vmw_vmci shpchp i2c_piix4 parport_pc mac_hid xfs lp libcrc32c parport psmouse floppy vmw_pvscsi vmxnet3 pata_acpi [17007961.189856] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.13.0-135-generic #184-Ubuntu [17007961.189862] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 10/22/2013 [17007961.189867] 88042f263b90 8172d959 88042f263d30 [17007961.189874] 88042f273180 88042f263ba0 81726d8c 88042f263c00 [17007961.189879] 81731c8f 880428c29800 00013180 880428c25fd8 [17007961.189885] Call Trace: [17007961.189889] [] dump_stack+0x64/0x82 [17007961.189913] [] __schedule_bug+0x4c/0x5a [17007961.189922] [] __schedule+0x6af/0x7f0 [17007961.189929] [] schedule+0x29/0x70 [17007961.189935] [] schedule_timeout+0x279/0x310 [17007961.189947] [] ? select_task_rq_fair+0x56b/0x6f0 [17007961.189955] [] ? enqueue_task_fair+0x422/0x6d0 [17007961.189962] [] ? sched_clock_cpu+0xb5/0x100 [17007961.189971] [] wait_for_completion+0xa6/0x150 [17007961.189977] [] ? wake_up_state+0x20/0x20 [17007961.189987] [] ? __call_rcu+0x2d0/0x2d0 [17007961.189993] [] wait_rcu_gp+0x4b/0x60 [17007961.18] [] ? ftrace_raw_output_rcu_utilization+0x50/0x50 [17007961.190006] [] synchronize_sched+0x3a/0x50 [17007961.190047] [] vmci_event_unsubscribe+0x76/0xb0 [vmw_vmci] [17007961.190063] [] vmci_transport_destruct+0x21/0xe0 [vmw_vsock_vmci_transport] [17007961.190078] [] vsock_sk_destruct+0x17/0x60 [vsock] [17007961.190087] [] __sk_free+0x1f/0x180 [17007961.190092] [] sk_free+0x19/0x20 [17007961.190102] [] vmci_transport_recv_stream_cb+0x200/0x2f0 [vmw_vsock_vmci_transport] [17007961.190114] [] vmci_datagram_invoke_guest_handler+0xbc/0xf0 [vmw_vmci] [17007961.190126] [] vmci_dispatch_dgs+0xcf/0x230 [vmw_vmci] [17007961.190138] [] tasklet_action+0x11e/0x130 [17007961.190145] [] __do_softirq+0xfc/0x310 [17007961.190153] [] irq_exit+0x105/0x110 [17007961.190161] [] do_IRQ+0x56/0xc0 [17007961.190170] [] common_interrupt+0x6d/0x6d [17007961.190173] [] ? native_safe_halt+0x6/0x10 [17007961.190190] [] default_idle+0x1f/0x100 [17007961.190197] [] arch_cpu_idle+0x26/0x30 [17007961.190205] [] cpu_startup_entry+0xc1/0x2b0 [17007961.190214] [] start_secondary+0x21d/0x2d0 [17007961.190221] bad: scheduling from the idle thread! [Other infos] I have identified a patch series[2] which seems to fix the exact same situation. A full discussion can be found on patchworks[3], suggesting a certain patch series[2] authored by Vmware. [1] - VM details : Release: Trusty Kernel: Ubuntu-3.13.0-135 [2] Upstream patch series 8ab18d7 VSOCK: Detach QP check should filter out non matching QPs. 8566b86 VSOCK: Fix lockdep issue. 4ef7ea9 VSOCK: sock_put wasn't safe to call in interrupt context [3] - https://patchwork.kernel.org/patch/9948741/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Trusty) Importance: Medium Assignee: Eric Desrochers (slashd) Status: In Progress ** Tags: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780470 Title: BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Bug description: [Impact] It has been brought to my attention that VMware Guest[1] randomly crashes after moving the VMs from a VMware "5.5" env to VMware 6.5 env. The crashes started after the above move (5.5->6.5). Notes: * The crashes wasn't present in VMware 5.5 (with the same VMs). Only started to happens with Vmware 6.5 * The Trusty HWE kernel (Ubuntu-4.4.0-X) doesn't exhibit the situation on VMware 6.5. Here's the stack trace took from the .vmss converted to be readable by Linux debugger: [17007961.187411] BUG:
[Kernel-packages] [Bug 1776155] Re: Touchpad detected as SYNA3602, does not work at all.
No. It is, and has always been completely dead. Except on Windows 10, where it worked fine. I did not think to check on what make it was reported as under Win 10 device manager, unfortunately, before I installed Ubuntu 8.04 beta 2. There has been no previous installation of Ubuntu on this laptop, because Ubuntu versions older than 18.04 fail to boot due to UEFI SecureBoot. Suspend/resume does not work either, by the way. But this is nornal for Ubuntu on netbooks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776155 Title: Touchpad detected as SYNA3602, does not work at all. Status in linux package in Ubuntu: Confirmed Bug description: On my cheaper-end slimline laptop/netbook the touchpad is (I think wrongly) detected by Linux to be the SYNA 3602. Anyway it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. External mouse works fine. It seems that there is a bug reported on a similar issue, although I can not confirm that my touchpad hardware is exactly the same: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625 If so, there may be a whole new generation of slimline Windows 10 netbooks that have this problem. martin@alanah:~$ cat /proc/bus/input/devices I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0018 Vendor=0911 Product=5288 Version=0100 N: Name="SYNA3602:00 0911:5288 Touchpad" P: Phys=i2c-SYNA3602:00 S: Sysfs=/devices/pci:00/:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15 U: Uniq= H: Handlers=mouse0 event14 B: PROP=5 B: EV=1b B: KEY=e420 3 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=045e Product=00b9 Version=0111 N: Name="Microsoft Microsoft USB Wireless Mouse" P: Phys=usb-:00:15.0-1/input0 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-1/1-1:1.0/0003:045E:00B9.0002/input/input16 U: Uniq= H: Handlers=mouse1 event15 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1c3 B: MSC=10 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: MATE Date: Mon Jun 11 07:57:56 2018 InstallationDate: Installed on 2018-04-25 (46 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1536 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-25 (48 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: Multicom Multicom U230 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c7a82fee-6e9d-491d-a38d-f5d6bdb4a930 ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ORO10x.WP313P.NHNAUHL01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrORO10x.WP313P.NHNAUHL01:bd09/15/2017:svnMulticom:pnMulticomU230:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: U-series dmi.product.name: Multicom U230 dmi.product.version: Default string dmi.sys.vendor: Multicom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1780466] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160493/+files/UdevDb.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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160492/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] AplayDevices.txt
apport information ** Attachment added: "AplayDevices.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160478/+files/AplayDevices.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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160482/+files/Card0.Codecs.codec.0.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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160487/+files/PciMultimedia.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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] Card0.Amixer.values.txt
apport information ** Attachment added: "Card0.Amixer.values.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160481/+files/Card0.Amixer.values.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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160485/+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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160488/+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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160480/+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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160489/+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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] Card1.Amixer.values.txt
apport information ** Attachment added: "Card1.Amixer.values.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160483/+files/Card1.Amixer.values.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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160491/+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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] ArecordDevices.txt
apport information ** Attachment added: "ArecordDevices.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160479/+files/ArecordDevices.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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160486/+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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] Card1.Codecs.codec.0.txt
apport information ** Attachment added: "Card1.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160484/+files/Card1.Codecs.codec.0.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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] Re: Kernel panic at boot
apport information ** Tags added: apport-collected ** Description changed: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. - The last working kernel version for me was linux-image-4.13.0-15-generic - and the next version did already create a kernel panic for which I - created originally the upstream report. + The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. + ApportVersion: 2.20.10-0ubuntu5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: sworddragon 1521 F pulseaudio + /dev/snd/controlC0: sworddragon 1521 F pulseaudio + Card0.Amixer.info: + Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' +Mixer name : 'Realtek ALC662 rev1' +Components : 'HDA:10ec0662,18497662,00100101' +Controls : 37 +Simple ctrls : 19 + Card1.Amixer.info: + Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' +Mixer name : 'Nvidia GPU 42 HDMI/DP' +Components : 'HDA:10de0042,14583555,00100100' +Controls : 21 +Simple ctrls : 3 + CurrentDesktop: LXDE + DistroRelease: Ubuntu 18.10 + EcryptfsInUse: Yes + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq + ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-15-generic N/A + linux-backports-modules-4.13.0-15-generic N/A + linux-firmware 1.174 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: cosmic + Uname: Linux 4.13.0-15-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 07/23/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P1.50 + dmi.board.name: 960GM/U3S3 FX + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160477/+files/AlsaDevices.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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521
[Kernel-packages] [Bug 1780466] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1780466/+attachment/5160490/+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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1780466 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Incomplete Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux- image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Yes, the current output of uname -r is 4.15.0-26-generic, and this is the /var/log/dpkg.log output, is it the right one? 2018-07-06 17:44:45 startup archives unpack 2018-07-06 17:44:45 install linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:45 status half-installed linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:48 status unpacked linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:48 status unpacked linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:49 install linux-image-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:49 status half-installed linux-image-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:49 status unpacked linux-image-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:49 status unpacked linux-image-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:49 install linux-modules-extra-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:49 status half-installed linux-modules-extra-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:59 status unpacked linux-modules-extra-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:59 status unpacked linux-modules-extra-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:00 upgrade linux-generic:amd64 4.15.0.24.26 4.15.0.26.28 2018-07-06 17:45:00 status half-configured linux-generic:amd64 4.15.0.24.26 2018-07-06 17:45:00 status unpacked linux-generic:amd64 4.15.0.24.26 2018-07-06 17:45:00 status half-installed linux-generic:amd64 4.15.0.24.26 2018-07-06 17:45:00 status half-installed linux-generic:amd64 4.15.0.24.26 2018-07-06 17:45:00 status unpacked linux-generic:amd64 4.15.0.26.28 2018-07-06 17:45:00 status unpacked linux-generic:amd64 4.15.0.26.28 2018-07-06 17:45:00 upgrade linux-image-generic:amd64 4.15.0.24.26 4.15.0.26.28 2018-07-06 17:45:00 status half-configured linux-image-generic:amd64 4.15.0.24.26 2018-07-06 17:45:00 status unpacked linux-image-generic:amd64 4.15.0.24.26 2018-07-06 17:45:00 status half-installed linux-image-generic:amd64 4.15.0.24.26 2018-07-06 17:45:00 status half-installed linux-image-generic:amd64 4.15.0.24.26 2018-07-06 17:45:00 status unpacked linux-image-generic:amd64 4.15.0.26.28 2018-07-06 17:45:00 status unpacked linux-image-generic:amd64 4.15.0.26.28 2018-07-06 17:45:00 install linux-headers-4.15.0-26:all 4.15.0-26.28 2018-07-06 17:45:00 status half-installed linux-headers-4.15.0-26:all 4.15.0-26.28 2018-07-06 17:45:25 status unpacked linux-headers-4.15.0-26:all 4.15.0-26.28 2018-07-06 17:45:25 status unpacked linux-headers-4.15.0-26:all 4.15.0-26.28 2018-07-06 17:45:25 install linux-headers-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:25 status half-installed linux-headers-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:38 status unpacked linux-headers-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:38 status unpacked linux-headers-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:38 upgrade linux-headers-generic:amd64 4.15.0.24.26 4.15.0.26.28 2018-07-06 17:45:38 status half-configured linux-headers-generic:amd64 4.15.0.24.26 2018-07-06 17:45:38 status unpacked linux-headers-generic:amd64 4.15.0.24.26 2018-07-06 17:45:38 status half-installed linux-headers-generic:amd64 4.15.0.24.26 2018-07-06 17:45:38 status half-installed linux-headers-generic:amd64 4.15.0.24.26 2018-07-06 17:45:38 status unpacked linux-headers-generic:amd64 4.15.0.26.28 2018-07-06 17:45:38 status unpacked linux-headers-generic:amd64 4.15.0.26.28 2018-07-06 17:45:39 startup packages configure 2018-07-06 17:45:39 configure linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:39 status unpacked linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:39 status half-configured linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:39 status installed linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:39 configure linux-image-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:39 status unpacked linux-image-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:39 status half-configured linux-image-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:40 status installed linux-image-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:40 status triggers-pending linux-image-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:40 configure linux-modules-extra-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:40 status unpacked linux-modules-extra-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:40 status half-configured linux-modules-extra-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:40 status installed linux-modules-extra-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:45:40 configure linux-headers-4.15.0-26:all 4.15.0-26.28 2018-07-06 17:45:40 status unpacked linux-headers-4.15.0-26:all 4.15.0-26.28 2018-07-06 17:45:40 status half-configured linux-headers-4.15.0-26:all 4.15.0-26.28 2018-07-06 17:45:40
[Kernel-packages] [Bug 1780466] Re: Kernel panic at boot
** Description changed: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 - But after testing out linux-image-4.17.0-4-generic the details changed a - bit. Mainly I'm getting the error message "VFS: Cannot open root device - "sda1" or unknown-block(0,0): error -6". Informations on the web imply - that it might be possible that the required drivers are not anymore in - recent kernel versions so I decided to post that issue now here too. + But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev + the details changed a bit. Mainly I'm getting the error message "VFS: + Cannot open root device "sda1" or unknown-block(0,0): error -6". + Informations on the web imply that it might be possible that the + required drivers are not anymore in recent kernel versions so I decided + to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Incomplete Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux- image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776155] Re: Touchpad detected as SYNA3602, does not work at all.
Does the touchpad start to work after suspend/resume? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776155 Title: Touchpad detected as SYNA3602, does not work at all. Status in linux package in Ubuntu: Confirmed Bug description: On my cheaper-end slimline laptop/netbook the touchpad is (I think wrongly) detected by Linux to be the SYNA 3602. Anyway it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. External mouse works fine. It seems that there is a bug reported on a similar issue, although I can not confirm that my touchpad hardware is exactly the same: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625 If so, there may be a whole new generation of slimline Windows 10 netbooks that have this problem. martin@alanah:~$ cat /proc/bus/input/devices I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0018 Vendor=0911 Product=5288 Version=0100 N: Name="SYNA3602:00 0911:5288 Touchpad" P: Phys=i2c-SYNA3602:00 S: Sysfs=/devices/pci:00/:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15 U: Uniq= H: Handlers=mouse0 event14 B: PROP=5 B: EV=1b B: KEY=e420 3 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=045e Product=00b9 Version=0111 N: Name="Microsoft Microsoft USB Wireless Mouse" P: Phys=usb-:00:15.0-1/input0 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-1/1-1:1.0/0003:045E:00B9.0002/input/input16 U: Uniq= H: Handlers=mouse1 event15 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1c3 B: MSC=10 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: MATE Date: Mon Jun 11 07:57:56 2018 InstallationDate: Installed on 2018-04-25 (46 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1536 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-25 (48 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: Multicom Multicom U230 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c7a82fee-6e9d-491d-a38d-f5d6bdb4a930 ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ORO10x.WP313P.NHNAUHL01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrORO10x.WP313P.NHNAUHL01:bd09/15/2017:svnMulticom:pnMulticomU230:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: U-series dmi.product.name: Multicom U230 dmi.product.version: Default string dmi.sys.vendor: Multicom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10
Though the symptoms are the same, a lot of time the root cause differs. So please file a new bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658345 Title: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10 Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not recognize the touchpad (it does recognize the touch screen nicely though). When I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, which recognizes the touchpad from Elantech. I searched online for days and I found Elantech drivers for Ubuntu 14.04, however, I was unable to load older versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad in future updates? I attached a screen shot of my xinput -list output. Please let me know if you require any additional information. Thank you. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: keary 2345 F pulseaudio DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656 InstallationDate: Installed on 2017-01-18 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U3 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 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.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2MCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Sofia-F dmi.board.vendor: LENOVO dmi.board.version: SDK0J91204WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad FLEX 4-1130 dmi.modalias: dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130: dmi.product.name: 80U3 dmi.product.version: Lenovo ideapad FLEX 4-1130 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-18 (181 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.13.0-041300rc1-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-05-07 (73 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-18 (208 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.13.0-rc5-elan0602 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-05-07 (100 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
@alwaystired - Did you verify that you have installed the new .26 version? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] [NEW] Kernel panic at boot
Public bug reported: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: New Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux- image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780117] Re: linux-azure: 4.15.0-1016.16 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 06. July 2018 17:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 06. July 2018 17:01 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1780117 Title: linux-azure: 4.15.0-1016.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
To restore the splash I reinstalled the ubuntu plymouth. apt-get install plymouth=0.9.3-1ubuntu7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Incomplete Status in plymouth package in Debian: Fix Released Bug description: After update of gdm and kernel gdm3 no longer enables graphics. What happens: = With and without: WaylandEnable=false in /etc/gdm3/custom.conf gdm3 does not switch to graphics. In both cases I case the X process running (Xwayland or Xorg) but no vt has it. lightdm does work, but barely. It takes up to a minute to get to the login screen. What I expected to happen: == gdm3 switching to graphics in ~20 after boot like pre-update. Release: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland kernel-common: Installed: (none) Candidate: 13.018+nmu1 Version table: 13.018+nmu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages gdm3: Installed: 3.28.2-0ubuntu1.3 Candidate: 3.28.2-0ubuntu1.3 Version table: *** 3.28.2-0ubuntu1.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-0ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xwayland: Installed: 2:1.19.6-1ubuntu4 Candidate: 2:1.19.6-1ubuntu4 Version table: *** 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Attaching journalctl -b. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (673 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: gdm3 3.28.2-0ubuntu1.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (674 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1768431
Title:
Request to revert SAUCE patches in the 18.04 SRU and update with
upstream version
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
This SRU was requested by IBM. It contains one SAUCE patch and three
commits from linux.next.
IBM requested that we revert a set of SAUCE patches from 18.04 and
replace them with patches from linux-next. Based on review comments,
there has been minor changes from the original SAUCE patches and the
versions in linux-next.
The first SAUCE patch contains all the changes between the current version
of SAUCE patches for latest cxlflash patches in bionic and the latest
version accepted by the community. This only has the needed changes and
makes it so we don't have to revert and re-apply a high number of patches.
In addition to the SAUCE patch, IBM requested the 3 additional new patches
from the linux-next tree.
== Fixes ==
UBUNTU: SAUCE: (no-up) cxlflash: OCXL diff between v2 and v3
a3feb6ef50de ("scsi: cxlflash: Synchronize reset and remove ops")
9a597cd4c0ce ("scsi: cxlflash: Remove commmands from pending list on timeout)"
d2d354a606d5 ("scsi: cxlflash: Handle spurious interrupts")
== Regression Potential ==
Medium. All the patches are specific to the cxlflash driver, but there
are four of them and one is a SAUCE patch.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 ==
---Problem Description---
Request to revert SAUCE patches from 18.04 and apply the patches from
next/master.
Below set of cxlflash patches were submitted to Canonical after they
were sent to the community. Based on review comments, there has been
minor changes from that version. This BZ is to request reverting those
SAUCE patches with the ones that are queued in next/master tree for
4.18.
- SAUCE: cxlflash: Preserve number of interrupts for master contexts
- SAUCE: cxlflash: Avoid clobbering context control register value
- SAUCE: cxlflash: Add argument identifier names
- SAUCE: cxlflash: Introduce OCXL backend
- SAUCE: cxlflash: Hardware AFU for OCXL
- SAUCE: cxlflash: Read host function configuration
- SAUCE: cxlflash: Setup function acTag range
- SAUCE: cxlflash: Read host AFU configuration
- SAUCE: cxlflash: Setup AFU acTag range
- SAUCE: cxlflash: Setup AFU PASID
- SAUCE: cxlflash: Adapter context support for OCXL
- SAUCE: cxlflash: Use IDR to manage adapter contexts
- SAUCE: cxlflash: Support adapter file descriptors for OCXL
- SAUCE: cxlflash: Support adapter context discovery
- SAUCE: cxlflash: Support image reload policy modification
- SAUCE: cxlflash: MMIO map the AFU
- SAUCE: cxlflash: Support starting an adapter context
- SAUCE: cxlflash: Support process specific mappings
- SAUCE: cxlflash: Support AFU state toggling
- SAUCE: cxlflash: Support reading adapter VPD data
- SAUCE: cxlflash: Setup function OCXL link
- SAUCE: cxlflash: Setup OCXL transaction layer
- SAUCE: cxlflash: Support process element lifecycle
- SAUCE: cxlflash: Support AFU interrupt management
- SAUCE: cxlflash: Support AFU interrupt mapping and registration
- SAUCE: cxlflash: Support starting user contexts
- SAUCE: cxlflash: Support adapter context polling
- SAUCE: cxlflash: Support adapter context reading
- SAUCE: cxlflash: Support adapter context mmap and release
- SAUCE: cxlflash: Support file descriptor mapping
- SAUCE: cxlflash: Introduce object handle fop
- SAUCE: cxlflash: Setup LISNs for user contexts
- SAUCE: cxlflash: Setup LISNs for master contexts
- SAUCE: cxlflash: Update synchronous interrupt status bits
- SAUCE: cxlflash: Introduce OCXL context state machine
- SAUCE: cxlflash: Register for translation errors
- SAUCE: cxlflash: Support AFU reset
- SAUCE: cxlflash: Enable OCXL operations
Also, there are 3 additional patches added to end of this series that we
would like to request being pulled into the SRU stream. These 3 patches address
bug fixes.
The commit ids for the patches queued in next/master tree are,
768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of
interrupts for master contexts
6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering
context control register value
fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument
identifier names
[Kernel-packages] [Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
After installing plymouth_0.9.3-3_amd64.deb gdm3 STILL DOES NOT START. Without haveged installed lightdm still takes AGES to start. plymouth 0.9.3-3 is NOT a resolution to this. And PLEASE change the title back. The original complaint was: gdm3 does not start, not that the boot process never completed. As I said: "In both cases I can see the X process running (Xwayland or Xorg) but no vt has it." Follow your own advise on comment #19 and do not group the gdm3 issue together with the delay on lightdm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Incomplete Status in plymouth package in Debian: Fix Released Bug description: After update of gdm and kernel gdm3 no longer enables graphics. What happens: = With and without: WaylandEnable=false in /etc/gdm3/custom.conf gdm3 does not switch to graphics. In both cases I case the X process running (Xwayland or Xorg) but no vt has it. lightdm does work, but barely. It takes up to a minute to get to the login screen. What I expected to happen: == gdm3 switching to graphics in ~20 after boot like pre-update. Release: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland kernel-common: Installed: (none) Candidate: 13.018+nmu1 Version table: 13.018+nmu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages gdm3: Installed: 3.28.2-0ubuntu1.3 Candidate: 3.28.2-0ubuntu1.3 Version table: *** 3.28.2-0ubuntu1.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-0ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xwayland: Installed: 2:1.19.6-1ubuntu4 Candidate: 2:1.19.6-1ubuntu4 Version table: *** 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Attaching journalctl -b. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (673 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: gdm3 3.28.2-0ubuntu1.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (674 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
@Mark, I just used the browser and let the software installer mime-type binding take care of it. Be warned: after installing this my splash screen was gone (it was using xubuntu theme), so you may need to reconfigure that afterwards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Incomplete Status in plymouth package in Debian: Fix Released Bug description: After update of gdm and kernel gdm3 no longer enables graphics. What happens: = With and without: WaylandEnable=false in /etc/gdm3/custom.conf gdm3 does not switch to graphics. In both cases I case the X process running (Xwayland or Xorg) but no vt has it. lightdm does work, but barely. It takes up to a minute to get to the login screen. What I expected to happen: == gdm3 switching to graphics in ~20 after boot like pre-update. Release: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland kernel-common: Installed: (none) Candidate: 13.018+nmu1 Version table: 13.018+nmu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages gdm3: Installed: 3.28.2-0ubuntu1.3 Candidate: 3.28.2-0ubuntu1.3 Version table: *** 3.28.2-0ubuntu1.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-0ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xwayland: Installed: 2:1.19.6-1ubuntu4 Candidate: 2:1.19.6-1ubuntu4 Version table: *** 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Attaching journalctl -b. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (673 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: gdm3 3.28.2-0ubuntu1.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (674 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780124] Re: linux-gcp: 4.15.0-1012.12~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Uploaded + kernel-stable-phase-changed:Friday, 06. July 2018 16:32 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 - phase: Uploaded - kernel-stable-phase-changed:Friday, 06. July 2018 16:32 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1780124 Title: linux-gcp: 4.15.0-1012.12~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780115] Re: linux-aws: 4.15.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Uploaded + kernel-stable-phase-changed:Friday, 06. July 2018 16:30 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 - phase: Uploaded - kernel-stable-phase-changed:Friday, 06. July 2018 16:30 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1780115 Title: linux-aws: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
Re. comment #42, how do you install that download package on Ubuntu? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Incomplete Status in plymouth package in Debian: Fix Released Bug description: After update of gdm and kernel gdm3 no longer enables graphics. What happens: = With and without: WaylandEnable=false in /etc/gdm3/custom.conf gdm3 does not switch to graphics. In both cases I case the X process running (Xwayland or Xorg) but no vt has it. lightdm does work, but barely. It takes up to a minute to get to the login screen. What I expected to happen: == gdm3 switching to graphics in ~20 after boot like pre-update. Release: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland kernel-common: Installed: (none) Candidate: 13.018+nmu1 Version table: 13.018+nmu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages gdm3: Installed: 3.28.2-0ubuntu1.3 Candidate: 3.28.2-0ubuntu1.3 Version table: *** 3.28.2-0ubuntu1.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-0ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xwayland: Installed: 2:1.19.6-1ubuntu4 Candidate: 2:1.19.6-1ubuntu4 Version table: *** 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Attaching journalctl -b. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (673 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: gdm3 3.28.2-0ubuntu1.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (674 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
I had already installed everything from the proposed mirror using software updater, but it didn't install the new .26 kernel on the 2 affected machines. So I installed the image, headers, module-extra packages using apt-get install /bioic-proposed. that worked and everything worked fine afterwards afaik. I then removed the developer check from the software updater. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779476] Re: Boot process hangs indefinitely. Never finishes.
Why was the title changed? It DOES NOT MATCH AT ALL the symptoms I reported! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779476 Title: Boot process hangs indefinitely. Never finishes. Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Incomplete Status in plymouth package in Debian: Fix Released Bug description: After update of gdm and kernel gdm3 no longer enables graphics. What happens: = With and without: WaylandEnable=false in /etc/gdm3/custom.conf gdm3 does not switch to graphics. In both cases I case the X process running (Xwayland or Xorg) but no vt has it. lightdm does work, but barely. It takes up to a minute to get to the login screen. What I expected to happen: == gdm3 switching to graphics in ~20 after boot like pre-update. Release: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland kernel-common: Installed: (none) Candidate: 13.018+nmu1 Version table: 13.018+nmu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages gdm3: Installed: 3.28.2-0ubuntu1.3 Candidate: 3.28.2-0ubuntu1.3 Version table: *** 3.28.2-0ubuntu1.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-0ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xwayland: Installed: 2:1.19.6-1ubuntu4 Candidate: 2:1.19.6-1ubuntu4 Version table: *** 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Attaching journalctl -b. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (673 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: gdm3 3.28.2-0ubuntu1.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (674 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
I updated the kernel through the bionic-proposed channel, but it still got stuck at startup: "Started Dispatcher daemon for systemd-networkd.ce..before the ppp link was shut down" had to revert back to lighdm in order to reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779357] Re: linux-oem: 4.15.0-1010.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1779357 Title: linux-oem: 4.15.0-1010.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1780112 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780309] Re: [Hyper-V] Please set CONFIG_BLK_DEV_DRBD to "m"
main, please -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1780309 Title: [Hyper-V] Please set CONFIG_BLK_DEV_DRBD to "m" Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Bionic: In Progress Bug description: DRBD modules are not loadable nor are they in extras. Please set CONFIG_BLK_DEV_DRBD to "m" in the linux-azure kernel config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1780309/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
You don't need to install all of the updates from the -proposed repository, only the kernel. When you check the proposed box in the software updater, you are effectively adding the following line to /etc/apt/sources.list (mirror is whatever mirror you have chosen): deb http://mirrors.namecheap.com/ubuntu/ bionic-proposed universe restricted multiverse main You can then either use the software updater or apt to install the kernel. I used the following apt command on the command line: apt-get install linux-generic This command automatically pulled in the other dependencies such as the kernel headers and modules from the -proposed repository. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780452] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780452 Title: 14e4:43ba Broadcom BCM43602 doesn't see 5GHz APs Status in linux package in Ubuntu: Confirmed Bug description: On a MackBookPro14,2 (2018 model), the wireless works with the brcmfmac on a Bionic install out of the box, but cannot see any APs on the 5GHz range, even though there are APs broadasting on 5GHz. $ sudo lspci -vnn -d 14e4: 02:00.0 Network controller [0280]: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 02) Subsystem: Apple Inc. BCM43602 802.11ac Wireless LAN SoC [106b:0157] Flags: bus master, fast devsel, latency 0, IRQ 75 Memory at 8240 (64-bit, non-prefetchable) [size=32K] Memory at 8200 (64-bit, non-prefetchable) [size=4M] Capabilities: [48] Power Management version 3 Capabilities: [58] MSI: Enable+ Count=1/16 Maskable- 64bit+ Capabilities: [68] Vendor Specific Information: Len=44 Capabilities: [ac] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Device Serial Number 9b-95-98-ff-ff-03-f0-18 Capabilities: [150] Power Budgeting Capabilities: [160] Virtual Channel Capabilities: [1b0] Latency Tolerance Reporting Capabilities: [220] #15 Capabilities: [240] L1 PM Substates Kernel driver in use: brcmfmac Kernel modules: brcmfmac, wl $ sudo iwlist wlp2s0 scan | grep Freq Frequency:2.437 GHz (Channel 6) Frequency:2.412 GHz (Channel 1) Frequency:2.412 GHz (Channel 1) Frequency:2.462 GHz (Channel 11) Frequency:2.412 GHz (Channel 1) Frequency:2.462 GHz (Channel 11) Found bug reports https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663711 and https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1487524, but there are no solutions for Bionic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 3080 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jul 6 16:43:32 2018 InstallationDate: Installed on 2018-07-05 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookPro14,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=8c4cc8cd-f9a2-4e84-9e5e-0f7d6bb49a01 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP142.88Z.0175.B00.1804091703 dmi.board.name: Mac-CAD6701F7CEA0921 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,2 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-CAD6701F7CEA0921 dmi.modalias: dmi:bvnAppleInc.:bvrMBP142.88Z.0175.B00.1804091703:bd04/09/2018:svnAppleInc.:pnMacBookPro14,2:pvr1.0:rvnAppleInc.:rnMac-CAD6701F7CEA0921:rvrMacBookPro14,2:cvnAppleInc.:ct9:cvrMac-CAD6701F7CEA0921: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1663711] Re: Broadcom BCM43602 does not see 5 gHz networks on Ubuntu 16.04
*** This bug is a duplicate of bug 1663710 *** https://bugs.launchpad.net/bugs/1663710 Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1663711 Title: Broadcom BCM43602 does not see 5 gHz networks on Ubuntu 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Dear team. I am using 02:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) with Ubuntu 16.04 and linux-firmware version (1.157.8). My system can scan and connect to 2.4 gHz wifi network, but could not see any AP's on 5 gHz. Found that bug report https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1487524 but it is not of much help. Situation exactly as in post 12. I can't find any solution ( ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kaim 3114 F pulseaudio Date: Fri Feb 10 20:52:51 2017 HibernationDevice: RESUME=UUID=79446d80-cb5d-4e10-8634-4d900c67cd42 InstallationDate: Installed on 2016-08-02 (192 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=770dfbb8-f273-4fca-b191-45743877e8d0 ro quiet splash nouveau.modeset=0 vt.handoff=7 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.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.16 dmi.board.name: 0X2P13 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.16:bd10/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0X2P13:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780452] [NEW] 14e4:43ba Broadcom BCM43602 doesn't see 5GHz APs
Public bug reported: On a MackBookPro14,2 (2018 model), the wireless works with the brcmfmac on a Bionic install out of the box, but cannot see any APs on the 5GHz range, even though there are APs broadasting on 5GHz. $ sudo lspci -vnn -d 14e4: 02:00.0 Network controller [0280]: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 02) Subsystem: Apple Inc. BCM43602 802.11ac Wireless LAN SoC [106b:0157] Flags: bus master, fast devsel, latency 0, IRQ 75 Memory at 8240 (64-bit, non-prefetchable) [size=32K] Memory at 8200 (64-bit, non-prefetchable) [size=4M] Capabilities: [48] Power Management version 3 Capabilities: [58] MSI: Enable+ Count=1/16 Maskable- 64bit+ Capabilities: [68] Vendor Specific Information: Len=44 Capabilities: [ac] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Device Serial Number 9b-95-98-ff-ff-03-f0-18 Capabilities: [150] Power Budgeting Capabilities: [160] Virtual Channel Capabilities: [1b0] Latency Tolerance Reporting Capabilities: [220] #15 Capabilities: [240] L1 PM Substates Kernel driver in use: brcmfmac Kernel modules: brcmfmac, wl $ sudo iwlist wlp2s0 scan | grep Freq Frequency:2.437 GHz (Channel 6) Frequency:2.412 GHz (Channel 1) Frequency:2.412 GHz (Channel 1) Frequency:2.462 GHz (Channel 11) Frequency:2.412 GHz (Channel 1) Frequency:2.462 GHz (Channel 11) Found bug reports https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663711 and https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1487524, but there are no solutions for Bionic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 3080 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jul 6 16:43:32 2018 InstallationDate: Installed on 2018-07-05 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookPro14,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=8c4cc8cd-f9a2-4e84-9e5e-0f7d6bb49a01 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP142.88Z.0175.B00.1804091703 dmi.board.name: Mac-CAD6701F7CEA0921 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,2 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-CAD6701F7CEA0921 dmi.modalias: dmi:bvnAppleInc.:bvrMBP142.88Z.0175.B00.1804091703:bd04/09/2018:svnAppleInc.:pnMacBookPro14,2:pvr1.0:rvnAppleInc.:rnMac-CAD6701F7CEA0921:rvrMacBookPro14,2:cvnAppleInc.:ct9:cvrMac-CAD6701F7CEA0921: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1780452 Title: 14e4:43ba Broadcom BCM43602 doesn't see 5GHz APs Status in linux package in Ubuntu: Confirmed Bug description: On a MackBookPro14,2 (2018 model), the wireless works with the brcmfmac on a Bionic install out of the box, but cannot see any APs on the 5GHz range, even though there are APs broadasting on 5GHz. $ sudo lspci -vnn -d 14e4: 02:00.0 Network controller [0280]: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 02) Subsystem: Apple Inc. BCM43602 802.11ac Wireless LAN SoC [106b:0157] Flags: bus master, fast devsel, latency 0, IRQ 75 Memory at 8240 (64-bit, non-prefetchable) [size=32K] Memory at 8200 (64-bit, non-prefetchable) [size=4M] Capabilities: [48] Power Management version 3 Capabilities: [58] MSI: Enable+ Count=1/16 Maskable- 64bit+ Capabilities: [68] Vendor Specific Information: Len=44 Capabilities: [ac] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Device Serial Number
