[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[Christopher M. Penalver]

Nick (q-nick), it will help immensely if you filed a new report with Ubuntu by 
ensuring you have the package xdiagnose installed, and that you click the Yes 
button for attaching additional debugging information running the following 
from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

** Attachment removed: "Xorg.0.log.old"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+attachment/4808950/+files/Xorg.0.log.old

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[Nick]

I'm possibly experiencing this bug, but I'm using the Nvidia proprietary 
driver, particularly the 367.57 version.
I tried to switch the clocksource to acpi_pm, as suggested in some forums, but 
it doesn't help.

While that's EQ overflowing, I couldn't check anything but reboot.

Attached is the Xorg.0.log.old file.

** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+attachment/4808950/+files/Xorg.0.log.old

** Changed in: xorg (Ubuntu)
   Status: Expired => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[Nick]

P.S. mine is also GT710 and Xubuntu 16.04, with kernel 4.4.0-59-generic.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[James]

Many thanks

I will try this on Monday.

On 3 Jul, 2016, at 6:57 am, Christopher M. Penalver
 wrote:

> James, thank you for reporting this and helping make Ubuntu better.
> 
> As per http://www.gigabyte.com/products/product-
> page.aspx?pid=5486=1#bios an update to your computer's buggy,
> insecure, and outdated BIOS is available (F5). When you update to this
> following https://help.ubuntu.com/community/BIOSUpdate how does this
> improve the situation?
> 
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
> 
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful.
> 
> Also, you don't have to create a new bug report.
> 
> Once the BIOS is updated, if the problem is still reproducible:
> 1) Please provide the output of the following terminal command (not perform 
> an apport-collect):
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
> 2) Please make a comment specifically advising on if there was an improvement 
> or not.
> 3) Please mark this report Status New.
> 
> If it's not reproducible, please mark this as Invalid.
> 
> Thank you for your help.
> 
> ** Tags added: bios-outdated-f5
> 
> ** Changed in: xorg (Ubuntu)
>   Importance: Critical => Low
> 
> ** Changed in: xorg (Ubuntu)
>   Status: Confirmed => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1587730
> 
> Title:
>  graphic system freezes after a while, can still ssh into machine
> 
> Status in xorg package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  Ubuntu 16.04 desktop with all updates up to date
>  Gigagyte GA-Z170 motherboard, Intel i7-6700 3.4gHz, 64GB RAM, Samsung 840 
> SSD, Gigabyte GEForce GT710 graphics (nvidia chipset)
> 
>  Very light load. A few terminal windows, a few Firefox pages,
>  Thunderbird, and VirtualBox (with the extension pack loaded) running
>  one small Linux VM with 512Mb memory (very lightly loaded as it's only
>  running bind9). I think (but don't have perfect certainty on this)
>  that some of the crashes have happened without VirtualBox running.
>  Also running rsync so that backuppc on a separate machine can back it
>  up over the network (backuppc has been a real lifesaver with all the
>  reinstallations!)
> 
>  After booting the system runs happily for a while then the GUI
>  freezes. This can take a few hours or up to a day or two. You can
>  still ssh into the system, and if you do "top" it typically shows 100%
>  CPU load on systemd-timesync.
> 
>  The same happens whether I use nouveau or the proprietary nvidia driver (361)
>  I have tried a complete reinstallation (4 times already, starting to get 
> quite frustrating) using the proprietary drivers and NOT using the 
> proprietary drivers and the same still happens. The most recent time was with 
> nouveau, and Xorg.log has a number of entries like this:
>  (EE) [mi] EQ overflowing.  Additional events will be discarded until 
> existing events are processed.
>  (EE) 
>  (EE) Backtrace:
>  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5652cde325ce]
>  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x5652cde14083]
>  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x5652cdcec662]
>  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x61f3) 
> [0x7f31f98621f3]
>  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x6a5d) 
> [0x7f31f9862a5d]
>  (EE) 5: /usr/lib/xorg/Xorg (0x5652cdc8+0x94228) [0x5652cdd14228]
>  (EE) 6: /usr/lib/xorg/Xorg (0x5652cdc8+0xb96f2) [0x5652cdd396f2]
>  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
> [0x7f3202d244a0]
>  (EE) 8: /usr/lib/xorg/Xorg (GiveUp+0x0) [0x5652cde37330]
>  (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
> [0x7f3202d244a0]
>  (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f3202debcf3]
>  (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1d7) [0x5652cde2f307]
>  (EE) 12: /usr/lib/xorg/Xorg (0x5652cdc8+0x539ee) [0x5652cdcd39ee]
>  (EE) 13: /usr/lib/xorg/Xorg (0x5652cdc8+0x57c33) [0x5652cdcd7c33]
>  (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
> [0x7f3202d0f830]
>  (EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x5652cdcc1f59]
>  (EE) 
>  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
> the stack.
>  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
>  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
> 
>  Then at the end the last few are:
> 
>  [  6265.543] [mi] Increasing EQ size to 1024 to prevent dropped events.
>  [  6265.543] [mi] EQ processing has resumed after 1070 dropped events.
>  [  6265.543] [mi] This may be caused by a misbehaving driver monopolizing 
> the server's resources.
> 
>  What cna the problem possibly be, especially as 

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[Christopher M. Penalver]

James, thank you for reporting this and helping make Ubuntu better.

As per http://www.gigabyte.com/products/product-
page.aspx?pid=5486=1#bios an update to your computer's buggy,
insecure, and outdated BIOS is available (F5). When you update to this
following https://help.ubuntu.com/community/BIOSUpdate how does this
improve the situation?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement 
or not.
3) Please mark this report Status New.

If it's not reproducible, please mark this as Invalid.

Thank you for your help.

** Tags added: bios-outdated-f5

** Changed in: xorg (Ubuntu)
   Importance: Critical => Low

** Changed in: xorg (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[James]

It has locked up again overnight but I can still SSH in.
One possible thought is - could it be systemd-timesync which is the problem and 
not actually xorg?

The Xorg.0.log shows nothing unusual but syslog and kern.log are full of
entries about CPU lockup, and "top" as always shows systemd-timesync as
the process hogging the CPU (xorg sometimes shows up hogging 100% of CPU
time in the "top" list, but systems-timesync ALWAYS does when I
experience a freeze:

top - 07:41:20 up 13:26,  2 users,  load average: 10.00, 10.01, 9.98
Tasks: 262 total,   7 running, 252 sleeping,   0 stopped,   3 zombie
%Cpu(s):  0.0 us, 14.3 sy,  0.0 ni, 85.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem : 64276444 total, 46083912 free,  1240520 used, 16952012 buff/cache
KiB Swap: 65379324 total, 65379324 free,0 used. 62810940 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
   
  521 systemd+  20   0  102384   2588   2352 R 100.0  0.0 727:17.66 
systemd-timesyn
1 root  20   0  119860   6044   4008 D   0.0  0.0   0:01.07 systemd 
   
2 root  20   0   0  0  0 S   0.0  0.0   0:00.00 kthreadd
   
3 root  20   0   0  0  0 S   0.0  0.0   0:00.01 ksoftirqd/0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[James]

Because of this bug I have held off putting any vital data on this
computer for the time being, so if you want me to try anything or give
details of any other log entries or whatever please let me know and I
can run stuff Monday morning Hong Kong time and post any more data you
might want before morning in the UK/Europe/US

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[Alberto Salvia Novella]

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xorg (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[Artem]

Have the similar issue under lubuntu 16.04. Virtualbox 5.20. i5 GTX 960
Freez in firefox/libreoffice/chromium..
It helps to switch terminals CtrlAlt-F1 and back CtrlAlt-F7

Usaly I killall firefox from CtrlAlt-F1 (terminal alway works)
But today I have just switched to new terminal and back and it helps.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[James]

Two more freezes today. In one of them there were no errors in Xorg.log,
but there were kern.log and syslog entries complaining about the CPU
locking up, possibly systemd related:

Jun  2 16:07:03 ot08 kernel: [ 1707.978976] Code: d2 e8 7d aa 2f 00 3b 05 3b 25 
e3 00 89 c1 0f 8d 99 fe ff ff 48 98 49 8b 55 00 48 03 14 c5 80 42 f3 81 8b 42 
18 a8 01 74 ca f3 90 <8b> 42 18 a8 01 75 f7 eb bf 0f b6 4d d0 4c 89 fa 4c 89 f6 
44 89 
Jun  2 16:07:31 ot08 kernel: [ 1735.976083] NMI watchdog: BUG: soft lockup - 
CPU#3 stuck for 22s! [systemd-timesyn:481]
Jun  2 16:07:31 ot08 kernel: [ 1735.976084] Modules linked in: pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp i915_bpo kvm_intel kvm intel_ips irqbypass 
crct10dif_pclmul crc32_pclmul aesni_intel joydev input_leds aes_x86_64 lrw 
gf128mul glue_helper snd_hda_intel ablk_helper cryptd snd_hda_codec 
snd_hda_core snd_hwdep snd_seq_midi serio_raw snd_pcm snd_seq_midi_event 
snd_rawmidi snd_seq snd_seq_device mei_me snd_timer mei snd soundcore hci_uart 
btbcm btqca btintel bluetooth 8250_fintek shpchp intel_lpss_acpi tpm_infineon 
intel_lpss mac_hid acpi_pad acpi_als binfmt_misc kfifo_buf industrialio 
parport_pc ppdev lp parport autofs4 uas usb_storage hid_generic hid_microsoft 
usbhid nouveau mxm_wmi i2c_algo_bit ttm drm_kms_helper e1000e syscopyarea 
sysfillrect psmouse sysimgblt ptp fb_sys_fops pps_core ahci drm libahci wmi 
video i2c_hid pinctrl_sunrisep
 oint pinctrl_intel hid fjes
Jun  2 16:07:31 ot08 kernel: [ 1735.976123] CPU: 3 PID: 481 Comm: 
systemd-timesyn Tainted: G   OEL  4.4.0-22-generic #40-Ubuntu
Jun  2 16:07:31 ot08 kernel: [ 1735.976124] Hardware name: Gigabyte Technology 
Co., Ltd. Z170-D3H/Z170-D3H-CF, BIOS F2 07/24/2015
Jun  2 16:07:31 ot08 kernel: [ 1735.976125] task: 880fb4942c40 ti: 
880fb8c1 task.ti: 880fb8c1
Jun  2 16:07:31 ot08 kernel: [ 1735.976125] RIP: 0010:[]  
[] smp_call_function_many+0x1f8/0x260
Jun  2 16:07:31 ot08 kernel: [ 1735.976128] RSP: 0018:880fb8c13d20  EFLAGS: 
0202
Jun  2 16:07:31 ot08 kernel: [ 1735.976129] RAX: 0003 RBX: 
0100 RCX: 0002
Jun  2 16:07:31 ot08 kernel: [ 1735.976129] RDX: 880fffc9add8 RSI: 
0100 RDI: 880fffcd7c88
Jun  2 16:07:31 ot08 kernel: [ 1735.976130] RBP: 880fb8c13d58 R08: 
 R09: 00f7
Jun  2 16:07:31 ot08 kernel: [ 1735.976131] R10: 0004 R11: 
880fffcd7c88 R12: 880fffcd7c88
Jun  2 16:07:31 ot08 kernel: [ 1735.976131] R13: 880fffcd7c80 R14: 
81035d10 R15: 
Jun  2 16:07:31 ot08 kernel: [ 1735.976132] FS:  7f8fb4c19780() 
GS:880fffcc() knlGS:
Jun  2 16:07:31 ot08 kernel: [ 1735.976133] CS:  0010 DS:  ES:  CR0: 
80050033
Jun  2 16:07:31 ot08 kernel: [ 1735.976133] CR2: 7fa0f7fa CR3: 
000fb31b1000 CR4: 003406e0
Jun  2 16:07:31 ot08 kernel: [ 1735.976134] DR0:  DR1: 
 DR2: 
Jun  2 16:07:31 ot08 kernel: [ 1735.976135] DR3:  DR6: 
fffe0ff0 DR7: 0400
Jun  2 16:07:31 ot08 kernel: [ 1735.976135] Stack:
Jun  2 16:07:31 ot08 kernel: [ 1735.976136]  00017c40 01ff880f0001 
8171d4d7 81035d10
Jun  2 16:07:31 ot08 kernel: [ 1735.976137]   8171d4d8 
0001 880fb8c13d80
Jun  2 16:07:31 ot08 kernel: [ 1735.976138]  81103f4d 8171d4d7 
0005 880fb8c13dd3
Jun  2 16:07:31 ot08 kernel: [ 1735.976139] Call Trace:
Jun  2 16:07:31 ot08 kernel: [ 1735.976154]  [] ? 
dev_hard_start_xmit+0x137/0x3d0
Jun  2 16:07:31 ot08 kernel: [ 1735.976155]  [] ? 
arch_unregister_cpu+0x30/0x30
Jun  2 16:07:31 ot08 kernel: [ 1735.976156]  [] ? 
dev_hard_start_xmit+0x138/0x3d0
Jun  2 16:07:31 ot08 kernel: [ 1735.976158]  [] 
on_each_cpu+0x2d/0x60
Jun  2 16:07:31 ot08 kernel: [ 1735.976159]  [] ? 
dev_hard_start_xmit+0x137/0x3d0
Jun  2 16:07:31 ot08 kernel: [ 1735.976160]  [] 
text_poke_bp+0x6a/0xf0
Jun  2 16:07:31 ot08 kernel: [ 1735.976161]  [] ? 
dev_hard_start_xmit+0x137/0x3d0
Jun  2 16:07:31 ot08 kernel: [ 1735.976162]  [] 
arch_jump_label_transform+0x9b/0x120
Jun  2 16:07:31 ot08 kernel: [ 1735.976177]  [] 
__jump_label_update+0x6c/0x80
Jun  2 16:07:31 ot08 kernel: [ 1735.976178]  [] 
jump_label_update+0x88/0x90
Jun  2 16:07:31 ot08 kernel: [ 1735.976179]  [] 
static_key_slow_inc+0x94/0xa0
Jun  2 16:07:31 ot08 kernel: [ 1735.976181]  [] 
net_enable_timestamp+0x3b/0x40
Jun  2 16:07:31 ot08 kernel: [ 1735.976182]  [] 
sock_enable_timestamp+0x36/0x40
Jun  2 16:07:31 ot08 kernel: [ 1735.976183]  [] 
sock_setsockopt+0x366/0x810
Jun  2 16:07:31 ot08 kernel: [ 1735.976185]  [] ? 
apparmor_socket_setsockopt+0x22/0x30
Jun  2 16:07:31 ot08 kernel: [ 1735.976186]  [] 
SyS_setsockopt+0xcd/0xe0
Jun  2 

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[James]

sudo kill -9 18922 is not working (18992 is the PID of systemd-timesync,
which is hogging 100% of one CPU core fro the last few hours and
clogging the logs with errors)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[James]

It's starting to happen again. "top" shows that systemd-timesync is
using 100% of CPU, and many errors are turning up in the kern.log and
syslog:

Jun  1 20:46:57 ot08 kernel: [27109.247795] NMI watchdog: Watchdog detected 
hard LOCKUP on cpu 3
Jun  1 20:46:57 ot08 kernel: [27109.247797] Modules linked in: nls_iso8859_1 
btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic i915_bpo 
intel_ips snd_hda_intel snd_hda_codec snd_hda_core joydev input_leds intel_rapl 
snd_hwdep x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm snd_seq_midi 
snd_seq_midi_event kvm_intel snd_rawmidi snd_seq kvm snd_seq_device snd_timer 
irqbypass crct10dif_pclmul crc32_pclmul snd shpchp mei_me mei aesni_intel 
soundcore serio_raw aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
hci_uart btbcm btqca btintel bluetooth 8250_fintek intel_lpss_acpi acpi_als 
intel_lpss kfifo_buf industrialio tpm_infineon acpi_pad mac_hid binfmt_misc 
parport_pc ppdev lp parport autofs4 uas usb_storage hid_generic hid_microsoft 
usbhid nouveau mxm_wmi i2c_algo_bit ttm drm_kms_helper syscopyarea e1000e 
sysfillrect psmou
 se sysimgblt fb_sys_fops ptp pps_core ahci drm libahci wmi i2c_hid video 
pinctrl_sunrisepoint hid pinctrl_intel fjes
Jun  1 20:46:57 ot08 kernel: [27109.247833] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G   OE   4.4.0-22-generic #40-Ubuntu
Jun  1 20:46:57 ot08 kernel: [27109.247834] Hardware name: Gigabyte Technology 
Co., Ltd. Z170-D3H/Z170-D3H-CF, BIOS F2 07/24/2015
Jun  1 20:46:57 ot08 kernel: [27109.247834] task: 880fba4cbb00 ti: 
880fba4dc000 task.ti: 880fba4dc000
Jun  1 20:46:57 ot08 kernel: [27109.247835] RIP: 0010:[]  
[] cpuidle_enter_state+0x111/0x2b0
Jun  1 20:46:57 ot08 kernel: [27109.247839] RSP: 0018:880fba4dfe70  EFLAGS: 
0246
Jun  1 20:46:57 ot08 kernel: [27109.247840] RAX:  RBX: 
0006 RCX: 0018
Jun  1 20:46:57 ot08 kernel: [27109.247840] RDX: 0036858fe1872cf3 RSI: 
004b1e6b RDI: 
Jun  1 20:46:57 ot08 kernel: [27109.247841] RBP: 880fba4dfea8 R08: 
000af8b3 R09: 0014
Jun  1 20:46:57 ot08 kernel: [27109.247841] R10: 000100663ed0 R11: 
be5b R12: 0006
Jun  1 20:46:57 ot08 kernel: [27109.247842] R13: 880fffcdec00 R14: 
18a66d13ebb4 R15: 81eb1eb8
Jun  1 20:46:57 ot08 kernel: [27109.247843] FS:  () 
GS:880fffcc() knlGS:
Jun  1 20:46:57 ot08 kernel: [27109.247844] CS:  0010 DS:  ES:  CR0: 
80050033
Jun  1 20:46:57 ot08 kernel: [27109.247844] CR2: 7fad3ee0a000 CR3: 
01e0a000 CR4: 003406e0
.
.
.
.
and so on
.
.
.
Jun  1 22:10:13 ot08 kernel: [32156.713009] Code: d2 e8 7d aa 2f 00 3b 05 3b 25 
e3 00 89 c1 0f 8d 99 fe ff ff 48 98 49 8b 55 00 48 03 14 c5 80 42 f3 81 8b 42 
18 a8 01 74 ca f3 90 <8b> 42 18 a8 01 75 f7 eb bf 0f b6 4d d0 4c 89 fa 4c 89 f6 
44 89 
Jun  1 22:10:41 ot08 kernel: [32184.709855] NMI watchdog: BUG: soft lockup - 
CPU#4 stuck for 23s! [systemd-timesyn:18992]
Jun  1 22:10:41 ot08 kernel: [32184.709857] Modules linked in: nls_iso8859_1 
btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic i915_bpo 
intel_ips snd_hda_intel snd_hda_codec snd_hda_core joydev input_leds intel_rapl 
snd_hwdep x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm snd_seq_midi 
snd_seq_midi_event kvm_intel snd_rawmidi snd_seq kvm snd_seq_device snd_timer 
irqbypass crct10dif_pclmul crc32_pclmul snd shpchp mei_me mei aesni_intel 
soundcore serio_raw aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
hci_uart btbcm btqca btintel bluetooth 8250_fintek intel_lpss_acpi acpi_als 
intel_lpss kfifo_buf industrialio tpm_infineon acpi_pad mac_hid binfmt_misc 
parport_pc ppdev lp parport autofs4 uas usb_storage hid_generic hid_microsoft 
usbhid nouveau mxm_wmi i2c_algo_bit ttm drm_kms_helper syscopyarea e1000e 
sysfillrect psmou
 se sysimgblt fb_sys_fops ptp pps_core ahci drm libahci wmi i2c_hid video 
pinctrl_sunrisepoint hid pinctrl_intel fjes
Jun  1 22:10:41 ot08 kernel: [32184.709921] CPU: 4 PID: 18992 Comm: 
systemd-timesyn Tainted: G   OEL  4.4.0-22-generic #40-Ubuntu
Jun  1 22:10:41 ot08 kernel: [32184.709922] Hardware name: Gigabyte Technology 
Co., Ltd. Z170-D3H/Z170-D3H-CF, BIOS F2 07/24/2015
Jun  1 22:10:41 ot08 kernel: [32184.709923] task: 880fb4ee2c40 ti: 
880f1d684000 task.ti: 880f1d684000
Jun  1 22:10:41 ot08 kernel: [32184.709924] RIP: 0010:[]  
[] smp_call_function_many+0x1f8/0x260
Jun  1 22:10:41 ot08 kernel: [32184.709928] RSP: 0018:880f1d687d20  EFLAGS: 
0202
Jun  1 22:10:41 ot08 kernel: [32184.709928] RAX: 0003 RBX: 

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[James]

One more observation - when the display is in the frozen state (frozen windows, 
no response to mouse or keyboard input) and you ssh into the machine, certain 
things don't work. For example, 'sudo shutdown now' or 'sudo shutdown -r now' 
produce no result.
Sometimes there is a timeout message after a few minutes which says:
"Failed to start poweroff.target: Connection timed out
See system logs and 'systemctl status poweroff.target' for details"

Likewise 'kill -9 ' produces inconsistent results -
sometimes the process in question is successfully killed and other times
not.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

[James]

One further comment. The BIOS is set to no UEFI boot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs