Not a member yet? Why not Sign up today
Create an account  

Welcome, Guest
You have to register before you can post on our site.

Username/Email:
  

Password
  





Search Forums

(Advanced Search)

Latest Threads
XanMod Kernel
Forum: Releases
Last Post: tropic
10 hours ago
» Replies: 388
» Views: 81,244
10min netdev budget ran o...
Forum: General Discussion
Last Post: tropic
10 hours ago
» Replies: 3
» Views: 29
Nice quotes for a better ...
Forum: General Discussion
Last Post: Guest
17-02-2018, 05:19 PM
» Replies: 70
» Views: 9,219
Slow system start and una...
Forum: General Discussion
Last Post: tropic
16-02-2018, 04:27 PM
» Replies: 7
» Views: 98
Brainstorming for XanMod ...
Forum: Development
Last Post: tropic
16-02-2018, 04:10 PM
» Replies: 140
» Views: 15,835
Kernel compiling problems...
Forum: Development
Last Post: spektykles
14-02-2018, 07:53 AM
» Replies: 8
» Views: 85
uksm
Forum: General Discussion
Last Post: tropic
09-02-2018, 02:04 PM
» Replies: 2
» Views: 68
VirtualBox 5.2.x related ...
Forum: General Discussion
Last Post: tropic
06-02-2018, 02:24 AM
» Replies: 6
» Views: 700
XanMod 4.15.0,1 'file mis...
Forum: Bug Report
Last Post: tropic
06-02-2018, 02:22 AM
» Replies: 2
» Views: 162
Intel and AMD microcodes
Forum: Releases
Last Post: tropic
05-02-2018, 02:42 PM
» Replies: 12
» Views: 5,989

 
Forum Statistics

Members: 318,   Latest member: NapoleonRu,   Forum threads: 134,   Forum posts: 2,551,   Full Statistics


  10min netdev budget ran outs
Posted by: neoark - Yesterday, 03:21 PM - Forum: General Discussion - Replies (3)

With netdata I am seeing a lot of 10min netdev budget ran outs ~40. There might be an issue with timeslice. It net.core.netdev_budget but I am still seeing these errors. Something might need to be tweaked in 4.15.

Print this item

  Slow system start and unable to close down and software switch off the power
Posted by: R871247G - 14-02-2018, 10:00 PM - Forum: General Discussion - Replies (7)

I am running Ubuntu-gnome 16.04 LTS AMD 64 on a desktop computer.
AMD A10-7800 Radeon R7, 12 Compute Cores 4C+8
GNOME Shell 3.18.5 (which often crashes)

I ran systemd-analyze blame > blame.txt

I am not sure if xanmod has anything to do with the delays and the close down problem, but in view of the depth of knowledge shown here, I decided to ask here first if there is a known solution to one or both problems

The top 5 delays were:

24.519s apt-daily.service
5.384s NetworkManager-wait-online.service
5.272s udev-configure-printer@-devices-pci0000:00-0000:00:15.0-0000:02:00.0-usb10-10\x2d1-10\x2d1.3.service
5.212s plymouth-quit-wait.service

I am currently running
4.14.17-xanmod21

Robin

Print this item

  Kernel compiling problems with PDS
Posted by: spektykles - 10-02-2018, 07:43 PM - Forum: Development - Replies (8)

Hi, Im trying to compiling Xanmod kernel with some modifications (not related to PDS anyway) and got this error. Source: 4.15.2-xanmod3 using gcc version 8.0.1 20180208 (experimental) [trunk revision 257477], Ofast + LTO + Skylake march + thunk-inline flags ) with some minor modifications on F2FS and Retpoline. Used GCC 7.3 and got this too so its not GCC 8 problem. Not a big one to fix but it would be nice to inform the PDS guy and take a look at it. Thanks
P/S: Im new to this forum so I dont know where to properly file this bug. And pardon for my English.
Snippet of my log:

Code:
CC [M]  fs/aufs/mvdown.o
  CC      kernel/sched/pds.o
  CC      kernel/sched/loadavg.o
  CC      mm/frame_vector.o
  CC [M]  crypto/camellia_generic.o
  CC      arch/x86/kernel/fpu/xstate.o
  CC [M]  fs/aufs/ioctl.o
  CC      mm/usercopy.o
  CC      mm/hmm.o
kernel/sched/pds.c: In function ‘sched_init’:
kernel/sched/pds.c:6348:30: error: passing argument 2 of ‘open_softirq’ from incompatible pointer type [-Werror=incompatible-pointer-types]
  open_softirq(SCHED_SOFTIRQ, pds_run_rebalance);
                              ^~~~~~~~~~~~~~~~~
In file included from ./include/linux/kernel_stat.h:9:0,
                 from ./include/linux/cgroup.h:26,
                 from ./include/linux/perf_event.h:57,
                 from ./include/linux/trace_events.h:10,
                 from ./include/trace/syscall.h:7,
                 from ./include/linux/syscalls.h:82,
                 from kernel/sched/pds.c:32:
./include/linux/interrupt.h:503:20: note: expected ‘void (*)(void)’ but argument is of type ‘void (*)(struct softirq_action *)’
 extern void __init open_softirq(int nr, void (*action)(void));
                    ^~~~~~~~~~~~
  CC [M]  mm/hwpoison-inject.o
  CC      kernel/sched/clock.o
  CC [M]  kernel/rcu/rcuperf.o

Print this item

  uksm
Posted by: SeventhSon - 08-02-2018, 04:59 AM - Forum: General Discussion - Replies (2)

Hello!

Can anyone please post an instruction how to get xanmod sources, apply UKSM patch and install patched kernel?

P.S.
My current OS Ubuntu

Print this item

  4.15 will not boot, but 4.14 does perfectly?
Posted by: SkOrPn - 03-02-2018, 08:29 AM - Forum: Bug Report - Replies (2)

Hello again,  Smile

I'm now on LM 18.3 with a Intel Xeon X5650. I decided to give Xanmod 4.15 a try but the Linux Mint boot screen just stays busy forever it seems, and I tried several times but its just stuck. So, I decided to try 4.14.15 instead and it boots perfectly, thanks.

Is this because Linux Mint 18.3 only allows you to boot on LTS kernels? What should I do to try 4.15? Or should I purge 4.15 and stick with 4.14 LTS for now? If I should stick to 4.14, how can I purge 4.15 please?

Thank you greatly for any advice, or purge help. Thanks

Best Regards
Rod

Print this item

  XanMod 4.15.0,1 'file missing' building Virtualbox Guest Additions 5.2.6,7 [solved]
Posted by: tropic - 30-01-2018, 01:02 PM - Forum: Bug Report - Replies (2)

Error and some warnings while building Virtualbox Guest Additions modules:

Code:
Building the main Guest Additions module.
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.15.0-xanmod1/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j1 modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 "  ERROR: Kernel configuration is invalid."; \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/tmp/vbox.0
  gcc -Wp,-MD,/tmp/vbox.0/.VBoxGuest-linux.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/5/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=1024 -fstack-protector-strong -Wno-unused-but-set-variable -fno-var-tracking-assignments -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wno-declaration-after-statement -include /tmp/vbox.0/include/VBox/VBoxGuestMangling.h -fno-pie -I/lib/modules/4.15.0-xanmod1/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxguest/ -I/tmp/vbox.0/vboxguest/include -I/tmp/vbox.0/vboxguest/r0drv/linux -D__KERNEL__ -DMODULE -DVBOX -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_GUEST -DIN_GUEST_R0 -DIN_MODULE -DRT_WITH_VBOX -DVBGL_VBOXGUEST -DVBOX_WITH_HGCM -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS  -DMODULE  -DKBUILD_BASENAME='"VBoxGuest_linux"'  -DKBUILD_MODNAME='"vboxguest"' -c -o /tmp/vbox.0/VBoxGuest-linux.o /tmp/vbox.0/VBoxGuest-linux.c
In file included from ./include/linux/module.h:18:0,
                 from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:88,
                 from /tmp/vbox.0/VBoxGuest-linux.c:36:
/tmp/vbox.0/VBoxGuest-linux.c:1165:35: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log,            vgdrvLinuxParamLogGrpSet,   vgdrvLinuxParamLogGrpGet,   NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1165:35: note: (near initialization for ‘__param_ops_log.set’)
 module_param_call(log,            vgdrvLinuxParamLogGrpSet,   vgdrvLinuxParamLogGrpGet,   NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1165:63: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log,            vgdrvLinuxParamLogGrpSet,   vgdrvLinuxParamLogGrpGet,   NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1165:63: note: (near initialization for ‘__param_ops_log.get’)
 module_param_call(log,            vgdrvLinuxParamLogGrpSet,   vgdrvLinuxParamLogGrpGet,   NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1166:35: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log_flags,      vgdrvLinuxParamLogFlagsSet, vgdrvLinuxParamLogFlagsGet, NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1166:35: note: (near initialization for ‘__param_ops_log_flags.set’)
 module_param_call(log_flags,      vgdrvLinuxParamLogFlagsSet, vgdrvLinuxParamLogFlagsGet, NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1166:63: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log_flags,      vgdrvLinuxParamLogFlagsSet, vgdrvLinuxParamLogFlagsGet, NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1166:63: note: (near initialization for ‘__param_ops_log_flags.get’)
 module_param_call(log_flags,      vgdrvLinuxParamLogFlagsSet, vgdrvLinuxParamLogFlagsGet, NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1167:35: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log_dest,       vgdrvLinuxParamLogDstSet,   vgdrvLinuxParamLogDstGet,   NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1167:35: note: (near initialization for ‘__param_ops_log_dest.set’)
 module_param_call(log_dest,       vgdrvLinuxParamLogDstSet,   vgdrvLinuxParamLogDstGet,   NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1167:63: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log_dest,       vgdrvLinuxParamLogDstSet,   vgdrvLinuxParamLogDstGet,   NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1167:63: note: (near initialization for ‘__param_ops_log_dest.get’)
 module_param_call(log_dest,       vgdrvLinuxParamLogDstSet,   vgdrvLinuxParamLogDstGet,   NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1173:35: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(r3_log_to_host, vgdrvLinuxParamR3LogToHostSet, vgdrvLinuxParamR3LogToHostGet, NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1173:35: note: (near initialization for ‘__param_ops_r3_log_to_host.set’)
 module_param_call(r3_log_to_host, vgdrvLinuxParamR3LogToHostSet, vgdrvLinuxParamR3LogToHostGet, NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1173:66: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(r3_log_to_host, vgdrvLinuxParamR3LogToHostSet, vgdrvLinuxParamR3LogToHostGet, NULL, 0664);

                                                                  ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1173:66: note: (near initialization for ‘__param_ops_r3_log_to_host.get’)
 module_param_call(r3_log_to_host, vgdrvLinuxParamR3LogToHostSet, vgdrvLinuxParamR3LogToHostGet, NULL, 0664);

                                                                  ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
cc1: some warnings being treated as errors
scripts/Makefile.build:316: fallo en las instrucciones para el objetivo '/tmp/vbox.0/VBoxGuest-linux.o'
make[2]: *** [/tmp/vbox.0/VBoxGuest-linux.o] Error 1
Makefile:1508: fallo en las instrucciones para el objetivo '_module_/tmp/vbox.0'
make[1]: *** [_module_/tmp/vbox.0] Error 2
/tmp/vbox.0/Makefile.include.footer:101: fallo en las instrucciones para el objetivo 'vboxguest'
make: *** [vboxguest] Error 2
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.

I'm not sure if the cause is from Xanmod or from Virtualbox itself, however some info about "invalid kernel configuration" is shown:

Code:
echo >&2;                            \
echo >&2 "  ERROR: Kernel configuration is invalid.";        \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";    \
echo >&2 ;

Print this item

  4.15
Posted by: CybDex - 29-01-2018, 03:37 PM - Forum: General Discussion - Replies (3)

Guess 4.15 was released yesterday:

Code:
mainline:
[b]4.15[/b]
2018-01-28
Holding my breath while waiting for 4.15.0-xanmod1 ! Angel

Print this item

  4.14.13-xanmod17 [solved]
Posted by: CybDex - 12-01-2018, 02:34 PM - Forum: Bug Report - Replies (3)

What does this message in dmesg with the latest 4.14.13-xanmod17 mean?

Code:
[    0.000000]
[    0.000000] **********************************************************
[    0.000000] **   NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE   **
[    0.000000] **                                                      **
[    0.000000] ** trace_printk() being used. Allocating extra memory.  **
[    0.000000] **                                                      **
[    0.000000] ** This means that this is a DEBUG kernel and it is     **
[    0.000000] ** unsafe for production use.                           **
[    0.000000] **                                                      **
[    0.000000] ** If you see this message and you are not debugging    **
[    0.000000] ** the kernel, report this immediately to your vendor!  **
[    0.000000] **                                                      **
[    0.000000] **   NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE   **
[    0.000000] **********************************************************


C

Print this item

  use of intel_pstate in passive
Posted by: jki - 11-01-2018, 07:33 PM - Forum: General Discussion - Replies (1)

I just wanted to ask why exactly this is used in xanmod.
Is the performance better in passive mode ?

Print this item

  Xanmod16 vs Xanmod17 - bench
Posted by: CybDex - 11-01-2018, 07:02 PM - Forum: General Discussion - Replies (3)

Oki.. just grabbed the latest 4.14.13-xanmod17, and from what i saw some post about yesterday it was some tweak regarding interactivity.. or something like that Smile

Anyway.. Did some benchies, and got some results:
[Image: Complete.jpg]
I did a "make -j8" of a wine build in a loop while doing theese (make -j8) results, and overall it is a increase.. Not sure why redis was a huge drop while compiling tho, but i guess it all pans out. Unigine-Valley got a slight bump and that i like Smile

Also tested wine-staging-2.18 with Unigine Valley in DX11 mode, and the results:

Code:
xanmod16                        77.7 fps (3252)
xanmod16 (make -j8)             14.3 fps (598)

xanmod17                        77.9 fps (3258)
xanmod17 (make -j8)             14.5 fps (605)

[url=https://ibb.co/cqnWnR][/url]
Again, a slight bump for the 4.14.13-xanmod17 kernel Big Grin 

Conclusion for MY part: I like! Smile

C

Print this item

Online Users
There are currently 17 online users. » 0 Member(s) | 17 Guest(s)