Date: Sat, 17 Jan 2004 10:52:39 -0800
From: Andrew Morton <akpm@osdl.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: tmolina@cablespeed.com, linux-kernel@vger.kernel.org,
       rusty@rustcorp.com.au
Subject: Re: 2.6.1-mm4
Message-Id: <20040117105239.0b94f2b3.akpm@osdl.org>
In-Reply-To: <Pine.LNX.4.44.0401171805120.10403-100000@localhost.localdomain>
References: <Pine.LNX.4.58.0401170708280.14572@localhost.localdomain>
	<Pine.LNX.4.44.0401171805120.10403-100000@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1064
Lines: 21

Hugh Dickins <hugh@veritas.com> wrote:
>
>  > Code: 0a 3c c0 89 10 83 0d 20 0a 3c c0 20 a3 00 0a 3c c0 b8 00 e0 ff ff 21 
>  > e0 f7 40 14 00 ff ff 00 75 15 8b 15 40 0b 3c c0 85 d2 74 0b <8b> 02 85 c0 
>  > 75 0a 90 8d 74 26 00 53 9d 5b 5d c3 89 d0 e8 b4 1a
>  > <6>note: S01reboot[2352] exited with preempt_count 1
> 
>  I was getting something like that on reboot a few days ago, I think it
>  was with 2.6.1-mm2.  I had to move on before debugging it fully, but
>  the impression I got (maybe vile calumny, sue me Rusty) was that the
>  new kthread_create for 2.6.1-mm's ksoftirqd was leaving it vulnerable
>  to shutdown kill, whereas other things (RCU in my traces) still needed
>  it around and assumed its task address still valid.

Yes.  ksoftirqd and the migration threads can now be killed off
with `kill -9'.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/