unofficial linux-ck repo with cpu optimized packages is ONLINE

mauritiusdadd · 2015-05-17 19:23:14

nomorewindows wrote:

Do you do something different with linux-ck? Because I tried nvidia-ck and now I get the nvidia logo whereas I don't get it with stock kernel and nvidia.

It sometimes appears on my desktop too (it does not last more than few hundred milliseconds) but, if I remember correctly, it happened sometime also using the stock nvidia package.

paneless · 2015-05-17 19:45:01

Ok, 4.0.3-3-ck ran all day yesterday approx 25 full power off / on reboots no panics. This morning again 4 or 5 full reboots without issue. System not started for about six hours and first attempt to boot resulted in panic, and once again no trace recorded in journalctl. I have rebooted three or four times since without any problems. Will keep testing 4.0.3-3 and hopefully will be able to get at least some useful info.

mauritiusdadd · 2015-05-18 07:57:53

For me 4.0.3-3-ck still panics, soon or later, at every boot. I added another couple of memory dumps and dmesg outputs (see my previous post). However I just learnt that the the call-trace shown by dmesg refers to last active task running (that is ksoftirqd in my case) and that there can be other processes that failed too. Then I run crash on every kernel memory dump I collected and noticed that in each of them there is at least another process that fails before ksoftirqd and it is BFS/n (which I think it is the CK's cpu scheduelr, right?). The following are the call-traces for each BFS/n extracted form vmcore-4.dump. I hope this helps.

PID: 0      TASK: ffffffff818124c0  CPU: 0   COMMAND: "BFS/0"
 #0 [ffffffff81803de0] __schedule at ffffffff81553586
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/kernel/sched/bfs.c: 1972
 #1 [ffffffff81803e60] schedule at ffffffff81554007
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/./arch/x86/include/asm/bitops.h: 311
 #2 [ffffffff81803e80] schedule_preempt_disabled at ffffffff81554285
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/./arch/x86/include/asm/preempt.h: 72
 #3 [ffffffff81803e90] cpu_startup_entry at ffffffff810a195d
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/kernel/sched/idle.c: 285
 #4 [ffffffff81803f10] rest_init at ffffffff81548b20
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/init/main.c: 408
 #5 [ffffffff81803f30] start_kernel at ffffffff818d7030
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/init/main.c: 675
 #6 [ffffffff81803f70] x86_64_start_reservations at ffffffff818d6339
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/head64.c: 201
 #7 [ffffffff81803f80] x86_64_start_kernel at ffffffff818d649c
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/head64.c: 190

PID: 0      TASK: ffff8801981d2000  CPU: 1   COMMAND: "BFS/1"
 #0 [ffff88019f245e20] crash_nmi_callback at ffffffff8104a7e1
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/./arch/x86/include/asm/paravirt.h: 116
 #1 [ffff88019f245e30] nmi_handle at ffffffff81019fcc
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/nmi.c: 132
 #2 [ffff88019f245ea0] default_do_nmi at ffffffff8101a5ea
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/nmi.c: 336
 #3 [ffff88019f245ed0] do_nmi at ffffffff8101a768
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/nmi.c: 538
 #4 [ffff88019f245ef0] end_repeat_nmi at ffffffff81559ea1
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/entry_64.S: 1680
    [exception RIP: intel_idle+212]
    RIP: ffffffff813243e4  RSP: ffff8801981e7e18  RFLAGS: 00000046
    RAX: 0000000000000030  RBX: 0000000000000010  RCX: 0000000000000001
    RDX: 0000000000000000  RSI: ffff8801981e7fd8  RDI: 0000000000000001
    RBP: ffff8801981e7e48   R8: 0000011601adf872   R9: ffff88019f250f2c
    R10: 0000000000000008  R11: 0000000000000f42  R12: 0000000000000030
    R13: 0000000000000004  R14: 0000000000000005  R15: 000000a24b3d3f9b
    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/./arch/x86/include/asm/thread_info.h: 162
--- <NMI exception stack> ---
 #5 [ffff8801981e7e18] intel_idle at ffffffff813243e4
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/./arch/x86/include/asm/thread_info.h: 162
 #6 [ffff8801981e7e50] cpuidle_enter_state at ffffffff81411305
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/drivers/cpuidle/cpuidle.c: 167
 #7 [ffff8801981e7ea0] cpuidle_enter at ffffffff81411497
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/drivers/cpuidle/cpuidle.c: 224
 #8 [ffff8801981e7eb0] cpu_startup_entry at ffffffff810a1b10
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/kernel/sched/idle.c: 177
 #9 [ffff8801981e7f30] start_secondary at ffffffff8104baaa
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/smpboot.c: 273

PID: 0      TASK: ffff8801981d2800  CPU: 2   COMMAND: "BFS/2"
 #0 [ffff8801981ebe00] __schedule at ffffffff81553586
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/kernel/sched/bfs.c: 1972
 #1 [ffff8801981ebe80] schedule at ffffffff81554007
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/./arch/x86/include/asm/bitops.h: 311
 #2 [ffff8801981ebea0] schedule_preempt_disabled at ffffffff81554285
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/./arch/x86/include/asm/preempt.h: 72
 #3 [ffff8801981ebeb0] cpu_startup_entry at ffffffff810a195d
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/kernel/sched/idle.c: 285
 #4 [ffff8801981ebf30] start_secondary at ffffffff8104baaa
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/smpboot.c: 273

PID: 0      TASK: ffff8801981d3000  CPU: 3   COMMAND: "BFS/3"
 #0 [ffff88019f2c5e20] crash_nmi_callback at ffffffff8104a7e1
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/./arch/x86/include/asm/paravirt.h: 116
 #1 [ffff88019f2c5e30] nmi_handle at ffffffff81019fcc
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/nmi.c: 132
 #2 [ffff88019f2c5ea0] default_do_nmi at ffffffff8101a5ea
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/nmi.c: 336
 #3 [ffff88019f2c5ed0] do_nmi at ffffffff8101a768
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/nmi.c: 538
 #4 [ffff88019f2c5ef0] end_repeat_nmi at ffffffff81559ea1
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/entry_64.S: 1680
    [exception RIP: intel_idle+212]
    RIP: ffffffff813243e4  RSP: ffff8801981efe18  RFLAGS: 00000046
    RAX: 0000000000000030  RBX: 0000000000000010  RCX: 0000000000000001
    RDX: 0000000000000000  RSI: ffff8801981effd8  RDI: 0000000000000003
    RBP: ffff8801981efe48   R8: 0000011601adf872   R9: ffff88019f2d0f2c
    R10: ffffea0003316680  R11: 0000000000000f43  R12: 0000000000000030
    R13: 0000000000000004  R14: 0000000000000005  R15: 000000a24b3d3ab8
    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/./arch/x86/include/asm/thread_info.h: 162
--- <NMI exception stack> ---
 #5 [ffff8801981efe18] intel_idle at ffffffff813243e4
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/./arch/x86/include/asm/thread_info.h: 162
 #6 [ffff8801981efe50] cpuidle_enter_state at ffffffff81411305
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/drivers/cpuidle/cpuidle.c: 167
 #7 [ffff8801981efea0] cpuidle_enter at ffffffff81411497
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/drivers/cpuidle/cpuidle.c: 224
 #8 [ffff8801981efeb0] cpu_startup_entry at ffffffff810a1b10
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/kernel/sched/idle.c: 177
 #9 [ffff8801981eff30] start_secondary at ffffffff8104baaa
    /home/daddona/ckk/build/linux-ck/src/linux-4.0/arch/x86/kernel/smpboot.c: 273

Last edited by mauritiusdadd (2015-05-18 07:59:49)

akspecs · 2015-05-18 08:33:17

mauritiusdadd wrote:

nomorewindows wrote:
Do you do something different with linux-ck? Because I tried nvidia-ck and now I get the nvidia logo whereas I don't get it with stock kernel and nvidia.
It sometimes appears on my desktop too (it does not last more than few hundred milliseconds) but, if I remember correctly, it happened sometime also using the stock nvidia package.

Have you guys both done what's outlined in the wiki?

https://wiki.archlinux.org/index.php/NV … on_startup

mauritiusdadd · 2015-05-18 10:04:40

akspecs wrote:

Have you guys both done what's outlined in the wiki?

Yeah, you're right, I didn't set the NoLogo option in the configuration file, but the question now is why the logo didn't show up most of the times?

paneless · 2015-05-18 10:33:59

Edit) message posted prior to running update to 4.04.

Last edited by paneless (2015-05-18 15:54:37)

nomorewindows · 2015-05-18 18:24:08

mauritiusdadd wrote:

akspecs wrote:
Have you guys both done what's outlined in the wiki?
Yeah, you're right, I didn't set the NoLogo option in the configuration file, but the question now is why the logo didn't show up most of the times?

I don't remember it ever showing up with the stock nvidia driver.

keepitsimpleengineer · 2015-05-19 13:09:20

Morning graysky

A little hiccough today... .. .

error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia-ck-k10: requires nvidia-utils=349.16
[ljohnson@KISE-066 ~]$ sudo pacman -Qii nvidia-utils
Name : nvidia-utils
Version : 349.16-1
---
error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia-ck-sandybridge: requires nvidia-utils=349.16
[--ljohnson{06:06:05}~]$ sudo pacman -Qii nvidia-utils
Name : nvidia-utils
Version : 349.16-1

Regards... .. .

graysky · 2015-05-19 14:07:44

Try now... forgot to push the new index. Should be there now.

eigengrau · 2015-05-20 16:28:32

Should this patch be applied until 4.1 arrives? The official kernel does apply it now; this seems to have eaten quite a bit of data. Discussion on Phoronix.

Last edited by eigengrau (2015-05-20 16:31:53)

graysky · 2015-05-20 19:26:09

eigengrau wrote:

Should this patch be applied until 4.1 arrives? The official kernel does apply it now; this seems to have eaten quite a bit of data. Discussion on Phoronix.

Do you mean the ARCH kernel when you use the term "official kernel?" I don't see it queued into the 4.0 queue just yet if you meant upstream (https://git.kernel.org/cgit/linux/kerne … /queue-4.0)...

EDIT: perhaps I am misunderstanding this, but according to this, the patch was included in 4.0.3 and since we are on linux-ck-4.0.4-1 I would think we're good, no?

EDIT2: No, the patch is not applied to 4.0.4 as far as I can tell...

Last edited by graysky (2015-05-20 19:52:49)

eigengrau · 2015-05-21 06:22:41

graysky wrote:

eigengrau wrote:
Should this patch be applied until 4.1 arrives? The official kernel does apply it now; this seems to have eaten quite a bit of data. Discussion on Phoronix.
Do you mean the ARCH kernel when you use the term "official kernel?" I don't see it queued into the 4.0 queue just yet if you meant upstream (https://git.kernel.org/cgit/linux/kerne … /queue-4.0)...
EDIT: perhaps I am misunderstanding this, but according to this, the patch was included in 4.0.3 and since we are on linux-ck-4.0.4-1 I would think we're good, no?
EDIT2: No, the patch is not applied to 4.0.4 as far as I can tell...

Huh, weird, I could’ve sworn seeing an …ext4….patch file in the ABS when i looked yesterday. Must have been tired, I guess, since I can’t find it now, either.

In any case, I meant the ARCH one, but obviously I was mistaken. As for mainline, I’m not sure. The GH commit said it’s in master and 4.1-rc2, so I guessed it’s not in 4.0.x. Anyways, thought I’d ping you about it, just in case.

graysky · 2015-05-21 08:59:31

The patch seems harmless enough, but I don't want to start throwing patches into the package based on my limited knowledge... May I ask that you open a FS against the Arch kernel to see what our maintainers think about including it?

eigengrau · 2015-05-21 11:55:47

graysky wrote:

The patch seems harmless enough, but I don't want to start throwing patches into the package based on my limited knowledge... May I ask that you open a FS against the Arch kernel to see what our maintainers think about including it?

Filed

graysky · 2015-05-21 18:43:59

eigengrau wrote:

Filed

https://bugzilla.kernel.org/show_bug.cgi?id=98501

That patch fixes the problem? Seems to affect only raid0 users?

keepitsimpleengineer · 2015-05-25 20:55:38

Hello all... .. . Re: Long launch times for Xfce Terminal et al

So recently around the time Xfce went to 4.12 and xorg went to 1.17 the time required to open Xfce Terminal went from instantaneous to more than four seconds. Other applications also take longer than usual, but the XFCE terminal was the most noticeable (and annoying).

I tried replacing the Xfce compositor with Compton and still saw long launch times.

If I disable any compositor, the terminal will again open instantaneously.

If I boot with the non -ck kernel, it becomes instantaneous again with the Compton compositor running.

So now I'm disabling any compositor and sticking with the -ck kernel, but am curious as to why running the -ck kernel with compositors causes the launch times to be so long... .. ?

[root@KISE-005 ~]# pacman -Qs nvidia
local/cuda 7.0.28-2
    NVIDIA's GPU programming toolkit
local/lib32-libvdpau 1.1-1
    Nvidia VDPAU library
local/lib32-nvidia-libgl 352.09-1
    NVIDIA drivers libraries symlinks (32-bit)
local/lib32-nvidia-utils 352.09-1
    NVIDIA drivers utilities (32-bit)
local/libcl 1.1-4
    OpenCL library and ICD loader from NVIDIA
local/libvdpau 1.1-1
    Nvidia VDPAU library
local/nvidia 352.09-1
    NVIDIA drivers for linux
local/nvidia-ck-sandybridge 352.09-2 (ck-sandybridge)
    NVIDIA drivers for linux-ck. Second Gen Intel Core i3/i5/i7 optimized.
local/nvidia-libgl 352.09-1
    NVIDIA drivers libraries symlinks
local/nvidia-utils 352.09-1
    NVIDIA drivers utilities
local/opencl-nvidia 352.09-1
    OpenCL implemention for NVIDIA

[[root@KISE-005 ~]# pacman -Qi xorg-server
Name           : xorg-server
Version        : 1.17.1-5
...
root@KISE-005 ~]# pacman -Qi linux
Name           : linux
Version        : 4.0.4-2
Description    : The Linux kernel and modules
Architecture   : x86_64
...
[root@KISE-005 ~]# pacman -Qi linux-ck-sandybridge
Name           : linux-ck-sandybridge
...
[root@KISE-005 ~]# pacman -Qi nvidia-ck-sandybridge
Name           : nvidia-ck-sandybridge
Version        : 352.09-2
...
[root@KISE-005 ~]# pacman -Qi nvidia
Name           : nvidia
Version        : 352.09-1
...
[root@KISE-005 ~]# pacman -Qi linux
Name           : linux
Version        : 4.0.4-2
...
[root@KISE-005 ~]# pacman -Qi linux-ck-sandybridge
Name           : linux-ck-sandybridge
...
[root@KISE-005 ~]# pacman -Qi nvidia-ck-sandybridge
Name           : nvidia-ck-sandybridge
Version        : 352.09-2
...
[root@KISE-005 ~]# pacman -Qi nvidia
Name           : nvidia
Version        : 352.09-1
...
[root@KISE-005 ~]# pacman -Qi compton-git
Name           : compton-git
Version        : 0.1_beta2.68.gb1889c1-1
Description    : X Compositor (a fork of xcompmgr-dana) (git-version)
..
Depends On     : libgl  libdbus  libxcomposite  libxdamage  libxrandr  pcre  libconfig
                 libxinerama
..
Build Date     : Mon 25 May 2015 10:53:45 AM PDT
Install Date   : Mon 25 May 2015 10:54:38 AM PDT

SOLVED: It was a diminished performance HDD, now diminished to death... .. .
Replacement is SSD, a blitzoid. Plus a fresh system install as the root directory (sans /home) was clobbered. Screen now paints before sound of click reaches ears.

Last edited by keepitsimpleengineer (2015-06-03 00:54:38)

lano1106 · 2015-06-11 04:00:03

Hi Graysky,

I have tried to install linux-ck-4.0.5-2-x86_64.pkg.tar.xz from repo-ck and

error: linux-ck: missing required signature
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

Scimmia · 2015-06-11 04:04:49

lano1106, did you add graysky's key to the pacman keyring?

lano1106 · 2015-06-11 04:41:28

Yes. I have been using repo-ck for a while. It is the first time I have this issue.
I have rerun this command from repo-ck.com just in case:
pacman-key -r 5EE46C4C && pacman-key --lsign-key 5EE46C4C

but it didn't change anything.
The funny thing is that nvidia-ck-352.09-2 was checked as well and the signature was ok for that package.

Scimmia · 2015-06-11 04:50:11

And looking at http://repo-ck.com/x86_64/ , it appears that the generic package is missing a signature. All of the others are there, just not on the generic package.

lano1106 · 2015-06-11 05:21:32

oh well. one more reason to dl a build optimized for my cpu then.
thank you for your help!

graysky · 2015-06-11 08:57:35

I will check and fix later today. Meantime, you can download manually through wget or a browser then pacman -U ... Or just use a cpu specific package set as you have done.

Last edited by graysky (2015-06-11 08:59:53)

chaonaut · 2015-06-11 12:33:39

graysky wrote:

I will check and fix later today. Meantime, you can download manually through wget or a browser then pacman -U

changing SigLevel to Optional for repo-ck in pacman.conf worked for me.

holahmeds · 2015-07-08 11:43:21

Hello,

Can you check the package linux-ck-pentm-4.0.7-1-i686 ?
When I download it I get a 3.6MB file.

graysky · 2015-07-08 19:05:50

@holahmeds - Try to d/l it again... it is the correct size on the server.

% ll linux* | grep pentm
-rw-r--r-- 1 repockuser inetuser  55M Jun 30 14:14 linux-ck-pentm-4.0.7-1-i686.pkg.tar.xz
-rw-r--r-- 1 repockuser inetuser  287 Jun 30 14:14 linux-ck-pentm-4.0.7-1-i686.pkg.tar.xz.sig
-rw-r--r-- 1 repockuser inetuser 6.3M Jun 30 14:14 linux-ck-pentm-headers-4.0.7-1-i686.pkg.tar.xz
-rw-r--r-- 1 repockuser inetuser  287 Jun 30 14:14 linux-ck-pentm-headers-4.0.7-1-i686.pkg.tar.xz.sig

Last edited by graysky (2015-07-08 19:06:08)

Arch Linux

#2451 2015-05-17 19:23:14

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2452 2015-05-17 19:45:01

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2453 2015-05-18 07:57:53

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2454 2015-05-18 08:33:17

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2455 2015-05-18 10:04:40

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2456 2015-05-18 10:33:59

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2457 2015-05-18 18:24:08

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2458 2015-05-19 13:09:20

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2459 2015-05-19 14:07:44

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2460 2015-05-20 16:28:32

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2461 2015-05-20 19:26:09

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2462 2015-05-21 06:22:41

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2463 2015-05-21 08:59:31

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2464 2015-05-21 11:55:47

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2465 2015-05-21 18:43:59

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2466 2015-05-25 20:55:38

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2467 2015-06-11 04:00:03

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2468 2015-06-11 04:04:49

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2469 2015-06-11 04:41:28

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2470 2015-06-11 04:50:11

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2471 2015-06-11 05:21:32

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2472 2015-06-11 08:57:35

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2473 2015-06-11 12:33:39

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2474 2015-07-08 11:43:21

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

#2475 2015-07-08 19:05:50

Re: unofficial linux-ck repo with cpu optimized packages is ONLINE

Board footer