public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: g.liakhovetski@gmx.de, 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 13:36:32 -0800	[thread overview]
Message-ID: <20080306133632.34d77bbc.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080306205951.GA23989@elte.hu>

On Thu, 6 Mar 2008 21:59:51 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > 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?
> 
> it's in the full x86.git or you can pick up the kgdb-light tree:
> 
>   http://people.redhat.com/mingo/kgdb-light.git/README
> 

We'll see.

Meanwhile, further investigation show that cpu_callback() (the one in
kernel/softlockup.c) is waiting on this thread:

watchdog/1    R  running task        0     8      2 task_struct:ffff81025f1089e0
 ffff81025f10deb0 0000000000000046 0000000000000000 0000000000000246
 ffff81025f10de20 ffff81025f1089e0 ffff81025f1080c0 ffff81025f108d30
 000000015f10de50 00000000ffff2adf ffffffffffffffff ffffffffffffffff
Call Trace:
 [<ffffffff80263290>] ? watchdog+0x0/0x1dc
 [<ffffffff802632d6>] watchdog+0x46/0x1dc
 [<ffffffff80263290>] ? watchdog+0x0/0x1dc
 [<ffffffff8024704d>] kthread+0x44/0x6b
 [<ffffffff8020cd88>] child_rip+0xa/0x12
 [<ffffffff80247009>] ? kthread+0x0/0x6b
 [<ffffffff8020cd7e>] ? child_rip+0x0/0x12

kthread_stop_info.k=ffff81025f1089e0

(gdb) l *0xffffffff802632d6
0xffffffff802632d6 is in watchdog (kernel/softlockup.c:229).
224              */
225             while (!kthread_should_stop()) {
226                     touch_softlockup_watchdog();
227                     schedule();
228     
229                     if (kthread_should_stop())
230                             break;
231     
232                     if (this_cpu == check_cpu) {
233                             if (sysctl_hung_task_timeout_secs)

so this watchdog thread seems to be runnable, but not running.  What would
cause this?  

The only other runnable task is

events/2      R  running task        0    29      2 task_struct:ffff81025f2da300
 ffff81025f2e3ec0 0000000000000046 0000000000000286 ffff81000102ebc0
 ffff81000102ebe0 ffff81025f2da300 ffff81025f147380 ffff81025f2da650
 000000025f2e3e60 00000000ffff3310 ffff81000102ebc8 ffff81025f20e440
Call Trace:
 [<ffffffff802442ce>] ? worker_thread+0x0/0xe5
 [<ffffffff80244371>] worker_thread+0xa3/0xe5
 [<ffffffff80247364>] ? autoremove_wake_function+0x0/0x36
 [<ffffffff802442ce>] ? worker_thread+0x0/0xe5
 [<ffffffff8024704d>] kthread+0x44/0x6b
 [<ffffffff8020cd88>] child_rip+0xa/0x12
 [<ffffffff80247009>] ? kthread+0x0/0x6b
 [<ffffffff8020cd7e>] ? child_rip+0x0/0x12

which is on a different CPU.

  reply	other threads:[~2008-03-06 21:37 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
2008-03-06 20:59         ` Ingo Molnar
2008-03-06 21:36           ` Andrew Morton [this message]
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=20080306133632.34d77bbc.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