Comments

29 Comments

Both the default and performance kernel tests passed. Intel i7-6850K, ASUS X99 MB, 64G RAM, RX 590 GPU

Both the default and performance kernel tests passed. Intel i7-6850K, ASUS X99 MB, 64G RAM, RX 590 GPU

karma

Both the default and performance kernel tests passed. Intel i7-6850K, ASUS X99 MB, 64G RAM, RX 590 GPU

karma

Both the default and performance kernel tests passed. Intel i7-6850K, ASUS X99 MB, 64G RAM, AMD R9 390 GPU

karma

Both the default and performance kernel tests passed. Intel i7-6850K, ASUS X99 MB, 64G RAM, RX 590 GPU

Both the default and performance kernel tests passed. Intel i7-6850K, ASUS X99 MB, 64G RAM, RX 590 GPU

Both the default and performance kernel tests passed. Intel i7-6850K, ASUS X99 MB, 64G RAM, RX 590 GPU

Both the default and performance kernel tests passed. Intel i7-6850K, 64G RAM, RX 590 GPU

Both the default and performance kernel tests passed. Intel i7-6850K, 64G RAM, RX 590 GPU

Edit Adding karma for kernel test run.

Tested on Intel i7-6850K, 64Gb RAM, MSI R9 390 GPU, both the default and performance tests ran without error.

Tested on Intel i7-6850K, 64Gb RAM, MSI R9 390 GPU, both the default and performance tests ran without error.

The update seems to have fixed #1665740 but I am experiencing #1665521 and getting GLIB_CRITICAL errors in the journal after applying the patch.

*** Last reboot before applying patch

Jan 16 02:24:33 red-dwarf gnome-session[2488]: gnome-session-binary[2488]: GLib-CRITICAL: g_child_watch_add_full: assertion 'pid > 0' failed Jan 16 02:24:33 red-dwarf gnome-session-binary[2488]: GLib-CRITICAL: g_child_watch_add_full: assertion 'pid > 0' failed

*** Reboot after patch applied

Jan 16 03:03:27 red-dwarf gnome-session[2492]: gnome-session-binary[2492]: GLib-CRITICAL: g_child_watch_add_full: assertion 'pid > 0' failed Jan 16 03:03:27 red-dwarf gnome-session-binary[2492]: GLib-CRITICAL: g_child_watch_add_full: assertion 'pid > 0' failed

Note: I am running Kernel 4.20.1-200.fc29.x86_64 for the test day.

BZ#1665521 GLib-CRITICAL: g_child_watch_add_full: assertion 'pid > 0' failed
BZ#1665740 abrt-applet creates "weird" directories in my home directory

No problems on Intel i7-6850K after update, both the default and performance kernel tests passed.

Everything working OK after update. Both the default and performance kernel tests passed.

Everything working OK after update. Both the default and performance kernel tests passed.

Everything working OK after update. Both the default and performance kernel tests passed.

System is working as normal and both the standard and performance kernel test have passed on Intel i7-6850K, 64GB RAM, MSI R9 390 GPU.

System is working as normal and both the standard and performance kernel test have passed on Intel i7-6850K, 64GB RAM, MSI R9 390 GPU.

I am assuming that other testers have not had to re-compile the kernel test suite as I still need to patch the lmbench source locally in order to compile the performance test. I've submitted a pull request with fix for the compilation errors.

Update: Just discovered that this a known issue with the kernel-test suite and that jforbes is looking into it.

https://pagure.io/kernel-tests/issue/25

I've managed to get lmbench to build with gcc 8.2.1 20180801 by changing the seekto() function in disk.c to use lseek64 rather than llseek.

I am not sure what the correct long term solution would be or if this is even an issue others might encounter or specific to my build environment but perhaps someone more familiar with Linux development than me can take a look a the disk.c source (specifically the seekto() function) and suggest the correct version of lseek to use.

Once lmbench builds the performance tests run ok and pass.