** Tags added: hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu.
https://bugs.launchpad.net/bugs/1881701
Title:
NVIDIA cards should have set AllowExternalGpus in
/usr/share/X11/xorg.conf.d/
I think the bug is still present upstream following more thorough usage.
It seems sensitive to ambient light levels; using the computer in a
darkened room (night) causes more intense and regular symptoms. It seems
related to a bug I swear I filed a few years ago but didn't get any
traction with, bu
** Tags removed: kernel-fixed-upstream
** 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.
https://bugs.launchpad.net/bugs/1748678
Title:
Intel graphics timeout, possibly caused wif
Yes, this appears to be either a Firmware or Hardware issue. I have
managed to get everything working via a process of removing other PCIe
devices until it worked in Windows and running a firmware update at that
point before putting all the other devices back. It's working correctly
now.
** Change
Public bug reported:
[0.994565] thunderbolt :09:00.0: enabling device ( -> 0002)
[0.994957] thunderbolt :09:00.0: NHI initialized, starting thunderbolt
[0.994961] thunderbolt :09:00.0: allocating TX ring 0 of size 10
[0.994983] thunderbolt :09:00.0: allocating R
Further, I've managed to cause two system lock-ups, which I do not have
logs for because the lock-ups were so severe that the logging system
didn't record the kernel logs before death. I therefore cannot attribute
those two lockups to this issue for now. I've set-up netconsole now to
try to gather
I've tentatively marked it as fixed upstream, but as the bug occurs
sporadically I might not have tested long enough to recreate the
conditions which trigger the bug. I don't have reliable reproduction
steps (read: any steps) so I will continue testing the upstream kernel
in case I do hit it.
** T
** Description changed:
My wifi network device stopped responding, unable to list any local wifi
networks, which required turning off the adapter in settings and back-on
again. while investigating I found the following in the dmesg output
from the time the network device stopped responding
Public bug reported:
My wifi network device stopped responding, unable to list any local wifi
networks, which required turning off the adapter in settings and back-on
again. while investigating I found the following in the dmesg output
from the time the network device stopped responding. This is t
this is mentioned on the LKML: http://www.spinics.net/lists/linux-
btrfs/msg49766.html
** Bug watch added: Red Hat Bugzilla #1287508
https://bugzilla.redhat.com/show_bug.cgi?id=1287508
** Also affects: linux via
https://bugzilla.redhat.com/show_bug.cgi?id=1287508
Importance: Unknown
Thank you for taking the time to report this bug and helping to make Ubuntu
better. I believe you were right to file this under bluez, so I've reassigned
it back there. While waiting for someone to take a look, please execute the
following command, as it will automatically gather debugging infor
@rushack: if the problem truly is the same as this issue tracks then the
only solution is to turn off the IOMMU feature of your BIOS settings.
unfortunately this means that any software that relies on IOMMU (mostly
KVM or Xen) will fail to provide the features it supplies.
IOMMU is mainly used to
12 matches
Mail list logo
