[Kernel-packages] [Bug 1860390] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321859/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321861/+files/UdevDb.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Attachment removed: "AlsaDevices.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+attachment/5321845/+files/AlsaDevices.txt
** Attachment removed: "AplayDevices.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+attachment/5321846/+files/AplayDevices.txt
** Attachment removed: "RfKill.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+attachment/5321860/+files/RfKill.txt
** Attachment removed: "Card0.Amixer.values.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+attachment/5321848/+files/Card0.Amixer.values.txt
** Attachment removed: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+attachment/5321849/+files/Card0.Codecs.codec.0.txt
** Attachment removed: "PciMultimedia.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+attachment/5321854/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
[Kernel-packages] [Bug 1860390] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321860/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321858/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321857/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321856/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321847/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321853/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] Card0.Codecs.codec.0.txt
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321849/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] Card0.Codecs.codec.2.txt
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321850/+files/Card0.Codecs.codec.2.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] AplayDevices.txt
apport information
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321846/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321855/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321852/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] PciMultimedia.txt
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321854/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321851/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] Re: Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep (suspend to ram)
apport information ** Tags added: apport-collected ** Description changed: This is a reintroduction of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did not happen before in Ubuntu 19.04. It seems that the Dell 9360 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo update-grub). + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-9-generic. + ApportVersion: 2.20.11-0ubuntu15 + Architecture: amd64 + ArecordDevices: + List of CAPTURE Hardware Devices + card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog] +Subdevices: 1/1 +Subdevice #0: subdevice #0 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: user 1570 F pulseaudio + Card0.Amixer.info: + Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131' +Mixer name : 'Realtek ALC3246' +Components : 'HDA:10ec0256,1028075b,0012 HDA:8086280b,80860101,0010' +Controls : 55 +Simple ctrls : 17 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 8087:0a2b Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M + |__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M + |__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M + MachineType: Dell Inc. XPS 13 9360 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@ resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2 i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-9-generic N/A + linux-backports-modules-5.4.0-9-generic N/A + linux-firmware 1.184 + Tags: focal + Uname: Linux 5.4.0-9-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: cdrom lp lpadmin plugdev sudo + WifiSyslog: + + _MarkForUpload: False + dmi.bios.date: 11/14/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.13.0 + dmi.board.name: 04N87K + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 13 9360 + dmi.product.sku: 075B + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1860390/+attachment/5321845/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860390 Title: Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep (suspend to ram) Status in linux package in Ubuntu: Confirmed Bug description: This is a reintroduction of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did not happen before in Ubuntu 19.04. It seems that the Dell 9360 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep >
[Kernel-packages] [Bug 1860390] Card0.Amixer.values.txt
apport information
** Attachment added: "Card0.Amixer.values.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321848/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep
(suspend to ram)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle mode rather than
deep sleep, forgoing significant power savings.
I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is
PM: suspend entry (s2idle)
PM: suspend exit
cat /sys/power/mem_sleep showed
[s2idle] deep
As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).
Then the output of cat /sys/power/mem_sleep was
s2idle [deep]
After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns
PM: suspend entry (deep)
PM: suspend exit
I have made this permanent by editing
/etc/default/grub
and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 1570 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
Mixer name : 'Realtek ALC3246'
Components : 'HDA:10ec0256,1028075b,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic
root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@
resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2
i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
linux-restricted-modules-5.4.0-9-generic N/A
linux-backports-modules-5.4.0-9-generic N/A
linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858543] Re: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker
5.0.0-1010.15 - oracle Regression test CMPL, RTB. Issue to note in oracle (amd64): ubuntu_kernel_selftests - net test timeout (bug 1860111) trace_printk in ftrace (bug 1830084) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) apic-split (bug 1821390) pmu (bug 1853797) port80 (bug 1845688) vmx (bug 1821394) ubunut_ltp - proc01 (bug 1829849) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_subgroup_charge (bug 1847982) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) umip_basic_test (bug 1853798) Skipped / blacklisted: * libhugetlbfs * Note the ubuntu_kernel_selftests must be reviewed on the jenkins directly (bug 1860093) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1858543 Title: disco/linux-oracle: 5.0.0-1010.15 -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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1859724' packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Monday, 13. January 2020 16:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.0: bug 1858542 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846899] Re: X won't start at boot with either nvidia driver on GeForce GT 730 (bionic)
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Won't Fix ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- 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/1846899 Title: X won't start at boot with either nvidia driver on GeForce GT 730 (bionic) Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: The video card is a GeForce GT 730, which worked well with Ubuntu 16.04. After changing to Xubuntu 18.04, I can only run the Nouveau driver and the lack of acceleration is quite noticeable. When I try to enable the "tested" NVidia driver (390), the system never presents a log-in prompt, I just get a colorful display of large blinking gibberish. I have to go to the boot options, go directly to root prompt, and remove the NVidia driver. This make the system usable again, but I'm back to the Nouveau driver. I get similar symptoms with version 340.107 of the NVidia driver. It's a little hard to collect debug information when I can't get to a prompt to look at log files... Suggestions are welcome. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Sat Oct 5 13:56:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF108 [GeForce GT 730] [19da:8199] InstallationDate: Installed on 2019-04-13 (175 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=d19b5e72-689e-4877-93dd-0d4bf5f7cc98 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4024 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Oct 5 13:56:03 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3
** Also affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux-hwe (Ubuntu) Status: New => Confirmed -- 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/1851162 Title: nvidia-drivers-390 fail to build with kernel 5.3 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853798] Re: umip_basic_test in kernel_misc from ubuntu_ltp failed on D-Oracle
Found in B-5.0-oracle as well. ** Tags added: sru-20200106 ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1853798 Title: umip_basic_test in kernel_misc from ubuntu_ltp failed on D-Oracle Status in ubuntu-kernel-tests: New Status in linux-signed-oracle package in Ubuntu: New Bug description: <<>> tag=umip_basic_test stime=1574662675 cmdline="umip_basic_test" contacts="" analysis=exit <<>> tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1005-oracle' incrementing stop tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s umip_basic_test.c:158: INFO: cpuinfo contains umip, CPU supports umip umip_basic_test.c:40: INFO: TEST sgdt, sgdt result save at [0x7ffdd514086e] umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4 umip_basic_test.c:135: PASS: Got SIGSEGV umip_basic_test.c:50: INFO: TEST sidt, sidt result save at [0x7ffdd514086e] umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4 umip_basic_test.c:135: PASS: Got SIGSEGV umip_basic_test.c:59: INFO: TEST sldt, sldt result save at [0x7ffdd5140860] umip_basic_test.c:135: PASS: Got SIGSEGV umip_basic_test.c:68: INFO: TEST smsw, smsw result save at [0x7ffdd5140860] umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4 umip_basic_test.c:139: FAIL: Didn't receive SIGSEGV, child exited with exited with 0 umip_basic_test.c:77: INFO: TEST str, str result save at [0x7ffdd5140860] umip_basic_test.c:135: PASS: Got SIGSEGV Summary: passed 4 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9 ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21 Uname: Linux 5.0.0-1005-oracle x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Nov 25 06:18:04 2019 SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852976] Re: zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on D-Oracle
Hi Sean, I found the ACT repo on AWS is out-dated, if you found this issue on it please give it another try. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852976 Title: zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on D-Oracle Status in ubuntu-kernel-tests: Fix Released Status in linux-aws package in Ubuntu: New Status in linux-signed-oracle package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Status in linux-signed-oracle source package in Bionic: New Status in linux-aws source package in Disco: New Status in linux-signed-oracle source package in Disco: Invalid Bug description: It looks like the failures in zram01 are causing zram02 and zram03 to fail as well. Seems that this is broken since commit 7cfac804 (zram: Rewrite shell tests into new API) tag=zram01 stime=1573887406 dur=300 exit=signaled stat=9 core=no cu=23757 cs=7590 startup='Sat Nov 16 06:56:46 2019' zram01 1 TINFO: timeout per run is 0h 5m 0s zram01 1 TINFO: create '4' zram device(s) zram01 1 TPASS: test succeeded zram01 1 TCONF: The device attribute max_comp_streams was introduced in kernel 3.15 and deprecated in 4.7 zram01 2 TINFO: test that we can set compression algorithm zram01 2 TINFO: supported algs: [lzo] lz4 lz4hc 842 zstd zram01 2 TINFO: /sys/block/zram0/comp_algorithm = 'lzo' (1/4) zram01 2 TINFO: /sys/block/zram1/comp_algorithm = 'lzo' (2/4) zram01 2 TINFO: /sys/block/zram2/comp_algorithm = 'lzo' (3/4) zram01 2 TINFO: /sys/block/zram3/comp_algorithm = 'lzo' (4/4) zram01 2 TPASS: test succeeded zram01 3 TINFO: set disk size to zram device(s) zram01 3 TINFO: /sys/block/zram0/disksize = '26214400' (1/4) zram01 3 TINFO: /sys/block/zram1/disksize = '26214400' (2/4) zram01 3 TINFO: /sys/block/zram2/disksize = '26214400' (3/4) zram01 3 TINFO: /sys/block/zram3/disksize = '402653184' (4/4) zram01 3 TPASS: test succeeded zram01 4 TINFO: set memory limit to zram device(s) zram01 4 TINFO: /sys/block/zram0/mem_limit = '25M' (1/4) zram01 4 TINFO: /sys/block/zram1/mem_limit = '25M' (2/4) zram01 4 TINFO: /sys/block/zram2/mem_limit = '25M' (3/4) zram01 4 TINFO: /sys/block/zram3/mem_limit = '384M' (4/4) zram01 4 TPASS: test succeeded zram01 5 TINFO: make ext3 filesystem on /dev/zram0 zram01 5 TINFO: make ext4 filesystem on /dev/zram1 zram01 5 TINFO: make xfs filesystem on /dev/zram2 zram01 5 TINFO: make btrfs filesystem on /dev/zram3 zram01 5 TPASS: zram_makefs succeeded zram01 6 TINFO: mount /dev/zram0 zram01 6 TINFO: mount /dev/zram1 zram01 6 TINFO: mount /dev/zram2 zram01 6 TINFO: mount /dev/zram3 zram01 6 TPASS: mount of zram device(s) succeeded zram01 7 TINFO: filling zram0 (it can take long time) zram01 7 TPASS: zram0 was filled with '20628' KB zram01 7 TPASS: compression ratio: 732.90:1 zram01 7 TINFO: filling zram1 (it can take long time) zram01 7 TPASS: zram1 was filled with '20140' KB zram01 7 TPASS: compression ratio: 5151.97:1 zram01 7 TINFO: filling zram2 (it can take long time) zram01 7 TPASS: zram2 was filled with '17756' KB zram01 7 TPASS: compression ratio: 285.26:1 zram01 7 TINFO: filling zram3 (it can take long time) zram01 1 TBROK: test killed, timeout! If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tag=zram02 stime=1573887712 dur=0 exit=exited stat=1 core=no cu=2 cs=0 startup='Sat Nov 16 07:01:52 2019' zram02 1 TINFO: timeout per run is 0h 5m 0s zram02 1 TINFO: create '1' zram device(s) zram02 1 TFAIL: unexpected num of devices: 4 /opt/ltp/testcases/bin/zram02.sh: 27: echo: echo: I/O error zram02 1 TINFO: AppArmor enabled, this may affect test results zram02 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) zram02 1 TINFO: loaded AppArmor profiles: none Summary: passed 0 failed 1 skipped 0 warnings 0 tag=zram03 stime=1573887718 dur=0 exit=exited stat=2 core=no cu=0 cs=0 startup='Sat Nov 16 07:01:58 2019' zram03 0 TINFO : create a zram device with 536870912 bytes in size. zram03 1 TBROK : safe_file_ops.c:301: Failed to close FILE '/sys/block/zram0/disksize' at zram03.c:87: errno=EBUSY(16): Device or resource busy zram03 2 TBROK : safe_file_ops.c:301: Remaining cases broken ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9 ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21 Uname: Linux 5.0.0-1005-oracle x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Nov 18 07:50:37 2019 SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Kernel-packages] [Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes
** Tags added: sru-20200106 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836167 Title: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: New Bug description: <<>> incrementing stop Name: cpuhotplug03 Date: Thu Jul 11 08:31:48 UTC 2019 Desc: Do tasks get scheduled to a newly on-lined CPU? CPU is 1 sh: echo: I/O error cpuhotplug03 1 TBROK: CPU1 cannot be offlined USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 4642 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4643 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4644 0.0 0.0 2020 468 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4645 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4646 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4647 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4648 0.0 0.0 2020 456 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4649 0.0 0.0 2020 508 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4650 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4651 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4652 0.0 0.0 2020 484 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4653 0.0 0.0 2020 496 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4654 0.0 0.0 2020 464 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4655 0.0 0.0 2020 492 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4656 0.0 0.0 2020 448 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4657 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4661 0.0 0.0 7540 648 pts/0S08:31 0:00 grep cpuhotplug_do_spin_loop cpuhotplug03 1 TINFO: Onlining CPU 1 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found onCPU1 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=2 corefile=no cutime=1060 cstime=9 <<>> Test passed on ThunderX ARM64, probably a test case issue. Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug03 cpuhotplug03.sh -c 1 -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer']
[Kernel-packages] [Bug 1843385] Re: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
Anyway, since then nvidia-390 does support kernel 5.0 -- 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/1843385 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Just upgraded the distro to 19.10 (dev) ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 (not installed) ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Tue Sep 10 08:08:26 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2016-02-03 (1314 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.3 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1843385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843385] Re: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
Yes, though this looks like a pre-release (Sep 2019) instance of that bug. ERROR (dkms apport): kernel package linux-headers-5.0.0-27-generic is not supported Error! Bad return status for module build on kernel: 5.0.0-27-generic (x86_64) Consult /var/lib/dkms/nvidia/390.129/build/make.log for more information. dpkg: error processing package nvidia-dkms-390 (--configure): installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Fix Committed => Fix Released -- 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/1843385 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Just upgraded the distro to 19.10 (dev) ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 (not installed) ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Tue Sep 10 08:08:26 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2016-02-03 (1314 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.3 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1843385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3
** Tags added: regression-release ** Tags added: regression-update -- 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/1851162 Title: nvidia-drivers-390 fail to build with kernel 5.3 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858588] Re: xenial/linux-snapdragon: 4.4.0-1132.140 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1859718' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Monday, 13. January 2020 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858588 Title: xenial/linux-snapdragon: 4.4.0-1132.140 -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: Fix Released 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1859718' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Monday, 13. January 2020 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858588] Re: xenial/linux-snapdragon: 4.4.0-1132.140 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: https://certification.canonical.com/hardware/201611-25221/submission/159401/ ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858588 Title: xenial/linux-snapdragon: 4.4.0-1132.140 -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: Fix Released 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1859718' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Monday, 13. January 2020 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858586] Re: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1859718' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Monday, 13. January 2020 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1858586 Title: xenial/linux-raspi2: 4.4.0-1128.137 -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: Fix Released 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1859718' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Monday, 13. January 2020 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859700] Re: bionic/linux-raspi2: 4.15.0-1054.58 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1860123' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 16. January 2020 00:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1859699 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1859700 Title: bionic/linux-raspi2: 4.15.0-1054.58 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1860123' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 16. January 2020 00:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1859699 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859700] Re: bionic/linux-raspi2: 4.15.0-1054.58 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: rpi2: https://certification.canonical.com/hardware/201906-27188/submission/159374/ rpi3b-armhf: https://certification.canonical.com/hardware/201811-26649/submission/159375/ rpi3b-arm64: https://certification.canonical.com/hardware/201811-26649/submission/159371/ rpi3b+-armhf: https://certification.canonical.com/hardware/201810-26542/submission/159372/ rpi3b+-arm64: https://certification.canonical.com/hardware/201810-26542/submission/159377/ ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1859700 Title: bionic/linux-raspi2: 4.15.0-1054.58 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1860123' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 16. January 2020 00:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1859699 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858586] Re: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: https://certification.canonical.com/hardware/201906-27188/submission/159379/ ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1858586 Title: xenial/linux-raspi2: 4.4.0-1128.137 -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: Fix Released 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1859718' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Monday, 13. January 2020 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838176] Re: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor
Using Thinkpad T495s with Ryzen 3500U, on Ubuntu Budgie 18.04. After upgrading to Kernel 5.3, I ran into black screen at login and general system instability, and lots of "failed to write reg ... wait reg ..." in dmesg. No issues when booting to Kernel 5.0. Seems like there are several amdgpu firmeware upgrades in the past few week (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/log/). Followed these instructions (source: https://www.phoronix.com/scan.php?page=news_item=Ubuntu-19.10-Radeon- RX-5700): git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware/ sudo cp -va amdgpu/ /lib/firmware/ sudo update-initramfs -u reboot After that, and I'm no longer seeing "failed to write reg ... wait reg ..." in dmesg, and system is generally more stable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838176 Title: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor Status in linux package in Ubuntu: Confirmed Bug description: Was on 4.20, booted fine (with the boot option ivrs_ioapic[32]=00:14.0) Tried to boot 5.2.3 (but I believe this happened on 5.1.X too) It will boot to a certain extent, it does my disk password, i can see everything say "ok" when i do no quiet splash. But where it should go to the login screen I just see a single cursor Setting nomodeset lets me boot, looking at logs: Syslog Jul 27 21:28:58 kenji-mintop systemd[1]: Startup finished in 41.291s (kernel) + 8.383s (userspace) = 49.675s. Jul 27 21:28:59 kenji-mintop kernel: [ 50.535066] failed to write reg 1a6f4 wait reg 1a706 Jul 27 21:28:59 kenji-mintop NetworkManager[1082]: [1564288139.7335] manager: NetworkManager state is now CONNECTED_GLOBAL Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': new request (1 scripts) Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': start running ordered scripts... Jul 27 21:29:09 kenji-mintop kernel: [ 60.615575] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:09 kenji-mintop kernel: [ 60.615662] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:09 kenji-mintop kernel: [ 60.615665] [drm] GPU recovery disabled. Jul 27 21:29:11 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:19 kenji-mintop kernel: [ 70.855956] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:19 kenji-mintop kernel: [ 70.856043] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:19 kenji-mintop kernel: [ 70.856047] [drm] GPU recovery disabled. Jul 27 21:29:20 kenji-mintop zerotier-one[1984]: message repeated 3 times: [ connect: Host is unreachable] Jul 27 21:29:22 kenji-mintop systemd-timesyncd[968]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com). Jul 27 21:29:23 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:29 kenji-mintop kernel: [ 81.095310] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:29 kenji-mintop kernel: [ 81.095397] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:29 kenji-mintop kernel: [ 81.095401] [drm] GPU recovery disabled. Jul 27 21:29:40 kenji-mintop kernel: [ 91.335557] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:40 kenji-mintop kernel: [ 91.335645] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:40 kenji-mintop kernel: [ 91.335648] [drm] GPU recovery disabled. Jul 27 21:29:41 kenji-mintop zerotier-one[1984]: message repeated 6 times: [ connect: Host is unreachable] Jul 27 21:29:43 kenji-mintop systemd[1]: Starting Stop ureadahead data collection... Jul 27 21:29:43 kenji-mintop systemd[1]: Started Stop ureadahead data collection. Jul 27 21:29:44 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:50 kenji-mintop kernel: [ 101.575935] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:50 kenji-mintop kernel: [ 101.576023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:50 kenji-mintop kernel: [ 101.576027] [drm] GPU recovery disabled. Jul 27 21:30:00 kenji-mintop kernel: [ 111.815551] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted
[Kernel-packages] [Bug 1859799] Re: xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1859704 + kernel-stable-master-bug: '1860122' packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Monday, 20. January 2020 14:06 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1860122' packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Monday, 20. January 2020 14:06 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859799 Title: xenial/linux-deeplens: 4.15.0-1015.15 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1860122' packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Monday, 20. January 2020 14:06 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build kernel 5.3 [error: redefinition of ‘list_is_first’]
** Summary changed: - nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 [error: redefinition of ‘list_is_first’] + nvidia-drivers-390 fail to build kernel 5.3 [error: redefinition of ‘list_is_first’] ** Tags added: rls-bb-incoming rls-ee-incoming ** Summary changed: - nvidia-drivers-390 fail to build kernel 5.3 [error: redefinition of ‘list_is_first’] + nvidia-drivers-390 fail to build with kernel 5.3 -- 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/1851162 Title: nvidia-drivers-390 fail to build with kernel 5.3 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857821] Re: External HDMI monitor audio always reported as "unplugged"
Please start by testing the latest kernel version: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/ ** Changed in: linux (Ubuntu) Status: Fix Released => 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/1857821 Title: External HDMI monitor audio always reported as "unplugged" Status in linux package in Ubuntu: Incomplete Bug description: Hello my Ubuntu friends, I can no longer play sound over my external HDMI connected TV. The image displays perfectly, but all the HDMI output devices are listed as "unplugged" I have spent a huge amount of time trying every solution that Internet searching will bring but this has changed nothing. I have tired all available video drivers, including Xorg and NVIDEA 396.26, 340.107, and 384.130. This failure is recent because in the past I could play both audio and video through the HDMI connector. The laptop is dual boot with Windows 10 and the HDMI works perfectly on that OS, although I rarely use it... I am wondering if upgrading my Xubuntu to the latest LTS could potentially solve this issue, but I fear such an update since I depend on this computer and an outage would be very hard for me... Any thoughts would be great. Thanks for making Linux great! Bob ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Dec 29 17:00:14 2019 InstallationDate: Installed on 2015-05-11 (1693 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859071] Re: Native mode 2560x1080 is randomly unavailable on some boots
I believe this is a kernel bug or a hardware fault. So that's why it's assigned to the kernel now. This is not a Wayland issue since the same applies to Xorg, and we've confirmed in comment #42 that the problem is originating in the kernel. The next step I think will be to play with different "i2c timeouts", which you can google. But I am guessing now and we need the help of the kernel team. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859071 Title: Native mode 2560x1080 is randomly unavailable on some boots Status in linux package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu1 Candidate: 1.30.0-0ubuntu1 Version table: *** 1.30.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) I have a 3rd gen Intel laptop with only Ubuntu 19.10 installed, and a monitor attached via DisplayPort. The monitor has a native resolution of 2560x1080. When I power on my laptop, it is seemingly random whether one of the three following situations occurs. 1. Displays at the proper native resolution of 2560x1080, 2. Displays at 1600x1200 but not let me select a higher resolution in display settings, or 3. The display will fail to connect and stay blank (when I enter display settings it will be on "Single Monitor" mode, but from there I can enable Join Displays and set it to its native resolution). Please note I selected "I don't know" instead of gdm3 or lightdm since i've been having this issue since before installing/switching to lightdm. Please let me know what additional information I can provide at this time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f7] InstallationDate: Installed on 2020-01-05 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2478A44 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=5b93649d-7f54-41f8-85e1-dc9d5d494872 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Tags: eoan ubuntu Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G3ET96WW(2.56) dmi.board.asset.tag: Not Available dmi.board.name: 2478A44 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG3ET96WW(2.56):bd08/23/2013:svnLENOVO:pn2478A44:pvrThinkPadL530:rvnLENOVO:rn2478A44:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad L530 dmi.product.name: 2478A44 dmi.product.sku: LENOVO_MT_2478 dmi.product.version: ThinkPad L530 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 - xenial/linux-hwe: bug 1859704, bug 1860122 + xenial/linux-hwe: bug 1860122 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859702] Re: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Ready for Promote to Proposed phase-changed: Monday, 20. January 2020 12:56 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1859702 Title: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Ready for Promote to Proposed phase-changed: Monday, 20. January 2020 12:56 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] 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 1860390 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/1860390 Title: Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep (suspend to ram) Status in linux package in Ubuntu: Incomplete Bug description: This is a reintroduction of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did not happen before in Ubuntu 19.04. It seems that the Dell 9360 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo update-grub). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
Affects me too on a Dell XPS 13 9360, I opened a new bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 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 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860390] [NEW] Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep (suspend to ram)
Public bug reported: This is a reintroduction of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did not happen before in Ubuntu 19.04. It seems that the Dell 9360 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo update-grub). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860390 Title: Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep (suspend to ram) Status in linux package in Ubuntu: New Bug description: This is a reintroduction of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did not happen before in Ubuntu 19.04. It seems that the Dell 9360 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo update-grub). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859154] Re: bionic/linux-gke-5.3: 5.3.0-1011.12~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1856988 packages: main: linux-gke-5.3 meta: linux-meta-gke-5.3 signed: linux-signed-gke-5.3 - phase: Holding before Promote to Security - phase-changed: Monday, 20. January 2020 11:27 UTC + phase: Ready for Promote to Security + phase-changed: Monday, 20. January 2020 23:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- not ready for security (replication dwell) + promote-to-security: Pending -- ready to copy trackers: bionic/linux-gke-5.3/gke-kernel: bug 1859153 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859154 Title: bionic/linux-gke-5.3: 5.3.0-1011.12~18.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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released 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 verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1856988 packages: main: linux-gke-5.3 meta: linux-meta-gke-5.3 signed: linux-signed-gke-5.3 phase: Ready for Promote to Security phase-changed: Monday, 20. January 2020 23:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy trackers: bionic/linux-gke-5.3/gke-kernel: bug 1859153 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Touchpad not showing up in /proc/bus/input/devices
hello, also having this problem with the ThinkBook 15. The touchpad seems to be of type "ELAN062F". I see this is also the same as listed in OP's udevdb. It seems that this could be the fix, since the ID "ELAN062F" is not present in the whitelist in "include/linux/input/elan-i2c-ids.h": https://lkml.org/lkml/2019/12/1/179 ? Can anyone confirm if this is correct? And, is there any easy way to enable this without recompiling the kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849720] Re: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)
Sorry for responding so late, I've been using the workaround of setting the device model of the virtual NIC to use "virtio" instead of "e1000e" for the last several months for some critical production work and I didn't want to rock the boat. I'm currently running kernel: 5.3.0-26-generic and I'm no longer experiencing the hard crash. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: qemu (Ubuntu) Status: In Progress => 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/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9
[Kernel-packages] [Bug 1859071] Re: Native mode 2560x1080 is randomly unavailable on some boots
Yes, it usually shows more modes, notably with some duplicates (different refresh rates, perhaps)? it basically looks like the modes.txt i already posted except also with this at the top: /sys/class/drm/card0-DP-2/modes:2560x1080 /sys/class/drm/card0-DP-2/modes:2560x1080 /sys/class/drm/card0-DP-2/modes:2560x1080 /sys/class/drm/card0-DP-2/modes:1920x1080 /sys/class/drm/card0-DP-2/modes:1920x1080 /sys/class/drm/card0-DP-2/modes:1920x1080 /sys/class/drm/card0-DP-2/modes:1920x1080 /sys/class/drm/card0-DP-2/modes:1920x1080 /sys/class/drm/card0-DP-2/modes:1680x1050 Anyway, I wanted to comment that I was able to reproduce this bug on a fresh install of CentOS 8 on the same laptop, albeit only once and after waking the computer from suspend, instead of during boot. I did the same command to dump all the modes to a text file and saw the results were the same after waking that install from suspend. So, i'm assuming it's not a Ubuntu problem, instead it's either a hardware issue as you suggested it could be, or a Wayland issue - since this CentOS 8 install is also using Wayland to log in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859071 Title: Native mode 2560x1080 is randomly unavailable on some boots Status in linux package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu1 Candidate: 1.30.0-0ubuntu1 Version table: *** 1.30.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) I have a 3rd gen Intel laptop with only Ubuntu 19.10 installed, and a monitor attached via DisplayPort. The monitor has a native resolution of 2560x1080. When I power on my laptop, it is seemingly random whether one of the three following situations occurs. 1. Displays at the proper native resolution of 2560x1080, 2. Displays at 1600x1200 but not let me select a higher resolution in display settings, or 3. The display will fail to connect and stay blank (when I enter display settings it will be on "Single Monitor" mode, but from there I can enable Join Displays and set it to its native resolution). Please note I selected "I don't know" instead of gdm3 or lightdm since i've been having this issue since before installing/switching to lightdm. Please let me know what additional information I can provide at this time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f7] InstallationDate: Installed on 2020-01-05 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2478A44 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=5b93649d-7f54-41f8-85e1-dc9d5d494872 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Tags: eoan ubuntu Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G3ET96WW(2.56) dmi.board.asset.tag: Not Available dmi.board.name: 2478A44 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG3ET96WW(2.56):bd08/23/2013:svnLENOVO:pn2478A44:pvrThinkPadL530:rvnLENOVO:rn2478A44:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad L530 dmi.product.name: 2478A44 dmi.product.sku: LENOVO_MT_2478 dmi.product.version: ThinkPad L530 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2:
[Kernel-packages] [Bug 1860306] Re: Linux kernel 5.3.0-26 breaks nvidia driver
Using dkms manually: sudo dkms install -m nvidia -v 390.116 -k 5.3.0-26-generic DKMS make.log for nvidia-390.116 for kernel 5.3.0-26-generic (x86_64) lundi 20 janvier 2020, 22:05:02 (UTC+0100) make[1] : on entre dans le répertoire « /usr/src/linux-headers-5.3.0-26-generic » test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860306 Title: Linux kernel 5.3.0-26 breaks nvidia driver Status in linux package in Ubuntu: Confirmed Bug description: Upon installation of kernel update 5.3.0.26.95, after a reboot, Second screen would not come on and nvidia control panel was missing majority of options Graphics driver settings could not be changed and upon reinstallation attempt of nvidia driver 390, installation failed and drivers became corrupted. Ended up reinstalling OS, but discovered later that booting in an older kernel fixed the issue. VERSION.LOG: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Release: Description: Linux Mint 19.3 Tricia Release: 19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777586] Re: Ubuntu Server 18.04 LTS aacraid error
I compiled kernels with the patch for u16.04 and u18.04, seems to be working for me: https://t12.catchmedia.com/kernel_adaptec/ No warranties, use on your own risk. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777586 Title: Ubuntu Server 18.04 LTS aacraid error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and am now running into these raid adapter driver errors. The server ran fine in older version. My apologies as I lost the exact version, but it never had any errors like this version. Now when ever I try to copy files to the RAID 5 drive, or untar a file, I get these errors now after a few MB's of written data. Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux batboat:/var/log$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 I have tried the IRQ debugging tips to no avail. I loaded in Debian9.4.0 and it only briefly showed this error once. But appears to be much more resilient and appears to work fine. Jun 19 00:02:21 batboat kernel: [ 498.770839] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.139167] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.795083] aacraid :03:09.0: Adapter health - 199 Jun 19 00:02:37 batboat kernel: [ 514.800376] aacraid :03:09.0: outstanding cmd: midlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800378] aacraid :03:09.0: outstanding cmd: lowlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800381] aacraid :03:09.0: outstanding cmd: error handler-0 Jun 19 00:02:37 batboat kernel: [ 514.800383] aacraid :03:09.0: outstanding cmd: firmware-5 Jun 19 00:02:37 batboat kernel: [ 514.800385] aacraid :03:09.0: outstanding cmd: kernel-0 Jun 19 00:02:37 batboat kernel: [ 514.800391] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800394] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800396] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800399] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800401] sd 4:0:0:0: Device offlined - not ready after error recovery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 - xenial/linux-hwe: bug 1860122, bug 1859704 + xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860119] Re: eoan/linux: 5.3.0-29.31 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860119 Title: eoan/linux: 5.3.0-29.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860306] Re: Linux kernel 5.3.0-26 breaks nvidia driver
I confirm: /lib/modules/5.3.0-26-generic/updates is missing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860306 Title: Linux kernel 5.3.0-26 breaks nvidia driver Status in linux package in Ubuntu: Confirmed Bug description: Upon installation of kernel update 5.3.0.26.95, after a reboot, Second screen would not come on and nvidia control panel was missing majority of options Graphics driver settings could not be changed and upon reinstallation attempt of nvidia driver 390, installation failed and drivers became corrupted. Ended up reinstalling OS, but discovered later that booting in an older kernel fixed the issue. VERSION.LOG: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Release: Description: Linux Mint 19.3 Tricia Release: 19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860306] Re: Linux kernel 5.3.0-26 breaks nvidia driver
My syslog: Jan 20 21:20:26 pollux gpu-manager[997]: Error: can't open /lib/modules/5.3.0-26-generic/updates/dkms Jan 20 21:20:27 pollux gpu-manager[997]: Error: can't open /lib/modules/5.3.0-26-generic/updates/dkms ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860306 Title: Linux kernel 5.3.0-26 breaks nvidia driver Status in linux package in Ubuntu: Confirmed Bug description: Upon installation of kernel update 5.3.0.26.95, after a reboot, Second screen would not come on and nvidia control panel was missing majority of options Graphics driver settings could not be changed and upon reinstallation attempt of nvidia driver 390, installation failed and drivers became corrupted. Ended up reinstalling OS, but discovered later that booting in an older kernel fixed the issue. VERSION.LOG: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Release: Description: Linux Mint 19.3 Tricia Release: 19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860355] 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/1860355 Title: Bluetooth not working Status in linux package in Ubuntu: Confirmed Bug description: I tried hard reset but it didn't work, on doing hard reset, it showed message that [16.28759] Bluetooth: hci0: unexpected eventfor opcode 0x What should i do, the bluetooth is getting on but not showing any devices. After running command ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: suyash 1582 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 22:59:11 2020 InstallationDate: Installed on 2020-01-12 (8 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=f36f3094-f010-43d8-a94d-ea9e22a57626 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183A dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/17/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr0796100056160:rvnHewlett-Packard:rn183A:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: C8D00PA#ACJ dmi.product.version: 0796100056160 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860355] Re: Bluetooth not working
** 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/1860355 Title: Bluetooth not working Status in linux package in Ubuntu: New Bug description: I tried hard reset but it didn't work, on doing hard reset, it showed message that [16.28759] Bluetooth: hci0: unexpected eventfor opcode 0x What should i do, the bluetooth is getting on but not showing any devices. After running command ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: suyash 1582 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 22:59:11 2020 InstallationDate: Installed on 2020-01-12 (8 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=f36f3094-f010-43d8-a94d-ea9e22a57626 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183A dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/17/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr0796100056160:rvnHewlett-Packard:rn183A:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: C8D00PA#ACJ dmi.product.version: 0796100056160 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860355] [NEW] Bluetooth not working
You have been subscribed to a public bug: I tried hard reset but it didn't work, on doing hard reset, it showed message that [16.28759] Bluetooth: hci0: unexpected eventfor opcode 0x What should i do, the bluetooth is getting on but not showing any devices. After running command ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: suyash 1582 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 22:59:11 2020 InstallationDate: Installed on 2020-01-12 (8 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=f36f3094-f010-43d8-a94d-ea9e22a57626 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183A dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/17/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr0796100056160:rvnHewlett-Packard:rn183A:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: C8D00PA#ACJ dmi.product.version: 0796100056160 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- Bluetooth not working https://bugs.launchpad.net/bugs/1860355 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
Re: [Kernel-packages] [Bug 1857821] Re: External HDMI monitor audio always reported as "unplugged"
Well the workaround that I reported last suddenly stopped working today... Sigh I assume the change in behavior us due to some recent update... I am at a loss as to how to get this to work.. Cheers, Bob On Tue, 31 Dec 2019, 10:06 Grateful Frog, wrote: > Hi! > > Thanks for the tip. > > When I ran my PC on the 18.04 live OS, I noticed that by plugging the HDMI > cable on the normal HDMI port, that HDMI*2* was indicated as *plugged*. > > Later when I went back to the installed 16.04, the HDMI2 port was > indicated as unplugged (all the ports were) but it still worked correctly, > sending sound and video to the HDMI monitor. > > Although odd, this works so I will wait to upgrade until I have a backup > system available. > > As to trying the v5 kernels, in the past they were not compatible with my > v4 system so I will also wait on that as well. > > In summary, I learned that : > >- the standard HDMI connector maps to port HDMI2 >- the mini display connector maps to port HDMI1 >- despite being indicated as "unplugged" in the pulseaudio volume >control, the HDMI2 port works properly. > > Thank you for all your help - this is a great improvement! > > I hope you and all the Ubuntu team have a happy new year! > Cheers, > Bob > > On Tue, 31 Dec 2019 at 03:00, Daniel van Vugt < > daniel.van.v...@canonical.com> wrote: > >> Great! Sounds like a newer kernel is all you need. >> >> If you can't risk upgrading then I suggest just installing the latest >> stable kernel: >> >> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.6/ >> >> Please try that (and run 'uname' to confirm it's active). >> >> ** Changed in: linux (Ubuntu) >>Status: Incomplete => Fix Released >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1857821 >> >> Title: >> External HDMI monitor audio always reported as "unplugged" >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857821/+subscriptions >> > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857821 Title: External HDMI monitor audio always reported as "unplugged" Status in linux package in Ubuntu: Fix Released Bug description: Hello my Ubuntu friends, I can no longer play sound over my external HDMI connected TV. The image displays perfectly, but all the HDMI output devices are listed as "unplugged" I have spent a huge amount of time trying every solution that Internet searching will bring but this has changed nothing. I have tired all available video drivers, including Xorg and NVIDEA 396.26, 340.107, and 384.130. This failure is recent because in the past I could play both audio and video through the HDMI connector. The laptop is dual boot with Windows 10 and the HDMI works perfectly on that OS, although I rarely use it... I am wondering if upgrading my Xubuntu to the latest LTS could potentially solve this issue, but I fear such an update since I depend on this computer and an outage would be very hard for me... Any thoughts would be great. Thanks for making Linux great! Bob ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Dec 29 17:00:14 2019 InstallationDate: Installed on 2015-05-11 (1693 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin18043 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: Fix Committed Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Won't Fix Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang---  Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce---  1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory  --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
+1 (with kernel 5.4.0-2-amd64) No message with "dmesg" :'( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860144] Re: linux 5.4.0-11 fails to boot on arm64
FWIW, i rebuilt the tip of focal/master-next on the same box, and it works fine too: ubuntu@apollo:~$ uname -a Linux apollo 5.4.0-12-generic #15~1032f4a665a4 SMP Mon Jan 20 15:05:45 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860144 Title: linux 5.4.0-11 fails to boot on arm64 Status in linux package in Ubuntu: Incomplete Bug description: Series: Focal Kernel: 5.4.0-11.14 Problem: Kernel Fails to boot on arm64 hardware. During preliminary the following failure was observed in a VM after the -proposed kernel was installed from ppa:canonical-kernel- team/proposed autopkgtest login: [ 44.923688] kernel BUG at arch/arm64/kernel/traps.c:406! [ 44.925735] Internal error: Oops - BUG: 0 [#1] SMP [ 44.927059] Modules linked in: iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_ce ofpart redboot cmdlinepart cfi_cmdset_0001 cfi_probe cfi_util gen_probe physmap qemu_fw_cfg uio_pdrv_genirq uio map_funcs chipreg mtd sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon zstd_compress raid6_pq libcrc32c virtio_net net_failover virtio_blk failover [ 44.943611] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.5.0-4-snapdragon #5-Ubuntu [ 44.948138] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 44.951579] pstate: 0045 (nzcv daif +PAN -UAO) [ 44.953905] pc : do_undefinstr+0x60/0x68 [ 44.955836] lr : do_undefinstr+0x34/0x68 [ 44.957695] sp : 800010013550 [ 44.959644] x29: 800010013550 x28: 0001fd173c00 [ 44.962107] x27: x26: c642935b [ 44.964652] x25: x24: 80001001379c [ 44.966750] x23: 8045 x22: 800010cdc2f8 [ 44.968930] x21: 41573000 x20: [ 44.970885] x19: 800010013580 x18: 1400 [ 44.973300] x17: 1c00 x16: 1000 [ 44.975899] x15: 0c00 x14: [ 44.978497] x13: 01d8 x12: 0001ec755428 [ 44.981178] x11: 503e2aa6 x10: [ 44.983809] x9 : 80001036b4d0 x8 : [ 44.986435] x7 : 0001fd174128 x6 : 800010013548 [ 44.988607] x5 : x4 : 800011f5e100 [ 44.990548] x3 : 800011cf5f10 x2 : db67b15ed7685100 [ 44.992687] x1 : x0 : 8045 [ 44.994456] Call trace: [ 44.995286] do_undefinstr+0x60/0x68 [ 44.996622] el1_sync_handler+0x8c/0xd8 [ 44.998434] el1_sync+0xb4/0x180 [ 44.999604] e843419@0b9d_0001182e_66f8+0x0/0xff8 [ 45.001407] tcp_ack+0x428/0x940 [ 45.002578] tcp_rcv_established+0x174/0x6b0 [ 45.003984] tcp_v4_do_rcv+0x168/0x250 [ 45.005235] tcp_v4_rcv+0xb9c/0xd08 [ 45.006437] ip_protocol_deliver_rcu+0x44/0x200 [ 45.008109] ip_local_deliver_finish+0x54/0x68 [ 45.009492] ip_local_deliver+0x104/0x110 [ 45.010596] ip_sublist_rcv_finish+0x48/0x68 [ 45.011732] ip_sublist_rcv+0x174/0x1e8 [ 45.012707] ip_list_rcv+0x108/0x168 [ 45.013561] __netif_receive_skb_list_core+0x18c/0x220 [ 45.014832] netif_receive_skb_list_internal+0x194/0x2a0 [ 45.016207] gro_normal_list.part.0+0x24/0x40 [ 45.017548] napi_gro_receive+0x1bc/0x1d8 [ 45.018773] receive_buf+0x1d4/0x498 [virtio_net] [ 45.019967] virtnet_poll+0x168/0x6f8 [virtio_net] [ 45.021161] net_rx_action+0x178/0x460 [ 45.022087] __do_softirq+0x130/0x32c [ 45.023019] irq_exit+0xa0/0xc8 [ 45.023796] __handle_domain_irq+0x6c/0xc0 [ 45.024805] gic_handle_irq+0x58/0xa8 [ 45.025692] el1_irq+0x104/0x1c0 [ 45.026488] arch_cpu_idle+0x38/0x1c8 [ 45.027412] default_idle_call+0x20/0x40 [ 45.028361] do_idle+0x20c/0x2b0 [ 45.029184] cpu_startup_entry+0x28/0x68 [ 45.030146] secondary_start_kernel+0x154/0x1e0 [ 45.031275] Code: 97b6 f9400bf3 a8c27bfd d65f03c0 (d421) [ 45.032751] ---[ end trace b0983b157b7a3c23 ]--- [ 45.033868] Kernel panic - not syncing: Fatal exception in interrupt [ 45.035609] SMP: stopping secondary CPUs [ 45.036876] Kernel Offset: disabled [ 45.037966] CPU features: 0x0,20802000 [ 45.039153] Memory Limit: none [ 45.039952] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- Focal was deployed on a Hisilicon D05, After installing the kernel on bare metal there were no console logs after the EFI Boot Stub Booting local disk... [ grub.cfg-02:0f:b7:04 527B 100% 2.25B/s ] EFI stub: Booting Linux Kernel...[ grubaa64.efi 1.70MiB 100% 7.45KiB/s ] EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: Using DTB from configuration table EFI stub: Exiting boot
[Kernel-packages] [Bug 1860231] Re: 5.4.0-11 crash on cryptsetup open
After a first look at the kernel bug trace, it seems that q->make_request_fn(q, bio) (block/blk-core.c:1064) became NULL. The reason might be a race with a block device not yet properly initialized when some I/O requests were submitted (or a block device de- registered too early while some I/O was still in progress), but, considering it was triggered upon a mount, I would say the former scenario is more likely to be the case. I haven't noticed any potentially related fix in DM or in the core block layer. I'll keep investigating. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860231 Title: 5.4.0-11 crash on cryptsetup open Status in linux package in Ubuntu: Incomplete Bug description: An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc-kernel_374.snap. Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file:    1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image    1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm    2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work)    2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \   -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \   -device virtio-net-pci,netdev=mynet0 \   -drive file=pc.img,if=virtio \   -bios /usr/share/OVMF/OVMF_CODE.ms.fd    2.3. In the grub menu, edit the default option to include parameter "systemd.debug-shell=1" in the kernel command line    2.4. Boot the kernel 3. Crash the kernel    3.1. When the system boots to the "Press enter to configure" message, press ALT-F9 to enter the debug shell.    3.2. The system should have two partitions in /dev/vda. Create a third one with fdisk.    3.3. Create a LUKS encrypted partition: # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 (the system will complain about a missing locking directory, just ignore it.)    3.4. Open the encrypted device: # echo 123|cryptsetup open --key-file - /dev/vda name The Core 20 images contain the following udev rule which causes the new block device to be mounted automatically. This mount is what triggers the BUG: ACTION=="add", SUBSYSTEM=="block", KERNEL!="loop*", KERNEL!="ram*" \ RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k"    3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem to be caused by a race between dm-crypt loading and cryptsetup luksFormat for example). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860343] Re: Create new linux-raspi2-5.4 package
** Summary changed: - Update linux-raspi2 from 5.3 to 5.4 + Create new linux-raspi2-5.4 package ** Description changed: - The main Focal kernel in now based on 5.4, so update linux-raspi2 - accordingly. + The main Focal kernel in now based on 5.4, so create a corresponding + linux-raspi2-5.4 package. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1860343 Title: Create new linux-raspi2-5.4 package Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Focal: Confirmed Bug description: The main Focal kernel in now based on 5.4, so create a corresponding linux-raspi2-5.4 package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860144] Re: linux 5.4.0-11 fails to boot on arm64
Ok, i rebuilt the kernel locally: ubuntu@apollo:~$ uname -a Linux apollo 5.4.0-11-generic #14 SMP Mon Jan 20 12:58:43 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux and it works fine here. Seth mentioned a possible binutils regression, here's what i had installed (and what i used to build the kernel): ubuntu@apollo:~$ dpkg -l | grep binutils ii binutils 2.33.50.20200114-0ubuntu1 arm64GNU assembler, linker and binary utilities ii binutils-aarch64-linux-gnu2.33.50.20200114-0ubuntu1 arm64GNU binary utilities, for aarch64-linux-gnu target ii binutils-common:arm64 2.33.50.20200114-0ubuntu1 arm64Common files for the GNU assembler, linker and binary utilities ii libbinutils:arm64 2.33.50.20200114-0ubuntu1 arm64GNU binary utilities (private shared library) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860144 Title: linux 5.4.0-11 fails to boot on arm64 Status in linux package in Ubuntu: Incomplete Bug description: Series: Focal Kernel: 5.4.0-11.14 Problem: Kernel Fails to boot on arm64 hardware. During preliminary the following failure was observed in a VM after the -proposed kernel was installed from ppa:canonical-kernel- team/proposed autopkgtest login: [ 44.923688] kernel BUG at arch/arm64/kernel/traps.c:406! [ 44.925735] Internal error: Oops - BUG: 0 [#1] SMP [ 44.927059] Modules linked in: iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_ce ofpart redboot cmdlinepart cfi_cmdset_0001 cfi_probe cfi_util gen_probe physmap qemu_fw_cfg uio_pdrv_genirq uio map_funcs chipreg mtd sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon zstd_compress raid6_pq libcrc32c virtio_net net_failover virtio_blk failover [ 44.943611] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.5.0-4-snapdragon #5-Ubuntu [ 44.948138] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 44.951579] pstate: 0045 (nzcv daif +PAN -UAO) [ 44.953905] pc : do_undefinstr+0x60/0x68 [ 44.955836] lr : do_undefinstr+0x34/0x68 [ 44.957695] sp : 800010013550 [ 44.959644] x29: 800010013550 x28: 0001fd173c00 [ 44.962107] x27: x26: c642935b [ 44.964652] x25: x24: 80001001379c [ 44.966750] x23: 8045 x22: 800010cdc2f8 [ 44.968930] x21: 41573000 x20: [ 44.970885] x19: 800010013580 x18: 1400 [ 44.973300] x17: 1c00 x16: 1000 [ 44.975899] x15: 0c00 x14: [ 44.978497] x13: 01d8 x12: 0001ec755428 [ 44.981178] x11: 503e2aa6 x10: [ 44.983809] x9 : 80001036b4d0 x8 : [ 44.986435] x7 : 0001fd174128 x6 : 800010013548 [ 44.988607] x5 : x4 : 800011f5e100 [ 44.990548] x3 : 800011cf5f10 x2 : db67b15ed7685100 [ 44.992687] x1 : x0 : 8045 [ 44.994456] Call trace: [ 44.995286] do_undefinstr+0x60/0x68 [ 44.996622] el1_sync_handler+0x8c/0xd8 [ 44.998434] el1_sync+0xb4/0x180 [ 44.999604] e843419@0b9d_0001182e_66f8+0x0/0xff8 [ 45.001407] tcp_ack+0x428/0x940 [ 45.002578] tcp_rcv_established+0x174/0x6b0 [ 45.003984] tcp_v4_do_rcv+0x168/0x250 [ 45.005235] tcp_v4_rcv+0xb9c/0xd08 [ 45.006437] ip_protocol_deliver_rcu+0x44/0x200 [ 45.008109] ip_local_deliver_finish+0x54/0x68 [ 45.009492] ip_local_deliver+0x104/0x110 [ 45.010596] ip_sublist_rcv_finish+0x48/0x68 [ 45.011732] ip_sublist_rcv+0x174/0x1e8 [ 45.012707] ip_list_rcv+0x108/0x168 [ 45.013561] __netif_receive_skb_list_core+0x18c/0x220 [ 45.014832] netif_receive_skb_list_internal+0x194/0x2a0 [ 45.016207] gro_normal_list.part.0+0x24/0x40 [ 45.017548] napi_gro_receive+0x1bc/0x1d8 [ 45.018773] receive_buf+0x1d4/0x498 [virtio_net] [ 45.019967] virtnet_poll+0x168/0x6f8 [virtio_net] [ 45.021161] net_rx_action+0x178/0x460 [ 45.022087] __do_softirq+0x130/0x32c [ 45.023019] irq_exit+0xa0/0xc8 [ 45.023796] __handle_domain_irq+0x6c/0xc0 [ 45.024805] gic_handle_irq+0x58/0xa8 [ 45.025692] el1_irq+0x104/0x1c0 [ 45.026488] arch_cpu_idle+0x38/0x1c8 [ 45.027412] default_idle_call+0x20/0x40 [ 45.028361] do_idle+0x20c/0x2b0 [ 45.029184] cpu_startup_entry+0x28/0x68 [ 45.030146] secondary_start_kernel+0x154/0x1e0 [ 45.031275] Code: 97b6 f9400bf3 a8c27bfd d65f03c0 (d421) [ 45.032751] ---[ end trace b0983b157b7a3c23 ]--- [ 45.033868] Kernel panic - not syncing: Fatal exception in interrupt [ 45.035609] SMP:
[Kernel-packages] [Bug 1860343] [NEW] Update linux-raspi2 from 5.3 to 5.4
Public bug reported: The main Focal kernel in now based on 5.4, so update linux-raspi2 accordingly. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-raspi2 (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: linux-raspi2 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1860343 Title: Update linux-raspi2 from 5.3 to 5.4 Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Focal: Confirmed Bug description: The main Focal kernel in now based on 5.4, so update linux-raspi2 accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860231] Re: 5.4.0-11 crash on cryptsetup open
** Description changed: An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc- kernel_374.snap. Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: -1.1. Install the ubuntu-image from latest/edge - $ sudo snap install --channel latest/edge ubuntu-image -1.2. Build the image - $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model + Â Â Â 1.1. Install the ubuntu-image from latest/edge + $ sudo snap install --channel latest/edge ubuntu-image + Â Â Â 1.2. Build the image + $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm -2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the - stock ovmf from bionic may not work) -2.2. Boot the image - $ sudo kvm -snapshot -m 2048 -smp 4 \ - -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ - -device virtio-net-pci,netdev=mynet0 \ - -drive file=pc.img,if=virtio \ - -bios /usr/share/OVMF/OVMF_CODE.ms.fd -2.3. In the grub menu, edit the default option to include parameter - "systemd.debug-shell=1" in the kernel command line -2.4. Boot the kernel + Â Â Â 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the + stock ovmf from bionic may not work) + Â Â Â 2.2. Boot the image + $ sudo kvm -snapshot -m 2048 -smp 4 \ + Â Â -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ + Â Â -device virtio-net-pci,netdev=mynet0 \ + Â Â -drive file=pc.img,if=virtio \ + Â Â -bios /usr/share/OVMF/OVMF_CODE.ms.fd + Â Â Â 2.3. In the grub menu, edit the default option to include parameter + "systemd.debug-shell=1" in the kernel command line + Â Â Â 2.4. Boot the kernel 3. Crash the kernel -3.1. When the system boots to the "Press enter to configure" - message, press ALT-F9 to enter the debug shell. -3.2. The system should have two partitions in /dev/vda. Create a - third one with fdisk. -3.3. Create a LUKS encrypted partition: - # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 - (the system will complain about a missing locking directory, - just ignore it.) -3.4. Open the encrypted device: - # echo 123|cryptsetup open --key-file - /dev/vda name -3.5. Read the crash message + Â Â Â 3.1. When the system boots to the "Press enter to configure" + message, press ALT-F9 to enter the debug shell. + Â Â Â 3.2. The system should have two partitions in /dev/vda. Create a + third one with fdisk. + Â Â Â 3.3. Create a LUKS encrypted partition: + # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 + (the system will complain about a missing locking directory, + just ignore it.) + Â Â Â 3.4. Open the encrypted device: + # echo 123|cryptsetup open --key-file - /dev/vda name + + The Core 20 images contain the following udev rule which causes + the new block device to be mounted automatically. This mount is + what triggers the BUG: + ACTION=="add", SUBSYSTEM=="block", KERNEL!="loop*", KERNEL!="ram*" \ + RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k" + Â Â Â 3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem to be caused by a race between dm-crypt loading and cryptsetup luksFormat for
[Kernel-packages] [Bug 1859718] Re: xenial/linux: 4.4.0-173.203 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 16. January 2020 04:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-lts-xenial: bug 1859717 xenial/linux-fips: bug 1858589 + xenial/linux-kvm: bug 1858584 xenial/linux-raspi2: bug 1858586 xenial/linux-snapdragon: bug 1858588 xenial/linux/caracalla-kernel: bug 1859714 xenial/linux/pc-kernel: bug 1859715 xenial/linux/stlouis-kernel: bug 1859716 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859718 Title: xenial/linux: 4.4.0-173.203 -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: Fix Released 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 16. January 2020 04:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-lts-xenial: bug 1859717 xenial/linux-fips: bug 1858589 xenial/linux-kvm: bug 1858584 xenial/linux-raspi2: bug 1858586 xenial/linux-snapdragon: bug 1858588 xenial/linux/caracalla-kernel: bug 1859714 xenial/linux/pc-kernel: bug 1859715 xenial/linux/stlouis-kernel: bug 1859716 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844245] Re: Integrate Intel SGX driver into linux-azure
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1844245 Title: Integrate Intel SGX driver into linux-azure Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-azure source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-azure source package in Eoan: Fix Committed Bug description: Intel is still trying to upstream the SGX driver, but in the meantime it would be desirable to have it available on the linux-azure kernel. The following version relies only on Kbuild: https://github.com/haimc-intel/SGXDataCenterAttestationPrimitives inker-ph1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844245] Re: Integrate Intel SGX driver into linux-azure
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-eoan ** Tags added: verification-needed-bionic -- 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/1844245 Title: Integrate Intel SGX driver into linux-azure Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-azure source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-azure source package in Eoan: Fix Committed Bug description: Intel is still trying to upstream the SGX driver, but in the meantime it would be desirable to have it available on the linux-azure kernel. The following version relies only on Kbuild: https://github.com/haimc-intel/SGXDataCenterAttestationPrimitives inker-ph1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857074] Re: Cavium ThunderX CN88XX crashes on boot
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857074 Title: Cavium ThunderX CN88XX crashes on boot Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Series: Bionic Kernel: 4.15.0-74.84 linux-generic Steps to reproduce: Install 4.15.0-74.84 Kernel and boot the system. The following crash was observed while testing the proposed kernel for the 2019.12.02 SRU Cycle. This kernel was built to include fixes for the following bugs:   * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX (LP: #1853326) - Revert "arm64: Use firmware to detect CPUs that are not affected by   Spectre-v2" - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"   * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and Kunpeng920 (LP: #1852723) - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to   correct place The following crash appears to be a NEW bug. not related to the prior bugs listed above. This bug DOES NOT APPEAR to be related to LP#1857073. This is another NEW BUG. Hostname: Starmie Probable Cause is unknown at this point and still under investigation. [ OK ] Found device WDC_WD5003ABYZ-011FA0 efi.  Mounting /boot/efi... [ OK ] Mounted /boot/efi. [ OK ] Reached target Local File Systems.  Starting AppArmor initialization...  Starting Tell Plymouth To Write Out Runtime Data...  Starting ebtables ruleset management... [ 20.942427] kernel BUG at /build/linux-pWET3k/linux-4.15.0/fs/buffer.c:1240! [ 20.951416] Internal error: Oops - BUG: 0 [#1] SMP [ 20.958153] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip cavium_rng_vf shpchp cavium_rng gpio_keys uio_pdrv_genirq ipmi_ssif uio ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect aes_ce_blk sysimgblt fb_sys_fops aes_ce_cipher crc32_ce drm crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce ahci thunder_bgx libahci thunder_xcv i2c_thunderx mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 21.044326] Process systemd (pid: 1, stack limit = 0x5af6f18b) [ 21.053858] CPU: 1 PID: 1 Comm: systemd Not tainted 4.15.0-74-generic #84-Ubuntu [ 21.063931] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012 [ 21.074790] pstate: 20400085 (nzCv daIf +PAN -UAO) [ 21.082096] pc : __find_get_block+0x2e8/0x398 [ 21.088917] lr : __getblk_gfp+0x3c/0x2a8 [ 21.095379] sp : 099ab7e0 [ 21.101062] x29: 099ab7e0 x28: [ 21.108699] x27: x26: [ 21.116265] x25: 0001 x24: [ 21.123788] x23: 0008 x22: 801f26116c80 [ 21.131302] x21: 801f26116c80 x20: 245c [ 21.138808] x19: 1000 x18: a59c3a70 [ 21.146300] x17: x16: [ 21.153730] x15: 0020 x14: 0012 [ 21.161083] x13: 2f7374696e752f64 x12: 0101010101010101 [ 21.168397] x11: 7f7f7f7f7f7f7f7f x10: 0972d000 [ 21.175689] x9 : x8 : 801f7ba7e3c0 [ 21.183042] x7 : 801f7ba7e3e0 x6 : [ 21.190667] x5 : 0004 x4 : 0020 [ 21.197955] x3 : 0008 x2 : 1000 [ 21.205680] x1 : 245c x0 : 0080 [ 21.212918] Call trace: [ 21.217257] __find_get_block+0x2e8/0x398 [ 21.223160] __getblk_gfp+0x3c/0x2a8 [ 21.228644] ext4_getblk+0xcc/0x1b0 [ 21.233991] ext4_bread_batch+0x78/0x1c8 [ 21.239726] ext4_find_entry+0x2d4/0x598 [ 21.245416] ext4_lookup+0xac/0x278 [ 21.250612] lookup_slow+0xac/0x190 [ 21.255736]
[Kernel-packages] [Bug 1860119] Re: eoan/linux: 5.3.0-29.31 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 + bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Promote to Proposed - phase-changed: Monday, 20. January 2020 10:26 UTC + phase: Testing + phase-changed: Monday, 20. January 2020 14:11 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860119 Title: eoan/linux: 5.3.0-29.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859799] Re: xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1859704 packages: main: linux-deeplens meta: linux-meta-deeplens - phase: Holding before Promote to Proposed - phase-changed: Monday, 20. January 2020 11:47 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 20. January 2020 14:06 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859799 Title: xenial/linux-deeplens: 4.15.0-1015.15 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1859704 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Monday, 20. January 2020 14:06 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859718] Re: xenial/linux: 4.4.0-173.203 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/gT5whGUa/276-xenial-linux- image-440-173-generic-440-173203 ** Changed in: kernel-sru-workflow/certification-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/1859718 Title: xenial/linux: 4.4.0-173.203 -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: Fix Released 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 16. January 2020 04:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-lts-xenial: bug 1859717 xenial/linux-fips: bug 1858589 xenial/linux-raspi2: bug 1858586 xenial/linux-snapdragon: bug 1858588 xenial/linux/caracalla-kernel: bug 1859714 xenial/linux/pc-kernel: bug 1859715 xenial/linux/stlouis-kernel: bug 1859716 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 + bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Promote to Proposed - phase-changed: Monday, 20. January 2020 10:46 UTC + phase: Testing + phase-changed: Monday, 20. January 2020 14:12 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 - xenial/linux-hwe: bug 1859704, bug 1860122 + xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1860295] Re: dpkg-reconfigure nvidia-dkms-390 fails for kernel 5.3.0.-26 [error: redefinition of ‘list_is_first’]
*** This bug is a duplicate of bug 1851162 *** https://bugs.launchpad.net/bugs/1851162 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- 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/1860295 Title: dpkg-reconfigure nvidia-dkms-390 fails for kernel 5.3.0.-26 [error: redefinition of ‘list_is_first’] Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After the update from 5.0 to 5.3 the dkms reconfigure of the nvidia-390 kernel module fails. The problem seems to be in a conflict between the "list_is_first" routine in the module and the new kernel, which causes a compile error. I will upload /var/lib/dkms/nvidia/390.116/build/make.log The reference in the log to autoconf.h missing is spurious. The generated/autoconf.h exists. Here is the reconfigure output # dpkg-reconfigure nvidia-dkms-390 Removing all DKMS Modules Done. update-initramfs: deferring update (trigger activated) INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad Loading new nvidia-390.116 DKMS files... Building for 5.3.0-26-generic Building for architecture x86_64 Building initial module for 5.3.0-26-generic Error! Bad return status for module build on kernel: 5.3.0-26-generic (x86_64) Consult /var/lib/dkms/nvidia/390.116/build/make.log for more information. Processing triggers for initramfs-tools (0.130ubuntu3.9) ... update-initramfs: Generating /boot/initrd.img-5.3.0-26-generic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 19 19:34:34 2020 InstallationDate: Installed on 2012-12-14 (2592 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to bionic on 2018-04-29 (630 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1860295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
Im also experiencing this bug.
uname -a gives:
Linux ThinkPad-T480s 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19
08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
I set nvme_core.default_ps_max_latency_us=0, to turn APST off. Uptil now, I
haven't experienced any crashes. I haven't tried any other parameter values yet.
However, upon booting, some new text appears, but this doesn't seem to cause
any problems.
When will this bug be solved finally?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678184
Title:
APST quirk needed for Samsung 512GB NVMe drive
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Yakkety:
Fix Released
Status in linux source package in Zesty:
Fix Released
Bug description:
APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
That patch has a quirk for certain 256GB Samsung drives found in Dell
laptops that do not behave well when APST is enabled. I am
experiencing the same symptoms with the same model laptop except with
a 512GB Samsung. Prior to manually disabling APST the drive would die
and system would go down in flames with I/O errors within 20 to 40
minutes of boot.
$ sudo nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB
1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-14-generic 4.10.0-14.16
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ajclayton 3305 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Fri Mar 31 09:42:38 2017
InstallationDate: Installed on 2012-09-08 (1665 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MachineType: Dell Inc. XPS 15 9550
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt
nouveau.modeset=0 log_buf_len=20M
RelatedPackageVersions:
linux-restricted-modules-4.10.0-14-generic N/A
linux-backports-modules-4.10.0-14-generic N/A
linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
Oh, this is also helpful:
sudo nvme list:
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 385S1046T31Q KXG5AZNV512G TOSHIBA
1 512,11
so obviously this bug occurs for a 512GB Toshiba as well
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678184
Title:
APST quirk needed for Samsung 512GB NVMe drive
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Yakkety:
Fix Released
Status in linux source package in Zesty:
Fix Released
Bug description:
APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
That patch has a quirk for certain 256GB Samsung drives found in Dell
laptops that do not behave well when APST is enabled. I am
experiencing the same symptoms with the same model laptop except with
a 512GB Samsung. Prior to manually disabling APST the drive would die
and system would go down in flames with I/O errors within 20 to 40
minutes of boot.
$ sudo nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB
1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-14-generic 4.10.0-14.16
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ajclayton 3305 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Fri Mar 31 09:42:38 2017
InstallationDate: Installed on 2012-09-08 (1665 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MachineType: Dell Inc. XPS 15 9550
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt
nouveau.modeset=0 log_buf_len=20M
RelatedPackageVersions:
linux-restricted-modules-4.10.0-14-generic N/A
linux-backports-modules-4.10.0-14-generic N/A
linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858584] Re: xenial/linux-kvm: 4.4.0-1065.72 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1858594 + kernel-stable-master-bug: '1859718' packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Friday, 10. January 2020 14:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs ** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1859718' packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Friday, 10. January 2020 14:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1858584 Title: xenial/linux-kvm: 4.4.0-1065.72 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1859718' packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Friday, 10. January 2020 14:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859702] Re: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Holding before Promote to Proposed - phase-changed: Monday, 20. January 2020 09:51 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 20. January 2020 12:56 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,meta:building,signed:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1859702 Title: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Ready for Promote to Proposed phase-changed: Monday, 20. January 2020 12:56 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860119] Re: eoan/linux: 5.3.0-29.31 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:26 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:building + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860119 Title: eoan/linux: 5.3.0-29.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:26 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859702] Re: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Monday, 20. January 2020 09:51 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,meta:queued,signed:queued + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,meta:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1859702 Title: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Monday, 20. January 2020 09:51 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:46 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:46 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859799] Re: xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1859704 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Holding before Promote to Proposed phase-changed: Monday, 20. January 2020 11:47 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859799 Title: xenial/linux-deeplens: 4.15.0-1015.15 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1859704 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Holding before Promote to Proposed phase-changed: Monday, 20. January 2020 11:47 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845823] Re: [radeon] Kubuntu 19.10 System Settings Add-On Installer "Details" text unreadable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemsettings (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/1845823 Title: [radeon] Kubuntu 19.10 System Settings Add-On Installer "Details" text unreadable Status in linux package in Ubuntu: Confirmed Status in systemsettings package in Ubuntu: Confirmed Bug description: 19.10 QA-test 'live' on dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) This was noticed on an fresh install last night (in setup post-install on same box), I had it occur on yesterday's daily ISO and it has occurred with today's daily ISO (see next line). It's probably related to video card; I've seen other corrupted text too, but this is the easist to re-create.. deb cdrom:[Kubuntu 19.10 _Eoan Ermine_ - Beta amd64 (20190928)]/ eoan main multiverse restricted universe Please refer picture - On right display look for mouse pointer; text being displayed "Details" looked corrupted. This issue is really minor, the purpose can be understood in this case, though other times it appeared to be multiple lines of text (12-15 words) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemsettings 4:5.16.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.419 CurrentDesktop: KDE Date: Sun Sep 29 04:09:35 2019 LiveMediaBuild: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190928) SourcePackage: systemsettings UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu4718 F pulseaudio /dev/snd/controlC1: kubuntu4718 F pulseaudio CasperVersion: 1.419 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 IwConfig: lono wireless extensions. enp0s25 no wireless extensions. LiveMediaBuild: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190928) MachineType: Dell Inc. OptiPlex 780 Package: systemsettings 4:5.16.5-0ubuntu1 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed maybe-ubiquity initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 RfKill: Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/13/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0200DY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/13/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0200DY:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:46 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:46 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859702] Re: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Monday, 20. January 2020 09:51 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,meta:queued,signed:queued variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1859702 Title: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Monday, 20. January 2020 09:51 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,meta:queued,signed:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860119] Re: eoan/linux: 5.3.0-29.31 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:26 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Ongoing -- package copied to Proposed signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860119 Title: eoan/linux: 5.3.0-29.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:26 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860144] Re: linux 5.4.0-11 fails to boot on arm64
On a ThunderX2 node, after adding "earlycon debug" to cmdline, i was able to capture this: ... Loading Linux 5.4.0-11-generic ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [0.00] Booting Linux on physical CPU 0x00 [0x431f0af1] [0.00] Linux version 5.4.0-11-generic (buildd@bos02-arm64-077) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16 :16:25 UTC 2020 (Ubuntu 5.4.0-11.14-generic 5.4.8) [0.00] efi: Getting EFI parameters from FDT: [0.00] efi: EFI v2.70 by American Megatrends [0.00] efi: ESRT=0xfd38dc98 SMBIOS=0xfcca SMBIOS 3.0=0xfcc9 ACPI 2.0=0xf9a1 MEMRESERVE=0xfa7f9e98 [0.00] secureboot: Secure boot disabled [0.00] esrt: Reserving ESRT space from 0xfd38dc98 to 0xfd38dcd0. [0.00] cma: Reserved 32 MiB at 0xf000 [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0xF9A1 24 (v02 ALASKA) [0.00] ACPI: XSDT 0xF9A10028 DC (v01 ALASKA A M I 01072009 AMI 00010013) [0.00] ACPI: FACP 0xF9A10108 000114 (v06 ALASKA A M I 01072009 AMI 00010013) [0.00] ACPI: DSDT 0xF9A10220 000714 (v02 CAVM CN99XX 20150406 INTL 20170224) [0.00] ACPI: FIDT 0xF9A10938 9C (v01 ALASKA A M I 01072009 AMI 00010013) [0.00] ACPI: DBG2 0xF9A109D8 62 (v00 CAVM CN99XX INTL 20170224) [0.00] ACPI: SPMI 0xF9A10A40 41 (v05 ALASKA A M I AMI. ) [0.00] ACPI: PCCT 0xF9A10A88 000FB0 (v01 CAVM CN99XX 0001 INTL 20170224) [0.00] ACPI: SLIT 0xF9A11A38 30 (v01 CAVM CN99XX 0001 INTL 20170224) [0.00] ACPI: SPMI 0xF9A11A68 41 (v04 CAVM CN99XX 0001 INTL 20170224) [0.00] ACPI: SSDT 0xF9A11AB0 004217 (v02 CAVM N0BXPCI 20150406 INTL 20170224) [0.00] ACPI: SSDT 0xF9A15CC8 019654 (v02 CAVM N0T128 20150406 INTL 20170224) [0.00] ACPI: SSDT 0xF9A2F320 0041CB (v02 CAVM N1BXPCI 20150406 INTL 20170224) [0.00] ACPI: SSDT 0xF9A334F0 01980C (v02 CAVM N1T128 20150406 INTL 20170224) [0.00] ACPI: BERT 0xF9A4CD00 30 (v01 CAVM CN99XX 20150406 CAVM 0099) [0.00] ACPI: GTDT 0xF9A4CD30 7C (v02 CAVM CN99XX 20150406 CAVM 0099) [0.00] ACPI: HEST 0xF9A4CDB0 000308 (v01 CAVM
[Kernel-packages] [Bug 1859799] Re: xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1859704 packages: main: linux-deeplens meta: linux-meta-deeplens - phase: Packaging - phase-changed: Thursday, 16. January 2020 17:22 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 20. January 2020 11:47 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859799 Title: xenial/linux-deeplens: 4.15.0-1015.15 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1859704 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Holding before Promote to Proposed phase-changed: Monday, 20. January 2020 11:47 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859702] Re: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Monday, 20. January 2020 09:51 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1859702 Title: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Monday, 20. January 2020 09:51 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859154] Re: bionic/linux-gke-5.3: 5.3.0-1011.12~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1856988 packages: main: linux-gke-5.3 meta: linux-meta-gke-5.3 signed: linux-signed-gke-5.3 - phase: Promote to Updates - phase-changed: Monday, 20. January 2020 11:00 UTC + phase: Holding before Promote to Security + phase-changed: Monday, 20. January 2020 11:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- not ready for security (replication dwell) - promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-gke-5.3/gke-kernel: bug 1859153 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859154 Title: bionic/linux-gke-5.3: 5.3.0-1011.12~18.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: Fix Released 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 verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1856988 packages: main: linux-gke-5.3 meta: linux-meta-gke-5.3 signed: linux-signed-gke-5.3 phase: Holding before Promote to Security phase-changed: Monday, 20. January 2020 11:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- not ready for security (replication dwell) trackers: bionic/linux-gke-5.3/gke-kernel: bug 1859153 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:46 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 - xenial/linux-hwe: bug 1860122, bug 1859704 + xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:46 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859797] Re: trusty/linux-azure: 4.15.0-1067.72~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1859798 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:55 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Pending -- package copied to Signing signed:retry-needed variant: debs -- 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/1859797 Title: trusty/linux-azure: 4.15.0-1067.72~14.04.1 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1859798 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:55 UTC reason: promote-to-proposed: Pending -- package copied to Signing signed:retry-needed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859797] Re: trusty/linux-azure: 4.15.0-1067.72~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1859798 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Promote to Proposed - phase-changed: Friday, 17. January 2020 17:29 UTC + phase: Promote to Proposed + phase-changed: Monday, 20. January 2020 10:55 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress variant: debs -- 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/1859797 Title: trusty/linux-azure: 4.15.0-1067.72~14.04.1 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1859798 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:55 UTC reason: promote-to-proposed: Pending -- package copied to Signing signed:retry-needed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859154] Re: bionic/linux-gke-5.3: 5.3.0-1011.12~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859154 Title: bionic/linux-gke-5.3: 5.3.0-1011.12~18.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: In Progress 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 verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1856988 packages: main: linux-gke-5.3 meta: linux-meta-gke-5.3 signed: linux-signed-gke-5.3 phase: Promote to Updates phase-changed: Monday, 20. January 2020 11:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- not ready for security (replication dwell) promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-gke-5.3/gke-kernel: bug 1859153 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859154] Re: bionic/linux-gke-5.3: 5.3.0-1011.12~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1856988 packages: main: linux-gke-5.3 meta: linux-meta-gke-5.3 signed: linux-signed-gke-5.3 - phase: Ready for Promote to Updates - phase-changed: Friday, 17. January 2020 10:46 UTC + phase: Promote to Updates + phase-changed: Monday, 20. January 2020 11:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-security: Holding -- not ready for security (replication dwell) + promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-gke-5.3/gke-kernel: bug 1859153 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859154 Title: bionic/linux-gke-5.3: 5.3.0-1011.12~18.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: In Progress 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 verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1856988 packages: main: linux-gke-5.3 meta: linux-meta-gke-5.3 signed: linux-signed-gke-5.3 phase: Promote to Updates phase-changed: Monday, 20. January 2020 11:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- not ready for security (replication dwell) promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-gke-5.3/gke-kernel: bug 1859153 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860119] Re: eoan/linux: 5.3.0-29.31 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:26 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860119 Title: eoan/linux: 5.3.0-29.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:26 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859797] Re: trusty/linux-azure: 4.15.0-1067.72~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1859797 Title: trusty/linux-azure: 4.15.0-1067.72~14.04.1 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1859798 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:55 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Promote to Proposed - phase-changed: Saturday, 18. January 2020 03:27 UTC + phase: Promote to Proposed + phase-changed: Monday, 20. January 2020 10:46 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-aws: bug 1859795 + bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:46 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859724] Re: disco/linux: 5.0.0-40.44 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 16. January 2020 04:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1858546 bionic/linux-oem-osp1: bug 1859722 disco/linux-aws: bug 1858531 disco/linux-azure: bug 1858534 disco/linux-gcp: bug 1858539 disco/linux-kvm: bug 1858541 disco/linux-oracle: bug 1858543 disco/linux-raspi2: bug 1858529 disco/linux-snapdragon: bug 1858544 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859724 Title: disco/linux: 5.0.0-40.44 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 16. January 2020 04:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1858546 bionic/linux-oem-osp1: bug 1859722 disco/linux-aws: bug 1858531 disco/linux-azure: bug 1858534 disco/linux-gcp: bug 1858539 disco/linux-kvm: bug 1858541 disco/linux-oracle: bug 1858543 disco/linux-raspi2: bug 1858529 disco/linux-snapdragon: bug 1858544 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 20. January 2020 10:46 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
