[Bug 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade
I only have one s390x guest and adding another would be painful due to the slowness of its emulation :) but I have just tried removing all of /etc/ssh and reinstalling openssh-client/openssh-server, same crash. To be clear, this is only happening on my s390x guest. I have a few other non-x86 qemu guests (arm64, ppc64el, riscv64, etc) which have also been upgraded to jammy, none of which have this problem. So I'm willing to bet this is more of a kernel or qemu problem and that openssh is just a symptom. (Though it seems to be a recurring indicative symptom... ISTR openssh segfaults during the bootstrap of riscv64 on qemu; William Grant may be able to chime in.) I've attached my libvirt definition in case it's relevant, but it's pretty standard. ** Attachment added: "s390x-dev.xml" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+attachment/5584015/+files/s390x-dev.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970076 Title: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade
** Tags added: apport-crash need-amd64-retrace ** Tags removed: need-amd64-retrace ** Tags added: need-s390x-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970076 Title: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970076] [NEW] "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade
Public bug reported: This s390x VM has been upgraded to Jammy, including the host (qemu- system-s390x 1:6.2+dfsg-2ubuntu6). Now any attempt to use ssh, or any incoming sshd attempt immediately results in e.g.: ryan@s390x-dev:~$ ssh g...@github.com [ 433.672800] User process fault: interruption code 0011 ilc:3 in libc.so.6[3ffa6c0+1ca000] [ 433.672946] Failing address: 02aa0b84d000 TEID: 02aa0b84d800 [ 433.672977] Fault in primary space mode while using user ASCE. [ 433.673030] AS:02bc01c7 R3:087cc007 S:0798a000 P:0400 Segmentation fault (core dumped) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash jammy need-s390x-retrace qemu s390x ** Attachment added: "_usr_bin_ssh.1000.crash" https://bugs.launchpad.net/bugs/1970076/+attachment/5582994/+files/_usr_bin_ssh.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970076 Title: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961454] [NEW] [SRU] Package unusable due to yearly key changes
Public bug reported: [Impact] * ftp.ports.debian.org changes keys every year, and updates debian- ports-archive-keyring 2 years ahead of time. * Packages in bionic and focal do not have 2022's key, making the packages unusable. * SRU falls under "Updates that need to be applied to Ubuntu packages to adjust to changes in the environment, server protocols, web services, and similar" * Package can be synced directly from Debian [Test Plan] sudo debootstrap --arch=riscv64 --force-check-gpg --foreign --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg sid /tmp/sid http://ftp.ports.debian.org/debian-ports/ Expected: I: Checking Release signature I: Valid Release signature (key id CBC70A60B9ED6F237A5F5B0BE852514F5DF312F6) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... [...] Currently: I: Checking Release signature E: Release signed by unknown key (key id E852514F5DF312F6) The specified keyring /usr/share/keyrings/debian-ports-archive-keyring.gpg may be incorrect or out of date. You can find the latest Debian release key at https://ftp-master.debian.org/keys.html [Where problems could occur] * Very old keys are removed from the keyring by subsequent package updates. An existing program might be looking for old keys and start failing, but this scenario is probably unlikely. [Other Info] ** Affects: debian-ports-archive-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal ** Tags added: bionic focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961454 Title: [SRU] Package unusable due to yearly key changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-ports-archive-keyring/+bug/1961454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
** Changed in: linux-raspi2 (Ubuntu) Assignee: Ryan Finnie (fo0bar) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771740] Re: Expose link offload options
I no longer have the network card in question and don't have a suitable environment to test, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771740 Title: Expose link offload options To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1771740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
With the regression fix tested, I've gone ahead and fixed the core
problem on my system, switching the backing device to 4k. Documented
below and worked for me, but PLEASE don't take it at face value, since
part of it is literally destroying the bcache header area of the backing
disk.
# WARNING! Loss of data, life, liberty, etc. Do not blindly copy/paste!
# You need to unmount and make sure the bcache device is not being used,
# and specifically wait for the cache state to go from dirty to clean
# if using writeback.
DEV_BACKING=/dev/sdx1 # /dev/md0 for me
DEV_CACHE=/dev/sdy1 # /dev/sdb1 for me
DEV_BCACHE=bcache0
OFFSET="$(bcache-super-show ${DEV_BACKING?} | awk '$1=="dev.data.first_sector"
{print $2}')"
CSET_UUID="$(bcache-super-show ${DEV_CACHE?} | awk '$1=="cset.uuid" {print
$2}')"
file -s ${DEV_CACHE?}
file -s ${DEV_BACKING?}
dd if=${DEV_BACKING?} bs=512 skip=${OFFSET?} count=8 | file -
# Remove and wipe cache device
echo ${CSET_UUID?} >/sys/block/${DEV_BCACHE?}/bcache/detach
cat /sys/block/${DEV_BCACHE?}/bcache/state
echo 1 >/sys/fs/bcache/${CSET_UUID?}/stop
while [ -e /sys/fs/bcache/${CSET_UUID?}/stop ]; do sleep 1; done
wipefs -a ${DEV_CACHE?}
# Stop bcache0, wipe and recreate bcache portion of backing device
echo 1 >/sys/block/${DEV_BCACHE?}/bcache/stop
while [ -e /sys/block/${DEV_BCACHE?}/bcache/stop ]; do sleep 1; done
# Removes bcache magic bytes from beginning and (hopefully) leaves all data from
# ${OFFSET?} onward (the actual data). But don't trust me here.
wipefs -a ${DEV_BACKING?}
dd if=/dev/zero of=${DEV_BACKING?} bs=512 count=${OFFSET?}
make-bcache --block 4k --bucket 2M --data-offset ${OFFSET?} -B ${DEV_BACKING?}
while [ ! -e /sys/block/${DEV_BCACHE?}/bcache/attach ]; do sleep 1; done
file -s /dev/${DEV_BCACHE?}
# Safe to remount and use bcache device now
# Recreate and attach cache
make-bcache --block 4k --bucket 2M -C ${DEV_CACHE?}
CSET_UUID="$(bcache-super-show ${DEV_CACHE?} | awk '$1=="cset.uuid" {print
$2}')"
echo ${CSET_UUID?} >/sys/block/${DEV_BCACHE?}/bcache/attach
echo writeback >/sys/block/${DEV_BCACHE?}/bcache/cache_mode
cat /sys/block/${DEV_BCACHE?}/bcache/state
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Works on focal, thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873545] Re: Permission denied error from show-motd when updates available
This fails when logging in from the console (see below). Doesn't appear to be affected when logging in via SSH. The check should probably be [ -z "$EUID" -o "$EUID" -ne 0 ]. Ubuntu 20.04 LTS riscv64-dev ttyS0 riscv64-dev login: ryan Password: /etc/update-motd.d/91-release-upgrade: 9: [: Illegal number: Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-28-generic riscv64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage 0 updates can be installed immediately. 0 of these updates are security updates. Last login: Mon Jul 6 17:24:50 UTC 2020 on ttyS0 ryan@riscv64-dev:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873545 Title: Permission denied error from show-motd when updates available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1873545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
On 6/2/20 10:19 AM, Mauricio Faria de Oliveira wrote: > Do you remember specifying a block size of 512 kB for 'make-bcache' when > creating it? > > e.g., make-bcache --bdev|-B /dev/mdN --block|-w 512k # or similarly. My set was created by hand, and it's entirely possible I specified "--block 512k" instead of "--block 512" (though the backing device is 4096, so it should have actually been 4k). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Works on focal! Linux nibbler 5.4.0-34-generic #38+lp1867916b1 SMP Sun May 31 21:41:06 -03 2020 x86_64 x86_64 x86_64 GNU/Linux Thanks! I'm curious to see the patch; I tried root causing it myself and suspected it had to do with something like an overflow in an unanticipated block size, but never got anywhere on that. Also keep in mind I filed an upstream bug (https://bugzilla.kernel.org/show_bug.cgi?id=207811), so please make sure to reference that when submitting the fix upstream. Again, thank you Mauricio! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Sure, done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
** Attachment added: "lp1867916-lsblk" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378817/+files/lp1867916-lsblk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Done, please see attached. (The sd* devices do tend to move around; the bcache backing device is currently at sdb1.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
** Attachment added: "lp1867916-bcache-super-show.md" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378590/+files/lp1867916-bcache-super-show.md -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
** Attachment added: "lp1867916-bcache-super-show.sd" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378589/+files/lp1867916-bcache-super-show.sd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
** Attachment added: "lp1867916-queue_block_size" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378588/+files/lp1867916-queue_block_size -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Here's a crashdump from the working kernel, with everything enabled: https://www.finnie.org/stuff/lp1867916-crashdump-20200528.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
The bcache device is raid+bcache, with luks below it (and then lvm), so it's not directly mountable. Do you just want the stack set up and functional like normal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Mike: Sorry, that is not related. I'd suggest filing a new bug. Mauricio: Any update on this? This also affects the 5.4 line, so after upgrading to focal I needed to remain on 4.15.0-88. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876620] [NEW] Enable riscv64 build
Public bug reported: RISC-V EFI support is not yet in the Linux kernel (ca. 5.8: https://lkml.org/lkml/2020/4/20/1800), and while GRUB2 EFI Loader support needs to happen with the kernel (https://lists.gnu.org/archive/html/grub-devel/2020-04/msg00203.html), GRUB2 already has RISC-V EFI support. It can't currently boot anything, but it is a valid UEFI application and displays a pretty menu. Please see the attached debdiff. Of note: * grub2 requires efibootmgr and efivar. I've filed Debian bugs to enable riscv64 for them (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959498 and https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959499 respectively), but if this is actioned before those end up happening, it's a simple Architecture: update on each. * riscv-default-platform.patch: Upstreamed, allows `grub-install` to work without --platform. * riscv-relocation-offset.patch: Upstreamed, fixes "unaligned pointer" failure. * riscv-ubuntu-linuxefi.patch: Patches ubuntu-linuxefi.patch for riscv support; not sure if this should be integrated into ubuntu- linuxefi.patch. * Tested on qemu-system-riscv64 focal. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "grub2-riscv64.debdiff" https://bugs.launchpad.net/bugs/1876620/+attachment/5365841/+files/grub2-riscv64.debdiff ** Description changed: RISC-V EFI support is not yet in the Linux kernel (ca. 5.8: https://lkml.org/lkml/2020/4/20/1800), and while GRUB2 EFI Loader support needs to happen with the kernel (https://lists.gnu.org/archive/html/grub-devel/2020-04/msg00203.html), GRUB2 already has RISC-V EFI support. It can't currently boot anything, but it is a valid UEFI application and displays a pretty menu. Please see the attached debdiff. Of note: * grub2 requires efibootmgr and efivar. I've filed Debian bugs to enable riscv64 for them (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959498 and https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959499 respectively), but if this is actioned before those end up happening, it's a simple Architecture: update on each. * riscv-default-platform.patch: Upstreamed, allows `grub-install` to work without --platform. - * riscv-relocation-offset.patch: Upstreamed: fixes "unaligned pointer" + * riscv-relocation-offset.patch: Upstreamed, fixes "unaligned pointer" failure. * riscv-ubuntu-linuxefi.patch: Patches ubuntu-linuxefi.patch for riscv support; not sure if this should be integrated into linuxefi.patch. * Tested on qemu-system-riscv64 focal. ** Description changed: RISC-V EFI support is not yet in the Linux kernel (ca. 5.8: https://lkml.org/lkml/2020/4/20/1800), and while GRUB2 EFI Loader support needs to happen with the kernel (https://lists.gnu.org/archive/html/grub-devel/2020-04/msg00203.html), GRUB2 already has RISC-V EFI support. It can't currently boot anything, but it is a valid UEFI application and displays a pretty menu. Please see the attached debdiff. Of note: * grub2 requires efibootmgr and efivar. I've filed Debian bugs to enable riscv64 for them (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959498 and https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=959499 respectively), but if this is actioned before those end up happening, it's a simple Architecture: update on each. * riscv-default-platform.patch: Upstreamed, allows `grub-install` to work without --platform. * riscv-relocation-offset.patch: Upstreamed, fixes "unaligned pointer" failure. * riscv-ubuntu-linuxefi.patch: Patches ubuntu-linuxefi.patch for riscv - support; not sure if this should be integrated into linuxefi.patch. + support; not sure if this should be integrated into ubuntu- + linuxefi.patch. * Tested on qemu-system-riscv64 focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876620 Title: Enable riscv64 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872945] Re: risc-v doubles getting clobbered somehow
Sorry, I said 4.2-3ubuntu6 but meant 1:4.2-3ubuntu6~ppa5 from the PPA (which works). Sounds like Colin got 1:4.2-3ubuntu6 from the PPA; I will test 1:4.2-3ubuntu6 from -proposed to be sure. $ apt-cache policy qemu-system-misc qemu-system-misc: Installed: 1:4.2-3ubuntu6~ppa5 Candidate: 1:4.2-3ubuntu6~ppa5 Version table: *** 1:4.2-3ubuntu6~ppa5 500 500 http://ppa.launchpad.net/ci-train-ppa-service/4015/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2-3ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872945 Title: risc-v doubles getting clobbered somehow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872945] Re: risc-v doubles getting clobbered somehow
Yep, 1:4.2-3ubuntu6 from focal-proposed test case works for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872945 Title: risc-v doubles getting clobbered somehow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872945] Re: risc-v doubles getting clobbered somehow
Confirmed qemu 4.2-3ubuntu6 fixes the OpenSSH sshd hang on riscv64 guest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872945 Title: risc-v doubles getting clobbered somehow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
I've bisected the problem down to commit
c35a4a858d0616e7817026d88f377c7201ad449a ("block: fix an integer
overflow in logical block size", upstream
ad6bf88a6c19a39fb3b0045d78ea880325dfcf15).
I don't know what the exact problem is with the commit, but seems to be
in the area of fs/block_dev.c set_init_blocksize() calling
bdev_logical_block_size() which the offending commit touches.
# bad: [a78d21bd8bb58c158f73108eb7d7402619fcae3d] UBUNTU: Ubuntu-4.15.0-91.92
# good: [d5b8ff45eabff3cb2232a2eea38a862edc647ab8] UBUNTU: Ubuntu-4.15.0-88.88
git bisect start 'Ubuntu-4.15.0-91.92' 'Ubuntu-4.15.0-88.88'
# bad: [c04c6d87ca3a7e2c8019e0a2349fcf1175ffcce0] KVM: PPC: Release all
hardware TCE tables attached to a group
git bisect bad c04c6d87ca3a7e2c8019e0a2349fcf1175ffcce0
# good: [9a6b3cea5792f94f03f579c668a60eb4ddd209f0] dt-bindings: reset: meson8b:
fix duplicate reset IDs
git bisect good 9a6b3cea5792f94f03f579c668a60eb4ddd209f0
# bad: [6783f1bf22bb55bcd2628d7cabeacc9c720971e6] ALSA: usb-audio: update quirk
for B PX to remove microphone
git bisect bad 6783f1bf22bb55bcd2628d7cabeacc9c720971e6
# skip: [c4099e7e88621e82a5b3a5b0a2e3d6d8eee4e8e0] ptp: free ptp device pin
descriptors properly
git bisect skip c4099e7e88621e82a5b3a5b0a2e3d6d8eee4e8e0
# bad: [3222d8b5d803ed733dba2da03b595cf90c871fe6] drm/nouveau/mmu: qualify vmm
during dtor
git bisect bad 3222d8b5d803ed733dba2da03b595cf90c871fe6
# skip: [3db4efba8dea644e54e339ac2e46b497aea93638] NFC: pn533: fix bulk-message
timeout
git bisect skip 3db4efba8dea644e54e339ac2e46b497aea93638
# skip: [211ff6ef5f2f19d86d35dcbb94d4b09ab7de00fc] batman-adv: Fix DAT
candidate selection on little endian systems
git bisect skip 211ff6ef5f2f19d86d35dcbb94d4b09ab7de00fc
# skip: [3cb4cbc154b57c2fb842fbacc6ea4bd625ce680f] perf hists: Fix variable
name's inconsistency in hists__for_each() macro
git bisect skip 3cb4cbc154b57c2fb842fbacc6ea4bd625ce680f
# good: [1d9d2aae71b2d1c18d7d69c4850ca57ebd1e6fc1] clk: Don't try to enable
critical clocks if prepare failed
git bisect good 1d9d2aae71b2d1c18d7d69c4850ca57ebd1e6fc1
# skip: [37f1c7c4bf8eaf03f0e07152f55e0dda97bd52e8] cfg80211: check for
set_wiphy_params
git bisect skip 37f1c7c4bf8eaf03f0e07152f55e0dda97bd52e8
# good: [43cdcecf3a1bd5fdf9cbce0f3908cdde789c7ffd] ALSA: seq: Fix racy access
for queue timer in proc read
git bisect good 43cdcecf3a1bd5fdf9cbce0f3908cdde789c7ffd
# bad: [7a10b28e6122e12323da46732fc345d476a21829] ARM: dts: am571x-idk: Fix
gpios property to have the correct gpio number
git bisect bad 7a10b28e6122e12323da46732fc345d476a21829
# good: [31e3c075719a3afe5ffd2b9b8e1f18e07255bd96] Fix built-in early-load
Intel microcode alignment
git bisect good 31e3c075719a3afe5ffd2b9b8e1f18e07255bd96
# bad: [c35a4a858d0616e7817026d88f377c7201ad449a] block: fix an integer
overflow in logical block size
git bisect bad c35a4a858d0616e7817026d88f377c7201ad449a
# first bad commit: [c35a4a858d0616e7817026d88f377c7201ad449a] block: fix an
integer overflow in logical block size
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
BTW, for future searchers, I've uploaded dmesg.202004081903 separately, and pasted the crash here: [ 194.36] bcache: bch_journal_replay() journal replay done, 3 keys in 6 entries, seq 23285862 [ 194.444622] bcache: register_cache() registered cache device sdb1 [ 194.448381] bcache: register_bdev() registered backing device md0 [ 194.602075] BUG: unable to handle kernel NULL pointer dereference at 0008 [ 194.602100] IP: create_empty_buffers+0x29/0xf0 [ 194.602110] PGD 0 P4D 0 [ 194.602121] Oops: [#1] SMP NOPTI [ 194.602137] Modules linked in: bcache ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter pps_ldisc aufs overlay cmac bnep bonding bridge stp llc arc4 snd_hda_codec_hdmi nls_iso8859_1 edac_mce_amd kvm_amd kvm irqbypass rtl8xxxu mac80211 btusb btrtl btbcm snd_hda_intel btintel snd_hda_codec bluetooth cfg80211 eeepc_wmi snd_hda_core asus_wmi joydev sparse_keymap snd_hwdep wmi_bmof input_leds snd_pcm ecdh_generic snd_timer snd soundcore ccp k10temp shpchp mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp libiscsi_tcp auth_rpcgss libiscsi nfs_acl scsi_transport_iscsi lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx [ 194.602323] xor raid6_pq libcrc32c hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nouveau crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc mxm_wmi video ttm drm_kms_helper aesni_intel syscopyarea sysfillrect igb sysimgblt aes_x86_64 fb_sys_fops crypto_simd glue_helper dca cryptd i2c_algo_bit drm i2c_piix4 ptp ahci nvme pps_core libahci nvme_core gpio_amdpt wmi gpio_generic [ 194.602406] CPU: 1 PID: 4403 Comm: bcache-register Not tainted 4.15.0-91-generic #92-Ubuntu [ 194.602425] Hardware name: System manufacturer System Product Name/PRIME X370-PRO, BIOS 4207 12/08/2018 [ 194.602447] RIP: 0010:create_empty_buffers+0x29/0xf0 [ 194.602459] RSP: 0018:a833cc37f7a8 EFLAGS: 00010246 [ 194.602471] RAX: RBX: f6227c3f4c00 RCX: 0013 [ 194.602487] RDX: RSI: 0008 RDI: f6227c3f4c00 [ 194.602503] RBP: a833cc37f7c0 R08: 0001 R09: dead00ff [ 194.602519] R10: 8976ca4f7aa0 R11: R12: [ 194.602535] R13: R14: R15: 0200 [ 194.602551] FS: 7f51c3bb2500() GS:89771ec4() knlGS: [ 194.602569] CS: 0010 DS: ES: CR0: 80050033 [ 194.602582] CR2: 0008 CR3: 000f24aea000 CR4: 003406e0 [ 194.602598] Call Trace: [ 194.602606] create_page_buffers+0x51/0x60 [ 194.602616] block_read_full_page+0x4e/0x370 [ 194.602626] ? set_init_blocksize+0x80/0x80 [ 194.602636] blkdev_readpage+0x18/0x20 [ 194.602646] do_read_cache_page+0x2a2/0x580 [ 194.602656] ? blkdev_writepages+0x40/0x40 [ 194.602667] ? update_load_avg+0x57f/0x6e0 [ 194.602676] read_cache_page+0x15/0x20 [ 194.602687] read_dev_sector+0x2d/0xd0 [ 194.602696] read_lba+0x130/0x220 [ 194.602704] ? efi_partition+0x11a/0x790 [ 194.602713] efi_partition+0x138/0x790 [ 194.602723] ? string+0x60/0x90 [ 194.602731] ? vsnprintf+0xfb/0x510 [ 194.602740] ? snprintf+0x45/0x70 [ 194.602748] ? is_gpt_valid.part.6+0x420/0x420 [ 194.602760] check_partition+0x130/0x230 [ 194.603304] ? check_partition+0x130/0x230 [ 194.603837] rescan_partitions+0xaa/0x350 [ 194.604372] bdev_disk_changed+0x53/0x60 [ 194.604895] __blkdev_get+0x34a/0x510 [ 194.605413] blkdev_get+0x129/0x320 [ 194.605930] ? wake_up_bit+0x42/0x50 [ 194.606445] ? unlock_new_inode+0x4c/0x80 [ 194.606947] ? bdget+0x108/0x120 [ 194.607432] device_add_disk+0x38b/0x490 [ 194.607909] ? bcache_dev_sectors_dirty_add+0xb0/0xb0 [bcache] [ 194.608373] bch_cached_dev_run.part.28+0x42/0x1a0 [bcache] [ 194.608821] ? wait_woken+0x80/0x80 [ 194.609258] bch_cached_dev_attach+0x3b5/0x4f0 [bcache] [ 194.609681] ? vprintk_func+0x47/0xc0 [ 194.610088] ? printk+0x52/0x6e [ 194.610479] register_bcache+0x864/0x1110 [bcache] [ 194.610861] ? register_bcache+0x864/0x1110 [bcache] [ 194.611227] kobj_attr_store+0x12/0x20 [ 194.611580] ? kobj_attr_store+0x12/0x20 [ 194.611925] sysfs_kf_write+0x3c/0x50 [ 194.612259] kernfs_fop_write+0x125/0x1a0 [ 194.612595] __vfs_write+0x1b/0x40 [ 194.612921] vfs_write+0xb1/0x1a0 [ 194.613245] SyS_write+0x5c/0xe0 [ 194.613565] do_syscall_64+0x73/0x130 [ 194.613886] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 194.614212] RIP: 0033:0x7f51c36b8154 [ 194.614530] RSP: 002b:7ffd27009a58 EFLAGS: 0246 ORIG_RAX: 0001 [ 194.614858] RAX: ffda RBX: 0009 RCX: 7f51c36b8154 [ 194.615183] RDX: 0009 RSI: 560160a77260 RDI: 0003 [ 194.615506] RBP:
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Here you go: https://www.finnie.org/stuff/lp1867916-crashdump.tar.xz (138MB) Some notes on the process: - Also blacklisted it87 (DKMS) so the running kernel wasn't "tainted" - Also disabled the relevant crypttab entry for this group - 768M produced "crashkernel reservation failed - No suitable area found" in dmesg, used 512M instead - Had to disable secure boot (https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869672 which you also appear to be working on, heh) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
I can confirm going from 4.15.0-88 to 4.15.0-91 on my bcache system
panics in the same way. Here's my layout:
-> sd{c,d,f,g,h}: each 4TB gpt, sd{c,d,f,g,h}1: each type linux_raid_member
--> md0: raid6, sd{c,d,f,g,h}1
--> sda: 512GB gpt, sda1: type bcache
---> bcache0: md0 + sda1
> whatadisk_crypt: LUKS on bcache0
-> LVM VG whatadisk: whatadisk_crypt
--> multiple LVs
There are also a handful of other disks (for example, nvme0n1 is the
encrypted boot disk), but the layout above is the only part which bcache
touches.
Happy to help with additional info or testing, please let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870850] Re: Multi-line paste broken between kitty and nano 4.8 [focal]
Thanks Benno. Yeah, I've tested that works (albeit with s,'\r',CR_CODE, on the - line since focal is currently 4.8). I've asked -release if it's possible to get a sync exception for 4.9.1-1 from sid since focal is past the freeze, rather than trying to SRU this (and e.g. LP: #1866820 crash); waiting to heard back about that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870850 Title: Multi-line paste broken between kitty and nano 4.8 [focal] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870850] Re: Multi-line paste broken between kitty and nano 4.8 [focal]
** Summary changed: - Multi-line paste broken between kitty ~0.15 and nano 8.4 [focal] + Multi-line paste broken between kitty and nano 4.8 [focal] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870850 Title: Multi-line paste broken between kitty and nano 4.8 [focal] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870850] [NEW] Multi-line paste broken between kitty ~0.15 and nano 8.4 [focal]
Public bug reported: Ubuntu 20.04 Focal beta (as of 2020-04-04) nano 4.8-1 What I expect to happen: multi-line paste into nano via kitty pastes multiple lines. What happens instead: pasted multi-line text is one line with no line breaks. There is a bit of a spat between the developers of kitty (gnome- terminal:kitty::screen:tmux, basically) and nano about how to do multi- line pasting. See e.g.: * https://savannah.gnu.org/bugs/?58010 * https://lists.gnu.org/archive/html/nano-devel/2020-03/msg5.html * https://github.com/kovidgoyal/kitty/issues/994 Without taking sides, the facts are: * With the current versions in focal (kitty 0.15.0 and nano 4.8), pasting multi-line will result in newlines being eaten. * nano 4.9 introduces a fix (commit 481529e8650d105c3280def764e4917af0cabb49) which brings the newline handling more in line with other terminal-aware programs (treating raw \n as line break). Peripherally, nano 4.8 introduced new bracketed paste mode support. This makes a read of the kitty github issue above harder, since the issue being reported here is about an incompatibility in bracketed paste mode between kitty and nano, not pre-bracketed ^J handling. ** Affects: nano (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870850 Title: Multi-line paste broken between kitty ~0.15 and nano 8.4 [focal] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580326] Re: Add raspi3 subarch
** Branch unlinked: lp:~fo0bar/livecd-rootfs/livecd-rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580326 Title: Add raspi3 subarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1580326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
Per https://wiki.ubuntu.com/QATeam/PerformingSRUVerification I had added the procedure and results to the description: TEST CASE: 1. Enable -proposed 2. apt-get install mountall=2.53ubuntu1 3. update-initramfs -k all -u 4. Reboot VERIFICATION DONE Rebooted successfully on affected Gen10 systems. Confirmed no regression on unaffected systems. ** Changed in: mountall (Ubuntu Trusty) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
** Description changed: [Impact] - * udev block nodes without a devname will crash mountall, resulting in + Â * udev block nodes without a devname will crash mountall, resulting in an unbootable system (emergency root shell) - * While this is not likely to happen in a matched distro/kernel + Â * While this is not likely to happen in a matched distro/kernel environment (it was discovered while needing to run a bionic 4.15 kernel on trusty), it is possible. - * The code in try_udev_device() assumes a block subsystem will always + Â * The code in try_udev_device() assumes a block subsystem will always have a devname; the SRU patches explicitly check for a devname and return if null. [Test Case] - * HPE DL385 Gen10, Samsung a822 NVMe controller, trusty install + Â * HPE DL385 Gen10, Samsung a822 NVMe controller, trusty install - * Kernels <4.15 (or possibly 4.14) do not expose nvme0c33n1 and do not + Â * Kernels <4.15 (or possibly 4.14) do not expose nvme0c33n1 and do not trigger the bug. Tested on 4.13, 4.4 and 3.13. - * Kernel 4.15 exposes nvme0c33n1 in udev but does not have a devname, + Â * Kernel 4.15 exposes nvme0c33n1 in udev but does not have a devname, mountall crash ensues. [Regression Potential] - * Patch might ignore legitimate block devices on existing + Â * Patch might ignore legitimate block devices on existing installations. Unlikely, since the logic path for null devname leads directly to a program crash. [Other Info] - - * Additional context for Canonical employees: PS4.5 is a trusty backend cloud, but we now have Gen10 hardware incoming (this was discovered while adding new nova-compute hardware). Older kernels are not usable because Gen10 requires ilorest, which requires a >4.4 kernel (at least artful 4.13 is known good). So trusty+4.15 is the only viable combination for continued support of the cloud while adding new hardware. This is done via apt pinning of bionic for the kernel packages, and, mountall notwithstanding, is working fine so far. + + Â * Additional context for Canonical employees: PS4.5 is a trusty backend + cloud, but we now have Gen10 hardware incoming (this was discovered + while adding new nova-compute hardware). Older kernels are not usable + because Gen10 requires ilorest, which requires a >4.4 kernel (at least + artful 4.13 is known good). So trusty+4.15 is the only viable + combination for continued support of the cloud while adding new + hardware. This is done via apt pinning of bionic for the kernel + packages, and, mountall notwithstanding, is working fine so far. + + TEST CASE: + 1. Enable -proposed + 2. apt-get install mountall=2.53ubuntu1 + 3. update-initramfs -k all -u + 4. Reboot + + VERIFICATION DONE + Rebooted successfully on affected Gen10 systems. Confirmed no regression on unaffected systems. Original description: Running bionic's 4.15 kernel on trusty on an HPE DL385 Gen10 results in a device node for the NVMe controller, /devices/pci:40/:40:03.1/:43:00.0/nvme/nvme0/nvme0c33n1 which itself does not have a devname. When mountall gets to it: fsck_update: updating check priorities try_mount: /srv/nova/instances waiting for device try_udev_device: ignored /dev/loop5 (not yet ready?) try_udev_device: ignored /dev/loop6 (not yet ready?) try_udev_device: ignored /dev/loop1 (not yet ready?) try_udev_device: ignored /dev/loop0 (not yet ready?) try_udev_device: block (null) (null) (null) and then crashes, leaving the boot at an emergency root shell. A successful scan looks like this for comparison: try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sda (null) (null) try_udev_device: block /dev/nvme0n1 ed56e3a9-60f7-4636-85a2-b53137b598e7 (null) try_udev_device: block /dev/bcache0 756cb2c6-b999-4905-a021-c2e688e81a86 instances The debdiffs check for a null devname in try_udev_device() and will not attempt to process it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
** Changed in: mountall (Ubuntu Trusty) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
Thanks. I saw xenial had mountall and figured maybe there was transition path where it was used, but if it's vestigial, I agree this should be trusty-only. ** Tags removed: xenial ** Patch removed: "lp1807077-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+attachment/5219620/+files/lp1807077-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: mountall crashes on udev node with missing devname
** Tags added: patch trusty xenial ** Also affects: mountall (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: mountall (Ubuntu Xenial) Importance: Undecided Status: New ** Summary changed: - mountall crashes on udev node with missing devname + [SRU] mountall crashes on udev node with missing devname -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: mountall crashes on udev node with missing devname
** Description changed: + [Impact] + + * udev block nodes without a devname will crash mountall, resulting in + an unbootable system (emergency root shell) + + * While this is not likely to happen in a matched distro/kernel + environment (it was discovered while needing to run a bionic 4.15 kernel + on trusty), it is possible. + + * The code in try_udev_device() assumes a block subsystem will always + have a devname; the SRU patches explicitly check for a devname and + return if null. + + [Test Case] + + * HPE DL385 Gen10, Samsung a822 NVMe controller, trusty install + + * Kernels <4.15 (or possibly 4.14) do not expose nvme0c33n1 and do not + trigger the bug. Tested on 4.13, 4.4 and 3.13. + + * Kernel 4.15 exposes nvme0c33n1 in udev but does not have a devname, + mountall crash ensues. + + [Regression Potential] + + * Patch might ignore legitimate block devices on existing + installations. Unlikely, since the logic path for null devname leads + directly to a program crash. + + [Other Info] + + * Additional context for Canonical employees: PS4.5 is a trusty backend cloud, but we now have Gen10 hardware incoming (this was discovered while adding new nova-compute hardware). Older kernels are not usable because Gen10 requires ilorest, which requires a >4.4 kernel (at least artful 4.13 is known good). So trusty+4.15 is the only viable combination for continued support of the cloud while adding new hardware. This is done via apt pinning of bionic for the kernel packages, and, mountall notwithstanding, is working fine so far. + + + Original description: + Running bionic's 4.15 kernel on trusty on an HPE DL385 Gen10 results in a device node for the NVMe controller, /devices/pci:40/:40:03.1/:43:00.0/nvme/nvme0/nvme0c33n1 which itself does not have a devname. When mountall gets to it: fsck_update: updating check priorities try_mount: /srv/nova/instances waiting for device try_udev_device: ignored /dev/loop5 (not yet ready?) try_udev_device: ignored /dev/loop6 (not yet ready?) try_udev_device: ignored /dev/loop1 (not yet ready?) try_udev_device: ignored /dev/loop0 (not yet ready?) try_udev_device: block (null) (null) (null) and then crashes, leaving the boot at an emergency root shell. A successful scan looks like this for comparison: try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sda (null) (null) try_udev_device: block /dev/nvme0n1 ed56e3a9-60f7-4636-85a2-b53137b598e7 (null) try_udev_device: block /dev/bcache0 756cb2c6-b999-4905-a021-c2e688e81a86 instances - The (forthcoming) debdiffs check for a null devname in try_udev_device() - and will not attempt to process it. + The debdiffs check for a null devname in try_udev_device() and will not + attempt to process it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: mountall crashes on udev node with missing devname
** Patch added: "lp1807077-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+attachment/5219620/+files/lp1807077-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: mountall crashes on udev node with missing devname
** Patch added: "lp1807077-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+attachment/5219619/+files/lp1807077-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] [NEW] mountall crashes on udev node with missing devname
Public bug reported: Running bionic's 4.15 kernel on trusty on an HPE DL385 Gen10 results in a device node for the NVMe controller, /devices/pci:40/:40:03.1/:43:00.0/nvme/nvme0/nvme0c33n1 which itself does not have a devname. When mountall gets to it: fsck_update: updating check priorities try_mount: /srv/nova/instances waiting for device try_udev_device: ignored /dev/loop5 (not yet ready?) try_udev_device: ignored /dev/loop6 (not yet ready?) try_udev_device: ignored /dev/loop1 (not yet ready?) try_udev_device: ignored /dev/loop0 (not yet ready?) try_udev_device: block (null) (null) (null) and then crashes, leaving the boot at an emergency root shell. A successful scan looks like this for comparison: try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sda (null) (null) try_udev_device: block /dev/nvme0n1 ed56e3a9-60f7-4636-85a2-b53137b598e7 (null) try_udev_device: block /dev/bcache0 756cb2c6-b999-4905-a021-c2e688e81a86 instances The (forthcoming) debdiffs check for a null devname in try_udev_device() and will not attempt to process it. ** Affects: mountall (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
** Patch added: "lp1794629-artful.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200768/+files/lp1794629-artful.debdiff ** Patch removed: "bionic-upstream-delay-bailout-for-invalid-authenticating-user.patch" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200217/+files/bionic-upstream-delay-bailout-for-invalid-authenticating-user.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
** Patch added: "lp1794629-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200766/+files/lp1794629-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
** Patch added: "lp1794629-bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200767/+files/lp1794629-bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
All debdiffs tested in the wild (except artful). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
** Patch added: "lp1794629-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200765/+files/lp1794629-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
FYI, Qualys is now considering CVE-2018-15473 a PCI-DSS fail condition (QID: 38726). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
** Patch added: "bionic-upstream-delay-bailout-for-invalid-authenticating-user.patch" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200217/+files/bionic-upstream-delay-bailout-for-invalid-authenticating-user.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786397] Re: 2ping crashes on non-encrypted session
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786397 Title: 2ping crashes on non-encrypted session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/2ping/+bug/1786397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786397] Re: 2ping crashes on non-encrypted session
Tested 4.1-1ubuntu1 from bionic-proposed which fixes the issue correctly. No regressions observed. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786397 Title: 2ping crashes on non-encrypted session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/2ping/+bug/1786397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786397] Re: 2ping crashes on non-encrypted session
Sponsorship isn't needed; upload is waiting for bionic-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786397 Title: 2ping crashes on non-encrypted session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/2ping/+bug/1786397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786397] Re: 2ping crashes on non-encrypted session
** Changed in: 2ping (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786397 Title: 2ping crashes on non-encrypted session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/2ping/+bug/1786397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786397] Re: 2ping crashes on non-encrypted session
[ubuntu/bionic-proposed] 2ping 4.1-1ubuntu1 (Waiting for approval) > Redirecting ubuntu bionic to ubuntu bionic-proposed. > This upload awaits approval by a distro manager ** Changed in: 2ping (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786397 Title: 2ping crashes on non-encrypted session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/2ping/+bug/1786397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786397] Re: 2ping crashes on non-encrypted session
** Description changed: - Originally reported by Github user - joe1981alAPR (https://github.com/rfinnie/2ping/issues/5). + [Impact] - Fixed in commit 4a636763850bcea590fba6066751d13a36c2b28d + * When 2ping is being run as a non-encrypted session between two + affected 4.1 releases, within a few minutes the client and/or server + will crash with "TypeError: 'NoneType' object is not subscriptable" in + scheduled_cleanup_sock_class. + + * Clients cannot sustain a 2ping session for more than a few minutes. + + * When configured as a daemon without respawn, this results in a denial + of service. (Not default in bionic.) + + * SRU fix adds a type check for the encrypted_sessions peer table, + which is not initialized if no encrypted packets have been received. + + * Fixed in commit 4a636763850bcea590fba6066751d13a36c2b28d (https://github.com/rfinnie/2ping/commit/4a636763850bcea590fba6066751d13a36c2b28d) and included in upstream version 4.1.2. - SRU for bionic to be filed once it reaches cosmic. + [Test Case] + + * In one windows, run `2ping --listen` + + * In another, run `2ping 127.0.0.1` + + * Wait up to 5 minutes for TypeError. + + [Regression Potential] + + * SRU might not fix issue. + + * SRU fix might break scheduled cleanup of sessions when encryption + *is* activated, leading to resource exhaustion. + + * SRU fix might break scheduled cleanup of other data unrelated to + encryption. + + * Patch author has tested these scenarios and cannot reproduce any of + them. + + [Other Info] + + * Originally reported by Github user joe1981alAPR (https://github.com/rfinnie/2ping/issues/5). ** Patch added: "Fix cleanup crash on non-encrypted sessions" https://bugs.launchpad.net/ubuntu/+source/2ping/+bug/1786397/+attachment/5173866/+files/lp1786397.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786397 Title: 2ping crashes on non-encrypted session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/2ping/+bug/1786397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786397] [NEW] 2ping crashes on non-encrypted session
Public bug reported: Originally reported by Github user joe1981alAPR (https://github.com/rfinnie/2ping/issues/5). Fixed in commit 4a636763850bcea590fba6066751d13a36c2b28d (https://github.com/rfinnie/2ping/commit/4a636763850bcea590fba6066751d13a36c2b28d) and included in upstream version 4.1.2. SRU for bionic to be filed once it reaches cosmic. ** Affects: 2ping (Ubuntu) Importance: High Assignee: Ryan Finnie (fo0bar) Status: New ** Tags: bionic ** Tags added: bionic ** Changed in: 2ping (Ubuntu) Assignee: (unassigned) => Ryan Finnie (fo0bar) ** Changed in: 2ping (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786397 Title: 2ping crashes on non-encrypted session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/2ping/+bug/1786397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
The fix was bikeshedded a tiny bit on LKML, but is now accepted upstream and AIUI will be in linux-next soon: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?id=0d98ba8d70b0070ac117452ea0b663e26bbf46bf This change is tested as backwards compatible with Ubuntu 4.15, and would be appreciated for SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771467 Title: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1771467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775732] [NEW] arm64 soft lock crashes on nova-compute charm running
Public bug reported: Discovered on bionic, arm64 (Moonshot, verified on multiple swirlix cartridges), 4.15.0-22-generic. After deploying the nova-compute Juju charm, on subsequent reboots, within a few seconds after complete boot, everything will freeze and eventually display on the serial console (just these, no traces): [ 188.010510] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] [ 216.010292] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] (From here on, "lock up" refers to that sequence: boot a kernel, it completes boot to login prompt, then everything freezes a few seconds later, then BUGs.) It's usually but not always juju-log, sometimes a relation-ids or similar. I was able to briefly notice that it was in its startup config-changed hook. I've separated out and tested nearly everything it does during its startup config-changed (sets up bridging, writes some config files, restarts libvirtd/nova-compute/etc) without being able to trigger the bug, but I suspect proximity to boot is a factor. If I disable jujud- unit-nova-compute startup, boot, log in, re-enable and start (by which time over a minute or so has elapsed from boot finish), it will not lock up. Similarly, if I wrap the jujud startup in a `strace -Ff -o /var/log/strace.log` (which slows it down massively), it will not lock up. Watched pot syndrome. I've tried kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/ . I noticed most of the recent arm64 mainline kernels had failed builds, notified the kernel team channel and apw fixed the issue and started some rebuilds. What I've discovered (after many dead ends and a futile bisection) is that mainline builds before the rebuilds lock up, but fixed mainline builds initiated by apw DO NOT lock up. e.g. 4.16.3-041603.201804190730 locks up, but 4.16.6-041606.201806042022 does not lock up. (4.16.4 and 4.16.5 appear to have never been rebuilt and don't have arm64 debs, and that period is what I tried to bisect after figuring a fix must be in there.) But when I try to compile any of these recent kernels myself, they lock up when booted. Same kernel configs, tried on both bionic and in a cosmic chroot, tried both native arm64 compile and cross-compile from amd64. e.g. 4.16.6-041606.201806042022 from k.u.c does not lock up, but when I build it myself, it does. TBC, I've verified lock ups on the following kernels (all assume kernel configs from their respective Ubuntu or k.u.c mainline builds): - 4.15.0-22-generic from bionic (both Ubuntu-provided and my own recompile) - v4.16 (and all point releases) - v4.17 As I write this, my compiled v4.10 DOES NOT appear to lock up. I will attempt to bisect at a macro level from 4.10..4.15 and dig deeper. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 2 04:22 seq crw-rw 1 root audio 116, 33 Jun 2 04:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: arm64 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: Date: Fri Jun 8 00:13:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug arm64 bionic uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775732 Title: arm64 soft lock crashes on nova-compute charm running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
A patch has been submitted to linux-pci, and I've confirmed this fix works: https://lkml.org/lkml/2018/5/22/817 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771467 Title: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1771467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360 Gen9 w/ bionic 4.15.0
I tracked it down to https://patchwork.kernel.org/patch/10027157/ just before 4.15-rc1. This appears to affect all DL360/DL380 Gen9 I've encountered so far. Opened https://bugzilla.kernel.org/show_bug.cgi?id=199779 and currently working with Sinan Kaya to disagnose. ** Tags added: kernel-bug-exists-upstream ** Bug watch added: Linux Kernel Bug Tracker #199779 https://bugzilla.kernel.org/show_bug.cgi?id=199779 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed ** Summary changed: - Reboot/shutdown kernel panic on HP DL360 Gen9 w/ bionic 4.15.0 + Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771467 Title: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771467] [NEW] Reboot/shutdown kernel panic on HP DL360 Gen9 w/ bionic 4.15.0
Public bug reported:
Verified on multiple DL360 Gen9 servers with up to date firmware. Just
before reboot or shutdown, there is the following panic:
[ 289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 289.093085] {1}[Hardware Error]: event severity: fatal
[ 289.093087] {1}[Hardware Error]: Error 0, type: fatal
[ 289.093088] {1}[Hardware Error]: section_type: PCIe error
[ 289.093090] {1}[Hardware Error]: port_type: 4, root port
[ 289.093091] {1}[Hardware Error]: version: 1.16
[ 289.093093] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093094] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093095] {1}[Hardware Error]: slot: 0
[ 289.093096] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093097] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093098] {1}[Hardware Error]: class_code: 040600
[ 289.093378] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093380] {1}[Hardware Error]: Error 1, type: fatal
[ 289.093381] {1}[Hardware Error]: section_type: PCIe error
[ 289.093382] {1}[Hardware Error]: port_type: 4, root port
[ 289.093383] {1}[Hardware Error]: version: 1.16
[ 289.093384] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093386] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093386] {1}[Hardware Error]: slot: 0
[ 289.093387] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093388] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093674] {1}[Hardware Error]: class_code: 040600
[ 289.093676] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093678] Kernel panic - not syncing: Fatal hardware error!
[ 289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 289.105835] ERST: [Firmware Warn]: Firmware does not respond in time.
It does eventually restart after this. Then during the subsequent POST,
the following warning appears:
Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical
Drive(s) - Operation Failed
- 1719-Slot 0 Drive Array - A controller failure event occurred prior
to this power-up. (Previous lock up code = 0x13) Action: Install the
latest controller firmware. If the problem persists, replace the
controller.
The latter's symptoms are described in
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
but the running storage controller firmware is much newer than the doc's
resolution.
Neither of these problems occur during shutdown/reboot on the xenial
kernel.
FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56 (01/22/2018)),
the shutdown failure mode was a loop like so:
[529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0.
[529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.222884] Do you have a strange power saving mode enabled?
[529153.222884] Dazed and confused, but trying to continue
[529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554448] Do you have a strange power saving mode enabled?
[529153.554449] Dazed and confused, but trying to continue
[529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554451] Do you have a strange power saving mode enabled?
[529153.554452] Dazed and confused, but trying to continue
[529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554453] Do you have a strange power saving mode enabled?
[529153.554454] Dazed and confused, but trying to continue
[529153.554454] Uhhuh. NMI received for unknown reason 35 on CPU 0.
[529153.554455] Do you have a strange power saving mode enabled?
[529153.554456] Dazed and confused, but trying to continue
[529153.554457] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554458] Do you have a strange power saving mode enabled?
[529153.554458] Dazed and confused, but trying to continue
[529153.554459] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554460] Do you have a strange power saving mode enabled?
[529153.554460] Dazed and confused, but trying to continue
[529154.953916] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529154.953917] Do you have a strange power saving mode enabled?
[529154.953918] Dazed and confused, but trying to continue
But upgrading to 2.56 changes that to a kernel panic.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-signed-image-generic 4.15.0.21.22
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 15 23:11 seq
crw-rw 1 root audio 116, 33 May 15 23:11 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error:
[Bug 1764491] Re: Missing RaspberryPi 3B+
Here's the appropriate entry for all.db: # Raspberry Pi 3 B+ Machine: Raspberry Pi 3 Model B Plus Rev 1.3 DTB-Id: bcm2710-rpi-3-b-plus.dtb U-Boot-Script-Name: bootscr.rpi3 Required-Packages: u-boot-tools Boot-DTB-Path: /boot/firmware/bcm2710-rpi-3-b-plus.dtb Boot-Kernel-Path: /boot/firmware/vmlinuz Boot-Initrd-Path: /boot/firmware/initrd.img Boot-Script-Path: /boot/firmware/boot.scr "Machine: BCM2710" is not listed to not overlap with the 3 B entry; the B+ is also apparently considered a BCM2710, but /proc/device-tree/model shows "Raspberry Pi 3 Model B Plus Rev 1.3" on modern kernels/DTBs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764491 Title: Missing RaspberryPi 3B+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1764491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768371] [NEW] lan78xx_get_link_ksettings Oops when using bridging on Raspberry Pi 3 B+
Public bug reported: When trying to bridge lan78xx eth0 to a bridge on Raspberry Pi 3 B+, an Oops is generated and all interactions with eth0 deadlock. It appears to be the same as https://github.com/raspberrypi/linux/issues/2442 (patch at https://github.com/raspberrypi/linux/commit/c445a42487ff862a352911f485b8d3c45744edf0). [ 17.172107] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50 [ 17.191290] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 17.202764] Unable to handle kernel NULL pointer dereference at virtual address 0220 [ 17.202772] pgd = ff8acf62 [ 17.202775] [0220] *pgd= [ 17.202786] Internal error: Oops: 5 [#1] PREEMPT SMP ARM [ 17.202791] Modules linked in: bridge stp llc btsdio(+) bluetooth ecdh_generic brcmfmac brcmutil microchip cfg80211 joydev lan78xx uio_pdrv_genirq uio sch_fq_codel iscsi_tcp libiscsi_tcp libiscsi ip_tables x_tables btrfs zstd_decompress zstd_compress xxhash raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq raid1 raid0 multipath linear uas crc32_arm_ce sdhci_iproc aes_arm_bs crypto_simd cryptd [ 17.202882] CPU: 2 PID: 1133 Comm: brctl Not tainted 4.15.0-1010-raspi2 #11-Ubuntu [ 17.202884] Hardware name: BCM2835 [ 17.202900] PC is at phy_ethtool_ksettings_get+0x1c/0x94 [ 17.202919] LR is at lan78xx_get_link_ksettings+0x3c/0x4c [lan78xx] [ 17.202922] pc : [<8071b700>]lr : [<7f3deec8>]psr: 600f0013 [ 17.202925] sp : b0a77cd8 ip : b0a77cf0 fp : b0a77cec [ 17.202928] r10: b51b6fe0 r9 : 8102cba0 r8 : b6686400 [ 17.202931] r7 : b0a77d64 r6 : r5 : r4 : b0a77d64 [ 17.202934] r3 : b552c5ac r2 : 0001 r1 : b0a77d64 r0 : [ 17.202940] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none [ 17.202942] Control: 10c5383d Table: 30a7806a DAC: 0051 [ 17.202946] Process brctl (pid: 1133, stack limit = 0x6c3d92c5) [ 17.202949] Stack: (0xb0a77cd8 to 0xb0a78000) [ 17.202958] 7cc0: b56d9000 [ 17.202968] 7ce0: b0a77d0c b0a77cf0 7f3deec8 8071b6f0 80f05dc8 b56d9000 b0a77d64 [ 17.202974] 7d00: b0a77d5c b0a77d10 8089ab04 7f3dee98 b0a77d44 b0a77d20 80320e58 809ee454 [ 17.202980] 7d20: b52dd0b8 b52fcb28 afd16bc0 b52fc198 0001 b0a77e68 b0a77d64 889f956e [ 17.202988] 7d40: 80387378 80f05dc8 b56d9000 b9e04580 b0a77dc4 b0a77d60 7f884f94 8089aa40 [ 17.202993] 7d60: 8038f2f0 [ 17.202998] 7d80: [ 17.203004] 7da0: 889f956e b56d9000 0001 b0a77df4 b0a77dc8 [ 17.203013] 7dc0: 7f885900 7f884f6c b0a77de4 b0a77dd8 80f81200 b9e04580 0002 0001 [ 17.203020] 7de0: 7f89a0c4 b0a77e14 b0a77df8 7f88697c 7f885718 b0a77e7c 89a2 [ 17.203026] 7e00: b9e04000 b0a77e7c b0a77e2c b0a77e18 7f887460 7f88691c 80f05dc8 89a2 [ 17.203031] 7e20: b0a77e64 b0a77e30 808b6d08 7f887400 80889e58 808b6f20 b0a77e7c 889f956e [ 17.203041] 7e40: 80f81200 89a2 80f05dc8 7eb889ac b0a77ecc b0a77e68 [ 17.203055] 7e60: 808b73b4 808b6b84 89a2 7eb889ac 00cc 00307262 [ 17.203060] 7e80: 0002 00509d4c 0002 7eb88ca3 889f956e [ 17.203066] 7ea0: 89a2 fdfd 7eb889ac 80f81200 80f05dc8 7eb889ac b51b6fe0 [ 17.203071] 7ec0: b0a77eec b0a77ed0 8086d984 808b6f8c b5668780 0003 89a2 [ 17.203078] 7ee0: b0a77f7c b0a77ef0 8031b578 8086d87c b52fcee0 b9eb0310 b0a77f14 b0a77f08 [ 17.203084] 7f00: 8032bb48 8032b934 b0a77f54 b0a77f18 80307914 8032bb20 0020 [ 17.203089] 7f20: 8014e3a8 b9f94264 b9f94240 b9f94240 b9f93d00 80fb5230 b9f94264 [ 17.203095] 7f40: 889f956e e000 889f956e 0002 b5668780 b5668780 [ 17.203100] 7f60: 89a2 7eb889ac 0003 0080 b0a77fa4 b0a77f80 8031be04 8031b4c4 [ 17.203105] 7f80: 0050a008 76f99968 0002 0036 80109284 b0a76000 b0a77fa8 [ 17.203111] 7fa0: 8010924c 8031bd9c 0050a008 76f99968 0003 89a2 7eb889ac 00cc [ 17.203116] 7fc0: 0050a008 76f99968 0002 0036 7eb88ca9 00509f1c [ 17.203122] 7fe0: 00509f64 7eb88994 004f80cd 76f0c0a8 a00f0030 0003 [ 17.203153] [<8071b700>] (phy_ethtool_ksettings_get) from [<7f3deec8>] (lan78xx_get_link_ksettings+0x3c/0x4c [lan78xx]) [ 17.203195] [<7f3deec8>] (lan78xx_get_link_ksettings [lan78xx]) from [<8089ab04>] (__ethtool_get_link_ksettings+0xd0/0x104) [ 17.203256] [<8089ab04>] (__ethtool_get_link_ksettings) from [<7f884f94>] (port_cost+0x34/0xa0 [bridge]) [ 17.203329] [<7f884f94>] (port_cost [bridge]) from [<7f885900>] (br_add_if+0x1f4/0x630 [bridge])
[Bug 1768371] Re: lan78xx_get_link_ksettings Oops when using bridging on Raspberry Pi 3 B+
(ProcCpuinfoMinimal.txt indicates a Pi 3, not 3 B+, but that's the hardware the userland was attached to while reporting this. The dmesg output is from when it was attached to a 3 B+). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768371 Title: lan78xx_get_link_ksettings Oops when using bridging on Raspberry Pi 3 B+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1768371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766106] Re: ntp.ubuntu.com not reliable, but used in standard configuration
Thank you, 2001:67c:1560:8003::c8 availability has been fixed. $ ntpdate -q 2001:67c:1560:8003::c8 server 2001:67c:1560:8003::c8, stratum 2, offset 0.031201, delay 0.18932 24 Apr 13:10:37 ntpdate[26740]: adjust time server 2001:67c:1560:8003::c8 offset 0.031201 sec ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766106 Title: ntp.ubuntu.com not reliable, but used in standard configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
I'm not even remotely sure about things here, so some raw notes:
* Current bisect effort ("oh man, this will take forever"):
# bad: [69973b830859bc6529a7a0468ba0d80ee5117826] Linux 4.9
# good: [c8d2bc9bc39ebea8437fd974fdbc21847bb897a3] Linux 4.8
git bisect start 'v4.9' 'v4.8'
# good: [a5af7e1fc69a46f29b977fd4b570e0ac414c2338] rxrpc: Fix loss of PING
RESPONSE ACK production due to PING ACKs
git bisect good a5af7e1fc69a46f29b977fd4b570e0ac414c2338
# bad: [a379f71a30dddbd2e7393624e455ce53c87965d1] Merge branch 'akpm' (patches
from Andrew)
git bisect bad a379f71a30dddbd2e7393624e455ce53c87965d1
* Found ppc_tm=off, tried it on 4.15.0 generic, works!
* Might be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1664622 - might be a
qemu issue
* 4.15.0 does work on scalingstack bos02 POWER8 KVM xenial xenial hosts
(-machine pseries-xenial,accel=kvm,usb=off -cpu host), but I figured
that had already been tested and would have been noticed by now. (If I
hadn't mentioned before, the host running the ppc64el fullvirt VM at
home is a xenial host.)
* See also http://lists.gnu.org/archive/html/qemu-
ppc/2018-01/msg00021.html - might be mitigated with pseries-2.12 with a
bionic host qemu setup, but I don't have an easy way to test with a
bionic host + qemu at the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761626
Title:
[regression] bionic 4.15.0-13-generic panics on qemu ppc64el
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
4.8.0 works, 4.9.0 panics. I'll see about bisecting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
I can test earlier mainlines, but keep in mind that ppc64el is very slow on my home qemu setup (note "only" "very slow"; ppc64 is "amazingly slow", presumably due to endian swapping). Does Kernel have a POWER8 playground machine, if it comes to bisect compiling? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
Same result with 4.16.0-041600-generic and 4.13.0-38-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761626] [NEW] [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
Public bug reported: When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel panics before initrd. Going back to xenial 4.4.0 works correctly. linux-image-4.15.0-13-generic: Installed: 4.15.0-13.14 Candidate: 4.15.0-13.14 Version table: *** 4.15.0-13.14 500 500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main ppc64el Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 16:11 seq crw-rw 1 root audio 116, 33 Apr 5 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: ppc64el 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: Date: Thu Apr 5 16:13:28 2018 HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro ProcLoadAvg: 3.04 2.18 0.92 3/119 1643 ProcLocks: 1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF 2: POSIX ADVISORY WRITE 841 00:12:459 0 EOF 3: FLOCK ADVISORY WRITE 832 00:12:449 0 EOF 4: POSIX ADVISORY WRITE 802 00:12:432 0 EOF 5: POSIX ADVISORY WRITE 350 00:12:294 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/vda3 partition 1408960 0 -1 ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP Mon Apr 2 16:08:02 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.4.0-119-generic N/A linux-backports-modules-4.4.0-119-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago) cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug bionic ppc64el -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
** Attachment added: "Kernel boot log for 4.15.0-13-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+attachment/5103357/+files/1761626-4.15.0-13-generic.boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
** Attachment added: "libvirt XML file for instance" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+attachment/5103368/+files/1761626-libvirt.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739838] [NEW] geoip.ubuntu.com should use HTTPS
Public bug reported: geoip.ubuntu.com allows for HTTPS now; tzsetup/geoip_server should use https://geoip.ubuntu.com/lookup to prevent MITM location information disclosure. A complication is the d-i server variant (possibly others, but not e.g. desktop LiveCD) do not appear to have a certificate store, so wget will fail against this. I *think* pulling in ca-certificates-udeb would solve this, but I haven't been able to test. Note also that ubiquity uses geoname-lookup for city searching; that is covered by https://code.launchpad.net/~fo0bar/ubiquity/geoname-use- https/+merge/335568 . ** Affects: tzsetup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739838 Title: geoip.ubuntu.com should use HTTPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzsetup/+bug/1739838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 16632] Re: popcon should offer an option for submission via https
popcon.ubuntu.com now defaults to HTTPS, with default HTTPS for all GET functions. However, it appears popcon-upload would require a sizable rewrite to support HTTPS, as it currently does TCP communication by hand. Debian bug #880121 is the upstream bug for this, and looks like it is actively being discussed if/how to implement this. ** Bug watch added: Debian Bug tracker #880121 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880121 ** Also affects: popularity-contest (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880121 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/16632 Title: popcon should offer an option for submission via https To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/16632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702785] [NEW] High memory and "can't fork" on heavy long-lived cron daemon
Public bug reported: Ubuntu 14.04.5 LTS, cron 3.0pl1-124ubuntu2 On a server with heavy cron use (a few thousand entries across cron.d / users, several runs per second, a few dozen forks running at any given time), cron will creep up in memory usage. Last I saw was 6GB RSS, at which point it will start doing: Jul 6 07:01:27 host cron[21699]: (CRON) error (can't fork) Not all runs will fail, but this trend will continue until cron is restarted. ** Affects: cron (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702785 Title: High memory and "can't fork" on heavy long-lived cron daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647020] [NEW] Brightness resets to full when on/off battery
Public bug reported: In yakkety, when my ThinkPad X250 goes on or off battery, the screen is reset to full brightness. Xenial and before did not have this problem. I have not found any other instances which trigger this (lid close, etc). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-power-manager 3.22.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 2 22:16:21 2016 InstallationDate: Installed on 2015-03-07 (637 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to yakkety on 2016-12-01 (1 days ago) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647020 Title: Brightness resets to full when on/off battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1647020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578745] Re: Update firmware for Raspberry Pi 3 support
The debdiff was meant to be a general overview of what had changed w/r/t the binaries, not a literal debdiff, sorry. ppa:ubuntu-raspi2/ppa-rpi3 linux-firmware-raspi2 1.20160503+6832d9a- 0ubuntu1~rpi3 is the same as what's being proposed (minus the ~rpi3 suffix). Paolo, could you possible take this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578745 Title: Update firmware for Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581720] Re: Raspberry Pi 3 64-bit kernel
Yeah sorry, meant to loop back on this. His kernel is minimally functional and I've been using it on a test arm64 machine (though looks like vchiq is intentionally disabled presumably because it's not functional, and the brcmfmac module doesn't recognize the wifi chipset even with firmware present), but it looks like it is a very early one- off effort. We do eventually want to have RPi3 arm64 support, but it's probably not going to happen for awhile. Interestingly, the Raspbian kernel trees show no work toward arm64 support; hopefully they're just working on it in the background. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581720 Title: Raspberry Pi 3 64-bit kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1581720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578745] Re: Update firmware for Raspberry Pi 3 support
This firmware also works with 64-bit kernel / userland; enable arm64 arch (debdiff updated). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578745 Title: Update firmware for Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578745] Re: Update firmware for Raspberry Pi 3 support
** Patch added: "linux-firmware-raspi2-1.20160503+6832d9a_3.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+attachment/4664171/+files/linux-firmware-raspi2-1.20160503+6832d9a_3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578745 Title: Update firmware for Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581720] Re: Raspberry Pi 3 64-bit kernel
Looks like the kernel in that image was sourced from https://github.com/Electron752/boot64-rpi3, built from https://github.com/Electron752/linux . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581720 Title: Raspberry Pi 3 64-bit kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1581720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581720] [NEW] Raspberry Pi 3 64-bit kernel
Public bug reported: The raspi2 kernel works fine on the Raspberry Pi 3 in 32-bit mode, but 64-bit mode is also an option. I've currently got a test setup using xenial arm64 userland + updated firmware/u-boot + the 4.5.0 kernel from someone who made a Debian image a month ago (http://www.tom- yam.or.jp/rpi3/rpi3-arm64-debian-20160414.img.xz), but I don't see any information about the source tree he used to compile it. Presumably https://github.com/raspberrypi/linux/tree/rpi-4.5.y; I'll see if I can reproduce with his config (attached). Hopefully the same kernel tree can be used for (raspi2 32-bit & raspi3 32-bit) and (raspi3 64-bit). ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Tags: raspi3 ** Attachment added: "config-4.5.0+" https://bugs.launchpad.net/bugs/1581720/+attachment/4662582/+files/config-4.5.0+ ** Tags added: raspi3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581720 Title: Raspberry Pi 3 64-bit kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1581720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578745] Re: Update firmware for Raspberry Pi 3 support
** Patch removed: "linux-firmware-raspi2-1.20160503+6832d9a.patch" https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+attachment/4656563/+files/linux-firmware-raspi2-1.20160503+6832d9a.patch ** Patch added: "linux-firmware-raspi2-1.20160503+6832d9a_2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+attachment/4661069/+files/linux-firmware-raspi2-1.20160503+6832d9a_2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578745 Title: Update firmware for Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578745] Re: Update firmware for Raspberry Pi 3 support
Debdiff updated with postinst config test for config.txt ^device_tree_address=. If not found, it adds: # Added by linux-firmware-raspi2 device_tree_address=0x100 device_tree_end=0x8000 Tested with vanilla raspi2 install + upgrade to 1.20160503+6832d9a- 0ubuntu1, and subsequent reinstalls. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578745 Title: Update firmware for Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578745] Re: Update firmware for Raspberry Pi 3 support
Damn, you're right. I knew that was needed in certain situations with the new firmware (and have it being written in my MP for raspi3 support in livecd-rootfs), but for some reason thought xenial u-boot + new firmware + raspi2 didn't need it. I'll write a configure hook for detecting the upgrade and modifying config.txt, and get back to you. FYI, this seems to be the traditional location for the DTB (and where it was placed originally): device_tree_address=0x100 device_tree_end=0x8000 0x100 begin is the same, but end is now 0x8000 (before the kernel area) as the xenial kernel DTB is approaching the size of (0x4000-0x100). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578745 Title: Update firmware for Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580323] Re: Pull/merge 2016.05~rc3+dfsg1-1 from Debian experimental
Note: I don't mean above this was an endorsement from Adam, just that this is the general path we want to take to get raspi3 support into yakkety. Related bugs at https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3#Bugs_filed . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580323 Title: Pull/merge 2016.05~rc3+dfsg1-1 from Debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1580323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580323] Re: Pull/merge 2016.05~rc3+dfsg1-1 from Debian experimental
** Description changed: Per a conversation with Adam Conrad, please merge 2016.05~rc3+dfsg1-1 (currently in Debian experimental) into yakkety, and apply the patch at - https://bugs.debian.org/823524 to enable Raspberry Pi 32-bit support. + https://bugs.debian.org/823524 to enable Raspberry Pi 3 32-bit support. 2016.05 (when released) is likely to get that patch and be released long before yakkety, but we want to get a jump on official raspi3 support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580323 Title: Pull/merge 2016.05~rc3+dfsg1-1 from Debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1580323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580326] [NEW] Add raspi3 subarch
Public bug reported: MP: #293959 contains the gory details. https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3#Bugs_filed ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Tags: patch raspi3 ** Tags added: patch raspi3 ** Branch linked: lp:~fo0bar/livecd-rootfs/raspi2-rpi3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580326 Title: Add raspi3 subarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1580326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578745] Re: Update firmware for Raspberry Pi 3 support
** Tags added: raspi3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578745 Title: Update firmware for Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578505] Re: Raspberry Pi 3 support
** Tags added: raspi3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578505 Title: Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1578505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580323] [NEW] Pull/merge 2016.05~rc3+dfsg1-1 from Debian experimental
Public bug reported: Per a conversation with Adam Conrad, please merge 2016.05~rc3+dfsg1-1 (currently in Debian experimental) into yakkety, and apply the patch at https://bugs.debian.org/823524 to enable Raspberry Pi 32-bit support. 2016.05 (when released) is likely to get that patch and be released long before yakkety, but we want to get a jump on official raspi3 support. ** Affects: u-boot (Ubuntu) Importance: Undecided Status: New ** Tags: raspi3 ** Tags added: raspi3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580323 Title: Pull/merge 2016.05~rc3+dfsg1-1 from Debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1580323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578505] Re: Raspberry Pi 3 support
** Description changed: Note that this makes a few assumptions: - 1) Will not work as-is; updated u-boot and linux-firmware-raspi2 will - also be required. I'm testing with u-boot HEAD and raspberrypi/firmware - HEAD. Details at https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3 + 1) Will not work as-is (but is safe to apply); updated u-boot (Debian: + #823524) and linux-firmware-raspi2 (LP: #1578745) will also be required + to take advantage of booting on the RPi3. Details at + https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3 2) For some reason, u-boot mkenvimage creates a uboot.env using the RPi2 config which u-boot HEAD just doesn't read, citing a CRC error. This occurs even when using mkenvimage from HEAD. I'm still trying to determine if it's a bug with u-boot, but boot.scr works fine. I've translated the uboot.env to its equivalent boot.scr script and it works fine, so I don't see why we can't just use boot.scr on the RPi3. (saveenv within the u-boot shell writes a uboot.env which it can subsequently re-read, interestingly.) 3) The all.db entry, minus the move to boot.scr, is based on the RPi2 entry above, right down to the "XXX". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578505 Title: Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1578505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578745] Re: Update firmware for Raspberry Pi 3 support
** Patch added: "linux-firmware-raspi2-1.20160503+6832d9a.patch" https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+attachment/4656563/+files/linux-firmware-raspi2-1.20160503+6832d9a.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578745 Title: Update firmware for Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578745] [NEW] Update firmware for Raspberry Pi 3 support
Public bug reported: Please see the debdiff for updating to 1.20160503+6832d9a (https://github.com/raspberrypi/firmware/tree/6832d9a431a98b640accb2b76eac38a420d7c680). This enables boot support for the Raspberry Pi 3 (https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3). In addition, I've modified the package to install Broadcom 43430 firmware, needed for the RPi3's wifi/bluetooth module. Apparently this firmware was given directly from Broadcom to the Raspberry Pi folks, as the only canonical location I've found for it is http://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree /firmware-nonfree_0.43+rpi4.dsc . There's a copy on Github at https://github.com/RPi-Distro/firmware- nonfree/tree/54bab3d6a6d43239c71d26464e6e10e5067ffea7/brcm80211/brcm though: a591a0865e5af6803aab4dc2dda83141b4e0de3bf36e9ee0f986518af4da4ffc brcmfmac43430-sdio.bin 872fde4f9942d9aba805880d6eaddfe050305626fd58ad955bfe77c04f6b75a5 brcmfmac43430-sdio.txt ** Affects: linux-firmware-raspi2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578745 Title: Update firmware for Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578505] Re: Raspberry Pi 3 support
** Patch added: "flash-kernel-3.0~rc.4ubuntu63.debdiff" https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1578505/+attachment/4656132/+files/flash-kernel-3.0~rc.4ubuntu63.debdiff ** Description changed: - Debdiff to follow. - Note that this makes a few assumptions: 1) Will not work as-is; updated u-boot and linux-firmware-raspi2 will also be required. I'm testing with u-boot HEAD and raspberrypi/firmware HEAD. Details at https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3 2) For some reason, u-boot mkenvimage creates a uboot.env using the RPi2 config which u-boot just doesn't read, citing a CRC error. This occurs even when using mkenvimage from HEAD. I'm still trying to determine if it's a bug with u-boot, but boot.scr works fine. I've translated the uboot.env to its equivalent boot.scr script and it works fine, so I don't see why we can't just use boot.scr on the RPi3. (saveenv within the u-boot shell writes a uboot.env which it can subsequently re-read, interestingly.) 3) The all.db entry, minus the move to boot.scr, is based on the RPi2 entry above, right down to the "XXX". ** Description changed: Note that this makes a few assumptions: 1) Will not work as-is; updated u-boot and linux-firmware-raspi2 will also be required. I'm testing with u-boot HEAD and raspberrypi/firmware HEAD. Details at https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3 2) For some reason, u-boot mkenvimage creates a uboot.env using the RPi2 - config which u-boot just doesn't read, citing a CRC error. This occurs - even when using mkenvimage from HEAD. I'm still trying to determine if - it's a bug with u-boot, but boot.scr works fine. I've translated the - uboot.env to its equivalent boot.scr script and it works fine, so I - don't see why we can't just use boot.scr on the RPi3. (saveenv within - the u-boot shell writes a uboot.env which it can subsequently re-read, - interestingly.) + config which u-boot HEAD just doesn't read, citing a CRC error. This + occurs even when using mkenvimage from HEAD. I'm still trying to + determine if it's a bug with u-boot, but boot.scr works fine. I've + translated the uboot.env to its equivalent boot.scr script and it works + fine, so I don't see why we can't just use boot.scr on the RPi3. + (saveenv within the u-boot shell writes a uboot.env which it can + subsequently re-read, interestingly.) 3) The all.db entry, minus the move to boot.scr, is based on the RPi2 entry above, right down to the "XXX". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578505 Title: Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1578505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578505] [NEW] Raspberry Pi 3 support
Public bug reported: Debdiff to follow. Note that this makes a few assumptions: 1) Will not work as-is; updated u-boot and linux-firmware-raspi2 will also be required. I'm testing with u-boot HEAD and raspberrypi/firmware HEAD. Details at https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3 2) For some reason, u-boot mkenvimage creates a uboot.env using the RPi2 config which u-boot just doesn't read, citing a CRC error. This occurs even when using mkenvimage from HEAD. I'm still trying to determine if it's a bug with u-boot, but boot.scr works fine. I've translated the uboot.env to its equivalent boot.scr script and it works fine, so I don't see why we can't just use boot.scr on the RPi3. (saveenv within the u-boot shell writes a uboot.env which it can subsequently re-read, interestingly.) 3) The all.db entry, minus the move to boot.scr, is based on the RPi2 entry above, right down to the "XXX". ** Affects: flash-kernel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578505 Title: Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1578505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562455] [NEW] Please sync 2ping 3.2.1-1 (universe) from Debian unstable (main)
Public bug reported:
2ping 3.2.0-1 (currently in xenial) contains a remote crash denial of
service condition when the peer sends a notice with non-ASCII (e.g.
Unicode) text. This cannot lead to a remote crash in the listener's
default configuration (only when --debug is passed), but IMHO is serious
enough that this fix should be included before xenial is released.
Please sync 2ping 3.2.1-1 from Debian unstable. 3.2.1-1 contains the
following fix against 3.2.0-1 to properly render Unicode notices and
filter invalid high characters:
diff --git a/twoping/cli.py b/twoping/cli.py
index 418f5b7..3e94573 100755
--- a/twoping/cli.py
+++ b/twoping/cli.py
@@ -335,7 +335,7 @@ class TwoPing():
(packets.OpcodeExtended.id in packet_in.opcodes) and
(packets.ExtendedNotice.id in
packet_in.opcodes[packets.OpcodeExtended.id].segments)
):
-notice =
str(packet_in.opcodes[packets.OpcodeExtended.id].segments[packets.ExtendedNotice.id].text)
+notice =
unicode(str(packet_in.opcodes[packets.OpcodeExtended.id].segments[packets.ExtendedNotice.id].text),
'UTF-8', 'replace')
self.print_out(' ' + _('Peer notice:
{notice}').format(notice=notice))
sock_class.courtesy_messages[peer_tuple][replied_message_id_int] =
(time_begin, replied_message_id)
** Affects: 2ping (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1562455
Title:
Please sync 2ping 3.2.1-1 (universe) from Debian unstable (main)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/2ping/+bug/1562455/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 3] Re: Custom information for each translation team
** Information type changed from Private Security to Public ** Changed in: launchpad Assignee: stayros (lsuzex3) => (unassigned) ** Changed in: ubuntu Assignee: stayros (lsuzex3) => (unassigned) ** Changed in: mono (Ubuntu) Assignee: stayros (lsuzex3) => (unassigned) ** Changed in: ubuntu Status: Fix Released => Invalid ** Changed in: mono (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/3 Title: Custom information for each translation team To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/3/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510322] [NEW] xenial-proposed tar 1.28-2 generates illegal instruction on ppc64el
Public bug reported: Please disregard, this was attempted on a POWER7 host. ** Affects: tar (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510322 Title: xenial-proposed tar 1.28-2 generates illegal instruction on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1510322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510322] Re: xenial-proposed tar 1.28-2 generates illegal instruction on ppc64el
** Description changed: - Preparing to unpack .../tar_1.28-2_ppc64el.deb ... - Unpacking tar (1.28-2) over (1.27.1-2) ... - Setting up tar (1.28-2) ... - dpkg-deb: error: subprocess tar was killed by signal (Illegal instruction) - dpkg: error processing archive /var/cache/apt/archives/binutils_2.25.51.20151022-0ubuntu3_ppc64el.deb (--unpack): - subprocess dpkg-deb --control returned error exit status 2 - dpkg-deb: error: subprocess tar was killed by signal (Illegal instruction) - dpkg: error processing archive /var/cache/apt/archives/libdpkg-perl_1.18.3ubuntu1_all.deb (--unpack): - subprocess dpkg-deb --control returned error exit status 2 - dpkg-deb: error: subprocess tar was killed by signal (Illegal instruction) - dpkg: error processing archive /var/cache/apt/archives/dpkg-dev_1.18.3ubuntu1_all.deb (--unpack): - subprocess dpkg-deb --control returned error exit status 2 - Errors were encountered while processing: - /var/cache/apt/archives/binutils_2.25.51.20151022-0ubuntu3_ppc64el.deb - /var/cache/apt/archives/libdpkg-perl_1.18.3ubuntu1_all.deb - /var/cache/apt/archives/dpkg-dev_1.18.3ubuntu1_all.deb - E: Sub-process /usr/bin/dpkg returned an error code (1) - - (xenial-ppc64el)I have no name!@kelsey01:~$ apt-cache policy tar - tar: - Installed: 1.28-2 - Candidate: 1.28-2 - Version table: - *** 1.28-2 0 - 500 http://ports.ubuntu.com/ubuntu-ports/ xenial-proposed/main ppc64el Packages - 100 /var/lib/dpkg/status - 1.27.1-2 0 - 500 http://ports.ubuntu.com/ubuntu-ports/ xenial/main ppc64el Packages - (xenial-ppc64el)I have no name!@kelsey01:~$ tar zcvf /tmp/bin.tar.gz /bin - Illegal instruction - (xenial-ppc64el)I have no name!@kelsey01:~$ dmesg | tail -n 1 - [2939559.907248] tar[23871]: unhandled signal 4 at 10060490 nip 10060490 lr 10060384 code 30001 + Please disregard, this was attempted on a POWER7 host. ** Changed in: tar (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510322 Title: xenial-proposed tar 1.28-2 generates illegal instruction on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1510322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
