Hi all, Changes since next-20080529: The ide tree got a build failure that required several newly out of lined routines to be exported. The rr tree picked up another conflict with the driver-core tree. The semaphore-removal tree still needed three patches reverted because simi= lar patches were merged into upstream and the scsi-rc-fixes trees. I have applied the following temporary patch for known build problems: "Fix various 8390 builds" - the net tree broke builds on various architectures - hopefully this patch will go into the net tree shortly. "hil_kbd: restore pci_ids.h" - this is to fix a patch in the semaphore tree and hopefully will be fixed there shortly. The "sparc: fallout from pci_name() constifying" patch is no longer needed. ---------------------------------------------------------------------------- I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" as mentioned in the FAQ on the wiki (see below). You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the final fixups, it is also built with powerpc allnoconfig, 44x_defconfig and allyesconfig and i386, sparc and sparc64 defconfig. Below is a summary of the state of the merge. We are up to 81 trees (counting Linus' and 13 trees of patches pending for Linus' tree), more are welcome (even if they are currently empty). Thanks to those who have contributed, and to those who haven't, please do. Status of my local build tests will be ...
Last next kernel booting for me is next-20080527. I didn't try next-20080528, but next-20080529 and next-20080530 fail to boot. Git told me to revert a63ef28f149c113740c7e429072351078a8821c6 (x86: fix bootmem crash). After reverting above commit, next-20080530 boots again. Basicly I'm running Fedora 9 with the linux-next kernel. See attached screenshot of boot error. config is: # # Automatically generated make config: don't edit # Linux kernel version: 2.6.26-rc4 # Sun Jun 1 11:35:05 2008 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" # CONFIG_GENERIC_LOCKBREAK is not set CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y # CONFIG_GENERIC_GPIO is not set CONFIG_ARCH_MAY_HAVE_PC_FDC=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y # CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not ...
hm, that commit is gone in latest tip - does tip/master boot fine for you? It's: http://people.redhat.com/mingo/tip.git/README that commit was an interim fix that got removed meanwhile and replaced with the real fixes. Ingo --
I just booted next-20080602 successfully, and the latest commit on file arch/x86/kernel/setup_32.c is: 4efc5450e19128e0c77fbfdf4a14804f5a4a1d95 (Merge branch 'x86/numa' into auto-x86-next). So yes, the original commit causing the error for me is gone. Thanks and greets. thomas --
