From: Andrew Morton <akpm@linux-foundation.org>
To: g.liakhovetski@gmx.de, 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:51:53 -0800 [thread overview]
Message-ID: <20080306125153.d95db2b9.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080306121127.42ac0682.akpm@linux-foundation.org>
On Thu, 6 Mar 2008 12:11:27 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:
> 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 */
sysrq-t works: http://userweb.kernel.org/~akpm/x.txt
It shows that `halt' is stuck in kthread_stop(), waiting for `watchdog' to
go away. But all the watchdog tasks are dreamily asleep, as if the wakeup
didn't work.
I'd love to poke around in kgdb (what does kthread_stop_info.k point at?)
but it seems that -mm's copy of kgdb got taken away when I wasn't looking.
Can I have it back please?
(btw, it isn't compulsory that every cpu callback function be literally
called "cpu_callback").
next prev parent reply other threads:[~2008-03-06 20:53 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
2008-03-06 20:51 ` Andrew Morton [this message]
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=20080306125153.d95db2b9.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