Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad?
Correcting my previous message, and confirming Leroy's one : linux-2.6.20.tar.gz : bad linux-2.6.20.1.tar.gz: bad linux-2.6.20.2.tar.gz: good linux-2.6.20.3.tar.gz: good With : COMPAT_VDSO=y CONFIG_HIGHMEM64G=y So problem have been solved with 2.6.20.2 Nilshar. 2007/3/15, Leroy van Logchem <[EMAIL PROTECTED]>: > Can you please double check this by trying with/without again -- sometimes bisects go bad. As requested I started to redo the test but now without git using kernel.org tars. The results now are, still using the same .config: linux-2.6.20.tar.gz : bad linux-2.6.20.1.tar.gz: bad (boot log equal) linux-2.6.20.2.tar.gz: good linux-2.6.20.3.tar.gz: good (triple checked) Really strange. Nilshar, please try these kernels too with: COMPAT_VDSO=y CONFIG_HIGHMEM64G=y - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] - Bad?
Correcting my previous message, and confirming Leroy's one : linux-2.6.20.tar.gz : bad linux-2.6.20.1.tar.gz: bad linux-2.6.20.2.tar.gz: good linux-2.6.20.3.tar.gz: good With : COMPAT_VDSO=y CONFIG_HIGHMEM64G=y So problem have been solved with 2.6.20.2 Nilshar. 2007/3/15, Leroy van Logchem [EMAIL PROTECTED]: Can you please double check this by trying with/without again -- sometimes bisects go bad. As requested I started to redo the test but now without git using kernel.org tars. The results now are, still using the same .config: linux-2.6.20.tar.gz : bad linux-2.6.20.1.tar.gz: bad (boot log equal) linux-2.6.20.2.tar.gz: good linux-2.6.20.3.tar.gz: good (triple checked) Really strange. Nilshar, please try these kernels too with: COMPAT_VDSO=y CONFIG_HIGHMEM64G=y - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad
Chuck Ebbert wrote: Leroy van Logchem wrote: Bisecting went well, after 13 compiles this commit was found: a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f Author: Roland McGrath <[EMAIL PROTECTED]> Date: Fri Jan 26 00:56:46 2007 -0800 [PATCH] Fix CONFIG_COMPAT_VDSO So you do have CONFIG_COMPAT_VDSO in your config, then? Yes. 2.6.20 and 2.6.20.1 hang using this .config: (Nilshar now also reported all is fine with 2.6.20.3) # Thu Mar 15 14:24:32 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_SYSFS_DEPRECATED=y CONFIG_INITRAMFS_SOURCE="" CONFIG_SYSCTL=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_EXTRA_PASS=y CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Block layer # CONFIG_BLOCK=y CONFIG_LBD=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y CONFIG_DEFAULT_CFQ=y CONFIG_DEFAULT_IOSCHED="cfq" # # Processor type and features # CONFIG_SMP=y CONFIG_X86_GENERICARCH=y CONFIG_X86_CYCLONE_TIMER=y CONFIG_M686=y CONFIG_X86_GENERIC=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_NR_CPUS=32 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y CONFIG_PREEMPT_VOLUNTARY=y CONFIG_PREEMPT_BKL=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_P4THERMAL=y CONFIG_VM86=y CONFIG_TOSHIBA=m CONFIG_I8K=m CONFIG_MICROCODE=m CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # CONFIG_EDD=m CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_HIGHMEM64G=y CONFIG_PAGE_OFFSET=0xC000 CONFIG_HIGHMEM=y CONFIG_X86_PAE=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_RESOURCES_64BIT=y CONFIG_HIGHPTE=y CONFIG_MTRR=y CONFIG_SECCOMP=y CONFIG_HZ_250=y CONFIG_HZ=250 CONFIG_PHYSICAL_START=0x10 CONFIG_PHYSICAL_ALIGN=0x10 CONFIG_COMPAT_VDSO=y CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y # # Power management options (ACPI, APM) # CONFIG_PM=y CONFIG_PM_LEGACY=y # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y CONFIG_ACPI_ASUS=m CONFIG_ACPI_TOSHIBA=m CONFIG_ACPI_BLACKLIST_YEAR=2001 CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # # APM (Advanced Power Management) BIOS Support # CONFIG_APM=y CONFIG_APM_CPU_IDLE=y CONFIG_APM_RTC_IS_GMT=y # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=m # # CPUFreq processor drivers # CONFIG_X86_ACPI_CPUFREQ=y CONFIG_X86_POWERNOW_K6=m CONFIG_X86_POWERNOW_K7=y CONFIG_X86_POWERNOW_K7_ACPI=y CONFIG_X86_SPEEDSTEP_CENTRINO=y CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y CONFIG_X86_SPEEDSTEP_ICH=y CONFIG_X86_P4_CLOCKMOD=m CONFIG_X86_LONGRUN=y CONFIG_X86_LONGHAUL=y # # shared options # CONFIG_X86_SPEEDSTEP_LIB=y # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_MSI=y CONFIG_HT_IRQ=y CONFIG_ISA_DMA_API=y CONFIG_ISA=y CONFIG_K8_NB=y # # PCCARD (PCMCIA/CardBus) support # # # PCI Hotplug Support # # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # # Networking # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_XFRM=y CONFIG_XFRM_USER=y CONFIG_NET_KEY=m CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_ASK_IP_FIB_HASH=y
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad
Leroy van Logchem wrote: > > Bisecting went well, after 13 compiles this commit was found: > > a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit > commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f > Author: Roland McGrath <[EMAIL PROTECTED]> > Date: Fri Jan 26 00:56:46 2007 -0800 > > [PATCH] Fix CONFIG_COMPAT_VDSO > So you do have CONFIG_COMPAT_VDSO in your config, then? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad?
Andi Kleen wrote: Where does it hang exactly? Do you have a boot log? Linux version 2.6.20 ([EMAIL PROTECTED]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)) #1 SMP Thu Mar 15 11:06:29 CET 2007 BIOS-provided physical RAM map: sanitize start sanitize end copy_e820_map() start: size: 0009b800 end: 0009b800 type: 1 copy_e820_map() type is E820_RAM copy_e820_map() start: 0009b800 size: 4800 end: 000a type: 2 copy_e820_map() start: 000ca000 size: 2000 end: 000cc000 type: 2 copy_e820_map() start: 000e4000 size: 0001c000 end: 0010 type: 2 copy_e820_map() start: 0010 size: cfe7 end: cff7 type: 1 copy_e820_map() type is E820_RAM copy_e820_map() start: cff7 size: 8000 end: cff78000 type: 3 copy_e820_map() start: cff78000 size: 8000 end: cff8 type: 4 copy_e820_map() start: cff8 size: 0008 end: d000 type: 2 copy_e820_map() start: e000 size: 1000 end: f000 type: 2 copy_e820_map() start: fec0 size: 0001 end: fec1 type: 2 copy_e820_map() start: fee0 size: 1000 end: fee01000 type: 2 copy_e820_map() start: ff80 size: 0040 end: ffc0 type: 2 copy_e820_map() start: fc00 size: 0400 end: 0001 type: 2 copy_e820_map() start: 0001 size: 3000 end: 00013000 type: 1 copy_e820_map() type is E820_RAM BIOS-e820: - 0009b800 (usable) BIOS-e820: 0009b800 - 000a (reserved) BIOS-e820: 000ca000 - 000cc000 (reserved) BIOS-e820: 000e4000 - 0010 (reserved) BIOS-e820: 0010 - cff7 (usable) BIOS-e820: cff7 - cff78000 (ACPI data) BIOS-e820: cff78000 - cff8 (ACPI NVS) BIOS-e820: cff8 - d000 (reserved) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ff80 - ffc0 (reserved) BIOS-e820: fc00 - 0001 (reserved) BIOS-e820: 0001 - 00013000 (usable) 3968MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000f5d00 NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 4096 Normal 4096 -> 229376 HighMem229376 -> 1245184 early_node_map[1] active PFN ranges 0:0 -> 1245184 DMI present. Using APIC driver default ACPI: PM-Timer IO Port: 0x1008 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled) Processor #6 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled) Processor #7 15:4 APIC version 20 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: IOAPIC (id[0x03] address[0xfec1] gsi_base[24]) IOAPIC[1]: apic_id 3, version 32, address 0xfec1, GSI 24-47 ACPI: IOAPIC (id[0x04] address[0xfec8] gsi_base[48]) IOAPIC[2]: apic_id 4, version 32, address 0xfec8, GSI 48-71 ACPI: IOAPIC (id[0x05] address[0xfec80400] gsi_base[72]) IOAPIC[3]: apic_id 5, version 32, address 0xfec80400, GSI 72-95 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Enabling APIC mode: Flat. Using 4 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at d100 (gap: d000:1000) Detected 3200.406 MHz processor. Built 1 zonelists. Total pages: 1233024 Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb console=tty0 console=ttyS0,9600n8 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c0485000 soft=c0465000 PID hash table entries: 4096 (order: 12, 16384 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 4137600k/4980736k available (2344k kernel code, 54916k reserved, 855k data, 236k init, 3276224k highmem) virtual kernel memory layout: fixmap : 0xffc56000 - 0xf000 (3748 kB) pkmap : 0xffa0 - 0xffc0 (2048 kB) vmalloc : 0xf880 - 0xff9fe000 ( 113
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] - Bad?
Andi Kleen wrote: Where does it hang exactly? Do you have a boot log? Linux version 2.6.20 ([EMAIL PROTECTED]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)) #1 SMP Thu Mar 15 11:06:29 CET 2007 BIOS-provided physical RAM map: sanitize start sanitize end copy_e820_map() start: size: 0009b800 end: 0009b800 type: 1 copy_e820_map() type is E820_RAM copy_e820_map() start: 0009b800 size: 4800 end: 000a type: 2 copy_e820_map() start: 000ca000 size: 2000 end: 000cc000 type: 2 copy_e820_map() start: 000e4000 size: 0001c000 end: 0010 type: 2 copy_e820_map() start: 0010 size: cfe7 end: cff7 type: 1 copy_e820_map() type is E820_RAM copy_e820_map() start: cff7 size: 8000 end: cff78000 type: 3 copy_e820_map() start: cff78000 size: 8000 end: cff8 type: 4 copy_e820_map() start: cff8 size: 0008 end: d000 type: 2 copy_e820_map() start: e000 size: 1000 end: f000 type: 2 copy_e820_map() start: fec0 size: 0001 end: fec1 type: 2 copy_e820_map() start: fee0 size: 1000 end: fee01000 type: 2 copy_e820_map() start: ff80 size: 0040 end: ffc0 type: 2 copy_e820_map() start: fc00 size: 0400 end: 0001 type: 2 copy_e820_map() start: 0001 size: 3000 end: 00013000 type: 1 copy_e820_map() type is E820_RAM BIOS-e820: - 0009b800 (usable) BIOS-e820: 0009b800 - 000a (reserved) BIOS-e820: 000ca000 - 000cc000 (reserved) BIOS-e820: 000e4000 - 0010 (reserved) BIOS-e820: 0010 - cff7 (usable) BIOS-e820: cff7 - cff78000 (ACPI data) BIOS-e820: cff78000 - cff8 (ACPI NVS) BIOS-e820: cff8 - d000 (reserved) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ff80 - ffc0 (reserved) BIOS-e820: fc00 - 0001 (reserved) BIOS-e820: 0001 - 00013000 (usable) 3968MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000f5d00 NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 - 4096 Normal 4096 - 229376 HighMem229376 - 1245184 early_node_map[1] active PFN ranges 0:0 - 1245184 DMI present. Using APIC driver default ACPI: PM-Timer IO Port: 0x1008 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled) Processor #6 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled) Processor #7 15:4 APIC version 20 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: IOAPIC (id[0x03] address[0xfec1] gsi_base[24]) IOAPIC[1]: apic_id 3, version 32, address 0xfec1, GSI 24-47 ACPI: IOAPIC (id[0x04] address[0xfec8] gsi_base[48]) IOAPIC[2]: apic_id 4, version 32, address 0xfec8, GSI 48-71 ACPI: IOAPIC (id[0x05] address[0xfec80400] gsi_base[72]) IOAPIC[3]: apic_id 5, version 32, address 0xfec80400, GSI 72-95 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Enabling APIC mode: Flat. Using 4 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at d100 (gap: d000:1000) Detected 3200.406 MHz processor. Built 1 zonelists. Total pages: 1233024 Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb console=tty0 console=ttyS0,9600n8 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c0485000 soft=c0465000 PID hash table entries: 4096 (order: 12, 16384 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 4137600k/4980736k available (2344k kernel code, 54916k reserved, 855k data, 236k init, 3276224k highmem) virtual kernel memory layout: fixmap : 0xffc56000 - 0xf000 (3748 kB) pkmap : 0xffa0 - 0xffc0 (2048 kB) vmalloc : 0xf880 - 0xff9fe000 ( 113 MB)
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] - Bad
Leroy van Logchem wrote: Bisecting went well, after 13 compiles this commit was found: a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f Author: Roland McGrath [EMAIL PROTECTED] Date: Fri Jan 26 00:56:46 2007 -0800 [PATCH] Fix CONFIG_COMPAT_VDSO So you do have CONFIG_COMPAT_VDSO in your config, then? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] - Bad
Chuck Ebbert wrote: Leroy van Logchem wrote: Bisecting went well, after 13 compiles this commit was found: a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f Author: Roland McGrath [EMAIL PROTECTED] Date: Fri Jan 26 00:56:46 2007 -0800 [PATCH] Fix CONFIG_COMPAT_VDSO So you do have CONFIG_COMPAT_VDSO in your config, then? Yes. 2.6.20 and 2.6.20.1 hang using this .config: (Nilshar now also reported all is fine with 2.6.20.3) # Thu Mar 15 14:24:32 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # Code maturity level options # CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_SYSFS_DEPRECATED=y CONFIG_INITRAMFS_SOURCE= CONFIG_SYSCTL=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_EXTRA_PASS=y CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Block layer # CONFIG_BLOCK=y CONFIG_LBD=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y CONFIG_DEFAULT_CFQ=y CONFIG_DEFAULT_IOSCHED=cfq # # Processor type and features # CONFIG_SMP=y CONFIG_X86_GENERICARCH=y CONFIG_X86_CYCLONE_TIMER=y CONFIG_M686=y CONFIG_X86_GENERIC=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_NR_CPUS=32 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y CONFIG_PREEMPT_VOLUNTARY=y CONFIG_PREEMPT_BKL=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_P4THERMAL=y CONFIG_VM86=y CONFIG_TOSHIBA=m CONFIG_I8K=m CONFIG_MICROCODE=m CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # CONFIG_EDD=m CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_HIGHMEM64G=y CONFIG_PAGE_OFFSET=0xC000 CONFIG_HIGHMEM=y CONFIG_X86_PAE=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_RESOURCES_64BIT=y CONFIG_HIGHPTE=y CONFIG_MTRR=y CONFIG_SECCOMP=y CONFIG_HZ_250=y CONFIG_HZ=250 CONFIG_PHYSICAL_START=0x10 CONFIG_PHYSICAL_ALIGN=0x10 CONFIG_COMPAT_VDSO=y CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y # # Power management options (ACPI, APM) # CONFIG_PM=y CONFIG_PM_LEGACY=y # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y CONFIG_ACPI_ASUS=m CONFIG_ACPI_TOSHIBA=m CONFIG_ACPI_BLACKLIST_YEAR=2001 CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # # APM (Advanced Power Management) BIOS Support # CONFIG_APM=y CONFIG_APM_CPU_IDLE=y CONFIG_APM_RTC_IS_GMT=y # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=m # # CPUFreq processor drivers # CONFIG_X86_ACPI_CPUFREQ=y CONFIG_X86_POWERNOW_K6=m CONFIG_X86_POWERNOW_K7=y CONFIG_X86_POWERNOW_K7_ACPI=y CONFIG_X86_SPEEDSTEP_CENTRINO=y CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y CONFIG_X86_SPEEDSTEP_ICH=y CONFIG_X86_P4_CLOCKMOD=m CONFIG_X86_LONGRUN=y CONFIG_X86_LONGHAUL=y # # shared options # CONFIG_X86_SPEEDSTEP_LIB=y # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_MSI=y CONFIG_HT_IRQ=y CONFIG_ISA_DMA_API=y CONFIG_ISA=y CONFIG_K8_NB=y # # PCCARD (PCMCIA/CardBus) support # # # PCI Hotplug Support # # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # # Networking # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_XFRM=y CONFIG_XFRM_USER=y CONFIG_NET_KEY=m CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_ASK_IP_FIB_HASH=y CONFIG_IP_FIB_HASH=y
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad
On Thursday 15 March 2007 02:01, Andrew Morton wrote: > > On Wed, 14 Mar 2007 17:52:01 + (UTC) Leroy van Logchem <[EMAIL > > PROTECTED]> wrote: > > Leroy van Logchem wldelft.nl> writes: > > Where does it hang exactly? Do you have a boot log? > > > > > None whatsoever. Three people are reporting this and it's a drop-dead > > > > > showstopper for a 2.6.21 release so we just have to wait until someone > > > > > wakes up and thinks about it. > > > > > > The topic should be "when CONFIG_HIGHMEM64G=y" imo. > > > > > > I'll try to do my first bi-sect today. > > Thanks. Please always do reply-to-all. Cc's restored (and added..) > > > Bisecting went well, after 13 compiles this commit was found: > > > > a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit > > commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f > > Author: Roland McGrath <[EMAIL PROTECTED]> > > Date: Fri Jan 26 00:56:46 2007 -0800 Can you please double check this by trying with/without again -- sometimes bisects go bad. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad
> On Wed, 14 Mar 2007 17:52:01 + (UTC) Leroy van Logchem <[EMAIL > PROTECTED]> wrote: > Leroy van Logchem wldelft.nl> writes: > > > > > > > None whatsoever. Three people are reporting this and it's a drop-dead > > > > showstopper for a 2.6.21 release so we just have to wait until someone > > > > wakes up and thinks about it. > > > > The topic should be "when CONFIG_HIGHMEM64G=y" imo. > > > > I'll try to do my first bi-sect today. Thanks. Please always do reply-to-all. Cc's restored (and added..) > Bisecting went well, after 13 compiles this commit was found: > > a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit > commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f > Author: Roland McGrath <[EMAIL PROTECTED]> > Date: Fri Jan 26 00:56:46 2007 -0800 > > [PATCH] Fix CONFIG_COMPAT_VDSO > > I wouldn't mind if CONFIG_COMPAT_VDSO went away entirely. But if it's > there, > it should work properly. Currently it's quite haphazard: both real vma > and > fixmap are mapped, both are put in the two different AT_* slots, sysenter > returns to the vma address rather than the fixmap address, and core dumps > yet > are another story. > > This patch makes CONFIG_COMPAT_VDSO disable the real vma and use the > fixmap > area consistently. This makes it actually compatible with what the old > vdso > implementation did. > > Signed-off-by: Roland McGrath <[EMAIL PROTECTED]> > Cc: Ingo Molnar <[EMAIL PROTECTED]> > Cc: Paul Mackerras <[EMAIL PROTECTED]> > Cc: Benjamin Herrenschmidt <[EMAIL PROTECTED]> > Cc: Andi Kleen <[EMAIL PROTECTED]> > Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> > Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]> > > :04 04 802ab3366a651ecba28c8677fa84a9f7c506392b > f44adc4dcdab733e5965b68ccd0d643f0a550a80 M arch > :04 04 be1e217152d8b3fcd05f09aa2b3f4f9dcb8208aa > 46cc86427e861350dd3fef9469474c55119f27ce M include > > I had both CONFIG_COMPAT_VDSO=y and CONFIG_HIGHMEM64G=y configured. > Using a 4GB Supermicro 7044 SMP dual Xeon. Details upon request. > > -- > Leroy > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad
Leroy van Logchem wldelft.nl> writes: > > > > None whatsoever. Three people are reporting this and it's a drop-dead > > > showstopper for a 2.6.21 release so we just have to wait until someone > > > wakes up and thinks about it. > > The topic should be "when CONFIG_HIGHMEM64G=y" imo. > > I'll try to do my first bi-sect today. Bisecting went well, after 13 compiles this commit was found: a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f Author: Roland McGrath <[EMAIL PROTECTED]> Date: Fri Jan 26 00:56:46 2007 -0800 [PATCH] Fix CONFIG_COMPAT_VDSO I wouldn't mind if CONFIG_COMPAT_VDSO went away entirely. But if it's there, it should work properly. Currently it's quite haphazard: both real vma and fixmap are mapped, both are put in the two different AT_* slots, sysenter returns to the vma address rather than the fixmap address, and core dumps yet are another story. This patch makes CONFIG_COMPAT_VDSO disable the real vma and use the fixmap area consistently. This makes it actually compatible with what the old vdso implementation did. Signed-off-by: Roland McGrath <[EMAIL PROTECTED]> Cc: Ingo Molnar <[EMAIL PROTECTED]> Cc: Paul Mackerras <[EMAIL PROTECTED]> Cc: Benjamin Herrenschmidt <[EMAIL PROTECTED]> Cc: Andi Kleen <[EMAIL PROTECTED]> Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]> :04 04 802ab3366a651ecba28c8677fa84a9f7c506392b f44adc4dcdab733e5965b68ccd0d643f0a550a80 M arch :04 04 be1e217152d8b3fcd05f09aa2b3f4f9dcb8208aa 46cc86427e861350dd3fef9469474c55119f27ce M include I had both CONFIG_COMPAT_VDSO=y and CONFIG_HIGHMEM64G=y configured. Using a 4GB Supermicro 7044 SMP dual Xeon. Details upon request. -- Leroy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] - Bad
Leroy van Logchem leroy.vanlogchem at wldelft.nl writes: None whatsoever. Three people are reporting this and it's a drop-dead showstopper for a 2.6.21 release so we just have to wait until someone wakes up and thinks about it. The topic should be when CONFIG_HIGHMEM64G=y imo. I'll try to do my first bi-sect today. Bisecting went well, after 13 compiles this commit was found: a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f Author: Roland McGrath [EMAIL PROTECTED] Date: Fri Jan 26 00:56:46 2007 -0800 [PATCH] Fix CONFIG_COMPAT_VDSO I wouldn't mind if CONFIG_COMPAT_VDSO went away entirely. But if it's there, it should work properly. Currently it's quite haphazard: both real vma and fixmap are mapped, both are put in the two different AT_* slots, sysenter returns to the vma address rather than the fixmap address, and core dumps yet are another story. This patch makes CONFIG_COMPAT_VDSO disable the real vma and use the fixmap area consistently. This makes it actually compatible with what the old vdso implementation did. Signed-off-by: Roland McGrath [EMAIL PROTECTED] Cc: Ingo Molnar [EMAIL PROTECTED] Cc: Paul Mackerras [EMAIL PROTECTED] Cc: Benjamin Herrenschmidt [EMAIL PROTECTED] Cc: Andi Kleen [EMAIL PROTECTED] Signed-off-by: Andrew Morton [EMAIL PROTECTED] Signed-off-by: Linus Torvalds [EMAIL PROTECTED] :04 04 802ab3366a651ecba28c8677fa84a9f7c506392b f44adc4dcdab733e5965b68ccd0d643f0a550a80 M arch :04 04 be1e217152d8b3fcd05f09aa2b3f4f9dcb8208aa 46cc86427e861350dd3fef9469474c55119f27ce M include I had both CONFIG_COMPAT_VDSO=y and CONFIG_HIGHMEM64G=y configured. Using a 4GB Supermicro 7044 SMP dual Xeon. Details upon request. -- Leroy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] - Bad
On Wed, 14 Mar 2007 17:52:01 + (UTC) Leroy van Logchem [EMAIL PROTECTED] wrote: Leroy van Logchem leroy.vanlogchem at wldelft.nl writes: None whatsoever. Three people are reporting this and it's a drop-dead showstopper for a 2.6.21 release so we just have to wait until someone wakes up and thinks about it. The topic should be when CONFIG_HIGHMEM64G=y imo. I'll try to do my first bi-sect today. Thanks. Please always do reply-to-all. Cc's restored (and added..) Bisecting went well, after 13 compiles this commit was found: a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f Author: Roland McGrath [EMAIL PROTECTED] Date: Fri Jan 26 00:56:46 2007 -0800 [PATCH] Fix CONFIG_COMPAT_VDSO I wouldn't mind if CONFIG_COMPAT_VDSO went away entirely. But if it's there, it should work properly. Currently it's quite haphazard: both real vma and fixmap are mapped, both are put in the two different AT_* slots, sysenter returns to the vma address rather than the fixmap address, and core dumps yet are another story. This patch makes CONFIG_COMPAT_VDSO disable the real vma and use the fixmap area consistently. This makes it actually compatible with what the old vdso implementation did. Signed-off-by: Roland McGrath [EMAIL PROTECTED] Cc: Ingo Molnar [EMAIL PROTECTED] Cc: Paul Mackerras [EMAIL PROTECTED] Cc: Benjamin Herrenschmidt [EMAIL PROTECTED] Cc: Andi Kleen [EMAIL PROTECTED] Signed-off-by: Andrew Morton [EMAIL PROTECTED] Signed-off-by: Linus Torvalds [EMAIL PROTECTED] :04 04 802ab3366a651ecba28c8677fa84a9f7c506392b f44adc4dcdab733e5965b68ccd0d643f0a550a80 M arch :04 04 be1e217152d8b3fcd05f09aa2b3f4f9dcb8208aa 46cc86427e861350dd3fef9469474c55119f27ce M include I had both CONFIG_COMPAT_VDSO=y and CONFIG_HIGHMEM64G=y configured. Using a 4GB Supermicro 7044 SMP dual Xeon. Details upon request. -- Leroy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] - Bad
On Thursday 15 March 2007 02:01, Andrew Morton wrote: On Wed, 14 Mar 2007 17:52:01 + (UTC) Leroy van Logchem [EMAIL PROTECTED] wrote: Leroy van Logchem leroy.vanlogchem at wldelft.nl writes: Where does it hang exactly? Do you have a boot log? None whatsoever. Three people are reporting this and it's a drop-dead showstopper for a 2.6.21 release so we just have to wait until someone wakes up and thinks about it. The topic should be when CONFIG_HIGHMEM64G=y imo. I'll try to do my first bi-sect today. Thanks. Please always do reply-to-all. Cc's restored (and added..) Bisecting went well, after 13 compiles this commit was found: a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f Author: Roland McGrath [EMAIL PROTECTED] Date: Fri Jan 26 00:56:46 2007 -0800 Can you please double check this by trying with/without again -- sometimes bisects go bad. -Andi - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
