Persistent system crash

I am finding 42.3 very unstable on a brand new system.

uname -a gives

Linux hostname 4.4.85-22-default #1 SMP Fri Sep 1 14:21:21 UTC 2017 (0c39a1f) x86_64 x86_64 x86_64 GNU/Linux

The motherboard is an Asus Prime B250-Pro with Intel Core i3-7100 with 16GB DDR4 RAM. Graphics is the integrated Intel device. HD is a Samsung 500GB SSD.

The install is a clean install from a USB stick

The system works for a while but after an hour or more the typical failure is the crash of a running application and then the complete seizure of the keyboard and mouse. No F1.
I can sometimes SSH into the system but often even that is slow and crashes.

An example is a crash of firtefox which was run from a konsole command line. This looks like this:

AiOGest: init
AiOGest: end init
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
ExceptionHandler::GenerateDump cloned child 6921
ExceptionHandler::SendContinueSignalToChild sent continue signal to child

When I move to iceWM in an attempt to evade plasma problems that also seizes after a while.

Can I supply more info and if so what?

Thanks
Peter

Try to uninstall the kernel graphics stack update, drm-kmp-default, and see if it helps.

Or uninstall the intel Xorg driver, xf86-video-intel, and use the generic modesetting driver (which is even said to have better performance on some systems…).

Hi Wolfi,

I uninstalled drm-kmp-default and the display was dropped into a fixed 1024 x 768 resolution with no option to change the resolution back to my normal 1920 x 1080.
System settings did not have the resolution change feature normally found in the Dispalys tab.
Is there any way round this please?

peter

Then apparently your GPU is quite new and not supported by kernel 4.4 yet.
So the system probably uses the generic fbdev driver now, which doesn’t allow resolution changes.
/var/log/Xorg.0.log should tell more though.

Is there any way round this please?

Yes, install it again.

And try to uninstall xf86-video-intel instead.

Unfortunately xf86-video-intel is not installed on the system.
Would it be worth trying with it installed?

Peter

I have now installed xf86-video-intel without any noticeable problems but it I have since had a system crash. I was able to ssh into the system but an attempt to halt the system from the remote host failed. Having su’d into root:

bardsey:/home/peter # halt

Broadcast message from systemd-journald@bardsey (Fri 2017-09-15 14:34:46 BST):

systemd[1]: Caught <SEGV>, dumped core as pid 19702.


Broadcast message from systemd-journald@bardsey (Fri 2017-09-15 14:34:46 BST):

systemd[1]: Freezing execution.

Warning! D-Bus connection terminated.
Failed to wait for response: Connection reset by peer
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.
bardsey:/home/peter # 
bardsey:/home/peter # halt
Failed to start halt.target: Connection timed out
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.
bardsey:/home/peter # halt
Failed to start halt.target: Activation of org.freedesktop.systemd1 timed out
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.
bardsey:/home/peter # exit
exit

So this is looks to me as a complete failure of the system daemon.

Peter

Well, if it is not installed, it cannot be the cause of the problems either. (I mainly suggested to uninstall it because it is quite buggy on certain chipsets it seems)

Installing it probably won’t change anything at all, because if it is not installed by default it probably doesn’t support your graphics chip anyway (which means it won’t get used even if installed).

Again, /var/log/Xorg.0.log should tell what happens.

Looks like systemd crashed. (and that would also explain why the subsequent “halt” doesn’t work at all, as there’s no init system any more to talk to and initiate the halt)
Btw, it would probably be better to run “systemctl poweroff”, “shutdown”, or “halt -p”, as “halt” alone will not poweroff the system.

If systemd crashes, that can cause all sort of problems of course, but the question is whether this is related to your other problems, or rather only happens when you run “halt” via ssh.

coredumpctl should list all crashes, so having a look at that via ssh after the system froze may give more clues.
And the output of dmesg might be interesting too.

As this seems to be brand new hardware (as e.g. the GPU apparently is not even supported by the standard kernel), the best thing probably would be trying to install the latest kernel version though, available from the Kernel:stable repo.
http://download.opensuse.org/repositories/Kernel:/stable/standard/

E.g. add this URL as repo with YaST->Repositories and then install the highest version of kernel-default in YaST->Software Management (click on “Versions” below the package list to see all available versions).
The standard kernel will be kept (and available to boot in “Advanced Options” in the boot menu) if you do this, so you can easily switch back in case of problems.

FWIW, I have ‘enjoyed’ many of the issues described by the OP on four very new systems (Kabylake, released by Intel about the same time as the B250 series) and found simply updating the Kernel to resolve most of those issues, however it’s important to know what version to update to.

Based on my experience my highly subjective opinion is as follows:

4.4 -not able to handle Kabylake, particularly graphics, very unstable
4.9 - better but not much better
4.11 - should be ok based on posts elsewhere, but that’s not my experience.
4.12 - very stable
4.13 - only using it on two systems for two days, but seems OK

Thank you for that advice.

I have upgraded as Wolfi suggests and now have version 4.13.2-1.1.g68f4aee installed.

I am guessing that I will have to re-install virtualbox to get that running.

Thanks for the stability advice caprus. I will report back on the results of this upgrade.

The oldest computer that I have run code on is a Mercury computer which ran Pegasus autocode. One hot room full of valves and drum memory!

Basically you need to compile/install the kernel modules for the new kernel.

If you use Oracle’s RPM, you can do that by running “sudo vboxconfig setup”.

If you use openSUSE’s RPM, this won’t work out of the box, as it only comes with a pre-compiled module that fits the distribution kernel, but no source code.
Additionally installing virtualbox-host-source should make that work (but I never tried that myself).
OTOH, there is a Virtualization repo that comes with a kmp (kernel module package) built against the latest kernel from Kernel:stable:
http://download.opensuse.org/repositories/Virtualization/Kernel_stable_standard/
(you should also install virtualbox from there then, to avoid version mismatches)

I have experienced a crash with the latest kernel.
The output from journalctl from what I guess to be the start of the crash to the reboot is as follows:

Sep 18 10:52:57 bardsey kernel: show_signal_msg: 34 callbacks suppressed
Sep 18 10:52:57 bardsey kernel: plasmashell[4355]: segfault at 8 ip 00007f236bf23d60 sp 00007ffce47f22a8 error 4 in libQt5Gui.so.5.6.2[7f236be46000+533000]
Sep 18 10:52:57 bardsey kernel: BUG: unable to handle kernel paging request at 0000000000800020
Sep 18 10:52:57 bardsey kernel: IP: find_get_entry+0x3f/0xf0
Sep 18 10:52:57 bardsey kernel: PGD 0 
Sep 18 10:52:57 bardsey kernel: P4D 0 
Sep 18 10:52:57 bardsey kernel: 
Sep 18 10:52:57 bardsey kernel: Oops: 0000 #1] PREEMPT SMP
Sep 18 10:52:57 bardsey kernel: Modules linked in: fuse bnep nf_log_ipv6 xt_comment nf_log_ipv4 nf_log_common xt_LOG xt_limit af_packet vboxpci(O) vboxnetadp(O) vboxnetflt(O) iscsi_ibft iscsi_boot_sysfs ip6t_REJECT nf_reject_ipv6 nf_conntr
Sep 18 10:52:57 bardsey kernel:  snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm aesni_intel hci_uart btbcm serdev aes_x86_64 btqca crypto_simd r8169 glue_helper btintel snd_timer mii cryptd snd bluetooth tpm_tis ecdh_generic tp
Sep 18 10:52:57 bardsey kernel: CPU: 3 PID: 4376 Comm: systemd-coredum Tainted: G           O    4.13.2-1.g68f4aee-default #1
Sep 18 10:52:57 bardsey kernel: Hardware name: System manufacturer System Product Name/PRIME B250-PRO, BIOS 0608 03/24/2017
Sep 18 10:52:57 bardsey kernel: task: ffff993a3d6840c0 task.stack: ffffb55f8882c000
Sep 18 10:52:57 bardsey kernel: RIP: 0010:find_get_entry+0x3f/0xf0
Sep 18 10:52:57 bardsey kernel: RSP: 0018:ffffb55f8882fb80 EFLAGS: 00010246
Sep 18 10:52:57 bardsey kernel: RAX: 0000000000000000 RBX: ffff993a06ec38a0 RCX: 0000000000800000
Sep 18 10:52:57 bardsey kernel: RDX: 0000000000000000 RSI: ffff9939e4a3a448 RDI: ffff9939e4a3a448
Sep 18 10:52:57 bardsey kernel: RBP: 00000000000407bc R08: ffff9939e4a3a240 R09: 0000000000800000
Sep 18 10:52:57 bardsey kernel: R10: 0000000000000000 R11: 0000000000000040 R12: 0000000001c2004a
Sep 18 10:52:57 bardsey kernel: R13: ffff993a06ec3898 R14: 00000000000407bc R15: ffffffffa7e81f80
Sep 18 10:52:57 bardsey kernel: FS:  00007f49899f3840(0000) GS:ffff993af6d80000(0000) knlGS:0000000000000000
Sep 18 10:52:57 bardsey kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 18 10:52:57 bardsey kernel: CR2: 0000000000800020 CR3: 000000037d686000 CR4: 00000000003406e0
Sep 18 10:52:57 bardsey kernel: Call Trace:
Sep 18 10:52:57 bardsey kernel:  pagecache_get_page+0x30/0x200
Sep 18 10:52:57 bardsey kernel:  prepare_pages+0xf0/0x1e0 [btrfs]
Sep 18 10:52:57 bardsey kernel:  __btrfs_buffered_write+0x278/0x710 [btrfs]
Sep 18 10:52:57 bardsey kernel:  ? account_entity_dequeue+0xa4/0xd0
Sep 18 10:52:57 bardsey kernel:  btrfs_file_write_iter+0x1da/0x600 [btrfs]
Sep 18 10:52:57 bardsey kernel:  __vfs_write+0xd5/0x150
Sep 18 10:52:57 bardsey kernel:  __kernel_write+0x48/0xe0
Sep 18 10:52:57 bardsey kernel:  ? default_file_splice_read+0x2a0/0x2a0
Sep 18 10:52:57 bardsey kernel:  write_pipe_buf+0x42/0x50
Sep 18 10:52:57 bardsey kernel:  __splice_from_pipe+0x7d/0x180
Sep 18 10:52:57 bardsey kernel:  ? default_file_splice_read+0x2a0/0x2a0
Sep 18 10:52:57 bardsey kernel:  splice_from_pipe+0x4f/0x70
Sep 18 10:52:57 bardsey kernel:  default_file_splice_write+0x15/0x20
Sep 18 10:52:57 bardsey kernel:  SyS_splice+0x2d9/0x670
Sep 18 10:52:57 bardsey kernel:  do_syscall_64+0x57/0xc0
Sep 18 10:52:57 bardsey kernel:  entry_SYSCALL64_slow_path+0x25/0x25
Sep 18 10:52:57 bardsey kernel: RIP: 0033:0x7f49888c5393
Sep 18 10:52:57 bardsey kernel: RSP: 002b:00007ffdf2bda9d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000113
Sep 18 10:52:57 bardsey kernel: RAX: ffffffffffffffda RBX: 000000003f844000 RCX: 00007f49888c5393
Sep 18 10:52:57 bardsey kernel: RDX: 0000000000000003 RSI: 0000000000000000 RDI: 0000000000000000
Sep 18 10:52:57 bardsey kernel: RBP: 00007ffdf2bdaa20 R08: 0000000000004000 R09: 0000000000000000
Sep 18 10:52:57 bardsey kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000004000
Sep 18 10:52:57 bardsey kernel: R13: 0000000000000001 R14: 0000000000001000 R15: 0000000000000000
Sep 18 10:52:57 bardsey kernel: Code: d8 3b f4 ff 48 89 ee 48 89 df e8 fd 00 5b 00 48 85 c0 48 89 c6 74 75 48 8b 08 48 85 c9 74 6d 48 89 c8 83 e0 03 0f 85 85 00 00 00 <48> 8b 41 20 48 8d 78 ff a8 01 48 0f 44 f9 8b 47 1c 85 c0 74 c4 
Sep 18 10:52:57 bardsey kernel: RIP: find_get_entry+0x3f/0xf0 RSP: ffffb55f8882fb80
Sep 18 10:52:57 bardsey kernel: CR2: 0000000000800020
Sep 18 10:52:57 bardsey kernel: --- end trace 7235ce579f4cc7af ]---
Sep 18 10:52:57 bardsey kernel: ------------ cut here ]------------
Sep 18 10:52:57 bardsey kernel: WARNING: CPU: 3 PID: 4376 at ../kernel/rcu/tree_plugin.h:323 rcu_note_context_switch+0x5e/0x4a0
Sep 18 10:52:57 bardsey kernel: Modules linked in: fuse bnep nf_log_ipv6 xt_comment nf_log_ipv4 nf_log_common xt_LOG xt_limit af_packet vboxpci(O) vboxnetadp(O) vboxnetflt(O) iscsi_ibft iscsi_boot_sysfs ip6t_REJECT nf_reject_ipv6 nf_conntr
Sep 18 10:52:57 bardsey kernel:  snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm aesni_intel hci_uart btbcm serdev aes_x86_64 btqca crypto_simd r8169 glue_helper btintel snd_timer mii cryptd snd bluetooth tpm_tis ecdh_generic tp
Sep 18 10:52:57 bardsey kernel: CPU: 3 PID: 4376 Comm: systemd-coredum Tainted: G      D    O    4.13.2-1.g68f4aee-default #1
Sep 18 10:52:57 bardsey kernel: Hardware name: System manufacturer System Product Name/PRIME B250-PRO, BIOS 0608 03/24/2017
Sep 18 10:52:57 bardsey kernel: task: ffff993a3d6840c0 task.stack: ffffb55f8882c000
Sep 18 10:52:57 bardsey kernel: RIP: 0010:rcu_note_context_switch+0x5e/0x4a0
Sep 18 10:52:57 bardsey kernel: RSP: 0018:ffffb55f8882fce0 EFLAGS: 00010002
Sep 18 10:52:57 bardsey kernel: RAX: 0000000000000001 RBX: ffff993a3d6840c0 RCX: 0000000000000000
Sep 18 10:52:57 bardsey kernel: RDX: 0000000000000000 RSI: ffffffffa7765a69 RDI: 0000000000000000
Sep 18 10:52:57 bardsey kernel: RBP: 0000000000000000 R08: ffff993a37d689cc R09: 0000000000000000
Sep 18 10:52:57 bardsey kernel: R10: ffffb55f8882fe48 R11: 00000000ffffffff R12: 0000000000000000
Sep 18 10:52:57 bardsey kernel: R13: ffff993a3d6840c0 R14: ffff993855ef66e0 R15: ffff993a37d689c0
Sep 18 10:52:57 bardsey kernel: FS:  0000000000000000(0000) GS:ffff993af6d80000(0000) knlGS:0000000000000000
Sep 18 10:52:57 bardsey kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 18 10:52:57 bardsey kernel: CR2: 0000000000800020 CR3: 0000000356e09000 CR4: 00000000003406e0
Sep 18 10:52:57 bardsey kernel: Call Trace:
Sep 18 10:52:57 bardsey kernel:  __schedule+0x8d/0x880
Sep 18 10:52:57 bardsey kernel:  ? mutex_spin_on_owner+0x4a/0xc0
Sep 18 10:52:57 bardsey kernel:  schedule+0x39/0x90
Sep 18 10:52:57 bardsey kernel:  schedule_preempt_disabled+0x11/0x20
Sep 18 10:52:57 bardsey kernel:  __mutex_lock.isra.1+0x475/0x4f0
Sep 18 10:52:57 bardsey kernel:  ? __inode_wait_for_writeback+0x6f/0xc0
Sep 18 10:52:57 bardsey kernel:  ? bit_waitqueue+0x30/0x30
Sep 18 10:52:57 bardsey kernel:  ? pipe_release+0x1e/0xa0
Sep 18 10:52:57 bardsey kernel:  pipe_release+0x1e/0xa0
Sep 18 10:52:57 bardsey kernel:  __fput+0xc7/0x1d0
Sep 18 10:52:57 bardsey kernel:  task_work_run+0x70/0x90
Sep 18 10:52:57 bardsey kernel:  do_exit+0x2ca/0xb80
Sep 18 10:52:57 bardsey kernel:  rewind_stack_do_exit+0x17/0x20
Sep 18 10:52:57 bardsey kernel: Code: 0e f3 58 84 c0 0f 85 4d 02 00 00 65 48 8b 1c 25 c0 d3 00 00 40 84 ed 8b 83 f8 03 00 00 0f 85 05 01 00 00 85 c0 0f 8e 05 01 00 00 <0f> ff 80 bb fc 03 00 00 00 0f 84 79 01 00 00 65 66 8b 05 93 0b 
Sep 18 10:52:57 bardsey kernel: --- end trace 7235ce579f4cc7b0 ]---
Sep 18 10:53:00 bardsey kernel: QtWebEngineProc[4336]: segfault at 2a9e4b55a6b1 ip 00007fcec22d2f60 sp 00007ffd900ecf10 error 4 in libQt5WebEngineCore.so.5.6.2[7fcec09be000+4329000]
Sep 18 10:53:00 bardsey kernel: drkonqi[4377]: segfault at 2749fa8 ip 00007fe6f15559f5 sp 00007ffc6bd83a18 error 4 in libc-2.22.so[7fe6f142d000+199000]
Sep 18 10:53:00 bardsey kernel: BUG: unable to handle kernel paging request at 0000000000800020
Sep 18 10:53:00 bardsey kernel: IP: find_get_entry+0x3f/0xf0
Sep 18 10:53:00 bardsey kernel: PGD 0 
Sep 18 10:53:00 bardsey kernel: P4D 0 
Sep 18 10:53:00 bardsey kernel: 
Sep 18 10:53:00 bardsey kernel: Oops: 0000 #2] PREEMPT SMP

After the oops there is more until a reboot. I will put the rest in a second post and then try to find out how to upload and reference a file.

The effect was kontact crashing while I was reading emails and when I tried to restart contact the plasma desktop vanished and then the entire system locked up. I could not even ssh in to do a reboot.

My next move will be to remove drm-kmp-default with the new kernel 4.13.2-1.1.g68f4aee to see if I am able to select the correct display resolution.

If the above means anything, please let me know.

Peter

The rest of the journal up to the reboot is:

Sep 18 10:53:00 bardsey kernel: Oops: 0000 #3] PREEMPT SMP
Sep 18 10:53:00 bardsey kernel: Modules linked in: fuse bnep nf_log_ipv6 xt_comment nf_log_ipv4 nf_log_common xt_LOG xt_limit af_packet vboxpci(O) vboxnetadp(O) vboxnetflt(O) iscsi_ibft iscsi_boot_sysfs ip6t_REJECT nf_reject_ipv6 nf_conntr
Sep 18 10:53:00 bardsey kernel:  snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm aesni_intel hci_uart btbcm serdev aes_x86_64 btqca crypto_simd r8169 glue_helper btintel snd_timer mii cryptd snd bluetooth tpm_tis ecdh_generic tp
Sep 18 10:53:00 bardsey kernel: CPU: 1 PID: 4383 Comm: systemd-coredum Tainted: G      D W  O    4.13.2-1.g68f4aee-default #1
Sep 18 10:53:00 bardsey kernel: Hardware name: System manufacturer System Product Name/PRIME B250-PRO, BIOS 0608 03/24/2017
Sep 18 10:53:00 bardsey kernel: task: ffff993a3c13a0c0 task.stack: ffffb55f8264c000
Sep 18 10:53:00 bardsey kernel: RIP: 0010:find_get_entry+0x3f/0xf0
Sep 18 10:53:00 bardsey kernel: RSP: 0018:ffffb55f8264fb80 EFLAGS: 00010246
Sep 18 10:53:00 bardsey kernel: RAX: 0000000000000000 RBX: ffff9939e4a72528 RCX: 0000000000800000
Sep 18 10:53:00 bardsey kernel: RDX: 0000000000000000 RSI: ffff9939e4a3dc98 RDI: ffff9939e4a3dc98
Sep 18 10:53:00 bardsey kernel: RBP: 00000000000075e6 R08: ffff9939e4a3db40 R09: 0000000000800000
Sep 18 10:53:00 bardsey kernel: R10: 0000000000000000 R11: 0000000000000040 R12: 0000000001c2004a
Sep 18 10:53:00 bardsey kernel: R13: ffff9939e4a72520 R14: 00000000000075e6 R15: ffffffffa7e81f80
Sep 18 10:53:00 bardsey kernel: FS:  00007f06af2f7840(0000) GS:ffff993af6c80000(0000) knlGS:0000000000000000
Sep 18 10:53:00 bardsey kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 18 10:53:00 bardsey kernel: CR2: 0000000000800020 CR3: 000000037d610000 CR4: 00000000003406e0
Sep 18 10:53:00 bardsey kernel: Call Trace:
Sep 18 10:53:00 bardsey kernel:  pagecache_get_page+0x30/0x200
Sep 18 10:53:00 bardsey kernel:  prepare_pages+0xf0/0x1e0 [btrfs]
Sep 18 10:53:00 bardsey kernel:  __btrfs_buffered_write+0x278/0x710 [btrfs]
Sep 18 10:53:00 bardsey kernel:  btrfs_file_write_iter+0x1da/0x600 [btrfs]
Sep 18 10:53:00 bardsey kernel:  ? ttwu_do_wakeup+0x19/0x160
Sep 18 10:53:00 bardsey kernel:  __vfs_write+0xd5/0x150
Sep 18 10:53:00 bardsey kernel:  __kernel_write+0x48/0xe0
Sep 18 10:53:00 bardsey kernel:  ? default_file_splice_read+0x2a0/0x2a0
Sep 18 10:53:00 bardsey kernel:  write_pipe_buf+0x42/0x50
Sep 18 10:53:00 bardsey kernel:  __splice_from_pipe+0x7d/0x180
Sep 18 10:53:00 bardsey kernel:  ? default_file_splice_read+0x2a0/0x2a0
Sep 18 10:53:00 bardsey kernel:  splice_from_pipe+0x4f/0x70
Sep 18 10:53:00 bardsey kernel:  default_file_splice_write+0x15/0x20
Sep 18 10:53:00 bardsey kernel:  SyS_splice+0x2d9/0x670
Sep 18 10:53:00 bardsey kernel:  do_syscall_64+0x57/0xc0
Sep 18 10:53:00 bardsey kernel:  entry_SYSCALL64_slow_path+0x25/0x25
Sep 18 10:53:00 bardsey kernel: RIP: 0033:0x7f06ae1c9393
Sep 18 10:53:00 bardsey kernel: RSP: 002b:00007ffff5074e88 EFLAGS: 00000246 ORIG_RAX: 0000000000000113
Sep 18 10:53:00 bardsey kernel: RAX: ffffffffffffffda RBX: 0000000078a1d000 RCX: 00007f06ae1c9393
Sep 18 10:53:00 bardsey kernel: RDX: 0000000000000003 RSI: 0000000000000000 RDI: 0000000000000000
Sep 18 10:53:00 bardsey kernel: RBP: 00007ffff5074ed0 R08: 0000000000004000 R09: 0000000000000000
Sep 18 10:53:00 bardsey kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000004000
Sep 18 10:53:00 bardsey kernel: R13: 0000000000000001 R14: 0000000000004000 R15: 0000000000000000
Sep 18 10:53:00 bardsey kernel: Code: d8 3b f4 ff 48 89 ee 48 89 df e8 fd 00 5b 00 48 85 c0 48 89 c6 74 75 48 8b 08 48 85 c9 74 6d 48 89 c8 83 e0 03 0f 85 85 00 00 00 <48> 8b 41 20 48 8d 78 ff a8 01 48 0f 44 f9 8b 47 1c 85 c0 74 c4 
Sep 18 10:53:00 bardsey kernel: RIP: find_get_entry+0x3f/0xf0 RSP: ffffb55f8264fb80
Sep 18 10:53:00 bardsey kernel: CR2: 0000000000800020
Sep 18 10:53:00 bardsey kernel: --- end trace 7235ce579f4cc7b2 ]---
Sep 18 10:53:02 bardsey kernel: BUG: unable to handle kernel paging request at 0000000000800020
Sep 18 10:53:02 bardsey kernel: IP: find_get_entry+0x3f/0xf0
Sep 18 10:53:02 bardsey kernel: PGD 0 
Sep 18 10:53:02 bardsey kernel: P4D 0 
Sep 18 10:53:02 bardsey kernel: 
Sep 18 10:53:02 bardsey kernel: Oops: 0000 #4] PREEMPT SMP
Sep 18 10:53:02 bardsey kernel: Modules linked in: fuse bnep nf_log_ipv6 xt_comment nf_log_ipv4 nf_log_common xt_LOG xt_limit af_packet vboxpci(O) vboxnetadp(O) vboxnetflt(O) iscsi_ibft iscsi_boot_sysfs ip6t_REJECT nf_reject_ipv6 nf_conntr
Sep 18 10:53:02 bardsey kernel:  snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm aesni_intel hci_uart btbcm serdev aes_x86_64 btqca crypto_simd r8169 glue_helper btintel snd_timer mii cryptd snd bluetooth tpm_tis ecdh_generic tp
Sep 18 10:53:02 bardsey kernel: CPU: 1 PID: 4382 Comm: systemd-coredum Tainted: G      D W  O    4.13.2-1.g68f4aee-default #1
Sep 18 10:53:02 bardsey kernel: Hardware name: System manufacturer System Product Name/PRIME B250-PRO, BIOS 0608 03/24/2017
Sep 18 10:53:02 bardsey kernel: task: ffff993a66d8e080 task.stack: ffffb55f8889c000
Sep 18 10:53:02 bardsey kernel: RIP: 0010:find_get_entry+0x3f/0xf0
Sep 18 10:53:02 bardsey kernel: RSP: 0018:ffffb55f8889fd08 EFLAGS: 00010246
Sep 18 10:53:02 bardsey kernel: RAX: 0000000000000000 RBX: ffff9939e4830d18 RCX: 0000000000800000
Sep 18 10:53:02 bardsey kernel: RDX: 0000000000000000 RSI: ffff9939e4a3e4a8 RDI: ffff9939e4a3e4a8
Sep 18 10:53:02 bardsey kernel: RBP: 0000000000000c40 R08: ffff9939e4a3e480 R09: 0000000000800000
Sep 18 10:53:02 bardsey kernel: R10: 0000000000000000 R11: 0000000000000040 R12: 0000000000000000
Sep 18 10:53:02 bardsey kernel: R13: ffff9939e4830d10 R14: 0000000000000c40 R15: ffffffffa7e81f80
Sep 18 10:53:02 bardsey kernel: FS:  00007f761c504840(0000) GS:ffff993af6c80000(0000) knlGS:0000000000000000
Sep 18 10:53:02 bardsey kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 18 10:53:02 bardsey kernel: CR2: 0000000000800020 CR3: 0000000377d93000 CR4: 00000000003406e0
Sep 18 10:53:02 bardsey kernel: Call Trace:
Sep 18 10:53:02 bardsey kernel:  pagecache_get_page+0x30/0x200
Sep 18 10:53:02 bardsey kernel:  generic_file_read_iter+0x20d/0x940
Sep 18 10:53:02 bardsey kernel:  ? aa_file_perm+0x196/0x310
Sep 18 10:53:02 bardsey kernel:  ? __handle_mm_fault+0x4b0/0xfd0
Sep 18 10:53:02 bardsey kernel:  __vfs_read+0xd2/0x140
Sep 18 10:53:02 bardsey kernel:  vfs_read+0x89/0x130
Sep 18 10:53:02 bardsey kernel:  SyS_read+0x42/0x90
Sep 18 10:53:02 bardsey kernel:  do_syscall_64+0x57/0xc0
Sep 18 10:53:02 bardsey kernel:  entry_SYSCALL64_slow_path+0x25/0x25
Sep 18 10:53:02 bardsey kernel: RIP: 0033:0x7f761b3e449c
Sep 18 10:53:02 bardsey kernel: RSP: 002b:00007fff11d94168 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
Sep 18 10:53:02 bardsey kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f761b3e449c
Sep 18 10:53:02 bardsey kernel: RDX: 0000000000002000 RSI: 00007fff11d94220 RDI: 0000000000000003
Sep 18 10:53:02 bardsey kernel: RBP: 00007fff11d94190 R08: fffffffffffecf30 R09: 0000000000000000
Sep 18 10:53:02 bardsey kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff11d96220
Sep 18 10:53:02 bardsey kernel: R13: ffffffffffffffff R14: 0000000000000004 R15: 0000000000000000
Sep 18 10:53:02 bardsey kernel: Code: d8 3b f4 ff 48 89 ee 48 89 df e8 fd 00 5b 00 48 85 c0 48 89 c6 74 75 48 8b 08 48 85 c9 74 6d 48 89 c8 83 e0 03 0f 85 85 00 00 00 <48> 8b 41 20 48 8d 78 ff a8 01 48 0f 44 f9 8b 47 1c 85 c0 74 c4 
Sep 18 10:53:02 bardsey kernel: RIP: find_get_entry+0x3f/0xf0 RSP: ffffb55f8889fd08
-- Reboot --

Hope that helps.

Peter

I have uninstalled drm-kmp-default with the 4.13.2-1.1.g68f4aee kernel and can scale the display resolution.
I am now soak testing the system without the drm-kmp-default module so fingers crossed.

Peter

Having left the system for a while I return to find that it has rebooted itself.
Command journalctl gives be this:

Sep 19 12:30:01 bardsey kernel: BUG: unable to handle kernel paging request at 0000000000800008
Sep 19 12:30:01 bardsey kernel: IP: kernfs_refresh_inode+0x26/0xd0
Sep 19 12:30:01 bardsey kernel: PGD 0 
Sep 19 12:30:01 bardsey kernel: P4D 0 
Sep 19 12:30:01 bardsey kernel: 
Sep 19 12:30:01 bardsey kernel: Oops: 0000 #1] PREEMPT SMP
Sep 19 12:30:01 bardsey kernel: Modules linked in: fuse bnep nf_log_ipv6 xt_comment nf_log_ipv4 nf_log_common xt_LOG xt_limit af_packet vboxpci(O) vboxnetadp(O) vboxnetflt(O) iscsi_ibft iscsi_boot_sysfs ip6t_REJECT nf_reject_ipv6 nf_conntr
Sep 19 12:30:01 bardsey kernel:  asus_wmi hci_uart btbcm r8169 sparse_keymap wmi_bmof mxm_wmi serdev iTCO_vendor_support aesni_intel snd_timer battery mii btqca aes_x86_64 snd pcspkr i2c_i801 btintel crypto_simd glue_helper bluetooth crypt
Sep 19 12:30:01 bardsey kernel: CPU: 0 PID: 6488 Comm: systemd Tainted: G           O    4.13.2-1.g68f4aee-default #1
Sep 19 12:30:01 bardsey kernel: Hardware name: System manufacturer System Product Name/PRIME B250-PRO, BIOS 0608 03/24/2017
Sep 19 12:30:01 bardsey kernel: task: ffff9e05676980c0 task.stack: ffffab6a81a10000
Sep 19 12:30:01 bardsey kernel: RIP: 0010:kernfs_refresh_inode+0x26/0xd0
Sep 19 12:30:01 bardsey kernel: RSP: 0018:ffffab6a81a13ba8 EFLAGS: 00010206
Sep 19 12:30:01 bardsey kernel: RAX: 00000000000081a4 RBX: 0000000000800000 RCX: 0000000000000017
Sep 19 12:30:01 bardsey kernel: RDX: 0000000033625bdd RSI: ffff9e05a6a41310 RDI: ffff9e0566c3c618
Sep 19 12:30:01 bardsey kernel: RBP: ffffab6a81a13bc8 R08: ffff9e05a6a418d0 R09: 0000000000000001
Sep 19 12:30:01 bardsey kernel: R10: ffff9e056758c01c R11: 61c8864680b583eb R12: ffff9e05a6a41310
Sep 19 12:30:01 bardsey kernel: R13: ffff9e0566c3c618 R14: ffffab6a81a13d40 R15: ffff9e0621f49410
Sep 19 12:30:01 bardsey kernel: FS:  00007fb93c2bc8c0(0000) GS:ffff9e0676c00000(0000) knlGS:0000000000000000
Sep 19 12:30:01 bardsey kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 19 12:30:01 bardsey kernel: CR2: 0000000000800008 CR3: 0000000327666000 CR4: 00000000003406f0
Sep 19 12:30:01 bardsey kernel: Call Trace:
Sep 19 12:30:01 bardsey kernel:  kernfs_get_inode+0x8e/0x100
Sep 19 12:30:01 bardsey kernel:  kernfs_iop_lookup+0x76/0xb0
Sep 19 12:30:01 bardsey kernel:  lookup_slow+0x92/0x140
Sep 19 12:30:01 bardsey kernel:  walk_component+0x197/0x310
Sep 19 12:30:01 bardsey kernel:  ? link_path_walk+0x427/0x4d0
Sep 19 12:30:01 bardsey kernel:  ? path_init+0x2b0/0x320
Sep 19 12:30:01 bardsey kernel:  path_lookupat+0x75/0x1d0
Sep 19 12:30:01 bardsey kernel:  filename_lookup+0xa7/0x160
Sep 19 12:30:01 bardsey kernel:  ? aa_file_perm+0x196/0x310
Sep 19 12:30:01 bardsey kernel:  ? inode_io_list_move_locked+0x5a/0xc0
Sep 19 12:30:01 bardsey kernel:  ? vfs_statx+0x63/0xb0
Sep 19 12:30:01 bardsey kernel:  vfs_statx+0x63/0xb0
Sep 19 12:30:01 bardsey kernel:  SYSC_newfstatat+0x1e/0x40
Sep 19 12:30:01 bardsey kernel:  ? __audit_syscall_entry+0xab/0x100
Sep 19 12:30:01 bardsey kernel:  ? syscall_trace_enter+0x1c2/0x2b0
Sep 19 12:30:01 bardsey kernel:  ? __audit_syscall_exit+0x231/0x2c0
Sep 19 12:30:01 bardsey kernel:  do_syscall_64+0x57/0xc0
Sep 19 12:30:01 bardsey kernel:  entry_SYSCALL64_slow_path+0x25/0x25
Sep 19 12:30:01 bardsey kernel: RIP: 0033:0x7fb93aaf3d9a
Sep 19 12:30:01 bardsey kernel: RSP: 002b:00007ffecfd3f078 EFLAGS: 00000246 ORIG_RAX: 0000000000000106
Sep 19 12:30:01 bardsey kernel: RAX: ffffffffffffffda RBX: 00007ffecfd3f570 RCX: 00007fb93aaf3d9a
Sep 19 12:30:01 bardsey kernel: RDX: 00007ffecfd3f090 RSI: 0000560b278be833 RDI: 0000000000000009
Sep 19 12:30:01 bardsey kernel: RBP: 0000560b278be833 R08: 0000000000000100 R09: 0000560b278be858
Sep 19 12:30:01 bardsey kernel: R10: 0000000000000100 R11: 0000000000000246 R12: 00007ffecfd3f090
Sep 19 12:30:01 bardsey kernel: R13: 00007ffecfd3f180 R14: 0000000000000008 R15: 0000560b278af000
Sep 19 12:30:01 bardsey kernel: Code: 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 41 56 41 55 41 54 53 49 89 fd 48 8b 5f 70 0f b7 47 6a 49 89 f4 48 85 db 66 89 06 74 7c <8b> 43 08 4c 8b 76 28 89 46 04 8b 43 0c 89 46 08 48 8b 7b 18 48 
Sep 19 12:30:01 bardsey kernel: RIP: kernfs_refresh_inode+0x26/0xd0 RSP: ffffab6a81a13ba8
Sep 19 12:30:01 bardsey kernel: CR2: 0000000000800008
Sep 19 12:30:01 bardsey kernel: --- end trace cc9b41053a8c9764 ]---
Sep 19 12:30:01 bardsey systemd[6489]: pam_unix(systemd-user:session): session closed for user root
-- Reboot --

Which looks to my inexperienced eye like disk activity, am I right?

Is there any further information I can find out?

Peter

Hi
Get rid of the modules that taint the kernel (vbox?) and then does it duplicate, can’t raise a bug if it’s tainted…

OK Malcolm I have removed virtualbox which took virtualbox-host-source and virtualbox-qt with it. I also removed virtualbox-host-kmp-default.

I had to do a reboot with the big red button as the system crashed.

On reboot I reinstalled kernel-default, kernel-devel and kernel-default-devel (all 4.13.2-1.1.g68f4aee) which pulled in drm-kmp-default so I removed that again.

I have now rebooted and await eventualities.

Anything else to look for?

Thanks Peter

Hi
Well it’s wait an see now… if it doesn’t happen, then I would have to assume it could be tied to vbox… One of the other reasons to run KVM :wink:

Bad news. The system has crashed again. This time there was no record in journalctl other than a hint.
The journal has a cron job each quarter hour until 12:45. The 13:00, 13:15 and 13:30 records are missing:

Sep 20 12:30:01 bardsey CRON[4586]: pam_unix(crond:session): session closed for user root
Sep 20 12:30:01 bardsey systemd[1]: Stopping User Manager for UID 0...
Sep 20 12:30:01 bardsey systemd[4587]: Stopped target Default.
Sep 20 12:30:01 bardsey systemd[4587]: Stopped target Basic System.
Sep 20 12:30:01 bardsey systemd[4587]: Stopped target Paths.
Sep 20 12:30:01 bardsey systemd[4587]: Stopped target Timers.
Sep 20 12:30:01 bardsey systemd[4587]: Stopped target Sockets.
Sep 20 12:30:01 bardsey systemd[4587]: Reached target Shutdown.
Sep 20 12:30:01 bardsey systemd[4587]: Starting Exit the Session...
Sep 20 12:30:01 bardsey systemd[4587]: Received SIGRTMIN+24 from PID 4622 (kill).
Sep 20 12:30:01 bardsey systemd[4588]: pam_unix(systemd-user:session): session closed for user root
Sep 20 12:30:01 bardsey systemd[1]: Stopped User Manager for UID 0.
Sep 20 12:30:01 bardsey systemd[1]: Removed slice User Slice of root.
Sep 20 12:45:01 bardsey cron[4694]: pam_unix(crond:session): session opened for user root by (uid=0)
Sep 20 12:45:01 bardsey systemd[1]: Created slice User Slice of root.
Sep 20 12:45:01 bardsey systemd[1]: Starting User Manager for UID 0...
Sep 20 12:45:01 bardsey systemd[1]: Started Session 18 of user root.
Sep 20 12:45:01 bardsey systemd[4695]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Sep 20 12:45:01 bardsey systemd[4695]: Reached target Paths.
Sep 20 12:45:01 bardsey systemd[4695]: Reached target Timers.
Sep 20 12:45:01 bardsey systemd[4695]: Reached target Sockets.
Sep 20 12:45:01 bardsey systemd[4695]: Reached target Basic System.
Sep 20 12:45:01 bardsey systemd[4695]: Reached target Default.
Sep 20 12:45:01 bardsey systemd[4695]: Startup finished in 11ms.
Sep 20 12:45:01 bardsey systemd[1]: Started User Manager for UID 0.
Sep 20 12:45:11 bardsey dbus[889]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Sep 20 12:45:11 bardsey dbus[889]: [system] Successfully activated service 'org.opensuse.Snapper'
Sep 20 12:45:34 bardsey kernel: BTRFS info (device sda3): qgroup scan completed (inconsistency flag cleared)
-- Reboot --
Sep 20 13:44:17 linux-8v7o systemd-journald[167]: Runtime journal (/run/log/journal/) is currently using 8.0M.
                                                  Maximum allowed usage is set to 795.3M.
                                                  Leaving at least 1.1G free (of currently available 7.7G of space).
                                                  Enforced usage limit is thus 795.3M, of which 787.3M are still available.
Sep 20 13:44:17 linux-8v7o kernel: microcode: microcode updated early to revision 0x5e, date = 2017-04-06

After waking the system with a keystroke (no log in) kontact was in focus. I pressed the keypad ‘+’ key to see the next unread message but kontact crashed with the usual KDE application crash dialogue. I could not complete this as the system stopped responding soon after.

Is there any way I can ensure that the kernel is untainted?
Do I have to just wait for a total crash and self-reboot to get that useful information that I was able to post last time?

Peter

On Wed 20 Sep 2017 01:06:01 PM CDT, pblewis wrote:

Bad news. The system has crashed again. This time there was no record in
journalctl other than a hint.
The journal has a cron job each quarter hour until 12:45. The 13:00,
13:15 and 13:30 records are missing:

Code:

Sep 20 12:30:01 bardsey CRON[4586]: pam_unix(crond:session):
session closed for user root Sep 20 12:30:01 bardsey systemd[1]:
Stopping User Manager for UID 0… Sep 20 12:30:01 bardsey
systemd[4587]: Stopped target Default. Sep 20 12:30:01 bardsey
systemd[4587]: Stopped target Basic System. Sep 20 12:30:01 bardsey
systemd[4587]: Stopped target Paths. Sep 20 12:30:01 bardsey
systemd[4587]: Stopped target Timers. Sep 20 12:30:01 bardsey
systemd[4587]: Stopped target Sockets. Sep 20 12:30:01 bardsey
systemd[4587]: Reached target Shutdown. Sep 20 12:30:01 bardsey
systemd[4587]: Starting Exit the Session… Sep 20 12:30:01 bardsey
systemd[4587]: Received SIGRTMIN+24 from PID 4622 (kill). Sep 20
12:30:01 bardsey systemd[4588]: pam_unix(systemd-user:session): session
closed for user root Sep 20 12:30:01 bardsey systemd[1]: Stopped User
Manager for UID 0. Sep 20 12:30:01 bardsey systemd[1]: Removed slice
User Slice of root. Sep 20 12:45:01 bardsey cron[4694]:
pam_unix(crond:session): session opened for user root by (uid=0) Sep 20
12:45:01 bardsey systemd[1]: Created slice User Slice of root. Sep 20
12:45:01 bardsey systemd[1]: Starting User Manager for UID 0… Sep 20
12:45:01 bardsey systemd[1]: Started Session 18 of user root. Sep 20
12:45:01 bardsey systemd[4695]: pam_unix(systemd-user:session): session
opened for user root by (uid=0) Sep 20 12:45:01 bardsey systemd[4695]:
Reached target Paths. Sep 20 12:45:01 bardsey systemd[4695]: Reached
target Timers. Sep 20 12:45:01 bardsey systemd[4695]: Reached target
Sockets. Sep 20 12:45:01 bardsey systemd[4695]: Reached target Basic
System. Sep 20 12:45:01 bardsey systemd[4695]: Reached target Default.
Sep 20 12:45:01 bardsey systemd[4695]: Startup finished in 11ms. Sep 20
12:45:01 bardsey systemd[1]: Started User Manager for UID 0. Sep 20
12:45:11 bardsey dbus[889]: [system] Activating service
name=‘org.opensuse.Snapper’ (using servicehelper) Sep 20 12:45:11
bardsey dbus[889]: [system] Successfully activated service
‘org.opensuse.Snapper’ Sep 20 12:45:34 bardsey kernel: BTRFS info
(device sda3): qgroup scan completed (inconsistency flag cleared) –
Reboot – Sep 20 13:44:17 linux-8v7o systemd-journald[167]: Runtime
journal (/run/log/journal/) is currently using 8.0M. Maximum allowed
usage is set to 795.3M. Leaving at least 1.1G free (of currently
available 7.7G of space). Enforced usage limit is thus 795.3M, of which
787.3M are still available. Sep 20 13:44:17 linux-8v7o kernel:
microcode: microcode updated early to revision 0x5e, date = 2017-04-06

After waking the system with a keystroke (no log in) kontact was in
focus. I pressed the keypad ‘+’ key to see the next unread message but
kontact crashed with the usual KDE application crash dialogue. I could
not complete this as the system stopped responding soon after.

Is there any way I can ensure that the kernel is untainted?
Do I have to just wait for a total crash and self-reboot to get that
useful information that I was able to post last time?

Peter

Hi
OK, sounds like at this point two issues, one kernel (vbox) and one for
the desktop, so if not getting the kernel output now, that’s possibly
identified one issue…

So you might just have to peruse the last log with journalctl -x are
there any core dumps (coredumpctl list)?


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.79-18.26-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

I have had another crash and this time I was able to reboot the machine.
An initial crash in Firefox followed by konsole and akonadi while the system was rebooting.
journalctl -x output of those evernts:

Sep 20 15:20:57 bardsey systemd-coredump[3875]: Process 3846 (Web Content) of user 500 dumped core.
-- Subject: Process 3846 (Web Content) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 3846 (Web Content) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.

<--snip-->

Sep 20 15:23:58 bardsey systemd-coredump[4117]: Process 3251 (konsole) of user 500 dumped core.
-- Subject: Process 3251 (konsole) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 3251 (konsole) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.

<--snip-->

Sep 20 15:24:03 bardsey systemd-coredump[4119]: Process 2769 (akonadiserver) of user 500 dumped core.
-- Subject: Process 2769 (akonadiserver) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 2769 (akonadiserver) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.

Then the coredumpctl list and info:

Wed 2017-09-20 15:20:57 BST    3846   500   500  11 * /usr/lib64/firefox/plugin-container
Wed 2017-09-20 15:23:58 BST    3251   500   500  11 * /usr/bin/konsole
Wed 2017-09-20 15:24:03 BST    2769   500   500  11 * /usr/bin/akonadiserver

peter@bardsey:~> coredumpctl info 3846
           PID: 3846 (Web Content)
           UID: 500 (peter)
           GID: 500 (users)
        Signal: 11 (SEGV)
     Timestamp: Wed 2017-09-20 15:20:47 BST (34min ago)
  Command Line: /usr/lib64/firefox/plugin-container -greomni /usr/lib64/firefox/omni.ja -appomni /usr/lib64/firefox/browser/omni.ja -appdir /usr/lib64/firefox/browser 2754 true tab
    Executable: /usr/lib64/firefox/plugin-container
 Control Group: /
         Slice: -.slice
       Boot ID: ae35694854f34aceb0f4d54a4fabb869
    Machine ID: 73d2a4d6650229ffeec74d4e59afd99b
      Hostname: bardsey
      Coredump: /var/lib/systemd/coredump/core.Web\x20Content.500.ae35694854f34aceb0f4d54a4fabb869.3846.1505917247000000.xz
       Message: Process 3846 (Web Content) of user 500 dumped core.
peter@bardsey:~> coredumpctl info 3251
           PID: 3251 (konsole)
           UID: 500 (peter)
           GID: 500 (users)
        Signal: 11 (SEGV)
     Timestamp: Wed 2017-09-20 15:23:52 BST (32min ago)
  Command Line: /usr/bin/konsole
    Executable: /usr/bin/konsole
 Control Group: /user.slice/user-500.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-500.slice
       Session: 2
     Owner UID: 500 (peter)
       Boot ID: ae35694854f34aceb0f4d54a4fabb869
    Machine ID: 73d2a4d6650229ffeec74d4e59afd99b
      Hostname: bardsey
      Coredump: /var/lib/systemd/coredump/core.konsole.500.ae35694854f34aceb0f4d54a4fabb869.3251.1505917432000000.xz
       Message: Process 3251 (konsole) of user 500 dumped core.
peter@bardsey:~> coredumpctl info 2769
           PID: 2769 (akonadiserver)
           UID: 500 (peter)
           GID: 500 (users)
        Signal: 11 (SEGV)
     Timestamp: Wed 2017-09-20 15:23:57 BST (32min ago)
  Command Line: akonadiserver
    Executable: /usr/bin/akonadiserver
 Control Group: /
         Slice: -.slice
       Boot ID: ae35694854f34aceb0f4d54a4fabb869
    Machine ID: 73d2a4d6650229ffeec74d4e59afd99b
      Hostname: bardsey
      Coredump: /var/lib/systemd/coredump/core.akonadiserver.500.ae35694854f34aceb0f4d54a4fabb869.2769.1505917437000000.xz
       Message: Process 2769 (akonadiserver) of user 500 dumped core.
peter@bardsey:~>

The core dump files are 3.9, 1.2 and 1.1 megabytes.

Can I inspect the core dumps for anything?

Peter