From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: kernel-testers@vger.kernel.org
Subject: Re: [REGRESSION][BISECTED][X86] next-20080526 hangs on boot
Date: Tue, 27 May 2008 23:16:41 +0100 [thread overview]
Message-ID: <g1i1ls$pkl$1@ger.gmane.org> (raw)
In-Reply-To: aa79d98a0805262335lf5cd4e1p8f318d45dfe7ff92@mail.gmail.com
<posted & mailed>
Cyrill Gorcunov wrote:
> Hi Sitsofe, actually I can't imagine how this revert have helped you
> from hang. Newly introduced nmi_watchdog_default() didn't change
> the logic of the code being used before this merge-series.
I've just retested again and I'm fairly sure it's that commit. I can do the
following:
git checkout -f 4039cbaacf7874ab1effd0e9fb6c60bf9217f373
(compiled kernel hangs during boot)
git revert 1798bc22b2790bf2a956588e6b17c36ef79ceff7
git revert fd5cea02de100197a4c26d9e103508cf09b50a82
git revert 4b82b277707a39b97271439c475f186f63ec4692
(compiled kernel boots normally)
The last thing I normally see is
ACPI: Sleep Button (CM) [SLPB
during a normal boot is followed by
ACPI: device:03 is registered as cooling_device0
input: Video Bus
as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/input/input3
If you can give me a patch that reverts just
4b82b277707a39b97271439c475f186f63ec4692 again the current HEAD of
linux-next then I will try that too...
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2008-05-27 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 14:04 [REGRESSION][BISECTED][X86] next-20080526 hangs on boot Sitsofe Wheeler
2008-05-26 14:41 ` Cyrill Gorcunov
2008-05-26 16:16 ` Cyrill Gorcunov
2008-05-26 19:11 ` Sitsofe Wheeler
2008-05-26 19:36 ` Sitsofe Wheeler
2008-05-26 19:44 ` Cyrill Gorcunov
2008-05-27 6:35 ` Cyrill Gorcunov
2008-05-27 22:16 ` Sitsofe Wheeler [this message]
2008-05-27 22:50 ` Adrian Bunk
2008-05-28 3:21 ` Cyrill Gorcunov
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='g1i1ls$pkl$1@ger.gmane.org' \
--to=sitsofe@yahoo.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@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