** Also affects: nvidia-drivers-ubuntu
Importance: Undecided
Status: New
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
Public bug reported:
Despite being this similar to an old bug 1625119, which was on a now
unsupported release, I asked on #ubuntu whether I should go for a new
bug and was directed to file this as a new bug.
I have an Asus NVidia RTX 3060. I am running:
Description:Ubuntu 22.04.1 LTS
16.04 is old at this point. I had a similar problem with Ubuntu 22.04, which
should be currently supported, and found a solution on that release. I am using
a fully patched system with nvidia-settings 510.47.03-0ubuntu1. It needs to be
able to write /etc/X11/xorg.conf when running as root when
For me initially I saw it when working with large office documents and
when attempting to do certain 1080p A/V playback. When it really got bad
I couldn't use a browser as it was happening all the time.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hmm so patches were effective for:
i5-8250U Kaby Lake R i.e. Gen 8
i9-9880H and i3-8100 both Coffee Lake Gen 9
It's hard enough debugging this directly on hardware. Doing it in a VM isn't
going to be helpful.
Which CPU models are still failing with 5.3.0-52.46 or 5.3.0-52.46+lp1861395v1?
--
To be clear 5.3.0-51 did NOT include the backported patches.
Proposed 5.3.0-52.46 had some and 5.3.0-52.46+lp1861395v1 had more.
Out of curiosity could the people who are still having hangs on the 5.3.0-52.46
proposed or 5.3.0-52.46+lp1861395v1 kernel have different generations of CPUs?
I've
I also had the issue on the 5.3.0-45 kernel but it happened once for 2 seconds
every two days.
It wasn't even noticeable unless you really looked for it. The 5.3 kernel
series seems to be a total write off at this point.
While it likely isn't allowed as a solution it might be less effort to
After it was pretty clear a stable kernel wasn't coming any time soon for 19.10
I gave up and took a dangerous leap. The only way I was going to get a 5.4
kernel was to move to 20.04.
It was dangerous and I had to get there through a do-release-upgrade -d. Highly
not recommended if you don't
I got about another 4 hrs before I had a 2nd hard crash with 5.3.0-52. I
once again could not shutdown or reboot and was forced to hit my reset
button. What a mess
Basically BT audio works until the connection stops. Pausing an audio
stream encourages the BT audio to unpair. The Audio sink
Here is the syslog content just before the hard crash on proposed 5.3.0-52 from
which I could not reboot and finally had to hit my reset button. Please note
this syslog extract contains a long string of UTF8 characters I had never seen
before in a syslog just before the crash where I had to hit
The lack of kernel stability here is really getting frustrating
With recent kernels audio playback over HDMI has stopped working for me
altogether.
I'm getting zero traction resolving it.
I get audio playback when I plug in a headset but short cables are preventing
use of that. Longer ones
Just an FYI for those trying to figure out what the heck is going on.
The fix related to this thread wasn't in 5.3.0-51.44.
>From the changelog, which is hard to find, the fix was committed in
>5.3.0-52.46 which is currently in eoan-proposed:
5.3.0-46-generic - i915 - frequent GPU hangs /
I thought 5.3.0-48.41+lp1861395v1 fixed it for me. I haven't logged a hang for
a very long time.
Now out of the blue my audio stopped working altogether. I tried rebooting into
5.3.0-51.44 and I still don't have audio but I'm not hanging with that either.
--
You received this bug notification
The test kernel 5.3.0-48.41+lp1861395v1 seems to be a major improvement!
On 5.3.0-45.37 pauses still happened rarely i.e. a single 2 second pause every
15 hrs and I hadn't noticed them until I was watching the logs for them.
5.3.0-46 and later were pausing several times a minute and the system
I wanted the security patches in 5.3.0-46.38 so I tried updating to the
kernel from proposed i.e. 5.3.0-47.39. Sadly hangs returned within a
couple minutes of trying to use the kernel.
# cat /sys/class/drm/card0/error | head -2
GPU HANG: ecode 9:0:0x, hang on rcs0
Kernel: 5.3.0-47-generic
For what it is worth I just downgraded my kernel to 5.3.0-45.37 and I haven't
had a hang since:
https://launchpad.net/ubuntu/+source/linux/5.3.0-45.37
Not clear at all from the change log as to what brought this on in 5.3.0-46.38:
https://launchpad.net/ubuntu/+source/linux/5.3.0-46.38
--
You
I just started having this issue on Ubuntu 19.10 w/ 5.3.0-46-generic. What a
mess...
My system is an Asrock Z370M-ITXax with an Intel i3-8100.
sudo cat /sys/class/drm/card0/error
GPU HANG: ecode 9:0:0x, hang on rcs0
Kernel: 5.3.0-46-generic x86_64
As if all my Intel NIC problems weren't
FYI in terms of sustainable options I was able to find a very hard to
find .deb with the latest driver as a DKMS module. It works fine for me
on Ubuntu 19.10. I really wish this was in a repository which was part
of universe but I'm never figured out how to do things like that.
# dpkg -l | grep
FYI a kernel bisection may be outside the skill set of your average user
and chances are much lower without detailed instructions. Please don't
shoot the messenger.
I too have a Asrock motherboard but a ASRock Z370M-ITX/ac. I had a lot
off trouble getting my I219-V NICs to behave on Ubuntu.
I
19 matches
Mail list logo
