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
** 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
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
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
** 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-1
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
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.
#
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:
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: [:
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
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
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:
** 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
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
** 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.
** 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.
** 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.
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:
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.
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
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.
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:
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
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
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
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:
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
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
>
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);
** 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.
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
** 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:
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.
** 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
** 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
** 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
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"
** 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]
** 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
** 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.
** 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.
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
** 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"
** 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.
** 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.
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
** 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.
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
** 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
** 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
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.
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
** 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
[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
** 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
.
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)
** Chan
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
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
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
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:
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:
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:
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
(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.
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
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:
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
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
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
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
** 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
** 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.
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
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
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
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:
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
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
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
** 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
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
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-
** 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"
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.
--
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
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
** 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
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:
** 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:
** 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:
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
** 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)
** 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
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
** 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
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
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
** 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
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.
** 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
1 - 100 of 244 matches
Mail list logo
