Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Kernel stops booting
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
GentooForEver
n00b
n00b


Joined: 09 Mar 2017
Posts: 5

PostPosted: Thu Mar 09, 2017 3:47 pm    Post subject: Kernel stops booting Reply with quote

I'm new to gentoo and I'm inexperienced with the command line. I tried to install gentoo with the live kde environment several times. I followed the gentoo handbook. (Despite my problems I think the gentoo distro is great. I appreciate the learning experience with the articles on gentoo.org very much. Lots of thanks to the gentoo community!)

There are several harddrives in my computer. On the /dev/sda are Windows 7 and Linux Mint installed and everything works, with the exception of two usb 3.0 connectors. These usb connectors stopped working after half a year. Probably a hardware problem.

I tried to install gentoo on /dev/sdf with a msdos partition table. I'm booting only with bios. There are other harddrives in my system with gpt-partitions tables. I compiled a custom kernel.

I have searched the /var/log/messages for clues. I also searched the gentoo forums.

The last thing I tried: I actived the following kernel configuration: "Automount devtmpfs at /dev, after the kernel mounted the rootfs" In the handbook this option is deactivated. I found in the gentoo forum two old posts, that described, that activating this solved the boot problem. Not for me.

So here are the /var/log/messages:

Code:
Mar  9 14:52:22 tux syslogd 1.5.1: restart.
Mar  9 14:52:23 tux kernel: klogd 1.5.1, log source = /proc/kmsg started.
Mar  9 14:52:23 tux kernel: Inspecting /boot/System.map-4.9.6-gentoo-r1
Mar  9 14:52:23 tux kernel: Inspecting /usr/src/linux/System.map
Mar  9 14:52:23 tux kernel: Cannot find map file.
Mar  9 14:52:23 tux kernel: Loaded 48185 symbols from 2 modules.
Mar  9 14:52:23 tux kernel: [    0.000000] Linux version 4.9.6-gentoo-r1 (root@livecd) (gcc version 4.9.4 (Gentoo 4.9.4 p1.0, pie-0.6.4) ) #2 SMP Thu Mar 9 15:44:37 MET 2017
Mar  9 14:52:23 tux kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.9.6-gentoo-r1 root=/dev/sdf4 ro
Mar  9 14:52:23 tux kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Mar  9 14:52:23 tux kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Mar  9 14:52:23 tux kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Mar  9 14:52:23 tux kernel: [    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Mar  9 14:52:23 tux kernel: [    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Mar  9 14:52:23 tux kernel: [    0.000000] x86/fpu: Using 'eager' FPU context switches.
Mar  9 14:52:23 tux kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000009f02bfff] usable
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x000000009f02c000-0x000000009f032fff] ACPI NVS
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x000000009f033000-0x00000000a00aefff] usable
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000a00af000-0x00000000a0637fff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000a0638000-0x00000000b9bbbfff] usable
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000b9bbc000-0x00000000ba0fafff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000ba0fb000-0x00000000ba1ebfff] ACPI NVS
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000ba1ec000-0x00000000baffefff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000bafff000-0x00000000baffffff] usable
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000bb800000-0x00000000bf9fffff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Mar  9 14:52:23 tux kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000043f5fffff] usable
Mar  9 14:52:23 tux kernel: [    0.000000] NX (Execute Disable) protection: active
Mar  9 14:52:23 tux kernel: [    0.000000] SMBIOS 2.7 present.
Mar  9 14:52:23 tux kernel: [    0.000000] e820: last_pfn = 0x43f600 max_arch_pfn = 0x400000000
Mar  9 14:52:23 tux kernel: [    0.000000] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT 
Mar  9 14:52:23 tux kernel: [    0.000000] e820: last_pfn = 0xbb000 max_arch_pfn = 0x400000000
Mar  9 14:52:23 tux kernel: [    0.000000] found SMP MP-table at [mem 0x000fd770-0x000fd77f] mapped at [ffff8800000fd770]
Mar  9 14:52:23 tux kernel: [    0.000000] Scanning 1 areas for low memory corruption
Mar  9 14:52:23 tux kernel: [    0.000000] Using GB pages for direct mapping
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: Early table checksum verification disabled
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: RSDP 0x00000000000F0490 000024 (v02 ALASKA)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: XSDT 0x00000000BA1C1080 000084 (v01 ALASKA A M I    01072009 AMI  00010013)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: FACP 0x00000000BA1CD0C8 00010C (v05 ALASKA A M I    01072009 AMI  00010013)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: DSDT 0x00000000BA1C11A0 00BF25 (v02 ALASKA A M I    000000F9 INTL 20091112)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: FACS 0x00000000BA1EA080 000040
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: APIC 0x00000000BA1CD1D8 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: FPDT 0x00000000BA1CD270 000044 (v01 ALASKA A M I    01072009 AMI  00010013)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: SSDT 0x00000000BA1CD2B8 000539 (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: SSDT 0x00000000BA1CD7F8 000AD8 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: MCFG 0x00000000BA1CE2D0 00003C (v01                 01072009 MSFT 00000097)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: HPET 0x00000000BA1CE310 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: SSDT 0x00000000BA1CE348 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: SSDT 0x00000000BA1CE6B8 003299 (v01 SaSsdt SaSsdt   00003000 INTL 20091112)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: DMAR 0x00000000BA1D1958 0000B8 (v01 INTEL  HSW      00000001 INTL 00000001)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: SSDT 0x00000000BA1D1A10 000803 (v01 Intel_ IsctTabl 00001000 INTL 20091112)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: MATS 0x00000000BA1D2218 000034 (v02 ALASKA A M I    00000002 w?x2 00000000)
Mar  9 14:52:23 tux kernel: [    0.000000] No NUMA configuration found
Mar  9 14:52:23 tux kernel: [    0.000000] Faking a node at [mem 0x0000000000000000-0x000000043f5fffff]
Mar  9 14:52:23 tux kernel: [    0.000000] NODE_DATA(0) allocated [mem 0x43f5f8000-0x43f5fbfff]
Mar  9 14:52:23 tux kernel: [    0.000000] Zone ranges:
Mar  9 14:52:23 tux kernel: [    0.000000]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Mar  9 14:52:23 tux kernel: [    0.000000]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Mar  9 14:52:23 tux kernel: [    0.000000]   Normal   [mem 0x0000000100000000-0x000000043f5fffff]
Mar  9 14:52:23 tux kernel: [    0.000000] Movable zone start for each node
Mar  9 14:52:23 tux kernel: [    0.000000] Early memory node ranges
Mar  9 14:52:23 tux kernel: [    0.000000]   node   0: [mem 0x0000000000001000-0x000000000009cfff]
Mar  9 14:52:23 tux kernel: [    0.000000]   node   0: [mem 0x0000000000100000-0x000000009f02bfff]
Mar  9 14:52:23 tux kernel: [    0.000000]   node   0: [mem 0x000000009f033000-0x00000000a00aefff]
Mar  9 14:52:23 tux kernel: [    0.000000]   node   0: [mem 0x00000000a0638000-0x00000000b9bbbfff]
Mar  9 14:52:23 tux kernel: [    0.000000]   node   0: [mem 0x00000000bafff000-0x00000000baffffff]
Mar  9 14:52:23 tux kernel: [    0.000000]   node   0: [mem 0x0000000100000000-0x000000043f5fffff]
Mar  9 14:52:23 tux kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000043f5fffff]
Mar  9 14:52:23 tux kernel: [    0.000000] Reserving Intel graphics memory at 0x00000000bba00000-0x00000000bf9fffff
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x1808
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Mar  9 14:52:23 tux kernel: [    0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Mar  9 14:52:23 tux kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Mar  9 14:52:23 tux kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Mar  9 14:52:23 tux kernel: [    0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0x9f02c000-0x9f032fff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xa00af000-0xa0637fff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xb9bbc000-0xba0fafff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xba0fb000-0xba1ebfff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xba1ec000-0xbaffefff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xbb000000-0xbb7fffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xbb800000-0xbf9fffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xbfa00000-0xf7ffffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Mar  9 14:52:23 tux kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Mar  9 14:52:23 tux kernel: [    0.000000] e820: [mem 0xbfa00000-0xf7ffffff] available for PCI devices
Mar  9 14:52:23 tux kernel: [    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
Mar  9 14:52:23 tux kernel: [    0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1
Mar  9 14:52:23 tux kernel: [    0.000000] percpu: Embedded 34 pages/cpu @ffff88043f200000 s101656 r8192 d29416 u262144
Mar  9 14:52:23 tux kernel: [    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 4099459
Mar  9 14:52:23 tux kernel: [    0.000000] Policy zone: Normal
Mar  9 14:52:23 tux kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.6-gentoo-r1 root=/dev/sdf4 ro
Mar  9 14:52:23 tux kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Mar  9 14:52:23 tux kernel: [    0.000000] Memory: 16308784K/16658212K available (11107K kernel code, 1554K rwdata, 3204K rodata, 1212K init, 836K bss, 349428K reserved, 0K cma-reserved)
Mar  9 14:52:23 tux kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
Mar  9 14:52:23 tux kernel: [    0.000000] Hierarchical RCU implementation.
Mar  9 14:52:23 tux kernel: [    0.000000] ^IBuild-time adjustment of leaf fanout to 64.
Mar  9 14:52:23 tux kernel: [    0.000000] ^IRCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=8.
Mar  9 14:52:23 tux kernel: [    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=8
Mar  9 14:52:23 tux kernel: [    0.000000] NR_IRQS:4352 nr_irqs:488 16
Mar  9 14:52:23 tux kernel: [    0.000000] Console: colour VGA+ 80x25
Mar  9 14:52:23 tux kernel: [    0.000000] console [tty0] enabled
Mar  9 14:52:23 tux kernel: [    0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Mar  9 14:52:23 tux kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Mar  9 14:52:23 tux kernel: [    0.000000] tsc: Detected 3392.103 MHz processor
Mar  9 14:52:23 tux kernel: [    0.000014] Calibrating delay loop (skipped), value calculated using timer frequency.. 6784.20 BogoMIPS (lpj=3392103)
Mar  9 14:52:23 tux kernel: [    0.000342] pid_max: default: 32768 minimum: 301
Mar  9 14:52:23 tux kernel: [    0.000502] ACPI: Core revision 20160831
Mar  9 14:52:23 tux kernel: [    0.005657] ACPI: 6 ACPI AML tables successfully acquired and loaded
Mar  9 14:52:23 tux kernel: [    0.005866] Security Framework initialized
Mar  9 14:52:23 tux kernel: [    0.006028] SELinux:  Initializing.
Mar  9 14:52:23 tux kernel: [    0.006597] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Mar  9 14:52:23 tux kernel: [    0.008883] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Mar  9 14:52:23 tux kernel: [    0.010069] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mar  9 14:52:23 tux kernel: [    0.010246] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mar  9 14:52:23 tux kernel: [    0.010703] CPU: Physical Processor ID: 0
Mar  9 14:52:23 tux kernel: [    0.010865] CPU: Processor Core ID: 0
Mar  9 14:52:23 tux kernel: [    0.011029] mce: CPU supports 9 MCE banks
Mar  9 14:52:23 tux kernel: [    0.011189] CPU0: Thermal monitoring enabled (TM1)
Mar  9 14:52:23 tux kernel: [    0.011359] process: using mwait in idle threads
Mar  9 14:52:23 tux kernel: [    0.011516] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
Mar  9 14:52:23 tux kernel: [    0.011687] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
Mar  9 14:52:23 tux kernel: [    0.012149] Freeing SMP alternatives memory: 40K (ffffffff822b5000 - ffffffff822bf000)
Mar  9 14:52:23 tux kernel: [    0.013827] smpboot: Max logical packages: 2
Mar  9 14:52:23 tux kernel: [    0.014353] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Mar  9 14:52:23 tux kernel: [    0.024519] smpboot: CPU0: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (family: 0x6, model: 0x3c, stepping: 0x3)
Mar  9 14:52:23 tux kernel: [    0.024924] Performance Events: PEBS fmt2+, Haswell events, 16-deep LBR, full-width counters, Intel PMU driver.
Mar  9 14:52:23 tux kernel: [    0.025424] ... version:                3
Mar  9 14:52:23 tux kernel: [    0.025584] ... bit width:              48
Mar  9 14:52:23 tux kernel: [    0.025738] ... generic registers:      4
Mar  9 14:52:23 tux kernel: [    0.025900] ... value mask:             0000ffffffffffff
Mar  9 14:52:23 tux kernel: [    0.026064] ... max period:             00007fffffffffff
Mar  9 14:52:23 tux kernel: [    0.026226] ... fixed-purpose events:   3
Mar  9 14:52:23 tux kernel: [    0.026388] ... event mask:             000000070000000f
Mar  9 14:52:23 tux kernel: [    0.026723] x86: Booting SMP configuration:
Mar  9 14:52:23 tux kernel: [    0.026887] .... node  #0, CPUs:      #1 #2 #3 #4 #5 #6 #7
Mar  9 14:52:23 tux kernel: [    0.460922] x86: Booted up 1 node, 8 CPUs
Mar  9 14:52:23 tux kernel: [    0.461240] smpboot: Total of 8 processors activated (54299.85 BogoMIPS)
Mar  9 14:52:23 tux kernel: [    0.467194] devtmpfs: initialized
Mar  9 14:52:23 tux kernel: [    0.467457] PM: Registering ACPI NVS region [mem 0x9f02c000-0x9f032fff] (28672 bytes)
Mar  9 14:52:23 tux kernel: [    0.467737] PM: Registering ACPI NVS region [mem 0xba0fb000-0xba1ebfff] (987136 bytes)
Mar  9 14:52:23 tux kernel: [    0.470755] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
Mar  9 14:52:23 tux kernel: [    0.470766] kworker/u16:0 (50) used greatest stack depth: 14128 bytes left
Mar  9 14:52:23 tux kernel: [    0.471179] xor: automatically using best checksumming function   avx       
Mar  9 14:52:23 tux kernel: [    0.471355] RTC time: 14:52:17, date: 03/09/17
Mar  9 14:52:23 tux kernel: [    0.471546] NET: Registered protocol family 16
Mar  9 14:52:23 tux kernel: [    0.477765] cpuidle: using governor menu
Mar  9 14:52:23 tux kernel: [    0.477931] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Mar  9 14:52:23 tux kernel: [    0.478184] ACPI: bus type PCI registered
Mar  9 14:52:23 tux kernel: [    0.478361] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Mar  9 14:52:23 tux kernel: [    0.478618] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Mar  9 14:52:23 tux kernel: [    0.478773] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
Mar  9 14:52:23 tux kernel: [    0.479058] PCI: Using configuration type 1 for base access
Mar  9 14:52:23 tux kernel: [    0.479242] core: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Mar  9 14:52:23 tux kernel: [    0.487881] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Mar  9 14:52:23 tux kernel: [    0.504830] raid6: sse2x1   gen() 11875 MB/s
Mar  9 14:52:23 tux kernel: [    0.521837] raid6: sse2x1   xor()  9277 MB/s
Mar  9 14:52:23 tux kernel: [    0.538848] raid6: sse2x2   gen() 15007 MB/s
Mar  9 14:52:23 tux kernel: [    0.555858] raid6: sse2x2   xor() 10667 MB/s
Mar  9 14:52:23 tux kernel: [    0.572868] raid6: sse2x4   gen() 17531 MB/s
Mar  9 14:52:23 tux kernel: [    0.589879] raid6: sse2x4   xor() 12019 MB/s
Mar  9 14:52:23 tux kernel: [    0.606889] raid6: avx2x1   gen() 23421 MB/s
Mar  9 14:52:23 tux kernel: [    0.623900] raid6: avx2x2   gen() 26988 MB/s
Mar  9 14:52:23 tux kernel: [    0.640910] raid6: avx2x4   gen() 31718 MB/s
Mar  9 14:52:23 tux kernel: [    0.641058] raid6: using algorithm avx2x4 gen() 31718 MB/s
Mar  9 14:52:23 tux kernel: [    0.641207] raid6: using avx2x2 recovery algorithm
Mar  9 14:52:23 tux kernel: [    0.641376] ACPI: Added _OSI(Module Device)
Mar  9 14:52:23 tux kernel: [    0.641524] ACPI: Added _OSI(Processor Device)
Mar  9 14:52:23 tux kernel: [    0.641671] ACPI: Added _OSI(3.0 _SCP Extensions)
Mar  9 14:52:23 tux kernel: [    0.641820] ACPI: Added _OSI(Processor Aggregator Device)
Mar  9 14:52:23 tux kernel: [    0.642075] ACPI: Executed 1 blocks of module-level executable AML code
Mar  9 14:52:23 tux kernel: [    0.644651] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Mar  9 14:52:23 tux kernel: [    0.645098] ACPI: Dynamic OEM Table Load:
Mar  9 14:52:23 tux kernel: [    0.645329] ACPI: SSDT 0xFFFF88042C5B0000 0003D3 (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Mar  9 14:52:23 tux kernel: [    0.645862] ACPI: Dynamic OEM Table Load:
Mar  9 14:52:23 tux kernel: [    0.646096] ACPI: SSDT 0xFFFF88042C530000 0005AA (v01 PmRef  ApIst    00003000 INTL 20051117)
Mar  9 14:52:23 tux kernel: [    0.646640] ACPI: Dynamic OEM Table Load:
Mar  9 14:52:23 tux kernel: [    0.646872] ACPI: SSDT 0xFFFF88042C404000 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Mar  9 14:52:23 tux kernel: [    0.648174] ACPI: Interpreter enabled
Mar  9 14:52:23 tux kernel: [    0.648336] ACPI: (supports S0 S3 S4 S5)
Mar  9 14:52:23 tux kernel: [    0.648483] ACPI: Using IOAPIC for interrupt routing
Mar  9 14:52:23 tux kernel: [    0.648648] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Mar  9 14:52:23 tux kernel: [    0.653955] ACPI: Power Resource [FN00] (off)
Mar  9 14:52:23 tux kernel: [    0.654152] ACPI: Power Resource [FN01] (off)
Mar  9 14:52:23 tux kernel: [    0.654341] ACPI: Power Resource [FN02] (off)
Mar  9 14:52:23 tux kernel: [    0.654531] ACPI: Power Resource [FN03] (off)
Mar  9 14:52:23 tux kernel: [    0.654719] ACPI: Power Resource [FN04] (off)
Mar  9 14:52:23 tux kernel: [    0.655296] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Mar  9 14:52:23 tux kernel: [    0.655449] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Mar  9 14:52:23 tux kernel: [    0.655819] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME]
Mar  9 14:52:23 tux kernel: [    0.656144] acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability]
Mar  9 14:52:23 tux kernel: [    0.656295] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
Mar  9 14:52:23 tux kernel: [    0.656680] PCI host bridge to bus 0000:00
Mar  9 14:52:23 tux kernel: [    0.656828] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Mar  9 14:52:23 tux kernel: [    0.656980] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Mar  9 14:52:23 tux kernel: [    0.657133] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Mar  9 14:52:23 tux kernel: [    0.657386] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Mar  9 14:52:23 tux kernel: [    0.657639] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Mar  9 14:52:23 tux kernel: [    0.657892] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Mar  9 14:52:23 tux kernel: [    0.658146] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window]
Mar  9 14:52:23 tux kernel: [    0.658399] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window]
Mar  9 14:52:23 tux kernel: [    0.658652] pci_bus 0000:00: root bus resource [mem 0xbfa00000-0xfeafffff window]
Mar  9 14:52:23 tux kernel: [    0.658906] pci_bus 0000:00: root bus resource [bus 00-3e]
Mar  9 14:52:23 tux kernel: [    0.659191] pci 0000:00:01.0: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.659590] pci 0000:00:14.0: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.659966] pci 0000:00:19.0: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.660256] pci 0000:00:1a.0: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.660521] pci 0000:00:1b.0: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.660786] pci 0000:00:1c.0: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.661052] pci 0000:00:1c.3: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.661317] pci 0000:00:1c.4: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.661580] pci 0000:00:1c.6: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.661868] pci 0000:00:1d.0: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.662453] pci 0000:01:00.0: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.665215] pci 0000:00:01.0: PCI bridge to [bus 01]
Mar  9 14:52:23 tux kernel: [    0.665394] pci 0000:00:1c.0: PCI bridge to [bus 02]
Mar  9 14:52:23 tux kernel: [    0.665805] pci 0000:03:00.0: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.668218] pci 0000:00:1c.3: PCI bridge to [bus 03]
Mar  9 14:52:23 tux kernel: [    0.668477] pci 0000:04:00.0: Enabling fixed DMA alias to 00.1
Mar  9 14:52:23 tux kernel: [    0.668684] pci 0000:04:00.0: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.671218] pci 0000:00:1c.4: PCI bridge to [bus 04]
Mar  9 14:52:23 tux kernel: [    0.671540] pci 0000:05:00.0: System wakeup disabled by ACPI
Mar  9 14:52:23 tux kernel: [    0.671705] pci 0000:00:1c.6: PCI bridge to [bus 05-06] (subtractive decode)
Mar  9 14:52:23 tux kernel: [    0.672176] pci 0000:05:00.0: PCI bridge to [bus 06] (subtractive decode)
Mar  9 14:52:23 tux kernel: [    0.672831] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Mar  9 14:52:23 tux kernel: [    0.673453] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Mar  9 14:52:23 tux kernel: [    0.674073] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *10 11 12 14 15)
Mar  9 14:52:23 tux kernel: [    0.674694] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 10 11 12 14 15)
Mar  9 14:52:23 tux kernel: [    0.675313] ACPI: PCI Interrupt Link [LNKE] (IRQs *3 4 5 6 10 11 12 14 15)
Mar  9 14:52:23 tux kernel: [    0.675934] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Mar  9 14:52:23 tux kernel: [    0.676737] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Mar  9 14:52:23 tux kernel: [    0.677356] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 10 11 12 14 15)
Mar  9 14:52:23 tux kernel: [    0.678149] ACPI: Enabled 4 GPEs in block 00 to 3F
Mar  9 14:52:23 tux kernel: [    0.678471] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=mem,locks=none
Mar  9 14:52:23 tux kernel: [    0.678730] vgaarb: setting as boot device: PCI:0000:01:00.0
Mar  9 14:52:23 tux kernel: [    0.678880] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
Mar  9 14:52:23 tux kernel: [    0.679134] vgaarb: loaded
Mar  9 14:52:23 tux kernel: [    0.679280] vgaarb: bridge control possible 0000:01:00.0
Mar  9 14:52:23 tux kernel: [    0.679429] vgaarb: no bridge control possible 0000:00:02.0
Mar  9 14:52:23 tux kernel: [    0.679611] SCSI subsystem initialized
Mar  9 14:52:23 tux kernel: [    0.679800] ACPI: bus type USB registered
Mar  9 14:52:23 tux kernel: [    0.679958] usbcore: registered new interface driver usbfs
Mar  9 14:52:23 tux kernel: [    0.680112] usbcore: registered new interface driver hub
Mar  9 14:52:23 tux kernel: [    0.680273] usbcore: registered new device driver usb
Mar  9 14:52:23 tux kernel: [    0.680431] pps_core: LinuxPPS API ver. 1 registered
Mar  9 14:52:23 tux kernel: [    0.680580] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Mar  9 14:52:23 tux kernel: [    0.680839] PTP clock support registered
Mar  9 14:52:23 tux kernel: [    0.681024] Advanced Linux Sound Architecture Driver Initialized.
Mar  9 14:52:23 tux kernel: [    0.681182] PCI: Using ACPI for IRQ routing
Mar  9 14:52:23 tux kernel: [    0.682608] NetLabel: Initializing
Mar  9 14:52:23 tux kernel: [    0.682755] NetLabel:  domain hash size = 128
Mar  9 14:52:23 tux kernel: [    0.682902] NetLabel:  protocols = UNLABELED CIPSOv4
Mar  9 14:52:23 tux kernel: [    0.683063] NetLabel:  unlabeled traffic allowed by default
Mar  9 14:52:23 tux kernel: [    0.683257] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Mar  9 14:52:23 tux kernel: [    0.683772] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Mar  9 14:52:23 tux kernel: [    0.685947] clocksource: Switched to clocksource hpet
Mar  9 14:52:23 tux kernel: [    0.691320] VFS: Disk quotas dquot_6.6.0
Mar  9 14:52:23 tux kernel: [    0.691479] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Mar  9 14:52:23 tux kernel: [    0.692492] pnp: PnP ACPI init
Mar  9 14:52:23 tux kernel: [    0.692694] system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.692954] system 00:01: [io  0x0680-0x069f] has been reserved
Mar  9 14:52:23 tux kernel: [    0.693106] system 00:01: [io  0xffff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.693256] system 00:01: [io  0xffff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.693405] system 00:01: [io  0xffff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.693555] system 00:01: [io  0x1c00-0x1cfe] has been reserved
Mar  9 14:52:23 tux kernel: [    0.693705] system 00:01: [io  0x1d00-0x1dfe] has been reserved
Mar  9 14:52:23 tux kernel: [    0.693855] system 00:01: [io  0x1e00-0x1efe] has been reserved
Mar  9 14:52:23 tux kernel: [    0.694011] system 00:01: [io  0x1f00-0x1ffe] has been reserved
Mar  9 14:52:23 tux kernel: [    0.694161] system 00:01: [io  0x1800-0x18fe] has been reserved
Mar  9 14:52:23 tux kernel: [    0.694311] system 00:01: [io  0x164e-0x164f] has been reserved
Mar  9 14:52:23 tux kernel: [    0.694508] system 00:03: [io  0x1854-0x1857] has been reserved
Mar  9 14:52:23 tux kernel: [    0.694729] system 00:04: [io  0x0a00-0x0a0f] has been reserved
Mar  9 14:52:23 tux kernel: [    0.694882] system 00:04: [io  0x0a30-0x0a3f] has been reserved
Mar  9 14:52:23 tux kernel: [    0.695038] system 00:04: [io  0x0a20-0x0a2f] has been reserved
Mar  9 14:52:23 tux kernel: [    0.695386] system 00:06: [io  0x04d0-0x04d1] has been reserved
Mar  9 14:52:23 tux kernel: [    0.695786] system 00:07: [mem 0xfed1c000-0xfed1ffff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.695940] system 00:07: [mem 0xfed10000-0xfed17fff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.696098] system 00:07: [mem 0xfed18000-0xfed18fff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.696249] system 00:07: [mem 0xfed19000-0xfed19fff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.696401] system 00:07: [mem 0xf8000000-0xfbffffff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.696552] system 00:07: [mem 0xfed20000-0xfed3ffff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.696704] system 00:07: [mem 0xfed90000-0xfed93fff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.696855] system 00:07: [mem 0xfed45000-0xfed8ffff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.697012] system 00:07: [mem 0xff000000-0xffffffff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.697163] system 00:07: [mem 0xfee00000-0xfeefffff] could not be reserved
Mar  9 14:52:23 tux kernel: [    0.697315] system 00:07: [mem 0xf7ffe000-0xf7ffefff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.697467] system 00:07: [mem 0xf7fe0000-0xf7fe0fff] has been reserved
Mar  9 14:52:23 tux kernel: [    0.697764] pnp: PnP ACPI: found 8 devices
Mar  9 14:52:23 tux kernel: [    0.702439] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Mar  9 14:52:23 tux kernel: [    0.702733] pci 0000:00:01.0: PCI bridge to [bus 01]
Mar  9 14:52:23 tux kernel: [    0.702882] pci 0000:00:01.0:   bridge window [io  0xe000-0xefff]
Mar  9 14:52:23 tux kernel: [    0.703039] pci 0000:00:01.0:   bridge window [mem 0xd0000000-0xdb0fffff]
Mar  9 14:52:23 tux kernel: [    0.703193] pci 0000:00:1c.0: PCI bridge to [bus 02]
Mar  9 14:52:23 tux kernel: [    0.703349] pci 0000:00:1c.3: PCI bridge to [bus 03]
Mar  9 14:52:23 tux kernel: [    0.703498] pci 0000:00:1c.3:   bridge window [io  0xd000-0xdfff]
Mar  9 14:52:23 tux kernel: [    0.703651] pci 0000:00:1c.3:   bridge window [mem 0xdb800000-0xdbafffff]
Mar  9 14:52:23 tux kernel: [    0.703807] pci 0000:00:1c.4: PCI bridge to [bus 04]
Mar  9 14:52:23 tux kernel: [    0.703961] pci 0000:00:1c.4:   bridge window [io  0xc000-0xcfff]
Mar  9 14:52:23 tux kernel: [    0.706560] pci 0000:00:1c.4:   bridge window [mem 0xdbc00000-0xdbcfffff]
Mar  9 14:52:23 tux kernel: [    0.706716] pci 0000:05:00.0: PCI bridge to [bus 06]
Mar  9 14:52:23 tux kernel: [    0.706867] pci 0000:05:00.0:   bridge window [io  0xb000-0xbfff]
Mar  9 14:52:23 tux kernel: [    0.707028] pci 0000:05:00.0:   bridge window [mem 0xdbb00000-0xdbbfffff]
Mar  9 14:52:23 tux kernel: [    0.707192] pci 0000:00:1c.6: PCI bridge to [bus 05-06]
Mar  9 14:52:23 tux kernel: [    0.707341] pci 0000:00:1c.6:   bridge window [io  0xb000-0xbfff]
Mar  9 14:52:23 tux kernel: [    0.707494] pci 0000:00:1c.6:   bridge window [mem 0xdbb00000-0xdbbfffff]
Mar  9 14:52:23 tux kernel: [    0.707731] NET: Registered protocol family 2
Mar  9 14:52:23 tux kernel: [    0.707997] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
Mar  9 14:52:23 tux kernel: [    0.708363] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Mar  9 14:52:23 tux kernel: [    0.708623] TCP: Hash tables configured (established 131072 bind 65536)
Mar  9 14:52:23 tux kernel: [    0.708789] UDP hash table entries: 8192 (order: 6, 262144 bytes)
Mar  9 14:52:23 tux kernel: [    0.708977] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
Mar  9 14:52:23 tux kernel: [    0.709179] NET: Registered protocol family 1
Mar  9 14:52:23 tux kernel: [    0.709379] RPC: Registered named UNIX socket transport module.
Mar  9 14:52:23 tux kernel: [    0.709529] RPC: Registered udp transport module.
Mar  9 14:52:23 tux kernel: [    0.709678] RPC: Registered tcp transport module.
Mar  9 14:52:23 tux kernel: [    0.709826] RPC: Registered tcp NFSv4.1 backchannel transport module.
Mar  9 14:52:23 tux kernel: [    0.742017] pci 0000:01:00.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Mar  9 14:52:23 tux kernel: [    0.742316] DMAR: Host address width 39
Mar  9 14:52:23 tux kernel: [    0.742464] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
Mar  9 14:52:23 tux kernel: [    0.742617] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap c0000020660462 ecap f0101a
Mar  9 14:52:23 tux kernel: [    0.742871] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
Mar  9 14:52:23 tux kernel: [    0.743028] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008020660462 ecap f010da
Mar  9 14:52:23 tux kernel: [    0.743283] DMAR: RMRR base: 0x000000b9df0000 end: 0x000000b9dfcfff
Mar  9 14:52:23 tux kernel: [    0.743433] DMAR: RMRR base: 0x000000bb800000 end: 0x000000bf9fffff
Mar  9 14:52:23 tux kernel: [    0.743590] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Mar  9 14:52:23 tux kernel: [    0.743741] software IO TLB [mem 0xb5bbc000-0xb9bbc000] (64MB) mapped at [ffff8800b5bbc000-ffff8800b9bbbfff]
Mar  9 14:52:23 tux kernel: [    0.744061] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer
Mar  9 14:52:23 tux kernel: [    0.744316] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
Mar  9 14:52:23 tux kernel: [    0.744466] RAPL PMU: hw unit of domain package 2^-14 Joules
Mar  9 14:52:23 tux kernel: [    0.744615] RAPL PMU: hw unit of domain dram 2^-14 Joules
Mar  9 14:52:23 tux kernel: [    0.744764] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Mar  9 14:52:23 tux kernel: [    0.745262] Scanning for low memory corruption every 60 seconds
Mar  9 14:52:23 tux kernel: [    0.745563] futex hash table entries: 2048 (order: 5, 131072 bytes)
Mar  9 14:52:23 tux kernel: [    0.745729] audit: initializing netlink subsys (disabled)
Mar  9 14:52:23 tux kernel: [    0.745883] audit: type=2000 audit(1489071136.727:1): initialized
Mar  9 14:52:23 tux kernel: [    0.746289] workingset: timestamp_bits=56 max_order=22 bucket_order=0
Mar  9 14:52:23 tux kernel: [    0.747543] NFS: Registering the id_resolver key type
Mar  9 14:52:23 tux kernel: [    0.747696] Key type id_resolver registered
Mar  9 14:52:23 tux kernel: [    0.747844] Key type id_legacy registered
Mar  9 14:52:23 tux kernel: [    0.748033] JFS: nTxBlock = 8192, nTxLock = 65536
Mar  9 14:52:23 tux kernel: [    0.749019] SGI XFS with security attributes, no debug enabled
Mar  9 14:52:23 tux kernel: [    0.749991] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Mar  9 14:52:23 tux kernel: [    0.750247] io scheduler noop registered
Mar  9 14:52:23 tux kernel: [    0.750395] io scheduler deadline registered
Mar  9 14:52:23 tux kernel: [    0.750545] io scheduler cfq registered (default)
Mar  9 14:52:23 tux kernel: [    0.751011] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Mar  9 14:52:23 tux kernel: [    0.751183] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Mar  9 14:52:23 tux kernel: [    0.771856] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Mar  9 14:52:23 tux kernel: [    0.772376] Non-volatile memory driver v1.3
Mar  9 14:52:23 tux kernel: [    0.772538] Linux agpgart interface v0.103
Mar  9 14:52:23 tux kernel: [    0.772759] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
Mar  9 14:52:23 tux kernel: [    0.773024] ACPI: Power Button [PWRB]
Mar  9 14:52:23 tux kernel: [    0.773191] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Mar  9 14:52:23 tux kernel: [    0.773447] ACPI: Power Button [PWRF]
Mar  9 14:52:23 tux kernel: [    0.774780] thermal LNXTHERM:00: registered as thermal_zone0
Mar  9 14:52:23 tux kernel: [    0.774931] ACPI: Thermal Zone [TZ00] (28 C)
Mar  9 14:52:23 tux kernel: [    0.775225] thermal LNXTHERM:01: registered as thermal_zone1
Mar  9 14:52:23 tux kernel: [    0.775375] ACPI: Thermal Zone [TZ01] (30 C)
Mar  9 14:52:23 tux kernel: [    0.775541] [drm] Initialized
Mar  9 14:52:23 tux kernel: [    0.775770] i915 0000:00:02.0: enabling device (0006 -> 0007)
Mar  9 14:52:23 tux kernel: [    0.776063] [drm] Memory usable by graphics device = 2048M
Mar  9 14:52:23 tux kernel: [    0.776236] [drm] Replacing VGA console driver
Mar  9 14:52:23 tux kernel: [    0.778751] Console: switching to colour dummy device 80x25
Mar  9 14:52:23 tux kernel: [    0.785019] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Mar  9 14:52:23 tux kernel: [    0.785021] [drm] Driver supports precise vblank timestamp query.
Mar  9 14:52:23 tux kernel: [    0.787235] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=none:owns=mem
Mar  9 14:52:23 tux kernel: [    0.805174] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Mar  9 14:52:23 tux kernel: [    0.805480] acpi device:70: registered as cooling_device13
Mar  9 14:52:23 tux kernel: [    0.805549] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input2
Mar  9 14:52:23 tux kernel: [    0.805563] [drm] Initialized i915 1.6.0 20160919 for 0000:00:02.0 on minor 0
Mar  9 14:52:23 tux kernel: [    0.806739] loop: module loaded
Mar  9 14:52:23 tux kernel: [    0.806898] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
Mar  9 14:52:23 tux kernel: [    0.806902] ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst
Mar  9 14:52:23 tux kernel: [    0.808503] i915 0000:00:02.0: No connectors reported connected with modes
Mar  9 14:52:23 tux kernel: [    0.808507] [drm] Cannot find any crtc or sizes - going 1024x768
Mar  9 14:52:23 tux kernel: [    0.809709] Console: switching to colour frame buffer device 128x48
Mar  9 14:52:23 tux kernel: [    0.810653] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Mar  9 14:52:23 tux kernel: [    0.821582] scsi host0: ahci
Mar  9 14:52:23 tux kernel: [    0.821687] scsi host1: ahci
Mar  9 14:52:23 tux kernel: [    0.821771] scsi host2: ahci
Mar  9 14:52:23 tux kernel: [    0.821827] scsi host3: ahci
Mar  9 14:52:23 tux kernel: [    0.821887] scsi host4: ahci
Mar  9 14:52:23 tux kernel: [    0.822015] scsi host5: ahci
Mar  9 14:52:23 tux kernel: [    0.822056] ata1: SATA max UDMA/133 abar m2048@0xdbd3a000 port 0xdbd3a100 irq 26
Mar  9 14:52:23 tux kernel: [    0.822073] ata2: SATA max UDMA/133 abar m2048@0xdbd3a000 port 0xdbd3a180 irq 26
Mar  9 14:52:23 tux kernel: [    0.822090] ata3: SATA max UDMA/133 abar m2048@0xdbd3a000 port 0xdbd3a200 irq 26
Mar  9 14:52:23 tux kernel: [    0.822106] ata4: SATA max UDMA/133 abar m2048@0xdbd3a000 port 0xdbd3a280 irq 26
Mar  9 14:52:23 tux kernel: [    0.822122] ata5: SATA max UDMA/133 abar m2048@0xdbd3a000 port 0xdbd3a300 irq 26
Mar  9 14:52:23 tux kernel: [    0.822138] ata6: SATA max UDMA/133 abar m2048@0xdbd3a000 port 0xdbd3a380 irq 26
Mar  9 14:52:23 tux kernel: [    0.822206] ahci 0000:04:00.0: controller can do FBS, turning on CAP_FBS
Mar  9 14:52:23 tux kernel: [    0.832401] ahci 0000:04:00.0: AHCI 0001.0200 32 slots 8 ports 6 Gbps 0xff impl SATA mode
Mar  9 14:52:23 tux kernel: [    0.832419] ahci 0000:04:00.0: flags: 64bit ncq fbs pio
Mar  9 14:52:23 tux kernel: [    0.832911] scsi host6: ahci
Mar  9 14:52:23 tux kernel: [    0.833039] scsi host7: ahci
Mar  9 14:52:23 tux kernel: [    0.833495] scsi host8: ahci
Mar  9 14:52:23 tux kernel: [    0.833931] scsi host9: ahci
Mar  9 14:52:23 tux kernel: [    0.834606] scsi host10: ahci
Mar  9 14:52:23 tux kernel: [    0.835317] scsi host11: ahci
Mar  9 14:52:23 tux kernel: [    0.835753] scsi host12: ahci
Mar  9 14:52:23 tux kernel: [    0.836192] scsi host13: ahci
Mar  9 14:52:23 tux kernel: [    0.836551] ata7: SATA max UDMA/133 abar m2048@0xdbc10000 port 0xdbc10100 irq 27
Mar  9 14:52:23 tux kernel: [    0.836940] ata8: SATA max UDMA/133 abar m2048@0xdbc10000 port 0xdbc10180 irq 27
Mar  9 14:52:23 tux kernel: [    0.837308] ata9: SATA max UDMA/133 abar m2048@0xdbc10000 port 0xdbc10200 irq 27
Mar  9 14:52:23 tux kernel: [    0.837628] ata10: SATA max UDMA/133 abar m2048@0xdbc10000 port 0xdbc10280 irq 27
Mar  9 14:52:23 tux kernel: [    0.837964] ata11: SATA max UDMA/133 abar m2048@0xdbc10000 port 0xdbc10300 irq 27
Mar  9 14:52:23 tux kernel: [    0.838291] ata12: SATA max UDMA/133 abar m2048@0xdbc10000 port 0xdbc10380 irq 27
Mar  9 14:52:23 tux kernel: [    0.838591] ata13: SATA max UDMA/133 abar m2048@0xdbc10000 port 0xdbc10400 irq 27
Mar  9 14:52:23 tux kernel: [    0.838881] ata14: SATA max UDMA/133 abar m2048@0xdbc10000 port 0xdbc10480 irq 27
Mar  9 14:52:23 tux kernel: [    0.839301] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
Mar  9 14:52:23 tux kernel: [    0.839755] e100: Copyright(c) 1999-2006 Intel Corporation
Mar  9 14:52:23 tux kernel: [    0.840089] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
Mar  9 14:52:23 tux kernel: [    0.840427] e1000: Copyright (c) 1999-2006 Intel Corporation.
Mar  9 14:52:23 tux kernel: [    0.840757] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
Mar  9 14:52:23 tux kernel: [    0.841063] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
Mar  9 14:52:23 tux kernel: [    0.841402] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Mar  9 14:52:23 tux kernel: [    0.929946] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
Mar  9 14:52:23 tux kernel: [    1.012278] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 94:de:80:a5:f2:ac
Mar  9 14:52:23 tux kernel: [    1.012578] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Mar  9 14:52:23 tux kernel: [    1.012873] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
Mar  9 14:52:23 tux kernel: [    1.013188] sky2: driver version 1.30
Mar  9 14:52:23 tux kernel: [    1.013493] PPP generic driver version 2.4.2
Mar  9 14:52:23 tux kernel: [    1.069018] firewire_ohci 0000:06:01.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x11
Mar  9 14:52:23 tux kernel: [    1.069403] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Mar  9 14:52:23 tux kernel: [    1.069711] ehci-pci: EHCI PCI platform driver
Mar  9 14:52:23 tux kernel: [    1.070101] ehci-pci 0000:00:1a.0: EHCI Host Controller
Mar  9 14:52:23 tux kernel: [    1.070507] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Mar  9 14:52:23 tux kernel: [    1.070852] ehci-pci 0000:00:1a.0: debug port 2
Mar  9 14:52:23 tux kernel: [    1.075084] ehci-pci 0000:00:1a.0: irq 16, io mem 0xdbd3c000
Mar  9 14:52:23 tux kernel: [    1.081988] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Mar  9 14:52:23 tux kernel: [    1.082336] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Mar  9 14:52:23 tux kernel: [    1.082662] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar  9 14:52:23 tux kernel: [    1.083046] usb usb1: Product: EHCI Host Controller
Mar  9 14:52:23 tux kernel: [    1.083375] usb usb1: Manufacturer: Linux 4.9.6-gentoo-r1 ehci_hcd
Mar  9 14:52:23 tux kernel: [    1.083732] usb usb1: SerialNumber: 0000:00:1a.0
Mar  9 14:52:23 tux kernel: [    1.084214] hub 1-0:1.0: USB hub found
Mar  9 14:52:23 tux kernel: [    1.084569] hub 1-0:1.0: 2 ports detected
Mar  9 14:52:23 tux kernel: [    1.085028] ehci-pci 0000:00:1d.0: EHCI Host Controller
Mar  9 14:52:23 tux kernel: [    1.085454] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Mar  9 14:52:23 tux kernel: [    1.085834] ehci-pci 0000:00:1d.0: debug port 2
Mar  9 14:52:23 tux kernel: [    1.090099] ehci-pci 0000:00:1d.0: irq 23, io mem 0xdbd3b000
Mar  9 14:52:23 tux kernel: [    1.096986] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Mar  9 14:52:23 tux kernel: [    1.097363] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Mar  9 14:52:23 tux kernel: [    1.097724] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar  9 14:52:23 tux kernel: [    1.098142] usb usb2: Product: EHCI Host Controller
Mar  9 14:52:23 tux kernel: [    1.098502] usb usb2: Manufacturer: Linux 4.9.6-gentoo-r1 ehci_hcd
Mar  9 14:52:23 tux kernel: [    1.098901] usb usb2: SerialNumber: 0000:00:1d.0
Mar  9 14:52:23 tux kernel: [    1.099417] hub 2-0:1.0: USB hub found
Mar  9 14:52:23 tux kernel: [    1.099820] hub 2-0:1.0: 2 ports detected
Mar  9 14:52:23 tux kernel: [    1.100276] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Mar  9 14:52:23 tux kernel: [    1.100693] ohci-pci: OHCI PCI platform driver
Mar  9 14:52:23 tux kernel: [    1.101115] uhci_hcd: USB Universal Host Controller Interface driver
Mar  9 14:52:23 tux kernel: [    1.101626] xhci_hcd 0000:00:14.0: xHCI Host Controller
Mar  9 14:52:23 tux kernel: [    1.102161] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
Mar  9 14:52:23 tux kernel: [    1.103648] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x00009810
Mar  9 14:52:23 tux kernel: [    1.104140] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
Mar  9 14:52:23 tux kernel: [    1.104531] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar  9 14:52:23 tux kernel: [    1.104920] usb usb3: Product: xHCI Host Controller
Mar  9 14:52:23 tux kernel: [    1.105336] usb usb3: Manufacturer: Linux 4.9.6-gentoo-r1 xhci-hcd
Mar  9 14:52:23 tux kernel: [    1.105716] usb usb3: SerialNumber: 0000:00:14.0
Mar  9 14:52:23 tux kernel: [    1.106249] hub 3-0:1.0: USB hub found
Mar  9 14:52:23 tux kernel: [    1.106664] hub 3-0:1.0: 14 ports detected
Mar  9 14:52:23 tux kernel: [    1.108468] xhci_hcd 0000:00:14.0: xHCI Host Controller
Mar  9 14:52:23 tux kernel: [    1.108864] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
Mar  9 14:52:23 tux kernel: [    1.109326] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
Mar  9 14:52:23 tux kernel: [    1.109696] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar  9 14:52:23 tux kernel: [    1.110087] usb usb4: Product: xHCI Host Controller
Mar  9 14:52:23 tux kernel: [    1.110441] usb usb4: Manufacturer: Linux 4.9.6-gentoo-r1 xhci-hcd
Mar  9 14:52:23 tux kernel: [    1.110801] usb usb4: SerialNumber: 0000:00:14.0
Mar  9 14:52:23 tux kernel: [    1.111252] hub 4-0:1.0: USB hub found
Mar  9 14:52:23 tux kernel: [    1.111649] hub 4-0:1.0: 6 ports detected
Mar  9 14:52:23 tux kernel: [    1.112658] usbcore: registered new interface driver usb-storage
Mar  9 14:52:23 tux kernel: [    1.113100] i8042: PNP: No PS/2 controller found. Probing ports directly.
Mar  9 14:52:23 tux kernel: [    1.113885] serio: i8042 KBD port at 0x60,0x64 irq 1
Mar  9 14:52:23 tux kernel: [    1.114297] serio: i8042 AUX port at 0x60,0x64 irq 12
Mar  9 14:52:23 tux kernel: [    1.114713] mousedev: PS/2 mouse device common for all mice
Mar  9 14:52:23 tux kernel: [    1.115340] rtc_cmos 00:02: RTC can wake from S4
Mar  9 14:52:23 tux kernel: [    1.115850] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Mar  9 14:52:23 tux kernel: [    1.116266] rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Back to top
View user's profile Send private message
GentooForEver
n00b
n00b


Joined: 09 Mar 2017
Posts: 5

PostPosted: Thu Mar 09, 2017 3:58 pm    Post subject: Sorry, post was apparently to long. Preview was ok though. Reply with quote

Here the link to the boot messages:

http://pastebin.com/Wjjc9Ncr

fstab:

Code:
/dev/sdf2      /boot      ext2      defaults   0 2
/dev/sdf3      none      swap      sw      0 0
/dev/sdf4      /      ext4      noatime      0 1


At this time I have no clue, what the problem is. Any help is appreciated. Thanks.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43198
Location: 56N 3W

PostPosted: Thu Mar 09, 2017 6:40 pm    Post subject: Reply with quote

GentooForEver,

Welcome to Gentoo.

Your boot messages look normal until the shutting down for a reboot.
Did that just happen or did you do something?
If you want a wild guess, your kernel is missing CONFIG_BINFMT_SCRIPT=y, so it can't run the init script.

Please post the output of lspci and put your kernel .config file onte a pastebin site.
wgetpaste can help there.

In general, its not a good idea to use kernel device names like /dev/sdf4 when you have several HDD and several distros.
The problem being that the names are not fixed, the are allocated in device discovery order, which can vary from kernel to kernel.

Make friends with blkid.
Code:
 $ /sbin/blkid           
/dev/sda1: UUID="9392926d-6408-6e7a-8663-82834138a597" TYPE="linux_raid_member" PARTUUID="0553caf4-01"
/dev/sda2: UUID="b6633d8e-41ef-4485-9bbe-c4c2d69f4e8c" TYPE="swap" PARTUUID="0553caf4-02"
/dev/sda5: UUID="5e3cadd4-cfd2-665d-9690-1ac76d8f5a5d" TYPE="linux_raid_member" PARTUUID="0553caf4-05"
/dev/sda6: UUID="9657e667-5b60-f6a3-0391-65e6dcf662fa" TYPE="linux_raid_member" PARTUUID="0553caf4-06"


On the kernel command line, use root=PARTUUID=Your_sdf4_PARTUUID. Google will tell you the syntax.
In /etc/fstab, use either the filesystem UUID or the PARTUUID.
/etc/fstab:
UUID=cf559dbe-81bb-45b7-bbdd-0bcdc81e066b               /               ext4            noatime,discard         0 1

The kernel understands PARTUUID without any help for root= but for UUID, you need an initrd as the nser space mount command is required.

PARTUUID and UUID are err ... unique. It just works even if your sdf is detected as sda.
This is not a Gentoo thing, its a hardware and kernel thing, so its Linux wide.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
GentooForEver
n00b
n00b


Joined: 09 Mar 2017
Posts: 5

PostPosted: Thu Mar 09, 2017 10:10 pm    Post subject: Reply with quote

Thank you, NeddySeagoon, for the quick response.

Quote:
Your boot messages look normal until the shutting down for a reboot.
Did that just happen or did you do something?
If you want a wild guess, your kernel is missing CONFIG_BINFMT_SCRIPT=y, so it can't run the init script.


Reboot was initiated by me. After nothing was happening on the screen I typed ctrl-alt delete.
I checked, it is like this: CONFIG_BINFMT_SCRIPT=y

Quote:
In general, its not a good idea to use kernel device names like /dev/sdf4

I changed that to UUID. But nothing changed.

Quote:
On the kernel command line, use root=PARTUUID=Your_sdf4_PARTUUID.

I changed that too. But now the reboot with ctrl-alt delete does not work anymore and there were no new /var/log/messages at all. But the screen output halted at the same time as before. At 0.7s.

The screen output freezes at about 0.7s every time. But according to the /var/log/messages (prior to the command line change) the boot process goes on to about 5.6s.

I'v read on an other post when I use the kernel commandline I need a initramfs. Is that correct?

lspci output:
Code:
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4)
00:1c.6 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 10)
05:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41)
06:01.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)


kernel config:

http://pastebin.com/LEB8XXq8

Thanks for you help.
Back to top
View user's profile Send private message
GentooForEver
n00b
n00b


Joined: 09 Mar 2017
Posts: 5

PostPosted: Thu Mar 09, 2017 11:03 pm    Post subject: Reply with quote

I just realized that I made a mistake, when I changed the kernel command line. I pointed the PARTUUID to the sdf2.
I changed that to the sdf4. At now the boot process behaves like before. The screen freezes at 0.7s. But /var/log/messages go on until 5 to 10 seconds. ctrl-alt delete works again.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43198
Location: 56N 3W

PostPosted: Fri Mar 10, 2017 9:28 am    Post subject: Reply with quote

GentooForEver,

You need an initrd if the kernel cannot mount the root filesystem without using some user space tools, like mount.
The initrd is a root filesystem in a file. It provides a temporary root filesystem that is used to mount the real root file system.
From your original
/var/log/messages:
Mar  9 14:52:23 tux kernel: [    2.214438] EXT4-fs (sdf4): mounted filesystem with ordered data mode. Opts: (null)
Mar  9 14:52:23 tux kernel: [    2.215003] VFS: Mounted root (ext4 filesystem) readonly on device 8:84.
we see that root is mounted, so that you do not need an initrd.
That's why you use PARTUUID in the kernel command line and not UUID.

dmesg:
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 10)
That's your Hard drive controllers and we know the kernel is right there as root mounts.

You lose screen messages but the boot contines ... maybe it all works but you just can't see it on the console. Lets check out your video cards.
dmesg:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)

Ahh, you have two.

/var/log/messages:
Mar  9 14:52:23 tux kernel: [    0.775541] [drm] Initialized
Mar  9 14:52:23 tux kernel: [    0.775770] i915 0000:00:02.0: enabling device (0006 -> 0007)
Mar  9 14:52:23 tux kernel: [    0.776063] [drm] Memory usable by graphics device = 2048M
Mar  9 14:52:23 tux kernel: [    0.776236] [drm] Replacing VGA console driver
Mar  9 14:52:23 tux kernel: [    0.778751] Console: switching to colour dummy device 80x25
...
Mar  9 14:52:23 tux kernel: [    0.808507] [drm] Cannot find any crtc or sizes - going 1024x768
Mar  9 14:52:23 tux kernel: [    0.809709] Console: switching to colour frame buffer device 128x48
Mar  9 14:52:23 tux kernel: [    0.810653] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device


Here's what's happening. For the first half a second, the kernel draws boot messages on both display adaptors.
At 0.810653 its using the built in graphics only. You didn't buy a GeForce GTX 760 to not use it, so your display is connected there, not to the Intel built in graphics.
After that switch you don't see anything on the console as the kernel is driving one display while you watch another.

There will be a BIOS setting to disable the on board graphics.
The BIOS may let you choose a graphics card as boot or primary, Choosing the GTX 760 as boot/primary will put the boot messages on the GTX 760 and allow you to use the Intel card as a secondary in Xory later, if you wish.

There is another complication. If you intend to use nvidia-drivers with Xorg, the nvidia kernel module will spit out dire warnings about framebuffer consoles in use.
If it works, ignore it.
Your CONFIG_FB_EFI=y should be safe, as long as you use EFI mode to boot. If not, try CONFIG_FB_VESA.

Next steps.
Connect the display to the built in graphics card. It will probably work.
Go into the BIOS and set the GTX 760 as the primary graphics card. Move the display back to the GTX 760. That might work too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
GentooForEver
n00b
n00b


Joined: 09 Mar 2017
Posts: 5

PostPosted: Fri Mar 10, 2017 10:48 am    Post subject: NeddySeagoon, you solved the problem, thank you. Reply with quote

As you correctly analyzed the problem was, the two video cards installed in my computer. The i915, which is build into Central Processing Unit (CPU), and the Nvidia GTX 760 on the pci slot.

Solution:
As you proposed, I just went into the BIOS/UEFI and disabled the i915. I saved the BIOS/UEFI configuration and rebooted. The screen didn't freeze anymore. I was able to login into the root account as described in the Gentoo handbook.

I have struggled for about a week to solve this problem and I have tried several times in years long passed to install gentoo. And now, finally, there is a login prompt on my screen. I still can't believe it! Now, I'm able to progress to the next chapter of the handbook: "Finalizing". And some day, may be, I'll manage to install a graphical user interface. :lol:

You made my day, week, month, year. THANK YOU!

I would have never been able to solve that problem on my own! Thank you! You are GREAT! :D
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43198
Location: 56N 3W

PostPosted: Fri Mar 10, 2017 10:59 am    Post subject: Reply with quote

GentooForEver,

Compared to your first boot, installing the GUI is easy.
You get error messages to work with, you can ssh in when the display is black and poke about.
It might not work first time but diagnostics are simpler.

There are wiki pages for Xorg and all the common window managers.
Install Xorg and test it.
Add the Window manager of your choice.

The testing of Xorg is important. It that works and your WM doesn't, the problem is your WM.
If you don't do the test, problems can be in Xorg or the WM.

Everywhere in Gentoo, build on what you know works. Then when, not if, you break it, you can back out the changes.
That's why the first boot is hard. There is nothing to build on.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ShyPixie
n00b
n00b


Joined: 20 Nov 2015
Posts: 19
Location: Brazil

PostPosted: Fri Mar 10, 2017 1:22 pm    Post subject: Re: Kernel stops booting Reply with quote

GentooForEver wrote:
I'm new to gentoo and I'm inexperienced with the command line.


Awesome!

For someone who does not have command line experience, I think it should be a challenge to use Gentoo.

Congratulations!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum