[Kernel-packages] [Bug 1287401] [NEW] please include virtio-scsi in linux-virtual

Public bug reported: please include virtio-scsi in linux-virtual. It's currently packaged in linux-image-extras. Including it in the base kernel package would allow the cloud image to make use of the virtio-scsi device which includes TRIM/DISCARD support for minimizing ever growing virtual disk

[Kernel-packages] [Bug 1392501] [NEW] intel 915 graphics fails to detect monitor resolution

Public bug reported: What should happen: Upon login, an external monitor connected via displayport to the laptop should be detected correctly and the screen size should be set to the correct resolution. Further, if the display sleeps, it should restore back to the previous state before powering

Re: [Kernel-packages] [Bug 1392501] Re: intel 915 graphics fails to detect monitor resolution

On Thu, Nov 13, 2014 at 4:08 PM, Joseph Salisbury joseph.salisb...@canonical.com wrote: Did this issue start happening after an update/upgrade? Was there a I'm not 100% sure. It's possible that 13.10 (original install on this x1 carbon gen1) didn't have this behavior. kernel version where

[Kernel-packages] [Bug 1392501] Re: intel 915 graphics fails to detect monitor resolution

upstream kernel didn't help: [ 33.822175] [drm] vendor descriptor length:1b data:1b 5f 01 00 19 05 00 01 03 00 04 [ 33.988042] udl 1-2.3.1:1.0: fb1: udldrmfb frame buffer device [ 33.988045] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 33.988046] [drm] No driver support

[Kernel-packages] [Bug 1392501] Re: intel 915 graphics fails to detect monitor resolution

Here's what I did: After installing all of the kernels, I rebooted and tried each one. Upon booting into desktop, login, document state after login, dumped dmesg | grep drm into versioned file, unplugged laptop power, ctrl-alt-l to lock display, wait 5 seconds for all displays to sleep, press key

[Kernel-packages] [Bug 1392501] Re: intel 915 graphics fails to detect monitor resolution

** Attachment added: 3.13.0-031300-generic-dmesg-drm.out https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392501/+attachment/4260690/+files/3.13.0-031300-generic-dmesg-drm.out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux

[Kernel-packages] [Bug 1392501] Re: intel 915 graphics fails to detect monitor resolution

** Attachment added: 3.18.0-994-generic-dmesg-drm.out https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392501/+attachment/4260689/+files/3.18.0-994-generic-dmesg-drm.out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1392501] Re: intel 915 graphics fails to detect monitor resolution

** Attachment added: 3.11.0-031100-generic-dmesg-drm.out https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392501/+attachment/4260691/+files/3.11.0-031100-generic-dmesg-drm.out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux

[Kernel-packages] [Bug 1392501] Re: intel 915 graphics fails to detect monitor resolution

Is there any reason to believe that this is related to bios version? Any changelog from Lenovo that indicates they've fixed anything related to display port? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1392501] Re: intel 915 graphics fails to detect monitor resolution

I've examined all of the changelogs for the x1 Carbon gen1 http://support.lenovo.com/us/en/downloads/ds030684 and there is nothing in there to indicate there is any fix for anything graphic related. I don't feel that the bios out-dated tag is relevant at this point. -- You received this bug

[Kernel-packages] [Bug 1413540] Re: issues with KSM enabled for nested KVM VMs

I think you'll find that nested kvm and ksm will be a worst-case scenario w.r.t memory swap-out. KSM actively scans the hosts memory for pages it can unmap , which means when a guest (level 1) or nested guest (level 2) needs to write to that memory, then you incur a page table walk (Guest virtual

[Kernel-packages] [Bug 1413540] Re: issues with KSM enabled for nested KVM VMs

Any information about the physical host running the L1 guest? -- 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/1413540 Title: issues with KSM enabled for nested KVM VMs Status in linux

[Kernel-packages] [Bug 1445273] [NEW] trusty amd64 kernel with bcache module panics on unregister

Public bug reported: We have a system with 3 block devices (SATA) split into 2 partitions each, and create RAID0 md0 (sda1, sdb1, sdc1), and RAID0 md1 (sda2, sdb2, sdc2). We then create a bcache device on an SSD and set it to writeback mode, (/dev/bcache0). When we attempt to

[Kernel-packages] [Bug 1445273] Re: trusty amd64 kernel with bcache module panics on unregister

A quick test shows stopping and then unregistering helps. I've only tested that a few times. That said, clearly if we do things in the wrong order, the module should refuse instead of panic =). -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1377130] Re: Crash at creation of bcache if caching size backing size

I can't reproduce this on vivid w.r.t the hang. For the release all the devs used in bcache setup; it's certainly awkward. Fundamentally, there's no path in sysfs that contains both the cache devs and the backing devs. And AFAIK, there is no way to know that the bcacheX devices is being cached

[Kernel-packages] [Bug 1377142] Re: Bcache doesn't allow full unregistering without rebooting

While the interface is annoying, it *is* possible to have bcache let go of both backing store and cache devices via the sysfs interfaces. ** Changed in: bcache-tools (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which

[Kernel-packages] [Bug 1515687] Re: Curtin booting after install failed on wily image with a kernel BUG at /build/linux-AxjFAn/linux-4.2.0/drivers/block/virtio_blk.c:172!

This does not affect curtin, rather it's a bug in dm_crypt, fixed in upstream linux. ** 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.

[Kernel-packages] [Bug 1592541] Re: trusty kernel with virtio-blk oops

Here's the qemu launch command used, in case that's useful. qemu-system-x86_64 -enable-kvm -device virtio-scsi-pci,id=virtio-scsi-xkvm -device virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -m 1024 -serial

[Kernel-packages] [Bug 1592541] [NEW] trusty kernel with virtio-blk oops

Public bug reported: The following oops was found in a Trusty Cloud-image when doing storage operations with software raid, lvm and various filesystems. [ 85.327298] general protection fault: [#1] SMP [ 85.327806] Modules linked in: bcache btrfs jfs xfs libcrc32c iscsi_tcp

Re: [Kernel-packages] [Bug 1592541] Re: trusty kernel with virtio-blk oops

Having posted, I see that this is actually a utopic kernel that oopsed (3.16.0-71-generic) However, the oops stack is still possible on trusty, the blk-merge code in 3.13 doesn't include the fix that appears in the vivid kernel. On Tue, Jun 14, 2016 at 2:56 PM, Ryan Harper <1

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

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:

[Kernel-packages] [Bug 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails

** 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

[Kernel-packages] [Bug 1552752] [NEW] kernel bug when mounting a qemu-nbd backed image

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/

[Kernel-packages] [Bug 1565029] [NEW] bcache doesn't register/recognize devices on s390x

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

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

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

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

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:

Re: [Kernel-packages] [Bug 1602299] Re: bcache is unstable on ppc64el

This looks relevant: https://www.redhat.com/archives/dm-devel/2016-June/msg00015.html On Tue, Jul 19, 2016 at 5:19 AM, Stefan Bader wrote: > While I have not found out where exactly things go wrong, I could > confirm that this is related to ppc64el builds using a

[Kernel-packages] [Bug 1602299] [NEW] bcache is unstable on ppc64el

Public bug reported: Stopping and unregistering bcache caches and backing devices results in losing the bcache superblock on devices rendering bcached devices corrupt or broken. 1. Ubuntu 4.4.0-28.47-generic 4.4.13 2. attaching lspci log 3. Description:Ubuntu 16.04 LTS Release:

[Kernel-packages] [Bug 1602299] Re: bcache is unstable on ppc64el

Here's my recreate: On Power8 system with Xenial, KVM enabled. 1. sudo apt-get install uvtool uvtool-libvirt 2. wget http://people.canonical.com/~rharper/bugs/lp_1602299/lp_1602299.tgz 3. tar xzvf lp_1602299.tgz 4. cd lp_1602299 5. uvt-simplestreams-libvirt sync --source

[Kernel-packages] [Bug 1602299] Re: bcache is unstable on ppc64el

** Attachment added: "lp_1602299.tgz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602299/+attachment/4699510/+files/lp_1602299.tgz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

Re: [Kernel-packages] [Bug 1667078] Re: bcache device numbers increase by 16

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

[Kernel-packages] [Bug 1667078] [NEW] bcache device numbers increase by 16

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

Re: [Kernel-packages] [Bug 1667078] Re: bcache device numbers increase by 16

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

[Kernel-packages] [Bug 1682456] Re: md devices may leave remnants in /sys/class/block after removal

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

[Kernel-packages] [Bug 1682456] [NEW] md devices may leave remnants in /sys/class/block after removal

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

[Kernel-packages] [Bug 1682456] Re: md devices may leave remnants in /sys/class/block after removal

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

[Kernel-packages] [Bug 1682456] Re: md devices may leave remnants in /sys/class/block after removal

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"

[Kernel-packages] [Bug 1682456] Re: md devices may leave remnants in /sys/class/block after removal

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

Re: [Kernel-packages] [Bug 1683919] Re: installation fails with trusty and hwe-t kernel

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

[Kernel-packages] [Bug 1683919] Re: installation fails with trusty and hwe-t kernel

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

[Kernel-packages] [Bug 1722311] Re: softlockups/rcu sched

** 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.

[Kernel-packages] [Bug 1722311] [NEW] softlockups/rcu sched

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

[Kernel-packages] [Bug 1722311] Re: softlockups/rcu sched

** 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.

[Kernel-packages] [Bug 1734490] Re: Graphics mode never switches from console mode on Artful kernel

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

[Kernel-packages] [Bug 1734490] [NEW] Graphics mode never switches from console mode on Artful kernel

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

[Kernel-packages] [Bug 1734490] Re: Graphics mode never switches from console mode on Artful kernel

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

[Kernel-packages] [Bug 1734490] Re: Graphics mode never switches from console mode on Artful kernel

[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

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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 <ryan.har...@canonical.com> wr

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

** 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:

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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, Ryan Harper

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

; ../../bcacheN On Thu, Nov 30, 2017 at 7:16 PM, Ryan Harper <ryan.har...@canonical.com> wrote: > 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\x2f0a27

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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

[Kernel-packages] [Bug 1737817] [NEW] artful bcache NULL pointer defererence

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:

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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/

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after 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.

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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 <ryan.har...

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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/~jsalisbury/lp1729145/ > > Can

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Thanks for doing the cleanup; Patch looks good and I approve. Signed-off-by: Ryan Harper <ryan.har...@canonical.com> 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 Sign

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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 <ryan.har...@canonical.com> wrote: > Here's the Zesty test; all looks good. > > ubuntu@ubuntu:~$ cat /etc/cloud/build.in

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Confirmed bionic works as expected. I suspect you can send that upstream with my SoB faster than I can. Definitely interested in seeing if they'll take something like that. On Thu, Dec 7, 2017 at 1:21 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Thanks for testing and the

Re: [Kernel-packages] [Bug 1722311] Re: softlockups/rcu sched

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

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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

[Kernel-packages] [Bug 1726818] Re: vagrant artful64 box filesystem too small

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

[Kernel-packages] [Bug 1729145] [NEW] /dev/bcache/by-uuid links not created after reboot

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

[Kernel-packages] [Bug 1772490] Re: bcache: register_bcache() error

ay 21 10:57:05 geodude kernel: [ 49.126408] bcache: register_bcache() error /dev/sda3: device already registered (emitting change event) These are not curtin or kernel errors but expected output. I looked at the qa link but I didn't find the install.log debug output. ** Changed in: curtin

[Kernel-packages] [Bug 1772490] Re: bcache: register_bcache() error

May 21 11:00:42 geodude cloud-init[1643]: curtin: Installation finished. >From the rsyslog, curtin finished the install without error. ** Changed in: curtin Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is

Re: [Kernel-packages] [Bug 1772490] Re: bcache: register_bcache() error

Thanks for the log. Curtin installed without error, I'll mark invalid. AFAICT, it booted fine and was instructed to power off. May 21 13:18:51 geodude cloud-init[1676]: Powering node off. May 21 13:18:51 geodude ec2: May 21 13:18:51 geodude ec2:

Re: [Kernel-packages] [Bug 1772490] Re: bcache: register_bcache() error

On Mon, May 21, 2018 at 3:59 PM, Andres Rodriguez wrote: > @Ryan, > > I'm marking this as incomplete for curtin provided that after further > debugging, I can see that the late command that's supposed to send the > "netboot_off" operation is not being sent. > > This could

Re: [Kernel-packages] [Bug 1772490] Re: 'Deploying' timed out after 40 minutes / Failedbcache: register_bcache() error

*** This bug is a duplicate of bug 1768893 *** https://bugs.launchpad.net/bugs/1768893 The bcache message is *NOT* a failure in the kernel; That message is emitted when a bcache device is reregistered, the kernel will emit the changed event to ensure that udev will create

[Kernel-packages] [Bug 1768777] [NEW] libnvpair1linux doc contents have busted symlinks

Public bug reported: % apt-cache policy libnvpair1linux libnvpair1linux: Installed: 0.7.5-1ubuntu15 Candidate: 0.7.5-1ubuntu15 Version table: *** 0.7.5-1ubuntu15 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status % lsb_release -rd

Re: [Kernel-packages] [Bug 1768777] Re: libnvpair1linux doc contents have busted symlinks

Yes; this was a an upgraded system. On Thu, May 3, 2018 at 5:28 PM, Colin Ian King <1768...@bugs.launchpad.net> wrote: > This seems to only occur with a Xenial -> Artful or Xenial -> Bionic > upgrades and not Artful -> Bionic. > > -- > You received this bug notification because you are subscribed

[Kernel-packages] [Bug 1760173] Re: zfs, zpool commands hangs for 10 seconds without a /dev/zfs

If they're going to modprobe and are waiting on udev, then I would like them to do something like udevadm settle --exit-if-exists=/dev/zfs That means they can exit early without paying the 10s by default value. -- You received this bug notification because you are a member of Kernel Packages,

Re: [Kernel-packages] [Bug 1760173] Re: zfs, zpool commands hangs for 10 seconds without a /dev/zfs

On Mon, Apr 30, 2018 at 12:14 PM, Colin Ian King <1760...@bugs.launchpad.net> wrote: > The code actually polls /dev/zfs until it appears. The issue here is > that it does not appear after 10 seconds, and then it gives up. Yes, you're right. Would it make sense to have zfsutils know it's running

[Kernel-packages] [Bug 1742560] [NEW] zfsutils-linux recommends dkms when it's not needed

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

Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

@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

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

We've just had a second occurrence of this, same kernel, but with Xenial. (Xenial HWE Edge kernel 4.15.0-29) with the same scenario, mkfs.ext4 a /dev/bcache0. I'll see if I can recreate by stressing things. -- You received this bug notification because you are a member of Kernel Packages,

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? We've had plenty of successful runs on this kernel. I suspect io load or something else may trigger this. We've only seen it once out of tens of not

[Kernel-packages] [Bug 1784665] [NEW] mkfs.ext4 over /dev/bcache0 hangs

Public bug reported: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description:Ubuntu Cosmic Cuttlefish (development branch) Release:18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

I can recreate on upstream: # uname -r; dmesg | tail -n 16 4.18.0-041800rc7-generic [ 967.657492] INFO: task bcache_allocato:14240 blocked for more than 120 seconds. [ 967.664138] Not tainted 4.18.0-041800rc7-generic #201807292230 [ 967.669641] "echo 0 >

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

** Attachment added: "bcache-basic-repro.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5170528/+files/bcache-basic-repro.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

I'll see if I can reproduce on the mainline kernel. -- 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/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu:

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

I think I've got one. It doesn't always hang the mkfs, but it does wedge bcache in a few ways. [ 484.322546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 484.326230] INFO: task bcache_allocato:32503 blocked for more than 120 seconds. 1) when it occurs, a

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

4.14 Final: OK 4.15-rc1:OK I started a further bisect: 4.15-rc9:FAIL 4.15-rc5:OK 4.15-rc7:FAIL 4.15-rc6:OK So, it appears something between rc6 (last known good) and rc7 (FAIL) -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

test kernel 4.15-rc1 up to abb62c46d4949d44979fa647740feff3f7538799 FAILED ** Attachment added: "kernel oops for 4.15-rc1 up to abb62c46d4949d44979fa647740feff3f7538799" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5175947/+files/rc1-bisect2-oops.txt -- You

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

test kernel 4.15-rc6 up to d8887f1c7289848e74c92bd4322789a9cd7de699 FAILED ** Attachment added: "kernel oops for 4.15-rc6-up-to-d8887f1c7289848e74c92bd4322789a9cd7de699" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5175379/+files/rc6-bisect1-oops.txt -- You

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

test kernel 4.15-rc6 up to d8887f1c7289848e74c92bd4322789a9cd7de699 FAILED Attaching oops. -- 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/1784665 Title: mkfs.ext4 over /dev/bcache0

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

4.10: Status: OK Comment: Survived 30 minute loop over recreating with no issues. 4.13: Status: OK Comment: Survived 30 minute loop over recreating with no issues. 4.15: Status: FAIL Comment: triggered within less than a minute of the loop. Kernel Trace: [ 122.500943] Oops:

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

PASS: Kernel 4.15-rc1 (bisect6) up to 87eba0716011e528f7841026f2cc65683219d0ad -- 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/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

FAILED: Kernel 4.15-rc1 up to bc631943faba6fc3f755748091ada31798fb7d50 Attached is the oops of the failure. ** Attachment added: "rc1-bisect7-oops.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5181823/+files/rc1-bisect7-oops.txt -- You received this bug

Re: [Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

It's always been a locking issue, so either misuse (or missing) locks in the bcache attach/detach path, or generic locking changes to block layer path I'd think. I'll see if I can find any hits on those oops tracebacks too On Tue, Aug 28, 2018 at 2:29 PM Ryan Harper wrote: > >

Re: [Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

https://patchwork.kernel.org/patch/10094201/ diff --git a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts index d4f80786e7c2..3890468678ce 100644 --- a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts +++

Re: [Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

https://www.spinics.net/lists/linux-bcache/msg04869.html https://www.spinics.net/lists/linux-bcache/msg05774.html On Tue, Aug 28, 2018 at 2:30 PM Ryan Harper wrote: > > It's always been a locking issue, so either misuse (or missing) locks > in the bcache attach/detach path, or generi

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

FAILED: Kernel 4.15-rc1 up to f48f66a962a54c3d26d688c3df5441c9d1ba8730 Attached is the oops of the failure. ** Attachment added: "rc1-bisect4-oops.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5181417/+files/rc1-bisect4-oops.txt -- You received this bug

  1   2   3   >