From: "K.R. Foley" <kr@cybsft.com>
To: Luca Falavigna <dktrkranz@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Daniel Walker <dwalker@mvista.com>,
john cooper <john.cooper@timesys.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] Softlockup detected with linux-2.6.14-rt6
Date: Fri, 18 Nov 2005 12:33:57 -0600 [thread overview]
Message-ID: <437E1E95.2010809@cybsft.com> (raw)
In-Reply-To: <437DF0A8.6060409@gmail.com>
Luca Falavigna wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Luca Falavigna ha scritto:
> | Actually I am testing linux-2.6.14-rt13. If this problem come out again,
> | I will notify you ASAP.
>
> Unfortunately this soft lockup bug affects version 2.6.14-rt13 too :(
> Stack traces are almost the same, except base addresses.
>
> The bug was much harder to track down this time. Kernel detected a soft
> lockup bug after about three days of uptime.
>
> I noticed another strange behaviour. When I rebooted the machine
> (actually pushing reset button, not CTRL+ALT+CANC or SysRq at all), it
> became *very* slow. GRUB took up to five seconds to be fully loaded
> (usualy it takes only a fraction of second) and the initial phase of
> booting the kernel was about 4 times slower. Even after a power off this
> behaviour was still present! Need more coffee?
The slow booting sounds a lot like the RCU_TORTURE_TEST slowing things
down. You might try turning off RCU_TORTURE_TEST or setting it to be a
module.
>
> Regards,
> - --
> Luca
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iQEVAwUBQ33wppK+HIH6ZZ2zAQIYSQgAh7T0/a40F9ImNK4Ut7WvVxdLZn7Hekvn
> 8xBr2jSm5Vz4Ewiht1kZ+sXvAV98J8oDGBghQK8CVE+LdGnyFxncMH8sIlnOViq1
> PAwVXYOI7FQzk0UX0FTfsVcsmGkqZk653HC/VRTfY+7xg0NKzUFTjwZg0pDmhkoC
> yKg73Krr2Zx9N4JH5v2y9uFHhn3YC7mPmbO1mSsmF6WIcePLaY3+Um/FGkQZXr3b
> ZDwAd8IQmbgiJiyO7sAgc6ydPWxjDzrlPTri7pFHERkJJKxQAan+rKxYdGO7e9C4
> 57iny6wa2C2sdmn8quL+ZXnmpgB7vNRroDZ1kg5Qm/1SiKjbvC5BqQ==
> =RNUt
> -----END PGP SIGNATURE-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
kr
next prev parent reply other threads:[~2005-11-18 18:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 16:00 [BUG] Softlockup detected with linux-2.6.14-rt6 Luca Falavigna
2005-11-14 19:48 ` john cooper
2005-11-15 15:32 ` Ingo Molnar
2005-11-15 17:03 ` john cooper
2005-11-15 20:00 ` Ingo Molnar
2005-11-15 20:07 ` Daniel Walker
2005-11-16 0:16 ` Luca Falavigna
2005-11-18 15:18 ` Luca Falavigna
2005-11-18 18:33 ` K.R. Foley [this message]
2005-11-19 0:50 ` Luca Falavigna
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=437E1E95.2010809@cybsft.com \
--to=kr@cybsft.com \
--cc=dktrkranz@gmail.com \
--cc=dwalker@mvista.com \
--cc=john.cooper@timesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox