I have a similar workaround as Rekby, only as a pm-action hook.
https://gitlab.com/snippets/1786967
--
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/1784152
Title:
i2c_hid_get_input flood
I was having the same issue on a dell inspiron 15 7000, with more
i2c_hid i2c-ELAN2097:00: i2c_hid_get_input: incomplete report (67/65535)
records in my logs per second than I cared to count.
adding 'acpi_osi=' to GRUB_CMD_LINE_DEFAULT only seemed to succeed in disabling
my trackpad, so i qui
Public bug reported:
After a fresh install of ubuntu 18.10 everything was fine for days
now when I suspend then resume it has logged me out
This behaviour is repeatable ... every suspend results in a resume into a fresh
login session.
My uptime indicates its not a reboot just a log out
Descript
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
The screen brightness is now working on kernel 4.10.0-21 generic but the
keyboard brightness is not, on Asus GL753VE.
Very close
--
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/1653456
Tit
Still no keyboard brightness, all other FN keys are working, on GL753VE
uname -a:
Linux Taz 4.10.0-21-generic #23~lp1653456+elan SMP Fri Apr 28 14:34:03 CST 2017
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** 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
Public bug reported:
apt-get upgrade caused crash of wireless bcmwl
afterwards my wifi fails to work
before updates had
x86_64
5.4.0-57-generic
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"
apt-get upgrade
The following NEW package
lspci | grep -i network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4322
802.11a/b/g/n Wireless LAN Controller (rev 01)
SOLUTION
sudo apt-get purge bcmwl-kernel-source
sudo apt-get install broadcom-sta-source broadcom-sta-dkms
broadcom-sta-common
reboot
now w
Public bug reported:
I started seeing my system fail to resume from suspend over the last
couple of weeks. It happens about 1 in 5 times maybe? I press the power
button on my system to resume it and my screens stay blank. I am able to
connect to the system remotely over ssh and check syslog to fin
Ah, the included dmesg output doesn't actually have the useful snippet
in it. Please see attached section of log output which runs from when I
attempted to resume the system to when it was rebooted.
** Attachment added: "amd-gpu-resume-fail-syslog.log"
https://bugs.launchpad.net/ubuntu/+source
Sorry, I may not have made it obvious. The problem started on Focal but
I have since upgraded to Groovy as I thought a newer kernel may help
given various amdgpu fixes hit the kernel between 5.4 and 5.8.
I do see a pending update for 5.8.0-34 though which I'll install.
--
You received this bug n
Public bug reported:
dell laptop wifi worked prior to upgrade from Ubuntu 20.04 to 20.10
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6
ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55
Uname: Linux 5.4.0-44-generic x86_64
ApportVersion
*** This bug is a duplicate of bug 1878045 ***
https://bugs.launchpad.net/bugs/1878045
** This bug has been marked a duplicate of bug 1878045
doing dist-upgrade got error related do Broadcom
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
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
Public bug reported:
on a fresh install which happened with no wifi connection so no updates
during install
once installed I defined a good wifi connection
then ran apt-get update && apt-get upgrade
I get this error on next reboot
ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: bcmw
lspci | grep -i network
02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac
Wireless Network Adapter (rev 03)
sudo lshw -C network
*-network UNCLAIMED
description: Network controller
product: BCM4352 802.11ac Wireless Network Adapter
vendor:
on a fresh ubuntu 20.10 install ( not upgrade ) seeing same bug
wifi not working
in settings option to change wifi is grayed out
able to reach internet OK using ethernet
x86_64
5.8.0-26-generic
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.10
DISTRIB_CODENAME=groovy
DISTRIB_DESCRIPTION="Ubuntu 20.10"
lspci | grep -i network
02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac
Wireless Network Adapter (rev 03)
sudo lshw -C network
*-network UNCLAIMED
description: Network controller
product: BCM4352 802.11ac Wireless Network Adapter
vendor:
** 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
Hey all,
This workaround has seemingly fixed the issue for me (temporarily)
- Unpair the headphones from the USB adapter using the Bluetooth Manager
application
- sudo service bluetooth restart
- Pair headphones again and choose A2DF from Sound settings.
This has worked for me without fail eac
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
I tried what Wren tried, but this did not fix the problem for me. I
replaced the entire QCA6147 directory, not just hw3.0. Still no luck.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
[Impact]
Most attempts to use IPv6 on the ThunderX NIC will fail.
[Test Case]
Attempt an IPv6 TCP connection:
$ wget -6 'http://www.kernel.org/'
The connection will time out.
[Regression Risk]
The fix is upstream, and is limited to the ThunderX nicvf driver.
[Workaround]
Returning to confirmed status - easily reproducible with LTS kernels.
--
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/1755627
Title:
ibrs/ibpb fixes result in excessive kernel logging
St
We use LTS kernels, so no - unfortunately we cannot.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Thank you Leann!
--
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/1755627
Title:
ibrs/ibpb fixes result in excessive kernel logging
Status in linux package in Ubuntu:
Confirmed
Status i
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/
Let me know what I can do to help move this forward. The ubuntu-load-
zfs-unconditionally patch was not a great solution as it results in
systems that install zfsutils-linux to come up in a failed state when
there are no ZFS pools present:
$ systemctl --failed
UNIT LOAD ACT
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
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
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/1736593
Title:
ThunderX: TX failure unless checksum off
I am glad to report that the problem has been resolved. The issues I
saw with 4.13.0-35.39 during verification appear to be KPTI-related.
After upgrading to 4.13.0-36.40, all is well.
Thanks to everyone that assisted with moving this forward.
--
You received this bug notification because you ar
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
Note that for bionic as of this week the behavior is now different. This
particular problem doesn't surface for zfs-import-cache.service (because
the ConditionPathExists expression is back in the unit).
It's not all good news, however, as that one failed unit has been
replaced with:
$ systemctl -
I found the xenial issue I was thinking of [1] but I'd be surprised if
that particular case regressed (it had to do with use of /etc/mtab). For
completeness, I'll mention it here anyway.
[1] https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1607920
--
You received this bug notification be
Great, thanks Colin! We will test this on bionic very soon and will
follow up to confirm.
--
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/1741081
Title:
zfs-import-cache.service fails
OK, I retested with 0.7.5-1ubuntu3 and it's almost there but zfs-
mount.service still runs before the zfs kernel module is loaded:
$ systemctl --failed
UNIT LOAD ACTIVE SUBDESCRIPTION
● zfs-mount.service loaded failed failed Mount ZFS filesystems
$ sudo journalctl -u zfs-moun
I can confirm that with the latest bionic packages (zfsutils-linux
0.7.5-1ubuntu4) all units start successfully for the case where no ZFS
pools are present. This is exactly as I would expect.
I can't really speak to the discussion about tainted kernel. If I didn't
want ZFS, I wouldn't install zfsu
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
Not sure if this is the same issue, but I'm getting:
[ 32.468026] watchdog: BUG: soft lockup - CPU#5 stuck for 23s!
[nvidia-smi:594]
on Kubuntu 17.04 (kernel 4.13.3-041303-generic, i7-4790, GTX 1070,
Nvidia 384.69). My desktop still works fine, I do not experience any
crashes or freezes, but sh
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
Public bug reported:
I recently updated Ubuntu 18.04 in a vm have a long dormancy and I found
the issues I had after a reboot.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-generic 4.13.0.17.18
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-gen
I also get the attached screenshot when attempting to boot into recovery
mode.
** Description changed:
I recently updated Ubuntu 18.04 in a vm have a long dormancy and I found
- the issues I had after a reboot. I am currently running
- 4.10.0-19-generic.
+ the issues I had after a reboot.
** Tags added: kernel-bug-exists-upstream
--
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/1744214
Title:
Boots into initramfs with an error stating that the UUID of the main
partition c
** Tags removed: kernel-bug-exists-upstream
--
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/1744214
Title:
Boots into initramfs with an error stating that the UUID of the main
partition
Confirmed to also affect bionic:
$ sudo journalctl -u zfs-import-cache.service
-- Logs begin at Tue 2018-01-23 17:46:55 UTC, end at Tue 2018-01-23 17:49:18
UTC. --
Jan 23 17:46:58 ubuntu systemd[1]: Starting Import ZFS pools by cache file...
Jan 23 17:46:59 ubuntu zpool[640]: failed to open cache
I tried installing and testing the mainline kernel, but I encountered
issues with the linux-image not generating. I also tried to install
openssh-server and ssh while on 4.10.0-19-generic and I get errors that
dpkg failed processing 4.13.0-25 with the new modules. I have tried
uninstalling this sam
** Attachment added: "This is the output when I run dpkg --configure -a"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+attachment/5042465/+files/zMWvxbzf.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
** Attachment added: "This is the output I get when I try to install
4.15.0-041500rc9-generic."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+attachment/5042464/+files/PiJFDc42.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
** Attachment added: "This is the output of apt-get remove --purge
linux-image-extra-4.13.0-25-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+attachment/5042466/+files/P0kVWunc.txt
--
You received this bug notification because you are a member of Kernel
Packages, whic
I needed to reinstall Ubuntu and the problems I attached earlier no
longer apply.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
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
This bug is not to track a problem, it's to change a default kernel
option to a more secure setting already in use by other distributions,
such as upstream Debian.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Public bug reported:
bcmwl-kernel-source worked correctly on the original 16.04 LTS kernel,
but no longer works on the hwe kernel (4.10.0-33). I am using the b43
open source driver temporarily in order to file this report.
Description:Ubuntu 16.04.3 LTS
Release:16.04
bcmwl-kernel-so
Laptop info:
description: Notebook
product: 0769AK8 (Lenovo)
vendor: LENOVO
version: 3000 N200
serial: redacted
width: 64 bits
capabilities: smbios-2.4 dmi-2.4 vsyscall32
configuration: boot=oem-specific chassis=notebook family=Lenovo sku=Lenovo
uuid=redacted
*-core
Sorry, my previous comment was for another initramfs-tools related bug.
Please disregard #18.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1515513
Title:
/boot/initrd.img-*.old-dkms fil
The commit for this in upstream Debian (0.123 version of initramfs-
tools) is here: https://anonscm.debian.org/cgit/kernel/initramfs-
tools.git/commit/?id=ac6d31fc2c707b72ff8af9944c9b4f8af303a6a3 - I would
be happy to make a patch for this commit to xenial (zesty and later has
0.125+, so should alr
Mistaken identification of affected package. After reinstalling
16.04(.0) I have verified that bcmwl-kernel-source is not involved.
Marking this bug invalid.
** Changed in: bcmwl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Pack
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
101 - 200 of 816 matches
Mail list logo
