[Kernel-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

I think we know almost the entire story now. See LP: #1656391 The one piece still missing is what changed. Very clearly the armhf container tests passed for several months, and then stopped working. My best guess is that they switched from using privileged containers to unprivileged

[Kernel-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

LP: #1656391 And it's reproducible in an amd64 container run locally. So probably some change in the images or lxc. Maybe a new missing dependency? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

Re: [Kernel-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

If you run `dmsetup ls` as non-root on amd64, you get an error that's close: % dmsetup ls /dev/mapper/control: open failed: Permission denied Failure to communicate with kernel device-mapper driver. Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). Command

[Kernel-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

Found this older bug: https://bugs.launchpad.net/ubuntu/+source/devmapper/+bug/105623 -- 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/1655735 Title: Incompatible libdevmapper 1.02.136

Re: [Kernel-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

On Jan 11, 2017, at 08:10 PM, Joseph Salisbury wrote: >Does the error go away if you boot a Xenial test kernel on this machine >and re-run the test? That will tell us if it is a kernel regression. We're a bit hardware starved atm, but trying to test this. -- You received this bug notification

[Kernel-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

On Jan 11, 2017, at 06:30 PM, Brad Figg wrote: >If, due to the nature of the issue you have encountered, you are unable >to run this command, please add a comment stating that fact and change >the bug status to 'Confirmed'. This is probably a regression only on armhf, so the logs generated on

[Kernel-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

Removed unhelpful attachments and retagged to armhf. ** Also affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Also affects: multipath-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1655735] [NEW] Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

Public bug reported: There is a new Zesty regression on armhf, related to the autopkgtest for ubuntu-image. Here's a log of a recent run: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/u/ubuntu-

Re: [Kernel-packages] [Bug 1641976] Re: Kernel panics and boot problems in Zesty

On Nov 15, 2016, at 07:24 PM, Seth Forshee wrote: >There are a couple of things in kern.log.1 with 4.8.0-26, but if the >dates in the log can be trusted they're from about a week ago. One of >them looks like the same issue as in bug 1630774, and that one has a fix >in 4.8.0-28.30. That build is

[Kernel-packages] [Bug 1641976] Re: Kernel panics and boot problems in Zesty

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

[Kernel-packages] [Bug 1641976] Re: Kernel panics and boot problems in Zesty

Interestingly, kern.log is empty -- 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/1641976 Title: Kernel panics and boot problems in Zesty Status in linux package in Ubuntu: Confirmed

[Kernel-packages] [Bug 1641976] Re: Kernel panics and boot problems in Zesty

dmesg from a successful boot ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641976/+attachment/474/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1641976] Re: Kernel panics and boot problems in Zesty

FTR: OS X 10.11.6 fully updated Fusion 8.5.2 (4635224) -- 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/1641976 Title: Kernel panics and boot problems in Zesty Status in linux package

[Kernel-packages] [Bug 1641976] Re: Kernel panics and boot problems in Zesty

Okay, this is highly strange, and quite unpredictable. Because the boot console output in Fusion scrolled off and can't be captured (AFAICT), I don't have specifics, but there was definitely an oops and a kernel crash. At the end of the output I saw something like "recursive error fixed, reboot

[Kernel-packages] [Bug 1641976] Re: Kernel panics and boot problems in Zesty

4.8.0-27.29 from zesty-proposed does *not* fix the problem. -- 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/1641976 Title: Kernel panics and boot problems in Zesty Status in linux

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

This has returned for Zesty. LP: #1641976 -- 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/1627198 Title: 4.8.0 kernels do not complete boot process on VM Status in Linux: Unknown

[Kernel-packages] [Bug 1641976] [NEW] Kernel panics and boot problems in Zesty

Public bug reported: Back in Yakkety, I reported LP: #1627198 which described boot problems with the 4.8.0 kernel on a VMware Fusion guest of Yakkety. With a fresh install on Zesty, I'm seeing very similar boot problems. With linux-image-generic 4.8.0.26.35, the system booted, but will not

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

Confirmed that Yakkety main kernel boots and logs into the desktop. % uname -a Linux anarchist 4.8.0-040800rc1-generic #201609281024 SMP Wed Sep 28 14:26:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux % dpkg-query -W linux-image-generic linux-image-generic 4.8.0.19.28 Thanks! -- You received

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

Thanks for the extra details Seth. Can you say whether it's the second problem that was breaking the desktop coming up on login? IOW, I observed two problems. One was a freeze during the boot process, and the other was a freeze during the login process (although the latter wasn't a total

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

FWIW, I posted to the Fusion forums: https://communities.vmware.com/message/2623359#2623359 -- 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/1627198 Title: 4.8.0 kernels do not complete

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

On Sep 29, 2016, at 03:20 AM, Joseph Salisbury wrote: >I built the next test kernel, up to the following commit: >1eccfa090eaea22558570054bbdc147817e1df5e 201609282035 boots, does not give me a desktop, and I see the crash in the syslog. -- You received this bug notification because you are a

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

On Sep 28, 2016, at 11:06 PM, Joseph Salisbury wrote: >I built the next test kernel, up to the following commit: >97433ea4fda62349bfa42089455593cbcb57e06c 201609281855 boots and gives me a desktop. No crash in usercopy.c found in syslog. -- You received this bug notification because you are a

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

On Sep 28, 2016, at 02:39 PM, Joseph Salisbury wrote: >It looks like we'll have to perform a second bisect, but also reverting >commit 2deb4be2 between each step. Just to follow up, I was able to eventually gain a desktop with the rc1 kernel and the bad commit reverted. My current plan is to

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

On Sep 27, 2016, at 11:12 PM, Joseph Salisbury wrote: >I built a mainline kenel with commit >2deb4be28077638591fe5fc593b7f8aabc140f42 reverted. > >Can you test this kernel to see if it also has the new desktop issue? That one gets a little farther but ultimately doesn't give me a desktop either.

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

On Sep 27, 2016, at 09:15 PM, Joseph Salisbury wrote: >Can you see if this kernel resolves this bug? Almost! As mentioned in IRC, it boots but login doesn't give me a desktop. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

On Sep 27, 2016, at 08:28 PM, Joseph Salisbury wrote: >The bisect reported the following as the first bad commit: > >commit 2deb4be28077638591fe5fc593b7f8aabc140f42 >Author: Andy Lutomirski >Date: Thu Jul 14 13:22:55 2016 -0700 > >x86/dumpstack: When OOPSing, rewind the

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

On Sep 27, 2016, at 03:32 PM, Joseph Salisbury wrote: >I built the next test kernel, up to the following commit: >0f657262d5f99ad86b9a63fb5dcd29036c2ed916 Thanks. 201609271113 does *not* boot. -- You received this bug notification because you are a member of Kernel Packages, which is

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

On Sep 26, 2016, at 11:36 PM, Joseph Salisbury wrote: >I built the next test kernel, up to the following commit: >5048c2af078d5976895d521262a8802ea791f3b0 #201609261917 boots! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

On Sep 26, 2016, at 10:52 PM, Joseph Salisbury wrote: >I built the next test kernel, up to the following commit: >52770c37db2c0ee5585dae2de3d19c8453f1e8dc This one boots! linux-image-4.7.0-040700-generic_4.7.0-040700.201609261819_amd64.deb -- You received this bug notification because you are

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

4.8 rc1 does not boot -- 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/1627198 Title: 4.8.0 kernels do not complete boot process on VM Status in linux package in Ubuntu: Confirmed

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

On Sep 26, 2016, at 06:18 PM, Joseph Salisbury wrote: >v4.5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ >v4.6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ >v4.7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/ All of these kernels (amd64, generic) boot

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

On Sep 26, 2016, at 12:48 PM, Leann Ogasawara wrote: >Could you re-test with the 4.8.0-17.19 kernel we have in ppa:canonical- >kernel-team/unstable Unfortunately this kernel also fails to completely boot. The last things I see in the console are [ OK ] Started Login Service. [ 36.445144]

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

Unfortunately, I cannot run this command on the system in question since booting with the defective kernel never gives me a prompt or an ssh login. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

** Summary changed: - 4.4.8 kernels do not complete boot process on VM + 4.8.0 kernels do not complete boot process on VM -- 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/1627198 Title:

[Kernel-packages] [Bug 1627198] [NEW] 4.4.8 kernels do not complete boot process on VM

Public bug reported: On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare Fusion 8.5 system, none of the 4.8.0 kernels complete the boot process. I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-proposed. Currently I am seeing the last message in my console at boot up as:

Re: [Kernel-packages] [Bug 1289410] Re: Xorg freeze

On Mar 11, 2014, at 10:15 PM, Joseph Salisbury wrote: This issue may have been introduced by the 3.13.6 stable update. Can you test the following kernel and see if it also exhibits the bug: I'm now on 3.13.0-17 and didn't notice the freeze on login after reboot to this kernel. I'll try a few

[Kernel-packages] [Bug 1289410] Re: Xorg freeze

3.13.0-17 seems to be freeze-free, so I'll close this bug for now. ** 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/1289410

Re: [Kernel-packages] [Bug 1157914] Re: time never catches up to reality after VM sleep

On Mar 12, 2014, at 07:31 AM, Neil Wilson wrote: It would be as well to try it out - particularly as the package has been updated recently. Indeed. I installed it, timesync is enabled, removed ntp, and indeed after about a 20m suspend, once resumed time syncs up again. Since I've not noticed

Re: [Kernel-packages] [Bug 1157914] Re: time never catches up to reality after VM sleep

On Mar 11, 2014, at 07:56 PM, Serge Hallyn wrote: Is it safe to assume that other VMs - other Ubuntu releases, or other distros, or windows, do not have this behavior? I haven't tried other guest OSes. I'll give Debian and Windows 7 a try. -- You received this bug notification because you are

[Kernel-packages] [Bug 1289410] [NEW] Xorg freeze

Public bug reported: This may be a kernel bug, and I'll add a bug task for that. % uname -a Linux anarchist 3.13.0-15-generic #35-Ubuntu SMP Mon Mar 3 15:54:59 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux With this kernel, I can log in just fine. With -16 however, after I type my password, the

[Kernel-packages] [Bug 1289410] Re: Xorg freeze

% dpkg-query -W linux-image-generic linux-image-generic 3.13.0.16.20 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1289410 Title: Xorg freeze Status in “linux-meta” package

[Kernel-packages] [Bug 1253826] [NEW] package linux-image-3.12.0-3-generic 3.12.0-3.9 failed to install/upgrade: trying to overwrite '/lib/modules/3.12.0-3-generic/kernel/net/openvswitch/openvswitch.k

*** This bug is a duplicate of bug 1253498 *** https://bugs.launchpad.net/bugs/1253498 Public bug reported: apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-3-generic 3.12.0-3.9 ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0 Uname:

[Kernel-packages] [Bug 1226025] [NEW] possible missing firmware

Public bug reported: After today's apt-get dist-upgrade: Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.11.0-7-generic W: Possible missing firmware /lib/firmware/radeon/KAVERI_sdma.bin for module radeon W: Possible missing firmware

[Kernel-packages] [Bug 1226025] Re: possible missing firmware

*** This bug is a duplicate of bug 1218691 *** https://bugs.launchpad.net/bugs/1218691 Rebooted. No ill effects that I can see. -- 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/1226025

[Kernel-packages] [Bug 1223408] Re: Greeter does not respond to keyboard or mouse

I think this one can be closed. % uname -a Linux limelight 3.11.0-7-generic #13-Ubuntu SMP Tue Sep 10 20:55:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Everything works just fine with this kernel on this native desktop machine. -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1223352] Re: Tiny fonts, bad screen resolution with 3.0.11-6

I think this one can be closed actually. With today's kernel update, everything seems back to normal. However, if you still want me to test some kernels for diagnostic purposes, just let me know. % uname -a Linux anarchist 3.11.0-7-generic #13-Ubuntu SMP Tue Sep 10 20:55:38 UTC 2013 x86_64

[Kernel-packages] [Bug 1223352] [NEW] Several regressions with 3.0.11-6

Public bug reported: Two different problems on two different machines. Virtual machine running in VMware Fusion 5: After today's kernel upgrade, all fonts and windows are too small, from the greeter through login and desktop. Rebooting to 3.0.11-5 fixes the problem. And I've seen this before,

[Kernel-packages] [Bug 1223352] Re: Several regressions with 3.0.11-6

The Fusion VM is running this kernel successfully. % uname -a Linux anarchist 3.11.0-5-generic #11-Ubuntu SMP Fri Sep 6 19:01:31 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux I'll open a separate bug for the greeter issue. Thanks! ** Summary changed: - Several regressions with 3.0.11-6 + Tiny

Re: [Kernel-packages] [Bug 1223352] Re: Tiny fonts, bad screen resolution with 3.0.11-6

On Sep 10, 2013, at 04:23 PM, Joseph Salisbury wrote: I started a bisect between 3.11.0-5.11 and 3.11.0-6.12. The bisect will require the testing of about 4 test kernels. I built the first kernel, which is up to commit: 264eca017cbbb23dd39a60697fff0bb019c31e2c The test kernel can be downloaded

[Kernel-packages] [Bug 1223408] [NEW] Greeter does not respond to keyboard or mouse

Public bug reported: This is split off from LP: #1223352 which originally described two different regressions I was seeing with 3.0.11-6. I've made that bug about the Fusion VM tiny fonts issue. This one is about the native install greeter problem. Specifically, when booting into 3.0.11-6, the