Confirmed, my system boots fine when that second monitor isn't plugged
in. I removed the bluetooth driver as well, but that didn't fix it.
This is the adapter I'm using (I believe):
https://us.amazon.com/NiaoChao-Adapter-Charging-Compatible-MacBook/dp/B08CRXD22M
I have a bunch of USBC / HDMI
I'm seeing the same thing with 20.04 when running any of the 5.13
kernels. Last tested with 5.13.0-41.
My setup is an ASUS Hero XIII motherboard. Monitor plugged in, with a
second monitor plugged in via a USB / HDMI adapter (not sure if that is
relevant)
I had to remove iwlwifi-ty-a0-gf-a0.pnvm
Why was this set invalid? The change in
/etc/modprobe.d/audio_powersave.conf seems more of a work-around than a
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/1885462
Title:
Follow-up to #2 (again, please note I am NOT the originator of this
report).
Searching through some old notes/logs, I found the attached information
about _my_ WiFi H/W (excerpted and slightly redacted because I have not
checked the complete notes/logs for sensitive information). Abbreviated
NOTE: I am NOT the originator of this bug report,
but have a similar(? identical?) problem.
My machine is an Acer Aspire E17 E5-722-425Q,
and the built-in microphone (and also the mouse pad)
has never(?) been detected. (Since I use a USB mouse
and a USB headset-with-microphone, neither
Make sure your unit really is an r8169, and not an r8168.
Whilst (as I understand it) the r8169 module is supposed
to work with an r8168, at least on my laptop (Acer Aspire E17
(E5-722-425Q), currently 18.04 (up-to-date)),
using the r8169 module has resulted in "flakely" behaviour
for as long as
Still happening on 4.16.6 kernel for me.
--
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/1550779
Title:
[i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
Status in linux package
For me this manifests in lockups. The hardware buttons on my laptop
still work, fans etc. but xorg basically hard locks (Kernel 4.15.12).
There is no monitor in play.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
For me this manifests in lockups. The hardware buttons on my laptop
still work, fans etc. but xorg basically hard locks (Kernel 4.15.12)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This still occurs for me on kernel 4.15.12.
--
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/1550779
Title:
[i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
Status in linux
I have experienced this bug on a non Ubuntu system for some time. I
spent some time comparing the SparkLAN DPO driver source with the main
line kernel driver source and tried a couple of changes.
1) There were some places missing a lock (this change did not affect this bug,
however).
2) The DPO
The patch is now upstream in 4.4.20 and 4.7.3, both released on 7th of
September.
>From what I know, it's not in the Ubuntu kernels yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This seems to be a problem in ESXi, it was promised to be fixed in 6.0
Update 3 which hasn't been released as of yet.
However there is now a workaround patch that will make it to 4.4 and 4.7
stable trees:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-
queue.git;a=summary
Reported to Thomas Gleixner and linux-kernel:
https://lkml.org/lkml/2016/7/23/93
Jiang Liu is no longer reachable under the address specified in
MAINTAINERS: "Recipient address rejected: User unknown in virtual
mailbox table".
--
You received this bug notification because you are a member of
Also, the bug is present in 4.7-rc7.
--
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/1581777
Title:
igb transmit queue times out
Status in linux package in Ubuntu:
Confirmed
Bug
** Attachment added: "Bisect for bug"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581777/+attachment/4703544/+files/Bisect.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: kernel-bug-exists-upstream-4.6-rc7 needs-bisect
** Tags added:
52f518a3a7c2f80551a38d38be28bc9f335e713c is the first bad commit
Full bisect log attached.
A couple of notes:
1. Often the bug is not reproduced the first time the system is booted
with a given kernel version. Subsequent boots reproduce the bug.
2. In order to get bootable kernels from commit
Bug reported to Intel Ethernet Driver mailing list:
http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-
Mon-20160516/005444.html
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Tested with latest mainline kernel (linux-
image-4.6.0-040600rc7-generic), problem persists, appropriate tag added.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Using an Intel I210AT built-in PCI-E NIC passed through from the ESXi 6
host to an Ubuntu 16.04 server virtual machine. Network is unusable due
to constant "transmit queue 0 timed out" errors.
Issue is NOT present on a 14.04.4 machine running "3.19.0-59-generic
The bug appears to be a crash when unloading the vdpau library, either
via a dl_close() or dl_fini() call. It also affects any application
using the vdpau library, such as mplayer and mythfrontend.
A backtrace from mythfrontend follows:
mythfrontend crash details:
*** Error in
21 matches
Mail list logo
