Re: BUG: Soft Lockup detected on CPU#
On Tue, Oct 10, 2006 at 01:24:20PM +0200, Martin Schwidefsky wrote: > On Tue, 2006-10-10 at 12:14 +0200, Carsten Otte wrote: > > > The way how the soft-lockup detection works right now is broken for > > > system that utilize virtual cpus. You could argue that all zSeries > > > systems use virtualized cpu so the feature does not make sense. > > With dedicated PUs on a logical partition, and when running on raw > > iron the feature should work fine afaict. No? > > Yes, in that special case it should work. But who is using dedicated PUs > on LPAR? 1% of the installed linux systems? The best thing to do is to > disable the config option, as it is harmful for the majority of the > systems. Heiko already sent a patch. The right thing would be to disable it for virtualized systems at runtime. Especially as S/390 is not the only virtualized system these days. I wonder why no one has hit this issue with Power5 or Xen systems yet. -- 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
Re: BUG: Soft Lockup detected on CPU#
I am using a vanilla kernel as this is a sandbox system that I like tinkering with. Thanks for all the responses !! I'll try disabling the option and re-compiling! Greg * 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
Re: BUG: Soft Lockup detected on CPU#
On Tue, 2006-10-10 at 12:14 +0200, Carsten Otte wrote: > > The way how the soft-lockup detection works right now is broken for > > system that utilize virtual cpus. You could argue that all zSeries > > systems use virtualized cpu so the feature does not make sense. > With dedicated PUs on a logical partition, and when running on raw > iron the feature should work fine afaict. No? Yes, in that special case it should work. But who is using dedicated PUs on LPAR? 1% of the installed linux systems? The best thing to do is to disable the config option, as it is harmful for the majority of the systems. Heiko already sent a patch. -- blue skies, Martin. Martin Schwidefsky Linux for zSeries Development & Services IBM Deutschland Entwicklung GmbH "Reality continues to ruin my life." - Calvin. -- 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
Re: BUG: Soft Lockup detected on CPU#
Martin wrote: The way how the soft-lockup detection works right now is broken for system that utilize virtual cpus. You could argue that all zSeries systems use virtualized cpu so the feature does not make sense. With dedicated PUs on a logical partition, and when running on raw iron the feature should work fine afaict. No? cheers, Carsten -- Carsten Otte has stopped smoking: Ich habe in 4 Monate, 2 Wochen und 1 Tag schon 665,94 Euro gespart anstatt 2.774,76 Zigaretten zu kaufen. -- 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
Re: BUG: Soft Lockup detected on CPU#
On Mon, 2006-10-09 at 15:06 -0400, Post, Mark K wrote: > Is the plan to make this work in the future? If not, it should not be a > config option that can be set. The way how the soft-lockup detection works right now is broken for system that utilize virtual cpus. You could argue that all zSeries systems use virtualized cpu so the feature does not make sense. -- blue skies, Martin. Martin Schwidefsky Linux for zSeries Development & Services IBM Deutschland Entwicklung GmbH "Reality continues to ruin my life." - Calvin. -- 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
Re: BUG: Soft Lockup detected on CPU#
Is the plan to make this work in the future? If not, it should not be a config option that can be set. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Heiko Carstens Sent: Saturday, October 07, 2006 6:18 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: BUG: Soft Lockup detected on CPU# On Fri, Oct 06, 2006 at 02:56:05PM -0400, Greg Keuken wrote: > 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! Disable CONFIG_DETECT_SOFTLOCKUP before compiling the kernel. Softlockup detection does not work on s390. You can safely ignore the warnings you got. Please note that 2.6.19-rc1 has a bug that causes your clock running way too slow. Updating to 2.6.19-rc1-git3 sounds like a good idea to me... -- 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
Re: BUG: Soft Lockup detected on CPU#
On Fri, Oct 06, 2006 at 02:56:05PM -0400, Greg Keuken wrote: > 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! Disable CONFIG_DETECT_SOFTLOCKUP before compiling the kernel. Softlockup detection does not work on s390. You can safely ignore the warnings you got. Please note that 2.6.19-rc1 has a bug that causes your clock running way too slow. Updating to 2.6.19-rc1-git3 sounds like a good idea to me... -- 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
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!
1ff8bae8 005957e8 003787c0 003787c0
00105122 0400 0056f500 00570300
00501d30 0001000b
1ff8baa8 003558c0 00105122 1ff8ba48
Call Trace:
([<00105064>] show_trace+0x5c/0xc0)
[<0010518e>] show_stack+0xc6/0xec
[<001051d8>] dump_stack+0x24/0x34
[<0015587e>] softlockup_tick+0x106/0x12c
[<00132e4e>] run_local_timers+0x26/0x34
[<00132ee2>] update_process_times+0x86/0xc8
[<001056dc>] account_ticks+0x1c0/0x220
[<001092ee>] do_extint+0xf2/0xf8
[<0010dad4>] ext_int_handler+0xa0/0xa4
[<00255eec>] kref_put+0x7c/0xc4
([<1f7b84c8>] 0x1f7b84c8)
[<0035098a>] klist_dec_and_del+0x26/0x34
[<003509ea>] klist_next+0x52/0xd8
[<00273be8>] next_device+0x1c/0x40
[<00273c6a>] bus_find_device+0x5e/0xa8
[<002916f8>] get_subchannel_by_schid+0x34/0x58
[<00291fbc>] reprobe_subchannel+0x74/0xfc
[<00291452>] reprobe_all+0xde/0x160
[<0013c220>] run_workqueue+0x64/0x158
[<0013c43a>] worker_thread+0x126/0x16c
[<00141ec6>] kthread+0x11e/0x154
[<00105afe>] kernel_thread_starter+0x6/0xc
[<00105af8>] kernel_thread_starter+0x0/0xc
*
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
