* Can anyone boot a system using btrfs root with linux 3.14 or newer?
@ 2014-04-23 17:30 Пламен Петров
2014-04-23 18:33 ` Swâmi Petaramesh
` (3 more replies)
0 siblings, 4 replies; 39+ messages in thread
From: Пламен Петров @ 2014-04-23 17:30 UTC (permalink / raw)
To: linux-btrfs
Can anyone boot a system using btrfs root with linux 3.14 or newer?
Because I can't.
I'm trying to move some 3.13.x based systems to 3.14.x and the kernel panics
during boot. It says to append a correct root=sdaX partition, but the one
provided is correct, because if use 3.13.x with the same kernel command line
- the system boots fine.
The thing is - there is an ext2 /boot partition and root / is btrfs, like
so:
# cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump>
<pass>
#/dev/#REISERFS_ROOT# / reiserfs defaults 0 0
#/dev/#EXT3FS_ROOT# / ext3 defaults 0 1
/dev/sda2 / btrfs relatime,compress=zlib 0 0
/dev/sda1 /boot ext4 defaults 0 1
#/dev/#JFS_ROOT# / jfs defaults 1 1
Here is my relevant GRUB config file part:
#menuentry 0
title Linux
root (hd0,0)
kernel /vmlinuz rw root=/dev/sda2 vga=6 raid=noautodetect
And for the record - I used the same kernel config as the one from 3.13.x -
I just copied my old .config file over to linux 3.14.x sources and did a
"make olddefconfig" and compiled my kernel, just as I did with all previous
ones...
Ideas?
P.S. Please, CC me - I'm not subscribed.
---------------------------------
Plamen Petrov
^ permalink raw reply [flat|nested] 39+ messages in thread* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 17:30 Can anyone boot a system using btrfs root with linux 3.14 or newer? Пламен Петров @ 2014-04-23 18:33 ` Swâmi Petaramesh 2014-04-23 18:54 ` Marc MERLIN ` (2 subsequent siblings) 3 siblings, 0 replies; 39+ messages in thread From: Swâmi Petaramesh @ 2014-04-23 18:33 UTC (permalink / raw) To: Пламен Петров Cc: linux-btrfs Le mercredi 23 avril 2014 20:30:08 Пламен Петров a écrit : > Can anyone boot a system using btrfs root with linux 3.14 or newer? Yes I do. $ grep /boot /proc/mounts /dev/sda8 /boot btrfs rw,noatime,compress=lzo,space_cache,autodefrag 0 0 /dev/sda1 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount- ro 0 0 $ uname -r 3.14.1-1-ARCH -- Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 17:30 Can anyone boot a system using btrfs root with linux 3.14 or newer? Пламен Петров 2014-04-23 18:33 ` Swâmi Petaramesh @ 2014-04-23 18:54 ` Marc MERLIN 2014-04-23 19:02 ` Hugo Mills 2014-04-23 19:06 ` Пламен Петров 2014-04-23 19:06 ` Kai Krakow 2014-04-24 3:23 ` Chris Murphy 3 siblings, 2 replies; 39+ messages in thread From: Marc MERLIN @ 2014-04-23 18:54 UTC (permalink / raw) To: Пламен Петров Cc: linux-btrfs On Wed, Apr 23, 2014 at 08:30:08PM +0300, Пламен Петров wrote: > Can anyone boot a system using btrfs root with linux 3.14 or newer? > > Because I can't. It works fine for me. > I'm trying to move some 3.13.x based systems to 3.14.x and the kernel panics > during boot. It says to append a correct root=sdaX partition, but the one > provided is correct, because if use 3.13.x with the same kernel command line > - the system boots fine. My guess is that you have btrfs compiled as a module, it then needs to be in an initrd, and you either haven't built it and put it in the right place, or grub isn't setup to load that initrd. > #menuentry 0 > title Linux > root (hd0,0) > kernel /vmlinuz rw root=/dev/sda2 vga=6 raid=noautodetect That's missing an initrd. Are you absolutely certain then that btrfs is compiled in the kernel and not as a module? Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 18:54 ` Marc MERLIN @ 2014-04-23 19:02 ` Hugo Mills 2014-04-23 19:06 ` Пламен Петров 1 sibling, 0 replies; 39+ messages in thread From: Hugo Mills @ 2014-04-23 19:02 UTC (permalink / raw) To: Marc MERLIN Cc: Пламен Петров, linux-btrfs [-- Attachment #1: Type: text/plain, Size: 1486 bytes --] On Wed, Apr 23, 2014 at 11:54:13AM -0700, Marc MERLIN wrote: > On Wed, Apr 23, 2014 at 08:30:08PM +0300, Пламен Петров wrote: > > Can anyone boot a system using btrfs root with linux 3.14 or newer? > > > > Because I can't. > > It works fine for me. > > > I'm trying to move some 3.13.x based systems to 3.14.x and the kernel panics > > during boot. It says to append a correct root=sdaX partition, but the one > > provided is correct, because if use 3.13.x with the same kernel command line > > - the system boots fine. > > My guess is that you have btrfs compiled as a module, it then needs to be in > an initrd, and you either haven't built it and put it in the right place, or > grub isn't setup to load that initrd. > > > #menuentry 0 > > title Linux > > root (hd0,0) > > kernel /vmlinuz rw root=/dev/sda2 vga=6 raid=noautodetect > > That's missing an initrd. Are you absolutely certain then that btrfs is > compiled in the kernel and not as a module? And the other thing to check here is that if this is a multi-device filesystem, you need to have your initrd run "btrfs dev scan" before trying to mount. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- The glass is neither half-full nor half-empty; it is twice as --- large as it needs to be. [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 811 bytes --] ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 18:54 ` Marc MERLIN 2014-04-23 19:02 ` Hugo Mills @ 2014-04-23 19:06 ` Пламен Петров 2014-04-23 19:15 ` Marc MERLIN 1 sibling, 1 reply; 39+ messages in thread From: Пламен Петров @ 2014-04-23 19:06 UTC (permalink / raw) To: 'Marc MERLIN'; +Cc: linux-btrfs [-- Attachment #1: Type: text/plain, Size: 2274 bytes --] > -----Original Message----- > From: Marc MERLIN [mailto:marc@merlins.org] > Sent: Wednesday, April 23, 2014 9:54 PM > To: Пламен Петров > Cc: linux-btrfs@vger.kernel.org > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > On Wed, Apr 23, 2014 at 08:30:08PM +0300, Пламен Петров wrote: > > Can anyone boot a system using btrfs root with linux 3.14 or newer? > > > > Because I can't. > > It works fine for me. > > > I'm trying to move some 3.13.x based systems to 3.14.x and the kernel > > panics during boot. It says to append a correct root=sdaX partition, > > but the one provided is correct, because if use 3.13.x with the same > > kernel command line > > - the system boots fine. > > My guess is that you have btrfs compiled as a module, it then needs to be in > an initrd, and you either haven't built it and put it in the right place, or grub > isn't setup to load that initrd. > > > #menuentry 0 > > title Linux > > root (hd0,0) > > kernel /vmlinuz rw root=/dev/sda2 vga=6 raid=noautodetect > > That's missing an initrd. Are you absolutely certain then that btrfs is compiled > in the kernel and not as a module? > > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet cooking Home page: > http://marc.merlins.org/ Just to clarify - I am using a monolithic kernel built from source, and it has all the stuff it needs to support built-in, and then some. And no modules. The sources I'm using are the vanilla kernels from Linus and Greg KH downloaded from kernel.org. Check out the attached config I am using - it’s a kernel I'm running on one server and a couple of virtual machines. Until now - copying said config and doing a "make oldconfig" or "make olddefconfig" and compiling-then-booting worked fine. Can it be that for 3.14 it matters which btrfs version/kernel/tools the filesystem was mkfs'd with play a role here? Because if that's it - my filesystem should be very old - now more than a year, come to think about it... --------------------------------- Plamen Petrov [-- Attachment #2: config-v3.13.11-mix64.txt --] [-- Type: text/plain, Size: 77829 bytes --] # # Automatically generated file; DO NOT EDIT. # Linux/x86 3.13.11 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_ARCH_HAS_CPU_AUTOPROBE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_ARCH_WANT_GENERAL_HUGETLB=y CONFIG_ZONE_DMA32=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_X86_64_SMP=y CONFIG_X86_HT=y CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y # # General setup # CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" # CONFIG_COMPILE_TEST is not set CONFIG_LOCALVERSION="-mix64" CONFIG_LOCALVERSION_AUTO=y CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_HAVE_KERNEL_LZ4=y # CONFIG_KERNEL_GZIP is not set # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set CONFIG_KERNEL_XZ=y # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y # CONFIG_FHANDLE is not set # CONFIG_AUDIT is not set # # IRQ subsystem # CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_ARCH_CLOCKSOURCE_DATA=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set CONFIG_NO_HZ_IDLE=y # CONFIG_NO_HZ_FULL is not set CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # # CPU/Task time and stats accounting # CONFIG_TICK_CPU_ACCOUNTING=y # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set # CONFIG_IRQ_TIME_ACCOUNTING is not set CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y # CONFIG_TASKSTATS is not set # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_PREEMPT_RCU is not set CONFIG_RCU_STALL_COMMON=y # CONFIG_RCU_USER_QS is not set CONFIG_RCU_FANOUT=32 CONFIG_RCU_FANOUT_LEAF=16 # CONFIG_RCU_FANOUT_EXACT is not set # CONFIG_RCU_FAST_NO_HZ is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_RCU_NOCB_CPU is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=21 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y CONFIG_ARCH_SUPPORTS_INT128=y CONFIG_ARCH_WANTS_PROT_NUMA_PROT_NONE=y CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set CONFIG_CGROUP_FREEZER=y # CONFIG_CGROUP_DEVICE is not set CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y CONFIG_CGROUP_CPUACCT=y CONFIG_RESOURCE_COUNTERS=y # CONFIG_MEMCG is not set # CONFIG_CGROUP_HUGETLB is not set # CONFIG_CGROUP_PERF is not set CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y # CONFIG_CFS_BANDWIDTH is not set # CONFIG_RT_GROUP_SCHED is not set # CONFIG_BLK_CGROUP is not set # CONFIG_CHECKPOINT_RESTORE is not set CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y # CONFIG_USER_NS is not set CONFIG_PID_NS=y CONFIG_NET_NS=y # CONFIG_UIDGID_STRICT_TYPE_CHECKS is not set # CONFIG_SCHED_AUTOGROUP is not set # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_HAVE_UID16=y CONFIG_SYSCTL_EXCEPTION_TRACE=y CONFIG_HAVE_PCSPKR_PLATFORM=y # CONFIG_EXPERT is not set CONFIG_UID16=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_PCI_QUIRKS=y # CONFIG_EMBEDDED is not set CONFIG_HAVE_PERF_EVENTS=y # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y # CONFIG_DEBUG_PERF_USE_VMALLOC is not set CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set CONFIG_SLUB=y CONFIG_SLUB_CPU_PARTIAL=y # CONFIG_PROFILING is not set CONFIG_HAVE_OPROFILE=y CONFIG_OPROFILE_NMI_TIMER=y # CONFIG_JUMP_LABEL is not set # CONFIG_HAVE_64BIT_ALIGNED_ACCESS is not set CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_ARCH_USE_BUILTIN_BSWAP=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_OPTPROBES=y CONFIG_HAVE_KPROBES_ON_FTRACE=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y CONFIG_GENERIC_SMP_IDLE_THREAD=y CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y CONFIG_HAVE_DMA_API_DEBUG=y CONFIG_HAVE_HW_BREAKPOINT=y CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y CONFIG_HAVE_USER_RETURN_NOTIFIER=y CONFIG_HAVE_PERF_EVENTS_NMI=y CONFIG_HAVE_PERF_REGS=y CONFIG_HAVE_PERF_USER_STACK_DUMP=y CONFIG_HAVE_ARCH_JUMP_LABEL=y CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y CONFIG_HAVE_ALIGNED_STRUCT_PAGE=y CONFIG_HAVE_CMPXCHG_LOCAL=y CONFIG_HAVE_CMPXCHG_DOUBLE=y CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y CONFIG_HAVE_ARCH_SECCOMP_FILTER=y CONFIG_SECCOMP_FILTER=y CONFIG_HAVE_CONTEXT_TRACKING=y CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_HAVE_ARCH_SOFT_DIRTY=y CONFIG_MODULES_USE_ELF_RELA=y CONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK=y CONFIG_OLD_SIGSUSPEND3=y CONFIG_COMPAT_OLD_SIGACTION=y # # GCOV-based kernel profiling # # CONFIG_GCOV_KERNEL is not set # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 # CONFIG_SYSTEM_TRUSTED_KEYRING is not set # CONFIG_MODULES is not set CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y CONFIG_BLK_DEV_BSG=y # CONFIG_BLK_DEV_BSGLIB is not set CONFIG_BLK_DEV_INTEGRITY=y # CONFIG_BLK_CMDLINE_PARSER is not set # # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y CONFIG_EFI_PARTITION=y CONFIG_BLOCK_COMPAT=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y # CONFIG_IOSCHED_CFQ is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_NOOP=y CONFIG_DEFAULT_IOSCHED="noop" CONFIG_UNINLINE_SPIN_UNLOCK=y CONFIG_INLINE_SPIN_UNLOCK_IRQ=y CONFIG_INLINE_READ_UNLOCK=y CONFIG_INLINE_READ_UNLOCK_IRQ=y CONFIG_INLINE_WRITE_UNLOCK=y CONFIG_INLINE_WRITE_UNLOCK_IRQ=y CONFIG_MUTEX_SPIN_ON_OWNER=y CONFIG_FREEZER=y # # Processor type and features # CONFIG_ZONE_DMA=y CONFIG_SMP=y CONFIG_X86_MPPARSE=y # CONFIG_X86_EXTENDED_PLATFORM is not set # CONFIG_X86_INTEL_LPSS is not set CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_HYPERVISOR_GUEST=y CONFIG_PARAVIRT=y # CONFIG_PARAVIRT_DEBUG is not set CONFIG_PARAVIRT_SPINLOCKS=y CONFIG_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=500 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_KVM_GUEST=y # CONFIG_KVM_DEBUG_FS is not set # CONFIG_PARAVIRT_TIME_ACCOUNTING is not set CONFIG_PARAVIRT_CLOCK=y CONFIG_NO_BOOTMEM=y # CONFIG_MEMTEST is not set # CONFIG_MK8 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_MATOM is not set CONFIG_GENERIC_CPU=y CONFIG_X86_INTERNODE_CACHE_SHIFT=6 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_TSC=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_DEBUGCTLMSR=y CONFIG_CPU_SUP_INTEL=y CONFIG_CPU_SUP_AMD=y CONFIG_CPU_SUP_CENTAUR=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_DMI=y CONFIG_GART_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_IOMMU_HELPER=y # CONFIG_MAXSMP is not set CONFIG_NR_CPUS=8 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y # CONFIG_X86_MCE_AMD is not set CONFIG_X86_MCE_THRESHOLD=y # CONFIG_X86_MCE_INJECT is not set CONFIG_X86_THERMAL_VECTOR=y # CONFIG_I8K is not set CONFIG_MICROCODE=y CONFIG_MICROCODE_INTEL=y CONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_MICROCODE_INTEL_LIB=y # CONFIG_MICROCODE_INTEL_EARLY is not set # CONFIG_MICROCODE_AMD_EARLY is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_ARCH_DMA_ADDR_T_64BIT=y CONFIG_DIRECT_GBPAGES=y # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_SELECT_MEMORY_MODEL=y CONFIG_SPARSEMEM_MANUAL=y CONFIG_SPARSEMEM=y CONFIG_HAVE_MEMORY_PRESENT=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y CONFIG_SPARSEMEM_VMEMMAP=y CONFIG_HAVE_MEMBLOCK=y CONFIG_HAVE_MEMBLOCK_NODE_MAP=y CONFIG_ARCH_DISCARD_MEMBLOCK=y CONFIG_MEMORY_ISOLATION=y # CONFIG_HAVE_BOOTMEM_INFO_NODE is not set # CONFIG_MEMORY_HOTPLUG is not set CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y # CONFIG_COMPACTION is not set CONFIG_MIGRATION=y CONFIG_PHYS_ADDR_T_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_MMU_NOTIFIER=y CONFIG_KSM=y CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y # CONFIG_MEMORY_FAILURE is not set # CONFIG_TRANSPARENT_HUGEPAGE is not set CONFIG_CROSS_MEMORY_ATTACH=y CONFIG_CLEANCACHE=y # CONFIG_FRONTSWAP is not set CONFIG_CMA=y # CONFIG_CMA_DEBUG is not set # CONFIG_ZBUD is not set # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set CONFIG_X86_RESERVE_LOW=64 CONFIG_MTRR=y CONFIG_MTRR_SANITIZER=y CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0 CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 CONFIG_X86_PAT=y CONFIG_ARCH_USES_PG_UNCACHED=y CONFIG_ARCH_RANDOM=y CONFIG_X86_SMAP=y # CONFIG_EFI is not set CONFIG_SECCOMP=y # CONFIG_CC_STACKPROTECTOR is not set CONFIG_HZ_100=y # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set CONFIG_HZ=100 CONFIG_SCHED_HRTICK=y # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x1000000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_HOTPLUG_CPU=y # CONFIG_BOOTPARAM_HOTPLUG_CPU0 is not set # CONFIG_DEBUG_HOTPLUG_CPU0 is not set # CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y # # Power management and ACPI options # # CONFIG_SUSPEND is not set CONFIG_HIBERNATE_CALLBACKS=y # CONFIG_HIBERNATION is not set CONFIG_PM_SLEEP=y CONFIG_PM_SLEEP_SMP=y # CONFIG_PM_AUTOSLEEP is not set # CONFIG_PM_WAKELOCKS is not set # CONFIG_PM_RUNTIME is not set CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set CONFIG_ACPI=y CONFIG_ACPI_PROCFS=y # CONFIG_ACPI_EC_DEBUGFS is not set CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=y CONFIG_ACPI_FAN=y CONFIG_ACPI_DOCK=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_HOTPLUG_CPU=y # CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_CUSTOM_DSDT is not set # CONFIG_ACPI_DEBUG is not set # CONFIG_ACPI_PCI_SLOT is not set CONFIG_X86_PM_TIMER=y CONFIG_ACPI_CONTAINER=y # CONFIG_ACPI_SBS is not set # CONFIG_ACPI_HED is not set # CONFIG_ACPI_CUSTOM_METHOD is not set # CONFIG_ACPI_APEI is not set # CONFIG_ACPI_EXTLOG is not set # CONFIG_SFI is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_COMMON=y # CONFIG_CPU_FREQ_STAT is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_GOV_POWERSAVE is not set CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set # # x86 CPU frequency scaling drivers # CONFIG_X86_INTEL_PSTATE=y # CONFIG_X86_PCC_CPUFREQ is not set CONFIG_X86_ACPI_CPUFREQ=y CONFIG_X86_ACPI_CPUFREQ_CPB=y # CONFIG_X86_POWERNOW_K8 is not set # CONFIG_X86_AMD_FREQ_SENSITIVITY is not set # CONFIG_X86_SPEEDSTEP_CENTRINO is not set # CONFIG_X86_P4_CLOCKMOD is not set # # shared options # # CONFIG_X86_SPEEDSTEP_LIB is not set # # CPU Idle # CONFIG_CPU_IDLE=y # CONFIG_CPU_IDLE_MULTIPLE_DRIVERS is not set CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set CONFIG_INTEL_IDLE=y # # Memory power savings # # CONFIG_I7300_IDLE is not set # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_XEN=y CONFIG_PCI_DOMAINS=y CONFIG_PCIEPORTBUS=y CONFIG_PCIEAER=y # CONFIG_PCIE_ECRC is not set # CONFIG_PCIEAER_INJECT is not set CONFIG_PCIEASPM=y # CONFIG_PCIEASPM_DEBUG is not set CONFIG_PCIEASPM_DEFAULT=y # CONFIG_PCIEASPM_POWERSAVE is not set # CONFIG_PCIEASPM_PERFORMANCE is not set CONFIG_PCI_MSI=y # CONFIG_PCI_DEBUG is not set # CONFIG_PCI_REALLOC_ENABLE_AUTO is not set # CONFIG_PCI_STUB is not set CONFIG_XEN_PCIDEV_FRONTEND=y CONFIG_HT_IRQ=y # CONFIG_PCI_IOV is not set # CONFIG_PCI_PRI is not set # CONFIG_PCI_PASID is not set CONFIG_PCI_IOAPIC=y CONFIG_PCI_LABEL=y # # PCI host controller drivers # CONFIG_ISA_DMA_API=y CONFIG_AMD_NB=y # CONFIG_PCCARD is not set # CONFIG_HOTPLUG_PCI is not set # CONFIG_RAPIDIO is not set CONFIG_X86_SYSFB=y # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_COMPAT_BINFMT_ELF=y CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y CONFIG_BINFMT_SCRIPT=y # CONFIG_HAVE_AOUT is not set CONFIG_BINFMT_MISC=y CONFIG_COREDUMP=y CONFIG_IA32_EMULATION=y CONFIG_IA32_AOUT=y CONFIG_X86_X32=y CONFIG_COMPAT=y CONFIG_COMPAT_FOR_U64_ALIGNMENT=y CONFIG_SYSVIPC_COMPAT=y CONFIG_KEYS_COMPAT=y CONFIG_X86_DEV_DMA_OPS=y CONFIG_NET=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_DIAG=y CONFIG_UNIX=y # CONFIG_UNIX_DIAG is not set CONFIG_XFRM=y CONFIG_XFRM_ALGO=y CONFIG_XFRM_USER=y # CONFIG_XFRM_SUB_POLICY is not set # CONFIG_XFRM_MIGRATE is not set # CONFIG_XFRM_STATISTICS is not set # CONFIG_NET_KEY is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y # CONFIG_IP_FIB_TRIE_STATS is not set CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_MULTIPATH=y CONFIG_IP_ROUTE_VERBOSE=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y CONFIG_IP_PNP_BOOTP=y CONFIG_IP_PNP_RARP=y # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE_DEMUX is not set # CONFIG_NET_IP_TUNNEL is not set CONFIG_IP_MROUTE=y # CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set CONFIG_IP_PIMSM_V1=y CONFIG_IP_PIMSM_V2=y CONFIG_SYN_COOKIES=y # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_XFRM_TUNNEL is not set # CONFIG_INET_TUNNEL is not set # CONFIG_INET_XFRM_MODE_TRANSPORT is not set # CONFIG_INET_XFRM_MODE_TUNNEL is not set # CONFIG_INET_XFRM_MODE_BEET is not set CONFIG_INET_LRO=y # CONFIG_INET_DIAG is not set CONFIG_TCP_CONG_ADVANCED=y # CONFIG_TCP_CONG_BIC is not set CONFIG_TCP_CONG_CUBIC=y # CONFIG_TCP_CONG_WESTWOOD is not set # CONFIG_TCP_CONG_HTCP is not set # CONFIG_TCP_CONG_HSTCP is not set # CONFIG_TCP_CONG_HYBLA is not set CONFIG_TCP_CONG_VEGAS=y # CONFIG_TCP_CONG_SCALABLE is not set # CONFIG_TCP_CONG_LP is not set CONFIG_TCP_CONG_VENO=y CONFIG_TCP_CONG_YEAH=y # CONFIG_TCP_CONG_ILLINOIS is not set # CONFIG_DEFAULT_CUBIC is not set # CONFIG_DEFAULT_VEGAS is not set # CONFIG_DEFAULT_VENO is not set CONFIG_DEFAULT_RENO=y CONFIG_DEFAULT_TCP_CONG="reno" CONFIG_TCP_MD5SIG=y # CONFIG_IPV6 is not set CONFIG_NETLABEL=y CONFIG_NETWORK_SECMARK=y # CONFIG_NETWORK_PHY_TIMESTAMPING is not set CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set # CONFIG_NETFILTER_ADVANCED is not set # # Core Netfilter Configuration # CONFIG_NETFILTER_NETLINK=y CONFIG_NETFILTER_NETLINK_LOG=y CONFIG_NF_CONNTRACK=y CONFIG_NF_CONNTRACK_SECMARK=y CONFIG_NF_CONNTRACK_PROCFS=y CONFIG_NF_CONNTRACK_FTP=y CONFIG_NF_CONNTRACK_IRC=y # CONFIG_NF_CONNTRACK_NETBIOS_NS is not set CONFIG_NF_CONNTRACK_SIP=y CONFIG_NF_CT_NETLINK=y CONFIG_NF_NAT=y CONFIG_NF_NAT_NEEDED=y # CONFIG_NF_NAT_AMANDA is not set CONFIG_NF_NAT_FTP=y CONFIG_NF_NAT_IRC=y CONFIG_NF_NAT_SIP=y # CONFIG_NF_NAT_TFTP is not set # CONFIG_NF_TABLES is not set CONFIG_NETFILTER_XTABLES=y # # Xtables combined modules # # CONFIG_NETFILTER_XT_MARK is not set # # Xtables targets # CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=y CONFIG_NETFILTER_XT_TARGET_LOG=y CONFIG_NETFILTER_XT_TARGET_NETMAP=y CONFIG_NETFILTER_XT_TARGET_NFLOG=y CONFIG_NETFILTER_XT_TARGET_REDIRECT=y CONFIG_NETFILTER_XT_TARGET_SECMARK=y CONFIG_NETFILTER_XT_TARGET_TCPMSS=y # # Xtables matches # CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y CONFIG_NETFILTER_XT_MATCH_POLICY=y CONFIG_NETFILTER_XT_MATCH_STATE=y # CONFIG_IP_SET is not set # CONFIG_IP_VS is not set # # IP: Netfilter Configuration # CONFIG_NF_DEFRAG_IPV4=y CONFIG_NF_CONNTRACK_IPV4=y CONFIG_NF_CONNTRACK_PROC_COMPAT=y CONFIG_IP_NF_IPTABLES=y CONFIG_IP_NF_FILTER=y CONFIG_IP_NF_TARGET_REJECT=y CONFIG_IP_NF_TARGET_ULOG=y CONFIG_NF_NAT_IPV4=y CONFIG_IP_NF_TARGET_MASQUERADE=y # CONFIG_NF_NAT_PPTP is not set # CONFIG_NF_NAT_H323 is not set CONFIG_IP_NF_MANGLE=y # CONFIG_IP_NF_RAW is not set # CONFIG_IP_DCCP is not set # CONFIG_IP_SCTP is not set # CONFIG_RDS is not set # CONFIG_TIPC is not set # CONFIG_ATM is not set # CONFIG_L2TP is not set # CONFIG_BRIDGE is not set CONFIG_HAVE_NET_DSA=y # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_PHONET is not set # CONFIG_IEEE802154 is not set CONFIG_NET_SCHED=y # # Queueing/Scheduling # # CONFIG_NET_SCH_CBQ is not set # CONFIG_NET_SCH_HTB is not set # CONFIG_NET_SCH_HFSC is not set # CONFIG_NET_SCH_PRIO is not set # CONFIG_NET_SCH_MULTIQ is not set # CONFIG_NET_SCH_RED is not set # CONFIG_NET_SCH_SFB is not set # CONFIG_NET_SCH_SFQ is not set # CONFIG_NET_SCH_TEQL is not set # CONFIG_NET_SCH_TBF is not set # CONFIG_NET_SCH_GRED is not set # CONFIG_NET_SCH_DSMARK is not set # CONFIG_NET_SCH_NETEM is not set CONFIG_NET_SCH_DRR=y # CONFIG_NET_SCH_MQPRIO is not set CONFIG_NET_SCH_CHOKE=y CONFIG_NET_SCH_QFQ=y CONFIG_NET_SCH_CODEL=y CONFIG_NET_SCH_FQ_CODEL=y CONFIG_NET_SCH_FQ=y # CONFIG_NET_SCH_PLUG is not set # # Classification # # CONFIG_NET_CLS_BASIC is not set # CONFIG_NET_CLS_TCINDEX is not set # CONFIG_NET_CLS_ROUTE4 is not set # CONFIG_NET_CLS_FW is not set # CONFIG_NET_CLS_U32 is not set # CONFIG_NET_CLS_RSVP is not set # CONFIG_NET_CLS_RSVP6 is not set # CONFIG_NET_CLS_FLOW is not set # CONFIG_NET_CLS_CGROUP is not set # CONFIG_NET_CLS_BPF is not set # CONFIG_NET_EMATCH is not set # CONFIG_NET_CLS_ACT is not set CONFIG_NET_SCH_FIFO=y # CONFIG_DCB is not set CONFIG_DNS_RESOLVER=y # CONFIG_BATMAN_ADV is not set # CONFIG_OPENVSWITCH is not set # CONFIG_VSOCKETS is not set CONFIG_NETLINK_MMAP=y CONFIG_NETLINK_DIAG=y # CONFIG_NET_MPLS_GSO is not set # CONFIG_HSR is not set CONFIG_RPS=y CONFIG_RFS_ACCEL=y CONFIG_XPS=y # CONFIG_NETPRIO_CGROUP is not set CONFIG_NET_RX_BUSY_POLL=y CONFIG_BQL=y CONFIG_NET_FLOW_LIMIT=y # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_CAN is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # CONFIG_AF_RXRPC is not set CONFIG_FIB_RULES=y # CONFIG_WIRELESS is not set # CONFIG_WIMAX is not set # CONFIG_RFKILL is not set # CONFIG_NET_9P is not set # CONFIG_CAIF is not set # CONFIG_CEPH_LIB is not set # CONFIG_NFC is not set CONFIG_HAVE_BPF_JIT=y # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" CONFIG_FW_LOADER_USER_HELPER=y # CONFIG_DEBUG_DRIVER is not set CONFIG_DEBUG_DEVRES=y CONFIG_SYS_HYPERVISOR=y # CONFIG_GENERIC_CPU_DEVICES is not set CONFIG_DMA_SHARED_BUFFER=y # # Bus devices # CONFIG_CONNECTOR=y CONFIG_PROC_EVENTS=y # CONFIG_MTD is not set # CONFIG_PARPORT is not set CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y CONFIG_PNP=y # CONFIG_PNP_DEBUG_MESSAGES is not set # # Protocols # CONFIG_PNPACPI=y CONFIG_BLK_DEV=y # CONFIG_BLK_DEV_NULL_BLK is not set # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set CONFIG_BLK_CPQ_CISS_DA=y # CONFIG_CISS_SCSI_TAPE is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_LOOP_MIN_COUNT=8 # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_DRBD is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_NVME is not set # CONFIG_BLK_DEV_SKD is not set # CONFIG_BLK_DEV_SX8 is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=16384 # CONFIG_BLK_DEV_XIP is not set # CONFIG_CDROM_PKTCDVD is not set # CONFIG_ATA_OVER_ETH is not set CONFIG_XEN_BLKDEV_FRONTEND=y # CONFIG_XEN_BLKDEV_BACKEND is not set # CONFIG_BLK_DEV_HD is not set # CONFIG_BLK_DEV_RBD is not set # CONFIG_BLK_DEV_RSXX is not set # # Misc devices # # CONFIG_SENSORS_LIS3LV02D is not set # CONFIG_AD525X_DPOT is not set # CONFIG_DUMMY_IRQ is not set # CONFIG_IBM_ASM is not set # CONFIG_PHANTOM is not set # CONFIG_SGI_IOC4 is not set # CONFIG_TIFM_CORE is not set # CONFIG_ICS932S401 is not set # CONFIG_ATMEL_SSC is not set # CONFIG_ENCLOSURE_SERVICES is not set # CONFIG_HP_ILO is not set # CONFIG_APDS9802ALS is not set # CONFIG_ISL29003 is not set # CONFIG_ISL29020 is not set # CONFIG_SENSORS_TSL2550 is not set # CONFIG_SENSORS_BH1780 is not set # CONFIG_SENSORS_BH1770 is not set # CONFIG_SENSORS_APDS990X is not set # CONFIG_HMC6352 is not set # CONFIG_DS1682 is not set CONFIG_VMWARE_BALLOON=y # CONFIG_BMP085_I2C is not set # CONFIG_PCH_PHUB is not set # CONFIG_USB_SWITCH_FSA9480 is not set # CONFIG_SRAM is not set # CONFIG_C2PORT is not set # # EEPROM support # # CONFIG_EEPROM_AT24 is not set # CONFIG_EEPROM_LEGACY is not set # CONFIG_EEPROM_MAX6875 is not set # CONFIG_EEPROM_93CX6 is not set # CONFIG_CB710_CORE is not set # # Texas Instruments shared transport line discipline # # CONFIG_SENSORS_LIS3_I2C is not set # # Altera FPGA firmware download module # # CONFIG_ALTERA_STAPL is not set CONFIG_VMWARE_VMCI=y # # Intel MIC Host Driver # # CONFIG_INTEL_MIC_HOST is not set # # Intel MIC Card Driver # # CONFIG_INTEL_MIC_CARD is not set CONFIG_HAVE_IDE=y # CONFIG_IDE is not set # # SCSI device support # CONFIG_SCSI_MOD=y CONFIG_RAID_ATTRS=y CONFIG_SCSI=y CONFIG_SCSI_DMA=y # CONFIG_SCSI_TGT is not set CONFIG_SCSI_NETLINK=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_CHR_DEV_SG=y # CONFIG_CHR_DEV_SCH is not set # CONFIG_SCSI_MULTI_LUN is not set CONFIG_SCSI_CONSTANTS=y # CONFIG_SCSI_LOGGING is not set # CONFIG_SCSI_SCAN_ASYNC is not set # # SCSI Transports # CONFIG_SCSI_SPI_ATTRS=y CONFIG_SCSI_FC_ATTRS=y # CONFIG_SCSI_ISCSI_ATTRS is not set CONFIG_SCSI_SAS_ATTRS=y # CONFIG_SCSI_SAS_LIBSAS is not set # CONFIG_SCSI_SRP_ATTRS is not set CONFIG_SCSI_LOWLEVEL=y # CONFIG_ISCSI_TCP is not set # CONFIG_ISCSI_BOOT_SYSFS is not set # CONFIG_SCSI_CXGB3_ISCSI is not set # CONFIG_SCSI_CXGB4_ISCSI is not set # CONFIG_SCSI_BNX2_ISCSI is not set # CONFIG_SCSI_BNX2X_FCOE is not set # CONFIG_BE2ISCSI is not set # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_HPSA is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_3W_SAS is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_SCSI_AIC7XXX is not set # CONFIG_SCSI_AIC7XXX_OLD is not set # CONFIG_SCSI_AIC79XX is not set # CONFIG_SCSI_AIC94XX is not set # CONFIG_SCSI_MVSAS is not set # CONFIG_SCSI_MVUMI is not set # CONFIG_SCSI_DPT_I2O is not set # CONFIG_SCSI_ADVANSYS is not set # CONFIG_SCSI_ARCMSR is not set # CONFIG_SCSI_ESAS2R is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set # CONFIG_MEGARAID_SAS is not set CONFIG_SCSI_MPT2SAS=y CONFIG_SCSI_MPT2SAS_MAX_SGE=128 # CONFIG_SCSI_MPT2SAS_LOGGING is not set # CONFIG_SCSI_MPT3SAS is not set # CONFIG_SCSI_UFSHCD is not set # CONFIG_SCSI_HPTIOP is not set CONFIG_SCSI_BUSLOGIC=y # CONFIG_SCSI_FLASHPOINT is not set CONFIG_VMWARE_PVSCSI=y # CONFIG_LIBFC is not set # CONFIG_LIBFCOE is not set # CONFIG_FCOE is not set # CONFIG_FCOE_FNIC is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_ISCI is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_STEX is not set # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_QLOGIC_1280 is not set # CONFIG_SCSI_QLA_FC is not set # CONFIG_SCSI_QLA_ISCSI is not set # CONFIG_SCSI_LPFC is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_DEBUG is not set # CONFIG_SCSI_PMCRAID is not set # CONFIG_SCSI_PM8001 is not set # CONFIG_SCSI_SRP is not set # CONFIG_SCSI_BFA_FC is not set # CONFIG_SCSI_CHELSIO_FCOE is not set # CONFIG_SCSI_DH is not set # CONFIG_SCSI_OSD_INITIATOR is not set CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_VERBOSE_ERROR=y CONFIG_ATA_ACPI=y # CONFIG_SATA_ZPODD is not set CONFIG_SATA_PMP=y # # Controllers with non-SFF native interface # CONFIG_SATA_AHCI=y # CONFIG_SATA_AHCI_PLATFORM is not set # CONFIG_SATA_INIC162X is not set # CONFIG_SATA_ACARD_AHCI is not set # CONFIG_SATA_SIL24 is not set CONFIG_ATA_SFF=y # # SFF controllers with custom DMA interface # # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_SX4 is not set CONFIG_ATA_BMDMA=y # # SATA SFF controllers with BMDMA # CONFIG_ATA_PIIX=y # CONFIG_SATA_HIGHBANK is not set # CONFIG_SATA_MV is not set CONFIG_SATA_NV=y # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_RCAR is not set # CONFIG_SATA_SIL is not set # CONFIG_SATA_SIS is not set # CONFIG_SATA_SVW is not set # CONFIG_SATA_ULI is not set # CONFIG_SATA_VIA is not set # CONFIG_SATA_VITESSE is not set # # PATA SFF controllers with BMDMA # # CONFIG_PATA_ALI is not set CONFIG_PATA_AMD=y # CONFIG_PATA_ARTOP is not set # CONFIG_PATA_ATIIXP is not set # CONFIG_PATA_ATP867X is not set # CONFIG_PATA_CMD64X is not set # CONFIG_PATA_CS5520 is not set # CONFIG_PATA_CS5530 is not set # CONFIG_PATA_CS5536 is not set # CONFIG_PATA_CYPRESS is not set # CONFIG_PATA_EFAR is not set # CONFIG_PATA_HPT366 is not set # CONFIG_PATA_HPT37X is not set # CONFIG_PATA_HPT3X2N is not set # CONFIG_PATA_HPT3X3 is not set # CONFIG_PATA_IT8213 is not set # CONFIG_PATA_IT821X is not set # CONFIG_PATA_JMICRON is not set # CONFIG_PATA_MARVELL is not set # CONFIG_PATA_NETCELL is not set # CONFIG_PATA_NINJA32 is not set # CONFIG_PATA_NS87415 is not set CONFIG_PATA_OLDPIIX=y # CONFIG_PATA_OPTIDMA is not set # CONFIG_PATA_PDC2027X is not set # CONFIG_PATA_PDC_OLD is not set # CONFIG_PATA_RADISYS is not set # CONFIG_PATA_RDC is not set # CONFIG_PATA_SC1200 is not set CONFIG_PATA_SCH=y # CONFIG_PATA_SERVERWORKS is not set # CONFIG_PATA_SIL680 is not set # CONFIG_PATA_SIS is not set # CONFIG_PATA_TOSHIBA is not set # CONFIG_PATA_TRIFLEX is not set # CONFIG_PATA_VIA is not set # CONFIG_PATA_WINBOND is not set # # PIO-only SFF controllers # # CONFIG_PATA_CMD640_PCI is not set CONFIG_PATA_MPIIX=y # CONFIG_PATA_NS87410 is not set # CONFIG_PATA_OPTI is not set # CONFIG_PATA_RZ1000 is not set # # Generic fallback / legacy drivers # # CONFIG_PATA_ACPI is not set CONFIG_ATA_GENERIC=y # CONFIG_PATA_LEGACY is not set CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_AUTODETECT=y CONFIG_MD_LINEAR=y CONFIG_MD_RAID0=y CONFIG_MD_RAID1=y CONFIG_MD_RAID10=y CONFIG_MD_RAID456=y # CONFIG_MD_MULTIPATH is not set # CONFIG_MD_FAULTY is not set # CONFIG_BCACHE is not set CONFIG_BLK_DEV_DM_BUILTIN=y CONFIG_BLK_DEV_DM=y # CONFIG_DM_DEBUG is not set # CONFIG_DM_CRYPT is not set CONFIG_DM_SNAPSHOT=y # CONFIG_DM_THIN_PROVISIONING is not set # CONFIG_DM_CACHE is not set CONFIG_DM_MIRROR=y # CONFIG_DM_LOG_USERSPACE is not set CONFIG_DM_RAID=y # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # CONFIG_DM_DELAY is not set # CONFIG_DM_UEVENT is not set # CONFIG_DM_FLAKEY is not set # CONFIG_DM_VERITY is not set # CONFIG_DM_SWITCH is not set # CONFIG_TARGET_CORE is not set CONFIG_FUSION=y CONFIG_FUSION_SPI=y CONFIG_FUSION_FC=y CONFIG_FUSION_SAS=y CONFIG_FUSION_MAX_SGE=128 # CONFIG_FUSION_CTL is not set # CONFIG_FUSION_LOGGING is not set # # IEEE 1394 (FireWire) support # # CONFIG_FIREWIRE is not set # CONFIG_FIREWIRE_NOSY is not set # CONFIG_I2O is not set # CONFIG_MACINTOSH_DRIVERS is not set CONFIG_NETDEVICES=y CONFIG_MII=y CONFIG_NET_CORE=y CONFIG_BONDING=y # CONFIG_DUMMY is not set # CONFIG_EQUALIZER is not set # CONFIG_NET_FC is not set # CONFIG_NET_TEAM is not set # CONFIG_MACVLAN is not set # CONFIG_VXLAN is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # CONFIG_TUN is not set # CONFIG_VETH is not set # CONFIG_NLMON is not set # CONFIG_ARCNET is not set # # CAIF transport drivers # # # Distributed Switch Architecture drivers # # CONFIG_NET_DSA_MV88E6XXX is not set # CONFIG_NET_DSA_MV88E6060 is not set # CONFIG_NET_DSA_MV88E6XXX_NEED_PPU is not set # CONFIG_NET_DSA_MV88E6131 is not set # CONFIG_NET_DSA_MV88E6123_61_65 is not set CONFIG_ETHERNET=y # CONFIG_NET_VENDOR_3COM is not set # CONFIG_NET_VENDOR_ADAPTEC is not set # CONFIG_NET_VENDOR_ALTEON is not set CONFIG_NET_VENDOR_AMD=y CONFIG_AMD8111_ETH=y CONFIG_PCNET32=y CONFIG_NET_VENDOR_ARC=y # CONFIG_NET_VENDOR_ATHEROS is not set # CONFIG_NET_CADENCE is not set CONFIG_NET_VENDOR_BROADCOM=y # CONFIG_B44 is not set # CONFIG_BNX2 is not set # CONFIG_CNIC is not set CONFIG_TIGON3=y # CONFIG_BNX2X is not set # CONFIG_NET_VENDOR_BROCADE is not set # CONFIG_NET_CALXEDA_XGMAC is not set # CONFIG_NET_VENDOR_CHELSIO is not set # CONFIG_NET_VENDOR_CISCO is not set # CONFIG_DNET is not set # CONFIG_NET_VENDOR_DEC is not set # CONFIG_NET_VENDOR_DLINK is not set # CONFIG_NET_VENDOR_EMULEX is not set # CONFIG_NET_VENDOR_EXAR is not set # CONFIG_NET_VENDOR_HP is not set CONFIG_NET_VENDOR_INTEL=y # CONFIG_E100 is not set CONFIG_E1000=y CONFIG_E1000E=y CONFIG_IGB=y CONFIG_IGB_HWMON=y # CONFIG_IGBVF is not set # CONFIG_IXGB is not set # CONFIG_IXGBE is not set # CONFIG_IXGBEVF is not set # CONFIG_I40E is not set CONFIG_NET_VENDOR_I825XX=y # CONFIG_IP1000 is not set # CONFIG_JME is not set # CONFIG_NET_VENDOR_MARVELL is not set # CONFIG_NET_VENDOR_MELLANOX is not set # CONFIG_NET_VENDOR_MICREL is not set # CONFIG_NET_VENDOR_MYRI is not set # CONFIG_FEALNX is not set # CONFIG_NET_VENDOR_NATSEMI is not set # CONFIG_NET_VENDOR_NVIDIA is not set # CONFIG_NET_VENDOR_OKI is not set # CONFIG_ETHOC is not set # CONFIG_NET_PACKET_ENGINE is not set # CONFIG_NET_VENDOR_QLOGIC is not set CONFIG_NET_VENDOR_REALTEK=y CONFIG_8139CP=y CONFIG_8139TOO=y # CONFIG_8139TOO_PIO is not set # CONFIG_8139TOO_TUNE_TWISTER is not set # CONFIG_8139TOO_8129 is not set # CONFIG_8139_OLD_RX_RESET is not set CONFIG_R8169=y # CONFIG_SH_ETH is not set # CONFIG_NET_VENDOR_RDC is not set # CONFIG_NET_VENDOR_SEEQ is not set # CONFIG_NET_VENDOR_SILAN is not set # CONFIG_NET_VENDOR_SIS is not set # CONFIG_SFC is not set # CONFIG_NET_VENDOR_SMSC is not set # CONFIG_NET_VENDOR_STMICRO is not set # CONFIG_NET_VENDOR_SUN is not set # CONFIG_NET_VENDOR_TEHUTI is not set # CONFIG_NET_VENDOR_TI is not set # CONFIG_NET_VENDOR_VIA is not set # CONFIG_NET_VENDOR_WIZNET is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_NET_SB1000 is not set CONFIG_PHYLIB=y # # MII PHY device drivers # # CONFIG_AT803X_PHY is not set CONFIG_AMD_PHY=y # CONFIG_MARVELL_PHY is not set # CONFIG_DAVICOM_PHY is not set # CONFIG_QSEMI_PHY is not set CONFIG_LXT_PHY=y # CONFIG_CICADA_PHY is not set # CONFIG_VITESSE_PHY is not set # CONFIG_SMSC_PHY is not set CONFIG_BROADCOM_PHY=y CONFIG_BCM87XX_PHY=y # CONFIG_ICPLUS_PHY is not set CONFIG_REALTEK_PHY=y # CONFIG_NATIONAL_PHY is not set # CONFIG_STE10XP is not set # CONFIG_LSI_ET1011C_PHY is not set # CONFIG_MICREL_PHY is not set # CONFIG_FIXED_PHY is not set # CONFIG_MDIO_BITBANG is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # # USB Network Adapters # # CONFIG_USB_CATC is not set # CONFIG_USB_KAWETH is not set # CONFIG_USB_PEGASUS is not set # CONFIG_USB_RTL8150 is not set # CONFIG_USB_RTL8152 is not set # CONFIG_USB_USBNET is not set # CONFIG_USB_IPHETH is not set # CONFIG_WLAN is not set # # Enable WiMAX (Networking options) to see the WiMAX drivers # # CONFIG_WAN is not set CONFIG_XEN_NETDEV_FRONTEND=y # CONFIG_XEN_NETDEV_BACKEND is not set CONFIG_VMXNET3=y # CONFIG_ISDN is not set # # Input device support # CONFIG_INPUT=y CONFIG_INPUT_FF_MEMLESS=y CONFIG_INPUT_POLLDEV=y CONFIG_INPUT_SPARSEKMAP=y # CONFIG_INPUT_MATRIXKMAP is not set # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y # CONFIG_INPUT_MOUSEDEV_PSAUX is not set CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y # CONFIG_KEYBOARD_ADP5588 is not set # CONFIG_KEYBOARD_ADP5589 is not set CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_QT1070 is not set # CONFIG_KEYBOARD_QT2160 is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_TCA6416 is not set # CONFIG_KEYBOARD_TCA8418 is not set # CONFIG_KEYBOARD_LM8333 is not set # CONFIG_KEYBOARD_MAX7359 is not set # CONFIG_KEYBOARD_MCS is not set # CONFIG_KEYBOARD_MPR121 is not set # CONFIG_KEYBOARD_NEWTON is not set # CONFIG_KEYBOARD_OPENCORES is not set # CONFIG_KEYBOARD_STOWAWAY is not set # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_XTKBD is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_CYPRESS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y # CONFIG_MOUSE_PS2_ELANTECH is not set # CONFIG_MOUSE_PS2_SENTELIC is not set # CONFIG_MOUSE_PS2_TOUCHKIT is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_APPLETOUCH is not set # CONFIG_MOUSE_BCM5974 is not set # CONFIG_MOUSE_CYAPA is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_MOUSE_SYNAPTICS_I2C is not set # CONFIG_MOUSE_SYNAPTICS_USB is not set CONFIG_INPUT_JOYSTICK=y # CONFIG_JOYSTICK_ANALOG is not set # CONFIG_JOYSTICK_A3D is not set # CONFIG_JOYSTICK_ADI is not set # CONFIG_JOYSTICK_COBRA is not set # CONFIG_JOYSTICK_GF2K is not set # CONFIG_JOYSTICK_GRIP is not set # CONFIG_JOYSTICK_GRIP_MP is not set # CONFIG_JOYSTICK_GUILLEMOT is not set # CONFIG_JOYSTICK_INTERACT is not set # CONFIG_JOYSTICK_SIDEWINDER is not set # CONFIG_JOYSTICK_TMDC is not set # CONFIG_JOYSTICK_IFORCE is not set # CONFIG_JOYSTICK_WARRIOR is not set # CONFIG_JOYSTICK_MAGELLAN is not set # CONFIG_JOYSTICK_SPACEORB is not set # CONFIG_JOYSTICK_SPACEBALL is not set # CONFIG_JOYSTICK_STINGER is not set # CONFIG_JOYSTICK_TWIDJOY is not set # CONFIG_JOYSTICK_ZHENHUA is not set # CONFIG_JOYSTICK_AS5011 is not set # CONFIG_JOYSTICK_JOYDUMP is not set # CONFIG_JOYSTICK_XPAD is not set CONFIG_INPUT_TABLET=y # CONFIG_TABLET_USB_ACECAD is not set # CONFIG_TABLET_USB_AIPTEK is not set # CONFIG_TABLET_USB_GTCO is not set # CONFIG_TABLET_USB_HANWANG is not set # CONFIG_TABLET_USB_KBTAB is not set # CONFIG_TABLET_USB_WACOM is not set CONFIG_INPUT_TOUCHSCREEN=y # CONFIG_TOUCHSCREEN_AD7879 is not set # CONFIG_TOUCHSCREEN_ATMEL_MXT is not set # CONFIG_TOUCHSCREEN_BU21013 is not set # CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set # CONFIG_TOUCHSCREEN_CYTTSP4_CORE is not set # CONFIG_TOUCHSCREEN_DYNAPRO is not set # CONFIG_TOUCHSCREEN_HAMPSHIRE is not set # CONFIG_TOUCHSCREEN_EETI is not set # CONFIG_TOUCHSCREEN_FUJITSU is not set # CONFIG_TOUCHSCREEN_ILI210X is not set # CONFIG_TOUCHSCREEN_GUNZE is not set # CONFIG_TOUCHSCREEN_ELO is not set # CONFIG_TOUCHSCREEN_WACOM_W8001 is not set # CONFIG_TOUCHSCREEN_WACOM_I2C is not set # CONFIG_TOUCHSCREEN_MAX11801 is not set # CONFIG_TOUCHSCREEN_MCS5000 is not set # CONFIG_TOUCHSCREEN_MMS114 is not set # CONFIG_TOUCHSCREEN_MTOUCH is not set # CONFIG_TOUCHSCREEN_INEXIO is not set # CONFIG_TOUCHSCREEN_MK712 is not set # CONFIG_TOUCHSCREEN_PENMOUNT is not set # CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set # CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set # CONFIG_TOUCHSCREEN_TOUCHWIN is not set # CONFIG_TOUCHSCREEN_PIXCIR is not set # CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set # CONFIG_TOUCHSCREEN_TOUCHIT213 is not set # CONFIG_TOUCHSCREEN_TSC_SERIO is not set # CONFIG_TOUCHSCREEN_TSC2007 is not set # CONFIG_TOUCHSCREEN_ST1232 is not set # CONFIG_TOUCHSCREEN_SUR40 is not set # CONFIG_TOUCHSCREEN_TPS6507X is not set CONFIG_INPUT_MISC=y # CONFIG_INPUT_AD714X is not set # CONFIG_INPUT_BMA150 is not set # CONFIG_INPUT_PCSPKR is not set # CONFIG_INPUT_MMA8450 is not set # CONFIG_INPUT_MPU3050 is not set # CONFIG_INPUT_ATLAS_BTNS is not set # CONFIG_INPUT_ATI_REMOTE2 is not set # CONFIG_INPUT_KEYSPAN_REMOTE is not set # CONFIG_INPUT_KXTJ9 is not set # CONFIG_INPUT_POWERMATE is not set # CONFIG_INPUT_YEALINK is not set # CONFIG_INPUT_CM109 is not set # CONFIG_INPUT_UINPUT is not set # CONFIG_INPUT_PCF8574 is not set # CONFIG_INPUT_ADXL34X is not set # CONFIG_INPUT_CMA3000 is not set CONFIG_INPUT_XEN_KBDDEV_FRONTEND=y # CONFIG_INPUT_IDEAPAD_SLIDEBAR is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_SERIO_ALTERA_PS2 is not set # CONFIG_SERIO_PS2MULT is not set # CONFIG_SERIO_ARC_PS2 is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_TTY=y CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_VT_CONSOLE_SLEEP=y CONFIG_HW_CONSOLE=y CONFIG_VT_HW_CONSOLE_BINDING=y CONFIG_UNIX98_PTYS=y # CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set # CONFIG_LEGACY_PTYS is not set CONFIG_SERIAL_NONSTANDARD=y # CONFIG_ROCKETPORT is not set # CONFIG_CYCLADES is not set # CONFIG_MOXA_INTELLIO is not set # CONFIG_MOXA_SMARTIO is not set # CONFIG_SYNCLINK is not set # CONFIG_SYNCLINKMP is not set # CONFIG_SYNCLINK_GT is not set # CONFIG_NOZOMI is not set # CONFIG_ISI is not set # CONFIG_N_HDLC is not set # CONFIG_N_GSM is not set # CONFIG_TRACE_SINK is not set CONFIG_DEVKMEM=y # # Serial drivers # # CONFIG_SERIAL_8250 is not set CONFIG_FIX_EARLYCON_MEM=y # # Non-8250 serial port support # # CONFIG_SERIAL_MFD_HSU is not set # CONFIG_SERIAL_JSM is not set # CONFIG_SERIAL_SCCNXP is not set # CONFIG_SERIAL_TIMBERDALE is not set # CONFIG_SERIAL_ALTERA_JTAGUART is not set # CONFIG_SERIAL_ALTERA_UART is not set # CONFIG_SERIAL_PCH_UART is not set # CONFIG_SERIAL_ARC is not set # CONFIG_SERIAL_RP2 is not set # CONFIG_SERIAL_FSL_LPUART is not set CONFIG_HVC_DRIVER=y CONFIG_HVC_IRQ=y CONFIG_HVC_XEN=y CONFIG_HVC_XEN_FRONTEND=y # CONFIG_IPMI_HANDLER is not set CONFIG_HW_RANDOM=y # CONFIG_HW_RANDOM_TIMERIOMEM is not set CONFIG_HW_RANDOM_INTEL=y CONFIG_HW_RANDOM_AMD=y CONFIG_HW_RANDOM_VIA=y CONFIG_NVRAM=y # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set CONFIG_HPET=y # CONFIG_HPET_MMAP is not set # CONFIG_HANGCHECK_TIMER is not set # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set CONFIG_DEVPORT=y CONFIG_I2C=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_COMPAT=y # CONFIG_I2C_CHARDEV is not set # CONFIG_I2C_MUX is not set CONFIG_I2C_HELPER_AUTO=y CONFIG_I2C_ALGOBIT=y # # I2C Hardware Bus support # # # PC SMBus host controller drivers # # CONFIG_I2C_ALI1535 is not set # CONFIG_I2C_ALI1563 is not set # CONFIG_I2C_ALI15X3 is not set # CONFIG_I2C_AMD756 is not set # CONFIG_I2C_AMD8111 is not set CONFIG_I2C_I801=y # CONFIG_I2C_ISCH is not set # CONFIG_I2C_ISMT is not set # CONFIG_I2C_PIIX4 is not set # CONFIG_I2C_NFORCE2 is not set # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set # CONFIG_I2C_SIS96X is not set # CONFIG_I2C_VIA is not set # CONFIG_I2C_VIAPRO is not set # # ACPI drivers # # CONFIG_I2C_SCMI is not set # # I2C system bus drivers (mostly embedded / system-on-chip) # # CONFIG_I2C_DESIGNWARE_PCI is not set # CONFIG_I2C_EG20T is not set # CONFIG_I2C_OCORES is not set # CONFIG_I2C_PCA_PLATFORM is not set # CONFIG_I2C_PXA_PCI is not set # CONFIG_I2C_SIMTEC is not set # CONFIG_I2C_XILINX is not set # # External I2C/SMBus adapter drivers # # CONFIG_I2C_DIOLAN_U2C is not set # CONFIG_I2C_PARPORT_LIGHT is not set # CONFIG_I2C_TAOS_EVM is not set # CONFIG_I2C_TINY_USB is not set # # Other I2C/SMBus bus drivers # # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_SPI is not set # CONFIG_HSI is not set # # PPS support # CONFIG_PPS=y # CONFIG_PPS_DEBUG is not set # # PPS clients support # # CONFIG_PPS_CLIENT_KTIMER is not set # CONFIG_PPS_CLIENT_LDISC is not set # CONFIG_PPS_CLIENT_GPIO is not set # # PPS generators support # # # PTP clock support # CONFIG_PTP_1588_CLOCK=y # # Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks. # # CONFIG_PTP_1588_CLOCK_PCH is not set CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y # CONFIG_GPIOLIB is not set # CONFIG_W1 is not set CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set # CONFIG_PDA_POWER is not set # CONFIG_TEST_POWER is not set # CONFIG_BATTERY_DS2780 is not set # CONFIG_BATTERY_DS2781 is not set # CONFIG_BATTERY_DS2782 is not set # CONFIG_BATTERY_SBS is not set # CONFIG_BATTERY_BQ27x00 is not set # CONFIG_BATTERY_MAX17040 is not set # CONFIG_BATTERY_MAX17042 is not set # CONFIG_CHARGER_MAX8903 is not set # CONFIG_CHARGER_LP8727 is not set # CONFIG_CHARGER_BQ2415X is not set # CONFIG_CHARGER_SMB347 is not set # CONFIG_POWER_RESET is not set # CONFIG_POWER_AVS is not set CONFIG_HWMON=y # CONFIG_HWMON_VID is not set # CONFIG_HWMON_DEBUG_CHIP is not set # # Native drivers # # CONFIG_SENSORS_ABITUGURU is not set # CONFIG_SENSORS_ABITUGURU3 is not set # CONFIG_SENSORS_AD7414 is not set # CONFIG_SENSORS_AD7418 is not set # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1029 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set # CONFIG_SENSORS_ADT7410 is not set # CONFIG_SENSORS_ADT7411 is not set # CONFIG_SENSORS_ADT7462 is not set # CONFIG_SENSORS_ADT7470 is not set # CONFIG_SENSORS_ADT7475 is not set # CONFIG_SENSORS_ASC7621 is not set # CONFIG_SENSORS_K8TEMP is not set # CONFIG_SENSORS_K10TEMP is not set # CONFIG_SENSORS_FAM15H_POWER is not set # CONFIG_SENSORS_ASB100 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS620 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_I5K_AMB is not set # CONFIG_SENSORS_F71805F is not set # CONFIG_SENSORS_F71882FG is not set # CONFIG_SENSORS_F75375S is not set # CONFIG_SENSORS_FSCHMD is not set # CONFIG_SENSORS_G760A is not set # CONFIG_SENSORS_G762 is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_HIH6130 is not set # CONFIG_SENSORS_HTU21 is not set # CONFIG_SENSORS_CORETEMP is not set # CONFIG_SENSORS_IT87 is not set # CONFIG_SENSORS_JC42 is not set # CONFIG_SENSORS_LINEAGE is not set # CONFIG_SENSORS_LM63 is not set # CONFIG_SENSORS_LM73 is not set # CONFIG_SENSORS_LM75 is not set # CONFIG_SENSORS_LM77 is not set # CONFIG_SENSORS_LM78 is not set # CONFIG_SENSORS_LM80 is not set # CONFIG_SENSORS_LM83 is not set # CONFIG_SENSORS_LM85 is not set # CONFIG_SENSORS_LM87 is not set # CONFIG_SENSORS_LM90 is not set # CONFIG_SENSORS_LM92 is not set # CONFIG_SENSORS_LM93 is not set # CONFIG_SENSORS_LTC4151 is not set # CONFIG_SENSORS_LTC4215 is not set # CONFIG_SENSORS_LTC4245 is not set # CONFIG_SENSORS_LTC4261 is not set # CONFIG_SENSORS_LM95234 is not set # CONFIG_SENSORS_LM95241 is not set # CONFIG_SENSORS_LM95245 is not set # CONFIG_SENSORS_MAX16065 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_MAX1668 is not set # CONFIG_SENSORS_MAX197 is not set # CONFIG_SENSORS_MAX6639 is not set # CONFIG_SENSORS_MAX6642 is not set # CONFIG_SENSORS_MAX6650 is not set # CONFIG_SENSORS_MAX6697 is not set # CONFIG_SENSORS_MCP3021 is not set # CONFIG_SENSORS_NCT6775 is not set # CONFIG_SENSORS_NTC_THERMISTOR is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_PC87427 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_PMBUS is not set # CONFIG_SENSORS_SHT21 is not set # CONFIG_SENSORS_SIS5595 is not set # CONFIG_SENSORS_SMM665 is not set # CONFIG_SENSORS_DME1737 is not set # CONFIG_SENSORS_EMC1403 is not set # CONFIG_SENSORS_EMC2103 is not set # CONFIG_SENSORS_EMC6W201 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47M192 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_SCH56XX_COMMON is not set # CONFIG_SENSORS_ADS1015 is not set # CONFIG_SENSORS_ADS7828 is not set # CONFIG_SENSORS_AMC6821 is not set # CONFIG_SENSORS_INA209 is not set # CONFIG_SENSORS_INA2XX is not set # CONFIG_SENSORS_THMC50 is not set # CONFIG_SENSORS_TMP102 is not set # CONFIG_SENSORS_TMP401 is not set # CONFIG_SENSORS_TMP421 is not set # CONFIG_SENSORS_VIA_CPUTEMP is not set # CONFIG_SENSORS_VIA686A is not set # CONFIG_SENSORS_VT1211 is not set # CONFIG_SENSORS_VT8231 is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83791D is not set # CONFIG_SENSORS_W83792D is not set # CONFIG_SENSORS_W83793 is not set # CONFIG_SENSORS_W83795 is not set # CONFIG_SENSORS_W83L785TS is not set # CONFIG_SENSORS_W83L786NG is not set # CONFIG_SENSORS_W83627HF is not set # CONFIG_SENSORS_W83627EHF is not set # CONFIG_SENSORS_APPLESMC is not set # # ACPI drivers # # CONFIG_SENSORS_ACPI_POWER is not set # CONFIG_SENSORS_ATK0110 is not set CONFIG_THERMAL=y CONFIG_THERMAL_HWMON=y CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y # CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set CONFIG_THERMAL_GOV_FAIR_SHARE=y CONFIG_THERMAL_GOV_STEP_WISE=y CONFIG_THERMAL_GOV_USER_SPACE=y # CONFIG_CPU_THERMAL is not set # CONFIG_THERMAL_EMULATION is not set # CONFIG_INTEL_POWERCLAMP is not set CONFIG_X86_PKG_TEMP_THERMAL=y # # Texas Instruments thermal drivers # # CONFIG_WATCHDOG is not set CONFIG_SSB_POSSIBLE=y # # Sonics Silicon Backplane # # CONFIG_SSB is not set CONFIG_BCMA_POSSIBLE=y # # Broadcom specific AMBA # # CONFIG_BCMA is not set # # Multifunction device drivers # # CONFIG_MFD_CORE is not set # CONFIG_MFD_CS5535 is not set # CONFIG_MFD_AS3711 is not set # CONFIG_PMIC_ADP5520 is not set # CONFIG_MFD_CROS_EC is not set # CONFIG_PMIC_DA903X is not set # CONFIG_MFD_DA9052_I2C is not set # CONFIG_MFD_DA9055 is not set # CONFIG_MFD_DA9063 is not set # CONFIG_MFD_MC13XXX_I2C is not set # CONFIG_HTC_PASIC3 is not set # CONFIG_LPC_ICH is not set # CONFIG_LPC_SCH is not set # CONFIG_MFD_JANZ_CMODIO is not set # CONFIG_MFD_KEMPLD is not set # CONFIG_MFD_88PM800 is not set # CONFIG_MFD_88PM805 is not set # CONFIG_MFD_88PM860X is not set # CONFIG_MFD_MAX77686 is not set # CONFIG_MFD_MAX77693 is not set # CONFIG_MFD_MAX8907 is not set # CONFIG_MFD_MAX8925 is not set # CONFIG_MFD_MAX8997 is not set # CONFIG_MFD_MAX8998 is not set # CONFIG_MFD_VIPERBOARD is not set # CONFIG_MFD_RETU is not set # CONFIG_MFD_PCF50633 is not set # CONFIG_MFD_RDC321X is not set # CONFIG_MFD_RTSX_PCI is not set # CONFIG_MFD_RC5T583 is not set # CONFIG_MFD_SEC_CORE is not set # CONFIG_MFD_SI476X_CORE is not set # CONFIG_MFD_SM501 is not set # CONFIG_MFD_SMSC is not set # CONFIG_ABX500_CORE is not set # CONFIG_MFD_STMPE is not set # CONFIG_MFD_SYSCON is not set # CONFIG_MFD_TI_AM335X_TSCADC is not set # CONFIG_MFD_LP8788 is not set # CONFIG_MFD_PALMAS is not set # CONFIG_TPS6105X is not set # CONFIG_TPS6507X is not set # CONFIG_MFD_TPS65090 is not set # CONFIG_MFD_TPS65217 is not set # CONFIG_MFD_TPS6586X is not set # CONFIG_MFD_TPS80031 is not set # CONFIG_TWL4030_CORE is not set # CONFIG_TWL6040_CORE is not set # CONFIG_MFD_WL1273_CORE is not set # CONFIG_MFD_LM3533 is not set # CONFIG_MFD_TC3589X is not set # CONFIG_MFD_TMIO is not set # CONFIG_MFD_VX855 is not set # CONFIG_MFD_ARIZONA_I2C is not set # CONFIG_MFD_WM8400 is not set # CONFIG_MFD_WM831X_I2C is not set # CONFIG_MFD_WM8350_I2C is not set # CONFIG_MFD_WM8994 is not set # CONFIG_REGULATOR is not set # CONFIG_MEDIA_SUPPORT is not set # # Graphics support # CONFIG_AGP=y CONFIG_AGP_AMD64=y CONFIG_AGP_INTEL=y # CONFIG_AGP_SIS is not set # CONFIG_AGP_VIA is not set CONFIG_VGA_ARB=y CONFIG_VGA_ARB_MAX_GPUS=16 # CONFIG_VGA_SWITCHEROO is not set CONFIG_DRM=y CONFIG_DRM_KMS_HELPER=y CONFIG_DRM_KMS_FB_HELPER=y # CONFIG_DRM_LOAD_EDID_FIRMWARE is not set # # I2C encoder or helper chips # # CONFIG_DRM_I2C_CH7006 is not set # CONFIG_DRM_I2C_SIL164 is not set # CONFIG_DRM_I2C_NXP_TDA998X is not set # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set # CONFIG_DRM_RADEON is not set # CONFIG_DRM_NOUVEAU is not set # CONFIG_DRM_I810 is not set CONFIG_DRM_I915=y # CONFIG_DRM_I915_KMS is not set CONFIG_DRM_I915_FBDEV=y # CONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT is not set # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_DRM_VIA is not set # CONFIG_DRM_SAVAGE is not set # CONFIG_DRM_VMWGFX is not set # CONFIG_DRM_GMA500 is not set # CONFIG_DRM_UDL is not set # CONFIG_DRM_AST is not set # CONFIG_DRM_MGAG200 is not set # CONFIG_DRM_CIRRUS_QEMU is not set # CONFIG_DRM_QXL is not set # CONFIG_VGASTATE is not set CONFIG_VIDEO_OUTPUT_CONTROL=y CONFIG_HDMI=y CONFIG_FB=y # CONFIG_FIRMWARE_EDID is not set # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set CONFIG_FB_SYS_FILLRECT=y CONFIG_FB_SYS_COPYAREA=y CONFIG_FB_SYS_IMAGEBLIT=y # CONFIG_FB_FOREIGN_ENDIAN is not set CONFIG_FB_SYS_FOPS=y CONFIG_FB_DEFERRED_IO=y # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_UVESA is not set # CONFIG_FB_VESA is not set # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I740 is not set # CONFIG_FB_LE80578 is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_S3 is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_VIA is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_VT8623 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_ARK is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_CARMINE is not set # CONFIG_FB_SMSCUFX is not set # CONFIG_FB_UDL is not set # CONFIG_FB_GOLDFISH is not set # CONFIG_FB_VIRTUAL is not set CONFIG_XEN_FBDEV_FRONTEND=y # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set # CONFIG_FB_BROADSHEET is not set # CONFIG_FB_AUO_K190X is not set CONFIG_FB_SIMPLE=y # CONFIG_EXYNOS_VIDEO is not set CONFIG_BACKLIGHT_LCD_SUPPORT=y # CONFIG_LCD_CLASS_DEVICE is not set CONFIG_BACKLIGHT_CLASS_DEVICE=y CONFIG_BACKLIGHT_GENERIC=y # CONFIG_BACKLIGHT_APPLE is not set # CONFIG_BACKLIGHT_SAHARA is not set # CONFIG_BACKLIGHT_ADP8860 is not set # CONFIG_BACKLIGHT_ADP8870 is not set # CONFIG_BACKLIGHT_LM3630A is not set # CONFIG_BACKLIGHT_LM3639 is not set # CONFIG_BACKLIGHT_LP855X is not set # CONFIG_BACKLIGHT_LV5207LP is not set # CONFIG_BACKLIGHT_BD6107 is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_VGACON_SOFT_SCROLLBACK=y CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64 CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set CONFIG_LOGO=y # CONFIG_LOGO_LINUX_MONO is not set # CONFIG_LOGO_LINUX_VGA16 is not set CONFIG_LOGO_LINUX_CLUT224=y # CONFIG_SOUND is not set # # HID support # CONFIG_HID=y # CONFIG_HID_BATTERY_STRENGTH is not set # CONFIG_HIDRAW is not set # CONFIG_UHID is not set CONFIG_HID_GENERIC=y # # Special HID drivers # CONFIG_HID_A4TECH=y # CONFIG_HID_ACRUX is not set CONFIG_HID_APPLE=y # CONFIG_HID_APPLEIR is not set # CONFIG_HID_AUREAL is not set CONFIG_HID_BELKIN=y CONFIG_HID_CHERRY=y CONFIG_HID_CHICONY=y CONFIG_HID_CYPRESS=y # CONFIG_HID_DRAGONRISE is not set # CONFIG_HID_EMS_FF is not set # CONFIG_HID_ELECOM is not set # CONFIG_HID_ELO is not set CONFIG_HID_EZKEY=y # CONFIG_HID_HOLTEK is not set # CONFIG_HID_HUION is not set # CONFIG_HID_KEYTOUCH is not set # CONFIG_HID_KYE is not set # CONFIG_HID_UCLOGIC is not set # CONFIG_HID_WALTOP is not set # CONFIG_HID_GYRATION is not set # CONFIG_HID_ICADE is not set # CONFIG_HID_TWINHAN is not set CONFIG_HID_KENSINGTON=y # CONFIG_HID_LCPOWER is not set # CONFIG_HID_LENOVO_TPKBD is not set CONFIG_HID_LOGITECH=y # CONFIG_HID_LOGITECH_DJ is not set # CONFIG_LOGITECH_FF is not set # CONFIG_LOGIRUMBLEPAD2_FF is not set # CONFIG_LOGIG940_FF is not set # CONFIG_LOGIWHEELS_FF is not set # CONFIG_HID_MAGICMOUSE is not set CONFIG_HID_MICROSOFT=y CONFIG_HID_MONTEREY=y # CONFIG_HID_MULTITOUCH is not set # CONFIG_HID_NTRIG is not set # CONFIG_HID_ORTEK is not set # CONFIG_HID_PANTHERLORD is not set # CONFIG_HID_PETALYNX is not set # CONFIG_HID_PICOLCD is not set # CONFIG_HID_PRIMAX is not set # CONFIG_HID_ROCCAT is not set # CONFIG_HID_SAITEK is not set # CONFIG_HID_SAMSUNG is not set # CONFIG_HID_SPEEDLINK is not set # CONFIG_HID_STEELSERIES is not set # CONFIG_HID_SUNPLUS is not set # CONFIG_HID_GREENASIA is not set # CONFIG_HID_SMARTJOYPLUS is not set # CONFIG_HID_TIVO is not set # CONFIG_HID_TOPSEED is not set # CONFIG_HID_THRUSTMASTER is not set # CONFIG_HID_XINMO is not set # CONFIG_HID_ZEROPLUS is not set # CONFIG_HID_ZYDACRON is not set # CONFIG_HID_SENSOR_HUB is not set # # USB HID support # CONFIG_USB_HID=y # CONFIG_HID_PID is not set # CONFIG_USB_HIDDEV is not set # # I2C HID support # # CONFIG_I2C_HID is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_SUPPORT=y CONFIG_USB_COMMON=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB=y # CONFIG_USB_DEBUG is not set # CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set # # Miscellaneous USB options # CONFIG_USB_DEFAULT_PERSIST=y # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_MON is not set # CONFIG_USB_WUSB_CBAF is not set # # USB Host Controller Drivers # # CONFIG_USB_C67X00_HCD is not set # CONFIG_USB_XHCI_HCD is not set CONFIG_USB_EHCI_HCD=y # CONFIG_USB_EHCI_ROOT_HUB_TT is not set CONFIG_USB_EHCI_TT_NEWSCHED=y CONFIG_USB_EHCI_PCI=y # CONFIG_USB_EHCI_HCD_PLATFORM is not set # CONFIG_USB_OXU210HP_HCD is not set # CONFIG_USB_ISP116X_HCD is not set # CONFIG_USB_ISP1760_HCD is not set # CONFIG_USB_ISP1362_HCD is not set # CONFIG_USB_FUSBH200_HCD is not set # CONFIG_USB_FOTG210_HCD is not set CONFIG_USB_OHCI_HCD=y CONFIG_USB_OHCI_HCD_PCI=y # CONFIG_USB_OHCI_HCD_PLATFORM is not set CONFIG_USB_UHCI_HCD=y # CONFIG_USB_SL811_HCD is not set # CONFIG_USB_R8A66597_HCD is not set # CONFIG_USB_HCD_TEST_MODE is not set # # USB Device Class drivers # # CONFIG_USB_ACM is not set # CONFIG_USB_PRINTER is not set # CONFIG_USB_WDM is not set # CONFIG_USB_TMC is not set # # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may # # # also be needed; see USB_STORAGE Help for more info # # CONFIG_USB_STORAGE is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # CONFIG_USB_DWC3 is not set # CONFIG_USB_CHIPIDEA is not set # # USB port drivers # # CONFIG_USB_SERIAL is not set # # USB Miscellaneous drivers # # CONFIG_USB_EMI62 is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_ADUTUX is not set # CONFIG_USB_SEVSEG is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_LEGOTOWER is not set # CONFIG_USB_LCD is not set # CONFIG_USB_LED is not set # CONFIG_USB_CYPRESS_CY7C63 is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_IDMOUSE is not set # CONFIG_USB_FTDI_ELAN is not set # CONFIG_USB_APPLEDISPLAY is not set # CONFIG_USB_SISUSBVGA is not set # CONFIG_USB_LD is not set # CONFIG_USB_TRANCEVIBRATOR is not set # CONFIG_USB_IOWARRIOR is not set # CONFIG_USB_TEST is not set # CONFIG_USB_EHSET_TEST_FIXTURE is not set # CONFIG_USB_ISIGHTFW is not set # CONFIG_USB_YUREX is not set # CONFIG_USB_EZUSB_FX2 is not set # CONFIG_USB_HSIC_USB3503 is not set # # USB Physical Layer drivers # # CONFIG_USB_PHY is not set # CONFIG_NOP_USB_XCEIV is not set # CONFIG_SAMSUNG_USB2PHY is not set # CONFIG_SAMSUNG_USB3PHY is not set # CONFIG_USB_ISP1301 is not set # CONFIG_USB_RCAR_PHY is not set # CONFIG_USB_GADGET is not set # CONFIG_UWB is not set # CONFIG_MMC is not set # CONFIG_MEMSTICK is not set # CONFIG_NEW_LEDS is not set # CONFIG_ACCESSIBILITY is not set # CONFIG_INFINIBAND is not set CONFIG_EDAC=y CONFIG_EDAC_LEGACY_SYSFS=y # CONFIG_EDAC_DEBUG is not set # CONFIG_EDAC_MM_EDAC is not set CONFIG_RTC_LIB=y CONFIG_RTC_CLASS=y CONFIG_RTC_HCTOSYS=y CONFIG_RTC_SYSTOHC=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" # CONFIG_RTC_DEBUG is not set # # RTC interfaces # CONFIG_RTC_INTF_SYSFS=y CONFIG_RTC_INTF_PROC=y CONFIG_RTC_INTF_DEV=y # CONFIG_RTC_INTF_DEV_UIE_EMUL is not set # CONFIG_RTC_DRV_TEST is not set # # I2C RTC drivers # # CONFIG_RTC_DRV_DS1307 is not set # CONFIG_RTC_DRV_DS1374 is not set # CONFIG_RTC_DRV_DS1672 is not set # CONFIG_RTC_DRV_DS3232 is not set # CONFIG_RTC_DRV_MAX6900 is not set # CONFIG_RTC_DRV_RS5C372 is not set # CONFIG_RTC_DRV_ISL1208 is not set # CONFIG_RTC_DRV_ISL12022 is not set # CONFIG_RTC_DRV_X1205 is not set # CONFIG_RTC_DRV_PCF2127 is not set # CONFIG_RTC_DRV_PCF8523 is not set # CONFIG_RTC_DRV_PCF8563 is not set # CONFIG_RTC_DRV_PCF8583 is not set # CONFIG_RTC_DRV_M41T80 is not set # CONFIG_RTC_DRV_BQ32K is not set # CONFIG_RTC_DRV_S35390A is not set # CONFIG_RTC_DRV_FM3130 is not set # CONFIG_RTC_DRV_RX8581 is not set # CONFIG_RTC_DRV_RX8025 is not set # CONFIG_RTC_DRV_EM3027 is not set # CONFIG_RTC_DRV_RV3029C2 is not set # # SPI RTC drivers # # # Platform RTC drivers # CONFIG_RTC_DRV_CMOS=y # CONFIG_RTC_DRV_DS1286 is not set # CONFIG_RTC_DRV_DS1511 is not set # CONFIG_RTC_DRV_DS1553 is not set # CONFIG_RTC_DRV_DS1742 is not set # CONFIG_RTC_DRV_STK17TA8 is not set # CONFIG_RTC_DRV_M48T86 is not set # CONFIG_RTC_DRV_M48T35 is not set # CONFIG_RTC_DRV_M48T59 is not set # CONFIG_RTC_DRV_MSM6242 is not set # CONFIG_RTC_DRV_BQ4802 is not set # CONFIG_RTC_DRV_RP5C01 is not set # CONFIG_RTC_DRV_V3020 is not set # CONFIG_RTC_DRV_DS2404 is not set # # on-CPU RTC drivers # # CONFIG_RTC_DRV_MOXART is not set # # HID Sensor RTC drivers # # CONFIG_RTC_DRV_HID_SENSOR_TIME is not set # CONFIG_DMADEVICES is not set # CONFIG_AUXDISPLAY is not set # CONFIG_UIO is not set # CONFIG_VIRT_DRIVERS is not set # # Virtio drivers # # CONFIG_VIRTIO_PCI is not set # CONFIG_VIRTIO_MMIO is not set # # Microsoft Hyper-V guest support # # CONFIG_HYPERV is not set # # Xen driver support # CONFIG_XEN_BALLOON=y # CONFIG_XEN_SELFBALLOONING is not set CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=y CONFIG_XEN_GNTDEV=y CONFIG_XEN_GRANT_DEV_ALLOC=y CONFIG_SWIOTLB_XEN=y CONFIG_XEN_TMEM=y CONFIG_XEN_PCIDEV_BACKEND=y CONFIG_XEN_PRIVCMD=y CONFIG_XEN_ACPI_PROCESSOR=y # CONFIG_XEN_MCE_LOG is not set CONFIG_XEN_HAVE_PVMMU=y # CONFIG_STAGING is not set # CONFIG_X86_PLATFORM_DEVICES is not set # CONFIG_CHROME_PLATFORMS is not set # # Hardware Spinlock drivers # CONFIG_CLKEVT_I8253=y CONFIG_I8253_LOCK=y CONFIG_CLKBLD_I8253=y # CONFIG_MAILBOX is not set CONFIG_IOMMU_SUPPORT=y # CONFIG_AMD_IOMMU is not set # CONFIG_INTEL_IOMMU is not set # CONFIG_IRQ_REMAP is not set # # Remoteproc drivers # # CONFIG_STE_MODEM_RPROC is not set # # Rpmsg drivers # # CONFIG_PM_DEVFREQ is not set # CONFIG_EXTCON is not set # CONFIG_MEMORY is not set # CONFIG_IIO is not set # CONFIG_NTB is not set # CONFIG_VME_BUS is not set # CONFIG_PWM is not set # CONFIG_IPACK_BUS is not set # CONFIG_RESET_CONTROLLER is not set # CONFIG_FMC is not set # # PHY Subsystem # # CONFIG_GENERIC_PHY is not set # CONFIG_PHY_EXYNOS_MIPI_VIDEO is not set # CONFIG_POWERCAP is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_FIRMWARE_MEMMAP=y # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set CONFIG_DMIID=y # CONFIG_DMI_SYSFS is not set # CONFIG_ISCSI_IBFT_FIND is not set # CONFIG_GOOGLE_FIRMWARE is not set # # File systems # CONFIG_DCACHE_WORD_ACCESS=y # CONFIG_EXT2_FS is not set # CONFIG_EXT3_FS is not set CONFIG_EXT4_FS=y CONFIG_EXT4_USE_FOR_EXT23=y # CONFIG_EXT4_FS_POSIX_ACL is not set # CONFIG_EXT4_FS_SECURITY is not set # CONFIG_EXT4_DEBUG is not set CONFIG_JBD2=y # CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set CONFIG_XFS_FS=y # CONFIG_XFS_QUOTA is not set # CONFIG_XFS_POSIX_ACL is not set # CONFIG_XFS_RT is not set # CONFIG_XFS_WARN is not set # CONFIG_XFS_DEBUG is not set # CONFIG_GFS2_FS is not set # CONFIG_OCFS2_FS is not set CONFIG_BTRFS_FS=y # CONFIG_BTRFS_FS_POSIX_ACL is not set # CONFIG_BTRFS_FS_CHECK_INTEGRITY is not set # CONFIG_BTRFS_FS_RUN_SANITY_TESTS is not set # CONFIG_BTRFS_DEBUG is not set # CONFIG_BTRFS_ASSERT is not set # CONFIG_NILFS2_FS is not set CONFIG_FS_POSIX_ACL=y CONFIG_EXPORTFS=y CONFIG_FILE_LOCKING=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_FANOTIFY=y # CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set # CONFIG_QUOTA is not set # CONFIG_QUOTACTL is not set CONFIG_AUTOFS4_FS=y CONFIG_FUSE_FS=y # CONFIG_CUSE is not set CONFIG_GENERIC_ACL=y # # Caches # CONFIG_FSCACHE=y # CONFIG_FSCACHE_STATS is not set # CONFIG_FSCACHE_HISTOGRAM is not set # CONFIG_FSCACHE_DEBUG is not set # CONFIG_FSCACHE_OBJECT_LIST is not set # CONFIG_CACHEFILES is not set # # CD-ROM/DVD Filesystems # # CONFIG_ISO9660_FS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # # CONFIG_MSDOS_FS is not set # CONFIG_VFAT_FS is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_PROC_PAGE_MONITOR=y CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_TMPFS_XATTR=y CONFIG_HUGETLBFS=y CONFIG_HUGETLB_PAGE=y CONFIG_CONFIGFS_FS=y # CONFIG_MISC_FILESYSTEMS is not set # CONFIG_NETWORK_FILESYSTEMS is not set CONFIG_NLS=y CONFIG_NLS_DEFAULT="utf8" CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_CODEPAGE_737=y CONFIG_NLS_CODEPAGE_775=y CONFIG_NLS_CODEPAGE_850=y CONFIG_NLS_CODEPAGE_852=y CONFIG_NLS_CODEPAGE_855=y CONFIG_NLS_CODEPAGE_857=y CONFIG_NLS_CODEPAGE_860=y CONFIG_NLS_CODEPAGE_861=y CONFIG_NLS_CODEPAGE_862=y CONFIG_NLS_CODEPAGE_863=y CONFIG_NLS_CODEPAGE_864=y CONFIG_NLS_CODEPAGE_865=y CONFIG_NLS_CODEPAGE_866=y CONFIG_NLS_CODEPAGE_869=y CONFIG_NLS_CODEPAGE_936=y CONFIG_NLS_CODEPAGE_950=y CONFIG_NLS_CODEPAGE_932=y CONFIG_NLS_CODEPAGE_949=y CONFIG_NLS_CODEPAGE_874=y CONFIG_NLS_ISO8859_8=y CONFIG_NLS_CODEPAGE_1250=y CONFIG_NLS_CODEPAGE_1251=y CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y CONFIG_NLS_ISO8859_2=y CONFIG_NLS_ISO8859_3=y CONFIG_NLS_ISO8859_4=y CONFIG_NLS_ISO8859_5=y CONFIG_NLS_ISO8859_6=y CONFIG_NLS_ISO8859_7=y CONFIG_NLS_ISO8859_9=y CONFIG_NLS_ISO8859_13=y CONFIG_NLS_ISO8859_14=y CONFIG_NLS_ISO8859_15=y CONFIG_NLS_KOI8_R=y CONFIG_NLS_KOI8_U=y # CONFIG_NLS_MAC_ROMAN is not set # CONFIG_NLS_MAC_CELTIC is not set # CONFIG_NLS_MAC_CENTEURO is not set # CONFIG_NLS_MAC_CROATIAN is not set # CONFIG_NLS_MAC_CYRILLIC is not set # CONFIG_NLS_MAC_GAELIC is not set # CONFIG_NLS_MAC_GREEK is not set # CONFIG_NLS_MAC_ICELAND is not set # CONFIG_NLS_MAC_INUIT is not set # CONFIG_NLS_MAC_ROMANIAN is not set # CONFIG_NLS_MAC_TURKISH is not set CONFIG_NLS_UTF8=y # CONFIG_DLM is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # # printk and dmesg options # CONFIG_PRINTK_TIME=y CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4 # CONFIG_BOOT_PRINTK_DELAY is not set # CONFIG_DYNAMIC_DEBUG is not set # # Compile-time checks and compiler options # # CONFIG_DEBUG_INFO is not set # CONFIG_ENABLE_WARN_DEPRECATED is not set CONFIG_ENABLE_MUST_CHECK=y CONFIG_FRAME_WARN=2048 # CONFIG_STRIP_ASM_SYMS is not set # CONFIG_READABLE_ASM is not set # CONFIG_UNUSED_SYMBOLS is not set CONFIG_DEBUG_FS=y # CONFIG_HEADERS_CHECK is not set # CONFIG_DEBUG_SECTION_MISMATCH is not set CONFIG_ARCH_WANT_FRAME_POINTERS=y CONFIG_FRAME_POINTER=y # CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set CONFIG_MAGIC_SYSRQ=y CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1 CONFIG_DEBUG_KERNEL=y # # Memory Debugging # # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_DEBUG_OBJECTS is not set # CONFIG_SLUB_DEBUG_ON is not set # CONFIG_SLUB_STATS is not set CONFIG_HAVE_DEBUG_KMEMLEAK=y # CONFIG_DEBUG_KMEMLEAK is not set CONFIG_DEBUG_STACK_USAGE=y # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_VIRTUAL is not set CONFIG_DEBUG_MEMORY_INIT=y # CONFIG_DEBUG_PER_CPU_MAPS is not set CONFIG_HAVE_DEBUG_STACKOVERFLOW=y CONFIG_DEBUG_STACKOVERFLOW=y CONFIG_HAVE_ARCH_KMEMCHECK=y # CONFIG_KMEMCHECK is not set # CONFIG_DEBUG_SHIRQ is not set # # Debug Lockups and Hangs # # CONFIG_LOCKUP_DETECTOR is not set # CONFIG_DETECT_HUNG_TASK is not set # CONFIG_PANIC_ON_OOPS is not set CONFIG_PANIC_ON_OOPS_VALUE=0 # CONFIG_SCHED_DEBUG is not set CONFIG_SCHEDSTATS=y CONFIG_TIMER_STATS=y # # Lock Debugging (spinlocks, mutexes, etc...) # # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_MUTEXES is not set # CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_ATOMIC_SLEEP is not set # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y # CONFIG_DEBUG_WRITECOUNT is not set # CONFIG_DEBUG_LIST is not set # CONFIG_DEBUG_SG is not set # CONFIG_DEBUG_NOTIFIERS is not set # CONFIG_DEBUG_CREDENTIALS is not set # # RCU Debugging # # CONFIG_SPARSE_RCU_POINTER is not set # CONFIG_RCU_TORTURE_TEST is not set CONFIG_RCU_CPU_STALL_TIMEOUT=60 # CONFIG_RCU_CPU_STALL_INFO is not set # CONFIG_RCU_TRACE is not set # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set # CONFIG_NOTIFIER_ERROR_INJECTION is not set # CONFIG_FAULT_INJECTION is not set # CONFIG_LATENCYTOP is not set CONFIG_ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS=y # CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_SYSCALL_TRACEPOINTS=y CONFIG_HAVE_FENTRY=y CONFIG_HAVE_C_RECORDMCOUNT=y CONFIG_TRACING_SUPPORT=y # CONFIG_FTRACE is not set # # Runtime Testing # # CONFIG_LKDTM is not set # CONFIG_TEST_LIST_SORT is not set # CONFIG_BACKTRACE_SELF_TEST is not set # CONFIG_RBTREE_TEST is not set # CONFIG_ATOMIC64_SELFTEST is not set # CONFIG_ASYNC_RAID6_TEST is not set # CONFIG_TEST_STRING_HELPERS is not set # CONFIG_TEST_KSTRTOX is not set # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set # CONFIG_DMA_API_DEBUG is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y # CONFIG_KGDB is not set # CONFIG_STRICT_DEVMEM is not set CONFIG_X86_VERBOSE_BOOTUP=y CONFIG_EARLY_PRINTK=y CONFIG_EARLY_PRINTK_DBGP=y # CONFIG_X86_PTDUMP is not set CONFIG_DEBUG_RODATA=y # CONFIG_DEBUG_RODATA_TEST is not set CONFIG_DOUBLEFAULT=y # CONFIG_DEBUG_TLBFLUSH is not set # CONFIG_IOMMU_DEBUG is not set # CONFIG_IOMMU_STRESS is not set CONFIG_HAVE_MMIOTRACE_SUPPORT=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 CONFIG_IO_DELAY_0X80=y # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=0 CONFIG_DEBUG_BOOT_PARAMS=y # CONFIG_CPA_DEBUG is not set CONFIG_OPTIMIZE_INLINING=y # CONFIG_DEBUG_NMI_SELFTEST is not set # CONFIG_X86_DEBUG_STATIC_CPU_HAS is not set # # Security options # CONFIG_KEYS=y # CONFIG_PERSISTENT_KEYRINGS is not set # CONFIG_BIG_KEYS is not set # CONFIG_ENCRYPTED_KEYS is not set CONFIG_KEYS_DEBUG_PROC_KEYS=y # CONFIG_SECURITY_DMESG_RESTRICT is not set CONFIG_SECURITY=y # CONFIG_SECURITYFS is not set CONFIG_SECURITY_NETWORK=y # CONFIG_SECURITY_NETWORK_XFRM is not set # CONFIG_SECURITY_PATH is not set # CONFIG_SECURITY_SMACK is not set # CONFIG_SECURITY_TOMOYO is not set # CONFIG_SECURITY_APPARMOR is not set # CONFIG_SECURITY_YAMA is not set # CONFIG_IMA is not set # CONFIG_EVM is not set CONFIG_DEFAULT_SECURITY_DAC=y CONFIG_DEFAULT_SECURITY="" CONFIG_XOR_BLOCKS=y CONFIG_ASYNC_CORE=y CONFIG_ASYNC_MEMCPY=y CONFIG_ASYNC_XOR=y CONFIG_ASYNC_PQ=y CONFIG_ASYNC_RAID6_RECOV=y CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=y CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP2=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y # CONFIG_CRYPTO_USER is not set CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y CONFIG_CRYPTO_GF128MUL=y # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_PCRYPT is not set CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=y CONFIG_CRYPTO_AUTHENC=y # # Authenticated Encryption with Associated Data # # CONFIG_CRYPTO_CCM is not set # CONFIG_CRYPTO_GCM is not set # CONFIG_CRYPTO_SEQIV is not set # # Block modes # CONFIG_CRYPTO_CBC=y # CONFIG_CRYPTO_CTR is not set # CONFIG_CRYPTO_CTS is not set CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_LRW=y # CONFIG_CRYPTO_PCBC is not set CONFIG_CRYPTO_XTS=y # # Hash modes # # CONFIG_CRYPTO_CMAC is not set CONFIG_CRYPTO_HMAC=y # CONFIG_CRYPTO_XCBC is not set # CONFIG_CRYPTO_VMAC is not set # # Digest # CONFIG_CRYPTO_CRC32C=y # CONFIG_CRYPTO_CRC32C_INTEL is not set CONFIG_CRYPTO_CRC32=y CONFIG_CRYPTO_CRC32_PCLMUL=y CONFIG_CRYPTO_CRCT10DIF=y # CONFIG_CRYPTO_CRCT10DIF_PCLMUL is not set # CONFIG_CRYPTO_GHASH is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_RMD128 is not set # CONFIG_CRYPTO_RMD160 is not set # CONFIG_CRYPTO_RMD256 is not set # CONFIG_CRYPTO_RMD320 is not set CONFIG_CRYPTO_SHA1=y # CONFIG_CRYPTO_SHA1_SSSE3 is not set CONFIG_CRYPTO_SHA256_SSSE3=y CONFIG_CRYPTO_SHA512_SSSE3=y CONFIG_CRYPTO_SHA256=y CONFIG_CRYPTO_SHA512=y # CONFIG_CRYPTO_TGR192 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL is not set # # Ciphers # CONFIG_CRYPTO_AES=y # CONFIG_CRYPTO_AES_X86_64 is not set # CONFIG_CRYPTO_AES_NI_INTEL is not set # CONFIG_CRYPTO_ANUBIS is not set CONFIG_CRYPTO_ARC4=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_BLOWFISH_X86_64 is not set # CONFIG_CRYPTO_CAMELLIA is not set # CONFIG_CRYPTO_CAMELLIA_X86_64 is not set # CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64 is not set # CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64 is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST5_AVX_X86_64 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_CAST6_AVX_X86_64 is not set CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_FCRYPT is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_SALSA20 is not set # CONFIG_CRYPTO_SALSA20_X86_64 is not set # CONFIG_CRYPTO_SEED is not set CONFIG_CRYPTO_SERPENT=y # CONFIG_CRYPTO_SERPENT_SSE2_X86_64 is not set # CONFIG_CRYPTO_SERPENT_AVX_X86_64 is not set # CONFIG_CRYPTO_SERPENT_AVX2_X86_64 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_TWOFISH_X86_64 is not set # CONFIG_CRYPTO_TWOFISH_X86_64_3WAY is not set # CONFIG_CRYPTO_TWOFISH_AVX_X86_64 is not set # # Compression # # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_ZLIB is not set # CONFIG_CRYPTO_LZO is not set # CONFIG_CRYPTO_LZ4 is not set # CONFIG_CRYPTO_LZ4HC is not set # # Random Number Generation # # CONFIG_CRYPTO_ANSI_CPRNG is not set # CONFIG_CRYPTO_USER_API_HASH is not set # CONFIG_CRYPTO_USER_API_SKCIPHER is not set # CONFIG_CRYPTO_HW is not set # CONFIG_ASYMMETRIC_KEY_TYPE is not set CONFIG_HAVE_KVM=y # CONFIG_VIRTUALIZATION is not set # CONFIG_BINARY_PRINTF is not set # # Library routines # CONFIG_RAID6_PQ=y CONFIG_BITREVERSE=y CONFIG_GENERIC_STRNCPY_FROM_USER=y CONFIG_GENERIC_STRNLEN_USER=y CONFIG_GENERIC_NET_UTILS=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_PCI_IOMAP=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_IO=y CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y # CONFIG_CRC_CCITT is not set CONFIG_CRC16=y CONFIG_CRC_T10DIF=y # CONFIG_CRC_ITU_T is not set CONFIG_CRC32=y CONFIG_CRC32_SELFTEST=y CONFIG_CRC32_SLICEBY8=y # CONFIG_CRC32_SLICEBY4 is not set # CONFIG_CRC32_SARWATE is not set # CONFIG_CRC32_BIT is not set CONFIG_CRC7=y CONFIG_LIBCRC32C=y CONFIG_CRC8=y # CONFIG_RANDOM32_SELFTEST is not set CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_LZO_COMPRESS=y CONFIG_LZO_DECOMPRESS=y CONFIG_XZ_DEC=y CONFIG_XZ_DEC_X86=y CONFIG_XZ_DEC_POWERPC=y CONFIG_XZ_DEC_IA64=y CONFIG_XZ_DEC_ARM=y CONFIG_XZ_DEC_ARMTHUMB=y CONFIG_XZ_DEC_SPARC=y CONFIG_XZ_DEC_BCJ=y # CONFIG_XZ_DEC_TEST is not set CONFIG_ASSOCIATIVE_ARRAY=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y CONFIG_CHECK_SIGNATURE=y CONFIG_CPU_RMAP=y CONFIG_DQL=y CONFIG_NLATTR=y CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y # CONFIG_AVERAGE is not set # CONFIG_CORDIC is not set CONFIG_DDR=y CONFIG_FONT_SUPPORT=y # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 19:06 ` Пламен Петров @ 2014-04-23 19:15 ` Marc MERLIN 2014-04-23 19:37 ` Пламен Петров 2014-04-24 17:19 ` Пламен Петров 0 siblings, 2 replies; 39+ messages in thread From: Marc MERLIN @ 2014-04-23 19:15 UTC (permalink / raw) To: Пламен Петров Cc: linux-btrfs On Wed, Apr 23, 2014 at 10:06:12PM +0300, Пламен Петров wrote: > Just to clarify - I am using a monolithic kernel built from source, and it has all the stuff it needs to support built-in, and then some. And no modules. > The sources I'm using are the vanilla kernels from Linus and Greg KH downloaded from kernel.org. Ok. > Check out the attached config I am using - it’s a kernel I'm running on one server and a couple of virtual machines. That's the working .config. I suggest you diff that one with the new one you have for 3.14 > Until now - copying said config and doing a "make oldconfig" or "make olddefconfig" and compiling-then-booting worked fine. This should indeed work, this is what I do too. So now, we're kind of guessing. To save us all time, could you capture a serial console boot from the running 3.13 and then the failing 3.14. My guess is that if you diff both you'll likely find what went wrong, but if not you can post here. As for the btrfs FS format, it has not changed in a way that new kernels wouldn't be able to mount an FS from a year ago or more. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 19:15 ` Marc MERLIN @ 2014-04-23 19:37 ` Пламен Петров 2014-04-23 20:58 ` Marc MERLIN 2014-04-24 17:19 ` Пламен Петров 1 sibling, 1 reply; 39+ messages in thread From: Пламен Петров @ 2014-04-23 19:37 UTC (permalink / raw) To: 'Marc MERLIN'; +Cc: linux-btrfs [-- Attachment #1: Type: text/plain, Size: 2248 bytes --] > -----Original Message----- > From: Marc MERLIN [mailto:marc@merlins.org] > Sent: Wednesday, April 23, 2014 10:16 PM > To: Пламен Петров > Cc: linux-btrfs@vger.kernel.org > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > On Wed, Apr 23, 2014 at 10:06:12PM +0300, Пламен Петров wrote: > > Just to clarify - I am using a monolithic kernel built from source, and it has all > the stuff it needs to support built-in, and then some. And no modules. > > The sources I'm using are the vanilla kernels from Linus and Greg KH > downloaded from kernel.org. > > Ok. > > > Check out the attached config I am using - it’s a kernel I'm running on one > server and a couple of virtual machines. > > That's the working .config. > I suggest you diff that one with the new one you have for 3.14 > > > Until now - copying said config and doing a "make oldconfig" or "make > olddefconfig" and compiling-then-booting worked fine. > > This should indeed work, this is what I do too. > > So now, we're kind of guessing. To save us all time, could you capture a serial > console boot from the running 3.13 and then the failing 3.14. Well, for the details - see for example here: https://bugzilla.kernel.org/attachment.cgi?id=133111 how does a 3.14.1 built the way described earlier fails. And for that matter - see the whole bugzilla bug entry - I went on and bisected this, using the linux-stable git tree, and after that landed me on the commit that introduces some "shiny new btrfs feature" for 3.14 - I decided my git bisection has gone wrong. And because I reported it on April 17-th and since then there has been no activity on the bugzilla entry besides me updating it - I posted my problem here, for more eyes to see. > > My guess is that if you diff both you'll likely find what went wrong, but if not > you can post here. See the result of "diff config-v3.14.1-mix64 config-v3.13.11-mix64" in the attached file. > > As for the btrfs FS format, it has not changed in a way that new kernels > wouldn't be able to mount an FS from a year ago or more. Good to know! Thanks! > > Marc --------------------------------- Plamen Petrov [-- Attachment #2: diff-3.14.1-to-3.13.11.txt --] [-- Type: text/plain, Size: 1916 bytes --] diff config-v3.14.1-mix64 config-v3.13.11-mix64 3c3 < # Linux/x86 3.14.1 Kernel Configuration --- > # Linux/x86 3.13.11 Kernel Configuration 155a156 > # CONFIG_UIDGID_STRICT_TYPE_CHECKS is not set 230,234d230 < CONFIG_HAVE_CC_STACKPROTECTOR=y < # CONFIG_CC_STACKPROTECTOR is not set < CONFIG_CC_STACKPROTECTOR_NONE=y < # CONFIG_CC_STACKPROTECTOR_REGULAR is not set < # CONFIG_CC_STACKPROTECTOR_STRONG is not set 309d304 < # CONFIG_XEN_PVH is not set 358a354 > CONFIG_MICROCODE_INTEL_LIB=y 407d402 < # CONFIG_ZSMALLOC is not set 419a415 > # CONFIG_CC_STACKPROTECTOR is not set 430d425 < # CONFIG_RANDOMIZE_BASE is not set 762,763d756 < # CONFIG_NET_SCH_HHF is not set < # CONFIG_NET_SCH_PIE is not set 794,795c787 < # CONFIG_CGROUP_NET_PRIO is not set < # CONFIG_CGROUP_NET_CLASSID is not set --- > # CONFIG_NETPRIO_CGROUP is not set 944d935 < # CONFIG_GENWQE is not set 997a989 > # CONFIG_SCSI_AIC7XXX_OLD is not set 1158d1149 < CONFIG_DM_BUFIO=y 1256d1246 < # CONFIG_I40EVF is not set 1489d1478 < CONFIG_ARCH_MIGHT_HAVE_PC_SERIO=y 1608d1596 < # CONFIG_I2C_DESIGNWARE_PLATFORM is not set 1622d1609 < # CONFIG_I2C_ROBOTFUZZ_OSIF is not set 1807a1795 > # CONFIG_CPU_THERMAL is not set 1811d1798 < # CONFIG_ACPI_INT3403_THERMAL is not set 1851d1837 < # CONFIG_MFD_MAX14577 is not set 1872d1857 < # CONFIG_MFD_LP3943 is not set 1904d1888 < CONFIG_INTEL_GTT=y 1928d1911 < # CONFIG_DRM_I915_UMS is not set 1940d1922 < # CONFIG_DRM_BOCHS is not set 1978d1959 < # CONFIG_FB_OPENCORES is not set 2080a2062 > # CONFIG_HID_LOGITECH_DJ is not set 2184d2165 < # CONFIG_USB_MUSB_HDRC is not set 2186d2166 < # CONFIG_USB_DWC2 is not set 2225d2204 < # CONFIG_USB_OTG_FSM is not set 2269d2247 < # CONFIG_RTC_DRV_ISL12057 is not set 2403d2380 < CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y 2450a2428 > CONFIG_GENERIC_ACL=y 2604d2581 < CONFIG_PANIC_TIMEOUT=0 ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 19:37 ` Пламен Петров @ 2014-04-23 20:58 ` Marc MERLIN 2014-04-23 21:54 ` Пламен Петров 2014-04-24 12:34 ` Chris Mason 0 siblings, 2 replies; 39+ messages in thread From: Marc MERLIN @ 2014-04-23 20:58 UTC (permalink / raw) To: Пламен Петров Cc: linux-btrfs On Wed, Apr 23, 2014 at 10:37:44PM +0300, Пламен Петров wrote: > > So now, we're kind of guessing. To save us all time, could you capture a serial > > console boot from the running 3.13 and then the failing 3.14. > > Well, for the details - see for example here: > https://bugzilla.kernel.org/attachment.cgi?id=133111 > how does a 3.14.1 built the way described earlier fails. Thanks, that helps. Except, now I'm perplexed. It indeed shows btrfs loaded and your block device being detected. However it does not show a btrfs mount error. I haven't had to debug this in a while, but I'm wondering if you're having a block device problem. It may help to look up what error -38 translates into for that mount error. > And for that matter - see the whole bugzilla bug entry - I went on and bisected this, using the linux-stable git tree, and after that landed me on the commit that introduces some "shiny new btrfs feature" for 3.14 - I decided my git bisection has gone wrong. And because I reported it on April 17-th and since then there has been no activity on the bugzilla entry besides me updating it - I posted my problem here, for more eyes to see. One easier way to debug this would be to create an initrd for 3.13 and 3.14. Make sure it works with 3.13 first, then boot 3.14 and see what error you get. You'll get an error from mount(8) and not the kernel and you'll be dropped to a shell, giving you more debug options. > > My guess is that if you diff both you'll likely find what went wrong, but if not > > you can post here. > > See the result of "diff config-v3.14.1-mix64 config-v3.13.11-mix64" in the attached file. diff -u is your friend ;) but diff looks reasonable. > > As for the btrfs FS format, it has not changed in a way that new kernels > > wouldn't be able to mount an FS from a year ago or more. > > Good to know! Thanks! Of course, that doesn't mean you didn't find a bug saying otherwise. If you try from an initrd, it'll make it easier to debug. You don't have to build a new kernel or make btrfs a module, just mounting a working initrd and then trying this again with userland tools will help debug. (alternatively, rescue boot media with your kernel would work too, but that's likely more work to build than an initrd) Actually, you could also use your VM setup to boot another linux image running ext4 as root with your new kernel, setup your existing drive as sdb, and try to mount it then. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 20:58 ` Marc MERLIN @ 2014-04-23 21:54 ` Пламен Петров 2014-04-23 22:03 ` Marc MERLIN 2014-04-24 12:34 ` Chris Mason 1 sibling, 1 reply; 39+ messages in thread From: Пламен Петров @ 2014-04-23 21:54 UTC (permalink / raw) To: 'Marc MERLIN'; +Cc: linux-btrfs [-- Attachment #1: Type: text/plain, Size: 3382 bytes --] > -----Original Message----- > From: Marc MERLIN [mailto:marc@merlins.org] > Sent: Wednesday, April 23, 2014 11:58 PM > To: Пламен Петров > Cc: linux-btrfs@vger.kernel.org > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > On Wed, Apr 23, 2014 at 10:37:44PM +0300, Пламен Петров wrote: > > > So now, we're kind of guessing. To save us all time, could you > > > capture a serial console boot from the running 3.13 and then the failing > 3.14. > > > > Well, for the details - see for example here: > > https://bugzilla.kernel.org/attachment.cgi?id=133111 > > how does a 3.14.1 built the way described earlier fails. > > Thanks, that helps. > Except, now I'm perplexed. > > It indeed shows btrfs loaded and your block device being detected. > However it does not show a btrfs mount error. > > I haven't had to debug this in a while, but I'm wondering if you're having a > block device problem. > > It may help to look up what error -38 translates into for that mount error. My searches so far failed to return anything useful to solving this problem. > > > And for that matter - see the whole bugzilla bug entry - I went on and > bisected this, using the linux-stable git tree, and after that landed me on the > commit that introduces some "shiny new btrfs feature" for 3.14 - I decided > my git bisection has gone wrong. And because I reported it on April 17-th and > since then there has been no activity on the bugzilla entry besides me > updating it - I posted my problem here, for more eyes to see. > > One easier way to debug this would be to create an initrd for 3.13 and 3.14. > Make sure it works with 3.13 first, then boot 3.14 and see what error you get. > You'll get an error from mount(8) and not the kernel and you'll be dropped to > a shell, giving you more debug options. > The initrd way will require some reading up on my part - so will have to wait for tomorrow. > > > My guess is that if you diff both you'll likely find what went > > > wrong, but if not you can post here. > > > > See the result of "diff config-v3.14.1-mix64 config-v3.13.11-mix64" in the > attached file. > > diff -u is your friend ;) > but diff looks reasonable. > > > > As for the btrfs FS format, it has not changed in a way that new > > > kernels wouldn't be able to mount an FS from a year ago or more. > > > > Good to know! Thanks! > > Of course, that doesn't mean you didn't find a bug saying otherwise. > > If you try from an initrd, it'll make it easier to debug. I will have to lookup how to do that... > You don't have to build a > new kernel or make btrfs a module, just mounting a working initrd and then > trying this again with userland tools will help debug. > (alternatively, rescue boot media with your kernel would work too, but that's > likely more work to build than an initrd) Not more work - just replaced the kernel on the setup/rescue media with mine and the result is the same - see attached image file. > Actually, you could also use your VM > setup to boot another linux image running ext4 as root with your new kernel, > setup your existing drive as sdb, and try to mount it then. > > Marc > -- Thanks for the ideas, Marc. It's nice to see someone trying to help! ----------------- Plamen Petrov [-- Attachment #2: rescue-media-plus-my-kernel-3.14.1.png --] [-- Type: image/png, Size: 46112 bytes --] ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 21:54 ` Пламен Петров @ 2014-04-23 22:03 ` Marc MERLIN 2014-04-23 22:20 ` Пламен Петров 2014-04-23 22:41 ` Hugo Mills 0 siblings, 2 replies; 39+ messages in thread From: Marc MERLIN @ 2014-04-23 22:03 UTC (permalink / raw) To: Пламен Петров Cc: linux-btrfs On Thu, Apr 24, 2014 at 12:54:57AM +0300, Пламен Петров wrote: > > It may help to look up what error -38 translates into for that mount error. > > My searches so far failed to return anything useful to solving this problem. Yeah, I searched before you :) this would require reading the kernel source to track down -38. (not hard, I just didn't do it)( > The initrd way will require some reading up on my part - so will have to wait for tomorrow. On debian, I just have to run this: update-initramfs -v -c -k `grep linux-source debian/changelog | awk '{ print $1 }' | sed "s/linux-source-//"` Then see /etc/initramfs-tools/initramfs.conf but the defaults should work Running update-grub2 should give you something like this: echo 'Loading Linux 3.12.7-amd64-i915-preempt-20131107 ...' linux /vmlinuz-3.12.7-amd64-i915-preempt-20131107 root=/dev/mapper/cryptroot ro rootflags=subvol=root cryptopts=source=/dev/sda4,keyscript=/sbin/cryptgetpw,discard usbcore.autosuspend=1 pcie_aspm=force i915.i915_enable_rc6 =7 i915.i915_enable_fbc=1 i915.semaphores=1 i915.lvds_downclock=1 acpi_osi=Linux acpi_backlight=vendor echo 'Loading initial ramdisk ...' initrd /initrd.img-3.12.7-amd64-i915-preempt-20131107 > > You don't have to build a > > new kernel or make btrfs a module, just mounting a working initrd and then > > trying this again with userland tools will help debug. > > (alternatively, rescue boot media with your kernel would work too, but that's > > likely more work to build than an initrd) > > Not more work - just replaced the kernel on the setup/rescue media with mine and the result is the same - see attached image file. That's not what I meant, I meant a rescue media that boots another filesystem than you root filesystem. Then from there, you can use normal userland tools to manually mount your root filesystem and/or see errors. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 22:03 ` Marc MERLIN @ 2014-04-23 22:20 ` Пламен Петров 2014-04-23 22:40 ` Chris Murphy 2014-04-23 22:41 ` Hugo Mills 1 sibling, 1 reply; 39+ messages in thread From: Пламен Петров @ 2014-04-23 22:20 UTC (permalink / raw) To: 'Marc MERLIN'; +Cc: linux-btrfs > -----Original Message----- > From: Marc MERLIN [mailto:marc@merlins.org] > Sent: Thursday, April 24, 2014 1:03 AM > To: Пламен Петров > Cc: linux-btrfs@vger.kernel.org > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > On Thu, Apr 24, 2014 at 12:54:57AM +0300, Пламен Петров wrote: > > > It may help to look up what error -38 translates into for that mount error. > > > > My searches so far failed to return anything useful to solving this problem. > > Yeah, I searched before you :) this would require reading the kernel source > to track down -38. > (not hard, I just didn't do it)( > > > The initrd way will require some reading up on my part - so will have to wait > for tomorrow. > > On debian, I just have to run this: > update-initramfs -v -c -k `grep linux-source debian/changelog | awk '{ print > $1 }' | sed "s/linux-source-//"` > Well, I'm using a source based distro - ever heard of CRUX - http://crux.nu/ ? > Then see /etc/initramfs-tools/initramfs.conf > but the defaults should work > > Running update-grub2 should give you something like this: > echo 'Loading Linux 3.12.7-amd64-i915-preempt-20131107 ...' > linux /vmlinuz-3.12.7-amd64-i915-preempt-20131107 > root=/dev/mapper/cryptroot ro rootflags=subvol=root > cryptopts=source=/dev/sda4,keyscript=/sbin/cryptgetpw,discard > usbcore.autosuspend=1 pcie_aspm=force i915.i915_enable_rc6 =7 > i915.i915_enable_fbc=1 i915.semaphores=1 i915.lvds_downclock=1 > acpi_osi=Linux acpi_backlight=vendor > echo 'Loading initial ramdisk ...' > initrd /initrd.img-3.12.7-amd64-i915-preempt-20131107 > Never got to understand GRUB2 inner workings... so I keep to what works for me - GRUB Legacy here! > > > You don't have to build a > > > new kernel or make btrfs a module, just mounting a working initrd > > > and then trying this again with userland tools will help debug. > > > (alternatively, rescue boot media with your kernel would work too, > > > but that's likely more work to build than an initrd) > > > > Not more work - just replaced the kernel on the setup/rescue media with > mine and the result is the same - see attached image file. > > That's not what I meant, I meant a rescue media that boots another > filesystem than you root filesystem. > Then from there, you can use normal userland tools to manually mount your > root filesystem and/or see errors. > > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet cooking Home page: > http://marc.merlins.org/ I'm trying to boot into the rescue media's environment with my own kernel, but it fails now that my monolithic kernel has no support for initrd whatsoever (or something else missing)! I guess I’ll leave this testing for tomorrow - getting tired and sleepy now... Thanks! --------------------------------- Plamen Petrov ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 22:20 ` Пламен Петров @ 2014-04-23 22:40 ` Chris Murphy 2014-04-23 22:43 ` Hugo Mills 0 siblings, 1 reply; 39+ messages in thread From: Chris Murphy @ 2014-04-23 22:40 UTC (permalink / raw) To: Btrfs BTRFS The screen shot provided makes it clear that one of the following kernel parameters is incorrect: > root=/dev/mapper/cryptroot > rootflags=subvol=root So either the dmcrypt volume hasn't been opened, thus isn't available; or rootfs isn't on a subvolume named root found at the top level of the file system. So I'd say this isn't a btrfs problem, rather it's due to some earlier misconfiguration that's preventing rootfs from being mounted. Chris Murphy ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 22:40 ` Chris Murphy @ 2014-04-23 22:43 ` Hugo Mills 2014-04-23 22:50 ` Marc MERLIN 0 siblings, 1 reply; 39+ messages in thread From: Hugo Mills @ 2014-04-23 22:43 UTC (permalink / raw) To: Chris Murphy; +Cc: Btrfs BTRFS [-- Attachment #1: Type: text/plain, Size: 1006 bytes --] On Wed, Apr 23, 2014 at 04:40:33PM -0600, Chris Murphy wrote: > The screen shot provided makes it clear that one of the following kernel parameters is incorrect: > > > root=/dev/mapper/cryptroot > > > rootflags=subvol=root > > So either the dmcrypt volume hasn't been opened, thus isn't available; or rootfs isn't on a subvolume named root found at the top level of the file system. So I'd say this isn't a btrfs problem, rather it's due to some earlier misconfiguration that's preventing rootfs from being mounted. You'll need an initrd to run cryptsetup (or whatever) to collect a passphrase and decrypt the volume before you try to mount it. This sounds like a case for an initrd again. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Computer Science is not about computers, any more than --- astronomy is about telescopes. [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 811 bytes --] ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 22:43 ` Hugo Mills @ 2014-04-23 22:50 ` Marc MERLIN 2014-04-23 22:53 ` Hugo Mills 0 siblings, 1 reply; 39+ messages in thread From: Marc MERLIN @ 2014-04-23 22:50 UTC (permalink / raw) To: Hugo Mills, Chris Murphy, Btrfs BTRFS [-- Attachment #1: Type: text/plain, Size: 1157 bytes --] On Wed, Apr 23, 2014 at 11:43:03PM +0100, Hugo Mills wrote: > On Wed, Apr 23, 2014 at 04:40:33PM -0600, Chris Murphy wrote: > > The screen shot provided makes it clear that one of the following kernel parameters is incorrect: > > > > > root=/dev/mapper/cryptroot > > > > > rootflags=subvol=root > > > > So either the dmcrypt volume hasn't been opened, thus isn't available; or rootfs isn't on a subvolume named root found at the top level of the file system. So I'd say this isn't a btrfs problem, rather it's due to some earlier misconfiguration that's preventing rootfs from being mounted. > > You'll need an initrd to run cryptsetup (or whatever) to collect a > passphrase and decrypt the volume before you try to mount it. This > sounds like a case for an initrd again. I think you are confused, that's my config I pasted as an example. He does not use dmcrypt in his example. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 308 bytes --] ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 22:50 ` Marc MERLIN @ 2014-04-23 22:53 ` Hugo Mills 0 siblings, 0 replies; 39+ messages in thread From: Hugo Mills @ 2014-04-23 22:53 UTC (permalink / raw) To: Marc MERLIN; +Cc: Chris Murphy, Btrfs BTRFS [-- Attachment #1: Type: text/plain, Size: 1321 bytes --] On Wed, Apr 23, 2014 at 03:50:18PM -0700, Marc MERLIN wrote: > On Wed, Apr 23, 2014 at 11:43:03PM +0100, Hugo Mills wrote: > > On Wed, Apr 23, 2014 at 04:40:33PM -0600, Chris Murphy wrote: > > > The screen shot provided makes it clear that one of the following kernel parameters is incorrect: > > > > > > > root=/dev/mapper/cryptroot > > > > > > > rootflags=subvol=root > > > > > > So either the dmcrypt volume hasn't been opened, thus isn't available; or rootfs isn't on a subvolume named root found at the top level of the file system. So I'd say this isn't a btrfs problem, rather it's due to some earlier misconfiguration that's preventing rootfs from being mounted. > > > > You'll need an initrd to run cryptsetup (or whatever) to collect a > > passphrase and decrypt the volume before you try to mount it. This > > sounds like a case for an initrd again. > > I think you are confused, that's my config I pasted as an example. > He does not use dmcrypt in his example. Ah, OK. Never mind, then. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Computer Science is not about computers, any more than --- astronomy is about telescopes. [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 811 bytes --] ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 22:03 ` Marc MERLIN 2014-04-23 22:20 ` Пламен Петров @ 2014-04-23 22:41 ` Hugo Mills 1 sibling, 0 replies; 39+ messages in thread From: Hugo Mills @ 2014-04-23 22:41 UTC (permalink / raw) To: Marc MERLIN Cc: Пламен Петров, linux-btrfs [-- Attachment #1: Type: text/plain, Size: 836 bytes --] On Wed, Apr 23, 2014 at 03:03:12PM -0700, Marc MERLIN wrote: > On Thu, Apr 24, 2014 at 12:54:57AM +0300, Пламен Петров wrote: > > > It may help to look up what error -38 translates into for that mount error. > > > > My searches so far failed to return anything useful to solving this problem. > > Yeah, I searched before you :) this would require reading the kernel source > to track down -38. > (not hard, I just didn't do it)( #define ENOSYS 38 /* Function not implemented */ Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Computer Science is not about computers, any more than --- astronomy is about telescopes. [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 811 bytes --] ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 20:58 ` Marc MERLIN 2014-04-23 21:54 ` Пламен Петров @ 2014-04-24 12:34 ` Chris Mason 2014-04-24 12:36 ` Chris Mason 1 sibling, 1 reply; 39+ messages in thread From: Chris Mason @ 2014-04-24 12:34 UTC (permalink / raw) To: Marc MERLIN, Пламен Петров Cc: linux-btrfs On 04/23/2014 04:58 PM, Marc MERLIN wrote: > On Wed, Apr 23, 2014 at 10:37:44PM +0300, Пламен Петров wrote: >>> So now, we're kind of guessing. To save us all time, could you capture a serial >>> console boot from the running 3.13 and then the failing 3.14. >> >> Well, for the details - see for example here: >> https://bugzilla.kernel.org/attachment.cgi?id=133111 >> how does a 3.14.1 built the way described earlier fails. > > Thanks, that helps. > Except, now I'm perplexed. > > It indeed shows btrfs loaded and your block device being detected. > However it does not show a btrfs mount error. The mount error is popping up after the printk about not being able to find root. Add rootwait to the command line. -chris ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 12:34 ` Chris Mason @ 2014-04-24 12:36 ` Chris Mason 2014-04-24 17:08 ` Пламен Петров 0 siblings, 1 reply; 39+ messages in thread From: Chris Mason @ 2014-04-24 12:36 UTC (permalink / raw) To: Marc MERLIN, Пламен Петров Cc: linux-btrfs On 04/24/2014 08:34 AM, Chris Mason wrote: > > > On 04/23/2014 04:58 PM, Marc MERLIN wrote: >> On Wed, Apr 23, 2014 at 10:37:44PM +0300, Пламен Петров wrote: >>>> So now, we're kind of guessing. To save us all time, could you >>>> capture a serial >>>> console boot from the running 3.13 and then the failing 3.14. >>> >>> Well, for the details - see for example here: >>> https://bugzilla.kernel.org/attachment.cgi?id=133111 >>> how does a 3.14.1 built the way described earlier fails. >> >> Thanks, that helps. >> Except, now I'm perplexed. >> >> It indeed shows btrfs loaded and your block device being detected. >> However it does not show a btrfs mount error. > > The mount error is popping up after the printk about not being able to > find root. Add rootwait to the command line. Sorry, that's almost but not quite what I meant to say. The device detection message is popping up after the printk about not being able to find root. Add rootwait to the command line. In other words, the mount is failing before the root device is detected. rootwait will make us wait (forever) instead of failing. -chris ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 12:36 ` Chris Mason @ 2014-04-24 17:08 ` Пламен Петров 0 siblings, 0 replies; 39+ messages in thread From: Пламен Петров @ 2014-04-24 17:08 UTC (permalink / raw) To: 'Chris Mason', 'Marc MERLIN'; +Cc: linux-btrfs > -----Original Message----- > From: Chris Mason [mailto:clm@fb.com] > Sent: Thursday, April 24, 2014 3:36 PM > To: Marc MERLIN; Пламен Петров > Cc: linux-btrfs@vger.kernel.org > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > > > On 04/24/2014 08:34 AM, Chris Mason wrote: > > > > > > On 04/23/2014 04:58 PM, Marc MERLIN wrote: > >> On Wed, Apr 23, 2014 at 10:37:44PM +0300, Пламен Петров wrote: > >>>> So now, we're kind of guessing. To save us all time, could you > >>>> capture a serial console boot from the running 3.13 and then the > >>>> failing 3.14. > >>> > >>> Well, for the details - see for example here: > >>> https://bugzilla.kernel.org/attachment.cgi?id=133111 > >>> how does a 3.14.1 built the way described earlier fails. > >> > >> Thanks, that helps. > >> Except, now I'm perplexed. > >> > >> It indeed shows btrfs loaded and your block device being detected. > >> However it does not show a btrfs mount error. > > > > The mount error is popping up after the printk about not being able to > > find root. Add rootwait to the command line. > > Sorry, that's almost but not quite what I meant to say. The device detection > message is popping up after the printk about not being able to find root. Add > rootwait to the command line. > > In other words, the mount is failing before the root device is detected. > rootwait will make us wait (forever) instead of failing. > > -chris Today I managed to try adding rootwait to the kernel commandline - the kernel panic with it in place, too. --------------------------------- Plamen Petrov ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 19:15 ` Marc MERLIN 2014-04-23 19:37 ` Пламен Петров @ 2014-04-24 17:19 ` Пламен Петров 2014-04-24 17:33 ` Marc MERLIN 1 sibling, 1 reply; 39+ messages in thread From: Пламен Петров @ 2014-04-24 17:19 UTC (permalink / raw) To: 'Marc MERLIN'; +Cc: linux-btrfs > -----Original Message----- > From: Пламен Петров [mailto:plamen@petrovi.no-ip.info] > Sent: Wednesday, April 23, 2014 10:38 PM > To: 'Marc MERLIN' > Cc: 'linux-btrfs@vger.kernel.org' > Subject: RE: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > > -----Original Message----- > > From: Marc MERLIN [mailto:marc@merlins.org] > > Sent: Wednesday, April 23, 2014 10:16 PM > > To: Пламен Петров > > Cc: linux-btrfs@vger.kernel.org > > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 > > or newer? > > > > On Wed, Apr 23, 2014 at 10:06:12PM +0300, Пламен Петров wrote: > > > Just to clarify - I am using a monolithic kernel built from source, > > > and it has all > > the stuff it needs to support built-in, and then some. And no modules. > > > The sources I'm using are the vanilla kernels from Linus and Greg KH > > downloaded from kernel.org. > > > > Ok. > > > > > Check out the attached config I am using - it’s a kernel I'm running > > > on one > > server and a couple of virtual machines. > > > > That's the working .config. > > I suggest you diff that one with the new one you have for 3.14 > > > > > Until now - copying said config and doing a "make oldconfig" or > > > "make > > olddefconfig" and compiling-then-booting worked fine. > > > > This should indeed work, this is what I do too. > > > > So now, we're kind of guessing. To save us all time, could you capture > > a serial console boot from the running 3.13 and then the failing 3.14. > > Well, for the details - see for example here: > https://bugzilla.kernel.org/attachment.cgi?id=133111 > how does a 3.14.1 built the way described earlier fails. > > And for that matter - see the whole bugzilla bug entry - I went on and > bisected this, using the linux-stable git tree, and after that landed me on the > commit that introduces some "shiny new btrfs feature" for 3.14 - I decided > my git bisection has gone wrong. And because I reported it on April 17-th and > since then there has been no activity on the bugzilla entry besides me > updating it - I posted my problem here, for more eyes to see. > I just realized that the l gave no way for identifying the particular bugzilla entry. Here it is: https://bugzilla.kernel.org/show_bug.cgi?id=74261 Sorry about that! --------------------------------- Plamen Petrov ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 17:19 ` Пламен Петров @ 2014-04-24 17:33 ` Marc MERLIN 2014-04-24 17:44 ` Пламен Петров 2014-04-24 18:51 ` Пламен Петров 0 siblings, 2 replies; 39+ messages in thread From: Marc MERLIN @ 2014-04-24 17:33 UTC (permalink / raw) To: Пламен Петров Cc: linux-btrfs On Thu, Apr 24, 2014 at 08:19:21PM +0300, Пламен Петров wrote: > I just realized that the l gave no way for identifying the particular bugzilla entry. Here it is: > https://bugzilla.kernel.org/show_bug.cgi?id=74261 Thanks. But to save us a lot more speculation, can you please try booting a linux system (either initrd, or another one with a non btrfs root), and then trying to mount that filesystem from the command line? Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 17:33 ` Marc MERLIN @ 2014-04-24 17:44 ` Пламен Петров 2014-04-24 18:51 ` Пламен Петров 1 sibling, 0 replies; 39+ messages in thread From: Пламен Петров @ 2014-04-24 17:44 UTC (permalink / raw) To: 'Marc MERLIN'; +Cc: linux-btrfs > -----Original Message----- > From: Marc MERLIN [mailto:marc@merlins.org] > Sent: Thursday, April 24, 2014 8:33 PM > To: Пламен Петров > Cc: linux-btrfs@vger.kernel.org > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > On Thu, Apr 24, 2014 at 08:19:21PM +0300, Пламен Петров wrote: > > I just realized that the l gave no way for identifying the particular bugzilla > entry. Here it is: > > https://bugzilla.kernel.org/show_bug.cgi?id=74261 > > Thanks. > > But to save us a lot more speculation, can you please try booting a linux > system (either initrd, or another one with a non btrfs root), and then trying > to mount that filesystem from the command line? Using 3.14.1 perhaps? I will try to do that now, but if I can't manage to do it today - expect the results tomorrow. One more detail I managed to rule out today is that my problematic filesystems used subvol-other-than-root as default, made like so: $ mount /dev/sda2 /sda2 -o relatime,compress=zlib,subvol=system-main-fs $ btrfs subvolume set-default system-main-fs /sda2 Only using different name for the subvolume. Anyway - its irrelevant. I formatted a fresh root as BTRFS, skipped the above, and tried booting 3.14.1 - result was kernel panic. So different default subvolume or not - its not the problem. --------------------------------- Plamen Petrov ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 17:33 ` Marc MERLIN 2014-04-24 17:44 ` Пламен Петров @ 2014-04-24 18:51 ` Пламен Петров 2014-04-24 19:31 ` Marc MERLIN 2014-04-24 21:06 ` Chris Murphy 1 sibling, 2 replies; 39+ messages in thread From: Пламен Петров @ 2014-04-24 18:51 UTC (permalink / raw) To: 'Marc MERLIN'; +Cc: linux-btrfs [-- Attachment #1: Type: text/plain, Size: 15557 bytes --] > -----Original Message----- > From: Пламен Петров [mailto:plamen@petrovi.no-ip.info] > Sent: Thursday, April 24, 2014 8:44 PM > To: 'Marc MERLIN' > Cc: 'linux-btrfs@vger.kernel.org' > Subject: RE: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > > -----Original Message----- > > From: Marc MERLIN [mailto:marc@merlins.org] > > Sent: Thursday, April 24, 2014 8:33 PM > > To: Пламен Петров > > Cc: linux-btrfs@vger.kernel.org > > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 > > or newer? > > > > On Thu, Apr 24, 2014 at 08:19:21PM +0300, Пламен Петров wrote: > > > I just realized that the l gave no way for identifying the > > > particular bugzilla > > entry. Here it is: > > > https://bugzilla.kernel.org/show_bug.cgi?id=74261 > > > > Thanks. > > > > But to save us a lot more speculation, can you please try booting a > > linux system (either initrd, or another one with a non btrfs root), > > and then trying to mount that filesystem from the command line? > > Using 3.14.1 perhaps? > > I will try to do that now, but if I can't manage to do it today - expect the > results tomorrow. > > One more detail I managed to rule out today is that my problematic > filesystems used subvol-other-than-root as default, made like so: > > $ mount /dev/sda2 /sda2 -o relatime,compress=zlib,subvol=system-main-fs > $ btrfs subvolume set-default system-main-fs /sda2 > > Only using different name for the subvolume. > Anyway - its irrelevant. > I formatted a fresh root as BTRFS, skipped the above, and tried booting > 3.14.1 - result was kernel panic. So different default subvolume or not - its > not the problem. So, here is what I did: My debug VM had: sda sda1 200 MB /boot - ext2 sda2 5 GB / - BTRFS sda3 5 GB / - XFS sda4 One extra partition used for mangling (XFS). sda2 and sda3 were mostly the same, except /etc/fstab, for obvious reasons. I booted 3.14.1 using sda3 as root, and then tried mounting sda2. It went OK, here is what dmesg said: [ 12.412465] Btrfs loaded [ 12.418259] rtc_cmos 00:03: setting system clock to 2014-04-24 21:24:49 UTC (1398374689) [ 12.589585] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input3 [ 12.593662] md: Skipping autodetection of RAID arrays. (raid=autodetect will force) [ 12.622697] XFS (sda3): Mounting Filesystem [ 12.859854] XFS (sda3): Ending clean mount [ 12.860716] VFS: Mounted root (xfs filesystem) on device 8:3. [ 12.877671] devtmpfs: mounted [ 12.878878] Freeing unused kernel memory: 928K (ffffffff81c80000 - ffffffff81d68000) [ 12.879074] Write protecting the kernel read-only data: 12288k [ 12.880894] Freeing unused kernel memory: 280K (ffff8800017ba000 - ffff880001800000) [ 12.885059] Freeing unused kernel memory: 1480K (ffff880001a8e000 - ffff880001c00000) [ 13.260033] mount (1508) used greatest stack depth: 4600 bytes left [ 13.487836] udevd[1517]: starting version 182 [ 13.701783] cdrom_id (1577) used greatest stack depth: 4416 bytes left [ 14.413107] BTRFS: device fsid 2ba08fbc-4b95-46cc-b638-299f16462620 devid 1 transid 22 /dev/sda2 [ 14.579120] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [ 15.297292] hpet1: lost 2 rtc interrupts [ 15.942679] ip (1620) used greatest stack depth: 4352 bytes left [ 15.957207] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 16.052274] random: nonblocking pool is initialized [ 86.490078] BTRFS: device fsid 2ba08fbc-4b95-46cc-b638-299f16462620 devid 1 transid 22 /dev/sda2 [ 86.492947] BTRFS info (device sda2): disk space caching is enabled [ 86.579155] BTRFS: creating UUID tree [ 86.748681] mount (1899) used greatest stack depth: 2560 bytes left At this point I rebooted the VM with 3.13.11 just to verify everything works on the BTRFS sda2, and it did. Here is its dmesg: [ 8.292487] Btrfs loaded [ 8.292663] msgmni has been set to 1978 [ 8.302800] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 8.302991] io scheduler noop registered (default) [ 8.303101] io scheduler deadline registered [ 8.303475] crc32: CRC_LE_BITS = 64, CRC_BE BITS = 64 [ 8.303668] crc32: self tests passed, processed 225944 bytes in 130881 nsec [ 8.303945] crc32c: CRC_LE_BITS = 64 [ 8.304037] crc32c: self tests passed, processed 225944 bytes in 65371 nsec [ 8.519327] crc32_combine: 8373 self tests passed [ 8.736143] crc32c_combine: 8373 self tests passed [ 8.737102] pcieport 0000:00:15.0: irq 40 for MSI/MSI-X [ 8.738366] pcieport 0000:00:15.1: irq 41 for MSI/MSI-X [ 8.739587] pcieport 0000:00:15.2: irq 42 for MSI/MSI-X [ 8.740822] pcieport 0000:00:15.3: irq 43 for MSI/MSI-X [ 8.742007] pcieport 0000:00:15.4: irq 44 for MSI/MSI-X [ 8.743221] pcieport 0000:00:15.5: irq 45 for MSI/MSI-X [ 8.744555] pcieport 0000:00:15.6: irq 46 for MSI/MSI-X [ 8.745774] pcieport 0000:00:15.7: irq 47 for MSI/MSI-X [ 8.747230] pcieport 0000:00:16.0: irq 48 for MSI/MSI-X [ 8.748712] pcieport 0000:00:16.1: irq 49 for MSI/MSI-X [ 8.749967] pcieport 0000:00:16.2: irq 50 for MSI/MSI-X [ 8.751182] pcieport 0000:00:16.3: irq 51 for MSI/MSI-X [ 8.752366] pcieport 0000:00:16.4: irq 52 for MSI/MSI-X [ 8.753599] pcieport 0000:00:16.5: irq 53 for MSI/MSI-X [ 8.754821] pcieport 0000:00:16.6: irq 54 for MSI/MSI-X [ 8.756053] pcieport 0000:00:16.7: irq 55 for MSI/MSI-X [ 8.757243] pcieport 0000:00:17.0: irq 56 for MSI/MSI-X [ 8.758456] pcieport 0000:00:17.1: irq 57 for MSI/MSI-X [ 8.759656] pcieport 0000:00:17.2: irq 58 for MSI/MSI-X [ 8.760871] pcieport 0000:00:17.3: irq 59 for MSI/MSI-X [ 8.762232] pcieport 0000:00:17.4: irq 60 for MSI/MSI-X [ 8.763522] pcieport 0000:00:17.5: irq 61 for MSI/MSI-X [ 8.764798] pcieport 0000:00:17.6: irq 62 for MSI/MSI-X [ 8.765996] pcieport 0000:00:17.7: irq 63 for MSI/MSI-X [ 8.767202] pcieport 0000:00:18.0: irq 64 for MSI/MSI-X [ 8.768443] pcieport 0000:00:18.1: irq 65 for MSI/MSI-X [ 8.769624] pcieport 0000:00:18.2: irq 66 for MSI/MSI-X [ 8.770844] pcieport 0000:00:18.3: irq 67 for MSI/MSI-X [ 8.772031] pcieport 0000:00:18.4: irq 68 for MSI/MSI-X [ 8.773320] pcieport 0000:00:18.5: irq 69 for MSI/MSI-X [ 8.774596] pcieport 0000:00:18.6: irq 70 for MSI/MSI-X [ 8.775810] pcieport 0000:00:18.7: irq 71 for MSI/MSI-X [ 8.778754] ACPI: AC Adapter [ACAD] (on-line) [ 8.779467] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 [ 8.779663] ACPI: Power Button [PWRF] [ 8.783957] xenfs: not registering filesystem on non-xen platform [ 8.787231] Non-volatile memory driver v1.3 [ 8.787428] Linux agpgart interface v0.103 [ 8.788612] agpgart-intel 0000:00:00.0: Intel 440BX Chipset [ 8.790580] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0x0 [ 8.791666] [drm] Initialized drm 1.1.0 20060810 [ 8.809538] brd: module loaded [ 8.819642] loop: module loaded [ 8.819780] HP CISS Driver (v 3.6.26) [ 8.821732] vmw_vmci 0000:00:07.7: Found VMCI PCI device at 0x11080, irq 16 [ 8.821987] vmw_vmci 0000:00:07.7: Using capabilities 0xc [ 8.822319] vmw_vmci 0000:00:07.7: irq 72 for MSI/MSI-X [ 8.822377] vmw_vmci 0000:00:07.7: irq 73 for MSI/MSI-X [ 8.823258] Guest personality initialized and is active [ 8.824045] VMCI host device registered (name=vmci, major=10, minor=62) [ 8.824202] Initialized host personality [ 8.830316] mpt2sas version 16.100.00.00 loaded [ 8.831550] VMware PVSCSI driver - version 1.0.2.0-k [ 8.835267] ata_piix 0000:00:07.1: version 2.13 [ 8.839894] scsi0 : ata_piix [ 8.841344] scsi1 : ata_piix [ 8.842426] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x1060 irq 14 [ 8.842587] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x1068 irq 15 [ 8.845619] bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) [ 8.862876] pcnet32: pcnet32.c:v1.35 21.Apr.2008 tsbogend@alpha.franken.de [ 8.863649] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 8.863799] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 9.025659] ata2.00: ATAPI: VMware Virtual IDE CDROM Drive, 00000001, max UDMA/33 [ 9.065490] ata2.00: configured for UDMA/33 [ 9.066207] scsi 1:0:0:0: CD-ROM NECVMWar VMware IDE CDR10 1.00 PQ: 0 ANSI: 5 [ 9.067759] sr0: scsi3-mmc drive: 1x/1x writer dvd-ram cd/rw xa/form2 cdda tray [ 9.067978] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 9.073651] sr 1:0:0:0: Attached scsi CD-ROM sr0 [ 9.074388] sr 1:0:0:0: Attached scsi generic sg0 type 5 [ 9.305312] e1000 0000:02:00.0 eth0: (PCI:66MHz:32-bit) 00:0c:29:55:5f:81 [ 9.305558] e1000 0000:02:00.0 eth0: Intel(R) PRO/1000 Network Connection [ 9.306253] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 9.306474] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. [ 9.307179] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.0.5-k [ 9.307424] igb: Copyright (c) 2007-2013 Intel Corporation. [ 9.309118] VMware vmxnet3 virtual NIC driver - version 1.2.0.0-k-NAPI [ 9.309857] Fusion MPT base driver 3.04.20 [ 9.310048] Copyright (c) 1999-2008 LSI Corporation [ 9.310274] Fusion MPT SPI Host driver 3.04.20 [ 9.311661] mptbase: ioc0: Initiating bringup [ 9.486032] ioc0: LSI53C1030 B0: Capabilities={Initiator} [ 9.888306] scsi2 : ioc0: LSI53C1030 B0, FwRev=01032920h, Ports=1, MaxQ=128, IRQ=17 [ 10.165079] scsi 2:0:0:0: Direct-Access VMware, VMware Virtual S 1.0 PQ: 0 ANSI: 2 [ 10.165726] scsi target2:0:0: Beginning Domain Validation [ 10.168562] scsi target2:0:0: Domain Validation skipping write tests [ 10.169019] scsi target2:0:0: Ending Domain Validation [ 10.169571] scsi target2:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127) [ 10.172712] sd 2:0:0:0: [sda] 25165824 512-byte logical blocks: (12.8 GB/12.0 GiB) [ 10.173562] sd 2:0:0:0: [sda] Write Protect is off [ 10.173957] sd 2:0:0:0: [sda] Mode Sense: 61 00 00 00 [ 10.174196] sd 2:0:0:0: [sda] Cache data unavailable [ 10.174645] sd 2:0:0:0: [sda] Assuming drive cache: write through [ 10.176514] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 10.177047] sd 2:0:0:0: [sda] Cache data unavailable [ 10.177052] sd 2:0:0:0: [sda] Assuming drive cache: write through [ 10.184581] Fusion MPT FC Host driver 3.04.20 [ 10.185965] Fusion MPT SAS Host driver 3.04.20 [ 10.187431] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 10.187921] ehci-pci: EHCI PCI platform driver [ 10.189278] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 10.189759] ohci-pci: OHCI PCI platform driver [ 10.191061] uhci_hcd: USB Universal Host Controller Interface driver [ 10.194583] i8042: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MOUS] at 0x60,0x64 irq 1,12 [ 10.197335] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 10.197572] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 10.198744] sda: sda1 sda2 sda3 sda4 [ 10.199255] mousedev: PS/2 mouse device common for all mice [ 10.215071] sd 2:0:0:0: [sda] Cache data unavailable [ 10.215284] sd 2:0:0:0: [sda] Assuming drive cache: write through [ 10.215608] sd 2:0:0:0: [sda] Attached SCSI disk [ 10.223044] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 [ 10.223530] rtc_cmos 00:03: alarms up to one month, y3k, 114 bytes nvram, hpet irqs [ 10.225055] md: linear personality registered for level -1 [ 10.225498] md: raid0 personality registered for level 0 [ 10.225619] md: raid1 personality registered for level 1 [ 10.225740] md: raid10 personality registered for level 10 [ 10.225960] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1 [ 10.226287] md: raid6 personality registered for level 6 [ 10.226427] md: raid5 personality registered for level 5 [ 10.226560] md: raid4 personality registered for level 4 [ 10.229500] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com [ 10.229788] device-mapper: raid: Loading target version 1.5.2 [ 10.236443] usbcore: registered new interface driver usbhid [ 10.236590] usbhid: USB HID core driver [ 10.236776] Netfilter messages via NETLINK v0.30. [ 10.236901] nf_conntrack version 0.5.0 (7913 buckets, 31652 max) [ 10.237587] ctnetlink v0.93: registering with nfnetlink. [ 10.237883] ip_tables: (C) 2000-2006 Netfilter Core Team [ 10.238052] TCP: cubic registered [ 10.238142] TCP: vegas registered [ 10.238236] TCP: veno registered [ 10.238324] TCP: yeah registered [ 10.238410] Initializing XFRM netlink socket [ 10.238517] NET: Registered protocol family 17 [ 10.238632] Key type dns_resolver registered [ 10.250310] rtc_cmos 00:03: setting system clock to 2014-04-24 21:32:28 UTC (1398375148) [ 10.434122] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input3 [ 10.437178] md: Skipping autodetection of RAID arrays. (raid=autodetect will force) [ 10.469491] btrfs: device fsid 2ba08fbc-4b95-46cc-b638-299f16462620 devid 1 transid 25 /dev/root [ 10.472644] btrfs: disk space caching is enabled [ 10.629425] VFS: Mounted root (btrfs filesystem) on device 0:14. [ 10.630271] devtmpfs: mounted [ 10.634102] Freeing unused kernel memory: 916K (ffffffff81c7e000 - ffffffff81d63000) [ 10.634723] Write protecting the kernel read-only data: 12288k [ 10.639516] Freeing unused kernel memory: 376K (ffff8800017a2000 - ffff880001800000) [ 10.648068] Freeing unused kernel memory: 1504K (ffff880001a88000 - ffff880001c00000) [ 10.990350] mount (1131) used greatest stack depth: 4416 bytes left [ 11.082048] udevd[1139]: starting version 182 [ 11.082112] udevd (1138) used greatest stack depth: 4408 bytes left [ 11.866053] btrfs: device fsid 2ba08fbc-4b95-46cc-b638-299f16462620 devid 1 transid 25 /dev/sda2 [ 11.867495] btrfs (1196) used greatest stack depth: 4320 bytes left [ 12.307431] btrfs: use zlib compression [ 12.307549] btrfs: disk space caching is enabled [ 12.406078] mount (1197) used greatest stack depth: 3200 bytes left [ 12.522659] btrfs: use zlib compression [ 12.523038] btrfs: disk space caching is enabled [ 12.601811] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [ 15.629161] hpet1: lost 1 rtc interrupts [ 16.483149] random: nonblocking pool is initialized [ 17.126828] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 18.470646] cc1 (1271) used greatest stack depth: 3032 bytes left >From the above - the first obvious thing is that with 3.13.11 BTRFS gets loaded much earlier in the boot process - that is why the second dmesg dump is much larger, and both start at " Btrfs loaded" - mind you. Next was booting the BTRFS sda2 with 3.14.1. Sadly, it panicked again. So, no dmesg dump - just a screenshot. See the attached file. So, what got changed during the 3.14 merge window, that messed up booting for BTRFS partitions? Should I try building an "allyesconfig" kernel, in case something is messed up with my kernel .configs? What do you think guys and galls? Anything you want me try - this is entirely disposable VM now, so I'll gladly try everything you ask... --------------------------------- Plamen Petrov [-- Attachment #2: debug-vm-panic.png --] [-- Type: image/png, Size: 46408 bytes --] ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 18:51 ` Пламен Петров @ 2014-04-24 19:31 ` Marc MERLIN 2014-04-24 20:26 ` Пламен Петров 2014-04-24 21:06 ` Chris Murphy 1 sibling, 1 reply; 39+ messages in thread From: Marc MERLIN @ 2014-04-24 19:31 UTC (permalink / raw) To: Пламен Петров Cc: linux-btrfs On Thu, Apr 24, 2014 at 09:51:30PM +0300, Пламен Петров wrote: > So, here is what I did: > My debug VM had: > sda > sda1 200 MB /boot - ext2 > sda2 5 GB / - BTRFS > sda3 5 GB / - XFS > sda4 One extra partition used for mangling (XFS). > > sda2 and sda3 were mostly the same, except /etc/fstab, for obvious reasons. > > I booted 3.14.1 using sda3 as root, and then tried mounting sda2. It went OK, here is what dmesg said: > [ 12.412465] Btrfs loaded > [ 86.490078] BTRFS: device fsid 2ba08fbc-4b95-46cc-b638-299f16462620 devid 1 transid 22 /dev/sda2 > [ 86.492947] BTRFS info (device sda2): disk space caching is enabled > [ 86.579155] BTRFS: creating UUID tree > [ 86.748681] mount (1899) used greatest stack depth: 2560 bytes left Ok, that's good news. It indeed rules out that your new kernel cannot mount an older btrfs filesystem. At this point, you may have a problem with the device not being available when btrfs tries to mount it. > From the above - the first obvious thing is that with 3.13.11 BTRFS gets loaded much earlier in the boot process - that is why the second dmesg dump is much larger, and both start at " Btrfs loaded" - mind you. > > Next was booting the BTRFS sda2 with 3.14.1. > Sadly, it panicked again. So, no dmesg dump - just a screenshot. See the attached file. > So, what got changed during the 3.14 merge window, that messed up booting for BTRFS partitions? > Should I try building an "allyesconfig" kernel, in case something is messed up with my kernel .configs? > What do you think guys and galls? > Anything you want me try - this is entirely disposable VM now, so I'll gladly try everything you ask... So, I'm not sure how many people use btrfs built it vs as a module. Clearly the code works for mounting your partition, but when built in the kernel, there seems to be a timing issue. For reference, you said this was the bug where you found the CL that causes this change: https://bugzilla.kernel.org/show_bug.cgi?id=74261 You said using rootwait as recommended by Chris Mason did not help. What output are you getting when you use this? By the way, you should be able to define a pseudo serial port in your VM and specify something like console=tty0 console=ttyS0,38400n8 on your boot command line. This will give you serial console output in text that you can cut/paste/diff Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 19:31 ` Marc MERLIN @ 2014-04-24 20:26 ` Пламен Петров 2014-04-24 21:47 ` Chris Murphy 0 siblings, 1 reply; 39+ messages in thread From: Пламен Петров @ 2014-04-24 20:26 UTC (permalink / raw) To: 'Marc MERLIN'; +Cc: linux-btrfs > -----Original Message----- > From: Marc MERLIN [mailto:marc@merlins.org] > Sent: Thursday, April 24, 2014 10:31 PM > To: Пламен Петров > Cc: linux-btrfs@vger.kernel.org > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > On Thu, Apr 24, 2014 at 09:51:30PM +0300, Пламен Петров wrote: > > So, here is what I did: > > My debug VM had: > > sda > > sda1 200 MB /boot - ext2 > > sda2 5 GB / - BTRFS > > sda3 5 GB / - XFS > > sda4 One extra partition used for mangling (XFS). > > > > sda2 and sda3 were mostly the same, except /etc/fstab, for obvious > reasons. > > > > I booted 3.14.1 using sda3 as root, and then tried mounting sda2. It went > OK, here is what dmesg said: > > [ 12.412465] Btrfs loaded > > [ 86.490078] BTRFS: device fsid 2ba08fbc-4b95-46cc-b638-299f16462620 > devid 1 transid 22 /dev/sda2 > > [ 86.492947] BTRFS info (device sda2): disk space caching is enabled > > [ 86.579155] BTRFS: creating UUID tree > > [ 86.748681] mount (1899) used greatest stack depth: 2560 bytes left > > Ok, that's good news. It indeed rules out that your new kernel cannot mount > an older btrfs filesystem. > > At this point, you may have a problem with the device not being available > when btrfs tries to mount it. Need a way to pinpoint the actual problem then. > > > From the above - the first obvious thing is that with 3.13.11 BTRFS gets > loaded much earlier in the boot process - that is why the second dmesg > dump is much larger, and both start at " Btrfs loaded" - mind you. > > > > Next was booting the BTRFS sda2 with 3.14.1. > > Sadly, it panicked again. So, no dmesg dump - just a screenshot. See the > attached file. > > So, what got changed during the 3.14 merge window, that messed up > booting for BTRFS partitions? > > Should I try building an "allyesconfig" kernel, in case something is messed > up with my kernel .configs? > > What do you think guys and galls? > > Anything you want me try - this is entirely disposable VM now, so I'll gladly > try everything you ask... > > So, I'm not sure how many people use btrfs built it vs as a module. Clearly the > code works for mounting your partition, but when built in the kernel, there > seems to be a timing issue. Yeah, and an issue that just popped up with kernels >= 3.14. If memory serves - I started using BTRFS on linux 3.6.x, and since then I followed exactly the same method of upgrading the kernel - described in this thread and in the bugzilla entry - and it always "Just Works" TM! > > For reference, you said this was the bug where you found the CL that causes > this change: > https://bugzilla.kernel.org/show_bug.cgi?id=74261 > > You said using rootwait as recommended by Chris Mason did not help. > > What output are you getting when you use this? The image file attached to my previous mail applies to both rootwait and no-rootwait cases. Result is always a kernel panic for 3.14.x on BTRFS root. All other filesystem/kernel combos just work either way. > > By the way, you should be able to define a pseudo serial port in your VM and > specify something like > console=tty0 console=ttyS0,38400n8 > on your boot command line. > This will give you serial console output in text that you can cut/paste/diff I will try and use this the next time. Thanks! --------------------------------- Plamen Petrov ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 20:26 ` Пламен Петров @ 2014-04-24 21:47 ` Chris Murphy 0 siblings, 0 replies; 39+ messages in thread From: Chris Murphy @ 2014-04-24 21:47 UTC (permalink / raw) To: Пламен Петров Cc: 'Marc MERLIN', linux-btrfs On Apr 24, 2014, at 2:26 PM, Пламен Петров <plamen@petrovi.no-ip.info> wrote: >> -----Original Message----- >> From: Marc MERLIN [mailto:marc@merlins.org] >> You said using rootwait as recommended by Chris Mason did not help. >> >> What output are you getting when you use this? > > The image file attached to my previous mail applies to both rootwait and no-rootwait cases. Result is always a kernel panic for 3.14.x on BTRFS root. All other filesystem/kernel combos just work either way. rootwait should mean it waits indefinitely for rootfs to appear, so why does it still kernel panic? Is the root= parameter using UUID? If not can you try UUID instead of /dev/sda2? For Btrfs this is still the volume UUID, not subvolume UUID. Chris Murphy ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 18:51 ` Пламен Петров 2014-04-24 19:31 ` Marc MERLIN @ 2014-04-24 21:06 ` Chris Murphy 2014-04-24 21:23 ` Пламен Петров [not found] ` <000c01cf600b$b01f6cf0$105e46d0$@petrovi.no-ip.info> 1 sibling, 2 replies; 39+ messages in thread From: Chris Murphy @ 2014-04-24 21:06 UTC (permalink / raw) To: Пламен Петров Cc: 'Marc MERLIN', linux-btrfs On Apr 24, 2014, at 12:51 PM, Пламен Петров <plamen@petrovi.no-ip.info> wrote: > > I booted 3.14.1 using sda3 as root, and then tried mounting sda2. It went OK, here is what dmesg said: > [ 12.412465] Btrfs loaded For me, with Btrfs not compiled in the kernel, and with an initramfs, on SSD I get Btrfs loaded at 2.4 seconds. On HDD, it still happens by 6-7 seconds. So without an initrd and with btrfs compiled into the kernel I'd expect to see Btrfs loaded before 12.4 seconds. Is this an SSD? Or HDD, or hardware raid? I'd like to see the dmesg from the beginning, until "Btrfs Loaded", for both 3.13.11 and 3.14.1 (via serial console output). I think the clue is in the part before Btrfs loaded. Also can you post a diff of the config file for the working 3.13.11 and not working 3.14.1 kernels? Chris Murphy ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 21:06 ` Chris Murphy @ 2014-04-24 21:23 ` Пламен Петров [not found] ` <000c01cf600b$b01f6cf0$105e46d0$@petrovi.no-ip.info> 1 sibling, 0 replies; 39+ messages in thread From: Пламен Петров @ 2014-04-24 21:23 UTC (permalink / raw) To: 'Chris Murphy'; +Cc: 'Marc MERLIN', linux-btrfs [-- Attachment #1: Type: text/plain, Size: 1862 bytes --] > -----Original Message----- > From: Chris Murphy [mailto:lists@colorremedies.com] > Sent: Friday, April 25, 2014 12:06 AM > To: Пламен Петров > Cc: 'Marc MERLIN'; linux-btrfs@vger.kernel.org > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > > On Apr 24, 2014, at 12:51 PM, Пламен Петров <plamen@petrovi.no-ip.info> > wrote: > > > > I booted 3.14.1 using sda3 as root, and then tried mounting sda2. It went > OK, here is what dmesg said: > > [ 12.412465] Btrfs loaded > > For me, with Btrfs not compiled in the kernel, and with an initramfs, on SSD I > get Btrfs loaded at 2.4 seconds. On HDD, it still happens by 6-7 seconds. > Well, the actual time doesn't matter - I use this monolithic kernel on both virtual machines as well as a physical server. Up until 3.13.x this arrangement worked flawlessly, now for 3.14.x - everything will be the same except me using BTRFS... > So without an initrd and with btrfs compiled into the kernel I'd expect to see > Btrfs loaded before 12.4 seconds. Is this an SSD? Or HDD, or hardware raid? The most recent dmesg dumps were from a virtual machine. > > I'd like to see the dmesg from the beginning, until "Btrfs Loaded", for both > 3.13.11 and 3.14.1 (via serial console output). I think the clue is in the part > before Btrfs loaded. I will try to provide these, but it will have to wait for tomorrow as currently my monolithic kernel .config does not support serial ports, so I will have to reconfigure, recompile both 3.13.x and 3.14.x to test them and provide the requested data. > > Also can you post a diff of the config file for the working 3.13.11 and not > working 3.14.1 kernels? The requested diff was posted earlier, reattaching once more. --------------------------------- Plamen Petrov [-- Attachment #2: diff-3.14.1-to-3.13.11.txt --] [-- Type: text/plain, Size: 1916 bytes --] diff config-v3.14.1-mix64 config-v3.13.11-mix64 3c3 < # Linux/x86 3.14.1 Kernel Configuration --- > # Linux/x86 3.13.11 Kernel Configuration 155a156 > # CONFIG_UIDGID_STRICT_TYPE_CHECKS is not set 230,234d230 < CONFIG_HAVE_CC_STACKPROTECTOR=y < # CONFIG_CC_STACKPROTECTOR is not set < CONFIG_CC_STACKPROTECTOR_NONE=y < # CONFIG_CC_STACKPROTECTOR_REGULAR is not set < # CONFIG_CC_STACKPROTECTOR_STRONG is not set 309d304 < # CONFIG_XEN_PVH is not set 358a354 > CONFIG_MICROCODE_INTEL_LIB=y 407d402 < # CONFIG_ZSMALLOC is not set 419a415 > # CONFIG_CC_STACKPROTECTOR is not set 430d425 < # CONFIG_RANDOMIZE_BASE is not set 762,763d756 < # CONFIG_NET_SCH_HHF is not set < # CONFIG_NET_SCH_PIE is not set 794,795c787 < # CONFIG_CGROUP_NET_PRIO is not set < # CONFIG_CGROUP_NET_CLASSID is not set --- > # CONFIG_NETPRIO_CGROUP is not set 944d935 < # CONFIG_GENWQE is not set 997a989 > # CONFIG_SCSI_AIC7XXX_OLD is not set 1158d1149 < CONFIG_DM_BUFIO=y 1256d1246 < # CONFIG_I40EVF is not set 1489d1478 < CONFIG_ARCH_MIGHT_HAVE_PC_SERIO=y 1608d1596 < # CONFIG_I2C_DESIGNWARE_PLATFORM is not set 1622d1609 < # CONFIG_I2C_ROBOTFUZZ_OSIF is not set 1807a1795 > # CONFIG_CPU_THERMAL is not set 1811d1798 < # CONFIG_ACPI_INT3403_THERMAL is not set 1851d1837 < # CONFIG_MFD_MAX14577 is not set 1872d1857 < # CONFIG_MFD_LP3943 is not set 1904d1888 < CONFIG_INTEL_GTT=y 1928d1911 < # CONFIG_DRM_I915_UMS is not set 1940d1922 < # CONFIG_DRM_BOCHS is not set 1978d1959 < # CONFIG_FB_OPENCORES is not set 2080a2062 > # CONFIG_HID_LOGITECH_DJ is not set 2184d2165 < # CONFIG_USB_MUSB_HDRC is not set 2186d2166 < # CONFIG_USB_DWC2 is not set 2225d2204 < # CONFIG_USB_OTG_FSM is not set 2269d2247 < # CONFIG_RTC_DRV_ISL12057 is not set 2403d2380 < CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y 2450a2428 > CONFIG_GENERIC_ACL=y 2604d2581 < CONFIG_PANIC_TIMEOUT=0 ^ permalink raw reply [flat|nested] 39+ messages in thread
[parent not found: <000c01cf600b$b01f6cf0$105e46d0$@petrovi.no-ip.info>]
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? [not found] ` <000c01cf600b$b01f6cf0$105e46d0$@petrovi.no-ip.info> @ 2014-04-24 23:07 ` Marc MERLIN 2014-04-25 0:04 ` Chris Murphy 0 siblings, 1 reply; 39+ messages in thread From: Marc MERLIN @ 2014-04-24 23:07 UTC (permalink / raw) To: Пламен Петров Cc: 'Chris Murphy', linux-btrfs On Fri, Apr 25, 2014 at 01:22:32AM +0300, Пламен Петров wrote: > > -----Original Message----- > > From: Chris Murphy [mailto:lists@colorremedies.com] > > Sent: Friday, April 25, 2014 12:06 AM > > To: Пламен Петров > > Cc: 'Marc MERLIN'; linux-btrfs@vger.kernel.org > > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or > > newer? > > > > > > On Apr 24, 2014, at 12:51 PM, Пламен Петров <plamen@petrovi.no-ip.info> > > wrote: > > > > > > I booted 3.14.1 using sda3 as root, and then tried mounting sda2. It went > > OK, here is what dmesg said: > > > [ 12.412465] Btrfs loaded > > > > For me, with Btrfs not compiled in the kernel, and with an initramfs, on SSD I > > get Btrfs loaded at 2.4 seconds. On HDD, it still happens by 6-7 seconds. > > > > So without an initrd and with btrfs compiled into the kernel I'd expect to see > > Btrfs loaded before 12.4 seconds. Is this an SSD? Or HDD, or hardware raid? > > > > I'd like to see the dmesg from the beginning, until "Btrfs Loaded", for both > > 3.13.11 and 3.14.1 (via serial console output). I think the clue is in the part > > before Btrfs loaded. > > > > Also can you post a diff of the config file for the working 3.13.11 and not > > working 3.14.1 kernels? > > > > Attached to this mail find the requested kernel .config files, the result of "duff -u" between them, as well as the output to serial console of both kernels 3.13.11 and 3.14.1 compiled with attached configs. Thanks for the serial console logs. I see that you didn't add rootwait to the command line of your 3.14 boot. Please do that so that we can see that output. I'm pasting a diff of them for the benefit of others. The obvious things to me are: In 3.13 the device appears after btrfs is loaded: Btrfs loaded (...) scsi2 : ioc0: LSI53C1030 B0, FwRev=01032920h, Ports=1, MaxQ=128, IRQ=17 scsi 2:0:0:0: Direct-Access VMware, VMware Virtual S 1.0 PQ: 0 ANSI: 2 scsi target2:0:0: Beginning Domain Validation scsi target2:0:0: Domain Validation skipping write tests scsi target2:0:0: Ending Domain Validation scsi target2:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127) sd 2:0:0:0: [sda] 25165824 512-byte logical blocks: (12.8 GB/12.0 GiB) sd 2:0:0:0: [sda] Write Protect is off sd 2:0:0:0: [sda] Cache data unavailable sd 2:0:0:0: [sda] Assuming drive cache: write through sd 2:0:0:0: [sda] Cache data unavailable sd 2:0:0:0: [sda] Assuming drive cache: write through sd 2:0:0:0: Attached scsi generic sg1 type 0 Fusion MPT FC Host driver 3.04.20 Fusion MPT SAS Host driver 3.04.20 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-pci: EHCI PCI platform driver ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ohci-pci: OHCI PCI platform driver sda: sda1 sda2 sda3 sda4 In 3.14 the device shows up before btrfs is loaded: sd 2:0:0:0: [sda] Cache data unavailable sd 2:0:0:0: [sda] Assuming drive cache: write through sd 2:0:0:0: [sda] Attached SCSI disk (...) Btrfs loaded --- dmesg-3.13.11-mix64-serial.txt 2014-04-24 16:00:44.442491091 -0700 +++ dmesg-3.14.1-mix64-serial.txt 2014-04-24 16:00:50.394404267 -0700 @@ -1,7 +1,7 @@ Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Initializing cgroup subsys cpuacct -Linux version 3.13.11-mix64 (root@crux) (gcc version 4.7.3 (CRUX-x86_64-multilib) ) #1 SMP Fri Apr 25 00:59:11 EEST 2014 +Linux version 3.14.1-mix64 (root@crux) (gcc version 4.7.3 (CRUX-x86_64-multilib) ) #1 SMP Fri Apr 25 00:31:28 EEST 2014 Command line: rw root=/dev/sda2 vga=6 raid=noautodetect console=ttyS0,9600n8 console=tty0 e820: BIOS-provided physical RAM map: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable @@ -190,7 +190,7 @@ e820: [mem 0x40000000-0xefffffff] available for PCI devices Booting paravirtualized kernel on bare hardware setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1 -PERCPU: Embedded 25 pages/cpu @ffff88003fc00000 s80000 r0 d22400 u262144 +PERCPU: Embedded 25 pages/cpu @ffff88003fc00000 s80192 r0 d22208 u262144 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 257897 Kernel command line: rw root=/dev/sda2 vga=6 raid=noautodetect console=ttyS0,9600n8 console=tty0 PID hash table entries: 4096 (order: 3, 32768 bytes) @@ -198,7 +198,7 @@ Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Checking aperture... No AGP bridge found -Memory: 1012808K/1048056K available (7848K kernel code, 519K rwdata, 2604K rodata, 920K init, 2572K bss, 35248K reserved) +Memory: 1012780K/1048056K available (7943K kernel code, 527K rwdata, 2628K rodata, 932K init, 2580K bss, 35276K reserved) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 Hierarchical RCU implementation. CONFIG_RCU_FANOUT set to non-default value of 32 @@ -210,16 +210,16 @@ tsc: Detected 3000.079 MHz processor Calibrating delay loop (skipped) preset value.. 6000.15 BogoMIPS (lpj=30000790) pid_max: default: 32768 minimum: 301 +ACPI: Core revision 20131218 +ACPI: All ACPI Tables successfully acquired Security Framework initialized Mount-cache hash table entries: 2048 (order: 2, 16384 bytes) Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes) Initializing cgroup subsys freezer mce: CPU supports 0 MCE banks Last level iTLB entries: 4KB 512, 2MB 16, 4MB 8 -Last level dTLB entries: 4KB 512, 2MB 128, 4MB 64 -tlb_flushall_shift: 4 -ACPI: Core revision 20131115 -ACPI: All ACPI Tables successfully acquired +Last level dTLB entries: 4KB 512, 2MB 128, 4MB 64, 1GB 0 +tlb_flushall_shift: 6 ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 smpboot: CPU0: AMD Athlon(tm) II X4 640 Processor (fam: 10, model: 05, stepping: 03) Performance Events: AMD PMU driver. @@ -236,22 +236,22 @@ devtmpfs: initialized kworker/u16:0 (14) used greatest stack depth: 6248 bytes left xor: measuring software checksum speed - prefetch64-sse: 12214.400 MB/sec - generic_sse: 11586.000 MB/sec -xor: using function: prefetch64-sse (12214.400 MB/sec) + prefetch64-sse: 12244.000 MB/sec + generic_sse: 11621.200 MB/sec +xor: using function: prefetch64-sse (12244.000 MB/sec) NET: Registered protocol family 16 -kworker/u16:0 (24) used greatest stack depth: 5832 bytes left cpuidle: using governor ladder cpuidle: using governor menu ACPI: bus type PCI registered PCI: MMCONFIG for domain 0000 [bus 00-7f] at [mem 0xf0000000-0xf7ffffff] (base 0xf0000000) PCI: MMCONFIG at [mem 0xf0000000-0xf7ffffff] reserved in E820 PCI: Using configuration type 1 for base access +kworker/u16:0 (42) used greatest stack depth: 5832 bytes left bio: create slab <bio-0> at 0 -raid6: sse2x1 4044 MB/s -raid6: sse2x2 7065 MB/s -raid6: sse2x4 7603 MB/s -raid6: using algorithm sse2x4 (7603 MB/s) +raid6: sse2x1 3955 MB/s +raid6: sse2x2 6623 MB/s +raid6: sse2x4 7560 MB/s +raid6: using algorithm sse2x4 (7560 MB/s) raid6: using intx1 recovery algorithm ACPI: Added _OSI(Module Device) ACPI: Added _OSI(Processor Device) @@ -557,19 +557,18 @@ PCLMULQDQ-NI instructions are not detected. sha256_ssse3: Neither AVX nor SSSE3 is available/usable. sha512_ssse3: Neither AVX nor SSSE3 is available/usable. +futex hash table entries: 2048 (order: 5, 131072 bytes) HugeTLB registered 2 MB page size, pre-allocated 0 pages fuse init (API version 7.22) SGI XFS with security attributes, large block/inode numbers, no debug enabled -bio: create slab <bio-1> at 1 -Btrfs loaded msgmni has been set to 1978 Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) io scheduler noop registered (default) io scheduler deadline registered crc32: CRC_LE_BITS = 64, CRC_BE BITS = 64 -crc32: self tests passed, processed 225944 bytes in 130914 nsec +crc32: self tests passed, processed 225944 bytes in 131092 nsec crc32c: CRC_LE_BITS = 64 -crc32c: self tests passed, processed 225944 bytes in 86154 nsec +crc32c: self tests passed, processed 225944 bytes in 65503 nsec crc32_combine: 8373 self tests passed crc32c_combine: 8373 self tests passed ACPI: AC Adapter [ACAD] (on-line) @@ -609,13 +608,13 @@ e1000e: Copyright(c) 1999 - 2013 Intel Corporation. igb: Intel(R) Gigabit Ethernet Network Driver - version 5.0.5-k igb: Copyright (c) 2007-2013 Intel Corporation. -VMware vmxnet3 virtual NIC driver - version 1.2.0.0-k-NAPI ata2.00: configured for UDMA/33 +VMware vmxnet3 virtual NIC driver - version 1.2.0.0-k-NAPI Fusion MPT base driver 3.04.20 Copyright (c) 1999-2008 LSI Corporation Fusion MPT SPI Host driver 3.04.20 -mptbase: ioc0: Initiating bringup scsi 1:0:0:0: CD-ROM NECVMWar VMware IDE CDR10 1.00 PQ: 0 ANSI: 5 +mptbase: ioc0: Initiating bringup sr0: scsi3-mmc drive: 1x/1x writer dvd-ram cd/rw xa/form2 cdda tray cdrom: Uniform CD-ROM driver Revision: 3.20 sr 1:0:0:0: Attached scsi generic sg0 type 5 @@ -639,15 +638,15 @@ ehci-pci: EHCI PCI platform driver ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ohci-pci: OHCI PCI platform driver - sda: sda1 sda2 sda3 sda4 uhci_hcd: USB Universal Host Controller Interface driver i8042: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MOUS] at 0x60,0x64 irq 1,12 + sda: sda1 sda2 sda3 sda4 serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 +mousedev: PS/2 mouse device common for all mice sd 2:0:0:0: [sda] Cache data unavailable sd 2:0:0:0: [sda] Assuming drive cache: write through sd 2:0:0:0: [sda] Attached SCSI disk -mousedev: PS/2 mouse device common for all mice rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 rtc_cmos 00:03: alarms up to one month, y3k, 114 bytes nvram, hpet irqs md: linear personality registered for level -1 @@ -673,27 +672,35 @@ Initializing XFRM netlink socket NET: Registered protocol family 17 Key type dns_resolver registered -rtc_cmos 00:03: setting system clock to 2014-04-25 01:12:53 UTC (1398388373) +bio: create slab <bio-1> at 1 +Btrfs loaded +rtc_cmos 00:03: setting system clock to 2014-04-25 00:51:01 UTC (1398387061) input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input3 md: Skipping autodetection of RAID arrays. (raid=autodetect will force) -btrfs: device fsid 2ba08fbc-4b95-46cc-b638-299f16462620 devid 1 transid 74 /dev/root -btrfs: disk space caching is enabled -VFS: Mounted root (btrfs filesystem) on device 0:14. -devtmpfs: mounted -Freeing unused kernel memory: 920K (ffffffff81c83000 - ffffffff81d69000) -Write protecting the kernel read-only data: 12288k -Freeing unused kernel memory: 332K (ffff8800017ad000 - ffff880001800000) -Freeing unused kernel memory: 1492K (ffff880001a8b000 - ffff880001c00000) -mount (1108) used greatest stack depth: 4416 bytes left -udevd (1115) used greatest stack depth: 4400 bytes left -udevd[1116]: starting version 182 -udevadm (1117) used greatest stack depth: 4328 bytes left -btrfs: device fsid 2ba08fbc-4b95-46cc-b638-299f16462620 devid 1 transid 74 /dev/sda2 -btrfs (1175) used greatest stack depth: 4320 bytes left -btrfs: use zlib compression -btrfs: disk space caching is enabled -mount (1176) used greatest stack depth: 4144 bytes left -btrfs: use zlib compression -btrfs: disk space caching is enabled -EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) -rc (1107) used greatest stack depth: 4096 bytes left +VFS: Cannot open root device "sda2" or unknown-block(8,2): error -38 +Please append a correct "root=" boot option; here are the available partitions: +0b00 1048575 sr0 driver: sr +0800 12582912 sda driver: sd + 0801 204800 sda1 00061e1d-01 + 0802 4703232 sda2 00061e1d-02 + 0803 4726784 sda3 00061e1d-03 + 0804 2947072 sda4 00061e1d-04 +Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2) +CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.1-mix64 #1 +Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/31/2013 + 0000000000008000 ffff88003f8e1dc8 ffffffff817b4c00 0000000000000001 + ffffffff819e9650 ffff88003f8e1e48 ffffffff817b05f3 ffffffff81c37d40 + ffff880000000010 ffff88003f8e1e58 ffff88003f8e1df8 0000000034616473 +Call Trace: + [<ffffffff817b4c00>] dump_stack+0x46/0x58 + [<ffffffff817b05f3>] panic+0xbc/0x1ba + [<ffffffff81c9a3e5>] mount_block_root+0x1f4/0x292 + [<ffffffff81c9a5f9>] mount_root+0x57/0x5b + [<ffffffff81c9a75f>] prepare_namespace+0x162/0x19b + [<ffffffff81c9a117>] kernel_init_freeable+0x1df/0x1ef + [<ffffffff81c99894>] ? do_early_param+0x8c/0x8c + [<ffffffff817ab480>] ? rest_init+0x70/0x70 + [<ffffffff817ab489>] kernel_init+0x9/0xf0 + [<ffffffff817bda8c>] ret_from_fork+0x7c/0xb0 + [<ffffffff817ab480>] ? rest_init+0x70/0x70 +Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff) -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 23:07 ` Marc MERLIN @ 2014-04-25 0:04 ` Chris Murphy 2014-04-25 0:08 ` Chris Mason 2014-04-25 5:03 ` Пламен Петров 0 siblings, 2 replies; 39+ messages in thread From: Chris Murphy @ 2014-04-25 0:04 UTC (permalink / raw) To: Marc MERLIN Cc: Пламен Петров, linux-btrfs On Apr 24, 2014, at 5:07 PM, Marc MERLIN <marc@merlins.org> wrote: > > > In 3.14 the device shows up before btrfs is loaded: > sd 2:0:0:0: [sda] Cache data unavailable > sd 2:0:0:0: [sda] Assuming drive cache: write through > sd 2:0:0:0: [sda] Attached SCSI disk > (...) > Btrfs loaded Same for me though, and I can boot. [ 0.693215] ata1.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133 [ 0.693799] ata1.00: 167772160 sectors, multi 128: LBA48 NCQ (depth 31/32) [ 0.694153] ata1.00: configured for UDMA/133 [ 0.695475] scsi 0:0:0:0: Direct-Access ATA VBOX HARDDISK 1.0 PQ: 0 ANSI: 5 [ 0.699386] sd 0:0:0:0: [sda] 167772160 512-byte logical blocks: (85.8 GB/80.0 GiB) [ 0.699443] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 0.700604] sd 0:0:0:0: [sda] Write Protect is off [ 0.701151] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 0.701187] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 0.707841] sda: sda1 sda2 sda3 [ 0.709846] sd 0:0:0:0: [sda] Attached SCSI disk (…) [ 2.380090] bio: create slab <bio-1> at 1 [ 2.384645] Btrfs loaded So I don't think the order is it. The biggest difference I'm seeing between the 3.13.11 and 3.14.1 dmesg's provided: 3.13.11: [ 1.861740] bio: create slab <bio-1> at 1 [ 1.863389] Btrfs loaded 3.14.1: [ 3.949312] bio: create slab <bio-1> at 1 [ 3.950942] Btrfs loaded It's happening much later, and it's right at this point VFS complains: [ 4.182603] VFS: Cannot open root device "sda2" or unknown-block(8,2): error -38 The 8,2 message is consistent with the kernel not knowing what file system sda2 is. Seems like it's saying "I see sda2, I know you want to use it as root, but I don't know what's there - *poof*" and it panics. If rootwait alone doesn't work, I wonder if root=uuid=2ba08fbc-4b95-46cc-b638-299f16462620 instead of root=/dev/sda2 will work along with rootwait. It should then wait for that fs uuid to become available, rather than waiting for sda2 to become available. I vaguely recall there recently being btrfs boot problems with the module compiled in… Chris Murphy ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-25 0:04 ` Chris Murphy @ 2014-04-25 0:08 ` Chris Mason 2014-04-25 5:04 ` Пламен Петров 2014-04-25 7:02 ` Duncan 2014-04-25 5:03 ` Пламен Петров 1 sibling, 2 replies; 39+ messages in thread From: Chris Mason @ 2014-04-25 0:08 UTC (permalink / raw) To: Chris Murphy, Marc MERLIN Cc: Пламен Петров, linux-btrfs On 04/24/2014 08:04 PM, Chris Murphy wrote: > > On Apr 24, 2014, at 5:07 PM, Marc MERLIN <marc@merlins.org> wrote: >> >> >> In 3.14 the device shows up before btrfs is loaded: >> sd 2:0:0:0: [sda] Cache data unavailable >> sd 2:0:0:0: [sda] Assuming drive cache: write through >> sd 2:0:0:0: [sda] Attached SCSI disk >> (...) >> Btrfs loaded > > Same for me though, and I can boot. > > [ 0.693215] ata1.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133 > [ 0.693799] ata1.00: 167772160 sectors, multi 128: LBA48 NCQ (depth 31/32) > [ 0.694153] ata1.00: configured for UDMA/133 > [ 0.695475] scsi 0:0:0:0: Direct-Access ATA VBOX HARDDISK 1.0 PQ: 0 ANSI: 5 > [ 0.699386] sd 0:0:0:0: [sda] 167772160 512-byte logical blocks: (85.8 GB/80.0 GiB) > [ 0.699443] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [ 0.700604] sd 0:0:0:0: [sda] Write Protect is off > [ 0.701151] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > [ 0.701187] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > [ 0.707841] sda: sda1 sda2 sda3 > [ 0.709846] sd 0:0:0:0: [sda] Attached SCSI disk > (…) > [ 2.380090] bio: create slab <bio-1> at 1 > [ 2.384645] Btrfs loaded > > So I don't think the order is it. The biggest difference I'm seeing between the 3.13.11 and 3.14.1 dmesg's provided: > > 3.13.11: > [ 1.861740] bio: create slab <bio-1> at 1 > [ 1.863389] Btrfs loaded > > 3.14.1: > [ 3.949312] bio: create slab <bio-1> at 1 > [ 3.950942] Btrfs loaded > > It's happening much later, and it's right at this point VFS complains: > [ 4.182603] VFS: Cannot open root device "sda2" or unknown-block(8,2): error -38 > > The 8,2 message is consistent with the kernel not knowing what file system sda2 is. Seems like it's saying "I see sda2, I know you want to use it as root, but I don't know what's there - *poof*" and it panics. > > If rootwait alone doesn't work, I wonder if root=uuid=2ba08fbc-4b95-46cc-b638-299f16462620 instead of root=/dev/sda2 will work along with rootwait. It should then wait for that fs uuid to become available, rather than waiting for sda2 to become available. > > I vaguely recall there recently being btrfs boot problems with the module compiled in… > Yes, it was with the crc code. I noticed he has compression on and I'm wondering if we're hitting a similar ordering problem with the zlib init. The best way to know for sure is to please try with an initrd. If that does work we'll know it's an init ordering problem and we can track it down from there. -chris ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-25 0:08 ` Chris Mason @ 2014-04-25 5:04 ` Пламен Петров 2014-04-25 7:02 ` Duncan 1 sibling, 0 replies; 39+ messages in thread From: Пламен Петров @ 2014-04-25 5:04 UTC (permalink / raw) To: 'Chris Mason', 'Chris Murphy', 'Marc MERLIN' Cc: linux-btrfs > -----Original Message----- > From: Chris Mason [mailto:clm@fb.com] > Sent: Friday, April 25, 2014 3:08 AM > To: Chris Murphy; Marc MERLIN > Cc: Пламен Петров; linux-btrfs@vger.kernel.org > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > > > On 04/24/2014 08:04 PM, Chris Murphy wrote: > > > > On Apr 24, 2014, at 5:07 PM, Marc MERLIN <marc@merlins.org> wrote: > >> > >> > >> In 3.14 the device shows up before btrfs is loaded: > >> sd 2:0:0:0: [sda] Cache data unavailable sd 2:0:0:0: [sda] Assuming > >> drive cache: write through sd 2:0:0:0: [sda] Attached SCSI disk > >> (...) > >> Btrfs loaded > > > > Same for me though, and I can boot. > > > > [ 0.693215] ata1.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133 > > [ 0.693799] ata1.00: 167772160 sectors, multi 128: LBA48 NCQ (depth 31/32) > > [ 0.694153] ata1.00: configured for UDMA/133 > > [ 0.695475] scsi 0:0:0:0: Direct-Access ATA VBOX HARDDISK 1.0 PQ: 0 > ANSI: 5 > > [ 0.699386] sd 0:0:0:0: [sda] 167772160 512-byte logical blocks: (85.8 > GB/80.0 GiB) > > [ 0.699443] sd 0:0:0:0: Attached scsi generic sg0 type 0 > > [ 0.700604] sd 0:0:0:0: [sda] Write Protect is off > > [ 0.701151] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > > [ 0.701187] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, > doesn't support DPO or FUA > > [ 0.707841] sda: sda1 sda2 sda3 > > [ 0.709846] sd 0:0:0:0: [sda] Attached SCSI disk > > (…) > > [ 2.380090] bio: create slab <bio-1> at 1 > > [ 2.384645] Btrfs loaded > > > > So I don't think the order is it. The biggest difference I'm seeing between > the 3.13.11 and 3.14.1 dmesg's provided: > > > > 3.13.11: > > [ 1.861740] bio: create slab <bio-1> at 1 > > [ 1.863389] Btrfs loaded > > > > 3.14.1: > > [ 3.949312] bio: create slab <bio-1> at 1 > > [ 3.950942] Btrfs loaded > > > > It's happening much later, and it's right at this point VFS complains: > > [ 4.182603] VFS: Cannot open root device "sda2" or unknown-block(8,2): > error -38 > > > > The 8,2 message is consistent with the kernel not knowing what file system > sda2 is. Seems like it's saying "I see sda2, I know you want to use it as root, > but I don't know what's there - *poof*" and it panics. > > > > If rootwait alone doesn't work, I wonder if root=uuid=2ba08fbc-4b95-46cc- > b638-299f16462620 instead of root=/dev/sda2 will work along with rootwait. > It should then wait for that fs uuid to become available, rather than waiting > for sda2 to become available. > > > > I vaguely recall there recently being btrfs boot problems with the > > module compiled in… > > > > Yes, it was with the crc code. I noticed he has compression on and I'm > wondering if we're hitting a similar ordering problem with the zlib init. > > The best way to know for sure is to please try with an initrd. This will have to wait, though. Busy right now. > If that does > work we'll know it's an init ordering problem and we can track it down from > there. > Thanks, guys! -------------------------------- Plamen Petrov ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-25 0:08 ` Chris Mason 2014-04-25 5:04 ` Пламен Петров @ 2014-04-25 7:02 ` Duncan 1 sibling, 0 replies; 39+ messages in thread From: Duncan @ 2014-04-25 7:02 UTC (permalink / raw) To: linux-btrfs Chris Mason posted on Thu, 24 Apr 2014 20:08:28 -0400 as excerpted: > On 04/24/2014 08:04 PM, Chris Murphy wrote: >> So I don't think the order is it. The biggest difference I'm seeing >> between the 3.13.11 and 3.14.1 dmesg's provided: >> >> 3.13.11: >> [ 1.861740] bio: create slab <bio-1> at 1 [ 1.863389] Btrfs >> loaded >> >> 3.14.1: >> [ 3.949312] bio: create slab <bio-1> at 1 [ 3.950942] Btrfs >> loaded >> >> It's happening much later, and it's right at this point VFS complains: >> [ 4.182603] VFS: Cannot open root device "sda2" or >> unknown-block(8,2): error -38 >> >> The 8,2 message is consistent with the kernel not knowing what file >> system sda2 is. Seems like it's saying "I see sda2, I know you want to >> use it as root, but I don't know what's there - *poof*" and it panics. That's what I'm thinking too... >> I vaguely recall there recently being btrfs boot problems with the >> module compiled in… >> > Yes, it was with the crc code. I noticed he has compression on and I'm > wondering if we're hitting a similar ordering problem with the zlib > init. Everyone: I didn't think of this earlier, when I first saw the thread, but coming home and catching up after work, I think my subconscious must have been working on it all day, and even before I read this message, I was wondering if it might be another variant of that CRC32 problem. I was impatiently going thru the messages to see if someone mentioned it before I started another subthread on it... and here it is. =:^ But both crc32 and crc32c are loaded at about the same point in both kernels, before the filesystem tries to load, so that can't be it. But your zlib theory looks like a good candidate, Chris (Mason), and my sysadmin's intuition is behaving like a Geiger counter at Fukishima ATM, so I think we're on the right track! =:^) > The best way to know for sure is to please try with an initrd. If that > does work we'll know it's an init ordering problem and we can track it > down from there. Indeed, altho as I know from experience, reading/writing that is a lot easier than actually setting up an initr*, if you've not used one in a decade and haven't the foggiest how to create one. (Being a gentooer here, I ended up following a recommendation from an only semi-related gentoo discussion, and setting up dracut for my initr* when I needed one to support a multi-device btrfs rootfs. Wasn't too hard, but I did need to set aside some undisturbed time to study up on it and get it configured and working. Since this thread's about a single-device btrfs rootfs, he got away without one until now, but...) Meanwhile, if an initr* bypasses the issue, the fact that I'm running a multi-device btrfs root here, and thus an initr*, would explain why I hadn't run into the problem, here... There goes that Geiger counter again! -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ^ permalink raw reply [flat|nested] 39+ messages in thread
* RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-25 0:04 ` Chris Murphy 2014-04-25 0:08 ` Chris Mason @ 2014-04-25 5:03 ` Пламен Петров 1 sibling, 0 replies; 39+ messages in thread From: Пламен Петров @ 2014-04-25 5:03 UTC (permalink / raw) To: 'Chris Murphy', 'Marc MERLIN'; +Cc: linux-btrfs [-- Attachment #1: Type: text/plain, Size: 2771 bytes --] > -----Original Message----- > From: Chris Murphy [mailto:lists@colorremedies.com] > Sent: Friday, April 25, 2014 3:04 AM > To: Marc MERLIN > Cc: Пламен Петров; linux-btrfs@vger.kernel.org > Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or > newer? > > > On Apr 24, 2014, at 5:07 PM, Marc MERLIN <marc@merlins.org> wrote: > > > > > > In 3.14 the device shows up before btrfs is loaded: > > sd 2:0:0:0: [sda] Cache data unavailable sd 2:0:0:0: [sda] Assuming > > drive cache: write through sd 2:0:0:0: [sda] Attached SCSI disk > > (...) > > Btrfs loaded > > Same for me though, and I can boot. > > [ 0.693215] ata1.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133 > [ 0.693799] ata1.00: 167772160 sectors, multi 128: LBA48 NCQ (depth 31/32) > [ 0.694153] ata1.00: configured for UDMA/133 > [ 0.695475] scsi 0:0:0:0: Direct-Access ATA VBOX HARDDISK 1.0 PQ: 0 > ANSI: 5 > [ 0.699386] sd 0:0:0:0: [sda] 167772160 512-byte logical blocks: (85.8 GB/80.0 > GiB) > [ 0.699443] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [ 0.700604] sd 0:0:0:0: [sda] Write Protect is off > [ 0.701151] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > [ 0.701187] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, > doesn't support DPO or FUA > [ 0.707841] sda: sda1 sda2 sda3 > [ 0.709846] sd 0:0:0:0: [sda] Attached SCSI disk > (:) > [ 2.380090] bio: create slab <bio-1> at 1 > [ 2.384645] Btrfs loaded > > So I don't think the order is it. The biggest difference I'm seeing between the > 3.13.11 and 3.14.1 dmesg's provided: > > 3.13.11: > [ 1.861740] bio: create slab <bio-1> at 1 > [ 1.863389] Btrfs loaded > > 3.14.1: > [ 3.949312] bio: create slab <bio-1> at 1 > [ 3.950942] Btrfs loaded > > It's happening much later, and it's right at this point VFS complains: > [ 4.182603] VFS: Cannot open root device "sda2" or unknown-block(8,2): > error -38 > > The 8,2 message is consistent with the kernel not knowing what file system > sda2 is. Seems like it's saying "I see sda2, I know you want to use it as root, > but I don't know what's there - *poof*" and it panics. > > If rootwait alone doesn't work, I wonder if root=uuid=2ba08fbc-4b95-46cc- > b638-299f16462620 instead of root=/dev/sda2 will work along with rootwait. > It should then wait for that fs uuid to become available, rather than waiting > for sda2 to become available. > It does indeed wait, but I did not wait for it - just booted, saw it ended in "Waiting for root device uuid=..." and pasted the serial output. Is it supposed to somehow find its rootfs later? See the attached file. --------------------------------- Plamen Petrov [-- Attachment #2: dmesg-3.14.1-mix64-serial-rootwait-uuid.txt --] [-- Type: text/plain, Size: 45643 bytes --] [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.14.1-mix64 (root@crux) (gcc version 4.7.3 (CRUX-x86_64-multilib) ) #1 SMP Fri Apr 25 00:31:28 EEST 2014 [ 0.000000] Command line: rw root=uuid=2ba08fbc-4b95-46cc-b638-299f16462620 vga=6 raid=noautodetect console=ttyS0,9600n8 console=tty0 rootwait [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable [ 0.000000] BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000000ca000-0x00000000000cbfff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000000dc000-0x00000000000fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003fedffff] usable [ 0.000000] BIOS-e820: [mem 0x000000003fee0000-0x000000003fefefff] ACPI data [ 0.000000] BIOS-e820: [mem 0x000000003feff000-0x000000003fefffff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x000000003ff00000-0x000000003fffffff] usable [ 0.000000] BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fffe0000-0x00000000ffffffff] reserved [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] SMBIOS 2.4 present. [ 0.000000] Hypervisor detected: VMware [ 0.000000] No AGP bridge found [ 0.000000] e820: last_pfn = 0x40000 max_arch_pfn = 0x400000000 [ 0.000000] x86 PAT enabled: cpu 0, old 0x0, new 0x7010600070106 [ 0.000000] found SMP MP-table at [mem 0x000f6bf0-0x000f6bff] mapped at [ffff8800000f6bf0] [ 0.000000] Using GB pages for direct mapping [ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff] [ 0.000000] init_memory_mapping: [mem 0x3fc00000-0x3fdfffff] [ 0.000000] init_memory_mapping: [mem 0x3c000000-0x3fbfffff] [ 0.000000] init_memory_mapping: [mem 0x00100000-0x3bffffff] [ 0.000000] init_memory_mapping: [mem 0x3fe00000-0x3fedffff] [ 0.000000] init_memory_mapping: [mem 0x3ff00000-0x3fffffff] [ 0.000000] ACPI: RSDP 00000000000f6b80 000024 (v02 PTLTD ) [ 0.000000] ACPI: XSDT 000000003feeda33 00005C (v01 INTEL 440BX 06040000 VMW 01324272) [ 0.000000] ACPI: FACP 000000003fefee73 0000F4 (v04 INTEL 440BX 06040000 PTL 000F4240) [ 0.000000] ACPI: DSDT 000000003feee8eb 010588 (v01 PTLTD Custom 06040000 MSFT 03000001) [ 0.000000] ACPI: FACS 000000003fefffc0 000040 [ 0.000000] ACPI: BOOT 000000003feee8c3 000028 (v01 PTLTD $SBFTBL$ 06040000 LTP 00000001) [ 0.000000] ACPI: APIC 000000003feee501 0003C2 (v01 PTLTD ? APIC 06040000 LTP 00000000) [ 0.000000] ACPI: MCFG 000000003feee4c5 00003C (v01 PTLTD $PCITBL$ 06040000 LTP 00000001) [ 0.000000] ACPI: SRAT 000000003feedb2f 0004D0 (v02 VMWARE MEMPLUG 06040000 VMW 00000001) [ 0.000000] ACPI: HPET 000000003feedaf7 000038 (v01 VMWARE VMW HPET 06040000 VMW 00000001) [ 0.000000] ACPI: WAET 000000003feedacf 000028 (v01 VMWARE VMW WAET 06040000 VMW 00000001) [ 0.000000] Setting APIC routing to physical flat. [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x00001000-0x00ffffff] [ 0.000000] DMA32 [mem 0x01000000-0xffffffff] [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00001000-0x0009efff] [ 0.000000] node 0: [mem 0x00100000-0x3fedffff] [ 0.000000] node 0: [mem 0x3ff00000-0x3fffffff] [ 0.000000] ACPI: PM-Timer IO Port: 0x1008 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x08] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x0a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x0c] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x0e] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x12] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x14] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x16] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x18] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x1a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x1c] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x1e] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x22] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x24] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x26] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0x28] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0x2a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0x2c] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0x2e] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x30] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x32] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x34] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x36] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x38] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3c] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x20] lapic_id[0x40] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x21] lapic_id[0x42] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x22] lapic_id[0x44] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x23] lapic_id[0x46] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x24] lapic_id[0x48] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x25] lapic_id[0x4a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x26] lapic_id[0x4c] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x27] lapic_id[0x4e] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x28] lapic_id[0x50] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x29] lapic_id[0x52] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x2a] lapic_id[0x54] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x2b] lapic_id[0x56] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x2c] lapic_id[0x58] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x2d] lapic_id[0x5a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x2e] lapic_id[0x5c] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x2f] lapic_id[0x5e] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x30] lapic_id[0x60] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x31] lapic_id[0x62] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x32] lapic_id[0x64] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x33] lapic_id[0x66] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x34] lapic_id[0x68] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x35] lapic_id[0x6a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x36] lapic_id[0x6c] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x37] lapic_id[0x6e] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x38] lapic_id[0x70] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x39] lapic_id[0x72] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x3a] lapic_id[0x74] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x3b] lapic_id[0x76] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x3c] lapic_id[0x78] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x3d] lapic_id[0x7a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x3e] lapic_id[0x7c] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x3f] lapic_id[0x7e] disabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x14] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x15] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x16] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x17] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x1c] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x1d] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x1e] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x1f] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x20] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x21] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x22] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x23] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x24] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x25] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x26] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x27] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x28] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x29] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x2a] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x2b] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x2c] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x2d] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x2e] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x2f] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x30] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x31] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x32] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x33] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x34] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x35] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x36] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x37] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x38] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x39] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x3a] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x3b] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x3c] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x3d] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x3e] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x3f] high edge lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086af01 base: 0xfed00000 [ 0.000000] smpboot: 64 Processors exceeds NR_CPUS limit of 8 [ 0.000000] smpboot: Allowing 8 CPUs, 7 hotplug CPUs [ 0.000000] e820: [mem 0x40000000-0xefffffff] available for PCI devices [ 0.000000] Booting paravirtualized kernel on bare hardware [ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 25 pages/cpu @ffff88003fc00000 s80192 r0 d22208 u262144 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 257897 [ 0.000000] Kernel command line: rw root=uuid=2ba08fbc-4b95-46cc-b638-299f16462620 vga=6 raid=noautodetect console=ttyS0,9600n8 console=tty0 rootwait [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.000000] Checking aperture... [ 0.000000] No AGP bridge found [ 0.000000] Memory: 1012780K/1048056K available (7943K kernel code, 527K rwdata, 2628K rodata, 932K init, 2580K bss, 35276K reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] CONFIG_RCU_FANOUT set to non-default value of 32 [ 0.000000] NR_IRQS:4352 nr_irqs:744 16 [ 0.000000] Console: colour VGA+ 80x60 [ 0.000000] console [tty0] enabled [ 0.000000] console [ttyS0] enabled [ 0.000000] TSC freq read from hypervisor : 3000.079 MHz [ 0.000000] tsc: Detected 3000.079 MHz processor [ 0.000008] Calibrating delay loop (skipped) preset value.. 6000.15 BogoMIPS (lpj=30000790) [ 0.002246] pid_max: default: 32768 minimum: 301 [ 0.003470] ACPI: Core revision 20131218 [ 0.010935] ACPI: All ACPI Tables successfully acquired [ 0.016551] Security Framework initialized [ 0.017804] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes) [ 0.019533] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes) [ 0.021913] Initializing cgroup subsys freezer [ 0.023201] mce: CPU supports 0 MCE banks [ 0.024343] Last level iTLB entries: 4KB 512, 2MB 16, 4MB 8 [ 0.024343] Last level dTLB entries: 4KB 512, 2MB 128, 4MB 64, 1GB 0 [ 0.024343] tlb_flushall_shift: 6 [ 0.067819] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.169353] smpboot: CPU0: AMD Athlon(tm) II X4 640 Processor (fam: 10, model: 05, stepping: 03) [ 0.288714] Performance Events: AMD PMU driver. [ 0.290031] ... version: 0 [ 0.291120] ... bit width: 48 [ 0.292203] ... generic registers: 4 [ 0.293262] ... value mask: 0000ffffffffffff [ 0.294650] ... max period: 00007fffffffffff [ 0.296053] ... fixed-purpose events: 0 [ 0.297134] ... event mask: 000000000000000f [ 0.298759] x86: Booted up 1 node, 1 CPUs [ 0.299873] smpboot: Total of 1 processors activated (6000.15 BogoMIPS) [ 0.301887] x86 PAT enabled: cpu 0, old 0x0, new 0x7010600070106 [ 0.303669] devtmpfs: initialized [ 0.304806] kworker/u16:0 (14) used greatest stack depth: 6248 bytes left [ 0.306658] xor: measuring software checksum speed [ 0.408477] prefetch64-sse: 12224.800 MB/sec [ 0.508385] generic_sse: 11643.600 MB/sec [ 0.509567] xor: using function: prefetch64-sse (12224.800 MB/sec) [ 0.511333] NET: Registered protocol family 16 [ 0.512815] cpuidle: using governor ladder [ 0.514033] cpuidle: using governor menu [ 0.515907] ACPI: bus type PCI registered [ 0.517246] PCI: MMCONFIG for domain 0000 [bus 00-7f] at [mem 0xf0000000-0xf7ffffff] (base 0xf0000000) [ 0.519737] PCI: MMCONFIG at [mem 0xf0000000-0xf7ffffff] reserved in E820 [ 0.525415] PCI: Using configuration type 1 for base access [ 0.527337] kworker/u16:0 (41) used greatest stack depth: 5832 bytes left [ 0.540571] bio: create slab <bio-0> at 0 [ 0.708240] raid6: sse2x1 3985 MB/s [ 0.878012] raid6: sse2x2 6637 MB/s [ 1.047854] raid6: sse2x4 7519 MB/s [ 1.048878] raid6: using algorithm sse2x4 (7519 MB/s) [ 1.050200] raid6: using intx1 recovery algorithm [ 1.051802] ACPI: Added _OSI(Module Device) [ 1.052986] ACPI: Added _OSI(Processor Device) [ 1.054153] ACPI: Added _OSI(3.0 _SCP Extensions) [ 1.055434] ACPI: Added _OSI(Processor Aggregator Device) [ 1.064341] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ 1.072476] ACPI: Interpreter enabled [ 1.073519] ACPI: (supports S0 S5) [ 1.074446] ACPI: Using IOAPIC for interrupt routing [ 1.075932] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 1.097944] ACPI: No dock devices found. [ 1.176769] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7f]) [ 1.178495] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 1.180923] acpi PNP0A03:00: _OSC: platform does not support [AER] [ 1.182761] acpi PNP0A03:00: _OSC: OS now controls [PCIeHotplug PME PCIeCapability] [ 1.186223] PCI host bridge to bus 0000:00 [ 1.187398] pci_bus 0000:00: root bus resource [bus 00-7f] [ 1.188859] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff] [ 1.190662] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff] [ 1.192451] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff] [ 1.194273] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff] [ 1.196177] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff] [ 1.198040] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff] [ 1.199819] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7] [ 1.201457] pci_bus 0000:00: root bus resource [io 0x0d00-0xfeff] [ 1.209041] pci 0000:00:07.3: quirk: [io 0x1000-0x103f] claimed by PIIX4 ACPI [ 1.211084] pci 0000:00:07.3: quirk: [io 0x1040-0x104f] claimed by PIIX4 SMB [ 1.228702] pci 0000:00:11.0: System wakeup disabled by ACPI [ 1.231605] pci 0000:00:15.0: System wakeup disabled by ACPI [ 1.234254] pci 0000:00:15.1: System wakeup disabled by ACPI [ 1.236925] pci 0000:00:15.2: System wakeup disabled by ACPI [ 1.239568] pci 0000:00:15.3: System wakeup disabled by ACPI [ 1.242444] pci 0000:00:15.4: System wakeup disabled by ACPI [ 1.245204] pci 0000:00:15.5: System wakeup disabled by ACPI [ 1.248120] pci 0000:00:15.6: System wakeup disabled by ACPI [ 1.250863] pci 0000:00:15.7: System wakeup disabled by ACPI [ 1.253509] pci 0000:00:16.0: System wakeup disabled by ACPI [ 1.256163] pci 0000:00:16.1: System wakeup disabled by ACPI [ 1.258845] pci 0000:00:16.2: System wakeup disabled by ACPI [ 1.261597] pci 0000:00:16.3: System wakeup disabled by ACPI [ 1.264279] pci 0000:00:16.4: System wakeup disabled by ACPI [ 1.266982] pci 0000:00:16.5: System wakeup disabled by ACPI [ 1.269623] pci 0000:00:16.6: System wakeup disabled by ACPI [ 1.272304] pci 0000:00:16.7: System wakeup disabled by ACPI [ 1.274930] pci 0000:00:17.0: System wakeup disabled by ACPI [ 1.277705] pci 0000:00:17.1: System wakeup disabled by ACPI [ 1.280458] pci 0000:00:17.2: System wakeup disabled by ACPI [ 1.283102] pci 0000:00:17.3: System wakeup disabled by ACPI [ 1.285762] pci 0000:00:17.4: System wakeup disabled by ACPI [ 1.288441] pci 0000:00:17.5: System wakeup disabled by ACPI [ 1.291122] pci 0000:00:17.6: System wakeup disabled by ACPI [ 1.293771] pci 0000:00:17.7: System wakeup disabled by ACPI [ 1.296593] pci 0000:00:18.0: System wakeup disabled by ACPI [ 1.299285] pci 0000:00:18.1: System wakeup disabled by ACPI [ 1.301995] pci 0000:00:18.2: System wakeup disabled by ACPI [ 1.304622] pci 0000:00:18.3: System wakeup disabled by ACPI [ 1.307340] pci 0000:00:18.4: System wakeup disabled by ACPI [ 1.309974] pci 0000:00:18.5: System wakeup disabled by ACPI [ 1.312751] pci 0000:00:18.6: System wakeup disabled by ACPI [ 1.316227] pci 0000:00:18.7: System wakeup disabled by ACPI [ 1.318325] pci 0000:00:01.0: PCI bridge to [bus 01] [ 1.323991] pci 0000:02:00.0: System wakeup disabled by ACPI [ 1.325985] pci 0000:00:11.0: PCI bridge to [bus 02] (subtractive decode) [ 1.328465] pci 0000:00:15.0: PCI bridge to [bus 03] [ 1.330447] pci 0000:00:15.1: PCI bridge to [bus 04] [ 1.332282] pci 0000:00:15.2: PCI bridge to [bus 05] [ 1.334126] pci 0000:00:15.3: PCI bridge to [bus 06] [ 1.336035] pci 0000:00:15.4: PCI bridge to [bus 07] [ 1.337936] pci 0000:00:15.5: PCI bridge to [bus 08] [ 1.339772] pci 0000:00:15.6: PCI bridge to [bus 09] [ 1.341703] pci 0000:00:15.7: PCI bridge to [bus 0a] [ 1.343550] pci 0000:00:16.0: PCI bridge to [bus 0b] [ 1.345501] pci 0000:00:16.1: PCI bridge to [bus 0c] [ 1.347450] pci 0000:00:16.2: PCI bridge to [bus 0d] [ 1.349321] pci 0000:00:16.3: PCI bridge to [bus 0e] [ 1.351228] pci 0000:00:16.4: PCI bridge to [bus 0f] [ 1.353100] pci 0000:00:16.5: PCI bridge to [bus 10] [ 1.354933] pci 0000:00:16.6: PCI bridge to [bus 11] [ 1.356885] pci 0000:00:16.7: PCI bridge to [bus 12] [ 1.358748] pci 0000:00:17.0: PCI bridge to [bus 13] [ 1.360680] pci 0000:00:17.1: PCI bridge to [bus 14] [ 1.362580] pci 0000:00:17.2: PCI bridge to [bus 15] [ 1.364458] pci 0000:00:17.3: PCI bridge to [bus 16] [ 1.366381] pci 0000:00:17.4: PCI bridge to [bus 17] [ 1.368286] pci 0000:00:17.5: PCI bridge to [bus 18] [ 1.370187] pci 0000:00:17.6: PCI bridge to [bus 19] [ 1.372027] pci 0000:00:17.7: PCI bridge to [bus 1a] [ 1.373879] pci 0000:00:18.0: PCI bridge to [bus 1b] [ 1.375813] pci 0000:00:18.1: PCI bridge to [bus 1c] [ 1.377736] pci 0000:00:18.2: PCI bridge to [bus 1d] [ 1.379633] pci 0000:00:18.3: PCI bridge to [bus 1e] [ 1.381962] pci 0000:00:18.4: PCI bridge to [bus 1f] [ 1.383847] pci 0000:00:18.5: PCI bridge to [bus 20] [ 1.385761] pci 0000:00:18.6: PCI bridge to [bus 21] [ 1.387677] pci 0000:00:18.7: PCI bridge to [bus 22] [ 1.391377] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *9 10 11 14 15) [ 1.394030] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 14 15) [ 1.396905] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11 14 15) [ 1.399661] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled. [ 1.413372] ACPI: Enabled 2 GPEs in block 00 to 0F [ 1.415332] vgaarb: device added: PCI:0000:00:0f.0,decodes=io+mem,owns=io+mem,locks=none [ 1.417535] vgaarb: loaded [ 1.418293] vgaarb: bridge control possible 0000:00:0f.0 [ 1.419818] SCSI subsystem initialized [ 1.421042] ACPI: bus type USB registered [ 1.422182] usbcore: registered new interface driver usbfs [ 1.423674] usbcore: registered new interface driver hub [ 1.425126] usbcore: registered new device driver usb [ 1.426536] pps_core: LinuxPPS API ver. 1 registered [ 1.427922] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 1.430560] PTP clock support registered [ 1.431796] PCI: Using ACPI for IRQ routing [ 1.464415] NetLabel: Initializing [ 1.465410] NetLabel: domain hash size = 128 [ 1.466554] NetLabel: protocols = UNLABELED CIPSOv4 [ 1.467923] NetLabel: unlabeled traffic allowed by default [ 1.469533] HPET: 16 timers in total, 0 timers will be used for per-cpu timer [ 1.471481] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 [ 1.474689] hpet0: 16 comparators, 64-bit 14.318180 MHz counter [ 1.478425] Switched to clocksource hpet [ 1.479588] FS-Cache: Loaded [ 1.480864] pnp: PnP ACPI init [ 1.481772] ACPI: bus type PNP registered [ 1.483130] system 00:00: [io 0x1000-0x103f] could not be reserved [ 1.484783] system 00:00: [io 0x1040-0x104f] has been reserved [ 1.486361] system 00:00: [io 0x0cf0-0x0cf1] has been reserved [ 1.488568] system 00:07: [mem 0xfed00000-0xfed003ff] has been reserved [ 1.493015] system 00:0c: [io 0xfce0-0xfcff] has been reserved [ 1.494594] system 00:0c: [mem 0xf0000000-0xf7ffffff] has been reserved [ 1.496367] system 00:0c: [mem 0xfe800000-0xfe9fffff] has been reserved [ 1.504558] pnp: PnP ACPI: found 14 devices [ 1.505778] ACPI: bus type PNP unregistered [ 1.516299] pci 0000:00:0f.0: BAR 6: assigned [mem 0xc0000000-0xc0007fff pref] [ 1.518231] pci 0000:00:10.0: BAR 6: assigned [mem 0xc0008000-0xc000bfff pref] [ 1.520196] pci 0000:00:15.3: BAR 7: can't assign io (size 0x1000) [ 1.521805] pci 0000:00:15.4: BAR 7: can't assign io (size 0x1000) [ 1.523422] pci 0000:00:15.5: BAR 7: can't assign io (size 0x1000) [ 1.525193] pci 0000:00:15.6: BAR 7: can't assign io (size 0x1000) [ 1.526814] pci 0000:00:15.7: BAR 7: can't assign io (size 0x1000) [ 1.528460] pci 0000:00:16.3: BAR 7: can't assign io (size 0x1000) [ 1.530122] pci 0000:00:16.4: BAR 7: can't assign io (size 0x1000) [ 1.531785] pci 0000:00:16.5: BAR 7: can't assign io (size 0x1000) [ 1.533421] pci 0000:00:16.6: BAR 7: can't assign io (size 0x1000) [ 1.535058] pci 0000:00:16.7: BAR 7: can't assign io (size 0x1000) [ 1.536659] pci 0000:00:17.3: BAR 7: can't assign io (size 0x1000) [ 1.538269] pci 0000:00:17.4: BAR 7: can't assign io (size 0x1000) [ 1.539915] pci 0000:00:17.5: BAR 7: can't assign io (size 0x1000) [ 1.541519] pci 0000:00:17.6: BAR 7: can't assign io (size 0x1000) [ 1.543133] pci 0000:00:17.7: BAR 7: can't assign io (size 0x1000) [ 1.544732] pci 0000:00:18.2: BAR 7: can't assign io (size 0x1000) [ 1.546383] pci 0000:00:18.3: BAR 7: can't assign io (size 0x1000) [ 1.548069] pci 0000:00:18.4: BAR 7: can't assign io (size 0x1000) [ 1.549728] pci 0000:00:18.5: BAR 7: can't assign io (size 0x1000) [ 1.551350] pci 0000:00:18.6: BAR 7: can't assign io (size 0x1000) [ 1.552964] pci 0000:00:18.7: BAR 7: can't assign io (size 0x1000) [ 1.554567] pci 0000:00:18.7: BAR 7: can't assign io (size 0x1000) [ 1.556186] pci 0000:00:18.6: BAR 7: can't assign io (size 0x1000) [ 1.557794] pci 0000:00:18.5: BAR 7: can't assign io (size 0x1000) [ 1.559419] pci 0000:00:18.4: BAR 7: can't assign io (size 0x1000) [ 1.561047] pci 0000:00:18.3: BAR 7: can't assign io (size 0x1000) [ 1.562667] pci 0000:00:18.2: BAR 7: can't assign io (size 0x1000) [ 1.564326] pci 0000:00:17.7: BAR 7: can't assign io (size 0x1000) [ 1.566004] pci 0000:00:17.6: BAR 7: can't assign io (size 0x1000) [ 1.567611] pci 0000:00:17.5: BAR 7: can't assign io (size 0x1000) [ 1.569236] pci 0000:00:17.4: BAR 7: can't assign io (size 0x1000) [ 1.570864] pci 0000:00:17.3: BAR 7: can't assign io (size 0x1000) [ 1.572474] pci 0000:00:16.7: BAR 7: can't assign io (size 0x1000) [ 1.574083] pci 0000:00:16.6: BAR 7: can't assign io (size 0x1000) [ 1.575699] pci 0000:00:16.5: BAR 7: can't assign io (size 0x1000) [ 1.577318] pci 0000:00:16.4: BAR 7: can't assign io (size 0x1000) [ 1.578942] pci 0000:00:16.3: BAR 7: can't assign io (size 0x1000) [ 1.580627] pci 0000:00:15.7: BAR 7: can't assign io (size 0x1000) [ 1.582276] pci 0000:00:15.6: BAR 7: can't assign io (size 0x1000) [ 1.583916] pci 0000:00:15.5: BAR 7: can't assign io (size 0x1000) [ 1.585538] pci 0000:00:15.4: BAR 7: can't assign io (size 0x1000) [ 1.587139] pci 0000:00:15.3: BAR 7: can't assign io (size 0x1000) [ 1.588769] pci 0000:00:01.0: PCI bridge to [bus 01] [ 1.590210] pci 0000:02:00.0: BAR 6: assigned [mem 0xe7b00000-0xe7b0ffff pref] [ 1.592092] pci 0000:00:11.0: PCI bridge to [bus 02] [ 1.593423] pci 0000:00:11.0: bridge window [io 0x2000-0x3fff] [ 1.595052] pci 0000:00:11.0: bridge window [mem 0xfd500000-0xfdffffff] [ 1.596853] pci 0000:00:11.0: bridge window [mem 0xe7b00000-0xe7ffffff 64bit pref] [ 1.599018] pci 0000:00:15.0: PCI bridge to [bus 03] [ 1.600395] pci 0000:00:15.0: bridge window [io 0x4000-0x4fff] [ 1.602003] pci 0000:00:15.0: bridge window [mem 0xfd400000-0xfd4fffff] [ 1.603789] pci 0000:00:15.0: bridge window [mem 0xe7a00000-0xe7afffff 64bit pref] [ 1.605895] pci 0000:00:15.1: PCI bridge to [bus 04] [ 1.607216] pci 0000:00:15.1: bridge window [io 0x8000-0x8fff] [ 1.608880] pci 0000:00:15.1: bridge window [mem 0xfd000000-0xfd0fffff] [ 1.610694] pci 0000:00:15.1: bridge window [mem 0xe7600000-0xe76fffff 64bit pref] [ 1.612800] pci 0000:00:15.2: PCI bridge to [bus 05] [ 1.614156] pci 0000:00:15.2: bridge window [io 0xc000-0xcfff] [ 1.615851] pci 0000:00:15.2: bridge window [mem 0xfcc00000-0xfccfffff] [ 1.617658] pci 0000:00:15.2: bridge window [mem 0xe7200000-0xe72fffff 64bit pref] [ 1.620513] pci 0000:00:15.3: PCI bridge to [bus 06] [ 1.621857] pci 0000:00:15.3: bridge window [mem 0xfc800000-0xfc8fffff] [ 1.623653] pci 0000:00:15.3: bridge window [mem 0xe6e00000-0xe6efffff 64bit pref] [ 1.625748] pci 0000:00:15.4: PCI bridge to [bus 07] [ 1.627087] pci 0000:00:15.4: bridge window [mem 0xfc400000-0xfc4fffff] [ 1.628893] pci 0000:00:15.4: bridge window [mem 0xe6a00000-0xe6afffff 64bit pref] [ 1.631208] pci 0000:00:15.5: PCI bridge to [bus 08] [ 1.632633] pci 0000:00:15.5: bridge window [mem 0xfc000000-0xfc0fffff] [ 1.634426] pci 0000:00:15.5: bridge window [mem 0xe6600000-0xe66fffff 64bit pref] [ 1.636569] pci 0000:00:15.6: PCI bridge to [bus 09] [ 1.637917] pci 0000:00:15.6: bridge window [mem 0xfbc00000-0xfbcfffff] [ 1.639796] pci 0000:00:15.6: bridge window [mem 0xe6200000-0xe62fffff 64bit pref] [ 1.641866] pci 0000:00:15.7: PCI bridge to [bus 0a] [ 1.643217] pci 0000:00:15.7: bridge window [mem 0xfb800000-0xfb8fffff] [ 1.645054] pci 0000:00:15.7: bridge window [mem 0xe5e00000-0xe5efffff 64bit pref] [ 1.647148] pci 0000:00:16.0: PCI bridge to [bus 0b] [ 1.648544] pci 0000:00:16.0: bridge window [io 0x5000-0x5fff] [ 1.650265] pci 0000:00:16.0: bridge window [mem 0xfd300000-0xfd3fffff] [ 1.652039] pci 0000:00:16.0: bridge window [mem 0xe7900000-0xe79fffff 64bit pref] [ 1.654112] pci 0000:00:16.1: PCI bridge to [bus 0c] [ 1.655482] pci 0000:00:16.1: bridge window [io 0x9000-0x9fff] [ 1.657098] pci 0000:00:16.1: bridge window [mem 0xfcf00000-0xfcffffff] [ 1.658914] pci 0000:00:16.1: bridge window [mem 0xe7500000-0xe75fffff 64bit pref] [ 1.661057] pci 0000:00:16.2: PCI bridge to [bus 0d] [ 1.662375] pci 0000:00:16.2: bridge window [io 0xd000-0xdfff] [ 1.664024] pci 0000:00:16.2: bridge window [mem 0xfcb00000-0xfcbfffff] [ 1.665908] pci 0000:00:16.2: bridge window [mem 0xe7100000-0xe71fffff 64bit pref] [ 1.668011] pci 0000:00:16.3: PCI bridge to [bus 0e] [ 1.669370] pci 0000:00:16.3: bridge window [mem 0xfc700000-0xfc7fffff] [ 1.671201] pci 0000:00:16.3: bridge window [mem 0xe6d00000-0xe6dfffff 64bit pref] [ 1.673274] pci 0000:00:16.4: PCI bridge to [bus 0f] [ 1.674614] pci 0000:00:16.4: bridge window [mem 0xfc300000-0xfc3fffff] [ 1.676441] pci 0000:00:16.4: bridge window [mem 0xe6900000-0xe69fffff 64bit pref] [ 1.678537] pci 0000:00:16.5: PCI bridge to [bus 10] [ 1.679943] pci 0000:00:16.5: bridge window [mem 0xfbf00000-0xfbffffff] [ 1.681784] pci 0000:00:16.5: bridge window [mem 0xe6500000-0xe65fffff 64bit pref] [ 1.684045] pci 0000:00:16.6: PCI bridge to [bus 11] [ 1.685433] pci 0000:00:16.6: bridge window [mem 0xfbb00000-0xfbbfffff] [ 1.687219] pci 0000:00:16.6: bridge window [mem 0xe6100000-0xe61fffff 64bit pref] [ 1.689335] pci 0000:00:16.7: PCI bridge to [bus 12] [ 1.690775] pci 0000:00:16.7: bridge window [mem 0xfb700000-0xfb7fffff] [ 1.692572] pci 0000:00:16.7: bridge window [mem 0xe5d00000-0xe5dfffff 64bit pref] [ 1.694640] pci 0000:00:17.0: PCI bridge to [bus 13] [ 1.695985] pci 0000:00:17.0: bridge window [io 0x6000-0x6fff] [ 1.697660] pci 0000:00:17.0: bridge window [mem 0xfd200000-0xfd2fffff] [ 1.699511] pci 0000:00:17.0: bridge window [mem 0xe7800000-0xe78fffff 64bit pref] [ 1.701661] pci 0000:00:17.1: PCI bridge to [bus 14] [ 1.702996] pci 0000:00:17.1: bridge window [io 0xa000-0xafff] [ 1.704612] pci 0000:00:17.1: bridge window [mem 0xfce00000-0xfcefffff] [ 1.706421] pci 0000:00:17.1: bridge window [mem 0xe7400000-0xe74fffff 64bit pref] [ 1.708515] pci 0000:00:17.2: PCI bridge to [bus 15] [ 1.709856] pci 0000:00:17.2: bridge window [io 0xe000-0xefff] [ 1.711474] pci 0000:00:17.2: bridge window [mem 0xfca00000-0xfcafffff] [ 1.713263] pci 0000:00:17.2: bridge window [mem 0xe7000000-0xe70fffff 64bit pref] [ 1.715437] pci 0000:00:17.3: PCI bridge to [bus 16] [ 1.716812] pci 0000:00:17.3: bridge window [mem 0xfc600000-0xfc6fffff] [ 1.718622] pci 0000:00:17.3: bridge window [mem 0xe6c00000-0xe6cfffff 64bit pref] [ 1.720727] pci 0000:00:17.4: PCI bridge to [bus 17] [ 1.722063] pci 0000:00:17.4: bridge window [mem 0xfc200000-0xfc2fffff] [ 1.723863] pci 0000:00:17.4: bridge window [mem 0xe6800000-0xe68fffff 64bit pref] [ 1.725948] pci 0000:00:17.5: PCI bridge to [bus 18] [ 1.727305] pci 0000:00:17.5: bridge window [mem 0xfbe00000-0xfbefffff] [ 1.729102] pci 0000:00:17.5: bridge window [mem 0xe6400000-0xe64fffff 64bit pref] [ 1.731233] pci 0000:00:17.6: PCI bridge to [bus 19] [ 1.732608] pci 0000:00:17.6: bridge window [mem 0xfba00000-0xfbafffff] [ 1.734413] pci 0000:00:17.6: bridge window [mem 0xe6000000-0xe60fffff 64bit pref] [ 1.736510] pci 0000:00:17.7: PCI bridge to [bus 1a] [ 1.737858] pci 0000:00:17.7: bridge window [mem 0xfb600000-0xfb6fffff] [ 1.739685] pci 0000:00:17.7: bridge window [mem 0xe5c00000-0xe5cfffff 64bit pref] [ 1.741760] pci 0000:00:18.0: PCI bridge to [bus 1b] [ 1.743091] pci 0000:00:18.0: bridge window [io 0x7000-0x7fff] [ 1.744720] pci 0000:00:18.0: bridge window [mem 0xfd100000-0xfd1fffff] [ 1.746504] pci 0000:00:18.0: bridge window [mem 0xe7700000-0xe77fffff 64bit pref] [ 1.748658] pci 0000:00:18.1: PCI bridge to [bus 1c] [ 1.750089] pci 0000:00:18.1: bridge window [io 0xb000-0xbfff] [ 1.751742] pci 0000:00:18.1: bridge window [mem 0xfcd00000-0xfcdfffff] [ 1.753534] pci 0000:00:18.1: bridge window [mem 0xe7300000-0xe73fffff 64bit pref] [ 1.755627] pci 0000:00:18.2: PCI bridge to [bus 1d] [ 1.756966] pci 0000:00:18.2: bridge window [mem 0xfc900000-0xfc9fffff] [ 1.758780] pci 0000:00:18.2: bridge window [mem 0xe6f00000-0xe6ffffff 64bit pref] [ 1.760870] pci 0000:00:18.3: PCI bridge to [bus 1e] [ 1.762230] pci 0000:00:18.3: bridge window [mem 0xfc500000-0xfc5fffff] [ 1.764033] pci 0000:00:18.3: bridge window [mem 0xe6b00000-0xe6bfffff 64bit pref] [ 1.766164] pci 0000:00:18.4: PCI bridge to [bus 1f] [ 1.767549] pci 0000:00:18.4: bridge window [mem 0xfc100000-0xfc1fffff] [ 1.769351] pci 0000:00:18.4: bridge window [mem 0xe6700000-0xe67fffff 64bit pref] [ 1.771444] pci 0000:00:18.5: PCI bridge to [bus 20] [ 1.772797] pci 0000:00:18.5: bridge window [mem 0xfbd00000-0xfbdfffff] [ 1.774579] pci 0000:00:18.5: bridge window [mem 0xe6300000-0xe63fffff 64bit pref] [ 1.776680] pci 0000:00:18.6: PCI bridge to [bus 21] [ 1.778024] pci 0000:00:18.6: bridge window [mem 0xfb900000-0xfb9fffff] [ 1.779857] pci 0000:00:18.6: bridge window [mem 0xe5f00000-0xe5ffffff 64bit pref] [ 1.781972] pci 0000:00:18.7: PCI bridge to [bus 22] [ 1.783354] pci 0000:00:18.7: bridge window [mem 0xfb500000-0xfb5fffff] [ 1.785176] pci 0000:00:18.7: bridge window [mem 0xe5b00000-0xe5bfffff 64bit pref] [ 1.787455] NET: Registered protocol family 2 [ 1.788759] TCP established hash table entries: 8192 (order: 4, 65536 bytes) [ 1.790676] TCP bind hash table entries: 8192 (order: 5, 131072 bytes) [ 1.792421] TCP: Hash tables configured (established 8192 bind 8192) [ 1.794112] TCP: reno registered [ 1.795031] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 1.796581] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 1.798442] NET: Registered protocol family 1 [ 1.799715] pci 0000:00:00.0: Limiting direct PCI/PCI transfers [ 1.801903] Simple Boot Flag at 0x36 set to 0x80 [ 1.803194] Switched to clocksource tsc [ 1.804341] microcode: CPU0: patch_level=0x010000b6 [ 1.805770] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba [ 1.808222] PCLMULQDQ-NI instructions are not detected. [ 1.809685] sha256_ssse3: Neither AVX nor SSSE3 is available/usable. [ 1.811352] sha512_ssse3: Neither AVX nor SSSE3 is available/usable. [ 1.813569] futex hash table entries: 2048 (order: 5, 131072 bytes) [ 1.816123] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 1.821511] fuse init (API version 7.22) [ 1.823563] SGI XFS with security attributes, large block/inode numbers, no debug enabled [ 1.826856] msgmni has been set to 1978 [ 1.829708] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 1.831721] io scheduler noop registered (default) [ 1.833004] io scheduler deadline registered [ 1.834447] crc32: CRC_LE_BITS = 64, CRC_BE BITS = 64 [ 1.835819] crc32: self tests passed, processed 225944 bytes in 131098 nsec [ 1.837751] crc32c: CRC_LE_BITS = 64 [ 1.838749] crc32c: self tests passed, processed 225944 bytes in 65511 nsec [ 2.056426] crc32_combine: 8373 self tests passed [ 2.275509] crc32c_combine: 8373 self tests passed [ 2.300041] ACPI: AC Adapter [ACAD] (on-line) [ 2.301520] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 [ 2.303536] ACPI: Power Button [PWRF] [ 2.305823] xenfs: not registering filesystem on non-xen platform [ 2.307832] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 2.335413] 00:09: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [ 2.363411] 00:0a: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A [ 2.366192] Non-volatile memory driver v1.3 [ 2.367404] Linux agpgart interface v0.103 [ 2.368726] agpgart-intel 0000:00:00.0: Intel 440BX Chipset [ 2.372581] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0x0 [ 2.374407] [drm] Initialized drm 1.1.0 20060810 [ 2.377148] brd: module loaded [ 2.378821] loop: module loaded [ 2.379787] HP CISS Driver (v 3.6.26) [ 2.381288] vmw_vmci 0000:00:07.7: Found VMCI PCI device at 0x11080, irq 16 [ 2.383209] vmw_vmci 0000:00:07.7: Using capabilities 0xc [ 2.385464] Guest personality initialized and is active [ 2.387009] VMCI host device registered (name=vmci, major=10, minor=62) [ 2.388817] Initialized host personality [ 2.390445] mpt2sas version 16.100.00.00 loaded [ 2.391822] VMware PVSCSI driver - version 1.0.2.0-k [ 2.393878] scsi0 : ata_piix [ 2.394878] scsi1 : ata_piix [ 2.395744] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x1060 irq 14 [ 2.397605] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x1068 irq 15 [ 2.400167] bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) [ 2.406121] pcnet32: pcnet32.c:v1.35 21.Apr.2008 tsbogend@alpha.franken.de [ 2.408201] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 2.410084] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 2.788881] ata2.00: ATAPI: VMware Virtual IDE CDROM Drive, 00000001, max UDMA/33 [ 2.814823] e1000 0000:02:00.0 eth0: (PCI:66MHz:32-bit) 00:0c:29:55:5f:81 [ 2.816679] e1000 0000:02:00.0 eth0: Intel(R) PRO/1000 Network Connection [ 2.818534] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 2.820092] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. [ 2.821705] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.0.5-k [ 2.823504] igb: Copyright (c) 2007-2013 Intel Corporation. [ 2.825167] VMware vmxnet3 virtual NIC driver - version 1.2.0.0-k-NAPI [ 2.826976] Fusion MPT base driver 3.04.20 [ 2.828114] Copyright (c) 1999-2008 LSI Corporation [ 2.829435] Fusion MPT SPI Host driver 3.04.20 [ 2.831137] ata2.00: configured for UDMA/33 [ 2.832523] mptbase: ioc0: Initiating bringup [ 2.834148] scsi 1:0:0:0: CD-ROM NECVMWar VMware IDE CDR10 1.00 PQ: 0 ANSI: 5 [ 2.836817] sr0: scsi3-mmc drive: 1x/1x writer dvd-ram cd/rw xa/form2 cdda tray [ 2.838827] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 2.840704] sr 1:0:0:0: Attached scsi generic sg0 type 5 [ 3.009600] ioc0: LSI53C1030 B0: Capabilities={Initiator} [ 3.421176] scsi2 : ioc0: LSI53C1030 B0, FwRev=01032920h, Ports=1, MaxQ=128, IRQ=17 [ 3.708611] scsi 2:0:0:0: Direct-Access VMware, VMware Virtual S 1.0 PQ: 0 ANSI: 2 [ 3.716530] scsi target2:0:0: Beginning Domain Validation [ 3.724599] scsi target2:0:0: Domain Validation skipping write tests [ 3.730941] scsi target2:0:0: Ending Domain Validation [ 3.736253] scsi target2:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127) [ 3.744688] sd 2:0:0:0: [sda] 25165824 512-byte logical blocks: (12.8 GB/12.0 GiB) [ 3.752658] sd 2:0:0:0: [sda] Write Protect is off [ 3.757832] sd 2:0:0:0: [sda] Cache data unavailable [ 3.759650] sd 2:0:0:0: [sda] Assuming drive cache: write through [ 3.762307] sd 2:0:0:0: [sda] Cache data unavailable [ 3.764020] sd 2:0:0:0: [sda] Assuming drive cache: write through [ 3.766858] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 3.770432] Fusion MPT FC Host driver 3.04.20 [ 3.772014] Fusion MPT SAS Host driver 3.04.20 [ 3.773597] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 3.775812] ehci-pci: EHCI PCI platform driver [ 3.777423] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 3.779786] ohci-pci: OHCI PCI platform driver [ 3.781432] sda: sda1 sda2 sda3 sda4 [ 3.783001] uhci_hcd: USB Universal Host Controller Interface driver [ 3.785415] i8042: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MOUS] at 0x60,0x64 irq 1,12 [ 3.789311] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 3.790656] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 3.792305] sd 2:0:0:0: [sda] Cache data unavailable [ 3.793666] sd 2:0:0:0: [sda] Assuming drive cache: write through [ 3.795290] sd 2:0:0:0: [sda] Attached SCSI disk [ 3.796781] mousedev: PS/2 mouse device common for all mice [ 3.819487] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 [ 3.821298] rtc_cmos 00:03: alarms up to one month, y3k, 114 bytes nvram, hpet irqs [ 3.823516] md: linear personality registered for level -1 [ 3.825009] md: raid0 personality registered for level 0 [ 3.826460] md: raid1 personality registered for level 1 [ 3.827859] md: raid10 personality registered for level 10 [ 3.829431] md: raid6 personality registered for level 6 [ 3.830889] md: raid5 personality registered for level 5 [ 3.832312] md: raid4 personality registered for level 4 [ 3.833881] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1 [ 3.836312] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com [ 3.840511] device-mapper: raid: Loading target version 1.5.2 [ 3.842381] usbcore: registered new interface driver usbhid [ 3.843885] usbhid: USB HID core driver [ 3.844941] Netfilter messages via NETLINK v0.30. [ 3.846245] nf_conntrack version 0.5.0 (7912 buckets, 31648 max) [ 3.848046] ctnetlink v0.93: registering with nfnetlink. [ 3.849550] ip_tables: (C) 2000-2006 Netfilter Core Team [ 3.851051] TCP: cubic registered [ 3.851972] TCP: vegas registered [ 3.852898] TCP: veno registered [ 3.853791] TCP: yeah registered [ 3.854664] Initializing XFRM netlink socket [ 3.855837] NET: Registered protocol family 17 [ 3.857065] Key type dns_resolver registered [ 3.859251] bio: create slab <bio-1> at 1 [ 3.860859] Btrfs loaded [ 3.866693] rtc_cmos 00:03: setting system clock to 2014-04-25 07:58:15 UTC (1398412695) [ 4.046211] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input3 [ 4.055141] md: Skipping autodetection of RAID arrays. (raid=autodetect will force) [ 4.062867] Waiting for root device uuid=2ba08fbc-4b95-46cc-b638-299f16462620... ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 17:30 Can anyone boot a system using btrfs root with linux 3.14 or newer? Пламен Петров 2014-04-23 18:33 ` Swâmi Petaramesh 2014-04-23 18:54 ` Marc MERLIN @ 2014-04-23 19:06 ` Kai Krakow 2014-04-23 20:25 ` Calvin Walton 2014-04-23 22:34 ` Chris Murphy 2014-04-24 3:23 ` Chris Murphy 3 siblings, 2 replies; 39+ messages in thread From: Kai Krakow @ 2014-04-23 19:06 UTC (permalink / raw) To: linux-btrfs Пламен Петров <plamen@petrovi.no-ip.info> schrieb: I'm going with the module suggestion from Marc, too. > /dev/sda2 / btrfs relatime,compress=zlib 0 0 This line looks kinda useless to me. The compress=zlib option won't be applied at boot and cannot be changed at runtime because AFAIR btrfs does not allow that yet. This is because during initial mount by the kernel, /etc/fstab has not yet been read (and cannot for obvious reasons). The only way around it is to also append rootflags= to the kernel cmdline. This also explains why in a few other cases btrfs cannot be mounted, although it should make no difference in your case except the compress option won't be applied to the running file system. Also, you may want to try rootdelay=2 or something similar, it sometimes help mounting btrfs at boot. But first try the suggestion abount baking the btrfs module right into the kernel. -- Replies to list only preferred. ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 19:06 ` Kai Krakow @ 2014-04-23 20:25 ` Calvin Walton 2014-04-23 22:34 ` Chris Murphy 1 sibling, 0 replies; 39+ messages in thread From: Calvin Walton @ 2014-04-23 20:25 UTC (permalink / raw) To: Kai Krakow; +Cc: linux-btrfs On Wed, 2014-04-23 at 21:06 +0200, Kai Krakow wrote: > Пламен Петров <plamen@petrovi.no-ip.info> schrieb: > > I'm going with the module suggestion from Marc, too. > > > /dev/sda2 / btrfs relatime,compress=zlib 0 0 > > This line looks kinda useless to me. The compress=zlib option won't be > applied at boot and cannot be changed at runtime because AFAIR btrfs does > not allow that yet. ... My understanding is that the compress= option on btrfs *can* be changed at run time. After remounting with a compress= option, later writes will be done using the newly selected algorithm. The compress= option is filesystem-wide, you cannot currently use different compress= options for different subvolumes. Mounting a subvolume with a different compress= option will change the compression algorithm for all mounted subvolumes on that filesystem. (Note that I wouldn't recommend zlib on most systems as a / filesystem - it's slow to decompress compared to lzo, so it will cause slower boots if your disk is reasonably fast.) -- Calvin Walton <calvin.walton@kepstin.ca> ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 19:06 ` Kai Krakow 2014-04-23 20:25 ` Calvin Walton @ 2014-04-23 22:34 ` Chris Murphy 1 sibling, 0 replies; 39+ messages in thread From: Chris Murphy @ 2014-04-23 22:34 UTC (permalink / raw) To: Btrfs BTRFS On Apr 23, 2014, at 1:06 PM, Kai Krakow <hurikhan77+btrfs@gmail.com> wrote: > Пламен Петров <plamen@petrovi.no-ip.info> schrieb: > > I'm going with the module suggestion from Marc, too. > >> /dev/sda2 / btrfs relatime,compress=zlib 0 0 > > This line looks kinda useless to me. The compress=zlib option won't be > applied at boot and cannot be changed at runtime because AFAIR btrfs does > not allow that yet. So long as no other part of the same volume (including a subvolume) has been mounted, an ro rootfs remounted upon consultation of fstab will result in the fstab mount options being applied to remount. There might be a handful of btrfs options that don't work with remount, but compress isn't one of them. At least on Fedora since the dawn of btrfs, it's been possible to specify compress in fstab and its honored when rootfs is remounted rw. Also, relatime is default. So the cleaned up mount option for fstab for the above would be merely compress (zlib is the default). Chris Murphy ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-23 17:30 Can anyone boot a system using btrfs root with linux 3.14 or newer? Пламен Петров ` (2 preceding siblings ...) 2014-04-23 19:06 ` Kai Krakow @ 2014-04-24 3:23 ` Chris Murphy 2014-04-24 6:27 ` Fajar A. Nugraha 3 siblings, 1 reply; 39+ messages in thread From: Chris Murphy @ 2014-04-24 3:23 UTC (permalink / raw) To: Btrfs BTRFS It sounds like either a grub.cfg misconfiguration, or a failure to correctly build the initrd/initramfs. So I'd post the grub.cfg kernel command line for the boot entry that works and the entry that fails, for comparison. And then also check and see if whatever utility builds your initrd has been upgraded along with your kernel, maybe there's a bug/regression. Chris Murphy ^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? 2014-04-24 3:23 ` Chris Murphy @ 2014-04-24 6:27 ` Fajar A. Nugraha 0 siblings, 0 replies; 39+ messages in thread From: Fajar A. Nugraha @ 2014-04-24 6:27 UTC (permalink / raw) To: Btrfs BTRFS On Thu, Apr 24, 2014 at 10:23 AM, Chris Murphy <lists@colorremedies.com> wrote: > > It sounds like either a grub.cfg misconfiguration, or a failure to correctly build the initrd/initramfs. So I'd post the grub.cfg kernel command line for the boot entry that works and the entry that fails, for comparison. > > And then also check and see if whatever utility builds your initrd has been upgraded along with your kernel, maybe there's a bug/regression. > I believe the OP mentioned that he's using a distro without initrd, and that all required modules are built in. -- Fajar > > Chris Murphy-- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 39+ messages in thread
![[-- Attachment #2: rescue-media-plus-my-kernel-3.14.1.png --] [-- Type: image/png, Size: 46112 bytes --]](../../000001cf5f3e$aaf7a080$00e6e180$@petrovi.no-ip.info/2-rescue-media-plus-my-kernel-3.14.1.png){kind=link}
![[-- Attachment #2: debug-vm-panic.png --] [-- Type: image/png, Size: 46408 bytes --]](../../002301cf5fee$346fefc0$9d4fcf40$@petrovi.no-ip.info/2-debug-vm-panic.png){kind=link}
end of thread, other threads:[~2014-04-25 7:02 UTC | newest]
Thread overview: 39+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-23 17:30 Can anyone boot a system using btrfs root with linux 3.14 or newer? Пламен Петров
2014-04-23 18:33 ` Swâmi Petaramesh
2014-04-23 18:54 ` Marc MERLIN
2014-04-23 19:02 ` Hugo Mills
2014-04-23 19:06 ` Пламен Петров
2014-04-23 19:15 ` Marc MERLIN
2014-04-23 19:37 ` Пламен Петров
2014-04-23 20:58 ` Marc MERLIN
2014-04-23 21:54 ` Пламен Петров
2014-04-23 22:03 ` Marc MERLIN
2014-04-23 22:20 ` Пламен Петров
2014-04-23 22:40 ` Chris Murphy
2014-04-23 22:43 ` Hugo Mills
2014-04-23 22:50 ` Marc MERLIN
2014-04-23 22:53 ` Hugo Mills
2014-04-23 22:41 ` Hugo Mills
2014-04-24 12:34 ` Chris Mason
2014-04-24 12:36 ` Chris Mason
2014-04-24 17:08 ` Пламен Петров
2014-04-24 17:19 ` Пламен Петров
2014-04-24 17:33 ` Marc MERLIN
2014-04-24 17:44 ` Пламен Петров
2014-04-24 18:51 ` Пламен Петров
2014-04-24 19:31 ` Marc MERLIN
2014-04-24 20:26 ` Пламен Петров
2014-04-24 21:47 ` Chris Murphy
2014-04-24 21:06 ` Chris Murphy
2014-04-24 21:23 ` Пламен Петров
[not found] ` <000c01cf600b$b01f6cf0$105e46d0$@petrovi.no-ip.info>
2014-04-24 23:07 ` Marc MERLIN
2014-04-25 0:04 ` Chris Murphy
2014-04-25 0:08 ` Chris Mason
2014-04-25 5:04 ` Пламен Петров
2014-04-25 7:02 ` Duncan
2014-04-25 5:03 ` Пламен Петров
2014-04-23 19:06 ` Kai Krakow
2014-04-23 20:25 ` Calvin Walton
2014-04-23 22:34 ` Chris Murphy
2014-04-24 3:23 ` Chris Murphy
2014-04-24 6:27 ` Fajar A. Nugraha
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox