Approaching the end of year 2019 and these bugs are still here. To make
matters worse users with crashing systems unrelated to these bugs are
falsely assuming they are the cause of the crash. When looking in
journalctl boot startup these are the first errors you see in RED
letters:
Nov 12 06:01:25
I've been using NVMe M.2 Samsung Pro 960 for 18 months and never had a problem.
Ubuntu 16.04.6 LTS, Kernel 4.14.114 LTS, Skylake 6700HQ, nVidia 970m
UEFI, GPT, AHCI (Intel Raid off), Secure Boot off
`/etc/fstab`:
UUID=b40b3925-70ef-447f-923e-1b05467c00e7 / ext4
errors=remount-ro
This bug has been reported a few times in Ask Ubuntu. Just today (July
3rd, 2019) I was going back through `dmesg` and by chance I noticed on
June 22nd, 2019 the errors appear about a dozen times.
I've been on the same kernel version 4.14.114 LTS for a couple/few
months now but I did flirt with ve
Same problem with Kernel 4.14.36: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.14.36/
Also I would suspect (but cannot confirm) that Kernel 4.16.4 will suffer
the same fate.
For the first time all three of these kernels (including OP's 4.17-rc2)
deviated from history where there were three `
I've experienced similar situations for years where when resuming from
suspend, the system immediately completes uncompleted sleep and then
wakes up. More of an annoyance and loss of a second or two of life than
anything else.
Today however the cycle has changed with advent of nVidia drivers. Now
It's a kernel issue.
Using Ubuntu 16.04.5 LTS with the 18.04.1 LTS's kernel `4.15.0-36` when
you try to suspend it resumes after a dozen seconds or so. If you use
kernel `4.13.0-36` the suspend/resume cycle is normal. I believe
`4.13.0-36` was released for Ubuntu 17.10 which I've never installed a
Hi
Kai-Heng Feng,
I presume you want me to try the 9 rc's in the `4.15` kernel chain? I
assume the 8 to 9 rc's in `4.13`, 4.14`, `4.16`, `4.17`, `4.18` and `4.19`
rc's don't have to be installed?
Also would it make sense to try the LTS kernel `4.14.78` first and see if
it's already been fixed? Th
@Kai-Heng Feng (kaihengfeng) just an update...
Suddenly my suspend totally broke down (wakes immediately from suspend)
using same kernel I had for a few months (outdated `4.13.0-36-generic`).
In order to update to newer kernels I had to install libssl1.1 to side-
step linux-header installation er
@@Kai-Heng Feng (kaihengfeng) Everything seems to be fixed for both this
old bug and for new problems I was having over last few days.
I found a bug report from 2010 (link in script below) and used this:
#!/bin/bash
# Original script was using /bin/sh but shellcheck reporting warnings.
# NAME:
@Ole and @Feng.
The normal methodology of `echo XHC > /proc/acpi/wakeup` had no effect
whether `enabled` or `disabled`. By default `enabled` and all others are
`disabled`.
I also have `tlp` defaults which is probably USB_AUTOSUSPEND.
I could go into console mode and type `pm_suspend` (it's set t
Reply to #22 (Timo Jyrinki):
I don't see why `tlp` is being singled out (although I do have it
installed since reporting the bug in Ask Ubuntu). I would think the
fault is more with `systemd` or perhaps Linux Kernel not understanding
how ACPI works properly. (Wild hunch). That said the results of
Confirm this bug occurs on Ubuntu 16.04 w/Alienware 17R3, i7 6700HQ,
HM170 chipset. The workaround to use `acpiphp.disable=1` on kernel
command line fixes suspend/resume cycle.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
Same error Ubuntu 16.04.3 LTS, kexec-tools apt-installed today, Kernel
4.12.2, Skylake HM170, nVidia GTX 970M, NVMe M.2 Gen 3x4 SSD:
$ sudo kexec -l /boot/vmlinuz-`uname -r` --initrd=/boot/initrd.img-`uname -r`
--reuse-cmdline
Unknown type (Reserved) while parsing /sys/firmware/memmap/15/type. Pl
Two years later and bug still lurking on this new (to me) laptop. Ubuntu
16.04, Kernel 4.4.0-101-generic, Skylake HM170, nVidia GTX970M, HD530
graphics, USB-C Thunderbolt3, NVMe M.2 Samsung Pro 960 SSD, etc.
3c:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac
Wireless Network Adap
Kai-Heng,
I was on Hardware stack for awhile but had problems with. Remember many
users opt out of HWE even though it's the default.
I was running 4.14.2 mainline but `kexec` was broken after 4.12 so I
dropped into 4.4.0-101 provided by Ubuntu to make `kexec` work properly.
I do have Ubuntu kern
Kai-Heng sorry I can't try it right away. I'm still struggling with
systemd's kexec-load@service to quicken reboot times as I struggle with
nVidia having HDMI sound turned off by default BIOS POST. In the
meantime I've blacklisted `ath10k_pci` and that appears to have saved
2-3 seconds off the boot
@Robert Focht `4.11.5` is fairly old and won't have Meltdown or Spectre
fixes. Do you mean `4.15.5`? Regardless see this link to get Skylake
through Kabylake drivers: https://askubuntu.com/questions/832524
/updated-kernel-to-4-8-now-missing-firmware-warnings
--
You received this bug notification
Error remains Dell based Skylake 6700HQ, HM170, nVidia 384.98, NVMe
Gen3x4 M.2 SSD, Ubuntu 16.04.3, Kernel 4.14.4:
Dec 12 19:08:16 alien kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace
lookup failure, AE_NOT_FOUND (20170728/dswload-210)
Dec 12 19:08:16 alien kernel: ACPI Exception: AE_N
Same bug as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407 and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690502
--
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/168
Same bug as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407 opened one
year earlier.
--
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/1690502
Title:
ACPI Error: [\_SB_.PCI0.X
#15 says problem went away but is on Kernel 4.4 and Kerne 4.8 where
message was "hacked" to not display. With kernels 4.9, 4.10, etc. the
message reappears as per bug report here:
https://bugzilla.kernel.org/show_bug.cgi?id=193531
#17 closing this bug based upon #15 should be reconsidered.
Also n
This bug effects 128 people and closing it because you don't like the
title feels wrong. Two Ask Ubuntu questions point to this Lanuchpad bug
report in the hopes it will be solved:
https://askubuntu.com/questions/757396/bluetooth-how-to-solve-not-
enough-free-handles-to-register-service-error
and
Complement to #56, Ubuntu 16.04.3, Kernel 4.14.4, journalctl -b:
Dec 13 20:44:33 alien bluetoothd[928]: Failed to obtain handles for "Service
Changed" characteristic
Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register
service
Dec 13 20:44:33 alien bluetoothd[928]: Error ad
@dmytriy--I suspect your suspend/resume problems are unrelated simply
because there are hundreds of different problems in that area. I suggest
searching Ask Ubuntu or Linux & Unix sites. For example, my Alienware
AW17R3 with i-7 6700HQ (Skylake) wouldn't suspend/resume because of NVMe
M.2 Gen 3.0 x
To make these annoying warnings go away I used:
$ sudo cp assembly/hello /lib/firmware/i915/kbl_dmc_ver1_01.bin
$ sudo cp assembly/hello /lib/firmware/i915/kbl_guc_ver9_14.bin
$ sudo cp assembly/hello /lib/firmware/i915/bxt_guc_ver8_7.bin
$ sudo update-initramfs -u
update-initramfs: Generating /b
The warnings applied to Kabylake before it was even released / sold. Anyway
a few days ago the drivers were released so you can fix the error for real.
See:
http://askubuntu.com/questions/832524/updated-kernel-to-4-8-now-missing-firmware-warnings
On Sat, Feb 18, 2017 at 9:48 PM, simon wrote:
> T
Trusty 14.04, Kernel 3.13.0-79 on Dell Inspiron 7720 17R SE Bios version
A16, 10/20/213 also crashes.
A couple of days ago (after Ubuntu 55MB and then 38MB automatic updates)
it started immediately Resuming after Suspend.
Regressing to 3.13.0-32 fixes Suspend. Closing lid or initiating from
syste
Christopher M. Penalver (penalvch) , Thank you for the advise. I'm
currently struggling to download a valid ISO to reinstall Win 7 smacked
by Intel RST. Using an earlier Kernel is not a big deal today. I assume
Gregg and his army of programmers will fix the Kernel within a couple of
Sundays. If fut
I'd like to delete my previous two comments because on a second Suspend
under 3.13.0-32 the laptop resumed immediately and led to a system crash
again. However I'm loath to delete what's already been written.
A few months whilst still running Windows 7 ago I changed the BIOS to
wake on USB activit
Under Trusty 14.04 LTS 3.13.0-24-generic the ss_en=0 option did not work
on first try. The file was created but it was empty. After using gksu
gedit blah blah blah on the file and manually putting the option in it
worked fine. Thank you very much at getting this annoying undocumented
feature (ol
Well it did work until I rebooted. The successful solution was to use
"sudo gedit /etc/rc.local" and insert the following commnands before the
last line which contains "exit 0":
rmmod ums_realtek
modprobe ums_realtek ss_en=0
Note "sudo" prefix isn't needed because rc.local runs with root
privile
Under Kernel 3.13 and 3.15.0-031500-generic the Toshiba hotkeys Fn+F6
and Fn+F7 to control screen brightness (Satellite L300) only work after
manually suspending through the system tray drop down menu and then
resuming. Note the Suspend Hotkey Fn+F3 only works after manually
suspending and resumin
Same issue on stock Dell Inspiron 17R SE 7720, Ubuntu 14.04 w/EnhanceIO
ssd caching, Win 7 w/Intel iRST ssd caching, Linux 3.17.4 kernel.
An hour of googling led to kernel parameter pci=nocrs without any change
except, clearing up the message "kernel: [0.211061] PCI: Ignoring
host bridge windo
Christopher,
Sorry for the long delay I had put the "no hotkeys on cold boot, on
suspend/resume only" problem on the back-burner while I solved higher
priority problems. I tried to file the apport bug report but my Kernel
versions (after house cleaning 8 older versions) are only 3.15.7 and
3.15.8
34 matches
Mail list logo
