[Kernel-packages] [Bug 1836064] Re: linux-5.2 (?) breaks the c-t-b builds
I can confirm that a definition of __NR_osf_shmat was added during the 5.1 cycle: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=12b57c5c70f397a9410411d4e348096edada20f9 Looks like a fix has been applied to upstream glibc: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=d5ecee822e72a2fd156338ab2be2f2e70a1da55a -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836064 Title: linux-5.2 (?) breaks the c-t-b builds Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: as seen in https://launchpad.net/ubuntu/+source/cross-toolchain-base-ports/30ubuntu2/+build/17249410 the c-t-b-ports package ftbfs: /bin/bash ../scripts/move-if-change /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.T /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.h touch /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.stmp if test -r /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new; then mv -f /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h; \ else echo >&2 'This configuration not matched in ../abi-tags'; exit 1; fi In file included from :1: ../sysdeps/unix/sysv/linux/alpha/sysdep.h:54: error: "__NR_osf_shmat" redefined [-Werror] #define __NR_osf_shmat 209 In file included from ../sysdeps/unix/sysv/linux/sys/syscall.h:24, from ../sysdeps/unix/sysdep.h:20, from ../sysdeps/unix/alpha/sysdep.h:19, from ../sysdeps/unix/sysv/linux/alpha/sysdep.h:29, from :1: /<>/glibc-2.29/debian/include/asm/unistd.h:8: note: this is the location of the previous definition #define __NR_osf_shmat __NR_shmat cc1: all warnings being treated as errors Traceback (most recent call last): File "../scripts/gen-as-const.py", line 120, in main() File "../scripts/gen-as-const.py", line 116, in main consts = glibcextract.compute_c_consts(sym_data, args.cc) File "/<>/glibc-2.29/scripts/glibcextract.py", line 62, in compute_c_consts subprocess.check_call(cmd, shell=True) File "/usr/lib/python3.7/subprocess.py", line 347, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command 'alpha-linux-gnu-gcc-8 -no-pie -fno-PIE -std=gnu11 -fgnu89-inline -pipe -O2 -g -Wall -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fno-stack-protector -Wstrict-prototypes -Wold-style-definition -fmath-errno -mlong-double-128 -mieee -mfp-rounding-mode=d-ftls-model=initial-exec -U_FORTIFY_SOURCE -isystem /<>/glibc-2.29/debian/include -I../include -I/<>/glibc-2.29/build-tree/alpha-libc/csu -I/<>/glibc-2.29/build-tree/alpha-libc -I../sysdeps/unix/sysv/linux/alpha/alpha -I../sysdeps/unix/sysv/linux/alpha/fpu -I../sysdeps/alpha/fpu -I../sysdeps/unix/sysv/linux/alpha -I../sysdeps/alpha/nptl -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/ieee754/ldbl-64-128 -I../sysdeps/ieee754/ldbl-opt -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/alpha -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/alpha -I../sysdeps/wordsize-64 -I../sysdeps/ieee754/ldbl-128 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem /<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include -isystem /<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include-fixed -isystem /<>/glibc-2.29/debian/include -D_LIBC_REENTRANT -include /<>/glibc-2.29/build-tree/alpha-libc/libc-modules.h -DMODULE_NAME=libc -include ../include/libc-symbols.h -DTOP_NAMESPACE=glibc -DGEN_AS_CONST_HEADERS-MD -MP -MF /<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.dT -MT '/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.d /<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h' -S -o /tmp/tmpq06grbcg/test.s -x c - < /tmp/tmpq06grbcg/test.c' returned non-zero exit status 1. make[4]: *** [../Makerules:271: /<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h] Error 1 make[4]: Leaving directory '/<>/glibc-2.29/csu' make[3]: *** [Makefile:275: csu/subdir_lib] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1836064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836045] Re: ftbfs: gnat cross targeting powerpc
That's not true; most architectures don't have a match for SO_RCVTIMEO,
as they're using the definition from asm-generic, just as powerpc should
be. The others were updated differently because they do not include asm-
generic/socket.h. And powerpc clearly does have a definition for it,
since the build complains that SO_RCVTIMEO_OLD is not defined and not
SO_RCVTIMEO. The question is why isn't SO_RCVTIMEO_OLD defined.
I tried cross-compiling the following for ppc64el and did not receive
any errors about SO_RCVTIMEO or SO_RCVTIMEO_OLD being undefined, nor did
it complain when I used SO_RCVTIMEO_OLD, so it seems like it's working
as intended. That leaves me wondering whether something isn't including
asm-generic/socket.h when it should be including asm/socket.h, or
something like that. I don't see any such mistakes in linux-libc-dev
though.
#include
#include
int main(void)
{
printf("%d\n", SO_RCVTIMEO);
return 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/1836045
Title:
ftbfs: gnat cross targeting powerpc
Status in gcc-8-cross package in Ubuntu:
Confirmed
Status in gcc-9-cross package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
both seen with gcc-8-cross and gcc-9-cross (search the build logs for
"unfinished":
/<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/
-B/usr/powerpc-linux-gnu/bin/ -B/usr/powerpc-li
nux-gnu/lib/ -isystem /usr/powerpc-linux-gnu/include -isystem
/usr/powerpc-linux-gnu/sys-include -isystem /<
>/gcc/build/sys-include-c -g -O2 -W -Wall -gnatpg -nostdinc -gnatn
a-direct.adb -o a-direct.o
a-direct.adb:734:27: "NAME_MAX" is undefined
a-direct.adb:743:28: "SIZEOF_struct_dirent_alloc" is undefined
a-direct.adb:1210:24: "ENOENT" is undefined
s-filatt.ads:62:18: "SIZEOF_struct_file_attributes" not declared in
"OS_Constants"
s-oscons.ads:50:26: "Target_OS" is undefined
s-oscons.ads:54:01: (style) multiple blank lines
s-oscons.ads:59:01: (style) multiple blank lines
s-oscons.ads:64:01: (style) multiple blank lines
s-oscons.ads:69:01: (style) multiple blank lines
s-oscons.ads:74:01: (style) multiple blank lines
s-oscons.ads:79:01: (style) multiple blank lines
s-oscons.ads:86:01: (style) multiple blank lines
s-oscons.ads:91:01: (style) multiple blank lines
s-oscons.ads:96:01: (style) multiple blank lines
s-oscons.ads:101:01: (style) multiple blank lines
s-oscons.ads:106:01: (style) multiple blank lines
s-oscons.ads:111:01: (style) multiple blank lines
s-oscons.ads:116:01: (style) multiple blank lines
s-oscons.ads:121:01: (style) multiple blank lines
s-oscons.ads:126:01: (style) multiple blank lines
s-oscons.ads:131:01: (style) multiple blank lines
s-oscons.ads:136:01: (style) multiple blank lines
s-oscons.ads:147:01: (style) multiple blank lines
s-oscons.ads:166:01: (style) multiple blank lines
s-oscons.ads:173:01: (style) multiple blank lines
s-oscons.ads:176:01: (style) multiple blank lines
s-oscons.ads:181:01: (style) multiple blank lines
make[9]: *** [../gcc-interface/Makefile:299: a-direct.o] Error 1
make[9]: Leaving directory '/<>/gcc/build/gcc/ada/rts'
make[8]: *** [gcc-interface/Makefile:623: gnatlib] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-8-cross/+bug/1836045/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835345] Re: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Fix Released -- 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/1835345 Title: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] BT fails to enable again after disabled it by hotkey with the following message Bus 001 Device 004: ID 8087:0029 Intel Corp. [248987.643125] usb 1-10: device descriptor read/64, error -110 [249003.247721] usb 1-10: device descriptor read/64, error -110 [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249018.855466] usb 1-10: device descriptor read/64, error -110 [249034.467589] usb 1-10: device descriptor read/64, error -110 [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249045.299399] usb 1-10: device not accepting address 4, error -62 [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249050.675715] usb 1-10: Device not responding to setup address. [249050.883541] usb 1-10: device not accepting address 4, error -71 [Fix] Found the updated firmware fixes the issue [Test] Verify on the machine couple days, and can't duplicate the issue anymore. [Regression Potential] Low, the system keeps running for 5 days, and pass s3 tests 30 times, everything works well. [Misc] The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards require the new fw_revision, so SRU both of them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835449] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260)
** Changed in: linux-firmware (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1835449 Title: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260) Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Bug description: [Impact] Intel Wireless-AC 9260 Bluetooth doesn't pair to Bluetooth 5.0 HID devices. [Fix] Bluetooth FW Build REL0329 or newer is known to have fixed this problem on Cosmic, and for Disco we have REL0420. On Bionic and Xenial it takes a firmware backport from upstream commit c2d8f1b7f820b31b6120d741c23db23340a72821. Original patch modified to fix conflicts in the WHENCE file. [Test Case] Verified on hardware platforms with Intel Wireless AC 9260 installed, e.g. Dell Precision 7530. Copied the two blobs to /lib/firmware/intel and power off the device completely to trigger firmware reload at the next boot. [Regression Risk] Low. Tried following kernels with REL0329 firmware blobs: * 4.4.0-154-generic: Xenial, WiFi/Bluetooth doesn't work * 4.8.0-58-generic: Xenial, even doesn't boot to console * 4.10.0-42-generic: Xenial, WiFi/Bluetooth doesn't work * 4.11.0-14-generic: Xenial, WiFi/Bluetooth doesn't work * 4.13.0-45-generic: Xenial * 4.15.0-54-generic: Xenial, Bionic * 4.15.0-1043-oem: Xenial, Bionic For those WiFi/Bluetooth doesn't work versions, WiFi/Bluetooth doesn't work even with current firmware blobs shipped in Xenial's linux-firmware REL0186. So overall, these updated blobs are only loaded by hardware requires them, and they doesn't bring harm to known working configurations. Original Bug Description Same problem exactly as encountered with Intel 9560 is also happening with Intel 9260. Update to linux-firmware 1.173.8 did not fix the problem. Everything is working fine when using 4.15 kernel, but not for 4.18+ 5.0+. Reference problem: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1829737 You-Sheng Yang advised to do this by email and it fixed my issue, so I think the 9260 driver would need to be updated in the bionic branch (it seems to be updated in newer branches). -- Basically you should try copy the latest firmware (ibt-*) under https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel , power off the device completely and power on, then have a check on bluetooth pairing. -- Linux ideapad 5.0.0-20-generic #21~18.04.1-Ubuntu SMP Thu Jun 27 04:04:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux OS: Linux Mint 19.1 Tessa x86_64 Host: 81JB Lenovo ideapad 730S-13IWL Wifi/Bluetooth card is Intel 9260 @:/etc$ dmesg | egrep -i 'blue|firm' [0.099619] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.173124] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.379392] [Firmware Bug]: Invalid critical threshold (0) [2.699758] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [6.259427] iwlwifi :73:00.0: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [6.337749] Bluetooth: Core ver 2.22 [6.337767] Bluetooth: HCI device and connection manager initialized [6.337770] Bluetooth: HCI socket layer initialized [6.337773] Bluetooth: L2CAP socket layer initialized [6.33] Bluetooth: SCO socket layer initialized [6.368073] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [7.309936] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.309938] Bluetooth: BNEP filters: protocol multicast [7.309943] Bluetooth: BNEP socket layer initialized [ 17.197268] Bluetooth: RFCOMM TTY layer initialized [ 17.197275] Bluetooth: RFCOMM socket layer initialized [ 17.197284] Bluetooth: RFCOMM ver 1.11 [ 104.453159] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.509148] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.551340] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.589338] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.623323] Bluetooth: hci0: request failed to create LE connection: status 0x0c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1835449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1836372] [NEW] Update firmware in nic-firmware udeb for 5.0 hwe kernel
Public bug reported: SRU Justification Impact: Recent updates to linux-firmware means that there are new and updated firmware files relevant to the 5.0 hwe kernel from disco. Adding these files to give a better install experience for the 18.04.3 release. Fix: Add the new firmware files to the nic-firmware udeb. Test Case: Confirm that the new files are present in the nic-firmware udeb. Regression Potential: New firmware versions could contain regressions. These versions have already been released into bionic with no reported regressions though, and are known to fix actual problems, so the benefit seems to outweigh the potential risk. ** Affects: linux-firmware (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress -- 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/1836372 Title: Update firmware in nic-firmware udeb for 5.0 hwe kernel Status in linux-firmware package in Ubuntu: In Progress Bug description: SRU Justification Impact: Recent updates to linux-firmware means that there are new and updated firmware files relevant to the 5.0 hwe kernel from disco. Adding these files to give a better install experience for the 18.04.3 release. Fix: Add the new firmware files to the nic-firmware udeb. Test Case: Confirm that the new files are present in the nic-firmware udeb. Regression Potential: New firmware versions could contain regressions. These versions have already been released into bionic with no reported regressions though, and are known to fix actual problems, so the benefit seems to outweigh the potential risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel
** Description changed: SRU Justification Impact: Recent updates to linux-firmware means that there are new and updated firmware files relevant to the 5.0 hwe kernel from disco. Adding - these files may give a better install experience for the 18.04.3 - release. + these files to give a better install experience for the 18.04.3 release. Fix: Add the new firmware files to the nic-firmware udeb. Test Case: Confirm that the new files are present in the nic-firmware udeb. Regression Potential: New firmware versions could contain regressions. These versions have already been released into bionic with no reported regressions though, and are known to fix actual problems, so the benefit seems to outweigh the potential risk. ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Bionic) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux-firmware (Ubuntu Bionic) Importance: High => Medium ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Invalid -- 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/1836372 Title: Update firmware in nic-firmware udeb for 5.0 hwe kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Bug description: SRU Justification Impact: Recent updates to linux-firmware means that there are new and updated firmware files relevant to the 5.0 hwe kernel from disco. Adding these files to give a better install experience for the 18.04.3 release. Fix: Add the new firmware files to the nic-firmware udeb. Test Case: Confirm that the new files are present in the nic-firmware udeb. Regression Potential: New firmware versions could contain regressions. These versions have already been released into bionic with no reported regressions though, and are known to fix actual problems, so the benefit seems to outweigh the potential risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel
** Changed in: linux-firmware (Ubuntu) Status: Invalid => Fix Committed -- 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/1836372 Title: Update firmware in nic-firmware udeb for 5.0 hwe kernel Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: In Progress Bug description: SRU Justification Impact: Recent updates to linux-firmware means that there are new and updated firmware files relevant to the 5.0 hwe kernel from disco. Adding these files to give a better install experience for the 18.04.3 release. Fix: Add the new firmware files to the nic-firmware udeb. Test Case: Confirm that the new files are present in the nic-firmware udeb. Regression Potential: New firmware versions could contain regressions. These versions have already been released into bionic with no reported regressions though, and are known to fix actual problems, so the benefit seems to outweigh the potential risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)
@Warren - If you still experience the issue with linux-firmware 1.173.8 then it must not be exactly the same issue, so please open a new bug. -- 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/1829737 Title: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560) Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Bug description: SRU Justification [Impact] The firmware blob for Intel Bluetooth 9560/9462 is versioned 20.30.0.1 is not compatible with kernel version >= 4.19 and will cause failure to pair BT 4.0 devices. [Fix] 29a536a02cad linux-firmware: Update firmware file for Intel Bluetooth 9560 Above upstream change contains latest firmware file for Intel Bluetooth 9560 that fixes HID pairing in recent kernel versions. [Test Case] Copy ibt-17-16-1.sfi blob to /lib/firmware/intel and do a cold boot to reload firmware. One should find following message in dmesg: Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015 This indicates firmware reload has been activated. For further warm boots, kernel would dump updated revision: Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019 And perform BT 4.0 device pairing for functional tests. Tested blob against following kernel versions: * 5.0.0-1004-oem-osp1 * 5.0.0-15-generic * 4.18.0-20-generic * 4.15.0-1038-oem * 4.15.0-50-generic [Regression Risk] Low. This affects only Intel JeffersonPeak Bluetooth chip series, namely 9461/9462/9560, which are the hardware variants to be fixed. --- For kernel version >= 4.19, it fails to pair with BT4.0 HID devices and leave error messages in syslog: Bluetooth: hci0: request failed to create LE connection: status 0x0c Which can be detailed by btmon: < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 [hci0] 30.895622 Filter policy: White list is not used (0x00) Own address type: Public (0x00) Peer address type: Random (0x01) Peer address: DB:DD:51:2D:1C:CC (Static) Initiating PHYs: 0x01 Entry 0: LE 1M Scan interval: 60.000 msec (0x0060) Scan window: 60.000 msec (0x0060) Min connection interval: 30.00 msec (0x0018) Max connection interval: 50.00 msec (0x0028) Connection latency: 0 (0x) Supervision timeout: 420 msec (0x002a) Min connection length: 0.000 msec (0x) Max connection length: 0.000 msec (0x) > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453 LE Extended Create Connection (0x08|0x0043) ncmd 1 Status: Command Disallowed (0x0c) Indicating this is actually a firmware problem. Verified this has been fixed at least in upstream linux-firmware commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release version 21.10.0.6. With that firmware blob placed under /lib/firmware/intel and a cold boot, dmesg gives updated revision and device pairing works as expected: Firmware revision 0.1 build 184 week 15 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1829737/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel
Confirmed that the new files are now present in nic- firmware_1.173.9_all.udeb, marking verification done. ** Tags added: verification-done-bionic -- 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/1836372 Title: Update firmware in nic-firmware udeb for 5.0 hwe kernel Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Bug description: SRU Justification Impact: Recent updates to linux-firmware means that there are new and updated firmware files relevant to the 5.0 hwe kernel from disco. Adding these files to give a better install experience for the 18.04.3 release. Fix: Add the new firmware files to the nic-firmware udeb. Test Case: Confirm that the new files are present in the nic-firmware udeb. Regression Potential: New firmware versions could contain regressions. These versions have already been released into bionic with no reported regressions though, and are known to fix actual problems, so the benefit seems to outweigh the potential risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835345] Re: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
@AceLan: Why did you change the status to fix released when the packages are still in proposed? Setting them back to fix committed. If you want the package to release you need to mark verification done, not change the status. ** Changed in: linux-firmware (Ubuntu Bionic) Status: Fix Released => Fix Committed ** Changed in: linux-firmware (Ubuntu Disco) Status: Fix Released => Fix Committed -- 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/1835345 Title: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] BT fails to enable again after disabled it by hotkey with the following message Bus 001 Device 004: ID 8087:0029 Intel Corp. [248987.643125] usb 1-10: device descriptor read/64, error -110 [249003.247721] usb 1-10: device descriptor read/64, error -110 [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249018.855466] usb 1-10: device descriptor read/64, error -110 [249034.467589] usb 1-10: device descriptor read/64, error -110 [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249045.299399] usb 1-10: device not accepting address 4, error -62 [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249050.675715] usb 1-10: Device not responding to setup address. [249050.883541] usb 1-10: device not accepting address 4, error -71 [Fix] Found the updated firmware fixes the issue [Test] Verify on the machine couple days, and can't duplicate the issue anymore. [Regression Potential] Low, the system keeps running for 5 days, and pass s3 tests 30 times, everything works well. [Misc] The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards require the new fw_revision, so SRU both of them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836622] [NEW] Eoan update: v5.2.1 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.1 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** 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 ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836622 Title: Eoan update: v5.2.1 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress 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.1 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836622] Re: Eoan update: v5.2.1 upstream stable release
** Changed in: linux (Ubuntu Eoan) 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/1836622 Title: Eoan update: v5.2.1 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed 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.1 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -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/1835700 Title: linux: 5.2.0-8.9 -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: New Status in linux source package in Eoan: New 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 phase: Testing phase-changed: Tuesday, 09. July 2019 22:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL
** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Cosmic) Status: In Progress => Won't Fix ** Changed in: linux-firmware (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1835879 Title: Intel Wireless-AC 9462/9560 not supported on ICL Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Won't Fix Bug description: [Impact] Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake platforms. [Fix] Two changes from Intel maintained backport-iwlwifi repository are necessary to add device ID/configs to iwlwifi driver. [Test] Verified on hardware 9462/9560 on IceLake/CometLake platforms. [Regression Potential] Low. These changes are part of the series to enable 9462/9560 on CometLake/IceLake platforms that don't have the support originally. = Original Bug Description = Intel Wireless-AC 9462/9560 on CML was previously enabled via bug 1833065, bug 1834415 and bug 1834464. However on ICL, it fails to startup with following error messages with kernel v5.2-rc7: iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338 iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3 iwlwifi :00:14.3: Failed to start RT ucode: -5 iwlwifi :00:14.3: Collecting data: trigger 16 fired. iwlwifi :00:14.3: Firmware not running - cannot dump error iwlwifi :00:14.3: Failed to run INIT ucode: -5 Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at the moment) with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Changed in: linux (Ubuntu Eoan) 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/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Fix Committed 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: In Progress Status in linux source package in Eoan: Fix Committed Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of many patches with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4) and fio (sequential + random read-write). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836020] Re: Sometimes touchpad(goodix) can't use tap function
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1836020 Title: Sometimes touchpad(goodix) can't use tap function Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: New Bug description: [Impact] Wake up from runtime suspend, Goodix doesn't report correct Tap event by tapping it the first time, so if you double tap the touchpad, the system only got one tap. [Fix] Adding the platforms which uses Goodix touchpad IC to the i2c designware quirk list. [Test] Verified on the buggy machines. [Regression Potential] Low, this quirk doesn't hurt anything and do little or none to power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836020/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836152] Re: Intel ethernet I219 has slow RX speed
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- 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/1836152 Title: Intel ethernet I219 has slow RX speed Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Confirmed Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Confirmed Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Bug description: [Impact] RX speed on Intel ethernet I219 v6 is extremely slow due to multiple RX CRC errors. [Fix] Disable e1000e K1 feature to make I219 and PCH operate at higher speed to avoid the issue. [Test] Before applying the patch, the RX is slower than 150Kbps. After applying the fix the RX speed can achive gigabits. [Regression Potential] Low. This only applies to recent I219 generations. I've also test several other systems with e1000e and I don't see any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836308] Re: Unhide Nvidia HDA audio controller
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- 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/1836308 Title: Unhide Nvidia HDA audio controller Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: New Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Bug description: [Impact] Nvidia HDA audio controller comes with Nvidia graphics cannot be found by PCI subsystem. [Fix] Write bit 25 at graphics' config space offset 0x488 to enable the HDA controller. [Test] Nvidia HDA controller is not listed under lspci. After applying the fix lspci can find Nvidia HDA controller. [Regression Potential] Low. This fix doesn't bring any functional change other then exposing HDA controller at hardware level. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836177] Re: Intel ethernet I219 may wrongly detect connection speed as 10Mbps
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- 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/1836177 Title: Intel ethernet I219 may wrongly detect connection speed as 10Mbps Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Incomplete Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Bug description: [Impact] Intel I219 ethernet may wrongly detect 1Gbps network as 10Mbps after ethernet cable hotplugging. [Fix] Use delayed work before deciding the network speed. This essentially workarounds unreliable reading on MII_BMSR register. [Test] Before the patch the network operates at 10Mbps after cable gets plugged. With the fix, network always operates in 1Gbps. [Regression Potential] Low. It changes the watchdog task from timer to delayed work, the logic is essentially the same. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835054] Re: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64
** Changed in: linux (Ubuntu Eoan) 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/1835054 Title: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Committed Bug description: == SRU Justification == The mvpp2 is a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040. However this driver was neither enabled as a module or a built-in for Disco arm64. == Fix == Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can solve this problem. We need to enable the Armada SOCs support (CONFIG_ARCH_MVEBU) as well to meet the dependency requirement. Other configs were added by the updateconfigs process. == Test == A test kernel for Disco ARM64 could be found here: https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/V2/ User has confirmed that the V1 kernel can fix this missing driver issue (V2 is just with CONFIG_ARCH_MULTI_V7 dropped and some configs added explicitly, I have it tested on an ARM64 node, the mvpp2 module can be loaded without any issue). == Regression Potential == Low, this patch just enable the Armada SOCs and make this mvpp2 driver to be built as a module on ARM64, and we already have those for armhf. == Original Bug Report == At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) - a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040 - neither as a module or a built-in: $ uname -m aarch64 $ grep MVPP2 /boot/config-5.0.0-20-generic $ It makes very hard (and impossible for non-advanced users) to install and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a reasonably priced and performant server/mini-desktop platform. Could it be added, please, and the installer image re-generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: hibmc-drm Causes Unreadable Display for Huawei amd64 Servers
** Changed in: linux (Ubuntu Eoan) 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/1762940 Title: hibmc-drm Causes Unreadable Display for Huawei amd64 Servers Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1762940 [Impact] amd64 based Huawei servers have problems where the display output of their iBMC chips is broken, resulting in a "blurry" screen when viewed from their in house remote kvm-like console. Example: https://launchpadlibrarian.net/365907668/creen_picture_for_blur.png The issue is caused by the hibmc_drm kernel module being loaded. The PCI ID for the iBMC chips on amd64 hardware is the same as arm64 hardware, but the hibmc_drm driver was developed only for use on arm64 hardware, most notably for the Huawei D05 development board. The impact to Huawei is that their customers cannot use Ubuntu server install media as the screen goes "blurry" when the d-i install media or subuqity installer loads the hibmc_drm kernel module after language selection. The only workaround for their customers is to press the "E" key during the very first installer menu and adding "modprobe.blacklist=hibmc_drm" to the kernel command line in the grub menu. This is not good for customer experience with their servers. Other problems exist for the hibmc_drm driver on amd64, such as working on bios, but not uefi, and not being wayland compatible, making the screen blurry whenever a desktop session is started and gdm loaded. Huawei have asked us to remove hibmc_drm from all architectures except arm64, and this aligns with advice from Hisilicon. [Fix] I modified the config/annotations file to remove all architectures except arm64, and created a patch for Kconfig to set a firm requirement on ARM64 for hibmc_drm. I will send the Kconfig patch upstream in the coming days for a more permanent fix. [Testcase] Apply the patches and run: ubuntu-bionic/CONFIGS$ fakeroot debian/rules genconfigs ubuntu-bionic/CONFIGS$ grep -Rin "hibmc" . ./arm64-config.flavour.generic:5739:CONFIG_DRM_HISI_HIBMC=m You should see that only arm64 has the config option enabled. A test kernel has been built, and is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf232667-test Huawei requested a test d-i install iso to test server install with, which can be found here and uses the kernel from the ppa above: https://people.canonical.com/~mruffell/sf232667_ubuntu_server_d-i_20190711b1.iso Both the test kernel and the custom d-i install iso have been tested on amd64 Huawei server hardware successfully and video output is functional. [Regression Potential] Regressions will be limited to hardware containing the iBMC chips from Hisilicon, which I believe are exclusive to Huawei servers. I have taken care to ensure that hibmc_drm is enabled for ARM64 so it should not impact kernels built for the Huawei D05 arm64 development board, and d-i will still load the hibmc_drm driver during startup for arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836755] Re: hda/realtek: can't detect external mic on a Dell machine
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1836755 Title: hda/realtek: can't detect external mic on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The external can't be detected when plugging headset in the front audio jack. [Fix] apply the alc891 fixup to set headset-mic and headpphone-mic pins. [Test Case] apply this patch and boot with the kernel, plug the headset-mic and choose headset-mic from popup dialogue, the headset-mic can record sound very well. [Regression Risk] Low. this patch is specific to a dell machine by pin configuration definition. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
This driver is not useful for s390 so we should not change the kernel config just to get it building. An example was posted of how to disable a dkms build based on whether a required option is enabled the the kernel config, here: https://bugs.launchpad.net/ubuntu/+source/acpi- call/+bug/1830040/comments/8 I think we should try something similar here. ** Also affects: ddcci-driver-linux (Ubuntu) Importance: Undecided Status: New ** Changed in: ddcci-driver-linux (Ubuntu) Importance: Undecided => High ** Changed in: ddcci-driver-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/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in ddcci-driver-linux package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1837073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836914] Re: Doing multiple squashfs (and other loop?) mounts in parallel breaks
I confirmed the issue and that reverting the patch fixed it. I've pushed a revert as a temporary fix, Kai-Heng please keep me posted on the activity upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836914 Title: Doing multiple squashfs (and other loop?) mounts in parallel breaks Status in linux package in Ubuntu: Confirmed Bug description: On a system running a 5.2 kernel, doing a large number of mounts of squashfs filesystems in parallel results in the mounts getting out of sync with their backing devices. To reproduce, https://paste.ubuntu.com/p/VCpzGxvy6h/ this breaks people with ~40 snaps (easily achievable given snapd leaves up to 3 previous revisions of snaps mounted at any given time, so a person with ~13 snaps that get updated often will hit this number). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 15:11:15 2019 InstallationDate: Installed on 2019-07-17 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190716) IwConfig: ens3 no wireless extensions. lono wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9618ebbb-955d-4daf-b29a-37162ec7821a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up [9df0:0034]
** Changed in: linux-firmware (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up [9df0:0034] Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Bug description: SRU Justification: [Impact] Bluetooth for Intel Wireless-AC 9560 variant 9df0:0034 still fails to pair BT LE HID devices on recent (>= 4.19) kernel. [Fix] Bluetooth firmware REL0450 or newer is required to fix this issue. [Test Case] Install new firmware blob to /lib/firmware/intel, shutdown the machine completely and wait for a couple minutes to trigger firmware reloading at the next boot. Then perform Bluetooth LE HID devices pairing to verify if the proposed fw fixes this issue. [Regression Risk] Low. This affects only sub models of Intel JeffersonPeak Bluetooth chip series using these firmware blobs. == Original Bug Description == This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.207801] Bluetooth: BNEP filters: protocol multicast [ 15.207804] Bluetooth: BNEP socket layer initialized [ 22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 22.040232] Bluetooth: HIDP socket layer initialized [ 22.042238] input: Logitech K810 Keyboard as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27 [ 22.042996] input: Logitech K810 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28 [ 22.043235] input: Logitech K810 System Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29 [ 22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a [ 29.296700] Bluetooth: RFCOMM TTY layer initialized [ 2
[Kernel-packages] [Bug 1836983] Re: [Intel CyclonePeak] Pairing new BT mouse fails sometimes
** Changed in: linux-firmware (Ubuntu) Status: New => Fix Committed ** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1836983 Title: [Intel CyclonePeak] Pairing new BT mouse fails sometimes Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] After update the BT firmware, it requires to pair twice to pair a new device. There should be a "SMP: Pairing Request" send from hci0, but it doesn't be submitted in the first time. [Fix] The new firmware fix this issue. [Test] Verified on Dell platforms with BT Designer Mouse(DF:29:ED:BD:82:95) [Regression Potential] Low, the firmware is newly added for new Cyclone Peak wifi/bt, and it won't affect the devices on the market currently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834476] Re: Add nvidia-418 dkms build support to disco
** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1834476 Title: Add nvidia-418 dkms build support to disco Status in linux package in Ubuntu: Fix Committed Status in linux-restricted-modules package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-restricted-modules source package in Disco: Fix Committed Bug description: SRU Justification Impact: The nvidia-graphics-drivers-418 package landed in disco shortly before release and was not included in linux-restricted- modules, though it is wanted there. Fix: Update the linux and linux-restricted-modules packages to include nvidia-graphics-drivers-418. Test Case: Confirm that binary packages for nvidia-418 are built and function as expected, and confirm that nvidia-390 continue to work as before. A test build is available in ppa:sforshee/test-builds. Regression Potential: The nvidia-418 packages are new binary packages which must be installed by the user, so they cannot cause regressions. There is a risk of inadvertent errors affecting the nvidia-390 packages, however regression testing has turned up no such regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834476] Re: Add nvidia-418 dkms build support to disco
Confirmed that the nvidia-418 lrm packages were built, install fine, and load as expected when signed module enforcement is in effect. I lack hardware to test whether the module works as expected with supported hardware, but that is really beyond the scope of this bug anyway. Also confirmed the same set of functionality with the nvidia-390 module to confirm regressions were not introduced there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1834476 Title: Add nvidia-418 dkms build support to disco Status in linux package in Ubuntu: Fix Committed Status in linux-restricted-modules package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-restricted-modules source package in Disco: Fix Committed Bug description: SRU Justification Impact: The nvidia-graphics-drivers-418 package landed in disco shortly before release and was not included in linux-restricted- modules, though it is wanted there. Fix: Update the linux and linux-restricted-modules packages to include nvidia-graphics-drivers-418. Test Case: Confirm that binary packages for nvidia-418 are built and function as expected, and confirm that nvidia-390 continue to work as before. A test build is available in ppa:sforshee/test-builds. Regression Potential: The nvidia-418 packages are new binary packages which must be installed by the user, so they cannot cause regressions. There is a risk of inadvertent errors affecting the nvidia-390 packages, however regression testing has turned up no such regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836836] Re: First click on Goodix touchpad doesn't be recognized after runtime suspended
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1836836 Title: First click on Goodix touchpad doesn't be recognized after runtime suspended Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Confirmed Status in linux-oem-osp1 source package in Disco: Invalid Bug description: [Impact] Wake up from runtime suspend, Goodix doesn't report correct Tap event by tapping it the first time, so if you double tap the touchpad, the system only got one tap. [Fix] Adding one missing platform which uses Goodix touchpad IC to the i2c designware quirk list. [Test] Verified on the buggy machines. [Regression Potential] Low, this quirk doesn't hurt anything and do little or none to power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836760] Re: ixgbe{vf} - Physical Function gets IRQ when VF checks link state
** Changed in: linux (Ubuntu Eoan)
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/1836760
Title:
ixgbe{vf} - Physical Function gets IRQ when VF checks link state
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in FF-Series:
Fix Committed
Bug description:
[Impact]
* Intel NICs that are SR-IOV capable and are managed by ixgbe driver presents
a potentially harmful behavior when the ixgbevf-managed VFs (Virtual Functions)
perform an ethtool link check. The ixgbevf driver issues a mailbox command in
the ethtool link state handler, which induces one IRQ in the PF (Physical
Function) per link check.
* This was reported as a sort of "denial-of-service" from a guest; due to
some link check loop running inside a guest with PCI-PT of a ixgbevf-managed
VF, the host received a huge amount of IRQs causing soft-lockups.
* The patch proposed in this SRU request fix this behavior by relying in the
saved link state (obtained in the ixgbevf's watchdog routine) instead of
issuing a mailbox command to the PF in every link state check request. The
commit is available on Linus tree: 1e1b0c658d9b ("ixgbevf: Use cached link
state instead of re-reading the value for ethtool")
http://git.kernel.org/linus/1e1b0c658d9b
[Test case]
Reproducing the behavior is pretty simple; having a machine with an
Intel NIC managed by ixgbe, proceed with the following steps:
a) Create one or more VFs
(echo 1 > /sys/class/net//device/sriov_numvfs)
b) In a different terminal, monitor the non-TxRx PF IRQs:
(watch -n1 "cat /proc/interrupts | grep | grep -v Tx")
c) Run "ethtool " in a loop
Without the hereby proposed patch, the PF IRQs will increase.
[Regression potential]
The patch scope is restricted to ixgbevf ethtool link-check procedure,
and was developed by the vendor itself. Being a self-contained patch
affecting only this driver's ethtool handler, the worst potential
regression would be a wrong link state report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836760/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836916] Re: alsa/hdmi: add icelake hdmi audio support for a Dell machine
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1836916 Title: alsa/hdmi: add icelake hdmi audio support for a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: New Status in linux-oem-osp1 source package in Disco: Invalid Bug description: [Impact] On a Dell icelake platform, the hdmi audio doesn't work at all, when users plug hdmi cable, they can't find hdmi audio from gnome-sound-setting. [Fix] add icl hdmi audio id and related support patch to alsa driver. [Test Case] after applying the patchset, we plug hdmi cable and the hdmi audio shows up in the sound-setting and works well, after unplugging the cable, the hdmi audio disappears as expected. [Regression Risk] Low. this patchset is specific to a icl hdmi audio codec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835001] Re: System does not auto detect disconnection of external monitor
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- 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/1835001 Title: System does not auto detect disconnection of external monitor Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Bug description: [Impact] System does not auto detect disconnection of external monitor Steps to reproduce: 1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS 2. open "system settings > display settings" 3. connect laptop to an external HDMI monitor via HDMI port & cable 4. unplug the HDMI cable 5. check if "display settings" automatically detects the removal of the external monitor Expected result: display settings should automatically detect the removal of external monitor when unplugging the HDMI cable Actual result: System does not automatically detect the removal of the external monitor when HDMI cable is removed. Sound setting also list HDMI audio in output tab after removal external monitor. Failure rate: 2/10 to 1/10 [Fix] two commits from upstream drm-intel-next-queued branch [Test case] see "steps to reproduce" [Regression potential] still possible, but for the distro only Eoan will get it. OEM kernels will get tested on systems that get it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836752] Re: input/mouse: alps trackpoint-only device doesn't work
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1836752 Title: input/mouse: alps trackpoint-only device doesn't work Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Bug description: [Impact] On one of the latest Lenovo laptops, the trackpoint doesn't work, we consulted apls guys, they said this trackpoint is different from others, it is a trackpoint-only device, so the current alps.c doesn't support it well, while the trackpoint.c can drive it well. [Fix] Check if it is trakcpoint-only device, if it yes, let trackpoint.c handle it. [Test Case] apply this patch and boot with the kernel, the trackpoint can work well. [Regression Risk] Low. the way of detect trackpoint-only alps device is provided by alps. so it is pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
We need a fix to the dkms test script. When the build is skipped due to the BUILD_EXCLUSIVE directive the tar command fails, causing the script to fail since it contains "set -eu". I'd suggest we do something like the attached. ** Patch added: "dkms_2.7.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837073/+attachment/5278140/+files/dkms_2.7.1-1ubuntu2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in ddcci-driver-linux package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1837073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837440] Re: linux firmware 1.178.3 seems to break WPA enterprise
There haven't been any updates to the firmware for your wireless hardware since 1.178, so it seems unlikely that the linux-firmware update would be responsible. Let's see how your testing turns out though. -- 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/1837440 Title: linux firmware 1.178.3 seems to break WPA enterprise Status in linux-firmware package in Ubuntu: New Bug description: Seen on intel Wireless-N 2230 BGN (rev c4). After the update to said linux firmware version I had issues in connecting to the WPA enterprise wifi networks EDUROAM and ALMAWIFI. EDUROAM is the European universities Wi-Fi network. Ability to connect to non enterprise network is unaffected. Downgrading to 1.178 seems to restore proper functionality. In the next days I'll try further checks to see if the firmware is really the sole trigger for the issue. In the meantime, I am tentatively opening the bug in case others have my same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 22 19:27:16 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2047 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to disco on 2019-06-12 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1837440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
Since this seems like a bug in the firmware, you should report this issue to Intel as described here: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging Please post a link to the bug here so I can keep track of the status. Thanks! -- 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/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320172] iwlwifi :3b:00.0: 0x0001A7D2 | data1 Jul 17 15
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
@thedarb: To you, since you have the hardware to work with them to diagnose the problem. @kerneltoast: Sometimes these firmware crashes look the same but have different underlying causes, so imo it's better to go ahead and report it and let the Intel devs sort out whether or not it's actually a duplicate. -- 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/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320
Re: [Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
On Mon, Jul 22, 2019 at 09:45:49PM -, Sultan Alsawaf wrote: > @sforshee I've actually got the same hardware :) In that case either one of you can create the upstream bug I suppose. -- 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/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320172] iwlwifi :3b:00.0: 0x0001A7D2 | data1 Jul 17 15:13:31 Lappy kernel: [ 85.320173] iwlwifi :3b:00.0: 0x
[Kernel-packages] [Bug 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
Yes I saw, it seems to be behaving differently than when I tested those changes locally. Will try to investigate today. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in ddcci-driver-linux package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1837073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837440] Re: linux firmware 1.178.3 seems to break WPA enterprise
If it is a regression due to recent updates then trying to isolate which package caused the regression may be the best way to start. You can check /var/log/apt/history.log* to try and determine what packages were upgraded around the time you started experiencing issues. The most likely candidates are probably linux, wpasupplicant, or network-manager. I'm going to change the affected task to linux for now, then if you run 'apport-collect 1837440' in a terminal your system will attach logs which may be relevant to this bug report. Try to do it after you've been experiencing the connection issues, without rebooting. I know that this can be tricky when the problem is with networking -- perhaps you can connect to a different network or use a wired connection. ** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) -- 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/1837440 Title: linux firmware 1.178.3 seems to break WPA enterprise Status in linux package in Ubuntu: Incomplete Bug description: Seen on intel Wireless-N 2230 BGN (rev c4). After the update to said linux firmware version I had issues in connecting to the WPA enterprise wifi networks EDUROAM and ALMAWIFI. EDUROAM is the European universities Wi-Fi network. Ability to connect to non enterprise network is unaffected. Downgrading to 1.178 seems to restore proper functionality. In the next days I'll try further checks to see if the firmware is really the sole trigger for the issue. In the meantime, I am tentatively opening the bug in case others have my same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 22 19:27:16 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2047 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to disco on 2019-06-12 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822680] Re: Detect SMP PHY control command errors
** 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/1822680 Title: Detect SMP PHY control command errors Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] Errors from SMP PHY control commands (e.g. enabling, disabling, resetting phy links) are currently ignored. This is likely to escalate into problems later in driver initialization - mostly around reset paths. By logging a message and returning an error, it should be easier to root cause failures, as well as avoiding continued use of a phy that has failed to reset. [Test Case] Regression testing only on a system that uses a libsas-based driver (hisi_sas) [Fix] 01929a65dfa13 scsi: libsas: Check SMP PHY control function result [Regression Risk] Restricted to systems w/ libsas-based drivers (mvsas, hisi_sas, aic94xx). A possible risk is that a system was previously functioning normally even though SMP PHY control commands were failing, and now we'd be logging an error an aborting the operation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822692] Re: Please ship the ib_uverbs driver module in the main modules package
** Changed in: linux-aws (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1822692 Title: Please ship the ib_uverbs driver module in the main modules package Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Xenial: In Progress Status in linux-aws source package in Bionic: In Progress Status in linux-aws source package in Cosmic: In Progress Status in linux-aws source package in Disco: Fix Committed Bug description: Please include the module drivers/infiniband/core/ib_uverbs.ko and its companion ib_umad.ko in the main linux-modules-*-aws package, in order to support upcoming Amazon features. +++ b/debian.aws/control.d/aws.inclusion-list +drivers/infiniband/core/ib_umad.ko +drivers/infiniband/core/ib_uverbs.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1822692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787775] Re: touchpad not working on lenovo yoga 530
** Changed in: linux (Ubuntu Disco) Status: Confirmed => 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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Fix Committed Bug description: === SRU Justification === [Impact] AMD MP2 I2C driver doesn't support more than one bus. This makes touchpad on Lenovo Yoga 530 doensn't work as expected. [Fix] Sync the MP2 driver with upstream version. [Test] The new upstream driver doesn't break on Latitude 5495. Users haven't given any feedback yet, but since Disco is freezing I am sending this out. [Regression Potential] Low. It's from upstream, and only a subset of Raven Ridge has this device. === Original Bug Report === The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820868] Re: bionic: fork out linux-snapdragon into its own topic kernel
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux-meta (Ubuntu) Status: New => Fix Committed ** Changed in: linux-snapdragon (Ubuntu) Status: New => 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/1820868 Title: bionic: fork out linux-snapdragon into its own topic kernel Status in linux package in Ubuntu: Fix Committed Status in linux-meta package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux-meta source package in Bionic: New Status in linux-snapdragon source package in Bionic: In Progress Bug description: Impact: During the Bionic cycle, a decision was made to incorporate the linux-snapdragon kernel into the master branch, thus reducing the number of topic kernels and the stable maintenance burden. But as time passed and new patches were produced by Qualcomm, incorporating them into master while avoiding to destabilize generic became more and more problematic, down to the point where it was not a viable approach anymore. At that point, the decision was made to fork out linux-snapdragon into its own topic kernel (e.g. linux-raspi2), giving more room to incorporate new code coming from the Qualcomm tree and avoiding to destabilize any other target in generic. Fix: This is a three step process: 1) disable building linux-snapdragon from master by applying the attached patch to bionic/master 2) create a new bionic/linux-snapdragon branch and reset hard to my lp:snapdragon-topic-kernel branch (see below) 3) update bionic-meta to point to the new bionic/linux-snapdragon kernel Regression potential From the point of view of bionic/master, this pull request doesn't introduce any substantial change, and in the future will let us purge generic from several external patches. While from the point of view of linux-snapdragon, with ~600 code commits and ~4k config changes, this represent a brand new kernel and while great care was used while putting together this branch, there's clearly a regression potential here but we can't leave linux-snapdragon stagnate behind the curve, so the sooner we bite the bullet, the better we can the deal with the eventual fallout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade
@Hui does the test driver in comment #13 add 1002:437b to power_save_blacklist? From the duped bug seems we also want to add 8086:a170 to the blacklist as well, or else change CONFIG_SND_HDA_POWER_SAVE_DEFAULT back to 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/1821663 Title: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: I'm experiencing a repeating crackling noise after 19.04 upgrade that start just after the boot and before the login. I tried a bunch of fixes for pulseaudio I found googling, including this one https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling and this one https://askubuntu.com/questions/864608/audio-crackle-through-headphones. Neither of which helped. The command "killall pulseaudio" usually stop the noise for 10 seconds, then the noise restart. The system was running smoothly on 18.10 Alessandro- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 3310 F pulseaudio /dev/snd/controlC0: alessandro 3310 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 03:29:00 2019 InstallationDate: Installed on 2016-07-09 (989 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade
Ok, I guess I got the wrong id. Can you also add the ids from the duped bug so that can be tested too? https://launchpadlibrarian.net/417429198/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821663 Title: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: I'm experiencing a repeating crackling noise after 19.04 upgrade that start just after the boot and before the login. I tried a bunch of fixes for pulseaudio I found googling, including this one https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling and this one https://askubuntu.com/questions/864608/audio-crackle-through-headphones. Neither of which helped. The command "killall pulseaudio" usually stop the noise for 10 seconds, then the noise restart. The system was running smoothly on 18.10 Alessandro- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 3310 F pulseaudio /dev/snd/controlC0: alessandro 3310 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 03:29:00 2019 InstallationDate: Installed on 2016-07-09 (989 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: In Progress Bug description: Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823056] Re: autopkgtests run too often, too much and don't skip enough
** Changed in: linux (Ubuntu) Status: New => 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/1823056 Title: autopkgtests run too often, too much and don't skip enough Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] * linux autopkgtest should only execute either rebuild tests, when triggered by toolchain. or execute regression suite when triggered by meta but never both. As otherwise, it results in false negative results for the kernel [Test Case] * Trigger adt test of linux with a matching linux-meta. Check that rebuild test is skipped, and that the regression suite test runs. * trigger adt test of linux with triggered by gcc-6/7/8 (as appropriate) and observe that rebuild test runs, and regression suite test is skipped. * (when this is applied to flavours) trigger adt test of linux-* with a matching flavour meta, and check that regression test-suite is skipped on kernels that cannot boot in scaling stack (e.g. gcp, azure, aws, etc) [Fix] * debian/tests/* are modified to pay more attention as to what they are triggered by, and raise appropriate skipped error codes [Regression Potential] * incorrect tests may run at incorrect time is the regression potential here, hence the two test cases verify that the right tests are executed when expected. * care was taken to take into account all linux kernel flavours, hence the third test case need to be reverified on flavoured kernels. [Other Info] * affects all stable series xenial and up, across all kernel flavours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
Please try the attached package. I believe you should be able to install it alone; none of the other packages look to be locked to a specific version of linux-cloud-tools-common. ** Attachment added: "linux-cloud-tools-common_5.0.0-8.9+lp1820063v201904031200_all.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+attachment/5252571/+files/linux-cloud-tools-common_5.0.0-8.9+lp1820063v201904031200_all.deb ** Changed in: linux (Ubuntu) Status: In Progress => 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/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Incomplete Bug description: Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823060] [NEW] Disco update: v5.0.6 upstream stable release
x inode bh swapping mixup in ocfs2_reflink_inodes_lock
fs/open.c: allow opening only regular files during execve()
kbuild: modversions: Fix relative CRC byte order interpretation
ALSA: hda/realtek - Fix speakers on Acer Predator Helios 500 Ryzen laptops
ALSA: hda/realtek: Enable headset MIC of ASUS X430UN and X512DK with ALC256
ALSA: hda/realtek: Enable headset mic of ASUS P5440FF with ALC256
ALSA: hda/realtek: Enable ASUS X441MB and X705FD headset MIC with ALC256
ALSA: hda/realtek - Add support for Acer Aspire E5-523G/ES1-432 headset mic
ALSA: hda/realtek: Enable headset MIC of Acer Aspire Z24-890 with ALC286
ALSA: hda/realtek: Enable headset MIC of Acer AIO with ALC286
ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB
ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO
ALSA: hda/realtek: merge alc_fixup_headset_jack to alc295_fixup_chromebook
ALSA: hda/realtek - Fixed Headset Mic JD not stable
ALSA: pcm: Don't suspend stream in unrecoverable PCM state
ALSA: pcm: Fix possible OOB access in PCM oss plugins
ALSA: seq: oss: Fix Spectre v1 vulnerability
ALSA: rawmidi: Fix potential Spectre v1 vulnerability
net: dsa: qca8k: remove leftover phy accessors
NFSv4.1 don't free interrupted slot on open
NFS: fix mount/umount race in nlmclnt.
NFS: Fix nfs4_lock_state refcounting in nfs4_alloc_{lock,unlock}data()
vfio: ccw: only free cp on final interrupt
powerpc: bpf: Fix generation of load/store DW instructions
ARM: imx6q: cpuidle: fix bug that CPU might not wake up at expected time
tracing: initialize variable in create_dyn_event()
locks: wake any locks blocked on request before deadlock check
Btrfs: fix assertion failure on fsync with NO_HOLES enabled
btrfs: Avoid possible qgroup_rsv_size overflow in
btrfs_calculate_inode_block_rsv_size
btrfs: Fix bound checking in qgroup_trace_new_subtree_blocks
btrfs: don't report readahead errors and don't update statistics
btrfs: remove WARN_ON in log_dir_items
Btrfs: fix incorrect file size after shrinking truncate and fsync
powerpc/fsl: Fix the flush of branch predictor.
tun: add a missing rcu_read_unlock() in error path
ila: Fix rhashtable walker list corruption
r8169: fix cable re-plugging issue
net: phy: don't clear BMCR in genphy_soft_reset
net: mii: Fix PAUSE cap advertisement from linkmode_adv_to_lcl_adv_t() helper
net: dsa: mv88e6xxx: fix few issues in mv88e6390x_port_set_cmode
thunderx: eliminate extra calls to put_page() for pages held for recycling
thunderx: enable page recycling for non-XDP case
vxlan: Don't call gro_cells_destroy() before device is unregistered
vrf: prevent adding upper devices
tun: properly test for IFF_UP
tipc: fix cancellation of topology subscriptions
tipc: change to check tipc_own_id to return in tipc_net_stop
tipc: allow service ranges to be connect()'ed on RDM/DGRAM
tcp: do not use ipv6 header for ipv4 flow
sctp: use memdup_user instead of vmemdup_user
sctp: get sctphdr by offset in sctp_compute_cksum
rhashtable: Still do rehash when we get EEXIST
packets: Always register packet sk in the same order
net: usb: aqc111: Extend HWID table by QNAP device
net-sysfs: call dev_hold if kobject_init_and_add success
net: stmmac: fix memory corruption with large MTUs
net: rose: fix a possible stack overflow
net: phy: meson-gxl: fix interrupt support
net/packet: Set __GFP_NOWARN upon allocation in alloc_pg_vec
net: datagram: fix unbounded loop in __skb_try_recv_datagram()
net: aquantia: fix rx checksum offload for UDP/TCP over IPv6
mISDN: hfcpci: Test both vendor & device ID for Digium HFC4S
mac8390: Fix mmio access size probe
ipv6: make ip6_create_rt_rcu return ip6_null_entry instead of NULL
gtp: change NET_UDP_TUNNEL dependency to select
genetlink: Fix a memory leak on error path
dccp: do not use ipv6 header for ipv4 flow
netfilter: nf_tables: fix set double-free in abort path
The following patches from this stable update had already been applied:
Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
btrfs: raid56: properly unmap parity page in finish_parity_scrub()
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Fix Committed
** Affects: linux (Ubuntu Disco)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Fix Committed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
[Kernel-packages] [Bug 1822897] Re: RDMA/hns updates for disco
** 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/1822897 Title: RDMA/hns updates for disco Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] A number of changes for the RDMA/hns driver landed upstream post-5.0, including a number of bug fixes, corrections for consistency w/ the hip08 SoC spec, as well as a couple new features and cleanup. I recommend we sync up the changes for disco so that we have an established base for future changes. [Test Case] Regression tested w/ perftest: = server = sudo ib_send_bw -d hns_2 -i 1 -a -F --report_gbits = client = sudo ib_send_bw -d hns_2 -i 1 -a -F --report_gbits [Fixes] 9c6ccc035c209dda07685e8dba829a203ba17499 RDMA/hns: Fix the bug with updating rq head pointer when flush cqe 4d103905eb1e4f14cb62fcf962c9d35da7005dea RDMA/hns: Bugfix for the scene without receiver queue 44754b95dd35ee07c462b5425ae9c4cde8c7e7c8 RDMA/hns: Add constraint on the setting of local ACK timeout 91fb4d83b88a7b544ce564c44167aad29d4154f0 RDMA/hns: Modify the pbl ba page size for hip08 de77503a59403e7045c18c6bb0a10c245a99b648 RDMA/hns: RDMA/hns: Assign rq head pointer when enable rq record db 2b9acb9a97fe9b4101ca020643760c4a090b4cb4 RDMA/hns: Add the process of AEQ overflow for hip08 6a157f7d1b14eb88d89fbd396cfea15ac4bded2d RDMA/hns: Add SCC context allocation support for hip08 aa84fa18741b83daf0f8f160c46ae92f4d6f1343 RDMA/hns: Add SCC context clr support for hip08 0e40dc2f70cda099e13392a26bd37aed24bcd25d RDMA/hns: Add timer allocation support for hip08 da91ddfdc7212e6e716be55a5cf2305ce84a422f RDMA/hns: Remove set but not used variable 'rst' c3c668e742397dfc107e44c09606cc68b37df30d RDMA/hns: Make some function static d061effc36f7bd38a12912977a37a50ac9140d11 RDMA/hns: Fix the Oops during rmmod or insmod ko when reset occurs 6a04aed6afaefd5fd396f23da184298135f31e37 RDMA/hns: Fix the chip hanging caused by sending mailbox&CMQ during reset d3743fa94ccd177917783726faf54632439ddb54 RDMA/hns: Fix the chip hanging caused by sending doorbell during reset 3856ec55270099494afa0cabba020365a38430a2 RDMA/hns: Use for_each_sg_dma_page iterator on umem SGL 704e0e613a6d584fde1c80ead0329e918b4f8671 RDMA/hns: Limit minimum ROCE CQ depth to 64 ab22bf05216a6bb4812448f3a8609489047cf311 RDMA/hns: Fix the state of rereg mr f7f27a5f03cc9f47cc14f75a5be25f0f26b1b5ff RDMA/hns: Set allocated memory to zero for wrid e95c716c7faa0d0eede5eabb6fea2504709e25b6 RDMA/hns: Delete useful prints for aeq subtype event dad1f9802ecee3a21143293b2505e1b57b1ae525 RDMA/hns: Configure capacity of hns device 3e394f9413ecba2779b6a1d77095f4d8611a52d2 RDMA/hns: Modify qp&cq&pd specification according to UM 6ac16e403900a98f9b330daa5f0d89f76a24c6eb RDMA/hns: Bugfix for set hem of SCC 4e69cf1fe2c52d189acdd06c1fd99cc258aba61f RDMA/hns: Use GFP_ATOMIC in hns_roce_v2_modify_qp [Regression Risk] Driver is only for HNS nics on HiSilicon SoCs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823060] Re: Disco update: v5.0.6 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.0.6 upstream stable release + from git://git.kernel.org/ -v5.0.6 upstream stable release -from git://git.kernel.org/ - - Linux 5.0.6 mt76x02u: use usb_bulk_msg to upload firmware bpf: do not restore dst_reg when cur_state is freed KVM: x86: update %rip after emulating IO KVM: x86: Emulate MSR_IA32_ARCH_CAPABILITIES on AMD hosts KVM: Reject device ioctls from processes other than the VM's creator x86/smp: Enforce CONFIG_HOTPLUG_CPU when SMP=y cpu/hotplug: Prevent crash when CPU bringup fails on CONFIG_HOTPLUG_CPU=n watchdog: Respect watchdog cpumask on CPU hotplug powerpc/pseries/mce: Fix misleading print for TLB mutlihit powerpc/64: Fix memcmp reading past the end of src/dest powerpc/pseries/energy: Use OF accessor functions to read ibm,drc-indexes objtool: Query pkg-config for libelf location perf intel-pt: Fix TSC slip perf pmu: Fix parser error for uncore event alias mm/migrate.c: add missing flush_dcache_page for non-mapped page migrate mm/page_isolation.c: fix a wrong flag in set_migratetype_isolate() mm/memory_hotplug.c: fix notification in offline error path mm/debug.c: fix __dump_page when mapping->host is not set mm: mempolicy: make mbind() return -EIO when MPOL_MF_STRICT is specified iommu/io-pgtable-arm-v7s: request DMA32 memory, and improve debugging mm: add support for kmem caches in DMA32 zone mm/hotplug: fix offline undo_isolate_page_range() usb: typec: Fix unchecked return value usb: typec: tcpm: Try PD-2.0 if sink does not respond to 3.0 source-caps usb: cdc-acm: fix race during wakeup blocking TX traffic xhci: Don't let USB3 ports stuck in polling state prevent suspend usb: xhci: dbc: Don't free all memory with spinlock held xhci: Fix port resume done detection for SS ports with LPM enabled usb: host: xhci-rcar: Add XHCI_TRUST_TX_LENGTH quirk mm/memory.c: fix modifying of page protection by insert_pfn() usb: common: Consider only available nodes for dr_mode USB: gadget: f_hid: fix deadlock in f_hidg_write() usb: mtu3: fix EXTCON dependency phy: sun4i-usb: Support set_mode to USB_HOST for non-OTG PHYs gpio: adnp: Fix testing wrong value in adnp_gpio_direction_input gpio: exar: add a check for the return value of ida_simple_get fails drm/i915/icl: Fix the TRANS_DDI_FUNC_CTL2 bitfield macro drm/i915/gvt: Fix MI_FLUSH_DW parsing with correct index check drm/i915: Mark AML 0x87CA as ULX drm/vkms: fix use-after-free when drm_gem_handle_create() fails drm/vgem: fix use-after-free when drm_gem_handle_create() fails cpufreq: scpi: Fix use after free cpufreq: intel_pstate: Also use CPPC nominal_perf for base_frequency blk-mq: fix sbitmap ws_active for shared tags drivers/block/zram/zram_drv.c: fix idle/writeback string compare fs/proc/proc_sysctl.c: fix NULL pointer dereference in put_links Disable kgdboc failed by echo space to /sys/module/kgdboc/parameters/kgdboc ACPI / CPPC: Fix guaranteed performance handling USB: serial: option: add Olicard 600 USB: serial: option: add support for Quectel EM12 USB: serial: option: set driver_info for SIM5218 and compatibles USB: serial: mos7720: fix mos_parport refcount imbalance on error path USB: serial: ftdi_sio: add additional NovaTech products USB: serial: cp210x: add new device id serial: sh-sci: Fix setting SCSCR_TIE while transferring data serial: mvebu-uart: Fix to avoid a potential NULL pointer dereference serial: max310x: Fix to avoid potential NULL pointer dereference staging: erofs: keep corrupted fs from crashing kernel in erofs_readdir() staging: erofs: fix error handling when failed to read compresssed data staging: erofs: fix to handle error path of erofs_vmap() staging: vt6655: Fix interrupt race condition on device start up. staging: vt6655: Remove vif check from vnt_interrupt staging: speakup_soft: Fix alternate speech with other synths staging: olpc_dcon_xo_1: add missing 'const' qualifier staging: comedi: ni_mio_common:
[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset
** Changed in: xorg-server (Ubuntu) Status: Triaged => 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/1821820 Title: Cannot boot or install - have to use nomodeset Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Committed Bug description: On this 19.04 beta I have to use nomodeset to boot & install Ubuntu Budgie. This is different behaviour from 18.04 and 18.10 where it booted and installed just fine without nomodeset. Without nomodeset, grub/efi disappears, and after a while a solid rather than blinking cursor on a black screen is seen. It does not boot into a live session, nor displays the ubiquity window ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Mar 26 23:40:49 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf] InstallationDate: Installed on 2019-03-26 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823186] [NEW] Add uid shifting overlay filesystem (shiftfs)
Public bug reported: shiftfs transparently translates the on-disk ids of an underlaying filesystem into valid ids in a given user namespace. This is wanted in Ubuntu for LXD and Anbox and is targeted for inclusion in Disco. The main advantage of shiftfs is that it provides signficiant performance benefits as it lets us avoid recursively chowning the root filesystem for unprivileged containers when they are created or when their idmap is changed. This becomes very important with workloads where we are running a huge number of containers which Anbox and LXD both are currently doing. Other container runtimes will benefit from shiftfs in Ubuntu as well. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: Fix Committed ** 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/1823186 Title: Add uid shifting overlay filesystem (shiftfs) Status in linux package in Ubuntu: Fix Committed Bug description: shiftfs transparently translates the on-disk ids of an underlaying filesystem into valid ids in a given user namespace. This is wanted in Ubuntu for LXD and Anbox and is targeted for inclusion in Disco. The main advantage of shiftfs is that it provides signficiant performance benefits as it lets us avoid recursively chowning the root filesystem for unprivileged containers when they are created or when their idmap is changed. This becomes very important with workloads where we are running a huge number of containers which Anbox and LXD both are currently doing. Other container runtimes will benefit from shiftfs in Ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820187] Re: Huawei Hi1822 NIC has poor performance
** Changed in: linux (Ubuntu Disco) 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/1820187 Title: Huawei Hi1822 NIC has poor performance Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] Connect Hi1822 NIC with 10G switch but the performance is only 1-2Gb/s $ iperf -c 10.228.68.133 Client connecting to 10.228.68.133, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.228.68.116 port 56810 connected with 10.228.68.133 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 1.53 GBytes 1.32 Gbits/sec [Test Case] iperf -c [Fix] Backporting all patches from mainline for drivers/net/ethernet/huawei solves this issue. [Regression Risk] Only modify codes in drivers/net/ethernet/huawei. Lowest risk to other devices and platform without it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823218] [NEW] linux-raspi2: -proposed tracker
Public bug reported: 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: 1823228 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: linux-raspi2 (Ubuntu) Importance: Medium Status: New ** Affects: linux-raspi2 (Ubuntu Disco) Importance: Medium Status: New ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.04.04-1 kernel-sru-derivative-of-1823228 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Medium ** Tags added: disco ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: kernel-sru-cycle-d2019.04.04-1 -- 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/1823218 Title: linux-raspi2: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Disco: New 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-sr
[Kernel-packages] [Bug 1823221] [NEW] linux-gcp: -proposed tracker
Public bug reported: 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: 1823228 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-gcp (Ubuntu) Importance: Medium Status: New ** Affects: linux-gcp (Ubuntu Disco) Importance: Medium Status: New ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.04.04-1 kernel-sru-derivative-of-1823228 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-gcp (Ubuntu) Importance: Undecided => Medium ** Tags added: disco ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: kernel-sru-cycle-d2019.04.04-1 -- 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/1823221 Title: linux-gcp: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel
[Kernel-packages] [Bug 1823220] [NEW] linux-azure: -proposed tracker
Public bug reported: 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: 1823228 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: linux-azure (Ubuntu) Importance: Medium Status: New ** Affects: linux-azure (Ubuntu Disco) Importance: Medium Status: New ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.04.04-1 kernel-sru-derivative-of-1823228 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/stakeholder-signoff Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/stakeholder-signoff Assignee: (unassigned) => linux-azure stakeholder signoff (linux-azure-signoff) ** Changed in: linux-azure (Ubuntu) Importance: Undecided => Medium ** Tags added: disco ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: kernel-sru-cycle-d2019.04.04-1 -- You received this bug notification because you are a member of Kernel Pack
[Kernel-packages] [Bug 1823219] [NEW] linux-aws: -proposed tracker
Public bug reported: 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: 1823228 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Medium Status: New ** Affects: linux-aws (Ubuntu Disco) Importance: Medium Status: New ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.04.04-1 kernel-sru-derivative-of-1823228 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-aws (Ubuntu) Importance: Undecided => Medium ** Tags added: disco ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: kernel-sru-cycle-d2019.04.04-1 -- 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/1823219 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Disco: New 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: 1823228 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1823228] [NEW] linux: 5.0.0-9.10 -proposed tracker
Public bug reported: 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 1823224 (bionic/linux-hwe-edge), bug 1823227 (bionic/linux-oem-osp1) derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 (linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823223 (linux-snapdragon) -- swm properties -- ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Disco) Importance: Medium Status: New ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.04.04-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: disco ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: kernel-sru-cycle-d2019.04.04-1 ** 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 1823218 (linux-raspi2) + + -- swm properties -- ** Description changed: This bug will contain status and test resu
[Kernel-packages] [Bug 1823227] [NEW] linux-oem-osp1: -proposed tracker
Public bug reported: 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: 1823228 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:40 UTC reason: prepare-package: Stalled -- waiting for master bug ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: New ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1823228 kernel-sru-cycle-d2019.04.04-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undeci
[Kernel-packages] [Bug 1823222] [NEW] linux-kvm: -proposed tracker
Public bug reported: 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: 1823228 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Medium Status: New ** Affects: linux-kvm (Ubuntu Disco) Importance: Medium Status: New ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.04.04-1 kernel-sru-derivative-of-1823228 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-kvm (Ubuntu) Importance: Undecided => Medium ** Tags added: disco ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: kernel-sru-cycle-d2019.04.04-1 ** 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: 1823228 ** Tags added: kernel-sru-derivative-of-1823228 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1823222 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta s
[Kernel-packages] [Bug 1823218] Re: linux-raspi2: -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: 1823228 ** Tags added: kernel-sru-derivative-of-1823228 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium -- 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/1823218 Title: linux-raspi2: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Disco: New 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: 1823228 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823219] Re: linux-aws: -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: 1823228 ** Tags added: kernel-sru-derivative-of-1823228 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium -- 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/1823219 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Disco: New 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: 1823228 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823220] Re: linux-azure: -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: 1823228 ** Tags added: kernel-sru-derivative-of-1823228 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium -- 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/1823220 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Disco: New 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: 1823228 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823221] Re: linux-gcp: -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: 1823228 ** Tags added: kernel-sru-derivative-of-1823228 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium -- 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/1823221 Title: linux-gcp: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Disco: New 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: 1823228 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808886] Re: Microcode SW error detected. Restarting 0x0.
Updated firmware for bug #1808389 is in -proposed, please check whether or not this firmware solves the issue. Thanks! ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- 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/1808886 Title: Microcode SW error detected. Restarting 0x0. Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Incomplete Bug description: intel-microcode: Installed: 3.20180807a.0ubuntu0.18.04.1 Candidate: 3.20180807a.0ubuntu0.18.04.1 Version table: *** 3.20180807a.0ubuntu0.18.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.20180312.0~ubuntu18.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Version: Ubuntu 4.15.0-42.45-generic 4.15.18 Error: [ 3136.084499] rtsx_pci :06:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1 [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 source:0x [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: id=00e8 [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Transmitter ID) [ 3136.085694] pcieport :00:1d.0: device [8086:a335] error status/mask=1101/2000 [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First) [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6 [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0 [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0 [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2 [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1 [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2 [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1 [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2 [ 3166.625860] iwlwifi :00:14.3: 0x | data3 [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1 [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2 [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0 [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1 [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2 [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3 [ 3166.625944] iwlwifi :00:14.3: 0x | isr4 [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7 [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1 [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2 [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1 [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2 [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1 [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | uma
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
** No longer affects: linux-firmware (Ubuntu) -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823379] [NEW] Apparmor enforcement failure in lxc selftests
Public bug reported: The lxc apparmor tests are failing with linux 5.0.0-9.10. The test expects an open of /sys/kernel/uevent_helper to fail, but it succeeds: FAIL: lxc-tests: lxc-test-apparmor (2s) --- failed - opened /sys/kernel/uevent_helper --- Full test log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco-canonical-kernel-team- bootstrap/disco/amd64/l/lxc/20190405_07_d0e52@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823379 Title: Apparmor enforcement failure in lxc selftests Status in linux package in Ubuntu: Confirmed Bug description: The lxc apparmor tests are failing with linux 5.0.0-9.10. The test expects an open of /sys/kernel/uevent_helper to fail, but it succeeds: FAIL: lxc-tests: lxc-test-apparmor (2s) --- failed - opened /sys/kernel/uevent_helper --- Full test log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco-canonical-kernel-team- bootstrap/disco/amd64/l/lxc/20190405_07_d0e52@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823407] [NEW] net and ftrace selftests failures due to missing test modules
Public bug reported: SRU Justification Impact: The test_bpf net selftest and a couple of ftrace selftests are failing due to missing modules. These modules are only for test purposes and have no other use, so they are not wanted in the linux-modules package. Fix: Change the tests to treat the missing modules as skipped tests rather than failures. Regression Potential: Minimal, since the changes are only to test cases which are already failing. Test Case: Run the test cases with the patch applied and observe that they behave as skipped tests rather than failures. ** Affects: linux-aws (Ubuntu) Importance: High Assignee: Seth Forshee (sforshee) Status: In Progress ** Description changed: SRU Justification Impact: The test_bpf net selftest and a couple of ftrace selftests are failing due to missing modules. These modules are only for test purposes and have no other use, so they are not wanted in the linux-modules package. Fix: Change the tests to treat the missing modules as skipped tests rather than failures. Regression Potential: Minimal, since the changes are only to test cases which are already failing. + + Test Case: Run the test cases with the patch applied and observe that + they behave as skipped tests rather than failures. -- 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/1823407 Title: net and ftrace selftests failures due to missing test modules Status in linux-aws package in Ubuntu: In Progress Bug description: SRU Justification Impact: The test_bpf net selftest and a couple of ftrace selftests are failing due to missing modules. These modules are only for test purposes and have no other use, so they are not wanted in the linux- modules package. Fix: Change the tests to treat the missing modules as skipped tests rather than failures. Regression Potential: Minimal, since the changes are only to test cases which are already failing. Test Case: Run the test cases with the patch applied and observe that they behave as skipped tests rather than failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1823407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823407] Re: net and ftrace selftests failures due to missing test modules
** Changed in: linux-aws (Ubuntu) Status: In Progress => Fix Committed -- 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/1823407 Title: net and ftrace selftests failures due to missing test modules Status in linux-aws package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The test_bpf net selftest and a couple of ftrace selftests are failing due to missing modules. These modules are only for test purposes and have no other use, so they are not wanted in the linux- modules package. Fix: Change the tests to treat the missing modules as skipped tests rather than failures. Regression Potential: Minimal, since the changes are only to test cases which are already failing. Test Case: Run the test cases with the patch applied and observe that they behave as skipped tests rather than failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1823407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
** 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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: SRU Justification: [Impact] * Flow action buffer can be incorrectly resized to contain the newly added action entries: the buffer is always resized multiplying the previous size by 2, but this might be not enough if the requested size is bigger than previous_size*2, causing a buffer overflow * The fix correctly resizes the buffer to prevent the buffer overflow * Despite the subject this bug can be triggered potentially on any architecture, but it is very likely to happen on i386 running the following test case [Test Case] * run this openvswitch test case: https://launchpadlibrarian.net/416589265/lp1262692 [Fix] * Instead of resizing the buffer by a factor of 2, use max(current_size * 2, current_size + requested_size) [Regression Potential] * Fix has been tested on the affected platform and verified using slub_debug. The patch has been queued up for -stable by David Miller, it will be included upstream for the next merge window. It is also a very small patch (a one-liner basically), so backport changes are minimal. [Original bug report] This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_h
[Kernel-packages] [Bug 1823754] [NEW] Set CONFIG_RANDOM_TRUST_CPU=y
Public bug reported: SRU Justification Impact: Turning this option on will make our kernels by default trust the CPU's random number generator for the purpose of initializing the kernel's CRNG on Intel, AMD, and IBM CPUs. Users can disable this at boot time by passing random.trust_cpu=off. Turning this on has the potential to prevent getrandom(2) from blocking during early boot. This option was turned on in the master kernel shortly before disco kernel freeze; this bug is about propagating the option to derivative kernels. Regression Potential: No user-visible regressions are expected. Some security-conscious users may prefer to not trust the CPU maker's RNG, but in that case the boot options is available. Test Case: The benefit is difficult to verify empirically in Ubuntu kernels since we carry a patch to avoid problems with getrandom(2) blocking immediately following boot. However, it is possible to see whether or not the kernel used the CPU RNG for initializing the CRNG by searching for the string "random: crng done (trusting CPU's manufacturer)" in dmesg. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu) Importance: High Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- 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/1823754 Title: Set CONFIG_RANDOM_TRUST_CPU=y Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: SRU Justification Impact: Turning this option on will make our kernels by default trust the CPU's random number generator for the purpose of initializing the kernel's CRNG on Intel, AMD, and IBM CPUs. Users can disable this at boot time by passing random.trust_cpu=off. Turning this on has the potential to prevent getrandom(2) from blocking during early boot. This option was turned on in the master kernel shortly before disco kernel freeze; this bug is about propagating the option to derivative kernels. Regression Potential: No user-visible regressions are expected. Some security-conscious users may prefer to not trust the CPU maker's RNG, but in that case the boot options is available. Test Case: The benefit is difficult to verify empirically in Ubuntu kernels since we carry a patch to avoid problems with getrandom(2) blocking immediately following boot. However, it is possible to see whether or not the kernel used the CPU RNG for initializing the CRNG by searching for the string "random: crng done (trusting CPU's manufacturer)" in dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1823754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823754] Re: Set CONFIG_RANDOM_TRUST_CPU=y
** Changed in: linux-aws (Ubuntu) Importance: Undecided => High ** Changed in: linux-aws (Ubuntu) Status: New => In Progress ** Changed in: linux-aws (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux-gcp (Ubuntu) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux-kvm (Ubuntu) Importance: Undecided => High ** Changed in: linux-kvm (Ubuntu) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- 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/1823754 Title: Set CONFIG_RANDOM_TRUST_CPU=y Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: In Progress Status in linux-kvm package in Ubuntu: In Progress Bug description: SRU Justification Impact: Turning this option on will make our kernels by default trust the CPU's random number generator for the purpose of initializing the kernel's CRNG on Intel, AMD, and IBM CPUs. Users can disable this at boot time by passing random.trust_cpu=off. Turning this on has the potential to prevent getrandom(2) from blocking during early boot. This option was turned on in the master kernel shortly before disco kernel freeze; this bug is about propagating the option to derivative kernels. Regression Potential: No user-visible regressions are expected. Some security-conscious users may prefer to not trust the CPU maker's RNG, but in that case the boot options is available. Test Case: The benefit is difficult to verify empirically in Ubuntu kernels since we carry a patch to avoid problems with getrandom(2) blocking immediately following boot. However, it is possible to see whether or not the kernel used the CPU RNG for initializing the CRNG by searching for the string "random: crng done (trusting CPU's manufacturer)" in dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1823754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823754] Re: Set CONFIG_RANDOM_TRUST_CPU=y
** Changed in: linux-aws (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-kvm (Ubuntu) Status: In Progress => Fix Committed -- 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/1823754 Title: Set CONFIG_RANDOM_TRUST_CPU=y Status in linux-aws package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Fix Committed Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-kvm package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: Turning this option on will make our kernels by default trust the CPU's random number generator for the purpose of initializing the kernel's CRNG on Intel, AMD, and IBM CPUs. Users can disable this at boot time by passing random.trust_cpu=off. Turning this on has the potential to prevent getrandom(2) from blocking during early boot. This option was turned on in the master kernel shortly before disco kernel freeze; this bug is about propagating the option to derivative kernels. Regression Potential: No user-visible regressions are expected. Some security-conscious users may prefer to not trust the CPU maker's RNG, but in that case the boot options is available. Test Case: The benefit is difficult to verify empirically in Ubuntu kernels since we carry a patch to avoid problems with getrandom(2) blocking immediately following boot. However, it is possible to see whether or not the kernel used the CPU RNG for initializing the CRNG by searching for the string "random: crng done (trusting CPU's manufacturer)" in dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1823754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823379] Re: Apparmor enforcement failure in lxc selftests
** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Assignee: (unassigned) => John Johansen (jjohansen) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Description changed: + SRU Justification + + Impact: The LSM stacking patches for disco changed the values read from + /sys/module/apparmor/parameters/enabled from Y/N to 0/1. This has caused + regressions in applications which expect Y/N, as demonstrated by this + failing lxc dep8 test. + + Fix: Change the values read back from + /sys/module/apparmor/parameters/enabled to Y/N. + + Regression Potential: Minimal, the change is straightforward and fixes a + regression. + + Test Case: Can be confirmed with 'cat + /sys/module/apparmor/parameters/enabled' and by running the lxc dep8 + tests and confirming that lxc-test-apparmor passes. + + --- + The lxc apparmor tests are failing with linux 5.0.0-9.10. The test expects an open of /sys/kernel/uevent_helper to fail, but it succeeds: FAIL: lxc-tests: lxc-test-apparmor (2s) --- failed - opened /sys/kernel/uevent_helper --- Full test log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco-canonical-kernel-team- bootstrap/disco/amd64/l/lxc/20190405_07_d0e52@/log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823379 Title: Apparmor enforcement failure in lxc selftests Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The LSM stacking patches for disco changed the values read from /sys/module/apparmor/parameters/enabled from Y/N to 0/1. This has caused regressions in applications which expect Y/N, as demonstrated by this failing lxc dep8 test. Fix: Change the values read back from /sys/module/apparmor/parameters/enabled to Y/N. Regression Potential: Minimal, the change is straightforward and fixes a regression. Test Case: Can be confirmed with 'cat /sys/module/apparmor/parameters/enabled' and by running the lxc dep8 tests and confirming that lxc-test-apparmor passes. --- The lxc apparmor tests are failing with linux 5.0.0-9.10. The test expects an open of /sys/kernel/uevent_helper to fail, but it succeeds: FAIL: lxc-tests: lxc-test-apparmor (2s) --- failed - opened /sys/kernel/uevent_helper --- Full test log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco-canonical-kernel-team- bootstrap/disco/amd64/l/lxc/20190405_07_d0e52@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823379] Re: Apparmor enforcement failure in lxc selftests
** 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/1823379 Title: Apparmor enforcement failure in lxc selftests Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The LSM stacking patches for disco changed the values read from /sys/module/apparmor/parameters/enabled from Y/N to 0/1. This has caused regressions in applications which expect Y/N, as demonstrated by this failing lxc dep8 test. Fix: Change the values read back from /sys/module/apparmor/parameters/enabled to Y/N. Regression Potential: Minimal, the change is straightforward and fixes a regression. Test Case: Can be confirmed with 'cat /sys/module/apparmor/parameters/enabled' and by running the lxc dep8 tests and confirming that lxc-test-apparmor passes. --- The lxc apparmor tests are failing with linux 5.0.0-9.10. The test expects an open of /sys/kernel/uevent_helper to fail, but it succeeds: FAIL: lxc-tests: lxc-test-apparmor (2s) --- failed - opened /sys/kernel/uevent_helper --- Full test log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco-canonical-kernel-team- bootstrap/disco/amd64/l/lxc/20190405_07_d0e52@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823936] [NEW] linux: 5.0.0-10.11 -proposed tracker
Public bug reported: 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 1823224 (bionic/linux-hwe-edge), bug 1823227 (bionic/linux-oem-osp1) derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 (linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 (linux-snapdragon) -- swm properties -- ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Disco) Importance: Medium Status: New ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.04.04-2 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: disco ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: kernel-sru-cycle-d2019.04.04-2 ** 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 1823224 (bionic/linux-hwe-edge) + + -- swm properties -- ** Description changed: This bug will contain status and test
[Kernel-packages] [Bug 1823227] Re: linux-oem-osp1: 5.0.0-1001.2 -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 - - WAS: kernel-stable-master-bug: 1823228 + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true + kernel-stable-master-bug: 1823936 phase: Ready for Promote to Proposed phase-changed: Tuesday, 09. April 2019 11:33 UTC reason: promote-to-proposed: Pending -- ready for review ** Tags removed: kernel-sru-backport-of-1823228 ** Tags added: kernel-sru-backport-of-1823936 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823227 Title: linux-oem-osp1: 5.0.0-1001.2 -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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New 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: 1823936 phase: Promote to Proposed phase-changed: Tuesday, 09. April 2019 13:32 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823228] Re: linux: 5.0.0-9.10 -proposed tracker
*** This bug is a duplicate of bug 1823936 *** https://bugs.launchpad.net/bugs/1823936 ** 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 1823224 (bionic/linux-hwe-edge), bug 1823227 (bionic/linux-oem-osp1) - derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 (linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823223 (linux-snapdragon) + derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 (linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm) -- swm properties -- phase: Packaging phase-changed: Thursday, 04. April 2019 20:10 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 ** This bug has been marked a duplicate of bug 1823936 linux: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823228 Title: linux: 5.0.0-9.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Disco: New 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 1823224 (bionic/linux-hwe-edge), bug 1823227 (bionic/linux-oem-osp1) derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 (linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm) -- swm properties -- phase: Packaging phase-changed: Thursday, 04. April 2019 20:10 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823221] Re: linux-gcp: -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: 1823228 + kernel-stable-master-bug: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug ** Tags removed: kernel-sru-derivative-of-1823228 ** Tags added: kernel-sru-derivative-of-1823936 -- 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/1823221 Title: linux-gcp: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Disco: New 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823219] Re: linux-aws: -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: 1823228 + kernel-stable-master-bug: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug ** Tags removed: kernel-sru-derivative-of-1823228 ** Tags added: kernel-sru-derivative-of-1823936 -- 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/1823219 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Disco: New 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823220] Re: linux-azure: -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: 1823228 + kernel-stable-master-bug: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug ** Tags removed: kernel-sru-derivative-of-1823228 ** Tags added: kernel-sru-derivative-of-1823936 -- 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/1823220 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Disco: New 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823218] Re: linux-raspi2: -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: 1823228 + kernel-stable-master-bug: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug ** Tags removed: kernel-sru-derivative-of-1823228 ** Tags added: kernel-sru-derivative-of-1823936 -- 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/1823218 Title: linux-raspi2: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Disco: New 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823222] Re: linux-kvm: -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: 1823228 + kernel-stable-master-bug: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug ** Tags removed: kernel-sru-derivative-of-1823228 ** Tags added: kernel-sru-derivative-of-1823936 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1823222 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: New 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823219] Re: linux-aws: 5.0.0-1002.2 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 5.0.0-1002.2 -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) => Seth Forshee (sforshee) ** 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) => Seth Forshee (sforshee) -- 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/1823219 Title: linux-aws: 5.0.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Disco: New 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823220] Re: linux-azure: 5.0.0-1002.2 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 5.0.0-1002.2 -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) => Seth Forshee (sforshee) ** 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) => Seth Forshee (sforshee) ** 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) => Seth Forshee (sforshee) -- 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/1823220 Title: linux-azure: 5.0.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Disco: New 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: 1823936 phase: Packaging phase-changed: Tuesday, 09. April 2019 18:41 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823222] Re: linux-kvm: 5.0.0-1002.2 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 5.0.0-1002.2 -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) => Seth Forshee (sforshee) ** 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) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1823222 Title: linux-kvm: 5.0.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: New 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823218] Re: linux-raspi2: 5.0.0-1005.5 -proposed tracker
** Summary changed: - linux-raspi2: -proposed tracker + linux-raspi2: 5.0.0-1005.5 -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) => Seth Forshee (sforshee) ** 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) => Seth Forshee (sforshee) -- 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/1823218 Title: linux-raspi2: 5.0.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Disco: New 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: 1823936 phase: Packaging phase-changed: Tuesday, 09. April 2019 21:11 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
** Description changed: - Launching a recent daily image of disco on azure results in a VM in - which the hv-kvp-daemon.service fails to start: + SRU Justification + + Impact: The KVP daemon fails to start on first boot due to being started + before the hv_kvp device appears. + + Fix: Update the hv-kvp-daemon service file to start the daemon after + device node appears. + + Regression Potential: The changes are only to the hv-kvp-daemon service + file and adding a udev rule, so the worst case regression would be that + the service does not start. In testing the service did start as + expected. + + Test Case: See comment #15. + + --- + + + Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon -Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr -Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a - Main PID: 219 (code=exited, status=1/FAILURE) + Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr + Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a + Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. - The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. - --- + --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: - + ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: - linux-restricted-modules-4.18.0-1011-azure N/A - linux-backports-modules-4.18.0-1011-azure N/A - linux-firmware N/A + linux-restricted-modules-4.18.0-1011-azure N/A + linux-backports-modules-4.18.0-1011-azure N/A + linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: In Progress Bug description: SRU Justification Impact: The KVP daemon fails to start on first boot due to being started before the hv_kvp device appears. Fix: Update the hv-kvp-daemon
[Kernel-packages] [Bug 1823221] Re: linux-gcp: 5.0.0-1002.2 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 5.0.0-1002.2 -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) => Seth Forshee (sforshee) ** 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) => Seth Forshee (sforshee) ** 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) => Seth Forshee (sforshee) -- 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/1823221 Title: linux-gcp: 5.0.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Disco: New 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: 1823936 phase: Holding before Packaging phase-changed: Thursday, 04. April 2019 19:39 UTC reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
** 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/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The KVP daemon fails to start on first boot due to being started before the hv_kvp device appears. Fix: Update the hv-kvp-daemon service file to start the daemon after device node appears. Regression Potential: The changes are only to the hv-kvp-daemon service file and adding a udev rule, so the worst case regression would be that the service does not start. In testing the service did start as expected. Test Case: See comment #15. --- Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel
All that seems to be missing is bpffilter. I've made a test build with this moved to linux-modules. It appears to be working for check- requirements. Can you test and make sure everything is working as expected? Thanks! http://people.canonical.com/~sforshee/lp1823862/ ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to use iptables/enable ufw under -virtual kernel Status in linux package in Ubuntu: Incomplete Status in ufw package in Ubuntu: Invalid Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem
*** This bug is a duplicate of bug 1823862 *** https://bugs.launchpad.net/bugs/1823862 ** This bug has been marked a duplicate of bug 1823862 disco: unable to use iptables/enable ufw under -virtual kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820114 Title: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Status in iptables package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I hit this error on disco: ``` $ free -h totalusedfree shared buff/cache available Mem: 478Mi98Mi 311Mi 0.0Ki68Mi 366Mi Swap:0B 0B 0B $ sudo iptables -S iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: iptables 1.6.1-2ubuntu3 ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Thu Mar 14 19:16:15 2019 SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 DistroRelease: Ubuntu 19.04 Package: linux PackageArchitecture: amd64 ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0 Tags: disco uec-images Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1820114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel
** Description changed: + SRU Justification + + Impact: iptables does not work in disco with linux-virtual. + + Fix: Add bpfilter to the generic inclusion list. + + Regression Potential: There are no code changes and thus minimal + potential for regressions. + + Test Case: Verify that bpffilter.ko is shipped in linux-modues instead + of linux-module-extra and that iptables commands work in disco with the + linux-virtual kernel installed. + + --- + Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=screen-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to use iptables/enable ufw under -virtual kernel Status in linux package in Ubuntu: Incomplete Status in ufw package in Ubuntu: Invalid Bug description: SRU Justification Impact: iptables does not work in disco with linux-virtual. Fix: Add bpfilter to the generic inclusion list. Regression Potential: There are no code changes and thus minimal potential for regressions. Test Case: Verify that bpffilter.ko is shipped in linux-modues instead of linux-module-extra and that iptables commands work in disco with the linux-virtual kernel installed. --- Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to use iptables/enable ufw under -virtual kernel Status in linux package in Ubuntu: In Progress Status in ufw package in Ubuntu: Invalid Bug description: SRU Justification Impact: iptables does not work in disco with linux-virtual. Fix: Add bpfilter to the generic inclusion list. Regression Potential: There are no code changes and thus minimal potential for regressions. Test Case: Verify that bpffilter.ko is shipped in linux-modues instead of linux-module-extra and that iptables commands work in disco with the linux-virtual kernel installed. --- Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824233] [NEW] linux-signed is still producing snapdragon packages
Public bug reported: SRU Justification Impact: Support for snapdragon was split out from the linux package into a linux-snapdragon package, so linux-signed should no longer produce any packages for snapdragon. They aren't causing problems currently but need to be removed. Fix: Remove the snapdragon packages from linux-signed. Regression Potential: There should be no chance for regressions, the snapdragon meta packages will refer to kernels build from linux- snapdragon. ** Affects: linux-signed (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux-signed (Ubuntu Disco) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: linux-signed (Ubuntu Disco) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1824233 Title: linux-signed is still producing snapdragon packages Status in linux-signed package in Ubuntu: In Progress Status in linux-signed source package in Disco: In Progress Bug description: SRU Justification Impact: Support for snapdragon was split out from the linux package into a linux-snapdragon package, so linux-signed should no longer produce any packages for snapdragon. They aren't causing problems currently but need to be removed. Fix: Remove the snapdragon packages from linux-signed. Regression Potential: There should be no chance for regressions, the snapdragon meta packages will refer to kernels build from linux- snapdragon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1824233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824350] [NEW] shiftfs: chown sets untranslated ids in lower fs
Public bug reported: SRU Justification Impact: shiftfs_setattr() creates an iattr struct with shifted ids for the lower fs, but then mistakenly passes the original iattr struct when changing the lower filesystem attributes. As a result, chown on a shiftfs filesystem sets ownership using the untranslated user and group ids. Fix: Pass the struct containing shifted uids to notify_change(). Regression Potential: This is a simple and obvious fix, and it has been tested to confirm it fixes the issue. Therefore the risk of regressions is low. Test Case: Within a lxd container using shiftfs, run: # mkdir dir # touch file # ls -lh dir file drwxr-xr-x 2 root root 4.0K Apr 11 13:05 dir -rw-r--r-- 1 root root0 Apr 11 13:05 file # chown 500:500 dir file # ls -lh dir file Expected result: drwxr-xr-x 2 500 500 4.0K Apr 11 13:05 dir -rw-r--r-- 1 500 5000 Apr 11 13:05 file Result in 5.0.0-10.11: drwxr-xr-x 2 1000500 1000500 4.0K Apr 11 12:42 dir -rw-r--r-- 1 1000500 10005000 Apr 11 12:42 file ** Affects: linux (Ubuntu) Importance: High Assignee: Seth Forshee (sforshee) Status: In Progress ** Summary changed: - chown sets wrong owner in shiftfs + shiftfs: chown sets untranslated ids in lower fs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824350 Title: shiftfs: chown sets untranslated ids in lower fs Status in linux package in Ubuntu: In Progress Bug description: SRU Justification Impact: shiftfs_setattr() creates an iattr struct with shifted ids for the lower fs, but then mistakenly passes the original iattr struct when changing the lower filesystem attributes. As a result, chown on a shiftfs filesystem sets ownership using the untranslated user and group ids. Fix: Pass the struct containing shifted uids to notify_change(). Regression Potential: This is a simple and obvious fix, and it has been tested to confirm it fixes the issue. Therefore the risk of regressions is low. Test Case: Within a lxd container using shiftfs, run: # mkdir dir # touch file # ls -lh dir file drwxr-xr-x 2 root root 4.0K Apr 11 13:05 dir -rw-r--r-- 1 root root0 Apr 11 13:05 file # chown 500:500 dir file # ls -lh dir file Expected result: drwxr-xr-x 2 500 500 4.0K Apr 11 13:05 dir -rw-r--r-- 1 500 5000 Apr 11 13:05 file Result in 5.0.0-10.11: drwxr-xr-x 2 1000500 1000500 4.0K Apr 11 12:42 dir -rw-r--r-- 1 1000500 10005000 Apr 11 12:42 file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824354] [NEW] Make shiftfs a module rather than built-in
Public bug reported: SRU Justification Impact: shiftfs is built into the kernel, but there's no need for it to be built-in. It seems this was by mistake. Fix: Make it a module instead. Also add it to the generic inclusion list so that it is usable with linux-virtual. Regression Potential: Minimal, see testing results below. Test Case: Boot with shitfs built as a module and confirm that lxd still works with shiftfs. I have done this and confirmed that lxd still works as expected. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824354 Title: Make shiftfs a module rather than built-in Status in linux package in Ubuntu: In Progress Bug description: SRU Justification Impact: shiftfs is built into the kernel, but there's no need for it to be built-in. It seems this was by mistake. Fix: Make it a module instead. Also add it to the generic inclusion list so that it is usable with linux-virtual. Regression Potential: Minimal, see testing results below. Test Case: Boot with shitfs built as a module and confirm that lxd still works with shiftfs. I have done this and confirmed that lxd still works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823218] Re: linux-raspi2: 5.0.0-1005.5 -proposed tracker
*** This bug is a duplicate of bug 1824374 *** https://bugs.launchpad.net/bugs/1824374 ** Tags removed: kernel-sru-derivative-of-1823936 ** 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: 1823936 phase: Testing phase-changed: Wednesday, 10. April 2019 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED ** This bug has been marked a duplicate of bug 1824374 linux-raspi2: -proposed tracker -- 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/1823218 Title: linux-raspi2: 5.0.0-1005.5 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Disco: New 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 -- phase: Testing phase-changed: Wednesday, 10. April 2019 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
