From owner-freebsd-current Tue Nov 28 12:22: 6 2000 Delivered-To: freebsd-current@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 4282537B401 for ; Tue, 28 Nov 2000 12:22:04 -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 140rGM-0001TY-00; Tue, 28 Nov 2000 20:22:02 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eASKLBB01852; Tue, 28 Nov 2000 21:21:11 +0100 (CET) (envelope-from wkb) Date: Tue, 28 Nov 2000 21:21:10 +0100 From: Wilko Bulte To: Mike Eldridge Cc: Bernd Walter , freebsd-current@freebsd.org Subject: Re: Patch for current on LCA based alphas Message-ID: <20001128212110.A1820@freebie.demon.nl> References: <20001125193430.A40717@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: ; from diz@cafes.net on Mon, Nov 27, 2000 at 02:42:52PM -0600 X-OS: FreeBSD 4.2-RELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 27, 2000 at 02:42:52PM -0600, Mike Eldridge wrote: > On Sat, 25 Nov 2000, Bernd Walter wrote: > > LCA systems doesn't like probing after PCI slot 19. > > Probing slot 20 panics the system. > > The following patch made it into single user mode on my AXPpci33. > > I asume it will also work on multias. > > I can't tell more as the tested system is a 4.1-RELEASE and I need > > to update the world before further testing. > > Hmm, what exactly happens when slot 20 is probed? I remember my problems > with my Multia were related to PCI interrupts. It would spit out > "dec_axppci_33_intr_map: bad interrupt pin 192" about 50 or so times and > then panic. Wasn't this somehow related to the version of the SRM console code? -- 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-current" in the body of the message