Announcement

Collapse
No announcement yet.

You May Want To Wait On Trying Out The Linux 4.2 Kernel

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • sobkas
    replied
    Originally posted by osinclair View Post
    On a system using Kubuntu 14.10, non systemd in other words, I have no issues with this kernel. Picked from Ubuntu mainline kernel ppa. CPU is Intel Core i5 second gen. Could it be something to do with systemd?
    Nope, I use systemd and also doesn't have problems with panic at start(but have problem I mentioned earlier), must be something to do with cpu.
    So anyone having problems use 32-bit distro or kernel?
    It works on with 64 bit userspace and 64 biit kernel:
    processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD FX(tm)-6350 Six-Core Processor stepping : 0 microcode : 0x6000822 cpu MHz : 3600.000 cache size : 2048 KB physical id : 0 siblings : 6 core id : 0 cpu cores : 3 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold vmmcall bmi1 bugs : fxsave_leak bogomips : 8452.75 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro

    Leave a comment:


  • Ardje
    replied
    Originally posted by osinclair View Post
    On a system using Kubuntu 14.10, non systemd in other words, I have no issues with this kernel. Picked from Ubuntu mainline kernel ppa. CPU is Intel Core i5 second gen. Could it be something to do with systemd?
    I would love to blame systemd for everything but a kernel should not panic/crash no matter what the userspace does. (Ok, panic on no root-device and such, that's ok). If systemd refuses to boot up your system correctly it's a different thing. Just as long as the kernel is stable.

    Leave a comment:


  • osinclair
    replied
    On a system using Kubuntu 14.10, non systemd in other words, I have no issues with this kernel. Picked from Ubuntu mainline kernel ppa. CPU is Intel Core i5 second gen. Could it be something to do with systemd?

    Leave a comment:


  • jakubo
    replied
    for me it runs fine, no issues whatsoever since it was in the fc23 (rawhide) repos - i.e. 2 or 3 days

    Leave a comment:


  • dungeon
    replied
    It is compiled using Sid's default gcc 4.9 and rc1 tarball. localmodconfig-ed and couple things added/removed too, etc.. that config is likely completely unusable for you but anyway as you wish:

    http://paste.debian.net/plain/279629
    Last edited by dungeon; 07-06-2015, 05:05 PM.

    Leave a comment:


  • sobkas
    replied
    In Sunday I was bisecting kernel, and it booted every time. Can you provide .config of your kernel? What compiler you used?
    Last edited by sobkas; 07-06-2015, 04:59 PM.

    Leave a comment:


  • dungeon
    replied
    No idea, rc1 all works fine since yesterday release of rc1 here on Athlon 5350 and Debian Sid... but it is self compiled minimal one, not a distro kernel.

    Leave a comment:


  • Michael
    replied
    Originally posted by adler187 View Post
    It seems that with Grub's one time boot and automatic reboot on kernel panic, you could get around the latter limitation. Won't help the speed, though.

    A Continuous Integration-like system for testing Linux kernel development would be really great and something I would definitely support. I wonder if any companies like Intel are already doing something like this internally.
    I haven't found an easy way to tell GRUB that "If(kernel panic) reboot to older kernel instead as the default", if there was a way to do that, PTS already takes care of handling the rest. Rather right now it always seems to default to the latest (broken) kernel.

    Leave a comment:


  • adler187
    replied
    Before anyone asks, no, unfortunately it's not much of an option to do the bisecting of the regressions given the affected systems are rather slow, and while PTS has support for auto-bisecting and can withstand preserving states across reboots, it will hang on the faulty kernel revisions and require manual intervention to recover.
    It seems that with Grub's one time boot and automatic reboot on kernel panic, you could get around the latter limitation. Won't help the speed, though.

    A Continuous Integration-like system for testing Linux kernel development would be really great and something I would definitely support. I wonder if any companies like Intel are already doing something like this internally.

    Leave a comment:


  • Luke
    replied
    AMD FX-8120 on FX990 chipset also gets a very quick kernel panic attempting to boot the 4.2 kernel as built by the Ubuntu kernel PPA late on July 5

    Leave a comment:

Working...
X