From owner-freebsd-alpha Sun Dec 10 2:41:44 2000 From owner-freebsd-alpha@FreeBSD.ORG Sun Dec 10 02:41:40 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 791A737B400; Sun, 10 Dec 2000 02:41:39 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 1453vF-000Pd9-00; Sun, 10 Dec 2000 10:41:37 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eBAAfK909696; Sun, 10 Dec 2000 11:41:20 +0100 (CET) (envelope-from wkb) Date: Sun, 10 Dec 2000 11:41:20 +0100 From: Wilko Bulte To: Bill Paul Cc: jhb@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: cvs commit: src/sys/alpha/conf GENERIC Message-ID: <20001210114120.A9610@freebie.demon.nl> References: <20001209104038.A5866@freebie.demon.nl> <20001209102145.C1CC137B400@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001209102145.C1CC137B400@hub.freebsd.org>; from wpaul@freebsd.org on Sat, Dec 09, 2000 at 02:21:45AM -0800 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Dec 09, 2000 at 02:21:45AM -0800, Bill Paul wrote: > I would have prefered it if you had put the cable in the tx0 interface > and *then* ifconfig'ed it. Because you didn't do it this way, the OK, I have tried this, cable connected before boot. Results below. Look identical to me. > results are a little ambiguous. I would also have prefered it if you > had run tcpdump or checked netstat -in to see if you were receiving > any packets even though you may not have been sending any. OK, checked that as well. Tcpdump does not see anything on tx0 when run on the Alpha. tcpdump when run on another host also does not see anything from the Alpha on the wire (as expected) > -Bill > > P.S.: I noticed that you have your dc0 interface hardcoded to 100baseTX. > Did you set this manually or is this just the result of the NVRAM setting It is not in rc.conf.. hmm OK, it is hard set in SRM: ewa0_mode Fast Lets try: >>>set ewa0_mode auto-negotiate Change mode to auto negotiate >>> > on your particular alpha? Also, what alpha is it, and what happens if This is a Miata 500/ MX5. Using dc0: port 0x9080-0x90ff mem 0x80960080-0x809600ff irq 0 at device 3.0 on pci0 dc0: interrupting at CIA irq 0 dc0: Ethernet address: 00:00:f8:75:3c:6a miibus0: on dc0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > you do ifconfig dc0 media autoselect? This gives me: Doing initial network setup: hostname. dc0: flags=8843 mtu 1500 inet 192.168.200.24 netmask 0xffffff00 broadcast 192.168.200.255 ether 00:00:f8:75:3c:6a media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX Works just fine on 100Mbit. mx5# ifconfig tx0 192.168.200.24 mx5# tx0: can't stop Tx DMA Dec 20 11:27:13 mx5 /kernel: tx0: can't stop Tx DMA Dec 20 11:27:13 mx5 /kernel: tx0: can't stop Tx DMA mx5# tx0: device timeout 1 packets, reinitialization tx0: can't stop Tx DMA Dec 20 11:27:21 mx5 /kernel: tx0: device timeout 1 packets, reinitialization Dec 20 11:27:21 mx5 /kernel: tx0: device timeout 1 packets, reinitialization Dec 20 11:27:21 mx5 /kernel: tx0: can't stop Tx DMA Dec 20 11:27:21 mx5 /kernel: tx0: can't stop Tx DMA mx5# mx5# ifconfig -a dc0: flags=8802 mtu 1500 ether 00:00:f8:75:3c:6a media: autoselect (none) status: no carrier supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX tx0: flags=8843 mtu 1500 inet 192.168.200.24 netmask 0xffffff00 broadcast 192.168.200.255 ether 00:e0:29:15:b9:43 media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 mx5# ping 192.168.200.1 PING 192.168.200tx0: can't stop Tx DMA .1 (192.168.200.1): 48 data bytes Dec 20 11:28:29 mx5 /kernel: tx0: can't stop Tx DMA Dec 20 11:28:29 mx5 /kernel: tx0: can't stop Tx DMA ^C --- 192.168.200.1 ping statistics --- 6 packets transmitted, 0 packets received, 100% packet loss mx5# tx0: device timeout 5 packets, reinitialization tx0: can't stop Tx DMA Dec 20 11:28:41 mx5 /kernel: tx0: device timeout 5 packets, reinitialization Dec 20 11:28:41 mx5 /kernel: tx0: device timeout 5 packets, reinitialization Dec 20 11:28:41 mx5 /kernel: tx0: can't stop Tx DMA Dec 20 11:28:41 mx5 /kernel: tx0: can't stop Tx DMA mx5# ping 192.168.200.1 PING 192.168.200.1 (192.168.200.1): 48 data bytes ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down ^C --- 192.168.200.1 ping statistics --- 9 packets transmitted, 0 packets received, 100% packet loss mx5# arp -a ? (192.168.200.1) at (incomplete) [ethernet] mx5# tx0: device timeout 5 packets, reinitialization tx0: can't stop Tx DMA Dec 20 11:29:22 mx5 /kernel: tx0: device timeout 5 packets, reinitialization Dec 20 11:29:22 mx5 /kernel: tx0: device timeout 5 packets, reinitialization Dec 20 11:29:22 mx5 /kernel: tx0: can't stop Tx DMA Dec 20 11:29:22 mx5 /kernel: tx0: can't stop Tx DMA mx5# -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 10 8:30:40 2000 From owner-freebsd-alpha@FreeBSD.ORG Sun Dec 10 08:30:37 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 58B8937B402 for ; Sun, 10 Dec 2000 08:30:34 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 1459Mu-0007fe-00; Sun, 10 Dec 2000 17:30:32 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.1/8.11.1) id eBAFZar44423 for freebsd-alpha@freebsd.org; Sun, 10 Dec 2000 16:35:36 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: need help with dagrab, cdd Date: Sun, 10 Dec 2000 15:35:35 +0000 (UTC) Message-ID: <9107s7$1amk$1@kemoauc.mips.inka.de> References: <20001209122701.A14517@anomaly.stupid.net> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: daemon@mips.inka.de Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nick wrote: > bash-2.04# dagrab -d /dev/cd1a -a ^^^^ Er, that's a SCSI drive. ports/audio/dagrab/pkg-descr says: DAGRAB is a program for reading audio tracks from a CD into wav sound files. An IDE CD-rom drive that supports digital audio is required. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 10 15:20: 5 2000 From owner-freebsd-alpha@FreeBSD.ORG Sun Dec 10 15:20:03 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from anomaly.stupid.net (unknown [151.199.74.208]) by hub.freebsd.org (Postfix) with ESMTP id 3D3ED37B400 for ; Sun, 10 Dec 2000 15:20:01 -0800 (PST) Received: (from fb@localhost) by anomaly.stupid.net (8.9.3/8.9.3) id SAA01544 for freebsd-alpha@freebsd.org; Sun, 10 Dec 2000 18:22:42 -0500 (EST) (envelope-from fb) Date: Sun, 10 Dec 2000 18:22:42 -0500 From: Nick To: freebsd-alpha@freebsd.org Subject: having problems with cdrecord Message-ID: <20001210182242.B1508@anomaly.stupid.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i Sender: fb@anomaly.stupid.net Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This may not be the best place for this kind of question so I apologize in advance. I have a 4.1 system with cdrecord 1.9. I have found that I about every other CD that I burn gets screwed up. These are CDR's and I do not believe that this is due to a buffer under run. I have a Yamaha CDR 400T hanging off of my AS200's onboard NCR controller. 50% of the time, CDR's burn find, the other 50% of the time I get an error like this one: cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error It usually happens withing the first couple of minutes of burning. A log of the output of cdrecord is given at the end of this message. I am using cdrecord 1.9 from the ports collection from 4.2. I got the same behaviour from the 1.8.x version that came with the ports of 4.1. Thanks, Nick Maniscalco sh-2.04# cdrecord speed=4 dev=0,6,0 -pad -dao -audio 01.wav 02.wav 03.wav 04.w av 05.wav 06.wav 07.wav 08.wav 09.wav 10.wav Cdrecord 1.9 (alpha-unknown-freebsd4.2) Copyright (C) 1995-2000 Jörg Schilling scsidev: '0,6,0' scsibus: 0 target: 6 lun: 0 Using libscg version 'schily-0.1' Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : Vendor_info : 'YAMAHA ' Identifikation : 'CDR400t ' Revision : '1.0q' Device seems to be: Yamaha CDR-400. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO Starting to write CD/DVD at speed 4 in write mode for single session. Last chance to quit, starting real write in 1 seconds. cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 00 00 6A D7 00 00 1B 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 04 D3 C0 00 00 0A 00 00 00 00 09 00 00 00 00 00 00 00 00 08 0 0 00 00 00 00 00 08 00 01 06 Sense Key: 0x4 Hardware Error, Segment 0 Sense Code: 0x09 Qual 0x00 (track following error) Fru 0x0 Sense flags: Blk -742391808 (not valid) write track data: error after 64329552 bytes Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 bash-2.04# To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 10 15:30:50 2000 From owner-freebsd-alpha@FreeBSD.ORG Sun Dec 10 15:30:48 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 3BC7837B400 for ; Sun, 10 Dec 2000 15:30:48 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 145Fva-0003gp-00; Mon, 11 Dec 2000 00:30:46 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.1/8.11.1) id eBAMibE00699 for freebsd-alpha@freebsd.org; Sun, 10 Dec 2000 23:44:37 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: SRM: "ISA table corrupt!"? Date: Sun, 10 Dec 2000 22:44:37 +0000 (UTC) Message-ID: <91110l$am$1@kemoauc.mips.inka.de> References: <90ouu9$2ni$1@kemoauc.mips.inka.de> <20001207223833.A2651@freebie.demon.nl> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: daemon@mips.inka.de Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte wrote: > > ERROR: ISA table corrupt! > > Initializing table to defaults > > Guessing: would this possibly be related to: > > " > SRM quirks: > PC164 the SRM sometimes seems to loose its variable settings. Possibly. What's strange is that if I do "isacfg -init" followed by "isacfg -all" I get another warning about a corrupted ISA table. My SRM indeed doesn't seem to hold variable settings across power cycling. There's no special action to take, it should just remember things like "set bootdef_dev dka0", shouldn't it? -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 4: 9:17 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 04:09:10 2000 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 A06FA37B6B9 for ; Mon, 11 Dec 2000 04:08:46 -0800 (PST) Received: from master.telia.net (master.telia.net [194.237.170.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id E284B6E2E5F for ; Mon, 11 Dec 2000 00:51:10 -0800 (PST) Received: from localhost (elite@localhost) by master.telia.net (8.11.1/8.11.0) with ESMTP id eBB8mbF37084; Mon, 11 Dec 2000 09:48:37 +0100 (CET) (envelope-from khaled@w-arts.com) X-Authentication-Warning: master.telia.net: elite owned process doing -bs Date: Mon, 11 Dec 2000 09:48:37 +0100 (CET) From: Khaled Daham X-Sender: elite@master.telia.net To: Christian Weisgerber Cc: freebsd-alpha@freebsd.org Subject: Re: Borg SRM? In-Reply-To: <90tclq$2oih$1@kemoauc.mips.inka.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 9 Dec 2000, Christian Weisgerber wrote: > Wilko Bulte wrote: > > > Everything produced by Compaq these days has SRM. > > So has everything by Samsung and API. 164UX and BX does not have a SRM. so not entirely true. /Khaled Daham, w.arts Mail: khaled@w-arts.com Cell: +46-70-6785492, +966-54491462 FreeBSD: The Power to Serve! http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 5:32:57 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 05:32:55 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from home.se (smtphost2.home.se [195.66.35.198]) by hub.freebsd.org (Postfix) with ESMTP id B141837B400 for ; Mon, 11 Dec 2000 05:32:54 -0800 (PST) Received: from daniel.n.nilsson@home.se [161.114.88.74] by home.se with Novell Internet Messaging System Web Client; Mon, 11 Dec 2000 14:31:33 Subject: Re: Re: SRM: "ISA table corrupt!"? From: Daniel Nilsson To: naddy@mips.inka.de, freebsd-alpha@freebsd.org, Date: Mon, 11 Dec 2000 13:31:33 GMT X-Sender: Novell Internet Messaging System Web Client MIME-Version: 1.0 Message-ID: <976541493.190daniel.n.nilsson@home.se> Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Naddy, Some SRM versions requires you to do an init after changing the parameters. The SRM in may machines uses the NVRAM that hangs off the RTC to store some parameters. Check if your battery is dead. Regards Daniel Nilsson > Wilko Bulte wrote: > > > > ERROR: ISA table corrupt! > > > Initializing table to defaults > > > > Guessing: would this possibly be related to: > > > > " > > SRM quirks: > > PC164 the SRM sometimes seems to loose its variable settings. > > Possibly. What's strange is that if I do "isacfg -init" followed > by "isacfg -all" I get another warning about a corrupted ISA table. > > My SRM indeed doesn't seem to hold variable settings across power > cycling. There's no special action to take, it should just remember > things like "set bootdef_dev dka0", shouldn't it? > > -- > Christian "naddy" Weisgerber naddy@mips.inka.de > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 8:30:35 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 08:30:34 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id F16A037B400 for ; Mon, 11 Dec 2000 08:30:33 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 145VqS-0000we-01; Mon, 11 Dec 2000 17:30:32 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.1/8.11.1) id eBBFnJM01934 for freebsd-alpha@freebsd.org; Mon, 11 Dec 2000 16:49:19 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Borg SRM? Date: Mon, 11 Dec 2000 15:49:14 +0000 (UTC) Message-ID: <912t1q$151$3@kemoauc.mips.inka.de> References: <90tclq$2oih$1@kemoauc.mips.inka.de> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: daemon@mips.inka.de Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Khaled Daham wrote: > > > Everything produced by Compaq these days has SRM. > > > > So has everything by Samsung and API. > > 164UX and BX does not have a SRM. I'm only too well aware of that--I have a UX right here--but the stress is on "these days". The 164[BU]X are old boards that aren't available any longer. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 8:30:40 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 08:30:39 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 8D25F37B402 for ; Mon, 11 Dec 2000 08:30:38 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 145VqS-0000we-02; Mon, 11 Dec 2000 17:30:32 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.1/8.11.1) id eBBFp9K01992 for freebsd-alpha@freebsd.org; Mon, 11 Dec 2000 16:51:09 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: SRM: "ISA table corrupt!"? Date: Mon, 11 Dec 2000 15:51:09 +0000 (UTC) Message-ID: <912t5d$151$4@kemoauc.mips.inka.de> References: <976541493.190daniel.n.nilsson@home.se> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: daemon@mips.inka.de Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Daniel Nilsson wrote: > The SRM in may machines uses the NVRAM that hangs off the RTC to > store some parameters. Check if your battery is dead. Since system time is preserved across power cycling, the battery should be fine. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 14:31:37 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 14:31:35 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 11E2437B400 for ; Mon, 11 Dec 2000 14:31:35 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA59875 for ; Mon, 11 Dec 2000 14:31:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eBBMVXB33537 for alpha@freebsd.org; Mon, 11 Dec 2000 14:31:33 -0800 (PST) (envelope-from obrien) Date: Mon, 11 Dec 2000 14:31:33 -0800 From: "David O'Brien" To: alpha@freebsd.org Subject: -current not bootable on Rawhide (as4100) Message-ID: <20001211143132.A33433@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: obrien@NUXI.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Booting a kernel built last night produces: panic: cpu_initclocks: no clock attached Anybody have any idea what changed in the past week? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 14:38:51 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 14:38:49 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D968C37B404; Mon, 11 Dec 2000 14:38:48 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA06670; Mon, 11 Dec 2000 17:38:48 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eBBMcmH34404; Mon, 11 Dec 2000 17:38:48 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 11 Dec 2000 17:38:47 -0500 (EST) To: obrien@FreeBSD.ORG Cc: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-Reply-To: <20001211143132.A33433@dragon.nuxi.com> References: <20001211143132.A33433@dragon.nuxi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14901.22315.914524.872886@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David O'Brien writes: > Booting a kernel built last night produces: > > panic: cpu_initclocks: no clock attached > > Anybody have any idea what changed in the past week? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message Can we see the lines above that? It sounds like its missing the attachement to the eisa/isa bus. A shot in the dark, but Mike Smith has been playing with the pci code recently.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 14:52:48 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 14:52:44 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id BEEBA37B400 for ; Mon, 11 Dec 2000 14:52:44 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA59978 for ; Mon, 11 Dec 2000 14:52:43 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eBBMqgI33910 for alpha@FreeBSD.ORG; Mon, 11 Dec 2000 14:52:42 -0800 (PST) (envelope-from obrien) Date: Mon, 11 Dec 2000 14:52:42 -0800 From: "David O'Brien" To: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) Message-ID: <20001211145242.A88817@dragon.nuxi.com> Reply-To: alpha@FreeBSD.ORG References: <20001211143132.A33433@dragon.nuxi.com> <14901.22315.914524.872886@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14901.22315.914524.872886@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Mon, Dec 11, 2000 at 05:38:47PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: obrien@NUXI.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Dec 11, 2000 at 05:38:47PM -0500, Andrew Gallatin wrote: > Booting a kernel built last night produces: > > panic: cpu_initclocks: no clock attached Copyright (c) 1992-2000 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. Setting atkbd 0 at to atkbdc (string) Setting atkbd 0 irq to 1 (int) Setting atkbdc 0 at to isa (string) Setting atkbdc 0 port to 96 (int) Setting fd 0 at to fdc0 (string) Setting fd 0 drive to 0 (int) Setting fdc 0 at to isa (string) Setting fdc 0 drq to 2 (int) Setting fdc 0 irq to 6 (int) Setting fdc 0 port to 1008 (int) Setting mcclock 0 at to isa (string) Setting mcclock 0 port to 112 (int) Setting ppc 0 at to isa (string) Setting ppc 0 irq to 7 (int) Setting psm 0 at to atkbdc (string) Setting psm 0 irq to 12 (int) Setting sc 0 at to isa (string) Setting sio 0 at to isa (string) Setting sio 0 irq to 4 (int) Setting sio 0 port to 1016 (int) Setting sio 1 at to isa (string) Setting sio 1 flags to 80 (int) Setting sio 1 irq to 3 (int) Setting sio 1 port to 760 (int) Setting vga 0 at to isa (string) FreeBSD 5.0-CURRENT #0: Mon Dec 11 12:34:34 PST 2000 rootk@rawhide.osd.bsdi.com:/1/obj/usr/src/sys/GENERIC AlphaServer 4100 AlphaServer 4100 5/300 2MB, 299MHz 8192 byte page size, 2 processors. CPU: EV5 (21164) major=5 minor=5 OSF PAL rev: 0x4000200020117 real memory = 534757376 (522224K bytes) Physical memory chunk(s): 0x007da000 - 0x1fff3fff, 528588800 bytes (64525 pages) avail memory = 514400256 (502344K bytes) Preloaded elf kernel "kernel" at 0xfffffc00007ba000. random: mem: null: Creating DISK md0 md0: Malloc disk mcbus0: pcib0: at mcbus0 gid 7 mid 5 pcib0: Horse Revision 3, Left Handed Saddle Revision 3, CAP Revision 2 pci0: physical bus=0 found-> vendor=0x1000, dev=0x0001, revid=0x02 bus=0, slot=1, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=4 map[10]: type 4, range 32, base 01fffe00, size 8, enabled map[14]: type 1, range 32, base 07fffe00, size 8, enabled found-> vendor=0x1011, dev=0x0009, revid=0x11 bus=0, slot=2, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=8 map[10]: type 4, range 32, base 01ffff00, size 7, enabled map[14]: type 1, range 32, base 07ffff00, size 7, enabled pci0: on pcib0 sym0: <810> port 0x1fffe00-0x1fffeff mem 0x7fffe00-0x7fffeff irq 4 at device 1.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using NCR-generic 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) 03/c8/00/00/08/00 sym0: Delay (GEN=11): 267 msec, 33289 KHz sym0: Delay (GEN=11): 283 msec, 31407 KHz sym0: Delay (GEN=11): 283 msec, 31407 KHz sym0: interrupting at IRQ 0x10 intA (vec 0xb40) de0: port 0x1ffff00-0x1ffff7f mem 0x7ffff00-0x7ffff7f irq 8 at device 2.0 on pci0 de0: interrupting at IRQ 0x0 intA (vec 0xb80) de0: DEC DE500-XA 21140 [10-100Mb/s] pass 1.1 de0: address 00:00:f8:00:3c:ec de0: enabling Full Duplex 100baseTX port bpf: de0 attached pcib1: at mcbus0 gid 7 mid 4 pcib1: Horse Revision 3, Left Handed Saddle Revision 3, CAP Revision 2 Attaching Real Console pci1: physical bus=0 found-> vendor=0x8086, dev=0x0482, revid=0x15 bus=0, slot=1, func=0 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x5333, dev=0x8811, revid=0x00 bus=0, slot=2, func=0 class=88-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 07800000, size 23, enabled found-> vendor=0x1011, dev=0x0001, revid=0x02 bus=0, slot=4, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=0 secondarybus=0 pci1: on pcib1 pci1: at 1.0 (no driver attached) pci1: at 2.0 (no driver attached) pcib2: at device 4.0 on pci1 pcib2: secondary bus 6 pcib2: subordinate bus 6 pcib2: I/O decode 0x60000-0x60fff pcib2: memory decode 0x0-0xfffff pcib2: prefetched decode 0x0-0xfffff pci2: physical bus=6 pci2: on pcib2 panic: cpu_initclocks: no clock attached To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 15:15:16 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 15:15:15 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EAACA37B400; Mon, 11 Dec 2000 15:15:14 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA13588; Mon, 11 Dec 2000 15:15:21 -0800 Date: Mon, 11 Dec 2000 15:15:14 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-Reply-To: <20001211143132.A33433@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org no, it's bootable. You have something fouled up with your device.hints. > Booting a kernel built last night produces: > > panic: cpu_initclocks: no clock attached > > Anybody have any idea what changed in the past week? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 15:21:36 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 15:21:35 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id F0E0C37B400 for ; Mon, 11 Dec 2000 15:21:34 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA60111; Mon, 11 Dec 2000 15:21:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eBBNLWs34358; Mon, 11 Dec 2000 15:21:32 -0800 (PST) (envelope-from obrien) Date: Mon, 11 Dec 2000 15:21:32 -0800 From: "David O'Brien" To: Matthew Jacob Cc: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) Message-ID: <20001211152132.B88817@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20001211143132.A33433@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Mon, Dec 11, 2000 at 03:15:14PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: obrien@NUXI.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Dec 11, 2000 at 03:15:14PM -0800, Matthew Jacob wrote: > no, it's bootable. You have something fouled up with your device.hints. What device.hints are you using? I'm using straight GENERIC.hints. $FreeBSD: src/sys/alpha/conf/GENERIC.hints,v 1.1 2000/06/13 22:28:42 peter Exp $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 15:52:55 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 15:52:54 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id BE55D37B400 for ; Mon, 11 Dec 2000 15:52:53 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBC02h301059 for ; Mon, 11 Dec 2000 16:02:43 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012120002.eBC02h301059@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-reply-to: Your message of "Mon, 11 Dec 2000 14:52:42 PST." <20001211145242.A88817@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Dec 2000 16:02:43 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There was a window where I think I deleted the PCI:ISA bridge's ID from the isa_pci bridge driver. If the bridge has a stupid subclass, that would do this. I've since fixed this, I think. David, can you give us the output of 'pciconf -lv'? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 16:34:24 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 16:34:22 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7C81037B400; Mon, 11 Dec 2000 16:34:22 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA13889; Mon, 11 Dec 2000 16:34:28 -0800 Date: Mon, 11 Dec 2000 16:34:21 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-Reply-To: <20001211152132.B88817@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org No, I take it back. Things are now broken for Rawhide (top of tree checked out an hour ago). Basically, the isa bus isn't being configured. C'est la vie. -matt > On Mon, Dec 11, 2000 at 03:15:14PM -0800, Matthew Jacob wrote: > > no, it's bootable. You have something fouled up with your device.hints. > > What device.hints are you using? I'm using straight GENERIC.hints. > $FreeBSD: src/sys/alpha/conf/GENERIC.hints,v 1.1 2000/06/13 22:28:42 peter Exp $ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 18: 1:59 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 18:01:58 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 58DCE37B402; Mon, 11 Dec 2000 18:01:58 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBC21tE66429; Mon, 11 Dec 2000 18:01:55 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001211143132.A33433@dragon.nuxi.com> Date: Mon, 11 Dec 2000 18:02:01 -0800 (PST) From: John Baldwin To: "David O'Brien" Subject: RE: -current not bootable on Rawhide (as4100) Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 11-Dec-00 David O'Brien wrote: > Booting a kernel built last night produces: > > panic: cpu_initclocks: no clock attached > > Anybody have any idea what changed in the past week? Did mcclock0 attach and probe ok? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 18:47: 2 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 18:47:01 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1DD0837B400; Mon, 11 Dec 2000 18:47:01 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBC2kwE68445; Mon, 11 Dec 2000 18:46:58 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 11 Dec 2000 18:47:04 -0800 (PST) From: John Baldwin To: Matthew Jacob Subject: Re: -current not bootable on Rawhide (as4100) Cc: alpha@FreeBSD.org, "David O'Brien" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 11-Dec-00 Matthew Jacob wrote: > > no, it's bootable. You have something fouled up with your device.hints. No, his ISA bus never attached because the PCI-ISA bridge wasn't found. Note that he had _no_ isa devices, but that he did have hints for them at the top of the output that looked fine. Mike is probably right about it being the PCI:ISA bridge business. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 18:51:12 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 18:51:11 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id B3F6B37B400; Mon, 11 Dec 2000 18:51:10 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBC30x301536; Mon, 11 Dec 2000 19:00:59 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012120300.eBC30x301536@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: alpha@FreeBSD.org Subject: Re: -current not bootable on Rawhide (as4100) In-reply-to: Your message of "Mon, 11 Dec 2000 18:47:04 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Dec 2000 19:00:59 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > no, it's bootable. You have something fouled up with your device.hints. > > No, his ISA bus never attached because the PCI-ISA bridge wasn't found. > Note that he had _no_ isa devices, but that he did have hints for them at > the top of the output that looked fine. Mike is probably right about it > being the PCI:ISA bridge business. Can someone just please send me the output of 'pciconf -lv' on one of these boxes? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 18:58:42 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 18:58:40 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9BCE937B400; Mon, 11 Dec 2000 18:58:39 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBC2wbE68677; Mon, 11 Dec 2000 18:58:37 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200012120300.eBC30x301536@mass.osd.bsdi.com> Date: Mon, 11 Dec 2000 18:58:43 -0800 (PST) From: John Baldwin To: Mike Smith Subject: Re: -current not bootable on Rawhide (as4100) Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 12-Dec-00 Mike Smith wrote: >> > no, it's bootable. You have something fouled up with your device.hints. >> >> No, his ISA bus never attached because the PCI-ISA bridge wasn't found. >> Note that he had _no_ isa devices, but that he did have hints for them at >> the top of the output that looked fine. Mike is probably right about it >> being the PCI:ISA bridge business. > > Can someone just please send me the output of 'pciconf -lv' on one of > these boxes? sym0@pci0:1:0: class=0x010000 card=0x00000000 chip=0x00011000 rev=0x02 hdr=0x00 class = mass storage subclass = SCSI de0@pci0:2:0: class=0x020000 card=0x00000000 chip=0x00091011 rev=0x11 hdr=0x00 class = network subclass = ethernet isab0@pci0:1:0: class=0x000000 card=0x00000000 chip=0x04828086 rev=0x15 hdr=0x00 class = old subclass = non-VGA display device none0@pci0:2:0: class=0x880000 card=0x88000000 chip=0x88115333 rev=0x00 hdr=0x00 pcib2@pci0:4:0: class=0x060400 card=0x00000000 chip=0x00011011 rev=0x02 hdr=0x01 class = bridge subclass = PCI-PCI isp0@pci2:0:0: class=0x010000 card=0x00000000 chip=0x10201077 rev=0x02 hdr=0x00 class = mass storage subclass = SCSI Gee, a class of "old" and subclass of "non-VGA display device" looks like a fubar'd ID for that isa bus. :( -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 19:30:36 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 19:30:34 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 4751737B400; Mon, 11 Dec 2000 19:30:34 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBC3eM301684; Mon, 11 Dec 2000 19:40:23 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012120340.eBC3eM301684@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: alpha@FreeBSD.org Subject: Re: -current not bootable on Rawhide (as4100) In-reply-to: Your message of "Mon, 11 Dec 2000 18:58:43 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Dec 2000 19:40:22 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > isab0@pci0:1:0: class=0x000000 card=0x00000000 chip=0x04828086 rev=0x15 hdr=0x00 > class = old > subclass = non-VGA display device > > Gee, a class of "old" and subclass of "non-VGA display device" looks like a > fubar'd ID for that isa bus. :( (The box seems to be missing /usr/share/misc/pci_vendors). It's actually an EISA bridge, and I fubar'ed the PCI:EISA bridge code. Now I'm afraid that even requiring the class register to be right for the ISA code is too optomistic, so I'm going to change it again. Bah. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 19:40:55 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 19:40:53 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 93B4337B402; Mon, 11 Dec 2000 19:40:53 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBC3epE69694; Mon, 11 Dec 2000 19:40:51 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.0) id eBC3e6m11710; Mon, 11 Dec 2000 19:40:06 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200012120340.eBC3eM301684@mass.osd.bsdi.com> Date: Mon, 11 Dec 2000 19:40:05 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Mike Smith Subject: Re: -current not bootable on Rawhide (as4100) Cc: alpha@FreeBSD.org Sender: jhb@foo.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 12-Dec-00 Mike Smith wrote: >> isab0@pci0:1:0: class=0x000000 card=0x00000000 chip=0x04828086 rev=0x15 >> hdr=0x00 >> class = old >> subclass = non-VGA display device >> >> Gee, a class of "old" and subclass of "non-VGA display device" looks like a >> fubar'd ID for that isa bus. :( > > (The box seems to be missing /usr/share/misc/pci_vendors). Could be. It had a new world that hadn't been installed yet, and I had to install libc and pciconf by hand to get one that knew what the -v option was. > It's actually an EISA bridge, and I fubar'ed the PCI:EISA bridge code. > Now I'm afraid that even requiring the class register to be right for the > ISA code is too optomistic, so I'm going to change it again. > > Bah. Doh. Sounds like fun. *duck* -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 23:48:37 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 23:48:35 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6ED6F37B400; Mon, 11 Dec 2000 23:48:35 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id XAA14917; Mon, 11 Dec 2000 23:48:41 -0800 Date: Mon, 11 Dec 2000 23:48:35 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" , Mike Smith Cc: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tried Mike's change, but things not there yet. I'll try and bust loose some more time tomorrow to look at it (this is a Solaris/Linux for Veritas week). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 23:51:44 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 23:51:42 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 91E8237B400; Mon, 11 Dec 2000 23:51:42 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBC81T302396; Tue, 12 Dec 2000 00:01:29 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012120801.eBC81T302396@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: "David O'Brien" , alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-reply-to: Your message of "Mon, 11 Dec 2000 23:48:35 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Dec 2000 00:01:29 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Tried Mike's change, but things not there yet. I'll try and bust loose some > more time tomorrow to look at it (this is a Solaris/Linux for Veritas week). Um, still not probing an ISA bus? Does the kernel config have EISA in it? It just occurs to me that if you don't, you won't get the ISA bus (because the bridge is PCI:EISA). I guess I can easily add it as an ISA bridge as well, with a lower match, but that's not really the "right" answer... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 11 23:56:26 2000 From owner-freebsd-alpha@FreeBSD.ORG Mon Dec 11 23:56:25 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E17A637B400; Mon, 11 Dec 2000 23:56:23 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id XAA14938; Mon, 11 Dec 2000 23:56:30 -0800 Date: Mon, 11 Dec 2000 23:56:23 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: "David O'Brien" , alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-Reply-To: <200012120801.eBC81T302396@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 12 Dec 2000, Mike Smith wrote: > > > > Tried Mike's change, but things not there yet. I'll try and bust loose some > > more time tomorrow to look at it (this is a Solaris/Linux for Veritas week). > > Um, still not probing an ISA bus? > > Does the kernel config have EISA in it? It just occurs to me that if you > don't, you won't get the ISA bus (because the bridge is PCI:EISA). D'oh! This is what I get for just doing this stuff with half a brain, which, as you know, makes things pretty small for now. I just porked my system, so I can't fix this until I get in tomorrow. > > I guess I can easily add it as an ISA bridge as well, with a lower match, > but that's not really the "right" answer... That's right. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 0: 2:41 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 00:02:39 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D93937B400; Tue, 12 Dec 2000 00:02:38 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA14982; Tue, 12 Dec 2000 00:02:44 -0800 Date: Tue, 12 Dec 2000 00:02:38 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: "David O'Brien" , alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Even less brains... checking this out... There is no EISA code for the Alpha (at least in FreeBSD). So clearly some more thought needs to go into this. On Mon, 11 Dec 2000, Matthew Jacob wrote: > > > On Tue, 12 Dec 2000, Mike Smith wrote: > > > > > > > Tried Mike's change, but things not there yet. I'll try and bust loose some > > > more time tomorrow to look at it (this is a Solaris/Linux for Veritas week). > > > > Um, still not probing an ISA bus? > > > > Does the kernel config have EISA in it? It just occurs to me that if you > > don't, you won't get the ISA bus (because the bridge is PCI:EISA). > > D'oh! > > This is what I get for just doing this stuff with half a brain, which, as you > know, makes things pretty small for now. I just porked my system, so I can't > fix this until I get in tomorrow. > > > > > > I guess I can easily add it as an ISA bridge as well, with a lower match, > > but that's not really the "right" answer... > > That's right. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 0:16:17 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 00:16:14 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 1D15137B69E for ; Tue, 12 Dec 2000 00:16:13 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBC8Q1302477; Tue, 12 Dec 2000 00:26:01 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012120826.eBC8Q1302477@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-reply-to: Your message of "Mon, 11 Dec 2000 23:56:23 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Dec 2000 00:26:01 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Does the kernel config have EISA in it? It just occurs to me that if you > > don't, you won't get the ISA bus (because the bridge is PCI:EISA). > > D'oh! > > This is what I get for just doing this stuff with half a brain, which, as you > know, makes things pretty small for now. I just porked my system, so I can't > fix this until I get in tomorrow. You mean this is what I get. 8) At any rate, there are a couple of solutions. One is to say "if you have a PCI:EISA bridge, you must have EISA support to get ISA". I don't really like that. Another is to match an EISA bridge as an ISA bridge, but that's also bad. A third, and I kinda like this one, is to build the EISA bridge support anytime you build PCI. The EISA bridge code will hang out a hook for an EISA bus (which doesn't have to be there), but it will also hang out a hook for an ISA bus, which might be. This is the way it used to "work" as well... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 0:32:52 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 00:32:50 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 37ED237B400; Tue, 12 Dec 2000 00:32:50 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA15021; Tue, 12 Dec 2000 00:32:56 -0800 Date: Tue, 12 Dec 2000 00:32:49 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-Reply-To: <200012120826.eBC8Q1302477@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 12 Dec 2000, Mike Smith wrote: > > > Does the kernel config have EISA in it? It just occurs to me that if you > > > don't, you won't get the ISA bus (because the bridge is PCI:EISA). > > > > D'oh! > > > > This is what I get for just doing this stuff with half a brain, which, as you > > know, makes things pretty small for now. I just porked my system, so I can't > > fix this until I get in tomorrow. > > You mean this is what I get. 8) At any rate, there are a couple of > solutions. One is to say "if you have a PCI:EISA bridge, you must have > EISA support to get ISA". I don't really like that. That's the NetBSD solution. > Another is to match an EISA bridge as an ISA bridge, but that's also bad. True. > > A third, and I kinda like this one, is to build the EISA bridge support > anytime you build PCI. The EISA bridge code will hang out a hook for an > EISA bus (which doesn't have to be there), but it will also hang out a > hook for an ISA bus, which might be. This is the way it used to "work" > as well... If this was the change to conf/files, I'll try it in the morning. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 0:38:32 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 00:38:31 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 41D8937B400 for ; Tue, 12 Dec 2000 00:38:30 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBC8mI302562; Tue, 12 Dec 2000 00:48:18 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012120848.eBC8mI302562@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-reply-to: Your message of "Tue, 12 Dec 2000 00:32:49 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Dec 2000 00:48:18 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > You mean this is what I get. 8) At any rate, there are a couple of > > solutions. One is to say "if you have a PCI:EISA bridge, you must have > > EISA support to get ISA". I don't really like that. > > That's the NetBSD solution. Well, it'd work better if we had EISA code for the Alpha. 8) > > A third, and I kinda like this one, is to build the EISA bridge support > > anytime you build PCI. The EISA bridge code will hang out a hook for an > > EISA bus (which doesn't have to be there), but it will also hang out a > > hook for an ISA bus, which might be. This is the way it used to "work" > > as well... > > If this was the change to conf/files, I'll try it in the morning. It was, please let me know if it unbreaks things for you. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 8:55:46 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 08:55:44 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 5343237B400 for ; Tue, 12 Dec 2000 08:55:44 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 145siE-0005j0-00; Tue, 12 Dec 2000 17:55:34 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.1/8.11.1) id eBCFwup00752 for freebsd-alpha@freebsd.org; Tue, 12 Dec 2000 16:58:56 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: SRM: "ISA table corrupt!"? Date: Tue, 12 Dec 2000 15:58:56 +0000 (UTC) Message-ID: <915i00$lt$1@kemoauc.mips.inka.de> References: <90ouu9$2ni$1@kemoauc.mips.inka.de> <20001207223833.A2651@freebie.demon.nl> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: daemon@mips.inka.de Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte wrote: > > ERROR: ISA table corrupt! > > Guessing: would this possibly be related to: > > SRM quirks: > PC164 the SRM sometimes seems to loose its variable settings. > "For PC164, current superstition says that, to avoid losing settings, > you want to first downgrade to SRM 4.x and then upgrade to a 5.x" > Other PC164 owners report they have never seen the problem. Yes! I downgraded to SRM 4.9, did isacfg -init init there, upgraded again to SRM 5.5, and now (1) the error above is gone and (2) SRM remembers NVRAM settings. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 12:45:18 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 12:45:16 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D7F0D37B400; Tue, 12 Dec 2000 12:45:15 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA65316; Tue, 12 Dec 2000 12:45:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eBCKjER14600; Tue, 12 Dec 2000 12:45:14 -0800 (PST) (envelope-from obrien) Date: Tue, 12 Dec 2000 12:45:13 -0800 From: "David O'Brien" To: Mike Smith Cc: alpha@freebsd.org Subject: Re: -current not bootable on Rawhide (as4100) Message-ID: <20001212124513.C14459@dragon.nuxi.com> Reply-To: alpha@freebsd.org References: <200012120300.eBC30x301536@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200012120300.eBC30x301536@mass.osd.bsdi.com>; from msmith@freebsd.org on Mon, Dec 11, 2000 at 07:00:59PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: obrien@NUXI.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Dec 11, 2000 at 07:00:59PM -0800, Mike Smith wrote: > Can someone just please send me the output of 'pciconf -lv' on one of > these boxes? PRE_SMPNG kernel: rawhide# -lv sym0@pci0:1:0: class=0x010000 card=0x00000000 chip=0x00011000 rev=0x02 hdr=0x00 class = mass storage subclass = SCSI de0@pci0:2:0: class=0x020000 card=0x00000000 chip=0x00091011 rev=0x11 hdr=0x00 class = network subclass = ethernet isab0@pci0:1:0: class=0x000000 card=0x00000000 chip=0x04828086 rev=0x15 hdr=0x00 class = old subclass = non-VGA display device none0@pci0:2:0: class=0x880000 card=0x88000000 chip=0x88115333 rev=0x00 hdr=0x00 pcib2@pci0:4:0: class=0x060400 card=0x00000000 chip=0x00011011 rev=0x02 hdr=0x01 class = bridge subclass = PCI-PCI isp0@pci2:0:0: class=0x010000 card=0x00000000 chip=0x10201077 rev=0x02 hdr=0x00 class = mass storage subclass = SCSI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 12:46:50 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 12:46:47 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5E63E37B404; Tue, 12 Dec 2000 12:46:45 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA65328; Tue, 12 Dec 2000 12:46:44 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eBCKkhi14626; Tue, 12 Dec 2000 12:46:43 -0800 (PST) (envelope-from obrien) Date: Tue, 12 Dec 2000 12:46:43 -0800 From: "David O'Brien" To: Mike Smith Cc: John Baldwin , alpha@freebsd.org Subject: Re: -current not bootable on Rawhide (as4100) Message-ID: <20001212124642.D14459@dragon.nuxi.com> Reply-To: alpha@freebsd.org References: <200012120340.eBC3eM301684@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200012120340.eBC3eM301684@mass.osd.bsdi.com>; from msmith@freebsd.org on Mon, Dec 11, 2000 at 07:40:22PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: obrien@NUXI.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Dec 11, 2000 at 07:40:22PM -0800, Mike Smith wrote: > (The box seems to be missing /usr/share/misc/pci_vendors). It is at PRE_SMPNG. I'm not willing to issue the ``make installworld'' until a -current kernel boots on it. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 13:21:11 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 13:21:10 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id E3FB937B402 for ; Tue, 12 Dec 2000 13:21:09 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBCLUu305172 for ; Tue, 12 Dec 2000 13:30:59 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012122130.eBCLUu305172@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: alpha@freebsd.org Subject: Re: -current not bootable on Rawhide (as4100) In-reply-to: Your message of "Tue, 12 Dec 2000 12:46:43 PST." <20001212124642.D14459@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Dec 2000 13:30:56 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Mon, Dec 11, 2000 at 07:40:22PM -0800, Mike Smith wrote: > > (The box seems to be missing /usr/share/misc/pci_vendors). > > It is at PRE_SMPNG. I'm not willing to issue the ``make installworld'' > until a -current kernel boots on it. Understood. It should be fixed now. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 14:24:32 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 14:24:27 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 68E7A37B400; Tue, 12 Dec 2000 14:24:26 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA17906; Tue, 12 Dec 2000 14:24:32 -0800 Date: Tue, 12 Dec 2000 14:24:25 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: alpha@FreeBSD.ORG Subject: Re: -current not bootable on Rawhide (as4100) In-Reply-To: <200012122130.eBCLUu305172@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > On Mon, Dec 11, 2000 at 07:40:22PM -0800, Mike Smith wrote: > > > (The box seems to be missing /usr/share/misc/pci_vendors). > > > > It is at PRE_SMPNG. I'm not willing to issue the ``make installworld'' > > until a -current kernel boots on it. > > Understood. It should be fixed now. Not yet. Copyright (c) 1992-2000 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. Setting atkbd 0 at to atkbdc (string) Setting atkbd 0 irq to 1 (int) Setting atkbdc 0 at to isa (string) Setting atkbdc 0 port to 96 (int) Setting fd 0 at to fdc0 (string) Setting fd 0 drive to 0 (int) Setting fdc 0 at to isa (string) Setting fdc 0 drq to 2 (int) Setting fdc 0 irq to 6 (int) Setting fdc 0 port to 1008 (int) Setting mcclock 0 at to isa (string) Setting mcclock 0 port to 112 (int) Setting ppc 0 at to isa (string) Setting ppc 0 irq to 7 (int) Setting psm 0 at to atkbdc (string) Setting psm 0 irq to 12 (int) Setting sc 0 at to isa (string) Setting sio 0 at to isa (string) Setting sio 0 irq to 4 (int) Setting sio 0 port to 1016 (int) Setting sio 1 at to isa (string) Setting sio 1 flags to 80 (int) Setting sio 1 irq to 3 (int) Setting sio 1 port to 760 (int) Setting vga 0 at to isa (string) FreeBSD 5.0-CURRENT #0: Tue Dec 12 13:56:36 PST 2000 mjacob@farrago.feral.com:/tstsys/compile/GPLUS AlphaServer 4100 AlphaServer 4100 5/533 4MB, 531MHz 8192 byte page size, 4 processors. CPU: EV56 (21164A) major=7 minor=2 extensions=0x1 OSF PAL rev: 0x4000100020117 real memory = 1608482816 (1570784K bytes) Physical memory chunk(s): 0x00722000 - 0x5ffeffff, 1603067904 bytes (195687 pages) avail memory = 1560805376 (1524224K bytes) Preloaded elf kernel "kernel" at 0xfffffc0000702000. Preloaded elf module "ispfw.ko" at 0xfffffc00007020c0. WARNING: size of kinfo_proc (904) should be 640!!! random: null: mem: Creating DISK md0 md0: Malloc disk mcbus0: pcib0: at mcbus0 gid 7 mid 5 pcib0: Horse Revision 3, Left Handed Saddle Revision 3, CAP Revision 2 pci0: physical bus=0 found-> vendor=0x1000, dev=0x0001, revid=0x02 bus=0, slot=1, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=4 map[10]: type 4, range 32, base 01fffc00, size 8, enabled map[14]: type 1, range 32, base 07fdde00, size 8, enabled found-> vendor=0x1011, dev=0x0009, revid=0x12 bus=0, slot=2, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=8 map[10]: type 4, range 32, base 01fffd00, size 7, enabled map[14]: type 1, range 32, base 07fddf00, size 7, enabled found-> vendor=0x1077, dev=0x1020, revid=0x05 bus=0, slot=4, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 4, range 32, base 01fffe00, size 8, enabled map[14]: type 1, range 32, base 07fde000, size 12, enabled found-> vendor=0x1077, dev=0x1020, revid=0x05 bus=0, slot=5, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=20 map[10]: type 4, range 32, base 01ffff00, size 8, enabled map[14]: type 1, range 32, base 07fdf000, size 12, enabled pci0: on pcib0 sym0: <810> port 0x1fffc00-0x1fffcff mem 0x7fdde00-0x7fddeff irq 4 at device 1.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using NCR-generic 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) 03/c8/00/00/08/00 sym0: Delay (GEN=11): 268 msec, 33165 KHz sym0: Delay (GEN=11): 283 msec, 31407 KHz sym0: Delay (GEN=11): 284 msec, 31296 KHz sym0: interrupting at IRQ 0x10 intA (vec 0xb40) de0: port 0x1fffd00-0x1fffd7f mem 0x7fddf00-0x7fddf7f irq 8 at device 2.0 on pci0 de0: interrupting at IRQ 0x0 intA (vec 0xb80) de0: DEC DE500-XA 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:f8:01:8b:d7 de0: enabling Full Duplex 100baseTX port bpf: de0 attached Qlogic ISP Driver, FreeBSD Version 5.4, Core Version 2.0 isp0: port 0x1fffe00-0x1fffeff mem 0x7fde000-0x7fdefff irq 16 at device 4.0 on pci0 isp0: using Memory space register mapping isp0: interrupting at IRQ 0x8 intA (vec 0xc00) isp0: Ultra Mode Capable isp0: Board Revision 1040B, loaded F/W Revision 4.65.0 isp0: Last F/W revision was 5.57.1 isp0: 243 max I/O commands supported isp0: Initiator ID is 7 isp1: port 0x1ffff00-0x1ffffff mem 0x7fdf000-0x7fdffff irq 20 at device 5.0 on pci0 isp1: not configuring device_probe_and_attach: isp1 attach returned 19 pcib1: at mcbus0 gid 7 mid 4 pcib1: Horse Revision 3, Left Handed Saddle Revision 3, CAP Revision 2 Attaching Real Console sio1: gdb debugging port pci1: physical bus=0 found-> vendor=0x8086, dev=0x0482, revid=0x15 bus=0, slot=1, func=0 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1077, dev=0x2100, revid=0x03 bus=0, slot=3, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[10]: type 4, range 32, base 01ffff00, size 8, enabled map[14]: type 1, range 32, base 07fef000, size 12, enabled pci1: on pcib1 eisab0: at device 1.0 on pci1 isp2: port 0x1ffff00-0x1ffffff mem 0x7fef000-0x7feffff irq 12 at device 3.0 on pci1 isp2: not configuring device_probe_and_attach: isp2 attach returned 19 panic: cpu_initclocks: no clock attached panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffc0000707cc0> db> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 15:39:56 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 15:39:55 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id ADA3437B400 for ; Tue, 12 Dec 2000 15:39:54 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBCNnZ305749 for ; Tue, 12 Dec 2000 15:49:43 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012122349.eBCNnZ305749@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: alpha@freebsd.org Subject: Re: cvs commit: src/sys/isa isa_common.c In-reply-to: Your message of "Tue, 12 Dec 2000 15:33:29 PST." <200012122333.eBCNXT023968@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Dec 2000 15:49:35 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matt reports that this has finally fixed the 4100 again. It probably also fixes other Alphas with PCI:EISA bridges (eg. 2100). > msmith 2000/12/12 15:33:29 PST > > Modified files: > sys/isa isa_common.c > Log: > It's possible for an ISA bus to be hung off an EISA bridge, so we need to > reflect that here. > > Revision Changes Path > 1.22 +2 -1 src/sys/isa/isa_common.c > > > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 23:46:44 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 23:46:41 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E4F9C37B400; Tue, 12 Dec 2000 23:46:40 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA68405; Tue, 12 Dec 2000 23:46:39 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eBD7kXR73948; Tue, 12 Dec 2000 23:46:33 -0800 (PST) (envelope-from obrien) Date: Tue, 12 Dec 2000 23:46:32 -0800 From: "David O'Brien" To: Mike Smith Cc: alpha@freebsd.org Subject: Re: cvs commit: src/sys/isa isa_common.c Message-ID: <20001212234632.B73840@dragon.nuxi.com> Reply-To: alpha@freebsd.org References: <200012122333.eBCNXT023968@freefall.freebsd.org> <200012122349.eBCNnZ305749@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200012122349.eBCNnZ305749@mass.osd.bsdi.com>; from msmith@freebsd.org on Tue, Dec 12, 2000 at 03:49:35PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: obrien@NUXI.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Dec 12, 2000 at 03:49:35PM -0800, Mike Smith wrote: > Matt reports that this has finally fixed the 4100 again. It probably > also fixes other Alphas with PCI:EISA bridges (eg. 2100). It didn't for the BSDi Rawhide. But I see you've commited more PCI-related bits. So I'm building a new kernel.. we'll see. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 12 23:50:48 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 12 23:50:47 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0224A37B400; Tue, 12 Dec 2000 23:50:47 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id XAA19330; Tue, 12 Dec 2000 23:50:53 -0800 Date: Tue, 12 Dec 2000 23:50:46 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@FreeBSD.ORG Cc: Mike Smith Subject: Re: cvs commit: src/sys/isa isa_common.c In-Reply-To: <20001212234632.B73840@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, Dec 12, 2000 at 03:49:35PM -0800, Mike Smith wrote: > > Matt reports that this has finally fixed the 4100 again. It probably > > also fixes other Alphas with PCI:EISA bridges (eg. 2100). > > It didn't for the BSDi Rawhide. But I see you've commited more > PCI-related bits. So I'm building a new kernel.. we'll see. Hmm. Make sure you're not confusing this with other issues. What do you have in all the PCI slots in this RawHide? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 13 0: 0:21 2000 From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 13 00:00:18 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id C8BB837B69C for ; Wed, 13 Dec 2000 00:00:17 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBD8A6307198 for ; Wed, 13 Dec 2000 00:10:06 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012130810.eBD8A6307198@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: alpha@freebsd.org Subject: Re: cvs commit: src/sys/isa isa_common.c In-reply-to: Your message of "Tue, 12 Dec 2000 23:46:32 PST." <20001212234632.B73840@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Dec 2000 00:10:06 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, Dec 12, 2000 at 03:49:35PM -0800, Mike Smith wrote: > > Matt reports that this has finally fixed the 4100 again. It probably > > also fixes other Alphas with PCI:EISA bridges (eg. 2100). > > It didn't for the BSDi Rawhide. But I see you've commited more > PCI-related bits. So I'm building a new kernel.. we'll see. Can you elaborate? Was the EISA bridge found? Did it attach an ISA bus? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 13 0:18:41 2000 From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 13 00:18:40 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from master.telia.net (master.telia.net [194.237.170.70]) by hub.freebsd.org (Postfix) with ESMTP id 850BE37B400 for ; Wed, 13 Dec 2000 00:18:39 -0800 (PST) Received: from localhost (elite@localhost) by master.telia.net (8.11.1/8.11.0) with ESMTP id eBD8IXi44367; Wed, 13 Dec 2000 09:18:33 +0100 (CET) (envelope-from khaled@w-arts.com) X-Authentication-Warning: master.telia.net: elite owned process doing -bs Date: Wed, 13 Dec 2000 09:18:33 +0100 (CET) From: Khaled Daham X-Sender: elite@master.telia.net To: Christian Weisgerber Cc: freebsd-alpha@freebsd.org Subject: Re: Borg SRM? In-Reply-To: <912t1q$151$3@kemoauc.mips.inka.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 11 Dec 2000, Christian Weisgerber wrote: > Khaled Daham wrote: > > > > > Everything produced by Compaq these days has SRM. > > > > > > So has everything by Samsung and API. > > > > 164UX and BX does not have a SRM. > > I'm only too well aware of that--I have a UX right here--but the > stress is on "these days". The 164[BU]X are old boards that aren't > available any longer. Mh should have read more carefully.. ah well :) /Khaled Daham, w.arts Mail: khaled@w-arts.com Cell: +46-70-6785492, +966-54491462 FreeBSD: The Power to Serve! http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 13 0:28:13 2000 From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 13 00:28:12 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id ED9DE37B400 for ; Wed, 13 Dec 2000 00:28:11 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA19466; Wed, 13 Dec 2000 00:28:15 -0800 Date: Wed, 13 Dec 2000 00:28:08 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@FreeBSD.ORG Subject: Re: cvs commit: src/sys/isa isa_common.c In-Reply-To: <20001212234632.B73840@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I forgot to check this in into mcpcia.c: DEVMETHOD(pcib_route_interrupt, alpha_pci_route_interrupt), See if that's what you're missing. On Tue, 12 Dec 2000, David O'Brien wrote: > On Tue, Dec 12, 2000 at 03:49:35PM -0800, Mike Smith wrote: > > Matt reports that this has finally fixed the 4100 again. It probably > > also fixes other Alphas with PCI:EISA bridges (eg. 2100). > > It didn't for the BSDi Rawhide. But I see you've commited more > PCI-related bits. So I'm building a new kernel.. we'll see. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 13 1: 7:57 2000 From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 13 01:07:56 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BA6D437B400 for ; Wed, 13 Dec 2000 01:07:55 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id BAA19635; Wed, 13 Dec 2000 01:07:56 -0800 Date: Wed, 13 Dec 2000 01:07:49 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@FreeBSD.ORG Subject: Re: cvs commit: src/sys/isa isa_common.c In-Reply-To: <20001212234632.B73840@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Top 'o tree + change to mcpcia booted 4 hose system at NASA/Ames (well, it panic'd ifconfig'ing up an interface, but, hey, well, you can't have everything) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 13 2:11:55 2000 From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 13 02:11:54 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 063BB37B402 for ; Wed, 13 Dec 2000 02:11:54 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id CAA69039; Wed, 13 Dec 2000 02:11:53 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eBDABpk75764; Wed, 13 Dec 2000 02:11:51 -0800 (PST) (envelope-from obrien) Date: Wed, 13 Dec 2000 02:11:51 -0800 From: "David O'Brien" To: Matthew Jacob Cc: alpha@FreeBSD.ORG Subject: Re: cvs commit: src/sys/isa isa_common.c Message-ID: <20001213021151.A75716@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20001212234632.B73840@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Wed, Dec 13, 2000 at 12:28:08AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: obrien@NUXI.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Dec 13, 2000 at 12:28:08AM -0800, Matthew Jacob wrote: > I forgot to check this in into mcpcia.c: I updated sources around midnight, and built a new kernel. I am now back to hanging at "Waiting 15 seconds for SCSI devices to settle" -- so things are back to how they were before Mike's PCI changes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 13 6:21:13 2000 From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 13 06:21:01 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from arka.ids.bielsko.pl (arka.ids.bielsko.pl [195.117.233.8]) by hub.freebsd.org (Postfix) with ESMTP id AF9F037B402 for ; Wed, 13 Dec 2000 06:20:58 -0800 (PST) Received: by arka.ids.bielsko.pl (8.9.3/8.9.3) id PAA05540 for freebsd-alpha@FreeBSD.org; Wed, 13 Dec 2000 15:18:27 +0100 (MET) Date: Wed, 13 Dec 2000 15:18:27 +0100 (MET) Message-Id: <200012131418.PAA05540@arka.ids.bielsko.pl> Subject: New European Promotional Contest From: office@euroleader.org MIME-Version: 1.0 To: freebsd-alpha@FreeBSD.org Content-Type: multipart/alternative; boundary="------------070C33C436192682FC31B74B" Sender: lider@arka.ids.bielsko.pl Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------070C33C436192682FC31B74B Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit Dear Sirs, We are very pleased to welcome you and present a new economic initiative for producers from all European countries - both western and eastern. FOR THE FIRST TIME - ON SUCH A LARGE SCALE - IN THE VERY HEART OF EUROPE! [Image] "EURO LEADER 2001" This is an honourable title and prestigious Promotional Emblem in European Promotional Contest. This is an effective tool of promotion and marketing in Europe by means of which it is much easier to reach western markets, increase export and gain new partners for cooperation in the field of production and investment. The contest is a Polish initiative. It will be settled in March, 2001 in Warsaw. Therefore it will bring the best commercial effects on a stable, almost 40-million prospective customers Polish market, having over 5% economic growth, which will soon become an integral market of European Union. Click http://www.euroleader.org/ and get acquainted with the details of the contest, enter for the European competition. It will bring you success and a good start in the XXI century! You are good but are you well-known? You will be well-known! Join us. Yours faithfully, INTERRES International Building Fair and Promotion - from Poland B2B - Internet Portal Tadeusz Ziobro - President. --------------070C33C436192682FC31B74B Content-Type: multipart/related; boundary="------------CEE33E5E78D696CB4E0EC941" --------------CEE33E5E78D696CB4E0EC941 Content-Type: text/html; charset=iso-8859-2 Content-Transfer-Encoding: 8bit
Dear Sirs,

We are very pleased to welcome you and present a new economic initiative
for producers from all European countries - both western and eastern.

FOR THE FIRST TIME - ON SUCH A LARGE SCALE - IN THE VERY HEART OF EUROPE!

"EURO LEADER 2001"

This is an honourable title and prestigious Promotional Emblem
in European Promotional Contest.

This is an effective tool of promotion and marketing in Europe
by means of which it is much easier to reach western markets,
increase export and gain new partners for cooperation in the
field of production and investment.




The contest is a Polish initiative.
It will be settled in March, 2001 in Warsaw. Therefore it will bring the best commercial effects on a stable, almost 40-million
prospective customers Polish market, having over 5% economic growth, which will soon become an integral market of European Union.

Click http://www.euroleader.org/ and get acquainted with the details of the contest, enter for the European competition.

It will bring you success and a good start in the XXI century!
You are good but are you well-known? You will be well-known! Join us.

Yours faithfully,

INTERRES International Building Fair and Promotion - from Poland
B2B - Internet Portal
Tadeusz Ziobro - President.
  --------------CEE33E5E78D696CB4E0EC941 Content-Type: image/jpeg Content-ID: Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="C:\WINDOWS\TEMP\nsmail24.jpeg" /9j/4AAQSkZJRgABAgEASABIAAD//gAmRmlsZSB3cml0dGVuIGJ5IEFkb2JlIFBob3Rvc2hv cKggNS4w/+4ADkFkb2JlAGSAAAAAAf/bAIQADAgICAkIDAkJDBELCgsRFQ8MDA8VGBMTFRMT GBEMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAENCwsNDg0QDg4QFA4ODhQU Dg4ODhQRDAwMDAwREQwMDAwMDBEMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwM/8AAEQgA eAB4AwEiAAIRAQMRAf/dAAQACP/EAT8AAAEFAQEBAQEBAAAAAAAAAAMAAQIEBQYHCAkKCwEA AQUBAQEBAQEAAAAAAAAAAQACAwQFBgcICQoLEAABBAEDAgQCBQcGCAUDDDMBAAIRAwQhEjEF QVFhEyJxgTIGFJGhsUIjJBVSwWIzNHKC0UMHJZJT8OHxY3M1FqKygyZEk1RkRcKjdDYX0lXi ZfKzhMPTdePzRieUpIW0lcTU5PSltcXV5fVWZnaGlqa2xtbm9jdHV2d3h5ent8fX5/cRAAIC AQIEBAMEBQYHBwYFNQEAAhEDITESBEFRYXEiEwUygZEUobFCI8FS0fAzJGLhcoKSQ1MVY3M0 8SUGFqKygwcmNcLSRJNUoxdkRVU2dGXi8rOEw9N14/NGlKSFtJXE1OT0pbXF1eX1VmZ2hpam tsbW5vYnN0dXZ3eHl6e3x//aAAwDAQACEQMRAD8A1Prf9b+sdH6w/FxXtNRaHAOHCxP/ABx/ rF+8z7kv8Y//AIonf1AuVWjixQMIkxGy0kvVf+OP9Yv3mfcl/wCOP9Yv3mfcuVST/Zx/uhVl 6r/xyPrF+8z7kv8AxyPrF+8z7lysGJ7BJL2cf7oVZeq/8cj6xeLPuS/8cf6x6ElgB40WJ0bA wOoZQxcvN+wF8Cq1zNzC4/mWO3N9Jdz176jdOp6LhG7Pbhs6ZW5l2S9kize71Poh30/UPsUU /ZhIRMRr4K1cH/xyPrF+8z7kv/HH+sX7zPuXMXCltrxQ51lQMMe9u1zh+85ku2KHMAak6AfF Sezj/dH2KsvVf+OP9Yv3mfcl/wCOP9Yv3mfcuby8W/DybMXIbsupdssb4EIKXtYz+iFWXqv/ ABx/rF+8z7kv/HH+sX7zPuXKpI+zj/dCrL6L9UPrf1jrHWGYuU9oqDS4ho5SWJ/i3/8AFE3+ oUlD7cPf4eEVw7KvR//QB/jH/wDFE7+oFyq6r/GP/wCKJ39QLlVqYf5uPksO6kTHZTZexl9v oVOMPt2l+0fvbG+5yjsfsNm07AdpdGm4jdtn+qo69k9T6P0z6g0P+r2ZSzNpyH55rsx8tjSW NFR3N7/nS/euE6rhYmDknGxsxudskWW1tLaw4fmse4/pVu4f19zOm14eH0+hg6diV+nZTYPd cT/PWPsH8179/p7f+uLmsh1Lr7HUNLKXPc6tjuWtJ3NYY/dUOKOQSkZnQ6jb8UmmeBdRRm0X 5FZtpqe176hA3bTuDJP7zlu5n146n1LGzcPqbGXYuY39FWwBpoe33Uuqd+e1u3371zaSklCM iCRZG3gi1fFdZ9Q6ei5/Uq8DOwPVyWTdTlNe6B6fv25FW7Z9L6D1yasYnUMvCbc3FsNJyWen a9uj9k7jW1/5m/8AP2pZImUSAaP2KD3f+MSroeG5uV9g+0Z/UAYyS9wqbsDWb9rHfpLdv5q8 8Vh2flvwW9PfYX4tb/VqrdrsdG13pu+kxr/zmKvwJPZDFAwjwk34pKklYzcHJwbW05Ldj31s uaP5NjfUZ/0VXTwb1CHqv8W//iib/UKSX+Lf/wAUTf6hSUH/AII/wU9H/9EH+Mf/AMUTv6gX N4bcN2Qxuc+yvHOj7KQHPb/K2Pjcuk/xkf8Aiid/UC5XQ88d4Wni/mo+S07vqFH1K6I/6quo ZnOdjW2DOHUNoBDWtj6H7npb15xns6fXkuZ062y/GboLrWhhcf3mMb9Gv93ctofXvrNeTW6n YzBprFDOnxNRqA2RY76brXf6Vc67aXHYNrZO1p1gfmt/soYYZIk8Zu9Qo0skr1HQus5NLL6M O2yqwSx7QII4THonVxkDFOJZ9ocw2Nqj3FgO0vS+84LI97Hcb4hxxuPD83Erhl2P2NJJXP2P 1T7WMI4tn2ot3imPdt/fSPRuqjKGH9ls+1FnqCmPds/fS+8Yf87D5eP54/zf7/8Ac/rK4T2L TSV+3oPW6mF9mDcGjk7Z/wCpVKuqy2xtVTHPseYaxoJcT4bU6GbFMGUMkZiPzGMoyEfPhUYk bgsV0H1PPTMjqdXTOo9OZnNyn7WWy4PrMbvdtc1tlPt9yz7fq/1umo22YVrWDUnbMR4hqrYe dlYNjrsSw1WuY6v1G/Sa130/Td+Y530d6aMmPNCXtZIzrS8cuLhl5wUQRuCPN9K+v37ExsBn UX9Prz8gn7LVaXHZXG5w9X0nDds93sXl5MmdBOunCNXm5VeLbhtsP2a8h1lR1aXtMttG76Nv 8tARxY+CNE8Xj4KJt6r/ABb/APiib/UKSX+Lf/xRN/qFJM/8Ef4Kuj//0gf4yP8AxRO/qBc3 i4eRmOsZjsL3VVvuePBlY32OXSf4xzH1jJiYYNDwun+oNHQcrAtz6MAYV75xLyXudW+Yc5tP qO/P/dV/3PbwxNXoFtavl3mkFu/W1nSMTqVvTemYH2QYj9llr3Oc95j8xrnOayrX+2sIKeMu IA1V90PpP1eJ/wCbOIRYKSKTFroIb7ne87vaqeFbY/62NbZlMzdmG6Law1oEunZ+iLmqj0n6 2dHxekUdPyqrbHVsLLQGhzDJcY1P8pUr/rL0/H6zj5/SsYV011Gq6na2vfuPujZ+d/KXIQ+F 85LPz49iQ98Z/anIY+A8fqh+s/nI8f8AiNw5YcOP1D08Nh3Xf+Lqv/wmVJ//AIuKv/CJ/KVW /wCeH1b9cZxx7ftmz0w7YN23/R7921ZVH1pod9Y3dWy63MoFJprrZDnAfmzwm4vh/OzEieXn j9rkZcp6+G8ub/VqOSAr1A3Pj8g9q05rMy6yx9bcBtbTWPzw8fzrnO/0e1ZH1cb07L6r1Tqm IGkPtbXU+IgbZssaPzfWeqVf15xB1C57mWuwXsb6Ygbm2DR/tn+bsWVhfWPF6X1bIu6ex1nT 8shz8d8Nc13P6Plvs/NUfL/Bue9jmoHFLHlyYMccfDUMOSMZQyZcWT/yo9H/AKUTLNDiibsA m+48f7r03S/rFkZ3WcnpzsU1Mo3bbZM+w7f0kjb+k/NXKfXDFpxuuWikBjbWNtcwaAOcPdH9 b6S6G76+9HbWXU1W2XEfQIDBP8uyVxnUM7I6jmWZmQQbLTwOAB9Fjf5LFo/BOR5jHzks55Y8 lg9kYjjlPj93KOH9Z6mPPOJgI8XHK7vsELKrXgllbngclrS6PjtC0+qfV/M6djdPudXY451H rOaGk7Xbv5v2/wDB+k9T+qmf1LE6zjMwLvS+0WNZcH61mv6Vjrmn/R17nb/zF3fX/rji5XR8 7/m/mN+24hBedvuNUhl1uLv+nt3fzi38mScZxAAIO/19Pqa4Dy/+Llrm/WMNcC1wYZBEEfFJ L/F05z/rJve4ve5pLnOMkk/nOJSQ/wDBH+Aro//TB/jI/wDFE7+oFzz+o5j8WjD9VzMfGJfV Ww7RvJ3G5236Vv8ALXQ/4yP/ABRO/qBcoSBqTHxWniAOOHktO7Yzc7Kz7vtGW/1b9rWOsP0n Bg2sNn7z9v56AeCrf7Nv/Y/7Y0+zfaPs0/ytu/du/wCgqcgg7TPwUka6dNEPR/Wqqqvp/RzW xrC7HJcWgAnRn0o+ktPJqya/qtjWYmHj21uxT9rueAHsEaWV/vvVTrD+jdR6PiOHUGsycLHh tAEl7y1v6M/u/RUc67puZ0DCrHUhRfiY53YzZPqOI/mX8N/NXMAzli5OBjkBxc1m97jxZ5xq css8XycHHH1Q4J/zcGzoDM6axFUYtn6mdPxremZD8ljXnMsNFRcAT7WH6O5VvqrW3Gp6w62l ltmGyQ2xocNzN/j/AFUfC650jp3TukYzgMiyt3qWvY4j0bHfSfY2P0nts+ip42Z0VvUOts+2 114+e1vpW6kS5p9Tbp+Y5Mzy5mUueM8eb2uYljnj9Mj6OV5qGGXt8Hr9eD1/KmPD6KIuII/x otDruNg5XSsDruLS3GfkvFeRSzRu6eWt/rNWn9casijprhj4dDcJzGC3JADbGvJ0awN/NWR1 3qXThgYXRumPN2PhuD7LyI3O/k/e5zlb+td/TOoU/asbqQc+uprBhtmHkH6Wvt3NlS48eYZf h5nHIMUcvMGAywy5ZQwe7j+6xy8H83Pg/m5Z/wCbQTGslVdR2r5v0nZx8VtlXTqX4dD+n3Ym 7MvcxoLXBrdh9T81ef3NY26xtZ3Vh7gw+LQfb/0V2ret9Jtw6emX5LBj3YPp2v1hlrdoa1+i 4gtIO3mDEjv8FY+A480ZcwcsZwsjhjIS4Zx483631/5X/J/7OGJbnIPDWv8ALZYGPyJAxxp8 Fq9D+r2Z1bKuobXZX6NFl0lpbLmj9DX7h/hLFmupvY3dZU9g4Jc1zRPh7gtwSBJF6jdgen/x b/8Aiib/AFCkl/i3/wDFE3+oUlD/AOCP8FPR/9QH+Mj/AMUTv6gXO4Gff0/JblUBjns5ZY0P Y4d2PY/95dF/jI/8UTv6gXLBxaQQYIMg+YWniF4og9lp3fZm53Tz00YfoYv7Rdjfav2V7du/ b6m3Zt/f/k715Dn9Qv6jkuyr2sY5/FdTAxjR2YxjP3UL7Rf6/wBp9R3r7t/qyd+7nfv+luUC 4uJc4ySSSfMoYsIxkm7v8FErJKTarHse9jS5lQDrHAaNBOwOd/aUVKhSSSSKlJJJJKUkiU49 17ntpYXmtjrXgdmME2P/ALKGgp9G+qf1vZ07oLbev5Ze193pYTY32+m2Gvsf+e6lln57lzn1 66pm5vWXsfki/AAbZhCs/o/TeNzX+36Vn5r3rnJP8Akoo4YxmZjc+H/RTb1X+Lf/AMUTf6hS S/xb/wDiib/UKSb/AOCP8FXR/9UH+Mj/AMUTv6gXKrqv8Y//AIonf1AuVWph/m4+Sw7qUqjU LGm1rn1z72sO1xHfa4h21yiknqfUfqv9WPq5mdCy34Vl9tHVGela66BZXsP0GQwN3Ms9y8/6 5T0bHzHY/SX33V0ktsvvIG5w9rvSraxm1rf5aOz62dYx6sOjBuOJRgD9FVXw53NlmRP896jj 9D6Czs/LObmXZbmNqdkPNj2M+iHO+ntn953uUOPHOM5GUiQdtf8ApJJQTCt4PTb87GzcmiCz p9Qut7yC7Zt/7+q9Vj6bWW1na+shzTzBHk5esfVjreBZ0XEt6sMXDyOoF1bGBraxcGksbYa4 /P8A+20c2SUACBdn+WigHyMOB4IPwUgQCCRuAOoOkjw0Wz9a+oZeV1a/GvprxWYljq68elga 0QY3ucA11jntWKpImwCRV+KH0/6idN+reZh35+Di2022MOJlV3PNjQHAOsbS930muXGfWrH6 Dg51nTuk49zH4zy2+66wukj8yqs/mf8ACOVEdb6jXg0YFFzsfHx3G0ColpdYTu9a17fc9/7i H1HqOT1LJ+15UOyHNa2ywCN5aNvqPH+k2/SUUMUhkMjImJ6X/iptqpJJKZD1X+Lf/wAUTf6h SS/xb/8Aiib/AFCkoP8AwR/gp6P/1tT63/VDrHWOsPysVjRUGhoLjysT/wAbf6xfus+9eYpK 9j9/gjw8NVot0fTv/G3+sX7rPvS/8bf6xfus+9eYpJ39I/qq0fTv/G3+sX7rPvS/8bf6xfus +9eYpJf0j+qrR9O/8bf6xfus+9Ss/wAXf1mtINm1+1oY3c6YaPosb/JXl6SX9I/qq0fULP8A F39ZrX77S17yAC5zpMAbW6lR/wDG3+sX7rPvXmKSX9I/qK0fTv8Axt/rF+6z70v/ABt/rF+6 z715ikl/SP6qtH07/wAbf6xfus+9L/xt/rF+6z715ikl/SP6qtH2n6ofVDrHR+sMyspjTUWl pLTwkvFklF+t979Hj4fpSdKf/9k= --------------CEE33E5E78D696CB4E0EC941-- --------------070C33C436192682FC31B74B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 13 7:18:43 2000 From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 13 07:18:42 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CFF0637B400; Wed, 13 Dec 2000 07:18:41 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id HAA20772; Wed, 13 Dec 2000 07:18:48 -0800 Date: Wed, 13 Dec 2000 07:18:41 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@FreeBSD.ORG Subject: Re: cvs commit: src/sys/isa isa_common.c In-Reply-To: <20001213021151.A75716@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You didn't answer my question about what you have in the PCI sloots, mook... On Wed, 13 Dec 2000, David O'Brien wrote: > On Wed, Dec 13, 2000 at 12:28:08AM -0800, Matthew Jacob wrote: > > I forgot to check this in into mcpcia.c: > > I updated sources around midnight, and built a new kernel. > I am now back to hanging at "Waiting 15 seconds for SCSI devices to > settle" -- so things are back to how they were before Mike's PCI changes. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 13 9:15: 4 2000 From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 13 09:15:02 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B8C3D37B400 for ; Wed, 13 Dec 2000 09:15:02 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA70880; Wed, 13 Dec 2000 09:15:02 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eBDHF1k77457; Wed, 13 Dec 2000 09:15:01 -0800 (PST) (envelope-from obrien) Date: Wed, 13 Dec 2000 09:15:00 -0800 From: "David O'Brien" To: Matthew Jacob Cc: alpha@FreeBSD.ORG Subject: Re: cvs commit: src/sys/isa isa_common.c Message-ID: <20001213091500.B77399@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20001213021151.A75716@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Wed, Dec 13, 2000 at 07:18:41AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: obrien@NUXI.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Dec 13, 2000 at 07:18:41AM -0800, Matthew Jacob wrote: > You didn't answer my question about what you have in the PCI sloots, mook... I sent you SRM `show dev' and `show conf' along with /var/run/dmesg.boot directly to you. :-) I don't have carnal knowledge of the insides of the BSDi 4100. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 13 10: 1: 8 2000 From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 13 10:01:07 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2FAE037B402; Wed, 13 Dec 2000 10:01:06 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA21268; Wed, 13 Dec 2000 10:01:12 -0800 Date: Wed, 13 Dec 2000 10:01:05 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@FreeBSD.ORG Subject: Re: cvs commit: src/sys/isa isa_common.c In-Reply-To: <20001213091500.B77399@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Did you? I didn't see it... On Wed, 13 Dec 2000, David O'Brien wrote: > On Wed, Dec 13, 2000 at 07:18:41AM -0800, Matthew Jacob wrote: > > You didn't answer my question about what you have in the PCI sloots, mook... > > I sent you SRM `show dev' and `show conf' along with /var/run/dmesg.boot > directly to you. :-) I don't have carnal knowledge of the insides of > the BSDi 4100. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 13 10: 6:58 2000 From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 13 10:06:57 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DD31437B400; Wed, 13 Dec 2000 10:06:55 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA21301; Wed, 13 Dec 2000 10:07:02 -0800 Date: Wed, 13 Dec 2000 10:06:55 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@FreeBSD.ORG Subject: Re: cvs commit: src/sys/isa isa_common.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry, got it.... One theory shot down. On Wed, 13 Dec 2000, Matthew Jacob wrote: > You didn't answer my question about what you have in the PCI sloots, mook... > > > On Wed, 13 Dec 2000, David O'Brien wrote: > > > On Wed, Dec 13, 2000 at 12:28:08AM -0800, Matthew Jacob wrote: > > > I forgot to check this in into mcpcia.c: > > > > I updated sources around midnight, and built a new kernel. > > I am now back to hanging at "Waiting 15 seconds for SCSI devices to > > settle" -- so things are back to how they were before Mike's PCI changes. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-alpha" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 10:34:31 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 10:34:29 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 34A9C37B400; Thu, 14 Dec 2000 10:34:28 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA26057; Thu, 14 Dec 2000 10:34:35 -0800 Date: Thu, 14 Dec 2000 10:34:27 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: mutex/ithread jitters? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Since I (and maybe only I :-)) have gotten a 4100 up and running, I've been experiencing the following two behaviours: Periodic messages like: (da1:isp0:0:3:0): isp0: watchdog timeout (cf, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (21, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (9, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (65, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (c8, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (6e, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (1a, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (2, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (ee, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (cb, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (d4, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (d6, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (c8, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (89, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (56, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (19, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (ec, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (91, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (e0, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (50, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (77, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (5b, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (5, 0) (da1:isp0:0:3:0): isp0: watchdog timeout (c3, 0) and 'freezes' while rlogin'd in. Has anyone else seen anything like this? The former, which really shouldn't happen at all at all (and doesn't under 4.2 in the same framework) indicates a completely lost interrupt. The latter I'm not sure about, but it could be the same. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 11: 4:37 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 11:04:34 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 6E62737B400 for ; Thu, 14 Dec 2000 11:04:34 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBEJ4OE80187; Thu, 14 Dec 2000 11:04:24 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.0) id eBEJ3a040023; Thu, 14 Dec 2000 11:03:36 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 14 Dec 2000 11:03:36 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Matthew Jacob Subject: RE: mutex/ithread jitters? Cc: alpha@FreeBSD.ORG Sender: jhb@foo.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 14-Dec-00 Matthew Jacob wrote: > > Since I (and maybe only I :-)) have gotten a 4100 up and running, I've been > experiencing the following two behaviours: > > Periodic messages like: > > (da1:isp0:0:3:0): isp0: watchdog timeout (cf, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (21, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (9, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (65, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (c8, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (6e, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (1a, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (2, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (ee, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (cb, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (d4, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (d6, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (c8, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (89, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (56, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (19, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (ec, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (91, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (e0, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (50, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (77, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (5b, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (5, 0) > (da1:isp0:0:3:0): isp0: watchdog timeout (c3, 0) > > > and > > 'freezes' while rlogin'd in. > > > Has anyone else seen anything like this? The former, which really shouldn't > happen at all at all (and doesn't under 4.2 in the same framework) indicates > a > completely lost interrupt. The latter I'm not sure about, but it could be the > same. Sounds like lost interrupts. Possibly the interrupt isn't being enabled properly after the ithread finishes running the handler. > -matt -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 11:11:49 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 11:11:48 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3D7D037B400; Thu, 14 Dec 2000 11:11:47 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA09034; Thu, 14 Dec 2000 14:11:34 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eBEJBYv41269; Thu, 14 Dec 2000 14:11:34 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 14 Dec 2000 14:11:33 -0500 (EST) To: John Baldwin Cc: Matthew Jacob , alpha@FreeBSD.ORG Subject: RE: mutex/ithread jitters? In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14905.6815.2347.450995@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > Sounds like lost interrupts. Possibly the interrupt isn't being enabled > properly after the ithread finishes running the handler. Maybe it is time to accept defeat on squelching interrupts at their source and leave the IPL raised until the handler is run? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 11:13:28 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 11:13:27 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D98E437B400; Thu, 14 Dec 2000 11:13:26 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA26272; Thu, 14 Dec 2000 11:13:26 -0800 Date: Thu, 14 Dec 2000 11:13:19 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: John Baldwin , alpha@FreeBSD.ORG Subject: RE: mutex/ithread jitters? In-Reply-To: <14905.6815.2347.450995@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > John Baldwin writes: > > > > Sounds like lost interrupts. Possibly the interrupt isn't being enabled > > properly after the ithread finishes running the handler. > > Maybe it is time to accept defeat on squelching interrupts at their source > and leave the IPL raised until the handler is run? They may be orthogonal issues. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 11:21:55 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 11:21:53 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 50F1F37B400; Thu, 14 Dec 2000 11:21:52 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA09252; Thu, 14 Dec 2000 14:21:51 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eBEJLp141299; Thu, 14 Dec 2000 14:21:51 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 14 Dec 2000 14:21:50 -0500 (EST) To: mjacob@feral.com Cc: John Baldwin , alpha@FreeBSD.ORG Subject: RE: mutex/ithread jitters? In-Reply-To: References: <14905.6815.2347.450995@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14905.7357.440285.591097@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > > > John Baldwin writes: > > > > > > Sounds like lost interrupts. Possibly the interrupt isn't being enabled > > > properly after the ithread finishes running the handler. > > > > Maybe it is time to accept defeat on squelching interrupts at their source > > and leave the IPL raised until the handler is run? > > They may be orthogonal issues. Maybe, but maybe not. Your 4100's missing interrupts sound similar to the missing isa interrupt problems on my UP1000. As Doug mentioned before, leaving the ipl raised would probably be more efficient that groveling around in the interrupt hardware. And it would be nice to not make every platform have to be 100% perfect wrt to enabling/disabling interrupts... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 11:25: 3 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 11:25:01 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0458F37B400; Thu, 14 Dec 2000 11:24:56 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA26347; Thu, 14 Dec 2000 11:24:57 -0800 Date: Thu, 14 Dec 2000 11:24:50 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: John Baldwin , alpha@FreeBSD.ORG Subject: RE: mutex/ithread jitters? In-Reply-To: <14905.7357.440285.591097@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Matthew Jacob writes: > > > > > > John Baldwin writes: > > > > > > > > Sounds like lost interrupts. Possibly the interrupt isn't being enabled > > > > properly after the ithread finishes running the handler. > > > > > > Maybe it is time to accept defeat on squelching interrupts at their source > > > and leave the IPL raised until the handler is run? > > > > They may be orthogonal issues. > > Maybe, but maybe not. Your 4100's missing interrupts sound similar to > the missing isa interrupt problems on my UP1000. > > As Doug mentioned before, leaving the ipl raised would probably be > more efficient that groveling around in the interrupt hardware. And > it would be nice to not make every platform have to be 100% perfect > wrt to enabling/disabling interrupts... No arguments from me on this one (after all, ahem, I suggested it first!). But I haven't gotten around to breaking free the day or so it will take to do this. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 12:30:58 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 12:30:55 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 3D55B37B400; Thu, 14 Dec 2000 12:30:51 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id eBEKUS219165 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Thu, 14 Dec 2000 21:30:30 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eBEKUim22960 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Thu, 14 Dec 2000 21:30:50 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id eBEKUiZ60468; Thu, 14 Dec 2000 21:30:44 +0100 (CET) (envelope-from ticso) Date: Thu, 14 Dec 2000 21:30:44 +0100 From: Bernd Walter To: Matthew Jacob Cc: Andrew Gallatin , John Baldwin , alpha@FreeBSD.ORG Subject: Re: mutex/ithread jitters? Message-ID: <20001214213044.A60434@cicely5.cicely.de> References: <14905.7357.440285.591097@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mjacob@feral.com on Thu, Dec 14, 2000 at 11:24:50AM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Dec 14, 2000 at 11:24:50AM -0800, Matthew Jacob wrote: > > As Doug mentioned before, leaving the ipl raised would probably be > > more efficient that groveling around in the interrupt hardware. And > > it would be nice to not make every platform have to be 100% perfect > > wrt to enabling/disabling interrupts... > > No arguments from me on this one (after all, ahem, I suggested it first!). But > I haven't gotten around to breaking free the day or so it will take to do > this. The workaround for the PC164 brokeness should also work on other EV56 and up alphas. The only unclear thing is if the SRM of that machine supports the needed functionality to get access to the pal privileged commands. I asume it's worth to test as it's simple to bring in. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 12:51:11 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 12:51:08 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A741D37B400 for ; Thu, 14 Dec 2000 12:51:08 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA79127; Thu, 14 Dec 2000 12:51:07 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eBEKp6X09128; Thu, 14 Dec 2000 12:51:06 -0800 (PST) (envelope-from obrien) Date: Thu, 14 Dec 2000 12:51:05 -0800 From: "David O'Brien" To: Matthew Jacob , alpha@FreeBSD.ORG Subject: Re: mutex/ithread jitters? Message-ID: <20001214125105.A9048@dragon.nuxi.com> Reply-To: alpha@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Thu, Dec 14, 2000 at 11:03:36AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: obrien@NUXI.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Dec 14, 2000 at 11:03:36AM -0800, John Baldwin wrote: > > > > Since I (and maybe only I :-)) have gotten a 4100 up and running, I've been > > experiencing the following two behaviours: ... > Sounds like lost interrupts. Possibly the interrupt isn't being enabled > properly after the ithread finishes running the handler. This is probably the problem with my AS4100 -- it hangs in probing the SCSI chain -- just like the PC164's did. My guess is there is something in your 4100 that helps get off an interrupt at a key moment. Does anybody know if DFR's 4100 can run -current? -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 12:53: 8 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 12:53:06 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5670837B400 for ; Thu, 14 Dec 2000 12:53:06 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA26709; Thu, 14 Dec 2000 12:53:09 -0800 Date: Thu, 14 Dec 2000 12:53:01 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@FreeBSD.ORG Subject: Re: mutex/ithread jitters? In-Reply-To: <20001214125105.A9048@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Thu, Dec 14, 2000 at 11:03:36AM -0800, John Baldwin wrote: > > > > > > Since I (and maybe only I :-)) have gotten a 4100 up and running, I've been > > > experiencing the following two behaviours: > ... > > Sounds like lost interrupts. Possibly the interrupt isn't being enabled > > properly after the ithread finishes running the handler. > > This is probably the problem with my AS4100 -- it hangs in probing the > SCSI chain -- just like the PC164's did. My guess is there is something > in your 4100 that helps get off an interrupt at a key moment. Possibly. It also might explain why having multiple Qlogic's causes things to freeze as well. > Does anybody know if DFR's 4100 can run -current? Only doug can say. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 13: 6:27 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 13:06:26 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D40F237B400; Thu, 14 Dec 2000 13:06:25 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA26748; Thu, 14 Dec 2000 13:06:19 -0800 Date: Thu, 14 Dec 2000 13:06:12 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Bernd Walter Cc: Andrew Gallatin , John Baldwin , alpha@FreeBSD.ORG Subject: Re: mutex/ithread jitters? In-Reply-To: <20001214213044.A60434@cicely5.cicely.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 14 Dec 2000, Bernd Walter wrote: > On Thu, Dec 14, 2000 at 11:24:50AM -0800, Matthew Jacob wrote: > > > As Doug mentioned before, leaving the ipl raised would probably be > > > more efficient that groveling around in the interrupt hardware. And > > > it would be nice to not make every platform have to be 100% perfect > > > wrt to enabling/disabling interrupts... > > > > No arguments from me on this one (after all, ahem, I suggested it first!). But > > I haven't gotten around to breaking free the day or so it will take to do > > this. > > The workaround for the PC164 brokeness should also work on other EV56 and up > alphas. > The only unclear thing is if the SRM of that machine supports the needed > functionality to get access to the pal privileged commands. > I asume it's worth to test as it's simple to bring in. We could, but the fact of the matter here is that CSERVE is an undocumented PAL opcode reserved to Digital (sez the Sites book). I'm really glad you've added it so the PC164 now works again, but I don't want to grow this approach further. There are probably a bunch of other approaches we should take that keep us within the Alpha public architecture that would be better for us to do. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 14:29:54 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 14:29:52 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from front3.grolier.fr (front3.grolier.fr [194.158.96.53]) by hub.freebsd.org (Postfix) with ESMTP id 3BF4337B402; Thu, 14 Dec 2000 14:29:51 -0800 (PST) Received: from nas1-152.cgy.club-internet.fr (nas1-152.cgy.club-internet.fr [195.36.197.152]) by front3.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA11787; Thu, 14 Dec 2000 23:29:43 +0100 (MET) Date: Thu, 14 Dec 2000 22:29:38 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Andrew Gallatin Cc: John Baldwin , Matthew Jacob , alpha@FreeBSD.ORG Subject: RE: mutex/ithread jitters? In-Reply-To: <14905.6815.2347.450995@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 14 Dec 2000, Andrew Gallatin wrote: > John Baldwin writes: > >=20 > > Sounds like lost interrupts. Possibly the interrupt isn't being enabl= ed > > properly after the ithread finishes running the handler. >=20 > Maybe it is time to accept defeat on squelching interrupts at their sourc= e=20 > and leave the IPL raised until the handler is run? I am not an arch. guy and I will be fixed by jhb for sure :). Thanks by advance Jhon for teaching me. :) My understanding is that Alpha is actually IPL based and masking using actual level will kill most advantages if threading interrupts, at least for level sensitive. My probably false understanding let me think that result will be increase of interrupt latency without any gain in anything by threading interrupt handlers. On IA32, we can mask at IO APIC level and EOI in advance, but this looks like odd tinking to me and may-be will just fight with IO APIC optimizations that assume some behaviour of the CPU in optimization heuristics. Anyway tampering the IO APIC may well be slow. (?) Always regarding level-sensitive interrupts, I happen to dream of implementing interrupt handling in 2 separates handlers. - A fast half handler that runs in the "expected by hardware" interrupt context and that gets device status information, clears the device interrupt condition, passes the info to he other half handler.=20 - the other handler may be ithread if it is not fast enough or may=20 contend too much on other resources. (This is not original, indeed :-) ) I read Solaris does thread interrupt handlers. Could it be that Sparc hardware has been specifically tailored for this not to have adverse effects ? G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 14:46:39 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 14:46:36 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 492D337B402; Thu, 14 Dec 2000 14:46:36 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA27091; Thu, 14 Dec 2000 14:45:58 -0800 Date: Thu, 14 Dec 2000 14:45:51 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: Andrew Gallatin , John Baldwin , alpha@FreeBSD.ORG Subject: RE: mutex/ithread jitters? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > My understanding is that Alpha is actually IPL based and masking using > actual level will kill most advantages if threading interrupts, at least > for level sensitive. My probably false understanding let me think that > result will be increase of interrupt latency without any gain in anything > by threading interrupt handlers. > > On IA32, we can mask at IO APIC level and EOI in advance, but this looks > like odd tinking to me and may-be will just fight with IO APIC > optimizations that assume some behaviour of the CPU in optimization > heuristics. Anyway tampering the IO APIC may well be slow. (?) The problem, in sum, is that the FreeBSD ithread architecture assumes you can quiesce level sensitive ints (without getting to the the driver for that h/w) so that you can continue to run and schedule ithreads until you get to the driver that will deal with the interrupt for that interrupting device. The problem here is that it's not always clear that you can safely quiesce interrupts this way. It's fairly clear with an IO-APIC. It's been a bit of an edge case in how we deal with the Alpha. One *should* be able to do so, but we've been having problems with it. > > Always regarding level-sensitive interrupts, I happen to dream of > implementing interrupt handling in 2 separates handlers. > > - A fast half handler that runs in the "expected by hardware" interrupt > context and that gets device status information, clears the device > interrupt condition, passes the info to he other half handler. > > - the other handler may be ithread if it is not fast enough or may > contend too much on other resources. > > (This is not original, indeed :-) ) > > I read Solaris does thread interrupt handlers. Could it be that Sparc > hardware has been specifically tailored for this not to have adverse > effects ? No. They also run the threads at h/w interrupt priority. First of all, you can't do any kind of non-spin locking (or much of *anything*) above IPL 10- the clock and the uarts and audio actually come in above IPL 10 (that's why the zs && audioamd drivers are multi-level interrupt drivers). Secondly, there are explicit warnings about attempting do some things in interrupt context. That is, you *can* do things like cv_wait, but you get warnings in section 9 man pages, e.g. (from condvar(9f)): If cv_wait(), cv_timedwait(), cv_wait_sig(), or cv_timedwait_sig() are used from interrupt context, lower- priority interrupts will not be serviced during the wait. This means that if the thread that will eventually perform the wakeup becomes blocked on anything that requires the lower-priority interrupt, the system will hang. For example, the thread that will perform the wakeup may need to first allocate memory. This memory allocation may require waiting for paging I/O to complete, which may require a lower-priority disk or network interrupt to be serviced. In general, situations like this are hard to predict, so it is advisable to avoid waiting on condition variables or semaphores in an interrupt context. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 17:47: 0 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 17:46:59 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from nwcst330.netaddress.usa.net (nwcst330.netaddress.usa.net [204.68.23.75]) by hub.freebsd.org (Postfix) with SMTP id B763637B698 for ; Thu, 14 Dec 2000 17:46:58 -0800 (PST) Received: (qmail 19466 invoked by uid 60001); 15 Dec 2000 01:46:58 -0000 Message-ID: <20001215014658.19465.qmail@nwcst330.netaddress.usa.net> Received: from 204.68.23.75 by nwcst330 for [213.97.104.111] via web-mailer(34FM.0700.4B.01) on Fri Dec 15 01:46:58 GMT 2000 Date: 15 Dec 00 02:46:58 MET From: alain hache To: wilko@freebsd.org Subject: Help Cc: freebsd-alpha@freebsd.org X-Mailer: USANET web-mailer (34FM.0700.4B.01) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Sorry to disturb you, but as I saw you recently installed FreeBSD on an a= lpha 200 4/233... I have problems finding the software tools to convert my machine alpha 20= 0 4/233 from the ARC system to the SRM system. precise model is PB42A DB = Any idea on where to find the appropriate soft (download or find CD) Thanks for your help. Regards Alain Hache ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=3D= 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 14 18:53:11 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 18:53:09 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from virtual.valuelinx.net (virtual.valuelinx.net [208.189.209.17]) by hub.freebsd.org (Postfix) with ESMTP id 7770737B400 for ; Thu, 14 Dec 2000 18:53:08 -0800 (PST) Received: from penix.org (Toronto-ppp221370.sympatico.ca [64.228.106.187]) by virtual.valuelinx.net (8.9.1/8.9.1) with SMTP id CAA03393; Fri, 15 Dec 2000 02:53:02 GMT Sender: root@virtual.valuelinx.net Message-ID: <3A394178.547724F7@penix.org> Date: Thu, 14 Dec 2000 21:54:00 +0000 From: "[ -dp- ]" X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: alain hache Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Help References: <20001215014658.19465.qmail@nwcst330.netaddress.usa.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org alain hache wrote: > > Hi, > > Sorry to disturb you, but as I saw you recently installed FreeBSD on an alpha > 200 4/233... > > I have problems finding the software tools to convert my machine alpha 200 > 4/233 from the ARC system to the SRM system. > > precise model is PB42A DB > > Any idea on where to find the appropriate soft (download or find CD) This is the location of the firmware updates: ftp://ftp.digital.com/pub/Digital/Alpha/firmware/index.html Good Luck. > Thanks for your help. No problemo > > Regards > > Alain Hache > > ____________________________________________________________________ > Get free email and a permanent address at http://www.netaddress.com/?N=1 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message -- Paul H. ============================================================================ Don't underestimate the power of stupid people in large groups. Brute force is the last resort of the incompetent. Email: dp@penix.org BIO: http://www3.sympatico.ca/transmogrify GPG Key fingerprint: 2D7C A7E2 DB1F EA5F 8C6F D5EC 3D39 F274 4AA3 E8B9 Public Key available here: http://www3.sympatico.ca/transmogrify/dp.txt ============================================================================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 2:45:48 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 02:45:46 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id B9F6637B400 for ; Fri, 15 Dec 2000 02:45:45 -0800 (PST) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 146sMx-0009kj-0A; Fri, 15 Dec 2000 10:45:44 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA96839; Fri, 15 Dec 2000 10:45:23 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 15 Dec 2000 10:45:23 +0000 (GMT) From: Doug Rabson To: alpha@freebsd.org Cc: Matthew Jacob Subject: Re: mutex/ithread jitters? In-Reply-To: <20001214125105.A9048@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 14 Dec 2000, David O'Brien wrote: > On Thu, Dec 14, 2000 at 11:03:36AM -0800, John Baldwin wrote: > > > > > > Since I (and maybe only I :-)) have gotten a 4100 up and running, I've been > > > experiencing the following two behaviours: > ... > > Sounds like lost interrupts. Possibly the interrupt isn't being enabled > > properly after the ithread finishes running the handler. > > This is probably the problem with my AS4100 -- it hangs in probing the > SCSI chain -- just like the PC164's did. My guess is there is something > in your 4100 that helps get off an interrupt at a key moment. > > Does anybody know if DFR's 4100 can run -current? I haven't had time to test it since Matt's last set of fixes. I'll probably have a chance to look at it this weekend. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 5:16:24 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 05:16:22 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from iservern.teligent.se (mail.teligent.se [194.17.198.3]) by hub.freebsd.org (Postfix) with ESMTP id E476D37B400 for ; Fri, 15 Dec 2000 05:16:21 -0800 (PST) Received: from blackice (dyn-office-123.teligent.se [172.18.0.123]) by iservern.teligent.se (8.11.1/8.11.1) with SMTP id eBFDGHR06003 for ; Fri, 15 Dec 2000 14:16:17 +0100 (CET) (envelope-from wille@teligent.se) Reply-To: From: "William Carlsson - Teligent Nordic, AB - Sweden" To: Subject: FreeBSD on a HP9000/E45 ? Date: Fri, 15 Dec 2000 14:16:08 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Anyone who knows if it's possible to run any FreeBSD on a HP 9000/E45 ? Any one who has one running it? ---------------------------------------------------- William Carlsson Second Line Support Teligent Nordic AB P.O. Box 213 S-149 21 Nynäshamn SWEDEN Telephone: +46 - 8 - 59 99 11 92 eMail: william.carlsson@teligent.se http://www.teligent.se ---------------------------------------------------- "And then it comes to be that the soothing light at the end of your tunnel was just a freight train, comin' your way." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 5:19:47 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 05:19:46 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id BC36737B400 for ; Fri, 15 Dec 2000 05:19:45 -0800 (PST) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JXQIMF14WY00160O@research.kpn.com> for freebsd-alpha@FreeBSD.ORG; Fri, 15 Dec 2000 14:19:40 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Fri, 15 Dec 2000 14:19:39 +0100 Content-return: allowed Date: Fri, 15 Dec 2000 14:19:39 +0100 From: "Koster, K.J." Subject: RE: FreeBSD on a HP9000/E45 ? To: "'william.carlsson@teligent.se'" Cc: freebsd-alpha@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7AB7@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear William, > > Anyone who knows if it's possible to run any FreeBSD on a HP > 9000/E45 ? > > Any one who has one running it? > I think only OpenBSD has HP9000 support at the moment. Have a look at http://www.openbsd.org/hppa.html The page speaks of "will work eventually", so don't get all chuffed just yet. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 10:34:33 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 10:34:31 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 7177737B400 for ; Fri, 15 Dec 2000 10:34:30 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id eBFIYR207239 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Fri, 15 Dec 2000 19:34:29 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eBFIYmm26127 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO) for ; Fri, 15 Dec 2000 19:34:50 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id eBFIYhl62106 for freebsd-alpha@freebsd.org; Fri, 15 Dec 2000 19:34:43 +0100 (CET) (envelope-from ticso) Date: Fri, 15 Dec 2000 19:34:43 +0100 From: Bernd Walter To: freebsd-alpha@freebsd.org Subject: mb and wmb in atomic_ Message-ID: <20001215193443.B62048@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Why are the mb and wmb operations needed in the atomic_ functions? If I understood it correctly the locked operations are in synced with others CPUs and there is no memory operation beside the variable itself. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 10:42:46 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 10:42:45 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D089537B402 for ; Fri, 15 Dec 2000 10:42:44 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA30652; Fri, 15 Dec 2000 10:42:49 -0800 Date: Fri, 15 Dec 2000 10:42:41 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Bernd Walter Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: mb and wmb in atomic_ In-Reply-To: <20001215193443.B62048@cicely5.cicely.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I agree that they need not be there. Others do not. > Why are the mb and wmb operations needed in the atomic_ functions? > If I understood it correctly the locked operations are in synced > with others CPUs and there is no memory operation beside the variable > itself. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 11:36: 0 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 11:35:59 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9518037B6A0 for ; Fri, 15 Dec 2000 11:35:54 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBFJZVE24862; Fri, 15 Dec 2000 11:35:31 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001215193443.B62048@cicely5.cicely.de> Date: Fri, 15 Dec 2000 11:35:47 -0800 (PST) From: John Baldwin To: Bernd Walter Subject: RE: mb and wmb in atomic_ Cc: freebsd-alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15-Dec-00 Bernd Walter wrote: > Why are the mb and wmb operations needed in the atomic_ functions? > If I understood it correctly the locked operations are in synced > with others CPUs and there is no memory operation beside the variable > itself. They should probably only be used with the 'acq' and 'rel' variants. Hmm, btw, it looks like I have the order of the barriers in the 'acq' and 'rel' variants wrong. The barriers should be on the inside, not the outside. Anyone disagree? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 12: 1:41 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 12:01:39 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id B65F937B400; Fri, 15 Dec 2000 12:01:36 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id eBFK1Th16278 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Fri, 15 Dec 2000 21:01:32 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eBFK1jm26328 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Fri, 15 Dec 2000 21:01:52 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id eBFK1aF62196; Fri, 15 Dec 2000 21:01:36 +0100 (CET) (envelope-from ticso) Date: Fri, 15 Dec 2000 21:01:36 +0100 From: Bernd Walter To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: Andrew Gallatin , John Baldwin , Matthew Jacob , alpha@FreeBSD.ORG Subject: Re: mutex/ithread jitters? Message-ID: <20001215210136.C62048@cicely5.cicely.de> References: <14905.6815.2347.450995@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: ; from groudier@club-internet.fr on Thu, Dec 14, 2000 at 10:29:38PM +0100 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Dec 14, 2000 at 10:29:38PM +0100, Gérard Roudier wrote: > > > On Thu, 14 Dec 2000, Andrew Gallatin wrote: > > > John Baldwin writes: > > > > > > Sounds like lost interrupts. Possibly the interrupt isn't being enabled > > > properly after the ithread finishes running the handler. > > > > Maybe it is time to accept defeat on squelching interrupts at their source > > and leave the IPL raised until the handler is run? > > I am not an arch. guy and I will be fixed by jhb for sure :). Thanks by > advance Jhon for teaching me. :) > > My understanding is that Alpha is actually IPL based and masking using > actual level will kill most advantages if threading interrupts, at least > for level sensitive. My probably false understanding let me think that > result will be increase of interrupt latency without any gain in anything > by threading interrupt handlers. In my understanding the reason for implementing ithread was not to get a better response time but it is neccessary to make use of mutexes for interupt processing. Maybe it's better schedule an ithread only if we need to block which should be unlikely if designed properly and keep IPL raised if sensefull for the platform. But I'm far away from being capable of implementing this. Anyway - if the 4100 has a similar behavour as the PC164 had I'm more willing to believe that the PC164 is in reality not broken. I fact my PC164 masked ints fine several times until it stoped which sounds similar to what is being said for the 4100. Another point is that there are lots of MBs in tsunami_intr_enable/disable especialy the dups are questionable - what's the reason not trusting a single one? But I can't see where writing to hardware is enshured - are the registers marked non-cacheable - but then why an mb? I asume 4100 is tsunami based as I can't find any reference in alpha/dec_kn300.c for defining of platform.intr_disable/enable. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 12:19:19 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 12:19:17 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id D816B37B400; Fri, 15 Dec 2000 12:19:16 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id eBFKJDh18081 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Fri, 15 Dec 2000 21:19:15 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eBFKJUm26388 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Fri, 15 Dec 2000 21:19:36 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id eBFKJUL62222; Fri, 15 Dec 2000 21:19:30 +0100 (CET) (envelope-from ticso) Date: Fri, 15 Dec 2000 21:19:30 +0100 From: Bernd Walter To: John Baldwin Cc: freebsd-alpha@FreeBSD.org Subject: Re: mb and wmb in atomic_ Message-ID: <20001215211930.D62048@cicely5.cicely.de> References: <20001215193443.B62048@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jhb@FreeBSD.org on Fri, Dec 15, 2000 at 11:35:47AM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Dec 15, 2000 at 11:35:47AM -0800, John Baldwin wrote: > > On 15-Dec-00 Bernd Walter wrote: > > Why are the mb and wmb operations needed in the atomic_ functions? > > If I understood it correctly the locked operations are in synced > > with others CPUs and there is no memory operation beside the variable > > itself. > > They should probably only be used with the 'acq' and 'rel' variants. Hmm, btw, > it looks like I have the order of the barriers in the 'acq' and 'rel' variants > wrong. The barriers should be on the inside, not the outside. Anyone disagree? Depending on atomic(9) I agree. I don't asume the acq variant realy needs one as the locked operation should be finished at once at least out of the CPUs thus no post operation has the chance to make anything before. Do we have the situation anywhere that the bus reorders memory access? Do we care about this? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 13:10:59 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 13:10:56 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from front6m.grolier.fr (front6m.grolier.fr [195.36.216.56]) by hub.freebsd.org (Postfix) with ESMTP id 1EE1037B400; Fri, 15 Dec 2000 13:10:55 -0800 (PST) Received: from nas1-12.mea.club-internet.fr (nas1-12.mea.club-internet.fr [195.36.139.12]) by front6m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA25927; Fri, 15 Dec 2000 22:10:45 +0100 (MET) Date: Fri, 15 Dec 2000 21:10:39 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Bernd Walter Cc: Andrew Gallatin , John Baldwin , Matthew Jacob , alpha@FreeBSD.ORG Subject: Re: mutex/ithread jitters? In-Reply-To: <20001215210136.C62048@cicely5.cicely.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 15 Dec 2000, Bernd Walter wrote: > On Thu, Dec 14, 2000 at 10:29:38PM +0100, G=E9rard Roudier wrote: > >=20 > >=20 > > On Thu, 14 Dec 2000, Andrew Gallatin wrote: > >=20 > > > John Baldwin writes: > > > >=20 > > > > Sounds like lost interrupts. Possibly the interrupt isn't being e= nabled > > > > properly after the ithread finishes running the handler. > > >=20 > > > Maybe it is time to accept defeat on squelching interrupts at their s= ource=20 > > > and leave the IPL raised until the handler is run? > >=20 > > I am not an arch. guy and I will be fixed by jhb for sure :). Thanks by > > advance Jhon for teaching me. :) > >=20 > > My understanding is that Alpha is actually IPL based and masking using > > actual level will kill most advantages if threading interrupts, at leas= t > > for level sensitive. My probably false understanding let me think that > > result will be increase of interrupt latency without any gain in anythi= ng > > by threading interrupt handlers. >=20 > In my understanding the reason for implementing ithread was not to get > a better response time but it is neccessary to make use of mutexes for > interupt processing. Using mutexes instead or spinlocks is probably some means for the goal of scaling up better on mult' CPUs SMP machines. I am just afraid that such an hypothetical better scaling up for 0.0...01% machines may poorly scale down to 99,9999...% of usual machines. I just hope I am plain wrong on this point. > Maybe it's better schedule an ithread only if we need to block which > should be unlikely if designed properly and keep IPL raised if > sensefull for the platform. >=20 > But I'm far away from being capable of implementing this. There is nothing complex here, at least in theory. Semaphores with P and V primitives have been invented about 25+ years ago or more by Mr Djiskra (or some name like this) IIRC, and I remember using similar primitives 20 years ago. But the original UNIX kernel, invented on some PDP 6 or 7 machine, probably started with the `=E0 la DEC' spl/ipl synchronisation way, that only makes relevance on single processor machine in my opinion. > Anyway - if the 4100 has a similar behavour as the PC164 had I'm > more willing to believe that the PC164 is in reality not broken. > I fact my PC164 masked ints fine several times until it stoped which > sounds similar to what is being said for the 4100. >=20 > Another point is that there are lots of MBs in tsunami_intr_enable/disabl= e > especialy the dups are questionable - what's the reason not trusting a > single one? Several may be needed. Will have a look at this when I will have time for. Btw, I donnot seem to see interrupt disable/enable things in the official UNIX PAL code (Btw, the NT one has such verbs). Looks like a not regular use of Alpha hardware, and we probably must be very careful when doing so. > But I can't see where writing to hardware is enshured - are the registers > marked non-cacheable - but then why an mb? Alpha does not guarantee any implicit barrier. Programmer is required to insert all appropriate barriers. Cachable or not cachable does not matter. > I asume 4100 is tsunami based as I can't find any reference in > alpha/dec_kn300.c for defining of platform.intr_disable/enable. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 13:20:37 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 13:20:36 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 6846C37B6B1 for ; Fri, 15 Dec 2000 13:19:31 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBFLJ7E28513; Fri, 15 Dec 2000 13:19:07 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001215211930.D62048@cicely5.cicely.de> Date: Fri, 15 Dec 2000 13:19:25 -0800 (PST) From: John Baldwin To: Bernd Walter Subject: Re: mb and wmb in atomic_ Cc: freebsd-alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15-Dec-00 Bernd Walter wrote: > On Fri, Dec 15, 2000 at 11:35:47AM -0800, John Baldwin wrote: >> >> On 15-Dec-00 Bernd Walter wrote: >> > Why are the mb and wmb operations needed in the atomic_ functions? >> > If I understood it correctly the locked operations are in synced >> > with others CPUs and there is no memory operation beside the variable >> > itself. >> >> They should probably only be used with the 'acq' and 'rel' variants. Hmm, >> btw, >> it looks like I have the order of the barriers in the 'acq' and 'rel' >> variants >> wrong. The barriers should be on the inside, not the outside. Anyone >> disagree? > > Depending on atomic(9) I agree. > I don't asume the acq variant realy needs one as the locked operation > should be finished at once at least out of the CPUs thus no post operation > has the chance to make anything before. > Do we have the situation anywhere that the bus reorders memory access? > Do we care about this? Can the CPU perform out-of-order execution though? And out-of-order memory accesses as a result? That is what memory barriers really protect you against. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 13:20:41 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 13:20:35 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id CF4BD37B6AE for ; Fri, 15 Dec 2000 13:19:29 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBFLJ6E28509; Fri, 15 Dec 2000 13:19:06 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001215210136.C62048@cicely5.cicely.de> Date: Fri, 15 Dec 2000 13:19:24 -0800 (PST) From: John Baldwin To: Bernd Walter Subject: Re: mutex/ithread jitters? Cc: alpha@FreeBSD.org, Matthew Jacob , Andrew Gallatin , =?iso-8859-1?Q?G=E9rard_Roudier?= Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15-Dec-00 Bernd Walter wrote: > On Thu, Dec 14, 2000 at 10:29:38PM +0100, Gérard Roudier wrote: >> >> >> On Thu, 14 Dec 2000, Andrew Gallatin wrote: >> >> > John Baldwin writes: >> > > >> > > Sounds like lost interrupts. Possibly the interrupt isn't being >> > > enabled >> > > properly after the ithread finishes running the handler. >> > >> > Maybe it is time to accept defeat on squelching interrupts at their source >> > and leave the IPL raised until the handler is run? >> >> I am not an arch. guy and I will be fixed by jhb for sure :). Thanks by >> advance Jhon for teaching me. :) >> >> My understanding is that Alpha is actually IPL based and masking using >> actual level will kill most advantages if threading interrupts, at least >> for level sensitive. My probably false understanding let me think that >> result will be increase of interrupt latency without any gain in anything >> by threading interrupt handlers. > > In my understanding the reason for implementing ithread was not to get > a better response time but it is neccessary to make use of mutexes for > interupt processing. > Maybe it's better schedule an ithread only if we need to block which > should be unlikely if designed properly and keep IPL raised if > sensefull for the platform. This is sort of what light weight context switches for ithreads will do. > But I'm far away from being capable of implementing this. > > Anyway - if the 4100 has a similar behavour as the PC164 had I'm > more willing to believe that the PC164 is in reality not broken. > I fact my PC164 masked ints fine several times until it stoped which > sounds similar to what is being said for the 4100. > > Another point is that there are lots of MBs in tsunami_intr_enable/disable > especialy the dups are questionable - what's the reason not trusting a > single one? > But I can't see where writing to hardware is enshured - are the registers > marked non-cacheable - but then why an mb? > I asume 4100 is tsunami based as I can't find any reference in > alpha/dec_kn300.c for defining of platform.intr_disable/enable. Good question. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 13:20:45 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 13:20:42 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D618D37B6CC for ; Fri, 15 Dec 2000 13:20:30 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA31251; Fri, 15 Dec 2000 13:20:33 -0800 Date: Fri, 15 Dec 2000 13:20:26 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Bernd Walter Cc: alpha@FreeBSD.org, Andrew Gallatin , =?iso-8859-1?Q?G=E9rard_Roudier?= Subject: Re: mutex/ithread jitters? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > But I can't see where writing to hardware is enshured - are the registers > > marked non-cacheable - but then why an mb? > > I asume 4100 is tsunami based as I can't find any reference in > > alpha/dec_kn300.c for defining of platform.intr_disable/enable. No, it's not tsunami based. See mcbus. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 14:22:15 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 14:22:13 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from front4m.grolier.fr (front4m.grolier.fr [195.36.216.54]) by hub.freebsd.org (Postfix) with ESMTP id 0376637B400; Fri, 15 Dec 2000 14:22:12 -0800 (PST) Received: from nas1-109.cgy.club-internet.fr (nas1-109.cgy.club-internet.fr [195.36.197.109]) by front4m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA00177; Fri, 15 Dec 2000 23:19:49 +0100 (MET) Date: Fri, 15 Dec 2000 22:22:00 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: John Baldwin Cc: Bernd Walter , freebsd-alpha@FreeBSD.ORG Subject: RE: mb and wmb in atomic_ In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 15 Dec 2000, John Baldwin wrote: >=20 > On 15-Dec-00 Bernd Walter wrote: > > Why are the mb and wmb operations needed in the atomic_ functions? > > If I understood it correctly the locked operations are in synced > > with others CPUs and there is no memory operation beside the variable > > itself. >=20 > They should probably only be used with the 'acq' and 'rel' variants. Hmm= , btw, > it looks like I have the order of the barriers in the 'acq' and 'rel' var= iants > wrong. The barriers should be on the inside, not the outside. Anyone di= sagree? The mb() inside the atomic_ operations are obviously seriously miscommented: For example: static __inline void atomic_set_32(volatile u_int32_t *p, u_int32_t v) { =09u_int32_t temp; =09__asm __volatile ( =09=09"1:\tldl_l %0, %2\n\t"=09=09/* load old value */ =09=09"bis %0, %3, %0\n\t"=09=09/* calculate new value */ =09=09"stl_c %0, %1\n\t"=09=09/* attempt to store */ =09=09"beq %0, 2f\n\t"=09=09/* spin if failed */ =09=09"mb\n\t"=09=09=09/* drain to memory */ =09=09".section .text3,\"ax\"\n"=09/* improve branch prediction */ =09=09"2:\tbr 1b\n"=09=09=09/* try again */ =09=09".previous\n" =09=09: "=3D&r" (temp), "=3Dm" (*p) =09=09: "m" (*p), "r" (v) =09=09: "memory"); } There is obviously no relevance here in trying to drain something to memory. Note that thinking about a mb() as something that drains to memory is a serious mistake in my opinion. We want to order there, not to drain anything anywhere. However, the mb() above does have the effect of throwing away any read=20 that may have been prefetched by the CPU. If we need that here, we must not remove the mb(), otherwise the mb() can be removed. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 14:26:55 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 14:26:52 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 8F77237B6A9 for ; Fri, 15 Dec 2000 14:26:51 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBFMPqE31233; Fri, 15 Dec 2000 14:25:53 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 15 Dec 2000 14:26:10 -0800 (PST) From: John Baldwin To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Subject: RE: mb and wmb in atomic_ Cc: freebsd-alpha@FreeBSD.org, Bernd Walter Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15-Dec-00 Gérard Roudier wrote: > > > On Fri, 15 Dec 2000, John Baldwin wrote: > >> >> On 15-Dec-00 Bernd Walter wrote: >> > Why are the mb and wmb operations needed in the atomic_ functions? >> > If I understood it correctly the locked operations are in synced >> > with others CPUs and there is no memory operation beside the variable >> > itself. >> >> They should probably only be used with the 'acq' and 'rel' variants. Hmm, >> btw, >> it looks like I have the order of the barriers in the 'acq' and 'rel' >> variants >> wrong. The barriers should be on the inside, not the outside. Anyone >> disagree? > > The mb() inside the atomic_ operations are obviously seriously > miscommented: > > For example: > > static __inline void atomic_set_32(volatile u_int32_t *p, u_int32_t v) > { > u_int32_t temp; > > __asm __volatile ( > "1:\tldl_l %0, %2\n\t" /* load old value */ > "bis %0, %3, %0\n\t" /* calculate new value */ > "stl_c %0, %1\n\t" /* attempt to store */ > "beq %0, 2f\n\t" /* spin if failed */ > "mb\n\t" /* drain to memory */ > ".section .text3,\"ax\"\n" /* improve branch prediction */ > "2:\tbr 1b\n" /* try again */ > ".previous\n" > : "=&r" (temp), "=m" (*p) > : "m" (*p), "r" (v) > : "memory"); > } > > There is obviously no relevance here in trying to drain something to > memory. Note that thinking about a mb() as something that drains to memory > is a serious mistake in my opinion. We want to order there, not to drain > anything anywhere. > > However, the mb() above does have the effect of throwing away any read > that may have been prefetched by the CPU. If we need that here, we must > not remove the mb(), otherwise the mb() can be removed. What does NetBSD use for their atomic operations? Also, note that in FreeBSD, we have specific variants of atomic operations that include memory barriers (see the atomic(9) manpage in -current). If the actual atomicity of the operation doesn't need the mb, they should be removed. > Gérard. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 14:31:12 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 14:31:10 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6A4A837B400; Fri, 15 Dec 2000 14:31:10 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA31566; Fri, 15 Dec 2000 14:31:13 -0800 Date: Fri, 15 Dec 2000 14:31:05 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: John Baldwin , Bernd Walter , freebsd-alpha@FreeBSD.ORG Subject: RE: mb and wmb in atomic_ In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > } > > There is obviously no relevance here in trying to drain something to > memory. Note that thinking about a mb() as something that drains to memory > is a serious mistake in my opinion. We want to order there, not to drain > anything anywhere. That's correct. The 'drain' notion comes from the idea that write buffers (either from devices to memory or from memory to devices) may contain data that needs to arrive at it's 'real' location. > However, the mb() above does have the effect of throwing away any read > that may have been prefetched by the CPU. If we need that here, we must > not remove the mb(), otherwise the mb() can be removed. I don't *believe* that this is an issue for Alpha. It is for sparc which is not a memory coherent model. We went around and around with this discussion a while back. Since then I've gotten the newer Alpha architecture book. I'm swamped at the moment, but I'll post the relevant pages about this some time this weekend. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 14:42:27 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 14:42:26 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8CDA037B402; Fri, 15 Dec 2000 14:42:25 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA09308; Fri, 15 Dec 2000 17:42:23 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eBFMgNJ68797; Fri, 15 Dec 2000 17:42:23 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 15 Dec 2000 17:42:23 -0500 (EST) To: John Baldwin Cc: Bernd Walter , freebsd-alpha@FreeBSD.ORG Subject: Re: mb and wmb in atomic_ In-Reply-To: References: <20001215211930.D62048@cicely5.cicely.de> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14906.40438.240204.200341@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > Can the CPU perform out-of-order execution though? And out-of-order memory > accesses as a result? That is what memory barriers really protect you against. Yes, EV6 and better perform out of order execution. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 14:50:41 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 14:50:39 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id CDCF337B400; Fri, 15 Dec 2000 14:50:38 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id eBFMoY401936 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Fri, 15 Dec 2000 23:50:36 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eBFMotm26803 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Fri, 15 Dec 2000 23:50:57 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id eBFMooM62410; Fri, 15 Dec 2000 23:50:50 +0100 (CET) (envelope-from ticso) Date: Fri, 15 Dec 2000 23:50:50 +0100 From: Bernd Walter To: John Baldwin Cc: freebsd-alpha@FreeBSD.org Subject: Re: mb and wmb in atomic_ Message-ID: <20001215235049.A62322@cicely5.cicely.de> References: <20001215211930.D62048@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jhb@FreeBSD.org on Fri, Dec 15, 2000 at 01:19:25PM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Dec 15, 2000 at 01:19:25PM -0800, John Baldwin wrote: > > On 15-Dec-00 Bernd Walter wrote: > > On Fri, Dec 15, 2000 at 11:35:47AM -0800, John Baldwin wrote: > >> > >> On 15-Dec-00 Bernd Walter wrote: > >> > Why are the mb and wmb operations needed in the atomic_ functions? > >> > If I understood it correctly the locked operations are in synced > >> > with others CPUs and there is no memory operation beside the variable > >> > itself. > >> > >> They should probably only be used with the 'acq' and 'rel' variants. Hmm, > >> btw, > >> it looks like I have the order of the barriers in the 'acq' and 'rel' > >> variants > >> wrong. The barriers should be on the inside, not the outside. Anyone > >> disagree? > > > > Depending on atomic(9) I agree. > > I don't asume the acq variant realy needs one as the locked operation > > should be finished at once at least out of the CPUs thus no post operation > > has the chance to make anything before. > > Do we have the situation anywhere that the bus reorders memory access? > > Do we care about this? > > Can the CPU perform out-of-order execution though? And out-of-order memory > accesses as a result? That is what memory barriers really protect you against. Mmmm - true. I silently asumed conditioned store operations aren't reordered but in fact I havn't found a definition for this. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 15 16: 7:22 2000 From owner-freebsd-alpha@FreeBSD.ORG Fri Dec 15 16:07:19 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id B421637B400; Fri, 15 Dec 2000 16:07:17 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id eBG07Bh08734 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sat, 16 Dec 2000 01:07:13 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eBG07Rm27012 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Sat, 16 Dec 2000 01:07:34 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id eBG07Rj62560; Sat, 16 Dec 2000 01:07:27 +0100 (CET) (envelope-from ticso) Date: Sat, 16 Dec 2000 01:07:26 +0100 From: Bernd Walter To: John Baldwin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: mb and wmb in atomic_ Message-ID: <20001216010726.A62493@cicely5.cicely.de> References: <20001215211930.D62048@cicely5.cicely.de> <20001215235049.A62322@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20001215235049.A62322@cicely5.cicely.de>; from ticso@cicely5.cicely.de on Fri, Dec 15, 2000 at 11:50:50PM +0100 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Dec 15, 2000 at 11:50:50PM +0100, Bernd Walter wrote: > On Fri, Dec 15, 2000 at 01:19:25PM -0800, John Baldwin wrote: > > > > On 15-Dec-00 Bernd Walter wrote: > > > On Fri, Dec 15, 2000 at 11:35:47AM -0800, John Baldwin wrote: > > >> > > >> On 15-Dec-00 Bernd Walter wrote: > > >> > Why are the mb and wmb operations needed in the atomic_ functions? > > >> > If I understood it correctly the locked operations are in synced > > >> > with others CPUs and there is no memory operation beside the variable > > >> > itself. > > >> > > >> They should probably only be used with the 'acq' and 'rel' variants. Hmm, > > >> btw, > > >> it looks like I have the order of the barriers in the 'acq' and 'rel' > > >> variants > > >> wrong. The barriers should be on the inside, not the outside. Anyone > > >> disagree? > > > > > > Depending on atomic(9) I agree. > > > I don't asume the acq variant realy needs one as the locked operation > > > should be finished at once at least out of the CPUs thus no post operation > > > has the chance to make anything before. > > > Do we have the situation anywhere that the bus reorders memory access? > > > Do we care about this? > > > > Can the CPU perform out-of-order execution though? And out-of-order memory > > accesses as a result? That is what memory barriers really protect you against. > > Mmmm - true. > I silently asumed conditioned store operations aren't reordered but in fact > I havn't found a definition for this. I was shure I had read it somewhere. Finaly I've found the definition in the Alpha 21264 Microprocessor Reference Manual Chapter 4.6.2. The only out-of-order instructions are either none load/store nature or floating-point. And Chapter 2.10 says that instructions that store are executed with maintained order. But this doesn't say anything about future implementations. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Dec 16 0:31:59 2000 From owner-freebsd-alpha@FreeBSD.ORG Sat Dec 16 00:31:57 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from front1.grolier.fr (front1.grolier.fr [194.158.96.51]) by hub.freebsd.org (Postfix) with ESMTP id EBD1F37B400; Sat, 16 Dec 2000 00:31:56 -0800 (PST) Received: from nas1-218.mea.club-internet.fr (nas1-218.mea.club-internet.fr [195.36.139.218]) by front1.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id JAA20399; Sat, 16 Dec 2000 09:31:48 +0100 (MET) Date: Sat, 16 Dec 2000 08:31:42 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Matthew Jacob Cc: John Baldwin , Bernd Walter , freebsd-alpha@FreeBSD.ORG Subject: RE: mb and wmb in atomic_ In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 15 Dec 2000, Matthew Jacob wrote: > > } > >=20 > > There is obviously no relevance here in trying to drain something to > > memory. Note that thinking about a mb() as something that drains to mem= ory > > is a serious mistake in my opinion. We want to order there, not to drai= n > > anything anywhere. >=20 > That's correct. The 'drain' notion comes from the idea that write buffers > (either from devices to memory or from memory to devices) may contain dat= a > that needs to arrive at it's 'real' location. >=20 >=20 > > However, the mb() above does have the effect of throwing away any read= =20 > > that may have been prefetched by the CPU. If we need that here, we must > > not remove the mb(), otherwise the mb() can be removed. >=20 > I don't *believe* that this is an issue for Alpha. It is for sparc which = is > not a memory coherent model. This has nothing to do with memory coherency model but has to do with the ability of a CPU to exececutee LOADs out of order. > We went around and around with this discussion a while back. Since then I= 've > gotten the newer Alpha architecture book. I'm swamped at the moment, but = I'll > post the relevant pages about this some time this weekend. Handbook 1.0 1992 was already clear on this point. Unforgivable for having missed it you may well be. :-) G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Dec 16 1:59:10 2000 From owner-freebsd-alpha@FreeBSD.ORG Sat Dec 16 01:59:07 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from front7.grolier.fr (front7.grolier.fr [194.158.96.57]) by hub.freebsd.org (Postfix) with ESMTP id 9778A37B400; Sat, 16 Dec 2000 01:59:06 -0800 (PST) Received: from nas1-210.cgy.club-internet.fr (nas1-210.cgy.club-internet.fr [195.36.197.210]) by front7.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id KAA15954; Sat, 16 Dec 2000 10:59:00 +0100 (MET) Date: Sat, 16 Dec 2000 09:58:53 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: John Baldwin Cc: freebsd-alpha@FreeBSD.org, Bernd Walter Subject: RE: mb and wmb in atomic_ In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 15 Dec 2000, John Baldwin wrote: >=20 > On 15-Dec-00 G=E9rard Roudier wrote: > >=20 > >=20 > > On Fri, 15 Dec 2000, John Baldwin wrote: > >=20 > >>=20 > >> On 15-Dec-00 Bernd Walter wrote: > >> > Why are the mb and wmb operations needed in the atomic_ functions? > >> > If I understood it correctly the locked operations are in synced > >> > with others CPUs and there is no memory operation beside the variabl= e > >> > itself. > >>=20 > >> They should probably only be used with the 'acq' and 'rel' variants. = Hmm, > >> btw, > >> it looks like I have the order of the barriers in the 'acq' and 'rel' > >> variants > >> wrong. The barriers should be on the inside, not the outside. Anyone > >> disagree? > >=20 > > The mb() inside the atomic_ operations are obviously seriously > > miscommented: > >=20 > > For example: > >=20 > > static __inline void atomic_set_32(volatile u_int32_t *p, u_int32_t v) > > { > > u_int32_t temp; > >=20 > > __asm __volatile ( > > "1:\tldl_l %0, %2\n\t" /* load old value */ > > "bis %0, %3, %0\n\t" /* calculate new value */ > > "stl_c %0, %1\n\t" /* attempt to store */ > > "beq %0, 2f\n\t" /* spin if failed */ > > "mb\n\t" /* drain to memory */ > > ".section .text3,\"ax\"\n" /* improve branch predict= ion */ > > "2:\tbr 1b\n" /* try again */ > > ".previous\n" > > : "=3D&r" (temp), "=3Dm" (*p) > > : "m" (*p), "r" (v) > > : "memory"); > > } > >=20 > > There is obviously no relevance here in trying to drain something to > > memory. Note that thinking about a mb() as something that drains to mem= ory > > is a serious mistake in my opinion. We want to order there, not to drai= n > > anything anywhere. > >=20 > > However, the mb() above does have the effect of throwing away any read= =20 > > that may have been prefetched by the CPU. If we need that here, we must > > not remove the mb(), otherwise the mb() can be removed. >=20 > What does NetBSD use for their atomic operations? Duno. =20 > Also, note that in FreeBSD, > we have specific variants of atomic operations that include memory barrie= rs > (see the atomic(9) manpage in -current). If the actual atomicity of the > operation doesn't need the mb, they should be removed. Atomicity seems here for both Alpha and i386. =20 About Alpha, I doubt that using wmb() is a good idea, given that its does not guarantee ordering of memory-like with respect to non memory-like and this may lead to incorrect assumption from programmer when the both kinds= =20 of memory are used (device drivers for example). About i386 I donnot seem to see the promised read barrier for the atomic_load_acq_X() primitives. Note that I also donnot see where such primitive might be useful. :-) Anyway, they seems wrong to me given that Pentia II and above may reorder LOADs and LOADs against STOREs. We are only guaranteed STOREs to be carried out to system BUS in processor order when cachable is involved, and hitting non-cachable to insert implicit barriers. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Dec 16 10:42:33 2000 From owner-freebsd-alpha@FreeBSD.ORG Sat Dec 16 10:42:31 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1DA8537B400 for ; Sat, 16 Dec 2000 10:42:31 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBGIgEE60055; Sat, 16 Dec 2000 10:42:14 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.0) id eBGIfOc62489; Sat, 16 Dec 2000 10:41:24 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 16 Dec 2000 10:41:24 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Subject: RE: mb and wmb in atomic_ Cc: Bernd Walter , freebsd-alpha@FreeBSD.org Sender: jhb@foo.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Also, note that in FreeBSD, >> we have specific variants of atomic operations that include memory barriers >> (see the atomic(9) manpage in -current). If the actual atomicity of the >> operation doesn't need the mb, they should be removed. > > Atomicity seems here for both Alpha and i386. > > About Alpha, I doubt that using wmb() is a good idea, given that its does > not guarantee ordering of memory-like with respect to non memory-like and > this may lead to incorrect assumption from programmer when the both kinds > of memory are used (device drivers for example). From src/sys/alpha/include/alpha_cpu.h: static __inline void alpha_wmb(void) { /* * XXX dfr: NetBSD originally had mb instead of wmb for * alpha_wmb(). I'm not sure why so I'm leaving it alone. I * think it should be safe to use wmb though. */ __asm__ __volatile__ ("mb"); } > About i386 I donnot seem to see the promised read barrier for the > atomic_load_acq_X() primitives. Note that I also donnot see where such > primitive might be useful. :-) > Anyway, they seems wrong to me given that Pentia II and above may reorder > LOADs and LOADs against STOREs. We are only guaranteed STOREs to be > carried out to system BUS in processor order when cachable is involved, > and hitting non-cachable to insert implicit barriers. I'll have to look at this next week. So far only atomic_store_rel() has been used for the mutex operations. It could be that I need to change those to use lock'd cmpxchgl's in order to enforce ordering. > Gérard. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Dec 16 12:44:38 2000 From owner-freebsd-alpha@FreeBSD.ORG Sat Dec 16 12:44:36 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from switch2.switchpwr.com (switch1.switchpwr.com [12.14.48.19]) by hub.freebsd.org (Postfix) with ESMTP id 313A937B400 for ; Sat, 16 Dec 2000 12:44:36 -0800 (PST) Received: from switchpwr.com (switch4.switchpwr.com [12.14.48.22]) by switch2.switchpwr.com (8.11.0/8.11.0) with ESMTP id eBGKdei23322 for ; Sat, 16 Dec 2000 15:39:45 -0500 (EST) Sender: mel@switchpwr.com Message-ID: <3A3BD527.8F784C81@switchpwr.com> Date: Sat, 16 Dec 2000 15:48:39 -0500 From: mel kravitz Organization: switching power inc X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-3 alpha) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: up1000 install Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Has anyone tried to install 4.2 on a UP1000, if so can X -(mach64) server be made to work? If not what are the recommendations for video cards ? Is osf1(tru64 libs) support for netscape-xxx-dec.tar.gz present? -Mel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Dec 16 12:55:21 2000 From owner-freebsd-alpha@FreeBSD.ORG Sat Dec 16 12:55:19 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B34137B400 for ; Sat, 16 Dec 2000 12:55:19 -0800 (PST) Received: from thunder.cs.duke.edu (thunder.cs.duke.edu [152.3.145.24]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA21655; Sat, 16 Dec 2000 15:55:14 -0500 (EST) Received: (from gallatin@localhost) by thunder.cs.duke.edu (8.11.1/8.9.1) id eBGKsi200319; Sat, 16 Dec 2000 15:54:44 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14907.54932.80113.601300@thunder.cs.duke.edu> Date: Sat, 16 Dec 2000 15:54:44 -0500 (EST) To: mel kravitz Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: up1000 install In-Reply-To: <3A3BD527.8F784C81@switchpwr.com> References: <3A3BD527.8F784C81@switchpwr.com> X-Mailer: VM 6.71 under 21.1 "20 Minutes to Nikko" XEmacs Lucid (patch 2) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org mel kravitz writes: > Hi, > Has anyone tried to install 4.2 on a UP1000, if so can X -(mach64) I haven't actually installed from the installation media, but I've run 4.x on my UP1000 ever since merging the platform support from -current. > server be made to work? No idea. If the mach64 server doesn't work for you, I think you can try the svga server before you give up. > If not what are the recommendations for video cards ? Is osf1(tru64 Glint/Permedia cards such as the Elsa Gloria have the best support. > libs) support for netscape-xxx-dec.tar.gz > present? Yes. Install /usr/ports/emulators/osf1_base and then install your favorite version of netscape (communicator, navigator, etc) from /usr/ports/www/ Drew PS: I'm sending this mail from a up1000 running 5.0-CURRENT ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Dec 16 14:13:48 2000 From owner-freebsd-alpha@FreeBSD.ORG Sat Dec 16 14:13:47 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id A0D9537B400 for ; Sat, 16 Dec 2000 14:13:46 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 147PaF-000AN1-00; Sat, 16 Dec 2000 22:13:39 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.1) id eBGMDW510613; Sat, 16 Dec 2000 23:13:32 +0100 (CET) (envelope-from wkb) Date: Sat, 16 Dec 2000 23:13:32 +0100 From: Wilko Bulte To: mel kravitz Cc: freebsd-alpha@freebsd.org Subject: Re: up1000 install Message-ID: <20001216231332.A10543@freebie.demon.nl> References: <3A3BD527.8F784C81@switchpwr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A3BD527.8F784C81@switchpwr.com>; from melk@switchpwr.com on Sat, Dec 16, 2000 at 03:48:39PM -0500 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Dec 16, 2000 at 03:48:39PM -0500, mel kravitz wrote: > Hi, > Has anyone tried to install 4.2 on a UP1000, if so can X -(mach64) The only UP1000 owner I am aware of is Andrew Gallation. I think he verified if 4.2R booted on UP1000 but I don't know if he installed it. -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Dec 16 17:23:16 2000 From owner-freebsd-alpha@FreeBSD.ORG Sat Dec 16 17:23:15 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from tristero.cryptocourier.com (black-3.dsl.speakeasy.net [216.231.56.189]) by hub.freebsd.org (Postfix) with SMTP id DCA6437B400 for ; Sat, 16 Dec 2000 17:23:14 -0800 (PST) Received: (qmail 5322 invoked from network); 17 Dec 2000 01:26:48 -0000 Received: from roark.layer8.net (192.168.69.11) by tristero.cryptocourier.com with SMTP; 17 Dec 2000 01:26:48 -0000 Received: by roark.layer8.net (sSMTP sendmail emulation); Sat, 16 Dec 2000 17:11:28 +4000 Date: Sat, 16 Dec 2000 17:11:28 -0800 From: Ben Black To: freebsd-alpha@freebsd.org Subject: as2100 ECU? Message-ID: <20001216171128.B2792@layer8.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org does anyone happen to have a copy of the AS2100 EISA config utility handy? DEC does not seem excited about distributing them without new systems or a long wait for a floppy to be shipped. ben -- what great thing would you attempt if you knew you could not fail? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message