Looking at your stack trace, it looks like the most recent calls are
timer related. Here are some 2.6 code snapshots:
---------------
from s390/kernel/time.c:
/*
* timer_interrupt() needs to keep up the real-time clock,
* as well as call the "do_timer()" routine every clocktick
*/
void account_ticks(struct pt_regs *regs)
[snip]
#ifdef CONFIG_VIRT_CPU_ACCOUNTING
account_tick_ytime(current);
#else
while (ticks--)
update_process_times(user_mode(regs));
#endif
---------------
update_process_times() calls run_local_timers()..
run_local_timers() calls softlockup_tick()..
---------------
from kernel/softlockup.c:
void softlockup_tick(void)
[snip]
if (time_after(jiffies, touch_timestamp + 10*HZ)) {
[snip]
printk(KERN_ERR "BUG: soft lockup detected on CPU#%d!\n",
this_cpu);
dump_stack();
[..]
---------------
I would look into timer-related config differences (.config from kernel
source) and/or timer-related patches between the vanilla kernel and the
distro's kernel. Maybe something will jump out..
--
Brad Hinson <[EMAIL PROTECTED]>
Technical Account Manager
Red Hat, Inc.
On Fri, 2006-10-06 at 15:44 -0400, Greg Keuken wrote:
> Using the SUSE distro! Original kernal was based on the 2.6.5 (SLES9) with
> SP3.
>
>
>
>
>
>
> "Post, Mark K" <[EMAIL PROTECTED]>
> Sent by: Linux on 390 Port <[email protected]>
> 10/06/2006 03:32 PM
> Please respond to
> Linux on 390 Port <[email protected]>
>
>
> To
> [email protected]
> cc
>
> Subject
> Re: Soft Lockup detected on CPU#
>
>
>
>
>
>
> What distribution are you using? If it was SUSE or Red Hat, they have a
> fair amount of modifications that they make to the kernel source. A
> number of their other packages expect those modifications to be there.
> I don't know that having them missing could cause this sort of problem,
> but I wouldn't be surprised that it could, either.
>
>
> Mark Post
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Greg Keuken
> Sent: Friday, October 06, 2006 2:56 PM
> To: [email protected]
> Subject: BUG: Soft Lockup detected on CPU#
>
> Hello,
>
> I've been playing around with my kernel (sounds almost rude) on our z890
> LPAR (via sources from kernel.org) and received the following error
> after
> upgrading. Everything stills boots up fine. I am not sure what this
> error
> is indicating or what is its cause.
> Upgraded to kernel level 2.6.18 with prepatch 2.6.19-rc1. I was
> previously
> at 2.6.5 and did not encounter these lockups.
>
> Anyone else out there on s390 at this kernel level with any issues or
> anyone know where I might start looking for cause!
>
> Take it easy on me ... I'm new!!
>
> Greg
>
> Error follows:
>
>
> BUG: soft lockup detected on CPU#0!
> 000000001ff8bae8 00000000005957e8 00000000003787c0 00000000003787c0
> 0000000000105122 0400000000000000 000000000056f500
> 0000000000570300
> 0000000000501d30 0000000000000000 0000000000000000
> 000000010000000b
> 000000001ff8baa8 00000000003558c0 0000000000105122
> 000000001ff8ba48
> 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> Call Trace:
> ([<0000000000105064>] show_trace+0x5c/0xc0)
> [<000000000010518e>] show_stack+0xc6/0xec
> [<00000000001051d8>] dump_stack+0x24/0x34
> [<000000000015587e>] softlockup_tick+0x106/0x12c
> [<0000000000132e4e>] run_local_timers+0x26/0x34
> [<0000000000132ee2>] update_process_times+0x86/0xc8
> [<00000000001056dc>] account_ticks+0x1c0/0x220
> [<00000000001092ee>] do_extint+0xf2/0xf8
> [<000000000010dad4>] ext_int_handler+0xa0/0xa4
> [<0000000000255eec>] kref_put+0x7c/0xc4
> ([<000000001f7b84c8>] 0x1f7b84c8)
> [<000000000035098a>] klist_dec_and_del+0x26/0x34
> [<00000000003509ea>] klist_next+0x52/0xd8
> [<0000000000273be8>] next_device+0x1c/0x40
> [<0000000000273c6a>] bus_find_device+0x5e/0xa8
> [<00000000002916f8>] get_subchannel_by_schid+0x34/0x58
> [<0000000000291fbc>] reprobe_subchannel+0x74/0xfc
> [<0000000000291452>] reprobe_all+0xde/0x160
> [<000000000013c220>] run_workqueue+0x64/0x158
> [<000000000013c43a>] worker_thread+0x126/0x16c
> [<0000000000141ec6>] kthread+0x11e/0x154
> [<0000000000105afe>] kernel_thread_starter+0x6/0xc
> [<0000000000105af8>] kernel_thread_starter+0x0/0xc
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>
>
>
> *********************************************************************
> The information in this e-mail is intended solely for the addressee(s)
> named, and is confidential. Any other distribution, disclosure or
> copying is strictly prohibited. If you have received this communication
> in error, please reply by e-mail to the sender and delete or destroy all
> copies of this message.
>
> Les renseignements contenus dans le pr'esent message 'electronique sont
> confidentiels et concernent exclusivement le(s) destinataire(s)
> 'esign'e(s). Il est strictement interdit de distribuer ou de copier ce
> message. Si vous avez recu ce message par erreur, veuillez r'epondre
> par courriel `a l'exp'editeur et effacer ou d'etruire toutes les copies du
> pr'esent message..
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
