Public bug reported:
I can confirm this problem: https://askubuntu.com/questions/1306700
/fixing-gpu-hang-caused-by-i915-driver
Symptom: unable to launch any application after login on to the system,
login screen etc works fine. The system thus becomes completely unusable
for regular users. I
As kernels 5.2.0-x will bring zfs 0.8.x to Bionic LTS, I'd like to draw
some attention to this request. People will get the 0.8.x zfs module via
HWE but won't be able to do much with the major new features without the
userland tools.
I tried to install the debs from Eoan, but they require a
** Changed in: linux (Ubuntu)
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/787210
Title:
ath9k drivers freeze the system when changing
Check out https://wiki.ubuntu.com/Kernel/LTSEnablementStack. This is the
formal way Ubuntu provides newer kernels (and as such newer zfs
versions) during the lifecycle of an LTS release.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: zfs-linux (Ubuntu)
Status: New => Fix Released
--
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/1772412
Title:
zfs 0.7.9 fixes a bug
My main reason for suggesting this is that it seems Canonical is easier
on snaps wrt. having rolling upgrades. I don't see a reason debs can't
do it, but I notice over and over again Canonical is very conservative
upgrading major software versions on debs (which is no criticism, just a
Public bug reported:
This circumvents the need to keep it on the same major version
throughout the LTS cycle. LXD is doing snaps, perhaps for zfs this is
the best approach as well.
Xenial still has zfsutils on generation 0.6, with the module on 0.7.
Even when patches are applied as needed that
Closing this old bug. Newer versions should not see this issue anymore.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I don't see the confirmation for Bionic in this bug report. Any update
when the 4.17 kernel lands in bionic-proposed? Or do I need another
kernel version for Bionic? What do I need exactly for my Bionic server?
This bug prevents me from updating my lxd containers, it will hang the
system
Public bug reported:
I have experienced the problems fixed by this commit
https://github.com/zfsonlinux/zfs/pull/7343 a few times on my NAS. The
system hangs completely when it occurs. It looks like 0.7.9 brings other
interesting bug fixes that potentially freeze the system.
** Affects:
I think the answer does not cover my question, as the ZFS driver is
linked to the kernel, which evolves with point releases and/or HWE
kernels on LTS versions.
To make it as practical as possible, let's assume ZFS 0.8 gets released
in June. I think I now can conclude it will not get backported to
Public bug reported:
If we consider the zfs 0.x releases as being major (0.6, 0.7, 0.8), is
the assumption correct that LTS releases will not receive a new major
ZFS release ?
To be as practical as possible: Bionic will be stuck at zfs 0.7.x,
Xenial at zfs 0.6.x ?
If my assumption is wrong,
Yes, but what does that mean wrt. supporting ZFS releases? Are major
upgrades considered for all currently supported HWE kernels? The current
LTS kernels? Only future/next LTS kernels? What is the policy?
--
You received this bug notification because you are a member of Kernel
Packages, which is
What is the policy for ZFS release updates? Are they limited to LTS
releases? Will all HWE kernels get upgraded eventually?
As an example, would Xenial eventually see ZFS 0.7 or even 0.8 or 0.9 ?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Can't reproduce the crash as described before (consistently failed on a
heavy export job in virtualbox W10 guest).
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
** Description changed:
Upgraded to zesty about a week ago. Ran into this on latest kernel.
@brad-figg Thanks, that's good to hear!
--
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/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
Status in Linux:
Unknown
@matthias-opennomad
I use sudo apt install /directory-with-the-debs/*.deb. Use absolute
paths for this.
It warns about downgrading, after which the install runs fine.
@mstucki
Are you running on HWE ?
--
You received this bug notification because you are a member of Kernel
Packages, which
@chihchun
Out of interest: could you give the procedure how you build this (I've
seen various recipes online)?
On my system, your debs are considered a lower version to the
repositories that have 4.10.0-28 as well and will offer to "upgrade" it
to the official ones every apt upgrade cycle.
So I
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
--
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/1680904
Title:
zesty unable to handle kernel NULL pointer
Public bug reported:
ZFS 0.7.0 has been released: http://list.zfsonlinux.org/pipermail/zfs-
announce/2017-July/15.html.
It is important to note it will require an update of the userland tools
(zpool command). This can be an issue especially for the HWE kernel
stack if ZFS module versions
@flipvb
The main issue is not that this bug exists and that it is not the fault
of Canonical. The issue is that the 16.04 stable HWE LTS stack rolled to
4.10 despite this bug being known and being critical, with 16.04.3 not
even released yet.
--
You received this bug notification because you
I can consistently reproduce this issue doing a heavy mail export job in
a VirtualBox guest I use for work.
Just having done first run after applying the deb files provided per
comment 52, I was not able to reproduce the issue. Thank you @chihchun !
Canonical needs to apply these asap if they
I can now confirm this bug landed on the LTS HWE kernel.
Honestly, I get Ubuntu for free (well I support them but by no means
this is comparable to certain other license schemes out there) but I
have never been so disappointed. All my systems are now at risk. I don't
know who does QA at Canonical
Ok, I'll give it a go.
--
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/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
Status in linux package in Ubuntu:
In
@chihchun does your build contain zfs modules?
--
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/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
Status in linux
I was not expecting the 4.10 kernel to land in the HWE stack for LTS
without seeing a fix here, so I am genuinely worried about the LTS+HWE
stability now.
Can we get confirmation on the state of the HWE 4.10 kernel?
--
You received this bug notification because you are a member of Kernel
I noticed the HWE kernel rolled from 4.8 to 4.10.0-27-generic, and I
wondered if someone knows whether this bug was addressed in that?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I need zfs and it fails on the proprietary nvidia driver too. I'll see
if I can get it running.
--
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/1680904
Title:
zesty unable to handle
Can't we upstream the Xenial zfs script instead of fixing the "new" one?
It supports the same syntax, and does what it needs to do? And it does
not try to mount datasets I explicitly configured not to be mountable ;)
Seems like the faster solution, no?
--
You received this bug notification
So experiencing several crashes a day (hard lock) I decided to install
the HWE 4.8 kernel using the Xenial deb files. No more lock ups have
occured since.
This seems to me an extremely critical issue at the heart of the OS. I
would have expected more visibility on this TBH.
--
You received this
After a few days of using the patched kernel: the patch is not a 100%
fix.
--
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/1680904
Title:
zesty unable to handle kernel NULL pointer
I have implemented the workaround from #7
(https://bugs.freedesktop.org/show_bug.cgi?id=99295#c22) using the
attached patchfile on kernel 4.10.0-20.
My system crashed consistently when doing a resource heavy export job on
a VirtualBox Windows 10 guest. First try after patching this no longer
is
I have this issue and can provide logs if needed. Kernel
4.10.0-20-generic on Zesty. Very, very nasty bug causing very frequent
hard crashes. I think the importance ought to be raised on this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs
script might overrule canmount and mountpoint options for a dataset,
causing other mount operations and with them the boot process to fail.
Experienced this with Ubuntu Zesty. Xenial seems to ship with a
34 matches
Mail list logo
