linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* bug on shutdown from 68-mm4
@ 2003-05-11  3:25 Martin J. Bligh
  2003-05-11  5:44 ` Andrew Morton
  0 siblings, 1 reply; 11+ messages in thread
From: Martin J. Bligh @ 2003-05-11  3:25 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel

Sorry if this is old news, haven't been paying attention for a week.
Bug on shutdown (just after it says "Power Down") from 68-mm4.
(the NUMA-Q).

Power down.
------------[ cut here ]------------
kernel BUG at arch/i386/kernel/smp.c:354!
invalid operand: 0000 [#1]
CPU:    0
EIP:    0060:[<c0113250>]    Not tainted VLI
EFLAGS: 00010293
EIP is at flush_tlb_others+0x20/0xa8
eax: 00000000   ebx: 00000000   ecx: eeb43220   edx: 00000002
esi: eeb43220   edi: eeb43220   ebp: 00000000   esp: ed3e1e58
ds: 007b   es: 007b   ss: 0068
Process halt (pid: 23618, threadinfo=ed3e0000 task=ef1d00c0)
Stack: c0113376 00000002 eeb43220 ffffffff c032c740 00000000 c013e16c eeb43220 
       eeb43220 ef1d00c0 fee1dead c032c740 0000000c c011a53f eeb43220 eeb43220 
       c011ddfe eeb43220 fee1dead ed3e0000 fee1dead ed3e0000 c0126dea 00000000 
Call Trace:
 [<c0113376>] flush_tlb_mm+0x6a/0x70
 [<c013e16c>] exit_mmap+0x148/0x1e4
 [<c011a53f>] mmput+0x5b/0x74
 [<c011ddfe>] do_exit+0x172/0x338
 [<c0126dea>] sys_reboot+0x1e2/0x2e8
 [<c011750d>] wake_up_process+0xd/0x14
 [<c012458f>] kill_proc_info+0x37/0x48
 [<c0124670>] kill_something_info+0xd0/0xd8
 [<c0125c35>] sys_kill+0x51/0x5c
 [<c01473c3>] filp_open+0x3b/0x5c
 [<c01187d2>] schedule+0x43a/0x500
 [<c0147799>] sys_open+0x59/0x74
 [<c0108c97>] syscall_call+0x7/0xb

Code: 0f b3 0d e0 94 32 c0 c3 8d 76 00 8b 54 24 04 8b 4c 24 08 85 d2 75 08 0f 0b 60 01 ea 73 23 c0 89 d0 23 05 a0 95 32 c0 39 d0 74 08 <0f> 0b 62 01 ea 73 23 c0 b8 00 e0 ff ff 21 e0 8b 40 10 0f a3 c2 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: bug on shutdown from 68-mm4
  2003-05-11  5:44 ` Andrew Morton
@ 2003-05-11  3:36   ` Martin J. Bligh
  2003-05-11  6:11     ` Andrew Morton
  0 siblings, 1 reply; 11+ messages in thread
From: Martin J. Bligh @ 2003-05-11  3:36 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 284 bytes --]

>> Sorry if this is old news, haven't been paying attention for a week.
>>  Bug on shutdown (just after it says "Power Down") from 68-mm4.
>>  (the NUMA-Q).
> 
> Random guess: is it related to CONFIG_KEXEC?

Don't think so - I don't have that enabled. Config file is attatched.

M.



[-- Attachment #2: config.larry --]
[-- Type: application/octet-stream, Size: 13533 bytes --]

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_SWAP=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# General setup
#
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=16

#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODULE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_X86_PC is not set
# CONFIG_X86_VOYAGER is not set
CONFIG_X86_NUMAQ=y
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_PREFETCH=y
CONFIG_X86_CMOV=y
# CONFIG_HUGETLB_PAGE is not set
CONFIG_SMP=y
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_NR_CPUS=32
CONFIG_NUMA=y
CONFIG_DISCONTIGMEM=y
CONFIG_HAVE_ARCH_BOOTMEM_NODE=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
CONFIG_X86_CPUID=y
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
# CONFIG_HIGHMEM4G is not set
CONFIG_HIGHMEM64G=y
# CONFIG_05GB is not set
CONFIG_1GB=y
# CONFIG_2GB is not set
# CONFIG_3GB is not set
CONFIG_HIGHMEM=y
CONFIG_X86_PAE=y
# CONFIG_HIGHPTE is not set
# CONFIG_4K_STACK is not set
CONFIG_SHAREPTE=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_100HZ=y
# CONFIG_1000HZ is not set
CONFIG_HAVE_DEC_LOCK=y

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI Support
#
# CONFIG_ACPI is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
CONFIG_PCI_GODIRECT=y
# CONFIG_PCI_GOANY is not set
CONFIG_PCI_DIRECT=y
# CONFIG_SCx200 is not set
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set

#
# Executable file formats
#
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y

#
# 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 is not set
# CONFIG_BLK_DEV_XD is not set
# 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_LOOP=y
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_LBD=y

#
# ATA/ATAPI/MFM/RLL device support
#
# CONFIG_IDE is not set

#
# SCSI device support
#
CONFIG_SCSI=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=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
# CONFIG_CHR_DEV_SG is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_REPORT_LUNS=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_NCR53C8XX is not set
# CONFIG_SCSI_SYM53C8XX is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
CONFIG_SCSI_QLOGIC_ISP=y
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# 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_NETLINK_DEV is not set
# CONFIG_NETFILTER is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_XFRM_USER is not set
# CONFIG_IPV6 is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE 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
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
CONFIG_ADAPTEC_STARFIRE=y
# CONFIG_ADAPTEC_STARFIRE_NAPI is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices (depends on LLC=y)
#
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# 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 I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
# CONFIG_SERIO is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_INPUT_MOUSE=y
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC 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_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256

#
# I2C support
#
# CONFIG_I2C is not set

#
# I2C Hardware Sensors Mainboard support
#

#
# I2C Hardware Sensors Chip support
#

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_INTEL_RNG=y
# CONFIG_AMD_RNG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_FAT_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
# CONFIG_JOLIET is not set
# CONFIG_ZISOFS is not set
# CONFIG_JFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_XFS_FS is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_CIFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_FS_MBCACHE=y

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB is not set

#
# Bluetooth support
#
# CONFIG_BT is not set

#
# Profiling support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=y

#
# Kernel hacking
#
# CONFIG_CRASH_DUMP is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_X86_REMOTE_DEBUG is not set
# CONFIG_DEBUG_IOVIRT is not set
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_EARLY_PRINTK is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_SPINLINE is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_KALLSYMS=y
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
CONFIG_CRC32=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: bug on shutdown from 68-mm4
  2003-05-11  3:25 bug on shutdown from 68-mm4 Martin J. Bligh
@ 2003-05-11  5:44 ` Andrew Morton
  2003-05-11  3:36   ` Martin J. Bligh
  0 siblings, 1 reply; 11+ messages in thread
From: Andrew Morton @ 2003-05-11  5:44 UTC (permalink / raw)
  To: Martin J. Bligh; +Cc: linux-kernel

"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> Sorry if this is old news, haven't been paying attention for a week.
>  Bug on shutdown (just after it says "Power Down") from 68-mm4.
>  (the NUMA-Q).

Random guess: is it related to CONFIG_KEXEC?

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: bug on shutdown from 68-mm4
  2003-05-11  3:36   ` Martin J. Bligh
@ 2003-05-11  6:11     ` Andrew Morton
  2003-05-11 14:47       ` Martin J. Bligh
  0 siblings, 1 reply; 11+ messages in thread
From: Andrew Morton @ 2003-05-11  6:11 UTC (permalink / raw)
  To: Martin J. Bligh; +Cc: linux-kernel

"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> >> Sorry if this is old news, haven't been paying attention for a week.
> >>  Bug on shutdown (just after it says "Power Down") from 68-mm4.
> >>  (the NUMA-Q).
> > 
> > Random guess: is it related to CONFIG_KEXEC?
> 
> Don't think so - I don't have that enabled. Config file is attatched.

It doesn't matter - the kexec patch tends to futz with stuff like that
regardless of CONFIG_KEXEC.

It doesn't happen here.  Could you please retest without the kexec
patch applied?


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: bug on shutdown from 68-mm4
  2003-05-11  6:11     ` Andrew Morton
@ 2003-05-11 14:47       ` Martin J. Bligh
  2003-05-11 18:37         ` bug on shutdown from 68-mm4 (machine_power_off returning causes problems) Eric W. Biederman
  0 siblings, 1 reply; 11+ messages in thread
From: Martin J. Bligh @ 2003-05-11 14:47 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel

>> >> Sorry if this is old news, haven't been paying attention for a week.
>> >>  Bug on shutdown (just after it says "Power Down") from 68-mm4.
>> >>  (the NUMA-Q).
>> > 
>> > Random guess: is it related to CONFIG_KEXEC?
>> 
>> Don't think so - I don't have that enabled. Config file is attatched.
> 
> It doesn't matter - the kexec patch tends to futz with stuff like that
> regardless of CONFIG_KEXEC.
> 
> It doesn't happen here.  Could you please retest without the kexec
> patch applied?

Yup, backing out kexec fixes it.


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: bug on shutdown from 68-mm4 (machine_power_off returning causes problems)
  2003-05-11 14:47       ` Martin J. Bligh
@ 2003-05-11 18:37         ` Eric W. Biederman
  2003-05-12  3:30           ` Martin J. Bligh
  0 siblings, 1 reply; 11+ messages in thread
From: Eric W. Biederman @ 2003-05-11 18:37 UTC (permalink / raw)
  To: Martin J. Bligh; +Cc: Andrew Morton, linux-kernel

"Martin J. Bligh" <mbligh@aracnet.com> writes:

> >> >> Sorry if this is old news, haven't been paying attention for a week.
> >> >>  Bug on shutdown (just after it says "Power Down") from 68-mm4.
> >> >>  (the NUMA-Q).
> >> > 
> >> > Random guess: is it related to CONFIG_KEXEC?
> >> 
> >> Don't think so - I don't have that enabled. Config file is attatched.
> > 
> > It doesn't matter - the kexec patch tends to futz with stuff like that
> > regardless of CONFIG_KEXEC.
> > 
> > It doesn't happen here.  Could you please retest without the kexec
> > patch applied?
> 
> Yup, backing out kexec fixes it.


Ok.  Thinking it through the differences is that I have machine_power_off
call stop_apics (which is roughly equivalent to the old smp_send_stop).

In the kexec patch that does 2 things.
1) It shuts down the secondary cpus, and returns the bootstrap cpu to
   virtual wire mode. 
2) It calls set_cpus_allowed to force the reboot to be on the primary
   cpu.

After returning from machine_power_off. We run into a problem
in flush_tlb_mm.  Because we have a cpu disabled, that is still part
of the mm's vm mask.

Does anyone know why machine_halt, and machine_power_off return?

If not I am just going to disable the return path.

Eric

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: bug on shutdown from 68-mm4 (machine_power_off returning causes problems)
  2003-05-11 18:37         ` bug on shutdown from 68-mm4 (machine_power_off returning causes problems) Eric W. Biederman
@ 2003-05-12  3:30           ` Martin J. Bligh
  2003-05-12 13:37             ` Eric W. Biederman
  0 siblings, 1 reply; 11+ messages in thread
From: Martin J. Bligh @ 2003-05-12  3:30 UTC (permalink / raw)
  To: Eric W. Biederman; +Cc: Andrew Morton, linux-kernel

>> Yup, backing out kexec fixes it.
> 
> 
> Ok.  Thinking it through the differences is that I have machine_power_off
> call stop_apics (which is roughly equivalent to the old smp_send_stop).

Mmmm. Not sure NUMA-Q will like disconnect_bsp_APIC() much, but I guess
that's my problem, not yours ;-) I can't do init 6 at the moment, so I'm
walking on thin ice as is ... if I have to fix a couple of things up for
NUMA-Q, that's no problem.

> In the kexec patch that does 2 things.
> 1) It shuts down the secondary cpus, and returns the bootstrap cpu to
>    virtual wire mode. 
> 2) It calls set_cpus_allowed to force the reboot to be on the primary
>    cpu.
> 
> After returning from machine_power_off. We run into a problem
> in flush_tlb_mm.  Because we have a cpu disabled, that is still part
> of the mm's vm mask.

OK ... I presume that's just because you shut down the secondaries then.
If so ... shouldn't it remove them from the relevant vm mask when it
offlines them? (probably not your code, but still)

> Does anyone know why machine_halt, and machine_power_off return?

Nope, thats ... odd ;-)

M.


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: bug on shutdown from 68-mm4 (machine_power_off returning causes problems)
  2003-05-12 13:37             ` Eric W. Biederman
@ 2003-05-12 12:43               ` Martin J. Bligh
  2003-05-13  9:35                 ` Eric W. Biederman
  2003-05-14 17:27                 ` Eric W. Biederman
  0 siblings, 2 replies; 11+ messages in thread
From: Martin J. Bligh @ 2003-05-12 12:43 UTC (permalink / raw)
  To: Eric W. Biederman; +Cc: Andrew Morton, linux-kernel

>> >> Yup, backing out kexec fixes it.
>> > 
>> > 
>> > Ok.  Thinking it through the differences is that I have machine_power_off
>> > call stop_apics (which is roughly equivalent to the old smp_send_stop).
>> 
>> Mmmm. Not sure NUMA-Q will like disconnect_bsp_APIC() much, but I guess
>> that's my problem, not yours ;-) I can't do init 6 at the moment, so I'm
>> walking on thin ice as is ... if I have to fix a couple of things up for
>> NUMA-Q, that's no problem.
> 
> Ah ok.  This could explain some of your problems with kexec if you
> can't even reboot the box....

Well, yes ... but I'm not trying to use kexec, just doing an init 0 ;-)
That worked fine before. Perhaps you want to take this code out of the
power down path, and just have it in the reboot path? Seems odd to change
the power down path if you don't need to.

> I have sent the fixed patches to Andrew and CC'd the list so we will
> see what develops.

Thanks, will try them sometime soon-ish ;-)

M.


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: bug on shutdown from 68-mm4 (machine_power_off returning causes problems)
  2003-05-12  3:30           ` Martin J. Bligh
@ 2003-05-12 13:37             ` Eric W. Biederman
  2003-05-12 12:43               ` Martin J. Bligh
  0 siblings, 1 reply; 11+ messages in thread
From: Eric W. Biederman @ 2003-05-12 13:37 UTC (permalink / raw)
  To: Martin J. Bligh; +Cc: Andrew Morton, linux-kernel

"Martin J. Bligh" <mbligh@aracnet.com> writes:

> >> Yup, backing out kexec fixes it.
> > 
> > 
> > Ok.  Thinking it through the differences is that I have machine_power_off
> > call stop_apics (which is roughly equivalent to the old smp_send_stop).
> 
> Mmmm. Not sure NUMA-Q will like disconnect_bsp_APIC() much, but I guess
> that's my problem, not yours ;-) I can't do init 6 at the moment, so I'm
> walking on thin ice as is ... if I have to fix a couple of things up for
> NUMA-Q, that's no problem.

Ah ok.  This could explain some of your problems with kexec if you
can't even reboot the box....
 
> > In the kexec patch that does 2 things.
> > 1) It shuts down the secondary cpus, and returns the bootstrap cpu to
> >    virtual wire mode. 
> > 2) It calls set_cpus_allowed to force the reboot to be on the primary
> >    cpu.
> > 
> > After returning from machine_power_off. We run into a problem
> > in flush_tlb_mm.  Because we have a cpu disabled, that is still part
> > of the mm's vm mask.
> 
> OK ... I presume that's just because you shut down the secondaries then.
> If so ... shouldn't it remove them from the relevant vm mask when it
> offlines them? (probably not your code, but still)

Right.  The code is more about shutting down the secondaries then off
lining them.  In a general purpose scenario I expect more would need
to happen.

> > Does anyone know why machine_halt, and machine_power_off return?
> 
> Nope, thats ... odd ;-)

That is what I thought.

I have sent the fixed patches to Andrew and CC'd the list so we will
see what develops.

Eric


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: bug on shutdown from 68-mm4 (machine_power_off returning causes problems)
  2003-05-12 12:43               ` Martin J. Bligh
@ 2003-05-13  9:35                 ` Eric W. Biederman
  2003-05-14 17:27                 ` Eric W. Biederman
  1 sibling, 0 replies; 11+ messages in thread
From: Eric W. Biederman @ 2003-05-13  9:35 UTC (permalink / raw)
  To: Martin J. Bligh; +Cc: Andrew Morton, linux-kernel

"Martin J. Bligh" <mbligh@aracnet.com> writes:

> Well, yes ... but I'm not trying to use kexec, just doing an init 0 ;-)
> That worked fine before. Perhaps you want to take this code out of the
> power down path, and just have it in the reboot path? Seems odd to change
> the power down path if you don't need to.

Fundamental rule of software reliability/simplicity.  Build one basket
and put all of your eggs in it.

I guess I can't possibly imagine why after a system halt anyone
would want random cpus scurrying around.  So this forces the issues
up to the from so they can be examined and fixed.

If the code is wrong from NUMA-Q I would like to get a correct version.
 
Eric

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: bug on shutdown from 68-mm4 (machine_power_off returning causes problems)
  2003-05-12 12:43               ` Martin J. Bligh
  2003-05-13  9:35                 ` Eric W. Biederman
@ 2003-05-14 17:27                 ` Eric W. Biederman
  1 sibling, 0 replies; 11+ messages in thread
From: Eric W. Biederman @ 2003-05-14 17:27 UTC (permalink / raw)
  To: Martin J. Bligh; +Cc: Andrew Morton, linux-kernel

"Martin J. Bligh" <mbligh@aracnet.com> writes:

> Well, yes ... but I'm not trying to use kexec, just doing an init 0 ;-)
> That worked fine before.

Just a last thought with my updated patch init 0 will continue to work
because it does not return machine_halt now.

Unless there was some magic I am missing.


^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2003-05-14 17:18 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-11  3:25 bug on shutdown from 68-mm4 Martin J. Bligh
2003-05-11  5:44 ` Andrew Morton
2003-05-11  3:36   ` Martin J. Bligh
2003-05-11  6:11     ` Andrew Morton
2003-05-11 14:47       ` Martin J. Bligh
2003-05-11 18:37         ` bug on shutdown from 68-mm4 (machine_power_off returning causes problems) Eric W. Biederman
2003-05-12  3:30           ` Martin J. Bligh
2003-05-12 13:37             ` Eric W. Biederman
2003-05-12 12:43               ` Martin J. Bligh
2003-05-13  9:35                 ` Eric W. Biederman
2003-05-14 17:27                 ` Eric W. Biederman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).