Seems related or at least "close to" bug 1762748.
If nothing else, that bug has nice local recreate information.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1840686
Title:
Xenial
Public bug reported:
zfs cannot be used as a filesystem for an overlay mount's 'upperdir' or
'workdir' arguement.
If you have zfs root, or are inside an lxd that uses zfs then you'll not
be able to use overlay mounts without working around this bug.
It can be worked around by using a tmpfs.
$
*** This bug is a duplicate of bug 1718761 ***
https://bugs.launchpad.net/bugs/1718761
** This bug has been marked a duplicate of bug 1718761
It's not possible to use OverlayFS (mount -t overlay) to stack directories
on a ZFS volume
--
You received this bug notification because you are a
I hit this today, and filed bug 1873917 before dupe'ing it to this.
I'd think that the main pain points are
a.) using overlay in a container that is backed by zfs via lxd
b.) using overlay when using zfs root
(https://didrocks.fr/2019/10/11/ubuntu-zfs-support-in-19.10-zfs-on-root/)
I attached a r
** Merge proposal linked:
https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379177
** Changed in: cloud-utils
Status: New => Fix Committed
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-utils (Ubuntu)
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1834875
Title:
cloud-init growpart race with udev
Stat
The fix is in cloud-utils upstream now.
Still to do:
a.) review/merge cloud-initramfs-tools pull request
https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379177
b.) upload cloud-initramfs-tools to focal
c.) upload cloud-utils to focal
d.) any SRU
the order of 'b' a
a.) I gave the wrong link. ugh. It should have been:
https://code.launchpad.net/~smoser/cloud-initramfs-tools/+git/cloud-initramfs-tools/+merge/379774
b.) the fixed link to 'a' probably makes more sense now. But basically
you need a newer cloud-initramfs-tools to adjust for the fact that
growp
this seemed to "just work" for me.
http://paste.ubuntu.com/p/93dWDPZfZT/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1834875
Title:
cloud-init growpart race with udev
Status in
I really think you are all *way* over thinking this.
a. growpart made a change to the partition table (using sfdisk)
b. growpart called partx --update --nr 3 /dev/sda
c. growpart exited
With a and b growpart created udev events. If you create udev events,
you really need to wait for those event
> > So that means we have this sequence of events:
> > a.) growpart change partition table
> > b.) growpart call partx
> > c.) udev created and events being processed
> That is not true. whilst sfdisk is deleting, creating, finishing
> partition table (a) and partx is called (b), udev events ar
best. fix. ever.
working after a reboot.
$ snap list lxd
Name Version RevTracking Publisher Notes
lxd 3.18 12211 stablecanonical✓ -
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
marked this fix-released.
I dont see the problem any more.
It is possible it still affects 4.4 series, but bionic is fine for sure.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Public bug reported:
I'm not sure exactly what got me into this state, but I have several lxc
containers that cannot be deleted.
$ lxc info
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
addresses: []
architectures:
- x86_64
- i686
ce
I built and uploaded an image with cosmic-proposed enabled to get the
4.18.0-7-generic kernel.
Note that I'm fairly sure I also got linux-firmware at 1.175 (cosmic-proposed
version). But if that didn't make it into the initramfs (I'm assuming that
some linux-firmware files must make it into the
I updated the description to clarify. This issue only occurs on
VMStandard2.1 size. The image I uploaded works for VMStandard1.1 (which
gets a different NIC).
** Summary changed:
- Oracle cosmic image does not find broadcom network device in initramfs
+ Oracle cosmic image does not find broadc
** Attachment added: "dmesg, lspci -vvn from a bionic instance of same type
(vmstandard 2.1)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790652/+attachment/5184530/+files/vmstandard-2.1-bionic.log
--
You received this bug notification because you are a member of Kernel
Packages, w
@Seth,
I'm confused by:
"I'm not currently aware of any working kernel version."
Ubuntu 18.04 kernels (4.15) work correctly.
--
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/1790652
Title:
For the lazy
commit 707e7e96602675beb5e09bb994195663da6eb56d ->
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=707e7e96602675beb5e09bb994195663da6eb56d
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Invalid
** Changed in: cloud-init (Ubuntu Bionic)
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.n
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Invalid
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Public bug reported:
On a fresh instance of cosmic, run:
$ sudo iptables --list --numeric; echo $?
iptables: No chain/target/match by that name.
1
Expected result is something like:
$ iptables --list --numeric
Chain INPUT (policy ACCEPT)
target prot opt source destination
The module needed to magically make this work is 'bpfilter.ko'.
So at least one solution for this is to move bpfilter.ko from
the linux-modules-extra to linux-modules.
Currently linux-modules-extra-4.18.0-7-generic but we would want it
in linux-modules-4.18.0-7-generic.
bpfilter is described at
Originally ran into this trying to use lxd on cosmic as described in
https://github.com/lxc/lxd/issues/5081
Simple test case was just:
a.) launch fresh cosmic instance
b.) sudo snap install lxd
c.) sudo lxd waitready
d.) sudo lxd init --auto --storage-backend=dir
In the failure case, that ta
** Summary changed:
- iptables --list --numeric fails on -virtual kernel
+ iptables --list --numeric fails on -virtual kernel / -virtual missing bpfilter
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Hi.
I added a 'linux' package task here. It seems that in bug 1551419 patches were
added
to the ubuntu kernel to do the right thing. Possibly those patches were
inadvertantly
dropped? Either way, it seems like the [Ubuntu] kernel should promise this
consistently
so that multiple consumers do
Hi Adrian,
In a system where this recreates, could you please run:
cloud-init collect-logs
and attach the output?
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/1803173
Titl
Hi,
I recreated the issue using the Ubuntu upstream kernel builds at
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
After launching a 18.04 instance, and then installing those kernels
and rebooting (generic_4.20.0-999.201811252100) I saw the issue.
I noticed that cloud-init's /var
Marking this Invalid on cloud-initramfs-tools. It doesn't seem likely
that there is much we can do there.
** Changed in: cloud-initramfs-tools
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Zesty
** Changed in: cloud-init (Ubuntu Yakkety)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Zesty)
Importance: Undecided => M
I'm going to mark this fix-released.
The general bug as described in the description is that cloud-init can't
correctly apply networking for all interfaces.
cloud-init local applies networking configuration to the system, and
should apply before the system brings networking up. Thus appearing to
** Summary changed:
- attempts to rename vlans / get_interfaces_by_mac does not filter vlans
+ attempts to rename vlans / vlans have addr_assign_type of 2
** Summary changed:
- attempts to rename vlans / vlans have addr_assign_type of 2
+ attempts to rename vlans / vlans have addr_assign_type of
Public bug reported:
We have a node with nvme disk, and storage config like:
partitioning_commands:
builtin: [curtin, block-meta, custom]
storage:
config:
- {grub_device: true, id: nvme0n1, model: INTEL SSDPEDME400G4, name: nvme0n1,
ptable: gpt,
serial: CVMD5066001N400AGN, type: disk,
Some further investigation...
It sure appears to me that hwe-t kernel was probably never supported with this
system (at least that disk).
** Attachment added: "lshw run in trusty with hwe-t"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683919/+attachment/4864448/+files/lshw-hwe-t
--
Attaching lshw output in hwe-x.
The difference is really that hwe-x has this entry:
- physical id: 3.0.0
- bus info: scsi@0:3.0.0
+ physical id: 0.0.0
+ bus info: scsi@0:0.0.0
+ version: 4.52
+
OK.
So what seems to be the issue here is that
a.) I'm not sure why, but when installing with hwe-t (after commissioning with
xenial) the third party drivers section of the curtin preseed does not get
rendered (http://paste.ubuntu.com/24409744/). So we do not install hvpsa
driver.
b.) Even if
** No longer affects: linux (Ubuntu)
** No longer affects: curtin
--
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/1683919
Title:
installation fails with trusty and hwe-t kernel
Status i
Public bug reported:
Hi,
I was trying to verify bug 1677376 yesterday, and came to find out
that our kernel does not have virtio or virtio-scsi builtin drivers.
This generally has not been a problem as initramfs has been used.
However, as there is recently an interest in booting without initramfs
Yasuo,
It is not exposed in any way through vagrant.
It is a kernel command line option.
You'd have to edit /etc/default/grub and add it to GRUB_CMDLINE_LINUX_DEFAULT
and then run 'update-grub'.
I had done a quick test and didn't seem to think that it fixed the
issue, but I'd be interested in he
** Changed in: cloud-images
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/1726818
Title:
vagrant artful64 box filesystem too small
Status in cloud-image
An upstream commit landed for this bug.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=bd40234f
--
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/17575
Joseph,
Thanks for providing the link to the mailing list post. That is very
helpful.
On Fri, Mar 23, 2018 at 4:15 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> SRU request submitted:
> https://lists.ubuntu.com/archives/kernel-team/2018-March/090976.html
>
> --
> You received
Public bug reported:
Booted under maas in rescue mode system console has the attached failure.
First bit is
[ 440.196466] BUG: unable to handle kernel paging request at
fe3ed820
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-generic (not installed)
ProcVersionSignature: Ubu
Public bug reported:
Booted under maas in rescue mode system console has the attached failure.
First bit is
[ 440.196466] BUG: unable to handle kernel paging request at
fe3ed820
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-generic (not installed)
ProcVersionSignature: User
*** This bug is a duplicate of bug 1749221 ***
https://bugs.launchpad.net/bugs/1749221
The collected files here were from a different system.
** Attachment removed: "console log of bibarel and kernel trace"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749216/+attachment/5054346/+
** Attachment added: "full console log into kernel trace"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749221/+attachment/5054369/+files/bibarel-crash-full-console.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
It happens within 3 minutes of system boot into 4.13 kernel.
2 systems reproduced this. You're lucky to be able to log in before it crashes.
--
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/
Tetsuo,
Thanks for the info. Removing 'apparmor=0' isn't an option right now both
because MAAS doesn't let you control that and because it is there to work
around other bugs (originally bug 1677336).
--
You received this bug notification because you are a member of Kernel
Packages, which is su
** Description changed:
1. $ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
2. $ apt-cache policy linux-image-`uname -r`
linux-image-4.13.0-16-generic:
- Installed: 4.13.0-16.19
- Candidate: 4.13.0-16.19
- Version table:
- *** 4.13.0-16.19 500
- 500 http
I've removed the verification-failed-xenial tag.
The problem reported in bug 1750732 may be related to a grub upgrade, but
surely is not related to this specific grub upgrade.
Please see the changes
http://launchpadlibrarian.net/354651271/grub2_2.02~beta2-36ubuntu3.16_2.02~beta2-36ubuntu3.17.di
Hi.
I've confirmed this fix by using curtin's "vmtest" test harness.
I've applied the attached patch to curtin at 82622f129b.
The patch does:
a.) remove the work arounds we had in place to make zfs root work on xenial.
b.) enable proposed
Then I've run an install of a system that does a installat
** Attachment added: "first boot console log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/+attachment/5060822/+files/boot-serial.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.lau
>From the install log you can see that we install grub2 at
>2.02~beta2-36ubuntu3.17.
..
Unpacking grub2-common (2.02~beta2-36ubuntu3.17)
..
'dpkg-reconfigure grub-pc' and 'grub-install /dev/vda' are run
And also:
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-116-g
** Attachment added: "installation console log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/+attachment/5060821/+files/install-serial.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bug
Public bug reported:
I logged in this morning and found system kind of sluggish.
A 'top' showed 'zed' process spinning 100% of a cpu.
I didn't feel like worrying about it, so I simply rebooted.
System came back up into the same state.
Running 'strace -p 2002' shows repeated:
ioctl(5, _IOC(0, 0x5
sorry for not being clear above. I had dpkg-diverted that update-grub,
so my dist-upgrade and then reboot put me back into an older kernel.
--
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/bu
Colin, thanks for quick response.
rebooting into 4.15 did in resolve the issue.
I woudln't have stumbled on it at all except at some point i had dpkg-diverted
/etc/kernel/postinst.d/zz-update-grub
so dist-upgrades didn't fix it.
fwiw, I was booted into vmlinuz-4.13.0-32-generic when I found the
Why did you mark this invalid?
If zfs 0.7.X relies on kernel > 4.13, then it seems a valid bug.
zfs-zed does not mention any dependency on a specific linux version, and even
if it did wouldnt users be guaranteed to hit this issue after they'd upgraded
zfs-zed and before they'd upgraded (and rebo
Joseph forwarded this upstream. LKML mailing list post
https://lkml.org/lkml/2018/3/1/812 .
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729145
Title:
/dev/bcache/by-uuid links not c
recreate in a vm that had a free block device /dev/vdb.
sudo zpool create -f myzfs /dev/vdb
sudo zfs create -p myzfs/myproject/foo
sudo chmod 1777 /myzfs/myproject/foo
cd /myzfs/myproject/foo
apt-get update
apt-get install -y ubuntu-dev-tools
apt-get build-dep -y libaio
pull-lp-source libaio
sh
** Summary changed:
- system process hung on container stop/delete
+ zfs system process hung on container stop/delete
--
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/1754584
Title:
z
This does recreate on a zfs filesystem also. No lxc is required.
Recreated as root and non-root on 4.15.0-10-generic .
--
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/1754584
Title:
** Also affects: nss-pam-ldapd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu)
Importance: Undecided
Status: New
** Also affects: openvpn (Ubuntu)
Importance: Undecided
Status: New
** Also affects: postfix (Ubuntu)
Importance: Undecid
** Description changed:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same fun
This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ker
Public bug reported:
MAAS is currently failing to deploy artful.
[0.00] Kernel command line: nomodeset
iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-
ga-17.10-artful-daily iscsi_target_ip=10.245.71.3 iscsi_target_port=3260
iscsi_initiator=wichita ip=wichita:BO
Seems likely related to:
https://github.com/coreos/bugs/issues/2152
There are three overlayfs commits that add ESTALE returns in 4.13. Two of them
only affect mount time, and the third is torvalds/linux@b9ac5c2. Other 4.13
overlayfs changes may have introduced new calls to existing functions
Public bug reported:
My wireless seems to have stopped working (at least working well).
[ 27.950002] [ cut here ]
[ 27.950030] WARNING: CPU: 1 PID: 148 at
/build/linux-z2ccW0/linux-4.4.0/net/mac80211/driver-ops.c:175
drv_conf_tx+0x1c8/0x1e0 [mac80211]()
[ 27.95003
Hi,
I'm coming here from bug 1730744.
Is this bug expected to be fixed for 18.04?
--
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/1739672
Title:
Regression in getaddrinfo(): calls block
I've marked this 'Fix Released' in xenial as Ubuntu's package in xenial
at 0.6.5.6-0ubuntu3 which has the fix at [1] as mentioned in comment 29.
Further, my experience with our zfs work in curtin indicates that it is
fixed.
--
https://github.com/zfsonlinux/zfs/commit/d2f3e292dccab23e47ade3c67677a1
I've uploaded just now grub2 (2.02~beta2-36ubuntu3.17) and
grub2-signed (1.66.17) to the xenial SRU queue.
There are currently versions in xenial-proposed for these packages with
fixes for bug 722950 and bug 1708245.
Hopefully after those uploads clear xenial-proposed the fix for this bug will
ge
** Changed in: zfs-linux (Ubuntu)
Status: New => Fix Released
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: zfs-linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: zfs-linux (Ubuntu Xenial)
Status: New => Confirme
The attached /var/log/cloud-init.log has 2 boots in it.
One starts at 14:15:18 (line 1) and one starting at 14:21:17,808 (line 719).
The first boot successfully updated the partition table for /dev/sda
so that the first partition (/dev/sda1) took the whole ~ 10G disk.
2017-10-24 14:15:33,338 -
So the/some interesting points of dmesg.log:
[0.00] random: get_random_bytes called from start_kernel+0x42/0x4e1
with crng_init=0
[0.00] Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version
7.2.0 (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubu
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1726818/+attachment/4992312/+files/Dependencies.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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1726818/+attachment/4992313/+files/ProcCpuinfoMinimal.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** No longer affects: e2fsprogs (Ubuntu)
--
You received this bug
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
DistroRelease: Ubuntu 17.10
Ec2AMI: ami-02da
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
JournalErrors:
Error: command ['journalctl', '-b', '--priority=warning', '--l
Joseph,
I'm sorry, I'd not seen the request for test. This is unfortunately
non-trivial to test.
I agree, the next thing to do is to check and see if the issue is still
present in upstream, the hwe for 16.04 and the current GA for 16.04.
I dont expect that I will haev any time to look at this
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: N
** Attachment added: "qemu info from failed"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651602/+attachment/4795293/+files/bad-649-XenialTestNvme-install-launch.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
** Attachment added: "console serial log from failed"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651602/+attachment/4795294/+files/bad-649-XenialTestNvme-install-serial.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
** Attachment added: "console serial log from pass"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651602/+attachment/4795296/+files/good-647-XenialTestNvme-install-serial.log
** Tags added: apport-collected ec2-images xenial
--
You received this bug notification because you are a mem
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Dec 22 13:44 seq
crw-rw 1 root audio 116, 33 Dec 22 13:44 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioD
** Attachment added: "qemu info from pass"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651602/+attachment/4795295/+files/good-647-XenialTestNvme-install-launch.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1651602/+attachment/4795301/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1651602/+attachment/4795299/+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/1651602
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1651602/+attachment/4795297/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1651602/+attachment/4795300/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1651602/+attachment/4795303/+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/1651602
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1651602/+attachment/4795298/+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/1651602/+attachment/4795304/+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
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1651602/+attachment/4795302/+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
This script shows the failure, downloading a xenial cloud-image
that has vmlinuz-4.4.0-53-generic (release-20161214) and one that has
vmlinuz-4.4.0-57-generic (release-20161221).
Other differences are
changed: ['linux-image-virtual', 'apport', 'systemd',
'linux-image-4.4.0-57-generic', 'cloud-in
OK, so I installed vmlinuz-4.4.0-57-generic into the good image (apt-get
install linux-virtual) and the resulted kernel/initrd still show the
problem.
So this is squarely a kernel regression.
** Summary changed:
- [2.1.1] Yakkety - MAAS has nvme0n1 set as boot disk, curtin fails
+ [2.1.1] MAAS
Just to be clear, the failure I'm seeing is that in qemu, if you try to
boot with root=LABEL=cloudimg-rootfs it will no longer work.
I believe that this is another symptom of both the failure in vmtest and
the failure that Chris saw.
The reproduce above is just easier to run.
--
You received th
I've just now tested yakkety, and it seems like both 4.8.0-30-generic
and 4.8.0-32-generic are working fine, so I do not believe this to
affect yakkety.
** No longer affects: linux (Ubuntu Yakkety)
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notif
Seems only present in xenial, 4.4.0-57-generic.
** Changed in: linux (Ubuntu Xenial)
Importance: High => Critical
--
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/1651602
Title:
[2.1.1
Recreate is as show above, or:
qemu-system-x86_64 -enable-kvm \
-drive file=disk1.qcow,if=none,format=qcow2,id=nvme0 \
-device nvme,drive=nvme0,serial=nvme-0 \
-snapshot -nographic -echr 0x05 -m 512 \
-kernel kernel -initrd initrd \
-append "root=LABEL=cloudimg-rootfs console=t
Dan Streetman suggested that this should only be a problem with a single cpu
system.
I did verify that the failure shown above goes away if you add '-smp cpus=2' to
the qemu command line.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
1 - 100 of 408 matches
Mail list logo
