* RE: 2.6.12 with dual way dual core ck804 MB
@ 2005-06-24 18:56 YhLu
0 siblings, 0 replies; 21+ messages in thread
From: YhLu @ 2005-06-24 18:56 UTC (permalink / raw)
To: Andi Kleen; +Cc: Peter Buckingham, linux-kernel
Andi,
Thanks for the patch, I tried that with my LinuxBIOS + 8way dual core.
It works well.
I'm using that with 2.6.12, because 2.6.11 has problem with nvidia
chipset....
~ # cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
CPU6 CPU7 CPU8 CPU9 CPU10 CPU11 CPU12
CPU13 CPU14 CPU15
0: 378977 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-edge timer
2: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 XT-PIC cascade
4: 1284 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-edge serial
8: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-edge rtc
20: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level ehci_hcd:usb1
21: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level ohci_hcd:usb2
22: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level libata
23: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level libata
NMI: 781 661 48 51 51 51
51 51 51 51 53 52 53
53 53 53
LOC: 378822 378680 379254 379214 379172 379131
379088 379046 379004 378962 378921 378877 378834
378791 378748 378705
ERR: 55
and all int come to first cpu now.
the problem is the 2.6.12 timing problem with nvidia chipset is still there,
i hope that i have time to dubug it for your next week.
YH
> -----Original Message-----
> From: Andi Kleen [mailto:ak@suse.de]
> Sent: Wednesday, June 22, 2005 5:13 PM
> To: YhLu
> Cc: Andi Kleen; Peter Buckingham; linux-kernel@vger.kernel.org
> Subject: Re: 2.6.12 with dual way dual core ck804 MB
>
> On Wed, Jun 22, 2005 at 05:07:44PM -0700, YhLu wrote:
> > actually with LinuxBIOS I can boot into 8 way dual core system.
> >
> > But it will randomly hang. acutally when using cat /proc/interrupts.
>
> Because it needs physical addressing, not logical like it is
> used right now.
> That it works at all is surprising.
>
> -Andi
>
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-30 18:54 ` Andrew Vasquez
@ 2005-06-30 20:54 ` Eric W. Biederman
0 siblings, 0 replies; 21+ messages in thread
From: Eric W. Biederman @ 2005-06-30 20:54 UTC (permalink / raw)
To: Andrew Vasquez; +Cc: linux-kernel, YhLu, Andi Kleen, Peter Buckingham
Andrew Vasquez <andrew.vasquez@qlogic.com> writes:
>> A couple more tidbits of information on this problem.
>>
>> 1) I have seen this on two different boards
>> a Tyan S4882 and a Arima HDAMA, with and without linuxbios.
>> In just messing around adding "debug" on the kernel command line
>> or changing Dprintk in smpboot.c:smp_callin() to printk,
>> avoids this boot lock up for me.
>
> All,
>
> Has there been any resolution to this problem. I've just tried
> 2.6.13-rc1 on a Dell PowerEdge 2850 (dual-proc em64t) and am running
> into what appears to be a similar case where cpu initialization never
> completes. I'll attach my .config, boot-up messages, and the output
> of lspci.
>
> I've also tried the s/Dprintk/printk/ hack with no success.
I can confirm that I am seeing this on Xeons as well with my problem
2.6.12 kernel. And specifying debug does cause it to go away, for me.
As for which debug messages cause the bug not to be trigger I am
logging to the serial console which may be part of the difference.
Eric
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-24 23:47 YhLu
2005-06-29 2:40 ` Eric W. Biederman
@ 2005-06-30 18:54 ` Andrew Vasquez
2005-06-30 20:54 ` Eric W. Biederman
1 sibling, 1 reply; 21+ messages in thread
From: Andrew Vasquez @ 2005-06-30 18:54 UTC (permalink / raw)
To: linux-kernel; +Cc: YhLu, Andi Kleen, Peter Buckingham, ebiederm
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
> > YhLu <YhLu@tyan.com> writes:
> > start from 2.6.12.rc5.
>
> A couple more tidbits of information on this problem.
>
> 1) I have seen this on two different boards
> a Tyan S4882 and a Arima HDAMA, with and without linuxbios.
> In just messing around adding "debug" on the kernel command line
> or changing Dprintk in smpboot.c:smp_callin() to printk,
> avoids this boot lock up for me.
All,
Has there been any resolution to this problem. I've just tried
2.6.13-rc1 on a Dell PowerEdge 2850 (dual-proc em64t) and am running
into what appears to be a similar case where cpu initialization never
completes. I'll attach my .config, boot-up messages, and the output
of lspci.
I've also tried the s/Dprintk/printk/ hack with no success.
Thanks,
Andrew Vasquez
[-- Attachment #2: config --]
[-- Type: text/plain, Size: 20610 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.13-rc1
# Thu Jun 30 10:38:40 2005
#
CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_CMPXCHG=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_HOTPLUG=y
# CONFIG_KOBJECT_UEVENT is not set
# CONFIG_IKCONFIG is not set
# CONFIG_CPUSETS is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_KMOD is not set
CONFIG_STOP_MACHINE=y
#
# Processor type and features
#
# CONFIG_MK8 is not set
CONFIG_MPSC=y
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_L1_CACHE_BYTES=128
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_X86_HT=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_MTRR=y
CONFIG_SMP=y
CONFIG_SCHED_SMT=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
# CONFIG_K8_NUMA is not set
# CONFIG_NUMA_EMU is not set
# CONFIG_NUMA is not set
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_NR_CPUS=4
# CONFIG_HOTPLUG_CPU is not set
CONFIG_HPET_TIMER=y
CONFIG_X86_PM_TIMER=y
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_GART_IOMMU is not set
CONFIG_DUMMY_IOMMU=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_PHYSICAL_START=0x100000
# CONFIG_KEXEC is not set
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_ISA_DMA_API=y
#
# Power management options
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
# CONFIG_ACPI_BUTTON is not set
# CONFIG_ACPI_VIDEO is not set
# CONFIG_ACPI_FAN is not set
CONFIG_ACPI_PROCESSOR=y
# CONFIG_ACPI_THERMAL is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_CONTAINER is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_UNORDERED_IO is not set
CONFIG_PCIEPORTBUS=y
# CONFIG_HOTPLUG_PCI_PCIE is not set
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_PCI_DEBUG=y
#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set
#
# PCI Hotplug Support
#
CONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_ACPI is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_IA32_EMULATION is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
# CONFIG_PNP is not set
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA 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_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD 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=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_LBD is not set
# CONFIG_CDROM_PKTCDVD is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_ATA_OVER_ETH is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
CONFIG_BLK_DEV_SVWKS=y
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=y
# CONFIG_SCSI_ISCSI_ATTRS is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX 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_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC 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_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
CONFIG_SCSI_QLA2300=m
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 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
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
CONFIG_FUSION=y
CONFIG_FUSION_SPI=y
# CONFIG_FUSION_FC is not set
CONFIG_FUSION_MAX_SGE=128
# CONFIG_FUSION_CTL is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_IP_TCPDIAG=y
# CONFIG_IP_TCPDIAG_IPV6 is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_BIC=y
# CONFIG_IPV6 is not set
# CONFIG_NETFILTER is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# 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_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# Ethernet (10 or 100Mbit)
#
# CONFIG_NET_ETHERNET is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=y
CONFIG_E1000_NAPI=y
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SKGE is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
CONFIG_NETCONSOLE=m
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
CONFIG_RAW_DRIVER=y
# CONFIG_HPET is not set
CONFIG_MAX_RAW_DEVS=256
# CONFIG_HANGCHECK_TIMER is not set
#
# TPM devices
#
# CONFIG_TCG_TPM is not set
#
# I2C support
#
CONFIG_I2C=y
# CONFIG_I2C_CHARDEV is not set
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
#
# I2C Hardware Bus support
#
# 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 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_ISA is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set
#
# Hardware Sensors Chip support
#
# CONFIG_I2C_SENSOR is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 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_MAX1619 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
#
# Other I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
# CONFIG_FB is not set
CONFIG_VIDEO_SELECT=y
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
# CONFIG_USB is not set
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# MMC/SD Card support
#
# CONFIG_MMC is not set
#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set
#
# SN Devices
#
#
# Firmware Drivers
#
# CONFIG_EDD is not set
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
CONFIG_JBD_DEBUG=y
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
#
# XFS support
#
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVPTS_FS_XATTR is not set
# CONFIG_TMPFS is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Profiling support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=y
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_LOG_BUF_SHIFT=15
# CONFIG_SCHEDSTATS is not set
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_FS is not set
# CONFIG_INIT_DEBUG is not set
# CONFIG_KPROBES is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Hardware crypto devices
#
#
# Library routines
#
# CONFIG_CRC_CCITT is not set
CONFIG_CRC32=y
# CONFIG_LIBCRC32C is not set
[-- Attachment #3: boot.msg --]
[-- Type: text/plain, Size: 3459 bytes --]
Bootdata ok (command line is root=/dev/sda2 vga=1 selinux=0 resume=/dev/sda1 co)
Linux version 2.6.13-rc1 (root@elab2) (gcc version 3.3.3 (SuSE Linux)) #4 SMP T5
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 0000000000100000 - 000000007ffc0000 (usable)
BIOS-e820: 000000007ffc0000 - 000000007ffcfc00 (ACPI data)
BIOS-e820: 000000007ffcfc00 - 000000007ffff000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000fec90000 (reserved)
BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
ACPI: PM-Timer IO Port: 0x808
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:4 APIC version 16
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
Processor #6 15:4 APIC version 16
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
Processor #1 15:4 APIC version 16
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled)
Processor #7 15:4 APIC version 16
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: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[32])
IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 32-55
ACPI: IOAPIC (id[0x0a] address[0xfec83000] gsi_base[64])
IOAPIC[2]: apic_id 10, version 32, address 0xfec83000, GSI 64-87
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Setting APIC routing to flat
ACPI: HPET id: 0xffffffff base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 80000000 (gap: 7ffff000:60001000)
Built 1 zonelists
Kernel command line: root=/dev/sda2 vga=1 selinux=0 resume=/dev/sda1 console=tt0
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 131072 bytes)
time.c: Using 14.318180 MHz HPET timer.
time.c: Detected 3192.309 MHz processor.
Console: colour VGA+ 80x50
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Memory: 2057084k/2096896k available (2071k kernel code, 39220k reserved, 1499k )
Calibrating delay using timer specific routine.. 6389.91 BogoMIPS (lpj=12779828)
Mount-cache hash table entries: 256
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
using mwait in idle threads.
CPU: Physical Processor ID: 0
CPU0: Thermal monitoring enabled (TM1)
Using local APIC timer interrupts.
Detected 12.469 MHz APIC timer.
Booting processor 1/6 rip 6000 rsp ffff81007ff4df58
Initializing CPU#1
CPU#1 (phys ID: 6) waiting for CALLOUT
CALLIN, before setup_local_APIC().
Calibrating delay using timer specific routine.. 6384.64 BogoMIPS (lpj=12769291)
Stack at about ffff81007ff4def4
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 3
CPU1: Thermal monitoring enabled (TM1)
Intel(R) Xeon(TM) CPU 3.20GHz stepping 01
CPU 1: Syncing TSC to CPU 0.
Booting processor 2/1 rip 6000 rsp ffff8100032b7f58
Initializing CPU#2
CPU#2 (phys ID: 1) waiting for CALLOUT
CALLIN, before setup_local_APIC().
CPU 1: synchronized TSC with CPU 0 (last diff -4 cycles, maxerr 1240 cycles)
[-- Attachment #4: lspci.msg --]
[-- Type: text/plain, Size: 15278 bytes --]
0000:00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 09)
Subsystem: Dell: Unknown device 016d
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: [40] #09 [4105]
0000:00:02.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A0 (rev 09) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 10
Bus: primary=00, secondary=01, subordinate=03, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: dfd00000-dfffffff
Prefetchable memory behind bridge: 00000000d8000000-00000000d8f00000
Secondary status: SERR
Expansion ROM at 0000e000 [disabled] [size=4K]
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
Address: fee00000 Data: 0000
Capabilities: [64] #10 [0041]
0000:00:04.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port B0 (rev 09) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 10
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
Address: fee00000 Data: 0000
Capabilities: [64] #10 [0141]
0000:00:05.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port B1 (rev 09) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 10
Bus: primary=00, secondary=05, subordinate=07, sec-latency=0
I/O behind bridge: 0000c000-0000dfff
Memory behind bridge: df800000-dfcfffff
Secondary status: SERR
Expansion ROM at 0000c000 [disabled] [size=8K]
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
Address: fee00000 Data: 0000
Capabilities: [64] #10 [0041]
0000:00:06.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port C0 (rev 09) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 10
Bus: primary=00, secondary=08, subordinate=08, sec-latency=0
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: df600000-df7fffff
Expansion ROM at 0000b000 [disabled] [size=4K]
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
Address: fee00000 Data: 0000
Capabilities: [64] #10 [0141]
0000:00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev c2) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=09, subordinate=09, sec-latency=32
I/O behind bridge: 0000a000-0000afff
Memory behind bridge: df400000-df5fffff
Prefetchable memory behind bridge: d0000000-d7ffffff
BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: Dell: Unknown device 016d
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 0
Region 0: I/O ports at <unassigned>
Region 1: I/O ports at <unassigned>
Region 2: I/O ports at <unassigned>
Region 3: I/O ports at <unassigned>
Region 4: I/O ports at fc00 [size=16]
Region 5: Memory at 80000000 (32-bit, non-prefetchable) [size=1K]
0000:01:00.0 PCI bridge: Intel Corp. 80332 [Dobson] I/O processor (rev 06) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 10
Bus: primary=01, secondary=02, subordinate=02, sec-latency=64
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: dfe00000-dfffffff
Prefetchable memory behind bridge: 00000000d8000000-00000000d8f00000
Expansion ROM at 0000e000 [disabled] [size=4K]
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [44] #10 [0071]
Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [6c] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d8]
0000:01:00.2 PCI bridge: Intel Corp. 80332 [Dobson] I/O processor (rev 06) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 10
Bus: primary=01, secondary=03, subordinate=03, sec-latency=64
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [44] #10 [0071]
Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [6c] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d8]
0000:02:05.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 08)
Subsystem: Dell: Unknown device 016d
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 72 (4250ns min, 4500ns max), cache line size 10
Interrupt: pin A routed to IRQ 34
Region 0: I/O ports at ec00 [size=dff00000]
Region 1: Memory at dfef0000 (64-bit, non-prefetchable) [size=64K]
Region 3: Memory at dfee0000 (64-bit, non-prefetchable) [size=64K]
Expansion ROM at 00100000 [disabled]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [68]
0000:02:05.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 08)
Subsystem: Dell: Unknown device 016d
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 72 (4250ns min, 4500ns max), cache line size 10
Interrupt: pin B routed to IRQ 33
Region 0: I/O ports at e800 [size=dff00000]
Region 1: Memory at dfed0000 (64-bit, non-prefetchable) [size=64K]
Region 3: Memory at dfec0000 (64-bit, non-prefetchable) [size=64K]
Expansion ROM at 00100000 [disabled]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [68]
0000:05:00.0 PCI bridge: Intel Corp. PCI Bridge Hub A (rev 09) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 10
Bus: primary=05, secondary=06, subordinate=06, sec-latency=32
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: dfb00000-dfcfffff
Expansion ROM at 0000d000 [disabled] [size=4K]
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [44] #10 [0071]
Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [6c] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d8]
0000:05:00.2 PCI bridge: Intel Corp. PCI Bridge Hub B (rev 09) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 10
Bus: primary=05, secondary=07, subordinate=07, sec-latency=32
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: df900000-dfafffff
Expansion ROM at 0000c000 [disabled] [size=4K]
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [44] #10 [0071]
Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [6c] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d8]
0000:06:07.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05)
Subsystem: Dell: Unknown device 016d
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (63750ns min), cache line size 10
Interrupt: pin A routed to IRQ 64
Region 0: Memory at dfbe0000 (32-bit, non-prefetchable)
Region 2: I/O ports at dcc0 [size=64]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [e4] PCI-X non-bridge device.
Command: DPERE- ERO+ RBC=0 OST=0
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
0000:07:08.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05)
Subsystem: Dell: Unknown device 016d
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (63750ns min), cache line size 10
Interrupt: pin A routed to IRQ 65
Region 0: Memory at df9e0000 (32-bit, non-prefetchable)
Region 2: I/O ports at ccc0 [size=64]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [e4] PCI-X non-bridge device.
Command: DPERE- ERO+ RBC=0 OST=0
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
0000:08:00.0 Fibre Channel: QLogic Corp.: Unknown device 2432 (rev 02)
Subsystem: QLogic Corp.: Unknown device 0138
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 10
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at bc00 [size=df700000]
Region 1: Memory at df6fc000 (64-bit, non-prefetchable) [size=16K]
Expansion ROM at 00040000 [disabled]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [4c] #10 [0001]
Capabilities: [64] Message Signalled Interrupts: 64bit+ Queue=0/4 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [74] Vital Product Data
Capabilities: [7c] #11 [000f]
0000:08:00.1 Fibre Channel: QLogic Corp.: Unknown device 2432 (rev 02)
Subsystem: QLogic Corp.: Unknown device 0138
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 10
Interrupt: pin B routed to IRQ 17
Region 0: I/O ports at b800 [size=df700000]
Region 1: Memory at df6f8000 (64-bit, non-prefetchable) [size=16K]
Expansion ROM at 00040000 [disabled]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [4c] #10 [0001]
Capabilities: [64] Message Signalled Interrupts: 64bit+ Queue=0/4 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [74] Vital Product Data
Capabilities: [7c] #11 [000f]
0000:09:0d.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] (prog-if 00 [VGA])
Subsystem: Dell: Unknown device 016d
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+ ParErr- Stepping+ SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min), cache line size 10
Interrupt: pin A routed to IRQ 18
Region 0: Memory at d0000000 (32-bit, prefetchable)
Region 1: I/O ports at ac00 [size=256]
Region 2: Memory at df4f0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-24 23:47 YhLu
@ 2005-06-29 2:40 ` Eric W. Biederman
2005-06-30 18:54 ` Andrew Vasquez
1 sibling, 0 replies; 21+ messages in thread
From: Eric W. Biederman @ 2005-06-29 2:40 UTC (permalink / raw)
To: YhLu; +Cc: Andi Kleen, Peter Buckingham, linux-kernel
YhLu <YhLu@tyan.com> writes:
> start from 2.6.12.rc5.
A couple more tidbits of information on this problem.
1) I have seen this on two different boards
a Tyan S4882 and a Arima HDAMA, with and without linuxbios.
In just messing around adding "debug" on the kernel command line
or changing Dprintk in smpboot.c:smp_callin() to printk,
avoids this boot lock up for me.
Eric
^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: 2.6.12 with dual way dual core ck804 MB
@ 2005-06-29 1:01 YhLu
0 siblings, 0 replies; 21+ messages in thread
From: YhLu @ 2005-06-29 1:01 UTC (permalink / raw)
To: Andi Kleen; +Cc: Peter Buckingham, linux-kernel
andi,
some hints for you.
when using Opteron 875, the problem was more easily catched.
in smp_callin in smpboot.c
if change
Dprintk("CPU#%d (phys ID: %d) waiting for CALLOUT\n", cpuid, phys_id);
to
printk("CPU#%d (phys ID: %d) waiting for CALLOUT\n", cpuid, phys_id);
will have 50% to pass through.
if change
Dprintk("CALLIN, before setup_local_APIC().\n");
to
printk("CALLIN, before setup_local_APIC().\n");
will pass through every time.
YH
> -----Original Message-----
> From: YhLu
> Sent: Friday, June 24, 2005 4:44 PM
> To: 'Andi Kleen'
> Cc: Peter Buckingham; linux-kernel@vger.kernel.org
> Subject: RE: 2.6.12 with dual way dual core ck804 MB
>
> start from 2.6.12.rc5.
>
> YH
>
> > -----Original Message-----
> > From: Andi Kleen [mailto:ak@suse.de]
> > Sent: Friday, June 24, 2005 4:42 PM
> > To: YhLu
> > Cc: Andi Kleen; Peter Buckingham; linux-kernel@vger.kernel.org
> > Subject: Re: 2.6.12 with dual way dual core ck804 MB
> >
> > On Fri, Jun 24, 2005 at 04:42:58PM -0700, YhLu wrote:
> > > Andi,
> > >
> > > the timing problem come out from 2.6.12.rc5....
> >
> > What do you mean? It's gone or it started there?
> > -Andi
> >
^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: 2.6.12 with dual way dual core ck804 MB
@ 2005-06-24 23:47 YhLu
2005-06-29 2:40 ` Eric W. Biederman
2005-06-30 18:54 ` Andrew Vasquez
0 siblings, 2 replies; 21+ messages in thread
From: YhLu @ 2005-06-24 23:47 UTC (permalink / raw)
To: Andi Kleen; +Cc: Peter Buckingham, linux-kernel
start from 2.6.12.rc5.
YH
> -----Original Message-----
> From: Andi Kleen [mailto:ak@suse.de]
> Sent: Friday, June 24, 2005 4:42 PM
> To: YhLu
> Cc: Andi Kleen; Peter Buckingham; linux-kernel@vger.kernel.org
> Subject: Re: 2.6.12 with dual way dual core ck804 MB
>
> On Fri, Jun 24, 2005 at 04:42:58PM -0700, YhLu wrote:
> > Andi,
> >
> > the timing problem come out from 2.6.12.rc5....
>
> What do you mean? It's gone or it started there?
> -Andi
>
^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: 2.6.12 with dual way dual core ck804 MB
@ 2005-06-24 23:42 YhLu
2005-06-24 23:42 ` Andi Kleen
0 siblings, 1 reply; 21+ messages in thread
From: YhLu @ 2005-06-24 23:42 UTC (permalink / raw)
To: Andi Kleen; +Cc: Peter Buckingham, linux-kernel
Andi,
the timing problem come out from 2.6.12.rc5....
YH
> -----Original Message-----
> From: YhLu
> Sent: Friday, June 24, 2005 11:56 AM
> To: Andi Kleen
> Cc: Peter Buckingham; linux-kernel@vger.kernel.org
> Subject: RE: 2.6.12 with dual way dual core ck804 MB
>
> Andi,
>
> Thanks for the patch, I tried that with my LinuxBIOS + 8way dual core.
>
> It works well.
>
> I'm using that with 2.6.12, because 2.6.11 has problem with
> nvidia chipset....
>
> ~ # cat /proc/interrupts
> CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
> CPU6 CPU7 CPU8 CPU9 CPU10 CPU11
> CPU12
> CPU13 CPU14 CPU15
> 0: 378977 0 0 0 0 0
> 0 0 0 0 0 0 0
> 0 0 0 IO-APIC-edge timer
> 2: 0 0 0 0 0 0
> 0 0 0 0 0 0 0
> 0 0 0 XT-PIC cascade
> 4: 1284 0 0 0 0 0
> 0 0 0 0 0 0 0
> 0 0 0 IO-APIC-edge serial
> 8: 0 0 0 0 0 0
> 0 0 0 0 0 0 0
> 0 0 0 IO-APIC-edge rtc
> 20: 0 0 0 0 0 0
> 0 0 0 0 0 0 0
> 0 0 0 IO-APIC-level ehci_hcd:usb1
> 21: 0 0 0 0 0 0
> 0 0 0 0 0 0 0
> 0 0 0 IO-APIC-level ohci_hcd:usb2
> 22: 0 0 0 0 0 0
> 0 0 0 0 0 0 0
> 0 0 0 IO-APIC-level libata
> 23: 0 0 0 0 0 0
> 0 0 0 0 0 0 0
> 0 0 0 IO-APIC-level libata
> NMI: 781 661 48 51 51 51
> 51 51 51 51 53 52 53
> 53 53 53
> LOC: 378822 378680 379254 379214 379172 379131
> 379088 379046 379004 378962 378921 378877
> 378834
> 378791 378748 378705
> ERR: 55
>
> and all int come to first cpu now.
>
> the problem is the 2.6.12 timing problem with nvidia chipset
> is still there, i hope that i have time to dubug it for your
> next week.
>
> YH
>
> > -----Original Message-----
> > From: Andi Kleen [mailto:ak@suse.de]
> > Sent: Wednesday, June 22, 2005 5:13 PM
> > To: YhLu
> > Cc: Andi Kleen; Peter Buckingham; linux-kernel@vger.kernel.org
> > Subject: Re: 2.6.12 with dual way dual core ck804 MB
> >
> > On Wed, Jun 22, 2005 at 05:07:44PM -0700, YhLu wrote:
> > > actually with LinuxBIOS I can boot into 8 way dual core system.
> > >
> > > But it will randomly hang. acutally when using cat
> /proc/interrupts.
> >
> > Because it needs physical addressing, not logical like it is used
> > right now.
> > That it works at all is surprising.
> >
> > -Andi
> >
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to
> majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-24 23:42 YhLu
@ 2005-06-24 23:42 ` Andi Kleen
0 siblings, 0 replies; 21+ messages in thread
From: Andi Kleen @ 2005-06-24 23:42 UTC (permalink / raw)
To: YhLu; +Cc: Andi Kleen, Peter Buckingham, linux-kernel
On Fri, Jun 24, 2005 at 04:42:58PM -0700, YhLu wrote:
> Andi,
>
> the timing problem come out from 2.6.12.rc5....
What do you mean? It's gone or it started there?
-Andi
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-23 0:07 YhLu
@ 2005-06-23 0:12 ` Andi Kleen
0 siblings, 0 replies; 21+ messages in thread
From: Andi Kleen @ 2005-06-23 0:12 UTC (permalink / raw)
To: YhLu; +Cc: Andi Kleen, Peter Buckingham, linux-kernel
On Wed, Jun 22, 2005 at 05:07:44PM -0700, YhLu wrote:
> actually with LinuxBIOS I can boot into 8 way dual core system.
>
> But it will randomly hang. acutally when using
> cat /proc/interrupts.
Because it needs physical addressing, not logical like it is used right now.
That it works at all is surprising.
-Andi
^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: 2.6.12 with dual way dual core ck804 MB
@ 2005-06-23 0:07 YhLu
2005-06-23 0:12 ` Andi Kleen
0 siblings, 1 reply; 21+ messages in thread
From: YhLu @ 2005-06-23 0:07 UTC (permalink / raw)
To: Andi Kleen; +Cc: Peter Buckingham, linux-kernel
actually with LinuxBIOS I can boot into 8 way dual core system.
But it will randomly hang. acutally when using
cat /proc/interrupts.
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
CPU6 CPU7 CPU8 CPU9 CPU10 CPU11 CPU12
CPU13 CPU14 CPU15
0: 409 0 0 0 0 0
0 0 0 0 229 37399 0
0 0 0 IO-APIC-edge timer
2: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 XT-PIC cascade
4: 0 0 0 0 0 0
0 0 0 0 0 4915 0
0 0 0 IO-APIC-edge serial
8: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-edge rtc
14: 0 0 0 0 0 0
0 0 0 0 0 10 0
0 0 0 IO-APIC-edge ide0
19: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level ohci1394
20: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level libata
21: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level libata
22: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level ohci_hcd
23: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level ehci_hcd
NMI: 1 0 0 0 0 0
0 0 0 0 0 1 0
0 0 0
LOC: 37688 37965 37965 37965 37965 37965
37965 37965 37965 37965 37965 37446 37965
37965 37965 37966
ERR: 447
MIS: 0
I wonder why all int is direct to cpu8.
YH
> -----Original Message-----
> From: Andi Kleen [mailto:ak@suse.de]
> Sent: Wednesday, June 22, 2005 4:37 PM
> To: YhLu
> Cc: Peter Buckingham; Andi Kleen; linux-kernel@vger.kernel.org
> Subject: Re: 2.6.12 with dual way dual core ck804 MB
>
> On Wed, Jun 22, 2005 at 04:37:37PM -0700, YhLu wrote:
> > andi,
> >
> > do you mean the apic id lifting for opteron?
>
> Yes, with local APIC numbers > 8 physical mode needs to be
> used because logical mode only supports 8.
>
> -Andi
>
^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: 2.6.12 with dual way dual core ck804 MB
@ 2005-06-22 23:37 YhLu
2005-06-22 23:37 ` Andi Kleen
0 siblings, 1 reply; 21+ messages in thread
From: YhLu @ 2005-06-22 23:37 UTC (permalink / raw)
To: Peter Buckingham, Andi Kleen; +Cc: linux-kernel
andi,
do you mean the apic id lifting for opteron?
YH
> -----Original Message-----
> From: Peter Buckingham [mailto:peter@pantasys.com]
> Sent: Wednesday, June 22, 2005 4:32 PM
> To: Andi Kleen
> Cc: YhLu; linux-kernel@vger.kernel.org
> Subject: Re: 2.6.12 with dual way dual core ck804 MB
>
> Andi Kleen wrote:
> > There are two problems on AMD >8P. First the APIC
> addressing doesn't
> > work and needs to be done differently (I have a patch for
> that in the
> > final stages of testing). And then there is a mysterious scheduler
> > deadlock problem in 2.6.12 that I haven't tracked down yet.
> > 2.6.11+patch works though.
>
> okay, feel free to toss me the patch when your comfortable with it.
>
> thanks,
>
> peter
>
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-22 23:37 YhLu
@ 2005-06-22 23:37 ` Andi Kleen
0 siblings, 0 replies; 21+ messages in thread
From: Andi Kleen @ 2005-06-22 23:37 UTC (permalink / raw)
To: YhLu; +Cc: Peter Buckingham, Andi Kleen, linux-kernel
On Wed, Jun 22, 2005 at 04:37:37PM -0700, YhLu wrote:
> andi,
>
> do you mean the apic id lifting for opteron?
Yes, with local APIC numbers > 8 physical mode needs
to be used because logical mode only supports 8.
-Andi
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-22 23:10 ` Andi Kleen
@ 2005-06-22 23:31 ` Peter Buckingham
0 siblings, 0 replies; 21+ messages in thread
From: Peter Buckingham @ 2005-06-22 23:31 UTC (permalink / raw)
To: Andi Kleen; +Cc: YhLu, linux-kernel
Andi Kleen wrote:
> There are two problems on AMD >8P. First the APIC addressing doesn't
> work and needs to be done differently (I have a patch for that
> in the final stages of testing). And then there is a mysterious
> scheduler deadlock problem in 2.6.12 that I haven't tracked down yet.
> 2.6.11+patch works though.
okay, feel free to toss me the patch when your comfortable with it.
thanks,
peter
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-22 22:26 ` Peter Buckingham
@ 2005-06-22 23:10 ` Andi Kleen
2005-06-22 23:31 ` Peter Buckingham
0 siblings, 1 reply; 21+ messages in thread
From: Andi Kleen @ 2005-06-22 23:10 UTC (permalink / raw)
To: Peter Buckingham; +Cc: Andi Kleen, YhLu, linux-kernel
On Wed, Jun 22, 2005 at 03:26:10PM -0700, Peter Buckingham wrote:
> Andi Kleen wrote:
> >On Tue, Jun 21, 2005 at 02:41:52PM -0700, YhLu wrote:
> >It works for me on several dual core systems, except on a very big
> >one that seems to run into a scheduler problem.
>
> I'm having similar problems with a 16P x86_64. If I boot it with
> maxcpus=8 I have no problems. Is there some info that might be useful to
> help debug this problem?
There are two problems on AMD >8P. First the APIC addressing doesn't
work and needs to be done differently (I have a patch for that
in the final stages of testing). And then there is a mysterious
scheduler deadlock problem in 2.6.12 that I haven't tracked down yet.
2.6.11+patch works though.
-Andi
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-21 22:12 ` Andi Kleen
@ 2005-06-22 22:26 ` Peter Buckingham
2005-06-22 23:10 ` Andi Kleen
0 siblings, 1 reply; 21+ messages in thread
From: Peter Buckingham @ 2005-06-22 22:26 UTC (permalink / raw)
To: Andi Kleen; +Cc: YhLu, linux-kernel
Andi Kleen wrote:
> On Tue, Jun 21, 2005 at 02:41:52PM -0700, YhLu wrote:
> It works for me on several dual core systems, except on a very big
> one that seems to run into a scheduler problem.
I'm having similar problems with a 16P x86_64. If I boot it with
maxcpus=8 I have no problems. Is there some info that might be useful to
help debug this problem?
thanks,
peter
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-21 22:50 YhLu
@ 2005-06-21 23:55 ` Andi Kleen
0 siblings, 0 replies; 21+ messages in thread
From: Andi Kleen @ 2005-06-21 23:55 UTC (permalink / raw)
To: YhLu; +Cc: Andi Kleen, linux-kernel
On Tue, Jun 21, 2005 at 03:50:48PM -0700, YhLu wrote:
> I would like to help. Can you say more detail ? I don't know how to souce
> code tracing statement....
>
> Do you mean setup one global buffer, and in the setup.c compare the node id
> or node id to decide to write sth to the buffer, and print out when the cpu0
> get the control again?
Yes. You can just use a global variable because the smp bootup is essentially
single threaded. printk would destroy the timing though.
Start with the code that prints ExtInt enabled.
Writ current_text_address() into a buffer and dump it then on CPU #0
after some timeout (hopefully it is still alive)
If you have problems mail me and I will write you a tracing patch
tomorrow.
-Andi
^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: 2.6.12 with dual way dual core ck804 MB
@ 2005-06-21 22:50 YhLu
2005-06-21 23:55 ` Andi Kleen
0 siblings, 1 reply; 21+ messages in thread
From: YhLu @ 2005-06-21 22:50 UTC (permalink / raw)
To: Andi Kleen; +Cc: linux-kernel
I would like to help. Can you say more detail ? I don't know how to souce
code tracing statement....
Do you mean setup one global buffer, and in the setup.c compare the node id
or node id to decide to write sth to the buffer, and print out when the cpu0
get the control again?
YH
> -----Original Message-----
> From: Andi Kleen [mailto:ak@suse.de]
> Sent: Tuesday, June 21, 2005 3:36 PM
> To: YhLu
> Cc: Andi Kleen; linux-kernel@vger.kernel.org
> Subject: Re: 2.6.12 with dual way dual core ck804 MB
>
> On Tue, Jun 21, 2005 at 02:41:52PM -0700, YhLu wrote:
> > andi,
> >
> > for the dual way dual core Opteron ck804 MB, the 2.6.12
> still has the
> > timing problem, I still need to add one printk in
> amd_detec_cmp after
> > the phys_proc_id is setup.
>
> Can you perhaps do some debugging to find out where it hangs?
>
> e.g. you could let CPU #1 write into a buffer from source
> code tracing statement and then read that in CPU #0 after
> some time out. That should not disturb timing.
>
> -Andi
>
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-21 21:41 YhLu
2005-06-21 22:12 ` Andi Kleen
@ 2005-06-21 22:36 ` Andi Kleen
1 sibling, 0 replies; 21+ messages in thread
From: Andi Kleen @ 2005-06-21 22:36 UTC (permalink / raw)
To: YhLu; +Cc: Andi Kleen, linux-kernel
On Tue, Jun 21, 2005 at 02:41:52PM -0700, YhLu wrote:
> andi,
>
> for the dual way dual core Opteron ck804 MB, the 2.6.12 still has the timing
> problem, I still need to add one printk in amd_detec_cmp after the
> phys_proc_id is setup.
Can you perhaps do some debugging to find out where it hangs?
e.g. you could let CPU #1 write into a buffer from source
code tracing statement and then read that in CPU #0 after some time
out. That should not disturb timing.
-Andi
^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: 2.6.12 with dual way dual core ck804 MB
@ 2005-06-21 22:17 YhLu
0 siblings, 0 replies; 21+ messages in thread
From: YhLu @ 2005-06-21 22:17 UTC (permalink / raw)
To: Andi Kleen; +Cc: linux-kernel
just after starting core0 of node 1.
YH
Using local APIC timer interrupts.
Detected 12.564 MHz APIC timer.
Booting processor 1/1 rip 6000 rsp ffff81013ff89f58
Initializing CPU#1
masked ExtINT on CPU#1
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU 1(2) -> Node 0 -> Core 1
stepping 00
CPU 1: Syncing TSC to CPU 0.
Booting processor 2/2 rip 6000 rsp ffff81023ff11f58
Initializing CPU#2
masked ExtINT on CPU#2 --------------------------------------------here
> -----Original Message-----
> From: Andi Kleen [mailto:ak@suse.de]
> Sent: Tuesday, June 21, 2005 3:12 PM
> To: YhLu
> Cc: Andi Kleen; linux-kernel@vger.kernel.org
> Subject: Re: 2.6.12 with dual way dual core ck804 MB
>
> On Tue, Jun 21, 2005 at 02:41:52PM -0700, YhLu wrote:
> > andi,
> >
> > for the dual way dual core Opteron ck804 MB, the 2.6.12
> still has the
> > timing problem, I still need to add one printk in
> amd_detec_cmp after
> > the phys_proc_id is setup.
>
> It works for me on several dual core systems, except on a
> very big one that seems to run into a scheduler problem.
>
> Where exactly does yours lock up?
>
> -Andi
>
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: 2.6.12 with dual way dual core ck804 MB
2005-06-21 21:41 YhLu
@ 2005-06-21 22:12 ` Andi Kleen
2005-06-22 22:26 ` Peter Buckingham
2005-06-21 22:36 ` Andi Kleen
1 sibling, 1 reply; 21+ messages in thread
From: Andi Kleen @ 2005-06-21 22:12 UTC (permalink / raw)
To: YhLu; +Cc: Andi Kleen, linux-kernel
On Tue, Jun 21, 2005 at 02:41:52PM -0700, YhLu wrote:
> andi,
>
> for the dual way dual core Opteron ck804 MB, the 2.6.12 still has the timing
> problem, I still need to add one printk in amd_detec_cmp after the
> phys_proc_id is setup.
It works for me on several dual core systems, except on a very big
one that seems to run into a scheduler problem.
Where exactly does yours lock up?
-Andi
^ permalink raw reply [flat|nested] 21+ messages in thread
* 2.6.12 with dual way dual core ck804 MB
@ 2005-06-21 21:41 YhLu
2005-06-21 22:12 ` Andi Kleen
2005-06-21 22:36 ` Andi Kleen
0 siblings, 2 replies; 21+ messages in thread
From: YhLu @ 2005-06-21 21:41 UTC (permalink / raw)
To: Andi Kleen; +Cc: linux-kernel
andi,
for the dual way dual core Opteron ck804 MB, the 2.6.12 still has the timing
problem, I still need to add one printk in amd_detec_cmp after the
phys_proc_id is setup.
Regards
YH
static void __init amd_detect_cmp(struct cpuinfo_x86 *c)
{
#ifdef CONFIG_SMP
int cpu = smp_processor_id();
int node = 0;
unsigned bits;
if (c->x86_num_cores == 1)
return;
bits = 0;
while ((1 << bits) < c->x86_num_cores)
bits++;
/* Low order bits define the core id (index of core in socket) */
cpu_core_id[cpu] = phys_proc_id[cpu] & ((1 << bits)-1);
/* Convert the APIC ID into the socket ID */
phys_proc_id[cpu] >>= bits;
+ printk(KERN_INFO " CPU %d(%d) phys_proc_id %d Core %d\n",
+ cpu, c->x86_num_cores, phys_proc_id[cpu],
cpu_core_id[cpu]);
^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2005-06-30 20:56 UTC | newest]
Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-24 18:56 2.6.12 with dual way dual core ck804 MB YhLu
-- strict thread matches above, loose matches on Subject: below --
2005-06-29 1:01 YhLu
2005-06-24 23:47 YhLu
2005-06-29 2:40 ` Eric W. Biederman
2005-06-30 18:54 ` Andrew Vasquez
2005-06-30 20:54 ` Eric W. Biederman
2005-06-24 23:42 YhLu
2005-06-24 23:42 ` Andi Kleen
2005-06-23 0:07 YhLu
2005-06-23 0:12 ` Andi Kleen
2005-06-22 23:37 YhLu
2005-06-22 23:37 ` Andi Kleen
2005-06-21 22:50 YhLu
2005-06-21 23:55 ` Andi Kleen
2005-06-21 22:17 YhLu
2005-06-21 21:41 YhLu
2005-06-21 22:12 ` Andi Kleen
2005-06-22 22:26 ` Peter Buckingham
2005-06-22 23:10 ` Andi Kleen
2005-06-22 23:31 ` Peter Buckingham
2005-06-21 22:36 ` Andi Kleen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.