From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Schwab Subject: Re: [PATCH 0/4] Atari kernel-in-FastRAM patches, take three Date: Tue, 01 Apr 2014 11:06:32 +0200 Message-ID: References: <1396137686-32678-1-git-send-email-schmitz@debian.org> <8761mvl3jb.fsf@igel.home> <87a9c63x1c.fsf@igel.home> <533A6D43.30403@biophys.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from cantor2.suse.de ([195.135.220.15]:37458 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751251AbaDAJGe (ORCPT ); Tue, 1 Apr 2014 05:06:34 -0400 In-Reply-To: <533A6D43.30403@biophys.uni-duesseldorf.de> (schmitz@biophys.uni-duesseldorf.de's message of "Tue, 01 Apr 2014 20:39:47 +1300") Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: schmitz Cc: Geert Uytterhoeven , Michael Schmitz , Linux/m68k , debian m68k schmitz writes: > What size FastRAM did precipitate that bug for you, Andreas? It's the combination of kernel size and FastRAM setting that matters. You can easily watch it by adding the bootmem_debug kernel parameter. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."