From owner-freebsd-alpha@FreeBSD.ORG Sun Dec 5 11:05:47 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 2959716A4CE for ; Sun, 5 Dec 2004 11:05:47 +0000 (GMT) Received: from quark.rcac.purdue.edu (quark.rcac.purdue.edu [128.210.189.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC2D543D5A for ; Sun, 5 Dec 2004 11:05:46 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from quark.rcac.purdue.edu (localhost [127.0.0.1]) iB5B5kHJ025117 for ; Sun, 5 Dec 2004 06:05:46 -0500 (EST) (envelope-from linimon@FreeBSD.org) Date: Sun, 5 Dec 2004 06:05:46 -0500 (EST) Message-Id: <200412051105.iB5B5kHJ025117@quark.rcac.purdue.edu> From: linimon@FreeBSD.org To: freebsd-alpha@FreeBSD.org Subject: FreeBSD ports that you maintain which are currently marked forbidden 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, 05 Dec 2004 11:05:47 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we are attempting to notify maintainers of ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of the port, including errors seen on the build farm, is included below. portname: www/netscape47-communicator forbidden because: multiple vulnerabilities with no hope of fixes build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=www&portname=netscape47-communicator portname: www/netscape47-navigator forbidden because: multiple vulnerabilities with no hope of fixes build errors: none. overview: http://portsmon.firepipe.net/portoverview.py?category=www&portname=netscape47-navigator If this problem is one that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Thanks for your efforts to help improve FreeBSD. From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 6 11:02:18 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 BF49016A4CE for ; Mon, 6 Dec 2004 11:02:18 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9296843D1F for ; Mon, 6 Dec 2004 11:02:18 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB6B2IfC027299 for ; Mon, 6 Dec 2004 11:02:18 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB6B2HkU027293 for freebsd-alpha@freebsd.org; Mon, 6 Dec 2004 11:02:17 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 6 Dec 2004 11:02:17 GMT Message-Id: <200412061102.iB6B2HkU027293@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 Subject: Current problem reports assigned to you 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: Mon, 06 Dec 2004 11:02:18 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/09/10] alpha/30486 alpha AlphaServer DS10 floppy access is broken o [2001/09/10] alpha/30487 alpha Floppy access on AlphaServer DS20 solid l 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 f [2004/06/06] alpha/67626 alpha X crashes an alpha machine, resulting reb 7 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/01/27] alpha/24663 alpha Console output gets scribbled into /var/l o [2001/02/22] alpha/25284 alpha PC164 won't reboot with graphics console o [2001/06/07] alpha/27930 alpha NE2000 not supported on FreeBSD Alpha 4.x o [2001/06/07] alpha/27933 alpha Time jitter under load on FreeBSD 4.3 alp f [2001/07/29] alpha/29299 alpha FreeBSD 4.3 Alpha + Tekram SCSI adapter p o [2001/10/01] alpha/30970 alpha Ensoniq 1371 (Creative chipset) does not o [2002/01/24] alpha/34232 alpha rpc.statd throws alignment errors o [2002/05/13] alpha/38031 alpha osf1.ko not loaded during boot-time of li p [2002/11/12] alpha/45240 alpha pstat -f column headings misaligned on Al 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 o [2004/09/23] alpha/72024 alpha LONG_MIN / 1 sends a "Floating exception" 14 problems total. From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 8 22:56:45 2004 Return-Path: Delivered-To: freebsd-alpha@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1D8B16A4CE; Wed, 8 Dec 2004 22:56:45 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A762543D4C; Wed, 8 Dec 2004 22:56:45 +0000 (GMT) (envelope-from peadar@FreeBSD.org) Received: from freefall.freebsd.org (peadar@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB8MujWw022864; Wed, 8 Dec 2004 22:56:45 GMT (envelope-from peadar@freefall.freebsd.org) Received: (from peadar@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB8MujEp022860; Wed, 8 Dec 2004 22:56:45 GMT (envelope-from peadar) Date: Wed, 8 Dec 2004 22:56:45 GMT From: Peter Edwards Message-Id: <200412082256.iB8MujEp022860@freefall.freebsd.org> To: ppelissi@caramail.com, peadar@FreeBSD.org, freebsd-alpha@FreeBSD.org Subject: Re: alpha/72024: LONG_MIN / 1 sends a "Floating exception" 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: Wed, 08 Dec 2004 22:56:45 -0000 Synopsis: LONG_MIN / 1 sends a "Floating exception" State-Changed-From-To: open->closed State-Changed-By: peadar State-Changed-When: Wed Dec 8 22:55:59 GMT 2004 State-Changed-Why: Fix committed to 6-current and 5-stable http://www.freebsd.org/cgi/query-pr.cgi?pr=72024 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 10 01:21:36 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 A99DF16A4CE for ; Fri, 10 Dec 2004 01:21:36 +0000 (GMT) Received: from building.weird.com (building.weird.com [204.92.254.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA13443D2F for ; Fri, 10 Dec 2004 01:21:35 +0000 (GMT) (envelope-from woods@building.weird.com) Received: from localhost (20896 bytes) by building.weird.com via sendmail with STDIO (sender: ) (ident using UNIX) id for ; (dest:remote)(R=bind_hosts)(T=inet_zone_bind_smtp) Thu, 9 Dec 2004 20:21:35 -0500 (EST) (Smail-3.2.0.121-Pre 2004-Aug-27 #1 built 2004-Nov-1) Message-Id: Date: Thu, 9 Dec 2004 20:21:35 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: ;j3Eth2XV8h1Yfu*uL{<:dQ$#E[DB0gemGZJ"J#4fH*][ lz; @-iwMv_u\6uIEKR0KY"=MzoQH#CrqBN`nG_5B@rrM8,f~Gr&h5a\= To: freebsd-alpha@freebsd.org X-Mailer: VM 7.19 under Emacs 21.3.1 Organization: Planix, Inc.; Toronto, Ontario; Canada Subject: FYI, no-go with booting FreeBSD-5.3 on AlphaServer ES40 X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Greg A. Woods" List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 01:21:36 -0000 I was just trying to take a chance on testing the bge(4) driver from FreeBSD and so tried booting the latest release on my client's ES40. Unfortunately even if it had not panic'ed I wouldn't have got the root filesystem mounted as the bge(4) driver doesn't even seem to be a default in the GENERIC kernel, which is pretty silly given that it the driver for one of the more common GigE cards supplied by DEC/Compaq/HP, e.g. the DEGXA-TX..... Looks like there are some problems with other drivers too, but of course I don't know how serious they are. Maybe this "boot -v" output will help someone get it further along. Note that NetBSD does boot and run quite well on the system so long as the ohci driver is omitted from the kernel and so long as none of the IDE devices are accessed (or their driver is also omitted). The only only problem is that both NetBSD's bge(4) and wm(4) drivers have rather poor GigE performance on this system (once their minor bugs are fixed), apparently because we have too much memory installed in it (and it's only at half capacity!). What good is an alpha if you can't put more than 4GB in it! ;-) Perhaps omitting ochi and atapci et al would help FreeBSD boot on the ES40 as well? For the very near term I can try netbooting other kernels for testing. Note I'm not subscribed to the list though. P00>>>boot ega0 -flags -v (boot ega0.0.0.6.1 -flags -v) Trying BOOTP boot. Broadcasting BOOTP Request... .Received BOOTP Packet File Name is: netboot local inet address: 10.30.30.2 remote inet address: 10.30.30.1 TFTP Read File Name: netboot netmask = 255.0.0.0 Server is on same subnet as client. .... bootstrap code read in base = 200000, image_start = 0, image_bytes = 386c0(231104) initializing HWRPB at 2000 initializing page table at 3fb54000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Console: SRM firmware console VMS PAL rev: 0x4006800010162 OSF PAL rev: 0x400690002015c Switch to OSF PAL code succeeded. FreeBSD/alpha SRM net boot, Revision 1.2 (root@ds10.wbnet, Fri Nov 5 04:07:46 UTC 2004) Memory: 16777216 k boot: ethernet address: 00:08:02:91:89:ae net_open: server addr: 10.30.30.1 net_open: server path: /usr/export/freebsd-5.3-alpha-bootonly Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0x5c4ce0+0x3d990 syms=[0x8+0x64ab8+0x8+0x53436] - Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Entering /boot/kernel/kernel at 0xfffffc0000344c30... Unrecognized boot flag '-'. Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE #0: Fri Nov 5 11:30:09 UTC 2004 root@ds10.wbnet:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xfffffc0000df6000. Preloaded mfs_root "/boot/mfsroot" at 0xfffffc0000df60d0. ST6600 AlphaServer ES40, 666MHz 8192 byte page size, 4 processors. CPU: EV67 (21264A) major=11 minor=14 extensions=0x307 OSF PAL rev: 0x400690002015c real memory = 17172619264 (16377 MB) Physical memory chunk(s): 0x00e18000 - 0x3fb51fff, 1054056448 bytes (128669 pages) 0x40000000 - 0x3f0f9ffff, -1325793280 bytes (-161840 pages) avail memory = 16832651264 (16052 MB) smp_start_secondary: starting cpu 1 smp_start_secondary: cpu 1 started smp_start_secondary: starting cpu 2 smp_start_secondary: cpu 2 started smp_start_secondary: starting cpu 3 smp_start_secondary: cpu 3 started FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs null: random: mem: pchip0: wsba[0].reg = 0x800000 wsm[0].reg = 0x700000 tba[0].reg = 0x0 wsba[1].reg = 0x80000001 wsm[1].reg = 0x3ff00000 tba[1].reg = 0x0 wsba[2].reg = 0xc0000001 wsm[2].reg = 0x3ff00000 tba[2].reg = 0x40000000 wsba[3].reg = 0x0 wsm[3].reg = 0x0 tba[3].reg = 0x0 pchip1: wsba[0].reg = 0x800000 wsm[0].reg = 0x700000 tba[0].reg = 0x0 wsba[1].reg = 0x80000001 wsm[1].reg = 0x3ff00000 tba[1].reg = 0x0 wsba[2].reg = 0xc0000001 wsm[2].reg = 0x3ff00000 tba[2].reg = 0x40000000 wsba[3].reg = 0x0 wsm[3].reg = 0x0 tba[3].reg = 0x0 tsunami0: <21271 Core Logic chipset> pcib0: <21271 PCI host bus adapter> on tsunami0 pci0: on pcib0 pci0: physical bus=0 map[10]: type 1, range 32, base 01000000, size 24, enabled map[14]: type 4, range 32, base 00001000, size 8, enabled map[18]: type 1, range 32, base 020c0000, size 12, enabled found-> vendor=0x1002, dev=0x4755, revid=0x9a bus=0, slot=1, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x0280, cachelnsz=16 (dwords) lattimer=0xff (7650 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) map[10]: type 4, range 32, base 00001100, size 8, enabled map[14]: type 1, range 64, base 020c1000, size 12, enabled found-> vendor=0x9005, dev=0x00c0, revid=0x01 bus=0, slot=2, func=0 class=01-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0xfc (7560 ns), mingnt=0x28 (10000 ns), maxlat=0x19 (6250 ns) intpin=a, irq=12 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 00001200, size 8, enabled map[14]: type 1, range 64, base 020c2000, size 12, enabled found-> vendor=0x9005, dev=0x00c0, revid=0x01 bus=0, slot=2, func=1 class=01-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0xfc (7560 ns), mingnt=0x28 (10000 ns), maxlat=0x19 (6250 ns) intpin=b, irq=13 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 00001300, size 8, enabled map[14]: type 1, range 32, base 020c3000, size 12, enabled found-> vendor=0x1077, dev=0x2312, revid=0x02 bus=0, slot=3, func=0 class=0c-04-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0xf8 (7440 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=a, irq=16 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 4, range 32, base 00001400, size 7, enabled map[14]: type 1, range 32, base 020c5000, size 7, enabled found-> vendor=0x1011, dev=0x0019, revid=0x30 bus=0, slot=4, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0280, cachelnsz=16 (dwords) lattimer=0xff (7650 ns), mingnt=0x14 (5000 ns), maxlat=0x28 (10000 ns) intpin=a, irq=20 found-> vendor=0x10b9, dev=0x1533, revid=0xc3 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x3200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 00001490, size 4, enabled found-> vendor=0x10b9, dev=0x5229, revid=0xc1 bus=0, slot=15, func=0 class=01-01-fa, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0xff (7650 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns) intpin=a, irq=238 map[10]: type 1, range 32, base 020c4000, size 12, enabled found-> vendor=0x10b9, dev=0x5237, revid=0x03 bus=0, slot=19, func=0 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0280, cachelnsz=8 (dwords) lattimer=0xf8 (7440 ns), mingnt=0x00 (0 ns), maxlat=0x50 (20000 ns) intpin=a, irq=234 pci0: at device 1.0 (no driver attached) ahc0: port 0x1100-0x11ff mem 0x20c1000-0x20c1fff irq 12 at device 2.0 on pci0 ahc0: Defaulting to MEMIO off ahc0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x1100 ahc0: Enabling 39Bit Addressing ahc0: Reading SEEPROM...done. ahc0: BIOS eeprom is present ahc0: Secondary High byte termination Enabled ahc0: Secondary Low byte termination Enabled ahc0: Primary Low Byte termination Enabled ahc0: Primary High Byte termination Enabled ahc0: Downloading Sequencer Program... 433 instructions downloaded ahc0: Features 0x1fef6, Bugs 0x40, Flags 0x29485560 ahc0: interrupting at TSUNAMI irq 12 ahc0: [GIANT-LOCKED] aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: port 0x1200-0x12ff mem 0x20c2000-0x20c2fff irq 13 at device 2.1 on pci0 ahc1: Defaulting to MEMIO off ahc1: Reserved 0x100 bytes for rid 0x10 type 4 at 0x1200 ahc1: Enabling 39Bit Addressing ahc1: Reading SEEPROM...done. ahc1: BIOS eeprom is present ahc1: Secondary High byte termination Enabled ahc1: Secondary Low byte termination Enabled ahc1: Primary Low Byte termination Enabled ahc1: Primary High Byte termination Enabled ahc1: Downloading Sequencer Program... 433 instructions downloaded ahc1: Features 0x1fef6, Bugs 0x40, Flags 0x29485560 ahc1: interrupting at TSUNAMI irq 13 ahc1: [GIANT-LOCKED] aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs Qlogic ISP Driver, FreeBSD Version 5.9, Core Version 2.8 isp0: port 0x1300-0x13ff mem 0x20c3000-0x20c3fff irq 16 at device 3.0 on pci0 isp0: Reserved 0x1000 bytes for rid 0x14 type 3 at 0x20c3000 isp0: using Memory space register mapping isp0: interrupting at TSUNAMI irq 16 isp0: [GIANT-LOCKED] isp0: Board Type 2312, Chip Revision 0x2, loaded F/W Revision 3.2.15 isp0: Installed in 64-Bit PCI slot isp0: 839 max I/O commands supported isp0: NVRAM Port WWN 0x210000e08b0ac8f8 isp0: bad execution throttle of 0- using 16 isp0: Mailbox Command 'INIT FIRMWARE' failed (COMMAND PARAMETER ERROR) device_attach: isp0 attach returned 6 dc0: port 0x1400-0x147f mem 0x20c5000-0x20c507f irq 20 at device 4.0 on pci0 dc0: Reserved 0x80 bytes for rid 0x10 type 4 at 0x1400 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: bpf attached dc0: Ethernet address: 08:00:2b:c4:b5:26 dc0: if_start running deferred for Giant dc0: interrupting at TSUNAMI irq 20 dc0: [GIANT-LOCKED] isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1490-0x149f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 238 at device 15.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x1490 ata0: channel #0 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=00 ostat0=ff ostat1=ff ata0: interrupting at ISA irq 14 ata0: [MPSAFE] ata1: channel #1 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: interrupting at ISA irq 15 ata1: [MPSAFE] ohci0: mem 0x20c4000-0x20c4fff irq 234 at device 19.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x20c4000 ohci0: interrupting at ISA irq 10 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered pcib1: <21271 PCI host bus adapter> on tsunami0 pci1: on pcib1 pci1: physical bus=0 map[10]: type 4, range 32, base 00010000, size 8, enabled map[14]: type 1, range 32, base 010f0000, size 12, enabled found-> vendor=0x1077, dev=0x2312, revid=0x02 bus=0, slot=2, func=0 class=0c-04-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0xf8 (7440 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=a, irq=28 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 1, range 32, base 01060000, size 17, enabled map[14]: type 1, range 32, base 01080000, size 17, enabled map[18]: type 4, range 32, base 00010280, size 5, enabled found-> vendor=0x8086, dev=0x1008, revid=0x02 bus=0, slot=3, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0xfc (7560 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns) intpin=a, irq=32 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 4, range 32, base 00010100, size 8, enabled map[14]: type 1, range 32, base 010f2000, size 8, enabled map[18]: type 1, range 32, base 010f1000, size 12, enabled found-> vendor=0x1000, dev=0x000c, revid=0x02 bus=0, slot=4, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0200, cachelnsz=16 (dwords) lattimer=0xff (7650 ns), mingnt=0x1e (7500 ns), maxlat=0x40 (16000 ns) intpin=a, irq=36 map[10]: type 4, range 32, base 00010200, size 7, enabled map[14]: type 1, range 32, base 010f2100, size 7, enabled found-> vendor=0x1011, dev=0x0019, revid=0x30 bus=0, slot=5, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0280, cachelnsz=16 (dwords) lattimer=0xff (7650 ns), mingnt=0x14 (5000 ns), maxlat=0x28 (10000 ns) intpin=a, irq=40 map[10]: type 1, range 64, base 010d0000, size 16, enabled found-> vendor=0x14e4, dev=0x16a7, revid=0x02 bus=0, slot=6, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0xf8 (7440 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=a, irq=44 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit isp1: port 0x10000-0x100ff mem 0x10f0000-0x10f0fff irq 28 at device 2.0 on pci1 isp1: Reserved 0x1000 bytes for rid 0x14 type 3 at 0x10f0000 isp1: using Memory space register mapping isp1: interrupting at TSUNAMI irq 28 isp1: [GIANT-LOCKED] isp1: Board Type 2312, Chip Revision 0x2, loaded F/W Revision 3.2.15 isp1: Installed in 64-Bit PCI slot isp1: 839 max I/O commands supported isp1: NVRAM Port WWN 0x210000e08b0a5ff8 isp1: bad execution throttle of 0- using 16 isp1: Mailbox Command 'INIT FIRMWARE' failed (HOST INTERFACE ERROR) device_attach: isp1 attach returned 6 pci1: at device 3.0 (no driver attached) sym0: <895> port 0x10100-0x101ff mem 0x10f1000-0x10f1fff,0x10f2000-0x10f20ff irq 36 at device 4.0 on pci1 sym0: Reserved 0x100 bytes for rid 0x14 type 3 at 0x10f2000 sym0: Reserved 0x1000 bytes for rid 0x18 type 3 at 0x10f1000 sym0: Delay (GEN=11): 246 msec, 36131 KHz sym0: Delay (GEN=11): 227 msec, 39155 KHz sym0: Delay (GEN=11): 227 msec, 39155 KHz sym0: chip clock is 39155KHz sym0: clock multiplier assumed sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 00/00/00/00/00/00 sym0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 07/4e/80/01/08/24 sym0: Delay (GEN=11): 247 msec, 35985 KHz sym0: Delay (GEN=11): 283 msec, 31407 KHz sym0: Delay (GEN=11): 282 msec, 31518 KHz CACHE TEST FAILED: DMA error (dstat=0xa0).sym0: CACHE INCORRECTLY CONFIGURED. device_attach: sym0 attach returned 6 dc1: port 0x10200-0x1027f mem 0x10f2100-0x10f217f irq 40 at device 5.0 on pci1 dc1: Reserved 0x80 bytes for rid 0x10 type 4 at 0x10200 miibus1: on dc1 dcphy1: on miibus1 dcphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc1: bpf attached dc1: Ethernet address: 08:00:2b:c4:7a:70 dc1: if_start running deferred for Giant dc1: interrupting at TSUNAMI irq 40 dc1: [GIANT-LOCKED] pci1: at device 6.0 (no driver attached) ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0: atkbd0, generic (0), config:0x0, flags:0x1f0000 atkbd0: interrupting at ISA irq 1 atkbd0: [GIANT-LOCKED] psm0: current command byte:0061 kbdc: TEST_AUX_PORT status:0001 psm0: strange result for test aux port (1). kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0001 psm: keyboard port failed. psm0: failed to reset the aux device. fdc0: ic_type 90 part_id 80 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: ic_type 90 part_id 80 fdc0: interrupting at ISA irq 6 fdc0: [MPSAFE] fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 mcclock0: at port 0x70-0x71 on isa0 Calibrating clock(s) ... PCC clock: 666640007 Hz (firmware 666666666 Hz) i8254 clock: 1193164 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency ppc0: using extended I/O port range ppc0: failed to probe at port 0x3bc-0x3c3 irq 7 on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio0: interrupting at ISA irq 4 sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at port 0x2f8-0x2ff irq 3 flags 0x80 on isa0 sio1: type 16550A sio1: interrupting at ISA irq 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xb8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 04 02 14 01 05 03 07 38 3c 3a 3e 39 3d 3b 3f 04 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 04 02 14 01 05 03 07 38 3c 3a 3e 39 3d 3b 3f 04 00 0f 08 00 00 00 00 00 10 0e 00 ff isa_probe_children: probing PnP devices Reducing kern.maxvnodes 522159 -> 100000 procfs registered Timecounter "i8254" frequency 1193182 Hz quality 0 Timecounters tick every 0.976 msec lo0: bpf attached Waiting 15 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. md0: Preloaded image 4423680 bytes at 0xfffffc00009ba570 GEOM: Configure md0a, start 8192 length 4415488 end 4423679 GEOM: Configure md0c, start 0 length 4423680 end 4423679 panic: HOST_MSG_LOOP with invalid SCB ff cpuid = 0 Uptime: 16s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. -- Greg A. Woods +1 416 218-0098 VE3TCP RoboHack Planix, Inc. Secrets of the Weird From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 10 20:28:06 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 C3C8716A4CE for ; Fri, 10 Dec 2004 20:28:06 +0000 (GMT) Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10FA343D4C for ; Fri, 10 Dec 2004 20:28:06 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr4.xs4all.nl (8.12.11/8.12.11) with ESMTP id iBAKS4nf037096; Fri, 10 Dec 2004 21:28:04 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.1/8.12.9) with ESMTP id iBAKS4we090347; Fri, 10 Dec 2004 21:28:04 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.1/8.13.1/Submit) id iBAKS3iQ090346; Fri, 10 Dec 2004 21:28:03 +0100 (CET) (envelope-from wb) Date: Fri, 10 Dec 2004 21:28:03 +0100 From: Wilko Bulte To: "Greg A. Woods" Message-ID: <20041210202803.GI90137@freebie.xs4all.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 4.10-STABLE X-PGP: finger wilko@freebsd.org User-Agent: Mutt/1.5.6i X-Virus-Scanned: by XS4ALL Virus Scanner cc: freebsd-alpha@freebsd.org Subject: Re: FYI, no-go with booting FreeBSD-5.3 on AlphaServer ES40 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: Fri, 10 Dec 2004 20:28:06 -0000 On Thu, Dec 09, 2004 at 08:21:35PM -0500, Greg A. Woods wrote.. > I was just trying to take a chance on testing the bge(4) driver from > FreeBSD and so tried booting the latest release on my client's ES40. > > Unfortunately even if it had not panic'ed I wouldn't have got the root > filesystem mounted as the bge(4) driver doesn't even seem to be a > default in the GENERIC kernel, which is pretty silly given that it the > driver for one of the more common GigE cards supplied by DEC/Compaq/HP, > e.g. the DEGXA-TX..... Looks like there are some problems with other > drivers too, but of course I don't know how serious they are. > > Maybe this "boot -v" output will help someone get it further along. > > Note that NetBSD does boot and run quite well on the system so long as > the ohci driver is omitted from the kernel and so long as none of the > IDE devices are accessed (or their driver is also omitted). The only > only problem is that both NetBSD's bge(4) and wm(4) drivers have rather > poor GigE performance on this system (once their minor bugs are fixed), > apparently because we have too much memory installed in it (and it's > only at half capacity!). What good is an alpha if you can't put more > than 4GB in it! ;-) FreeBSD does not even support 4GB so don't moan... :-P > Perhaps omitting ochi and atapci et al would help FreeBSD boot on the > ES40 as well? For the very near term I can try netbooting other kernels That is not the reason. > for testing. Note I'm not subscribed to the list though. I tested FreeBSD on ES40 some releases back and it worked OK. > real memory = 17172619264 (16377 MB) But surely not on 16G RAM. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 10 21:07:43 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 C92B916A4CE for ; Fri, 10 Dec 2004 21:07:43 +0000 (GMT) Received: from building.weird.com (building.weird.com [204.92.254.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FDC843D2F for ; Fri, 10 Dec 2004 21:07:43 +0000 (GMT) (envelope-from woods@building.weird.com) Received: from localhost (2266 bytes) by building.weird.com via sendmail with STDIO (sender: ) (ident using UNIX) id for ; (dest:remote)(R=bind_hosts)(T=inet_zone_bind_smtp) Fri, 10 Dec 2004 16:07:39 -0500 (EST) (Smail-3.2.0.121-Pre 2004-Aug-27 #1 built 2004-Nov-1) Message-Id: Date: Fri, 10 Dec 2004 16:07:39 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: ;j3Eth2XV8h1Yfu*uL{<:dQ$#E[DB0gemGZJ"J#4fH*][ lz; @-iwMv_u\6uIEKR0KY"=MzoQH#CrqBN`nG_5B@rrM8,f~Gr&h5a\= To: Wilko Bulte In-Reply-To: <20041210202803.GI90137@freebie.xs4all.nl> References: <20041210202803.GI90137@freebie.xs4all.nl> X-Mailer: VM 7.19 under Emacs 21.3.1 Organization: Planix, Inc.; Toronto, Ontario; Canada cc: freebsd-alpha@freebsd.org Subject: Re: FYI, no-go with booting FreeBSD-5.3 on AlphaServer ES40 X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Greg A. Woods" List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 21:07:43 -0000 [ On Friday, December 10, 2004 at 21:28:03 (+0100), Wilko Bulte wrote: ] > Subject: Re: FYI, no-go with booting FreeBSD-5.3 on AlphaServer ES40 > > FreeBSD does not even support 4GB so don't moan... :-P Sigh.... Any ES40 with fewer than 4 memory options installed (i.e. 8GB _minimum_) is a huge waste of space, energy, and money. With just 2 RAM options installed (i.e. 4GB minimum), the machine is way under-utilized and can only achieve 1/2 its memory throughput. With just one RAM option installed (i.e. 2GB minimum), the machine crawls at 1/4 its potential memory throughput. There are many better, faster, cheaper, smaller, types of systems available if one does not need to break the 4GB 32-bit address space boundary. I.e. I guess FreeBSD doesn't really truly support the ES40 (or anything bigger) at all. You should definitely not list them as supported! I'm sure anyone else familiar with Alphas would make the same assumption as I have that the full RAM configurations of any supported machine would work -- that's the whole reason for wanting a 64-bit address space in the first place! > But surely not on 16G RAM. BUT, that's only half-way to where we want to go with 32GB installed... -- Greg A. Woods +1 416 218-0098 VE3TCP RoboHack Planix, Inc. Secrets of the Weird From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 10 21:16:15 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 74C2C16A4CE for ; Fri, 10 Dec 2004 21:16:15 +0000 (GMT) Received: from smtp-vbr6.xs4all.nl (smtp-vbr6.xs4all.nl [194.109.24.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1EA143D5C for ; Fri, 10 Dec 2004 21:16:14 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr6.xs4all.nl (8.12.11/8.12.11) with ESMTP id iBALGDTI039464; Fri, 10 Dec 2004 22:16:13 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.1/8.12.9) with ESMTP id iBALGCdj090627; Fri, 10 Dec 2004 22:16:12 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.1/8.13.1/Submit) id iBALGCQh090626; Fri, 10 Dec 2004 22:16:12 +0100 (CET) (envelope-from wb) Date: Fri, 10 Dec 2004 22:16:12 +0100 From: Wilko Bulte To: "Greg A. Woods" Message-ID: <20041210211612.GA90601@freebie.xs4all.nl> References: <20041210202803.GI90137@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 4.10-STABLE X-PGP: finger wilko@freebsd.org User-Agent: Mutt/1.5.6i X-Virus-Scanned: by XS4ALL Virus Scanner cc: freebsd-alpha@freebsd.org Subject: Re: FYI, no-go with booting FreeBSD-5.3 on AlphaServer ES40 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: Fri, 10 Dec 2004 21:16:15 -0000 On Fri, Dec 10, 2004 at 04:07:39PM -0500, Greg A. Woods wrote.. > [ On Friday, December 10, 2004 at 21:28:03 (+0100), Wilko Bulte wrote: ] > > Subject: Re: FYI, no-go with booting FreeBSD-5.3 on AlphaServer ES40 > > > > FreeBSD does not even support 4GB so don't moan... :-P > > Sigh.... > > Any ES40 with fewer than 4 memory options installed (i.e. 8GB _minimum_) > is a huge waste of space, energy, and money. With just 2 RAM options > installed (i.e. 4GB minimum), the machine is way under-utilized and can > only achieve 1/2 its memory throughput. With just one RAM option > installed (i.e. 2GB minimum), the machine crawls at 1/4 its potential > memory throughput. > > There are many better, faster, cheaper, smaller, types of systems > available if one does not need to break the 4GB 32-bit address space > boundary. I know. Feel free to fix it. > I.e. I guess FreeBSD doesn't really truly support the ES40 (or anything > bigger) at all. You should definitely not list them as supported! I'm That is bull, as I did run FreeBSD on the ES40 at work. Briefly, as it is not my machine. > sure anyone else familiar with Alphas would make the same assumption as You should not make assumptions, it is documented that dependent on the machine model the limit is 1 or 2GB for FreeBSD. > I have that the full RAM configurations of any supported machine would > work -- that's the whole reason for wanting a 64-bit address space in > the first place! Yep, it would be very nice. > > But surely not on 16G RAM. > > BUT, that's only half-way to where we want to go with 32GB installed... Go and run Tru64 for a UNIX that makes full use of the ES40. None of the *BSD or Linux will if you look at it more or less closely. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 10 22:02:39 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 B3FF716A4CE for ; Fri, 10 Dec 2004 22:02:39 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 038E543D4C for ; Fri, 10 Dec 2004 22:02:39 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) iBAM2YSS043912 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Fri, 10 Dec 2004 23:02:36 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id iBAM1GCE066026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Dec 2004 23:01:16 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id iBAM1GBL079101; Fri, 10 Dec 2004 23:01:16 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id iBAM1FRo079100; Fri, 10 Dec 2004 23:01:15 +0100 (CET) (envelope-from ticso) Date: Fri, 10 Dec 2004 23:01:15 +0100 From: Bernd Walter To: Wilko Bulte Message-ID: <20041210220114.GQ63234@cicely12.cicely.de> References: <20041210202803.GI90137@freebie.xs4all.nl> <20041210211612.GA90601@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041210211612.GA90601@freebie.xs4all.nl> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de cc: freebsd-alpha@freebsd.org cc: "Greg A. Woods" Subject: Re: FYI, no-go with booting FreeBSD-5.3 on AlphaServer ES40 X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 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, 10 Dec 2004 22:02:39 -0000 On Fri, Dec 10, 2004 at 10:16:12PM +0100, Wilko Bulte wrote: > On Fri, Dec 10, 2004 at 04:07:39PM -0500, Greg A. Woods wrote.. > > [ On Friday, December 10, 2004 at 21:28:03 (+0100), Wilko Bulte wrote: ] > > > Subject: Re: FYI, no-go with booting FreeBSD-5.3 on AlphaServer ES40 > > > > > > FreeBSD does not even support 4GB so don't moan... :-P > > > > Sigh.... > > > > Any ES40 with fewer than 4 memory options installed (i.e. 8GB _minimum_) > > is a huge waste of space, energy, and money. With just 2 RAM options > > installed (i.e. 4GB minimum), the machine is way under-utilized and can > > only achieve 1/2 its memory throughput. With just one RAM option > > installed (i.e. 2GB minimum), the machine crawls at 1/4 its potential > > memory throughput. > > > > There are many better, faster, cheaper, smaller, types of systems > > available if one does not need to break the 4GB 32-bit address space > > boundary. > > I know. Feel free to fix it. I have an implementation that should work for ES40 as well, but unfortunately there are some bugs I hadn't time to find yet. I thought about splitting it up and start commiting a few structural changes soon so FreeBSD at least knows it's limitations and can automatically reduce physical memory until the implementation is working. Since someone recently brought up some problems with isp driver it might also be very well that this got me into troubles since booting failed with the isp controller IIRC. > > I.e. I guess FreeBSD doesn't really truly support the ES40 (or anything > > bigger) at all. You should definitely not list them as supported! I'm > > That is bull, as I did run FreeBSD on the ES40 at work. Briefly, as > it is not my machine. > > > sure anyone else familiar with Alphas would make the same assumption as > > You should not make assumptions, it is documented that dependent on the > machine model the limit is 1 or 2GB for FreeBSD. > > > I have that the full RAM configurations of any supported machine would > > work -- that's the whole reason for wanting a 64-bit address space in > > the first place! > > Yep, it would be very nice. We already have 53 bit virtual address space, just not physical. I already used more then 4G address space - even on NoName. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 10 22:25:45 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 3ED9316A4CE for ; Fri, 10 Dec 2004 22:25:45 +0000 (GMT) Received: from building.weird.com (building.weird.com [204.92.254.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id B84CF43D53 for ; Fri, 10 Dec 2004 22:25:44 +0000 (GMT) (envelope-from woods@building.weird.com) Received: from localhost (5185 bytes) by building.weird.com via sendmail with STDIO (sender: ) (ident using UNIX) id for ; (dest:remote)(R=bind_hosts)(T=inet_zone_bind_smtp) Fri, 10 Dec 2004 17:25:42 -0500 (EST) (Smail-3.2.0.121-Pre 2004-Aug-27 #1 built 2004-Nov-1) Message-Id: Date: Fri, 10 Dec 2004 17:25:42 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: ;j3Eth2XV8h1Yfu*uL{<:dQ$#E[DB0gemGZJ"J#4fH*][ lz; @-iwMv_u\6uIEKR0KY"=MzoQH#CrqBN`nG_5B@rrM8,f~Gr&h5a\= To: Wilko Bulte In-Reply-To: <20041210211612.GA90601@freebie.xs4all.nl> References: <20041210202803.GI90137@freebie.xs4all.nl> <20041210211612.GA90601@freebie.xs4all.nl> X-Mailer: VM 7.19 under Emacs 21.3.1 Organization: Planix, Inc.; Toronto, Ontario; Canada cc: freebsd-alpha@freebsd.org Subject: Re: FYI, no-go with booting FreeBSD-5.3 on AlphaServer ES40 X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Greg A. Woods" List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 22:25:45 -0000 [ On Friday, December 10, 2004 at 22:16:12 (+0100), Wilko Bulte wrote: ] > Subject: Re: FYI, no-go with booting FreeBSD-5.3 on AlphaServer ES40 > > I know. Feel free to fix it. You're the FreeBSD guy, not me! ;-) I can give you (or anyone else who's qualified) console access for a few days, as well as access to the temporary netboot server, if you'd like to work on it and you have time available now or in the very near future. > > I.e. I guess FreeBSD doesn't really truly support the ES40 (or anything > > bigger) at all. You should definitely not list them as supported! I'm > > That is bull, as I did run FreeBSD on the ES40 at work. Briefly, as > it is not my machine. To me "supported" means that it'll _work_, and do real work, for real production use, not just boot in some minimal "useless" configuration. (less than 4GB is "useless" to me! ;-) > You should not make assumptions, it is documented that dependent on the > machine model the limit is 1 or 2GB for FreeBSD. You need to update the 5.3R/hardware-alpha.html doc then (and probably the similar one for all previous releases too). There's no mention I can see in section 2.3.19 of any limit on the amount of supported RAM for the ES40. In fact the only mention I can find about any kind of RAM limit for FreeBSD/alpha is in the section about the 8200/8400's where it says that only 2GB has been tested (though several mentions are made of 28GB possibilities). What it does not say though is that anything more than 2GB will NOT work. If it won't work then you have to say that clearly. I wouldn't want an 8x00 machine with just 4GB or less either. You might also want to note that problem with the sym(4) driver too -- it doesn't look like it's going to work -- or is that just another symptom of having too much RAM for the whole system to cope? (The isp(4) driver isn't listed as supporting the 2342, but the complaints it spits out are worring too.) > Go and run Tru64 for a UNIX that makes full use of the ES40. None of the > *BSD or Linux will if you look at it more or less closely. NetBSD-1.6.2_STABLE works amazingly well with all 16GB of RAM and all four CPUs (with a couple of minor pmap patches), and the isp(4) driver works great and is very fast with the pair of Qlogic 2342 cards we have connecting it to each side of an Apple Xserve RAID shelf. (~35MB/sec from each LUN simultaneously with a simple "dd" from a file in the filesystem -- about as fast as the Xserve can go I think with RAID-5 on 7 spindles) NetBSD-current boots and works well on it too of course, but I'm building a production mail and web server so I won't run -current (and 2.0, though it has more efficient SMP, and UFSv2, is too new! ;-).... The only problem I'm having is that the bge(4) and sk(4) drivers, which were ported from FreeBSD, but a long time ago, make some rather bad PC-based assumptions about allocating DMA segments and either perform very poorly or not at all. Of course the NetBSD wm(4) driver for the Intel PRO/1000 cards has similar problems, though I can at least get it up to ~30MB/s with ttcp (one stream or many it max's out the same). I was hoping to test the newer version of the FreeBSD bge(4) and sk(4) drivers, as well as the FreeBSD em(4) driver (and maybe nge(4) as well) to see if any had any significant improvements worth looking at over their NetBSD counterparts. Note that since I can read up to 70MB/s (or more -- I have some SCSI drives attached too) from the filesystems then I need to be able to push it out the network that fast too, or else I'm wasting my client's time and money. Tru64 can indeed push the bge card up to 50 MB/s (and with only about 4% CPU utilization, assuming their OS isn't hiding interrupt cycles from the getrusage() system time numbers), so I know it can be done! If I could get even that same speed with a *BSD driver then I'd be very happy because I could put a pair of cards in it (one on each PCI bus) and give it two addresses to load balance since it really has two separate functions. -- Greg A. Woods +1 416 218-0098 VE3TCP RoboHack Planix, Inc. Secrets of the Weird