public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: mingo@elte.hu, rjw@sisk.pl, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, bunk@kernel.org, gregkh@suse.de
Subject: Re: 2.6.25-rc3-git3: Reported regressions from 2.6.24
Date: Thu, 6 Mar 2008 12:11:27 -0800	[thread overview]
Message-ID: <20080306121127.42ac0682.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0803062054110.8669@axis700.grange>

On Thu, 6 Mar 2008 20:55:25 +0100 (CET)
Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:

> On Thu, 6 Mar 2008, Ingo Molnar wrote:
> 
> > 
> > * Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10123
> > > Subject		: No power-off / reboot with 2.6.25-rcX (up to -rc3) kernels
> > > Submitter	: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> > > Date		: 2008-02-27 08:15
> > 
> > Guennadi bisected this down to:
> > 
> >   commit fd7d1ced29e5beb88c9068801da7a362606d8273
> >   PCI: make pci_bus a struct device
> > 
> > and it's suspected that Andrew's poweroff problems might be related as 
> > well. Guennadi, Andrew, find below a manual revert of this change - does 
> > it make any difference?
> 
> Yes, this patch fixes both startup warnings and lets the system reboot and 
> power off again!

Ingo's revert doesn't fix my machine-wont-power-off regression.


Reminder: what _does_ fix it is:

a) CONFIG_DETECT_SOFTLOCKUP=n or

b) This:

--- a/kernel/softlockup.c~softlockup-workaround
+++ a/kernel/softlockup.c
@@ -289,6 +289,7 @@ cpu_callback(struct notifier_block *nfb,
 	case CPU_DEAD_FROZEN:
 		p = per_cpu(watchdog_task, hotcpu);
 		per_cpu(watchdog_task, hotcpu) = NULL;
+		msleep(1);
 		kthread_stop(p);
 		break;
 #endif /* CONFIG_HOTPLUG_CPU */
_


this one is unrelated to Greg's patch, I think.  It's a timing thing.

  reply	other threads:[~2008-03-06 20:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03  2:16 2.6.25-rc3-git3: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-03-03  7:53 ` Ingo Molnar
2008-03-03 11:41   ` Rafael J. Wysocki
2008-03-04  7:36 ` Pekka Enberg
2008-03-04 11:17 ` Pavel Machek
2008-03-04 13:59   ` Ingo Molnar
2008-03-04 23:00     ` Rafael J. Wysocki
2008-03-04 11:27 ` Dhaval Giani
2008-03-05  2:06   ` Zhang, Yanmin
2008-03-05  3:49     ` Balbir Singh
2008-03-05  5:15       ` Zhang, Yanmin
2008-03-05  6:36         ` Balbir Singh
2008-03-05  6:56         ` Ingo Molnar
2008-03-05  7:13           ` Zhang, Yanmin
2008-03-05  6:26     ` Zhang, Yanmin
2008-03-06  7:27 ` Ingo Molnar
2008-03-06 19:55   ` Guennadi Liakhovetski
2008-03-06 20:11     ` Andrew Morton [this message]
2008-03-06 20:51       ` Andrew Morton
2008-03-06 20:59         ` Ingo Molnar
2008-03-06 21:36           ` Andrew Morton
2008-03-06 22:57             ` Andrew Morton
2008-03-06 23:13               ` Suresh Siddha
2008-03-06 23:24                 ` Andrew Morton
2008-03-06 20:51     ` Greg KH
2008-03-06 17:57 ` Tilman Schmidt
2008-03-06 20:25   ` Rafael J. Wysocki

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=20080306121127.42ac0682.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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