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: Finn Thain <fthain@telegraphics.com.au>, 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: Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>
Date: Wed, 26 Feb 2014 21:39:52 +1300
Message-id: <[🔎] 9e5c155b2acf9b262a93e5a0eb9224d0@biophys.uni-duesseldorf.de>
In-reply-to: <[🔎] mvmsir8df5m.fsf@hawking.suse.de>
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> <[🔎] alpine.LNX.2.00.1402241534310.20191@nippy.intranet> <[🔎] mvmsir8df5m.fsf@hawking.suse.de>

Andreas,

Finn Thain <fthain@telegraphics.com.au> writes:

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?


I think it has to do with the recently messed up interrupt architecture
on m68k.

Thanks, that gives me something to try and pinpoint the reason for thememory leak I've been seeing.


Cheers,

	Michael

Andreas.

--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 82764ED5
"And now for something completely different."


--
To UNSUBSCRIBE, email to debian-68k-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contactlistmaster@lists.debian.org
Archive: [🔎] mvmsir8df5m.fsf@hawking.suse.de">http://lists.debian.org/[🔎] mvmsir8df5m.fsf@hawking.suse.de

Reply to:

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>
- Re: kswapd0, was Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
  - From: Finn Thain <fthain@telegraphics.com.au>
- Re: kswapd0, was Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
  - From: Andreas Schwab <schwab@linux-m68k.org>

Prev by Date: elgar now runs 3.12-1-m68k and systemd
Next by Date: Re: How to get a new palo source package into unstable?
Previous by thread: Re: kswapd0, was Re: Log for attempted build of blender_2.69-3 on m68k (dist=unstable)
Next by thread: Re: Log for attempted build of glib2.0_2.38.2-5 on m68k (dist=unstable)
Index(es):
- Date
- Thread