I am geeting messages like this: Jun 25 19:56:47 betsy kernel: BUG: soft lockup detected on CPU#2! Jun 25 19:56:47 betsy kernel: Jun 25 19:56:47 betsy kernel: Call Trace: Jun 25 19:56:47 betsy kernel: <IRQ> [<ffffffff800b2c85>] softlockup_tick+0xdb/0xed Jun 25 19:56:48 betsy kernel: [<ffffffff8003d0b6>] invalidate_bh_lru+0x0/0x42 Jun 25 19:56:48 betsy kernel: [<ffffffff800933d1>] update_process_times+0x42/0x68 Jun 25 19:56:48 betsy kernel: [<ffffffff80073d97>] smp_local_timer_interrupt+0x23/0x47 Jun 25 19:56:48 betsy kernel: [<ffffffff80074459>] smp_apic_timer_interrupt+0x41/0x47 Jun 25 19:56:48 betsy kernel: [<ffffffff8005bcc2>] apic_timer_interrupt+0x66/0x6c Jun 25 19:56:48 betsy kernel: <EOI> [<ffffffff800729ba>] __smp_call_function+0x64/0x8b Jun 25 19:56:48 betsy kernel: [<ffffffff800729b8>] __smp_call_function+0x62/0x8b Jun 25 19:56:48 betsy kernel: [<ffffffff8003d0b6>] invalidate_bh_lru+0x0/0x42 Jun 25 19:56:48 betsy kernel: [<ffffffff80072aee>] smp_call_function+0x32/0x47 Jun 25 19:56:48 betsy kernel: [<ffffffff8003d0b6>] invalidate_bh_lru+0x0/0x42 Jun 25 19:56:48 betsy kernel: [<ffffffff8008de7b>] on_each_cpu+0x10/0x22 Jun 25 19:56:48 betsy kernel: [<ffffffff800d14d9>] invalidate_bdev+0x2b/0x36 Jun 25 19:56:48 betsy kernel: [<ffffffff800d4a69>] kill_bdev+0xe/0x21 Jun 25 19:56:48 betsy kernel: [<ffffffff800d4f8f>] __blkdev_put+0x4f/0x169 Jun 25 19:56:48 betsy kernel: [<ffffffff80012281>] __fput+0xae/0x198 Jun 25 19:56:48 betsy kernel: [<ffffffff8002362c>] filp_close+0x5c/0x64 Jun 25 19:56:48 betsy kernel: [<ffffffff800384de>] put_files_struct+0x6c/0xc3 Jun 25 19:56:48 betsy kernel: [<ffffffff80014f01>] do_exit+0x2d2/0x8b1 Jun 25 19:56:48 betsy kernel: [<ffffffff80046e9b>] cpuset_exit+0x0/0x6c Jun 25 19:56:48 betsy kernel: [<ffffffff8005b2c1>] tracesys+0xd1/0xdc
I understand that the soft lockup happens when the kernel is holding a CPU for more that 10 seconds. I am trying to understand how to proceed in order to figure out which module is causing that. So, is there any documentation or howtos on how to do it? Thanks. Abdel... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jarod Wilson Sent: Tuesday, June 26, 2007 4:28 PM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: Re: [rhelv5-list] RE: kdump for soft lockup Sadek, Abdel wrote: > I am trying to get a kdump to investigate a BUG: soft lockup on CPU. but > when the soft lockup happens, the kdump does not get executed. > > So, The question is will the soft lockup trigger the kdump? No, because the system hasn't kernel panicked. > if not, is there an alternative? If you've got sysrq's enabled, hit alt-sysrq-c and I believe that should activate kdump. Dunno offhand if there's a way to make a soft lockup trigger a kp, but if so, that ought to do it too (and would probably be even better). -- Jarod Wilson [EMAIL PROTECTED] _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
