From: Linda Walsh <lkml@tlinx.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: auto-reboot "broken" in 2.6.23.1 (from 2.6.22.12)
Date: Mon, 12 Nov 2007 15:36:14 -0800 [thread overview]
Message-ID: <4738E36E.4090706@tlinx.org> (raw)
Hello,
I upgraded the kernel on a multi-cpu Dell workstation (690) to
2.6.23.1. It had been running at 2.6.20. I moved to the new kernel via
"make oldconfig" -- choosing defaults. That didn't work.
To narrow things down I tried it under 2.6.21.1 (made
oldconfig from working 2.6.20/proc/config.gz). This worked.
Downloaded and made 2.6.22.12 (w/oldconfig from the
working 2.6.21.1 config).
Tried deriving a new config from the 2.6.22.12/proc/config.gz
that worked (using make oldconfig). This kernel won't reboot.
It goes through the entire shutdown process, and says it is
about to reboot the system. Then it just stops.
One of the new questions on ".23", was suspend-to-ram support.
That defaulted to 'yes' in oldconfig -- tried 'no' (thinking
maybe it was related), but that made no difference.
I assume something is unique to my configuration, but don't
know what would have changed in machine shutdown that would
have affected my system. I also tried compiling in APM
and telling it to use real-mode to try to power-off the machine
(thinking, maybe, that flag might also affect rebooting; made
no difference).
I can post the config if that helps, but didn't want to include
a bunch of superfluous info if it wasn't needed.
Thanks,
Linda
next reply other threads:[~2007-11-13 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 23:36 Linda Walsh [this message]
2007-11-13 2:26 ` reboot -df "broken" in 2.6.23.1 (from 2.6.22.12) Linda Walsh
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=4738E36E.4090706@tlinx.org \
--to=lkml@tlinx.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