You are not logged in.
Is this with the most recent patch? I'm on UEFI here and having no problems at all. graysky's linux-ck-4.0.1-3 is still going strong.
I am glad to hear that 4.0.1-3 is working. This helps to narrow down the possible causes. In what I hope to be the final attempt, can you guys please try one more build and look for panics? Take a guess, 4.0.1-4
Option 1 (roll your own):
http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-4.src.tar.gz
Option 2 (my builds):
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-4-x86_64.pkg.tar.xz
and optional headers
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-headers-4.0.1-4-x86_64.pkg.tar.xz
Last edited by graysky (2015-05-04 07:11:56)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I am glad to hear that 4.0.1-3 is working. This helps to narrow down the possible causes. In what I hope to be the final attempt, can you guys please try one more build and look for panics? Take a guess, 4.0.1-4
I can confirm that 4.0.1-3 works (I let the system run for about 12h without any problem). 4.0.1-4 seems to work too.
Offline
yochaigal wrote:Everything is working great, but went to do pacman -Syu today and got:
:: Starting full system upgrade... warning: linux-ck-sandybridge: local (4.0-1) is newer than repo-ck (3.19.6-1) warning: linux-ck-sandybridge-headers: local (4.0-1) is newer than repo-ck (3.19.6-1) resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: acpi_call-ck: requires linux-ck>=4.0
Running 64bit Arch with 4.0.0-1-ck kernel on a Lenovo X1 Carbon (sandybridge).
Graysky mentioned earlier that he would downgrade the packages because of the crashes. If you get crashes, you can downgrade using pacman -Syyuu.
I have the same situation here, but pacman -Syyuu doesn't change a thing! I just get the same feedback as with pacman -Syu!
Offline
You can downgrade by just installing the group name or package name you wish to have and paceman will pull down the 3.19.x series for you.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
graysky wrote:I am glad to hear that 4.0.1-3 is working. This helps to narrow down the possible causes. In what I hope to be the final attempt, can you guys please try one more build and look for panics? Take a guess, 4.0.1-4
I can confirm that 4.0.1-3 works (I let the system run for about 12h without any problem). 4.0.1-4 seems to work too.
4.0.1-3 uses ck1 and Alfred's patch and has NUMA enabled.
4.0.1-4 uses ck1 and has NUMA enabled but is otherwise unmodified.
I'd like to hear from other users who have experienced panics if 4.0.1-4 solves it for them. This is much cleaner since no extra patches are applied.
Last edited by graysky (2015-05-04 09:55:31)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
OK, my promised morning report. No dmesg errors, no journal error messages concerning the kernel or nvidia driver, no panics and no lock ups or freezes. It hasn't been quite 24hrs, but I think I'm good with the patch.
edit: this is 4.0.1-3-ck. gonna test -4 now
edit2: installed 4.0.1-4-ck kernel and headers, removed and re-installed purpose-built nvidia-ck for kernel 4.0, rebuilt kernel image (mkinitcpio) and nvidia says it has a problem with the symbols (per journal). Tried removing, re-installing nvidia-ck 2 times (from cli, no gui because nvidia doesn't want to play well). Ended up downgrading to 4.0.1-3-ck, removing and re-installing nvidia-ck and rebuilding the image. System now works. I have to go to work today, so I'll look deeper into this once I get home.
journalctl error:
May 04 07:27:27 PatsMain kernel: nvidia: disagrees about version of symbol module_layout
Last edited by Buddlespit (2015-05-04 11:47:16)
Offline
You can downgrade by just installing the group name or package name you wish to have and paceman will pull down the 3.19.x series for you.
friendofarch ~ # pacman -S linux-ck
resolving dependencies...
looking for conflicting packages...
:: linux-ck and linux-ck-sandybridge are in conflict. Remove linux-ck-sandybridge? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: bbswitch-ck: requires linux-ck>=4.0
:: linux-ck-sandybridge-headers: requires linux-ck-sandybridge
:: nvidia-ck-sandybridge: requires linux-ck-sandybridge>=4.0
:: nvidia-ck-sandybridge: requires linux-ck-sandybridge<4.1
friendofarch ~ # pacman -S nvidia-ck
resolving dependencies...
looking for conflicting packages...
:: nvidia-ck and nvidia-ck-sandybridge are in conflict. Remove nvidia-ck-sandybridge? [y/N] y
:: linux-ck and linux-ck-sandybridge are in conflict. Remove linux-ck-sandybridge? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: bbswitch-ck: requires linux-ck>=4.0
:: linux-ck-sandybridge-headers: requires linux-ck-sandybridge
Either not as simple as that or I don't understand how to do it;)
Maybe I rather wait until ck-repo gets updated, since Kernel 4.0 runs mostly fine (except for some flickering on login-screen). All the other updates will have to wait then...
Thanks anyway!
Offline
pacman -S linux-ck bbswitch-ck linux-ck-headers nvidia-ck
all at once, and don't mix sandybridge with generic packages.
Online
graysky wrote:You can downgrade by just installing the group name or package name you wish to have and paceman will pull down the 3.19.x series for you.
Either not as simple as that or I don't understand how to do it;)
Maybe I rather wait until ck-repo gets updated, since Kernel 4.0 runs mostly fine (except for some flickering on login-screen). All the other updates will have to wait then...
Thanks anyway!
sudo pacman -S linux-ck nvidia-ck bbswitch-ck
Keep adding onto that line until you have no more errors
Offline
Option 2 (my builds):
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-4-x86_64.pkg.tar.xz
4.0.1-3 ran calmly for 17½ hours and linux-ck-4.0.1-4 has booted up, shutdown and is now currently running without issue. This is with BFQ, incidentally.
For full disclosure, although my panic with linux-ck-haswell 4.0-1 went away for a while, it (or a different panic) came back after wpa_supplicant 1:2.3-1 arrived, so I'd been back on linux-ck-haswell 3.19.6-1 until yesterday.
@archun: Intel® Core™ i5-4210M • [GPU] Intel® HD Graphics 4600 • [Kernel] linux-ck-haswell
Handmade.Network • GitLab
The Life and Times of Miblo del Carpio
Offline
i7-3770, Radeon HD 7570
linux-ck-4.0.1-4 just booted up. BFQ enabled. No more crashes.
Offline
i7-3770, Radeon HD 7570
linux-ck-4.0.1-4 just booted up. BFQ enabled. No more crashes.
This is good to hear. Can some others who have experienced panics in the past please try 4.0.1-4 from here and report back:
Option 1 (roll your own):
http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-4.src.tar.gz
Option 2 (my builds):
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-4-x86_64.pkg.tar.xz pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-headers-4.0.1-4-x86_64.pkg.tar.xz
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Just tried 4.0.1-4 (binaries) and boot normally - no kernel panic! hooray!
Offline
+1) 4.0.1-4 with BFQ enabled working fine here with AthlonII.
Last edited by paneless (2015-05-05 13:30:27)
Offline
Tried the 4.0.1-4 binaries posted. Still having nvidia issues, won't start SDDM. See my above post, #2331. I can log into tty2, tho.
Offline
Tried the 4.0.1-4 binaries posted. Still having nvidia issues, won't start SDDM. See my above post, #2331. I can log into tty2, tho.
That error just means that nvidia needs built against the new kernel. Since graysky isn't providing nvidia packages for the testing kernels, that's on you.
Offline
Buddlespit wrote:Tried the 4.0.1-4 binaries posted. Still having nvidia issues, won't start SDDM. See my above post, #2331. I can log into tty2, tho.
That error just means that nvidia needs built against the new kernel. Since graysky isn't providing nvidia packages for the testing kernels, that's on you.
I concur.
Unfortunately, unless I'm doing something horribly wrong, it's not working. I can install a purpose built nvidia-ck on 4.0.1-3-ck, but not on 4.0.1-4-ck. Or, I can build and install it, but it's just not working. Not really an issue, tbh. I can continue to run 4.0.1-3-ck until regular ck packages resume. Just to be clear, I boot into 4.0.1-4-ck, switch to tty2 (I'm on Plasma 5, SDDM has tty1), go to my build dir and makepkg -csi on a nvidia-ck 349.16-2 PKBUILD released when 4.0-ck first came out, then mkinitcpio -p linux-ck, then reboot and stare at tty1 for about a minute before deciding to switch to tty2 and back to 4.0.1-3.
Offline
OK gang, CK does not believe that simply disabling NUMA would affect this issue despite several of you running 4.0.1-4 without panics. I trust his opinion CK has released a new patch[1] which he would like those of you who have experienced a panic to test and to provide feedback.
As such, I have incorporated this patch into 4.0.1-5 and have re-disabled NUMA as I have done for linux-ck for over the past 3 years. Please test 4.0.1-5.
Option 1 (roll your own):
http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-5.src.tar.gz
Option 2 (my builds):
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-5-x86_64.pkg.tar.xz
and optional headers
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-headers-4.0.1-5-x86_64.pkg.tar.xz
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Well, 4.0.1-5 does not work, regardless of the IO scheduler used (bfq, deadline, etc.). Just installed and already got several kernel panics.
Last edited by mauritiusdadd (2015-05-05 05:25:06)
Offline
Installed 4.0.1.5 this morning, booted three times without issue. Fourth boot gave kernel panic, switched off and on again and rebooted five or six times without problem. BFQ enabled throughout.
Offline
Option 2 (my builds):
pacman -U http://repo-ck.com/PKG_source/next/testing/linux-ck-4.0.1-5-x86_64.pkg.tar.xz
Hmm… different experience from mauritiusdadd here:
Reboot out of linux-ck-4.0.1-4 (successfully, like normal)
Boot linux-ck-4.0.1-5 successfully, with BFQ
Poweroff to panic!
Boot successfully, with BFQ
Poweroff successfully
Boot successfully, with BFQ
Still live…
That first panic must be undesirable behaviour, mustn't it, but it seems to have settled down now. Any tips for stressing the system / anything in particular that'd be useful to test?
@archun: Intel® Core™ i5-4210M • [GPU] Intel® HD Graphics 4600 • [Kernel] linux-ck-haswell
Handmade.Network • GitLab
The Life and Times of Miblo del Carpio
Offline
linux-ck-4.0.1-5 (binary) boot panic!
i7-3770, Radeon HD 7570
linux-ck-4.0.1-4 just booted up. BFQ enabled. No more crashes.
Offline
Just for the record, I used ABS to download the PKGBUILD for the current stock kernel and rebuilt it disabling NUMA as in linux-ck. I rebooted several times without having any problem and the system is still running... so the problem is definitely NUMA=off + BFS.
Last edited by mauritiusdadd (2015-05-05 16:49:31)
Offline
My experiences are like Miblo with 4.0.1-5-ck (binaries):
- Boot success with 4.0.1-5-ck
- Power-off is a panic
- Boot on panic, hard reboot
- Boot on panic, hard reboot
Keeps doing that.
BFQ enabled on all tests, nouveau drivers.
So it's definitely not stable.
Offline
@all - Thanks for the testing of 4.0.1-5-ck. I will update ck's blogs with your results and reference this thread. Let's see what CK thinks.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline