[Kernel-packages] [Bug 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** 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: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - snap-release-to-candidate: Snap not in candidate channel verification-testing: Testing in progress -- 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/1806673 Title: linux-gcp: 4.15.0-1026.27~16.04.1 -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 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: 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: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806428] Re: linux: 3.13.0-164.214 -proposed tracker
** 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 backports: bug 1806429 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff - verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806428 Title: linux: 3.13.0-164.214 -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: 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: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: 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 backports: bug 1806429 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806665] Re: linux-azure: 4.15.0-1036.38 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress - snap-release-to-candidate: Snap not in 18/candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress -- 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/1806665 Title: linux-azure: 4.15.0-1036.38 -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: 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - snap-release-to-candidate: Snap not in candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress -- 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/1806672 Title: linux-azure: 4.15.0-1036.38~16.04.1 -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 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow 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 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806573] Re: linux-aws: 4.4.0-1074.84 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** 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: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Testing in progress + promote-to-security: Master bug not ready for release + promote-to-updates: Master bug not ready for release -- 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/1806573 Title: linux-aws: 4.4.0-1074.84 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807974] [NEW] Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
Public bug reported:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
work again.
dmesg output is as follows:
$ dmesg | grep ath10k
[ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid
6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id
0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs
0 testmode 0
[ 6646.270369] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp
max-sta 32 raw 0 hwcrypto 1
[ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci :02:00.0: device successfully recovered
[17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid
03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id
0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs
0 testmode 0
[17641.848065] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp
max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30
[17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
[17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
[17642.835601] ath10k_pci :02:00.0: device successfully recovered
[17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
[17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118
I do not recall having any wireless issues before I upgraded (when this
machine was running Bionic).
Bug #1730331 - ath10k_pci: firmware crashed!
Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
could be related, but appear to be related to earlier releases, whereas my
issue has appeared/become much worse on Cosmic.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-11-generic 4.18.0-11.12
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: aaron-work 3476 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 11 14:21:44 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1
InstallationDate: Installed on 2018-09-04 (98 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
[Kernel-packages] [Bug 1806429] Re: linux-lts-trusty: 3.13.0-164.214~precise1 -proposed tracker
No pending verification. ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1806429 Title: linux-lts-trusty: 3.13.0-164.214~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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: 1806428 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 02:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806569] Re: linux: 4.4.0-141.167 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806569 Title: linux: 4.4.0-141.167 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1806570 (linux-aws), bug 1806572 (linux-lts-xenial) derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 (linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress regression-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806429] Re: linux-lts-trusty: 3.13.0-164.214~precise1 -proposed tracker
** 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: 1806428 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 02:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress security-signoff: Waiting for signoff - verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1806429 Title: linux-lts-trusty: 3.13.0-164.214~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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: 1806428 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 02:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806428] Re: linux: 3.13.0-164.214 -proposed tracker
No pending verification. ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806428 Title: linux: 3.13.0-164.214 -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: 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: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: 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 backports: bug 1806429 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
Thanks, that looks good. I've merge proposed those changes to Debian since we are in sync it would be nice to stay this way, https://salsa.debian.org/alsa-team/alsa-lib/merge_requests/1. I'm going to upload to disco meanwhile so we don't block on them to merge it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806430] Re: linux: 3.2.0-139.185 -proposed tracker
No non-security changes, no pending verification. ** Changed in: linux (Ubuntu Precise) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806430 Title: linux: 3.2.0-139.185 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-lbm 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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Invalid 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 backports: derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806570] Re: linux-aws: 4.4.0-1037.40 -proposed tracker
No pending verification for AWS. ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Invalid -- 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/1806570 Title: linux-aws: 4.4.0-1037.40 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: 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: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806569] Re: linux: 4.4.0-141.167 -proposed tracker
** 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 backports: bug 1806570 (linux-aws), bug 1806572 (linux-lts-xenial) derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 (linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress regression-testing: Testing in progress - verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806569 Title: linux: 4.4.0-141.167 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1806570 (linux-aws), bug 1806572 (linux-lts-xenial) derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 (linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress regression-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806666] Re: linux-gcp: 4.15.0-1026.27 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED - snap-release-to-candidate: Snap not in 18/candidate channel verification-testing: Testing in progress -- 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/180 Title: linux-gcp: 4.15.0-1026.27 -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: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: 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 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806664] Re: linux-aws: 4.15.0-1031.33 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED - snap-release-to-candidate: Snap not in 18/candidate channel verification-testing: Testing in progress -- 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/1806664 Title: linux-aws: 4.15.0-1031.33 -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: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784659] Re: P9 PMU Events Update #5
** Changed in: ubuntu-power-systems Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784659 Title: P9 PMU Events Update #5 Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 - Sukadev Bhattiprolu - 2018-03-13 18:08:25 == ---Problem Description--- There has been some updates to the P9 PMU events list (some events dropped, some events changed linux category). We need to make corresponding updates to the PMU event JSON files in the Linux perf. Submitted a pull request https://lkml.org/lkml/2018/3/13/1428 with Subject line [GIT PULL] Please pull JSON files for POWR9 PMU events Userspace tool common name: perf Userspace rpm: linux-tools The userspace tool has the following bit modes: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806659] Re: linux: 4.15.0-43.46 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** 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 backports: bug 1806670 (linux-azure), bug 1806671 (linux-aws-hwe), bug 1806672 (linux-azure), bug 1806673 (linux-gcp), bug 1806674 (linux-hwe), bug 1806675 (linux-hwe-edge) derivatives: bug 1806661 (linux-raspi2), bug 1806663 (linux-oem), bug 1806664 (linux-aws), bug 1806665 (linux-azure), bug 180 (linux-gcp), bug 1806667 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Friday, 07. December 2018 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress - snap-release-to-candidate: Snap not in 18/candidate channel verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806659 Title: linux: 4.15.0-43.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1806670 (linux-azure), bug 1806671 (linux-aws-hwe), bug 1806672 (linux-azure), bug 1806673 (linux-gcp), bug 1806674 (linux-hwe), bug 1806675 (linux-hwe-edge) derivatives: bug 1806661 (linux-raspi2), bug 1806663 (linux-oem), bug 1806664 (linux-aws), bug 1806665 (linux-azure), bug 180 (linux-gcp), bug 1806667 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Friday, 07. December 2018 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784659] Re: P9 PMU Events Update #5
The changes in the link were included in 4.17-rc1 upstream and thus are already included in cosmic. Based on this I'm marking the development task fix released. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784659 Title: P9 PMU Events Update #5 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 - Sukadev Bhattiprolu - 2018-03-13 18:08:25 == ---Problem Description--- There has been some updates to the P9 PMU events list (some events dropped, some events changed linux category). We need to make corresponding updates to the PMU event JSON files in the Linux perf. Submitted a pull request https://lkml.org/lkml/2018/3/13/1428 with Subject line [GIT PULL] Please pull JSON files for POWR9 PMU events Userspace tool common name: perf Userspace rpm: linux-tools The userspace tool has the following bit modes: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807878] Re: Xenserver Ubuntu 16 VMs freezing on migration
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807878 Title: Xenserver Ubuntu 16 VMs freezing on migration Status in linux package in Ubuntu: Confirmed Bug description: Hello! We are experiencing virtual machines freezes during migration with Xenserver 7.1 CU1 and Ubuntu 16.04. We are not sure which kernel versions are affected but the last occurrence was with 4.4.0-139. We could catch some logs on VM failure with netconsole (attached). It has "logstash time: message" format, sorted by logstash time. We do not think that such freezes have ever happened with Ubuntu 14. Could you please help on the issue? affects ubuntu -- BR, Kseniya To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807757] Re: Drivers: hv: vmbus: Offload the handling of channels to two workqueues
A 18.04(Bionic) test kernel is built as well. The list of commits in
this kernel is:
4.18-rc1 - 7bf7bb37f16a ("hv_netvsc: fix network namespace issues with VF
support")
4.18-rc4 - 3ffe64f1a641 ("hv_netvsc: split sub-channel setup into async and
sync")
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
4.19-rc3 - e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock
earlier in netvsc_probe()")
4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized channels")
4.20-rc5 - eceb05965489 ("Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()")
4.20-rc6 - 37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels
to two workqueues")
It is available from:
http://kernel.ubuntu.com/~jsalisbury/lp1807757/bionic
** Description changed:
== SRU Justification ==
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
workqueues")
A second commit is also needed to prevent a deadlock with single NIC VMs.
This commit is in mainline as of 4.19-rc3:
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in
netvsc_probe()")
The Disco development release has been rebased to upstream 4.19, and it
already has commit eceb0596548. Disco only needs 37c2578c0c40.
Cosmic does not require any dependent commits, just the two
above(37c2578c0c40, e04e7a7bbd4b).
- linux-azure and Bionic(4.15+ kernels) require the following three dependent
commits:
+ linux-azure and Bionic(4.15+ kernels) require the following five dependent
commits:
+ 4.18-rc1 - 7bf7bb37f16a ("hv_netvsc: fix network namespace issues with VF
support")
+ 4.18-rc4 - 3ffe64f1a641 ("hv_netvsc: split sub-channel setup into async and
sync")
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
+ 4.19-rc3 - e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock
earlier in netvsc_probe()")
4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized
channels")
- 4.20-rc5 - eceb05965489 ("Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()")
Xenial(4.14 and older kernels) require the following five dependent commits:
4.15-rc1 - c2e5df616e1a ("vmbus: add per-channel sysfs info")
4.15-rc6 - 869b5567e12f ("vmbus: unregister device_obj->channels_kset")
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized
channels")
4.20-rc5 - eceb05965489 ("Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()")
== Fixes ==
("Dependent commits mentioned above, based on Ubuntu release")
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in
netvsc_probe()")
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to
two workqueues")
== Regression Potential ==
Low. Limited to hyperv.
== Test Case ==
--
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/1807757
Title:
Drivers: hv: vmbus: Offload the handling of channels to two workqueues
Status in linux package in Ubuntu:
Fix Committed
Status in linux-azure 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:
In Progress
Status in linux source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
workqueues")
A second commit is also needed to prevent a deadlock with single NIC VMs.
This commit is in mainline as of 4.19-rc3:
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in
netvsc_probe()")
The Disco development release has been rebased to upstream 4.19, and
it already has commit eceb0596548. Disco only needs 37c2578c0c40.
Cosmic does not require any dependent commits, just the two
above(37c2578c0c40, e04e7a7bbd4b).
linux-azure and Bionic(4.15+ kernels) require the following five dependent
commits:
4.18-rc1 - 7bf7bb37f16a ("hv_netvsc: fix network namespace issues with VF
support")
4.18-rc4 - 3ffe64f1a641 ("hv_netvsc: split sub-channel setup into async and
sync")
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
4.19-rc3 - e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock
earlier in netvsc_probe()")
4.19-rc4 -
[Kernel-packages] [Bug 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** 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: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - snap-release-to-beta: Snap not in beta channel - snap-release-to-edge: Snap not in edge channel + snap-release-to-candidate: Snap not in candidate channel verification-testing: Testing in progress -- 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/1806673 Title: linux-gcp: 4.15.0-1026.27~16.04.1 -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 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: 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: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress snap-release-to-candidate: Snap not in candidate channel verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807878] [NEW] Xenserver Ubuntu 16 VMs freezing on migration
You have been subscribed to a public bug: Hello! We are experiencing virtual machines freezes during migration with Xenserver 7.1 CU1 and Ubuntu 16.04. We are not sure which kernel versions are affected but the last occurrence was with 4.4.0-139. We could catch some logs on VM failure with netconsole (attached). It has "logstash time: message" format, sorted by logstash time. We do not think that such freezes have ever happened with Ubuntu 14. Could you please help on the issue? affects ubuntu -- BR, Kseniya ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment -- Xenserver Ubuntu 16 VMs freezing on migration https://bugs.launchpad.net/bugs/1807878 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - snap-release-to-beta: Snap not in beta channel - snap-release-to-edge: Snap not in edge channel + snap-release-to-candidate: Snap not in candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress -- 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/1806672 Title: linux-azure: 4.15.0-1036.38~16.04.1 -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 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow 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 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress snap-release-to-candidate: Snap not in candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806664] Re: linux-aws: 4.15.0-1031.33 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED - snap-release-to-beta: Snap not in 18/beta channel - snap-release-to-edge: Snap not in 18/edge channel + snap-release-to-candidate: Snap not in 18/candidate channel verification-testing: Testing in progress -- 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/1806664 Title: linux-aws: 4.15.0-1031.33 -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: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED snap-release-to-candidate: Snap not in 18/candidate channel verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic
To keep potential regressions even lower I'd for now only consider that for >=Bionic. That also helps as if someone intentionally spawns an old type KVM machine (pre Bionic) on a >=Bionic host we don#t have to care about this too much (machine type, not release runnin IN the guest). That makes us able to ignore ipxe-qemu-256k-compat-efi-roms in regard to this issue. ** Also affects: ipxe-qemu-256k-compat (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ipxe (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ipxe-qemu-256k-compat (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ipxe (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ipxe-qemu-256k-compat (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: Invalid ** Also affects: ipxe (Ubuntu Disco) Importance: Undecided Status: Fix Released ** Also affects: ipxe-qemu-256k-compat (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ipxe (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ipxe-qemu-256k-compat (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ipxe (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ipxe-qemu-256k-compat (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Trusty) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Disco) ** Changed in: ipxe-qemu-256k-compat (Ubuntu Trusty) Status: New => Invalid ** Changed in: ipxe-qemu-256k-compat (Ubuntu Xenial) Status: New => Invalid ** No longer affects: ipxe-qemu-256k-compat (Ubuntu Trusty) ** No longer affects: ipxe-qemu-256k-compat (Ubuntu Xenial) ** No longer affects: ipxe-qemu-256k-compat (Ubuntu Bionic) ** No longer affects: ipxe-qemu-256k-compat (Ubuntu Cosmic) ** No longer affects: ipxe-qemu-256k-compat (Ubuntu Disco) ** Changed in: ipxe-qemu-256k-compat (Ubuntu) Status: New => Won't Fix ** Changed in: ipxe (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: ipxe (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: ipxe-qemu-256k-compat (Ubuntu) Status: Won't Fix => Invalid ** Changed in: ipxe (Ubuntu Bionic) Status: New => Triaged ** Changed in: ipxe (Ubuntu Cosmic) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805920 Title: iPXE ignores vlan 0 traffic Status in MAAS: Invalid Status in ipxe package in Ubuntu: Fix Released Status in ipxe-qemu-256k-compat package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in ipxe source package in Trusty: Won't Fix Status in ipxe source package in Xenial: Won't Fix Status in ipxe source package in Bionic: Triaged Status in ipxe source package in Cosmic: Triaged Status in ipxe source package in Disco: Fix Released Bug description: I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority of packets. This is separate from vlan, it
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
This is the debdiff for disco. I installed a disco daily build through docker, then generated the debdiff under disco, there is no any errors when running "debuild -sa -S". thanks. ** Patch added: "alsa-lib_1.1.7-2ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806532/+attachment/5221308/+files/alsa-lib_1.1.7-2ubuntu0.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806665] Re: linux-azure: 4.15.0-1036.38 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress - snap-release-to-beta: Snap not in 18/beta channel - snap-release-to-edge: Snap not in 18/edge channel + snap-release-to-candidate: Snap not in 18/candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress -- 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/1806665 Title: linux-azure: 4.15.0-1036.38 -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: 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress snap-release-to-candidate: Snap not in 18/candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806666] Re: linux-gcp: 4.15.0-1026.27 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED - snap-release-to-beta: Snap not in 18/beta channel - snap-release-to-edge: Snap not in 18/edge channel + snap-release-to-candidate: Snap not in 18/candidate channel verification-testing: Testing in progress -- 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/180 Title: linux-gcp: 4.15.0-1026.27 -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: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: 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 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED snap-release-to-candidate: Snap not in 18/candidate channel verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806659] Re: linux: 4.15.0-43.46 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** 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 backports: bug 1806670 (linux-azure), bug 1806671 (linux-aws-hwe), bug 1806672 (linux-azure), bug 1806673 (linux-gcp), bug 1806674 (linux-hwe), bug 1806675 (linux-hwe-edge) derivatives: bug 1806661 (linux-raspi2), bug 1806663 (linux-oem), bug 1806664 (linux-aws), bug 1806665 (linux-azure), bug 180 (linux-gcp), bug 1806667 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Friday, 07. December 2018 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress - snap-release-to-beta: Snap not in 18/beta channel - snap-release-to-edge: Snap not in 18/edge channel + snap-release-to-candidate: Snap not in 18/candidate channel verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806659 Title: linux: 4.15.0-43.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1806670 (linux-azure), bug 1806671 (linux-aws-hwe), bug 1806672 (linux-azure), bug 1806673 (linux-gcp), bug 1806674 (linux-hwe), bug 1806675 (linux-hwe-edge) derivatives: bug 1806661 (linux-raspi2), bug 1806663 (linux-oem), bug 1806664 (linux-aws), bug 1806665 (linux-azure), bug 180 (linux-gcp), bug 1806667 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Friday, 07. December 2018 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress snap-release-to-candidate: Snap not in 18/candidate channel verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic
This bug was fixed in the package ipxe - 1.0.0+git-20180124.fbe8c52d- 0ubuntu5 --- ipxe (1.0.0+git-20180124.fbe8c52d-0ubuntu5) disco; urgency=medium * d/p/0005-strip-802.1Q-VLAN-0-priority-tags.patch: Strip 802.1Q VLAN 0 priority tags; Fixes PXE when VLAN tag is 0. (LP: #1805920) -- Andres Rodriguez Mon, 10 Dec 2018 16:26:42 -0500 ** Changed in: ipxe (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805920 Title: iPXE ignores vlan 0 traffic Status in MAAS: Invalid Status in ipxe package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority of packets. This is separate from vlan, it just happens to use that ethertype to do the priority tagging. Someone confirmed to me that, in the iPXE source, it drops all packets if they are vlan tagged. The customer is unable to figure out why the packets between blades is getting vlan tagged so we either need to figure out how to allow iPXE to accept vlan 0 or the customer will need to use different equipment for the MAAS nodes. I found a conversation on the ipxe-devel mailing list that suggested a commit was submitted and signed off but that was from 2016 so I'm not sure what became of it. Notable messages in the thread: http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html Would it be possible to install a local patch as part of the FCE deployment? I suspect the patch(es) mentioned in the above thread would require some modification to apply properly. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
Ok, let me know what error you get/if you can help. Note that the first patch is in 1.1.7 so you don't need it, also you might need to use 'update-maintainer' since we are adding a diff ... if you give your error/log I can try to help you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
@seb128, OK, got it. Before I upload the debdiff for cosmic and bionic, I tried to generate debdiff for disco too, but it always failed when I ran "debuild -sa -S" for disco. I am trying to generate the debdiff for disco now. Will upload it soon. thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
The cosmic debdiff looks fine, I can upload that once disco has been updated. Can you work on the debdiff for disco as well? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
Thanks for the work, it looks like 0011-conf-ucm-Dell-WD15-Dock-Fix- incorrect-device-names.patch and 0012-conf-USB-Audio-Add-Dell-WD19-Dock- in-the-IEC958-blac.patch were commited after 1.1.7 and is not in disco though so they need to be added there first before we upload the SRU -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
This is the debdiff for bionic And the debdiff is generated based on bionic-proposed branch of https://git.launchpad.net/ubuntu/+source/alsa-lib thanks. ** Patch added: "alsa-lib_1.1.3-5ubuntu0.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1806532/+attachment/5221225/+files/alsa-lib_1.1.3-5ubuntu0.2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
And the debdiff in the #2 is generated based on cosmic-proposed branch of https://git.launchpad.net/ubuntu/+source/alsa-lib -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807869] 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 1807869 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/1807869 Title: ubuntu_nbd_smoke_test failed with Xenial Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Spotted in this cycle with node: * daedalus (amd64-lowlatency) - https://pastebin.ubuntu.com/p/JxYNh9JPJd/ * daedalus (amd64-generic) - https://pastebin.ubuntu.com/p/4W8gDSDVqm/ * kernel01 (s390x.zVM) - https://pastebin.ubuntu.com/p/kFW7KQbbkf/ Error log from kernel01: creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-22282 Date: Mon Dec 10 05:22:47 EST 2018 Host: kernel01 Kernel:4.4.0-141-generic #167-Ubuntu SMP Wed Dec 5 10:32:22 UTC 2018 Machine: kernel01 s390x s390x CPUs online: 8 CPUs total:8 Page size: 4096 Pages avail: 641567 Pages total: 977383 Free space: Filesystem Size Used Avail Use% Mounted on udev 1.9G 0 1.9G 0% /dev tmpfs382M 39M 344M 11% /run /dev/dasda1 6.7G 6.2G 187M 98% / tmpfs1.9G 4.0K 1.9G 1% /dev/shm tmpfs5.0M 0 5.0M 0% /run/lock tmpfs1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/datavg-home 21G 3.1G 17G 17% /home testpool.3622624G 128K 24G 1% /testpool.36226 testpool.36226/testfs.36226 24G 128K 24G 1% /var/tmp/testdir36226 testpool.36226/testfs.36226/clone 24G 128K 24G 1% /var/tmp/testdir36226/clone testpool.36226/testfs.36226/renameme 24G 128K 24G 1% /var/tmp/testdir36226/renameme testpool.36226/testfs.36226/shared24G 128K 24G 1% /var/tmp/testdir36226/shared testpool.36226/testfs.36226/testfs2.36226 24G 128K 24G 1% /var/tmp/testdir36226/testfs2.36226 testpool.36226/testfs.36226/testfs2.36226.unmounted 24G 128K 24G 1% /var/tmp/testdir36226/testfs2.36226.unmounted testpool.36226/testfs.36226/unshared 24G 128K 24G 1% /var/tmp/testdir36226/unshared tmpfs382M 0 382M 0% /run/user/1000 tmpfs100K 0 100K 0% /var/lib/lxd/shmounts tmpfs100K 0 100K 0% /var/lib/lxd/devlxd NBD device /dev/nbd0 created found nbd export NBD exports found: test starting clien with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 failed unmounting /mnt/nbd-test-22282 stopping client disconnect, sock, done killing server stderr: bs=1024, sz=134217728 bytes timeout=30 umount: /mnt/nbd-test-22282: mountpoint not found ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Dec 11 04:08:37 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
ubuntu-sponsor-team: This bug also needs to backport 3 patches to alsa-lib of cosmic and bionic, here is the debdiff for alsa-lib cosmic. Please review it, if it passes review, please help enqueue it. thanks. ** Description changed: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] - Cherry-picked 3 upstream patches, these patches add the longname of the sound - card for the dock station. + For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. + For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will + add ucm configuration files for Dell WD15&19, and change the SPDIF conf + in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. ** Patch added: "alsa-lib_1.1.6-1ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1806532/+attachment/5221223/+files/alsa-lib_1.1.6-1ubuntu1.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807869] [NEW] ubuntu_nbd_smoke_test failed with Xenial
Public bug reported: Spotted in this cycle with node: * daedalus (amd64-lowlatency) - https://pastebin.ubuntu.com/p/JxYNh9JPJd/ * daedalus (amd64-generic) - https://pastebin.ubuntu.com/p/4W8gDSDVqm/ * kernel01 (s390x.zVM) - https://pastebin.ubuntu.com/p/kFW7KQbbkf/ Error log from kernel01: creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-22282 Date: Mon Dec 10 05:22:47 EST 2018 Host: kernel01 Kernel:4.4.0-141-generic #167-Ubuntu SMP Wed Dec 5 10:32:22 UTC 2018 Machine: kernel01 s390x s390x CPUs online: 8 CPUs total:8 Page size: 4096 Pages avail: 641567 Pages total: 977383 Free space: Filesystem Size Used Avail Use% Mounted on udev 1.9G 0 1.9G 0% /dev tmpfs382M 39M 344M 11% /run /dev/dasda1 6.7G 6.2G 187M 98% / tmpfs1.9G 4.0K 1.9G 1% /dev/shm tmpfs5.0M 0 5.0M 0% /run/lock tmpfs1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/datavg-home 21G 3.1G 17G 17% /home testpool.3622624G 128K 24G 1% /testpool.36226 testpool.36226/testfs.36226 24G 128K 24G 1% /var/tmp/testdir36226 testpool.36226/testfs.36226/clone 24G 128K 24G 1% /var/tmp/testdir36226/clone testpool.36226/testfs.36226/renameme 24G 128K 24G 1% /var/tmp/testdir36226/renameme testpool.36226/testfs.36226/shared24G 128K 24G 1% /var/tmp/testdir36226/shared testpool.36226/testfs.36226/testfs2.36226 24G 128K 24G 1% /var/tmp/testdir36226/testfs2.36226 testpool.36226/testfs.36226/testfs2.36226.unmounted 24G 128K 24G 1% /var/tmp/testdir36226/testfs2.36226.unmounted testpool.36226/testfs.36226/unshared 24G 128K 24G 1% /var/tmp/testdir36226/unshared tmpfs382M 0 382M 0% /run/user/1000 tmpfs100K 0 100K 0% /var/lib/lxd/shmounts tmpfs100K 0 100K 0% /var/lib/lxd/devlxd NBD device /dev/nbd0 created found nbd export NBD exports found: test starting clien with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 failed unmounting /mnt/nbd-test-22282 stopping client disconnect, sock, done killing server stderr: bs=1024, sz=134217728 bytes timeout=30 umount: /mnt/nbd-test-22282: mountpoint not found ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Dec 11 04:08:37 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 crashkernel=196M nobp=1 BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-141-generic N/A linux-backports-modules-4.4.0-141-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug package-from-proposed s390x xenial ** Summary changed: - ubuntu_nbd_smoke_test failed with Bionic + ubuntu_nbd_smoke_test failed with Xenial ** Also affects: ubuntu-kernel-tests 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/1807869 Title: ubuntu_nbd_smoke_test failed with Xenial Status
[Kernel-packages] [Bug 1807818] Re: Touchpad scroll does not work on occasion
lotuspsychje@RooTBooK:~$ xinput --list-props 13 Device 'SynPS/2 Synaptics TouchPad': Device Enabled (142): 1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (273): 1 Device Accel Constant Deceleration (274): 2.50 Device Accel Adaptive Deceleration (275): 1.00 Device Accel Velocity Scaling (276):25.00 Synaptics Edges (277): 1574, 5366, 1343, 4507 Synaptics Finger (278): 25, 30, 0 Synaptics Tap Time (279): 180 Synaptics Tap Move (280): 252 Synaptics Tap Durations (281): 180, 180, 100 Synaptics ClickPad (282): 0 Synaptics Middle Button Timeout (283): 75 Synaptics Two-Finger Pressure (284):282 Synaptics Two-Finger Width (285): 7 Synaptics Scrolling Distance (286): 114, 114 Synaptics Edge Scrolling (287): 1, 1, 0 Synaptics Two-Finger Scrolling (288): 0, 0 Synaptics Move Speed (289): 1.00, 1.75, 0.034843, 0.00 Synaptics Off (290):0 Synaptics Locked Drags (291): 0 Synaptics Locked Drags Timeout (292): 5000 Synaptics Tap Action (293): 0, 0, 0, 0, 1, 0, 0 Synaptics Click Action (294): 1, 0, 0 Synaptics Circular Scrolling (295): 0 Synaptics Circular Scrolling Distance (296):0.10 Synaptics Circular Scrolling Trigger (297): 0 Synaptics Circular Pad (298): 0 Synaptics Palm Detection (299): 1 Synaptics Palm Dimensions (300):10, 200 Synaptics Coasting Speed (301): 20.00, 50.00 Synaptics Pressure Motion (302):30, 160 Synaptics Pressure Motion Factor (303): 1.00, 1.00 Synaptics Resolution Detect (304): 1 Synaptics Grab Event Device (305): 0 Synaptics Gestures (306): 1 Synaptics Capabilities (307): 1, 0, 1, 1, 1, 1, 1 Synaptics Pad Resolution (308): 70, 45 Synaptics Area (309): 0, 0, 0, 0 Synaptics Noise Cancellation (310): 28, 28 Device Product ID (269):2, 7 Device Node (268): "/dev/input/event5" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807818 Title: Touchpad scroll does not work on occasion Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 all up to date @ 11/12/2018 on kernel 4.15.0-42-generic The scroll of the touchpad seems to be not working on occasion across several kernels reboot seems to fix this ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: lotuspsychje 16501 F...m pulseaudio /dev/snd/controlC0: lotuspsychje 16501 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 07:23:43 2018 InstallationDate: Installed on 2018-08-17 (115 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=6f47c936-5a01-46a0-ba45-9e56ecd8fd07 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.009 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.009:bd05/14/2018:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to:
[Kernel-packages] [Bug 1807838] 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/1807838 Title: Ubuntu crashed totally. Nothing responded. Could not even shut down. Status in linux package in Ubuntu: Confirmed Bug description: I was running a bash script which copied directories from a partition on my hard drive (never store data in the Linux partition) to external USB drives. After the script finished, Ubuntu 18.10 crashed. The mouse pointer moved but no window, or menu or keys responded. Could not even get the Menu to open so that I could shut down. Had to power down manually. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 3117 F pulseaudio /dev/snd/controlC0: robert 3117 F pulseaudio CurrentDesktop: MATE Date: Tue Dec 11 02:54:28 2018 InstallationDate: Installed on 2018-11-30 (11 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807842] 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/1807842 Title: [nouveau] Damage screen on boot Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I install Ubuntu 18.10 and when I booting system (installed or from usb) I see "broken" screen before system show desktop (attached photo). On this damage screen I see mouse cursor, but is OK and when I try move cursor arround screen in every place cursor is OK, but background of screen is broken. In Ubuntu 18.04.1 LTS is everything OK. I try nvidia drivers, but I have another problem: screen is not damaged, but when I open Activities or when I typing password on every keypress or cursor move screen blinking on bottom side. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Prístup odmietnutý: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 08:57:41 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0647] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. G96M [GeForce 9600M GT] [106b:00bc] NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00bb] InstallationDate: Installed on 2018-12-10 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Apple Inc. MacBookPro5,3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=46b8171c-35ba-4d62-9203-2edd74237d37 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP53.88Z.00AC.B03.0906151647 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22587C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22587C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,3:pvr1.0:rvnAppleInc.:rnMac-F22587C8:rvr:cvnAppleInc.:ct10:cvrMac-F22587C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro5,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807842] Re: Damage screen on boot
** Tags added: nouveau ** Summary changed: - Damage screen on boot + [nouveau] Damage screen on boot ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (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/1807842 Title: [nouveau] Damage screen on boot Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I install Ubuntu 18.10 and when I booting system (installed or from usb) I see "broken" screen before system show desktop (attached photo). On this damage screen I see mouse cursor, but is OK and when I try move cursor arround screen in every place cursor is OK, but background of screen is broken. In Ubuntu 18.04.1 LTS is everything OK. I try nvidia drivers, but I have another problem: screen is not damaged, but when I open Activities or when I typing password on every keypress or cursor move screen blinking on bottom side. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Prístup odmietnutý: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 08:57:41 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0647] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. G96M [GeForce 9600M GT] [106b:00bc] NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00bb] InstallationDate: Installed on 2018-12-10 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Apple Inc. MacBookPro5,3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=46b8171c-35ba-4d62-9203-2edd74237d37 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP53.88Z.00AC.B03.0906151647 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22587C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22587C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,3:pvr1.0:rvnAppleInc.:rnMac-F22587C8:rvr:cvnAppleInc.:ct10:cvrMac-F22587C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro5,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807842] [NEW] [nouveau] Damage screen on boot
You have been subscribed to a public bug: I install Ubuntu 18.10 and when I booting system (installed or from usb) I see "broken" screen before system show desktop (attached photo). On this damage screen I see mouse cursor, but is OK and when I try move cursor arround screen in every place cursor is OK, but background of screen is broken. In Ubuntu 18.04.1 LTS is everything OK. I try nvidia drivers, but I have another problem: screen is not damaged, but when I open Activities or when I typing password on every keypress or cursor move screen blinking on bottom side. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Prístup odmietnutý: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 08:57:41 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0647] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. G96M [GeForce 9600M GT] [106b:00bc] NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00bb] InstallationDate: Installed on 2018-12-10 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Apple Inc. MacBookPro5,3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=46b8171c-35ba-4d62-9203-2edd74237d37 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP53.88Z.00AC.B03.0906151647 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22587C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22587C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,3:pvr1.0:rvnAppleInc.:rnMac-F22587C8:rvr:cvnAppleInc.:ct10:cvrMac-F22587C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro5,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption cosmic nouveau ubuntu -- [nouveau] Damage screen on boot https://bugs.launchpad.net/bugs/1807842 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806423] Re: linux-gcp: 4.18.0-1005.6 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** 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: 1806409 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED verification-testing: Testing in progress -- 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/1806423 Title: linux-gcp: 4.18.0-1005.6 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow 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 Cosmic: 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: 1806409 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807838] [NEW] Ubuntu crashed totally. Nothing responded. Could not even shut down.
Public bug reported: I was running a bash script which copied directories from a partition on my hard drive (never store data in the Linux partition) to external USB drives. After the script finished, Ubuntu 18.10 crashed. The mouse pointer moved but no window, or menu or keys responded. Could not even get the Menu to open so that I could shut down. Had to power down manually. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 3117 F pulseaudio /dev/snd/controlC0: robert 3117 F pulseaudio CurrentDesktop: MATE Date: Tue Dec 11 02:54:28 2018 InstallationDate: Installed on 2018-11-30 (11 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "copyBooks" https://bugs.launchpad.net/bugs/1807838/+attachment/5221116/+files/copyBooks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807838 Title: Ubuntu crashed totally. Nothing responded. Could not even shut down. Status in linux package in Ubuntu: New Bug description: I was running a bash script which copied directories from a partition on my hard drive (never store data in the Linux partition) to external USB drives. After the script finished, Ubuntu 18.10 crashed. The mouse pointer moved but no window, or menu or keys responded. Could not even get the Menu to open so that I could shut down. Had to power down manually. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 3117 F pulseaudio /dev/snd/controlC0: robert 3117 F pulseaudio CurrentDesktop: MATE Date: Tue Dec 11 02:54:28 2018 InstallationDate: Installed on 2018-11-30 (11 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Uncommenting "WaylandEnable=false" worked for me in 18.10 fresh install and applying nvidia-390 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
** Also affects: alsa-lib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
