From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 75331] "soft lockup CPU#0 stuck for 23s" regression on 32bit 3.13.0+ kernels.
Date: Sat, 03 May 2014 20:13:20 +0000 [thread overview]
Message-ID: <bug-75331-28872-BBDAPvhOQZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-75331-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=75331
--- Comment #1 from Ivan Kalvachev <iive@yahoo.com> ---
I tried to isolate the difference in .o object files when compiling the kernel
with and without the above commit. Unfortunately there were no differences
(only in version, boot and init code).
Upon further testing the kernel with the reverted commit does seem to
experience the same lockup, it just took it more time.
The above commit is not the culprit. I'll try to redo the bisect.
Sorry for the noise.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-05-03 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 22:35 [Bug 75331] New: "soft lockup CPU#0 stuck for 23s" regression on 32bit 3.13.0+ kernels bugzilla-daemon
2014-05-02 22:36 ` [Bug 75331] " bugzilla-daemon
2014-05-03 20:13 ` bugzilla-daemon [this message]
2023-01-27 13:07 ` bugzilla-daemon
2023-02-08 15:42 ` bugzilla-daemon
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=bug-75331-28872-BBDAPvhOQZ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/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