From owner-freebsd-alpha@FreeBSD.ORG Mon Oct 31 11:02:27 2005 Return-Path: X-Original-To: freebsd-alpha@freebsd.org 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 297AC16A421 for ; Mon, 31 Oct 2005 11:02:27 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADE0343D62 for ; Mon, 31 Oct 2005 11:02:11 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j9VB2BOa008751 for ; Mon, 31 Oct 2005 11:02:11 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j9VB2Ac2008745 for freebsd-alpha@freebsd.org; Mon, 31 Oct 2005 11:02:10 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 31 Oct 2005 11:02:10 GMT Message-Id: <200510311102.j9VB2Ac2008745@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-alpha@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 11:02:27 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/12/20] alpha/75317 alpha ATA DMA broken on PCalpha 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/02/05] alpha/47952 alpha DEFPA causes machine check with V5.0-rele o [2003/11/10] alpha/59116 alpha [ntfs] mount_ntfs of a Windows 2000-forma o [2004/01/26] alpha/61940 alpha Can't disklabel new disk from FreeBSD/alp o [2004/01/27] alpha/61973 alpha Machine Check on boot-up of AlphaServer 2 s [2004/06/06] alpha/67626 alpha X crashes an alpha machine, resulting reb o [2005/08/27] alpha/85346 alpha PREEMPTION causes unstability in Alpha400 6 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/02/22] alpha/25284 alpha PC164 won't reboot with graphics console o [2002/05/13] alpha/38031 alpha osf1.ko not loaded during boot-time of li o [2003/02/25] alpha/48676 alpha Changing the baud rate of serial consoles o [2003/04/12] alpha/50868 alpha fd0 floppy device is not mapped into /dev o [2004/05/10] alpha/66478 alpha unexpected machine check: panic for 4.9, o [2004/06/13] alpha/67903 alpha hw.chipset.memory: 1099511627776 - thats 6 problems total. From owner-freebsd-alpha@FreeBSD.ORG Fri Nov 4 14:56:01 2005 Return-Path: X-Original-To: freebsd-alpha@freebsd.org 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 6D6B216A41F for ; Fri, 4 Nov 2005 14:56:01 +0000 (GMT) (envelope-from harrisb@rcisd.org) Received: from mail.rcisd.org (mail.rcisd.org [207.235.198.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 332B943D48 for ; Fri, 4 Nov 2005 14:56:00 +0000 (GMT) (envelope-from harrisb@rcisd.org) Received: from [10.0.4.131] (helo=[10.0.4.131]) by mail.rcisd.org with esmtp (Exim 4.42) id 1EY2z2-0004fw-5D for freebsd-alpha@freebsd.org; Fri, 04 Nov 2005 08:56:00 -0600 Mime-Version: 1.0 (Apple Message framework v623) Content-Transfer-Encoding: 7bit Message-Id: <3649559e2c4519666b973576dd67cc9c@rcisd.org> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-alpha@freebsd.org From: Bill Harris Date: Fri, 4 Nov 2005 08:56:01 -0600 X-Mailer: Apple Mail (2.623) Subject: AS4100/533 Machine checks still on 5.4-RELEASE X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 14:56:01 -0000 I replaced one, then the other CPU in this machine over the last 3 months. It works great for a few weeks, then dumps again. Now, it's every couple of days. I've cvsupped the kernel source from the release tree to make sure I had the latest patches just in case. I'm at a loss to what's causing this. I've got a similarly equipped AS4100 at home, that's running fine with the same code. This is a web and border mail server, but it's not very heavily loaded. I'm guessing that the perl script is my MRTG scripts that run every 5 mins or so. It crashed again last night.. unexpected machine check: mces = 0x1 vector = 0x670 param = 0xfffffc0000004838 pc = 0x1601fdd10 ra = 0x1601fda8c curproc = 0xfffffc00301cf490 pid = 29125, comm = perl5.8.6 panic: machine check cpuid = 0 Uptime: 10h40m39s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Since I've replaced both processors, what should I do next? Bill Bill Harris Director of Technology Royse City ISD (972)-635-5050 From owner-freebsd-alpha@FreeBSD.ORG Fri Nov 4 15:51:26 2005 Return-Path: X-Original-To: freebsd-alpha@freebsd.org 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 4F71716A41F for ; Fri, 4 Nov 2005 15:51:26 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9523D43D49 for ; Fri, 4 Nov 2005 15:51:25 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr11.xs4all.nl (8.13.3/8.13.3) with ESMTP id jA4FpE18020375; Fri, 4 Nov 2005 16:51:16 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id jA4FpEC4077005; Fri, 4 Nov 2005 16:51:14 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id jA4FpEWm077004; Fri, 4 Nov 2005 16:51:14 +0100 (CET) (envelope-from wb) Date: Fri, 4 Nov 2005 16:51:14 +0100 From: Wilko Bulte To: Bill Harris Message-ID: <20051104155113.GA76898@freebie.xs4all.nl> References: <3649559e2c4519666b973576dd67cc9c@rcisd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3649559e2c4519666b973576dd67cc9c@rcisd.org> X-OS: FreeBSD 6.0-RC1 User-Agent: Mutt/1.5.9i X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-alpha@freebsd.org Subject: Re: AS4100/533 Machine checks still on 5.4-RELEASE X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 15:51:26 -0000 On Fri, Nov 04, 2005 at 08:56:01AM -0600, Bill Harris wrote.. > I replaced one, then the other CPU in this machine over the last 3 > months. It works great for a few weeks, then dumps again. Now, it's > every couple of days. > > I've cvsupped the kernel source from the release tree to make sure > I had the latest patches just in case. I'm at a loss to what's causing > this. I've got a similarly equipped AS4100 at home, that's running > fine with the same code. This is a web and border mail server, but > it's not very heavily loaded. I'm guessing that the perl script is my > MRTG > scripts that run every 5 mins or so. > > It crashed again last night.. > > > unexpected machine check: > > mces = 0x1 > vector = 0x670 > param = 0xfffffc0000004838 > pc = 0x1601fdd10 > ra = 0x1601fda8c > curproc = 0xfffffc00301cf490 > pid = 29125, comm = perl5.8.6 > > panic: machine check > cpuid = 0 > Uptime: 10h40m39s > Cannot dump. No dump device defined. > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > > Since I've replaced both processors, what should I do next? A machinecheck 670 is a CPU detected error. The manuals say that typically the CPU that detected the error is broken ;-) But FreeBSD does not contain the smarts of Tru64 or VMS that allows further diagnosis than this. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-alpha@FreeBSD.ORG Fri Nov 4 16:19:04 2005 Return-Path: X-Original-To: freebsd-alpha@freebsd.org 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 981FB16A41F for ; Fri, 4 Nov 2005 16:19:04 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from ant.bwct.de (ant.bwct.de [85.159.14.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A23243D46 for ; Fri, 4 Nov 2005 16:18:55 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by ant.bwct.de (8.12.11/8.12.11) with ESMTP id jA4GIljl019117; Fri, 4 Nov 2005 17:18:51 +0100 (CET) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id jA4GIb2a004867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Nov 2005 17:18:38 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id jA4GIbFD003601; Fri, 4 Nov 2005 17:18:37 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id jA4GIUY5003600; Fri, 4 Nov 2005 17:18:30 +0100 (CET) (envelope-from ticso) Date: Fri, 4 Nov 2005 17:18:29 +0100 From: Bernd Walter To: Bill Harris Message-ID: <20051104161829.GA2997@cicely12.cicely.de> References: <3649559e2c4519666b973576dd67cc9c@rcisd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3649559e2c4519666b973576dd67cc9c@rcisd.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Report: * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on cicely12.cicely.de Cc: freebsd-alpha@freebsd.org Subject: Re: AS4100/533 Machine checks still on 5.4-RELEASE X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 16:19:04 -0000 On Fri, Nov 04, 2005 at 08:56:01AM -0600, Bill Harris wrote: > I replaced one, then the other CPU in this machine over the last 3 > months. It works great for a few weeks, then dumps again. Now, it's > every couple of days. > > I've cvsupped the kernel source from the release tree to make sure > I had the latest patches just in case. I'm at a loss to what's causing > this. I've got a similarly equipped AS4100 at home, that's running > fine with the same code. This is a web and border mail server, but > it's not very heavily loaded. I'm guessing that the perl script is my > MRTG > scripts that run every 5 mins or so. > > It crashed again last night.. > > > unexpected machine check: > > mces = 0x1 > vector = 0x670 > param = 0xfffffc0000004838 > pc = 0x1601fdd10 > ra = 0x1601fda8c > curproc = 0xfffffc00301cf490 > pid = 29125, comm = perl5.8.6 > > panic: machine check > cpuid = 0 > Uptime: 10h40m39s > Cannot dump. No dump device defined. > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > > Since I've replaced both processors, what should I do next? Can you mail the complete boot messages including SRM output? -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-alpha@FreeBSD.ORG Sat Nov 5 23:49:14 2005 Return-Path: X-Original-To: freebsd-alpha@freebsd.org 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 C330816A41F for ; Sat, 5 Nov 2005 23:49:14 +0000 (GMT) (envelope-from ansarm@sympatico.ca) Received: from BAYC1-PASMTP01.bayc1.hotmail.com (bayc1-pasmtp01.bayc1.hotmail.com [65.54.191.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id D90C743D45 for ; Sat, 5 Nov 2005 23:49:13 +0000 (GMT) (envelope-from ansarm@sympatico.ca) Message-ID: X-Originating-IP: [70.50.107.199] X-Originating-Email: [ansarm@sympatico.ca] Received: from ansarmm2 ([70.50.107.199]) by BAYC1-PASMTP01.bayc1.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Sat, 5 Nov 2005 15:49:13 -0800 From: "Ansar Mohammed" To: Date: Sat, 5 Nov 2005 18:49:20 -0500 Message-ID: <004b01c5e263$8d4b9e30$0c02a8c0@northamerica.corp.microsoft.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcXiY4qvGlKtfTv6RD6ltUzN1knfHA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-OriginalArrivalTime: 05 Nov 2005 23:49:13.0410 (UTC) FILETIME=[86617220:01C5E263] Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: SRM compatibility X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 23:49:14 -0000 Is there a recommended SRM version to use for FreeBSD Alpha? I have attempted an install on a 6.x SRM BIOS that is failing on kernel load of isp0 on a PWS 433au. The same system loads NetBSD fine. There is another guy in hawai who apparently has the same issues. I unplugged the controller and tried to reinstall on the IDE disks but got some extremely weird problems such as the sysinstall failing to detect some ide disks. In short, rather than solve my current issues, I would like to know if these issues can be mitigated by an SRM upgrade. Thanks.