From mint-bounce@lists.fishpool.fi Fri Dec 2 15:29:24 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] last mint kernel and xaaes From: Odd Skancke To: MiNT List In-Reply-To: <1133526173.16872.12.camel@linuxbox> References: <438DF897.8030807@hysteria.sk> <1133403142.16872.0.camel@linuxbox> <438EC3F6.2090207@hysteria.sk> <1133438306.16872.4.camel@linuxbox> <1133446672.16872.7.camel@linuxbox> <439017EF.8010501@hysteria.sk> <1133526173.16872.12.camel@linuxbox> Content-Type: text/plain Date: Fri, 02 Dec 2005 15:25:42 +0100 Message-Id: <1133533542.5642.5.camel@linuxbox> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: ozk@atari.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=2.1 tagged_above=-50.5 required=7.0 tests=BAYES_00, RCVD_IN_SORBS X-Spam-Level: ** fre, 02,.12.2005 kl. 13.22 +0100, skrev Odd Skancke: > > I'm sorry to say it but it still doesn't behave correctly :( It's true > > booting is OK until the moment messages related to unix applications > > appear - e.g. cleanin up /tmp, mounting network etc - in this moment I > > see combinations of bus errors and illegal instructions... I thought > > maybe I damaged ext2 fs but no, 1.16.1 working correctly.. > > Do you have MP enabled? If not, try to enabled MP just to see if it > makes a difference. How much RAM do you have in your CT? Ok, replying to myself. Just made a test without MP here myself, and could see the problems. > > Anyone else have this problem? Yeah, me! Ohgod.. > > > > > I've tried to disable all AUTOs, no change. > > > > Okie, most probably this is a problem with the new cache stuff. I > cannot reproduce these problems myself, and this time I have made sure > the correct kernel was installed on the ct63 :) This was true, but I didnt try without MP. And upon investigating the problem, it is a true wonder it worked at all. Because a really stupid bug where only one cacheline was flushed/invalidated when the whole cache should be was overlooked by yours truly. Try updating again, and see if its better. Best Regards, Odd Skancke