So after some discussion, it seems that what we have is not entirely
unreasonable.
There would/could be some gain (possbly on the order of 70-80M in
/lib/modules). That includes removal of wireless modules, graphics drivers,
sound, and some other misc drivers. I'll attach my revised list.
So
Public bug reported:
Oleg and I got changes into curtin to fix bug 1371634.
So that now we can boot into multipath iscsi devices on power.
It seems to go well enough with trusty+hwe-u, but when trying vivid, I am
seeing errors.
Boot was failing in one case
** Affects: linux (Ubuntu)
Import
Mike, Oleg, others.
I've opened bug 1462530 to address the errors I'm seeing like those Mike
pointed at.
--
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/1371634
Title:
block devices ap
marking confirmed... smb has some access now.
** 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/1462530
Title:
multipat
** Description changed:
$ sudo blkid
/dev/sr0: LABEL="Ubuntu-Server 14.04 LTS ppc64el" TYPE="iso9660"
/dev/sda2: UUID="795a6e14-ea4e-4718-9e98-c6df3696920c" TYPE="ext4"
/dev/sda3: UUID="0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4" TYPE="swap"
/dev/sdb2: UUID="1d14c1f3-716f-4fb8-9070-d321b39ffcb
Attaching console log of a wily (3.19.0-20-generic) kernel
** Attachment added: "console boot from wily (boot hangs)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462530/+attachment/4411645/+files/boot.log
--
You received this bug notification because you are a member of Kernel
Pack
** Summary changed:
- multipath errors on vivid kernel?
+ multipath errors on vivid and wily 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/1462530
Title:
multipath errors on vi
apport information
** Attachment added: "DeviceTree.tar.gz"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411649/+files/DeviceTree.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Tags added: apport-collected uec-images wily
** Description changed:
Oleg and I got changes into curtin to fix bug 1371634.
So that now we can boot into multipath iscsi devices on power.
It seems to go well enough with trusty+hwe-u, but when trying vivid, I am
see
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411650/+files/IwConfig.txt
--
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/14
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411656/+files/ProcModules.txt
--
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
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411658/+files/UdevDb.txt
--
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/1462530
apport information
** Attachment added: "nvram.gz"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411660/+files/nvram.gz
--
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/1462530
Ti
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411653/+files/ProcCpuinfo.txt
--
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
apport information
** Attachment added: "ProcPpc64.tar.gz"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411657/+files/ProcPpc64.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411654/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcMisc.txt"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411655/+files/ProcMisc.txt
--
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/14
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411648/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411651/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411659/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
Additional info:
$ sudo multipath -ll
mpath2 (1IBM IPR-0 5EC2A9A0) dm-2 IBM,IPR-0 5EC2A900
size=264G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='round-robin 0' prio=130 status=active
| `- 0:2:2:0 sdc 8:32 active ready running
`-+- policy='round-robin 0' prio
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1462530/+attachment/4411652/+files/Lspci.txt
--
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/1462530
** Also affects: multipath-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: multipath-tools (Ub
** Attachment added: "console log during install"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462530/+attachment/4413285/+files/trusty-log-install.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Well, I got what you asked for. full install log (with curtin -vv install).
And the console log of first boot.
Unfortunately, there are no issues in this boot.
I'd really think that I was making things up, in fact, I originally
ignored them, but then Mike saw the same thing I saw (log
https://bugs
** Attachment added: "console log during first boot [no errors]"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462530/+attachment/4413286/+files/trusty-log-boot.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
I'm copying Mike's log from bug 1371634 comment 21.
Note, this is a full installation log as Stefan asked for, and Mike is
still seeing issues.
I have tried the latest curtin-common and python-curtin from the wily
repositories running on 14.04.2:
#leftyfb@maaster[0]:~$ apt-cache policy curtin-co
Mike,
Please move issues with multipath (like are shown in that log) to bug 1462530.
Stefan had actually asked for almost exactly what you captured.
This bug is "fixed" as we're now booting into system correctly with
multipath enabled from installation under curtin.
I'll copy your comment and at
I collected the log in comment 23 and 24 yesterday, and then walked away.
Looked at the console from that system today, and it shows:
[54550.928492] EXT4-fs error (device dm-9): htree_dirblock_to_tree:914: inode
#7078166: block 28319821: comm updatedb.mlocat: bad entry in directory:
directory ent
** 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/1462530
Title:
multipath errors on vivid and wily kernel?
Status in l
So, just to catch this bug up with where Oleg and I are.
a.) curtin installs multipath-tools-boot into the target with /dev, /proc and
/sys mounted. However, it has disabled services from starting through
ChrootableTarget's allow_services=False [1]. That uses
disable_services_in_root [2].
b.)
related bug in redhat https://bugzilla.redhat.com/show_bug.cgi?id=630911
** Bug watch added: Red Hat Bugzilla #630911
https://bugzilla.redhat.com/show_bug.cgi?id=630911
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
I filed debian bug https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=788841 about the race condition that I think
exists.
** Bug watch added: Debian Bug tracker #788841
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788841
--
You received this bug notification because you are a member of K
Just a comment, as it is right now, attempt to install trusty with hwe-v will
fail due to this bug.
In order to make that work, we need a released (or daily) image and
specifically the related boot-initrd > 20150609.
That should happen in due course, the cloud-image daily builds had not
succee
ed in: maas-images
Importance: Undecided => High
** Changed in: maas-images
Status: New => Fix Committed
** Changed in: maas-images
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Public bug reported:
At first I thought it was a hard dive failure .. but sent it back and
another drive did the same thing. Then, put the drive on a different
machine and it booted/worked repeatedly with no problems. Got a 3rd
drive from a different manufacturer, and it did the same thing. Run
** No longer affects: linux (Ubuntu Trusty)
** Summary changed:
- block devices appear twice
+ block devices appear twice [install does not use multipath]
** No longer affects: multipath-tools (Ubuntu Trusty)
** No longer affects: multipath-tools (Ubuntu Vivid)
** Also affects: curtin
Impor
Please be patient ... I want to chase this bug to its end, but I have a
lot of things to deal with right away ... We may need to make some
decisions because I have only one of these boards. If I update the bios
and it fixes the problem, we can't chase it down in the code. If we
chase it down in the
I never didn't have this problem with the machine. However it has taken
me time to realize that it is a combination between main board and OS.
This machine was first put together about February. There is a new
kernel that just loaded onto the machine in updates, so even that might
unexpectedly fi
What I'm trying to point out is that I'm sure this board works with
other OSs, and I'm just as sure that the OS works with other boards. If
this were not true, neither the OS, nor the Board could be expected to
be out in the public as alpha products because this is an utter failure
of the system, n
well that chops out the new bios idea, so the remaining issue is whether
to try the upstream kernel or the newly downloaded kernel first.
--
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/1467
Public bug reported:
I have 2 different systems, both are kvm instances themselves, both running
vivid.
One of them has /dev/kvm and kvm working fine (well, fine-ish bug 1413540).
The other will not load the kvm_intel module.
=== system 1 ===
$ sudo kvm-ok
INFO: /dev/kvm does not exist
HINT:
** Summary changed:
- kvm_intel (nested) module will not load
+ kvm_intel (nested) module will not load [Input/output error]
--
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/1431473
Title:
To show that this issue is actually kernel (rather than host kernel not having
nested enabled), i booted into trusty kernel on the same 'system 1' above.
$ uname -r
3.13.0-46-generic
$ dpkg -S /boot/vmlinuz-$(uname -r)
linux-image-3.13.0-46-generic: /boot/vmlinuz-3.13.0-46-generic
$ lsmod | grep k
Also just verified that utopic kernel (3.16) also does not have /dev/kvm here.
So, short summary:
vmlinuz-3.13.0-46-generic - kvm_intel loads
vmlinuz-3.16.0-31-generic - Input/output error
vmlinuz-3.19.0-7-generic - Input/output error
--
You received this bug notification because you are a memb
Public bug reported:
sorry for the meta-bug here, but just upgraded from
linux-image-3.18.0-8-generic: /boot/vmlinuz-3.18.0-8-generic
to
linux-image-3.18.0-9-generic: /boot/vmlinuz-3.18.0-9-generic
and now:
a.) I don't seem to have an audio device ('settings -> sound' shows only
'Dummy Output'
just rebooted into 3.18.0-8-generic and verified that all three of the
items listed above are regressions between 3.18.0-8-generic and
3.18.0-9-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298581/+files/AlsaInfo.txt
--
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/14
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298582/+files/BootDmesg.txt
--
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/
Note, not running 3.18.0-9 due to issues as described in bug 1410921.
** Tags added: apport-collected vivid
** Description changed:
After upgrading to the 3.18 kernel in vivid (currently with
initrd.img-3.18.0-8-generic), hangouts are behaving badly for me. I
suspect this is due to video
Public bug reported:
After upgrading to the 3.18 kernel in vivid (currently with
initrd.img-3.18.0-8-generic), hangouts are behaving badly for me. I
suspect this is due to video device performance but that's just a guess.
Things I've noticed:
* hangouts have horizontal black bars / gitchy video
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298589/+files/ProcEnviron.txt
--
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
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298583/+files/CRDA.txt
--
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/1410940
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298590/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298584/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298592/+files/PulseList.txt
--
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/
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298595/+files/UdevLog.txt
--
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/1410
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298586/+files/Lspci.txt
--
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/1410940
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298587/+files/Lsusb.txt
--
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/1410940
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298591/+files/ProcModules.txt
--
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
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298588/+files/ProcCpuinfo.txt
--
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
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298585/+files/IwConfig.txt
--
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/14
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298594/+files/UdevDb.txt
--
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/1410940
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298593/+files/RfKill.txt
--
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/1410940
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1410940/+attachment/4298596/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
I'm now running upstream kernel and not seeing any of these issues.
$ uname -r
3.19.0-031900rc4-generic
$ dpkg -S /boot/vmlinuz-$(uname -r)
linux-image-3.19.0-031900rc4-generic: /boot/vmlinuz-3.19.0-031900rc4-generic
--
You received this bug notification because you are a member of Kernel
Package
I'm now running upstream kernel and not seeing this issue. mplayer plays fine
and hangout does not have glitchy video.
$ uname -r
3.19.0-031900rc4-generic
$ dpkg -S /boot/vmlinuz-$(uname -r)
linux-image-3.19.0-031900rc4-generic: /boot/vmlinuz-3.19.0-031900rc4-generic
--
You received this bug no
I'm marking this invalid. Such a massive regression just didn't make
sense between -8 and -9. So I 'dpkg --remove'd the package and re-
isntalled it, and its fine. There had been an error in upgrade
previously (related to a python package, not kernel) and I suspect that
the initramfs didn't get i
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: Triaged => In Progress
** Changed in: cloud-initramfs-tools (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
fix uploaded.
just for some more information, can fairly easily reproduce this bug using a
cloud image:
img_url="http://cloud-images.ubuntu.com/daily/server/vivid/current/vivid-server-cloudimg-amd64-disk1.img";
img_dl="${img_url##*/}"
Joseph, Also seems fixed with:
$ uname -r
3.18.2-031802-generic
$ dpkg -S /boot/vmlinuz-$(uname -r)
linux-image-3.18.2-031802-generic: /boot/vmlinuz-3.18.2-031802-generic
Thanks.
Scott
** Description changed:
After upgrading to the 3.18 kernel in vivid (currently with
initrd.img-3.18.0-8
currently *not* fixed in Ubuntu.
Booted into the following exhibits both the mplayer issue and hangout issue.
$ uname -r
3.18.0-11-generic
$ dpkg -S /boot/vmlinuz-$(uname -r)
linux-image-3.18.0-11-generic: /boot/vmlinuz-3.18.0-11-generic
$ apt-cache policy linux-generic
linux-generic:
Installed:
Public bug reported:
We currently build 2 meta packages for easy consumption and automatic
kernel upgrades. These are linux-virtual and linux-generic.
The -virtual meta package was created with the general purpose of
"support virtual environments", and then extended to include "and common
cloud
** Changed in: linux (Ubuntu)
Status: New => 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/1415634
Title:
RFC: replace linux-virtual with linux-server / tune kernel pa
It seems fixed now.
$ uname -r
3.18.0-12-generic
$ dpkg -S /boot/vmlinuz-$(uname -r)
linux-image-3.18.0-12-generic: /boot/vmlinuz-3.18.0-12-generic
$ apt-cache policy linux-generic
linux-generic:
Installed: 3.18.0.12.12
Candidate: 3.18.0.12.12
Version table:
*** 3.18.0.12.12 0
500 h
Sorry it took so long to get to this, but I was finally able to test on
my phone with OTA-8. The pairing worked as expected.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1552410
Title:
fix is now released to xenial under bug 1595302. daily cloud-images
with this newer version of cloud-init should appear in the next few
days. Any image with a serial number *newer* than 20160707 should have
cloud-init at 0.7.7~bzr1246-0ubuntu1~16.04.1 .
** Changed in: cloud-init (Ubuntu Xenial)
in: cloud-init (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1571761
Title:
zfs-import-cache.service slows boot b
Same problem. Reverted to 4.4.0-28. Didn't try mainline as -28 was
sufficient.
--
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/1603719
Title:
NFS client: access problems after updating to
** Changed in: maas-images
Status: Fix Committed => 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/1552378
Title:
Xenial doesn't see all cores nor usb network dongle
I didn't notice a difference with 16.04.01 either. I've switched most
of my computers to Linux Mint 18 Mate, which doesn't have this issue
even though it is based on 16.04. That OS uses about 400 MB with
nothing running, but some proprietary NVIDIA drivers boost it up to
about 800 MB. LM 18 Cinn
Also confirm -34 solves issue.
--
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/1603719
Title:
[regression] NFS client: access problems after updating to kernel
4.4.0-31-generic
Status
I booted a xenial guest as shown in my comment 10, added -proposed and
rebooted into overlayfs
ubuntu@sm-y1:~$ uname -r
4.4.0-38-generic
ubuntu@sm-y1:~$ dpkg -S /boot/vmlinuz-4.4.0-38-generic
linux-image-4.4.0-38-generic: /boot/vmlinuz-4.4.0-38-generic
$ grep overlayroot /proc/mounts
overlayroo
trusty + linux-virtual-lts-xenial looks good also.
ubuntu@sm-y1:~$ uname -r
4.4.0-38-generic
ubuntu@sm-y1:~$ dpkg -S /boot/vmlinuz-$(uname -r)
linux-image-4.4.0-38-generic: /boot/vmlinuz-4.4.0-38-generic
ubuntu@sm-y1:~$ grep overlay /proc/mounts
overlayroot / overlayfs rw,relatime,lowerdir=/media
OK, i recreated with simple:
uvt-kvm create sm-y1 release=yakkety
uvt-kvm ssh --insecure sm-y1
% echo "root:passw0rd" | sudo chpasswd
% sudo apt-get update && sudo apt-get dist-upgrade && sudo reboot
...
then at the virsh console i see the fail, log in and:
root@sm-y1:~# mount /dev/disk/by-
** No longer affects: cloud-init
--
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/1618572
Title:
apt-key add fails in overlayfs
Status in linux package in Ubuntu:
Confirmed
Status in li
** Changed in: cloud-initramfs-tools
Status: New => Confirmed
** Changed in: cloud-initramfs-tools
Importance: Undecided => Medium
--
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/
x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: scott 1702 F pulseaudio
/dev/snd/pcmC0D0p: scott 1702 F...m pulseaudio
/dev/snd/controlC0: scott 1702 F pulseaudio
I don't have a bootchart app either. Just in case I tried in terminal $
sudo rm /dev/.bootchart however there was no such file.
--
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/1572801
Titl
Here's a screenshot with various diagnostic windows up. It looks like
/dev/core is the culprit for me since my hdd is 1T but the process says
it is 140.7TB in size, the link goes to /proc/kcore but using sudo rm
/proc/kcore results in a message "Operation not Permitted" in the
terminal. However s
This is fixed for me. Thank you very much!!
--
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/1559308
Title:
Plugging HDMI screen in causes system hang
Status in linux package in Ubuntu:
I have a P65_P67RGRERA with an nVidia GTX 970m. I too have "kind of" got
it working by:
1. Installing the 4.6 kernel.
2. Installing the proprietary nVidia 364 driver.
3. sudo prime-select intel
4. Reboot, go in to the BIOS, and select "MSHYBRID" for the Graphics option.
5. Save BIOS changes and ex
Attaching a script that shows the failure without downloading an image.
** Attachment added: "script to show failure"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628336/+attachment/4749866/+files/show-fail.sh
--
You received this bug notification because you are a member of Kernel
Public bug reported:
This fails on 4.8.0-17-generic and passes on
$ sudo apt-get update
$ sudo apt-get install -qy cloud-image-utils
$ wget
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
$ cp xenial-server-cloudimg-amd64-disk1.img disk.img
$ sudo mount-image
** Description changed:
- This fails on 4.8.0-17-generic and passes on
+ This fails on 4.8.0-17-generic and passes on 4.4.0-9136-generic
$ sudo apt-get update
$ sudo apt-get install -qy cloud-image-utils
$ wget
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-di
I have this problem as well. Was already running 16.10 Development branch
successfully, I think that when 16.10 was released that the next sudo apt
update / upgrade changed something. I started getting errors that updates
needed to be applied, but some lock file was read-only; then whole screen
I am not running the low latency kernel, just generic kernel. I was
successfully using both AMD CPU (proprietary driver) AND the NVIDIA proprietary
driver.
I tried tweaking the UEFI settings, but made things worse. So I switched the
settings back.
--
You received this bug notification because
Public bug reported:
I booted a yakkety system on azure, and saw
$ systemctl status hv-fcopy-daemon.service --no-pager --full
● hv-fcopy-daemon.service - Hyper-V File Copy Protocol Daemon
Loaded: loaded (/lib/systemd/system/hv-fcopy-daemon.service; enabled; vendor
preset: enabled)
Active
Public bug reported:
I launched 2 different yakkety systems on azure instance types:
Basic_A0
Standard_D1_v2
More information what those things are at :
https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/
systemd-analize says:
## Basic A0
smoser@sm-y-d1v2-1:~$ systemd
** Description changed:
I launched 2 different yakkety systems on azure instance types:
Basic_A0
Standard_D1_v2
More information what those things are at :
https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/
systemd-analize says:
- ## Standard D1 v2
-
501 - 600 of 816 matches
Mail list logo
