If you're using zfs-auto-snapshot, you can tell it to ignore bpool by
setting the com.sun:auto-snapshot property to false on the bpool
dataset:
# zfs set com.sun:auto-snapshot=false bpool
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zf
affects 6.2.0-1011-aws -> 6.2.0-1016-aws, 6.2.0-1011-azure ->
6.2.0-1016-azure kernels, did not affect 5.19 and prior kernels in
22.04.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu.
https://bugs.launchpad
This is also a problem for me using beelink s12 pro ubuntu 23.10 with
ax201 intel however adding the file in manually didn't fix the problem,
still detects the ax101 and can't connect to wifi or use bluetooth. The
error message does go away though
--
You received this bug notification because you
After over a week crash-free after disabling hardware video decoding, I
started getting the same crashes again today, despite not using any
hardware video decoding anywhere that I can tell. So now I'm stumped.
--
You received this bug notification because you are a member of Kernel
Packages, whi
I have been using the [Intel iwlwifi] network more intensely than I have
in a couple weeks today, so that's probably the cause.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs
A few days after reporting, I noticed that VLC media player was
terminating its process whenever I would seek ahead in a video. I found
a workaround by disabling hardware video acceleration (VA API). I had
been watching a lot of videos in Chrome when the system freezes in this
bug were happening.
Public bug reported:
System consistently freezes requiring hard reset every few hours. Syslog
gives this message at the time of the crash:
UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-d7iZ5S/linux-
hwe-6.2-6.2.0/drivers/net/wireless/intel/iwlwifi/queue/tx.c:1556:39
ProblemType: Bug
D
Public bug reported:
Model Name: MVP-6200
scope:
## Dumping the devices information to
/var/tmp/checkbox-ng/sessions/session_title-2023-09-05T06.56.19.session/session-share/warm_reboot_cycle24...
Gathering information about PCI devices (lspci)...
Gathering information about WiFi connections (iw
Warm boot system configuration test 24
** Attachment added: "submission_2023-09-07T00.51.23.751999.html"
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2034646/+attachment/5698123/+files/submission_2023-09-07T00.51.23.751999.html
--
You received this bug notification because
Public bug reported:
Model Name: MVP-6200
suspend/1_xrandr_screens_after_suspend.tar.gz_auto
** Affects: linux-intel-iotg (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "submission_2023-09-05T06.08.46.393631.html"
https://bugs.launchpad.net/bugs/2034645/+atta
Public bug reported:
I literally have no idea why it generation this error. My computer just
have been idle for quite some time then when I logged in I got an
instruction to send this error
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-32-generic 6.2.0-32.32
ProcVers
I just got the kernel update this morning:
ryan@dell-xps-8700 [~]$ uname -a
Linux dell-xps-8700 5.19.0-42-generic #43~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Fri Apr 21 16:51:08 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
I now have HDMI audio working again. A great big Thank You to all the
developers and
Problem still exists for me after updating to
Linux dell-xps-8700 5.19.0-41-generic #42~22.04.1-Ubuntu SMP
PREEMPT_DYNAMIC Tue Apr 18 17:40:00 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
(Ubuntu 22.04.2 LTS)
--
You received this bug notification because you are a member of Kernel
Packages, which is su
I have an AMD/ATI R9 270 and I am also affected. Attached is my full
output from "lspci -"
$ uname -a
Linux dell-xps-8700 5.19.0-35-generic #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Fri Feb 17 15:17:25 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
** Attachment added: "Output from lspci"
https://b
Hi Dann,
Thanks for the comments.
VM has 4G, bumping the craskkernel size 256 still fails, but moving up
to 512M allows this to work, but the equivalent kernel in jammy works
with 192M...
Thoughts?
And you're quite right, once the dump works, I see bug 1970672
[3.684815] kdump-tools[487]:
Testing with jammy-server image (which uses 5.15 kernel) it crashes
fine.
The general steps are:
1) boot VM with server image
2) apt install kdump-tools (enable kexec, enable kdump)
3) reboot, check crashdump param is set
4) kdump-config show (says ok to dump)
5) echo c | sudo tee /proc/sysrq-tr
Serial console output of VM kexec panic after triggering crashdump on
5.15 hwe kernel.
** Attachment added: "serial console log of 5.15 kxec panic during crash dump"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.15/+bug/2000257/+attachment/5637077/+files/ubuntu-focal-hwe-20.04-cra
Public bug reported:
1)
$ lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04
2) ubuntu@ubuntu:~$ apt-cache policy makedumpfile
makedumpfile:
Installed: 1:1.6.7-1ubuntu2.4
Candidate: 1:1.6.7-1ubuntu2.4
Version table:
*** 1:1.6.7-1ubuntu2.4 500
500 http://archi
I am also having the same issue as Andrea/Camille above. I have tried
the work arounds above but have not had any luck. I see there hasn't
been any updates to this so I wanted to say that I am having this issue
as well.
--
You received this bug notification because you are a member of Kernel
Pack
I am also impacted by this. I had already logged a bug against
virtualbox:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1988460
Although, I can't really say if the problem is actually with the new
kernel or with virtualbox.
--
You received this bug notification because you are a me
Same system, same symptoms.
--
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/1959728
Title:
trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume
Status in linux package i
** Changed in: linux-raspi2 (Ubuntu)
Assignee: Ryan Finnie (fo0bar) => (unassigned)
--
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/1652270
Title:
Could not boot into R
* dann frazier <1918...@bugs.launchpad.net> [2021-03-19 12:16]:
> On Fri, Mar 19, 2021 at 10:01 AM Ryan Harper <1918...@bugs.launchpad.net>
> wrote:
> >
> > * dann frazier <1918...@bugs.launchpad.net> [2021-03-18 16:30]:
> > > On Th
* dann frazier <1918...@bugs.launchpad.net> [2021-03-18 16:30]:
> On Thu, Mar 18, 2021 at 12:25 PM Ryan Harper <1918...@bugs.launchpad.net>
> wrote:
> >
> > * dann frazier <1918...@bugs.launchpad.net> [2021-03-18 12:11]:
> > > On Th
* dann frazier <1918...@bugs.launchpad.net> [2021-03-18 12:11]:
> On Thu, Mar 18, 2021 at 10:25 AM Ryan Harper <1918...@bugs.launchpad.net>
> wrote:
> >
> > * dann frazier <1918...@bugs.launchpad.net> [2021-03-17 20:30]:
> > > On Tu
* dann frazier <1918...@bugs.launchpad.net> [2021-03-17 20:30]:
> On Tue, Mar 16, 2021 at 10:05 AM Ryan Harper <1918...@bugs.launchpad.net>
> wrote:
> >
> > Hi Dan,
> >
> > Could you summarize the problem with flash-kernel and this system?
>
>
* dann frazier <1918...@bugs.launchpad.net> [2021-03-17 20:40]:
> On Wed, Mar 17, 2021 at 4:56 PM Ryan Harper <1918...@bugs.launchpad.net>
> wrote:
> >
> > I still don't understand:
> >
> > 1) why does which not find flash-kernel if it's prese
e paths to binaries; we install
Ubuntu and Centos, and possibly other distros which may not have the
same path to this tools so I would like to understand what's not working
to understand why we're hardcoding paths to binaries for dpkg-divert.
Thanks,
Ryan
Ryan
--
You received this bug notifica
talled as expected.
>
> Once curtin has been updated with a fix like this, and MAAS has been
> refreshed to include it, I think we should then be able to remove flash-
> kernel from the arm64 cloud images.
What's the criteria for determining if a particular arm instance
requi
Still happens in kernel 5.8.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1715861
Title:
r592 & r852 IRQ: DMA errors cause excessive log file entries
Status in linux package in Ubuntu
** 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
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
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://
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
@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
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:
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
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_
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
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
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
Cancel that. As expected, issue still present.
--
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/1861936
Title:
Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
net
I *may* be jumping the gun here, but having just installed
5.4.0-1019-raspi this morning, things appear to be good!
Did an upgrade ~ 30 minutes ago (usually i find the issue is triggered
after around 10 minutes or so).
Will update if/when it crashes.
--
You received this bug notification be
wow ok. i actually have a a acer aspire 5 with a 4500u
i couldnt get ubuntu to boot on it so i abandoned it and re installed
windows.
is there a 20.10 iso available for download?
On Mon, Sep 28, 2020 at 4:01 PM Richard Elkins <1891...@bugs.launchpad.net>
wrote:
> This could very well be an issue
I am unable to collect logs because the system fails to boot.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895550
T
Sending to the kernel team but not sure it belongs with them.
** Package changed: ubuntu => linux (Ubuntu)
--
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 r
Turns out it's unrelated to bcache; it is trivially reproducible:
lxc launch ubuntu-daily:groovy g1 --vm
lxc exec g1 bash
fallocate -l 1024M /swap.img
mkswap /swap.img
swapon --verbose /swap.img
cat /proc/swaps
On the 5.4 kernel that groovy had a few weeks back this works, on daily
(5.8) this fa
** Summary changed:
- fallocate swapfile has holes on 5.8 ext4 over bcache
+ fallocate swapfile has holes on 5.8 ext4
--
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/1894910
Title:
fallo
Public bug reported:
1) Groovy
2)
root@ubuntu:/home/ubuntu# apt-cache policy linux-image-generic
linux-image-generic:
Installed: 5.8.0.18.22
Candidate: 5.8.0.18.22
Version table:
*** 5.8.0.18.22 500
500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib
were you able to figure it out?
should i post another log?
On Mon, Aug 17, 2020 at 12:46 AM Ryan D wrote:
>
> Thank you. I dont know how i did not see that before
>
> On Mon, Aug 17, 2020 at 12:25 AM Daniel van Vugt <
> 1891...@bugs.launchpad.net> wrote:
>
>>
Thank you. I dont know how i did not see that before
On Mon, Aug 17, 2020 at 12:25 AM Daniel van Vugt <1891...@bugs.launchpad.net>
wrote:
> Also, please don't use Alt+F2. This command needs to be run in the
> Terminal app:
>
> journalctl -b-1 > prevboot.txt
>
> But only using the steps from com
need a little more help than than. Im new to Ubuntu. I dont know how to
navigate
On Sun, Aug 16, 2020 at 11:55 PM Daniel van Vugt <1891...@bugs.launchpad.net>
wrote:
> The file should be created in the directory you ran the command so look
> there:
>
> journalctl -b-1 > prevboot.txt
> ls *.tx
i am not recieving a text file when i run the command
what am i doing wrong?
alt+f2 to bring up command
i have rebooted, suspended, reproduced flicker, rebooted then entered
verbatim. No text file appears?
On Sun, Aug 16, 2020 at 10:40 PM Daniel van Vugt <1891...@bugs.launchpad.net>
wrote:
> Ple
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
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
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
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.
-
Thinkpad T460 with Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz
Recently went Ubuntu 16.04 -> 18.04.
Using intel_pstate in default configuration.
HWE low latency kernel:
Linux machine 5.3.0-62-lowlatency #56~18.04.1-Ubuntu SMP PREEMPT Wed Jun
24 16:57:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
For
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!
Works on focal, thank you
--
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/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Status in Linux:
Confirmed
Statu
@ddstreet
I'm not sure where upstream is going just yet. For Ubuntu; I think
1) Adjusting the bcache-tools patch to use the full path to bcache-
super-show should change;
2) If we fix (1) then I think we can drop the systemd patch from a bug
fixing perspective; on the openSUSE image I did testi
On Tue, Jun 30, 2020 at 6:35 AM Balint Reczey <1861...@bugs.launchpad.net>
wrote:
> @raharper I've forwarded the systemd fix for you with minimal tidying of
> the commit message https://github.com/systemd/systemd/pull/16317
Thanks!
>
> --
> You received this bug notification because you are su
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
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
Sure, done.
--
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/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Status in Linux:
Unknown
Status in linux packa
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1867916
Title:
Regres
** 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 Kernel
Packages, which is subscribed to linux in Ubunt
** 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 Kernel
Packages, which is subscribed to linux in Ubunt
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1867916
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
** 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/1880943
Title:
[focal] disk I/O performance regression
Status in linux package in Ubuntu:
Confirmed
Bug descriptio
systemd debdiff with a fix to skip creating /dev/disk/by-uuid for bcache
backing, caching devices.
** Patch added: "lp1861941-skip-bcache-links.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+attachment/5375730/+files/lp1861941-skip-bcache-links.debdiff
--
You r
debdiff of the changes
** Attachment added: "bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375722/+files/bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1
--
You received this bug notification because you are a m
Updated test to be a bit more resilient.
** Attachment added: "test-bcache-byuuid-links-fixed.sh"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375723/+files/test-bcache-byuuid-links-fixed.sh
--
You received this bug notification because you are a member of
Tarball of a source package with a fix for this issue:
bcache-tools_1.0.8.orig.tar.gz
bcache-tools_1.0.8-4ubuntu1_amd64.build
bcache-tools_1.0.8-4ubuntu1_amd64.buildinfo
bcache-tools_1.0.8-4ubuntu1_amd64.changes
bcache-tools_1.0.8-4ubuntu1_amd64.deb
bcache-tools_1.0.8-4ubuntu1.debian.tar.xz
bcache
OK.
I've reviewed the kernel code, and there are no unexpected changes w.r.t
the CACHED_UUID change event. So I don't think we will need any kernel
changes which is good.
With the small change to the 60-persistent-storage.rules to not attempt
to create a /dev/disk/by-uuid symlink for the backing
Digging deeper and walking through this in a focal vm, I'm seeing some
strange things.
Starting with a clean disk, and just creating the backing device like
so:
make-bcache -B /dev/vdb
We see /dev/bcache0 get created with vdb as the backing device. Now,
after this, I see:
/dev/bcache/by-uuid/
@Balint
I do not thing the fix you're released is correct, can you upload a new
version without the scripts?
Also, we should fix make-bcache -B to ensure that cset.uuid is not
initialized; that may be why the kernel thinks it should emit the
CACHED_UUID if the suerpblock of the device has a cset.
That doesn't explain why they show up sometimes, but not all of
the time.
There are 3 devices in play here.
* The backing device, let's say /dev/vda; this is where we want
to store the data.
* The caching device, let's say /dev/vdb; this holds the cache.
* The bcache device; this only appears
I guess I don't understand why we see this in focal. The two events in
Colin's trace always happen on any Ubuntu kernel. We should see if we
can get another udev trace on bionic that captures both CHANGE events,
one will be from the bcache driver itself, and one is from the block
layer. THe orde
-speed USB device number 8 using xhci_hcd
May 19 09:16:14 RyanFriedmanLinux kernel: [ 8569.229353] acpi LNXPOWER:05:
Turning OFF
May 19 09:16:14 RyanFriedmanLinux kernel: [ 8569.229471] acpi LNXPOWER:04:
Turning OFF
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15
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 Kernel
Packages, which is subscribed to l
It doesn’t work for me either. I downloaded latest image and booted live. It
didn’t work there either.
I’m not sure why it was marked fix when it never worked for me. I was the one
who first reported the bug.
Sent from my iPhone
> On Apr 24, 2020, at 1:21 AM, You-Sheng Yang <1871...@bugs.laun
Following up my question; we should see both events in all kernels.
The first event is when the /dev/bcache0 is joined with a cache device,
and emitts the CACHED_UUID value in the uevent; the UUID is the *backing
device bcache metadata UUID* it is not related to the content contained
within the b
So, this looks like the bug to me:
Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0:
/usr/lib/udev/rules.d/60-persistent-storage.rules:112 LINK
'disk/by-uuid/30b28bee-6a1e-423d-9d53-32c78ba5454a'
Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: Updating old name,
'/dev/bcache
Do we have any more information on why we now get two events in Focal?
--
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/1861941
Title:
bcache by-uuid links disappear after mounting bcache0
@Paolo, test kernel didn't work for me. I had to reinstall official
Realtek driver again like i did in #3.
--
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/1871182
Title:
[RTL810xE] No eth
Ethernet stopped working again after update today.
@vicamo here are the results for would you suggested in #8. It does appear that
realtek.ko was included automatically for me but still not working.
finisdiem@finisdiem-HP-Pavilion-g6-Notebook-PC:~$ sudo modprobe -r realtek
[sudo] password for fin
Yes, adding realtek to /etc/modules makes the ethernet work. I'm not
sure if thats the actual bug.
$ systemd-analyze
Startup finished in 9.434s (firmware) + 4.866s (loader) + 3min 22.039s (kernel)
+ 56.143s (userspace) = 4min 32.483s
graphical.target reached after 55.830s in userspace
System lo
Still having issues even after update to 5.4.0-24 today. found a work
around by downloading latest driver from realtek here
https://www.realtek.com/en/component/zoo/category/network-interface-
controllers-10-100m-fast-ethernet-pci-express-software. followed
directions from here with latest drivers
> This is in an integration lab so these hosts (including maas) are stopped,
> MAAS is reinstalled, and the systems are redeployed without any release
> or option to wipe during a MAAS release.
> Then MAAS deploys Bionic on these hosts thinking they are completely new
> systems but in reality they
>
> Ryan,
> We believe this is a bug as we expect curtin to wipe the disks. In this
> case it's failing to wipe the disks and occasionally that causes issues
> with our automation deploying ceph on those disks.
I'm still confused about what the actual error you b
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
During a clear-holders operation we do not need to catch any failure;
we're attempting to destroy the devices in question. The destruction of
a device is explicitly requested in the config via a wipe: value[1]
present on one or more devices that are members of the LV.
1. https://curtin.readthedo
I'm on Focal desktop, running kvm like so
qemu-system-x86_64 -smp 2 -m 1024 --enable-kvm \
-drive id=disk0,if=none,format=qcow2,file=bionic-bcache-links.qcow2 \
-device virtio-blk-pci,drive=disk0,bootindex=0 \
-drive id=disk1,if=none,format=raw,file=bcache1.img \
-device virtio-blk-pci,dri
It appears that it's always been a touch racy. Curtin does not create
bcaches like the script does (make-bcache --wipe-bcache -C /dev/sdc -B
/dev/sdb), rather we make the cache-dev and backing dev separately, and
then attach them by echoing the cacheset uuid into the bcache device
attach sysfs fil
Requested output on bionic release image (4.15-20)
** Attachment added: "bcache-release-4.15-20.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861941/+attachment/5350481/+files/bcache-release-4.15-20.txt
--
You received this bug notification because you are a member o
Requested data from a daily cloud image with 4.15-76
** Attachment added: "bcache-daily-4.15-76.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861941/+attachment/5350483/+files/bcache-daily-4.15-76.txt
--
You received this bug notification because you are a member of
1 - 100 of 689 matches
Mail list logo
