From owner-freebsd-alpha Sun Nov 5 1:19:18 2000 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 B49EA37B4C5 for ; Sun, 5 Nov 2000 01:19:16 -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 13sLxL-000FdQ-00; Sun, 05 Nov 2000 09:19:15 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eA58MX516164; Sun, 5 Nov 2000 09:22:33 +0100 (CET) (envelope-from wkb) Date: Sun, 5 Nov 2000 09:22:32 +0100 From: Wilko Bulte To: Warner Losh Cc: alpha@freebsd.org Subject: Re: iso image? Message-ID: <20001105092232.A15553@freebie.demon.nl> References: <200011050459.VAA38690@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200011050459.VAA38690@harmony.village.org>; from imp@village.org on Sat, Nov 04, 2000 at 09:59:30PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Nov 04, 2000 at 09:59:30PM -0700, Warner Losh wrote: > > Will there be an iso cdrom image for alpha for testing before 4.2-RELEASE? David indicated he would make them available at some point. .ISO testing must definitely be done IMO. Alphas not booting were a bit too common on 4.1.1 -- 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 Nov 5 3:38:48 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 9ED3A37B4CF; Sun, 5 Nov 2000 03:38:39 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13sO87-00074x-00; Sun, 05 Nov 2000 11:38:32 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eA5AN7316511; Sun, 5 Nov 2000 11:23:07 +0100 (CET) (envelope-from wkb) Date: Sun, 5 Nov 2000 11:23:07 +0100 From: Wilko Bulte To: "Kenneth D. Merry" Cc: mjacob@freebsd.org, FreeBSD-alpha mailing list , justin@freebsd.org Subject: Re: SCSI cdrom attach problems on 4-stable Message-ID: <20001105112307.A16448@freebie.demon.nl> References: <20001104200119.A13502@freebie.demon.nl> <20001104133216.A11678@panzer.kdm.org> <20001104230717.B14074@freebie.demon.nl> <20001104172952.B12998@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001104172952.B12998@panzer.kdm.org>; from ken@kdm.org on Sat, Nov 04, 2000 at 05:29:52PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Nov 04, 2000 at 05:29:52PM -0700, Kenneth D. Merry wrote: > On Sat, Nov 04, 2000 at 23:07:17 +0100, Wilko Bulte wrote: > > On Sat, Nov 04, 2000 at 01:32:17PM -0700, Kenneth D. Merry wrote: > > > There are several things to try here. ... I now have a very fresh 4.2-BETA running (built last night). No change from before. > > flags 0xd500 > > Same problem, autosense failed. What happens if you issue a TUR, or an > inquiry? > > camcontrol tur pass3 -v without media: miata#camcontrol tur pass3 -v isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 Unit is not ready CAM status is 0x10 Nov 5 12:07:36 miata /kernel: isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 Nov 5 12:07:36 miata /kernel: isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 miata# > camcontrol inquiry pass3 -v miata#camcontrol inquiry pass3 -v isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 pass3: Removable CD-Rd500 OM SCSI-2 device CAM status is 0x10 pass3: 10.000MB/s transfers (10.000MHz, offset 8) miata# (isp output is mixed with the camcontrol output, this was on the console) > The thing is, I'm not sure what will happen if there is a unit attention > condition on the drive (as there will be when you insert media), and > autosense is failing. Will the condition be cleared or not? > > The inquiry at least should work, the test unit ready might work. Try the > TUR both with a CD in the drive and without one in the drive. with media: miata#camcontrol tur pass3 -v isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 Unit is not ready CAM status is 0x10 miata#camcontrol tur pass3 -v isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 Unit is not ready CAM status is 0x10 miata#camcontrol tur pass3 -v isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 Unit is ready miata#camcontrol tur pass3 -v isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 Unit is ready miata# (note that it takes a while to get ready, could be 20 secs or so). > > > try is booting with a CD in the drive, and without a CD in the drive, and Without CD produces the problem. > > > see if one or the other causes it to probe. Boot with CD present / GENERIC 4.2-BETA: Mounting root from ufs:/dev/da1a cd0 at isp0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: cd present [679912 x 512 byte records] da0 at isp0 bus 0 target 0 lun 0 Boot without CD present / same kernel: Mounting root from ufs:/dev/da1a da0 at isp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device isp0: 0.0 get current period 0xc offset 0x8 flags 0xfd00 da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4095MB (8388314 512 byte sectors: 255H 63S/T 522C) da2 at isp0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device isp0: 0.2 get current period 0xc offset 0x8 flags 0xfd00 da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da1 at isp0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device isp0: 0.1 get current period 0xc offset 0x8 flags 0xfd00 da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) (cd0:isp0:0:6:0): got CAM status 0x50 (cd0:isp0:0:6:0): fatal error, failed to attach to device (cd0:isp0:0:6:0): lost device (cd0:isp0:0:6:0): removing device entry swapon: adding /dev/da1b as swap device I also noted that GENERIC has a considerably longer delay before probing (15 versus 3 seconds like I have on my MIATA kernel config file). DOes not seem to make a difference. > > AS1000A I have tested both a RRD45 and a RRD46 (both rebadged Toshibas btw) > > with the same effect. > > > > Common is a Qlogic card, so driven by isp. Matt, any comments? > > Do you have another type of controller handy that you could plug the drive > into? That might help isolate the problem. I'll see what I can do. -- 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 Nov 5 8:38:23 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 945F037B4CF; Sun, 5 Nov 2000 08:38:21 -0800 (PST) Received: (from wilko@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id IAA04187; Sun, 5 Nov 2000 08:38:21 -0800 (PST) (envelope-from wilko@FreeBSD.org) Date: Sun, 5 Nov 2000 08:38:21 -0800 (PST) From: Message-Id: <200011051638.IAA04187@freefall.freebsd.org> To: wilko@freebsd.org, wilko@FreeBSD.org, freebsd-alpha@freebsd.org Subject: Re: alpha/22314: tcpdump causes unaligned accesses Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: tcpdump causes unaligned accesses State-Changed-From-To: open->closed State-Changed-By: wilko State-Changed-When: Sun Nov 5 08:37:59 PST 2000 State-Changed-Why: Closing PR per the following commit: fenner 2000/11/04 16:23:11 PST Modified files: (Branch: RELENG_4) usr.sbin/tcpdump/tcpdump config.h Log: Nasty hack to handle tcpdump alignment issues on Alpha. This is being committed directly to RELENG_4 as a bandaid for 4.2 and a better solution will be created soon. PR: alpha/22314 Submitted by: gallatin Approved by: jkh Revision Changes Path 1.1.2.1 +7 -1 src/usr.sbin/tcpdump/tcpdump/config.h http://www.freebsd.org/cgi/query-pr.cgi?pr=22314 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 5 9:28:57 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp3.libero.it (smtp3.libero.it [193.70.192.53]) by hub.freebsd.org (Postfix) with ESMTP id 4315237B4CF for ; Sun, 5 Nov 2000 09:28:54 -0800 (PST) Received: from stex (151.21.0.235) by smtp3.libero.it; 5 Nov 2000 18:28:52 +0100 Message-ID: <3a0598d43a87aa84@smtp3.libero.it> (added by smtp3.libero.it) To: alpha@freebsd.org From: tgmwebsite@hotpop.com Date: Sun, 05 Nov 2000 18:31:47 Subject: Free funnies every day! Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ** Quote of the day ****************************************************** "Love is to stay awake all the night with a sick child. Or with a very healthy adult." (David Frost) ********************************************************************* Are you looking for a good morning start and you have an e-mail address? This is only an example of how the Good Morrow site can provide you a few moments of pure amusement by sending to your E-mail address a funny joke, like this one, every morning. The Service provided by The Good Morrow site is: absolutely free, easy to unsubscribe in every moment, made possible exclusively thanks to our sponsors' contribution. To subscribe, you only need to visit our site at http://www.goodmorrow.com and follow the simple instructions. Support The Good Morrow site. It costs nothing but can pay you back with some moments of pure amusement. The Good Morrow site. The right way to start the day! Your E-mail address has been provided us by a friend or a colleague of yours, and will no more be used by The Good Morrow Site to send any other mail. Thanks for your patience and cooperation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 5 13:18:44 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from alcanet.com.au (unknown [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id 9437337B4D7; Sun, 5 Nov 2000 13:18:39 -0800 (PST) Received: by border.alcanet.com.au id <115209>; Mon, 6 Nov 2000 09:17:53 +1100 Content-return: prohibited Date: Mon, 06 Nov 2000 08:18:23 +1100 From: Peter Jeremy Subject: Re: cvs commit: src/sys/boot/alpha/common main.c src/sys/boot/al To: Doug Rabson Cc: Mike Smith , alpha@FreeBSD.ORG Mail-followup-to: Doug Rabson , Mike Smith , alpha@FreeBSD.ORG Message-Id: <00Nov6.091753est.115209@border.alcanet.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Oct 27, 2000 at 10:28:38AM +0100, Doug Rabson wrote: >On Thu, 26 Oct 2000, Mike Smith wrote: >> Forgive the silly question, but is there any reason that boot1 doesn't >> read the load address from the loader object? > >On alpha, /boot/loader is just a binary (the headers have been stripped >off). When I wrote it, I didn't think I would be able to squeeze an ELF >loader into the space available. Currently there are 280 bytes spare - >probably not enough. Any reason why you couldn't have a primitive header: eg magic number and start address in /boot/loader. The code to read this and appropriately relocate /boot/loader shouldn't be too big. I agree that it's undesirable to wind up with yet another incompatible object format, but having an unbootable machine because /boot/loader expects a different load address to boot1 is even less desirable. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 5 13:22:26 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 25F7837B4C5; Sun, 5 Nov 2000 13:22:21 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA19381; Sun, 5 Nov 2000 14:22:09 -0700 (MST) (envelope-from ken) Date: Sun, 5 Nov 2000 14:22:09 -0700 From: "Kenneth D. Merry" To: Wilko Bulte Cc: mjacob@freebsd.org, FreeBSD-alpha mailing list , justin@freebsd.org Subject: Re: SCSI cdrom attach problems on 4-stable Message-ID: <20001105142209.B19227@panzer.kdm.org> References: <20001104200119.A13502@freebie.demon.nl> <20001104133216.A11678@panzer.kdm.org> <20001104230717.B14074@freebie.demon.nl> <20001104172952.B12998@panzer.kdm.org> <20001105112307.A16448@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001105112307.A16448@freebie.demon.nl>; from wkb@freebie.demon.nl on Sun, Nov 05, 2000 at 11:23:07AM +0100 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Nov 05, 2000 at 11:23:07 +0100, Wilko Bulte wrote: > On Sat, Nov 04, 2000 at 05:29:52PM -0700, Kenneth D. Merry wrote: > > On Sat, Nov 04, 2000 at 23:07:17 +0100, Wilko Bulte wrote: > > > On Sat, Nov 04, 2000 at 01:32:17PM -0700, Kenneth D. Merry wrote: > > > > There are several things to try here. > > ... > > I now have a very fresh 4.2-BETA running (built last night). No change from > before. > > > > flags 0xd500 > > > > Same problem, autosense failed. What happens if you issue a TUR, or an > > inquiry? > > > > camcontrol tur pass3 -v > > without media: > > miata#camcontrol tur pass3 -v > isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 > Unit is not ready > CAM status is 0x10 > Nov 5 12:07:36 miata /kernel: isp0: 0.6 get current period 0x19 offset 0x8 > flags 0xd500 > Nov 5 12:07:36 miata /kernel: isp0: 0.6 get current period 0x19 offset 0x8 > flags 0xd500 > miata# Okay, that's as expected, since there would normally be an error returned when no media is in the drive, but for some reason autosense isn't working, so we're just getting the autosense failed error. > > camcontrol inquiry pass3 -v > > miata#camcontrol inquiry pass3 -v > isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 > pass3: flags 0x> Removable CD-Rd500 > OM SCSI-2 device > CAM status is 0x10 > pass3: 10.000MB/s transfers (10.000MHz, offset 8) > miata# The inquiry works, except for the serial number, which is normal for most CDROM drives. > (isp output is mixed with the camcontrol output, this was on the console) > > > The thing is, I'm not sure what will happen if there is a unit attention > > condition on the drive (as there will be when you insert media), and > > autosense is failing. Will the condition be cleared or not? > > > > The inquiry at least should work, the test unit ready might work. Try the > > TUR both with a CD in the drive and without one in the drive. > > with media: > > miata#camcontrol tur pass3 -v > isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 > Unit is not ready > CAM status is 0x10 > miata#camcontrol tur pass3 -v > isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 > Unit is not ready > CAM status is 0x10 > miata#camcontrol tur pass3 -v > isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 > Unit is ready > miata#camcontrol tur pass3 -v > isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 > Unit is ready > miata# > > (note that it takes a while to get ready, could be 20 secs or so). Some drives take a while. So the drive can return good status, autosense is just broken when there's an error. > > > > try is booting with a CD in the drive, and without a CD in the drive, and > > Without CD produces the problem. > > > > > see if one or the other causes it to probe. > > Boot with CD present / GENERIC 4.2-BETA: > > Mounting root from ufs:/dev/da1a > cd0 at isp0 bus 0 target 6 lun 0 > cd0: Removable CD-ROM SCSI-2 device > isp0: 0.6 get current period 0x19 offset 0x8 flags 0xd500 > cd0: 10.000MB/s transfers (10.000MHz, offset 8) > cd0: cd present [679912 x 512 byte records] > da0 at isp0 bus 0 target 0 lun 0 > > Boot without CD present / same kernel: > [ ... ] > (cd0:isp0:0:6:0): got CAM status 0x50 > (cd0:isp0:0:6:0): fatal error, failed to attach to device > (cd0:isp0:0:6:0): lost device > (cd0:isp0:0:6:0): removing device entry > swapon: adding /dev/da1b as swap device > > I also noted that GENERIC has a considerably longer delay before probing > (15 versus 3 seconds like I have on my MIATA kernel config file). DOes not > seem to make a difference. > > > > AS1000A I have tested both a RRD45 and a RRD46 (both rebadged Toshibas btw) > > > with the same effect. > > > > > > Common is a Qlogic card, so driven by isp. Matt, any comments? > > > > Do you have another type of controller handy that you could plug the drive > > into? That might help isolate the problem. > > I'll see what I can do. That's probably our best bet for isolating the problem. This is a problem somewhere below the CD driver, but I'm not sure where. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 5 13:35:55 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from grootstal.nijmegen.inter.nl.net (grootstal.nijmegen.inter.nl.net [193.67.237.11]) by hub.freebsd.org (Postfix) with ESMTP id 1FF9D37B4C5 for ; Sun, 5 Nov 2000 13:35:50 -0800 (PST) Received: from ntpc by grootstal.nijmegen.inter.nl.net via 1Cust237.tnt29.rtm1.nl.uu.net [213.116.152.237] with SMTP for id WAA12532 (8.8.8/1.19); Sun, 5 Nov 2000 22:35:46 +0100 (MET) Reply-To: From: "Peter Blok" To: Subject: 4.1.1-RELEASE Date: Sun, 5 Nov 2000 22:34:12 +0100 Message-ID: <000b01c04770$24143ff0$8aac9f0a@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a couple of AXP33 systems and none of them is booting 4.1.1. The kernel crashes in some piece of MMU code. Is AXP33 not supported anymore? Will 4.2RC work? When it is needed to have a permanent AXP33 as reference, I'd like to volunteer. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 5 14: 5:23 2000 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 A59F537B4CF for ; Sun, 5 Nov 2000 14:05:21 -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 13sXui-0003tX-00; Sun, 05 Nov 2000 22:05:20 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eA5L8dt19292; Sun, 5 Nov 2000 22:08:39 +0100 (CET) (envelope-from wkb) Date: Sun, 5 Nov 2000 22:08:38 +0100 From: Wilko Bulte To: Peter Blok Cc: freebsd-alpha@freebsd.org Subject: Re: 4.1.1-RELEASE Message-ID: <20001105220838.A19255@freebie.demon.nl> References: <000b01c04770$24143ff0$8aac9f0a@ntpc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <000b01c04770$24143ff0$8aac9f0a@ntpc>; from Peter.Blok@inter.NL.net on Sun, Nov 05, 2000 at 10:34:12PM +0100 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Nov 05, 2000 at 10:34:12PM +0100, Peter Blok wrote: > Hi, > > I have a couple of AXP33 systems and none of them is booting 4.1.1. The > kernel crashes in some piece of MMU code. Is AXP33 not supported anymore? 4.1.1 sort of stinks on Alpha. My Multias also panic on boot. Multia and NoName are close enough here :-( > Will 4.2RC work? It should! > When it is needed to have a permanent AXP33 as reference, I'd like to > volunteer. Please test the release candidates once they become available. -- 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 Nov 5 15: 1:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wa4phy.dyndns.org (cc449817-a.mrtnz1.ga.home.com [24.12.79.51]) by hub.freebsd.org (Postfix) with ESMTP id E093537B4C5 for ; Sun, 5 Nov 2000 15:01:56 -0800 (PST) Received: from wa4phy.dyndns.org (localhost [127.0.0.1]) by wa4phy.dyndns.org (8.9.3/8.9.3) with ESMTP id SAA33916 for ; Sun, 5 Nov 2000 18:01:55 -0500 (EST) (envelope-from sam@wa4phy.dyndns.org) Message-ID: <3A05E6C5.D3CDAB86@wa4phy.dyndns.org> Date: Sun, 05 Nov 2000 18:01:25 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: alpha@freebsd.org Subject: SMP status w/sable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been following this list continously, and have seen several I think mentions of smp, but nothing I could understand.. What is the current status wrt smp on the sable machines? With all the problems I'm seeing regarding booting, what actually IS the latest bootable release number? Sorry if I'm not as technicaly literate as I should be.. Thanks.. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 5 16:28:20 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 1D8B637B4E5 for ; Sun, 5 Nov 2000 16:28:18 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id B8B2E458 for ; Sun, 5 Nov 2000 16:28:17 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id QAA27882 for ; Sun, 5 Nov 2000 16:28:17 -0800 (PST) Message-ID: <3A05FB20.99C6AFBE@cup.hp.com> Date: Sun, 05 Nov 2000 16:28:16 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: alpha@FreeBSD.org Subject: sizeof(struct sigframe) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, It seems beast is down. Can someone tell me what the size of struct sigframe is on Alpha? The following compiles on i386: #include #include #include #include int main() { printf("%d\n", sizeof(struct sigframe)); return 0; } Thanks, -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 5 17:30:36 2000 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 AFC6137B4D7 for ; Sun, 5 Nov 2000 17:30:32 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13sb7G-0006s3-01; Mon, 6 Nov 2000 02:30:30 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.0/8.11.0) id eA610sb05413 for freebsd-alpha@freebsd.org; Mon, 6 Nov 2000 02:00:54 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Status of -CURRENT on PC164? Date: Mon, 6 Nov 2000 01:00:53 +0000 (UTC) Message-ID: <8u4vs5$58s$1@kemoauc.mips.inka.de> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What's the status of recent -CURRENT on PC164? I'm still at PRE_SMPNG. I checked out a current src/sys, build a GENERIC kernel and the loader, and tried both independently. The loader works, but when I played a bit around with the kernel in single user mode, it always froze within a few minutes, apparently during disk accesses (sym). Hmm. -- 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 Nov 5 17:32:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DAF3B37B479 for ; Sun, 5 Nov 2000 17:32:31 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA29777; Sun, 5 Nov 2000 17:32:29 -0800 Date: Sun, 5 Nov 2000 17:32:29 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Status of -CURRENT on PC164? In-Reply-To: <8u4vs5$58s$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 It's still broken. As far as I can tell, fewer alphas work than don't work at this time. On Mon, 6 Nov 2000, Christian Weisgerber wrote: > What's the status of recent -CURRENT on PC164? > > I'm still at PRE_SMPNG. I checked out a current src/sys, build a > GENERIC kernel and the loader, and tried both independently. The > loader works, but when I played a bit around with the kernel in > single user mode, it always froze within a few minutes, apparently > during disk accesses (sym). Hmm. > > -- > 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 Sun Nov 5 23:11:15 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id CBE1637B4C5 for ; Sun, 5 Nov 2000 23:11:13 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13sgQy-000774-00; Mon, 06 Nov 2000 07:11:12 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eA66EVv21030; Mon, 6 Nov 2000 07:14:31 +0100 (CET) (envelope-from wkb) Date: Mon, 6 Nov 2000 07:14:31 +0100 From: Wilko Bulte To: Sam Drinkard Cc: alpha@freebsd.org Subject: Re: SMP status w/sable Message-ID: <20001106071431.A20674@freebie.demon.nl> References: <3A05E6C5.D3CDAB86@wa4phy.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A05E6C5.D3CDAB86@wa4phy.dyndns.org>; from sam@wa4phy.dyndns.org on Sun, Nov 05, 2000 at 06:01:25PM -0500 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Nov 05, 2000 at 06:01:25PM -0500, Sam Drinkard wrote: > I've been following this list continously, and have seen several I think > mentions of smp, but nothing I could understand.. What is the current > status wrt smp on the sable machines? With all the problems I'm seeing > regarding booting, what actually IS the latest bootable release > number? Sorry if I'm not as technicaly literate as I should be.. Well, the status of SMP on alpha is also a bit mysterious to me. I guess the bulk of that is in -current, and 4.2 does not have SMP yet. If that proves false I have work to do on HARDWARE.TXT for 4.2... -- 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 Nov 5 23:12:48 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DD8E237B4C5 for ; Sun, 5 Nov 2000 23:12:45 -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 XAA30404; Sun, 5 Nov 2000 23:12:39 -0800 Date: Sun, 5 Nov 2000 23:12:39 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: Sam Drinkard , alpha@FreeBSD.ORG Subject: Re: SMP status w/sable In-Reply-To: <20001106071431.A20674@freebie.demon.nl> 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, 6 Nov 2000, Wilko Bulte wrote: > On Sun, Nov 05, 2000 at 06:01:25PM -0500, Sam Drinkard wrote: > > I've been following this list continously, and have seen several I think > > mentions of smp, but nothing I could understand.. What is the current > > status wrt smp on the sable machines? With all the problems I'm seeing > > regarding booting, what actually IS the latest bootable release > > number? Sorry if I'm not as technicaly literate as I should be.. > > Well, the status of SMP on alpha is also a bit mysterious to me. I guess > the bulk of that is in -current, and 4.2 does not have SMP yet. If that > proves false I have work to do on HARDWARE.TXT for 4.2... Nope, nothing in 4.2. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Nov 5 23:14: 2 2000 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 3BD7B37B479 for ; Sun, 5 Nov 2000 23:14:00 -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 13sgTf-000HrJ-00; Mon, 06 Nov 2000 07:13:59 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eA66HIZ21103; Mon, 6 Nov 2000 07:17:18 +0100 (CET) (envelope-from wkb) Date: Mon, 6 Nov 2000 07:17:18 +0100 From: Wilko Bulte To: Matthew Jacob Cc: Sam Drinkard , alpha@FreeBSD.ORG Subject: Re: SMP status w/sable Message-ID: <20001106071718.C20674@freebie.demon.nl> References: <20001106071431.A20674@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Sun, Nov 05, 2000 at 11:12:39PM -0800 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Nov 05, 2000 at 11:12:39PM -0800, Matthew Jacob wrote: > On Mon, 6 Nov 2000, Wilko Bulte wrote: > > > On Sun, Nov 05, 2000 at 06:01:25PM -0500, Sam Drinkard wrote: > > > I've been following this list continously, and have seen several I think > > > mentions of smp, but nothing I could understand.. What is the current > > > status wrt smp on the sable machines? With all the problems I'm seeing > > > regarding booting, what actually IS the latest bootable release > > > number? Sorry if I'm not as technicaly literate as I should be.. > > > > Well, the status of SMP on alpha is also a bit mysterious to me. I guess > > the bulk of that is in -current, and 4.2 does not have SMP yet. If that > > proves false I have work to do on HARDWARE.TXT for 4.2... > > Nope, nothing in 4.2. At least I was not completely off-track ;-) -- 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 Mon Nov 6 2: 7:26 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id 913F337B4C5; Mon, 6 Nov 2000 02:07:23 -0800 (PST) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 13sjBQ-0001II-0B; Mon, 6 Nov 2000 10:07:22 +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 KAA16412; Mon, 6 Nov 2000 10:14:06 GMT (envelope-from dfr@nlsystems.com) Date: Mon, 6 Nov 2000 10:14:06 +0000 (GMT) From: Doug Rabson To: Peter Jeremy Cc: Mike Smith , alpha@FreeBSD.ORG Subject: Re: cvs commit: src/sys/boot/alpha/common main.c src/sys/boot/al In-Reply-To: <00Nov6.091801est.115213@border.alcanet.com.au> 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, 6 Nov 2000, Peter Jeremy wrote: > On Fri, Oct 27, 2000 at 10:28:38AM +0100, Doug Rabson wrote: > >On Thu, 26 Oct 2000, Mike Smith wrote: > >> Forgive the silly question, but is there any reason that boot1 doesn't > >> read the load address from the loader object? > > > >On alpha, /boot/loader is just a binary (the headers have been stripped > >off). When I wrote it, I didn't think I would be able to squeeze an ELF > >loader into the space available. Currently there are 280 bytes spare - > >probably not enough. > > Any reason why you couldn't have a primitive header: eg magic number > and start address in /boot/loader. The code to read this and > appropriately relocate /boot/loader shouldn't be too big. I agree that > it's undesirable to wind up with yet another incompatible object > format, but having an unbootable machine because /boot/loader expects > a different load address to boot1 is even less desirable. That would also involve changing the ABI between boot1 and loader. The problem with that is that loader is updated on installworld but boot1 isn't so its easy to create a mismatch. The load address of loader is essentially fixed. -- 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 Mon Nov 6 4:20:14 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id A95BA37B4D7 for ; Mon, 6 Nov 2000 04:20:03 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id EAA11394; Mon, 6 Nov 2000 04:19:50 -0800 (PST) (envelope-from obrien) Date: Mon, 6 Nov 2000 04:19:49 -0800 From: "David O'Brien" To: Christian Weisgerber Cc: freebsd-alpha@freebsd.org Subject: Re: Status of -CURRENT on PC164? Message-ID: <20001106041949.A11350@dragon.nuxi.com> Reply-To: alpha@freebsd.org References: <8u4vs5$58s$1@kemoauc.mips.inka.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8u4vs5$58s$1@kemoauc.mips.inka.de>; from naddy@mips.inka.de on Mon, Nov 06, 2000 at 01:00:53AM +0000 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: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 06, 2000 at 01:00:53AM +0000, Christian Weisgerber wrote: > What's the status of recent -CURRENT on PC164? VERY, very FUBAR'ed (and yes F == fucked). I've bugged JHB several times to send a request out to the Alpha list telling PC164 owners what they could do to help find the problem. For some reason I have yet to see this email from him. I would email him directly at jhb@freebsd.org. -- -- 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 Mon Nov 6 4:28:24 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id B49DD37B4D7 for ; Mon, 6 Nov 2000 04:28:22 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id EAA11631; Mon, 6 Nov 2000 04:28:08 -0800 (PST) (envelope-from obrien) Date: Mon, 6 Nov 2000 04:28:08 -0800 From: "David O'Brien" To: Sam Drinkard Cc: alpha@freebsd.org Subject: Re: SMP status w/sable Message-ID: <20001106042808.B11350@dragon.nuxi.com> Reply-To: alpha@freebsd.org References: <3A05E6C5.D3CDAB86@wa4phy.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A05E6C5.D3CDAB86@wa4phy.dyndns.org>; from sam@wa4phy.dyndns.org on Sun, Nov 05, 2000 at 06:01:25PM -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: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Nov 05, 2000 at 06:01:25PM -0500, Sam Drinkard wrote: > I've been following this list continously, and have seen several I think > mentions of smp, but nothing I could understand.. What is the current > status wrt smp on the sable machines? The second CPU has been started up on both a AS4100 and AS2100. This alone is a major accomplishment, but is also far from a usable SMP implementation. -- -- 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 Mon Nov 6 4:34:48 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id B7B1C37B4C5 for ; Mon, 6 Nov 2000 04:34:46 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id EAA11766; Mon, 6 Nov 2000 04:30:59 -0800 (PST) (envelope-from obrien) Date: Mon, 6 Nov 2000 04:30:59 -0800 From: "David O'Brien" To: Marcel Moolenaar Cc: alpha@FreeBSD.org Subject: Re: sizeof(struct sigframe) Message-ID: <20001106043058.C11350@dragon.nuxi.com> Reply-To: alpha@FreeBSD.org References: <3A05FB20.99C6AFBE@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A05FB20.99C6AFBE@cup.hp.com>; from marcel@cup.hp.com on Sun, Nov 05, 2000 at 04:28:16PM -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: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Nov 05, 2000 at 04:28:16PM -0800, Marcel Moolenaar wrote: > It seems beast is down. Can someone tell me what the size of struct > sigframe is on Alpha? On a PWS600au(Miata) running today's 5-current I get: 808 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 6 4:35:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 4CAEF37B4C5 for ; Mon, 6 Nov 2000 04:35:10 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id EAA11805; Mon, 6 Nov 2000 04:34:51 -0800 (PST) (envelope-from obrien) Date: Mon, 6 Nov 2000 04:34:51 -0800 From: "David O'Brien" To: Peter Blok Cc: freebsd-alpha@freebsd.org Subject: Re: 4.1.1-RELEASE Message-ID: <20001106043451.E11350@dragon.nuxi.com> Reply-To: alpha@freebsd."org" References: <000b01c04770$24143ff0$8aac9f0a@ntpc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000b01c04770$24143ff0$8aac9f0a@ntpc>; from Peter.Blok@inter.NL.net on Sun, Nov 05, 2000 at 10:34:12PM +0100 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: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Nov 05, 2000 at 10:34:12PM +0100, Peter Blok wrote: > I have a couple of AXP33 systems and none of them is booting 4.1.1. I've yanked 4.1.1 from the FTP site as there was a snafu in rolling the release. 4.1(.0) is really solid for me. I would use that for now on your Alhpa. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 6 5:11:13 2000 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 EC7EB37B4C5 for ; Mon, 6 Nov 2000 05:11:09 -0800 (PST) Received: from [195.11.243.26] (helo=Debug) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13sm3J-000Aaq-00; Mon, 06 Nov 2000 13:11:09 +0000 To: alpha@freebsd."org", Peter Blok , freebsd-alpha@freebsd.org From: wkb@freebie.demon.nl Subject: Re: 4.1.1-RELEASE Date: Mon, 6 Nov 2000 13:11:09 GMT X-Mailer: www.webmail.nl.demon.net X-Sender: postmaster@wkb@freebie.demon.nl X-Originating-IP: 207.122.110.166 Message-Id: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sun, Nov 05, 2000 at 10:34:12PM +0100, Peter Blok wrote: > > I have a couple of AXP33 systems and none of them is booting 4.1.1. > > I've yanked 4.1.1 from the FTP site as there was a snafu in rolling the Excellent idea!! Fortunately 4.1.1. is not a CD release on alpha. > release. 4.1(.0) is really solid for me. I would use that for now on > your Alhpa. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 6 5:14:59 2000 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 6E7AA37B479 for ; Mon, 6 Nov 2000 05:14:56 -0800 (PST) Received: from [195.11.243.26] (helo=Debug) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13sm6x-000AxZ-00; Mon, 06 Nov 2000 13:14:55 +0000 To: alpha@freebsd.org, Sam Drinkard , alpha@freebsd.org From: wkb@freebie.demon.nl Subject: Re: SMP status w/sable Date: Mon, 6 Nov 2000 13:14:55 GMT X-Mailer: www.webmail.nl.demon.net X-Sender: postmaster@wkb@freebie.demon.nl X-Originating-IP: 207.122.110.166 Message-Id: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sun, Nov 05, 2000 at 06:01:25PM -0500, Sam Drinkard wrote: > > I've been following this list continously, and have seen several I think > > mentions of smp, but nothing I could understand.. What is the current > > status wrt smp on the sable machines? > > The second CPU has been started up on both a AS4100 and AS2100. in -current > This alone is a major accomplishment, but is also far from a usable SMP > implementation. Right.. Wilko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 6 6: 5: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail17a.wh.ocn.ne.jp (mail17a.wh.ocn.ne.jp [210.190.172.36]) by hub.freebsd.org (Postfix) with SMTP id 76F4F37B4D7 for ; Mon, 6 Nov 2000 06:04:51 -0800 (PST) Received: from www.ittoku.net (210.190.150.13) by mail17a.wh.ocn.ne.jp (RS ver 1.0.57s) with SMTP id 37402554; Mon, 6 Nov 2000 23:03:19 +0900 (JST) Message-ID: <000201c047fa$4e9d4660$0100a8c0@mshome.net> Reply-To: "=?iso-2022-jp?B?aXR0b2t1Lm5ldBskQj9kP0o7djZISXQbKEI=?=" From: "=?iso-2022-jp?B?aXR0b2t1Lm5ldBskQj9kP0o7djZISXQbKEI=?=" To: Subject: =?iso-2022-jp?B?aS1tb2RlGyRCTVElaiUiJWslPyUkJWBFOUpeOS0bKEI=?= =?iso-2022-jp?B?GyRCOXAbKEJIUBskQiROJDQwRkZiGyhC?= Date: Mon, 6 Nov 2000 08:08:59 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00AF_01C047C8.D18A31A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Loop-Detect: 1 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_00AF_01C047C8.D18A31A0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit $B$O$8$a$^$7$F!"FMA3$N%a!<%k$r$*5v$7$/$@$5$$!#(B $B$b$7$4IT2w$@$H;W$o$l$?>l9g$OJV?.$7$F$$$?$@$-$^$7$?$i!!%j%9%H$+$i:o=|$5$;$F$$(B $B$?$@$-$^$9!#(B $B;d6&(Bittoku.net$B$O!"#1#17n#1F|$K@5<0H/B-$7$^$7$?7HBS%3%s%F%s%DAm9g%M%C%H$G$9!#(B $B:#$d8\5R3MF@$NHs>o$KFq$7$$K\Ev$KNI$$$b$N$@$1$rE,@5$J2A3J$GDs6!$7$J$1$l$P!"@8(B $B$-;D$l$J$$;~Be$H$J$j$^$7$?!#(B $B%$%s%?!<%M%C%H$dOCBj$N(Bi$B%b!<%I$r3hMQ$7$h$&$K$bJ}K!O@$,2r$i$J$$!"$"$k$$$O!"%$(B $B%s%?!<%M%C%H$G%5!<%P!<$rN)$A>e$2$k$N$K$O%3%9%H$,3]$+$j$9$.$kEy!"Fq$7$$LdBj$,(B $B;3@Q$_$G$9!#(B $B$=$3$G!"$3$NEY$^$C$?$/?7$7$$(Bi-mode$BMQ%j%"%k%?%$%`E9J^9-9p(BHP$B$r%9%?!<%H$$$?$7$^(B $B$9!#(B $BEv%M%C%H$O!"8\5R$G$"$k>&E9&7w$N?M$?$A$r3MF@$9$k0Y$N%5%$%H$rL\(B $B;X$7$F$$$^$9!#(B $B$D$^$j!"K\Ev$N0UL#$G$N%T%s%]%$%s%H@oN,$r%$%s%?!<%M%C%H$N(Bi$B%b!<%I$rMxMQ$9$k;v(B $B$G!"9T$&$3$H$,=PMh$k$N$G$9!#(B $BJ8;zDL$j!"E9J^$N99?7!&JQ99$,%Q%=%3%s$O$b$A$m$s(Bi-mode$B$+$i$G$b4JC1$K=PMh$k0Y!"(B $BE9$N>u67$r8+$J$,$i(B $B$=$N>l$G>pJs$rH/?.$9$k$3$H$,=PMh$^$9!#(B $B2A3J$b!!(B3$B%v7n#1K|1_$HHs>o$K0B2A$K2!$5$(!"%*%W%7%g%s$GE9$NCO?^$b7G:\2DG=$G(B $B$9!#(B $B$5$i$K:#$J$i(B1$B%v7n4V$N$*;n$74|4V!"(B11$B7n@.LspJs$b$4$6$$$^$9!#(B ---------------------------------------------------------------------------- ---- $B$D$-$^$7$F$OFC$K2<5-$N$h$&$JJ}$K@'HsCN$C$FD:$-$?$/;W$C$F$$$^$9$N$G6=L#$"$kJ}(B $B$O0lEY>R2p(BHP$B$r$4Mw2<$5$$(B *$B!!E9J^$r7P1D$^$?$O7H$o$C$F$$$kJ}(B *$B!!E9J^$r7P1D$^$?$O7H$o$C$F$$$kJ}$NG:$_$rJ9$$$?$3$H$,$"$kJ}(B *$B!!%5%$%I%S%8%M%9$r9M$($i$l$F$$$kJ}(B ---------------------------------------------------------------------------- ---- $B6qBNE*$KMxMQ$5$l$k$3$H$G%a%j%C%H$,$"$kJ}(B $B:#$^$G$*5R$5$s$,Mh$k;~$H$=$&$G$J$$>l9g$N;~$H$N:9$,7c$7$$E9$NJ}(B $B9-9p$K$*6b$,$+$+$j$9$.$k$H;W$C$F$*$i$l$kJ}(B $B<+K}$N>&IJ$r$b$C$HCN$C$F$b$i$$$?$$$H;W$C$F$*$i$l$kJ}(B $B:#F|Cf$KGd$j@Z$j$?$$>&IJ$,=P$k$3$H$,NI$/$"$kJ}(B $B:#$*5R$5$s$KCN$i$;$?$$$3$H$,$"$k$N$KJ}K!$,$J$$$H;W$C$?$3$H$N$"$kJ}(B $B%[!<%`%Z!<%8$r=P$7$?$1$I:#0lH?1~$,$J$$$H$$$&J}(B $B85R2p(BHP$B%"%I%l%9!!(Bhttp://ittoku.net/hp/ $B".".".".".".".".".".(B/////////////////// ittoku.net $B?d?J;v6HIt!!C4Ev!!>.@>(B $BBg:e;TCf1{6h?4:X666Z(B2-7-2 TEL 06-6211-4726 FAX06-6211-6049 $BD>DL(BTEL 06-6211-4733 suisin@ittoku.net //////////////////$B".".".".".".".".".".(B ------=_NextPart_000_00AF_01C047C8.D18A31A0 Content-Type: text/html; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable
=1B$B$O$8$a$^$7$F!"FMA3$N%a!<%k$r$*5v$7$/$@$5$$!#=1B(B
 =
=1B$B$b$7$4IT2w$@$H;W$o$l$?>l9g$OJV?.$7$F$$$?$@$-$^$7$?$i!!%j%9%H$+$i= :o=3D|$5$;$F$$$?$@$-$^$9!#=1B(B
 
=1B$B;d6&=1B(Bittoku.net=1B$B$O!"#1#17n#1F|$K@5<0H/B-$7$^$7$?7HB= S%3%s%F%s%DAm9g%M%C%H$G$9!#=1B(B
=1B$B:#$d8\5R3MF@$NHs>o$KFq$7$$K\Ev$KNI$$$b$N$@$1$rE,@5$J2A3J$GD= s6!$7$J$1$l$P!"@8$-;D$l$J$$;~Be$H$J$j$^$7$?!#=1B(B
=1B$B%$%s%?!<%M%C%H$dOCBj$N=1B(Bi=1B$B%b!<%I$r3hMQ$7$h$&$K$bJ}K!= O@$,2r$i$J$$!"$"$k$$$O!"%$%s%?!<%M%C%H$G%5!<%P!<$rN)$A>e$2$k$N$K$O%3%9%H$= ,3]$+$j$9$.$kEy!"Fq$7$$LdBj$,;3@Q$_$G$9!#=1B(B
=1B$B$=3D$3$G!"$3$NEY$^$C$?$/?7$7$$=1B(Bi-mode=1B$BMQ%j%"%k%?%$%`E9J^9-9p=1B(BHP=1B$B$r%9%= ?!<%H$$$?$7$^$9!#=1B(B
 
=1B$BEv%M%C%H$O!"8\5R$G$"$k>&E9&7w$N?M$?$A$r3MF= @$9$k0Y$N%5%$%H$rL\;X$7$F$$$^$9!#=1B(B
=1B$B$D$^$j!"K\Ev$N0UL#$G$N%T%s%]%$%s%H@oN,$r%$%s%?!<%M%C%H$N=1B= (Bi=1B$B%b!<%I$rMxMQ$9$k;v$G!"9T$&$3$H$,=3DPMh$k$N$G$9!#=1B(B
=1B$BJ8;zDL$j!"E9J^$N99?7!&JQ99$,%Q%=3D%3%s$O$b$A$m$s=1B(Bi-mode= =1B$B$+$i$G$b4JC1$K=3DPMh$k0Y!"E9$N>u67$r8+$J$,$i=1B(B
=1B$B$=3D$N>l$G= >pJs$rH/?.$9$k$3$H$,=3DPMh$^$9!#=1B(B
 
=1B$B2A3J$b!!=1B(B3=1B$B%v7n#1K|1_$HHs>o$K0B2A=1B(B=1B$B$K2!$5$(!"%*%W%7%g%= s$GE9$NCO?^$b7G:\2DG=3D$G$9!#=1B(B
=1B$B$5$i$K:#$J$i=1B(B1=1B$B%v7n4V$N$*;n$74|4V!"=1B(B11=1B$B7n@.Ls=1B$BEy$r$4MQ0U$7$F$$$^$9=1B(B
=1B$B$^$?!"%5%$%I%S%8%M%9$r9M$($i$l$F$$$kJ}$X<*4s$j$J>pJs$b$4$6$= $$^$9!#=1B(B
 

=1B$B$D$-$^$7$F$OFC$K2<5-$N$h$&$JJ}$K@'HsCN$C$FD:$-$?$/;W$C$F$$$^$9$N= $G6=3DL#$"$kJ}$O0lEY>R2p=1B(BHP=1B$B$r$4Mw2<$5$$=1B(B
 
*=1B$B= !!E9J^$r7P1D$^$?$O7H$o$C$F$$$kJ}=1B(B
*=1B$B!!E9J^$r7P1D$^$?$O7H$o$C$F= $$$kJ}$NG:$_$rJ9$$$?$3$H$,$"$kJ}=1B(B
*=1B$B!!%5%$%I%S%8%M%9$r9M$($i$l= $F$$$kJ}=1B(B
 =20

=1B$B6qBNE*$KMxMQ$5$l$k$3$H$G%a%j%C%H$,$"$kJ}=1B(B
 =1B$B:#$^= $G$*5R$5$s$,Mh$k;~$H$=3D$&$G$J$$>l9g$N;~$H$N:9$,7c$7$$E9$NJ}=1B(B=20
 =1B$B9-9p$K$*6b$,$+$+$j$9$.$k$H;W$C$F$*$i$l$kJ}=1B(B =
 =1B$B<+K}$N>&IJ$r$b$C$HCN$C$F$b$i$$$?$$$H;W$C$F$*$i$l$kJ}=1B(B =
 =1B$B:#F|Cf$KGd$j@Z$j$?$$>&IJ$,=3DP$k$3$H$,NI$/$"$kJ}=1B(B =
 =1B$B:#$*5R$5$s$KCN$i$;$?$$$3$H$,$"$k$N$KJ}K!$,$J$$$H;W$C$?$3$H= $N$"$kJ}=1B(B=20
 =1B$B%[!<%`%Z!<%8$r=3DP$7$?$1$I:#0lH?1~$,$J$$$H$$$&J}=1B(B =
 =1B$B85 =1B$BM'?M$,E9J^$r9=3D$($F$*$i$l$kJ}=1B(B
 
 =1B$B>R2p=1B(BHP=1B$B%"%I%l%9!!=1B(Bhttp://ittoku.net/hp/
 
 
=1B$B".".".".".".".".".".=1B(B//////////////= /////
 
ittoku.net=20 =1B$B?d?J;v6HIt!!C4Ev!!>.@>=1B(B
  =
=1B$BBg:e;TCf1{6h?4:X666Z=1B(B2-7-2
TEL 06-6211-4726 = FAX06-6211-6049=20
=1B$BD>DL=1B(BTEL 06-6211-4733
suisin@ittoku.net
 
//////////////////=1B$B".".".".".".".".".".=1B(B
------=_NextPart_000_00AF_01C047C8.D18A31A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 6 8: 9: 4 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 57CBF37B4D7; Mon, 6 Nov 2000 08:09:00 -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 IAA32042; Mon, 6 Nov 2000 08:09:00 -0800 Date: Mon, 6 Nov 2000 08:08:59 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@FreeBSD.ORG Cc: Christian Weisgerber , freebsd-alpha@FreeBSD.ORG Subject: Re: Status of -CURRENT on PC164? In-Reply-To: <20001106041949.A11350@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 Mon, Nov 06, 2000 at 01:00:53AM +0000, Christian Weisgerber wrote: > > What's the status of recent -CURRENT on PC164? > > VERY, very FUBAR'ed (and yes F == fucked). I've bugged JHB several times > to send a request out to the Alpha list telling PC164 owners what they > could do to help find the problem. For some reason I have yet to see > this email from him. I would email him directly at jhb@freebsd.org. It's not John's problem to get people to help- John's done the right thing within the constraints of the initial design that Doug left in place. All of us who own PC164s are aware of the breakage. It is my opinion, btw, that it isn't just a PC164 issue. I believe that the current quenching design may ask too much of hardware and that the platforms that -current currently works on only work by chance (the ability to turn off interrupts at the bridge in the middle of an interrupt). But I could still be quite wrong abou tthis. Without spending all week on this problem (which I haven't got time on now) and coming up with some testing strategy that can prove this one way or the other, I haven't been able to help directly. The list of machines that do *not* work is high, and yes, I'm losing lots of sleep over it. But I've also been trying to spend time to make sure that 4.2 is better than 4.1.1 is (and I'm waiting for an RC iso image from you to do some testing- I'll piss off some clients and blow wednesday and maybe thursday on testing if you have one ready). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 6 8: 9: 4 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 57CBF37B4D7; Mon, 6 Nov 2000 08:09:00 -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 IAA32042; Mon, 6 Nov 2000 08:09:00 -0800 Date: Mon, 6 Nov 2000 08:08:59 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@FreeBSD.ORG Cc: Christian Weisgerber , freebsd-alpha@FreeBSD.ORG Subject: Re: Status of -CURRENT on PC164? In-Reply-To: <20001106041949.A11350@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 Mon, Nov 06, 2000 at 01:00:53AM +0000, Christian Weisgerber wrote: > > What's the status of recent -CURRENT on PC164? > > VERY, very FUBAR'ed (and yes F == fucked). I've bugged JHB several times > to send a request out to the Alpha list telling PC164 owners what they > could do to help find the problem. For some reason I have yet to see > this email from him. I would email him directly at jhb@freebsd.org. It's not John's problem to get people to help- John's done the right thing within the constraints of the initial design that Doug left in place. All of us who own PC164s are aware of the breakage. It is my opinion, btw, that it isn't just a PC164 issue. I believe that the current quenching design may ask too much of hardware and that the platforms that -current currently works on only work by chance (the ability to turn off interrupts at the bridge in the middle of an interrupt). But I could still be quite wrong abou tthis. Without spending all week on this problem (which I haven't got time on now) and coming up with some testing strategy that can prove this one way or the other, I haven't been able to help directly. The list of machines that do *not* work is high, and yes, I'm losing lots of sleep over it. But I've also been trying to spend time to make sure that 4.2 is better than 4.1.1 is (and I'm waiting for an RC iso image from you to do some testing- I'll piss off some clients and blow wednesday and maybe thursday on testing if you have one ready). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 6 11:41:55 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id B101737B4C5 for ; Mon, 6 Nov 2000 11:41:52 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA53851; Mon, 6 Nov 2000 11:41:50 -0800 (PST) (envelope-from obrien) Date: Mon, 6 Nov 2000 11:41:50 -0800 From: "David O'Brien" To: Matthew Jacob Cc: alpha@FreeBSD.ORG Subject: Re: Status of -CURRENT on PC164? Message-ID: <20001106114150.G11350@dragon.nuxi.com> Reply-To: alpha@FreeBSD.ORG References: <20001106041949.A11350@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, Nov 06, 2000 at 08:08:59AM -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: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 06, 2000 at 08:08:59AM -0800, Matthew Jacob wrote: > It's not John's problem to get people to help- John's done the right > thing within the constraints of the initial design that Doug left in > place. Ok, then which FreeBSD developer that took responsibility for this code hasn't been looking into the issue? AFAIK those that have been working on this code don't know what is going on with the PC164. I do know there are some debugging macros, etc. that one can run that may help give some idea what is going on. A nice "request for output" email with a few instructions of how to get the debug info wouldn't hurt IMHO. -- -- 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 Mon Nov 6 12:56: 3 2000 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 2FF5D37B4E5; Mon, 6 Nov 2000 12:55:56 -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 13stJ3-0006Ew-00; Mon, 06 Nov 2000 20:55:54 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eA6JxF302224; Mon, 6 Nov 2000 20:59:15 +0100 (CET) (envelope-from wkb) Date: Mon, 6 Nov 2000 20:59:15 +0100 From: Wilko Bulte To: "Kenneth D. Merry" Cc: mjacob@freebsd.org, FreeBSD-alpha mailing list , justin@freebsd.org Subject: Re: SCSI cdrom attach problems on 4-stable Message-ID: <20001106205915.A2151@freebie.demon.nl> References: <20001104200119.A13502@freebie.demon.nl> <20001104133216.A11678@panzer.kdm.org> <20001104230717.B14074@freebie.demon.nl> <20001104172952.B12998@panzer.kdm.org> <20001105112307.A16448@freebie.demon.nl> <20001105142209.B19227@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001105142209.B19227@panzer.kdm.org>; from ken@kdm.org on Sun, Nov 05, 2000 at 02:22:09PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Nov 05, 2000 at 02:22:09PM -0700, Kenneth D. Merry wrote: > On Sun, Nov 05, 2000 at 11:23:07 +0100, Wilko Bulte wrote: > > On Sat, Nov 04, 2000 at 05:29:52PM -0700, Kenneth D. Merry wrote: > > > On Sat, Nov 04, 2000 at 23:07:17 +0100, Wilko Bulte wrote: > > > > On Sat, Nov 04, 2000 at 01:32:17PM -0700, Kenneth D. Merry wrote: > > > > > There are several things to try here. > > > > > > Common is a Qlogic card, so driven by isp. Matt, any comments? > > > > > > Do you have another type of controller handy that you could plug the drive > > > into? That might help isolate the problem. > > > > I'll see what I can do. > > That's probably our best bet for isolating the problem. This is a problem > somewhere below the CD driver, but I'm not sure where. Ok. I hooked up an external CD drive. This one reports as Toshiba (but is a RRD45 with it's jumper not set to DEC inquiry string). (sorry for the wrap) On isp: Nov 6 21:46:34 miata /kernel: isp0: 0.6 get user period 0xc offset 0x8 flags 0x fd00 Nov 6 21:46:34 miata /kernel: isp0: 0.6 get current period 0x19 offset 0x0 flag s 0xc500 Nov 6 21:46:34 miata /kernel: isp0: 0.6 set current period 0xc offset 0x8 flags 0xd500 Nov 6 21:46:34 miata /kernel: isp0: 0.0 get user period 0xc offset 0x8 flags 0x fd00 Nov 6 21:46:34 miata /kernel: isp0: 0.0 get current period 0x19 offset 0x0 flag s 0xc500 Nov 6 21:46:34 miata /kernel: isp0: 0.0 set current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:46:34 miata /kernel: isp0: 0.1 get user period 0xc offset 0x8 flags 0x fd00 Nov 6 21:46:34 miata /kernel: isp0: 0.1 get current period 0x19 offset 0x0 flag s 0xc500 Nov 6 21:46:34 miata /kernel: isp0: 0.1 set current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:46:34 miata /kernel: isp0: 0.2 get user period 0xc offset 0x8 flags 0x fd00 Nov 6 21:46:34 miata /kernel: isp0: 0.2 get current period 0x19 offset 0x0 flag s 0xc500 Nov 6 21:46:34 miata /kernel: isp0: 0.2 set current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:46:34 miata /kernel: isp1: 0.5 get user period 0x19 offset 0x8 flags 0 xc500 Nov 6 21:46:34 miata /kernel: isp1: 0.5 get current period 0x19 offset 0x0 flag s 0xc500 Nov 6 21:46:34 miata /kernel: isp1: 0.5 set current period 0x19 offset 0x8 flag s 0xc500 Nov 6 21:46:34 miata /kernel: Mounting root from ufs:/dev/da1a Nov 6 21:46:34 miata /kernel: da0 at isp0 bus 0 target 0 lun 0 Nov 6 21:46:35 miata /kernel: da0: Fixed Direct Access SCSI-2 device Nov 6 21:46:35 miata /kernel: isp0: 0.0 get current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:46:35 miata /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 8, 1 6bit), Tagged Queueing Enabled Nov 6 21:46:35 miata /kernel: da0: 4095MB (8388314 512 byte sectors: 255H 63S/T 522C) Nov 6 21:46:35 miata /kernel: da2 at isp0 bus 0 target 2 lun 0 Nov 6 21:46:35 miata /kernel: da2: Fixed Direct Access S CSI-2 device Nov 6 21:46:35 miata /kernel: isp0: 0.2 get current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:46:35 miata /kernel: da2: 40.000MB/s transfers (20.000MHz, offset 8, 1 6bit), Tagged Queueing Enabled Nov 6 21:46:35 miata /kernel: da2: 8715MB (17850000 512 byte sectors: 255H 63S/ T 1111C) Nov 6 21:46:35 miata /kernel: da1 at isp0 bus 0 target 1 lun 0 Nov 6 21:46:35 miata /kernel: da1: Fixed Direct Access S CSI-2 device Nov 6 21:46:35 miata /kernel: isp0: 0.1 get current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:46:35 miata /kernel: da1: 40.000MB/s transfers (20.000MHz, offset 8, 1 6bit), Tagged Queueing Enabled Nov 6 21:46:35 miata /kernel: da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Nov 6 21:46:35 miata /kernel: (cd0:isp0:0:6:0): got CAM status 0x50 Nov 6 21:46:35 miata /kernel: (cd0:isp0:0:6:0): fatal error, failed to attach t o device Nov 6 21:46:35 miata /kernel: (cd0:isp0:0:6:0): lost device Nov 6 21:46:35 miata /kernel: (cd0:isp0:0:6:0): removing device entry Nov 6 21:46:35 miata /kernel: (cd1:isp1:0:5:0): got CAM status 0x50 Nov 6 21:46:35 miata /kernel: (cd1:isp1:0:5:0): fatal error, failed to attach t o device Nov 6 21:46:35 miata /kernel: (cd1:isp1:0:5:0): lost device Nov 6 21:46:35 miata /kernel: (cd1:isp1:0:5:0): removing device entry Nov 6 21:48:37 miata login: ROOT LOGIN (root) ON console On sym (ncr810 card aka DEC KZPAA): Nov 6 21:38:41 miata /kernel: Waiting 15 seconds for SCSI devices to settle Nov 6 21:38:41 miata /kernel: isp0: 0.6 get user period 0xc offset 0x8 flags 0x fd00 Nov 6 21:38:41 miata /kernel: isp0: 0.6 get current period 0x19 offset 0x0 flag s 0xc500 Nov 6 21:38:41 miata /kernel: isp0: 0.6 set current period 0xc offset 0x8 flags 0xd500 Nov 6 21:38:41 miata /kernel: isp0: 0.0 get user period 0xc offset 0x8 flags 0x fd00 Nov 6 21:38:41 miata /kernel: isp0: 0.0 get current period 0x19 offset 0x0 flag s 0xc500 Nov 6 21:38:41 miata /kernel: isp0: 0.0 set current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:38:41 miata /kernel: isp0: 0.1 get user period 0xc offset 0x8 flags 0x fd00 Nov 6 21:38:41 miata /kernel: isp0: 0.1 get current period 0x19 offset 0x0 flag s 0xc500 Nov 6 21:38:41 miata /kernel: isp0: 0.1 set current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:38:41 miata /kernel: isp0: 0.2 get user period 0xc offset 0x8 flags 0x fd00 Nov 6 21:38:41 miata /kernel: isp0: 0.2 get current period 0x19 offset 0x0 flag s 0xc500 Nov 6 21:38:41 miata /kernel: isp0: 0.2 set current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:38:41 miata /kernel: Mounting root from ufs:/dev/da1a Nov 6 21:38:41 miata /kernel: da0 at isp0 bus 0 target 0 lun 0 Nov 6 21:38:41 miata /kernel: da0: Fixed Direct Access SCSI-2 device Nov 6 21:38:41 miata /kernel: isp0: 0.0 get current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:38:41 miata /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 8, 1 6bit), Tagged Queueing Enabled Nov 6 21:38:41 miata /kernel: da0: 4095MB (8388314 512 byte sectors: 255H 63S/T 522C) Nov 6 21:38:41 miata /kernel: da2 at isp0 bus 0 target 2 lun 0 Nov 6 21:38:42 miata /kernel: da2: Fixed Direct Access S CSI-2 device Nov 6 21:38:42 miata /kernel: isp0: 0.2 get current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:38:42 miata /kernel: da2: 40.000MB/s transfers (20.000MHz, offset 8, 1 6bit), Tagged Queueing Enabled Nov 6 21:38:42 miata /kernel: da2: 8715MB (17850000 512 byte sectors: 255H 63S/ T 1111C) Nov 6 21:38:42 miata /kernel: da1 at isp0 bus 0 target 1 lun 0 Nov 6 21:38:42 miata /kernel: da1: Fixed Direct Access S CSI-2 device Nov 6 21:38:42 miata /kernel: isp0: 0.1 get current period 0xc offset 0x8 flags 0xfd00 Nov 6 21:38:42 miata /kernel: da1: 40.000MB/s transfers (20.000MHz, offset 8, 1 6bit), Tagged Queueing Enabled Nov 6 21:38:42 miata /kernel: da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): got CAM status 0x50 Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): fatal error, failed to attach t o device Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): lost device Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): removing device entry Nov 6 21:38:42 miata /kernel: cd1 at sym0 bus 0 target 5 lun 0 Nov 6 21:38:42 miata /kernel: cd1: Removable CD -ROM SCSI-2 device Nov 6 21:38:42 miata /kernel: cd1: 4.237MB/s transfers (4.237MHz, offset 8) Nov 6 21:38:42 miata /kernel: cd1: Attempt to query device size failed: NOT REA DY, Medium not present So: it appears that isp is acting differently than sym. Where sym appears to DTRT. Note that there are multiple Qlogics in the system, don't get confused. Wilko -- 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 Mon Nov 6 12:59:36 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3EE4C37B479; Mon, 6 Nov 2000 12:59:32 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA06578; Mon, 6 Nov 2000 13:59:17 -0700 (MST) (envelope-from ken) Date: Mon, 6 Nov 2000 13:59:17 -0700 From: "Kenneth D. Merry" To: Wilko Bulte Cc: mjacob@freebsd.org, FreeBSD-alpha mailing list , justin@freebsd.org Subject: Re: SCSI cdrom attach problems on 4-stable Message-ID: <20001106135917.A6554@panzer.kdm.org> References: <20001104200119.A13502@freebie.demon.nl> <20001104133216.A11678@panzer.kdm.org> <20001104230717.B14074@freebie.demon.nl> <20001104172952.B12998@panzer.kdm.org> <20001105112307.A16448@freebie.demon.nl> <20001105142209.B19227@panzer.kdm.org> <20001106205915.A2151@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001106205915.A2151@freebie.demon.nl>; from wkb@freebie.demon.nl on Mon, Nov 06, 2000 at 08:59:15PM +0100 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 06, 2000 at 20:59:15 +0100, Wilko Bulte wrote: > On Sun, Nov 05, 2000 at 02:22:09PM -0700, Kenneth D. Merry wrote: > > On Sun, Nov 05, 2000 at 11:23:07 +0100, Wilko Bulte wrote: > > > On Sat, Nov 04, 2000 at 05:29:52PM -0700, Kenneth D. Merry wrote: > > > > On Sat, Nov 04, 2000 at 23:07:17 +0100, Wilko Bulte wrote: > > > > > On Sat, Nov 04, 2000 at 01:32:17PM -0700, Kenneth D. Merry wrote: > > > > > > There are several things to try here. > > > > > > > > > Common is a Qlogic card, so driven by isp. Matt, any comments? > > > > > > > > Do you have another type of controller handy that you could plug the drive > > > > into? That might help isolate the problem. > > > > > > I'll see what I can do. > > > > That's probably our best bet for isolating the problem. This is a problem > > somewhere below the CD driver, but I'm not sure where. > > Ok. I hooked up an external CD drive. This one reports as Toshiba (but is a > RRD45 with it's jumper not set to DEC inquiry string). > > (sorry for the wrap) > > On isp: [ ... ] > Nov 6 21:46:35 miata /kernel: (cd0:isp0:0:6:0): got CAM status 0x50 > Nov 6 21:46:35 miata /kernel: (cd0:isp0:0:6:0): fatal error, failed to > attach t > o device > Nov 6 21:46:35 miata /kernel: (cd0:isp0:0:6:0): lost device > Nov 6 21:46:35 miata /kernel: (cd0:isp0:0:6:0): removing device entry > Nov 6 21:46:35 miata /kernel: (cd1:isp1:0:5:0): got CAM status 0x50 > Nov 6 21:46:35 miata /kernel: (cd1:isp1:0:5:0): fatal error, failed to > attach t > o device > Nov 6 21:46:35 miata /kernel: (cd1:isp1:0:5:0): lost device > Nov 6 21:46:35 miata /kernel: (cd1:isp1:0:5:0): removing device entry > Nov 6 21:48:37 miata login: ROOT LOGIN (root) ON console > > > On sym (ncr810 card aka DEC KZPAA): [ ... ] > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): got CAM status 0x50 > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): fatal error, failed to > attach t > o device > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): lost device > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): removing device entry > Nov 6 21:38:42 miata /kernel: cd1 at sym0 bus 0 target 5 lun 0 > Nov 6 21:38:42 miata /kernel: cd1: > Removable CD > -ROM SCSI-2 device > Nov 6 21:38:42 miata /kernel: cd1: 4.237MB/s transfers (4.237MHz, offset 8) > Nov 6 21:38:42 miata /kernel: cd1: Attempt to query device size failed: NOT > REA > DY, Medium not present > > > So: it appears that isp is acting differently than sym. Where sym appears to > DTRT. Note that there are multiple Qlogics in the system, don't get > confused. Yep, this looks like a controller issue. Matt? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 6 13:11:57 2000 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 0F73737B4D7 for ; Mon, 6 Nov 2000 13:11:53 -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 eA6LBio05731 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Mon, 6 Nov 2000 22:11:46 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eA6LBUi09735; Mon, 6 Nov 2000 22:11:34 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id eA6LBT944399; Mon, 6 Nov 2000 22:11:30 +0100 (CET) (envelope-from ticso) Date: Mon, 6 Nov 2000 22:11:29 +0100 From: Bernd Walter To: alpha@FreeBSD.ORG Cc: Matthew Jacob Subject: Re: Status of -CURRENT on PC164? Message-ID: <20001106221129.A44361@cicely8.cicely.de> References: <20001106041949.A11350@dragon.nuxi.com> <20001106114150.G11350@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20001106114150.G11350@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Mon, Nov 06, 2000 at 11:41:50AM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 06, 2000 at 11:41:50AM -0800, David O'Brien wrote: > On Mon, Nov 06, 2000 at 08:08:59AM -0800, Matthew Jacob wrote: > > It's not John's problem to get people to help- John's done the right > > thing within the constraints of the initial design that Doug left in > > place. > > Ok, then which FreeBSD developer that took responsibility for this code > hasn't been looking into the issue? AFAIK those that have been working > on this code don't know what is going on with the PC164. I do know there > are some debugging macros, etc. that one can run that may help give some > idea what is going on. A nice "request for output" email with a few > instructions of how to get the debug info wouldn't hurt IMHO. John already mentioned this here and AFAIK there is nothing new to say about it. Basicly everyone has the same problem and the same output using the macros. I'm quite shure that the result of this phaenomen is well known, but the current aproach unfortunately did not show the reason. The question is what is more important: The debug code that John builds (which may help finding our and future problems) or starring at the PC164 problem. -- 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 Mon Nov 6 13:50:31 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id AB32A37B4D7 for ; Mon, 6 Nov 2000 13:50:29 -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 NAA00905 for ; Mon, 6 Nov 2000 13:50:29 -0800 Date: Mon, 6 Nov 2000 13:50:29 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@FreeBSD.ORG Subject: Re: Status of -CURRENT on PC164? In-Reply-To: <20001106114150.G11350@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 Mon, 6 Nov 2000, David O'Brien wrote: > On Mon, Nov 06, 2000 at 08:08:59AM -0800, Matthew Jacob wrote: > > It's not John's problem to get people to help- John's done the right > > thing within the constraints of the initial design that Doug left in > > place. > > Ok, then which FreeBSD developer that took responsibility for this code Responsibility w/o authority is an anathema. > hasn't been looking into the issue? AFAIK those that have been working > on this code don't know what is going on with the PC164. I do know there > are some debugging macros, etc. that one can run that may help give some > idea what is going on. A nice "request for output" email with a few > instructions of how to get the debug info wouldn't hurt IMHO. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 6 14:12:51 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3A08437B4CF; Mon, 6 Nov 2000 14:12:48 -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 OAA01077; Mon, 6 Nov 2000 14:12:14 -0800 Date: Mon, 6 Nov 2000 14:12:13 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Wilko Bulte , FreeBSD-alpha mailing list , scsi@FreeBSD.ORG Subject: Re: SCSI cdrom attach problems on 4-stable In-Reply-To: <20001106135917.A6554@panzer.kdm.org> 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 [ not an alpha specific issue ] > [ ... ] > > > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): got CAM status 0x50 > > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): fatal error, failed to > > attach t > > o device > > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): lost device > > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): removing device entry > Yep, this looks like a controller issue. Matt? I've seen this before a couple of times. Don't know what the actual issue is. I can tell you that it may not get fixed for 4.2 (ENOTIME). Wilko- file a PR and keep poking me, okay? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 6 14:23: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 0806637B4D7; Mon, 6 Nov 2000 14:22:58 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13sufI-0003WP-00; Mon, 06 Nov 2000 22:22:57 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eA6LQKo02937; Mon, 6 Nov 2000 22:26:20 +0100 (CET) (envelope-from wkb) Date: Mon, 6 Nov 2000 22:26:20 +0100 From: Wilko Bulte To: Matthew Jacob Cc: "Kenneth D. Merry" , FreeBSD-alpha mailing list , scsi@FreeBSD.ORG Subject: Re: SCSI cdrom attach problems on 4-stable Message-ID: <20001106222620.A2796@freebie.demon.nl> References: <20001106135917.A6554@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Mon, Nov 06, 2000 at 02:12:13PM -0800 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 06, 2000 at 02:12:13PM -0800, Matthew Jacob wrote: > > [ not an alpha specific issue ] > > > [ ... ] > > > > > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): got CAM status 0x50 > > > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): fatal error, failed to > > > attach t > > > o device > > > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): lost device > > > Nov 6 21:38:42 miata /kernel: (cd0:isp0:0:6:0): removing device entry > > > Yep, this looks like a controller issue. Matt? > > > I've seen this before a couple of times. Don't know what the actual issue is. > I can tell you that it may not get fixed for 4.2 (ENOTIME). Wilko- file a PR > and keep poking me, okay? send-pr-ed just a minute ago. Time permitting I'll try to dig into it a bit more. Don't hold your breath.. -- 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 Mon Nov 6 14:30: 6 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 20E3537B4CF for ; Mon, 6 Nov 2000 14:30:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id OAA71577; Mon, 6 Nov 2000 14:30:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id A73D537B4E5 for ; Mon, 6 Nov 2000 14:21:44 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13sue7-0003V4-00 for FreeBSD-gnats-submit@freebsd.org; Mon, 06 Nov 2000 22:21:43 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eA6LP6T02919; Mon, 6 Nov 2000 22:25:06 +0100 (CET) (envelope-from wkb) Message-Id: <200011062125.eA6LP6T02919@freebie.demon.nl> Date: Mon, 6 Nov 2000 22:25:06 +0100 (CET) From: wilko@freebsd.org Reply-To: wilko@freebsd.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: alpha/22650: SCSI CD drives not attached on boot on isp driver Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 22650 >Category: alpha >Synopsis: SCSI CD drives not attached on boot on isp driver >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 06 14:30:00 PST 2000 >Closed-Date: >Last-Modified: >Originator: Wilko Bulte >Release: FreeBSD 4-stable on alpha >Organization: Private FreeBSD site - The Netherlands >Environment: Alpha with isp driven adapter and SCSI cdrom. DEC RRD4[56] does reproduce well. >Description: Typical error is: da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) (cd0:isp0:0:6:0): got CAM status 0x50 (cd0:isp0:0:6:0): fatal error, failed to attach to device (cd0:isp0:0:6:0): lost device (cd0:isp0:0:6:0): removing device entry Same hardware but using sym driven ncr810 works OK. Please refer to mail thread with: Subject: SCSI cdrom attach problems on 4-stable Message-ID: <20001104200119.A13502@freebie.demon.nl> posted on -alpha at Nov 4, 2000 This contains multiple log / experiments. >How-To-Repeat: See above >Fix: Use other adapter than isp-drive one. Alternatively keeping a CD in the drive appears to help. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Nov 6 14:35:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id F027A37B479; Mon, 6 Nov 2000 14:35:48 -0800 (PST) Received: (from mjacob@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id OAA72167; Mon, 6 Nov 2000 14:35:48 -0800 (PST) (envelope-from mjacob@FreeBSD.org) Date: Mon, 6 Nov 2000 14:35:48 -0800 (PST) From: Message-Id: <200011062235.OAA72167@freefall.freebsd.org> To: mjacob@FreeBSD.org, freebsd-alpha@freebsd.org, mjacob@FreeBSD.org Subject: Re: alpha/22650: SCSI CD drives not attached on boot on isp driver Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: SCSI CD drives not attached on boot on isp driver Responsible-Changed-From-To: freebsd-alpha->mjacob Responsible-Changed-By: mjacob Responsible-Changed-When: Mon Nov 6 14:35:41 PST 2000 Responsible-Changed-Why: mine. . http://www.freebsd.org/cgi/query-pr.cgi?pr=22650 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 7 9:18:17 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2ECE837B4C5; Tue, 7 Nov 2000 09:18:03 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA11225; Tue, 7 Nov 2000 09:18:01 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 07 Nov 2000 09:18:01 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: stable@freebsd.org Subject: Is sockstat broken in -stable? Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On a -stable system from October 31, I'm seeing this from sockstat: alpha$ sockstat USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root sshd 13195 5 ? ? ? root sshd 13160 5 ? ? ? root sshd 132 4 ? ? ? root lpd 125 6 ? ? ? root inetd 120 4 ? ? ? root inetd 120 5 ? ? ? root inetd 120 6 ? ? ? root inetd 120 7 ? ? ? root amd 106 4 ? ? ? root amd 106 5 ? ? ? root amd 106 6 ? ? ? root amd 106 7 ? ? ? daemon portmap 91 3 ? ? ? daemon portmap 91 4 ? ? ? root ntpd 89 4 ? ? ? root ntpd 89 5 ? ? ? root ntpd 89 6 ? ? ? root syslogd 82 4 ? ? ? USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root sshd 132 3 ? ? ? root inetd 120 8 ? ? ? root inetd 120 9 ? ? ? USER COMMAND PID FD PROTO ADDRESS root sshd 13195 6 stream ? root sshd 13160 6 stream ? root sendmail 128 3 dgram ? root lpd 125 3 dgram ? root lpd 125 5 stream ? root cron 122 4 dgram ? root amd 106 3 dgram ? root ntpd 89 3 dgram ? root syslogd 82 3 dgram ? Userland and kernel are in sync. This is on an Alpha, though I don't know whether that's significant or not. Is anybody else seeing this problem? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Nov 7 10: 3:16 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from venus.sunquest.com (venus.sunquest.COM [149.138.10.114]) by hub.freebsd.org (Postfix) with ESMTP id 5F56037B479 for ; Tue, 7 Nov 2000 10:03:14 -0800 (PST) Received: (from terry@localhost) by venus.sunquest.com (8.10.1/8.10.1) id eA7I3E100764 for freebsd-alpha@freebsd.org; Tue, 7 Nov 2000 11:03:14 -0700 Date: Tue, 7 Nov 2000 11:03:14 -0700 From: "Terry R. Friedrichsen" Message-Id: <200011071803.eA7I3E100764@venus.sunquest.com> To: freebsd-alpha@freebsd.org Subject: window manager probs Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I hope this isn't the wrong place for this, but I see no other Alpha- specific group, and I'm fairly certain this is an Alpha-specific problem. Which window manager do y'all use under FreeBSD/alpha (or /AXP, as it says on the CDs)? I'm trying to use vtwm, but it has problems; I see by the mailing list archive (in a year-old message) that the problems have been reported previously, but under a *different* window manager (afterstep, which I hadn't heard of before). (I just installed FreeBSD/alpha version 4.1 with XFree86 3.3.6 on an AlphaStation 255/233 with an S3 ViRGE/DX 4 MB video board.) It would appear that the problems are actually XFree86 problems, unless several different window managers do things in the same incorrect way. Does anyone use FreeBSD/alpha as an X platform? Which window managers are known to work/not work well? Thanks for any help. Terry R. Friedrichsen terry@venus.sunquest.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 8 0:22: 0 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dd-mail-smtp.dk.damgaard.com (client.dk.damgaard.com [213.237.136.126]) by hub.freebsd.org (Postfix) with SMTP id 9779837B4C5 for ; Wed, 8 Nov 2000 00:21:57 -0800 (PST) Received: from 213.237.137.2 by dd-mail-smtp.dk.damgaard.com (InterScan E-Mail VirusWall NT); Wed, 08 Nov 2000 09:21:49 +0100 (Romance Standard Time) Received: by dd-mail-smtp.dk.damgaard.com with Internet Mail Service (5.5.2650.21) id ; Wed, 8 Nov 2000 09:21:49 +0100 Message-ID: <5ED89301AE60D311AAD500508B0EF55F50E0A7@dd-mail.intern.dd.dk> From: Bjarne Blichfeldt To: freebsd-alpha@freebsd.org Subject: RE: window manager probs Date: Wed, 8 Nov 2000 09:16:36 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My current environment at work : Miata 500au, ELSA Gloria Synergi video card, FreeBSD -stable XFree86 4.0.1 KDE 1.1.2 I have also used fvwm2 and icewm, and have never had any problems, at least not related to windowmanagers. mvh, Bjarne Blichfeldt -----Original Message----- From: Terry R. Friedrichsen [mailto:terry@venus.sunquest.com] Sent: 7. november 2000 19:03 To: freebsd-alpha@freebsd.org Subject: window manager probs I hope this isn't the wrong place for this, but I see no other Alpha- specific group, and I'm fairly certain this is an Alpha-specific problem. Which window manager do y'all use under FreeBSD/alpha (or /AXP, as it says on the CDs)? I'm trying to use vtwm, but it has problems; I see by the mailing list archive (in a year-old message) that the problems have been reported previously, but under a *different* window manager (afterstep, which I hadn't heard of before). (I just installed FreeBSD/alpha version 4.1 with XFree86 3.3.6 on an AlphaStation 255/233 with an S3 ViRGE/DX 4 MB video board.) It would appear that the problems are actually XFree86 problems, unless several different window managers do things in the same incorrect way. Does anyone use FreeBSD/alpha as an X platform? Which window managers are known to work/not work well? Thanks for any help. Terry R. Friedrichsen terry@venus.sunquest.com 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 Nov 8 2:41:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from grafin.fujimori.cache.waseda.ac.jp (grafin.fujimori.cache.waseda.ac.jp [133.9.152.154]) by hub.freebsd.org (Postfix) with ESMTP id 2CE0637B479 for ; Wed, 8 Nov 2000 02:41:35 -0800 (PST) Received: from grafin.fujimori.cache.waseda.ac.jp (fujimori@localhost [127.0.0.1]) by grafin.fujimori.cache.waseda.ac.jp (8.9.3/3.7W) with ESMTP id TAA05972 for ; Wed, 8 Nov 2000 19:40:54 +0900 Message-Id: <200011081040.TAA05972@grafin.fujimori.cache.waseda.ac.jp> To: freebsd-alpha@freebsd.org Subject: J30 settings for AlphaPC164/500 Date: Wed, 08 Nov 2000 19:40:54 +0000 From: Yoriaki FUJIMORI Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear folks, Recently I got a second-hand AlphaPC164/500MHz motherboard. It was almost a junk, but anyway I found it works with SRM. But, I cannot figure out how to set the J30 jumpers for 500MHz cpu clock---IRQ0,IRQ1,IRQ2 and IRQ3. # I have got a manual for 433MHz AlphaPC164. So, I could configure the jumpers for 433MHz (ratio 13). I guess there should be a possibility for setting ratio 14 or 15. Can some kind soul send me the information or pointers for that? Thank you for your attention. Best wishes, Yoriaki Fujimori To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 8 4:14: 3 2000 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 8035237B4C5 for ; Wed, 8 Nov 2000 04:14:00 -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 eA8CDfp28043 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Wed, 8 Nov 2000 13:13:44 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0::104:200:92ff:fe9b:20e7]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eA8CDNj17965 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Wed, 8 Nov 2000 13:13:29 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id eA8CDNA02053; Wed, 8 Nov 2000 13:13:23 +0100 (CET) (envelope-from ticso) Date: Wed, 8 Nov 2000 13:13:22 +0100 From: Bernd Walter To: Yoriaki FUJIMORI Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: J30 settings for AlphaPC164/500 Message-ID: <20001108131322.A2030@cicely5.cicely.de> References: <200011081040.TAA05972@grafin.fujimori.cache.waseda.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200011081040.TAA05972@grafin.fujimori.cache.waseda.ac.jp>; from fujimori@grafin.fujimori.cache.waseda.ac.jp on Wed, Nov 08, 2000 at 07:40:54PM +0000 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Nov 08, 2000 at 07:40:54PM +0000, Yoriaki FUJIMORI wrote: > Dear folks, > Recently I got a second-hand AlphaPC164/500MHz motherboard. > It was almost a junk, but anyway I found it works with SRM. > But, I cannot figure out how to set the J30 jumpers for > 500MHz cpu clock---IRQ0,IRQ1,IRQ2 and IRQ3. > # I have got a manual for 433MHz AlphaPC164. So, I could configure > the jumpers for 433MHz (ratio 13). > > I guess there should be a possibility for setting ratio 14 or 15. > Can some kind soul send me the information or pointers for that? > Thank you for your attention. > Best wishes, > Yoriaki Fujimori The documentation is missleading as you need to exchange the Oscilator which need to have the 10th of the CPU clock. I never saw that the Jumpers have any functionality. Originally you get a set of oscilators with the board. -- 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 Wed Nov 8 5:20:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freyr.cba.ualr.edu (freyr.cba.ualr.edu [144.167.120.20]) by hub.freebsd.org (Postfix) with ESMTP id 3247537B479 for ; Wed, 8 Nov 2000 05:20:38 -0800 (PST) Received: (from joe@localhost) by freyr.cba.ualr.edu (8.11.1/8.11.1) id eA8DKUG01921; Wed, 8 Nov 2000 07:20:30 -0600 (CST) (envelope-from joe) Date: Wed, 8 Nov 2000 07:20:29 -0600 From: "Joseph E. Royce" To: terry@venus.sunquest.com Cc: freebsd-alpha@freebsd.org Subject: Re: window manager probs Message-ID: <20001108072029.A1899@freyr.cba.ualr.edu> References: <5ED89301AE60D311AAD500508B0EF55F50E0A7@dd-mail.intern.dd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <5ED89301AE60D311AAD500508B0EF55F50E0A7@dd-mail.intern.dd.dk>; from bbl@dk.damgaard.com on Wed, Nov 08, 2000 at 09:16:36AM +0100 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Nov 08, 2000 at 09:16:36AM +0100, Bjarne Blichfeldt wrote: > My current environment at work : > > Miata 500au, ELSA Gloria Synergi video card, > FreeBSD -stable > XFree86 4.0.1 > KDE 1.1.2 > > I have also used fvwm2 and icewm, and have never had any problems, at > least not related to windowmanagers. > > > mvh, > Bjarne Blichfeldt > I use Windowmaker and tried vtwm and they both work fine with XFree86 3.3.6. My system is a PC164 and a Oxygen ACX video card. > > > -----Original Message----- > From: Terry R. Friedrichsen [mailto:terry@venus.sunquest.com] > Sent: 7. november 2000 19:03 > To: freebsd-alpha@freebsd.org > Subject: window manager probs > > > > I hope this isn't the wrong place for this, but I see no other Alpha- > specific group, and I'm fairly certain this is an Alpha-specific problem. > > Which window manager do y'all use under FreeBSD/alpha (or /AXP, as it says > on the CDs)? I'm trying to use vtwm, but it has problems; I see by the > mailing list archive (in a year-old message) that the problems have been > reported previously, but under a *different* window manager (afterstep, > which I hadn't heard of before). > > (I just installed FreeBSD/alpha version 4.1 with XFree86 3.3.6 on an > AlphaStation 255/233 with an S3 ViRGE/DX 4 MB video board.) > > It would appear that the problems are actually XFree86 problems, unless > several different window managers do things in the same incorrect way. > > Does anyone use FreeBSD/alpha as an X platform? Which window managers > are known to work/not work well? > > Thanks for any help. > > Terry R. Friedrichsen > > terry@venus.sunquest.com > > > 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 Wed Nov 8 7: 7:31 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from venus.sunquest.com (venus.sunquest.COM [149.138.10.114]) by hub.freebsd.org (Postfix) with ESMTP id 36B5F37B4C5 for ; Wed, 8 Nov 2000 07:07:29 -0800 (PST) Received: (from terry@localhost) by venus.sunquest.com (8.10.1/8.10.1) id eA8F7RE02797 for freebsd-alpha@freebsd.org; Wed, 8 Nov 2000 08:07:27 -0700 Date: Wed, 8 Nov 2000 08:07:27 -0700 From: "Terry R. Friedrichsen" Message-Id: <200011081507.eA8F7RE02797@venus.sunquest.com> To: freebsd-alpha@freebsd.org Subject: re: window manager probs Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wrote, asking about window managers for FreeBSD/alpha, because vtwm was failing miserably ... joe@freyr.cba.ualr.edu responded: > I use Windowmaker and tried vtwm and they both work fine with XFree86 3.3.6. > My system is a PC164 and a Oxygen ACX video card. Indeed, the problem does not appear to lie with vtwm itself. I can use the FreeBSD/alpha vtwm as the window manager for my Ultrix machine (running MIT X11R6) and it works just fine. So it looks as though the genesis of the problem is within XFree86 itself somewhere. Terry R. Friedrichsen terry@venus.sunquest.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 8 7:38: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freyr.cba.ualr.edu (freyr.cba.ualr.edu [144.167.120.20]) by hub.freebsd.org (Postfix) with ESMTP id 4E29A37B479 for ; Wed, 8 Nov 2000 07:38:00 -0800 (PST) Received: (from joe@localhost) by freyr.cba.ualr.edu (8.11.1/8.11.1) id eA8Fbt802226; Wed, 8 Nov 2000 09:37:55 -0600 (CST) (envelope-from joe) Date: Wed, 8 Nov 2000 09:37:55 -0600 From: "Joseph E. Royce" To: "Terry R. Friedrichsen" Cc: freebsd-alpha@freebsd.org Subject: Re: FreeBSD/alpha wm problems Message-ID: <20001108093755.A2161@freyr.cba.ualr.edu> References: <200011081512.eA8FCom02819@venus.sunquest.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200011081512.eA8FCom02819@venus.sunquest.com>; from terry@venus.sunquest.com on Wed, Nov 08, 2000 at 08:12:50AM -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Nov 08, 2000 at 08:12:50AM -0700, Terry R. Friedrichsen wrote: > Joe, > > Thanks for responding to my post about vtwm problems. I am using vtwm (I've > tried 5.3 and 5.4.5a) with XFree86 3.3.6 under FreeBSD/AXP 4.1 on an Alpha > Station 255/233. > > What X server are you using with the Oxygen ACX? And what version of vtwm > are you using? > > I'm on an S3 ViRGE/DX card - I hope that's not the source of my trouble. > > Thanks again. > > Terry R. Friedrichsen > > terry@venus.sunquest.com THe Oxygen ACX is a Permedia 2 based card so I am using the 3DLabs server. Origionally, I had a S3 card using the SVGA server and had no problems as well; I installed XFree86 from the ports. I installed the lastest vtwm (I guess 5.4.5a) from the ports yesterday to test it out and it worked fine. Can you be a little more specific on what problems you are having so that we may be able to determine if we can help you.Including error messages would help. -Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 8 7:51:18 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from venus.sunquest.com (venus.sunquest.COM [149.138.10.114]) by hub.freebsd.org (Postfix) with ESMTP id 1894137B479 for ; Wed, 8 Nov 2000 07:51:16 -0800 (PST) Received: (from terry@localhost) by venus.sunquest.com (8.10.1/8.10.1) id eA8FpCS02896 for freebsd-alpha@freebsd.org; Wed, 8 Nov 2000 08:51:12 -0700 Date: Wed, 8 Nov 2000 08:51:12 -0700 From: "Terry R. Friedrichsen" Message-Id: <200011081551.eA8FpCS02896@venus.sunquest.com> To: freebsd-alpha@freebsd.org Subject: re: FreeBSD/alpha wm problems Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can you be a little more specific on what > problems you are having so that we may be able to determine if > we can help you.Including error messages would help. OK. I wasn't really expecting X help from this list, which is why I hadn't detailed the problems earlier ... There are LOTS of problems, other than drawing glitches where a slice of the display maybe 5 pixels high or so gets drawn in the wrong place on the screen ... I'll just mention a few. 1) if you iconify an xterm that overlies another xterm, when you deiconify it, the part of its background that overlaid the other xterm is permanently switched to the overlaid xterm's color 2) if you bring up a root menu (by clicking on the background), only a transparent rectangle gets drawn (with the background showing through); dragging the mouse pointer through the menu rectangle paints the menu as the pointer hits each menu row 3) if said root menu overlaps an xterm, the overlapping chunk of root becomes the background of that piece of the xterm window There are others ... I saw the exact same problems reported in the freebsd-alpha mailing list archives about a year ago. I get the stripe of titlebar color in twm that is mentioned below, too - but that goes away if you "sleep 2" before firing up twm ... ---------------------------------------------------------------------- --dxRQSzdsN/lOP445 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On Mon, Oct 04, 1999 at 10:23:12AM +0100, Doug Rabson wrote: > On Sun, 3 Oct 1999, Dave wrote: >=20 > >=20 > > Getting the same sorts of problems; System is a PC164SX w/a Diamond > > Stealth 3D 2000...under twm got wierd stripes of titlebar color in > > some resolution modes..fvwm2 looked fine but I couldn't move windows... > > afterstep is prety mellow but the toolbar is a set of solid black > > boxes lined up on the side of the screen, but clicking on one of > > them launches xterms :> If I click and produce the application > > laucher menu over an xterm the menu becomes the new permanent > > background of the xterm... ---------------------------------------------------------------------- Terry R. Friedrichsen terry@venus.sunquest.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 8 7:57: 2 2000 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 9377037B4C5 for ; Wed, 8 Nov 2000 07:56:59 -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 <01JWAZBMTHMS000Y86@research.kpn.com> for freebsd-alpha@FreeBSD.ORG; Wed, 8 Nov 2000 16:56:56 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Wed, 08 Nov 2000 16:56:55 +0100 Content-return: allowed Date: Wed, 08 Nov 2000 16:56:54 +0100 From: "Koster, K.J." Subject: RE: FreeBSD/alpha wm problems To: "'Terry R. Friedrichsen'" Cc: freebsd-alpha@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D79D5@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I saw the exact same problems reported in the freebsd-alpha > mailing list > archives about a year ago. I get the stripe of titlebar color > in twm that is mentioned below, too - but that goes away if you > "sleep 2" before firing up twm ... > I've seen this kind of stuff on x86 PC's when XFree86 did not probe the video RAM correctly. In particular when XFree86 thinks it has more than there really is. Does XFree86 autoprobe the RAM or do you specify it yourself? If you specified it, try autoprobing it instead. Are you *absolutely sure* that's how much RAM is on the graphics board? I fell into this one when an unnamed supplier gave me a board with only half the RAM it said on the box... 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 Wed Nov 8 8:30:30 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from venus.sunquest.com (venus.sunquest.COM [149.138.10.114]) by hub.freebsd.org (Postfix) with ESMTP id C636937B479 for ; Wed, 8 Nov 2000 08:30:28 -0800 (PST) Received: (from terry@localhost) by venus.sunquest.com (8.10.1/8.10.1) id eA8GUSM02977 for freebsd-alpha@freebsd.org; Wed, 8 Nov 2000 09:30:28 -0700 Date: Wed, 8 Nov 2000 09:30:28 -0700 From: "Terry R. Friedrichsen" Message-Id: <200011081630.eA8GUSM02977@venus.sunquest.com> To: freebsd-alpha@freebsd.org Subject: re: FreeBSD/alpha wm problems Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Are you *absolutely sure* that's how much RAM is on the graphics board? X -probeonly reports 4096k of video RAM (I'm using the SVGA server, BTW ...). However, the VideoRam line is commented out of the "Devices" section of /etc/XF86Config - should I uncomment it (it says 4096, too)? Thanks. Terry R. Friedrichsen terry@venus.sunquest.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 8 8:50:19 2000 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 71FB137B4C5 for ; Wed, 8 Nov 2000 08:50:17 -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 LAA18853; Wed, 8 Nov 2000 11:50:16 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eA8GoGM15337; Wed, 8 Nov 2000 11:50:16 -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: Wed, 8 Nov 2000 11:50:16 -0500 (EST) To: "Terry R. Friedrichsen" Cc: freebsd-alpha@FreeBSD.ORG Subject: re: FreeBSD/alpha wm problems In-Reply-To: <200011081630.eA8GUSM02977@venus.sunquest.com> References: <200011081630.eA8GUSM02977@venus.sunquest.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14857.33822.127584.556860@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Terry R. Friedrichsen writes: > > > Are you *absolutely sure* that's how much RAM is on the graphics board? > > X -probeonly reports 4096k of video RAM (I'm using the SVGA server, BTW ...). > > However, the VideoRam line is commented out of the "Devices" section of > /etc/XF86Config - should I uncomment it (it says 4096, too)? Try uncommenting it and telling it you have 2MB (2048). Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Nov 8 9:20: 0 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from venus.sunquest.com (venus.sunquest.COM [149.138.10.114]) by hub.freebsd.org (Postfix) with ESMTP id 3E10D37B4CF for ; Wed, 8 Nov 2000 09:19:58 -0800 (PST) Received: (from terry@localhost) by venus.sunquest.com (8.10.1/8.10.1) id eA8HJv903109 for freebsd-alpha@freebsd.org; Wed, 8 Nov 2000 10:19:57 -0700 Date: Wed, 8 Nov 2000 10:19:57 -0700 From: "Terry R. Friedrichsen" Message-Id: <200011081719.eA8HJv903109@venus.sunquest.com> To: freebsd-alpha@freebsd.org Subject: re: FreeBSD/alpha wm problems Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For the record on this, twm does not have the problem with iconify/deiconify getting the wrong background when windows overlap. However, twm *does* have the problem that the menu brought up by clicking on the root background draws initially as a transparent rectangle. Otherwise, it exhibits all the same problems I reported with vtwm. Forcing the video RAM to half-size had no effect on the problem. Thanks for all the help; I'll try windowmaker and see what happens next ... Terry R. Friedrichsen terry@venus.sunquest.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 3: 0: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 01F5F37B4C5 for ; Thu, 9 Nov 2000 03:00:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id DAA06028; Thu, 9 Nov 2000 03:00:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 2C8DB37B4C5 for ; Thu, 9 Nov 2000 02:57:21 -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 eA9AvHX04744 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Thu, 9 Nov 2000 11:57:19 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0::104:200:92ff:fe9b:20e7]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eA9Av6j22047 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO) for ; Thu, 9 Nov 2000 11:57:09 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id eA9Av1d03968; Thu, 9 Nov 2000 11:57:01 +0100 (CET) (envelope-from ticso) Message-Id: <200011091057.eA9Av1d03968@cicely5.cicely.de> Date: Thu, 9 Nov 2000 11:57:01 +0100 (CET) From: Bernd Walter Reply-To: ticso@cicely5.cicely.de To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: alpha/22713: minor typo in pci_eb164_intr.s Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 22713 >Category: alpha >Synopsis: minor typo in pci_eb164_intr.s >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 09 03:00:01 PST 2000 >Closed-Date: >Last-Modified: >Originator: >Release: FreeBSD 5.0-CURRENT alpha >Organization: >Environment: System: FreeBSD-alpha STABLE and current >Description: in src/sys/alpha/pci/pci_eb164_intr.s both assembly END lines say enable while the later should be disable. >How-To-Repeat: >Fix: correct the typo. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 9: 1:56 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E645E37B479; Thu, 9 Nov 2000 09:01:54 -0800 (PST) Received: (from mjacob@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA62551; Thu, 9 Nov 2000 09:01:54 -0800 (PST) (envelope-from mjacob@FreeBSD.org) Date: Thu, 9 Nov 2000 09:01:54 -0800 (PST) From: Message-Id: <200011091701.JAA62551@freefall.freebsd.org> To: ticso@cicely5.cicely.de, mjacob@FreeBSD.org, freebsd-alpha@freebsd.org Subject: Re: alpha/22713: minor typo in pci_eb164_intr.s Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: minor typo in pci_eb164_intr.s State-Changed-From-To: open->closed State-Changed-By: mjacob State-Changed-When: Thu Nov 9 09:01:40 PST 2000 State-Changed-Why: Fixed. Thanks. http://www.freebsd.org/cgi/query-pr.cgi?pr=22713 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 14:34:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 12EAD37B479; Thu, 9 Nov 2000 14:34:33 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA17164; Thu, 9 Nov 2000 14:34:19 -0800 Date: Thu, 9 Nov 2000 14:34:19 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG Subject: Re: SCSI cdrom attach problems on 4-stable In-Reply-To: <20001106135917.A6554@panzer.kdm.org> 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 updated the PR (22650) with edit-pr, but it doesn't seem to then email submitter/responsible person. The short answer is "f/w breakage(?), don't know how to fix yet". mjacob Wed Nov 8 17:08:53 PST 2000 Okay- here's what is happening- the Qlogic f/w is returning an AUTOSENSE failure- that is, it's unable to automatically run a request sense (reason unknown). So, the CAM status being returned is CAM_AUTOSENSE_FAIL CAM_DEV_QFRZN It's been apparent to me for some time that cam_periph_error should be then running an INQUIRY command in this case. What's particularly obnoxious here is that the CD in question doesn't actually completely detach- that is, it's pass instance stays, but the cd instance won't attach- and this, for some reason, makes it impossible to rescan it later. I don't know why the Qlogic f/w is returning this code, but the fundamental problem here is that CAM is broken. And, no, it's not up to each SIM to run INQUIRY commands themselves if AUTOSENSE fails. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 14:49:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 745A137B4CF; Thu, 9 Nov 2000 14:49:37 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA33921; Thu, 9 Nov 2000 15:49:11 -0700 (MST) (envelope-from ken) Date: Thu, 9 Nov 2000 15:49:11 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable Message-ID: <20001109154911.A33812@panzer.kdm.org> References: <20001106135917.A6554@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Thu, Nov 09, 2000 at 02:34:19PM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 09, 2000 at 14:34:19 -0800, Matthew Jacob wrote: > > I updated the PR (22650) with edit-pr, but it doesn't seem to then email > submitter/responsible person. The short answer is "f/w breakage(?), don't know > how to fix yet". > > mjacob Wed Nov 8 17:08:53 PST 2000 > > Okay- here's what is happening- the Qlogic f/w is returning an AUTOSENSE > failure- that is, it's unable to automatically run a request sense > (reason unknown). So, the CAM status being returned is > > CAM_AUTOSENSE_FAIL > CAM_DEV_QFRZN > > It's been apparent to me for some time that cam_periph_error should be > then running an INQUIRY command in this case. Why an inquiry, if autosense failed? Don't you mean a request sense? > What's particularly obnoxious here is that the CD in question doesn't > actually completely detach- that is, it's pass instance stays, but > the cd instance won't attach- and this, for some reason, makes it > impossible to rescan it later. The reason the device isn't gone is because the pass(4) driver actually attached successfully. The problem is that when there is no CD in the drive, any CDROM drive will return an error in response to a READ CAPACITY command. Since autosense is failing, the cd(4) driver can't tell what sort of error is getting returned (and therefore whether the drive is really accessible), so it won't attach. The pass(4) driver doesn't issue any commands to check the device (it doesn't have any requirements for device functionality beyond the basic probe code), so it attaches without problems. Both drivers are doing the right thing from what I can see. > I don't know why the Qlogic f/w is returning this code, but the fundamental > problem here is that CAM is broken. And, no, it's not up to each SIM to > run INQUIRY commands themselves if AUTOSENSE fails. Don't you mean request sense? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 14:54:52 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 62F4037B4C5; Thu, 9 Nov 2000 14:54:49 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA17249; Thu, 9 Nov 2000 14:54:35 -0800 Date: Thu, 9 Nov 2000 14:54:35 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable In-Reply-To: <20001109154911.A33812@panzer.kdm.org> 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, 9 Nov 2000, Kenneth D. Merry wrote: > On Thu, Nov 09, 2000 at 14:34:19 -0800, Matthew Jacob wrote: > > > > I updated the PR (22650) with edit-pr, but it doesn't seem to then email > > submitter/responsible person. The short answer is "f/w breakage(?), don't know > > how to fix yet". > > > > mjacob Wed Nov 8 17:08:53 PST 2000 > > > > Okay- here's what is happening- the Qlogic f/w is returning an AUTOSENSE > > failure- that is, it's unable to automatically run a request sense > > (reason unknown). So, the CAM status being returned is > > > > CAM_AUTOSENSE_FAIL > > CAM_DEV_QFRZN > > > > It's been apparent to me for some time that cam_periph_error should be > > then running an INQUIRY command in this case. > > Why an inquiry, if autosense failed? Don't you mean a request sense? Sorry. Ooops. Yes. > > > What's particularly obnoxious here is that the CD in question doesn't > > actually completely detach- that is, it's pass instance stays, but > > the cd instance won't attach- and this, for some reason, makes it > > impossible to rescan it later. > > The reason the device isn't gone is because the pass(4) driver actually > attached successfully. The problem is that when there is no CD in the > drive, any CDROM drive will return an error in response to a READ CAPACITY > command. > > Since autosense is failing, the cd(4) driver can't tell what sort of error > is getting returned (and therefore whether the drive is really accessible), > so it won't attach. An AUTOSENSE failing means that a check condition occurred, but no sense data is available. That should, in fact, be treated identically to READ CAPACITY failing because there's no media. > > The pass(4) driver doesn't issue any commands to check the device (it > doesn't have any requirements for device functionality beyond the basic > probe code), so it attaches without problems. > > Both drivers are doing the right thing from what I can see. But a later rescan should see it but it doesm't. And see above. But the high order bit is that the autosense is failing. All other stuff in scsi_cd is is secondary. What's more important is that cam_periph_error or the periph should send a REQUEST SENSE if AUTOSENSE fails- the sim should not be the one doing this. > > > I don't know why the Qlogic f/w is returning this code, but the fundamental > > problem here is that CAM is broken. And, no, it's not up to each SIM to > > run INQUIRY commands themselves if AUTOSENSE fails. > > Don't you mean request sense? Yes, sorry. Brains..... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 14:57:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8555F37B479; Thu, 9 Nov 2000 14:57:53 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA17266; Thu, 9 Nov 2000 14:57:46 -0800 Date: Thu, 9 Nov 2000 14:57:46 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable 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 I should also note, btw, that this doesn't always happen predictably. One 8200 running 4.2 Beta does: (cd0:isp3:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:isp3:0:4:0): NOT READY asc:3a,0 (cd0:isp3:0:4:0): Medium not present cd0 at isp3 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device isp3: 0.4 get current period 0x3e offset 0xc flags 0xd500 cd0: 4.032MB/s transfers (4.032MHz, offset 12) cd0: Attempt to query device size failed: NOT READY, Medium not present da0: invalid primary partition table: no magic While another does: (cd0:isp3:0:4:0): got CAM status 0x50 (cd0:isp3:0:4:0): fatal error, failed to attach to device (cd0:isp3:0:4:0): lost device (cd0:isp3:0:4:0): removing device entry Essentially the same hardware is involved. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 15:13:54 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id BFBF337B479; Thu, 9 Nov 2000 15:13:48 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA34228; Thu, 9 Nov 2000 16:13:38 -0700 (MST) (envelope-from ken) Date: Thu, 9 Nov 2000 16:13:38 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable Message-ID: <20001109161338.A34112@panzer.kdm.org> References: <20001109154911.A33812@panzer.kdm.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Thu, Nov 09, 2000 at 02:54:35PM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Nov 09, 2000 at 14:54:35 -0800, Matthew Jacob wrote: > On Thu, 9 Nov 2000, Kenneth D. Merry wrote: > > On Thu, Nov 09, 2000 at 14:34:19 -0800, Matthew Jacob wrote: > > > What's particularly obnoxious here is that the CD in question doesn't > > > actually completely detach- that is, it's pass instance stays, but > > > the cd instance won't attach- and this, for some reason, makes it > > > impossible to rescan it later. > > > > The reason the device isn't gone is because the pass(4) driver actually > > attached successfully. The problem is that when there is no CD in the > > drive, any CDROM drive will return an error in response to a READ CAPACITY > > command. > > > > Since autosense is failing, the cd(4) driver can't tell what sort of error > > is getting returned (and therefore whether the drive is really accessible), > > so it won't attach. > > An AUTOSENSE failing means that a check condition occurred, but no sense data > is available. That should, in fact, be treated identically to READ CAPACITY > failing because there's no media. Right. > > The pass(4) driver doesn't issue any commands to check the device (it > > doesn't have any requirements for device functionality beyond the basic > > probe code), so it attaches without problems. > > > > Both drivers are doing the right thing from what I can see. > > But a later rescan should see it but it doesm't. And see above. That's how the rescan semantics work. The device only gets announced to the peripheral drivers if it is a new device, or if it has gone away. In this case the device is still there, and still attached to the pass(4) driver. So from the transport layer's perspective, all the peripheral drivers have already seen the device and had a chance to attach or not. > But the high order bit is that the autosense is failing. All other stuff in > scsi_cd is is secondary. > > What's more important is that cam_periph_error or the periph should send a > REQUEST SENSE if AUTOSENSE fails- the sim should not be the one doing this. I agree. It would be interesting to find out what the SCSI status byte is here. I've attached a patch that should print it out. Ken -- Kenneth Merry ken@kdm.org --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_cd.c.scsi_status.20001109" ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_cd.c#13 - /c/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_cd.c ==== *** /tmp/tmp.34213.0 Thu Nov 9 16:12:46 2000 --- /c/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_cd.c Thu Nov 9 16:12:33 2000 *************** *** 1728,1733 **** --- 1728,1735 ---- xpt_print_path(periph->path); printf("got CAM status %#x\n", done_ccb->ccb_h.status); + printf("got SCSI status %#x\n", + done_ccb->csio.scsi_status); } xpt_print_path(periph->path); printf("fatal error, failed" --qMm9M+Fa2AknHoGS-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 15:33:57 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CD07D37B4CF; Thu, 9 Nov 2000 15:33:55 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA17421; Thu, 9 Nov 2000 15:33:48 -0800 Date: Thu, 9 Nov 2000 15:33:47 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable In-Reply-To: <20001109154911.A33812@panzer.kdm.org> 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 It reported: got SCSI status 0x2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 15:37:28 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4A31E37B479; Thu, 9 Nov 2000 15:37:26 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA17442; Thu, 9 Nov 2000 15:37:17 -0800 Date: Thu, 9 Nov 2000 15:37:17 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: "Kenneth D. Merry" , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable 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 Wilko - does your machine that has this problem say: isp0: invalid NVRAM header ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 15:38: 0 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 2F15137B479; Thu, 9 Nov 2000 15:37:58 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eA9Nbea96953; Thu, 9 Nov 2000 16:37:41 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200011092337.eA9Nbea96953@aslan.scsiguy.com> To: mjacob@feral.com Cc: "Kenneth D. Merry" , Wilko Bulte , FreeBSD-alpha mailing list , freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable In-Reply-To: Your message of "Thu, 09 Nov 2000 14:54:35 PST." Date: Thu, 09 Nov 2000 16:37:40 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Since autosense is failing, the cd(4) driver can't tell what sort of error >> is getting returned (and therefore whether the drive is really accessible), >> so it won't attach. > >An AUTOSENSE failing means that a check condition occurred, but no sense data >is available. That should, in fact, be treated identically to READ CAPACITY >failing because there's no media. Are you saying that the Qlogic firmware will return autosense fail if the sense information is all zeros (no sense)? That would be really broken. >What's more important is that cam_periph_error or the periph should send a >REQUEST SENSE if AUTOSENSE fails- the sim should not be the one doing this. I don't know that you are guaranteed to get correct sense in this case as the first attempt to retrieve sense may have cleared or changed the sense information. I do have this implemented, BTW, in some error recovery enhancements I've made, but I still don't know that it is the appropriate thing to do. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 15:42:32 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id B5C9A37B4C5; Thu, 9 Nov 2000 15:42:28 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA34495; Thu, 9 Nov 2000 16:41:35 -0700 (MST) (envelope-from ken) Date: Thu, 9 Nov 2000 16:41:35 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable Message-ID: <20001109164135.A34451@panzer.kdm.org> References: <20001109154911.A33812@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Thu, Nov 09, 2000 at 03:33:47PM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 09, 2000 at 15:33:47 -0800, Matthew Jacob wrote: > > It reported: > > got SCSI status 0x2 Which is check condition. So what would happen in cam_periph_error() is that we would retry until our retry count was exhausted, and then return EIO. I suppose it would be nice to do a request sense there. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 15:43: 7 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 7902737B479; Thu, 9 Nov 2000 15:43:03 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13u1LN-0001f3-00; Thu, 09 Nov 2000 23:42:59 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eA9Mk6s14709; Thu, 9 Nov 2000 23:46:06 +0100 (CET) (envelope-from wkb) Date: Thu, 9 Nov 2000 23:46:06 +0100 From: Wilko Bulte To: Matthew Jacob Cc: "Kenneth D. Merry" , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable Message-ID: <20001109234606.A14689@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Thu, Nov 09, 2000 at 03:37:17PM -0800 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 09, 2000 at 03:37:17PM -0800, Matthew Jacob wrote: > > > Wilko - does your machine that has this problem say: > > isp0: invalid NVRAM header Don't remember having seen this (ever). But will check tomorrow (heading to bed now W/ -- 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 Thu Nov 9 15:43: 8 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A171E37B4C5; Thu, 9 Nov 2000 15:43:03 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA17495; Thu, 9 Nov 2000 15:42:49 -0800 Date: Thu, 9 Nov 2000 15:42:48 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: "Kenneth D. Merry" , Wilko Bulte , FreeBSD-alpha mailing list , freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable In-Reply-To: <200011092337.eA9Nbea96953@aslan.scsiguy.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, 9 Nov 2000, Justin T. Gibbs wrote: > >> Since autosense is failing, the cd(4) driver can't tell what sort of error > >> is getting returned (and therefore whether the drive is really accessible), > >> so it won't attach. > > > >An AUTOSENSE failing means that a check condition occurred, but no sense data > >is available. That should, in fact, be treated identically to READ CAPACITY > >failing because there's no media. > > Are you saying that the Qlogic firmware will return autosense fail > if the sense information is all zeros (no sense)? That would be > really broken. No, no, no... It gives you a special status of "AUTOSENSE FAIL"- sort of much like how the AHA1542 does it. But you know a check condition occurred. > > >What's more important is that cam_periph_error or the periph should send a > >REQUEST SENSE if AUTOSENSE fails- the sim should not be the one doing this. > > I don't know that you are guaranteed to get correct sense in this case > as the first attempt to retrieve sense may have cleared or changed > the sense information. I do have this implemented, BTW, in some error > recovery enhancements I've made, but I still don't know that it is > the appropriate thing to do. Yes- that troubles me also. But w/o being able to say *why* autosense failed it's the best one can do. The pragmatics here are that if you have a CHECK CONDITION, maybe 7 times out of 10 you really don't care what the Sense Key is. It's either an operation you can retry on (most I/O to stateless devices) or fundamentally don't much care about (e.g., a CHECK CONDITION on a tape unload). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 15:45:23 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2083737B4C5; Thu, 9 Nov 2000 15:45:21 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA17533; Thu, 9 Nov 2000 15:45:15 -0800 Date: Thu, 9 Nov 2000 15:45:15 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable In-Reply-To: <20001109164135.A34451@panzer.kdm.org> 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, 9 Nov 2000, Kenneth D. Merry wrote: > On Thu, Nov 09, 2000 at 15:33:47 -0800, Matthew Jacob wrote: > > > > It reported: > > > > got SCSI status 0x2 > > Which is check condition. So what would happen in cam_periph_error() is > that we would retry until our retry count was exhausted, and then return > EIO. Yes. I added a > 1 retry count to READ CAPACITY, but the problem seems to be persistent. It's this !@$*!$)!*$)!$*!)$*!)$!*$!)$*!$) problem with Qlogic and startup resurfacing again. Remember that something similar bunged up Andrew for quite some time about 8 months ago. Now that I have a bus analyzer, I can probably even track down what's actually up when I get time to do it. > > I suppose it would be nice to do a request sense there. > Yes. But it still puzzles me (at a high levelk) why I can't rescan and get cd to attach later. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 15:53: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id AFBB637B4C5; Thu, 9 Nov 2000 15:53:01 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA34672; Thu, 9 Nov 2000 16:52:53 -0700 (MST) (envelope-from ken) Date: Thu, 9 Nov 2000 16:52:53 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable Message-ID: <20001109165253.A34636@panzer.kdm.org> References: <20001109164135.A34451@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Thu, Nov 09, 2000 at 03:45:15PM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 09, 2000 at 15:45:15 -0800, Matthew Jacob wrote: > On Thu, 9 Nov 2000, Kenneth D. Merry wrote: > > > I suppose it would be nice to do a request sense there. > > > > Yes. But it still puzzles me (at a high levelk) why I can't rescan and get cd > to attach later. Because the device hasn't gone away, it's still in the EDT. So there's no need to re-announce a device that is hasn't shown up or gone away since the last time the bus was scanned. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 15:53:52 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B5BC737B4C5; Thu, 9 Nov 2000 15:53:50 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA17591; Thu, 9 Nov 2000 15:53:45 -0800 Date: Thu, 9 Nov 2000 15:53:44 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable In-Reply-To: <20001109165253.A34636@panzer.kdm.org> 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 > Because the device hasn't gone away, it's still in the EDT. So there's no > need to re-announce a device that is hasn't shown up or gone away since the > last time the bus was scanned. Yeah, but it's ready now to attach a different driver other than pass... :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 16: 4:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1B48D37B479; Thu, 9 Nov 2000 16:04:35 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA34766; Thu, 9 Nov 2000 17:04:28 -0700 (MST) (envelope-from ken) Date: Thu, 9 Nov 2000 17:04:28 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable Message-ID: <20001109170428.B34636@panzer.kdm.org> References: <20001109165253.A34636@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Thu, Nov 09, 2000 at 03:53:44PM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 09, 2000 at 15:53:44 -0800, Matthew Jacob wrote: > > > Because the device hasn't gone away, it's still in the EDT. So there's no > > need to re-announce a device that is hasn't shown up or gone away since the > > last time the bus was scanned. > > Yeah, but it's ready now to attach a different driver other than pass... :-) The cd(4) driver had its chance, and declined. It doesn't get another chance. We could make a design decision to always re-announce all devices during a rescan, but it would take some thought and discussion to get to that point, and then some code changes to make all the probe code work that way. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 16: 7:57 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7769437B479; Thu, 9 Nov 2000 16:07:55 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA17664; Thu, 9 Nov 2000 16:07:50 -0800 Date: Thu, 9 Nov 2000 16:07:50 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Wilko Bulte , mjacob@FreeBSD.ORG, FreeBSD-alpha mailing list , justin@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: alpha/22650: SCSI cdrom attach problems on 4-stable In-Reply-To: <20001109170428.B34636@panzer.kdm.org> 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 > > Yeah, but it's ready now to attach a different driver other than pass... :-) > > The cd(4) driver had its chance, and declined. It doesn't get another > chance. Well, if it were loadable it would. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 18:13: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 0EF9137B479 for ; Thu, 9 Nov 2000 18:13:03 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA18216 for alpha@freebsd.org; Thu, 9 Nov 2000 18:13:02 -0800 (PST) (envelope-from obrien) Date: Thu, 9 Nov 2000 18:13:02 -0800 From: "David O'Brien" To: alpha@freebsd.org Subject: Does your Alpha run a SMPng kernel? Message-ID: <20001109181301.A17584@dragon.nuxi.com> Reply-To: alpha@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: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There is some debate as to which machines can run the latest SMPng kernel so I'd like to take a poll. If you can, please CVSup and then build a GENERIC -current kernel and see if it boots. Then if no one has emailed alpha@freebsd.org reply and give your results. If some one else has replied with your same type of Alpha and had the same results, then there is no need to reply. But if you get a different result, then I'd like to know it of course. thanks! -- -- 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 Nov 9 18:15: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 2E2D637B479 for ; Thu, 9 Nov 2000 18:15:00 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA18436 for alpha@freebsd.org; Thu, 9 Nov 2000 18:14:59 -0800 (PST) (envelope-from obrien) Date: Thu, 9 Nov 2000 18:14:59 -0800 From: "David O'Brien" To: alpha@freebsd.org Subject: Re: Does your Alpha run a SMPng kernel? Message-ID: <20001109181459.A18236@dragon.nuxi.com> Reply-To: alpha@freebsd.org References: <20001109181301.A17584@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: <20001109181301.A17584@dragon.nuxi.com>; from obrien@freebsd.org on Thu, Nov 09, 2000 at 06:13:02PM -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: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 09, 2000 at 06:13:02PM -0800, David O'Brien wrote: > There is some debate as to which machines can run the latest SMPng > kernel so I'd like to take a poll. If you can, please CVSup and then > build a GENERIC -current kernel and see if it boots. PWS 600au (Miata-MX5) runs -current SMPng. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 18:29:26 2000 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 EBEF537B4C5 for ; Thu, 9 Nov 2000 18:29:24 -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 VAA24637 for ; Thu, 9 Nov 2000 21:29:24 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAA2TOQ20684; Thu, 9 Nov 2000 21:29:24 -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, 9 Nov 2000 21:29:24 -0500 (EST) To: alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: <20001109181301.A17584@dragon.nuxi.com> References: <20001109181301.A17584@dragon.nuxi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14859.23664.641868.642173@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David O'Brien writes: > There is some debate as to which machines can run the latest SMPng > kernel so I'd like to take a poll. If you can, please CVSup and then > build a GENERIC -current kernel and see if it boots. Depends on what you mean by latest. If you mean post-ithreads, then I've booted the following with SMPng API UP1000 Compaq XP1000 (I'd expect XP900/DS10/DS20/DP264 to also work) DEC AlphaStation 500/266 DEC DPW433a (Miata GL) As of last week, there were stil massive stability problems. Eg, my Miata-GL cannot make it through an installworld w/o locking up. (or at least couldn't last week). Heck, it cannot even reinstall the linux_base port reliably. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 18:31:42 2000 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 1AFF537B479 for ; Thu, 9 Nov 2000 18:31:41 -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 VAA24659 for ; Thu, 9 Nov 2000 21:31:40 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAA2Vep20698; Thu, 9 Nov 2000 21:31:40 -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, 9 Nov 2000 21:31:40 -0500 (EST) To: alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: <20001109181301.A17584@dragon.nuxi.com> References: <20001109181301.A17584@dragon.nuxi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14859.24058.924857.282526@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'll poke Bill about sable.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 18:38:54 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 1566E37B4C5 for ; Thu, 9 Nov 2000 18:38:53 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA19710 for alpha@FreeBSD.ORG; Thu, 9 Nov 2000 18:38:52 -0800 (PST) (envelope-from obrien) Date: Thu, 9 Nov 2000 18:38:52 -0800 From: "David O'Brien" To: alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? Message-ID: <20001109183852.C18236@dragon.nuxi.com> Reply-To: alpha@FreeBSD.ORG References: <20001109181301.A17584@dragon.nuxi.com> <14859.23664.641868.642173@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: <14859.23664.641868.642173@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Nov 09, 2000 at 09:29:24PM -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: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > There is some debate as to which machines can run the latest SMPng > kernel so I'd like to take a poll. If you can, please CVSup and then > build a GENERIC -current kernel and see if it boots. DECpaq DS20 boots -current SMPng fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 18:46: 9 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id AD1E637B479 for ; Thu, 9 Nov 2000 18:46:07 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA20353; Thu, 9 Nov 2000 18:46:02 -0800 (PST) (envelope-from obrien) Date: Thu, 9 Nov 2000 18:46:02 -0800 From: "David O'Brien" To: "Terry R. Friedrichsen" Cc: freebsd-alpha@freebsd.org Subject: Re: window manager probs Message-ID: <20001109184602.E18236@dragon.nuxi.com> Reply-To: alpha@freebsd.org References: <200011071803.eA7I3E100764@venus.sunquest.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011071803.eA7I3E100764@venus.sunquest.com>; from terry@venus.sunquest.com on Tue, Nov 07, 2000 at 11:03:14AM -0700 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: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Nov 07, 2000 at 11:03:14AM -0700, Terry R. Friedrichsen wrote: > Which window manager do y'all use under FreeBSD/alpha (or /AXP, as it says ctwm (enhanced vtwm and is based on vtwm code) on a DS20 running the XFree86 3.3.6 XF86_3DLabs server. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 18:50:28 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5977D37B4CF for ; Thu, 9 Nov 2000 18:50:26 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA18058; Thu, 9 Nov 2000 18:50:20 -0800 Date: Thu, 9 Nov 2000 18:50:20 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: <20001109181301.A17584@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 Seems like you missed mail I've sent out. Alpha PC164 - No Alpha XP1000 - Yes AlphaStation 500- Yes AlphaServer 4100- No AlphaServer 8200- No To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Nov 9 18:55:28 2000 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 7134637B479 for ; Thu, 9 Nov 2000 18:55:26 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAA2seH55309; Thu, 9 Nov 2000 18:54:40 -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: <14859.23664.641868.642173@grasshopper.cs.duke.edu> Date: Thu, 09 Nov 2000 18:55:13 -0800 (PST) From: John Baldwin To: Andrew Gallatin Subject: Re: Does your Alpha run a SMPng kernel? Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 10-Nov-00 Andrew Gallatin wrote: > > David O'Brien writes: > > There is some debate as to which machines can run the latest SMPng > > kernel so I'd like to take a poll. If you can, please CVSup and then > > build a GENERIC -current kernel and see if it boots. > > Depends on what you mean by latest. If you mean post-ithreads, then > I've booted the following with SMPng > > API UP1000 > Compaq XP1000 (I'd expect XP900/DS10/DS20/DP264 to also work) > DEC AlphaStation 500/266 > DEC DPW433a (Miata GL) > > As of last week, there were stil massive stability problems. > Eg, my Miata-GL cannot make it through an installworld w/o > locking up. (or at least couldn't last week). > Heck, it cannot even reinstall the linux_base port reliably. Have any clues as to where it is hanging? One thing that may help is that I have finally gotten the kernel cleaned up so that it can run with WITNESS enabled. In fact, I'm using an MP safe 'psm' driver with WITNESS enabled as I type this. Having WITNESS on will help find some deadlocks that may hang machines. I need to clean up the patches and untangle them from the 4-5 other patchsets on here and then test it on SMP x86 and alpha, but hopefully I can commit it next week some time. > Drew -- 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 Nov 9 18:57:48 2000 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 E984137B4CF; Thu, 9 Nov 2000 18:57:38 -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 VAA25133; Thu, 9 Nov 2000 21:57:38 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAA2vc120761; Thu, 9 Nov 2000 21:57:38 -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, 9 Nov 2000 21:57:38 -0500 (EST) To: John Baldwin Cc: alpha@FreeBSD.org Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: References: <14859.23664.641868.642173@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14859.25551.713957.300992@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > Have any clues as to where it is hanging? One thing that may help is that I No. I've been focusing on other things (linux alpha emu) and have been mainly working in -stable to avoid sharp corners wherever possible ;) > have finally gotten the kernel cleaned up so that it can run with WITNESS > enabled. In fact, I'm using an MP safe 'psm' driver with WITNESS enabled as I > type this. Having WITNESS on will help find some deadlocks that may hang > machines. I need to clean up the patches and untangle them from the 4-5 other > patchsets on here and then test it on SMP x86 and alpha, but hopefully I can > commit it next week some time. Cool. I'll watch for it.. Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 8:15:59 2000 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 C4BB237B479 for ; Fri, 10 Nov 2000 08:15:56 -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 eAAGFpX06058 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Fri, 10 Nov 2000 17:15:54 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eAAGFcf01541 for ; Fri, 10 Nov 2000 17:15:42 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id eAAGFcs00493 for alpha@FreeBSD.ORG; Fri, 10 Nov 2000 17:15:38 +0100 (CET) (envelope-from ticso) Date: Fri, 10 Nov 2000 17:15:36 +0100 From: Bernd Walter To: alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? Message-ID: <20001110171536.A474@cicely8.cicely.de> References: <20001109181301.A17584@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20001109181301.A17584@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Thu, Nov 09, 2000 at 06:13:02PM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 09, 2000 at 06:13:02PM -0800, David O'Brien wrote: > There is some debate as to which machines can run the latest SMPng > kernel so I'd like to take a poll. If you can, please CVSup and then > build a GENERIC -current kernel and see if it boots. PC164 - Hangs during SCSI-scan. AxpPCI33 - Panics after LCA detection The AxpPCI33 Problem is some weeks older than SMPng. -- 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 Nov 10 8:21:55 2000 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 1F02F37B479 for ; Fri, 10 Nov 2000 08:21:53 -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 13uGvz-0005Zm-00; Fri, 10 Nov 2000 16:21:47 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eAB5PEB00801; Sat, 11 Nov 2000 06:25:14 +0100 (CET) (envelope-from wkb) Date: Sat, 11 Nov 2000 06:25:14 +0100 From: Wilko Bulte To: Bernd Walter Cc: alpha@freebsd.org Subject: Re: Does your Alpha run a SMPng kernel? Message-ID: <20001111062514.C317@freebie.demon.nl> References: <20001109181301.A17584@dragon.nuxi.com> <20001110171536.A474@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001110171536.A474@cicely8.cicely.de>; from ticso@cicely8.cicely.de on Fri, Nov 10, 2000 at 05:15:36PM +0100 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Nov 10, 2000 at 05:15:36PM +0100, Bernd Walter wrote: > On Thu, Nov 09, 2000 at 06:13:02PM -0800, David O'Brien wrote: > > There is some debate as to which machines can run the latest SMPng > > kernel so I'd like to take a poll. If you can, please CVSup and then > > build a GENERIC -current kernel and see if it boots. > > PC164 - Hangs during SCSI-scan. > AxpPCI33 - Panics after LCA detection > The AxpPCI33 Problem is some weeks older than SMPng. It is probably the same problem that made 4.1.1 not much fun on Multia. -- 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 Fri Nov 10 9:10: 5 2000 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 D713037B479 for ; Fri, 10 Nov 2000 09:10:01 -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 eAAH9oA16308 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Fri, 10 Nov 2000 18:09:52 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eAAH9ef01746; Fri, 10 Nov 2000 18:09:41 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id eAAH9eW00540; Fri, 10 Nov 2000 18:09:40 +0100 (CET) (envelope-from ticso) Date: Fri, 10 Nov 2000 18:09:39 +0100 From: Bernd Walter To: Wilko Bulte Cc: alpha@freebsd.org Subject: Re: Does your Alpha run a SMPng kernel? Message-ID: <20001110180939.B474@cicely8.cicely.de> References: <20001109181301.A17584@dragon.nuxi.com> <20001110171536.A474@cicely8.cicely.de> <20001111062514.C317@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20001111062514.C317@freebie.demon.nl>; from wkb@freebie.demon.nl on Sat, Nov 11, 2000 at 06:25:14AM +0100 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Nov 11, 2000 at 06:25:14AM +0100, Wilko Bulte wrote: > On Fri, Nov 10, 2000 at 05:15:36PM +0100, Bernd Walter wrote: > > AxpPCI33 - Panics after LCA detection > > The AxpPCI33 Problem is some weeks older than SMPng. > > It is probably the same problem that made 4.1.1 not much fun on Multia. Maybe, but that will mean that 4.2 should have the same problem. I will check this. Actually I'm running 4.1-RELEASE and tried netbooting a current kernel. -- 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 Nov 10 10: 1:20 2000 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 7285237B479; Fri, 10 Nov 2000 10:01:16 -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 NAA06747; Fri, 10 Nov 2000 13:01:15 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAAI1FK22146; Fri, 10 Nov 2000 13:01:15 -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, 10 Nov 2000 13:01:14 -0500 (EST) To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: References: <14859.23664.641868.642173@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14860.13678.594397.310814@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > Have any clues as to where it is hanging? One thing that may help is that I This is the "one device goes south but everything else is happy" sort of problem I was complaining about last week. My UP1000 running today's -current just wedged while I was rcp'ing a large file to it over a 100Mb link. It's busy speweing "fxp0: device timeout" Everything but the nic seems happy. (But since I'm running with NIS and NFS, loosing the nic is fatal) The machine's state is as follows: Stopped at siointr1+0x17c: br zero,siointr1+0x32c db> ps pid proc addr uid ppid pgrp flag stat wmesg wchan cmd 293 fffffe0005aaffa0 fffffe0006a44000 0 124 124 000084 3 select fffffc00006411c8 ypbind 289 fffffe0005ab0280 fffffe0006a40000 1387 286 286 004184 3 sbwait fffffe0006315c08 rcp 286 fffffe0005ab0560 fffffe0006a30000 1387 159 286 2004084 3 opause fffffe0006a301b0 tcsh 249 fffffe0005ab13c0 fffffe0006a08000 0 1 249 004086 3 nanslp fffffc000064b398 login 248 fffffe0005ab0b20 fffffe0006a26000 0 1 248 004086 3 ttyin fffffe00007acc10 getty 247 fffffe0005ab0e00 fffffe0006a22000 0 1 247 004086 3 ttyin fffffe00007ad210 getty 246 fffffe0005ab3ee0 fffffe00069a6000 0 1 246 004086 3 ttyin fffffe0000670e10 getty 241 fffffe0005ab27e0 fffffe00069e8000 0 1 241 000084 3 sbwait fffffe0006314ce8 zhm 227 fffffe0005ab0840 fffffe0006a2c000 0 1 227 000184 3 select fffffc00006411c8 lpd 168 fffffe0005ab16a0 fffffe0006a02000 0 1 168 000084 3 select fffffc00006411c8 sshd 164 fffffe0005ab3080 fffffe00069d8000 0 1 164 2000184 3 pause fffffe00069d81b0 sendmail 161 fffffe0005ab1980 fffffe00069fe000 0 1 161 000084 3 nanslp fffffc000064b398 cron 159 fffffe0005ab10e0 fffffe0006a10000 0 1 159 000084 3 select fffffc00006411c8 inetd 140 fffffe0005ab3c00 fffffe00069aa000 0 1 140 000084 3 select fffffc00006411c8 amd 134 fffffe0005ab1c60 fffffe00069fa000 0 1 129 000084 3 nfsidl fffffc000066faf0 nfsiod 133 fffffe0005ab1f40 fffffe00069f6000 0 1 129 000084 3 nfsidl fffffc000066fae8 nfsiod 132 fffffe0005ab2220 fffffe00069f2000 0 1 129 000084 3 nfsidl fffffc000066fae0 nfsiod 131 fffffe0005ab2500 fffffe00069ee000 0 1 129 000084 3 nfsidl fffffc000066fad8 nfsiod 124 fffffe0005ab2ac0 fffffe00069e2000 0 1 124 000084 3 select fffffc00006411c8 ypbind 122 fffffe0005ab2da0 fffffe00069dc000 1 1 122 000184 3 select fffffc00006411c8 portmap 119 fffffe0005ab3360 fffffe00069d4000 0 1 119 000084 3 select fffffc00006411c8 ntpd 110 fffffe0005ab3920 fffffe00069b6000 0 1 110 000084 3 select fffffc00006411c8 syslogd 44 fffffe0005ab3640 fffffe00069bc000 0 1 44 000084 3 mfsidl fffffe00064ebfe0 mount_mfs 5 fffffe0005ab41c0 fffffe00064fc000 0 0 0 000204 3 syncer fffffc00006410f0 syncer 4 fffffe0005ab44a0 fffffe00064f8000 0 0 0 100204 3 psleep fffffc000064b64c bufdaemon 3 fffffe0005ab4780 fffffe00064f4000 0 0 0 000204 3 psleep fffffc000065e02c vmdaemon 2 fffffe0005ab4a60 fffffe00064f0000 0 0 0 100204 3 psleep fffffc0000624990 pagedaemon 25 fffffe0005ab4d40 fffffe0006304000 0 0 0 000204 6 intr: sbc1 24 fffffe0005ab5020 fffffe0006300000 0 0 0 000204 6 swi0: tty:sio 23 fffffe0005ab5300 fffffe00062fc000 0 0 0 000204 6 intr: atkbd0 22 fffffe0005ab55e0 fffffe00062f6000 0 0 0 000204 6 intr: fdc0 21 fffffe0005ab58c0 fffffe00062f2000 0 0 0 000204 6 intr: ata1 20 fffffe0005ab5ba0 fffffe00062ee000 0 0 0 000204 6 intr: ata0 19 fffffe0005ab5e80 fffffe00062ea000 0 0 0 000204 6 intr: sym0 18 fffffe0005ab6160 fffffe00062e4000 0 0 0 000204 6 intr: dc0 fxp0 17 fffffe0005ab6440 fffffe00062e0000 0 0 0 000204 6 swi5: task queue 16 fffffe0005ab6720 fffffe00062dc000 0 0 0 000204 6 swi3: cambio 15 fffffe0005ab6a00 fffffe00062d8000 0 0 0 000204 6 swi2: camnet 14 fffffe0005ab6ce0 fffffe00062d4000 0 0 0 000204 3 rndslp fffffc000066ba08 random 13 fffffe0005ab6fc0 fffffe00062d0000 0 0 0 000204 6 swi4: vm 12 fffffe0005ab72a0 fffffe00062cc000 0 0 0 00020c 2 swi6: clock 11 fffffe0005ab7580 fffffe00062c8000 0 0 0 000204 6 swi1: net 10 fffffe0005ab7860 fffffe0005ac2000 0 0 0 00020c 2 idle 1 fffffe0005ab7b40 fffffe0005abe000 0 0 1 004284 3 wait fffffe0005ab7b40 init 0 fffffc000066ba18 fffffc00006ec000 0 0 0 000204 3 sched fffffc000066ba18 swapper db> c fxp0: device timeout fxp0: device timeout fxp0: device timeout Is there a chance that this is being caused by the kernel, say, getting a clock interrupt in the middle of doing some low-level should-be-atomic timing-dependant I/O operations in either the driver or the I/O support routines? Remember that on the UP1000, everything goes through the isa interrupt controller. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 10: 6:25 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E7FDE37B4C5; Fri, 10 Nov 2000 10:06:14 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA20653; Fri, 10 Nov 2000 10:06:12 -0800 Date: Fri, 10 Nov 2000 10:06:12 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: John Baldwin , alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: <14860.13678.594397.310814@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 On Fri, 10 Nov 2000, Andrew Gallatin wrote: > > John Baldwin writes: > > > > Have any clues as to where it is hanging? One thing that may help is that I > > This is the "one device goes south but everything else is happy" sort > of problem I was complaining about last week. > > My UP1000 running today's -current just wedged while I was rcp'ing a > large file to it over a 100Mb link. It's busy speweing "fxp0: device > timeout" Everything but the nic seems happy. (But since I'm running > with NIS and NFS, loosing the nic is fatal) 'ata' timeouts occur with abandon during probing PC164 or on XP1000. > > The machine's state is as follows: > > Stopped at siointr1+0x17c: br zero,siointr1+0x32c > db> ps > pid proc addr uid ppid pgrp flag stat wmesg wchan cmd > 293 fffffe0005aaffa0 fffffe0006a44000 0 124 124 000084 3 select fffffc00006411c8 ypbind > 289 fffffe0005ab0280 fffffe0006a40000 1387 286 286 004184 3 sbwait fffffe0006315c08 rcp > 286 fffffe0005ab0560 fffffe0006a30000 1387 159 286 2004084 3 opause fffffe0006a301b0 tcsh > 249 fffffe0005ab13c0 fffffe0006a08000 0 1 249 004086 3 nanslp fffffc000064b398 login > 248 fffffe0005ab0b20 fffffe0006a26000 0 1 248 004086 3 ttyin fffffe00007acc10 getty > 247 fffffe0005ab0e00 fffffe0006a22000 0 1 247 004086 3 ttyin fffffe00007ad210 getty > 246 fffffe0005ab3ee0 fffffe00069a6000 0 1 246 004086 3 ttyin fffffe0000670e10 getty > 241 fffffe0005ab27e0 fffffe00069e8000 0 1 241 000084 3 sbwait fffffe0006314ce8 zhm > 227 fffffe0005ab0840 fffffe0006a2c000 0 1 227 000184 3 select fffffc00006411c8 lpd > 168 fffffe0005ab16a0 fffffe0006a02000 0 1 168 000084 3 select fffffc00006411c8 sshd > 164 fffffe0005ab3080 fffffe00069d8000 0 1 164 2000184 3 pause fffffe00069d81b0 sendmail > 161 fffffe0005ab1980 fffffe00069fe000 0 1 161 000084 3 nanslp fffffc000064b398 cron > 159 fffffe0005ab10e0 fffffe0006a10000 0 1 159 000084 3 select fffffc00006411c8 inetd > 140 fffffe0005ab3c00 fffffe00069aa000 0 1 140 000084 3 select fffffc00006411c8 amd > 134 fffffe0005ab1c60 fffffe00069fa000 0 1 129 000084 3 nfsidl fffffc000066faf0 nfsiod > 133 fffffe0005ab1f40 fffffe00069f6000 0 1 129 000084 3 nfsidl fffffc000066fae8 nfsiod > 132 fffffe0005ab2220 fffffe00069f2000 0 1 129 000084 3 nfsidl fffffc000066fae0 nfsiod > 131 fffffe0005ab2500 fffffe00069ee000 0 1 129 000084 3 nfsidl fffffc000066fad8 nfsiod > 124 fffffe0005ab2ac0 fffffe00069e2000 0 1 124 000084 3 select fffffc00006411c8 ypbind > 122 fffffe0005ab2da0 fffffe00069dc000 1 1 122 000184 3 select fffffc00006411c8 portmap > 119 fffffe0005ab3360 fffffe00069d4000 0 1 119 000084 3 select fffffc00006411c8 ntpd > 110 fffffe0005ab3920 fffffe00069b6000 0 1 110 000084 3 select fffffc00006411c8 syslogd > 44 fffffe0005ab3640 fffffe00069bc000 0 1 44 000084 3 mfsidl fffffe00064ebfe0 mount_mfs > 5 fffffe0005ab41c0 fffffe00064fc000 0 0 0 000204 3 syncer fffffc00006410f0 syncer > 4 fffffe0005ab44a0 fffffe00064f8000 0 0 0 100204 3 psleep fffffc000064b64c bufdaemon > 3 fffffe0005ab4780 fffffe00064f4000 0 0 0 000204 3 psleep fffffc000065e02c vmdaemon > 2 fffffe0005ab4a60 fffffe00064f0000 0 0 0 100204 3 psleep fffffc0000624990 pagedaemon > 25 fffffe0005ab4d40 fffffe0006304000 0 0 0 000204 6 intr: sbc1 > 24 fffffe0005ab5020 fffffe0006300000 0 0 0 000204 6 swi0: tty:sio > 23 fffffe0005ab5300 fffffe00062fc000 0 0 0 000204 6 intr: atkbd0 > 22 fffffe0005ab55e0 fffffe00062f6000 0 0 0 000204 6 intr: fdc0 > 21 fffffe0005ab58c0 fffffe00062f2000 0 0 0 000204 6 intr: ata1 > 20 fffffe0005ab5ba0 fffffe00062ee000 0 0 0 000204 6 intr: ata0 > 19 fffffe0005ab5e80 fffffe00062ea000 0 0 0 000204 6 intr: sym0 > 18 fffffe0005ab6160 fffffe00062e4000 0 0 0 000204 6 intr: dc0 fxp0 > 17 fffffe0005ab6440 fffffe00062e0000 0 0 0 000204 6 swi5: task queue > 16 fffffe0005ab6720 fffffe00062dc000 0 0 0 000204 6 swi3: cambio > 15 fffffe0005ab6a00 fffffe00062d8000 0 0 0 000204 6 swi2: camnet > 14 fffffe0005ab6ce0 fffffe00062d4000 0 0 0 000204 3 rndslp fffffc000066ba08 random > 13 fffffe0005ab6fc0 fffffe00062d0000 0 0 0 000204 6 swi4: vm > 12 fffffe0005ab72a0 fffffe00062cc000 0 0 0 00020c 2 swi6: clock > 11 fffffe0005ab7580 fffffe00062c8000 0 0 0 000204 6 swi1: net > 10 fffffe0005ab7860 fffffe0005ac2000 0 0 0 00020c 2 idle > 1 fffffe0005ab7b40 fffffe0005abe000 0 0 1 004284 3 wait fffffe0005ab7b40 init > 0 fffffc000066ba18 fffffc00006ec000 0 0 0 000204 3 sched fffffc000066ba18 swapper > db> c > fxp0: device timeout > fxp0: device timeout > fxp0: device timeout > > > Is there a chance that this is being caused by the kernel, say, > getting a clock interrupt in the middle of doing some low-level > should-be-atomic timing-dependant I/O operations in either the driver > or the I/O support routines? > > Remember that on the UP1000, everything goes through the isa interrupt > controller. > > > Drew > > > 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 Fri Nov 10 10: 6:31 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 38AA837B4D7 for ; Fri, 10 Nov 2000 10:06:23 -0800 (PST) Received: (qmail 21445 invoked from network); 10 Nov 2000 18:04:47 -0000 Received: from unknown (HELO telehouse.ch) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 10 Nov 2000 18:04:47 -0000 Message-ID: <3A0C391C.63273AA7@telehouse.ch> Date: Fri, 10 Nov 2000 19:06:20 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: John Baldwin , alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? References: <14859.23664.641868.642173@grasshopper.cs.duke.edu> <14860.13678.594397.310814@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > > John Baldwin writes: > > > > Have any clues as to where it is hanging? One thing that may help is that I > > This is the "one device goes south but everything else is happy" sort > of problem I was complaining about last week. > > My UP1000 running today's -current just wedged while I was rcp'ing a > large file to it over a 100Mb link. It's busy speweing "fxp0: device > timeout" Everything but the nic seems happy. (But since I'm running > with NIS and NFS, loosing the nic is fatal) -snip- > fxp0: device timeout > fxp0: device timeout > fxp0: device timeout > > Is there a chance that this is being caused by the kernel, say, > getting a clock interrupt in the middle of doing some low-level > should-be-atomic timing-dependant I/O operations in either the driver > or the I/O support routines? > > Remember that on the UP1000, everything goes through the isa interrupt > controller. I get this error as well but I'm on i386. AMD Athlon 900 to be exact. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 10:20:16 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from rios.sitaranetworks.com (rios.sitaranetworks.com [199.103.141.78]) by hub.freebsd.org (Postfix) with ESMTP id 0F84B37B4C5; Fri, 10 Nov 2000 10:20:12 -0800 (PST) Received: by rios.sitaranetworks.com with Internet Mail Service (5.5.2650.21) id ; Fri, 10 Nov 2000 13:22:57 -0500 Message-ID: <31269226357BD211979E00A0C9866DABE41220@rios.sitaranetworks.com> From: Charles Richmond To: 'Andre Oppermann' , Andrew Gallatin Cc: John Baldwin , alpha@FreeBSD.ORG Subject: RE: Does your Alpha run a SMPng kernel? Date: Fri, 10 Nov 2000 13:22:57 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Are you running with a cross connect? At full duplex? If so, try backing down to half and/or sticking a switch in there, whichever is appropiate. > -----Original Message----- > From: Andre Oppermann [mailto:oppermann@telehouse.ch] > Sent: Friday, November 10, 2000 1:06 PM > To: Andrew Gallatin > Cc: John Baldwin; alpha@FreeBSD.ORG > Subject: Re: Does your Alpha run a SMPng kernel? > > > Andrew Gallatin wrote: > > > > John Baldwin writes: > > > > > > Have any clues as to where it is hanging? One thing > that may help is that I > > > > This is the "one device goes south but everything else is > happy" sort > > of problem I was complaining about last week. > > > > My UP1000 running today's -current just wedged while I was rcp'ing a > > large file to it over a 100Mb link. It's busy speweing > "fxp0: device > > timeout" Everything but the nic seems happy. (But since I'm running > > with NIS and NFS, loosing the nic is fatal) > -snip- > > fxp0: device timeout > > fxp0: device timeout > > fxp0: device timeout > > > > Is there a chance that this is being caused by the kernel, say, > > getting a clock interrupt in the middle of doing some low-level > > should-be-atomic timing-dependant I/O operations in either > the driver > > or the I/O support routines? > > > > Remember that on the UP1000, everything goes through the > isa interrupt > > controller. > > I get this error as well but I'm on i386. AMD Athlon 900 to be exact. > > -- > Andre > > > 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 Fri Nov 10 11:14:14 2000 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 9B0D237B4C5; Fri, 10 Nov 2000 11:14:12 -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 OAA08494; Fri, 10 Nov 2000 14:14:10 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAAJEAn22226; Fri, 10 Nov 2000 14:14:10 -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, 10 Nov 2000 14:14:09 -0500 (EST) To: Charles Richmond Cc: "'Andre Oppermann'" , John Baldwin , alpha@FreeBSD.ORG Subject: RE: Does your Alpha run a SMPng kernel? In-Reply-To: <31269226357BD211979E00A0C9866DABE41220@rios.sitaranetworks.com> References: <31269226357BD211979E00A0C9866DABE41220@rios.sitaranetworks.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14860.18535.736764.31772@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Charles Richmond writes: > Are you running with a cross connect? At full duplex? > If so, try backing down to half and/or sticking a > switch in there, whichever is appropiate. Full duplex, with a switch in between. Regardless of the network topology, I'd rather see the OS fixed than cure the symptoms by crippling the network. Eg, the machine is rock-solid with old IPL based kernels. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 11:16:45 2000 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 A21AE37B4C5; Fri, 10 Nov 2000 11:16:43 -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 OAA08566; Fri, 10 Nov 2000 14:16:43 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAAJGgV22235; Fri, 10 Nov 2000 14:16:42 -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, 10 Nov 2000 14:16:42 -0500 (EST) To: mjacob@feral.com Cc: John Baldwin , alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: References: <14860.13678.594397.310814@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14860.18701.572533.296722@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > 'ata' timeouts occur with abandon during probing PC164 or on XP1000. Does the ata device ever recover? Neither if_fxp or if_dc ever recover. After the first timeout, they're gone for good. This makes me think its some fundimental problem, like leaving an interrupt disabled or something. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 11:18:29 2000 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 A3C7A37B4CF; Fri, 10 Nov 2000 11:18:27 -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 OAA08627; Fri, 10 Nov 2000 14:18:27 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAAJIQO22241; Fri, 10 Nov 2000 14:18:26 -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, 10 Nov 2000 14:18:26 -0500 (EST) To: Andre Oppermann Cc: John Baldwin , alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: <3A0C391C.63273AA7@telehouse.ch> References: <14859.23664.641868.642173@grasshopper.cs.duke.edu> <14860.13678.594397.310814@grasshopper.cs.duke.edu> <3A0C391C.63273AA7@telehouse.ch> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14860.18856.388759.889439@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andre Oppermann writes: > I get this error as well but I'm on i386. AMD Athlon 900 to be exact. Does your Athlon box have an AMD 751 chipset just like my UP1000? Does your nic ever come back, or is it gone for good? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 11:27: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0302A37B683; Fri, 10 Nov 2000 11:27:00 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA21025; Fri, 10 Nov 2000 11:26:58 -0800 Date: Fri, 10 Nov 2000 11:26:58 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: John Baldwin , alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: <14860.18701.572533.296722@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 On Fri, 10 Nov 2000, Andrew Gallatin wrote: > > Matthew Jacob writes: > > > > 'ata' timeouts occur with abandon during probing PC164 or on XP1000. > > Does the ata device ever recover? Neither if_fxp or if_dc ever > recover. After the first timeout, they're gone for good. Sometimes, but often not because the ata driver can't attach, e.g.: ata0-master: ata_command: timeout waiting for intr ata0-master: identify failed > This makes me think its some fundimental problem, like leaving an > interrupt disabled or something. See separate mail to you about this. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 11:35:14 2000 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 36FEF37B4CF for ; Fri, 10 Nov 2000 11:35:11 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp241.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAAJYrH77845; Fri, 10 Nov 2000 11:34: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, 10 Nov 2000 11:35:30 -0800 (PST) From: John Baldwin To: Matthew Jacob Subject: Re: Does your Alpha run a SMPng kernel? Cc: alpha@FreeBSD.org, Andrew Gallatin Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 10-Nov-00 Matthew Jacob wrote: > > > On Fri, 10 Nov 2000, Andrew Gallatin wrote: > >> >> Matthew Jacob writes: >> > >> > 'ata' timeouts occur with abandon during probing PC164 or on XP1000. >> >> Does the ata device ever recover? Neither if_fxp or if_dc ever >> recover. After the first timeout, they're gone for good. > > Sometimes, but often not because the ata driver can't attach, e.g.: > > ata0-master: ata_command: timeout waiting for intr > ata0-master: identify failed That is either a bogus interrupt coming in or no interrupt coming in. Sticking a printf in the ata interrupt handler to confirm would be useful. It might be that we get the first interrupt ok and don't properly re-enable the source afterwards. Is there a chance we aren't sending an EOI to the PIC? >> This makes me think its some fundimental problem, like leaving an >> interrupt disabled or something. > > See separate mail to you about this. > -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 Fri Nov 10 11:35:18 2000 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 5D11737B4C5 for ; Fri, 10 Nov 2000 11:35:08 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp241.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAAJYrH77841; Fri, 10 Nov 2000 11:34: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, 10 Nov 2000 11:35:30 -0800 (PST) From: John Baldwin To: Matthew Jacob Subject: Re: Does your Alpha run a SMPng kernel? Cc: alpha@FreeBSD.org, Andrew Gallatin Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 10-Nov-00 Matthew Jacob wrote: > > > On Fri, 10 Nov 2000, Andrew Gallatin wrote: > >> >> John Baldwin writes: >> > >> > Have any clues as to where it is hanging? One thing that may help is >> > that I >> >> This is the "one device goes south but everything else is happy" sort >> of problem I was complaining about last week. >> >> My UP1000 running today's -current just wedged while I was rcp'ing a >> large file to it over a 100Mb link. It's busy speweing "fxp0: device >> timeout" Everything but the nic seems happy. (But since I'm running >> with NIS and NFS, loosing the nic is fatal) > > 'ata' timeouts occur with abandon during probing PC164 or on XP1000. ata timeouts are due to the interrupt either not arriving or the interrupt being ignored due to other weirdness. Try adding some printf()'s into the ata interrupt handler to see if it gets called and how far it gets if it does get called. The fxp timeouts are definitely due to no interrupts as well. If you look below, neither the fxp0 or swi:net interrupt threads are runnable, but are stuck in SWAIT instead. >> The machine's state is as follows: >> >> Stopped at siointr1+0x17c: br zero,siointr1+0x32c >> db> ps >> pid proc addr uid ppid pgrp flag stat wmesg wchan cmd >> 293 fffffe0005aaffa0 fffffe0006a44000 0 124 124 000084 3 select >> fffffc00006411c8 ypbind >> 289 fffffe0005ab0280 fffffe0006a40000 1387 286 286 004184 3 sbwait >> fffffe0006315c08 rcp >> 286 fffffe0005ab0560 fffffe0006a30000 1387 159 286 2004084 3 opause >> fffffe0006a301b0 tcsh >> 249 fffffe0005ab13c0 fffffe0006a08000 0 1 249 004086 3 nanslp >> fffffc000064b398 login >> 248 fffffe0005ab0b20 fffffe0006a26000 0 1 248 004086 3 ttyin >> fffffe00007acc10 getty >> 247 fffffe0005ab0e00 fffffe0006a22000 0 1 247 004086 3 ttyin >> fffffe00007ad210 getty >> 246 fffffe0005ab3ee0 fffffe00069a6000 0 1 246 004086 3 ttyin >> fffffe0000670e10 getty >> 241 fffffe0005ab27e0 fffffe00069e8000 0 1 241 000084 3 sbwait >> fffffe0006314ce8 zhm >> 227 fffffe0005ab0840 fffffe0006a2c000 0 1 227 000184 3 select >> fffffc00006411c8 lpd >> 168 fffffe0005ab16a0 fffffe0006a02000 0 1 168 000084 3 select >> fffffc00006411c8 sshd >> 164 fffffe0005ab3080 fffffe00069d8000 0 1 164 2000184 3 pause >> fffffe00069d81b0 sendmail >> 161 fffffe0005ab1980 fffffe00069fe000 0 1 161 000084 3 nanslp >> fffffc000064b398 cron >> 159 fffffe0005ab10e0 fffffe0006a10000 0 1 159 000084 3 select >> fffffc00006411c8 inetd >> 140 fffffe0005ab3c00 fffffe00069aa000 0 1 140 000084 3 select >> fffffc00006411c8 amd >> 134 fffffe0005ab1c60 fffffe00069fa000 0 1 129 000084 3 nfsidl >> fffffc000066faf0 nfsiod >> 133 fffffe0005ab1f40 fffffe00069f6000 0 1 129 000084 3 nfsidl >> fffffc000066fae8 nfsiod >> 132 fffffe0005ab2220 fffffe00069f2000 0 1 129 000084 3 nfsidl >> fffffc000066fae0 nfsiod >> 131 fffffe0005ab2500 fffffe00069ee000 0 1 129 000084 3 nfsidl >> fffffc000066fad8 nfsiod >> 124 fffffe0005ab2ac0 fffffe00069e2000 0 1 124 000084 3 select >> fffffc00006411c8 ypbind >> 122 fffffe0005ab2da0 fffffe00069dc000 1 1 122 000184 3 select >> fffffc00006411c8 portmap >> 119 fffffe0005ab3360 fffffe00069d4000 0 1 119 000084 3 select >> fffffc00006411c8 ntpd >> 110 fffffe0005ab3920 fffffe00069b6000 0 1 110 000084 3 select >> fffffc00006411c8 syslogd >> 44 fffffe0005ab3640 fffffe00069bc000 0 1 44 000084 3 mfsidl >> fffffe00064ebfe0 mount_mfs >> 5 fffffe0005ab41c0 fffffe00064fc000 0 0 0 000204 3 syncer >> fffffc00006410f0 syncer >> 4 fffffe0005ab44a0 fffffe00064f8000 0 0 0 100204 3 psleep >> fffffc000064b64c bufdaemon >> 3 fffffe0005ab4780 fffffe00064f4000 0 0 0 000204 3 psleep >> fffffc000065e02c vmdaemon >> 2 fffffe0005ab4a60 fffffe00064f0000 0 0 0 100204 3 psleep >> fffffc0000624990 pagedaemon >> 25 fffffe0005ab4d40 fffffe0006304000 0 0 0 000204 6 >> intr: sbc1 >> 24 fffffe0005ab5020 fffffe0006300000 0 0 0 000204 6 >> swi0: tty:sio >> 23 fffffe0005ab5300 fffffe00062fc000 0 0 0 000204 6 >> intr: atkbd0 >> 22 fffffe0005ab55e0 fffffe00062f6000 0 0 0 000204 6 >> intr: fdc0 >> 21 fffffe0005ab58c0 fffffe00062f2000 0 0 0 000204 6 >> intr: ata1 >> 20 fffffe0005ab5ba0 fffffe00062ee000 0 0 0 000204 6 >> intr: ata0 >> 19 fffffe0005ab5e80 fffffe00062ea000 0 0 0 000204 6 >> intr: sym0 >> 18 fffffe0005ab6160 fffffe00062e4000 0 0 0 000204 6 >> intr: dc0 fxp0 >> 17 fffffe0005ab6440 fffffe00062e0000 0 0 0 000204 6 >> swi5: task queue >> 16 fffffe0005ab6720 fffffe00062dc000 0 0 0 000204 6 >> swi3: cambio >> 15 fffffe0005ab6a00 fffffe00062d8000 0 0 0 000204 6 >> swi2: camnet >> 14 fffffe0005ab6ce0 fffffe00062d4000 0 0 0 000204 3 rndslp >> fffffc000066ba08 random >> 13 fffffe0005ab6fc0 fffffe00062d0000 0 0 0 000204 6 >> swi4: vm >> 12 fffffe0005ab72a0 fffffe00062cc000 0 0 0 00020c 2 >> swi6: clock >> 11 fffffe0005ab7580 fffffe00062c8000 0 0 0 000204 6 >> swi1: net >> 10 fffffe0005ab7860 fffffe0005ac2000 0 0 0 00020c 2 >> idle >> 1 fffffe0005ab7b40 fffffe0005abe000 0 0 1 004284 3 wait >> fffffe0005ab7b40 init >> 0 fffffc000066ba18 fffffc00006ec000 0 0 0 000204 3 sched >> fffffc000066ba18 swapper >> db> c >> fxp0: device timeout >> fxp0: device timeout >> fxp0: device timeout >> >> >> Is there a chance that this is being caused by the kernel, say, >> getting a clock interrupt in the middle of doing some low-level >> should-be-atomic timing-dependant I/O operations in either the driver >> or the I/O support routines? >> >> Remember that on the UP1000, everything goes through the isa interrupt >> controller. So you get some interrupts and then they stop. On the x86 we do a disable/enable interrupt scheme for ISA interrupts by dinking with the PIC, so Matt's suggestion to use isa_enable_intr()/isa_disable_intr() might be needed actually. (see hte INTREN() call in ithd_loop() in i386/isa/ithread.c) Actually, it looks like we wait too long to enable the interrupt sources on the x86. However, using the isa_enable/disable_intr() stuff that Matt suggested might help. >> Drew -- 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 Nov 10 11:38:26 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 17CD337B4C5; Fri, 10 Nov 2000 11:38:23 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA21099; Fri, 10 Nov 2000 11:38:23 -0800 Date: Fri, 10 Nov 2000 11:38:23 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.ORG, Andrew Gallatin Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-751304845-973885103=:83354" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-751304845-973885103=:83354 Content-Type: TEXT/PLAIN; charset=US-ASCII > So you get some interrupts and then they stop. On the x86 we do a > disable/enable interrupt scheme for ISA interrupts by dinking with the PIC, so > Matt's suggestion to use isa_enable_intr()/isa_disable_intr() might be needed > actually. (see hte INTREN() call in ithd_loop() in i386/isa/ithread.c) > Actually, it looks like we wait too long to enable the interrupt sources on the > x86. However, using the isa_enable/disable_intr() stuff that Matt suggested > might help. --0-751304845-973885103=:83354 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=isa_patch Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=isa_patch SW5kZXg6IGFscGhhL2lzYS9pc2EuYw0KPT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PQ0KUkNTIGZpbGU6IC9ob21lL25jdnMvc3JjL3N5cy9hbHBoYS9pc2EvaXNh LmMsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjIzDQpkaWZmIC11IC1yMS4y MyBpc2EuYw0KLS0tIGFscGhhL2lzYS9pc2EuYwkyMDAwLzExLzAxIDE4OjQw OjQxCTEuMjMNCisrKyBhbHBoYS9pc2EvaXNhLmMJMjAwMC8xMS8xMCAxOToz NzozMg0KQEAgLTcxLDYgKzcxLDE5IEBADQogCXNwbHgocyk7DQogfQ0KIA0K K3N0YXRpYyB2b2lkDQorZXh0ZXJuX2lzYV9pbnRyX2VuYWJsZShpbnQgdmVj dG9yKQ0KK3sNCisJaXNhX2ludHJfZW5hYmxlKCh2ZWN0b3IgLSAweDgwMCkg Pj4gNCk7DQorfQ0KKw0KK3N0YXRpYyB2b2lkDQorZXh0ZXJuX2lzYV9pbnRy X2Rpc2FibGUoaW50IHZlY3RvcikNCit7DQorCWlzYV9pbnRyX2Rpc2FibGUo KHZlY3RvciAtIDB4ODAwKSA+PiA0KTsNCit9DQorDQorDQogaW50cm1hc2tf dA0KIGlzYV9pcnFfcGVuZGluZyh2b2lkKQ0KIHsNCkBAIC0zMjIsNyArMzM1 LDcgQEANCiAJCQkgMHg4MDAgKyAoaXJxLT5yX3N0YXJ0IDw8IDQpLCBpc2Ff aGFuZGxlX2ludHIsIGlpLA0KIAkJCSBpdGhyZWFkX3ByaW9yaXR5KGZsYWdz KSwgZmxhZ3MsICZpaS0+aWgsDQogCQkJICZpbnRyY250W0lOVFJDTlRfSVNB X0lSUSArIGlycS0+cl9zdGFydF0sDQotCQkJIE5VTEwsIE5VTEwpOw0KKwkJ CSBleHRlcm5faXNhX2ludHJfZW5hYmxlLCBleHRlcm5faXNhX2ludHJfZGlz YWJsZSk7DQogCWlmIChlcnJvcikgew0KIAkJZnJlZShpaSwgTV9ERVZCVUYp Ow0KIAkJcmV0dXJuIGVycm9yOw0K --0-751304845-973885103=:83354-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 12:13:58 2000 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 E60B137B686 for ; Fri, 10 Nov 2000 12:13:53 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp241.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAAKCrH79699; Fri, 10 Nov 2000 12:12: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: <20001111062514.C317@freebie.demon.nl> Date: Fri, 10 Nov 2000 12:13:30 -0800 (PST) From: John Baldwin To: Wilko Bulte Subject: Re: Does your Alpha run a SMPng kernel? Cc: alpha@FreeBSD.org, Bernd Walter Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 11-Nov-00 Wilko Bulte wrote: > On Fri, Nov 10, 2000 at 05:15:36PM +0100, Bernd Walter wrote: >> On Thu, Nov 09, 2000 at 06:13:02PM -0800, David O'Brien wrote: >> > There is some debate as to which machines can run the latest SMPng >> > kernel so I'd like to take a poll. If you can, please CVSup and then >> > build a GENERIC -current kernel and see if it boots. >> >> PC164 - Hangs during SCSI-scan. >> AxpPCI33 - Panics after LCA detection >> The AxpPCI33 Problem is some weeks older than SMPng. > > It is probably the same problem that made 4.1.1 not much fun on Multia. Since 4.1.1-axp was actually a -current snapshot and not a releng_4 snapshot, most definitely. :) -- 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 Nov 10 13:30:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 8465337B479 for ; Fri, 10 Nov 2000 13:30:43 -0800 (PST) Received: (qmail 24615 invoked from network); 10 Nov 2000 21:29:07 -0000 Received: from unknown (HELO telehouse.ch) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 10 Nov 2000 21:29:07 -0000 Message-ID: <3A0C6903.4B165D3@telehouse.ch> Date: Fri, 10 Nov 2000 22:30:43 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: John Baldwin , alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? References: <14859.23664.641868.642173@grasshopper.cs.duke.edu> <14860.13678.594397.310814@grasshopper.cs.duke.edu> <3A0C391C.63273AA7@telehouse.ch> <14860.18856.388759.889439@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > > Andre Oppermann writes: > > I get this error as well but I'm on i386. AMD Athlon 900 to be exact. > > Does your Athlon box have an AMD 751 chipset just like my UP1000? No, it's a VIA KT133 chipset. I've got this now on two machines, one is a Asus K7V board with an Athlon 700 and one is a Asus A7V with an Athlon Thunderbird 900. > Does your nic ever come back, or is it gone for good? Once this happend it's gone for good. Only hardware reset helps. This happens only after some time (some hours in my case) *without* any network activity on that paticular machine. Before the kernel threads went into -current this did not happen at all. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 14:28:14 2000 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 DBBBA37B479; Fri, 10 Nov 2000 14:28:12 -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 RAA13077; Fri, 10 Nov 2000 17:28:12 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAAMSBQ23722; Fri, 10 Nov 2000 17:28:11 -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, 10 Nov 2000 17:28:10 -0500 (EST) To: mjacob@feral.com Cc: John Baldwin , alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14860.30276.954787.826150@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After your patch, my UP1000 is totally unusable. Timecounter "alpha" frequency 598975780 Hz ata0-master: ata_command: timeout waiting for intr ata0-master: ata_command: timeout waiting for intr ad0: enabling readahead cache failed ata0-master: ata_command: timeout waiting for intr ad0: enabling write cache failed ad0: 6149MB [12495/16/63] at ata0-master UDMA33 (null): MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done (null): MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done (null): MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done (null): MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done acd0: CDROM at ata1-master using PIO4 (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 15:40: 9 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E0F3F37B4C5 for ; Fri, 10 Nov 2000 15:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id PAA27502; Fri, 10 Nov 2000 15:40:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from ldah.math.uni.lodz.pl (ldah.math.uni.lodz.pl [212.191.65.29]) by hub.freebsd.org (Postfix) with ESMTP id 7E64B37B4CF for ; Fri, 10 Nov 2000 15:31:16 -0800 (PST) Received: (from dagoon@localhost) by ldah.math.uni.lodz.pl (8.11.1/8.11.0) id eAANSTW00916; Sat, 11 Nov 2000 00:28:29 +0100 (CET) (envelope-from dagoon) Message-Id: <200011102328.eAANSTW00916@ldah.math.uni.lodz.pl> Date: Sat, 11 Nov 2000 00:28:29 +0100 (CET) From: Marcin Gryszkalis Reply-To: dagoon@ldah.math.uni.lodz.pl To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: alpha/22759: zip not working on 4.2-beta/alpha (not a zip fault) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 22759 >Category: alpha >Synopsis: zip cannot work with existing .zip archives >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Nov 10 15:40:01 PST 2000 >Closed-Date: >Last-Modified: >Originator: Marcin Gryszkalis >Release: FreeBSD 4.2-BETA alpha >Organization: University of Lodz >Environment: FreeBSD 4.2-BETA (ldah) #10: Thu Nov 9 19:42:13 CET 2000 This is Zip 2.3 (November 29th 1999), by Info-ZIP. Compiled with gcc 2.95.2 19991024 (release) for Unix (FreeBSD 4.2-BETA) on Nov 9 2000. >Description: any operation on .zip archive (add,update, etc.) fails , - didn't happen on 4.1.1 >How-To-Repeat: dagoon@ldah:~,0> zip archive opt.sh adding: opt.sh (deflated 41%) dagoon@ldah:~,0> zip archive opt.sh zip warning: missing end signature--probably not a zip file (did you zip warning: remember to use binary mode when you transferred it?) zip error: Zip file structure invalid (archive.zip) (opt.sh is "any" file) >Fix: I guess it's somthing wrong with system not with zip >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 16: 3:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4350737B479 for ; Fri, 10 Nov 2000 16:03: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 QAA22199 for ; Fri, 10 Nov 2000 16:03:10 -0800 Date: Fri, 10 Nov 2000 16:03:09 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@freebsd.org Subject: *thwap me*... possibly useful 4.2Beta Alpha ISO image 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 actually had a make release run all the way through for me (w/o DOC/PORTS/X11, etc..), so I've tarred up the disc1 image which can be found at this location: http://people.freebsd.org/~mjacob/4.2BETA-alpha-iso.tgz I have not even tried to install from it yet- will do so later or in the morning. But I thought folks might find it useful to get *some* kind of start on seeing what is or isn't broken. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Nov 10 16:29:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8DE2737B479 for ; Fri, 10 Nov 2000 16:29:57 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id QAA03219 for ; Fri, 10 Nov 2000 16:29:56 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id eAB0Tu533970; Fri, 10 Nov 2000 16:29:56 -0800 (PST) (envelope-from jdp) Date: Fri, 10 Nov 2000 16:29:56 -0800 (PST) Message-Id: <200011110029.eAB0Tu533970@vashon.polstra.com> To: alpha@freebsd.org From: John Polstra Reply-To: alpha@freebsd.org Cc: alpha@freebsd.org Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: <20001109181301.A17584@dragon.nuxi.com> References: <20001109181301.A17584@dragon.nuxi.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <20001109181301.A17584@dragon.nuxi.com>, David O'Brien wrote: > There is some debate as to which machines can run the latest SMPng > kernel so I'd like to take a poll. If you can, please CVSup and then > build a GENERIC -current kernel and see if it boots. This one works fine: FreeBSD 5.0-CURRENT #0: Fri Nov 10 16:11:55 PST 2000 jdp@alpha.polstra.com:/c/obj/c/src/sys/ALPHA EB164 Digital AlphaPC 164LX 533 MHz, 531MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=2 extensions=0x1 OSF PAL rev: 0x1000200020117 John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Nov 11 0:53:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 29CF437B479 for ; Sat, 11 Nov 2000 00:53:33 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id EAAA25730B; Sat, 11 Nov 2000 02:53:46 -0600 (CST) Date: Sat, 11 Nov 2000 02:53:46 -0600 From: "Michael C . Wu" To: Matthew Jacob Cc: alpha@freebsd.org Subject: Re: *thwap me*... possibly useful 4.2Beta Alpha ISO image Message-ID: <20001111025346.A92797@peorth.iteration.net> Reply-To: "Michael C . Wu" 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 mjacob@feral.com on Fri, Nov 10, 2000 at 04:03:09PM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Nov 10, 2000 at 04:03:09PM -0800, Matthew Jacob scribbled: | I actually had a make release run all the way through for me (w/o | DOC/PORTS/X11, etc..), so I've tarred up the disc1 image which can be found at | this location: | | http://people.freebsd.org/~mjacob/4.2BETA-alpha-iso.tgz | | I have not even tried to install from it yet- will do so later or in the | morning. It installs perfectly and boots fine on my DEC PWS-500au. :) Running perfectly too, cvsupping and trying a buildworld to test it under load. Is the Alpha build -jX safe with the breakage of -jX in x86? Time for a real release iso from our lovely release engineers? :) -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Nov 11 1:56:11 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 5332137B479; Sat, 11 Nov 2000 01:56:08 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 1239B5730B; Sat, 11 Nov 2000 03:56:21 -0600 (CST) Date: Sat, 11 Nov 2000 03:56:21 -0600 From: "Michael C . Wu" To: John Baldwin Cc: Matthew Jacob , alpha@FreeBSD.org, Andrew Gallatin Subject: Re: Does your Alpha run a SMPng kernel? Message-ID: <20001111035621.J93151@peorth.iteration.net> Reply-To: "Michael C . Wu" 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 Fri, Nov 10, 2000 at 11:35:30AM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Nov 10, 2000 at 11:35:30AM -0800, John Baldwin scribbled: | On 10-Nov-00 Matthew Jacob wrote: | > On Fri, 10 Nov 2000, Andrew Gallatin wrote: | >> John Baldwin writes: | >> > Have any clues as to where it is hanging? One thing that may help is | >> > that I | >> This is the "one device goes south but everything else is happy" sort | >> of problem I was complaining about last week. | >> | >> My UP1000 running today's -current just wedged while I was rcp'ing a | >> large file to it over a 100Mb link. It's busy speweing "fxp0: device | >> timeout" Everything but the nic seems happy. (But since I'm running | >> with NIS and NFS, loosing the nic is fatal) | > 'ata' timeouts occur with abandon during probing PC164 or on XP1000. | ata timeouts are due to the interrupt either not arriving or the interrupt | being ignored due to other weirdness. Try adding some printf()'s into the ata | interrupt handler to see if it gets called and how far it gets if it does get | called. The fxp timeouts are definitely due to no interrupts as well. If you | look below, neither the fxp0 or swi:net interrupt threads are runnable, but are | stuck in SWAIT instead. | >> getting a clock interrupt in the middle of doing some low-level | >> should-be-atomic timing-dependant I/O operations in either the driver | >> or the I/O support routines? | >> | >> Remember that on the UP1000, everything goes through the isa interrupt | >> controller. | | So you get some interrupts and then they stop. On the x86 we do a | disable/enable interrupt scheme for ISA interrupts by dinking with the PIC, so | Matt's suggestion to use isa_enable_intr()/isa_disable_intr() might be needed | actually. (see hte INTREN() call in ithd_loop() in i386/isa/ithread.c) | Actually, it looks like we wait too long to enable the interrupt sources on the | x86. However, using the isa_enable/disable_intr() stuff that Matt suggested | might help. Soren has freebsd.dk/pub/ATA patches online if you wish to try. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Nov 11 8: 8:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 5383337B683 for ; Sat, 11 Nov 2000 08:08:05 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13udCG-0006TE-00 for freebsd-alpha@freebsd.org; Sat, 11 Nov 2000 16:08:04 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eABMB9803733 for freebsd-alpha@freebsd.org; Sat, 11 Nov 2000 23:11:09 +0100 (CET) (envelope-from wkb) Date: Sat, 11 Nov 2000 23:11:09 +0100 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: floppy cable for Multia Message-ID: <20001111231109.A3717@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry for a slightly-offtopic question: I got myself some test-Multias but one lacks the little flexwire/cable for the floppy drive. Rather unpractical when you want to test floppy installs. Maybe someone with a Multia that died is willing to donate his/her cable to me? tnx -- 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 Nov 11 8:21:32 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 57ADD37B479 for ; Sat, 11 Nov 2000 08:21:30 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA24118; Sat, 11 Nov 2000 08:21:23 -0800 Date: Sat, 11 Nov 2000 08:21:23 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: floppy cable for Multia In-Reply-To: <20001111231109.A3717@freebie.demon.nl> 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'm sure I can dig up a spare. Let me know your snail mail.... On Sat, 11 Nov 2000, Wilko Bulte wrote: > Sorry for a slightly-offtopic question: I got myself some test-Multias > but one lacks the little flexwire/cable for the floppy drive. Rather > unpractical when you want to test floppy installs. > > Maybe someone with a Multia that died is willing to donate his/her cable to me? > > tnx > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Nov 11 12:53: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id CFE2437B479 for ; Sat, 11 Nov 2000 12:52:58 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 2F4395730B; Sat, 11 Nov 2000 14:53:11 -0600 (CST) Date: Sat, 11 Nov 2000 14:53:11 -0600 From: "Michael C . Wu" To: freebsd-alpha@freebsd.org Subject: Crosscompiling from x86 host to alpha target Message-ID: <20001111145311.A18007@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , freebsd-alpha@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi guys, I am trying to use our basesystem gcc to cross compile to an Alpha from my x86 box. David O'Brien told me to use export TARGET_MACHINE=alpha make buildworld I have done so and it appears to keeps compiling to x86 instead of to Alpha peorth:/home/keichii/alphasrc/src# export TARGET_MACHINE=alpha peorth:/home/keichii/alphasrc/src# env|grep TARGET TARGET_MACHINE=alpha peorth:/home/keichii/alphasrc/src# make buildworld -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- rm -rf /usr/obj/usr/home/keichii/alphasrc/src/i386 mkdir -p /usr/obj/usr/home/keichii/alphasrc/src/i386/usr/bin mkdir -p /usr/obj/usr/home/keichii/alphasrc/src/i386/usr/lib/compat/aout mkdir -p /usr/obj/usr/home/keichii/alphasrc/src/i386/usr/games mkdir -p /usr/obj/usr/home/keichii/alphasrc/src/i386/usr/libdata/ldscripts mkdir -p /usr/obj/usr/home/keichii/alphasrc/src/i386/usr/libexec/elf mkdir -p /usr/obj/usr/home/keichii/alphasrc/src/i386/usr/sbin [..] It compiles to finish, and the result in usr/obj is x86 binaries that I can run on x86. Has anyone had any luck doing so? -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Nov 11 13: 6:54 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id BF5EF37B479 for ; Sat, 11 Nov 2000 13:06:51 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 2B78E477; Sat, 11 Nov 2000 13:06:51 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id NAA29247; Sat, 11 Nov 2000 13:06:50 -0800 (PST) Message-ID: <3A0DB4E9.C6C5D067@cup.hp.com> Date: Sat, 11 Nov 2000 13:06:49 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Michael C . Wu" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Crosscompiling from x86 host to alpha target References: <20001111145311.A18007@peorth.iteration.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Michael C . Wu" wrote: > > I am trying to use our basesystem gcc to cross compile > to an Alpha from my x86 box. David O'Brien told me to use > > export TARGET_MACHINE=alpha > make buildworld Use MACHINE_ARCH. Don't use TARGET_MACHINE. The following gets you reasonably far: % make MACHINE_ARCH=alpha buildworld If you don't have the gcc patches, it'll probably fail compiling libmd (which is quite early). With the gcc patches it fails for perl. The gcc patches can be downloaded from http://people.freebsd.org/~marcel/ -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Nov 11 13:57:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 443AF37B479 for ; Sat, 11 Nov 2000 13:57:56 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 86C485730B; Sat, 11 Nov 2000 15:58:11 -0600 (CST) Date: Sat, 11 Nov 2000 15:58:11 -0600 From: "Michael C . Wu" To: alpha@freebsd.org Subject: Re: Does your Alpha run a SMPng kernel? Message-ID: <20001111155811.A18522@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20001109181301.A17584@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: <20001109181301.A17584@dragon.nuxi.com>; from obrien@freebsd.org on Thu, Nov 09, 2000 at 06:13:02PM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 09, 2000 at 06:13:02PM -0800, David O'Brien scribbled: | There is some debate as to which machines can run the latest SMPng | kernel so I'd like to take a poll. If you can, please CVSup and then | build a GENERIC -current kernel and see if it boots. | | Then if no one has emailed alpha@freebsd.org reply and give your results. | If some one else has replied with your same type of Alpha and had the | same results, then there is no need to reply. But if you get a different | result, then I'd like to know it of course. PWS500au boots SMPng fine, the problem with cd0:isp0 not being detect exists on this box, exactly the same error messages. (for both Matt's 4BETA snapshot and HEAD buildworld) FreeBSD pdp11.ece.utexas.edu 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Nov 11 14:56:57 CST 2000 keichii@pdp11.ece.utexas.edu:/usr/obj/usr/src/sys/GENERIC alpha -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Nov 11 14:47:28 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 7BC5837B479 for ; Sat, 11 Nov 2000 14:47:26 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA21752; Sat, 11 Nov 2000 14:44:31 -0800 (PST) (envelope-from obrien) Date: Sat, 11 Nov 2000 14:44:31 -0800 From: "David O'Brien" To: "Michael C . Wu" Cc: Marcel Moolenaar , freebsd-alpha@FreeBSD.ORG Subject: Re: Crosscompiling from x86 host to alpha target Message-ID: <20001111144431.A21664@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20001111145311.A18007@peorth.iteration.net> <3A0DB4E9.C6C5D067@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A0DB4E9.C6C5D067@cup.hp.com>; from marcel@cup.hp.com on Sat, Nov 11, 2000 at 01:06:49PM -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: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Nov 11, 2000 at 01:06:49PM -0800, Marcel Moolenaar wrote: > "Michael C . Wu" wrote: > > > > I am trying to use our basesystem gcc to cross compile > > to an Alpha from my x86 box. David O'Brien told me to use > > > > export TARGET_MACHINE=alpha > > make buildworld > > Use MACHINE_ARCH. Don't use TARGET_MACHINE. Doh! Sorry, it was quite late at night when you asked and I had GCC on my mind (which set TARGET_MACHINE). > If you don't have the gcc patches, it'll probably fail compiling libmd > (which is quite early). With the gcc patches it fails for perl. > The gcc patches can be downloaded from http://people.freebsd.org/~marcel/ These patches are OBE. The first one being applied in src/contrib/gcc.295/config/alpha.c rev 1.2: Add missing prototypes. This allows cross building an Alpha Gcc on a 32-bit host to work. Obtained from: alpha-protos.h (GCC 2.96 / head branch of FSF/GCC CVS repo) A different form of the Makefile patch was committed along time ago. (These two changes also exist in the RELENG_4 branch.) -- -- 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 Sat Nov 11 21:31:32 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id BA39037B4CF; Sat, 11 Nov 2000 21:31:30 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 3AB64D36; Sat, 11 Nov 2000 21:31:30 -0800 (PST) Received: from cup.hp.com (p1000182.nsr.hp.com [15.109.0.182]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id VAA07667; Sat, 11 Nov 2000 21:31:26 -0800 (PST) Message-ID: <3A0E2B5B.5D2C22D0@cup.hp.com> Date: Sat, 11 Nov 2000 21:32:11 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: "Michael C . Wu" , freebsd-alpha@FreeBSD.ORG Subject: Re: Crosscompiling from x86 host to alpha target References: <20001111145311.A18007@peorth.iteration.net> <3A0DB4E9.C6C5D067@cup.hp.com> <20001111144431.A21664@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David O'Brien wrote: > > > If you don't have the gcc patches, it'll probably fail compiling libmd > > (which is quite early). With the gcc patches it fails for perl. > > The gcc patches can be downloaded from http://people.freebsd.org/~marcel/ > > These patches are OBE. The first one being applied in > src/contrib/gcc.295/config/alpha.c rev 1.2: > > Add missing prototypes. > This allows cross building an Alpha Gcc on a 32-bit host to work. > Obtained from: alpha-protos.h (GCC 2.96 / head branch of FSF/GCC CVS repo) > > A different form of the Makefile patch was committed along time ago. > (These two changes also exist in the RELENG_4 branch.) I should have known. Thanks! I'll remove the patches from my page. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message