public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: Dinakar Guniguntala <dino@in.ibm.com>
Cc: Paul Jackson <pj@sgi.com>,
	Simon.Derr@bull.net, lse-tech@lists.sourceforge.net,
	Andrew Morton <akpm@osdl.org>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	V Srivatsa <vatsa@in.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpusets+hotplug+preepmt broken
Date: Wed, 11 May 2005 14:51:56 -0500	[thread overview]
Message-ID: <20050511195156.GE3614@otto> (raw)
In-Reply-To: <20050511191654.GA3916@in.ibm.com>

On Thu, May 12, 2005 at 12:46:54AM +0530, Dinakar Guniguntala wrote:
> 
> cpusets+hotplug+preempt hangs up the machine, if both
> cpuset and hotplug operations are going on simultaneously
> 
> I also get this oops first
> 
> scheduling while atomic: cpuoff.sh/0x00000001/25331
>  [<c040195d>] schedule+0xa4d/0xa60
>  [<c0401b25>] wait_for_completion+0xc5/0xf0
>  [<c011a200>] default_wake_function+0x0/0x20
>  [<c0400cd3>] __down+0x83/0x110
>  [<c011a200>] default_wake_function+0x0/0x20
>  [<c0400eab>] __down_failed+0x7/0xc
>  [<c0141fe7>] .text.lock.cpuset+0x105/0x15e
>  [<c011b860>] move_task_off_dead_cpu+0x130/0x1f0
>  [<c011ba7c>] migrate_live_tasks+0x8c/0x90
>  [<c011be25>] migration_call+0x75/0x2c0
>  [<c01423f2>] __stop_machine_run+0x92/0xb0
>  [<c012e0dd>] notifier_call_chain+0x2d/0x50
>  [<c013a6fb>] cpu_down+0x16b/0x2a0
>  [<c027ddfb>] store_online+0x5b/0x80
>  [<c027ae15>] sysdev_store+0x35/0x40
>  [<c019f43e>] flush_write_buffer+0x3e/0x50
>  [<c019f4a8>] sysfs_write_file+0x58/0x80
>  [<c0163d26>] vfs_write+0xc6/0x180
>  [<c0163eb1>] sys_write+0x51/0x80
>  [<c01034e5>] syscall_call+0x7/0xb

This trace is what should be fixed -- we're trying to schedule while
the machine is "stopped" (all cpus except for one spinning with
interrupts off).  I'm not too familiar with the cpusets code but I
would like to stay away from nesting these semaphores if at all
possible.

Will you share your testcase please?


Nathan

  parent reply	other threads:[~2005-05-11 19:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 19:16 [PATCH] cpusets+hotplug+preepmt broken Dinakar Guniguntala
2005-05-11 19:25 ` [Lse-tech] " Paul Jackson
2005-05-11 19:55   ` Paul Jackson
2005-05-11 20:26     ` Nathan Lynch
2005-05-11 20:45       ` Paul Jackson
2005-05-11 19:51 ` Nathan Lynch [this message]
2005-05-11 20:42   ` Paul Jackson
2005-05-11 20:58     ` Paul Jackson
2005-05-14  2:23       ` Paul Jackson
2005-05-14 12:14         ` Nathan Lynch
2005-05-14 17:04           ` Paul Jackson
2005-05-14 17:44             ` Paul Jackson
2005-05-18  4:14               ` Paul Jackson
2005-05-18  9:29               ` [Lse-tech] " Dinakar Guniguntala
2005-05-18 14:48               ` Nathan Lynch
2005-05-18 21:16               ` Paul Jackson
2005-05-14 16:28         ` Srivatsa Vaddagiri
2005-05-12 15:10     ` Dinakar Guniguntala
2005-05-13 12:15       ` [Lse-tech] " Dinakar Guniguntala
2005-05-13  0:34     ` Nathan Lynch
2005-05-13 12:32   ` [Lse-tech] " Dinakar Guniguntala
2005-05-13 17:25     ` Srivatsa Vaddagiri
2005-05-13 19:59       ` Paul Jackson
2005-05-13 20:20         ` Dipankar Sarma
2005-05-13 20:46           ` Nathan Lynch
2005-05-13 21:05             ` Paul Jackson
2005-05-13 21:06             ` Dipankar Sarma
2005-05-13 20:52           ` Paul Jackson
2005-05-13 21:02             ` Dipankar Sarma
2005-05-14  2:58               ` Paul Jackson
2005-05-14 16:09                 ` Srivatsa Vaddagiri
2005-05-14 17:50                   ` Paul Jackson
2005-05-14 17:57                   ` Paul Jackson
2005-05-14 16:30                 ` Nathan Lynch
2005-05-14 17:23                   ` Srivatsa Vaddagiri
2005-05-14 23:17                     ` Nathan Lynch
2005-05-13 19:59     ` Paul Jackson
2005-05-13 21:27     ` Nathan Lynch

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=20050511195156.GE3614@otto \
    --to=ntl@pobox.com \
    --cc=Simon.Derr@bull.net \
    --cc=akpm@osdl.org \
    --cc=dino@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=nickpiggin@yahoo.com.au \
    --cc=pj@sgi.com \
    --cc=vatsa@in.ibm.com \
    /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