I've applied the latest BIOS update from HP but this has not made any
difference to the problem. I've also verified the problem still exists
when running the 2.8.0-26-generic kernel from groovy.
I've also run the apport-collect requested above using that kernel.
** Changed in: linux (Ubuntu)
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433484/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433482/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433478/+files/Lsusb.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/1903292
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433479/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433489/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433483/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433490/+files/modified.conffile..etc.apport.crashdb.conf.txt
--
You received this bug notification because you are a member of Kernel
Packages, which
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433480/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433474/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433475/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433476/+files/Lspci.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/1903292
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433477/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: groovy staging
** Description changed:
I'm running 20.04 LTS on an HP Envy x360 Ryzen 7 3700U with Radeon Vega
Mobile. The gdm3 package is at version 3.36.3-0ubuntu0.20.04.2.
When I trigger a suspend with `echo mem > /sys/power/state` the system
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1903292/+attachment/5433473/+files/CRDA.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/1903292
I'm running a custom kernel build because when I installed Ubuntu on
this laptop (19.10) various things were not supported in the stock
kernel. I'm now trying to apply a BIOS update which apparently has some
ACPI-related stuff in it, but this is proving difficult as HP's BIOS
updates are somewhat
** Summary changed:
- High I am having issues on Xubuntu 20.04 revolving around WiFi
+ iwl3945: Low throughput on focal / Linux 5.4
--
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/1902421
*** This bug is a duplicate of bug 1897299 ***
https://bugs.launchpad.net/bugs/1897299
Linux version 5.4.0-48-generic (buildd@lcy01-amd64-010) (gcc version 9.3.0
(Ubuntu 9.3.0-10ubuntu2)) #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 (Ubuntu
5.4.0-48.52-generic 5.4.60)
dmesg shows repeat
>From CurrentDmesg.txt:
Linux version 5.4.0-45-generic (buildd@lgw01-amd64-033) (gcc version 9.3.0
(Ubuntu 9.3.0-10ubuntu2)) #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 (Ubuntu
5.4.0-45.49-generic 5.4.55)
[0.00] DMI: Acer Nitro AN515-44/Stonic_RNS, BIOS V1.01 04/16/2020
[Firmware Bug]:
** Changed in: linux-lts-utopic (Ubuntu)
Status: New => Invalid
--
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/1892890
Title:
The eggs were off and it hurts my belly.
Thanks for your great work. I have just verified that the kernel works
as it should.
I don't know if I am supposed to add a tag as well or how to do it.
Again, thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in
** Package changed: ubuntu => linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1888070
Title:
latest update freezes system on boot
Status in linux-meta package
It is my impression that specifying "mtrr_gran_size/mtrr_chunk_size" when
"mtrr_cleanup: can not find optimal value" is still useful on some systems.
The latest system where I helped identifying good values (according to
https://github.com/tomreyn/linux_mtrr_size_fix) was a
Gigabyte
Thanks for the bug report. I'm reassigning this to (the proper?) package
- calibre is an e-book library manager.
** Project changed: calibre => linux-meta (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Possibly related? https://bugzilla.kernel.org/show_bug.cgi?id=204343
** Bug watch added: Linux Kernel Bug Tracker #204343
https://bugzilla.kernel.org/show_bug.cgi?id=204343
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
"I/O error, dev sdb, sector 82830936 flags 0" would seem to suggest this
is a hardware error (physically defective storage media sdb), have you
ruled this out, yet?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
~esserre This is not the same bug - please report it separately (run
"ubuntu-bug linux").
--
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/1804577
Title:
ACPI BIOS Error (bug): Failure
Related links:
https://lore.kernel.org/patchwork/project/lkml/list/?series=419906=*
https://github.com/torvalds/linux/blob/master/drivers/platform/x86/hp-wmi.c
https://wiki.ubuntu.com/Kernel/Reference/WMI
https://lwn.net/Articles/391230/
** Bug watch added: Linux Kernel Bug Tracker #201981
I can confirm that I have applied the same patch to
4.15.0-76.86-generic. Without the patch my system failed as described
above. With the patch it seems to work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi,
I seem to have the same problem. I have no experience with linux kernels or bug
reports, but I am a computer engineer so with guidance I will be able to
contribute to debugging.
I am running "Ubuntu 4.15.0-46.49-generic 4.15.18" on an HP zbook the
lspci output is attached.
Both 4.15.0-72
Verified fix in proposed 4.15.0-71-generic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1843487
For me, the fix is to change line 812 of /usr/sbin/dkms from:
[ -z $kernels_module ] || return 0
to
[ -z $kernels_module ] && return 0
This was fixed upstream here:
https://github.com/dell/dkms/commit/b95779938805aca8e98d57492b18dee07d35d285
--
You received this bug notification
I'm still seeing this on Eoan, which has dkms 2.7.1-4ubuntu2 - the
symptom is that virtualbox-dkms does not correctly build and install its
kernel modules with the message `modinfo: ERROR: missing module or
filename.`
--
You received this bug notification because you are a member of Kernel
According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943569,
this is fixed in debian dkms=2.7.1-5.
** Bug watch added: Debian Bug tracker #943569
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943569
--
You received this bug notification because you are a member of Kernel
@Kamal yes this seems to fix it. I was able to run my device stress
test for over 15 minutes. With the bug I was lucky if I could make it
15 seconds.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Kamal thanks for the quick response. I tried the files you sent over
but it looks like I need some additional packages in order to rebuild my
kernel module for that kernel. I tried to tell modprobe to force load
my module built against 4.15.0-66 and it would not load it.
--
You received this
The commit for "uio: fix crash after the device is unregistered" in this
bug introduces another bug which is fixed upstream in the kernel. It
adds an illegal mutex_lock in uio_interrupt() in uio.c. This completely
breaks interrupt handling in UIO.
I opened the following bug to track this:
Switching back to lz4, now I don't get the error! Maybe it's the newest
kernel (.19 out today), or maybe it's just tweaking the decoding to gzip
and back? Very strange.
Booting lz4 again
Startup finished in 7.775s (firmware) + 7.947s (loader) + 2.136s (kernel) +
9.105s (userspace) = 26.965s
Is yours failing? Mine is displaying the error message with lz4, but
still booting and finding the root filesystem, that's what I thought
this bug is about. You must not be failing either, as you have a boot
time to measure. In the olden days, the other people who got this error
weren't able to
Boot lz4
Startup finished in 6.907s (firmware) + 8.338s (loader) + 2.595s (kernel) +
3.705s (userspace) = 21.547s
graphical.target reached after 3.695s in userspace
Boot gzip
Startup finished in 7.799s (firmware) + 8.070s (loader) + 3.562s (kernel) +
10.306s (userspace) = 29.739s
Boot lz4
Startup finished in 6.907s (firmware) + 8.338s (loader) + 2.595s (kernel) +
3.705s (userspace) = 21.547s
graphical.target reached after 3.695s in userspace
Will come back with gzip and see.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Summary changed:
- Intel wifi 3165 not working properly in Ubuntu 18.10
+ Intel wifi 3165 not working properly in Ubuntu 19.10
--
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/1848953
Related logs from journalctl -b:
os-prober[6348]: debug: running /usr/lib/os-probes/10zvol-test on /dev/sda5
os-prober[6351]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda5
50mounted-tests[6361]: debug: creating device mapper device
/dev/mapper/osprober-linux-sda5
kernel:
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1848496
Title:
[zfs-root] device-mapper: reload ioctl
Changing to gzip is bad. 19.10 switched over to lz4 because it's way
faster decompressing, which makes for faster boots!
--
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/1835660
Title:
As a potential workaround, please try to boot a current kernel (one that
was also tested to not work otherwise) with kernel parameter
sdhci.debug_quirks=32832 as per https://forums.xilinx.com/t5/Embedded-
Linux/Linux-Kernel-4-6-mmc-issue/td-p/727465
--
You received this bug notification because
** Description changed:
Running:
Bionic Beaver
Ubuntu 4.15.0-62.69-generic 4.15.18
In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
uio_interrupt. This results in a "scheduling while atomic" error if
someone else owns the mutex at the time it is invoked.
- [
The following commit in the kernel mainline fixes this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3d27c4de8d4fb2d4099ff324671792aa2578c6f9
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288071/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288075/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288068/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288063/+files/CRDA.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/1843487
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288074/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288066/+files/Lspci.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/1843487
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288070/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288065/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288072/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288069/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Running:
Bionic Beaver
Ubuntu 4.15.0-62.69-generic 4.15.18
In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
uio_interrupt. This results in a "scheduling while atomic" error if
someone
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288064/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288067/+files/Lsusb.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/1843487
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1843487/+attachment/5288073/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: bionic
--
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/1843487
Title:
UIO: mutex used in interrupt handler causes crash
Status in linux package in Ubuntu:
Incomplete
** Description changed:
+ Running:
+ Bionic Beaver
Ubuntu 4.15.0-62.69-generic 4.15.18
In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
uio_interrupt. This results in a "scheduling while atomic" error if
someone else owns the mutex at the time it is invoked.
[
Public bug reported:
Ubuntu 4.15.0-62.69-generic 4.15.18
In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
uio_interrupt. This results in a "scheduling while atomic" error if
someone else owns the mutex at the time it is invoked.
[ 1941.409212] BUG: scheduling while atomic:
@ovari: It's good that you contacted these mailing lists. Note, however,
that the developers subscribed to these lists are extremely overwhelmed
with e-mail. They will likely not respond to e-mails which do not
(concisely) state the actual issue by means of error messages, version
number and
Image referenced in comment 31 by _doom (duso315-gmail) - cropped + scaled down:
"mmc0: mmc_hs400_to_hs200 failed, error -84"
** Attachment added: "mmc0: mmc_hs400_to_hs200 failed, error -84"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/+attachment/5285942/+files/9q7jRYx.jpg
See comment 26 if you're still interested in seeing this fixed. After
sending mail there, be sure to mention it here, ideally with some kind
of reference (mailing list name and (message id) or (date and time of
message send, sender's e-mail address, subject line)) so others will not
send duplicate
** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1796443
Title:
HP EliteBook 745 G5 (Ryzen 2500U) fails
The "[drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel
modesetting." was also reported in bug 1837945 where kernel / boot
parameter "amdgpu.dc=0" worked around an otherwise boot to black screen.
There, however, Linux versions 5.1 and 5.2 would also not work with this
parameter set.
I'm still seeing this in 18.04 LTS.
Linux newt 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
I've attached dmesg output.
** Attachment added: "dmesg.save"
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1796443
Title:
HP EliteBook 745 G5 (Ryzen 2500U) fails
ing Xdiagnose version 3.8.8
Please help!
Tom.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: am
tion: Ubuntu 18.04.2 LTS. Release:
18.04
I am using Xdiagnose version 3.8.8
Please help!
Tom.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
ApportVe
@sfeole, checking with our devops folks. I don't have Azure access to
the hosts in question.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance never
It looks like people are resolving this by upgrading to latest Disco
with 5.0.0-1007.7 kernel?
We are on 18.04.1 LTS and having similar symptoms. Is there a fix in the
works for 18.04.1?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Eric: This issue should only affect Ubuntu running bare metal on Intel
systems, so not Ubuntu running in a VM. Put differently: if you do not
run Ubuntu as the primary operating system on this MacBook Pro then
please file a separate bug report, or (ideally beforehand) see if you
can get this
u 18.04.2 LTS. Release:
18.04
I am using Xdiagnose version 3.8.8
Please help!
Tom.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
ApportVersion: 2.20
OP had also tested this with linux-image-generic-hwe-18.04 / linux-
image-4.18.0-20-generic, where dmesg looked very similar to that of this
hwe-18.04-edge kernel.
Gabriele:
(1) Please do as discussed in comment 2.
(2) Please also re-run alsa-info as discussed at
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1831301
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1829620 ***
https://bugs.launchpad.net/bugs/1829620
Thanks for testing, Jackneill.
To explain, the "dis_ucode_ldr" option disables loading of microcode
updates by Linux. Microcode updates are are binary blobs (no source code
is available) which modify
Possible duplicate of bug #1829620.
--
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/1829402
Title:
Purple screen hangup during boot
Status in linux package in Ubuntu:
Confirmed
Bug
Diederik: Ubuntu 14.04 reached end of life, is no longer supported.
Max, and anyone else affected by this issue with identical symptoms as
Max on Ubuntu 16.04 with kernel 4.4.0-148, please consider testing this:
1. Add this to /etc/default/grub :
GRUB_GFXPAYLOAD_LINUX="text"
2. Add this to the
Please consider testing this:
1. Add this to /etc/default/grub :
GRUB_GFXPAYLOAD_LINUX="text"
2. Add this to the GRUB_CMDLINE_LINUX_DEFAULT option in /etc/default/grub :
earlyprintk=efi,keep
3. Run: sudo update-grub
4. Try all of the following combinations of kernel boot parameters by editing
Also, before you do the testing, please attach your current
/boot/grub/grub.cfg
/boot/efi/EFI/ubuntu/grub.cfg
files to this bug report. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Possibly related to bug 699802. See comments 24 and 101 for potential
workarounds.
If you'll test these, please test them thoroughly, doing multiple warm
and cold boots with each changed setting, since successful boots are
currently non-deterministic.
--
You received this bug notification
Thanks for filing this bug report, Jack.
I'm one of the IRC support volunteers who tried to help here, but I'm mostly
out of ideas.
As suggested on IRC, trying a mainline kernel may be a good idea (only if you
can still reproduce the issue).
I should mention that a "USB-C Triple-4K Dock"
I'm facing this issue in the latest kernel mainline, too.
CPU is an Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (which uses i915 graphics).
The graphic glitches were gone after some kernel update but the error messages
in dmesg remained.
--
You received this bug notification because you are a
Chris (~iplayfast): You're not running the latest HWE kernel image:
linux-image-generic-hwe-18.04 | 4.18.0.18.68 | bionic-updates
"cat /proc/version" would report:
Linux version 4.18.0-18-generic (buildd@lcy01-amd64-006) (gcc version 7.3.0
(Ubuntu 7.3.0-16ubuntu3)) #19~18.04.1-Ubuntu SMP Fri
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1824852
Title:
linux-firmware package not
** 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/1824546
Title:
Intel N3060 booting into black screen with 5.0 kernel
Status in linux package
This seems to be an issue with network namespaces, which I assume may
point to Linux. This report is about Ubuntu Kylin, a supported Ubuntu
flavor.
** Project changed: ubuntu-ubuntu-server => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which
Regarding Ubuntu 16.04's "xenial" GA kernel (4.4), I've been told that
the Kernel team ran into some issues with these and are now planning to
release them next week. As Brandon discussed, installing the 4.15
hardware enablement (HWE) kernel - as documented at
** 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/1818407
Title:
Cant access emmc, error -84
Status in linux package
We discussed this on IRC.
Linux reports (DMI) this is an: ASUSTeK COMPUTER INC. TP202NAS/TP202NAS, BIOS
TP202NAS.209 07/19/2018
This systesm' only internal storage which is not detected here (other than the
error messages quoted above) is a SanDisk DF4064 eMMC.
I recommend testing also with an
complement (sorry for multiple-comments):
$ dmesg | grep i915
[1.439662] i915 :00:02.0: vgaarb: changed VGA decodes:
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[1.439938] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin
(v1.27)
[1.443269] [drm] Initialized i915
Let me join this with the following `dmesg | tail`:
[Feb24 23:34] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe
A FIFO underrun
[Feb25 00:23] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe
A FIFO underrun
[Feb25 01:57]
Considering that this is a regression, with major impact (TTY login no
longer possible, often no graphical login either), many affected users
on (amongst other) the latest LTS release, and both this fact and how to
fix it has been known since at least January 30, I am puzzled as to why
this is
hi guys,
Well now, that is one old bug I reported.
The 'powerd down, remove battery, restart it all' workaround didn't quite fix
it for me but it was no big deal otherwise.
And since the laptop had died since then I have no problem if we close this bug.
cheers
Tom
--
You received this bug
Booted mainline rc2.
g
Jan 18 18:52:39 hatstand kernel: [5.902278] ipu3-cio2 :00:14.3:
enabling device ( -> 0002)
Jan 18 18:52:39 hatstand kernel: [5.903133] ipu3-cio2 :00:14.3: device
0x9d32 (rev: 0x1)
Jan 18 18:52:39 hatstand kernel: [5.906012] ipu3-cio2 :00:14.3:
101 - 200 of 535 matches
Mail list logo
