From: Mike Galbraith <efault@gmx.de>
To: Simon Sudler <Simon.Sudler@iis.fraunhofer.de>
Cc: Darren Hart <dvhart@linux.intel.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: 3.0.4-rt14 "shutdown -h now" hangs on x86 32b
Date: Tue, 04 Oct 2011 11:28:09 +0200 [thread overview]
Message-ID: <1317720489.6260.9.camel@marge.simson.net> (raw)
In-Reply-To: <4E8ABB4B.6000204@iis.fraunhofer.de>
On Tue, 2011-10-04 at 09:52 +0200, Simon Sudler wrote:
> Hi Darren,
>
> i had the same problem on a Z530 with all RT kernels 3.0. I didn't
> search for the reason, however the problem went away when i used the
> "Intel Atom" at the "Processor family" option.
I see something similar at least on my Q6600 and E5620 boxen.
'poweroff' or shutting down from KDE doesn't always do so, sometimes
leaving boxen with a message saying it'll be halted immediately or such
on the screen, but requiring press/hold of power button to get box
really powered down. I just tried Q6600 again to get exact quote, but
of course the little bugger powered down properly.
> On 03.10.2011 20:15, Darren Hart wrote:
> > I have a couple of platforms (including the n450 dev board from kernel
> > summit) where an x86 32b build of 3.0.4-rt14 fails to shutdown with
> > "shutdown -h now". reboot works properly, and shutdown works with
> > maxcpus=1 (otherwise the n450 has 2 hardware threads).
> >
> > The last messages to hit the console are:
> >
> > e1000e 0000:04:00.0: PCI INT A disabled
> > ehci_hcd 0000:00:1d.7: PCI INT A disabled
> > ehci_hcd 0000:00:1a.7: PCI INT C disabled
> >
> > I am booting from a USB stick. If I install to a SATA connected SSD, the
> > shutdown still fails, but I don't see the "INT X disabled" messages.
> >
> > Has anyone run into this with a known workaround? Any thoughts on where
> > to start digging?
> >
> > .config attached.
>
next prev parent reply other threads:[~2011-10-04 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 18:15 3.0.4-rt14 "shutdown -h now" hangs on x86 32b Darren Hart
2011-10-04 7:52 ` Simon Sudler
2011-10-04 9:28 ` Mike Galbraith [this message]
2011-10-04 21:20 ` Thomas Gleixner
2011-10-04 22:09 ` Aaron Lindsay
2011-10-04 22:46 ` Darren Hart
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=1317720489.6260.9.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=Simon.Sudler@iis.fraunhofer.de \
--cc=dvhart@linux.intel.com \
--cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.