[Bug 1906449] Re: [nvidia] [amdgpu] Xorg randomly freezes
Same problem here. Reproducable by switching virtual terminals a few times with . The only thing the system responds to is a ping (but no ssh) and a REISUB. This only happens to me on kernel 5.4.0-56-generic. If I revert to the previous kernel, 5.4.0-54-generic, the freeze does not happen. After every freeze journalctl always shows a SIMD error that seems to cause the freeze. Below are two examples: dec 03 17:23:05 zen kernel: simd exception: [#1] SMP NOPTI dec 03 17:23:05 zen kernel: CPU: 5 PID: 1195 Comm: Xorg Tainted: G OE 5.4.0-56-generic #62-Ubuntu dec 03 17:23:05 zen kernel: Hardware name: Micro-Star International Co., Ltd. MS-7C52/B450M-A PRO MAX (MS-7C52), BIOS 3.40 01/22/2020 dec 03 17:23:05 zen kernel: RIP: 0010:CalculateDelayAfterScaler.constprop.0+0xb2/0x320 [amdgpu] dec 03 17:23:05 zen kernel: Code: 10 45 b0 f2 45 0f 59 84 24 08 0d 00 00 f2 44 0f 5e 45 d0 f2 48 0f 2a c8 f2 0f 59 c8 66 0f ef c0 f2 41 0f 5a 84 24 60 17 00 00 41 0f 5e c8 f2 0f 5c 4d c8 f2 0f 5a c9 e8 7b df f7 ff f2 0f 10 dec 03 17:23:05 zen kernel: RSP: 0018:a135419cf708 EFLAGS: 00010202 dec 03 17:23:05 zen kernel: RAX: 3c00 RBX: 0002 RCX: dec 03 17:23:05 zen kernel: RDX: 0001 RSI: RDI: 8e2cb16c1f38 dec 03 17:23:05 zen kernel: RBP: a135419cf780 R08: 0002 R09: 0f00 dec 03 17:23:05 zen kernel: R10: 0001 R11: 8e2cb16c53b8 R12: 8e2cb16c1f38 dec 03 17:23:05 zen kernel: R13: R14: R15: 0001 dec 03 17:23:05 zen kernel: FS: 7f43ee050a80() GS:8e2d6e94() knlGS: dec 03 17:23:05 zen kernel: CS: 0010 DS: ES: CR0: 80050033 dec 03 17:23:05 zen kernel: CR2: 7fc926c8b3e0 CR3: 0007e605 CR4: 00340ee0 dec 03 17:23:05 zen kernel: Call Trace: and dec 04 06:53:51 zen kernel: simd exception: [#1] SMP NOPTI dec 04 06:53:51 zen kernel: CPU: 0 PID: 5889 Comm: kworker/0:2 Tainted: G OE 5.4.0-56-generic #62-Ubuntu dec 04 06:53:51 zen kernel: Hardware name: Micro-Star International Co., Ltd. MS-7C52/B450M-A PRO MAX (MS-7C52), BIOS 3.40 01/22/2020 dec 04 06:53:51 zen kernel: Workqueue: events console_callback dec 04 06:53:51 zen kernel: RIP: 0010:CalculateDelayAfterScaler.constprop.0+0xb2/0x320 [amdgpu] dec 04 06:53:51 zen kernel: Code: 10 45 b0 f2 45 0f 59 84 24 08 0d 00 00 f2 44 0f 5e 45 d0 f2 48 0f 2a c8 f2 0f 59 c8 66 0f ef c0 f2 41 0f 5a 84 24 60 17 00 00 41 0f 5e c8 f2 0f 5c 4d c8 f2 0f 5a c9 e8 7b df f7 ff f2 0f 10 dec 04 06:53:51 zen kernel: RSP: 0018:ad2c42a77618 EFLAGS: 00010202 dec 04 06:53:51 zen kernel: RAX: 0f00 RBX: 0002 RCX: dec 04 06:53:51 zen kernel: RDX: 0001 RSI: RDI: 9e845b851f38 dec 04 06:53:51 zen kernel: RBP: ad2c42a77690 R08: 0002 R09: 0f00 dec 04 06:53:51 zen kernel: R10: 0001 R11: 9e845b8553b8 R12: 9e845b851f38 dec 04 06:53:51 zen kernel: R13: R14: R15: 0001 dec 04 06:53:51 zen kernel: FS: () GS:9e852e80() knlGS: dec 04 06:53:51 zen kernel: CS: 0010 DS: ES: CR0: 80050033 dec 04 06:53:51 zen kernel: CR2: 55d78231afd0 CR3: 000724648000 CR4: 00340ef0 dec 04 06:53:51 zen kernel: Call Trace: dec 04 06:53:51 zen kernel: dml20v2_ModeSupportAndSystemConfigurationFull+0x403f/0x5d60 [amdgpu] dec 04 06:53:51 zen kernel: dml_get_voltage_level+0x127/0x200 [amdgpu] dec 04 06:53:51 zen kernel: dcn20_fast_validate_bw+0x376/0xaf0 [amdgpu] dec 04 06:53:51 zen kernel: dcn20_validate_bandwidth_internal+0xaf/0x290 [amdgpu] dec 04 06:53:51 zen kernel: ? resource_build_scaling_params+0x709/0x9c0 [amdgpu] dec 04 06:53:51 zen kernel: dcn20_validate_bandwidth+0x31/0x100 [amdgpu] dec 04 06:53:51 zen kernel: dc_validate_global_state+0x260/0x2d0 [amdgpu] dec 04 06:53:51 zen kernel: ? drm_modeset_lock_all_ctx+0xd9/0xe0 [drm] dec 04 06:53:51 zen kernel: amdgpu_dm_atomic_check+0x60c/0x860 [amdgpu] dec 04 06:53:51 zen kernel: drm_atomic_check_only+0x2b1/0x450 [drm] dec 04 06:53:51 zen kernel: drm_atomic_commit+0x18/0x50 [drm] dec 04 06:53:51 zen kernel: drm_client_modeset_commit_atomic+0x1d0/0x1f0 [drm] dec 04 06:53:51 zen kernel: drm_client_modeset_commit_force+0x55/0x160 [drm] dec 04 06:53:51 zen kernel: drm_fb_helper_pan_display+0xcf/0x230 [drm_kms_helper] dec 04 06:53:51 zen kernel: fb_pan_display+0x8c/0x110 dec 04 06:53:51 zen kernel: bit_update_start+0x20/0x50 dec 04 06:53:51 zen kernel: fbcon_switch+0x380/0x550 dec 04 06:53:51 zen kernel: redraw_screen+0xfe/0x270 dec 04 06:53:51 zen kernel: complete_change_console+0x3f/0xe0 dec 04 06:53:51 zen kernel: change_console+0x55/0x90 dec 04 06:53:51 zen kernel: console_callback+0x178/0x190 dec 04 06:53:51 zen kernel: ?
[Bug 1679488] Re: Thunar freezes when left inactive for a while
Cool, fixed at last :) So when will is this patch going to hit my machines ? Cant find it in the repo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679488 Title: Thunar freezes when left inactive for a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1679488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679488] Re: Thunar freezes when left inactive for a while
I am using Thunar 1.6.11 on Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial Thunar still freezes on a daily basis. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679488 Title: Thunar freezes when left inactive for a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1679488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679488] Re: Thunar freezes when left inactive for a while
Thunar 1.6.11 hangs (Xubuntu 16.04.2), mainly after doing a user switch and back again. No SSD, no QtCreator nor a physical external drive involved. This is what happens, reproducably: User A ( home directory on an internal ext4 partition ) opens two Thunar windows. Then user B logs in ( home directory on a LUKS volume, not a LUKS partition but a file on a normal ext4 partition ) and also starts Thunar. Then user B logs out again and upon return to the user A session both Thunar windows hang. This started around the end of febuary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679488 Title: Thunar freezes when left inactive for a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1679488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1441253] Re: hanging suspend job prevents shutdown
I think it is related to the monstrosity called systemd. Using this command to suspend solves all suspend/resume problems here echo mem> /sys/power/state I guess this command directly tells the kernel to suspend, without relying on buggy systemd crap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441253 Title: hanging suspend job prevents shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1441253] Re: hanging suspend job prevents shutdown
Same problem here. Xubuntu 14.04 through 16.04. Suspend, reboot, shutdown. All fail in some or other way on all the above versions. On 16.04: shutdown -h now Failed to start poweroff.target: Transaction is destructive. and systemctl suspend fails because a suspend process is already in progress. If I kill this process, the machine suspends immediately but is unusable after power on ( black screen or no networking etc ). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441253 Title: hanging suspend job prevents shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1238678] Re: Double suspend to ram and system malfunction after 2nd sleep.
Aloha, is there anybody in there. It is April 2016. The problem started after 12.04. That is 4 years and 2 LTS releases ago. OpenSUSE does not have this problem. Is there antbody in there ? Does anybody ever actually read these bug reports ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1238678 Title: Double suspend to ram and system malfunction after 2nd sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1238678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 528798] Re: Firefox menus unresposive, output Usage:program_name [address][:port]
This problem is years old now . It was reported in 2010. It took three (3) whole years before it got 'confirmed'. Now that was more than a year ago. Is their any chance of this being 'solved' or 'diagnosed' or something promising like that in the years to come ? Or is to remain 'confirmed' forever. In the meantime rebooting crappy Ubuntu Linux machines multiple times a day because that is the only temporary 'solution' to this 'confirmed' problem. The problem is not caused by /etc/hosts nor by addons nor an old profile. Even with a fresh install of Firefox and a completely new profile without addons the problem persists. The problem occurs on Xubuntu 12.04. ( I'm back on 12.04 and skipping 14.04 because of the huge number of bugs and problemes in that release ). I used to actually promote Ubuntu and Linux. Can't really remember why actually, the reason must be buried under a the accumulated mountain of frustration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/528798 Title: Firefox menus unresposive, output Usage:program_name [address][:port] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/528798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
