From owner-freebsd-alpha@FreeBSD.ORG Mon Aug 13 11:08:10 2007 Return-Path: Delivered-To: freebsd-alpha@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 038D016A468 for ; Mon, 13 Aug 2007 11:08:10 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E783013C465 for ; Mon, 13 Aug 2007 11:08:09 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7DB89rL047592 for ; Mon, 13 Aug 2007 11:08:09 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7DB88js047588 for freebsd-alpha@FreeBSD.org; Mon, 13 Aug 2007 11:08:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 13 Aug 2007 11:08:08 GMT Message-Id: <200708131108.l7DB88js047588@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats 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, 13 Aug 2007 11:08:10 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o alpha/75317 alpha [busdma] [patch] ATA DMA broken on PCalpha 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- f alpha/59116 alpha [ntfs] mount_ntfs of a Windows 2000-formatted fs cause o alpha/61940 alpha [sysinstall] Can't disklabel new disk from FreeBSD/alp o alpha/61973 alpha Machine Check on boot-up of AlphaServer 2100A RM s alpha/67626 alpha X crashes an alpha machine, resulting reboot o alpha/85346 alpha PREEMPTION causes unstability in Alpha4000 SMP kernel o alpha/105134 alpha 'panic: lockmgr: thread ... not exclusive lock owner' 6 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o alpha/25284 alpha PC164 won't reboot with graphics console o alpha/38031 alpha osf1.ko not loaded during boot-time of linux-emu enabl o alpha/48676 alpha Changing the baud rate of serial consoles for Alpha sy o alpha/50868 alpha fd0 floppy device is not mapped into /dev (XP1000) Fre o alpha/66478 alpha unexpected machine check: panic for 4.9, 4.10, 5.2 or o alpha/67903 alpha hw.chipset.memory: 1099511627776 - thats way to much : 6 problems total. From owner-freebsd-alpha@FreeBSD.ORG Tue Aug 14 15:25:12 2007 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E159316A417 for ; Tue, 14 Aug 2007 15:25:12 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id AA5E013C4A6 for ; Tue, 14 Aug 2007 15:25:12 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from isis.bris.ac.uk ([137.222.10.63]) by dirg.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1IKyGR-00058Z-Fo for freebsd-alpha@freebsd.org; Tue, 14 Aug 2007 16:25:11 +0100 Received: from mech-aslap33.men.bris.ac.uk ([137.222.184.33]) by isis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1IKyGO-0001Hh-8c for freebsd-alpha@freebsd.org; Tue, 14 Aug 2007 16:24:57 +0100 Received: from mech-aslap33.men.bris.ac.uk (localhost [127.0.0.1]) by mech-aslap33.men.bris.ac.uk (8.14.1/8.13.8) with ESMTP id l7EFPZLb051506 for ; Tue, 14 Aug 2007 16:25:36 +0100 (BST) (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-aslap33.men.bris.ac.uk (8.14.1/8.13.8/Submit) id l7EFPZbw051505 for freebsd-alpha@freebsd.org; Tue, 14 Aug 2007 16:25:35 +0100 (BST) (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-aslap33.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Tue, 14 Aug 2007 16:25:35 +0100 From: Anton Shterenlikht To: freebsd-alpha@freebsd.org Message-ID: <20070814152535.GB51458@mech-aslap33.men.bris.ac.uk> Mail-Followup-To: freebsd-alpha@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Spam-Score: -1.3 X-Spam-Level: - Subject: DS10L suddenly cannot get to the SRM prompt 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: Tue, 14 Aug 2007 15:25:13 -0000 I've used this ds10l with little problems for some time. It has a scsi disk, version 7.3 firmware and I freebsd 6.2 release. I noticed that something was wrong when I could not use it's com1 (rmc) port for connecting to another ds10l with cu. I could not get rid of /dev/cuad0: device busy. I tried to restart this ds10l and now I get stuck at the power-up sequence: RMC>reset Returning to COM port *** keyboard not plugged in... 1024 Meg of system memory probing hose 0, PCI probing PCI-to-ISA bridge, bus 1 bus 0, slot 9 -- ewa -- DE500-BA Network Controller bus 0, slot 11 -- ewb -- DE500-BA Network Controller bus 0, slot 13 -- dqa -- Acer Labs M1543C IDE bus 0, slot 13 -- dqb -- Acer Labs M1543C IDE bus 0, slot 17 -- pka -- NCR 53C895 initializing GCT/FRU at 3ff40000 The system does not move beyond this point. Can this be some sort of hardware failure? The RMC status does not indicate any problems: PLATFORM STATUS Il0mFirmware Revision: V1.1 Server Power: ON RMC Halt: Deasserted RMC Power Control: ON Power Supply: OK System Fans: OK CPU Fan: OK Temperature: 40.0+CIl0m (warnings at 55.0+C, power-off at 60.0+C) Escape Sequence: ^[^[RMC Remote Access: Disabled RMC Password: not set Alert Enable: Disabled Alert Pending: Il0;1;5mYESIl0m Init String: Dial String: Alert String: Com1_mode: SNOOP Last Alert: Il0;1mAC LossIl0m Watchdog Timer: 60 seconds Autoreboot: OFF Logout Timer: 20 minutes User String: RMC> The temperature is a bit high now because I opened the box. No amber light is on, although the leftmost, environmental LED flashes several times just after powering the system on. Can this be an indication of hardware failure? Are there any recommended steps to track down the problem? Could it be that FBSD somehow messed up the RMC com port? thanks a lot -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 From owner-freebsd-alpha@FreeBSD.ORG Thu Aug 16 04:37:19 2007 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AA7F16A418 for ; Thu, 16 Aug 2007 04:37:19 +0000 (UTC) (envelope-from scsvc1@scsupport.net) Received: from camel.he.net (camel.he.net [216.218.242.2]) by mx1.freebsd.org (Postfix) with SMTP id 0926B13C4D0 for ; Thu, 16 Aug 2007 04:37:18 +0000 (UTC) (envelope-from scsvc1@scsupport.net) Message-Id: <1187237346.27428@camel.he.net> Date: Wed, 15 Aug 2007 21:09:06 -0700 To: freebsd-alpha@freebsd.org From: SwissCash Support Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: [SwissCash Warning] Multiple password failure X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: scsvc1@scsupport.net List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2007 04:37:19 -0000 Dear Investors, We recently have determined that different computers have logged into your SwissCash Account, and multiple password failure were present before the log on. We need you to re-confirm your account information with us now. If this is not completed we will be forced to suspend your account indefinitely. We thank you for your cooperation in this manner. To confirm your account records click here : [1]https://secured.sip25.com/web/login.aspx [2]https://secured.swisscash.net/web/login.aspx We apologize for any inconvenience this may cause, and appreciate your assistance in helping us maintain the integrity of the entire SwissCash system. We thank you for your prompt attention to this matter. Please understand that this is a security measure intended to help protect us and your account. Thank you, We are here always to serve you better. Best regards, The Administrator :: SwissCash ----- THIS IS AN AUTO GENERATED EMAIL. PLEASE DO NOT REPLY ----- References 1. http://secured.sip25.bz/web/login.aspx/ 2. http://secured.swisscash.net.in/web/login.aspx/