Re: Oops when rebooting 2.6.13-rc4-RT-V0.7.52-*
On Fri, 5 Aug 2005, Ingo Molnar wrote:
it's the first oops that matters. You could try to 'freeze' the system
after printing the first stacktrace, via the patch below - but debugging
boot-time crashes without logging support is a quite tedious process.
(maybe, if the crash happens after the ethernet card is detected, you
could try netconsole logging.)
Ingo
Index: linux/arch/i386/kernel/traps.c
===
--- linux.orig/arch/i386/kernel/traps.c
+++ linux/arch/i386/kernel/traps.c
@@ -170,6 +170,7 @@ void show_trace(struct task_struct *task
printk(" ===\n");
}
print_traces(task);
+ for (;;) raw_local_irq_disable();
show_held_locks(task);
}
I patched 52-16 with this and now I see at least part of the register
dump and the stack and call trace:
Process reboot(pid : 4551, threadinfo=f13f8000 task=f195f230 stack_left=7764
worst_left=-1)
stack: f13f8000 c0116042 0700 28121969
:
:
call trace:
[] disable_IO_APIC+0x5a/0x90 (8)
[] machine_restart+0x5/0xa (28)
[] sys_reboot+0x147/0x15b (4)
[] netdev_run_todo+0xa4/0x209 (4)
[] dev_change_flags+0xca/0xf3 (16)
[] devinet_IOCTL+0x419/0x526 (20)
[] invalidate_inode_buffers+0xa/0x5d (88)
[] kmem_cache_free+0x1/0x90 (8)
[] destroy_inode+0x4a/0x75 (24)
[] generic_forget_inode+0x102/0x136 (8)
[] iput+0x57/0x89 (12)
[] atomic_dec_and_spin_lock+0x30/0x40 (12)
[] dput+0x76/0x1b7 (12)
[] __fput+0x114/0x182 (16)
[] filp_close+0x33/0x60 (28)
[] sysenter_past_esp+0x54/0x75 (20)
my .config is attached.
hope this helps.
--
Charles D. (Chuck) Harding <[EMAIL PROTECTED]> Voice: 925-423-8879
Senior Computer Associate ICCDFax: 925-423-6961
Lawrence Livermore National Laboratory Computation Directorate
Livermore, CA USA http://www.llnl.gov GPG Public Key ID: B9EB6601
-- http://tinyurl.com/5w5ey ---
-- Heads I win, tails you lose. --
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.13-rc4-RT-V0.7.52-16
# Mon Aug 8 10:36:01 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
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 is not set
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 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 is not set
# CONFIG_MPENTIUMM is not set
CONFIG_MPENTIUM4=y
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_GENERIC_CALIBRATE_DELAY=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_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
# CONFIG_SMP is not set
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT_DESKTOP is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_RCU=y
CONFIG_PREEMPT_BKL=y
CONFIG_RCU_STATS=y
CONFIG_RCU_TORTURE_TEST=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_ASM_SEMAPHORES=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_IOAPIC_FAST=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
Re: Oops when rebooting 2.6.13-rc4-RT-V0.7.52-*
On Fri, 5 Aug 2005, Ingo Molnar wrote: it's the first oops that matters. You could try to 'freeze' the system after printing the first stacktrace, via the patch below - but debugging boot-time crashes without logging support is a quite tedious process. (maybe, if the crash happens after the ethernet card is detected, you could try netconsole logging.) Ingo Index: linux/arch/i386/kernel/traps.c === --- linux.orig/arch/i386/kernel/traps.c +++ linux/arch/i386/kernel/traps.c @@ -170,6 +170,7 @@ void show_trace(struct task_struct *task printk( ===\n); } print_traces(task); + for (;;) raw_local_irq_disable(); show_held_locks(task); } I patched 52-16 with this and now I see at least part of the register dump and the stack and call trace: Process reboot(pid : 4551, threadinfo=f13f8000 task=f195f230 stack_left=7764 worst_left=-1) stack: f13f8000 c0116042 0700 28121969 : : call trace: [] disable_IO_APIC+0x5a/0x90 (8) [] machine_restart+0x5/0xa (28) [] sys_reboot+0x147/0x15b (4) [] netdev_run_todo+0xa4/0x209 (4) [] dev_change_flags+0xca/0xf3 (16) [] devinet_IOCTL+0x419/0x526 (20) [] invalidate_inode_buffers+0xa/0x5d (88) [] kmem_cache_free+0x1/0x90 (8) [] destroy_inode+0x4a/0x75 (24) [] generic_forget_inode+0x102/0x136 (8) [] iput+0x57/0x89 (12) [] atomic_dec_and_spin_lock+0x30/0x40 (12) [] dput+0x76/0x1b7 (12) [] __fput+0x114/0x182 (16) [] filp_close+0x33/0x60 (28) [] sysenter_past_esp+0x54/0x75 (20) my .config is attached. hope this helps. -- Charles D. (Chuck) Harding [EMAIL PROTECTED] Voice: 925-423-8879 Senior Computer Associate ICCDFax: 925-423-6961 Lawrence Livermore National Laboratory Computation Directorate Livermore, CA USA http://www.llnl.gov GPG Public Key ID: B9EB6601 -- http://tinyurl.com/5w5ey --- -- Heads I win, tails you lose. -- # # Automatically generated make config: don't edit # Linux kernel version: 2.6.13-rc4-RT-V0.7.52-16 # Mon Aug 8 10:36:01 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION= CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_EXTRA_PASS=y 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 is not set CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 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 is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set CONFIG_X86_GENERIC=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_GENERIC_CALIBRATE_DELAY=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_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y # CONFIG_SMP is not set # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT_DESKTOP is not set CONFIG_PREEMPT_RT=y CONFIG_PREEMPT=y CONFIG_PREEMPT_SOFTIRQS=y CONFIG_PREEMPT_HARDIRQS=y CONFIG_PREEMPT_RCU=y CONFIG_PREEMPT_BKL=y CONFIG_RCU_STATS=y CONFIG_RCU_TORTURE_TEST=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_ASM_SEMAPHORES=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y
Re: Oops when rebooting 2.6.13-rc4-RT-V0.7.52-*
* Chuck Harding <[EMAIL PROTECTED]> wrote:
> couldn't see the beginning of the oops but at the end was
> Init: no more processes left in this run level
> and have to power cycle to be able to boot. I tried vanilla -rc4, -rc5
> and -rc4-mm1 which all worked just fine. But all 3 of the -RT versions
> I have on hand (08,10,13) showed the same symptom.
>
> This is my desktop system - Dell Optiplex GX-240 2GHz P4 1Gb SDRAM ATI
> Radeon VE/7000 QY SB Live! Value. Dell FP2000 RHEL 4.0 KDE 3.3
>
> I don't have serial console debugging capability here at work, so what
> can I do to debug this? Thanks.
it's the first oops that matters. You could try to 'freeze' the system
after printing the first stacktrace, via the patch below - but debugging
boot-time crashes without logging support is a quite tedious process.
(maybe, if the crash happens after the ethernet card is detected, you
could try netconsole logging.)
Ingo
Index: linux/arch/i386/kernel/traps.c
===
--- linux.orig/arch/i386/kernel/traps.c
+++ linux/arch/i386/kernel/traps.c
@@ -170,6 +170,7 @@ void show_trace(struct task_struct *task
printk(" ===\n");
}
print_traces(task);
+ for (;;) raw_local_irq_disable();
show_held_locks(task);
}
-
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: Oops when rebooting 2.6.13-rc4-RT-V0.7.52-*
* Chuck Harding [EMAIL PROTECTED] wrote: couldn't see the beginning of the oops but at the end was Init: no more processes left in this run level and have to power cycle to be able to boot. I tried vanilla -rc4, -rc5 and -rc4-mm1 which all worked just fine. But all 3 of the -RT versions I have on hand (08,10,13) showed the same symptom. This is my desktop system - Dell Optiplex GX-240 2GHz P4 1Gb SDRAM ATI Radeon VE/7000 QY SB Live! Value. Dell FP2000 RHEL 4.0 KDE 3.3 I don't have serial console debugging capability here at work, so what can I do to debug this? Thanks. it's the first oops that matters. You could try to 'freeze' the system after printing the first stacktrace, via the patch below - but debugging boot-time crashes without logging support is a quite tedious process. (maybe, if the crash happens after the ethernet card is detected, you could try netconsole logging.) Ingo Index: linux/arch/i386/kernel/traps.c === --- linux.orig/arch/i386/kernel/traps.c +++ linux/arch/i386/kernel/traps.c @@ -170,6 +170,7 @@ void show_trace(struct task_struct *task printk( ===\n); } print_traces(task); + for (;;) raw_local_irq_disable(); show_held_locks(task); } - 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/
