[Ubuntu-x-swat] [Bug 1794033]
I haven't encountered this issue at all since moving away from modesetting and back to the intel DDX driver. So whatever extra exercises GLAMOR was doing may be triggering the bug. I'm sure that doesn't help actually fix it but it might at least help people experiencing it to have a more stable desktop. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1794033 Title: i965: Failed to submit batchbuffer: Bad address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1794033]
(In reply to Mark Janes from comment #22) > Hmm...`cp` in xterm is a pretty clear indicator that this issue is random > and not triggered by a specific workload. > > Lionel suggested that it would be good to have a feedback from the kernel > about what didn't pass validation. > > There is a kernel option to generate debug traces for that but you have to > recompile your kernel with that option. Lionel, can you provide some > details? > > It would be a good data point to see if a much older kernel produces this > error (eg 4.9, 4.4). I can't deploy those kernels in Mesa i965 CI because > they lack features needed to run our Vulkan test suites. With the kernel compiled with CONFIG_DRM_I915_DEBUG_GEM and the following command issued as root : echo 15 > /sys/module/drm/parameters/debug You should be able to get some traces about why the execbuffer failed. Unfortunately that generates a lot of traces... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1794033 Title: i965: Failed to submit batchbuffer: Bad address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1820031] Re: My Ubuntu 18.04 GUI seems frozen
** No longer affects: xorg-server (Ubuntu) ** Summary changed: - My Ubuntu 18.04 GUI seems frozen + My Ubuntu 18.04 GUI seems frozen (kernel crash in 0010:gen8_ppgtt_set_pde.isra.43+0x45/0x60 [i915]) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1820031 Title: My Ubuntu 18.04 GUI seems frozen (kernel crash in 0010:gen8_ppgtt_set_pde.isra.43+0x45/0x60 [i915]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820031/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
Thank you for the suggestion. I tried enabling 3D-acceleration. But there is no difference. ** Attachment added: "xorg_leak.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1815693/+attachment/5246295/+files/xorg_leak.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1815693 Title: Kubuntu 18.10 Xorg severe memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1815693/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
Can confirm this is happening on fresh install of Linux Mint and Manjaro as well. Tried installing Kernel 5.0.2 but no fix. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1818516] Re: FFe: Mesa 19.0.x for disco
@Timo 1) Close LP: #1819277 2) For me, this new version of 'mesa' works well Thanks! ** Attachment added: "$ dpkg -l | grep mesa | grep 19" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+attachment/5246287/+files/mesa_19.0.0-1ubuntu1.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1818516 Title: FFe: Mesa 19.0.x for disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1819277] Re: I see stripes plomas in full screen mode
mesa (19.0.0-1ubuntu1) disco; urgency=medium * Merge from Debian. (LP: #1818516) * revert-set-full-thread-affinity.diff: Fix qemu crash. (LP: #1815889) -- Timo Aaltonen Thu, 14 Mar 2019 18:48:18 +0200 ** Changed in: mesa (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1819277 Title: I see stripes plomas in full screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1819277/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1820074] [NEW] Running glxgears with Indirect GLX crashes Xorg
Public bug reported: Replication Steps - sudo mv /usr/bin/Xorg /usr/bin/Xorg.real echo
[Ubuntu-x-swat] [Bug 1820074] Re: Running glxgears with Indirect GLX crashes Xorg
The crash is in XorgLogOld.txt, and the backtrace reproduced here: [ 9027.274] (EE) Backtrace: [ 9027.274] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b9210ba229] [ 9027.275] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fdf6dcc4e1f] [ 9027.275] (EE) 2: /usr/lib/xorg/Xorg (ResetCurrentRequest+0xb) [0x55b9210b92ab] [ 9027.275] (EE) 3: /usr/lib/xorg/Xorg (DRI2WaitSwap+0x56) [0x55b921086716] [ 9027.275] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 9027.275] (EE) 4: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fdf6c7faa20] [ 9027.276] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 9027.276] (EE) 5: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fdf6c7f3010] [ 9027.276] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 9027.276] (EE) 6: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fdf6c7eefd0] [ 9027.276] (EE) 7: /usr/lib/xorg/Xorg (dri3_send_open_reply+0xe2a) [0x55b92108b12a] [ 9027.277] (EE) 8: /usr/lib/xorg/Xorg (_CallCallbacks+0x34) [0x55b920f60be4] [ 9027.277] (EE) 9: /usr/lib/xorg/Xorg (CloseDownClient+0x5f) [0x55b920f5acbf] [ 9027.277] (EE) 10: /usr/lib/xorg/Xorg (OsCleanup+0x591) [0x55b9210bb021] [ 9027.277] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1c3) [0x55b9210b3b93] [ 9027.277] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x10c) [0x55b920f5b72c] [ 9027.277] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x55b920f5f906] [ 9027.278] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fdf6daea09b] [ 9027.278] (EE) 15: /usr/lib/xorg/Xorg (_start+0x2a) [0x55b920f4967a] [ 9027.278] (EE) [ 9027.278] (EE) Segmentation fault at address 0x8 [ 9027.278] (EE) Fatal server error: [ 9027.278] (EE) Caught signal 11 (Segmentation fault). Server aborting -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1820074 Title: Running glxgears with Indirect GLX crashes Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1820074] Re: Running glxgears with Indirect GLX crashes Xorg
Also crashes with nVidia using nouveau drivers (see attached log) ** Attachment added: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+attachment/5246195/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1820074 Title: Running glxgears with Indirect GLX crashes Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1820031] Re: My Ubuntu 18.04 GUI seems frozen
the kernel driver "crashed", which is why the screen froze You could try booting with i915.enable_ppgtt=0 to see if the bug goes away, or a newer kernel. 4.18 is available via 'linux-image-generic- hwe-18.04'. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1820031 Title: My Ubuntu 18.04 GUI seems frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820031/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1818899] Re: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1818899 Title: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818899/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1818899] Re: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login
I have the same problem 18.04.2 LTS, 4.15.0-46-generic #49 With something perhaps useful : I have grub for multi-boot, and only this one ubuntu OS installed -When the computer was on, with ubuntu or another system, a system restart leads me to grub, that leads me to ubuntu, and it is stuck. -At this point a command like ctrl+alt+del restarts the system, takes me back to grub, that leads to ubuntu, and it keeps hanging. When i perform a hard reset while it's stuck (computer button), grub leads me to ubuntu that boots instantaneously, no hanging. Repeated several times. So for the moment, hard reset is my workaround. I don't know how apport works so sorry not to feed the issue with one. (typed apport-collect 1818899, ubuntu replies im not 'abonné' (french)...etc.) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1818899 Title: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818899/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1820029] Re: My Ubuntu 18.04 GUI seems frozen
*** This bug is a duplicate of bug 1820031 *** https://bugs.launchpad.net/bugs/1820031 yes it's a dupe, caused by the i915 kernel driver ** This bug has been marked a duplicate of bug 1820031 My Ubuntu 18.04 GUI seems frozen -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdm in Ubuntu. https://bugs.launchpad.net/bugs/1820029 Title: My Ubuntu 18.04 GUI seems frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdm/+bug/1820029/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
the failure without -intel needs to be debugged, attach X log ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1819943/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol
** Changed in: libva Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-vaapi-driver in Ubuntu. https://bugs.launchpad.net/bugs/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1813131/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1820031] Re: My Ubuntu 18.04 GUI seems frozen
Nothing new comes out in the crash report. When I visit https://errors.ubuntu.com/user/1d81a00d35531ca846cc8b470c853c9c4cc299c3a0a42040e68da92210168a3d96818f5de95d8f7d85e66516d77e481a6259123145189d1685f6d22ac584114a the most recent report is: https://errors.ubuntu.com/oops/0d2b0694-2b7d-11e9-9d81-fa163e102db1 I shall try to apply the work around from https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/994921 as suggested in step 3 of the instructions you have linked to. I do not need to apply it as it is already in place. So what next... apport-collect perhapse although it seems that enough debug may be already posted. Maybe just a reboot of my system (as I cannot restart a service) and move on. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1820031 Title: My Ubuntu 18.04 GUI seems frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820031/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1820031] Re: My Ubuntu 18.04 GUI seems frozen
Assuming your GUI is Gnome Shell, please... 1. Log in via SSH while the GUI is still frozen. 2. Run: killall -ABRT gnome-shell 3. Follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment However if that all doesn't work then don't panic. It appears the problem might be a kernel crash that happened in the Intel graphics driver: 97113.540137] general protection fault: [#1] SMP PTI [97113.540140] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc overlay aufs ip6table_filter ip6_tables iptable_filter binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic eeepc_wmi asus_wmi snd_hda_intel sparse_keymap wmi_bmof mxm_wmi snd_hda_codec snd_hda_core snd_hwdep intel_rapl snd_pcm x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq aesni_intel snd_seq_device snd_timer aes_x86_64 crypto_simd glue_helper cryptd snd mei_me [97113.540168] intel_cstate intel_rapl_perf joydev input_leds soundcore shpchp mei wmi mac_hid acpi_pad sch_fq_codel coretemp parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid uas usb_storage i915 i2c_algo_bit drm_kms_helper syscopyarea e1000e sysfillrect sysimgblt fb_sys_fops ptp i2c_i801 drm nvme pps_core r8169 ahci nvme_core mii libahci video [97113.540187] CPU: 3 PID: 15181 Comm: code Not tainted 4.15.0-45-generic #48-Ubuntu [97113.540188] Hardware name: System manufacturer System Product Name/STRIX H270F GAMING, BIOS 0811 09/27/2017 [97113.540210] RIP: 0010:gen8_ppgtt_set_pde.isra.43+0x45/0x60 [i915] [97113.540212] RSP: 0018:a40fcce1b8d0 EFLAGS: 00010206 [97113.540214] RAX: cd9e819870096ec8 RBX: bb20 RCX: 8eeb5bf7c5c0 [97113.540215] RDX: 0003a2c64003 RSI: 8ee8f3da7fa0 RDI: 8eeaa253e000 [97113.540216] RBP: a40fcce1b8d0 R08: R09: [97113.540217] R10: R11: R12: 01d9 [97113.540218] R13: 0004 R14: 8eeaa253e000 R15: 8eeb843a8000 [97113.540220] FS: 7f5b1947c540() GS:8eec76cc() knlGS: [97113.540221] CS: 0010 DS: ES: CR0: 80050033 [97113.540222] CR2: 7f5b00de6000 CR3: 0003441f4003 CR4: 003606e0 [97113.540224] DR0: DR1: DR2: [97113.540225] DR3: DR6: fffe0ff0 DR7: 0400 [97113.540226] Call Trace: [97113.540241] gen8_ppgtt_alloc_pdp+0x1c2/0x340 [i915] [97113.540255] gen8_ppgtt_alloc_4lvl+0x56/0x150 [i915] [97113.540267] ppgtt_bind_vma+0x39/0x70 [i915] [97113.540282] i915_vma_bind+0x75/0xd0 [i915] [97113.540296] __i915_vma_do_pin+0x2d7/0x490 [i915] [97113.540309] eb_lookup_vmas+0x7b3/0xb40 [i915] [97113.540312] ? __pm_runtime_resume+0x5b/0x80 [97113.540324] i915_gem_do_execbuffer+0x49c/0x1120 [i915] [97113.540327] ? ttwu_do_wakeup+0x1e/0x140 [97113.540329] ? try_to_wake_up+0x59/0x4b0 [97113.540331] ? default_wake_function+0x12/0x20 [97113.540333] ? __wake_up_common+0x72/0x130 [97113.540345] i915_gem_execbuffer2+0x1b8/0x390 [i915] [97113.540347] ? __wake_up_common+0x73/0x130 [97113.540358] ? i915_gem_execbuffer+0x2d0/0x2d0 [i915] [97113.540389] drm_ioctl_kernel+0x5f/0xb0 [drm] [97113.540395] drm_ioctl+0x31b/0x3d0 [drm] [97113.540407] ? i915_gem_execbuffer+0x2d0/0x2d0 [i915] [97113.540411] ? new_sync_write+0xe7/0x140 [97113.540413] do_vfs_ioctl+0xa8/0x630 [97113.540415] ? vfs_write+0x166/0x1a0 [97113.540417] SyS_ioctl+0x79/0x90 [97113.540419] do_syscall_64+0x73/0x130 [97113.540422] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [97113.540424] RIP: 0033:0x7f5b11b6b5d7 [97113.540425] RSP: 002b:7ffdc9f37c68 EFLAGS: 0246 ORIG_RAX: 0010 [97113.540426] RAX: ffda RBX: 05ed1ee70030 RCX: 7f5b11b6b5d7 [97113.540428] RDX: 7ffdc9f37cc0 RSI: 40406469 RDI: 000d [97113.540429] RBP: 7ffdc9f37cc0 R08: 05ed1ea06500 R09: [97113.540430] R10: 7ffdc9f37c90 R11: 0246 R12: 40406469 [97113.540431] R13: 000d R14: R15: 7f5b070e8c00 [97113.540433] Code: 01 00 83 81 48 12 00 00 01 48 2b 05 6e 51 aa dd 48 c1 f8 06 48 c1 e0 0c 48 8d 04 d0 48 8b 56 10 48 03 05 67 51 aa dd 48 83 ca 03 <48> 89 10 83 a9 48 12 00 00 01 5d c3 0f 1f 44 00 00 66 2e 0f 1f [97113.540466] RIP: gen8_ppgtt_set_pde.isra.43+0x45/0x60 [i915] RSP: a40fcce1b8d0 [97113.540468] ---[ end trace 9ac0a2bbf3104804 ]--- ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided
[Ubuntu-x-swat] [Bug 1820027] Re: Ubuntu Budgie 19.04 randomly starts with wrong resolution and nVidia driver fails to load.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1820027 Title: Ubuntu Budgie 19.04 randomly starts with wrong resolution and nVidia driver fails to load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820027/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1820029] [NEW] My Ubuntu 18.04 GUI seems frozen
Public bug reported: This will possibly be a duplicate of Bug #1820028 I was trying to report a frozen GUI over SSH. This is the second report that apport-cli generated when I ran it with xdm as the target package. The symptoms I see are that I started running a go test last night and my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless mouse or keyboard to move anything on the display and the time shown on the clock matches when things froze last night. Before I made the report I looked for any process using high amounts of CUP with top and htop but spotted none. I tried to local a SIGTERM the go test process but that made no difference. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xdm (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 14 09:02:43 2019 DistUpgraded: 2018-07-27 11:19:59,510 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694] InstallationDate: Installed on 2017-11-16 (482 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=UUID=473dc1b9-3a5c-4f95-8cc0-e3b0f628ca41 ro quiet splash vt.handoff=1 SourcePackage: xdm UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 5: PuTTY X11 proxy: unable to connect to forwarded X server: Network error: Connection refused Error: unable to open display UpgradeStatus: Upgraded to bionic on 2018-07-27 (229 days ago) dmi.bios.date: 09/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0811 dmi.board.asset.tag: Default string dmi.board.name: STRIX H270F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0811:bd09/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Mar 12 13:46:44 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: modeset ** Affects: xdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdm in Ubuntu. https://bugs.launchpad.net/bugs/1820029 Title: My Ubuntu 18.04 GUI seems frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdm/+bug/1820029/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1820031] [NEW] My Ubuntu 18.04 GUI seems frozen
Public bug reported: This will possibly be a duplicate of Bug #1820028 or Bug #1820029 or Bug #1820030 I was trying to report a frozen GUI over SSH. This is the second report that apport-cli generated when I ran it with xorg as the target package. I made three four reports to see if different diagnostics were geneereated as Ihave no way of knowing what is causing the lock up at present. The symptoms I see are that I started running a go test last night and my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless mouse or keyboard to move anything on the display and the time shown on the clock matches when things froze last night. Before I made the report I looked for any process using high amounts of CUP with top and htop but spotted none. I tried to local a SIGTERM the go test process but that made no difference. I shall attempt to restart my desktop service ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 14 09:12:51 2019 DistUpgraded: 2018-07-27 11:19:59,510 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694] InstallationDate: Installed on 2017-11-16 (482 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=UUID=473dc1b9-3a5c-4f95-8cc0-e3b0f628ca41 ro quiet splash vt.handoff=1 SourcePackage: xorg UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 5: PuTTY X11 proxy: unable to connect to forwarded X server: Network error: Connection refused Error: unable to open display UpgradeStatus: Upgraded to bionic on 2018-07-27 (229 days ago) dmi.bios.date: 09/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0811 dmi.board.asset.tag: Default string dmi.board.name: STRIX H270F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0811:bd09/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Mar 12 13:46:44 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1820031 Title: My Ubuntu 18.04 GUI seems frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1820031/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1820027] [NEW] Ubuntu Budgie 19.04 randomly starts with wrong resolution and nVidia driver fails to load.
Public bug reported: Ubuntu Budgie 19.04 starts with wrong resolution (1024x768) when 1920x1080 is the native resolution. When trying to manually start nVidia (418) control center it does not load. This happens randomly and most times the OS starts with correct resolution and nVidia driver loads properly. After a failure, log-out and log-in solves the problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu9 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.43 Tue Feb 19 01:12:11 CST 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-2ubuntu2) ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 14 10:43:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.43, 5.0.0-7-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP108 [GeForce GT 1030] [1462:8c98] InstallationDate: Installed on 2019-03-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190313) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=355935f8-10dd-4fe9-acd2-d124111bca46 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd11/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1820027 Title: Ubuntu Budgie 19.04 randomly starts with wrong resolution and nVidia driver fails to load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1820027/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1240738] Re: VG utility functions missing from libopenvg1-mesa
openvg support got removed ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1240738 Title: VG utility functions missing from libopenvg1-mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1240738/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1803681] Re: osmesa doesn't suport core contexts but could
gallium osmesa is already enabled where it's supported, so what's your platform? ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1803681 Title: osmesa doesn't suport core contexts but could To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803681/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1819383] Re: VEGA 64 config for 1680x1050 is incorrect
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v5.0 kernel [0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed”, and attach dmesg. Thanks in advance. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0/ -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1819383 Title: VEGA 64 config for 1680x1050 is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1819383/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1819383] Re: VEGA 64 config for 1680x1050 is incorrect
I guess it's still related to the kernel:
[3.674022] [drm] {1680x1050, 1840x1080@119000Khz}
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1819383
Title:
VEGA 64 config for 1680x1050 is incorrect
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1819383/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
