[Kernel-packages] [Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity
After enabling the HWE stack on my Kubuntu 18.04.3 64bit and upgrade to Kernel 5.0, the bluetooth mouse sleeps after some inactivity. An upgrade to Kubuntu 19.04, Kernel 5.0.0-23-generic, didn't solve the issue. No tlp installed. PowerTOP Good Bluetooth device interface status Any ideas how to disable this bluetooth power saving? Or it's a regression between original Kubuntu 18.04 kernel and 5.0? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801642 Title: Bluetooth mouse sleeps after 5 seconds of inactivity Status in linux package in Ubuntu: Confirmed Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839588] [NEW] Eoan update: v5.2.7 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.2.7 upstream stable release
from git://git.kernel.org/
Linux 5.2.7
Documentation: Add swapgs description to the Spectre v1 documentation
x86/speculation/swapgs: Exclude ATOMs from speculation through SWAPGS
x86/entry/64: Use JMP instead of JMPQ
x86/speculation: Enable Spectre v1 swapgs mitigations
x86/speculation: Prepare entry code for Spectre v1 swapgs mitigations
x86/cpufeatures: Combine word 11 and 12 into a new scattered features word
x86/cpufeatures: Carve out CQM features retrieval
drm/i915/gvt: fix incorrect cache entry for guest page mapping
drm/i915/perf: fix ICL perf register offsets
IB/hfi1: Field not zero-ed when allocating TID flow memory
IB/hfi1: Drop all TID RDMA READ RESP packets after r_next_psn
IB/hfi1: Check for error on call to alloc_rsm_map_table
IB/mlx5: Fix RSS Toeplitz setup to be aligned with the HW specification
IB/mlx5: Fix clean_mr() to work in the expected order
IB/mlx5: Move MRs to a kernel PD when freeing them to the MR cache
IB/mlx5: Use direct mkey destroy command upon UMR unreg failure
IB/mlx5: Fix unreg_umr to ignore the mkey state
RDMA/devices: Do not deadlock during client removal
RDMA/bnxt_re: Honor vlan_id in GID entry comparison
xen/gntdev.c: Replace vm_map_pages() with vm_map_pages_zero()
xen/swiotlb: fix condition for calling xen_destroy_contiguous_region()
nbd: replace kill_bdev() with __invalidate_device() again
scsi: mpt3sas: Use 63-bit DMA addressing on SAS35 HBA
clk: mediatek: mt8183: Register 13MHz clock earlier for clocksource
io_uring: fix KASAN use after free in io_sq_wq_submit_work
arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG,ERG}
arm64: compat: Allow single-byte watchpoints on all addresses
drivers/perf: arm_pmu: Fix failure path in PM notifier
parisc: Fix build of compressed kernel even with debug enabled
parisc: Strip debug info from kernel before creating compressed vmlinuz
parisc: Add archclean Makefile target
cgroup: kselftest: relax fs_spec checks
s390/dasd: fix endless loop after read unit address configuration
loop: Fix mount(2) failure due to race with LOOP_SET_FD
mm/migrate.c: initialize pud_entry in migrate_vma()
ubsan: build ubsan.c more conservatively
mm: compaction: avoid 100% CPU usage during compaction when a task is killed
mm: migrate: fix reference check race between __find_get_block() and migration
mm: vmscan: check if mem cgroup is disabled or not before calling memcg slab
shrinker
ALSA: hda: Fix 1-minute detection delay when i915 module is not available
selinux: fix memory leak in policydb_init()
powerpc/kasan: fix early boot failure on PPC32
i2c: at91: fix clk_offset for sama5d2
i2c: at91: disable TXRDY interrupt after sending data
i2c: iproc: Fix i2c master read more than 63 bytes
eeprom: at24: make spd world-readable again
mtd: rawnand: micron: handle on-die "ECC-off" devices correctly
drm/nouveau: Only release VCPI slots on mode changes
IB/hfi1: Fix Spectre v1 vulnerability
gpiolib: fix incorrect IRQ requesting of an active-low lineevent
gpio: don't WARN() on NULL descs if gpiolib is disabled
gpiolib: Preserve desc->flags when setting state
mmc: mmc_spi: Enable stable writes
mmc: host: sdhci-sprd: Fix the missing pm_runtime_put_noidle()
mmc: meson-mx-sdio: Fix misuse of GENMASK macro
mmc: dw_mmc: Fix occasional hang after tuning on eMMC
fgraph: Remove redundant ftrace_graph_notrace_addr() test
dax: Fix missed wakeup in put_unlocked_entry()
Btrfs: fix race leading to fs corruption after transaction abort
Btrfs: fix incremental send failure after deduplication
tpm: Fix null pointer dereference on chip register error path
kbuild: modpost: include .*.cmd files only when targets exist
kbuild: initialize CLANG_FLAGS correctly in the top Makefile
kconfig: Clear "written" flag to avoid data loss
drm/nouveau/dmem: missing mutex_lock in error path
drm/nouveau: fix memory leak in nouveau_conn_reset()
bpf: Disable GCC -fgcse optimization for ___bpf_prog_run()
x86, boot: Remove multiple copy of static function sanitize_boot_params()
x86/paravirt: Fix callee-saved function ELF sizes
x86/kvm: Don't call kvm_spurious_fault() from .fixup
xen/pv: Fix a boot up hang revealed by int3 self test
crypto: ccp - Fix SEV_VERSION_GREATER_OR_EQUAL
stacktrace: Force USER_DS for stack_trace_save_user()
mm/hotplug: make remove_memory() interface usable
device-dax: fix memory and resource leak if hotplug fails
nds32: fix asm/syscall.h
ipc/mqueue.c: only perform resource calculation if user valid
drivers/rapidio/devices/rio_mport_cdev.c: NUL terminate
[Kernel-packages] [Bug 1839587] [NEW] Eoan update: v5.2.6 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.2.6 upstream stable release from git://git.kernel.org/ Linux 5.2.6 ceph: hold i_ceph_lock when removing caps for freeing inode Fix allyesconfig output. drivers/pps/pps.c: clear offset flags in PPS_SETPARAMS ioctl /proc//cmdline: add back the setproctitle() special case /proc//cmdline: remove all the special cases sched/fair: Use RCU accessors consistently for ->numa_group sched/fair: Don't free p->numa_faults with concurrent readers Bluetooth: hci_uart: check for missing tty operations nvme: fix multipath crash when ANA is deactivated xfrm: policy: fix bydst hlist corruption on hash rebuild media: radio-raremono: change devm_k*alloc to k*alloc NFS: Cleanup if nfs_match_client is interrupted media: pvrusb2: use a different format for warnings media: cpia2_usb: first wake up, then free in disconnect ath10k: Change the warning message string media: au0828: fix null dereference in error path bpf: fix NULL deref in btf_type_is_resolve_source_only ISDN: hfcsusb: checking idx of ep configuration vsock: correct removal of socket from the list ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839587 Title: Eoan update: v5.2.6 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.2.6 upstream stable release from git://git.kernel.org/ Linux 5.2.6 ceph: hold i_ceph_lock when removing caps for freeing inode Fix allyesconfig output. drivers/pps/pps.c: clear offset flags in PPS_SETPARAMS ioctl /proc//cmdline: add back the setproctitle() special case /proc//cmdline: remove all the special cases sched/fair: Use RCU accessors consistently for ->numa_group sched/fair: Don't free p->numa_faults with concurrent readers Bluetooth: hci_uart: check for missing tty operations nvme: fix multipath crash when ANA is deactivated xfrm: policy: fix bydst hlist corruption on hash rebuild media: radio-raremono: change devm_k*alloc to k*alloc NFS: Cleanup if nfs_match_client is interrupted media: pvrusb2: use a different format for warnings media: cpia2_usb: first wake up, then free in disconnect ath10k: Change the warning message string media: au0828: fix null dereference in error path bpf: fix NULL deref in btf_type_is_resolve_source_only ISDN: hfcsusb: checking idx of ep configuration vsock: correct removal of socket from the list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1831995 Title: Bluetooth earphone is connected but disconnected immediately. [Intel 3165] Status in bluez package in Ubuntu: Expired Status in linux-firmware package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: I have erased and reinstalled Pulseaudio. It seems like this can not be done since. I tried the following. sudo apt-get remove alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio I did this again. sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils sudo apt-get install linux-sound-base alsa-base alsa-utils ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Fri Jun 7 20:33:05 2019 InstallationDate: Installed on 2019-04-04 (64 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7559 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.9 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.9 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 58:FB:84:C1:51:50 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:125274 acl:68 sco:0 events:1720 errors:0 TX bytes:15000 acl:64 sco:0 commands:861 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1831995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1831995 Title: Bluetooth earphone is connected but disconnected immediately. [Intel 3165] Status in bluez package in Ubuntu: Expired Status in linux-firmware package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: I have erased and reinstalled Pulseaudio. It seems like this can not be done since. I tried the following. sudo apt-get remove alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio I did this again. sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils sudo apt-get install linux-sound-base alsa-base alsa-utils ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Fri Jun 7 20:33:05 2019 InstallationDate: Installed on 2019-04-04 (64 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7559 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.9 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.9 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 58:FB:84:C1:51:50 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:125274 acl:68 sco:0 events:1720 errors:0 TX bytes:15000 acl:64 sco:0 commands:861 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1831995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]
[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1831995 Title: Bluetooth earphone is connected but disconnected immediately. [Intel 3165] Status in bluez package in Ubuntu: Expired Status in linux-firmware package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: I have erased and reinstalled Pulseaudio. It seems like this can not be done since. I tried the following. sudo apt-get remove alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio I did this again. sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils sudo apt-get install linux-sound-base alsa-base alsa-utils ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Fri Jun 7 20:33:05 2019 InstallationDate: Installed on 2019-04-04 (64 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7559 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.9 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.9 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 58:FB:84:C1:51:50 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:125274 acl:68 sco:0 events:1720 errors:0 TX bytes:15000 acl:64 sco:0 commands:861 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1831995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760013] Re: Problems with Lenovo input devices (keyboard & touchpad)
I confirm, this thing is happening to my Lenovo IP320 PC too. Emacs gives " is undefined" error often. My PC Configuration- Lenovo Ideapad 320 Processor: Core i3 (7th Gen) RAM: 8GB Graphics: Ubuntu 18.04 LTS with Kernel 5.2.7 ( This issues happened with Kernel 4.19.* too ) LightDM with XFCE display manager uname -a output: Linux codemascot-pc 5.2.7-050207-generic #201908061831 SMP Tue Aug 6 18:34:36 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "When my Ubuntu 18.04 is booting..." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760013/+attachment/5281727/+files/photo_2019-08-08_13-05-38.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760013 Title: Problems with Lenovo input devices (keyboard & touchpad) Status in linux package in Ubuntu: Expired Bug description: My Lenovo ideapad 700-15ISK repeatedly outputs the character '^@' about twice per second while in a tty. This interferes with the functionality of the keyboard (the "repeat keys" feature is quickly interrupted and stopped). Though the '^@' does not print in Unity, the effects are the same. I can login to Unity fine, but typing passwords is impossible in a tty. Additionally, enabled Synaptics touchpad features simply don't work, including two-finger scrolling and tap to click. This problem began after upgrading to the first 4.13 kernel. Reverting to kernel 4.11 fixes these issues, and so does installing the mainline kernel (v4.16-rc7). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-37-generic 4.13.0-37.42~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 30 00:20:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-21 (221 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839006] Re: No sound is playing from this laptop
Did you install the timidity? it can't work well with pulseaudio. dpkg --list | grep timidity* sudo dpkg -r timidity sudo dpkg -r timidity-daemon reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_selftests ftrace fails
** Tags added: sru-20190722 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1830084 Title: ubuntu_kernel_selftests ftrace fails Status in ubuntu-kernel-tests: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: New Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: Confirmed Status in linux-gcp source package in Disco: New Bug description: Cloud: Azure Series: Disco Kernel: 5.0.0-1007.7 linux-azure Instance: Standard_D2_v3 and others. 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > /proc/sys/net/ipv4/conf/all/accept_local'' 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done for 'all'. 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13 05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest 05/20 14:24:27 DEBUG| utils:0153| [stdout] 05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal number: 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests === 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file check 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for tracers 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock test 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing check 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the ringbuffer size 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing setting 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and trace_marker 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic event - add/remove kprobe events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic event - add/remove synthetic events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic event - selective clear (compatibility) 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic event - generic clear event 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - enable/disable with event level files 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - restricts events based on pid 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - enable/disable with subsystem level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - enable/disable with top level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [16] Test trace_printk from module 05/20 14:24:36 DEBUG| utils:0153| [stdout] -e [UNRESOLVED] 05/20 14:24:36 DEBUG| utils:0153| [stdout] -e -n [17] ftrace - function graph filters with stack tracer 05/20 14:24:38 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:38 DEBUG| utils:0153| [stdout] -e -n [18] ftrace - function graph f
[Kernel-packages] [Bug 1839352] Re: disco/linux-azure: 5.0.0-1014.14 -proposed tracker
** Tags added: regression-testing-passed -- 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/1839352 Title: disco/linux-azure: 5.0.0-1014.14 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 backports: bug 1839351 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 08. August 2019 18:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1839351 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839072] Re: disco/linux-aws: 5.0.0-1012.13 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839072 Title: disco/linux-aws: 5.0.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 backports: bug 1839070 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 06. August 2019 19:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839070 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839072] Re: disco/linux-aws: 5.0.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => 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 backports: bug 1839070 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 06. August 2019 19:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839070 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839072 Title: disco/linux-aws: 5.0.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 backports: bug 1839070 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 06. August 2019 19:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839070 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839352] Re: disco/linux-azure: 5.0.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => 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 backports: bug 1839351 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 08. August 2019 18:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1839351 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/1839352 Title: disco/linux-azure: 5.0.0-1014.14 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 backports: bug 1839351 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 08. August 2019 18:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1839351 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
"but we probably don't need to try any harder tracking down the history of the Armbian kernel releases here in an Ubuntu bug report..." Agreed, so the following is just out of interest... re kernel versions, sorry for the confusion, it looks like the reboot I did today moved me up another kernel release without me realising, so I was on .111 at the beginning of the day and .113 at the end. No idea what might have been there back when things were working, but as you say, it's not so important. lsb_release -a doesn't mention armbian: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 Codename: xenial But the login message does: ___ _ _ _ __ ___ _ _ _ / _ \ __| |_ __ ___ (_) __| | \ \/ / | | | || | | | | |/ _` | '__/ _ \| |/ _` | \ /| | | | || |_ | |_| | (_| | | | (_) | | (_| | / \| |_| |__ _| \___/ \__,_|_| \___/|_|\__,_| /_/\_\\___/ |_| Welcome to Ubuntu Xenial with Armbian Linux 4.14.133-odroidxu4 And I should probably stop spamming this bug report with irrelevant noise now. It seems like the problem is well understood, it's a shame there isn't a simpler way of choosing between the uas and usb-storage drivers, but at least it can be done. Many thanks for all the help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-1
Re: [Kernel-packages] [Bug 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
On Thu, Aug 08, 2019 at 23:50:14 -, James Kingdon wrote: > Hmm, you've got me curious now. It's been a while since I really looked > at the ARM boards. sources.list.d contains armbian.list which has a > single entry: > > deb http://apt.armbian.com xenial main xenial-utils xenial-desktop > > That seems like a reasonable candidate? I don't recall if I used an Well... I off hand don't see 4.14.111-odroidxu4 on the apt.armbian.com site at the moment (only 5.x packages), but that doesn't prove much about what was there in the past... (But if you are indeed using Armbian ["lsb_release -a" should tell you], then the link to the wiki.odroid.com Ubuntu release notes won't be of any help... seems like /boot/ArmbianEnv.txt may be what you are looking for instead.) > References to odroid in /etc/apt seem to be limited to apt.conf.d > /01autoremove-kernels. That might answer your earlier question about > what the previous kernel level was as it mentions 4.14.111. (In your previous email you said the running kernel version was "4.14.111-odroidxu4", so I think it's mentioned in 01autoremove-kernels simply because it's the currently-installed package version but we probably don't need to try any harder tracking down the history of the Armbian kernel releases here in an Ubuntu bug report... :) ) Nathan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
Having the same issue, Is there a work around while it gets fixed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839097] Re: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0
** Also affects: linux via https://bugs.freedesktop.org/show_bug.cgi?id=111333 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839097 Title: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Purged Open source PPA and problem persists: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 10:54:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (226 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro text resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1839097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839557] Re: Hard Disk Freezing
** Changed in: linux (Ubuntu) Assignee: Henrique Watanabe (henrixwat) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839557 Title: Hard Disk Freezing Status in linux package in Ubuntu: Incomplete Bug description: OS: Linux Mint 19.2 Cinnamon Version: 4.2.3 Kernel 4.15.0-55 Processor: Intel Core i5-4210U CPU @ 1.70GHz x 2 Memory: 3.8 GB Hard disc 316.8 GB Graphic card: Intel Corporation Haswell-ULT Integrated Graphics Controller. Issue Description: When I start the notebook and put the password in login screen and tap enter the computer doesn't responds and freeze the screen, sometimes the OS pass the screen login, but freeze and you cannot control or click anything. After it, I tried to change the version of Kernel to 5.0.0-23 and worked fine again. Please check it! The Kernel version 4.15.0-55 has serious problems with Hard Disc control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
Hmm, you've got me curious now. It's been a while since I really looked at the ARM boards. sources.list.d contains armbian.list which has a single entry: deb http://apt.armbian.com xenial main xenial-utils xenial-desktop That seems like a reasonable candidate? I don't recall if I used an original distro from Odroid or (more likely) went straight for a release from armbian - they were the my favourite when I was building an ARM farm a couple of years ago. References to odroid in /etc/apt seem to be limited to apt.conf.d /01autoremove-kernels. That might answer your earlier question about what the previous kernel level was as it mentions 4.14.111. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Jan 1 16:53:16 2019 InstallationDate: Installed on 2018-02-23 (312 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: smartmontools UpgradeStatus: Upgraded to bionic on 2018-10-21 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810215/+subscriptions
Re: [Kernel-packages] [Bug 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
On Thu, Aug 08, 2019 at 21:59:50 -, James Kingdon wrote: > source.list is using http://ports.ubuntu.com/ Okay, interesting. So I guess most of your install is the armhf architecture packages from ports.ubuntu.com. However, the the kernel you mentioned (4.14.111-odroidxu4) isn't from there; I guess there must be another source.list line pointing to http://deb.odroid.in/5422-s/ or something? (If that is indeed the origin of your kernel packages, it does look like the versons that have been published there do span across the kernel versions were the Seagate NO_ATA_1X patch was introduced) Nathan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Jan 1 16:53:16 2019 InstallationDate: Installed on 2018-02-23 (312 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: smartmontools UpgradeStatus: Upgraded to bionic on 2018-10-21 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810215/+subscriptions
[Kernel-packages] [Bug 1839557] 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 1839557 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/1839557 Title: Hard Disk Freezing Status in linux package in Ubuntu: Incomplete Bug description: OS: Linux Mint 19.2 Cinnamon Version: 4.2.3 Kernel 4.15.0-55 Processor: Intel Core i5-4210U CPU @ 1.70GHz x 2 Memory: 3.8 GB Hard disc 316.8 GB Graphic card: Intel Corporation Haswell-ULT Integrated Graphics Controller. Issue Description: When I start the notebook and put the password in login screen and tap enter the computer doesn't responds and freeze the screen, sometimes the OS pass the screen login, but freeze and you cannot control or click anything. After it, I tried to change the version of Kernel to 5.0.0-23 and worked fine again. Please check it! The Kernel version 4.15.0-55 has serious problems with Hard Disc control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839557] [NEW] Hard Disk Freezing
Public bug reported: OS: Linux Mint 19.2 Cinnamon Version: 4.2.3 Kernel 4.15.0-55 Processor: Intel Core i5-4210U CPU @ 1.70GHz x 2 Memory: 3.8 GB Hard disc 316.8 GB Graphic card: Intel Corporation Haswell-ULT Integrated Graphics Controller. Issue Description: When I start the notebook and put the password in login screen and tap enter the computer doesn't responds and freeze the screen, sometimes the OS pass the screen login, but freeze and you cannot control or click anything. After it, I tried to change the version of Kernel to 5.0.0-23 and worked fine again. Please check it! The Kernel version 4.15.0-55 has serious problems with Hard Disc control. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Henrique Watanabe (henrixwat) Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Henrique Watanabe (henrixwat) ** Description changed: OS: Linux Mint 19.2 Cinnamon Version: 4.2.3 Kernel 4.15.0-55 Processor: Intel Core i5-4210U CPU @ 1.70GHz x 2 Memory: 3.8 GB - Hard disc 316.8 GB + Hard disc 316.8 GB Graphic card: Intel Corporation Haswell-ULT Integrated Graphics Controller. Issue Description: When I start the notebook and put the password in login screen and tap enter the computer doesn't responds and freeze the screen, sometimes the OS pass the screen login, but freeze and you cannot control or click anything. After it, I tried to change the version of Kernel to 5.0.0-23 and worked fine again. Please check it! - The Kernel version 4.15.0-55 has serious problems with Hard Drive + The Kernel version 4.15.0-55 has serious problems with Hard Disc control. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839557 Title: Hard Disk Freezing Status in linux package in Ubuntu: New Bug description: OS: Linux Mint 19.2 Cinnamon Version: 4.2.3 Kernel 4.15.0-55 Processor: Intel Core i5-4210U CPU @ 1.70GHz x 2 Memory: 3.8 GB Hard disc 316.8 GB Graphic card: Intel Corporation Haswell-ULT Integrated Graphics Controller. Issue Description: When I start the notebook and put the password in login screen and tap enter the computer doesn't responds and freeze the screen, sometimes the OS pass the screen login, but freeze and you cannot control or click anything. After it, I tried to change the version of Kernel to 5.0.0-23 and worked fine again. Please check it! The Kernel version 4.15.0-55 has serious problems with Hard Disc control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
** Changed in: xrdp (Ubuntu) Status: In Progress => Fix Committed ** Package changed: xrdp (Ubuntu) => xrdp-hwe-18.04 (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/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xrdp-hwe-18.04 package in Ubuntu: Fix Committed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
Hello Rushi, or anyone else affected, Accepted xrdp-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xrdp- hwe-18.04/0.9.5-2~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed 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/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xrdp-hwe-18.04 package in Ubuntu: Fix Committed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.ven
[Kernel-packages] [Bug 1839286] Re: trusty/linux-azure: 4.15.0-1055.60~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** 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: 1839287 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Proposed - phase-changed: Thursday, 08. August 2019 18:32 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 08. August 2019 22:02 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait + 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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1839286 Title: trusty/linux-azure: 4.15.0-1055.60~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: 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: 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: 1839287 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Thursday, 08. August 2019 22:02 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/1839286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839287] Re: xenial/linux-azure: 4.15.0-1055.60 -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 backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Proposed - phase-changed: Thursday, 08. August 2019 18:31 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 08. August 2019 22:01 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait + promote-to-proposed: Pending -- ready for review trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 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/1839287 Title: xenial/linux-azure: 4.15.0-1055.60 -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: 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: 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 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 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 backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Thursday, 08. August 2019 22:01 UTC reason: promote-to-proposed: Pending -- ready for review trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
source.list is using http://ports.ubuntu.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Jan 1 16:53:16 2019 InstallationDate: Installed on 2018-02-23 (312 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: smartmontools UpgradeStatus: Upgraded to bionic on 2018-10-21 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810215/+subscriptions -- Mailing list: https://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 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
On Thu, Aug 08, 2019 at 18:57:24 -, James Kingdon wrote: > Yes, hdparm -S. Okay, thanks. > Not sure if it's relevant, but the distro is 16.04.6 LTS > (Xenial Xerus) in this case. Okay, yeah, that makes a little more sense. Again, I don't know the timeline on these specific kernels, but in the kernel.org kernel branches the Seagate NO_ATA_1X patch seems to have been applied in Nov/Dec 2017... so I would guess that it was included-from-the-start in the Ubuntu 18.04 kernels, but it would make sense for it to have been newly-added over the lifetime of the 16.04 distribution. (Out of curiousity, what's the path to the package repository given in your /etc/apt/sources.list file? The wiki.odroid.com pages have links for downloading the "install Ubuntu OS" image, but I have't found any information about where the associated package repository is located...) Nathan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Jan 1 16:53:16 2019 InstallationDate: Installed on 2018-02-23 (312 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
** Description changed: [Impact] - * Xenial's ZFS can deadlock in the memory shrinker path -after removing files with extended attributes (xattr). + * Xenial's ZFS can deadlock in the memory shrinker path + after removing files with extended attributes (xattr). - * Extended attributes are enabled by default, but are -_not_ used by default, which reduces the likelyhood. + * Extended attributes are enabled by default, but are + _not_ used by default, which reduces the likelyhood. - * It's very difficult/rare to reproduce this problem, -due to file/xattr/remove/shrinker/lru order/timing -circumstances required. (weeks for a reporter user) -but a synthetic test-case has been found for tests. + * It's very difficult/rare to reproduce this problem, + due to file/xattr/remove/shrinker/lru order/timing + circumstances required. (weeks for a reporter user) + but a synthetic test-case has been found for tests. [Test Case] - * A synthetic reproducer is available for this LP, -with a few steps to touch/setfattr/rm/drop_caches -plus a kernel module to massage the disposal list. + * A synthetic reproducer is available for this LP, + with a few steps to touch/setfattr/rm/drop_caches + plus a kernel module to massage the disposal list. +(comment #8) - * In the original ZFS module: -the xattr dir inode is not purged immediately on -file removal, but possibly purged _two_ shrinker -invocations later. This allows for other thread -started before file remove to call zfs_zget() on -the xattr child inode and iput() it, so it makes -to the same disposal list as the xattr dir inode. + * In the original ZFS module: + the xattr dir inode is not purged immediately on + file removal, but possibly purged _two_ shrinker + invocations later. This allows for other thread + started before file remove to call zfs_zget() on + the xattr child inode and iput() it, so it makes + to the same disposal list as the xattr dir inode. +(comment #3) - * In the modified ZFS module: -the xattr dir inode is purged immediately on file -removal not possibly later on shrinker invocation, -so the problem window above doesn't exist anymore. + * In the modified ZFS module: + the xattr dir inode is purged immediately on file + removal not possibly later on shrinker invocation, + so the problem window above doesn't exist anymore. +(comment #12) [Regression Potential] - * Low. The patches are confined to extended attributes -in ZFS, specifically node removal/purge, and another -change how an xattr child inode tracks its xattr dir -(parent) inode, so that it can be purged immediately -on removal. + * Low. The patches are confined to extended attributes + in ZFS, specifically node removal/purge, and another + change how an xattr child inode tracks its xattr dir + (parent) inode, so that it can be purged immediately + on removal. - * The ZFS test-suite has been run on original/modified -zfs-dkms package/kernel modules, with no regressions. + * The ZFS test-suite has been run on original/modified + zfs-dkms package/kernel modules, with no regressions. +(comment #11) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => Invalid ** Changed in: linux (Ubuntu Disco) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in linux package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Status in zfs-linux source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Invalid Status in linux source package in Disco: Invalid Status in zfs-linux source package in Disco: Invalid Status in linux source package in Eoan: Invalid Status in zfs-linux source package in Eoan: Invalid Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case]
[Kernel-packages] [Bug 1839287] Re: xenial/linux-azure: 4.15.0-1055.60 -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 backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 18:31 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 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/1839287 Title: xenial/linux-azure: 4.15.0-1055.60 -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: 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: 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 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 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 backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 18:31 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839286] Re: trusty/linux-azure: 4.15.0-1055.60~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 -- kernel-stable-master-bug: 1839287 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 18:32 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait 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/1839286 Title: trusty/linux-azure: 4.15.0-1055.60~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: 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: 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 -- kernel-stable-master-bug: 1839287 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 18:32 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
Eoan image uses Linux 5.2: http://cdimages.ubuntu.com/daily-live/pending/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Confirmed Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839395] Re: Regressions in CMA allocation rework
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839395 Title: Regressions in CMA allocation rework Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: In Progress Bug description: Introduced by the fixes for bug 1823753. [Impact] Crashes (as observed on a nigrogen8m device), and a potential memory leak. [Test Case] Regression tested only. [Fix] f46cc0152501e dma-contiguous: page-align the size in dma_free_contiguous() c6622a425acd1 dma-contiguous: do not overwrite align in dma_alloc_contiguous() [Regression Risk] Bugs in CMA code could lead to device driver errors/crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
Yes, hdparm -S. Not sure if it's relevant, but the distro is 16.04.6 LTS (Xenial Xerus) in this case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Jan 1 16:53:16 2019 InstallationDate: Installed on 2018-02-23 (312 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: smartmontools UpgradeStatus: Upgraded to bionic on 2018-10-21 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839286] Re: trusty/linux-azure: 4.15.0-1055.60~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 -- kernel-stable-master-bug: 1839287 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 18:32 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait 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/1839286 Title: trusty/linux-azure: 4.15.0-1055.60~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: 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: 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 -- kernel-stable-master-bug: 1839287 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 18:32 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839287] Re: xenial/linux-azure: 4.15.0-1055.60 -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 backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 18:31 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 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/1839287 Title: xenial/linux-azure: 4.15.0-1055.60 -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: 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: 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 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 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 backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 18:31 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839287/+subscriptions -- Mailing list: https://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 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools) works on kernel 4.13 but not on 4.15
On Thu, Aug 08, 2019 at 18:05:55 -, James Kingdon wrote: > I'm not sure what kernel was there before. I was expecting to see traces > in /boot but the only references are to 4.14.133. (Weird. I'm not familiar with the kernels for odroid, but off hand I'd be suprised if the Seagate-blacklisting behavior would have changed between this kernel version and previous ones within the Ubuntu 18.04 release I wonder if the full explanation is even more complex, e.g. that actually hdparm was failing in the previous kernel versions too, but the power-saving settings on the drives in the enclosures was retained from before... until you lost power and the drives did a fresh restart -- or something.) > Yes, the drives are Seagate 4TB ones, ID 0bc2:331a [...] > I came to this page in a typically long and circuitous fashion after I > noticed that the external drivers weren't spinning down anymore and > discovering that hdparm wasn't working. Basic file IO was still ok. Okay, yes, definitely the NO_ATA_1X problem. Ah, were you using the "hdparm -B" or "-S" options (or the corresponding apm=/spindown_time= settings in the Ubuntu package's hdparm.conf file) to set the spin-down behavior? That's another use case affected by the kernel's current NO_ATA_1X situation Nathan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-1 ProcVersionSignature: Ubunt
[Kernel-packages] [Bug 1839351] Re: bionic/linux-azure: 5.0.0-1014.14~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** 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 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-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/prepare-package-meta Status: Confirmed => In Progress ** 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 ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/promote-to-proposed 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 derivatives: bug 1839075 (linux-azure-edge), bug 1839350 (azure-kernel) -- swm properties -- kernel-stable-master-bug: 1839352 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Packaging - phase-changed: Wednesday, 07. August 2019 16:29 UTC + phase: Testing + phase-changed: Thursday, 08. August 2019 18:35 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - prepare-package: Holding -- waiting for master bug + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1839075 bionic/linux-azure/azure-kernel: bug 1839350 variant: debs ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released -- 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/1839351 Title: bionic/linux-azure: 5.0.0-1014.14~18.04.1 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug 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: h
[Kernel-packages] [Bug 1839287] Re: xenial/linux-azure: 4.15.0-1055.60 -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 ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed 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 backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Thursday, 08. August 2019 17:50 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 08. August 2019 18:31 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 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/1839287 Title: xenial/linux-azure: 4.15.0-1055.60 -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: 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: 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 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 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 backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 18:31 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839352] Re: disco/linux-azure: 5.0.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** 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 Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** 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 ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-disco ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/stakeholder-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/promote-to-proposed 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 backports: bug 1839351 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Thursday, 08. August 2019 07:00 UTC + phase: Testing + phase-changed: Thursday, 08. August 2019 18:35 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1839351 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/1839352 Title: disco/linux-azure: 5.0.0-1014.14 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 backports: bug 1839351 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 08. August 2019 18:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing:
[Kernel-packages] [Bug 1839286] Re: trusty/linux-azure: 4.15.0-1055.60~14.04.1 -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 ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed 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: 1839287 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Thursday, 08. August 2019 18:15 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 08. August 2019 18:32 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:depwait 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/1839286 Title: trusty/linux-azure: 4.15.0-1055.60~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: 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: 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 -- kernel-stable-master-bug: 1839287 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 18:32 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839351] Re: bionic/linux-azure: 5.0.0-1014.14~18.04.1 -proposed tracker
** Summary changed: - bionic/linux-azure: -proposed tracker + bionic/linux-azure: 5.0.0-1014.14~18.04.1 -proposed tracker -- 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/1839351 Title: bionic/linux-azure: 5.0.0-1014.14~18.04.1 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug 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 derivatives: bug 1839075 (linux-azure-edge), bug 1839350 (azure- kernel) -- swm properties -- kernel-stable-master-bug: 1839352 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 08. August 2019 18:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1839075 bionic/linux-azure/azure-kernel: bug 1839350 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839352] Re: disco/linux-azure: 5.0.0-1014.14 -proposed tracker
** Summary changed: - disco/linux-azure: 5.0.0-1015.15 -proposed tracker + disco/linux-azure: 5.0.0-1014.14 -proposed tracker -- 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/1839352 Title: disco/linux-azure: 5.0.0-1014.14 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 backports: bug 1839351 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 08. August 2019 18:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1839351 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
** Summary changed: - for Seagate USB drive enclosures, SAT (e.g. smartmontools) works on kernel 4.13 but not on 4.15 + for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Jan 1 16:53:16 2019 InstallationDate: Installed on 2018-02-23 (312 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: smartmontools UpgradeStatus: Upgraded to bionic on 2018-10-21 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839286] Re: trusty/linux-azure: 4.15.0-1055.60~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** 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: 1839287 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Packaging - phase-changed: Wednesday, 07. August 2019 09:00 UTC + phase: Packaging + phase-changed: Thursday, 08. August 2019 18:15 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded 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/1839286 Title: trusty/linux-azure: 4.15.0-1055.60~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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New 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: 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 -- kernel-stable-master-bug: 1839287 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Thursday, 08. August 2019 18:15 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839286] Re: trusty/linux-azure: 4.15.0-1055.60~14.04.1 -proposed tracker
** Summary changed: - trusty/linux-azure: -proposed tracker + trusty/linux-azure: 4.15.0-1055.60~14.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) -- 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/1839286 Title: trusty/linux-azure: 4.15.0-1055.60~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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New 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: 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 -- kernel-stable-master-bug: 1839287 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Thursday, 08. August 2019 18:15 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools) works on kernel 4.13 but not on 4.15
Hi Nathan, thanks for the reply. I'm not sure what kernel was there before. I was expecting to see traces in /boot but the only references are to 4.14.133. Yes, the drives are Seagate 4TB ones, ID 0bc2:331a Thanks for the link to the known issues. I was looking at boot.ini so it seems I was heading in the right direction. I'm not sure if the copy I can see in /boot is active during the boot process or not, or if I need some additional steps to make that happen. I'm sure I can dig that out with the help of Google. I came to this page in a typically long and circuitous fashion after I noticed that the external drivers weren't spinning down anymore and discovering that hdparm wasn't working. Basic file IO was still ok. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Jan 1 16:53:16 2019 InstallationDate: Installed on 2018-02-23 (312 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: smartmontools UpgradeStatus: Upgraded to bionic on 2018-10-21 (72 days ago) To manage notifications about this bug go to: https://b
[Kernel-packages] [Bug 1839287] Re: xenial/linux-azure: 4.15.0-1055.60 -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 backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Packaging - phase-changed: Wednesday, 07. August 2019 09:48 UTC + phase: Packaging + phase-changed: Thursday, 08. August 2019 17:50 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 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/1839287 Title: xenial/linux-azure: 4.15.0-1055.60 -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: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 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 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 backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Thursday, 08. August 2019 17:50 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-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 derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Promote to Proposed - phase-changed: Thursday, 08. August 2019 13:25 UTC + phase: Testing + phase-changed: Thursday, 08. August 2019 17:41 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 + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug 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 derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 08. August 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839278] Re: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-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 kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Promote to Proposed - phase-changed: Thursday, 08. August 2019 15:30 UTC + phase: Testing + phase-changed: Thursday, 08. August 2019 17:41 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 + 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1839278 Title: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Thursday, 08. August 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-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/1839278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839287] Re: xenial/linux-azure: 4.15.0-1055.60 -proposed tracker
** Summary changed: - xenial/linux-azure: -proposed tracker + xenial/linux-azure: 4.15.0-1055.60 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) -- 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/1839287 Title: xenial/linux-azure: 4.15.0-1055.60 -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: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 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 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 backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Thursday, 08. August 2019 17:50 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839504] Re: [ICL-Graphics] Black screen at desktop on kernel for ICL
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1839504 Title: [ICL-Graphics] Black screen at desktop on kernel for ICL Status in intel: Fix Committed Status in linux package in Ubuntu: Confirmed Bug description: Description: Recent 5.2 kernels showing black screen after logging into ICL machine. Commit which introduce this issue: Author: Ville Syrjälä drm/i915: Make sure we have enough memory bandwidth on ICL ICL has so many planes that it can easily exceed the maximum effective memory bandwidth of the system. We must therefore check that we don't exceed that limit ... Commit fix this issue commit 56e9371bc3f3e7d6c1a197a45d550b2ce6af25f6 Author: Ville Syrjälä Date: Thu Jun 6 15:42:10 2019 +0300 drm/i915: Deal with machines that expose less than three QGV points Target Kernel: 5.3 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1839504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838993] Re: Suspend immediately resumes on Ubuntu 18.04.2
I was searching why suspend is not working anymore with 5.0.0-23 for me and found this similar bug. Sometimes it is coming up again after trying, sometimes it freezes. I tried the echo cmd from #20, no difference for me. But with 4.15.0-55-generic it works for me (unlike the initial report if i understood it correctly) I have a Lenovo P52, let me know if you also want a full report. root@p52:~# lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 dmesg from 5.0.0-23 [ 47.473308] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by cc:50:0a:d0:d6:fb [ 104.073889] PM: suspend entry (deep) [ 104.073890] PM: Syncing filesystems ... done. [ 104.075845] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 104.077853] OOM killer disabled. [ 104.077854] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 104.079091] printk: Suspending console(s) (use no_console_suspend to debug) [ 104.141272] wlan0: deauthenticating from cc:50:0a:d0:d6:fb by local choice (Reason: 3=DEAUTH_LEAVING) [ 104.247354] e1000e: EEE TX LPI TIMER: 0011 [ 105.341267] ACPI: EC: interrupt blocked [ 105.445688] ACPI: Preparing to enter system sleep state S3 [ 105.452756] ACPI: EC: event blocked [ 105.452756] ACPI: EC: EC stopped [ 105.452756] PM: Saving platform NVS memory [ 105.452765] Disabling non-boot CPUs ... [ 105.453144] IRQ 159: no longer affine to CPU1 [ 105.454355] smpboot: CPU 1 is now offline [ 105.456008] IRQ 160: no longer affine to CPU2 [ 105.457025] smpboot: CPU 2 is now offline [ 105.458731] IRQ 161: no longer affine to CPU3 [ 105.459738] smpboot: CPU 3 is now offline [ 105.461542] IRQ 162: no longer affine to CPU4 [ 105.462768] smpboot: CPU 4 is now offline [ 105.464477] IRQ 163: no longer affine to CPU5 [ 105.465489] smpboot: CPU 5 is now offline [ 105.467258] IRQ 164: no longer affine to CPU6 [ 105.468471] smpboot: CPU 6 is now offline [ 105.470184] IRQ 165: no longer affine to CPU7 [ 105.471187] smpboot: CPU 7 is now offline [ 105.472915] IRQ 166: no longer affine to CPU8 [ 105.473935] smpboot: CPU 8 is now offline [ 105.475767] IRQ 167: no longer affine to CPU9 [ 105.476770] smpboot: CPU 9 is now offline [ 105.478440] IRQ 168: no longer affine to CPU10 [ 105.479445] smpboot: CPU 10 is now offline [ 105.482139] smpboot: CPU 11 is now offline [ 105.485910] ACPI: Low-level resume complete [ 105.485985] ACPI: EC: EC started [ 105.485985] PM: Restoring platform NVS memory [ 105.495359] Enabling non-boot CPUs ... [ 105.495412] x86: Booting SMP configuration: [ 105.495413] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 105.497144] cache: parent cpu1 should not be sleeping [ 105.497169] intel_pstate: Disabling energy efficiency optimization [ 105.497268] CPU1 is up [ 105.497285] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 105.497670] cache: parent cpu2 should not be sleeping [ 105.497804] CPU2 is up [ 105.497819] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 105.498188] cache: parent cpu3 should not be sleeping [ 105.498336] CPU3 is up [ 105.498351] smpboot: Booting Node 0 Processor 4 APIC 0x8 [ 105.498720] cache: parent cpu4 should not be sleeping [ 105.498874] CPU4 is up [ 105.498890] smpboot: Booting Node 0 Processor 5 APIC 0xa [ 105.499257] cache: parent cpu5 should not be sleeping [ 105.499425] CPU5 is up [ 105.499441] smpboot: Booting Node 0 Processor 6 APIC 0x1 [ 105.499868] cache: parent cpu6 should not be sleeping [ 105.500155] CPU6 is up [ 105.500174] smpboot: Booting Node 0 Processor 7 APIC 0x3 [ 105.500540] cache: parent cpu7 should not be sleeping [ 105.500730] CPU7 is up [ 105.500746] smpboot: Booting Node 0 Processor 8 APIC 0x5 [ 105.50] cache: parent cpu8 should not be sleeping [ 105.501312] CPU8 is up [ 105.501328] smpboot: Booting Node 0 Processor 9 APIC 0x7 [ 105.501697] cache: parent cpu9 should not be sleeping [ 105.501905] CPU9 is up [ 105.501921] smpboot: Booting Node 0 Processor 10 APIC 0x9 [ 105.502292] cache: parent cpu10 should not be sleeping [ 105.502524] CPU10 is up [ 105.502539] smpboot: Booting Node 0 Processor 11 APIC 0xb [ 105.502917] cache: parent cpu11 should not be sleeping [ 105.503154] CPU11 is up [ 105.511334] ACPI: Waking up from system sleep state S3 [ 105.527650] ACPI: EC: interrupt unblocked [ 105.618664] pci_raw_set_power_state: 30 callbacks suppressed [ 105.618667] snd_hda_intel :01:00.1: Refused to change power state, currently in D3 [ 105.685231] ACPI: EC: event unblocked [ 105.689793] ACPI: button: The lid device is not compliant to SW_LID. [ 105.877119] iwlwifi :00:14.3: BIOS contains WGDS but no WRDS [ 105.890388] e1000e :00:1f.6 eth0: Hardware Error [ 105.942740] nvme nvme0: Shutdown timeout set to 8 seconds [ 105.945489] nvme nvme1: Shutdown timeout set to 8 seconds [ 105.957273] nvme nvme0: 12/0/0 default/read/poll queues [ 105.960186] nvme nvme1: 12/0/0 default/read/poll queues [ 106.9463
[Kernel-packages] [Bug 1839072] Re: disco/linux-aws: 5.0.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** 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 backports: bug 1839070 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 06. August 2019 19:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839070 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839072 Title: disco/linux-aws: 5.0.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 backports: bug 1839070 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 06. August 2019 19:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839070 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
Fix Change Details -- (Compare with comment #3) The xattr dir/child inodes are evicted/disposed immediately on file removal, not on shrinker. $ touch /zfs/file <...>-23940 [006] d... 10808.746798: p_zfs_mknode_0: (zfs_mknode+0x0/0xe00 [zfs]) flag=0x0 dzp=0x88011aa94400 <...>-23940 [006] d... 10808.746925: p_zfs_znode_alloc_0: (zfs_znode_alloc+0x0/0x520 [zfs]) obj=0xa <...>-23940 [006] d... 10808.746938: r_zfs_znode_alloc_0: (zfs_mknode+0x8a3/0xe00 [zfs] <- zfs_znode_alloc) zpp=0x88011aa90880 $ setfattr -n user.debug -v 1 /zfs/file <...>-23941 [006] d... 10818.945733: p_zfs_mknode_0: (zfs_mknode+0x0/0xe00 [zfs]) flag=0x2 dzp=0x88011aa90880 <...>-23941 [006] d... 10818.945892: p_zfs_znode_alloc_0: (zfs_znode_alloc+0x0/0x520 [zfs]) obj=0xb <...>-23941 [006] d... 10818.945905: r_zfs_znode_alloc_0: (zfs_mknode+0x8a3/0xe00 [zfs] <- zfs_znode_alloc) zpp=0x88011aa961c0 <...>-23941 [006] d... 10818.945925: p_zfs_zget_0: (zfs_zget+0x0/0x230 [zfs]) zsb=0x880016f0 obj=0xa setfattr-23941 [006] d... 10818.945929: r_zfs_zget_0: (zfs_zaccess+0x12b/0x220 [zfs] <- zfs_zget) setfattr-23941 [006] d... 10818.945933: p_zfs_zget_0: (zfs_zget+0x0/0x230 [zfs]) zsb=0x880016f0 obj=0xa setfattr-23941 [006] d... 10818.945936: r_zfs_zget_0: (zfs_zaccess+0x12b/0x220 [zfs] <- zfs_zget) setfattr-23941 [006] d... 10818.945948: p_zfs_zget_0: (zfs_zget+0x0/0x230 [zfs]) zsb=0x880016f0 obj=0xa setfattr-23941 [006] d... 10818.945951: r_zfs_zget_0: (zfs_zaccess+0x12b/0x220 [zfs] <- zfs_zget) setfattr-23941 [006] d... 10818.945966: p_zfs_mknode_0: (zfs_mknode+0x0/0xe00 [zfs]) flag=0x0 dzp=0x88011aa961c0 setfattr-23941 [006] d... 10818.945990: p_zfs_znode_alloc_0: (zfs_znode_alloc+0x0/0x520 [zfs]) obj=0xc setfattr-23941 [006] d... 10818.945996: r_zfs_znode_alloc_0: (zfs_mknode+0x8a3/0xe00 [zfs] <- zfs_znode_alloc) zpp=0x88011aa90440 $ rm /zfs/file <...>-23942 [006] d... 10822.453456: p_zfs_zget_0: (zfs_zget+0x0/0x230 [zfs]) zsb=0x880016f0 obj=0xa <...>-23942 [006] d... 10822.453469: r_zfs_zget_0: (zfs_dirent_lock+0x56c/0x6c0 [zfs] <- zfs_zget) rm-23942 [006] d... 10822.453494: p_zfs_zget_0: (zfs_zget+0x0/0x230 [zfs]) zsb=0x880016f0 obj=0xb rm-23942 [006] d... 10822.453498: r_zfs_zget_0: (zfs_remove+0x22b/0x4c0 [zfs] <- zfs_zget) rm-23942 [006] d... 10822.453597: p_zpl_evict_inode_0: (zpl_evict_inode+0x0/0x60 [zfs]) inode=0x88011aa90a90 rm-23942 [006] d... 10822.453602: p_zfs_inactive_0: (zfs_inactive+0x0/0x270 [zfs]) inode=0x88011aa90a90 rm-23942 [006] d... 10822.453603: p_zfs_zinactive_0: (zfs_zinactive+0x0/0xe0 [zfs]) znode=0x88011aa90880 obj=0xa rm-23942 [006] d... 10822.453607: p_zfs_rmnode_0: (zfs_rmnode+0x0/0x360 [zfs]) znode=0x88011aa90880 rm-23942 [006] d... 10822.453619: p_zfs_zget_0: (zfs_zget+0x0/0x230 [zfs]) zsb=0x880016f0 obj=0xb rm-23942 [006] d... 10822.453623: r_zfs_zget_0: (zfs_rmnode+0x25b/0x360 [zfs] <- zfs_zget) rm-23942 [006] d... 10822.453656: p_zfs_iput_async_0: (zfs_iput_async+0x0/0x60 [zfs]) inode=0x88011aa963d0 obj=0x0 z_iput-23904 [006] d... 10822.453675: p_zpl_evict_inode_0: (zpl_evict_inode+0x0/0x60 [zfs]) inode=0x88011aa963d0 z_iput-23904 [006] d... 10822.453676: p_zfs_inactive_0: (zfs_inactive+0x0/0x270 [zfs]) inode=0x88011aa963d0 z_iput-23904 [006] d... 10822.453677: p_zfs_zinactive_0: (zfs_zinactive+0x0/0xe0 [zfs]) znode=0x88011aa961c0 obj=0xb z_iput-23904 [006] d... 10822.453679: p_zfs_rmnode_0: (zfs_rmnode+0x0/0x360 [zfs]) znode=0x88011aa961c0 z_iput-23904 [006] d... 10822.453681: p_zfs_purgedir_0: (zfs_purgedir+0x0/0x230 [zfs]) znode=0x88011aa961c0 z_iput-23904 [006] d... 10822.453686: p_zfs_zget_0: (zfs_zget+0x0/0x230 [zfs]) zsb=0x880016f0 obj=0xc z_iput-23904 [006] d... 10822.453690: r_zfs_zget_0: (zfs_purgedir+0xb4/0x230 [zfs] <- zfs_zget) z_iput-23904 [006] d... 10822.453713: p_zfs_iput_async_0: (zfs_iput_async+0x0/0x60 [zfs]) inode=0x88011aa90650 obj=0x0 z_iput-23904 [006] d... 10822.453719: r_zfs_purgedir_0: (zfs_rmnode+0x272/0x360 [zfs] <- zfs_purgedir) z_iput-23904 [006] d... 10822.453755: p_zpl_evict_inode_0: (zpl_evict_inode+0x0/0x60 [zfs]) inode=0x88011aa90650 z_iput-23904 [006] d... 10822.453756: p_zfs_inactive_0: (zfs_inactive+0x0/0x270 [zfs]) inode=0x88011aa90650 z_iput-23904 [006] d... 10822.453757: p_zfs_zinactive_0: (zfs_zinactive+0x0/0xe0 [zfs]) znode=0x88011aa90440 obj=0xc z_iput-23904 [006] d... 10822.453759: p_zfs_rmnode_0: (zfs_rmnode+0x0/0x360 [zfs]) znode=0x88011aa90440 $ echo 2
[Kernel-packages] [Bug 1839280] Re: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-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 backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Promote to Proposed - phase-changed: Thursday, 08. August 2019 13:10 UTC + phase: Testing + phase-changed: Thursday, 08. August 2019 17:28 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 + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1839278 variant: debs -- 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/1839280 Title: bionic/linux-oracle: 4.15.0-1021.23 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Thursday, 08. August 2019 17:28 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1839278 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839272] Re: bionic/linux-gcp: 4.15.0-1040.42 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-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 backports: bug 1839270 (xenial/linux-gcp) derivatives: bug 1839267 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Promote to Proposed - phase-changed: Thursday, 08. August 2019 12:35 UTC + phase: Testing + phase-changed: Thursday, 08. August 2019 17:27 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 + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1839267 xenial/linux-gcp: bug 1839270 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839272 Title: bionic/linux-gcp: 4.15.0-1040.42 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug 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 backports: bug 1839270 (xenial/linux-gcp) derivatives: bug 1839267 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 08. August 2019 17:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-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-gcp/gcp-kernel: bug 1839267 xenial/linux-gcp: bug 1839270 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839261] Re: bionic/linux-oem: 4.15.0-1050.57 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-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 kernel-stable-master-bug: 1839293 packages: main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Promote to Proposed - phase-changed: Thursday, 08. August 2019 12:25 UTC + phase: Testing + phase-changed: Thursday, 08. August 2019 17:26 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1839261 Title: bionic/linux-oem: 4.15.0-1050.57 -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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug 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: 1839293 packages: main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 08. August 2019 17:26 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/1839261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
zfs-test results w/ original & modified zfs-dkms
original
$ uname -rv
4.4.0-159-generic #187-Ubuntu SMP Thu Aug 1 16:28:06 UTC 2019
$ modinfo zfs | head
filename: /lib/modules/4.4.0-159-generic/updates/dkms/zfs.ko
version:0.6.5.6-0ubuntu27
...
srcversion: 0968F94158D646E259D86B5
...
$ /usr/share/zfs/zfs-tests.sh -r $TMP_RUN_FILE 2>&1 | tee zfs-tests.log
.orig-kernel.orig-dkms
modified
$ uname -rv
4.4.0-159-generic #187-Ubuntu SMP Thu Aug 1 16:28:06 UTC 2019
$ modinfo zfs | head
filename: /lib/modules/4.4.0-159-generic/updates/dkms/zfs.ko
version:0.6.5.6-0ubuntu28
...
srcversion: 99F1D0FED2F291CA7AED0C6
...
$ /usr/share/zfs/zfs-tests.sh -r $TMP_RUN_FILE 2>&1 | tee zfs-tests.log
.orig-kernel.test-dkms
Results Comparison
--
Filter test name and result only.
$ awk '/^Test:/ { print $2, $7 }' zfs-tests.log.orig-kernel.orig-dkms >
zfs-tests.log.orig-kernel.orig-dkms.awk
$ awk '/^Test:/ { print $2, $7 }' zfs-tests.log.orig-kernel.test-dkms >
zfs-tests.log.orig-kernel.test-dkms.awk
Example:
$ head -n3 zfs-tests.log.orig-kernel.orig-dkms.awk
/usr/share/zfs/zfs-tests/tests/functional/acl/posix/setup [PASS]
/usr/share/zfs/zfs-tests/tests/functional/acl/posix/posix_001_pos [PASS]
/usr/share/zfs/zfs-tests/tests/functional/acl/posix/posix_002_pos [PASS]
No differences/regressions between original zfs-dkms and modified zfs-
dkms.
$ diff zfs-tests.log.orig-kernel.{orig,test}-dkms.awk
$
$ grep -A3 Summary zfs-tests.log.orig-kernel.orig-dkms
Results Summary
FAIL 463
PASS 739
SKIP 184
$ grep -A3 Summary zfs-tests.log.orig-kernel.test-dkms
Results Summary
SKIP 184
PASS 739
FAIL 463
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1839521
Title:
Xenial: ZFS deadlock in shrinker path with xattrs
Status in zfs-linux package in Ubuntu:
Invalid
Status in zfs-linux source package in Xenial:
In Progress
Status in zfs-linux source package in Bionic:
Invalid
Status in zfs-linux source package in Disco:
Invalid
Status in zfs-linux source package in Eoan:
Invalid
Bug description:
[Impact]
* Xenial's ZFS can deadlock in the memory shrinker path
after removing files with extended attributes (xattr).
* Extended attributes are enabled by default, but are
_not_ used by default, which reduces the likelyhood.
* It's very difficult/rare to reproduce this problem,
due to file/xattr/remove/shrinker/lru order/timing
circumstances required. (weeks for a reporter user)
but a synthetic test-case has been found for tests.
[Test Case]
* A synthetic reproducer is available for this LP,
with a few steps to touch/setfattr/rm/drop_caches
plus a kernel module to massage the disposal list.
* In the original ZFS module:
the xattr dir inode is not purged immediately on
file removal, but possibly purged _two_ shrinker
invocations later. This allows for other thread
started before file remove to call zfs_zget() on
the xattr child inode and iput() it, so it makes
to the same disposal list as the xattr dir inode.
* In the modified ZFS module:
the xattr dir inode is purged immediately on file
removal not possibly later on shrinker invocation,
so the problem window above doesn't exist anymore.
[Regression Potential]
* Low. The patches are confined to extended attributes
in ZFS, specifically node removal/purge, and another
change how an xattr child inode tracks its xattr dir
(parent) inode, so that it can be purged immediately
on removal.
* The ZFS test-suite has been run on original/modified
zfs-dkms package/kernel modules, with no regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
zfs-test test suite on xenial - Build/install the latest zfs-test suite from zfs.git: $ git clone https://github.com/zfsonlinux/zfs.git $ cd zfs $ git log --oneline -1 c81f179 Metaslab max_size should be persisted while unloaded $ sudo apt-get build-dep zfs-linux $ sudo apt-get install libssl-dev alien libpython3-dev python3-setuptools python3-cffi $ ./autogen.sh $ ./configure $ make -j$(nproc) pkg-utils $ sudo dpkg -i zfs-test_0.8.0-170_amd64.deb $ /usr/share/zfs/zfs-tests.sh # hit kernel errors in the tests below, removed them from 'linux.run' mixed_create_failure [ 390.511557] VERIFY(!RW_LOCK_HELD(&l->l_rwlock)) failed [ 390.516303] PANIC at zap.c:395:zap_leaf_pageout() zfs_clone_deeply_nested << too. very long stack traces detected in scheduler. zfs_upgrade_007_neg << hung tasks. shows twice in the file?! [ 1715.988411] VERIFY3(newds == os->os_dsl_dataset) failed (8800b4e2a000 == 880064b83000) [ 1715.995255] PANIC at dmu_objset.c:618:dmu_objset_refresh_ownership() zpool_create_024_pos [ 572.926873] BUG: unable to handle kernel NULL pointer dereference at (null) import_cachefile_device_added [ 524.079638] PANIC: blkptr at 88009e9f8048 DVA 1 has invalid VDEV 1 zpool_upgrade_007_pos (not zfs_upgrade_007_neg above) [ 480.801356] VERIFY3(newds == os->os_dsl_dataset) failed (880203a98000 == 880203f75000) [ 480.808916] PANIC at dmu_objset.c:618:dmu_objset_refresh_ownership() enospc_003_pos [ 1201.448045] INFO: task txg_sync:1353 blocked for more than 120 seconds. [ 1201.456365] Tainted: P OE 4.4.0-159-generic #187-Ubuntu [ 1201.459650] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1201.464831] INFO: task file_write:1385 blocked for more than 120 seconds. [ 1201.468134] Tainted: P OE 4.4.0-159-generic #187-Ubuntu [ 1201.471387] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. RUN_FILE="/usr/share/zfs/runfiles/linux.run" TMP_RUN_FILE="/tmp/$(basename $RUN_FILE)" cp $RUN_FILE $TMP_RUN_FILE for TEST in \ mixed_create_failure \ zfs_clone_deeply_nested \ zfs_upgrade_007_neg \ zpool_create_024_pos \ import_cachefile_device_added \ zpool_upgrade_007_pos \ enospc_003_pos do sed \ -e "s:'$TEST',::" \ -e "s:\( ,\)\?'$TEST'::" \ -i $TMP_RUN_FILE done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Xenial: In Progress Status in zfs-linux source package in Bionic: Invalid Status in zfs-linux source package in Disco: Invalid Status in zfs-linux source package in Eoan: Invalid Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. To mana
[Kernel-packages] [Bug 1839521] [NEW] Xenial: ZFS deadlock in shrinker path with xattrs
Public bug reported: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: zfs-linux (Ubuntu Xenial) Importance: Undecided Assignee: Mauricio Faria de Oliveira (mfo) Status: In Progress ** Affects: zfs-linux (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Affects: zfs-linux (Ubuntu Disco) Importance: Undecided Status: Invalid ** Affects: zfs-linux (Ubuntu Eoan) Importance: Undecided Status: Invalid ** Also affects: zfs-linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu Eoan) Status: New => Invalid ** Changed in: zfs-linux (Ubuntu Disco) Status: New => Invalid ** Changed in: zfs-linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: zfs-linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: zfs-linux (Ubuntu Xenial) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Xenial: In Progress Status in zfs-linux source package in Bionic: Invalid Status in zfs-linux source package in Disco: Invalid Status in zfs-linux source package in Eoan: Invalid Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. To manage notifications about this bug go to: https://bug
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
** Attachment added: "zfs-kprobes.sh" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+attachment/5281633/+files/zfs-kprobes.sh ** Attachment removed: "kmod-zget.c" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+attachment/5281631/+files/kmod-zget.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Xenial: In Progress Status in zfs-linux source package in Bionic: Invalid Status in zfs-linux source package in Disco: Invalid Status in zfs-linux source package in Eoan: Invalid Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
Test-case for the problem (kmod-zget.c). Header comments with steps to reproduce. ** Attachment added: "kmod-zget.c" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+attachment/5281631/+files/kmod-zget.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Xenial: In Progress Status in zfs-linux source package in Bionic: Invalid Status in zfs-linux source package in Disco: Invalid Status in zfs-linux source package in Eoan: Invalid Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
debdiff for zfs-linux (zfs-linux_shrinker-deadlock-xattr.debdiff) based on ubuntu/xenial-devel branch from LP source pkg git repo [1]. [1] https://git.launchpad.net/ubuntu/+source/zfs-linux ** Patch added: "zfs-linux_shrinker-deadlock-xattr.debdiff" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+attachment/5281635/+files/zfs-linux_shrinker-deadlock-xattr.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Xenial: In Progress Status in zfs-linux source package in Bionic: Invalid Status in zfs-linux source package in Disco: Invalid Status in zfs-linux source package in Eoan: Invalid Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
Problem Summary: --- If an xattr directory inode and its xattr child inode are on the _same_ disposal list, and the xattr directory inode is _before_ its xattr child inode in this disposal list... Then zfs_purgedir() of the xattr directory calls zfs_zget() for the xattr child inode and it loops forever -- it can only stop if the xattr child inode is disposed/evicted, but it could only occur _after_ in the disposal list and current list node is looping... Because zfs_zget() gets non-NULL from dmu_buf_get_user() (which could go NULL only in the ZFS evict path later in disposal list) so it goes to igrab() but that returns NULL (because the inode.i_state got I_FREEING), then 'goto again:', which repeats that over. Function path: shrink_slab - do_shrink_slab - shrinker->scan_objects == super_cache_scan - prune_icache_sb - list_sru_shrink_walk (creates disposal list with xattr dir&child inodes) - inode_lru_isolate(inode) - inode->i_state |= I_FREEING (problem for igrab of xattr child inode, below) - dispose_list - evict(xattr dir inode) - op->evict_inode == zpl_evict_inode - zfs_inactive - zfs_zinactive - zfs_rmnode - zfs_purgedir - zfs_zget (xattr child nodes) - dmu_buf_get_user (non-NULL) - igrab (NULL) - goto again; ... thus never reaching ... - evict(xattr child inode) - op->evict_inode == zpl_evict_inode - zfs_inactive - zfs_zinactive - zfs_znode_dmu_fini - sa_handle_destroy - dmu_buf_remove_user (not calling this yet is a problem for dmu_buf_get_user, above) (this would make it return NULL and not go into the igrab call) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Xenial: In Progress Status in zfs-linux source package in Bionic: Invalid Status in zfs-linux source package in Disco: Invalid Status in zfs-linux source package in Eoan: Invalid Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
Problem Details: --- Helper scripts (create /zfs.img and mount it on /zfs; and setup kprobe events for debug) $ sudo ./zfs-mount.sh $ sudo ./zfs-kprobes.sh Print kprobe events to screen as we go: $ sudo cat /sys/kernel/debug/tracing/trace_pipe & Create file: - allocates normal/file znode (flag=0x0) - - its object number is obj=0x7 - - its znode pointer is zpp=0x8800a65f8000 $ touch /zfs/file <...>-20059 [000] d... 6718.949684: p_zfs_mknode_0: (zfs_mknode+0x0/0xe10 [zfs]) flag=0x0 dzp=0x8802115b touch-20059 [000] d... 6718.949791: p_zfs_znode_alloc_0: (zfs_znode_alloc+0x0/0x560 [zfs]) obj=0x7 touch-20059 [000] d... 6718.949806: r_zfs_znode_alloc_0: (zfs_mknode+0x8ae/0xe10 [zfs] <- zfs_znode_alloc) zpp=0x8800a65f8000 Set extended attribute on the file: - allocates xattr directory znode (flag=0x2) - - its parent znode is file znode (dzp=0x8800a65f8000) - - its object number is obj=0x8 - - its znode pointer is zpp=0x8802111a8000 - allocates xattr znode (flag=0x0, inherits xattr bit from parent node) - - its parent znode is xattr dir znode (dzp=0x8802111a8000) - - its object number is obj=0x9 - - its znode pointer is zpp=0x8802111a8448 $ setfattr -n user.debug -v 1 /zfs/file <...>-31701 [004] d... 6770.933127: p_zfs_mknode_0: (zfs_mknode+0x0/0xe10 [zfs]) flag=0x2 dzp=0x8800a65f8000 <...>-31701 [004] d... 6770.933287: p_zfs_znode_alloc_0: (zfs_znode_alloc+0x0/0x560 [zfs]) obj=0x8 <...>-31701 [004] d... 6770.933312: r_zfs_znode_alloc_0: (zfs_mknode+0x8ae/0xe10 [zfs] <- zfs_znode_alloc) zpp=0x8802111a8000 <...>-31701 [004] d... 6770.933414: p_zfs_mknode_0: (zfs_mknode+0x0/0xe10 [zfs]) flag=0x0 dzp=0x8802111a8000 <...>-31701 [004] d... 6770.933436: p_zfs_znode_alloc_0: (zfs_znode_alloc+0x0/0x560 [zfs]) obj=0x9 setfattr-31701 [004] d... 6770.933441: r_zfs_znode_alloc_0: (zfs_mknode+0x8ae/0xe10 [zfs] <- zfs_znode_alloc) zpp=0x8802111a8448 Remove file: - Nothing more than zfs_zget() (i.e., "load to memory/get znode and inode for object number") on the file and xattr dir. - No node removal yet (zfs_rmnode), nor its descendent functions. $ rm /zfs/file <...>-5240 [000] d... 6796.826938: p_zfs_zget_0: (zfs_zget+0x0/0x230 [zfs]) zsb=0x8802353a2000 obj=0x7 <...>-5240 [000] d... 6796.826967: r_zfs_zget_0: (zfs_dirent_lock+0x56c/0x6c0 [zfs] <- zfs_zget) rm-5240 [000] d... 6796.827023: p_zfs_zget_0: (zfs_zget+0x0/0x230 [zfs]) zsb=0x8802353a2000 obj=0x8 rm-5240 [000] d... 6796.827030: r_zfs_zget_0: (zfs_remove+0x22b/0x4c0 [zfs] <- zfs_zget) When dropping caches (e.g., inode LRU list) - In one disposal list (i.e., call to dispose_list()) - Evict/Dispose the xattr node (obj 0x9) - This iput()s its parent node (obj 0x8, the xattr dir node) thus dropping its last reference (allows it to be evicted) with zfs_iput_async(). - In another disposal list, before ZFS's async iput() task runs. - Evict/Dispose the xattr dir node (obj 0x8) - This iput()s its parent node (obj 0x7, the file node) thus dropping its last reference (allows it to be evicted). - Then ZFS's async iput() task runs. - Evict/Dispose the file node (obj 0x7) - This triggers the node removal function, zfs_rmnode(). - This zfs_zget()s the xattr dir node (obj 0x8), bringing it back, note it gets another znode pointer value zpp=0x8802115e and drops the reference to it with zfs_iput_async(), thus it's back again, and can/needs to be evicted/disposed again. $ echo 2 | sudo tee /proc/sys/vm/drop_caches ... tee-11196 [002] d... 6823.459967: p_dispose_list_0: (dispose_list+0x0/0x50) tee-11196 [002] d... 6823.459975: p_zpl_evict_inode_0: (zpl_evict_inode+0x0/0x60 [zfs]) inode=0x8802111a8660 tee-11196 [002] d... 6823.459980: p_zfs_inactive_0: (zfs_inactive+0x0/0x270 [zfs]) inode=0x8802111a8660 tee-11196 [002] d... 6823.459982: p_zfs_zinactive_0: (zfs_zinactive+0x0/0xe0 [zfs]) znode=0x8802111a8448 obj=0x9 tee-11196 [002] d... 6823.459994: p_zfs_iput_async_0: (zfs_iput_async+0x0/0x60 [zfs]) inode=0x8802111a8218 obj=0x8 tee-11196 [002] d... 6823.460178: p_dispose_list_0: (dispose_list+0x0/0x50) tee-11196 [002] d... 6823.460895: p_dispose_list_0: (dispose_list+0x0/0x50) tee-11196 [002] d... 6823.461876: p_dispose_list_0: (dispose_list+0x0/0x50) tee-11196 [002] d... 6823.463307: p_dispose_list_0: (dispose_list+0x0/0x50) tee-11196 [002] d... 6823.463412: p_dispose_list_0: (dispose_list+0x0/0x50) tee-11196 [002] d... 6823.463414: p_zpl_evict_inode_0: (zpl_evict_inode+0x0/0x60 [zfs]) inode=0x8802111a8218 tee-11196 [002] d... 6823.463415: p_zfs_inactive_0: (zfs
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
** Attachment added: "kmod-zget.c" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+attachment/5281634/+files/kmod-zget.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Xenial: In Progress Status in zfs-linux source package in Bionic: Invalid Status in zfs-linux source package in Disco: Invalid Status in zfs-linux source package in Eoan: Invalid Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
Fix Details
---
Problem report (GH Issue) upstream in ZFS on Linux:
https://github.com/zfsonlinux/zfs/issues/4816 ("Looping in zfs_zget()")
With very similar stack trace (syscall -> shrink ->
zfs_{inactive/rmnode/purgedir/zget})
https://github.com/zfsonlinux/zfs/issues/4816#issuecomment-229532796
Proposed patch in the Issue (not the right/final solution):
https://github.com/zfsonlinux/zfs/issues/4816#issuecomment-229537558
https://github.com/zfsonlinux/zfs/pull/4822 ("Allow zfs_purgedir() to
skip inodes undergoing eviction")
However, that proposed patch is not the right/final solution:
https://github.com/zfsonlinux/zfs/pull/4822#issuecomment-230938382
https://github.com/zfsonlinux/zfs/pull/4822#issuecomment-232208224
Instead, these proposed patches are actually the right/final solution:
https://github.com/zfsonlinux/zfs/pull/4827 ("xattr dir doesn't get
purged during iput")
The two patches are merged upstream:
https://github.com/zfsonlinux/zfs/pull/4827#issuecomment-232207013
1) ddae16a xattr dir doesn't get purged during ipu
2) 31b6111 Kill zp->z_xattr_parent to prevent pinning
Available in the 0.7.0 release:
$ git describe --contains ddae16a 31b6111
zfs-0.7.0-rc1~102
zfs-0.7.0-rc1~101
Thus Ubuntu only needs these patches on Xenial (zfs-linux < 0.7.0):
$ rmadison zfs-linux
zfs-linux | 0.6.5.6-0ubuntu8 | xenial/universe | source
zfs-linux | 0.6.5.6-0ubuntu27 | xenial-updates | source
zfs-linux | 0.7.5-1ubuntu15 | bionic | source
zfs-linux | 0.7.5-1ubuntu16.6 | bionic-updates | source
zfs-linux | 0.7.12-1ubuntu5 | disco | source
zfs-linux | 0.8.1-1ubuntu8| eoan| source
There's a later commit that changes/"reverts" the
commit ddae16a ("xattr dir doesn't get purged during ipu"),
but it's not a bug fix, but rather a refactor/feature.
https://github.com/zfsonlinux/zfs/pull/4838
With commit dfbc86309fd8 (below).
The commit ids are not mentioned in further commits upstream.
$ git log --oneline --grep ddae16a ddae16a^..origin/master
dfbc86309fd8 Use native inode->i_nlink instead of znode->z_links
$ git log --oneline --grep 31b6111 ddae16a^..origin/master
$
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1839521
Title:
Xenial: ZFS deadlock in shrinker path with xattrs
Status in zfs-linux package in Ubuntu:
Invalid
Status in zfs-linux source package in Xenial:
In Progress
Status in zfs-linux source package in Bionic:
Invalid
Status in zfs-linux source package in Disco:
Invalid
Status in zfs-linux source package in Eoan:
Invalid
Bug description:
[Impact]
* Xenial's ZFS can deadlock in the memory shrinker path
after removing files with extended attributes (xattr).
* Extended attributes are enabled by default, but are
_not_ used by default, which reduces the likelyhood.
* It's very difficult/rare to reproduce this problem,
due to file/xattr/remove/shrinker/lru order/timing
circumstances required. (weeks for a reporter user)
but a synthetic test-case has been found for tests.
[Test Case]
* A synthetic reproducer is available for this LP,
with a few steps to touch/setfattr/rm/drop_caches
plus a kernel module to massage the disposal list.
* In the original ZFS module:
the xattr dir inode is not purged immediately on
file removal, but possibly purged _two_ shrinker
invocations later. This allows for other thread
started before file remove to call zfs_zget() on
the xattr child inode and iput() it, so it makes
to the same disposal list as the xattr dir inode.
* In the modified ZFS module:
the xattr dir inode is purged immediately on file
removal not possibly later on shrinker invocation,
so the problem window above doesn't exist anymore.
[Regression Potential]
* Low. The patches are confined to extended attributes
in ZFS, specifically node removal/purge, and another
change how an xattr child inode tracks its xattr dir
(parent) inode, so that it can be purged immediately
on removal.
* The ZFS test-suite has been run on original/modified
zfs-dkms package/kernel modules, with no regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
** Attachment added: "zfs-mount.sh" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+attachment/5281632/+files/zfs-mount.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Xenial: In Progress Status in zfs-linux source package in Bionic: Invalid Status in zfs-linux source package in Disco: Invalid Status in zfs-linux source package in Eoan: Invalid Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
[Original Description] One LXC user reported lots of processes stuck in D state: several threads waiting in the memory shrinker semaphore (this symptom was thought to be/fixed via LP bug 1817628). After some time, a provided crashdump revealed the issue in ZFS's evict node path running in memory shrinker path (thus locking the semaphore as observed previously/above). The stack trace shows the inode memory shrinker entered ZFS and is looping in zfs_zget(). PID: 42105 TASK: 881169f3d400 CPU: 36 COMMAND: "lxcfs" #0 [88103ea88e38] crash_nmi_callback at 810518a7 #1 [88103ea88e48] nmi_handle at 810323ae #2 [88103ea88ea0] default_do_nmi at 810328f4 #3 [88103ea88ec0] do_nmi at 81032aa2 #4 [88103ea88ee8] end_repeat_nmi at 8185a587 [exception RIP: _raw_spin_lock+20] RIP: 81857464 RSP: 881a23bab138 RFLAGS: 0246 RAX: RBX: 8810a11afb78 RCX: 881e7ad76858 RDX: 0001 RSI: RDI: 8810a11afb78 RBP: 881a23bab138 R8: 0001a6a0 R9: c05e384a R10: ea0070071400 R11: 88014e96d340 R12: R13: 8810a11afb50 R14: 88014e96d340 R15: 8810a11afaf8 ORIG_RAX: CS: 0010 SS: 0018 --- --- #5 [881a23bab138] _raw_spin_lock at 81857464 #6 [881a23bab140] dbuf_read at c08c141a [zfs] #7 [881a23bab1e8] dnode_hold_impl at c08db218 [zfs] #8 [881a23bab250] dnode_hold at c08db659 [zfs] #9 [881a23bab260] dmu_bonus_hold at c08ca2b6 [zfs] #10 [881a23bab2a0] sa_buf_hold at c09023fe [zfs] #11 [881a23bab2b0] zfs_zget at c095cb47 [zfs] #12 [881a23bab350] zfs_purgedir at c093be54 [zfs] #13 [881a23bab558] zfs_rmnode at c093c212 [zfs] #14 [881a23bab5a0] zfs_zinactive at c095d2f8 [zfs] #15 [881a23bab5d8] zfs_inactive at c0956671 [zfs] #16 [881a23bab628] zpl_evict_inode at c096dc03 [zfs] #17 [881a23bab650] evict at 81233d81 #18 [881a23bab678] dispose_list at 81233e86 #19 [881a23bab690] prune_icache_sb at 81234fea #20 [881a23bab6c8] super_cache_scan at 8121b862 #21 [881a23bab720] shrink_slab at 811a8e0d #22 [881a23bab800] shrink_zone at 811ad488 #23 [881a23bab880] do_try_to_free_pages at 811ad5fb #24 [881a23bab900] try_to_free_pages at 811ad91e #25 [881a23bab980] __alloc_pages_slowpath.constprop.88 at 8119ee92 #26 [881a23baba60] __alloc_pages_nodemask at 8119f908 #27 [881a23babb00] alloc_pages_current at 811ea47c #28 [881a23babb48] alloc_kmem_pages at 8119d4d9 #29 [881a23babb70] kmalloc_order_trace at 811bb04e #30 [881a23babbb0] __kmalloc at 811f6e90 #31 [881a23babbf8] seq_buf_alloc at 8123ca00 #32 [881a23babc10] single_open_size at 8123dc1a #33 [881a23babc50] stat_open at 8128fc76 #34 [881a23babc68] proc_reg_open at 81286011 #35 [881a23babca0] do_dentry_open at 81215a02 #36 [881a23babce0] vfs_open at 81216b94 #37 [881a23babd08] path_openat at 81226bac #38 [881a23babdc8] do_filp_open at 81228b41 #39 [881a23babed0] do_sys_open at 81216f68 #40 [881a23babf40] sys_open at 812170ee #41 [881a23babf50] entry_SYSCALL_64_fastpath at 818576ce This stack trace is closely matched in this upstream ZFS github issue (#4816) with patches merged in this ZFS github pull request (#4827) [see LP comments for details. Other 2 threads were found in ZFS code, but not checked to be related to the above thread as an upstream Github issue closely matched & described the stack trace above. PID: 56179 TASK: 880106189c00 CPU: 3 COMMAND: "crond" #0 [88203de48e38] crash_nmi_callback at 810518a7 #1 [88203de48e48] nmi_handle at 810323ae #2 [88203de48ea0] default_do_nmi at 810328f4 #3 [88203de48ec0] do_nmi at 81032aa2 #4 [88203de48ee8] end_repeat_nmi at 8185a587 [exception RIP: _raw_spin_lock+20] RIP: 81857464 RSP: 880002dc7978 RFLAGS: 0246 RAX: RBX: 8812ee29f168 RCX: 0001 RDX: 0001 RSI: 0202 RDI: 8812ee29f1f0 RBP: 880002dc7978 R8: 880115e22c00 R9: 0080 R10: ea004758ac00 R11: c000 R12: 8812ee29f1f0 R13: R14: 8812ee29ef50 R15: 880eefad8060 ORIG_RAX: CS: 0010 SS: 0018 --- --- #5 [880002dc7978] _raw_spin_lock at 81857464 #6 [880002dc7980] igrab at 81233a4e #7 [880002dc79a0] zfs_zget at c095cad6 [zfs] #8 [880002dc7a40] zfs_dirent_lock at c093ae99 [zfs] #9 [880002dc7ae8
[Kernel-packages] [Bug 1839072] Re: disco/linux-aws: 5.0.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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 backports: bug 1839070 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 06. August 2019 19:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839070 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839072 Title: disco/linux-aws: 5.0.0-1012.13 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 backports: bug 1839070 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 06. August 2019 19:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839070 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL
I've sponsored this and uploaded it to -proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1811730 Title: Thermald does not set max CPU after reseting the voltage using RAPL Status in thermald package in Ubuntu: Confirmed Bug description: Hi, I was using Ubuntu 18.10 thermald package, but I noted that, after few seconds at max CPU usage (max temp), thermald send the signal to RALP to reduce the voltage of the CPU. It set the freq to minimum (800MHz in my case). But when the CPU is idle and temp is lowered (35-40ºC) it did not send the signal to resume normal operation of the CPU. I compiled the latest version of thermald from git (https://github.com/intel/thermal_daemon) and now everything works fine. I started to thought that the problem was the hardware or BIOS problem, as I disabled the CPU scaling on the BIOS, but intel_pstate continued doing freq scaling (I think for Turbo mode). But the real problem was Thermald. The latest version from git works really fine and it automatically disables and enable the Intel Turbo state and balance the freqs and fan control fine. My hardware is a Lenovo Thinkpad P52 with i7-8850H. I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7 processor but with Ubuntu default config (except processor family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low- Latency Desktop)" and Timer frequency="1000HZ". (Only changed those settings from make oldconfig and make deb-pkg). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thermald (not installed) ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 14 23:45:01 2019 InstallationDate: Installed on 2018-12-11 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+subscriptions -- Mailing list: https://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 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools) works on kernel 4.13 but not on 4.15
On Thu, Aug 08, 2019 at 15:27:20 -, James Kingdon wrote: > I got hit by this after a power outage cycled my file servers and > presumably activated a previous automatic kernel update (the servers > normally stay up for months at a time). > > The kernel that is currently running is: > > Linux oban8 4.14.111-odroidxu4 #2 SMP PREEMPT Wed May 8 17:30:01 CEST > 2019 armv7l armv7l armv7l GNU/Linux Interesting. Do you know what kernel version was running beforehand? Also, what are the USB ids of the drive enclosure device(s) that were affected? (Were they in fact Seagate drives?) > > The temporary work-around documented on the Smartmontools Wiki worked > for me (thanks for the link!), now I have to figure out how to make the Cool. > change persistent on these ARM based systems :( I don't use Odroid myself but did run across mentions of it in my web research on this topic... Does the "UASP" item in https://wiki.odroid.com/odroid-xu4/os_images/linux/ubuntu_4.14/20181203-minimal#known_issues_and_tips point you in the right direction? (After reading that paragraph, I'm curious to know if the problem you hit was actually the NO_ATA_1X flag getting set on your device when using the UAS driver [as originally covered in this bug], or a more general failure of the UAS driver on ARM for your devices. That is, did you come to this web page because Smartmontools stopped working, or because your disks stopped working? [In either case, the :u quirks would work around the problem; the question is just which problem you are working around...]) Nathan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write ca
[Kernel-packages] [Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL
The attachment "debdiff.patch" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1811730 Title: Thermald does not set max CPU after reseting the voltage using RAPL Status in thermald package in Ubuntu: Confirmed Bug description: Hi, I was using Ubuntu 18.10 thermald package, but I noted that, after few seconds at max CPU usage (max temp), thermald send the signal to RALP to reduce the voltage of the CPU. It set the freq to minimum (800MHz in my case). But when the CPU is idle and temp is lowered (35-40ºC) it did not send the signal to resume normal operation of the CPU. I compiled the latest version of thermald from git (https://github.com/intel/thermal_daemon) and now everything works fine. I started to thought that the problem was the hardware or BIOS problem, as I disabled the CPU scaling on the BIOS, but intel_pstate continued doing freq scaling (I think for Turbo mode). But the real problem was Thermald. The latest version from git works really fine and it automatically disables and enable the Intel Turbo state and balance the freqs and fan control fine. My hardware is a Lenovo Thinkpad P52 with i7-8850H. I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7 processor but with Ubuntu default config (except processor family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low- Latency Desktop)" and Timer frequency="1000HZ". (Only changed those settings from make oldconfig and make deb-pkg). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thermald (not installed) ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 14 23:45:01 2019 InstallationDate: Installed on 2018-12-11 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839461] Re: sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64
OK, it seems to hang on PCI device 00:01.0: 00:01.0 Serial controller: Amazon.com, Inc. Device 8250 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839461 Title: sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64 Status in linux-aws package in Ubuntu: New Bug description: Issue found on arm64 node with D-AWS kernel sysfs failed on: a1.2xlarge / a1.large procfs failed on: a1.2xlarge / a1.medium sysfs failure: sysfs FAILED stress-ng: debug: [16876] 8 processors online, 8 processors configured stress-ng: info: [16876] dispatching hogs: 4 sysfs stress-ng: debug: [16876] cache allocate: reducing cache level from L3 (too high) to L2 stress-ng: debug: [16876] cache allocate: default cache size: 2048K stress-ng: debug: [16876] starting stressors stress-ng: debug: [16877] stress-ng-sysfs: started [16877] (instance 0) stress-ng: debug: [16878] stress-ng-sysfs: started [16878] (instance 1) stress-ng: debug: [16876] 4 stressors spawned stress-ng: debug: [16879] stress-ng-sysfs: started [16879] (instance 2) stress-ng: debug: [16880] stress-ng-sysfs: started [16880] (instance 3) stress-ng: error: [16877] stress-ng-sysfs: A SIGSEGV occurred while exercising /sys/power/pm_print_times, aborting stress-ng: debug: [16877] stress-ng-sysfs: exited [16877] (instance 0) stress-ng: error: [16876] process 16877 (stress-ng-sysfs) terminated with an error, exit status=1 (stress-ng core failure) stress-ng: debug: [16876] process [16877] terminated stress-ng: error: [16878] stress-ng-sysfs: A SIGSEGV occurred while exercising /sys/kernel/irq/1/name, aborting stress-ng: debug: [16878] stress-ng-sysfs: exited [16878] (instance 1) stress-ng: error: [16876] process 16878 (stress-ng-sysfs) terminated with an error, exit status=1 (stress-ng core failure) stress-ng: debug: [16876] process [16878] terminated stress-ng: debug: [16879] stress-ng-sysfs: exited [16879] (instance 2) stress-ng: debug: [16876] process [16879] terminated stress-ng: debug: [16880] stress-ng-sysfs: exited [16880] (instance 3) stress-ng: debug: [16876] process [16880] terminated stress-ng: info: [16876] unsuccessful run completed in 5.04s procfs failure: procfs FAILED stress-ng: debug: [27728] 8 processors online, 8 processors configured stress-ng: info: [27728] dispatching hogs: 4 procfs stress-ng: debug: [27728] cache allocate: reducing cache level from L3 (too high) to L2 stress-ng: debug: [27728] cache allocate: default cache size: 2048K stress-ng: debug: [27728] starting stressors stress-ng: debug: [27729] stress-ng-procfs: started [27729] (instance 0) stress-ng: debug: [27730] stress-ng-procfs: started [27730] (instance 1) stress-ng: debug: [27728] 4 stressors spawned stress-ng: debug: [27731] stress-ng-procfs: started [27731] (instance 2) stress-ng: debug: [27732] stress-ng-procfs: started [27732] (instance 3) *** stack smashing detected ***: terminated stress-ng: debug: [27730] stress-ng-procfs: exited [27730] (instance 1) stress-ng: debug: [27729] stress-ng-procfs: exited [27729] (instance 0) stress-ng: debug: [27728] process [27729] terminated stress-ng: debug: [27728] process [27730] terminated stress-ng: debug: [27728] process [27731] (stress-ng-procfs) terminated on signal: 6 (Aborted) stress-ng: debug: [27728] process [27731] terminated stress-ng: debug: [27732] stress-ng-procfs: exited [27732] (instance 3) stress-ng: debug: [27728] process [27732] terminated stress-ng: info: [27728] unsuccessful run completed in 5.00s ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1011-aws 5.0.0-1011.12 ProcVersionSignature: User Name 5.0.0-1011.12-aws 5.0.15 Uname: Linux 5.0.0-1011-aws aarch64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: arm64 Date: Thu Aug 8 11:03:32 2019 Ec2AMI: ami-0ac1a3bc4f5c85238 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1839461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826447] Re: Azure: Backport vIOMMU driver (increase vCPU limits)
** Changed in: linux-azure (Ubuntu Disco) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1826447 Title: Azure: Backport vIOMMU driver (increase vCPU limits) Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure source package in Disco: In Progress Bug description: Description: To support VM instances with >255 vCPUS, we need the patch set below backported to the Azure 4.18 kernel. These patches include - - New Hyper-V IOMMU driver. This driver will be Hyper-V specific. - Minor update to the Hyper-V specific virtual PCI code. Need to expand the size of an array to allow for a larger number of vCPUs. There are very large VM instance sizes coming to Azure in 2019, and Ubuntu will require the following patches in order to function properly: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1826447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839281] Re: bionic/linux-fips: 4.15.0-1015.18 -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: 1839293 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 13:35 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- package copied to Signing signed:building 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: 1839293 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 13:35 UTC reason: - promote-to-proposed: Ongoing -- package copied to Signing signed:building + 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 in Ubuntu. https://bugs.launchpad.net/bugs/1839281 Title: bionic/linux-fips: 4.15.0-1015.18 -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: 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 verification-testing series: New 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: 1839293 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 13:35 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/1839281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839278] Re: xenial/linux-oracle: 4.15.0-1021.23~16.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: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 15:30 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1839278 Title: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -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: 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 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 15:30 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/1839278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839093] Re: disco/linux-gcp: 5.0.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** 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 backports: bug 1839086 (bionic/linux-gke-5.0), bug 1839090 (bionic /linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Tuesday, 06. August 2019 19:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1839090 bionic/linux-gke-5.0: bug 1839086 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839093 Title: disco/linux-gcp: 5.0.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 backports: bug 1839086 (bionic/linux-gke-5.0), bug 1839090 (bionic /linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Tuesday, 06. August 2019 19:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1839090 bionic/linux-gke-5.0: bug 1839086 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.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 derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 13:25 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:retry-needed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -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: 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 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-gcp package in Ubuntu: Invalid Status in linux-gcp 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 derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 13:25 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838113] Re: eoan/linux: 5.2.0-10.11 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-eoan ** Tags removed: 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 backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Testing - phase-changed: Thursday, 01. August 2019 17:41 UTC + phase: Ready for Release + phase-changed: Thursday, 08. August 2019 16:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + promote-to-release: Pending -- ready to copy trackers: bionic/linux-hwe-edge: bug 1838112 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/1838113 Title: eoan/linux: 5.2.0-10.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed 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 backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Release phase-changed: Thursday, 08. August 2019 16:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy trackers: bionic/linux-hwe-edge: bug 1838112 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839293] Re: bionic/linux: 4.15.0-58.64 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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 backports: bug 1839287 (xenial/linux-azure), bug 1839291 (xenial/linux-hwe) derivatives: bug 1839255 (pc-kernel), bug 1839256 (pc-lowlatency-kernel), bug 1839258 (linux-raspi2), bug 1839260 (linux-snapdragon), bug 1839261 (linux-oem), bug 1839266 (linux-aws), bug 1839272 (linux-gcp), bug 1839275 (linux-gke-4.15), bug 1839276 (linux-kvm), bug 1839277 (linux-ibm-gt), bug 1839280 (linux-oracle), bug 1839281 (linux-fips) -- 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, 08. August 2019 09:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + 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 1839266 bionic/linux-fips: bug 1839281 bionic/linux-gcp: bug 1839272 bionic/linux-gke-4.15: bug 1839275 bionic/linux-ibm-gt: bug 1839277 bionic/linux-kvm: bug 1839276 bionic/linux-oem: bug 1839261 bionic/linux-oracle: bug 1839280 bionic/linux-raspi2: bug 1839258 bionic/linux-snapdragon: bug 1839260 bionic/linux/pc-kernel: bug 1839255 bionic/linux/pc-lowlatency-kernel: bug 1839256 xenial/linux-azure: bug 1839287 xenial/linux-hwe: bug 1839291 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/1839293 Title: bionic/linux: 4.15.0-58.64 -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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug 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 backports: bug 1839287 (xenial/linux-azure), bug 1839291 (xenial/linux-hwe) derivatives: bug 1839255 (pc-kernel), bug 1839256 (pc-lowlatency-kernel), bug 1839258 (linux-raspi2), bug 1839260 (linux-snapdragon), bug 1839261 (linux-oem), bug 1839266 (linux-aws), bug 1839272 (linux-gcp), bug 1839275 (linux-gke-4.15), bug 1839276 (linux-kvm), bug 1839277 (linux-ibm-gt), bug 1839280 (linux-oracle), bug 1839281 (linux-fips) -- 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, 08. August 2019 09:16 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 1839266 bionic/linux-fips: bug 1839281 bionic/linux-gcp: bug 1839272 bionic/linux-gke-4.15: bug 1839275 bionic/linux-ibm-gt: bug 1839277 bionic/linux-kvm: bug 1839276 bionic/linux-oem: bug 1839261 bionic/linux-oracle: bug 1839280 bionic/linux-raspi2: bug 1839258 bionic/linux-snapdragon: bug 1839260 bionic/linux/pc-kernel: bug 1839255 bionic/linux/pc-lowlatency-kernel: bug 1839256 xenial/linux-azure: bug 1839
[Kernel-packages] [Bug 1839272] Re: bionic/linux-gcp: 4.15.0-1040.42 -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 backports: bug 1839270 (xenial/linux-gcp) derivatives: bug 1839267 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 12:35 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-gcp/gcp-kernel: bug 1839267 xenial/linux-gcp: bug 1839270 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839272 Title: bionic/linux-gcp: 4.15.0-1040.42 -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: 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 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-gcp package in Ubuntu: Invalid Status in linux-gcp 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 backports: bug 1839270 (xenial/linux-gcp) derivatives: bug 1839267 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 12:35 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-gcp/gcp-kernel: bug 1839267 xenial/linux-gcp: bug 1839270 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839261] Re: bionic/linux-oem: 4.15.0-1050.57 -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: 1839293 packages: main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 12:25 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1839261 Title: bionic/linux-oem: 4.15.0-1050.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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: 1839293 packages: main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 12:25 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/1839261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839280] Re: bionic/linux-oracle: 4.15.0-1021.23 -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 backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 13:10 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-oracle: bug 1839278 variant: debs -- 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/1839280 Title: bionic/linux-oracle: 4.15.0-1021.23 -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: 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 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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 backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 13:10 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-oracle: bug 1839278 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL
A test package has been built in https://launchpad.net/~anthonywong/+archive/ubuntu/for- review?field.series_filter=bionic for testing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1811730 Title: Thermald does not set max CPU after reseting the voltage using RAPL Status in thermald package in Ubuntu: Confirmed Bug description: Hi, I was using Ubuntu 18.10 thermald package, but I noted that, after few seconds at max CPU usage (max temp), thermald send the signal to RALP to reduce the voltage of the CPU. It set the freq to minimum (800MHz in my case). But when the CPU is idle and temp is lowered (35-40ºC) it did not send the signal to resume normal operation of the CPU. I compiled the latest version of thermald from git (https://github.com/intel/thermal_daemon) and now everything works fine. I started to thought that the problem was the hardware or BIOS problem, as I disabled the CPU scaling on the BIOS, but intel_pstate continued doing freq scaling (I think for Turbo mode). But the real problem was Thermald. The latest version from git works really fine and it automatically disables and enable the Intel Turbo state and balance the freqs and fan control fine. My hardware is a Lenovo Thinkpad P52 with i7-8850H. I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7 processor but with Ubuntu default config (except processor family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low- Latency Desktop)" and Timer frequency="1000HZ". (Only changed those settings from make oldconfig and make deb-pkg). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thermald (not installed) ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 14 23:45:01 2019 InstallationDate: Installed on 2018-12-11 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL
debdiff against thermald 1.7.0-5ubuntu2 in Bionic. ** Patch added: "debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+attachment/5281627/+files/debdiff.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1811730 Title: Thermald does not set max CPU after reseting the voltage using RAPL Status in thermald package in Ubuntu: Confirmed Bug description: Hi, I was using Ubuntu 18.10 thermald package, but I noted that, after few seconds at max CPU usage (max temp), thermald send the signal to RALP to reduce the voltage of the CPU. It set the freq to minimum (800MHz in my case). But when the CPU is idle and temp is lowered (35-40ºC) it did not send the signal to resume normal operation of the CPU. I compiled the latest version of thermald from git (https://github.com/intel/thermal_daemon) and now everything works fine. I started to thought that the problem was the hardware or BIOS problem, as I disabled the CPU scaling on the BIOS, but intel_pstate continued doing freq scaling (I think for Turbo mode). But the real problem was Thermald. The latest version from git works really fine and it automatically disables and enable the Intel Turbo state and balance the freqs and fan control fine. My hardware is a Lenovo Thinkpad P52 with i7-8850H. I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7 processor but with Ubuntu default config (except processor family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low- Latency Desktop)" and Timer frequency="1000HZ". (Only changed those settings from make oldconfig and make deb-pkg). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thermald (not installed) ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 14 23:45:01 2019 InstallationDate: Installed on 2018-12-11 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838113] Re: eoan/linux: 5.2.0-10.11 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => 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 backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 01. August 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1838112 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/1838113 Title: eoan/linux: 5.2.0-10.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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-release series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed 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 backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 01. August 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED trackers: bionic/linux-hwe-edge: bug 1838112 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838113] Re: eoan/linux: 5.2.0-10.11 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838113 Title: eoan/linux: 5.2.0-10.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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-release series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed 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 backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 01. August 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED trackers: bionic/linux-hwe-edge: bug 1838112 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839097] Re: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0
** Bug watch added: freedesktop.org Bugzilla #111333 https://bugs.freedesktop.org/show_bug.cgi?id=111333 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839097 Title: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 Status in linux package in Ubuntu: Confirmed Bug description: Purged Open source PPA and problem persists: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 10:54:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (226 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro text resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839097/+subscriptions -- Mailing list: https://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 1839097] Re: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0
Kai-Heng Feng pisze: > Please file an upstream bug at https://bugs.freedesktop.org/ > Product: DRI > Component: DRM/Radeon > It's under below link now: https://bugs.freedesktop.org/show_bug.cgi?id=111333 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839097 Title: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 Status in linux package in Ubuntu: Confirmed Bug description: Purged Open source PPA and problem persists: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 10:54:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (226 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro text resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839260] Re: bionic/linux-snapdragon: 4.15.0-1060.66 -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-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1839260 Title: bionic/linux-snapdragon: 4.15.0-1060.66 -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-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: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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 derivatives: bug 1839259 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 08. August 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839259 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839261] Re: bionic/linux-oem: 4.15.0-1050.57 -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: 1839293 packages: main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 12:25 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed 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/1839261 Title: bionic/linux-oem: 4.15.0-1050.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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: 1839293 packages: main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 12:25 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839266] Re: bionic/linux-aws: 4.15.0-1045.47 -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 backports: bug 1839264 (xenial/linux-aws-hwe) derivatives: bug 1839263 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-aws meta: linux-meta-aws - phase: Ready for Testing - phase-changed: Wednesday, 07. August 2019 16:40 UTC + phase: Signoff + phase-changed: Thursday, 08. August 2019 15:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws/aws-kernel: bug 1839263 xenial/linux-aws-hwe: bug 1839264 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839266 Title: bionic/linux-aws: 4.15.0-1045.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug 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 backports: bug 1839264 (xenial/linux-aws-hwe) derivatives: bug 1839263 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Thursday, 08. August 2019 15:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws/aws-kernel: bug 1839263 xenial/linux-aws-hwe: bug 1839264 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839258] Re: bionic/linux-raspi2: 4.15.0-1043.46 -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-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1839258 Title: bionic/linux-raspi2: 4.15.0-1043.46 -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-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: Confirmed 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 derivatives: bug 1839257 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 08. August 2019 13: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: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1839257 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.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 derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 13:25 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:retry-needed trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -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: 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 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-gcp package in Ubuntu: Invalid Status in linux-gcp 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 derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 13:25 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:retry-needed trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839266] Re: bionic/linux-aws: 4.15.0-1045.47 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839266 Title: bionic/linux-aws: 4.15.0-1045.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug 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 backports: bug 1839264 (xenial/linux-aws-hwe) derivatives: bug 1839263 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Thursday, 08. August 2019 15:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws/aws-kernel: bug 1839263 xenial/linux-aws-hwe: bug 1839264 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838208] Re: Wifi stops responding sporadically on lenovo-yoga-720-15ikb
Sorry, how do I install this? I don't want to mess anything up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:c
[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat
You're very welcome Christoph, thanks for the patch!
I've verified that with Bionic, but facing some non-related issues with Disco
kernel (5.x).
Cheers,
Guilherme
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824981
Title:
cifs set_oplock buffer overflow in strcat
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* We got reports of a kernel crash in cifs module with the following
signature:
detected buffer overflow in strcat
kernel BUG at <...>/lib/string.c:1052!
invalid opcode: [#1] SMP PTI
RIP: 0010:fortify_panic+0x13/0x1f
Call Trace:
smb21_set_oplock_level+0xde/0x190 [cifs]
smb3_set_oplock_level+0x22/0x90 [cifs]
smb2_set_fid+0x76/0xb0 [cifs]
cifs_new_fileinfo+0x268/0x3c0 [cifs]
? smb2_get_lease_key+0x40/0x40 [cifs]
? cifs_new_fileinfo+0x268/0x3c0 [cifs]
cifs_open+0x57c/0x8d0 [cifs]
do_dentry_open+0x1fe/0x320
[...]
* By analyzing the code of smb21_set_oplock_level(), we've noticed the
only way fortify function strcat() would get overflow was if the value
of cinode->oplock got corrupted in a another thread leading to a
buffer write bigger then buffer size. In this function, the 'message'
buffer writes are governed by cinode->oplock, so only a different
thread cleaning the oplock value would lead to 'message' overflow.
* By the same time we worked this analysis, a fix was proposed
upstream for this issue in the form of commit 6a54b2e002c9 ("cifs:
fix strcat buffer overflow and reduce raciness in
smb21_set_oplock_level()"), by the same reporter of this LP. The fix
is simple and directly addresses this problem, so we hereby request
its SRU into Bionic kernel - it's already present in linux stable
branches.
[Test case]
* Unfortunately we cannot reproduce the issue. The patch proposed here was
validated by us with xfstests (instructions followed from
https://wiki.samba.org/index.php/Xfstesting-cifs) and fio.
* Using xfstest with the exclusions proposed in the link above we
managed to get the same results as a non-patched kernel, i.e., the
same tests failed in both kernels, we didn't get worse results with
the patch. Fio also didn't show noticeable performance regression with
the patch.
[Regression potential]
* The patch was validated by the cifs filesystem maintainers and by
the aforementioned tests; also, the scope is restricted to cifs only
so the likelihood of regressions is considered low. The commit
introduces no functional changes and the only affected path was just
refactored in a way to prevent overflow and reduce race potential.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824981/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839278] Re: xenial/linux-oracle: 4.15.0-1021.23~16.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: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 15:30 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1839278 Title: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -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: 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 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 08. August 2019 15:30 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/1839278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
