[Kernel-packages] [Bug 2063365] [NEW] brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52
Public bug reported: On the noble server release candidate image testing, I noticed that the automated wifi tests we run for certification were passing, but they logged some errors from dmesg related to brcmfmac. The log is filled with lots of these errors: kern :err : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 kern :err : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set chanspec 0x100d fail, reason -52 kern :err : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52 ... To be clear, it was able to get a wifi connection, but something seems off with this. I've noticed this on rpi4 and rpi5 so far, not sure about others yet ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2063365 Title: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 Status in linux-raspi package in Ubuntu: New Bug description: On the noble server release candidate image testing, I noticed that the automated wifi tests we run for certification were passing, but they logged some errors from dmesg related to brcmfmac. The log is filled with lots of these errors: kern :err : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 kern :err : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set chanspec 0x100d fail, reason -52 kern :err : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52 ... To be clear, it was able to get a wifi connection, but something seems off with this. I've noticed this on rpi4 and rpi5 so far, not sure about others yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036995] [NEW] [mantic] rpi3 has no video output on HDMI
Public bug reported: On the mantic beta (20230919.1) I don't see any video output on hdmi with rpi3. I've tested the same image and configuration with rpiz2 and rpi4 so far, and I do get hdmi output on both of those, so I don't think it's likely to be an issue with my monitor or cable. Logs attached. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-raspi (not installed) ProcVersionSignature: Ubuntu 6.5.0-1002.2-raspi 6.5.0 Uname: Linux 6.5.0-1002-raspi aarch64 ApportVersion: 2.27.0-0ubuntu2 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Thu Sep 21 17:04:47 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-1002-raspi N/A linux-backports-modules-6.5.0-1002-raspi N/A linux-firmware20230919.git3672ccab-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: snd_bcm2835 bcm2835_mmal_vchiq bcm2835_v4l2 bcm2835_isp bcm2835_codec vc_sm_cma UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 mantic staging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2036995 Title: [mantic] rpi3 has no video output on HDMI Status in linux-raspi package in Ubuntu: New Bug description: On the mantic beta (20230919.1) I don't see any video output on hdmi with rpi3. I've tested the same image and configuration with rpiz2 and rpi4 so far, and I do get hdmi output on both of those, so I don't think it's likely to be an issue with my monitor or cable. Logs attached. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-raspi (not installed) ProcVersionSignature: Ubuntu 6.5.0-1002.2-raspi 6.5.0 Uname: Linux 6.5.0-1002-raspi aarch64 ApportVersion: 2.27.0-0ubuntu2 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Thu Sep 21 17:04:47 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-1002-raspi N/A linux-backports-modules-6.5.0-1002-raspi N/A linux-firmware20230919.git3672ccab-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: snd_bcm2835 bcm2835_mmal_vchiq bcm2835_v4l2 bcm2835_isp bcm2835_codec vc_sm_cma UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2036995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036841] [NEW] [mantic] usb ethernet not working
Public bug reported: Tested with the 20230919.1 arm64 image on rpi-zero2 This device does not have built-in ethernet, so it relies on USB ethernet to connect. I noticed on the initial boot that I was unable to login as ubuntu/ubuntu, and I suspect this might be loosely related to this because I also noticed that there were no lights on my ethernet dongle. If I unplugged it and replugged it, it would light up for a minute then stop. After reboot, I was able to login but still no ethernet. The dongle is detected, but it gets renamed from eth0 to something else, which I think is what's causing it to fail to be setup properly. ubuntu@ubuntu:~$ uname -a Linux ubuntu 6.5.0-1002-raspi #2-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 8 15:39:40 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux [6.990858] ax88179_178a 1-1.3.4.3:1.0 eth0: register 'ax88179_178a' at usb-3f98.usb-1.3.4.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0e:c6:c4:1f:57 ... [7.026290] ax88179_178a 1-1.3.4.3:1.0 enx000ec6c41f57: renamed from eth0 ubuntu@ubuntu:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enx000ec6c41f57: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:0e:c6:c4:1f:57 brd ff:ff:ff:ff:ff:ff 3: wlan0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether e4:5f:01:10:82:e1 brd ff:ff:ff:ff:ff:ff I am able to manually configure ethernet though, so the device itself is working with this kernel. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2036841 Title: [mantic] usb ethernet not working Status in linux-raspi package in Ubuntu: New Bug description: Tested with the 20230919.1 arm64 image on rpi-zero2 This device does not have built-in ethernet, so it relies on USB ethernet to connect. I noticed on the initial boot that I was unable to login as ubuntu/ubuntu, and I suspect this might be loosely related to this because I also noticed that there were no lights on my ethernet dongle. If I unplugged it and replugged it, it would light up for a minute then stop. After reboot, I was able to login but still no ethernet. The dongle is detected, but it gets renamed from eth0 to something else, which I think is what's causing it to fail to be setup properly. ubuntu@ubuntu:~$ uname -a Linux ubuntu 6.5.0-1002-raspi #2-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 8 15:39:40 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux [6.990858] ax88179_178a 1-1.3.4.3:1.0 eth0: register 'ax88179_178a' at usb-3f98.usb-1.3.4.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0e:c6:c4:1f:57 ... [7.026290] ax88179_178a 1-1.3.4.3:1.0 enx000ec6c41f57: renamed from eth0 ubuntu@ubuntu:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enx000ec6c41f57: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:0e:c6:c4:1f:57 brd ff:ff:ff:ff:ff:ff 3: wlan0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether e4:5f:01:10:82:e1 brd ff:ff:ff:ff:ff:ff I am able to manually configure ethernet though, so the device itself is working with this kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2036841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
I confirmed today that r1000 in beta fixes this. Thanks! -- 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/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi Status in linux package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: New Bug description: When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg: [ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56) Here's the full dmesg with grep -i blue: https://pastebin.canonical.com/p/99KvzHY4n9/ On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices: [5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [7.059104] Bluetooth: hci0: Waiting for firmware download to complete [7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs [7.059903] Bluetooth: hci0: Waiting for device to boot [7.073886] Bluetooth: hci0: Device booted in 13691 usecs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968617] [NEW] uc22 no serial console on rpi
Public bug reported: The current uc22 beta image (2022-04-11) shows nothing on the serial console during boot, nor does it allow console-conf over serial console. I've double checked with jammy, focal, and uc20 and my serial console is working fine with all of those images on this same device (an rpi3b+) but with uc22 I don't see any output at all. Kernel version: Linux ubuntu 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:25:49 UTC 2022 armv7l armv7l armv7l GNU/Linux One thing I did notice, is that I do not see a ttyS0 device, which appears to be what it's expecting to use for the serial console ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1968617 Title: uc22 no serial console on rpi Status in linux-raspi package in Ubuntu: New Bug description: The current uc22 beta image (2022-04-11) shows nothing on the serial console during boot, nor does it allow console-conf over serial console. I've double checked with jammy, focal, and uc20 and my serial console is working fine with all of those images on this same device (an rpi3b+) but with uc22 I don't see any output at all. Kernel version: Linux ubuntu 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:25:49 UTC 2022 armv7l armv7l armv7l GNU/Linux One thing I did notice, is that I do not see a ttyS0 device, which appears to be what it's expecting to use for the serial console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1968617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944593] [NEW] Virtual CAN (vcan) driver missing in raspi 5.13 kernel
Public bug reported: On the image tests we normally do, we have some socketcan tests that make use of the vcan driver. These have been able to run on Raspberry Pi in the past, but we are no longer able to run them because of a missing vcan module on impish. modprobe: FATAL: Module vcan not found in directory /lib/modules/5.13.0-1007-raspi I'm seeing this on the beta rc images for impish with both arm64 and armhf. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1944593 Title: Virtual CAN (vcan) driver missing in raspi 5.13 kernel Status in linux-raspi package in Ubuntu: New Bug description: On the image tests we normally do, we have some socketcan tests that make use of the vcan driver. These have been able to run on Raspberry Pi in the past, but we are no longer able to run them because of a missing vcan module on impish. modprobe: FATAL: Module vcan not found in directory /lib/modules/5.13.0-1007-raspi I'm seeing this on the beta rc images for impish with both arm64 and armhf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1944593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938912] Re: Bad Linux ARM64 Image magic
This appears to be fixed in the current beta kernel for 18-pi - 5.4.0-1042.46~18.04.3 r337 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1938912 Title: Bad Linux ARM64 Image magic Status in linux-raspi-5.4 package in Ubuntu: Invalid Status in linux-raspi-5.4 source package in Bionic: Fix Committed Bug description: [Impact] On all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails to boot. Here's the serial log on the failed boot from one of those devices: Hit any key to stop autoboot: 0 WARNING at /build/u-boot-GPcj9K/u-boot-2019.07+dfsg/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! WARNING at /build/u-boot-GPcj9K/u-boot-2019.07+dfsg/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! switch to partitions #0, OK mmc0(part 0) is current device LOADBOOTENV Running uenvcmd ... ENVCMD Saving Environment to FAT... OK 8624908 bytes read in 367 ms (22.4 MiB/s) 3947036 bytes read in 171 ms (22 MiB/s) 67581 bytes read in 22 ms (2.9 MiB/s) Bad Linux ARM64 Image magic! Armhf seems to be booting just fine after the refresh. [Test Case] See above. [Where Problems Could Occur] The worst that can probably happen is that the device won't boot, which is the current behavior. Well, since the kernel image is bigger I guess we could run out of disk space on the vfat partition... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi-5.4/+bug/1938912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934548] Re: RISC-V: Illegal instruction
That's the image I'm using, and it's reproducible every single time for me -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in linux-riscv package in Ubuntu: Confirmed Status in linux-riscv-5.11 package in Ubuntu: Confirmed Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [0.00] s2 : 0002 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe001a170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc5d0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0019cd3e0 t6 : ffe001803cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1934548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1938912] Re: Bad Linux ARM64 Image magic
I also noticed just now that this kernel from the 20 track does seem to work fine on uc20 systems: pi-kernel5.4.0-1042.46 33120/beta -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1938912 Title: Bad Linux ARM64 Image magic Status in linux-raspi-5.4 package in Ubuntu: New Bug description: on all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails to boot. Here's the serial log on the failed boot from one of those devices: Hit any key to stop autoboot: 0 WARNING at /build/u-boot-GPcj9K/u-boot-2019.07+dfsg/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! WARNING at /build/u-boot-GPcj9K/u-boot-2019.07+dfsg/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! switch to partitions #0, OK mmc0(part 0) is current device LOADBOOTENV Running uenvcmd ... ENVCMD Saving Environment to FAT... OK 8624908 bytes read in 367 ms (22.4 MiB/s) 3947036 bytes read in 171 ms (22 MiB/s) 67581 bytes read in 22 ms (2.9 MiB/s) Bad Linux ARM64 Image magic! Armhf seems to be booting just fine after the refresh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi-5.4/+bug/1938912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938912] [NEW] Bad Linux ARM64 Image magic
Public bug reported: on all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails to boot. Here's the serial log on the failed boot from one of those devices: Hit any key to stop autoboot: 0 WARNING at /build/u-boot-GPcj9K/u-boot-2019.07+dfsg/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! WARNING at /build/u-boot-GPcj9K/u-boot-2019.07+dfsg/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! switch to partitions #0, OK mmc0(part 0) is current device LOADBOOTENV Running uenvcmd ... ENVCMD Saving Environment to FAT... OK 8624908 bytes read in 367 ms (22.4 MiB/s) 3947036 bytes read in 171 ms (22 MiB/s) 67581 bytes read in 22 ms (2.9 MiB/s) Bad Linux ARM64 Image magic! Armhf seems to be booting just fine after the refresh. ** Affects: linux-raspi-5.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1938912 Title: Bad Linux ARM64 Image magic Status in linux-raspi-5.4 package in Ubuntu: New Bug description: on all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails to boot. Here's the serial log on the failed boot from one of those devices: Hit any key to stop autoboot: 0 WARNING at /build/u-boot-GPcj9K/u-boot-2019.07+dfsg/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! WARNING at /build/u-boot-GPcj9K/u-boot-2019.07+dfsg/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! switch to partitions #0, OK mmc0(part 0) is current device LOADBOOTENV Running uenvcmd ... ENVCMD Saving Environment to FAT... OK 8624908 bytes read in 367 ms (22.4 MiB/s) 3947036 bytes read in 171 ms (22 MiB/s) 67581 bytes read in 22 ms (2.9 MiB/s) Bad Linux ARM64 Image magic! Armhf seems to be booting just fine after the refresh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi-5.4/+bug/1938912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938269] Re: pc-kernel snap 4.15.0-152.159 (UC18) regression in network behaviour
I was also able to reproduce this in bionic on a dawson-j. We don't have serial console on that device, but I was able to get someone with remote access to grab a screenshot of the partial crash for me (attached) ** Attachment added: "partial-oops.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938269/+attachment/5514476/+files/partial-oops.png -- 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/1938269 Title: pc-kernel snap 4.15.0-152.159 (UC18) regression in network behaviour Status in linux package in Ubuntu: Confirmed Bug description: Several amd64 devices have shown an marked increase in failures to complete automated testing with this kernel snap that is currently on 18/beta channel. The devices tested are: dawson-j device type: NUC7PJYH, NUC7CJYH processor: Pentium Silver J5005 1.50GHz, Celeron J4005 2.00GHz ethernet: Realtek 10ec:8168 wireless: Intel 8086:31dc dawson-i device-type: NUC7i3DNHE, NUC7i5DNHE processor: i3-7100U 2.40GHz, i5-7300U 2.60GHz ethernet: Intel 8086:156f wireless: Intel 8086:24fd dearest-team device-type: Inspiron 5758 processor: i5-5200U 2.20GHz ethernet: Realtek 10ec:8136 wireless: Intel 8086:08b3 Symptoms shown by these devices are not the controller side that manages the test run loses connection with the device while carrying out WiFi connection tests. The failure rate does not appear to be 100%, there have been some runs that have completed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938269] Re: pc-kernel snap 4.15.0-152.159 (UC18) regression in network behaviour
I've been trying to gather some more data on this, and here's what I have so far... I added a config for eth0 in /etc/systemd/network so that the test (which replaces eth netplan config with wifi config temporarily) doesn't leave us without the ability to reconnect. Testing with dawson-uc18-m7-20190122-10 and stock uc18 after a snap refresh with current pc-kernel, it seems to sometimes work, sometimes crash and I can never reconnect, and sometimes it boots back up and I can ssh in again (and see 0m uptime) Using the current stable image, I get the same behavior though... it's pretty random, so it's hard to say when this started happening: pc-kernel4.15.0-151.157 80518/stable canonical kernel Reverting the kernel to the one that was on the image for the dawson-uc18 image: pc-kernel4.15.0-44.47 18218/stable canonical kernel ...This one is very old, I know, but after about 50 attempts, I haven't been able to reproduce it with this kernel. Using the current stable kernel again, and reverting core18 to rev 1081 (which was on the image originally), I was somehow (maybe dumb luck?) about to still reproduce a problem, but it was in a state where I could still ssh to it. I could not run snap, ps, or almost anything else, but I could at least find this oops in dmesg: https://pastebin.canonical.com/p/jsctQmJZGc/ -- 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/1938269 Title: pc-kernel snap 4.15.0-152.159 (UC18) regression in network behaviour Status in linux package in Ubuntu: Confirmed Bug description: Several amd64 devices have shown an marked increase in failures to complete automated testing with this kernel snap that is currently on 18/beta channel. The devices tested are: dawson-j device type: NUC7PJYH, NUC7CJYH processor: Pentium Silver J5005 1.50GHz, Celeron J4005 2.00GHz ethernet: Realtek 10ec:8168 wireless: Intel 8086:31dc dawson-i device-type: NUC7i3DNHE, NUC7i5DNHE processor: i3-7100U 2.40GHz, i5-7300U 2.60GHz ethernet: Intel 8086:156f wireless: Intel 8086:24fd dearest-team device-type: Inspiron 5758 processor: i5-5200U 2.20GHz ethernet: Realtek 10ec:8136 wireless: Intel 8086:08b3 Symptoms shown by these devices are not the controller side that manages the test run loses connection with the device while carrying out WiFi connection tests. The failure rate does not appear to be 100%, there have been some runs that have completed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905807] Re: insecure W+X mapping
I'm seeing something very similar to this with current focal images running on unmatched (5.8.0-29) It looks like the image on july 24 worked, but ever since the july 25, 2021 image, it fails to boot https://pastebin.canonical.com/p/c9czkm9x74/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1905807 Title: insecure W+X mapping Status in linux-riscv package in Ubuntu: New Bug description: [ 19.051518] Freeing unused kernel memory: 308K [ 19.062326] [ cut here ] [ 19.066219] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 19.074930] WARNING: CPU: 0 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 19.082806] Modules linked in: [ 19.085825] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12+21.04.1-Ubuntu [ 19.094007] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5b9fb30 [ 19.101104] gp : ffe001728ee0 tp : ffe1f5bedc00 t0 : ffe00173edf8 [ 19.108330] t1 : ffe00173ed90 t2 : 0001feca5000 s0 : ffe1f5b9fb80 [ 19.115536] s1 : ffe1f5b9fe10 a0 : 0053 a1 : 00020020 [ 19.122743] a2 : ffe1f5b9f870 a3 : a4 : ffe0016200f8 [ 19.129949] a5 : ffe0016200f8 a6 : 00c1 a7 : ffe0006f27fe [ 19.137156] s2 : ffdff8001000 s3 : s4 : 0004 [ 19.144376] s5 : s6 : s7 : ffe1f5b9fd20 [ 19.151570] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 19.158775] s11: ffe000c16e20 t3 : 0003ce50 t4 : 0003ce50 [ 19.165980] t5 : t6 : ffe001739462 [ 19.171255] status: 00020120 badaddr: cause: 0003 [ 19.179177] ---[ end trace 72fa85d58b123e2f ]--- [ 19.184544] Checked W+X mappings: failed, 513 W+X pages found [ 19.189561] Run /init as init process Not sure what that means. This is on [0.00] Linux version 5.8.0-10-generic (buildd@riscv64-qemu-lcy01-087) (gcc (Ubuntu 10.2.0-18ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #12+21.04.1-Ubuntu SMP Fri Nov 20 16:26:05 UTC 2020 (Ubuntu 5.8.0-10.12+21.04.1-generic 5.8.17) will try to get full logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1905807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
I also tried this on my pi400 and confirmed I can see and connect to bluetooth devices after updating to bluez 5.55-0ubuntu1.1 from groovy- proposed ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Committed Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1566468] Re: systemd-modules-load.service: Failing due to missing module 'ib_iser'
This also shows up still in the 18.04.5 candidate server images on raspberry pi -- 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/1566468 Title: systemd-modules-load.service: Failing due to missing module 'ib_iser' Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Status in linux-kvm source package in Xenial: Confirmed Status in linux-raspi2 source package in Xenial: Confirmed Status in open-iscsi source package in Xenial: Invalid Bug description: On a number of VMs using Xenial daily builds 20160330 and 20160403, out of the box (just after booting for the first time), the following appears in dmesg at boot time: systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: Failed to start Load Kernel Modules. systemd[1]: systemd-modules-load.service: Unit entered failed state. systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. The following related complaint appears in /var/log/syslog: ubuntu systemd-modules-load[352]: Inserted module 'iscsi_tcp' ubuntu systemd-modules-load[352]: Failed to find module 'ib_iser' It looks like 'ib_iser' is some Mellanox-related module, which I don't *think* is something that a stock cloudimg install should attempt to load but I may be wrong; in any case, it's not present (nor is there any similar whingeing) on similar VMs running off 14.04 cloudimg. More info: http://askubuntu.com/questions/753672/xenial-beta2-systemd- modules-load-service-failed-due-to-missing-module-ib-i --- root@testvm4:~# lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 root@testvm4:~# apt policy systemd systemd: Installed: 229-3ubuntu2 Candidate: 229-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890487] [NEW] rpi3b+ wifi doesn't get used if ethernet disconnected
Public bug reported: When testing 20.04.1, I noticed some different behavior on rpi3b+ that I didn't see on rpi3b or rpi4. I have configured the device with ethernet, added netplan yaml for my wifi network, and rebooted. So both eth0 and wlan0 have an ip address. On all other devices (rpi3b, rpi4, etc), if I unplug eth0 wile pinging something, I'll miss maybe 1 ping and then it will continue to work and just switch over to wlan0. However, on rpi3b+ it just stops being able to access the network completely. If I re-run netplan apply, it will start using wifi again, but if I plug eth0 back in, then unplug it, it stops just like before. I am seeing this with the current 20.04.1 release: Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I also went back and tested the original 20.04 release and it happens there too, so this is not a regression: Linux ubuntu 5.4.0-1008-raspi #8-Ubuntu SMP Wed Apr 8 11:13:06 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I see this happen on both armhf and arm64. One difference I did note, is that I get a link down message in dmesg on rpi3b, but not rpi3b+. When I disconnect eth0 on rpi3b I see this: [ 82.203702] smsc95xx 1-1.1:1.0 eth0: link down ...but nothing on the 3b+. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1890487 Title: rpi3b+ wifi doesn't get used if ethernet disconnected Status in linux-raspi2 package in Ubuntu: New Bug description: When testing 20.04.1, I noticed some different behavior on rpi3b+ that I didn't see on rpi3b or rpi4. I have configured the device with ethernet, added netplan yaml for my wifi network, and rebooted. So both eth0 and wlan0 have an ip address. On all other devices (rpi3b, rpi4, etc), if I unplug eth0 wile pinging something, I'll miss maybe 1 ping and then it will continue to work and just switch over to wlan0. However, on rpi3b+ it just stops being able to access the network completely. If I re-run netplan apply, it will start using wifi again, but if I plug eth0 back in, then unplug it, it stops just like before. I am seeing this with the current 20.04.1 release: Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I also went back and tested the original 20.04 release and it happens there too, so this is not a regression: Linux ubuntu 5.4.0-1008-raspi #8-Ubuntu SMP Wed Apr 8 11:13:06 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I see this happen on both armhf and arm64. One difference I did note, is that I get a link down message in dmesg on rpi3b, but not rpi3b+. When I disconnect eth0 on rpi3b I see this: [ 82.203702] smsc95xx 1-1.1:1.0 eth0: link down ...but nothing on the 3b+. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1890487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889468] Re: 20.04.1 selecting audio output device does not work on rpi
Apparently it's not just us, this is an upstream change. Dave Jones found this: https://www.raspberrypi.org/blog/latest-raspberry-pi-os- update-may-2020/ To select headphones, the recommended process is now to create a file called .asoundrc in your home dir with these contents: defaults.pcm.card 1 defaults.ctl.card 1 ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1889468 Title: 20.04.1 selecting audio output device does not work on rpi Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: Invalid Bug description: Testing the 20.04.1 candidate images on rpi (currently rpi4-2GB) I'm noticing that I can no longer select the audio output device with amixer. This used to be possible by using: amixer cset numid=3 2 for HDMI0 amixer cset numid=3 3 for HDMI1 amixer cset numid=3 1 for 3.5mm headphone jack However, now trying to set this gets the following error: amixer: Cannot find the given element from control default It seems that by default, it will now use the hdmi output for whichever one is connected, and will only output through the headphones if no hdmi device is connected. Kernel is: Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1889468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889468] [NEW] 20.04.1 selecting audio output device does not work on rpi
Public bug reported: Testing the 20.04.1 candidate images on rpi (currently rpi4-2GB) I'm noticing that I can no longer select the audio output device with amixer. This used to be possible by using: amixer cset numid=3 2 for HDMI0 amixer cset numid=3 3 for HDMI1 amixer cset numid=3 1 for 3.5mm headphone jack However, now trying to set this gets the following error: amixer: Cannot find the given element from control default It seems that by default, it will now use the hdmi output for whichever one is connected, and will only output through the headphones if no hdmi device is connected. Kernel is: Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1889468 Title: 20.04.1 selecting audio output device does not work on rpi Status in linux-raspi2 package in Ubuntu: New Bug description: Testing the 20.04.1 candidate images on rpi (currently rpi4-2GB) I'm noticing that I can no longer select the audio output device with amixer. This used to be possible by using: amixer cset numid=3 2 for HDMI0 amixer cset numid=3 3 for HDMI1 amixer cset numid=3 1 for 3.5mm headphone jack However, now trying to set this gets the following error: amixer: Cannot find the given element from control default It seems that by default, it will now use the hdmi output for whichever one is connected, and will only output through the headphones if no hdmi device is connected. Kernel is: Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1889468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888691] [NEW] [uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps
Public bug reported: The armhf kernel on the current uc20 beta image (5.4.0-1011.11 r156) boots fine on rpi4, but when the system refreshes to 5.4.0-1011.15 r179, the system does not boot. After it gets to "Starting kernel..." it just stops. Attempting to power off/on the device after the failed boot fails in the uboot script: Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 28 ms (161.1 KiB/s) ## Executing script at 0240 4096 bytes read in 39 ms (102.5 KiB/s) 131072 bytes read in 45 ms (2.8 MiB/s) 131072 bytes written in 89 ms (1.4 MiB/s) SCRIPT FAILED: continuing... 45618 bytes read in 41 ms (1.1 MiB/s) Card did not respond to voltage select! starting USB... ... This does not seem to happen with the arm64 kernel, and booting the armhf kernel seems to work fine on pi3 devices - it just seems to be the combination of armhf and rpi4 that breaks right now. ** Affects: snapd Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Tags: uc20 ** Tags added: uc20 -- 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/1888691 Title: [uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps Status in snapd: New Status in linux-raspi2 package in Ubuntu: New Bug description: The armhf kernel on the current uc20 beta image (5.4.0-1011.11 r156) boots fine on rpi4, but when the system refreshes to 5.4.0-1011.15 r179, the system does not boot. After it gets to "Starting kernel..." it just stops. Attempting to power off/on the device after the failed boot fails in the uboot script: Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 28 ms (161.1 KiB/s) ## Executing script at 0240 4096 bytes read in 39 ms (102.5 KiB/s) 131072 bytes read in 45 ms (2.8 MiB/s) 131072 bytes written in 89 ms (1.4 MiB/s) SCRIPT FAILED: continuing... 45618 bytes read in 41 ms (1.1 MiB/s) Card did not respond to voltage select! starting USB... ... This does not seem to happen with the arm64 kernel, and booting the armhf kernel seems to work fine on pi3 devices - it just seems to be the combination of armhf and rpi4 that breaks right now. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1888691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev
Seems to work in the latest images imported from the streams. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874279 Title: failed to boot focal image in maas: /root.tmp.img: can't open blockdev Status in linux package in Ubuntu: Invalid Bug description: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - Dell inspiron 5758 i5-5200 (dearest-team) - Dell inspiron 5759 i5-6200 (unknown-wealth) It's unknown yet whether there are others affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev
** Description changed: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - - Dell latitude 5758 i5-5200 - - Dell latitude 5759 i5-6200 + - Dell inspiron 5758 i5-5200 (dearest-team) + - Dell inspiron 5759 i5-6200 (unknown-wealth) It's unknown yet whether there are others affected by this. -- 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/1874279 Title: failed to boot focal image in maas: /root.tmp.img: can't open blockdev Status in linux package in Ubuntu: Incomplete Bug description: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - Dell inspiron 5758 i5-5200 (dearest-team) - Dell inspiron 5759 i5-6200 (unknown-wealth) It's unknown yet whether there are others affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878271] Re: rpi: no uboot or kernel boot mesages on console during boot on core20
** Tags added: uc20 -- 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/1878271 Title: rpi: no uboot or kernel boot mesages on console during boot on core20 Status in linux-raspi2 package in Ubuntu: New Bug description: I'm currently testing the image from http://cdimage.ubuntu.com/ubuntu- core/20/beta/20200512.3/ on rpi4-4GB. Normally, we would expect to see uboot prompt on screen, as well as kernel boot messages - as well as on serial. I see all of this coming over serial, but nothing on the screen until the system is completely booted. Current kernel version and snaps in this image are: $ uname -a Linux ubuntu 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:43:33 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux $ snap list Name VersionRev Tracking Publisher Notes core20 20 635 latest/beta canonical✓ base pi 20-1 5820/beta canonical✓ gadget pi-kernel 5.4.0-1011.11 154 20/beta canonical✓ kernel snapd 2.45 7780 latest/beta canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1878271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878432] Re: rpi3a+ does not boot with core20
I hadn't realized it at first, but this is actually similar to something we've seen in the past. There's some contiguous memory that is allocated and locked if vc4-fkms-v3d is enabled in the config.txt. This is ok for platforms with more RAM, but the RPI3A+ is too constrained. Removing that line will allow it to boot at least. -- 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/1878432 Title: rpi3a+ does not boot with core20 Status in pi2-kernel-snap: New Status in snapd: New Status in linux-raspi2 package in Ubuntu: New Bug description: MMC: mmc@7e202000: 0, mmcnr@7e30: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment RPI3a+ on core 20 from http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200513.2/ (also tested the previous - 20200512.3) are not booting. This is for both arm64 and armhf. This is the serial log for as far as it gets: In:serial Out: serial Err: serial Net: No ethernet found. starting USB... Bus usb@7e98: scanning bus usb@7e98 for devices... 5 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found ## Warning: Input data exceeds 1048576 bytes - truncated ## Info: input data size = 1048578 = 0x12 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 2 ms (2.2 MiB/s) ## Executing script at 0240 4096 bytes read in 3 ms (1.3 MiB/s) 8378005 bytes read in 363 ms (22 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 33637043 bytes read in 1448 ms (22.2 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 0260a065 Starting kernel ... To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878432] Re: rpi3a+ does not boot with core20
I disabled quiet and enabled early printk and was able to get a full capture of the panic. (see attachment) ** Attachment added: "boot.log" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1878432/+attachment/5371037/+files/boot.log -- 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/1878432 Title: rpi3a+ does not boot with core20 Status in pi2-kernel-snap: New Status in snapd: New Status in linux-raspi2 package in Ubuntu: New Bug description: MMC: mmc@7e202000: 0, mmcnr@7e30: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment RPI3a+ on core 20 from http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200513.2/ (also tested the previous - 20200512.3) are not booting. This is for both arm64 and armhf. This is the serial log for as far as it gets: In:serial Out: serial Err: serial Net: No ethernet found. starting USB... Bus usb@7e98: scanning bus usb@7e98 for devices... 5 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found ## Warning: Input data exceeds 1048576 bytes - truncated ## Info: input data size = 1048578 = 0x12 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 2 ms (2.2 MiB/s) ## Executing script at 0240 4096 bytes read in 3 ms (1.3 MiB/s) 8378005 bytes read in 363 ms (22 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 33637043 bytes read in 1448 ms (22.2 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 0260a065 Starting kernel ... To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878432] [NEW] rpi3a+ does not boot with core20
Public bug reported: MMC: mmc@7e202000: 0, mmcnr@7e30: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment RPI3a+ on core 20 from http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200513.2/ (also tested the previous - 20200512.3) are not booting. This is for both arm64 and armhf. This is the serial log for as far as it gets: In:serial Out: serial Err: serial Net: No ethernet found. starting USB... Bus usb@7e98: scanning bus usb@7e98 for devices... 5 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found ## Warning: Input data exceeds 1048576 bytes - truncated ## Info: input data size = 1048578 = 0x12 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 2 ms (2.2 MiB/s) ## Executing script at 0240 4096 bytes read in 3 ms (1.3 MiB/s) 8378005 bytes read in 363 ms (22 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 33637043 bytes read in 1448 ms (22.2 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 0260a065 Starting kernel ... ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1878432 Title: rpi3a+ does not boot with core20 Status in linux-raspi2 package in Ubuntu: New Bug description: MMC: mmc@7e202000: 0, mmcnr@7e30: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment RPI3a+ on core 20 from http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200513.2/ (also tested the previous - 20200512.3) are not booting. This is for both arm64 and armhf. This is the serial log for as far as it gets: In:serial Out: serial Err: serial Net: No ethernet found. starting USB... Bus usb@7e98: scanning bus usb@7e98 for devices... 5 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found ## Warning: Input data exceeds 1048576 bytes - truncated ## Info: input data size = 1048578 = 0x12 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 2 ms (2.2 MiB/s) ## Executing script at 0240 4096 bytes read in 3 ms (1.3 MiB/s) 8378005 bytes read in 363 ms (22 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 33637043 bytes read in 1448 ms (22.2 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 0260a065 Starting kernel ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1878432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878271] [NEW] rpi: no uboot or kernel boot mesages on console during boot on core20
Public bug reported: I'm currently testing the image from http://cdimage.ubuntu.com/ubuntu- core/20/beta/20200512.3/ on rpi4-4GB. Normally, we would expect to see uboot prompt on screen, as well as kernel boot messages - as well as on serial. I see all of this coming over serial, but nothing on the screen until the system is completely booted. Current kernel version and snaps in this image are: $ uname -a Linux ubuntu 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:43:33 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux $ snap list Name VersionRev Tracking Publisher Notes core20 20 635 latest/beta canonical✓ base pi 20-1 5820/beta canonical✓ gadget pi-kernel 5.4.0-1011.11 154 20/beta canonical✓ kernel snapd 2.45 7780 latest/beta canonical✓ snapd ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1878271 Title: rpi: no uboot or kernel boot mesages on console during boot on core20 Status in linux-raspi2 package in Ubuntu: New Bug description: I'm currently testing the image from http://cdimage.ubuntu.com/ubuntu- core/20/beta/20200512.3/ on rpi4-4GB. Normally, we would expect to see uboot prompt on screen, as well as kernel boot messages - as well as on serial. I see all of this coming over serial, but nothing on the screen until the system is completely booted. Current kernel version and snaps in this image are: $ uname -a Linux ubuntu 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:43:33 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux $ snap list Name VersionRev Tracking Publisher Notes core20 20 635 latest/beta canonical✓ base pi 20-1 5820/beta canonical✓ gadget pi-kernel 5.4.0-1011.11 154 20/beta canonical✓ kernel snapd 2.45 7780 latest/beta canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1878271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev
I'm pretty sure it gets links to the artifacts that it needs via streams at http://images.maas.io/ephemeral-v3/daily/focal/amd64/ -- 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/1874279 Title: failed to boot focal image in maas: /root.tmp.img: can't open blockdev Status in linux package in Ubuntu: Incomplete Bug description: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - Dell latitude 5758 i5-5200 - Dell latitude 5759 i5-6200 It's unknown yet whether there are others affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev
Screenshot 1 with errors at boot ** Attachment added: "20200422_111045.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+attachment/5358002/+files/20200422_111045.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874279 Title: failed to boot focal image in maas: /root.tmp.img: can't open blockdev Status in linux package in Ubuntu: New Bug description: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - Dell latitude 5758 i5-5200 - Dell latitude 5759 i5-6200 It's unknown yet whether there are others affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev
Screenshot 2 with errors at boot ** Attachment added: "20200422_112031.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+attachment/5358003/+files/20200422_112031.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874279 Title: failed to boot focal image in maas: /root.tmp.img: can't open blockdev Status in linux package in Ubuntu: New Bug description: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - Dell latitude 5758 i5-5200 - Dell latitude 5759 i5-6200 It's unknown yet whether there are others affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874279] [NEW] failed to boot focal image in maas: /root.tmp.img: can't open blockdev
Public bug reported: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - Dell latitude 5758 i5-5200 - Dell latitude 5759 i5-6200 It's unknown yet whether there are others affected by this. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874279 Title: failed to boot focal image in maas: /root.tmp.img: can't open blockdev Status in linux package in Ubuntu: New Bug description: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - Dell latitude 5758 i5-5200 - Dell latitude 5759 i5-6200 It's unknown yet whether there are others affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862831] [NEW] hciattach on rpi4 times out on first attempt
Public bug reported: I've observed this in both armhf and arm64 on: 19.10.1-server 18.04.4-server core18 It does not seem to happen on rpi3, only on rpi4. If you want to use Bluetooth on rpi, one must first run: $ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow On RPI4, this results in a timeout on the first attempt. Reattempting it right after will work though, 100% of the times I've tried it. In the failed attempt, the output is: bcm43xx_init Initialization timed out. And the following is the only new message to show up in dmesg when this fails: [ 270.303691] uart-pl011 fe201000.serial: no DMA platform data ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1862831 Title: hciattach on rpi4 times out on first attempt Status in linux-raspi2 package in Ubuntu: New Bug description: I've observed this in both armhf and arm64 on: 19.10.1-server 18.04.4-server core18 It does not seem to happen on rpi3, only on rpi4. If you want to use Bluetooth on rpi, one must first run: $ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow On RPI4, this results in a timeout on the first attempt. Reattempting it right after will work though, 100% of the times I've tried it. In the failed attempt, the output is: bcm43xx_init Initialization timed out. And the following is the only new message to show up in dmesg when this fails: [ 270.303691] uart-pl011 fe201000.serial: no DMA platform data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1862831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861338] Re: RPI4 wifi unreliable when usb3 storage is attached
I don't have another usb3 one at the moment, I'll see what I can find. However, I'm also starting to think it may be RF interference from the usb3 port and or stick. If I grab the rpi4 near the usb/ethernet block in the right place, the problem seems to go away a bit. possibly something similar to the known issues with hdmi at certain resolutions jamming wifi? I've tried with two different access points, both in the same room so I'm plenty close to have a strong signal, and I see this happen on 3 different rpi4 devices (1,2,4GB). -- 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/1861338 Title: RPI4 wifi unreliable when usb3 storage is attached Status in linux-raspi2 package in Ubuntu: Triaged Bug description: On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage device to one of the 2x usb3 ports (the ones closest to the ethernet port), wifi will sudden stop working. If you unplug the usb stick while running a ping, it will usually start working again almost instantaneously. Kernel version I have is: 5.3.0-1017-raspi2 and I've confirmed this happens on both armhf and arm64 The only thing I found in journalctl that looks suspicious is this, but it seems to have happened before plugging in the usb stick: Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from /dev/random: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861338] Re: RPI4 wifi unreliable when usb3 storage is attached
** Description changed: On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage device to one of the 2x usb3 ports (the ones closest to the ethernet port), wifi will sudden stop working. If you unplug the usb stick while running a ping, it will usually start working again almost instantaneously. Kernel version I have is: 5.3.0-1017-raspi2 and I've confirmed this happens on both armhf and arm64 - The only thing I found in journalctl that looks suspicious is that I get a lot of this after plugging in the usb stick: + The only thing I found in journalctl that looks suspicious is this, but it seems to have happened before plugging in the usb stick: Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from /dev/random: Resource temporarily unavailable -- 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/1861338 Title: RPI4 wifi unreliable when usb3 storage is attached Status in linux-raspi2 package in Ubuntu: New Bug description: On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage device to one of the 2x usb3 ports (the ones closest to the ethernet port), wifi will sudden stop working. If you unplug the usb stick while running a ping, it will usually start working again almost instantaneously. Kernel version I have is: 5.3.0-1017-raspi2 and I've confirmed this happens on both armhf and arm64 The only thing I found in journalctl that looks suspicious is this, but it seems to have happened before plugging in the usb stick: Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from /dev/random: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861338] [NEW] RPI4 wifi unreliable when usb3 storage is attached
Public bug reported: On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage device to one of the 2x usb3 ports (the ones closest to the ethernet port), wifi will sudden stop working. If you unplug the usb stick while running a ping, it will usually start working again almost instantaneously. Kernel version I have is: 5.3.0-1017-raspi2 and I've confirmed this happens on both armhf and arm64 The only thing I found in journalctl that looks suspicious is that I get a lot of this after plugging in the usb stick: Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from /dev/random: Resource temporarily unavailable ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1861338 Title: RPI4 wifi unreliable when usb3 storage is attached Status in linux-raspi2 package in Ubuntu: New Bug description: On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage device to one of the 2x usb3 ports (the ones closest to the ethernet port), wifi will sudden stop working. If you unplug the usb stick while running a ping, it will usually start working again almost instantaneously. Kernel version I have is: 5.3.0-1017-raspi2 and I've confirmed this happens on both armhf and arm64 The only thing I found in journalctl that looks suspicious is that I get a lot of this after plugging in the usb stick: Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from /dev/random: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852510] [NEW] IO errors when writing large amounts of data to USB storage in eoan on RPI
Public bug reported: Kernel tested: Linux ubuntu 5.3.0-1012-raspi2 #14-Ubuntu SMP Mon Nov 11 10:08:39 UTC 2019 armv7l armv7l armv7l GNU/Linux I've only been able to reproduce this with the armhf kernel and on the following devices: RPI3B+ RPI3B RPI2 At the moment, it does not appear that arm64 is affected, nor are RPI3A+ and RPI4 (at least not the 2GB version) Steps to reproduce: - Insert and mount a USB storage device - cp a large file to it (300-600MB recommended - smaller files will sometimes not trigger it) - sync After running the sync, a lot of IO errors will show up in dmesg like: [ 176.129299] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 176.129326] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 00 2e 24 b0 00 00 f0 00 [ 176.129349] blk_update_request: I/O error, dev sda, sector 3024048 op 0x1:(WRITE) flags 0x4000 phys_seg 15 prio class 0 [ 176.883968] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg [ 177.079960] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg It eventually finishes, and if you unmount/remount the device, the checksum will be different from the original file. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1852510/+attachment/5305257/+files/dmesg.log -- 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/1852510 Title: IO errors when writing large amounts of data to USB storage in eoan on RPI Status in linux-raspi2 package in Ubuntu: New Bug description: Kernel tested: Linux ubuntu 5.3.0-1012-raspi2 #14-Ubuntu SMP Mon Nov 11 10:08:39 UTC 2019 armv7l armv7l armv7l GNU/Linux I've only been able to reproduce this with the armhf kernel and on the following devices: RPI3B+ RPI3B RPI2 At the moment, it does not appear that arm64 is affected, nor are RPI3A+ and RPI4 (at least not the 2GB version) Steps to reproduce: - Insert and mount a USB storage device - cp a large file to it (300-600MB recommended - smaller files will sometimes not trigger it) - sync After running the sync, a lot of IO errors will show up in dmesg like: [ 176.129299] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 176.129326] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 00 2e 24 b0 00 00 f0 00 [ 176.129349] blk_update_request: I/O error, dev sda, sector 3024048 op 0x1:(WRITE) flags 0x4000 phys_seg 15 prio class 0 [ 176.883968] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg [ 177.079960] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg It eventually finishes, and if you unmount/remount the device, the checksum will be different from the original file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841841] Re: disk stress test extremely slow progress after cpu offline/online
reopening. I know it was automatically marked incomplete but there's no apport on core18. I believe I've already included the relevant information but I'm happy to provide more, or even get someone access to this system. ** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841841 Title: disk stress test extremely slow progress after cpu offline/online Status in linux package in Ubuntu: Incomplete Bug description: One of the test systems we use for testing snap updates is: Dell Inspiron 5759 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz Advanced Micro Devices, Inc. [AMD/ATI] - 1002:6660, Intel - 8086:1916 We picked this one, some time ago from a pool of hardware to use for one of the test systems to test amd64/i386 snaps in beta. One of the tests in the test suite does some disk stress testing using: bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000 Looking back through our results, I see that it has often taken from 20-40 min. to complete the test, and sometimes hit our timeout threshold. More recently, it seems to always just timeout, but as far back as our history goes with testing on this platform, it's always seemed bad to some extent. I tried the exact same test on another similar system, and it completed in only 11min. so we suspected a bad disk. After replacing the disk with a new one, it still has the same problem. We only see this problem on the core18 i386 images though, not on core16, and not on core18-amd64. Looking into it some more, I discovered that it was easily reproducible outside the test suite, but *only* if I tried running it after the full test suite without rebooting. If I reboot the system, and run the bonnie++ command above without the rest of the tests, it completes in about 13 min. I divided up the other tests and narrowed it down to a cpu offlining test - when that test runs, followed by this disk stress test, that's when it gets so horribly slow. This was all done using checkbox-snappy as the test suite, but if you have another way to get bonnie++ on here, it can be reproduced without it (or you can use bonnie++ from checkbox-snappy easily by doing 'sudo /snap/bin/checkbox-snappy.shell') Here's the basic instructions to reproduce (on core18-i386): $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu1/online" $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu2/online" $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu3/online" $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu1/online" $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu2/online" $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu3/online" $ sudo /snap/bin/checkbox-snappy.shell # bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000 Nothing particularly interesting in dmesg during all of this other than the NOHZ messages during cpu offline: [ 189.085026] smpboot: CPU 1 is now offline [ 199.371529] smpboot: CPU 2 is now offline [ 203.291835] NOHZ: local_softirq_pending 282 [ 203.293167] NOHZ: local_softirq_pending 282 [ 203.294581] smpboot: CPU 3 is now offline [ 247.521569] x86: Booting SMP configuration: [ 247.521576] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 247.522892] Initializing CPU#1 [ 252.127965] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 252.129533] Initializing CPU#2 [ 255.632004] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 255.633565] Initializing CPU#3 History I have for the past few kernels: 4.15.0-52.56-226 - passed - 41m 4.15.0-54.58-241 - passed - 36m 4.15.0-55.60-246 - passed after some timeouts/retries, took 41m though 4.15.0-55.60-253 - passed in 20min 4.15.0-56.62-263 - fails - seems to take much much longer from this point on *These results were from that test as part of the full test run, including the cpu offlining test. When the test is run by itself on the same system, it takes only around 13min To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848075] Re: eoan server image does not boot on RPI3-A+
Here's a screenshot from the errors I see on the hdmi console ** Attachment added: "screenshot" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848075/+attachment/5297127/+files/IMG_1389.JPG -- 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/1848075 Title: eoan server image does not boot on RPI3-A+ Status in linux-raspi2 package in Ubuntu: New Bug description: I've tried with both the 20191010.1 and 20191012 image, and it boots on all other pi devices I have, but not on the rpi3-a+. On the serial console, it only gets as far as "Starting kernel..." but over hdmi, there are some more details reported. I'll try to attach a screenshot in a moment. After talking to Dave Jones about this, it sounds like some dtb files are missing to make this work on a+ From the 20191012 image: ii linux-raspi25.3.0.1007.3arm64 Complete Linux kernel for the BCM2709 architecture. ii linux-firmware-raspi2 1.20190819-0ubuntu2 arm64 Raspberry Pi 2/3/4 GPU firmware and bootloaders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848075] [NEW] eoan server image does not boot on RPI3-A+
Public bug reported: I've tried with both the 20191010.1 and 20191012 image, and it boots on all other pi devices I have, but not on the rpi3-a+. On the serial console, it only gets as far as "Starting kernel..." but over hdmi, there are some more details reported. I'll try to attach a screenshot in a moment. After talking to Dave Jones about this, it sounds like some dtb files are missing to make this work on a+ >From the 20191012 image: ii linux-raspi25.3.0.1007.3arm64 Complete Linux kernel for the BCM2709 architecture. ii linux-firmware-raspi2 1.20190819-0ubuntu2 arm64 Raspberry Pi 2/3/4 GPU firmware and bootloaders ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1848075 Title: eoan server image does not boot on RPI3-A+ Status in linux-raspi2 package in Ubuntu: New Bug description: I've tried with both the 20191010.1 and 20191012 image, and it boots on all other pi devices I have, but not on the rpi3-a+. On the serial console, it only gets as far as "Starting kernel..." but over hdmi, there are some more details reported. I'll try to attach a screenshot in a moment. After talking to Dave Jones about this, it sounds like some dtb files are missing to make this work on a+ From the 20191012 image: ii linux-raspi25.3.0.1007.3arm64 Complete Linux kernel for the BCM2709 architecture. ii linux-firmware-raspi2 1.20190819-0ubuntu2 arm64 Raspberry Pi 2/3/4 GPU firmware and bootloaders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841841] [NEW] disk stress test extremely slow progress after cpu offline/online
Public bug reported: One of the test systems we use for testing snap updates is: Dell Inspiron 5759 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz Advanced Micro Devices, Inc. [AMD/ATI] - 1002:6660, Intel - 8086:1916 We picked this one, some time ago from a pool of hardware to use for one of the test systems to test amd64/i386 snaps in beta. One of the tests in the test suite does some disk stress testing using: bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000 Looking back through our results, I see that it has often taken from 20-40 min. to complete the test, and sometimes hit our timeout threshold. More recently, it seems to always just timeout, but as far back as our history goes with testing on this platform, it's always seemed bad to some extent. I tried the exact same test on another similar system, and it completed in only 11min. so we suspected a bad disk. After replacing the disk with a new one, it still has the same problem. We only see this problem on the core18 i386 images though, not on core16, and not on core18-amd64. Looking into it some more, I discovered that it was easily reproducible outside the test suite, but *only* if I tried running it after the full test suite without rebooting. If I reboot the system, and run the bonnie++ command above without the rest of the tests, it completes in about 13 min. I divided up the other tests and narrowed it down to a cpu offlining test - when that test runs, followed by this disk stress test, that's when it gets so horribly slow. This was all done using checkbox-snappy as the test suite, but if you have another way to get bonnie++ on here, it can be reproduced without it (or you can use bonnie++ from checkbox-snappy easily by doing 'sudo /snap/bin/checkbox-snappy.shell') Here's the basic instructions to reproduce (on core18-i386): $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu1/online" $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu2/online" $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu3/online" $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu1/online" $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu2/online" $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu3/online" $ sudo /snap/bin/checkbox-snappy.shell # bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000 Nothing particularly interesting in dmesg during all of this other than the NOHZ messages during cpu offline: [ 189.085026] smpboot: CPU 1 is now offline [ 199.371529] smpboot: CPU 2 is now offline [ 203.291835] NOHZ: local_softirq_pending 282 [ 203.293167] NOHZ: local_softirq_pending 282 [ 203.294581] smpboot: CPU 3 is now offline [ 247.521569] x86: Booting SMP configuration: [ 247.521576] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 247.522892] Initializing CPU#1 [ 252.127965] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 252.129533] Initializing CPU#2 [ 255.632004] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 255.633565] Initializing CPU#3 History I have for the past few kernels: 4.15.0-52.56-226 - passed - 41m 4.15.0-54.58-241 - passed - 36m 4.15.0-55.60-246 - passed after some timeouts/retries, took 41m though 4.15.0-55.60-253 - passed in 20min 4.15.0-56.62-263 - fails - seems to take much much longer from this point on *These results were from that test as part of the full test run, including the cpu offlining test. When the test is run by itself on the same system, it takes only around 13min ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1841841 Title: disk stress test extremely slow progress after cpu offline/online Status in linux package in Ubuntu: Incomplete Bug description: One of the test systems we use for testing snap updates is: Dell Inspiron 5759 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz Advanced Micro Devices, Inc. [AMD/ATI] - 1002:6660, Intel - 8086:1916 We picked this one, some time ago from a pool of hardware to use for one of the test systems to test amd64/i386 snaps in beta. One of the tests in the test suite does some disk stress testing using: bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000 Looking back through our results, I see that it has often taken from 20-40 min. to complete the test, and sometimes hit our timeout threshold. More recently, it seems to always just timeout, but as far back as our history goes with testing on this platform, it's always seemed bad to some extent. I tried the exact same test on another similar system, and it completed in only 11min. so we suspected a bad disk. After replacing the disk with a new one, it still has the same problem. We only see this problem on the core18 i386 images though, not on core16, and not on core18-amd64. Looking into it some more, I discovered that it was easily reproducible
[Kernel-packages] [Bug 1833698] Re: Bluetooth regressions with Xenial kernel 4.4.0-152.179
Ran tests with this on two different systems, results looked good on both: 12:34:12 job passed : BlueZ-Basic RFCOMM Socket - Success 12:34:12 job passed : BlueZ-Basic RFCOMM Socket Client - Success 12:34:12 job passed : BlueZ-Basic RFCOMM Socket Client - Write Success 12:34:12 job passed : BlueZ-Basic RFCOMM Socket Client - Read Success 12:34:12 job passed : BlueZ-Basic RFCOMM Socket Client - Conn Refused 12:34:12 job passed : BlueZ-Basic RFCOMM Socket Server - Success 12:34:12 job passed : BlueZ-Basic RFCOMM Socket Server - Write Success 12:34:12 job passed : BlueZ-Basic RFCOMM Socket Server - Read Success 12:34:12 job passed : BlueZ-Basic RFCOMM Socket Server - Conn Refused -- 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/1833698 Title: Bluetooth regressions with Xenial kernel 4.4.0-152.179 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: [Impact] The Certification Team is reporting regressions with the Bluetooth testcases with all Xenial kernels derivatives of 4.4.0-152.179. The suspected commit is "d5bb334a8e17 Bluetooth: Align minimum encryption key size for LE and BR/EDR connections". https://www.spinics.net/lists/linux-bluetooth/msg80148.html https://lkml.org/lkml/2019/6/13/1037 [Test Case] Certification Team test suite (currently the revert is to be verified to fix the issue). [Fix] Revert the introducing commit, as done upstream on stable branch linux-5.1.y by Greg K-H: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.1.y=b528880e8b0167c34cb36c1b4e6165192f76267c [Regression Risk] Low. Reverts a commit that's known to have cause problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826228] [NEW] api3a+ hang when reading /sys/devices/platform/soc/driver_override
Public bug reported: I discovered this when running some tests on a core16 image with various rpi3 devices. Rpi3b, b+, cm3, rpi2, etc... don't have this problem, only rpi3a+. Kernel version: Linux localhost 4.4.0-1107-raspi2 #115-Ubuntu SMP Wed Apr 10 18:06:42 UTC 2019 armv7l armv7l armv7l GNU/Linux To reproduce, simply 'cat /sys/devices/platform/soc/driver_override' The process just hangs and cannot be killed. On other rpi devices, I just get this output immediately: (null) There was nothing in dmesg or syslog when it happened, no kernel crash, and I can still ssh into the system. The process that ran that command just silently hangs and can't be killed even with sudo kill -9. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1826228 Title: api3a+ hang when reading /sys/devices/platform/soc/driver_override Status in linux-raspi2 package in Ubuntu: New Bug description: I discovered this when running some tests on a core16 image with various rpi3 devices. Rpi3b, b+, cm3, rpi2, etc... don't have this problem, only rpi3a+. Kernel version: Linux localhost 4.4.0-1107-raspi2 #115-Ubuntu SMP Wed Apr 10 18:06:42 UTC 2019 armv7l armv7l armv7l GNU/Linux To reproduce, simply 'cat /sys/devices/platform/soc/driver_override' The process just hangs and cannot be killed. On other rpi devices, I just get this output immediately: (null) There was nothing in dmesg or syslog when it happened, no kernel crash, and I can still ssh into the system. The process that ran that command just silently hangs and can't be killed even with sudo kill -9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1826228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825235] [NEW] Load average inexplicably high with 5.0 kernel on rpi
Public bug reported: Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the disco release candidate. After booting, the load average stays quite high, typically over 4.0. This persists, even if I leave it idle for several hours: ubuntu@ubuntu:~$ w 19:44:05 up 2:22, 1 user, load average: 4.16, 4.03, 4.01 /proc/loadavg is consistent with these numbers. But when I check top, there are no obvious culprits hogging the cpu or anything. Typically everything looks to be <1% cpu usage, with top being the biggest cpu hog at about 2%. The system doesn't seem too slow (for a pi), but it's unusual to see such high numbers. Nothing seems to be swapping: ubuntu@ubuntu:~$ free -m totalusedfree shared buff/cache available Mem:908 173 422 6 312 707 Swap: 0 0 0 ubuntu@ubuntu:~$ iostat Linux 5.0.0-1006-raspi2 (ubuntu)04/17/19_aarch64_ (4 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 1.640.151.572.060.00 94.57 Device tpskB_read/skB_wrtn/skB_readkB_wrtn loop0 0.08 0.50 0.00354 0 loop1 2.56 3.98 0.00 2805 0 loop2 0.01 0.01 0.00 4 0 mmcblk0 12.70 367.40 705.16 258830 496785 ubuntu@ubuntu:~$ vmstat 1 procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 0 0 0 514540 18004 2240720097 182 2564 76 2 2 94 2 0 0 0 0 514512 18004 22413600 0 2012 10136 142 0 0 94 5 0 0 0 0 514512 18004 22413600 0 0 10117 106 0 0 100 0 0 0 0 0 514512 18004 22413600 0 0 10121 98 0 0 100 0 0 0 0 0 514512 18012 22412800 0 2028 10129 141 0 0 93 7 0 0 0 0 514512 18012 22413600 0 0 10149 135 0 0 100 0 0 0 0 0 514512 18012 22413600 0 0 10108 97 0 0 100 0 0 0 0 0 514512 18012 22413600 0 2012 10125 126 0 0 95 5 0 0 0 0 514512 18012 22413600 0 0 10117 101 0 0 100 0 0 0 1 0 514512 18012 22413600 0 2012 10109 104 0 0 98 2 0 0 0 0 514512 18020 22412800 012 10139 150 0 0 96 4 0 0 0 0 514512 18020 22412800 0 0 10108 90 0 0 100 0 0 ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1825235 Title: Load average inexplicably high with 5.0 kernel on rpi Status in linux-raspi2 package in Ubuntu: New Bug description: Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the disco release candidate. After booting, the load average stays quite high, typically over 4.0. This persists, even if I leave it idle for several hours: ubuntu@ubuntu:~$ w 19:44:05 up 2:22, 1 user, load average: 4.16, 4.03, 4.01 /proc/loadavg is consistent with these numbers. But when I check top, there are no obvious culprits hogging the cpu or anything. Typically everything looks to be <1% cpu usage, with top being the biggest cpu hog at about 2%. The system doesn't seem too slow (for a pi), but it's unusual to see such high numbers. Nothing seems to be swapping: ubuntu@ubuntu:~$ free -m totalusedfree shared buff/cache available Mem:908 173 422 6 312 707 Swap: 0 0 0 ubuntu@ubuntu:~$ iostat Linux 5.0.0-1006-raspi2 (ubuntu) 04/17/19_aarch64_ (4 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 1.640.151.572.060.00 94.57 Device tpskB_read/skB_wrtn/skB_readkB_wrtn loop0 0.08 0.50 0.00354 0 loop1 2.56 3.98 0.00 2805 0 loop2 0.01 0.01 0.00 4 0 mmcblk0 12.70 367.40 705.16 258830 496785 ubuntu@ubuntu:~$ vmstat 1 procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 0 0 0
[Kernel-packages] [Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
This passes for me on 4.15.0-46.49 - (rev 82) kernel snap that is
currently in candidate
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810797
Title:
bluetooth controller not detected with 4.15 kernel
Status in linux package in Ubuntu:
Fix Released
Status in linux-snapdragon package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux-snapdragon source package in Bionic:
Invalid
Status in linux source package in Cosmic:
Fix Committed
Status in linux-snapdragon source package in Cosmic:
Invalid
Bug description:
Impact:
Upon boot, no hci device is available to userspace, thus bluetooth
communication is not possible.
Defect analysis:
The root of the problem lies in these two patches:
$ git log --online drivers/bluetooth/btqcomsmd.c
...
766154b Bluetooth: btqcomsmd: retrieve BD address from DT property
6e51811 Bluetooth: btqcomsmd: Add support for BD address setup
...
Qualcomm engineer found that btqcomsmd had no BD address burned in
(nor via ROM, neither internally) and it was always coming up with the
same address, probably derived from manufacturer ID and / or chip ID.
To fix this, they pushed the burden of generating a unique per-board
BD address to the Qualcomm bootloader and make it pass down via DTB to
the live kernel - and if no address was present in the DTB, the hci
was left unconfigured.
Fix:
So *technically* speaking, the kernel is correct in this case, it's
our dragonboard image (e.g. Ubuntu Core) that doesn't extract the
generated BD address from the Qualcomm bootloader and pass it down to
the kernel.
On the other hand, having Bluetooth working out of the box (even with
a dummy address), is a nice feature to have, so i slightly modified
Qualcomm's code introduced in the two above patches, and made the lack
of BD address in DTB non fatal:
if BD_is_present_in_DTB()
read_BD_and_apply_setup()
else
let_hci_core_generate_BD()
end if
And surrounded the modification in #ifdef...#endif brackets to keep it
local.
How to test:
By default, on a patched kernel, the hci device will have a default
address:
ubuntu@dragon410c:~$ hcitool dev
Devices:
hci000:00:00:00:5A:AD
the address " 00:00:00:00:5A:AD" might vary, but will be consistent
after every reboot.
The other option is to specify a custom BD address, e.g. using uboot
to manipulate the dtb - we assume the dtb was loaded in memory at
${fdt_addr}:
dragonboard410c => fdt addr ${fdt_addr}
dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
bt {
compatible = "qcom,wcnss-bt";
};
dragonboard410c => fdt resize
dragonboard410c => fdt set /soc/wcnss/smd-edge/wcnss/bt/ local-bd-
address [ 55 44 33 22 11 00 ]
dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
bt {
local-bd-address = [55 44 33 22 11 00];
compatible = "qcom,wcnss-bt";
};
then proceed with the rest of the boot process and check hci:
$ hcitool dev
Devices:
hci000:11:22:33:44:55
In both cases, blueooth work afterward, and can be used to communicate
with other devices:
ubuntu@dragon410c:~$ hcitool scan
Scanning ...
C0:BD:54:12:4E:D1 My dummy device
Regression potential:
None, the fix is surronded with #ifdef...#endif thus it doesn't exist
outside of it.
--
Using the core18 image from
http://cdimage.ubuntu.com/ubuntu-core/18/stable/current/
Kernel snap: 4.15.0-39.42 (72)
rfkill shows there is an hci0 device:
$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
But bluetoothctl does not detect any controller:
$ sudo bluetoothctl
08:58 Agent registered
08:58 [bluetooth]# list
[...no output...]
If you revert to the 4.4 kernel [4.4.0-1106.111 (76)] it works:
$ sudo bluetoothctl
[NEW] Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
Agent registered
[bluetooth]# list
Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
[bluetooth]# show
Controller 00:00:00:00:5A:AD
Name: BlueZ 5.47
Alias: BlueZ 5.47
Class: 0x
Powered: no
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID:
[Kernel-packages] [Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
I think we're waiting on a snap of this for testing. We already tested
and confirmed it worked on a snap that ppisati built (see comment #6 and
comment #8).
--
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/1810797
Title:
bluetooth controller not detected with 4.15 kernel
Status in linux package in Ubuntu:
Fix Released
Status in linux-snapdragon package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux-snapdragon source package in Bionic:
Invalid
Status in linux source package in Cosmic:
Fix Committed
Status in linux-snapdragon source package in Cosmic:
Invalid
Bug description:
Impact:
Upon boot, no hci device is available to userspace, thus bluetooth
communication is not possible.
Defect analysis:
The root of the problem lies in these two patches:
$ git log --online drivers/bluetooth/btqcomsmd.c
...
766154b Bluetooth: btqcomsmd: retrieve BD address from DT property
6e51811 Bluetooth: btqcomsmd: Add support for BD address setup
...
Qualcomm engineer found that btqcomsmd had no BD address burned in
(nor via ROM, neither internally) and it was always coming up with the
same address, probably derived from manufacturer ID and / or chip ID.
To fix this, they pushed the burden of generating a unique per-board
BD address to the Qualcomm bootloader and make it pass down via DTB to
the live kernel - and if no address was present in the DTB, the hci
was left unconfigured.
Fix:
So *technically* speaking, the kernel is correct in this case, it's
our dragonboard image (e.g. Ubuntu Core) that doesn't extract the
generated BD address from the Qualcomm bootloader and pass it down to
the kernel.
On the other hand, having Bluetooth working out of the box (even with
a dummy address), is a nice feature to have, so i slightly modified
Qualcomm's code introduced in the two above patches, and made the lack
of BD address in DTB non fatal:
if BD_is_present_in_DTB()
read_BD_and_apply_setup()
else
let_hci_core_generate_BD()
end if
And surrounded the modification in #ifdef...#endif brackets to keep it
local.
How to test:
By default, on a patched kernel, the hci device will have a default
address:
ubuntu@dragon410c:~$ hcitool dev
Devices:
hci000:00:00:00:5A:AD
the address " 00:00:00:00:5A:AD" might vary, but will be consistent
after every reboot.
The other option is to specify a custom BD address, e.g. using uboot
to manipulate the dtb - we assume the dtb was loaded in memory at
${fdt_addr}:
dragonboard410c => fdt addr ${fdt_addr}
dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
bt {
compatible = "qcom,wcnss-bt";
};
dragonboard410c => fdt resize
dragonboard410c => fdt set /soc/wcnss/smd-edge/wcnss/bt/ local-bd-
address [ 55 44 33 22 11 00 ]
dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
bt {
local-bd-address = [55 44 33 22 11 00];
compatible = "qcom,wcnss-bt";
};
then proceed with the rest of the boot process and check hci:
$ hcitool dev
Devices:
hci000:11:22:33:44:55
In both cases, blueooth work afterward, and can be used to communicate
with other devices:
ubuntu@dragon410c:~$ hcitool scan
Scanning ...
C0:BD:54:12:4E:D1 My dummy device
Regression potential:
None, the fix is surronded with #ifdef...#endif thus it doesn't exist
outside of it.
--
Using the core18 image from
http://cdimage.ubuntu.com/ubuntu-core/18/stable/current/
Kernel snap: 4.15.0-39.42 (72)
rfkill shows there is an hci0 device:
$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
But bluetoothctl does not detect any controller:
$ sudo bluetoothctl
08:58 Agent registered
08:58 [bluetooth]# list
[...no output...]
If you revert to the 4.4 kernel [4.4.0-1106.111 (76)] it works:
$ sudo bluetoothctl
[NEW] Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
Agent registered
[bluetooth]# list
Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
[bluetooth]# show
Controller 00:00:00:00:5A:AD
Name: BlueZ 5.47
Alias: BlueZ 5.47
Class: 0x
Powered: no
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: IrMC Sync
[Kernel-packages] [Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
I built an image with this kernel snap added to extra-snaps, and it
seems to find it now:
ubuntu@localhost:~$ sudo bluetoothctl
[NEW] Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
Agent registered
--
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/1810797
Title:
bluetooth controller not detected with 4.15 kernel
Status in linux package in Ubuntu:
Incomplete
Status in linux-snapdragon package in Ubuntu:
Invalid
Status in linux source package in Bionic:
New
Status in linux-snapdragon source package in Bionic:
Invalid
Bug description:
Impact:
Upon boot, no hci device is available to userspace, thus bluetooth
communication is not possible.
Defect analysis:
The root of the problem lies in these two patches:
$ git log --online drivers/bluetooth/btqcomsmd.c
...
766154b Bluetooth: btqcomsmd: retrieve BD address from DT property
6e51811 Bluetooth: btqcomsmd: Add support for BD address setup
...
Qualcomm engineer found that btqcomsmd had no BD address burned in
(nor via ROM, neither internally) and it was always coming up with the
same address, probably derived from manufacturer ID and / or chip ID.
To fix this, they pushed the burden of generating a unique per-board
BD address to the Qualcomm bootloader and make it pass down via DTB to
the live kernel - and if no address was present in the DTB, the hci
was left unconfigured.
Fix:
So *technically* speaking, the kernel is correct in this case, it's
our dragonboard image (e.g. Ubuntu Core) that doesn't extract the
generated BD address from the Qualcomm bootloader and pass it down to
the kernel.
On the other hand, having Bluetooth working out of the box (even with
a dummy address), is a nice feature to have, so i slightly modified
Qualcomm's code introduced in the two above patches, and made the lack
of BD address in DTB non fatal:
if BD_is_present_in_DTB()
read_BD_and_apply_setup()
else
let_hci_core_generate_BD()
end if
And surrounded the modification in #ifdef...#endif brackets to keep it
local.
How to test:
By default, on a patched kernel, the hci device will have a default
address:
ubuntu@dragon410c:~$ hcitool dev
Devices:
hci000:00:00:00:5A:AD
the address " 00:00:00:00:5A:AD" might vary, but will be consistent
after every reboot.
The other option is to specify a custom BD address, e.g. using uboot
to manipulate the dtb - we assume the dtb was loaded in memory at
${fdt_addr}:
dragonboard410c => fdt addr ${fdt_addr}
dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
bt {
compatible = "qcom,wcnss-bt";
};
dragonboard410c => fdt resize
dragonboard410c => fdt set /soc/wcnss/smd-edge/wcnss/bt/ local-bd-
address [ 55 44 33 22 11 00 ]
dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
bt {
local-bd-address = [55 44 33 22 11 00];
compatible = "qcom,wcnss-bt";
};
then proceed with the rest of the boot process and check hci:
$ hcitool dev
Devices:
hci000:11:22:33:44:55
In both cases, blueooth work afterward, and can be used to communicate
with other devices:
ubuntu@dragon410c:~$ hcitool scan
Scanning ...
C0:BD:54:12:4E:D1 My dummy device
Regression potential:
None, the fix is surronded with #ifdef...#endif thus it doesn't exist
outside of it.
--
Using the core18 image from
http://cdimage.ubuntu.com/ubuntu-core/18/stable/current/
Kernel snap: 4.15.0-39.42 (72)
rfkill shows there is an hci0 device:
$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
But bluetoothctl does not detect any controller:
$ sudo bluetoothctl
08:58 Agent registered
08:58 [bluetooth]# list
[...no output...]
If you revert to the 4.4 kernel [4.4.0-1106.111 (76)] it works:
$ sudo bluetoothctl
[NEW] Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
Agent registered
[bluetooth]# list
Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
[bluetooth]# show
Controller 00:00:00:00:5A:AD
Name: BlueZ 5.47
Alias: BlueZ 5.47
Class: 0x
Powered: no
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: Vendor specific
[Kernel-packages] [Bug 1799401] Re: linux: 4.4.0-139.165 -proposed tracker
on the snap testing, it fails test_095_kernel_symbols_missing from the kernel security tests because it is unable to read /proc/self/stack as a normal user. Can you confirm if this is expected? == FAIL: test_095_kernel_symbols_missing (test_kernel_security.KernelSecurityTest) kernel addresses in kallsyms and modules are zeroed out -- Traceback (most recent call last): File "/home/ubuntu/snap/checkbox-snappy/1418/.cache/plainbox/sessions/smoke-test-2018-10-30T13.32.02.session/CHECKBOX_DATA/test_kernel_security.py", line 1499, in test_095_kernel_symbols_missing self._check_pK_files(expected) File "/home/ubuntu/snap/checkbox-snappy/1418/.cache/plainbox/sessions/smoke-test-2018-10-30T13.32.02.session/CHECKBOX_DATA/test_kernel_security.py", line 1474, in _check_pK_files expected, retry=True) File "/home/ubuntu/snap/checkbox-snappy/1418/.cache/plainbox/sessions/smoke-test-2018-10-30T13.32.02.session/CHECKBOX_DATA/test_kernel_security.py", line 1378, in _read_twice self.assertEqual(rc, 0, regular) AssertionError: 1 != 0 : cat: /proc/self/stack: Permission denied -- 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/1799401 Title: linux: 4.4.0-139.165 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799403 (linux-aws), bug 1799404 (linux-lts-xenial) derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 (linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff snap-certification-testing: Ready verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797975] Re: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting
I also saw this on cosmic release candidate with rpi2. I ran apport- collect 1797975 as suggested but I'm not sure it really gathered anything new ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797975 Title: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting Status in linux package in Ubuntu: Confirmed Bug description: The follow error is shown in dmesg on my Raspberry Pi 2: [4.380151] device-mapper: uevent: version 1.0.3 [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-de...@redhat.com [4.396718] bcm2835-cpufreq: min=60 max=90 [4.407362] sdhci: Secure Digital Host Controller Interface driver [4.412699] sdhci: Copyright(c) Pierre Ossman [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, aborting... This may not be an issue at all, I don't know. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 22 11:11 seq crw-rw 1 root audio 116, 33 Jun 22 11:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-1004-raspi2 N/A linux-backports-modules-4.18.0-1004-raspi2 N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-1004-raspi2 armv7l 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/linux/+bug/1797975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797975] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1797975/+attachment/5201824/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797975 Title: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting Status in linux package in Ubuntu: Confirmed Bug description: The follow error is shown in dmesg on my Raspberry Pi 2: [4.380151] device-mapper: uevent: version 1.0.3 [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-de...@redhat.com [4.396718] bcm2835-cpufreq: min=60 max=90 [4.407362] sdhci: Secure Digital Host Controller Interface driver [4.412699] sdhci: Copyright(c) Pierre Ossman [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, aborting... This may not be an issue at all, I don't know. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 22 11:11 seq crw-rw 1 root audio 116, 33 Jun 22 11:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-1004-raspi2 N/A linux-backports-modules-4.18.0-1004-raspi2 N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-1004-raspi2 armv7l 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/linux/+bug/1797975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797975] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1797975/+attachment/5201818/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797975 Title: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting Status in linux package in Ubuntu: Confirmed Bug description: The follow error is shown in dmesg on my Raspberry Pi 2: [4.380151] device-mapper: uevent: version 1.0.3 [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-de...@redhat.com [4.396718] bcm2835-cpufreq: min=60 max=90 [4.407362] sdhci: Secure Digital Host Controller Interface driver [4.412699] sdhci: Copyright(c) Pierre Ossman [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, aborting... This may not be an issue at all, I don't know. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 22 11:11 seq crw-rw 1 root audio 116, 33 Jun 22 11:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-1004-raspi2 N/A linux-backports-modules-4.18.0-1004-raspi2 N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-1004-raspi2 armv7l 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/linux/+bug/1797975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797975] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1797975/+attachment/5201820/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797975 Title: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting Status in linux package in Ubuntu: Confirmed Bug description: The follow error is shown in dmesg on my Raspberry Pi 2: [4.380151] device-mapper: uevent: version 1.0.3 [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-de...@redhat.com [4.396718] bcm2835-cpufreq: min=60 max=90 [4.407362] sdhci: Secure Digital Host Controller Interface driver [4.412699] sdhci: Copyright(c) Pierre Ossman [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, aborting... This may not be an issue at all, I don't know. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 22 11:11 seq crw-rw 1 root audio 116, 33 Jun 22 11:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-1004-raspi2 N/A linux-backports-modules-4.18.0-1004-raspi2 N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-1004-raspi2 armv7l 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/linux/+bug/1797975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797975] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1797975/+attachment/5201819/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797975 Title: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting Status in linux package in Ubuntu: Confirmed Bug description: The follow error is shown in dmesg on my Raspberry Pi 2: [4.380151] device-mapper: uevent: version 1.0.3 [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-de...@redhat.com [4.396718] bcm2835-cpufreq: min=60 max=90 [4.407362] sdhci: Secure Digital Host Controller Interface driver [4.412699] sdhci: Copyright(c) Pierre Ossman [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, aborting... This may not be an issue at all, I don't know. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 22 11:11 seq crw-rw 1 root audio 116, 33 Jun 22 11:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-1004-raspi2 N/A linux-backports-modules-4.18.0-1004-raspi2 N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-1004-raspi2 armv7l 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/linux/+bug/1797975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797975] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1797975/+attachment/5201821/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797975 Title: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting Status in linux package in Ubuntu: Confirmed Bug description: The follow error is shown in dmesg on my Raspberry Pi 2: [4.380151] device-mapper: uevent: version 1.0.3 [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-de...@redhat.com [4.396718] bcm2835-cpufreq: min=60 max=90 [4.407362] sdhci: Secure Digital Host Controller Interface driver [4.412699] sdhci: Copyright(c) Pierre Ossman [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, aborting... This may not be an issue at all, I don't know. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 22 11:11 seq crw-rw 1 root audio 116, 33 Jun 22 11:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-1004-raspi2 N/A linux-backports-modules-4.18.0-1004-raspi2 N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-1004-raspi2 armv7l 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/linux/+bug/1797975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797975] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1797975/+attachment/5201822/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797975 Title: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting Status in linux package in Ubuntu: Confirmed Bug description: The follow error is shown in dmesg on my Raspberry Pi 2: [4.380151] device-mapper: uevent: version 1.0.3 [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-de...@redhat.com [4.396718] bcm2835-cpufreq: min=60 max=90 [4.407362] sdhci: Secure Digital Host Controller Interface driver [4.412699] sdhci: Copyright(c) Pierre Ossman [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, aborting... This may not be an issue at all, I don't know. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 22 11:11 seq crw-rw 1 root audio 116, 33 Jun 22 11:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-1004-raspi2 N/A linux-backports-modules-4.18.0-1004-raspi2 N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-1004-raspi2 armv7l 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/linux/+bug/1797975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797975] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1797975/+attachment/5201823/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797975 Title: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting Status in linux package in Ubuntu: Confirmed Bug description: The follow error is shown in dmesg on my Raspberry Pi 2: [4.380151] device-mapper: uevent: version 1.0.3 [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-de...@redhat.com [4.396718] bcm2835-cpufreq: min=60 max=90 [4.407362] sdhci: Secure Digital Host Controller Interface driver [4.412699] sdhci: Copyright(c) Pierre Ossman [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, aborting... This may not be an issue at all, I don't know. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 22 11:11 seq crw-rw 1 root audio 116, 33 Jun 22 11:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-1004-raspi2 N/A linux-backports-modules-4.18.0-1004-raspi2 N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-1004-raspi2 armv7l 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/linux/+bug/1797975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797975] apport information
ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 22 11:11 seq crw-rw+ 1 root audio 116, 33 Jun 22 11:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa21041 bcm2709.serial=0x9e293c87 smsc95xx.macaddr=B8:27:EB:29:3C:87 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: User Name 4.18.0-1005.7-raspi2 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-1005-raspi2 N/A linux-backports-modules-4.18.0-1005-raspi2 N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-1005-raspi2 armv7l UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True -- 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/1797975 Title: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting Status in linux package in Ubuntu: Confirmed Bug description: The follow error is shown in dmesg on my Raspberry Pi 2: [4.380151] device-mapper: uevent: version 1.0.3 [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-de...@redhat.com [4.396718] bcm2835-cpufreq: min=60 max=90 [4.407362] sdhci: Secure Digital Host Controller Interface driver [4.412699] sdhci: Copyright(c) Pierre Ossman [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, aborting... This may not be an issue at all, I don't know. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 22 11:11 seq crw-rw 1 root audio 116, 33 Jun 22 11:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-1004-raspi2 N/A linux-backports-modules-4.18.0-1004-raspi2 N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-1004-raspi2 armv7l 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:
[Kernel-packages] [Bug 1396188] Re: linux-ti-omap4: 3.2.0-1457.77 -proposed tracker qa-testing-passed
** Tags added: qa-testing-passed ** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1396188 Title: linux-ti-omap4: 3.2.0-1457.77 -proposed tracker qa-testing-passed Status in Kernel SRU Workflow: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 15:03 UTC kernel-stable-master-bug:1396072 kernel-stable-Certification-testing-end:Wednesday, 26. November 2014 21:02 UTC kernel-stable-Prepare-package-end:Thursday, 27. November 2014 14:02 UTC kernel-stable-Promote-to-proposed-start:Thursday, 27. November 2014 14:02 UTC ppa-package-testing-start:Thursday, 27. November 2014 14:02 UTC kernel-stable-Promote-to-proposed-end:Thursday, 27. November 2014 21:17 UTC kernel-stable-Security-signoff-start:Thursday, 27. November 2014 23:02 UTC kernel-stable-Verification-testing-start:Thursday, 27. November 2014 23:02 UTC kernel-stable-Regression-testing-start:Thursday, 27. November 2014 23:02 UTC kernel-stable-Security-signoff-end:Thursday, 04. December 2014 14:03 UTC kernel-stable-phase:OnHold kernel-stable-phase-changed:Sunday, 07. December 2014 06:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1396188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1396188] Re: linux-ti-omap4: 3.2.0-1457.77 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Summary changed: - linux-ti-omap4: 3.2.0-1457.77 -proposed tracker + linux-ti-omap4: 3.2.0-1457.77 -proposed tracker qa-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1396188 Title: linux-ti-omap4: 3.2.0-1457.77 -proposed tracker qa-testing-passed Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 15:03 UTC kernel-stable-master-bug:1396072 kernel-stable-Certification-testing-end:Wednesday, 26. November 2014 21:02 UTC kernel-stable-Prepare-package-end:Thursday, 27. November 2014 14:02 UTC kernel-stable-Promote-to-proposed-start:Thursday, 27. November 2014 14:02 UTC ppa-package-testing-start:Thursday, 27. November 2014 14:02 UTC kernel-stable-Promote-to-proposed-end:Thursday, 27. November 2014 21:17 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 27. November 2014 23:02 UTC kernel-stable-Security-signoff-start:Thursday, 27. November 2014 23:02 UTC kernel-stable-Verification-testing-start:Thursday, 27. November 2014 23:02 UTC kernel-stable-Regression-testing-start:Thursday, 27. November 2014 23:02 UTC kernel-stable-Security-signoff-end:Thursday, 04. December 2014 14:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1396188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1396112] Re: linux: 3.13.0-41.70 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-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/1396112 Title: linux: 3.13.0-41.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-41.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 12:01 UTC kernel-stable-Prepare-package-end:Tuesday, 25. November 2014 22:56 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 25. November 2014 22:56 UTC ppa-package-testing-start:Tuesday, 25. November 2014 22:56 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 26. November 2014 16:56 UTC kernel-stable-Certification-testing-start:Wednesday, 26. November 2014 16:56 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 26. November 2014 16:55 UTC kernel-stable-Regression-testing-start:Wednesday, 26. November 2014 16:56 UTC kernel-stable-Security-signoff-start:Wednesday, 26. November 2014 16:56 UTC kernel-stable-Verification-testing-start:Wednesday, 26. November 2014 16:56 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1396112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1396188] Re: linux-ti-omap4: 3.2.0-1457.77 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1396188 Title: linux-ti-omap4: 3.2.0-1457.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 15:03 UTC kernel-stable-master-bug:1396072 kernel-stable-Certification-testing-end:Wednesday, 26. November 2014 21:02 UTC kernel-stable-Prepare-package-end:Thursday, 27. November 2014 14:02 UTC kernel-stable-Promote-to-proposed-start:Thursday, 27. November 2014 14:02 UTC ppa-package-testing-start:Thursday, 27. November 2014 14:02 UTC kernel-stable-Promote-to-proposed-end:Thursday, 27. November 2014 21:17 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 27. November 2014 23:02 UTC kernel-stable-Security-signoff-start:Thursday, 27. November 2014 23:02 UTC kernel-stable-Verification-testing-start:Thursday, 27. November 2014 23:02 UTC kernel-stable-Regression-testing-start:Thursday, 27. November 2014 23:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1396188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1396112] Re: linux: 3.13.0-41.70 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- 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/1396112 Title: linux: 3.13.0-41.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-41.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 25. November 2014 12:01 UTC kernel-stable-Prepare-package-end:Tuesday, 25. November 2014 22:56 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 25. November 2014 22:56 UTC ppa-package-testing-start:Tuesday, 25. November 2014 22:56 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 26. November 2014 16:56 UTC kernel-stable-Certification-testing-start:Wednesday, 26. November 2014 16:56 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 26. November 2014 16:55 UTC kernel-stable-Regression-testing-start:Wednesday, 26. November 2014 16:56 UTC kernel-stable-Security-signoff-start:Wednesday, 26. November 2014 16:56 UTC kernel-stable-Verification-testing-start:Wednesday, 26. November 2014 16:56 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1396112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1390175] Re: linux-ti-omap4: 3.2.0-1456.76 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1390175 Title: linux-ti-omap4: 3.2.0-1456.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 06. November 2014 18:03 UTC kernel-stable-master-bug:1390048 kernel-stable-Certification-testing-end:Tuesday, 11. November 2014 11:03 UTC kernel-stable-Prepare-package-end:Tuesday, 11. November 2014 18:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 11. November 2014 18:04 UTC ppa-package-testing-start:Tuesday, 11. November 2014 18:04 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 12. November 2014 02:01 UTC kernel-stable-Security-signoff-start:Wednesday, 12. November 2014 03:02 UTC kernel-stable-Verification-testing-start:Wednesday, 12. November 2014 03:01 UTC kernel-stable-Regression-testing-start:Wednesday, 12. November 2014 03:02 UTC kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Wednesday, 12. November 2014 03:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1390175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1390048] Re: linux: 3.2.0-72.107 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-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/1390048 Title: linux: 3.2.0-72.107 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: Confirmed Bug description: This bug is for tracking the 3.2.0-72.107 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 06. November 2014 11:47 UTC kernel-stable-Prepare-package-end:Thursday, 06. November 2014 18:09 UTC kernel-stable-Promote-to-proposed-start:Thursday, 06. November 2014 18:09 UTC ppa-package-testing-start:Thursday, 06. November 2014 18:09 UTC kernel-stable-Promote-to-proposed-end:Friday, 07. November 2014 18:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 07. November 2014 19:02 UTC kernel-stable-Verification-testing-start:Friday, 07. November 2014 19:02 UTC kernel-stable-Certification-testing-start:Friday, 07. November 2014 19:02 UTC kernel-stable-Security-signoff-start:Friday, 07. November 2014 19:02 UTC kernel-stable-Regression-testing-start:Friday, 07. November 2014 19:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1390048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1390176] Re: linux-armadaxp: 3.2.0-1641.59 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1390176 Title: linux-armadaxp: 3.2.0-1641.59 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1641.59 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 06. November 2014 18:05 UTC kernel-stable-master-bug:1390048 kernel-stable-Certification-testing-end:Friday, 07. November 2014 06:03 UTC kernel-stable-Security-signoff-end:Friday, 07. November 2014 06:03 UTC kernel-stable-Prepare-package-end:Friday, 07. November 2014 08:02 UTC kernel-stable-Promote-to-proposed-start:Friday, 07. November 2014 08:02 UTC ppa-package-testing-start:Friday, 07. November 2014 08:02 UTC kernel-stable-Promote-to-proposed-end:Friday, 07. November 2014 18:02 UTC kernel-stable-Verification-testing-start:Friday, 07. November 2014 19:03 UTC kernel-stable-Regression-testing-start:Friday, 07. November 2014 19:03 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Saturday, 08. November 2014 16:01 UTC kernel-stable-Verification-testing-end:Saturday, 08. November 2014 16:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1390176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1390048] Re: linux: 3.2.0-72.107 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- 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/1390048 Title: linux: 3.2.0-72.107 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: Confirmed Bug description: This bug is for tracking the 3.2.0-72.107 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 06. November 2014 11:47 UTC kernel-stable-Prepare-package-end:Thursday, 06. November 2014 18:09 UTC kernel-stable-Promote-to-proposed-start:Thursday, 06. November 2014 18:09 UTC ppa-package-testing-start:Thursday, 06. November 2014 18:09 UTC kernel-stable-Promote-to-proposed-end:Friday, 07. November 2014 18:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 07. November 2014 19:02 UTC kernel-stable-Verification-testing-start:Friday, 07. November 2014 19:02 UTC kernel-stable-Certification-testing-start:Friday, 07. November 2014 19:02 UTC kernel-stable-Security-signoff-start:Friday, 07. November 2014 19:02 UTC kernel-stable-Regression-testing-start:Friday, 07. November 2014 19:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1390048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1389170] Re: linux: 3.16.0-25.33 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) ** Tags added: qa-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/1389170 Title: linux: 3.16.0-25.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Utopic: Confirmed Bug description: This bug is for tracking the 3.16.0-25.33 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 04. November 2014 10:43 UTC kernel-stable-Prepare-package-end:Tuesday, 04. November 2014 21:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 04. November 2014 21:03 UTC ppa-package-testing-start:Tuesday, 04. November 2014 21:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 05. November 2014 01:44 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Verification-testing-start:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Certification-testing-start:Wednesday, 05. November 2014 03:04 UTC kernel-stable-Security-signoff-start:Wednesday, 05. November 2014 03:05 UTC kernel-stable-Regression-testing-start:Wednesday, 05. November 2014 03:05 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1389170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1389060] Re: linux-armadaxp: 3.2.0-1640.58 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1389060 Title: linux-armadaxp: 3.2.0-1640.58 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 04. November 2014 03:04 UTC kernel-stable-master-bug:1388903 kernel-stable-Certification-testing-end:Tuesday, 04. November 2014 07:01 UTC kernel-stable-Security-signoff-end:Tuesday, 04. November 2014 07:01 UTC kernel-stable-Prepare-package-end:Tuesday, 04. November 2014 10:05 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 04. November 2014 10:05 UTC ppa-package-testing-start:Tuesday, 04. November 2014 10:05 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 04. November 2014 12:01 UTC kernel-stable-Verification-testing-start:Tuesday, 04. November 2014 13:03 UTC kernel-stable-Regression-testing-start:Tuesday, 04. November 2014 13:03 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Tuesday, 04. November 2014 15:01 UTC kernel-stable-Verification-testing-end:Tuesday, 04. November 2014 15:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1389060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1373656] Re: linux-armadaxp: 3.2.0-1639.57 -proposed tracker
CONFIG_DEBUG_RODATA was the only failure in regression testing ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1373656 Title: linux-armadaxp: 3.2.0-1639.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1639.57 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 24. September 2014 23:02 UTC kernel-stable-master-bug:1372522 kernel-stable-Certification-testing-end:Thursday, 25. September 2014 15:02 UTC kernel-stable-Security-signoff-end:Thursday, 25. September 2014 15:03 UTC kernel-stable-Prepare-package-end:Thursday, 25. September 2014 15:03 UTC kernel-stable-Promote-to-proposed-start:Thursday, 25. September 2014 15:03 UTC ppa-package-testing-start:Thursday, 25. September 2014 15:03 UTC kernel-stable-Promote-to-proposed-end:Thursday, 25. September 2014 22:17 UTC kernel-stable-Verification-testing-start:Friday, 26. September 2014 01:01 UTC kernel-stable-Regression-testing-start:Friday, 26. September 2014 01:01 UTC kernel-stable-Verification-testing-end:Friday, 26. September 2014 04:04 UTC kernel-stable-phase:CopyToUpdates kernel-stable-phase-changed:Wednesday, 08. October 2014 11:04 UTC kernel-stable-Promote-to-updates-start:Wednesday, 08. October 2014 11:04 UTC kernel-stable-Regression-testing-end:Wednesday, 08. October 2014 11:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1373656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1372683] Re: linux-ti-omap4: 3.2.0-1455.75 -proposed tracker
For regression testing, the only failures I got were the usual CONFIG_RODATA failure and the timeout with one of the ecryptfs tests seen on slow platforms like panda+usbstorage. ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1372683 Title: linux-ti-omap4: 3.2.0-1455.75 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 22. September 2014 23:20 UTC kernel-stable-master-bug:1372522 kernel-stable-Certification-testing-end:Tuesday, 23. September 2014 09:06 UTC kernel-stable-Prepare-package-end:Saturday, 27. September 2014 17:02 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. September 2014 17:02 UTC ppa-package-testing-start:Saturday, 27. September 2014 17:02 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 01. October 2014 20:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 01. October 2014 22:01 UTC kernel-stable-Security-signoff-start:Wednesday, 01. October 2014 22:01 UTC kernel-stable-Verification-testing-start:Wednesday, 01. October 2014 22:01 UTC kernel-stable-Regression-testing-start:Wednesday, 01. October 2014 22:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1372683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1372683] Re: linux-ti-omap4: 3.2.0-1455.75 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1372683 Title: linux-ti-omap4: 3.2.0-1455.75 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 22. September 2014 23:20 UTC kernel-stable-master-bug:1372522 kernel-stable-Certification-testing-end:Tuesday, 23. September 2014 09:06 UTC kernel-stable-Prepare-package-end:Saturday, 27. September 2014 17:02 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. September 2014 17:02 UTC ppa-package-testing-start:Saturday, 27. September 2014 17:02 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 01. October 2014 20:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 01. October 2014 22:01 UTC kernel-stable-Security-signoff-start:Wednesday, 01. October 2014 22:01 UTC kernel-stable-Verification-testing-start:Wednesday, 01. October 2014 22:01 UTC kernel-stable-Regression-testing-start:Wednesday, 01. October 2014 22:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1372683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1373656] Re: linux-armadaxp: 3.2.0-1639.57 -proposed tracker
Regression testing is blocked at the moment due to a failed hard drive on the armada we have in the lab. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1373656 Title: linux-armadaxp: 3.2.0-1639.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1639.57 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 24. September 2014 23:02 UTC kernel-stable-master-bug:1372522 kernel-stable-Certification-testing-end:Thursday, 25. September 2014 15:02 UTC kernel-stable-Security-signoff-end:Thursday, 25. September 2014 15:03 UTC kernel-stable-Prepare-package-end:Thursday, 25. September 2014 15:03 UTC kernel-stable-Promote-to-proposed-start:Thursday, 25. September 2014 15:03 UTC ppa-package-testing-start:Thursday, 25. September 2014 15:03 UTC kernel-stable-Promote-to-proposed-end:Thursday, 25. September 2014 22:17 UTC kernel-stable-Verification-testing-start:Friday, 26. September 2014 01:01 UTC kernel-stable-Regression-testing-start:Friday, 26. September 2014 01:01 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Friday, 26. September 2014 04:04 UTC kernel-stable-Verification-testing-end:Friday, 26. September 2014 04:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1373656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1373656] Re: linux-armadaxp: 3.2.0-1639.57 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1373656 Title: linux-armadaxp: 3.2.0-1639.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1639.57 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 24. September 2014 23:02 UTC kernel-stable-master-bug:1372522 kernel-stable-Certification-testing-end:Thursday, 25. September 2014 15:02 UTC kernel-stable-Security-signoff-end:Thursday, 25. September 2014 15:03 UTC kernel-stable-Prepare-package-end:Thursday, 25. September 2014 15:03 UTC kernel-stable-Promote-to-proposed-start:Thursday, 25. September 2014 15:03 UTC ppa-package-testing-start:Thursday, 25. September 2014 15:03 UTC kernel-stable-Promote-to-proposed-end:Thursday, 25. September 2014 22:17 UTC kernel-stable-Verification-testing-start:Friday, 26. September 2014 01:01 UTC kernel-stable-Regression-testing-start:Friday, 26. September 2014 01:01 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Friday, 26. September 2014 04:04 UTC kernel-stable-Verification-testing-end:Friday, 26. September 2014 04:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1373656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1372522] Re: linux: 3.2.0-70.105 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- 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/1372522 Title: linux: 3.2.0-70.105 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-70.105 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 22. September 2014 15:44 UTC kernel-stable-Prepare-package-end:Monday, 22. September 2014 23:25 UTC kernel-stable-Promote-to-proposed-start:Monday, 22. September 2014 23:25 UTC ppa-package-testing-start:Monday, 22. September 2014 23:25 UTC kernel-stable-Promote-to-proposed-end:Friday, 26. September 2014 18:24 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 26. September 2014 20:00 UTC kernel-stable-Verification-testing-start:Friday, 26. September 2014 20:00 UTC kernel-stable-Certification-testing-start:Friday, 26. September 2014 20:01 UTC kernel-stable-Security-signoff-start:Friday, 26. September 2014 20:01 UTC kernel-stable-Regression-testing-start:Friday, 26. September 2014 20:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1372522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1372522] Re: linux: 3.2.0-70.105 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-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/1372522 Title: linux: 3.2.0-70.105 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-70.105 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 22. September 2014 15:44 UTC kernel-stable-Prepare-package-end:Monday, 22. September 2014 23:25 UTC kernel-stable-Promote-to-proposed-start:Monday, 22. September 2014 23:25 UTC ppa-package-testing-start:Monday, 22. September 2014 23:25 UTC kernel-stable-Promote-to-proposed-end:Friday, 26. September 2014 18:24 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 26. September 2014 20:00 UTC kernel-stable-Verification-testing-start:Friday, 26. September 2014 20:00 UTC kernel-stable-Certification-testing-start:Friday, 26. September 2014 20:01 UTC kernel-stable-Security-signoff-start:Friday, 26. September 2014 20:01 UTC kernel-stable-Regression-testing-start:Friday, 26. September 2014 20:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1372522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364291] Re: linux-armadaxp: 3.2.0-1638.55 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1364291 Title: linux-armadaxp: 3.2.0-1638.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1638.55 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 09:04 UTC kernel-stable-master-bug:1364208 kernel-stable-Certification-testing-end:Wednesday, 03. September 2014 03:01 UTC kernel-stable-Security-signoff-end:Wednesday, 03. September 2014 03:01 UTC kernel-stable-Prepare-package-end:Wednesday, 03. September 2014 05:02 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 03. September 2014 05:02 UTC ppa-package-testing-start:Wednesday, 03. September 2014 05:02 UTC kernel-stable-Promote-to-proposed-end:Thursday, 04. September 2014 19:41 UTC kernel-stable-Verification-testing-start:Thursday, 04. September 2014 21:05 UTC kernel-stable-Regression-testing-start:Thursday, 04. September 2014 21:05 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Friday, 05. September 2014 02:02 UTC kernel-stable-Verification-testing-end:Friday, 05. September 2014 02:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364290] Re: linux-ti-omap4: 3.2.0-1453.73 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1364290 Title: linux-ti-omap4: 3.2.0-1453.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 09:01 UTC kernel-stable-master-bug:1364208 kernel-stable-Certification-testing-end:Wednesday, 03. September 2014 15:00 UTC kernel-stable-Prepare-package-end:Thursday, 04. September 2014 18:01 UTC kernel-stable-Promote-to-proposed-start:Thursday, 04. September 2014 18:01 UTC ppa-package-testing-start:Thursday, 04. September 2014 18:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 04. September 2014 19:43 UTC kernel-stable-Security-signoff-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-Verification-testing-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-Regression-testing-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 04. September 2014 21:05 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364290] Re: linux-ti-omap4: 3.2.0-1453.73 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1364290 Title: linux-ti-omap4: 3.2.0-1453.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 09:01 UTC kernel-stable-master-bug:1364208 kernel-stable-Certification-testing-end:Wednesday, 03. September 2014 15:00 UTC kernel-stable-Prepare-package-end:Thursday, 04. September 2014 18:01 UTC kernel-stable-Promote-to-proposed-start:Thursday, 04. September 2014 18:01 UTC ppa-package-testing-start:Thursday, 04. September 2014 18:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 04. September 2014 19:43 UTC kernel-stable-Security-signoff-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-Verification-testing-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-Regression-testing-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 04. September 2014 21:05 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364291] Re: linux-armadaxp: 3.2.0-1638.55 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1364291 Title: linux-armadaxp: 3.2.0-1638.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1638.55 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 09:04 UTC kernel-stable-master-bug:1364208 kernel-stable-Certification-testing-end:Wednesday, 03. September 2014 03:01 UTC kernel-stable-Security-signoff-end:Wednesday, 03. September 2014 03:01 UTC kernel-stable-Prepare-package-end:Wednesday, 03. September 2014 05:02 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 03. September 2014 05:02 UTC ppa-package-testing-start:Wednesday, 03. September 2014 05:02 UTC kernel-stable-Promote-to-proposed-end:Thursday, 04. September 2014 19:41 UTC kernel-stable-Verification-testing-start:Thursday, 04. September 2014 21:05 UTC kernel-stable-Regression-testing-start:Thursday, 04. September 2014 21:05 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Friday, 05. September 2014 02:02 UTC kernel-stable-Verification-testing-end:Friday, 05. September 2014 02:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1356455] Re: linux-armadaxp: 3.2.0-1637.54 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1356455 Title: linux-armadaxp: 3.2.0-1637.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1637.54 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 13. August 2014 16:03 UTC kernel-stable-master-bug:1355387 kernel-stable-Certification-testing-end:Thursday, 14. August 2014 08:02 UTC kernel-stable-Security-signoff-end:Thursday, 14. August 2014 08:02 UTC kernel-stable-Prepare-package-end:Thursday, 14. August 2014 11:02 UTC kernel-stable-Promote-to-proposed-start:Thursday, 14. August 2014 11:02 UTC ppa-package-testing-start:Thursday, 14. August 2014 11:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 19. August 2014 19:01 UTC kernel-stable-Verification-testing-start:Tuesday, 19. August 2014 20:01 UTC kernel-stable-Regression-testing-start:Tuesday, 19. August 2014 20:01 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Wednesday, 20. August 2014 06:00 UTC kernel-stable-Verification-testing-end:Wednesday, 20. August 2014 06:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1356455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355387] Re: linux: 3.2.0-68.102 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-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/1355387 Title: linux: 3.2.0-68.102 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-68.102 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 11. August 2014 19:03 UTC kernel-stable-Prepare-package-end:Wednesday, 13. August 2014 16:07 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 13. August 2014 16:07 UTC ppa-package-testing-start:Wednesday, 13. August 2014 16:07 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 19. August 2014 18:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 19. August 2014 19:00 UTC kernel-stable-Verification-testing-start:Tuesday, 19. August 2014 19:00 UTC kernel-stable-Certification-testing-start:Tuesday, 19. August 2014 19:00 UTC kernel-stable-Security-signoff-start:Tuesday, 19. August 2014 19:00 UTC kernel-stable-Regression-testing-start:Tuesday, 19. August 2014 19:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1355387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1356455] Re: linux-armadaxp: 3.2.0-1637.54 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1356455 Title: linux-armadaxp: 3.2.0-1637.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1637.54 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 13. August 2014 16:03 UTC kernel-stable-master-bug:1355387 kernel-stable-Certification-testing-end:Thursday, 14. August 2014 08:02 UTC kernel-stable-Security-signoff-end:Thursday, 14. August 2014 08:02 UTC kernel-stable-Prepare-package-end:Thursday, 14. August 2014 11:02 UTC kernel-stable-Promote-to-proposed-start:Thursday, 14. August 2014 11:02 UTC ppa-package-testing-start:Thursday, 14. August 2014 11:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 19. August 2014 19:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 19. August 2014 20:01 UTC kernel-stable-Verification-testing-start:Tuesday, 19. August 2014 20:01 UTC kernel-stable-Regression-testing-start:Tuesday, 19. August 2014 20:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1356455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355387] Re: linux: 3.2.0-68.102 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- 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/1355387 Title: linux: 3.2.0-68.102 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-68.102 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 11. August 2014 19:03 UTC kernel-stable-Prepare-package-end:Wednesday, 13. August 2014 16:07 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 13. August 2014 16:07 UTC ppa-package-testing-start:Wednesday, 13. August 2014 16:07 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 19. August 2014 18:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 19. August 2014 19:00 UTC kernel-stable-Verification-testing-start:Tuesday, 19. August 2014 19:00 UTC kernel-stable-Certification-testing-start:Tuesday, 19. August 2014 19:00 UTC kernel-stable-Security-signoff-start:Tuesday, 19. August 2014 19:00 UTC kernel-stable-Regression-testing-start:Tuesday, 19. August 2014 19:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1355387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349897] Re: linux: 3.13.0-33.58 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-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/1349897 Title: linux: 3.13.0-33.58 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.13.0-33.58 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 29. July 2014 15:09 UTC kernel-stable-Prepare-package-end:Wednesday, 30. July 2014 21:05 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 30. July 2014 21:05 UTC ppa-package-testing-start:Wednesday, 30. July 2014 21:05 UTC kernel-stable-Promote-to-proposed-end:Friday, 08. August 2014 22:00 UTC kernel-stable-Verification-testing-start:Friday, 08. August 2014 23:01 UTC kernel-stable-Certification-testing-start:Friday, 08. August 2014 23:01 UTC kernel-stable-Security-signoff-start:Friday, 08. August 2014 23:01 UTC kernel-stable-Regression-testing-start:Friday, 08. August 2014 23:01 UTC kernel-stable-Certification-testing-end:Monday, 11. August 2014 20:00 UTC kernel-stable-Promote-to-updates-end:Tuesday, 12. August 2014 00:01 UTC kernel-stable-phase:Released kernel-stable-phase-changed:Tuesday, 12. August 2014 02:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1349897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349897] Re: linux: 3.13.0-33.58 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- 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/1349897 Title: linux: 3.13.0-33.58 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.13.0-33.58 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 29. July 2014 15:09 UTC kernel-stable-Prepare-package-end:Wednesday, 30. July 2014 21:05 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 30. July 2014 21:05 UTC ppa-package-testing-start:Wednesday, 30. July 2014 21:05 UTC kernel-stable-Promote-to-proposed-end:Friday, 08. August 2014 22:00 UTC kernel-stable-Verification-testing-start:Friday, 08. August 2014 23:01 UTC kernel-stable-Certification-testing-start:Friday, 08. August 2014 23:01 UTC kernel-stable-Security-signoff-start:Friday, 08. August 2014 23:01 UTC kernel-stable-Regression-testing-start:Friday, 08. August 2014 23:01 UTC kernel-stable-Certification-testing-end:Monday, 11. August 2014 20:00 UTC kernel-stable-Promote-to-updates-end:Tuesday, 12. August 2014 00:01 UTC kernel-stable-phase:Released kernel-stable-phase-changed:Tuesday, 12. August 2014 02:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1349897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1336143] Re: linux-ti-omap4: 3.2.0-1451.70 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1336143 Title: linux-ti-omap4: 3.2.0-1451.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 01. July 2014 04:53 UTC kernel-stable-master-bug:1338654 kernel-stable-Certification-testing-end:Thursday, 03. July 2014 01:55 UTC kernel-stable-Prepare-package-end:Wednesday, 09. July 2014 17:00 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 09. July 2014 17:00 UTC ppa-package-testing-start:Wednesday, 09. July 2014 17:00 UTC kernel-stable-Promote-to-proposed-end:Friday, 11. July 2014 16:17 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 11. July 2014 18:01 UTC kernel-stable-Security-signoff-start:Friday, 11. July 2014 18:01 UTC kernel-stable-Verification-testing-start:Friday, 11. July 2014 18:01 UTC kernel-stable-Regression-testing-start:Friday, 11. July 2014 18:01 UTC kernel-stable-Regression-testing-end:Tuesday, 15. July 2014 16:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1336143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1336143] Re: linux-ti-omap4: 3.2.0-1451.70 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1336143 Title: linux-ti-omap4: 3.2.0-1451.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 01. July 2014 04:53 UTC kernel-stable-master-bug:1338654 kernel-stable-Certification-testing-end:Thursday, 03. July 2014 01:55 UTC kernel-stable-Prepare-package-end:Wednesday, 09. July 2014 17:00 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 09. July 2014 17:00 UTC ppa-package-testing-start:Wednesday, 09. July 2014 17:00 UTC kernel-stable-Promote-to-proposed-end:Friday, 11. July 2014 16:17 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 11. July 2014 18:01 UTC kernel-stable-Security-signoff-start:Friday, 11. July 2014 18:01 UTC kernel-stable-Verification-testing-start:Friday, 11. July 2014 18:01 UTC kernel-stable-Regression-testing-start:Friday, 11. July 2014 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1336143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338654] Re: linux: 3.2.0-67.100 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-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/1338654 Title: linux: 3.2.0-67.100 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: Confirmed Bug description: This bug is for tracking the 3.2.0-67.100 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 07. July 2014 16:11 UTC kernel-stable-Prepare-package-end:Tuesday, 08. July 2014 04:12 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 08. July 2014 04:12 UTC ppa-package-testing-start:Tuesday, 08. July 2014 04:12 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 09. July 2014 22:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 09. July 2014 23:01 UTC kernel-stable-Verification-testing-start:Wednesday, 09. July 2014 23:01 UTC kernel-stable-Certification-testing-start:Wednesday, 09. July 2014 23:01 UTC kernel-stable-Security-signoff-start:Wednesday, 09. July 2014 23:01 UTC kernel-stable-Regression-testing-start:Wednesday, 09. July 2014 23:01 UTC kernel-stable-Regression-testing-end:Friday, 11. July 2014 22:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1338654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338524] Re: linux: 3.13.0-32.56 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- 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/1338524 Title: linux: 3.13.0-32.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-32.56 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 07. July 2014 10:33 UTC kernel-stable-Prepare-package-end:Monday, 07. July 2014 18:08 UTC kernel-stable-Promote-to-proposed-start:Monday, 07. July 2014 18:08 UTC ppa-package-testing-start:Monday, 07. July 2014 18:08 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 09. July 2014 13:57 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 09. July 2014 15:01 UTC kernel-stable-Verification-testing-start:Wednesday, 09. July 2014 15:01 UTC kernel-stable-Certification-testing-start:Wednesday, 09. July 2014 15:01 UTC kernel-stable-Security-signoff-start:Wednesday, 09. July 2014 15:01 UTC kernel-stable-Regression-testing-start:Wednesday, 09. July 2014 15:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1338524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338556] Re: linux: 3.11.0-26.44 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- 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/1338556 Title: linux: 3.11.0-26.44 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-26.44 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 07. July 2014 12:18 UTC kernel-stable-Prepare-package-end:Monday, 07. July 2014 20:10 UTC kernel-stable-Promote-to-proposed-start:Monday, 07. July 2014 20:10 UTC ppa-package-testing-start:Monday, 07. July 2014 20:10 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 09. July 2014 14:36 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 09. July 2014 16:02 UTC kernel-stable-Verification-testing-start:Wednesday, 09. July 2014 16:02 UTC kernel-stable-Certification-testing-start:Wednesday, 09. July 2014 16:02 UTC kernel-stable-Security-signoff-start:Wednesday, 09. July 2014 16:03 UTC kernel-stable-Regression-testing-start:Wednesday, 09. July 2014 16:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1338556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338524] Re: linux: 3.13.0-32.56 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-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/1338524 Title: linux: 3.13.0-32.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-32.56 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 07. July 2014 10:33 UTC kernel-stable-Prepare-package-end:Monday, 07. July 2014 18:08 UTC kernel-stable-Promote-to-proposed-start:Monday, 07. July 2014 18:08 UTC ppa-package-testing-start:Monday, 07. July 2014 18:08 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 09. July 2014 13:57 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 09. July 2014 15:01 UTC kernel-stable-Verification-testing-start:Wednesday, 09. July 2014 15:01 UTC kernel-stable-Certification-testing-start:Wednesday, 09. July 2014 15:01 UTC kernel-stable-Security-signoff-start:Wednesday, 09. July 2014 15:01 UTC kernel-stable-Regression-testing-start:Wednesday, 09. July 2014 15:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1338524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338654] Re: linux: 3.2.0-67.100 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- 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/1338654 Title: linux: 3.2.0-67.100 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: Confirmed Bug description: This bug is for tracking the 3.2.0-67.100 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 07. July 2014 16:11 UTC kernel-stable-Prepare-package-end:Tuesday, 08. July 2014 04:12 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 08. July 2014 04:12 UTC ppa-package-testing-start:Tuesday, 08. July 2014 04:12 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 09. July 2014 22:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 09. July 2014 23:01 UTC kernel-stable-Verification-testing-start:Wednesday, 09. July 2014 23:01 UTC kernel-stable-Certification-testing-start:Wednesday, 09. July 2014 23:01 UTC kernel-stable-Security-signoff-start:Wednesday, 09. July 2014 23:01 UTC kernel-stable-Regression-testing-start:Wednesday, 09. July 2014 23:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1338654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338556] Re: linux: 3.11.0-26.44 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-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/1338556 Title: linux: 3.11.0-26.44 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-26.44 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 07. July 2014 12:18 UTC kernel-stable-Prepare-package-end:Monday, 07. July 2014 20:10 UTC kernel-stable-Promote-to-proposed-start:Monday, 07. July 2014 20:10 UTC ppa-package-testing-start:Monday, 07. July 2014 20:10 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 09. July 2014 14:36 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 09. July 2014 16:02 UTC kernel-stable-Verification-testing-start:Wednesday, 09. July 2014 16:02 UTC kernel-stable-Certification-testing-start:Wednesday, 09. July 2014 16:02 UTC kernel-stable-Security-signoff-start:Wednesday, 09. July 2014 16:03 UTC kernel-stable-Regression-testing-start:Wednesday, 09. July 2014 16:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1338556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1336203] Re: linux: 3.11.0-25.43 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-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/1336203 Title: linux: 3.11.0-25.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-25.43 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 01. July 2014 09:02 UTC kernel-stable-Prepare-package-end:Wednesday, 02. July 2014 15:58 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 02. July 2014 15:58 UTC ppa-package-testing-start:Wednesday, 02. July 2014 15:58 UTC kernel-stable-Promote-to-proposed-end:Thursday, 03. July 2014 16:31 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 03. July 2014 18:03 UTC kernel-stable-Verification-testing-start:Thursday, 03. July 2014 18:03 UTC kernel-stable-Certification-testing-start:Thursday, 03. July 2014 18:03 UTC kernel-stable-Security-signoff-start:Thursday, 03. July 2014 18:03 UTC kernel-stable-Regression-testing-start:Thursday, 03. July 2014 18:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1336203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1336203] Re: linux: 3.11.0-25.43 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- 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/1336203 Title: linux: 3.11.0-25.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-25.43 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 01. July 2014 09:02 UTC kernel-stable-Prepare-package-end:Wednesday, 02. July 2014 15:58 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 02. July 2014 15:58 UTC ppa-package-testing-start:Wednesday, 02. July 2014 15:58 UTC kernel-stable-Promote-to-proposed-end:Thursday, 03. July 2014 16:31 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 03. July 2014 18:03 UTC kernel-stable-Verification-testing-start:Thursday, 03. July 2014 18:03 UTC kernel-stable-Certification-testing-start:Thursday, 03. July 2014 18:03 UTC kernel-stable-Security-signoff-start:Thursday, 03. July 2014 18:03 UTC kernel-stable-Regression-testing-start:Thursday, 03. July 2014 18:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1336203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335875] Re: linux: 2.6.32-63.126 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- 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/1335875 Title: linux: 2.6.32-63.126 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-63.126 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 30. June 2014 14:25 UTC kernel-stable-Prepare-package-end:Tuesday, 01. July 2014 04:52 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. July 2014 04:52 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. July 2014 00:23 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 02. July 2014 01:37 UTC kernel-stable-Verification-testing-start:Wednesday, 02. July 2014 01:37 UTC kernel-stable-Certification-testing-start:Wednesday, 02. July 2014 01:37 UTC kernel-stable-Security-signoff-start:Wednesday, 02. July 2014 01:37 UTC kernel-stable-Regression-testing-start:Wednesday, 02. July 2014 01:37 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1335875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1329111] Re: linux-ti-omap4: 3.2.0-1450.69 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1329111 Title: linux-ti-omap4: 3.2.0-1450.69 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 12. June 2014 00:33 UTC kernel-stable-master-bug:1328620 kernel-stable-Certification-testing-end:Friday, 13. June 2014 11:02 UTC kernel-stable-Prepare-package-end:Friday, 13. June 2014 17:02 UTC kernel-stable-Promote-to-proposed-start:Friday, 13. June 2014 17:02 UTC ppa-package-testing-start:Friday, 13. June 2014 18:01 UTC kernel-stable-Promote-to-proposed-end:Friday, 13. June 2014 22:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 13. June 2014 23:02 UTC kernel-stable-Security-signoff-start:Friday, 13. June 2014 23:02 UTC kernel-stable-Verification-testing-start:Friday, 13. June 2014 23:02 UTC kernel-stable-Regression-testing-start:Friday, 13. June 2014 23:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1329111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328153] Re: linux: 3.11.0-24.41 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- 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/1328153 Title: linux: 3.11.0-24.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-24.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 09. June 2014 15:20 UTC kernel-stable-Prepare-package-end:Tuesday, 10. June 2014 03:06 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 10. June 2014 03:06 UTC ppa-package-testing-start:Tuesday, 10. June 2014 04:00 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 10. June 2014 07:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 10. June 2014 08:00 UTC kernel-stable-Verification-testing-start:Tuesday, 10. June 2014 08:00 UTC kernel-stable-Certification-testing-start:Tuesday, 10. June 2014 08:00 UTC kernel-stable-Security-signoff-start:Tuesday, 10. June 2014 08:01 UTC kernel-stable-Regression-testing-start:Tuesday, 10. June 2014 08:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1328153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328153] Re: linux: 3.11.0-24.41 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released ** Tags added: qa-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/1328153 Title: linux: 3.11.0-24.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-24.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 09. June 2014 15:20 UTC kernel-stable-Prepare-package-end:Tuesday, 10. June 2014 03:06 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 10. June 2014 03:06 UTC ppa-package-testing-start:Tuesday, 10. June 2014 04:00 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 10. June 2014 07:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 10. June 2014 08:00 UTC kernel-stable-Verification-testing-start:Tuesday, 10. June 2014 08:00 UTC kernel-stable-Certification-testing-start:Tuesday, 10. June 2014 08:00 UTC kernel-stable-Security-signoff-start:Tuesday, 10. June 2014 08:01 UTC kernel-stable-Regression-testing-start:Tuesday, 10. June 2014 08:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1328153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1329111] Re: linux-ti-omap4: 3.2.0-1450.69 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul Larson (pwlars) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1329111 Title: linux-ti-omap4: 3.2.0-1450.69 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 12. June 2014 00:33 UTC kernel-stable-master-bug:1328620 kernel-stable-Certification-testing-end:Friday, 13. June 2014 11:02 UTC kernel-stable-Prepare-package-end:Friday, 13. June 2014 17:02 UTC kernel-stable-Promote-to-proposed-start:Friday, 13. June 2014 17:02 UTC ppa-package-testing-start:Friday, 13. June 2014 18:01 UTC kernel-stable-Promote-to-proposed-end:Friday, 13. June 2014 22:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 13. June 2014 23:02 UTC kernel-stable-Security-signoff-start:Friday, 13. June 2014 23:02 UTC kernel-stable-Verification-testing-start:Friday, 13. June 2014 23:02 UTC kernel-stable-Regression-testing-start:Friday, 13. June 2014 23:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1329111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1322137] Re: linux-armadaxp: 3.2.0-1634.48 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = Fix Released ** Tags added: qa-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1322137 Title: linux-armadaxp: 3.2.0-1634.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1634.48 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 22. May 2014 11:07 UTC kernel-stable-master-bug:1321792 kernel-stable-Certification-testing-end:Monday, 26. May 2014 02:06 UTC kernel-stable-Security-signoff-end:Monday, 26. May 2014 02:06 UTC kernel-stable-Prepare-package-end:Monday, 26. May 2014 05:06 UTC kernel-stable-Promote-to-proposed-start:Monday, 26. May 2014 05:06 UTC ppa-package-testing-start:Monday, 26. May 2014 06:07 UTC kernel-stable-Promote-to-proposed-end:Thursday, 29. May 2014 11:54 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 30. May 2014 06:10 UTC kernel-stable-Verification-testing-start:Friday, 30. May 2014 06:10 UTC kernel-stable-Regression-testing-start:Friday, 30. May 2014 06:10 UTC kernel-stable-Regression-testing-end:Wednesday, 04. June 2014 13:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1322137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1321792] Re: linux: 3.2.0-64.96 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = Fix Released ** Tags added: qa-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/1321792 Title: linux: 3.2.0-64.96 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-64.96 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 21. May 2014 15:02 UTC kernel-stable-Prepare-package-end:Thursday, 22. May 2014 11:10 UTC kernel-stable-Promote-to-proposed-start:Thursday, 22. May 2014 11:10 UTC ppa-package-testing-start:Thursday, 22. May 2014 12:06 UTC kernel-stable-Promote-to-proposed-end:Thursday, 29. May 2014 08:21 UTC kernel-stable-Verification-testing-start:Thursday, 29. May 2014 10:12 UTC kernel-stable-Certification-testing-start:Thursday, 29. May 2014 10:12 UTC kernel-stable-Security-signoff-start:Thursday, 29. May 2014 10:12 UTC kernel-stable-Regression-testing-start:Thursday, 29. May 2014 10:12 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Monday, 02. June 2014 14:02 UTC kernel-stable-Verification-testing-end:Monday, 02. June 2014 14:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1321792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
