Hello, I have not forgotten about this.
1.) Does not exist.
2.) I've already reported.
I will have to apply the patch outlined in 3.) and cause the crash
again. However, this system uses an SD card, and the first system had a
corrupted boot partition after crashing a series of times. This
Is this covered by https://github.com/raspberrypi/linux/issues/3162 ?
** Bug watch added: github.com/raspberrypi/linux/issues #3162
https://github.com/raspberrypi/linux/issues/3162
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Verified the fix works on eoan with my 9360 running kernel 5.3.0-25
proposed. Updated the tag. Hope I did this right :S
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is
Present on 19.04 Disco Dingo with kernel:
Linux 5.0.0-11-generic #12-Ubuntu SMP Thu Apr 11 16:41:13 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
Errors in dmesg show:
[1.116542] Loading compiled-in X.509 certificates
[1.117339] Loaded X.509 cert 'Build time autogenerated kernel key:
Fixed with:
Section "Files"
ModulePath "/usr/lib/x86_64-linux-gnu/xorg"
ModulePath "/usr/lib/xorg/modules"
EndSection
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
Same issue with Xubuntu 18.10 Cosmic and nvidia-driver-415.
** Tags added: bionic cosmic nvidia
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1757202
Title:
i am also seeing this. In my case:
thermal thermal_zone3: failed to read out thermal zone (-61)
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.10
Release:18.10
Codename: cosmic
$ uname -a
Linux w00t 4.18.0-14-generic #15-Ubuntu SMP
I'd also like to mention that my system was a clean 18.04 install.
Also, would it be beneficial if I added my system info somehow? If so,
is there a way to add the same type of info Doug added without
generating a whole new bug report with say "ubuntu-bug linux"??
--
You received this bug
Ubuntu does not appear to be the only one with this issue on the 4.15 kernel:
https://bugzilla.redhat.com/show_bug.cgi?id=1551605
--
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/1781016
Same here. Not sure when this started:
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename: bionic
~$ uname -a
Linux w00t 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64
x86_64 x86_64
So this is now broken 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/1728238
Title:
update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware
fails to load
Status
And to clarify when I ran:
sudo update-initramfs -u -v -k all|grep kbl
The first round of firmware files is for 4.15.0-21-generic while the
second listing is for your patched kernel. Notice the added GuC entry.
As you can see the GuC firmware loads when running your patched kernel.
Thank you
@jsalisbury This does indeed fix the issue:
~$ sudo update-initramfs -u -v -k all|grep kbl
Adding firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin
Adding firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin
/usr/sbin/iucode_tool: system has processor(s) with signature 0x000806e9
@mtvoid Thank you for clearing that up. I was not aware that Broxton
was Atom. For some reason I thought it was an earlier generation x64
Core architecture.
@jsalisbury I am running Bionic. I've never tested a kernel before, but
am willing to do so.
--
You received this bug notification
Are they aware the same issue appears to be happening with the Broxton
firmware as well? Should that be tracked under a separate issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm not seeing this spammed in dmesg. Only maybe once per boot, but I'm
seeing the following on my 9360 running Ubuntu 17.10:
[ 4649.396767] pcieport :00:1c.4: AER: Corrected error received: id=00e4
[ 4649.396784] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected,
type=Data Link
I'm seeing something slightly different. MokListRT vs dbx list. Is it
the same issue?
[1.066401] Couldn't get size: 0x800e
[1.066403] MODSIGN: Couldn't get UEFI MokListRT
[1.066728] zswap: loaded using pool lzo/zbud
--
You received this bug notification because you are
[ 6283.204650] pcieport :00:1c.4: AER: Corrected error received: id=00e4
[ 6283.204661] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected,
type=Data Link Layer, id=00e4(Transmitter ID)
[ 6283.204671] pcieport :00:1c.4: device [8086:9d14] error
status/mask=1000/2000
[
Just now experiencing this on Ubuntu 17.10. Never saw this before.
Dell XPS 13 DE 9360 w/ Kabylake CPU.
** Tags added: 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/1521173
Hello, I just started seeing this on Ubuntu 17.10.
** Tags added: 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/1556419
Title:
nf_conntrack: automatic helper assignment is
nf_conntrack: default automatic helper assignment has been turned off
for security reasons and CT-based firewall rule not found. Use the
iptables CT target to attach helpers instead.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Not sure if using dkms, but if so may be related to bug 1515513
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1515363
Title:
/boot full could be handled more gracefully? --
Not sure if using dkms, but if so may be related to bug 1515513
--
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/1690817
Title:
Believe boot partition became filled
Status in linux
*** This bug is a duplicate of bug 1539826 ***
https://bugs.launchpad.net/bugs/1539826
Marked as dup per reporter's comment #3
** This bug has been marked a duplicate of bug 1539826
initramfs-tools hook-functions error causes failure
--
You received this bug notification because you are
/usr/share/pulseaudio/alsa-mixer/paths/analog-input-headphone-mic.conf
I just found this from a separate bug thread. This looks interesting.
The options for volume are:
volume = ignore | merge | off | zero |
# What to do with this volume: ignore it, merge it into the device
# volume slider,
I still haven't figured out how Pulse determines the default levels it
forces upon the user at each start of the service. I think it should
respect those levels set within ALSA/the system. If Pulse can't respect
selected values, then I'd like to know where it gets its default values.
That way I
@vanvugt I do have both cable types (with and without cable mic). In
testing the Quiet Comfort 15s:
Bose CQ 15 w/ normal cable - The hiss is present with 0 dB headphone mic
gain, but far more reduced than the Sony earbuds. It is almost
unnoticeable. If I weren't trying to hear it, I'd miss
Out of curiosity I tried my Bose Quiet Comfort 15s, and I can't detect
the hiss in those at either a dB gain of 0.00 or 10.00 with the
headphone mic boost.
That is odd.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I would like to say I have plain old Sony earbuds, and the sound is very
noticeable without playing any sound what so ever. As previously
mentioned, upping the dB gain on the headphone mic boost from 0.00 to
10.00 completely stops the hissing for whatever reason.
Also, the Arch Linux wiki has
Here's an earlier bug report (~Dec 2015):
http://lkml.iu.edu/hypermail/linux/kernel/1512.1/02819.html
--
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/1654448
Title:
XPS 13 9360, Realtek
** No longer affects: dell-sputnik
--
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 files left behind
Status in dkms package in Ubuntu:
** Also affects: initramfs-tools
Importance: Undecided
Status: New
** Project changed: initramfs-tools => dell-sputnik
--
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
** Description changed:
One notices *.old-dkms files being left behind still sitting on the disk
after purging the related kernel. This can cause /boot to become full,
and when it gets really bad, even sudo apt-get autoremove won't fix the
problem - only deleting the old-dkms files
Will the fix be included in Zesty or Artful?
** Tags added: artful yakkety
--
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 files left behind
** Tags added: xenial
** Also affects: bluez
Importance: Undecided
Status: New
** Project changed: bluez => dell-sputnik
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1651433
** Also affects: linux
Importance: Undecided
Status: New
** Project changed: linux => dell-sputnik
--
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/1687397
Title:
Kernel freeze
** Also affects: linux
Importance: Undecided
Status: New
** Project changed: linux => dell-sputnik
--
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/1663020
Title:
When I
** Tags added: hwe xenial
--
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/1634449
Title:
Black flicker when leaving monitor
Status in linux package in Ubuntu:
Triaged
Bug
** Tags added: zesty
--
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 files left behind
Status in dkms package in Ubuntu:
Confirmed
Status in
Ok...For anyone with a Dell XPS 13 9360 who experiences an issue like
this:
So I decided to purge and reinstall DKMS:
sudo apt-get purge dkms
BUT that removes all the following:
dkms hid-multitouch-dkms intel-hid-dkms intel-vbutton-dkms oem-audio-
hda-daily-dkms virtualbox-dkms
I purged, then
I'm seeing this in 16.04.2 LTS.
During dist-upgrade I see:
Error! Could not locate dkms.conf file.
File: does not exist.
I too have been having VBox issues, such as locking up my system.
$ sudo apt-cache policy virtualbox dkms
virtualbox:
Installed: 5.0.36-dfsg-0ubuntu1.16.04.2
Candidate:
For anyone who might find their way here while using newer versions of
Ubuntu such as 16.04 LTS, 16.10, 17.04...
This might be the solution. Worked for me:
https://github.com/blueman-project/blueman/issues/682
** Bug watch added: github.com/blueman-project/blueman/issues #682
Merged upstream :D
--
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 files left behind
Status in dkms package in Ubuntu:
Confirmed
Status in
I get this on my Dell XPS 13 9360:
$ uname -a
Linux blackhole 4.10.0-19-generic #21~16.04.1-Ubuntu SMP Fri Apr 7 08:20:02 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
** Tags added: xenial
--
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 files left behind
Status in dkms package in Ubuntu:
Confirmed
Status in
Also found this:
https://github.com/dell/dkms/issues/2
It's known upstream in debian and dkms, but whether dkms or initramfs-
tools should be responsible for cleaning up files left behind by
dkms...I dunno. What you posted sounded like it made sense to me.
I just wanted to note at least dkms
I too have a Dell XPS 9360, and I'm still experiencing this issue
running the latest 4.10 kernel on 16.04 LTS with HWE-Edge:
$ uname -a
Linux blackhole 4.10.0-14-generic #16~16.04.1-Ubuntu SMP Fri Mar 17 17:28:20
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I can confirm I have all the latest
This affects 16.04 LTS as well:
$ dkms --version
dkms: 2.2.0.3
--
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 files left behind
Status in
Might be causing/aggravating this issue with full /boot:
https://bugs.launchpad.net/ubuntu/+source/unattended-
upgrades/+bug/1357093
--
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
Debian Bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717584
--
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 files left behind
Status
*** This bug is a duplicate of bug 1283129 ***
https://bugs.launchpad.net/bugs/1283129
I am experiencing this issue every time I boot shortly after logging in
(~7 min). I'm on a physical intel machine, not a VM, running 14.04.2
LTS, kernel 3.13.0-53-generic
BUT I've also experienced this
51 matches
Mail list logo
