From owner-freebsd-stable Mon Jul 22 00:35:36 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA24219 for stable-outgoing; Mon, 22 Jul 1996 00:35:36 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA24205; Mon, 22 Jul 1996 00:35:34 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id DAA00374; Mon, 22 Jul 1996 03:35:31 -0400 (EDT) Date: Mon, 22 Jul 1996 03:35:31 -0400 (EDT) From: "Marc G. Fournier" Reply-To: "Marc G. Fournier" To: current@freebsd.org, stable@freebsd.org Subject: ncr53c810 driver in stable/current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... for the second time today, my -stable machine has crashed, and hung while trying to reboot. the machine is using an ncr53c810 SCSI controller (the ASUS PC-200(sp?)) is the only SCSI controller in the box.... Now, I can live with the crashes, for now, but the fact that it is hanging on reboots is becoming a royal pain... The last time I reported this, someone made mention that the cause was the NCR driver not switching modes or something like that, so that it can't dump core...? If anyone remembers this thread, or knows what the hell I'm talking about...has this been fixed in -current? I've disabled savecore/dumpdev in /etc/sysconfig now, in the hopes that since it isn't setup to dump core, it won't try too...is this a correct assumption? thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Mon Jul 22 01:03:58 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA25271 for stable-outgoing; Mon, 22 Jul 1996 01:03:58 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA25264; Mon, 22 Jul 1996 01:03:53 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id BAA10665; Mon, 22 Jul 1996 01:03:56 -0700 (PDT) Message-Id: <199607220803.BAA10665@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: "Marc G. Fournier" cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: ncr53c810 driver in stable/current In-reply-to: Your message of "Mon, 22 Jul 1996 03:35:31 EDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 22 Jul 1996 01:03:56 -0700 Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > for the second time today, my -stable machine has crashed, >and hung while trying to reboot. the machine is using an ncr53c810 >SCSI controller (the ASUS PC-200(sp?)) is the only SCSI controller >in the box.... > > Now, I can live with the crashes, for now, but the fact that >it is hanging on reboots is becoming a royal pain... > > The last time I reported this, someone made mention that >the cause was the NCR driver not switching modes or something like >that, so that it can't dump core...? > > If anyone remembers this thread, or knows what the hell I'm >talking about...has this been fixed in -current? We've seen this problem on freefall (which uses the NCR controller). It likes to hang when we try to reboot it. I don't recall any fixes for this, and I don't know what causes it. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Mon Jul 22 14:03:45 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08418 for stable-outgoing; Mon, 22 Jul 1996 14:03:45 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA08403; Mon, 22 Jul 1996 14:03:41 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-5.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA19903 (5.67b/IDA-1.5); Mon, 22 Jul 1996 23:03:16 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id XAA04254; Mon, 22 Jul 1996 23:03:08 +0200 (MET DST) Date: Mon, 22 Jul 1996 23:03:08 +0200 (MET DST) Message-Id: <199607222103.XAA04254@x14.mi.uni-koeln.de> From: Stefan Esser To: dg@root.com Cc: "Marc G. Fournier" , current@freebsd.org, stable@freebsd.org Subject: Re: ncr53c810 driver in stable/current In-Reply-To: <199607220803.BAA10665@root.com> References: <199607220803.BAA10665@root.com> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > > for the second time today, my -stable machine has crashed, > >and hung while trying to reboot. the machine is using an ncr53c810 > >SCSI controller (the ASUS PC-200(sp?)) is the only SCSI controller > >in the box.... > > > > Now, I can live with the crashes, for now, but the fact that > >it is hanging on reboots is becoming a royal pain... > > > > The last time I reported this, someone made mention that > >the cause was the NCR driver not switching modes or something like > >that, so that it can't dump core...? > > > > If anyone remembers this thread, or knows what the hell I'm > >talking about...has this been fixed in -current? > > We've seen this problem on freefall (which uses the NCR controller). It > likes to hang when we try to reboot it. I don't recall any fixes for this, > and I don't know what causes it. Hmm, I have not heard about this problem on other systems ... Could both of you please send details on the configuration: 1) CPU class (eg. P5/133) 2) controller chip (810 or 825) 3) disk drives connected 4) type of hang (does the SDMS BIOS probe complete ?) Since 1-3) is reported in the boot messages, I'd like to receive a verbose boot log. Regarding the kernel dump: It used to work at a time, and I'm not sure what makes it fail. There was some way to obtain a kernel core with DDB at no risk of data corruption on the disk (which I couldn't take !), but I don't remember any details. I'll build a kernel with the debugger and will try to test the dump feature over the next few days. (Please allow 10 days for me to get it fixed ...) Regards, STefan From owner-freebsd-stable Mon Jul 22 14:11:15 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09129 for stable-outgoing; Mon, 22 Jul 1996 14:11:15 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA09113; Mon, 22 Jul 1996 14:11:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id OAA01034; Mon, 22 Jul 1996 14:10:42 -0700 (PDT) Message-Id: <199607222110.OAA01034@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Stefan Esser cc: "Marc G. Fournier" , current@freebsd.org, stable@freebsd.org Subject: Re: ncr53c810 driver in stable/current In-reply-to: Your message of "Mon, 22 Jul 1996 23:03:08 +0200." <199607222103.XAA04254@x14.mi.uni-koeln.de> From: David Greenman Reply-To: dg@root.com Date: Mon, 22 Jul 1996 14:10:42 -0700 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > We've seen this problem on freefall (which uses the NCR controller). It > > likes to hang when we try to reboot it. I don't recall any fixes for this, > > and I don't know what causes it. > >Hmm, I have not heard about this problem on other systems ... > >Could both of you please send details on the configuration: > >1) CPU class (eg. P5/133) P5/100 >2) controller chip (810 or 825) 810 >3) disk drives connected I don't have an exact answer to this at the moment, but I think freefall has three Quantum PD-1800, one Quantum Grand Prix (might be a Seagate Baracuda), and a Toshiba 3501 CDROM drive. >4) type of hang (does the SDMS BIOS probe complete ?) The hang is at shutdown, not startup. Jordan might be able to tell you if there are any console messages prior to the hang. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Mon Jul 22 14:35:24 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA12158 for stable-outgoing; Mon, 22 Jul 1996 14:35:24 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA12106; Mon, 22 Jul 1996 14:35:06 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id OAA29810; Mon, 22 Jul 1996 14:33:42 -0700 Date: Mon, 22 Jul 1996 14:33:40 -0700 (PDT) From: Veggy Vinny To: Stefan Esser cc: dg@root.com, "Marc G. Fournier" , current@freebsd.org, stable@freebsd.org Subject: Re: ncr53c810 driver in stable/current In-Reply-To: <199607222103.XAA04254@x14.mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Stefan Esser wrote: > David Greenman writes: > > > for the second time today, my -stable machine has crashed, > > >and hung while trying to reboot. the machine is using an ncr53c810 > > >SCSI controller (the ASUS PC-200(sp?)) is the only SCSI controller > > >in the box.... > > > > > > Now, I can live with the crashes, for now, but the fact that > > >it is hanging on reboots is becoming a royal pain... > > > > > > The last time I reported this, someone made mention that > > >the cause was the NCR driver not switching modes or something like > > >that, so that it can't dump core...? > > > > > > If anyone remembers this thread, or knows what the hell I'm > > >talking about...has this been fixed in -current? > > > > We've seen this problem on freefall (which uses the NCR controller). It > > likes to hang when we try to reboot it. I don't recall any fixes for this, > > and I don't know what causes it. > > Hmm, I have not heard about this problem on other systems ... > > Could both of you please send details on the configuration: > > 1) CPU class (eg. P5/133) > > 2) controller chip (810 or 825) > > 3) disk drives connected > > 4) type of hang (does the SDMS BIOS probe complete ?) > > Since 1-3) is reported in the boot messages, I'd like > to receive a verbose boot log. > > Regarding the kernel dump: It used to work at a time, > and I'm not sure what makes it fail. > > There was some way to obtain a kernel core with DDB at > no risk of data corruption on the disk (which I couldn't > take !), but I don't remember any details. I'll build a > kernel with the debugger and will try to test the dump > feature over the next few days. (Please allow 10 days > for me to get it fixed ...) Maybe it could be the SCSI Tags problem I had before? Vince From owner-freebsd-stable Mon Jul 22 14:42:22 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA12887 for stable-outgoing; Mon, 22 Jul 1996 14:42:22 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA12880; Mon, 22 Jul 1996 14:42:16 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-5.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA20278 (5.67b/IDA-1.5); Mon, 22 Jul 1996 23:41:47 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id XAA04311; Mon, 22 Jul 1996 23:41:45 +0200 (MET DST) Date: Mon, 22 Jul 1996 23:41:45 +0200 (MET DST) Message-Id: <199607222141.XAA04311@x14.mi.uni-koeln.de> From: Stefan Esser To: jkh@freebsd.org Cc: "Marc G. Fournier" , current@freebsd.org, stable@freebsd.org, dg@root.com Subject: Re: ncr53c810 driver in stable/current In-Reply-To: <199607222110.OAA01034@root.com> References: <199607222103.XAA04254@x14.mi.uni-koeln.de> <199607222110.OAA01034@root.com> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > > > We've seen this problem on freefall (which uses the NCR controller). It > > > likes to hang when we try to reboot it. I don't recall any fixes for this, > > > and I don't know what causes it. > > > >Hmm, I have not heard about this problem on other systems ... > > > >Could both of you please send details on the configuration: > > > >1) CPU class (eg. P5/133) > > P5/100 Hmm, I had been thinking of a problem with a very fast CPU. > >2) controller chip (810 or 825) > > 810 Ok. > >3) disk drives connected > > I don't have an exact answer to this at the moment, but I think freefall > has three Quantum PD-1800, one Quantum Grand Prix (might be a Seagate > Baracuda), and a Toshiba 3501 CDROM drive. Also nothing special. > >4) type of hang (does the SDMS BIOS probe complete ?) > > The hang is at shutdown, not startup. Jordan might be able to tell you if > there are any console messages prior to the hang. Ok. I guess Jordan is reading this anyway: Please provide me with details: 1) does the system complete the final sync ? 2) does it clear the screen in preparation of a warm boot ? 3) does it require a power-off or can it be made to boot by some other means (Ctl-Alt-Del) ? 4) does it always hang ? 5) do you know that the hang is not caused by some unrelated problem (BROKEN_KEYBOARD_RESET comes to mind :) ? Regards, STefan From owner-freebsd-stable Mon Jul 22 15:04:47 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15012 for stable-outgoing; Mon, 22 Jul 1996 15:04:47 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14996; Mon, 22 Jul 1996 15:04:35 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id SAA14584; Mon, 22 Jul 1996 18:04:17 -0400 (EDT) Date: Mon, 22 Jul 1996 18:04:16 -0400 (EDT) From: "Marc G. Fournier" To: Stefan Esser cc: jkh@freebsd.org, current@freebsd.org, stable@freebsd.org, dg@root.com Subject: Re: ncr53c810 driver in stable/current In-Reply-To: <199607222141.XAA04311@x14.mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Stefan Esser wrote: > David Greenman writes: > > > > We've seen this problem on freefall (which uses the NCR controller). It > > > > likes to hang when we try to reboot it. I don't recall any fixes for this, > > > > and I don't know what causes it. > > > > > >Hmm, I have not heard about this problem on other systems ... > > > > > >Could both of you please send details on the configuration: > > > > > >1) CPU class (eg. P5/133) > > > > P5/100 > > Hmm, I had been thinking of a problem with a very fast CPU. > 486DX4-100 here > > >2) controller chip (810 or 825) > > > > 810 > > Ok. > Same > > >3) disk drives connected > > > > I don't have an exact answer to this at the moment, but I think freefall > > has three Quantum PD-1800, one Quantum Grand Prix (might be a Seagate > > Baracuda), and a Toshiba 3501 CDROM drive. > > Also nothing special. > (ncr0:0:0): "QUANTUM FIREBALL1280S 630C" type 0 fixe (ncr0:1:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI (ncr0:2:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fi (ncr0:3:0): "CONNER CFP1060S 1.05GB 243F" type 0 fix > > >4) type of hang (does the SDMS BIOS probe complete ?) > > > > The hang is at shutdown, not startup. Jordan might be able to tell you if > > there are any console messages prior to the hang. > Same, on shutdown, not startup... > Ok. I guess Jordan is reading this anyway: > > Please provide me with details: > > 1) does the system complete the final sync ? No, this is where it hangs... > 2) does it clear the screen in preparation of a warm boot ? No, see 1 > 3) does it require a power-off or can it be made to boot > by some other means (Ctl-Alt-Del) ? requires a power-off, but am not 100% certain, since I've gotten into the habit of doing a cold boot (99.9% certain the habit is because ctl-alt-del didn't work) > 4) does it always hang ? Everytime it crashes, yes...doing reboot from the console has never hung it... > 5) do you know that the hang is not caused by some unrelated > problem (BROKEN_KEYBOARD_RESET comes to mind :) ? > No, how would I find out? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Mon Jul 22 15:30:30 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA16853 for stable-outgoing; Mon, 22 Jul 1996 15:30:30 -0700 (PDT) Received: from troll.uunet.ca (troll.uunet.ca [142.77.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA16847; Mon, 22 Jul 1996 15:30:27 -0700 (PDT) Received: from localhost by troll.uunet.ca with SMTP id <21007-20218>; Mon, 22 Jul 1996 18:30:17 -0400 Date: Mon, 22 Jul 1996 18:30:10 -0400 From: Cat Okita To: "Marc G. Fournier" cc: Stefan Esser , jkh@freebsd.org, current@freebsd.org, stable@freebsd.org, dg@Root.COM Subject: Re: ncr53c810 driver in stable/current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Marc G. Fournier wrote: > Same, on shutdown, not startup... I have a vague recollection of a panic on not being able to write to assigned vnode (or something along those lines - it *was* 3:30am) > requires a power-off, but am not 100% certain, since I've gotten > into the habit of doing a cold boot (99.9% certain the habit is because > ctl-alt-del didn't work) Definately requires a power off - the keyboard doesn't respond to any key or combination that I've tried. > > 4) does it always hang ? > Everytime it crashes, yes...doing reboot from the console > has never hung it... *Only* when it crashes - a planned reboot, be it remote or local always seems to work. Cat From owner-freebsd-stable Tue Jul 23 05:18:28 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA10017 for stable-outgoing; Tue, 23 Jul 1996 05:18:28 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA09955; Tue, 23 Jul 1996 05:15:50 -0700 (PDT) Received: from schubert.Promo.DE by mail.crl.com with SMTP id AA19940 (5.65c/IDA-1.5); Tue, 23 Jul 1996 05:15:04 -0700 Received: from quick.promo.de (quick.Promo.DE [194.45.188.67]) by schubert.promo.de (8.6.12/8.6.12) with SMTP id KAA20515; Tue, 23 Jul 1996 10:31:41 +0200 Message-Id: Date: 23 Jul 1996 10:32:08 +0200 From: "Stefan Bethke" Subject: Re: ncr53c810 driver in sta To: jkh@FreeBSD.org, "Stefan Esser" Cc: current@FreeBSD.org, dg@root.com, "Marc G. Fournier" , stable@FreeBSD.org X-Mailer: Mail*Link SMTP-QM 3.0.2 Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; Name="Message Body" Content-Transfer-Encoding: quoted-printable Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk We have a similiar problem here: Asus SP3G-II (Neptune II chipset), 810, = Quantum Fireball, but I'm not sure it is related to the 810 in any way. It hangs sometimes on reboots, after clearing the screen. However, when = it does, it corrupts the BIOS nvram, so I have to re-enter all BIOS = settings :-( Currently, I always halt the machine and do a reset; this never caused = the problem to occur. > Ok. I guess Jordan is reading this anyway: > Please provide me with details: > 1) does the system complete the final sync ? > 2) does it clear the screen in preparation of a warm boot ? > 3) does it require a power-off or can it be made to boot > by some other means (Ctl-Alt-Del) ? > 4) does it always hang ? > 5) do you know that the hang is not caused by some unrelated > problem (BROKEN_KEYBOARD_RESET comes to mind :) ? Can you give me a pointer where to find an explanation of the broken = reset? Stefan -- Promo Datentechnik | Tel. +49-40-431360-0 + Systemberatung GmbH | Fax. +49-40-431360-60 Waterloohain 6-8 | e-mail: stefan@Promo.DE D-22769 Hamburg | http://www.Promo.DE/ From owner-freebsd-stable Tue Jul 23 06:40:04 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA13865 for stable-outgoing; Tue, 23 Jul 1996 06:40:04 -0700 (PDT) Received: from xwing.wcape.gov.za (xwing.wcape.gov.za [164.151.101.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA13826 for ; Tue, 23 Jul 1996 06:39:43 -0700 (PDT) Received: from jedi.wcape.gov.za. (jedi.wcape.gov.za [164.151.101.248]) by xwing.wcape.gov.za (8.6.12/8.6.12) with ESMTP id PAA05905 for ; Tue, 23 Jul 1996 15:48:18 +0200 Received: from JEDI/MAILQ by jedi.wcape.gov.za. (Mercury 1.21); 23 Jul 96 14:49:21 +0200 Received: from MAILQ by JEDI (Mercury 1.21); 23 Jul 96 14:48:58 +0200 From: "Sean White" Organization: CCS: Western Cape - OpeNET project To: stable@freebsd.org Date: Tue, 23 Jul 1996 14:48:53 +0200 Subject: PCI bus... or why I don't like Acer Reply-to: swhite@gov.za Priority: normal X-mailer: Pegasus Mail for Windows (v2.22) Message-ID: <31927694E70@jedi.wcape.gov.za.> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hiya, all! I've downloaded the 2.1.5-R boot floppy and briefly checked the Acer machine that gave me so many problems before with 2.1.0-R ... Hi Stefan! The problem detecting the PCI bus is still there. Now, I'm quite happy that it's not FreeBSD's fault at all, more the rather strange PCI setup in this particular machine. My fix for 2.1.0-R was to compile a custom kernel which reversed the PCI config mode probes (mode 2 before mode 1) and this has proven to work quite successfully. I've also tested the modified kernel on a couple of other machines including IBM and Unisys with no problems either. Compaq Prolinea model 590 machines are still a problem but I couldn't be bothered with those things anyway. Don't have one, don't want one. My question is, would anything be broken or disadvantaged if this change was incorporated into the FreeBSD release, obviously in a later version? Would the "team" be prepared to consider such a change? I'll happily post a diff for pcibus.c here if anyone is interested. My thanks again go to Stefan Esser for the help given in getting 2.1.0-R to run on this machine. Regards, Sean. +--------------------+----------------------+------------------------------+ | CCS: Western Cape | Tel: +27-21-462-2780 | DISCLAIMER: Any opinions ex- | | Private Bag X1 | Fax: +27-21-462-2791 | pressed above are *MINE*! If | | 8012 ROGGEBAAI | swhite@gov.za. | you want my boss's, ask him. | +--------------------+----------------------+------------------------------+ "Eagles may soar, but weasels don't get sucked into jet engine intakes" From owner-freebsd-stable Tue Jul 23 07:34:59 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA16439 for stable-outgoing; Tue, 23 Jul 1996 07:34:59 -0700 (PDT) Received: from solar.os.com (root@solar.os.com [199.232.136.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA16430 for ; Tue, 23 Jul 1996 07:34:55 -0700 (PDT) Received: from jupiter.os.com (jupiter.os.com [199.232.136.66]) by solar.os.com (8.7/8.7.0) with SMTP id KAA24572 for ; Tue, 23 Jul 1996 10:45:25 -0400 Message-Id: <1.5.4.32.19960723143144.0073e690@solar> X-Sender: craigs@solar X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 23 Jul 1996 10:31:44 -0400 To: stable@freebsd.org From: Craig Shrimpton Subject: 3C509 Combo problem on 2.1.5 (networking crashes) Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Folks, I'm not sure if this list is also for the new release, if not please point me elsewhere. I posted this to USNET but perhaps someone here has an answer. I have just installed FreeBSD 2.1.5 and am very unhappy. For some reason my 3C509 Combo card or the netwoking in general, simply quits. Everything starts out fine but if I try to ftp anything bigger than a few bytes, the networking craps out. Ftp dies and telnet, ping, etc. stop working. There are no error messages and all the daemons seem to be running. Only a reboot fixes it. All the same stuff I use with 2.1 is in the 2.1.5 kernel. It's very perplexing. Oh yes, one thing I didn't mention in my other post: ping localhost stops responding as well. It is apparently a complete networking failure (probably caused by the card). This card in this same machine will run: Win 3.1x Win NT 3.51 Win NT 4.0 Win95 FreeBSD 2.1.0 But *NOT* 2.1.5 Any ideas? Thanks, Craig =================================================================== Orbit Internet Email: craigs@os.com 400 Grove Street Phone: (508) 753-8776 Worcester, MA 01605 http://www.os.com/ From owner-freebsd-stable Tue Jul 23 08:40:28 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA21117 for stable-outgoing; Tue, 23 Jul 1996 08:40:28 -0700 (PDT) Received: from mispwoso.nosc.mil (mispwoso.nosc.mil [198.253.27.55]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA21104; Tue, 23 Jul 1996 08:40:24 -0700 (PDT) Received: (from huck@localhost) by mispwoso.nosc.mil (8.7.5/8.7.3) id LAA19629; Tue, 23 Jul 1996 11:39:45 -0400 (EDT) From: Craig Huckabee Message-Id: <199607231539.LAA19629@mispwoso.nosc.mil> Subject: Re: ncr53c810 driver in sta To: stefan@promo.de (Stefan Bethke), jkh@freebsd.org, se@zpr.uni-koeln.de, dg@root.com, scrappy@ki.net Date: Tue, 23 Jul 1996 11:39:45 -0400 (EDT) Cc: current@freebsd.org, stable@freebsd.org In-Reply-To: from Stefan Bethke at "Jul 23, 96 10:32:08 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > We have a similiar problem here: Asus SP3G-II (Neptune II chipset), 810, Quantum Fireball, but I'm not sure it is related to the 810 in any way. > > It hangs sometimes on reboots, after clearing the screen. However, when it does, it corrupts the BIOS nvram, so I have to re-enter all BIOS settings :-( > Same problem here: I issue a 'reboot' (or a 'shutdown -r') command. Disk synchs up. Screen goes black. Machine is dead. When I do a cold boot the BIOS nvram is hosed. Machine: ASUS PCI/E-P54NP4 ASUS SC-200 NCR SCSI controller (1) MAXTOR MXT-540SL hard drive (2) HITACHI DK517C-37 hard drives My answers to the questions : > > 1) does the system complete the final sync ? Yes. > > 2) does it clear the screen in preparation of a warm boot ? Yes, screen goes black. > > 3) does it require a power-off or can it be made to boot > > by some other means (Ctl-Alt-Del) ? A cold boot or a reset works. > > 4) does it always hang ? Yes. > > 5) do you know that the hang is not caused by some unrelated > > problem (BROKEN_KEYBOARD_RESET comes to mind :) ? Nope. Thanks, Craig > Currently, I always halt the machine and do a reset; this never caused the problem to occur. > > > Ok. I guess Jordan is reading this anyway: > > > Please provide me with details: > > > 1) does the system complete the final sync ? > > 2) does it clear the screen in preparation of a warm boot ? > > 3) does it require a power-off or can it be made to boot > > by some other means (Ctl-Alt-Del) ? > > 4) does it always hang ? > > 5) do you know that the hang is not caused by some unrelated > > problem (BROKEN_KEYBOARD_RESET comes to mind :) ? > > Can you give me a pointer where to find an explanation of the broken reset? > > Stefan > -- > Promo Datentechnik | Tel. +49-40-431360-0 > + Systemberatung GmbH | Fax. +49-40-431360-60 > Waterloohain 6-8 | e-mail: stefan@Promo.DE > D-22769 Hamburg | http://www.Promo.DE/ > From owner-freebsd-stable Tue Jul 23 11:01:56 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA00410 for stable-outgoing; Tue, 23 Jul 1996 11:01:56 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA00405 for ; Tue, 23 Jul 1996 11:01:54 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id LAA21767; Tue, 23 Jul 1996 11:01:42 -0700 (PDT) To: Craig Shrimpton cc: stable@freebsd.org Subject: Re: 3C509 Combo problem on 2.1.5 (networking crashes) In-reply-to: Your message of "Tue, 23 Jul 1996 10:31:44 EDT." <1.5.4.32.19960723143144.0073e690@solar> Date: Tue, 23 Jul 1996 11:01:41 -0700 Message-ID: <21765.838144901@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have just installed FreeBSD 2.1.5 and am very unhappy. For some reason my > 3C509 Combo card or the netwoking in general, simply quits. Everything Did you get this release from ftp.freebsd.org? If not, you may have been going to a mirror which is out of date and had the broken 2.1.5 release on it (please subscribe to the announce mailing list if you don't already - all of this was covered there). Jordan From owner-freebsd-stable Tue Jul 23 13:09:15 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA08899 for stable-outgoing; Tue, 23 Jul 1996 13:09:15 -0700 (PDT) Received: from solar.os.com (craigs@solar.os.com [199.232.136.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA08894 for ; Tue, 23 Jul 1996 13:09:11 -0700 (PDT) Received: (from craigs@localhost) by solar.os.com (8.7/8.7.0) id QAA25205; Tue, 23 Jul 1996 16:19:48 -0400 Date: Tue, 23 Jul 1996 16:19:48 -0400 From: Craig Shrimpton Subject: Re: 3C509 Combo problem on 2.1.5 (networking crashes) To: "Jordan K. Hubbard" cc: stable@FreeBSD.org In-Reply-To: <21765.838144901@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Jul 1996, Jordan K. Hubbard wrote: > > Did you get this release from ftp.freebsd.org? If not, you may have > been going to a mirror which is out of date and had the broken 2.1.5 Thanks, I got the dist. from ftp6.freebsd.org. Since Sprint can't keep BPG running to CIX, ftp.freebsd.org is not reachable for more than 10 mins. at a time. :-( Any other "known good" archives? -Craig +------------------------------------+--------------------------------------+ | Craig Shrimpton | e-mail: craigs@os.com | | Orbit Systems | information: info@os.com | | Worcester, MA 508.753.8776 | http://www.os.com/ | +------------------------------------+--------------------------------------+ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/ _/_/_/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/_/ _/ _/ _/_/_/_/ _/_/_/_/ _/ Strategic Systems From owner-freebsd-stable Tue Jul 23 13:33:47 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA10584 for stable-outgoing; Tue, 23 Jul 1996 13:33:47 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA10579 for ; Tue, 23 Jul 1996 13:33:44 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id NAA00698; Tue, 23 Jul 1996 13:33:38 -0700 (PDT) To: Craig Shrimpton cc: stable@FreeBSD.org Subject: Re: 3C509 Combo problem on 2.1.5 (networking crashes) In-reply-to: Your message of "Tue, 23 Jul 1996 16:19:48 EDT." Date: Tue, 23 Jul 1996 13:33:37 -0700 Message-ID: <696.838154017@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Nope, just the one. > On Tue, 23 Jul 1996, Jordan K. Hubbard wrote: > > > > > Did you get this release from ftp.freebsd.org? If not, you may have > > been going to a mirror which is out of date and had the broken 2.1.5 > > Thanks, I got the dist. from ftp6.freebsd.org. Since Sprint can't keep > BPG running to CIX, ftp.freebsd.org is not reachable for more than 10 mins. > at a time. :-( Any other "known good" archives? > > -Craig > > +------------------------------------+--------------------------------------+ > | Craig Shrimpton | e-mail: craigs@os.com | > | Orbit Systems | information: info@os.com | > | Worcester, MA 508.753.8776 | http://www.os.com/ | > +------------------------------------+--------------------------------------+ > > _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ > _/ _/ _/ _/ _/ _/ _/ _/ > _/ _/ _/_/_/ _/_/_/_/ _/ _/ > _/ _/ _/ _/ _/ _/ _/ _/ > _/_/_/_/ _/ _/ _/_/_/_/ _/_/_/_/ _/ > > Strategic Systems > > From owner-freebsd-stable Tue Jul 23 13:41:37 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11114 for stable-outgoing; Tue, 23 Jul 1996 13:41:37 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA11091; Tue, 23 Jul 1996 13:41:29 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id NAA00779; Tue, 23 Jul 1996 13:41:27 -0700 (PDT) To: stable@freebsd.org cc: freebsd-hubs@freebsd.org Subject: Mirror maintainers - please check your 2.1.5-RELEASE directory! Date: Tue, 23 Jul 1996 13:41:27 -0700 Message-ID: <777.838154487@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If your floppies/boot.flp image doesn't match the following MD5 signature: MD5 (boot.flp) = 234b975b63251a11382da8166dd292e6 Then you probably have the "replaced" 2.1.5-RELEASE and need to repopulate your mirror. We've been getting some complaints that many of the mirrors are out of date. Thanks! Jordan From owner-freebsd-stable Tue Jul 23 14:10:29 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA13643 for stable-outgoing; Tue, 23 Jul 1996 14:10:29 -0700 (PDT) Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA13632 for ; Tue, 23 Jul 1996 14:10:22 -0700 (PDT) Received: from 199.183.109.242 by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Tue, 23 Jul 1996 16:10:05 -0600 Message-ID: Date: 23 Jul 1996 16:09:20 -0500 From: "Richard Wackerbarth" Subject: Re: Mirror maintainers - please check your 2.1.5-RELEASE directory! To: "freebsd-hubs@freebsd.org" , "Jordan K. Hubbard" , "stable@freebsd.org" X-Mailer: Mail*Link PT/Internet 1.6.0 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan writes: > If your floppies/boot.flp image doesn't match the following MD5 > signature: > > MD5 (boot.flp) = 234b975b63251a11382da8166dd292e6 > > Then you probably have the "replaced" 2.1.5-RELEASE and need to > repopulate your mirror. We've been getting some complaints that many > of the mirrors are out of date. I assume that you mean that "you DON'T have". IOW, you have given the signature of the good file. -- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-stable Tue Jul 23 16:53:34 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA25012 for stable-outgoing; Tue, 23 Jul 1996 16:53:34 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA25005; Tue, 23 Jul 1996 16:53:32 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id QAA01151; Tue, 23 Jul 1996 16:53:20 -0700 (PDT) To: "Richard Wackerbarth" cc: "freebsd-hubs@freebsd.org" , "stable@freebsd.org" Subject: Re: Mirror maintainers - please check your 2.1.5-RELEASE directory! In-reply-to: Your message of "23 Jul 1996 16:09:20 CDT." Date: Tue, 23 Jul 1996 16:53:19 -0700 Message-ID: <1149.838165999@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Jordan writes: > > If your floppies/boot.flp image doesn't match the following MD5 > > signature: > > > > MD5 (boot.flp) = 234b975b63251a11382da8166dd292e6 > > > > Then you probably have the "replaced" 2.1.5-RELEASE and need to > > repopulate your mirror. We've been getting some complaints that many > > of the mirrors are out of date. > > > I assume that you mean that "you DON'T have". IOW, you have given the > signature of the good file. No, I mean DO have. As in "have the replaced 2.1.5 RELEASE" vs "have the FINAL 2.1.5 RELEASE." I've re-read my message several times and it's perfectly correct. Jordan From owner-freebsd-stable Tue Jul 23 19:54:47 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA06173 for stable-outgoing; Tue, 23 Jul 1996 19:54:47 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA06163; Tue, 23 Jul 1996 19:54:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id TAA03553; Tue, 23 Jul 1996 19:54:32 -0700 (PDT) Message-Id: <199607240254.TAA03553@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" cc: "Richard Wackerbarth" , "freebsd-hubs@freebsd.org" , "stable@freebsd.org" Subject: Re: Mirror maintainers - please check your 2.1.5-RELEASE directory! In-reply-to: Your message of "Tue, 23 Jul 1996 16:53:19 PDT." <1149.838165999@time.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 23 Jul 1996 19:54:32 -0700 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Jordan writes: >> > If your floppies/boot.flp image doesn't match the following MD5 >> > signature: >> > >> > MD5 (boot.flp) = 234b975b63251a11382da8166dd292e6 >> > >> > Then you probably have the "replaced" 2.1.5-RELEASE and need to >> > repopulate your mirror. We've been getting some complaints that many >> > of the mirrors are out of date. >> >> >> I assume that you mean that "you DON'T have". IOW, you have given the >> signature of the good file. > >No, I mean DO have. As in "have the replaced 2.1.5 RELEASE" vs "have >the FINAL 2.1.5 RELEASE." I've re-read my message several times and >it's perfectly correct. Perhaps I should be less ambiguous: ftp2.freebsd.org and ftp6.freebsd.org have the old, broken version. ftp4.freebsd.org doesn't have 2.1.5 at all. ftp, ftp3, ftp5, and ftp7 are the only ftp.freebsd.org sites that have the updated copy. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Wed Jul 24 22:01:41 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA16195 for stable-outgoing; Wed, 24 Jul 1996 22:01:41 -0700 (PDT) Received: from silver.sms.fi (root@silver.sms.fi [194.111.122.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA16180 for ; Wed, 24 Jul 1996 22:01:17 -0700 (PDT) Received: (from pete@localhost) by silver.sms.fi (8.7.5/8.6.9) id IAA09106; Thu, 25 Jul 1996 08:00:40 +0300 (EET DST) Date: Thu, 25 Jul 1996 08:00:40 +0300 (EET DST) Message-Id: <199607250500.IAA09106@silver.sms.fi> From: Petri Helenius To: freebsd-stable@freebsd.org Subject: ssh port Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is the ssh port broken, I just get this: pelican# make install >> ssh-1.2.14.tar.gz doesn't seem to exist on this system. >> Attempting to fetch from ftp://ftp.cs.hut.fi/pub/ssh/. Receiving ssh-1.2.14.tar.gz (587071 bytes): 100% 587071 bytes transfered in 1.1 seconds (519.33 K/s) >> Checksum mismatch for ssh-1.2.14.tar.gz *** Error code 1 Stop. Pete From owner-freebsd-stable Fri Jul 26 03:44:36 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA21065 for stable-outgoing; Fri, 26 Jul 1996 03:44:36 -0700 (PDT) Received: from zit1.zit.th-darmstadt.de (root@zit1.zit.th-darmstadt.de [130.83.63.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA21057; Fri, 26 Jul 1996 03:44:25 -0700 (PDT) Received: from [130.83.63.13] (apfel.zit.th-darmstadt.de [130.83.63.13]) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) with ESMTP id MAA05550; Fri, 26 Jul 1996 12:43:54 +0200 (MET DST) X-Sender: petzi@mail.zit.th-darmstadt.de Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 26 Jul 1996 12:43:28 +0200 To: "Stefan Bethke" From: Michael Beckmann Subject: Re: ncr53c810 driver in sta Cc: current@freebsd.org, stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 10:32 Uhr +0200 23.7.1996, Stefan Bethke wrote: >We have a similiar problem here: Asus SP3G-II (Neptune II chipset), I was under the impression that the SP3G had a Saturn II Chipset. >It hangs sometimes on reboots, after clearing the screen. However, when it >does, it corrupts the BIOS nvram, so I have to re-enter all BIOS settings >:-( That happened to me, too, when I was still using an SP3G mainboard. Later I upgraded it with a Gigabyte 586 ATE/P mainboard, and recently with a Gigabyte 586 HX mainboard; both equipped with an Asus SC-200 PCI controller (NCR 53c810 based); and with both Gigabyte board / Asus controller combinations I have never had a problem. Michael From owner-freebsd-stable Fri Jul 26 13:11:34 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA20746 for stable-outgoing; Fri, 26 Jul 1996 13:11:34 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA20708; Fri, 26 Jul 1996 13:11:20 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA02113 (5.67b/IDA-1.5); Fri, 26 Jul 1996 22:10:13 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id WAA00324; Fri, 26 Jul 1996 22:09:39 +0200 (MET DST) Date: Fri, 26 Jul 1996 22:09:39 +0200 (MET DST) Message-Id: <199607262009.WAA00324@x14.mi.uni-koeln.de> From: Stefan Esser To: Cat Okita Cc: "Marc G. Fournier" , Stefan Esser , jkh@freebsd.org, current@freebsd.org, stable@freebsd.org, dg@root.com Subject: Obtaining a kernel core with NCR In-Reply-To: References: Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Cat Okita writes: > > > 4) does it always hang ? > > Everytime it crashes, yes...doing reboot from the console > > has never hung it... > > *Only* when it crashes - a planned reboot, be it remote or local always seems > to work. Well, I just thought it might be a good idea to let you know, whether your system suffers form the same hang in the kernel dump code as mine. If you can afford the time to test this, I'd really appreciate receiving your results! The test requires a kernel compile a few more minutes of time for a the actual test. It does not cause a corrupt or dirty file system to be left over. (The FS is mounted R/O in single user mode anyway). 1) build a kernel with options "SCSI_DEBUG_FLAGS=DEBUG_SCATTER" options DDB 2) boot this kernel into single user mode 3) enter the command "dumpon /dev/sd0b" if you did not already define the dump device on the "config kernel" line in the config file 4) enter DDB by pressing CTL+ALT+ESC or CTL+Print depending on your keyboard (this is for syscons, don't know about PCVT) 5) enter the command "panic" at the debugger prompt. You will see a lot of trace output flow by, and it will stop with the well-known SCSI hang. My guess is, that the physical address of the last memory page touched is in the BIOS region. Please let me know what actual addresses (virtual and physical) there are at the start of the last scatter/gather block reported. Regards, STefan From owner-freebsd-stable Fri Jul 26 13:19:00 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21334 for stable-outgoing; Fri, 26 Jul 1996 13:19:00 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA21323; Fri, 26 Jul 1996 13:18:55 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA02248 (5.67b/IDA-1.5); Fri, 26 Jul 1996 22:18:45 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00305; Fri, 26 Jul 1996 21:45:55 +0200 (MET DST) Date: Fri, 26 Jul 1996 21:45:55 +0200 (MET DST) Message-Id: <199607261945.VAA00305@x14.mi.uni-koeln.de> From: Stefan Esser To: Michael Beckmann Cc: current@freebsd.org, stable@freebsd.org Subject: Re: ncr53c810 driver in sta In-Reply-To: References: Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Beckmann writes: > At 10:32 Uhr +0200 23.7.1996, Stefan Bethke wrote: > > >We have a similiar problem here: Asus SP3G-II (Neptune II chipset), > > I was under the impression that the SP3G had a Saturn II Chipset. Mine does :) > >It hangs sometimes on reboots, after clearing the screen. However, when it > >does, it corrupts the BIOS nvram, so I have to re-enter all BIOS settings > >:-( > > That happened to me, too, when I was still using an SP3G mainboard. The ASUS SP3G seems to need a "options BROKEN_KEYBOARD_RESET" line in the kernel config file. Mine does ... > Later I upgraded it with a Gigabyte 586 ATE/P mainboard, and recently with > a Gigabyte 586 HX mainboard; both equipped with an Asus SC-200 PCI > controller (NCR 53c810 based); and with both Gigabyte board / Asus > controller combinations I have never had a problem. That's not at all related to the SCSI controller. Regards, STefan From owner-freebsd-stable Fri Jul 26 13:19:45 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21514 for stable-outgoing; Fri, 26 Jul 1996 13:19:45 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA21443; Fri, 26 Jul 1996 13:19:32 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA02251 (5.67b/IDA-1.5); Fri, 26 Jul 1996 22:18:48 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00315; Fri, 26 Jul 1996 21:57:50 +0200 (MET DST) Date: Fri, 26 Jul 1996 21:57:50 +0200 (MET DST) Message-Id: <199607261957.VAA00315@x14.mi.uni-koeln.de> From: Stefan Esser To: Cat Okita Cc: "Marc G. Fournier" , Stefan Esser , jkh@freebsd.org, current@freebsd.org, stable@freebsd.org, dg@root.com Subject: Re: ncr53c810 driver in stable/current In-Reply-To: References: Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Cat Okita writes: > On Mon, 22 Jul 1996, Marc G. Fournier wrote: > > Same, on shutdown, not startup... > > I have a vague recollection of a panic on not being able to write to assigned > vnode (or something along those lines - it *was* 3:30am) > > > requires a power-off, but am not 100% certain, since I've gotten > > into the habit of doing a cold boot (99.9% certain the habit is because > > ctl-alt-del didn't work) > > Definately requires a power off - the keyboard doesn't respond to any key > or combination that I've tried. > > > > 4) does it always hang ? > > Everytime it crashes, yes...doing reboot from the console > > has never hung it... > > *Only* when it crashes - a planned reboot, be it remote or local always seems > to work. Ok. Today I found some time to have my system crash for the sake of science :-) Well, the hang occurs and it really can't be interrupted from the keyboard. But the code did work at some time, and it in fact still does. Mostly ... The dump writes out the first few MB within less than a second, and then the SCSI LED stays on and the system hangs, always after accessing the same virtual address. It took me some time to think about checking which physical address that corresponds to that page, and to my surprise I found that the BIOS region at e8000 is the last thing touched by the NCR chip. I have no idea why the page at 0e8000 is mapped into the kernel, and I do not think that I got some device at that address. But it still causes the hang :( I will add a debugging printf to the VM code, to identify the subroutine that registers a mapping for that physical address. Just wanted to let those interested in obtaining core dumps with the NCR know, that I'm working on this. I'd really appreciate if somebody could tell me why writing the page at 0e8000 to disk is a bad idea :) Regards, STefan From owner-freebsd-stable Fri Jul 26 13:20:03 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21637 for stable-outgoing; Fri, 26 Jul 1996 13:20:03 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA21573; Fri, 26 Jul 1996 13:19:55 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA02254 (5.67b/IDA-1.5); Fri, 26 Jul 1996 22:18:52 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00299; Fri, 26 Jul 1996 21:43:44 +0200 (MET DST) Date: Fri, 26 Jul 1996 21:43:44 +0200 (MET DST) Message-Id: <199607261943.VAA00299@x14.mi.uni-koeln.de> From: Stefan Esser To: "Stefan Bethke" Cc: jkh@freebsd.org, "Stefan Esser" , current@freebsd.org, dg@root.com, "Marc G. Fournier" , stable@freebsd.org Subject: Re: ncr53c810 driver in sta In-Reply-To: References: Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stefan Bethke writes: > We have a similiar problem here: Asus SP3G-II (Neptune II chipset), 810, = > Quantum Fireball, but I'm not sure it is related to the 810 in any way. Well, the SP3G has originally been delivered with a Saturn II (rev. 4) chip set. Guess that is what you got ... (???) > It hangs sometimes on reboots, after clearing the screen. However, when = > it does, it corrupts the BIOS nvram, so I have to re-enter all BIOS = > settings :-( This is most likely a problem with your NVRAM (ie. a hardware problem). > > 5) do you know that the hang is not caused by some unrelated > > problem (BROKEN_KEYBOARD_RESET comes to mind :) ? > > Can you give me a pointer where to find an explanation of the broken = > reset? This has been discussed a few months ago. You may try to seach for the key word in an archive of the mailing lists. I had to add the "options BROKEN_KEYBOARD_RESET" line to the kernel config file of my ASUS SP3g ... Regards, STefan From owner-freebsd-stable Fri Jul 26 14:21:50 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA27733 for stable-outgoing; Fri, 26 Jul 1996 14:21:50 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA27720 for ; Fri, 26 Jul 1996 14:21:45 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA03202 (5.67b/IDA-1.5 for ); Fri, 26 Jul 1996 23:21:05 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id XAA00503; Fri, 26 Jul 1996 23:19:48 +0200 (MET DST) Date: Fri, 26 Jul 1996 23:19:48 +0200 (MET DST) Message-Id: <199607262119.XAA00503@x14.mi.uni-koeln.de> From: Stefan Esser To: swhite@gov.za Cc: stable@freebsd.org Subject: Re: PCI bus... or why I don't like Acer In-Reply-To: <31927694E70@jedi.wcape.gov.za.> References: <31927694E70@jedi.wcape.gov.za.> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sean White writes: > Hiya, all! > > I've downloaded the 2.1.5-R boot floppy and briefly checked the Acer > machine that gave me so many problems before with 2.1.0-R ... Hi Stefan! > > The problem detecting the PCI bus is still there. Now, I'm quite happy that > it's not FreeBSD's fault at all, more the rather strange PCI setup in this > particular machine. My fix for 2.1.0-R was to compile a custom kernel which > reversed the PCI config mode probes (mode 2 before mode 1) and this has > proven to work quite successfully. I've also tested the modified kernel on > a couple of other machines including IBM and Unisys with no problems > either. Compaq Prolinea model 590 machines are still a problem but I > couldn't be bothered with those things anyway. Don't have one, don't want > one. Hmmm, they should work, too ... If anybody has problems with the PCI probe of an unpatched 2.1.5 kernel on his system, please let me know and send verbose boot messages! > My question is, would anything be broken or disadvantaged if this change > was incorporated into the FreeBSD release, obviously in a later version? > Would the "team" be prepared to consider such a change? I'll happily post a > diff for pcibus.c here if anyone is interested. Well, there are several problems with reversing the order of the probes. Did you test the boot floppy from the latest 2.2-SNAP on those machines ? (No need to do an actuall install, just test whether the boot floppy PCI probe is successful ...) The PCI probe in 2.2 is quite different from that in 2.1 and 2.1.5. It might be possible to select a mode from the boot config menu in a later version. But this is getting less important, since all currently sold systems use config mechanism 1 only. > My thanks again go to Stefan Esser for the help given in getting 2.1.0-R to > run on this machine. Well, my thanks go to those people (including you :) who actually give some feedback ... Regards, STefan From owner-freebsd-stable Fri Jul 26 15:23:50 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA08210 for stable-outgoing; Fri, 26 Jul 1996 15:23:50 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA08191; Fri, 26 Jul 1996 15:23:43 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-13.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA03773 (5.67b/IDA-1.5); Sat, 27 Jul 1996 00:23:29 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id AAA00256; Sat, 27 Jul 1996 00:23:26 +0200 (MET DST) Date: Sat, 27 Jul 1996 00:23:26 +0200 (MET DST) Message-Id: <199607262223.AAA00256@x14.mi.uni-koeln.de> From: Stefan Esser To: dg@root.com Subject: Re: ncr53c810 driver in stable/current Cc: current@freebsd.org, stable@freebsd.org, "Marc G. Fournier" In-Reply-To: <199607220803.BAA10665@root.com> References: <199607220803.BAA10665@root.com> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > > The last time I reported this, someone made mention that > >the cause was the NCR driver not switching modes or something like > >that, so that it can't dump core...? > > > > If anyone remembers this thread, or knows what the hell I'm > >talking about...has this been fixed in -current? > > We've seen this problem on freefall (which uses the NCR controller). It > likes to hang when we try to reboot it. I don't recall any fixes for this, > and I don't know what causes it. Hmmm, it hangs when you try to reboot it ? This is more probably related to some problem with the motherboard than the SCSI controller. (Ie. the (in)famous BROKEN_KEYBOARD_RESET.) But I now know how to make the NCR write a kernel dump in case of a crash: Just leave alone the "hole" between 0xe8000 and 0xfffff ... It seems that the NCR gets some error accessing this addresses. I did not have time to completely analyse the resulting chip status, but it appears that the failed memory access (which is reported to a PCI bus-master on a PCI bus line !) causes the hang. Isn't it dangerous to touch that region from the dump code, anyway ? There might be memory mapped registers that make some device change state when read ... I will try to make the driver ignore the access error in the dump, but it might be a good idea to not include the BIOS region in the dump (???) Regards, STefan From owner-freebsd-stable Sat Jul 27 03:53:01 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA28975 for stable-outgoing; Sat, 27 Jul 1996 03:53:01 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA28964; Sat, 27 Jul 1996 03:52:54 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id UAA08492; Sat, 27 Jul 1996 20:49:41 +1000 Date: Sat, 27 Jul 1996 20:49:41 +1000 From: Bruce Evans Message-Id: <199607271049.UAA08492@godzilla.zeta.org.au> To: cat@uunet.ca, se@ZPR.Uni-Koeln.DE Subject: Re: ncr53c810 driver in stable/current Cc: current@FreeBSD.org, dg@Root.COM, jkh@FreeBSD.org, scrappy@ki.net, stable@FreeBSD.org Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >The dump writes out the first few MB within less than a >second, and then the SCSI LED stays on and the system >hangs, always after accessing the same virtual address. >It took me some time to think about checking which physical >address that corresponds to that page, and to my surprise I >found that the BIOS region at e8000 is the last thing touched >by the NCR chip. I have no idea why the page at 0e8000 is >mapped into the kernel, and I do not think that I got some >device at that address. But it still causes the hang :( 0xe8000 is in the first MB so it's surprising that the first few MB got written. sddump() and wddump() write all pages from page #0 to page #MaxMem-1, so they always write the entire BIOS area. Perhaps they should write only RAM. phys_avail[] almost says where RAM is. Unfortunately, it is truncated at the start to skip the BIOS page and at the end to skip the message buffer. Bruce From owner-freebsd-stable Sat Jul 27 05:38:51 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA05502 for stable-outgoing; Sat, 27 Jul 1996 05:38:51 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA05497; Sat, 27 Jul 1996 05:38:47 -0700 (PDT) Received: by Sisyphos id AA14447 (5.67b/IDA-1.5); Sat, 27 Jul 1996 14:36:45 +0200 Message-Id: <199607271236.AA14447@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Sat, 27 Jul 1996 14:36:44 +0200 In-Reply-To: Bruce Evans "Re: ncr53c810 driver in stable/current" (Jul 27, 20:49) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Bruce Evans Subject: Re: ncr53c810 driver in stable/current Cc: current@freebsd.org, stable@freebsd.org, scrappy@ki.net Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jul 27, 20:49, Bruce Evans wrote: } Subject: Re: ncr53c810 driver in stable/current } >The dump writes out the first few MB within less than a } >second, and then the SCSI LED stays on and the system } >hangs, always after accessing the same virtual address. } } >It took me some time to think about checking which physical } >address that corresponds to that page, and to my surprise I } >found that the BIOS region at e8000 is the last thing touched } >by the NCR chip. I have no idea why the page at 0e8000 is } >mapped into the kernel, and I do not think that I got some } >device at that address. But it still causes the hang :( } } 0xe8000 is in the first MB so it's surprising that the first } few MB got written. Yes, sure, you are of course right! I wrote the message whiledoing the tests, and in fact had estimated that 2MB had been written at the time of the hand, when it in fact was a little less than 1MB ... } sddump() and wddump() write all pages from page #0 to page } #MaxMem-1, so they always write the entire BIOS area. Perhaps } they should write only RAM. phys_avail[] almost says where } RAM is. Unfortunately, it is truncated at the start to skip } the BIOS page and at the end to skip the message buffer. I'm not sure about the right way to deal with that region. There might be interesting data in some devices buffer (e.g. of an ISA ethernet card) that should go into the dump. PCI is different from ISA in that each transfer has to be acknowledged. But the ISA memory hole is subtractively decoded: If no PCI chip signals a "DEVSEL" (some device is selected) state within a few PCI bus clocks, then the PCI to ISA bridge will forward the request to the ISA bus. The NCR won't actually know whether the address was decoded on ISA, so I'm again not sure why the system hangs when the NCR tries to read from that address. I will add a few more micro-tests to find out what actually causes the hang. As a work around to those people in need to have kernel dumps written to disk on a NCR system: Is it worth the effort to detect the special situation and have the driver ignore the memory hole in the dump ? If all you want is to have the system come up automatically after crash, then you might as well just turn off the kernel dump feature (using the dumpon command or by not having a "sump on sd0" in the kernel config file ...) Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-stable Sat Jul 27 06:01:26 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA06405 for stable-outgoing; Sat, 27 Jul 1996 06:01:26 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA06364; Sat, 27 Jul 1996 06:01:07 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id WAA11898; Sat, 27 Jul 1996 22:58:24 +1000 Date: Sat, 27 Jul 1996 22:58:24 +1000 From: Bruce Evans Message-Id: <199607271258.WAA11898@godzilla.zeta.org.au> To: bde@zeta.org.au, se@zpr.uni-koeln.de Subject: Re: ncr53c810 driver in stable/current Cc: current@FreeBSD.org, scrappy@ki.net, stable@FreeBSD.org Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >As a work around to those people in need to have >kernel dumps written to disk on a NCR system: Is >it worth the effort to detect the special situation >and have the driver ignore the memory hole in the >dump ? It would have to fill the hole(s) with nulls or something for compatibility (savecore and gdb don't understand holes). To handle this machine-independently, xddump() should probably write a memory map and not dump the holes; then savecore should fill the holes with null blocks. Otherwise /dev/mem would take more than 2^64 bytes of memory to map on 64-bit systems with physical memory at high addresses. Bruce