From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linuxppc-dev@ozlabs.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@elte.hu>,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 11629] New: quad G5 fails to shut down
Date: Wed, 24 Sep 2008 00:45:15 +0200 [thread overview]
Message-ID: <1222209915.18015.51.camel@johannes.berg> (raw)
In-Reply-To: <20080923143057.e3e54536.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
On Tue, 2008-09-23 at 14:30 -0700, Andrew Morton wrote:
> > http://johannes.sipsolutions.net/files/dsc_2274.jpg
> >
>
> That went splat in the clockevents code.
>
> I saw a pull request with several fixes float past this morning:
>
> From: Ingo Molnar <mingo@elte.hu>
> To: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>, "H. Peter Anvin" <hpa@zytor.com>, Andrew Morton <akpm@linux-foundation.org>
> Subject: [git pull] timer fixes
> Date: Tue, 23 Sep 2008 21:41:00 +0200
>
> Fingers crossed..
Well, that does seem to fix the regression. That is, it no longer
crashes. It still doesn't shut down, but that seems older and possibly
partially my fault as I wrote the CPU hotplug implementation (thought it
works fine for hibernate, never mind the fact that resuming from
hibernate hangs)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-09-23 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11629-10286@http.bugzilla.kernel.org/>
2008-09-23 21:30 ` [Bugme-new] [Bug 11629] New: quad G5 fails to shut down Andrew Morton
2008-09-23 21:50 ` Johannes Berg
2008-09-23 22:45 ` Johannes Berg [this message]
2008-09-23 23:10 ` Johannes Berg
2008-09-24 10:07 ` Johannes Berg
2008-09-25 8:56 ` Johannes Berg
2008-09-26 19:17 ` Joel Schopp
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=1222209915.18015.51.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).