You are not logged in.
Same issue here. Could you please rebuild it and not enable BFS by default, considering that it's the culprit ? Seem like the best thing to do in the meantime considering the number of people affected.
This is not an option for the patchset. Linux-ck = BFS.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Until a fix could be found I just downgraded to 3.19.5-1-ck which works perfectly good (ivy bridge).
By the way, thank you very much for all those kernels !!!
Offline
no errors here, ck-haswell :
Linux arch 4.0.0-1-ck #1 SMP PREEMPT Sat Apr 25 19:16:30 EDT 2015 x86_64 GNU/Linux
04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13)
05:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
Offline
Getting the crashes on my system with ck-haswell on 4.0. They were so unpredictable, I had about a 50% success rate on any given attempt to boot the system, and it'd crash <30 minutes later. (Mostly glad that it turned out to be this instead of my initial suspicions my SSD was going bad.) Switched back to the standard Arch kernel until this is fixed, since that just required changing one line in my gummiboot config instead of trying to download and install a kernel on a crash-prone system.
Avatar by Ditey: https://twitter.com/phrobitey
Offline
I also had a crash, though I am not sure if it is related. It happened during shutdown and gave me this:
Apr 26 18:24:17 archbase kernel: ------------[ cut here ]------------
Apr 26 18:24:17 archbase kernel: WARNING: CPU: 3 PID: 450 at arch/x86/mm/pageattr.c:1119 __cpa_process_fault+0x46c/0x480()
Apr 26 18:24:17 archbase kernel: CPA: called for zero pte. vaddr = e9e626c9c6cbf000 cpa->vaddr = ffff88021ba45000
Apr 26 18:24:17 archbase kernel: Modules linked in: fuse snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nct6775 hwmon_vid nvidia(PO) iTCO_wdt iTCO_vendor_support mxm_wmi coretemp hwmon intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd evdev mousedev joydev mac_hid psmouse drm pcspkr serio_raw snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep i2c_hid snd_pcm snd_timer i2c_i801 tpm_tis i2c_designware_platform nuvoton_cir dw_dmac i2c_designware_core video rc_core tpm battery acpi_pad gpio_lynxpoint dw_dmac_core e1000e 8250_dw i2c_core spi_pxa2xx_platform mei_me snd mei shpchp ptp button soundcore pps_core lpc_ich processor wmi sch_fq_codel overlay
Apr 26 18:24:17 archbase kernel: ext4 crc16 mbcache jbd2 sr_mod cdrom sd_mod hid_generic usbhid hid atkbd libps2 ahci libahci libata xhci_pci scsi_mod ehci_pci xhci_hcd ehci_hcd usbcore usb_common i8042 serio sdhci_acpi sdhci led_class mmc_core
Apr 26 18:24:17 archbase kernel: CPU: 3 PID: 450 Comm: compton Tainted: P O 4.0.0-1-ck #1
Apr 26 18:24:17 archbase kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Pro4, BIOS P1.80 01/26/2015
Apr 26 18:24:17 archbase kernel: 0000000000000000 00000000394a9162 ffff8800c560b4e8 ffffffff81542c9c
Apr 26 18:24:17 archbase kernel: 0000000000000000 ffff8800c560b540 ffff8800c560b528 ffffffff8107250a
Apr 26 18:24:17 archbase kernel: 0000000000000000 000000000000000c ffff8800c560b780 0000000000000000
Apr 26 18:24:17 archbase kernel: Call Trace:
Apr 26 18:24:17 archbase kernel: [<ffffffff81542c9c>] dump_stack+0x4c/0x6e
Apr 26 18:24:17 archbase kernel: [<ffffffff8107250a>] warn_slowpath_common+0x8a/0xc0
Apr 26 18:24:17 archbase kernel: [<ffffffff81072595>] warn_slowpath_fmt+0x55/0x70
Apr 26 18:24:17 archbase kernel: [<ffffffff8106296c>] __cpa_process_fault+0x46c/0x480
Apr 26 18:24:17 archbase kernel: [<ffffffff810675b0>] ? rbt_memtype_copy_nth_element+0xc0/0xc0
Apr 26 18:24:17 archbase kernel: [<ffffffff81063192>] __change_page_attr_set_clr+0x542/0xcf0
Apr 26 18:24:17 archbase kernel: [<ffffffff81176a71>] ? __purge_vmap_area_lazy+0x181/0x480
Apr 26 18:24:17 archbase kernel: [<ffffffff81176ee7>] ? vm_unmap_aliases+0x177/0x1a0
Apr 26 18:24:17 archbase kernel: [<ffffffff81063aa2>] change_page_attr_set_clr+0x162/0x4e0
Apr 26 18:24:17 archbase kernel: [<ffffffff81063ff8>] set_memory_array_wb+0x38/0xb0
Apr 26 18:24:17 archbase kernel: [<ffffffffa0c1072e>] nv_free_system_pages+0x40e/0x430 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffff810c74ee>] ? getnstimeofday64+0xe/0x30
Apr 26 18:24:17 archbase kernel: [<ffffffffa0c0746d>] nv_free_pages+0x9d/0xb0 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0befe87>] _nv012286rm+0x97/0x100 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0a25f70>] ? _nv011064rm+0x120/0x220 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0a26188>] ? _nv011071rm+0x118/0x190 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b92f51>] ? _nv000640rm+0x2f41/0x3080 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b8feb9>] ? _nv000608rm+0x1479/0x1530 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b9077e>] ? _nv000640rm+0x76e/0x3080 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b8feb9>] ? _nv000608rm+0x1479/0x1530 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b625fd>] ? _nv000217rm+0xd/0x30 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b90237>] ? _nv000640rm+0x227/0x3080 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b8feb9>] ? _nv000608rm+0x1479/0x1530 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b8ff95>] ? _nv013823rm+0x25/0xa0 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0bf53c2>] ? _nv000647rm+0x62/0x1a0 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0bf81d1>] ? rm_free_unused_clients+0xc1/0xf0 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffff8109f492>] ? up+0x32/0x50
Apr 26 18:24:17 archbase kernel: [<ffffffffa0c0778f>] ? nvidia_close+0x30f/0x450 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0c13ead>] ? nvidia_frontend_close+0x4d/0xa0 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffff811ab18f>] ? __fput+0x9f/0x200
Apr 26 18:24:17 archbase kernel: [<ffffffff811ab33e>] ? ____fput+0xe/0x10
Apr 26 18:24:17 archbase kernel: [<ffffffff8108e124>] ? task_work_run+0xd4/0xf0
Apr 26 18:24:17 archbase kernel: [<ffffffff81074d79>] ? do_exit+0x2f9/0xaa0
Apr 26 18:24:17 archbase kernel: [<ffffffff810755b5>] ? do_group_exit+0x45/0xb0
Apr 26 18:24:17 archbase kernel: [<ffffffff81080c26>] ? get_signal+0x246/0x670
Apr 26 18:24:17 archbase kernel: [<ffffffff81014597>] ? do_signal+0x37/0x760
Apr 26 18:24:17 archbase kernel: [<ffffffff81014d20>] ? do_notify_resume+0x60/0x80
Apr 26 18:24:17 archbase kernel: [<ffffffff81548ca3>] ? int_signal+0x12/0x17
Apr 26 18:24:17 archbase kernel: ---[ end trace 65a2e0241f511198 ]---
Apr 26 18:24:17 archbase kernel: general protection fault: 0000 [#1] PREEMPT SMP
Apr 26 18:24:17 archbase kernel: Modules linked in: fuse snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nct6775 hwmon_vid nvidia(PO) iTCO_wdt iTCO_vendor_support mxm_wmi coretemp hwmon intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd evdev mousedev joydev mac_hid psmouse drm pcspkr serio_raw snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep i2c_hid snd_pcm snd_timer i2c_i801 tpm_tis i2c_designware_platform nuvoton_cir dw_dmac i2c_designware_core video rc_core tpm battery acpi_pad gpio_lynxpoint dw_dmac_core e1000e 8250_dw i2c_core spi_pxa2xx_platform mei_me snd mei shpchp ptp button soundcore pps_core lpc_ich processor wmi sch_fq_codel overlay
Apr 26 18:24:17 archbase kernel: ext4 crc16 mbcache jbd2 sr_mod cdrom sd_mod hid_generic usbhid hid atkbd libps2 ahci libahci libata xhci_pci scsi_mod ehci_pci xhci_hcd ehci_hcd usbcore usb_common i8042 serio sdhci_acpi sdhci led_class mmc_core
Apr 26 18:24:17 archbase kernel: CPU: 3 PID: 450 Comm: compton Tainted: P W O 4.0.0-1-ck #1
Apr 26 18:24:17 archbase kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Pro4, BIOS P1.80 01/26/2015
Apr 26 18:24:17 archbase kernel: task: ffff8800c6665800 ti: ffff8800c5608000 task.ti: ffff8800c5608000
Apr 26 18:24:17 archbase kernel: RIP: 0010:[<ffffffffa0c1052a>] [<ffffffffa0c1052a>] nv_free_system_pages+0x20a/0x430 [nvidia]
Apr 26 18:24:17 archbase kernel: RSP: 0018:ffff8800c560b858 EFLAGS: 00010207
Apr 26 18:24:17 archbase kernel: RAX: e9e626ca46cbf363 RBX: 0000000000000011 RCX: e9e626c9c6cbf363
Apr 26 18:24:17 archbase kernel: RDX: 03a7847b271b2fc0 RSI: dc8ea1f631a1df70 RDI: ffff880080000000
Apr 26 18:24:17 archbase kernel: RBP: ffff8800c560b8b8 R08: 0000000000000000 R09: ffff88001b9be558
Apr 26 18:24:17 archbase kernel: R10: ffffffffa0c10d9b R11: 00000000000003c4 R12: ffffea0000000000
Apr 26 18:24:17 archbase kernel: R13: 000077ff80000000 R14: ffff880000000000 R15: ffff880224a46f80
Apr 26 18:24:17 archbase kernel: FS: 00007fb65393a740(0000) GS:ffff88022ed80000(0000) knlGS:0000000000000000
Apr 26 18:24:17 archbase kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 26 18:24:17 archbase kernel: CR2: 00000000006041d8 CR3: 0000000223489000 CR4: 00000000001407e0
Apr 26 18:24:17 archbase kernel: Stack:
Apr 26 18:24:17 archbase kernel: ffff880225210098 ffff880225210098 ffff880225210000 ffff88001b9be558
Apr 26 18:24:17 archbase kernel: ffff88021bbc8008 00000000394a9162 ffffffffa0d10e00 ffff880224a46f80
Apr 26 18:24:17 archbase kernel: ffff880220a77808 0000000000000080 ffff880224a46f80 ffff8800c725c008
Apr 26 18:24:17 archbase kernel: Call Trace:
Apr 26 18:24:17 archbase kernel: [<ffffffffa0c0746d>] nv_free_pages+0x9d/0xb0 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0befe87>] _nv012286rm+0x97/0x100 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0a25f70>] ? _nv011064rm+0x120/0x220 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0a26188>] ? _nv011071rm+0x118/0x190 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b92f51>] ? _nv000640rm+0x2f41/0x3080 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b8feb9>] ? _nv000608rm+0x1479/0x1530 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b9077e>] ? _nv000640rm+0x76e/0x3080 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b8feb9>] ? _nv000608rm+0x1479/0x1530 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b625fd>] ? _nv000217rm+0xd/0x30 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b90237>] ? _nv000640rm+0x227/0x3080 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b8feb9>] ? _nv000608rm+0x1479/0x1530 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0b8ff95>] ? _nv013823rm+0x25/0xa0 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0bf53c2>] ? _nv000647rm+0x62/0x1a0 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0bf81d1>] ? rm_free_unused_clients+0xc1/0xf0 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffff8109f492>] ? up+0x32/0x50
Apr 26 18:24:17 archbase kernel: [<ffffffffa0c0778f>] ? nvidia_close+0x30f/0x450 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffffa0c13ead>] ? nvidia_frontend_close+0x4d/0xa0 [nvidia]
Apr 26 18:24:17 archbase kernel: [<ffffffff811ab18f>] ? __fput+0x9f/0x200
Apr 26 18:24:17 archbase kernel: [<ffffffff811ab33e>] ? ____fput+0xe/0x10
Apr 26 18:24:17 archbase kernel: [<ffffffff8108e124>] ? task_work_run+0xd4/0xf0
Apr 26 18:24:17 archbase kernel: [<ffffffff81074d79>] ? do_exit+0x2f9/0xaa0
Apr 26 18:24:17 archbase kernel: [<ffffffff810755b5>] ? do_group_exit+0x45/0xb0
Apr 26 18:24:17 archbase kernel: [<ffffffff81080c26>] ? get_signal+0x246/0x670
Apr 26 18:24:17 archbase kernel: [<ffffffff81014597>] ? do_signal+0x37/0x760
Apr 26 18:24:17 archbase kernel: [<ffffffff81014d20>] ? do_notify_resume+0x60/0x80
Apr 26 18:24:17 archbase kernel: [<ffffffff81548ca3>] ? int_signal+0x12/0x17
Apr 26 18:24:17 archbase kernel: Code: 80 00 88 ff ff 49 8b 01 4c 89 ea 4a 8d 0c 30 48 01 f8 48 39 c8 48 0f 42 15 f4 1a c0 e0 48 01 c2 48 c1 ea 0c 48 c1 e2 06 4c 01 e2 <48> 8b 32 f7 c6 00 80 00 00 0f 84 a7 fe ff ff 48 8b 72 30 48 8b
Apr 26 18:24:17 archbase kernel: RIP [<ffffffffa0c1052a>] nv_free_system_pages+0x20a/0x430 [nvidia]
Apr 26 18:24:17 archbase kernel: RSP <ffff8800c560b858>
Apr 26 18:24:17 archbase kernel: ---[ end trace 65a2e0241f511199 ]---
Apr 26 18:24:17 archbase kernel: Fixing recursive fault but reboot is needed!
I installed a new graphics card a few days ago, so it might be a hardware or driver problem and have nothing to do with linux-ck-haswell 4.0.
No Wi-Fi here, just ethernet:
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V
Offline
Due to the numerous reports of issues with ck1+linux v4.0.x, I think it's best to for me to place the 3.19.x series back in the repo until these are sorted out. Greg KH has announced 3.19.6 scheduled to be released tomorrow at 13:45 UTC so my plan is to build that once it goes gold, and to have users downgrade at that time. I will post again when that happens with simple instructions for the downgrade. For those of you experiencing problems, I encourage you to work with ck on his blog in order to troubleshoot.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Same problem on nehalem! Kernel panics, hard locks and random freezes, all sorts of stuff. Microcode was updated.
I'm actually glad this was the kernel and not my RAM as I thought.
I reverted to 3.19.5 for now.
Last edited by russ0r (2015-04-27 10:19:44)
Offline
Due to the numerous reports of issues with ck1+linux v4.0.x, I think it's best to for me to place the 3.19.x series back in the repo until these are sorted out. Greg KH has announced 3.19.6 scheduled to be released tomorrow at 13:45 UTC so my plan is to build that once it goes gold, and to have users downgrade at that time. I will post again when that happens with simple instructions for the downgrade. For those of you experiencing problems, I encourage you to work with ck on his blog in order to troubleshoot.
I don't use the ck. I use my own pkgbuild ( I have been doing since 3.10 ) and I still get locks and panics. Had to do a btrfs-zero-log at one point.
It only happens when I patch bfs 462.
I'm thinking it's a bug with bfs 462.
I didn't enable bfq as I don't see a 4.0.0 version on there yet so I assuming it's not ready yet
Still using 3.19.4 right now... Haven't had time to upgrade to 3.19.5 yet since then
If you want to see my pkgbuild... I'll post it... not much different from yours I mostly just tinkering
Last edited by sinatosk (2015-04-27 12:56:02)
Offline
I had a panic on first boot, rebooted and it booted up fine and has been fine since (more than a day). haswell build, BFQ enabled, btrfs root.
Online
I also have the same issues with -CK kernel patch.
I had to boot using the stock kernel.
[Acer E1-572-6870]
Offline
Just for the record, I've been running custom kernel 4.0 with bfs, bfq and enable_additional_cpu_optimizations patch on sandy bridge since yesterday, without any issues yet.
Only odd thing I've noticed is that running btrfs scrub makes my system extremely unresponsive, but it's clearly something to do with IO so bfs is probably not the culprit here.
Offline
Same here. After updating a Haswell-optimized kernel from the binary repository my system just froze on boot without any information about what's happening. After a reboot it seemed all right, though after a while everything just froze suddenly. (BFQ disabled)
Offline
I got completely random lockups with linux-ck-core2 4.0-1 and nvidia 349.16-2. Boots fine, sometimes it freezes while gaming, sometimes while idle. So far with stock kernel everything seems to work like it should.
Offline
Just for the record, happens to me as well (since today). Random freezes while booting or if that went through later on.
Boot error: http://wklej.org/id/1698611
My details:
BFQ enabled
$ pacman -Sl repo-ck | grep installed
repo-ck linux-ck-nehalem 4.0-1 [installed]
repo-ck nvidia-ck-nehalem 349.16-2 [installed]
repo-ck virtualbox-ck-host-modules-nehalem 4.3.26-4 [installed]
Last edited by sxe (2015-04-28 09:59:52)
Offline
I'm experiencing the kernel panic with latest linux-ck-bulldozer, I have nvidia GPU with nvidia-ck-bulldozer installed and I am using elevator BFQ. I tried downgrade to older version but experiencing a xorg issue. My versions are all installed from repo-ck:
$ pacman -Sl repo-ck | grep installed
repo-ck linux-ck-bulldozer 4.0-1 [installed: 3.19.5-1]
repo-ck linux-ck-bulldozer-headers 4.0-1 [installed: 3.19.5-1]
repo-ck nvidia-ck-bulldozer 349.16-2 [installed: 349.16-1]
Looking on the journalctl I found some errors under gdm for libEGL.so.1 This seems to be unrelated - I had to remove and install nvidia-libgl package to fix it.
Last edited by inglor (2015-04-28 20:35:11)
Offline
I am experiencing the same issue on my ThinkPad W530 (had to downgrade to 3.19.5-1). Every boot hangs with kernel panic.
The following repo-ck packages are installed:
$ pacman -Sl repo-ck | grep Install
repo-ck linux-ck-ivybridge 4.0-1 [Installiert: 3.19.5-1]
repo-ck linux-ck-ivybridge-headers 4.0-1 [Installiert: 3.19.5-1]
repo-ck nvidia-ck-ivybridge 349.16-2 [Installiert: 349.16-1]
repo-ck virtualbox-ck-guest-modules-ivybridge 4.3.26-4 [Installiert: 4.3.26-3]
repo-ck virtualbox-ck-host-modules-ivybridge 4.3.26-4 [Installiert: 4.3.26-3]
Regrads,
eNauz
Last edited by eNauz (2015-04-29 06:47:24)
Offline
Not using the repository but I compiled 4.0 with the ck patches from the last release the day 4.0 came out. Been working like a charm with -03, native, bfs, gcc opts and bfq when those patches came through a few days later. Graphics also works fine having installed the nvidia blobs manually.
Linux localhost 4.0.0-2-ck1-ARCH #1 SMP PREEMPT Tue Apr 21 01:17:57 BST 2015 x86_64 GNU/Linux
dmesg | grep -i kolivas
[ 0.309462] BFS CPU scheduler v0.462 by Con Kolivas.
Haswell 4790k, nvidia 970, asrock z97 extreme6. btrfs root with lzo
Only specific customisations I did was cutting out a bunch of modules I don't need.
Maybe try compiling it yourself and see if the issues persist. Has con released any new patches or notable altered the previous ones that im using?
Last edited by Iksf (2015-04-29 07:59:38)
Offline
Maybe try compiling it yourself and see if the issues persist. Has con released any new patches or notable altered the previous ones that im using?
Yes, he released a test patch to be applied on top of CK1 patch, but it seems that it doesn't work. I too tried to compile linux-ck (with and without the -march=native option) but it does not works either.
---
I also feel the need to quote graysky because there are a lot of comments here, but in proportion there are very few comments on Con's blog. Posting here only is pointless, the more information we can provide upstream the faster a possible fix will be released
From what you guys have written, it seem that something in 4.0 + CK1 might be to blame. Can I ask each of you to please report this to Con via his blog? He is usually very quick to investigate and offer a fix: http://ck-hack.blogspot.com/2015/04/bfs … 0-ck1.html
Last edited by mauritiusdadd (2015-04-29 09:02:01)
Offline
Of everyone who posted with a kernel panic: can I ask for a volunteer to communicate directly with Con to troubleshoot? For simplicity's sake, I would like to select someone who has a standard setup without the need for both nvidia-ck (any version) and broadcom-wl-ck. Ideally, who ever you are should be willing to troubleshoot with Con, have the knowledge to apply a patch from him, and to report back. I recommend that you totally disable any gcc patches (ie build the generic x86_64) for the purposes of this work. Please email me privately if you meet these criteria and want to help. Thanks.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Is anyone getting the errors with an AMD system?
PC1: Intel Sandybridge + NVIDIA -> Kernel Panic
Laptop: AMD Turion X2 (2007) + nouveau -> Works flawlessly
Could also be, because I use nouveau on the laptop and not nvidia-ck.
Offline
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).
Last edited by yochaigal (2015-04-30 14:33:00)
Offline
I've been having a weird crash, even on the vanilla Arch Linux kernel, where my computer screen stops responding, and my caps lock and network indicator lights start blinking rapidly and with the same time in between blinks. I haven't been able to find much, but here's what I was seeing looking back at the log:
Apr 30 00:00:00 steelhorse systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory.
Apr 30 00:00:00 steelhorse systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory.
Apr 30 00:00:00 steelhorse systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory.
Apr 30 00:00:00 steelhorse systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory.
Apr 30 00:00:00 steelhorse systemd[1]: Starting Update man-db cache...
Apr 30 00:00:00 steelhorse systemd[1]: Starting Rotate log files...
Apr 30 00:00:00 steelhorse systemd[1]: Starting Verify integrity of password and group files...
Apr 30 00:00:00 steelhorse systemd[1]: Starting Update locate database...
Apr 30 00:00:00 steelhorse systemd[1]: Started Rotate log files.
Apr 30 00:00:01 steelhorse pwck[19495]: user 'git': no group 2000
Apr 30 00:00:01 steelhorse pwck[19495]: pwck: no changes
Apr 30 00:00:01 steelhorse systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 30 00:00:01 steelhorse systemd[1]: Failed to start Verify integrity of password and group files.
Apr 30 00:00:01 steelhorse systemd[1]: Unit shadow.service entered failed state.
Apr 30 00:00:01 steelhorse systemd[1]: shadow.service failed.
Apr 30 00:00:15 steelhorse systemd[1]: Started Update man-db cache.
Apr 30 00:03:38 steelhorse systemd[1]: Started Update locate database.
Apr 30 01:21:50 steelhorse kernel: usb 4-4: USB disconnect, device number 13
Apr 30 01:21:50 steelhorse systemd-udevd[179]: error opening USB device 'descriptors' file
Apr 30 01:21:50 steelhorse kernel: usb 4-4: new high-speed USB device number 14 using ehci-pci
Apr 30 01:21:50 steelhorse colord[837]: (colord:837): Cd-WARNING **: CdMain: failed to emit DeviceAdded: failed to register object: An object is already exported for the interface org.freedesktop.ColorManager.Device at /org/freedesktop/ColorManager/devices/sysfs__null_
Apr 30 02:16:02 steelhorse kernel: usb 4-4: USB disconnect, device number 14
Apr 30 02:16:03 steelhorse systemd-udevd[179]: error opening USB device 'descriptors' file
Apr 30 02:16:04 steelhorse kernel: usb 4-4: new high-speed USB device number 15 using ehci-pci
Apr 30 02:16:04 steelhorse colord[837]: (colord:837): Cd-WARNING **: CdMain: failed to emit DeviceAdded: failed to register object: An object is already exported for the interface org.freedesktop.ColorManager.Device at /org/freedesktop/ColorManager/devices/sysfs__null_
Apr 30 02:16:05 steelhorse kernel: usb 4-4: USB disconnect, device number 15
Apr 30 02:16:05 steelhorse systemd-udevd[179]: error opening USB device 'descriptors' file
Apr 30 02:16:06 steelhorse kernel: usb 4-4: new high-speed USB device number 16 using ehci-pci
Apr 30 02:16:06 steelhorse colord[837]: (colord:837): Cd-WARNING **: CdMain: failed to emit DeviceAdded: failed to register object: An object is already exported for the interface org.freedesktop.ColorManager.Device at /org/freedesktop/ColorManager/devices/sysfs__null_
--Reboot --
[this morning's logs]
This morning I got a crash -- and a lot sooner than usualy. Here are some potentially relevant snippets:
Apr 30 06:40:16 steelhorse kernel: ACPI: AC Adapter [ACAD] (on-line)
Apr 30 06:40:16 steelhorse kernel: [Firmware Bug]: Invalid critical threshold (0)
Apr 30 06:40:16 steelhorse kernel: thermal LNXTHERM:00: registered as thermal_zone0
Oddly I'm having trouble finding anything between 6:55 when I believe it crashed and 7:15 when I forced it to reboot. Odd... Hope what I gave helps!
Offline
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.
Offline
But meanwhile, ignore repo-ck updates? Or should I downgrade as well? I'm not experiencing any crashes.
Offline
Is anyone getting the errors with an AMD system?
PC1: Intel Sandybridge + NVIDIA -> Kernel Panic
Laptop: AMD Turion X2 (2007) + nouveau -> Works flawlesslyCould also be, because I use nouveau on the laptop and not nvidia-ck.
I booted an AMD kernel-ck-k10 which uses nvidia-ck-k10 once or twice a day on a remote system.
I got one boot hang, otherwise it booted normally. After the hang, I switched to the non ck kernel.
Today I have switched back to the 3.19 ck kernel, &c.
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline