** Package changed: ubuntu => linux (Ubuntu)
--
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/2074262
Title:
thinkbook volume buttons don't work
Status in linux package in Ubuntu:
New
You're correct. It can fail for other reasons. I don't think we could check
the errno, could we? It would be 1, "Operation not permitted".
If not, I think we can live with the last suggestion.
Thanks,
--
You received this bug notification because you are a member of Kernel
Packages, which i
Hey Dann,
This seems to work ok if I make the changes in our script.
Let me propose this script change to the owners I'll get back to you.
Thanks,
Sam
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
Thanks, Dann,
This dpkg-divert won't work unless we first remove the package this "clashes"
with (nvidia-crashdump had already diverted this file). Not sure if this is
really much better than just removing kdump-tools (and dependencies) and then
reinstalling them later.
We're still looking into
Hello Ian,
I've uploaded the cm-chroot-sw-img script here.
Please let me know if you need more info.
--Sam
** Attachment added: "cm-chroot-sw-img script"
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2043059/+attachment/5719804/+files/cm-chroot-sw-img
--
Yo
file DGXOS-6.1.0-DGX-H100.tar.gz is too large to upload
here.
If you have an alternate location, I can upload it there.
--Sam
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2043059
Hi Ian,
I have access to
http://bright-dev.nvidia.com/base-distributions/x86_64/dgx-os/dgx-
os-6.1-trd4/DGXOS-6.1.0-DGX-H100.tar.gz
And can upload it here if you need.
--Sam
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia
The complete recreate steps with errors are the following:
Steps to reproduce:
1. Create a directory on a BCM head node or any Linux sever, say
/cm/images/dgx-h100-image
2. Download and unpack the DGX-OS base tar archive into the above
directory
$ wget http://bright-dev.nvidia.com/base-distribu
I can install nvidia-390 and it works on my Kubuntu 23.10 laptop
monitor, however the external monitor is not detected and does not work.
If I remove Nvidia 390 as well a bumblebee-NVIDIA, the external monitor
works without a problem.
--
You received this bug notification because you are a member
I had been using the 525 Nvidia drivers successfully for several months.
Today I ran an `apt upgrade` after being away from my PC for a month,
and the upgrade caused this graphics driver issue to occur again.
I fixed it by running:
sudo apt install --reinstall nvidia-driver-525/jammy
sudo apt
Also "Marvell Technology Group Ltd. 88SE9125 PCIe SATA 6.0 Gb/s
controller [1b4b:9125]" - fixed with:
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x9125,
quirk_dma_func1_alias);
Is this sufficient or should I open a new bug?
--
You received this bug notification
Public bug reported:
Just updated to 20.04, not sure what happened
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-88-generic 5.4.0-88.99
ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
Uname: Linux 5.4.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
A
nUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - R
5.4.0-65-generic for this report.
This is my first Ubuntu bug report. Let me know if you need information.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pu
PID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release
sInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" -
PID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release
sInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fo
sInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" -
sInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" -
dioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fo
PID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release
PID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release
PID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
(
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release
sInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" -
PID ACCESS COMMAND
/dev/snd/controlC0: sam1157 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-05 (160 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
(
eport.
This is my first Ubuntu bug report. Let me know if you need information.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.16
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: sam1157 F pulseaudio
+ CasperMD5CheckResult:
I've installed the latest in proposed:
4.4.0-203-generic #235-Ubuntu SMP Tue Feb 2 02:49:08 UTC 2021 x86_64 x86_64
x86_64 GNU/Linux
So far I've seen no issues after about 8 hours of running this kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I can confirm I'm seeing similar behavior on 4.4.0-202
--
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/1913853
Title:
Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging
Status in linux
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 hav
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911219/+attachment/5453074/+files/prevboot.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/1
I can also confirm that on 5.8.0-34 I am getting this bug still as well.
It *seems* to mostly start happening after resuming from suspend, but
its too random to say for sure.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Been affected by this bug on Thinkpad T560 w/ i915 since mid September
(2020). I have been using -proposed over the last few days. So far, it
seems to have fixed the issue for me, the "interference lines" have not
reoccurred since.
--
You received this bug notification because you are a member
After testing out various kernels, I've found that the keyboard and
trackpad gain functionality in kernel 5.4.18-050418-generic.
No luck in the latest (5.8~) yet, but as 5.4 is a LTS kernel for now
I'll just stick with booting to 5.4.18 as that's only a few point
releases behind current stable any
Same here.
Same computer as original bug report (Hewlett-Packard HP Pavilion 11 x360 PC)
But different distro release (Xubuntu 20.04)
Laptop keyboard and trackpad totally nonfunctional on any kernel higher
than 5.4.0.42. Starting with 5.4.0-45 and all further kernels to today
(2020-09-22) the pro
I found the thread I talked about.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870971
the laptop the first poster has a 3500U in it according to google and a
few comments mentioned it
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Hiya - I get this too.
HP 15s-eq0507na:
Ryzen 5 3500U + Vega 8 iGPU
8GB DDR4
256GB M.2 NVME SSD
Always had this problem since the release of 20.04 - tried w/ secure
boot on and off.
Haven't tried the iomu=soft thing yet
Others evidently have this problem (I swear I saw a thread ab this on laun
Thanks everyone rather.
--
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/1886245
Title:
0a5c:21e8 Broadcom BCM20702A0: bluetooth mouse freezing for 4-9
seconds
Status in linux package i
Hi All,
I will have to close or finish it off.
The laptop met an unfortunate end...
Thanks evertobe
--
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/1886245
Title:
0a5c:21e8 Broadcom BCM2
** Description changed:
Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it
will work as normal.
I am using a plugable USB Bluetooth adapter for Bluetooth connections.
I am using blueman to connect.
Mouse used is a Kensington Exper Mouse Wireless Trackball
Issue d
More info!
I checked the logs again and found:
xhci_hcd :3e:00.0: HC died; cleaning up
Another one at the same time shows this message:
xhci_hcd :3e:00.0: PCI post-resume error -19!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
So what i have done since is:
Downloaded and copied the firmware as advised by You-Sheng Yang (vicamo).
Rebooted and then tried again, time was slightly less in waiting.
I then removed blueman again just in case that was giving issues and
reattached the mouse via bluetooth (reboot again) with the
Public bug reported:
Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it will
work as normal.
I am using a plugable USB Bluetooth adapter for Bluetooth connections.
I am using blueman to connect.
Mouse used is a Kensington Exper Mouse Wireless Trackball
Issue does not occur
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159
This bug also affected me after upgrading to Ubuntu 20.04.
Changing the grub boot options in `/etc/default/grub` to remove "quiet
splash" fixed the problem with having an external HDMI monitor plugged
in on
Public bug reported:
Although its recognised by the terminal and is enabled in settings the
touchpad still doesnt work, Output of xinput in terminal
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=15 [slave p
-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gdm1411 F pulseaudio
sam1718 F pulseaudio
/dev/snd/controlC0: gdm1411 F pulseaudio
sam1718 F pulseaudio
Hello,
I have the same issue. I'm on ubuntu 18.04.4 LTS ( kernel 5.3.0-40-generic )
The camera is an Ipevo P2V Point 2 View USB Document Camera.
when I plug the usb dmesg -w show :
[ 3390.529798] usb 1-1.4: Manufacturer: IPEVO Inc.
[ 3390.531093] hid-generic 0003:1778:0214.0006: hiddev0,hidraw2: US
The "4Go board" is the Raspberry Pi 4 Modebl B with (with 4Go RAM) :
https://www.raspberrypi.org/products/raspberry-pi-4-model-b/ . Sorry if
it wasn't clear enough.
The UGREEN case was bought on Amazon :
https://www.amazon.fr/gp/product/B07D2BHVBD
I don't have the UGREEN packaging, but according
Public bug reported:
When I connect an external SSD (Samsung 850 EVO 500 Go in a UGREEN USB
3.1 case) on my Raspberry Pi 4 (4Go) the Wifi stop working. It is easy
to reproduce, either en USB3 or USB2 connectors.
The SSD is mounted, only the Wifi fails.
The problem does not occurs on a fresh Rasb
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 higher
], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1773 F xfce4-volumed
sam1794 F pulseaudio
CRDA: Error: [Errno 2] No su
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 zfs-
** 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 (https://github.com/zfsonlinu
Debug info for Kernel 4.15.0.20.21
https://wiki.ubuntu.com/DebuggingKernelSuspend
Debugging information to provide in the bug report
Kernel 4.15.0.20.21
=
1. Issue occurs with resume from 'Suspend to ram' (not hibernate).
2. Suspend action initiated by clicking Suspend in the GUI.
3. Resu
Debug info for Kernel 4.20.0-042000
https://wiki.ubuntu.com/DebuggingKernelSuspend
Debugging information to provide in the bug report
Kernel 4.20.0-042000
=
1. Issue occurs with resume from 'Suspend to ram' (not hibernate).
2. Suspend action initiated by clicking Suspend in the GUI.
3. Re
I have the same issue with Asus Z87-Pro motherboard. Running a newer
BIOS and newer kernel.
Command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
Output:
2103
08/18/2014
I believe 2103 is the latest BIOS for this motherboard.
** Changed in: linux (Ubuntu)
S
I had a similar issue with Adobe Reader. I think you should check your
file because this bug is missing log files. It is also available Adobe's
Photoshop. It is a very interesting software. If you have any issue with
Photoshop, like error issue, then simply visit
https://www.adobesupportphonenumber
I'm also running the ASPM patch and haven't had problems for the last
month or so. Any idea when this will get merged?
--
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/1746340
Title:
Samsu
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
constatation
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 ap
*** List of CAPTURE Hardware Devices
card 0: NVidia [HDA NVidia], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1773 F xfce4-volumed
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 consisten
ric x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sam1617 F pulseaudio
/dev/snd/controlC0: sam1617 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 6 15:30:14 2018
InstallationDate: Install
I also have the same issue on a Razer Blade 2017 - 7500U model. My
system has the exact same drive in it. I have just installed the
4.18.0-3 kernel linked above and will post here if I run into the issue
again.
--
You received this bug notification because you are a member of Kernel
Packages, whi
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: zfs-linux
I think I'm seeing the same issue, but not sure. Let me know if I should
file a new bug:
```
[31816.378948] bad: scheduling from the idle thread!
[31816.378950] CPU: 19 PID: 0 Comm: swapper/19 Tainted: GW OEL
4.4.0-21-generic #37-Ubuntu
[31816.378950] Hardware name: Supermicro SYS-F618R
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, when
@kamalmostafa: Is the latest kernel released? Your assistance is
appreciated
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1746806
Title:
sssd appears to crash AWS c5 and m5 instanc
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 subscrib
Enable proposed updates from the "Software updater" application, install
whatever updates you get, then disable proposed updates again.
--
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/168090
FWIW the Xenial kernel from -proposed seems to work just fine too.
--
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
S
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.
(du
Just installed the kernel from proposed, if I don't report back that
means it works fine.
--
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
Can someone comment here once a fix for the HWE kernel in Ubuntu 16.04
is available? I'm currently using one of the custom builds from earlier
in this thread but I haven't yet been able to confirm whether it fixes
the issue or not.
--
You received this bug notification because you are a member of
@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
S
@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 is
@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 d
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 woul
@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 are
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 wan
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 Progr
@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 packa
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
Package
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.
https://bugs.launchpad.net/bugs/1680904
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 kerne
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 becau
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 derefe
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 th
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 t
This fix was merged and landed in 4.10.5
commit be18cce7e665b09406c4168fd3da32492dd5d8f3
Author: Jarod Wilson
Date: Mon Mar 6 08:48:58 2017 -0500
team: use ETH_MAX_MTU as max mtu
[ Upstream commit 3331aa378e9bcbd0d16de9034b0c20f4050e26b4 ]
This restores the ability to se
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
Just did a fresh install with an dist-upgrade to 4.4.0-64, and
apt-get install zfs
worked just fine:). After reboot the exported zpools were automatically
imported.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
htt
1 - 100 of 281 matches
Mail list logo
