I can confirm I am also seeing a very similar set of circumstances:
-Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
-5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64
aarch64 GNU/Linux
-The "tunnel" in my case is using Wireguard to a server hosted externally.
-
Forgot to include:
Jul 28 18:18:25 dns1 kernel: [ 1289.970276] [ cut here ]
Jul 28 18:18:25 dns1 kernel: [ 1289.970354] NETDEV WATCHDOG: eth0 (lan78xx):
transmit queue 0 timed out
Jul 28 18:18:25 dns1 kernel: [ 1289.970463] WARNING: CPU: 1 PID: 0 at
net/sched/sch_generic
FWIW, i actually thought this was a bug with the latest raspbian image
and decided to move forward with using 20.04 on my raspberry pi's, turns
out that wasn't the case.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubunt
I am also on a 3B+
ubuntu@dns1:~$ cat /proc/device-tree/model
Raspberry Pi 3 Model B Plus Rev 1.3
I dont believe you need anything fancy with IPv6, im not tunneling any v6 and
its occurring with me.
I do have IPv6 enabled on the interface used for tuneling.
Hui Wang, im happy to provide a shel
Absolutely!
--
My Raspberry Pi sits inside my home network, its config:
eth0:
IP: 192.168.200.11
GW: 192.168.200.1
IPv6: enabled (prefix delegation from ISP)
Metric: 300
wlan0:
IP: 192.168.209.11
GW: 192.168.209.1
IPv6: enabled (prefix delegation from ISP)
Metric: 400
wg0: flags=209
Forgot to include:
Raspberry PI:
ubuntu@dns1:~$ uname -a
Linux dns1 5.4.0-1022-raspi #25-Ubuntu SMP PREEMPT Thu Oct 15 13:31:49 UTC 2020
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@dns1:~$
VPS:
root@m21:~# uname -a
Linux m21 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64
x86_6
And the most recent crash:
Oct 22 11:44:51 dns1 kernel: [ 3096.793118] [ cut here ]
Oct 22 11:44:51 dns1 kernel: [ 3096.793183] NETDEV WATCHDOG: eth0 (lan78xx):
transmit queue 0 timed out
Oct 22 11:44:51 dns1 kernel: [ 3096.793282] WARNING: CPU: 2 PID: 0 at
net/sched/sch_
So exactly what type of payload triggers the issues, that i cant work
out.
I know the traffic profile, vast majority of it is monitoring related as my VPS
is running grafana/influx and my internal clients are sending data over this
tunnel using telegraf.
There is also a fair bit of ICMP etc traf
RE IPv6, there is some manual config.
I have each vlan/network assigned a /64. On my pi's they get an address
in that /64 (different networks for eth0 and wlan0) but they do have a
static assignment as well (should have included that earlier:
interface eth0
metric 300
static ip6_address=2403:
@juergh I may have (somewhat) found the trigger.
As previously noted, my internal clients have a static route to the remote
wireguard networks via my raspberry pi. This is defined in my internal router
(Unifi)
ie:
client > router > static route (10.241.0.0/24) to pi eth0 IP > pi > tunnel > VPS
Ok yup this is almost certainly the issue (when the tunnel is pi is
tunnelling traffic for something other than itself)
My tunnel has been up for 12 hours, no crashes at all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in
Well, it took more than 24 hours for my Pi to crash again, but it did
happen. I wasn't able to capture much of what triggered it as i wasn't
home at the time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://
This has probably already been noticed, but in an attempt to simply get
my PI working somewhat the way i wanted, i changed my tunnel to run over
wlan0 instead of eth0 (they both connect back to the same network so
doesn't make a huge difference).
Tunnel and interfaces have been up for days, no iss
I also could not boot 20.04.1 on a Raspberry Pi 4.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895550
Title:
Ubuntu 18.04.5 release for Raspberry Pi 4 does not boot
Status in linux
** Package changed: linux (Ubuntu) => linux-raspi2 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1895550
Title:
Ubuntu 18.04.5 release for Raspberry Pi 4 does not boot
Public bug reported:
1. root@x1:~# cat /proc/version_signature
Ubuntu 4.4.0-72.93-generic 4.4.49
2. attached
3. # lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04
4. # apt-cache policy linux-image-`uname -r`
linux-image-4.4.0-72-generic:
Installed: 4.4.0-72.93
Candid
After partitioning two disks with two 1G partitions each, then this
script will create two RAID1 devices (md0, md1) to test mdadm --stop
commands
** Attachment added: "script to create two mirror raid devices"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682456/+attachment/4861363/+fi
I run this script to watch whether the sysfs md structure goes away
after stopping the device.
** Attachment added: "simple sysfs path watch script"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682456/+attachment/4861364/+files/w.sh
--
You received this bug notification because you
To recreate:
1. partition two disks sized the same into two equal partitions (2G
disk, two 1G partitions each)
# cat /proc/partitions
major minor #blocks name
252 322097152 vdc
252 331048576 vdc1
252 341047552 vdc2
252 482097152 vdd
252 49
I tested with the updated kernel and unfortunately, it does not resolve
the issue. Since these are recently uncovered issues upstream, could
you cherry pick those against the Zesty kernel? Once we know it's
resolved in the latest kernel we can track down what changes needed for
Xenial.
--
You r
Looking at the storage config vs. what's on the system, there is a disk
'sdb' with properties:
model: MM1000GBKAL,
name: sdb,
serial: 3001438033c8e841
which is no longer present on the system. I suspect either a bad disk,
or disk has been removed.
As such the storage config sent by maas is not
https://certification.ubuntu.com/hardware/201509-19592/
Possibly a different driver is needed but in any case, MaaS needs to figure
what driver is needed and
if the system isn't configured correctly.
On Tue, Apr 18, 2017 at 4:18 PM, Scott Moser wrote:
> OK.
> So what seems to be the issue here
Booting with 'nomodeset' allows system to boot into graphics mode.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734490
Title:
Graphics mode never switches from console mode on Artful
Public bug reported:
Booting a Lenovo S-10 Ideal pad on the 4.13 kernel in Artful fails to
bring up the Graphical display (only the mouse shows). Console-mode
works fine. Switch back to previous release kernel (4.10) works fine.
Booting includes an intel graphics assertion about plane B switchi
https://bugs.freedesktop.org/show_bug.cgi?id=102929
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734490
Title:
Graphics mode never switches from console mode on Artful kernel
Status
[4.710462] WARNING: CPU: 1 PID: 168 at
/build/linux-2JtliJ/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:1252
assert_planes_disabled+0x128/0x140 [i915]
[4.710466] Modules linked in: i915(+) psmouse ahci r8169 i2c_algo_bit
libahci drm_kms_helper pata_acpi ssb syscopyarea sysfillrect s
So, /dev/bcache/by-uuid is not getting created.
That's the same kernel bug I filed.
And, if they were, I think they'd get moved properly.
init-bottom/udev script does the following:
# Stop udevd, we'll miss a few events while we run init, but we catch up
udevadm control --exit
# move the /dev
pfs to the rootfs; fall back to util-linux mount that does
# not understand -o move
mount -n -o move /dev ${rootmnt}/dev || mount -n --move /dev ${rootmnt}/dev
Let's see if that helps resolve the "missing" symlinks.
On Thu, Nov 30, 2017 at 10:27 AM, Ryan Harper
wrote:
> So
** Bug watch added: Debian Bug tracker #844775
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844775
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729145
Title:
/dev/bcache/by-uu
It looks like there is some ordering issues:
This is a grep through /run/udev/links ; these are checked by udev-dev
# find . -name 'b250*'
./\x2fdisk\x2fby-uuid\x2f0a270acb-56b8-4498-8bad-b3bb149fe869/b250:1
./\x2fdisk\x2fby-uuid\x2f92b0868d-7e56-4956-8e55-2c90ebee4a72/b250:0
./\x2fbcache\x2fby-u
id/ and dname
will point to that, which abstracts away whether it points to bcache0, 1 ,
or N.
/dev/disk/by-dname/foo -> ../../../bcache/by-uuid/ ->
../../bcacheN
On Thu, Nov 30, 2017 at 7:16 PM, Ryan Harper
wrote:
> It looks like there is some ordering issues:
>
> This is a gre
Untested patch. Hoping to convey the change that's needed.
- decouple emitting a cached_dev CHANGE uevent which includes dev.uuid and
dev.label
from bch_cached_dev_run() which only happens when a bcacheX device is bound
to the
actual backing block device (bcache0 -> vdb)
- update bch_c
Hi Joseph,
Sorry, I didn't give that a compile either; I just wanted to show what the
change could look like;
Let me see if I can get that to at least compile.
On Mon, Dec 4, 2017 at 11:18 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> It looks like env[] was declared in bch_ca
Looks like those two kfree's in dev_run can be dropped since that was an
exit after kmalloc'ing env entries which are now only done in
bch_cached_dev_emit_change()
which is only called by dev_run after it knows that the device is not
yet running.
On Mon, Dec 4, 2017 at 11:35 AM, R
Revised patch, should fix error with kfree on env
** Patch added: "bcache_always_emit_backing_dev_change_uevent_v2.diff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+attachment/5018329/+files/bcache_always_emit_backing_dev_change_uevent_v2.diff
--
You received this bug notif
Thanks! I'll give it a try today.
On Tue, Dec 5, 2017 at 3:43 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> I built an Artful test kernel with the path provided by Ryan. The test
> kernel can be downloaded from:
>
> http://kernel.ubuntu.com/~jsalis
333685 -> ../../bcache2
├── 57e009b1-6bf4-42ea-abe0-334b10941a0b -> ../../bcache0
├── 7ce7dc32-7da9-42a8-899a-5d21ed7ea714 -> ../../bcache3
└── 92d882d8-38cd-4537-847b-6f9c40ba67b4 -> ../../bcache1
2 directories, 6 files
On Tue, Dec 5, 2017 at 4:00 PM, Ryan Harper
wrote:
> Th
Thanks for doing the cleanup; Patch looks good and I approve.
Signed-off-by: Ryan Harper
On Tue, Dec 5, 2017 at 4:59 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> In the final patch we submit for SRU, it will also include your Signed-
> off-by, I just forgot to a
Here's the Zesty test; all looks good.
ubuntu@ubuntu:~$ cat /etc/cloud/build.info
build_name: server
serial: 20171207
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 4.10.0-40-generic #44~lp1729145 SMP Wed Dec 6 16:21:45 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ubuntu:~$ tree /dev/bcache
/dev/bcache
Tested the xenial update. I had one boot where the links didn't get
created, but I cannot recreate that issue now.
On Thu, Dec 7, 2017 at 9:56 AM, Ryan Harper
wrote:
> Here's the Zesty test; all looks good.
>
> ubuntu@ubuntu:~$ cat /etc/cloud/build.info
> build_name: ser
esting and the patch, Ryan. I can submit and SRU request.
>
> We should also send this upstream for inclusion in the mainline kernel.
> Is that something you think you can do? If not, I can do it for you.
>
> --
> You received this bug notification because you are subscri
I think it may have always been present; I can recreate this on Trusty
GA kernels; we've changed how we clean/remove bcache devices which I
believe is triggering a new path on Trusty kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Not sure if this was supposed to also be fixed in bionic-proposed yet,
but I assumed so and
it's not working there; I'll test -proposed in artful and xenial next.
ubuntu@ubuntu:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu Bion
Artful verified:
ubuntu@ubuntu:~$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ubuntu:~$ apt-cache policy linux-image-virtual
linux-imag
Xenial verified.
root@ubuntu:~# lsb_release -rd
Description:Ubuntu 16.04.4 LTS
Release:16.04
root@ubuntu:~# uname -a
Linux ubuntu 4.4.0-117-generic #141-Ubuntu SMP Tue Mar 13 11:58:07 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu:~# apt-cache policy linux-image-virtual
linux-ima
Public bug reported:
root@ubuntu:~# lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
root@ubuntu:~# apt-cache policy linux-image-virtual
linux-image-virtual:
Installed: 4.13.0.37.40
Candidate: 4.13.0.37.40
Version table:
*** 4.13.0.37.40 500
500 http://archive.ubu
** Also affects: tar (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1757565
Title:
btrfs and tar sparse truncate archives
Status in
v4.14-rc1: BAD
ubuntu@ubuntu:~$ uname -r
4.14.0-041400rc1-generic
ubuntu@ubuntu:~$ sudo bash
root@ubuntu:~# mount /dev/sda /mnt
root@ubuntu:~# grep sda /proc/mounts
/dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0
root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/
v4.15.7: GOOD
root@ubuntu:~# uname -r
4.15.7-041507-generic
root@ubuntu:~# mount /dev/sda /mnt
root@ubuntu:~# grep sda /proc/mounts
/dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0
root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir
-p /mnt/tmp; cp -
On Thu, Mar 22, 2018 at 2:56 PM, Joseph Salisbury
wrote:
> @Scott, will that upstream commit make it so the kernel fix we are
> looking for is not required?
This is a curtin workaround; we're not using the sparse flag when invoking tar;
However, the bug/issue remains between tar and btrfs.
Outsi
v4.15 Final: GOOD
root@ubuntu:~# uname -r
4.15.0-041500-generic
root@ubuntu:~# mount /dev/sda /mnt
root@ubuntu:~# grep sda /proc/mounts
/dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0
root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir
-p /mnt/tmp;
v4.15-rc6: GOOD
root@ubuntu:~# uname -r
4.15.0-041500rc6-generic
root@ubuntu:~# mount /dev/sda /mnt
root@ubuntu:~# grep sda /proc/mounts
/dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0
root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir
-p /mnt/tmp;
This looks promising and landed in -rc2:
Btrfs: fix reported number of inode blocks after buffered append writes
https://www.spinics.net/lists/linux-btrfs/msg71274.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
Yeah, rc2 was fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1757565
Title:
btrfs and tar sparse truncate archives
Status in linux package in Ubuntu:
Triaged
Status in tar packa
Test kernel: GOOD
root@ubuntu:~# cat /proc/version_signature
Ubuntu 4.13.0-37.42~lp1757565-generic 4.13.13
root@ubuntu:~# mount /dev/sda /mnt
root@ubuntu:~# grep sda /proc/mounts
/dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0
root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5s
@jsalisbury Did you get a chance to forward the patch upstream? We've a
userspace fix in the bcache-tools package for now; I've sent that
upstream here:
https://github.com/koverstreet/bcache-tools/pull/1
Kent was asking about the kernel fix, to which I pointed to the patch
here.
--
You receive
On Fri, Feb 16, 2018 at 12:14 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> @raharper, I got side tracked and it got pushed down on my list. I can
> still send it upstream if you want. It's currently in Ubuntu as a SAUCE
> patch.
>
That would be great!
Thanks,
>
> --
> You
Public bug reported:
successfully wiped device /dev/md0 on attempt 1/4
shutdown running on holder type: 'bcache' syspath: '/sys/class/block/bcache0'
stopping bcache cacheset at: /sys/fs/bcache/7834b3df-d029-49a3-9c1b-3fd628db10f2
waiting for /sys/fs/bcache/7834b3df-d029-49a3-9c1b-3fd628db10f2 to b
On Fri, Mar 9, 2018 at 9:49 AM, Joseph Salisbury
wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
I don't think so; how we're using/clearing/stopping bcache has changed.
I can reproduce this on
** Tags added: uosci
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1720378
Title:
Two processes can bind to the same port
Status in linux package in Ubuntu:
Confirmed
Bug descriptio
Public bug reported:
1.$ lsb_release -rd
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10
2. $ apt-cache policy linux-image-virtual
linux-image-virtual:
Installed: 4.13.0.11.12
Candidate: 4.13.0.11.12
Version table:
*** 4.13.0.11.12 500
500 http://a
** Attachment added: "kernel version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722311/+attachment/4965975/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
** Attachment added: "lspci-vnvn log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722311/+attachment/4965976/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
1.
$ lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04
2.
$ apt-cache policy zfsutils-linux
zfsutils-linux:
Installed: 0.6.5.6-0ubuntu18
Candidate: 0.6.5.6-0ubuntu18
Version table:
*** 0.6.5.6-0ubuntu18 500
500 http://archive.ubuntu.com/u
This thread shows up with that xsave warn:
https://www.virtualbox.org/pipermail/vbox-dev/2017-May/014466.html
Which suggests adding 'noxsave' to the kernel command line as a
workaround.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
On Tue, Oct 10, 2017 at 2:30 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
Around, September this year is when we started noticing th
On Tue, Dec 12, 2017 at 5:52 AM, Dimitri John Ledkov wrote:
> Once the kernel is fixed, are there any changes that are required to
> systemd/udev?
>
No changes needed.
>
> ** Changed in: systemd (Ubuntu Bionic)
>Status: New => Incomplete
>
> --
> You received this bug notification beca
Public bug reported:
[ 20.935396] BUG: unable to handle kernel NULL pointer dereference at
0b84
[ 20.936130] IP: _raw_spin_lock_irqsave+0x22/0x40
[ 20.936540] PGD 0
[ 20.936540] P4D 0
[ 20.936725]
[ 20.937117] Oops: 0002 [#1] SMP
[ 20.937570] Modules linked in: bcache
I just thought I would add that I too am affect by this on my system:
SYNA3602 device on a YEPO 737A Laptop - Linux Mint 18.3 Cinnamon respun,
as OP describes. The touchpad doesn't work live, and has never worked
after install.
I'm currently on 4.15 RC6 which was respun into the install ISO via t
@bbaker6212/Brad, weirdly enough it does work after a suspend/wake but
will cease working after any sort of interaction with the touchpad
settings including on/off.
modprobe commands have no effect.
Requested Info:
theyield@Keyloggertop ~ $ uname -a
Linux Keyloggertop 4.15.0-041500rc6-generic #2
Adding some information obtained last night:
On my YEPO 737A I flashed both Lubuntu and Elementary images to test if
the suspend/wake "trick" would initialize the trackpad, and it did not.
Both flashes making use of 4.15rc6.
Attacking this problem via BIOS seems problematic, as so many brand
name
@Brad - As much as I dislike using "old" kernels, this is definitely
worth testing. I'll try as you've suggested tonight and report back
ASAP.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
That's fair enough. I'll be sure to try 4.14.3 as well as the newer .11
variant.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728244
Title:
Touchpad stops working after reboot on Apol
Alright so 4.14.4 and .11 actually resulted in worse behaviour from the
touch pad, and even some system wide instability. I'm back to 4.15-rc6
(Mint Cinnamon) and, although it will not initiate at boot, suspending
gets me full functionality including multi touch gestures - and it
doesn't randomly t
Public bug reported:
1. $ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
2. $ apt-cache policy linux-image-`uname -r`
linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
*** 4.13.0-16.19 500
500 http://nova.clouds.archiv
To recreate:
Add a second disk (any size will do) and split the disk into 4 equal
partitions. Then
make-bcache -C /dev/vdb1
make-bcache -B /dev/vdb2
make-bcache -B /dev/vdb3
make-bcache -B /dev/vdb4
Note, you can see the proper symlinks created at this time:
ls -al /dev/bcache/by-uuid/
Reboot
This fails on Xenial -> Artful. I've not yet tested Trusty, but I
suspect it's just a latent bug in the bcache driver.
I'll grab the upstream kernel and provide results.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
Mainline kernel does not help; it fails the same way and also has a bug
that's fixed in the Ubuntu kernel:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667078
Here's the details from the mainline test:
ubuntu@a-unsolar-melonie:~$ dpkg --list | grep linux-image
ii linux-image-4.13.0-16-
Affects OpenStack on ppc64el. Marking other bug as duplicate (it has
logs/attachments fyi).
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1716469
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Confirmed workaround for OpenStack Ocata on Xenial:
### Nova compute host [hwe-edge kernel via MAAS]
ubuntu@node-mawhile:~$ uname -a
Linux node-mawhile 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:18
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
### Nova guest [stock xenial ppc64el clou
** Tags added: arm64 uosci
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1695093
Title:
arm64: "unsupported RELA relocation: 275" loading certain modules
Status in linux package in Ubu
On Thu, Mar 2, 2017 at 4:56 AM, Stefan Bader
wrote:
> I created a modified patch and verified that
> - bcache base devices again are numbered 0,1,...
> - partioning a bcache device creates the expected bcacheXpY devices
> Will submit this change upstream (and for pre-stable zesty).
>
> ** Patch a
Public bug reported:
On 4.10 kernel, when creating bcache devices, each device kname is now
incremented by 16
/dev/bcache0
/dev/bcache16
/dev/bcache32
etc.
This was to support partitioning of bcache devices[1], however, This
also will limit the number of bcache devices and doesn't match how oth
On Fri, Feb 24, 2017 at 10:39 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> It doesn't look like that patch ever landed in mainline. Do you plan on
> responding to the upstream thread with your recommendation?
>
It's an untested change; I've not pushed anything upstream.
If tim
Public bug reported:
1. % lsb_release -rd
Description:Ubuntu 15.10
Release:15.10
2.
% apt-cache policy linux-image-generic
linux-image-generic:
Installed: (none)
Candidate: 4.2.0.30.33
Version table:
4.2.0.30.33 0
500 http://us.archive.ubuntu.com/ubuntu/ wily-upda
Public bug reported:
1. # cat /proc/version_signature
Ubuntu 4.4.0-16.32-generic 4.4.6
# no pci on s390x, but none-the-less
2. root@ubuntu:~# sudo lspci -vnvn
root@ubuntu:~#
# lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
# apt-cache policy lin
** Changed in: curtin
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1499869
Title:
maas wily deployment to HP Proliant m400 arm64 server cartridge fails
S
As the original impetus for this bug report: I cannot personally verify
that this solves the original problem
(https://answers.launchpad.net/launchpad/+question/285505) as it
manifests itself on the Launchpad build farm and I do not have necessary
hardware to reproduce this independently.
Latest a
Public bug reported:
Downgrade to 1.15 BIOS to install UBUNTU Mate
Mate installed successfully and working fine except linux kernel has no support
for my wifi hardware.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-16-generic 4.2.0-16.19
ProcVersionSignature: Ubuntu 4.2
Tested 3.19.0-49-generic #55~14.04.1hf1533043v20160201b1-Ubuntu on bare
metal.
Works like a charm. What a great effort by everyone involved. Thanks a
lot!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
I have the same issue. The work around with
"GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1" seems
to have solved the issue for now on my Acer E511 with Intel Pentium
N3540 CHIP. And the temp has not increased very much after recent hard
use.
--
You received this bug notificati
Oh sorry forgot to mention I am using Ubuntu 16.04. 64 bit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1575467
Title:
Ubuntu 16.04 consistently freezes up / hangs
Status in linux pa
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1575467
Title:
Ubuntu 16.04 consistently freezes up / hangs
Status
Oh sorry I clicked some thing wrong... I never said a fix was released
lol... how can I remove that part?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1575467
Title:
Ubuntu 16.04 consi
Thank you Andrew for the link. I am looking every where for other's that
might have the same problem or a fix more solid than messing with
cstates . Yes this is a big wide spread bug. I read about many with the
same Intel Pentium N354O that I have.
--
You received this bug notification because yo
Interesting that once my hangs were solved enough to use my machine the
thing now reboots on shut down. Windows 10 on other part of dual boot
works very well. How could Ubuntu release an LTS version knowing the
vast amounts of users that have this issue?. Or not even put out clear
warnings etc.
--
Good point Andrew I will find the bug affects me button and give it a
click. True what you mentioned and it must affect many people and
people will see our banter and get on board to complain, then we get
results. Thank you again Andrew.
--
You received this bug notification because you are a me
Here's an update.
The Xenial kernel doesn;t like the emulated POWER7 cpu that the command
line being used generates by default.
processor : 0
cpu : POWER7 (raw), altivec supported
clock : 1000.00MHz
revision: 2.3 (pvr 003f 0203)
timebase: 51200
I should also mention that the original command used will work if we
specify which cpu type to use:
qemu-system-ppc64 -m 256 \
-cpu POWER8 \
-display none -nographic \
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 \
-machine pseries \
-drive file=xenial-server-cl
As noted, Xenial kernel is not supporting POWER7 cpu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qem
401 - 500 of 696 matches
Mail list logo
