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. I
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-3
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 t
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 notificatio
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_i
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: registe
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 are
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_c
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); wait
** 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/187085
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:
https://bugs
12 matches
Mail list logo
