Re: kswapd0, was Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)

To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Thorsten Glaser <tg@mirbsd.de>, debian-68k@lists.debian.org
Subject: Re: kswapd0, was Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
From: Finn Thain <fthain@telegraphics.com.au>
Date: Mon, 24 Feb 2014 15:36:26 +1100 (EST)
Message-id: <[🔎] alpine.LNX.2.00.1402241534310.20191@nippy.intranet>
In-reply-to: <[🔎] 87bnxy3qju.fsf@igel.home>
References: <20140219133449.A97055F@ara5.mirbsd.org> <[🔎] Pine.BSM.4.64L.1402191402340.28940@herc.mirbsd.org> <[🔎] alpine.LNX.2.00.1402231632520.32381@nippy.intranet> <[🔎] Pine.BSM.4.64L.1402230950170.24343@herc.mirbsd.org> <[🔎] 87bnxy3qju.fsf@igel.home>

On Sun, 23 Feb 2014, Andreas Schwab wrote:

> There's a kernel bug that causes kswapd0 to steal all cpu time.

Does that bug affect other architectures? Has anyone run git bisect?

Finn

Reply to:

Follow-Ups:
- Re: kswapd0, was Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
  - From: Andreas Schwab <schwab@linux-m68k.org>

References:
- Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
  - From: Thorsten Glaser <tg@mirbsd.de>
- Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
  - From: Finn Thain <fthain@telegraphics.com.au>
- Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
  - From: Thorsten Glaser <tg@mirbsd.de>
- Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
  - From: Andreas Schwab <schwab@linux-m68k.org>

Prev by Date: Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
Next by Date: Re: kswapd0, was Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
Previous by thread: Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
Next by thread: Re: kswapd0, was Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
Index(es):
- Date
- Thread