Also affects Ubuntu/Focal:
# readlink /usr/share/doc/zfs-zed/changelog.Debian.gz
../libnvpair1linux/changelog.Debian.gz
# readlink /usr/share/doc/zfsutils-linux/changelog.Debian.gz
../libnvpair1linux/changelog.Debian.gz
# readlink /usr/share/doc/zfsutils-linux/../libnvpair1linux/changelog.Debia
Ok. I stand corrected.
I reinstall of libnvpair1linux _did_ fix it. (After removing zfs-doc.)
# apt-get install --reinstall libnvpair1linux
# ls -l /usr/share/doc/libnvpair1linux/
total 76
-rw-r--r-- 1 root root 1615 jul 12 16:36 changelog.Debian.gz
Move along.. nothing to see here.
--
You r
[~ozdror] / [~andraz313]:
> but cant apply the fix mentioned same write error
You cannot sudo echo to a file. The opener of the file is still regular-
user.
Try either:
sudo sh -c 'echo deep > /sys/power/mem_sleep'
Or:
echo deep | sudo tee /sys/power/mem_sleep >/dev/null
(P.S. Looks
Related to https://lkml.org/lkml/2019/10/3/862 ? (That rervert is _not_
in ubuntu linux 4.15.0-66.)
--
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/1849178
Title:
upgrading linux-image pa
BIOS Setup: Settings -> System Configuration -> Thunderbolt(tm) Adapter
Configuration:
[x] Enable Thunderbolt(tm) Technology Support
[ ] Enable Thunderbolt(tm) Adapter Boot Support
[ ] Enable Thunderbolt(tm) Adapter Pre-boot Modules
(x) Security level - User Authorization
I have/had no dev
Ok, rebooted and verified that Thunderbolt was enabled. Both pm-suspend
and lid-closing now works as intended.
Dec 25 23:35:41 walter-tretton kernel: [ 53.790125] Suspended for
135.895 seconds
LGTM :okay_hand:
--
You received this bug notification because you are a member of Kernel
Packages,
Ah..
$ gcc -I /usr/include/efivar 1.c -lsmbios_c
In file included from /usr/include/smbios_c/config/get_config.h:36:0,
from /usr/include/smbios_c/compat.h:27,
from /usr/include/smbios_c/smi.h:22,
from 1.c:22:
/usr/include/smbios_c/config/compiler/
No, because it won't install.
I tried "fwupdmgr install eac3961ba9bd466f6e34d9276c27d524395d7c3c-
NN1TN_NVM21.00.cab", but I got:
could not find thunderbolt device at
/sys/devices/pci:00/:00:1c.0/:01:00.0/:02:00.0/:03:00.0/domain0/0-0
So I rebooted with Thunderbolt enabled.
(And indeed, no suspend, it was waking/sleeping during the entire 1.5h it was
"suspended" just now.
$ dmesg | grep 'PM.*Preparing system for sleep' | wc -l
115)
Hi Mario, do you mean this?
$ fwupdmgr get-devices
Intel AMT (unprovisioned)
DeviceID: /dev/mei
Guid:
Additional info:
- if I use pm-suspend, it just refuses to suspend (after 20secs wait)
[ma dec 25 18:33:49 2017] PM: Preparing system for sleep (mem)
...
[ma dec 25 18:33:49 2017] thunderbolt :03:00.0: Ignoring mailbox command
error (-110) in icm_suspend
[ma dec 25 18:33:49 2017] PM: Some d
Hi there,
I upgraded to Ubuntu Artful the other day, and today I updated the Dell
BIOS (using the GUI tools).
Out of curiosity, I went back to check this: re-*enabling* Thunderbolt
in the BIOS *still* *breaks* *suspend*.
Again "Some devices failed to suspend, or early wake event detected".
dmid
Disabling Thunderbolt support in the BIOS (F2 during boot) worked for
me.
Suspend works.
Don't know when/if I'll need the Thunderbolt. This works for now.
Thanks!
Can I provide any additional info to help you debug/fix this properly?
Cheers,
Walter
Before disabling Thunderbolt:
[ 4694.66762
Uptime is now 13 days. I think we can close this one as "fixed by
4.4.0-79-generic".
--
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/1691741
Title:
Execute NX-protected page - 4.4.0-78-ge
Update: running 4.4.0-79-generic on the original machine with issues for
24hrs (normal workload) without kernel panics thusfar. *Crosses fingers*
--
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
The docker1-tcn machine with vanilla kernel 4.4.70 is still up.
And on another (abmfn-staging) machine with 4.4.0-78 I've seen the
crash. According to dmesg output in the console, btrfs and other fs
modules were loaded. Probably due to an update-grub call.
After restart, I ensured that those modu
Okay. So we've been running 4.4.70 now for 22 hours and counting on
docker1-tcn.
/var/crash# uptime
09:45:30 up 22:25, 1 user, load average: 0,01, 0,02, 0,00
/var/crash# uname -a
Linux ossoio-docker1-tcn 4.4.70-040470-generic #201705251131 SMP Thu May 25
15:34:16 UTC 2017 x86_64 x86_64 x86_64
Okay. On a different machine with different load, we've now got the same
problem:
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-78-generic
DUMPFILE: dump.201705300948 [PARTIAL DUMP]
CPUS: 4
DATE: Tue May 30 09:48:05 2017
UPTIME: 01:47:38
LOAD AVERAGE: 0.05, 0.06, 0.04
So, I tried to revert the backing_dev_info changes and dpkg-built an
updated kernel. But that didn't work out. Either because it isn't the
cause, or because I reverted too much or too little.
After several hours of normal-load uptime, a removal of the mysql data
dir quickly caused a panic. I did n
I could be on a wild goose chase here.
But one of the prominent changes between 77 and 78 is the
backing_dev_info element of the queue turning into a pointer.
Part of the "bdi" changes in this bit:
++ * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
++4.4.0-47-gene
Crash info appears the same:
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-78-generic
DUMPFILE: dump.201705191443 [PARTIAL DUMP]
CPUS: 4
DATE: Fri May 19 14:43:31 2017
UPTIME: 00:43:02
LOAD AVERAGE: 2.53, 1.81, 2.56
TASKS: 544
NODENAME:
RELEASE: 4.4.0-
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1691741
Title:
Execute NX-protected page - 4.4.0-78-generic - kernel p
Well. That did not go so well: there were no ZFS modules in the builds.
We've tried all of:
* http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-vivid/linux-
image-3.19.8-031908-generic_3.19.8-031908.201505110938_amd64.deb
* http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.68/linux-
image-4
> Does the panic stop happening if you boot back into -77?
Yes. It's now running fine for more thant 3 hours now on -77.
Observe that we have upgraded more than one machine to -78, and only one
machine has trouble.
> Would it be possible for you to test the latest upstream stable kernel?
Ah, y
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1691741
Title:
Execute NX-protected page - 4.4.0-78-generic - kernel p
24 matches
Mail list logo
