Re: [Bugme-new] [Bug 11629] New: quad G5 fails to shut down

2008-09-26 Thread Joel Schopp
From: Johannes Berg [EMAIL PROTECTED] Subject: powerpc: fix shutdown I tracked down the shutdown regression to CPUs not dying when being shut down during power-off. This turns out to be due to the system_state being SYSTEM_POWER_OFF, which this code doesn't take as a valid state for shutting

Re: [Bugme-new] [Bug 11629] New: quad G5 fails to shut down

2008-09-25 Thread Johannes Berg
I wrote: And here's the fix. Well, that should of course remove that comment there too. New version below. From: Johannes Berg [EMAIL PROTECTED] Subject: powerpc: fix shutdown I tracked down the shutdown regression to CPUs not dying when being shut down during power-off. This turns out to be

Re: [Bugme-new] [Bug 11629] New: quad G5 fails to shut down

2008-09-24 Thread Johannes Berg
On Tue, 2008-09-23 at 14:30 -0700, Andrew Morton wrote: Steps to reproduce: shut down the machine, see it fail. http://johannes.sipsolutions.net/files/dsc_2274.jpg That went splat in the clockevents code. This is still strange, it appears that when the CPUs fail to offline, we

Re: [Bugme-new] [Bug 11629] New: quad G5 fails to shut down

2008-09-23 Thread Andrew Morton
On Tue, 23 Sep 2008 14:20:55 -0700 (PDT) [EMAIL PROTECTED] wrote: http://bugzilla.kernel.org/show_bug.cgi?id=11629 Summary: quad G5 fails to shut down Product: Platform Specific/Hardware Version: 2.5 KernelVersion: 2.6.27-rc6+wireless bits

Re: [Bugme-new] [Bug 11629] New: quad G5 fails to shut down

2008-09-23 Thread Johannes Berg
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 [EMAIL PROTECTED] To: Linus Torvalds [EMAIL

Re: [Bugme-new] [Bug 11629] New: quad G5 fails to shut down

2008-09-23 Thread Johannes Berg
On Wed, 2008-09-24 at 00:45 +0200, Johannes Berg wrote: Well, that does seem to fix the regression. That is, it no longer crashes. Spoke too early, it seems that the crash isn't exactly reproducible all the time nor happens at the same spot all the time. I'd suspect that the timer code isn't