From owner-freebsd-alpha@FreeBSD.ORG Sun Feb 22 15:27:03 2004 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCCC016A4CE for ; Sun, 22 Feb 2004 15:27:03 -0800 (PST) Received: from tea.blinkenlights.nl (tea.blinkenlights.nl [62.58.162.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9461143D1F for ; Sun, 22 Feb 2004 15:27:03 -0800 (PST) (envelope-from sten@blinkenlights.nl) Received: by tea.blinkenlights.nl (Postfix, from userid 101) id 036D81BA; Mon, 23 Feb 2004 00:22:22 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by tea.blinkenlights.nl (Postfix) with ESMTP id DEBFF1B0; Mon, 23 Feb 2004 00:22:22 +0100 (CET) Date: Mon, 23 Feb 2004 00:22:22 +0100 (CET) From: Sten Spans To: ticso@cicely.de In-Reply-To: Message-ID: References: <20040209210453.GZ44313@cicely12.cicely.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Christian Weisgerber cc: freebsd-alpha@freebsd.org Subject: Re: -current: SCHED_ULE? X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2004 23:27:04 -0000 On Sun, 22 Feb 2004, Sten Spans wrote: > On Mon, 9 Feb 2004, Bernd Walter wrote: > > > On Mon, Feb 09, 2004 at 08:09:38PM +0000, Christian Weisgerber wrote: > > > Is SCHED_ULE known to be generally broken on alpha or did I just > > > run into a temporary problem? > > > > I'm running 25th Jan source with SCHED_ULE without any real problem. > > I just rebuild my kernel with source from today and if I enable > ULE my ds10 wont boot. > > With a GENERIC kernel I got this: > > FreeBSD/alpha SRM disk boot, Revision 1.2 > (root@deepthought.blinkenlights.nl, Tue Feb 3 01:42:01 CET 2004) > Memory: 524288 k > Loading /boot/defaults/loader.conf > /boot/kernel/kernel data=0x510f00+0x4be90 syms=[0x8+0x69a98+0x8+0x5330e] > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > Entering /boot/kernel/kernel at 0xfffffc0000344c90... > > halted CPU 0 > > halt code = 2 > kernel stack not valid halt > PC = fffffc000057e5d0 > boot failure > > > my own customized kernel just hung after the entering message. > I do use the CPUTYPE=ev6, but that's all really. > mmm this seems to be something else in current, I'll try grabbing older source to figure it out. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem