From owner-freebsd-stable Sun May 24 02:56:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23247 for freebsd-stable-outgoing; Sun, 24 May 1998 02:56:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from baloon.mimi.com (sjx-ca126-41.ix.netcom.com [207.92.177.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23232 for ; Sun, 24 May 1998 02:56:25 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by baloon.mimi.com (8.8.8/8.8.8) id CAA01969; Sun, 24 May 1998 02:56:25 -0700 (PDT) (envelope-from asami) Date: Sun, 24 May 1998 02:56:25 -0700 (PDT) Message-Id: <199805240956.CAA01969@baloon.mimi.com> To: stable@FreeBSD.ORG Subject: chipset identification code merge from -current From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I've made a diff to bring -stable's PCI chipset identification code almost up to par to -current's. Can people test it? I get this on my FIC PA-2007: === May 23 13:54:10 baloon /kernel: Probing for devices on PCI bus 0: May 23 13:54:10 baloon /kernel: chip0 rev 6 on pci0:0:0 May 23 13:54:10 baloon /kernel: chip1 rev 39 on pci0:7:0 May 23 13:54:10 baloon /kernel: pci0:7:1: VIA Technologies, device=0x0571, class=storage (ide) [no driver assigned] === I guess the IDE controller is not there yet. While I was there, I fixed the few lines that had inconsistent capitalization. Now only proper nouns and acronyms are capitalized. I intend to commit that part to -current too. Satoshi ------- Index: pcisupport.c =================================================================== RCS file: /usr/cvs/src/sys/pci/pcisupport.c,v retrieving revision 1.40.2.7 diff -u -r1.40.2.7 pcisupport.c --- pcisupport.c 1998/03/26 22:28:42 1.40.2.7 +++ pcisupport.c 1998/05/24 09:49:49 @@ -114,13 +114,16 @@ char *descr; switch (type) { + case 0x00088086: + /* Silently ignore this one! What is it, anyway ??? */ + return (""); case 0x04868086: return ("Intel 82425EX PCI system controller"); case 0x04848086: rev = (unsigned) pci_conf_read (tag, PCI_CLASS_REG) & 0xff; if (rev == 3) - return ("Intel 82378ZB PCI-ISA bridge"); - return ("Intel 82378IB PCI-ISA bridge"); + return ("Intel 82378ZB PCI to ISA bridge"); + return ("Intel 82378IB PCI to ISA bridge"); case 0x04838086: return ("Intel 82424ZX (Saturn) cache DRAM controller"); case 0x04828086: @@ -132,12 +135,12 @@ if (rev == 16 || rev == 17) return ("Intel 82434NX (Neptune) PCI cache memory controller"); return ("Intel 82434LX (Mercury) PCI cache memory controller"); + case 0x12258086: + return ("Intel 824?? host to PCI bridge"); case 0x122d8086: return ("Intel 82437FX PCI cache memory controller"); case 0x122e8086: - return ("Intel 82371FB PCI-ISA bridge"); - case 0x12308086: - return ("Intel 82371FB IDE interface"); + return ("Intel 82371FB PCI to ISA bridge"); case 0x12348086: return ("Intel 82371MX mobile PCI I/O IDE accelerator (MPIIX)"); case 0x12358086: @@ -151,33 +154,84 @@ case 0x06011039: return ("SiS 85c601"); case 0x70008086: - return ("Intel 82371SB PCI-ISA bridge"); - case 0x70108086: - return ("Intel 82371SB IDE interface"); + return ("Intel 82371SB PCI to ISA bridge"); + case 0x70208086: + return ("Intel 82371SB USB host controller"); case 0x70308086: return ("Intel 82437VX PCI cache memory controller"); case 0x71008086: - return ("Intel 82439TX PCI cache memory controller"); + return ("Intel 82439TX system controller (MTXC)"); case 0x71108086: - return ("Intel 82371AB PCI-ISA bridge"); - case 0x71118086: - return ("Intel 82371AB IDE interface"); + return ("Intel 82371AB PCI to ISA bridge"); case 0x71128086: - return ("Intel 82371AB USB interface"); + return ("Intel 82371AB USB host controller"); case 0x71138086: - return ("Intel 82371AB Power management controller"); + return ("Intel 82371AB power management controller"); + case 0x71908086: + return ("Intel 82443BX host to PCI bridge"); + case 0x71918086: + return ("Intel 82443BX host to AGP bridge"); + case 0x71928086: + return ("Intel 82443BX host to PCI bridge (AGP disabled)"); case 0x12378086: return ("Intel 82440FX (Natoma) PCI and memory controller"); case 0x84c48086: - return ("Intel 82450KX (Orion) PCI memory controller"); + return ("Intel 82454KX/GX (Orion) host to PCI bridge"); case 0x84c58086: - return ("Intel 82454GX (Orion) host to PCI bridge"); - case 0x00051166: - return ("Ross (?) host to PCI bridge"); + return ("Intel 82453KX/GX (Orion) PCI memory controller"); case 0x00221014: return ("IBM 82351 PCI-PCI bridge"); case 0x00011011: return ("DEC 21050 PCI-PCI bridge"); + case 0x124b8086: + return ("Intel 82380FB mobile PCI to PCI bridge"); + /* VLSI -- vendor 0x1004 */ + case 0x00051004: + return ("VLSI 82C592 host to PCI bridge"); + case 0x00061004: + return ("VLSI 82C593 PCI to ISA bridge"); + case 0x01011004: + return ("VLSI 82C532 Eagle II peripheral controller"); + case 0x01021004: + return ("VLSI 82C534 Eagle II PCI bus bridge"); + case 0x01031004: + return ("VLSI 82C538 Eagle II PCI docking bridge"); + case 0x01041004: + return ("VLSI 82C535 Eagle II system controller"); + case 0x01051004: + return ("VLSI 82C147 IrDA Controller"); + + /* VIA Technologies -- vendor 0x1106 + * Note that the old Apollo Master chipset is not in here, as VIA + * does not seem to have any docs on their website for it, and I do + * not have a Master board in my posession. -LC */ + + case 0x05851106: + return("VIA 82C585 (Apollo VP1/VPX) system controller"); + case 0x05861106: /* south bridge section -- IDE is covered in ide_pci.c */ + return("VIA 82C586 PCI-ISA bridge"); + case 0x05951106: + case 0x15951106: + return("VIA 82C595 (Apollo VP2) system controller"); + case 0x05971106: + return("VIA 82C597 (Apollo VP3) system controller"); + /* XXX need info on the MVP3 -- any takers? */ + case 0x30381106: + return("VIA 82C586B USB host controller"); + case 0x30401106: + return("VIA 82C586B ACPI interface"); + + /* NEC -- vendor 0x1033 */ + case 0x00011033: + return ("NEC 0001 PCI to PC-98 C-bus bridge"); + case 0x00021033: + return ("NEC 0002 PCI to PC-98 local bus bridge"); + case 0x00161033: + return ("NEC 0016 PCI to PC-98 local bus bridge"); + case 0x002c1033: + return ("NEC 002C PCI to PC-98 C-bus bridge"); + case 0x003b1033: + return ("NEC 003B PCI to PC-98 C-bus bridge"); }; if (descr = generic_pci_bridge(tag)) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 03:49:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29819 for freebsd-stable-outgoing; Sun, 24 May 1998 03:49:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from out4.ibm.net (out4.ibm.net [165.87.194.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29790 for ; Sun, 24 May 1998 03:49:12 -0700 (PDT) (envelope-from feigler@ibm.net) Received: from ibm.net (slip129-37-161-22.on.ca.ibm.net [129.37.161.22]) by out4.ibm.net (8.8.5/8.6.9) with ESMTP id KAA134272 for ; Sun, 24 May 1998 10:49:08 GMT Message-ID: <3567FB21.C86E2437@ibm.net> Date: Sun, 24 May 1998 06:49:05 -0400 From: "Frank J. Eigler" Reply-To: feigler@ibm.net Organization: Frank J. Eigler X-Mailer: Mozilla 4.05 [en] (Win95; U) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Subscription Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk subscribe freebsd-stable -- Frank J. Eigler mailto:feigler@ibm.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 09:09:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05831 for freebsd-stable-outgoing; Sun, 24 May 1998 09:09:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from SNYBUFAA.BUFFALOSTATE.EDU (SYSTEM@snybufaa.buffalostate.edu [136.183.34.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05820 for ; Sun, 24 May 1998 09:09:36 -0700 (PDT) (envelope-from HUMMDN36@BUFFALOSTATE.EDU) Received: from BUFFALOSTATE.EDU by BUFFALOSTATE.EDU (PMDF V5.1-5 #18385) id <01IXETAT4P8K9PRCXQ@BUFFALOSTATE.EDU> for freebsd-stable@freebsd.org; Sun, 24 May 1998 12:09:31 EST Date: Sun, 24 May 1998 12:09:31 -0500 (EST) From: Dave Hummel Subject: /usr/src/share/info.i386 To: freebsd-stable@FreeBSD.ORG Message-id: <01IXETAT4Q6E9PRCXQ@BUFFALOSTATE.EDU> X-VMS-To: in%"freebsd-stable@freebsd.org" MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk This is an error I haven't encountered before. I supped stable this morning, and I got the following error. Previous build was April 4. Apologies if this has been discussed: I've been away for a bit, but I did search the archives and came up with nothing. -------------------------------------------------------------- Cleaning up the obj tree ----------------------------------------------------- ===> share/info.i386 cd: can't cd to /usr/src/share/info.i386 *** Error code 2 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 11:36:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22168 for freebsd-stable-outgoing; Sun, 24 May 1998 11:36:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from karma.uchicago.edu (karma.uchicago.edu [128.135.21.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22156 for ; Sun, 24 May 1998 11:36:21 -0700 (PDT) (envelope-from sfarrell@karma.uchicago.edu) Received: (from sfarrell@localhost) by karma.uchicago.edu (8.9.0.Beta5/8.9.0.Beta5) id NAA00319; Sun, 24 May 1998 13:36:20 -0500 (CDT) To: freebsd-stable Subject: more 2.2.6-stable crashes From: sfarrell@farrell.org Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 24 May 1998 13:36:20 -0500 Message-ID: <87lnrrbjob.fsf@karma.uchicago.edu> Lines: 118 X-Mailer: Gnus v5.6.9/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk so I'm still having serious stability problems with 2.2.6-Stable. My last message was not very information-packed, but I'll do better this time. One suggestion I had was to rebuild my linux LKM (as the problem happened 100% when running linux stuff)... I've done this, and it has not helped. sources are spanking new 2.2.6-stable. World was last made, um, may 11. M/B is an ASUS with BX chipset. RAM is SDRAM, non-parity. Disks are seagate cheetah and an old 1 GB conner from a sun. Here's my dmesg: FreeBSD 2.2.6-STABLE #0: Sun May 24 12:37:04 CDT 1998 root@couatl.uchicago.edu:/usr/src/sys/compile/COUATL CPU: Pentium Pro (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183f9ff,,MMX,> real memory = 134217728 (131072K bytes) avail memory = 120303616 (117484K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0: 0 chip1 rev 2 on pci0:1: 0 chip2 rev 2 on pci0:4:0 chip3 rev 1 on pci0:4:1 chip4 rev 1 int d irq 9 on pci0:4:2 chip5 rev 2 on pci0:4:3 de0 rev 32 int a irq 9 on pci0:10:0 de0: ZNYX ZX34X 21140A [10-100Mb/s] pass 2.0 de0: address 00:c0:95:f8:15:2f ahc0 rev 1 int a irq 15 on pci0:11:0 ahc0: aic7860 Single Channel, SCSI Id=7, 3 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "SEAGATE ST34501N 0017" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4339MB (8887200 512 byte sectors) ahc0: target 1 Tagged Queuing Device (ahc0:1:0): "CONNER CFP1060S 1.05GB 2035" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 1013MB (2074880 512 byte sectors) Probing for devices on PCI bus 1: vga0 rev 0 int a irq 11 on pci1:0:0 Probing for PnP devices: CSN 1 Vendor ID: CTL0028 [0x28008c0e] Serial 0x1008415c pcm1 (SB16pnp sn 0x1008415c) at 0x220 irq 5 drq 1 flags 0x15 id 16 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 pcm0 not found at 0xffffffff fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, accel, iordis wcd0: 689Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: no disc inside, unlocked aha0 not found at 0x330 npx0 flags 0x1 on motherboard npx0: INT 16 interface Crashes occur 100% instantly when running any linux programs. I enabled the kernel debugger and so on. here's what i get (copied by hand, of course): fatal trap 12: page fault while in kernel mode fault virtual addr: 0xb56d3104 fault code: supervisor read, page not present instruction pointer: 0x8:0xf66d1a53 stack ptr: 0x10:0xefbffd8c frame ptr: (same) code seg: base 0x0, limit 0xffffff, type 0x1b, DPL 0, pres 1, def (no idea what i wrote here), gran 1 proc eflags: interrupt enabled, resume, IOPL=0 current proc: 251 (sh) mt mask: the trace didn't seem to useful to me, so i didn't bother to include all the addresses: (i'm doing something wrong, right?) _end() _execv() _syscall() _Xsyscall() ---syscall() I do NOT think this panic only happens when running linux code, but it is possible. (others use my machine, so perhaps at other times they were running some linux whatever, not me.) One thing that has changed with the machine is the ethernet card. I had an intel card (100+) go belly-up a couple of days ago and replaced it with the ZNYX which was kicking around. (the intel card got *really* slow over the course of a couple of days, dropping down to ftp transfers of 3kB/sec... replacing it with the ZNYX made the problem go away immediately...) just tried replacing the intel ethernet and the problem still exists, so i don't think this is pertinant. I have a 128MB core file with debugging symbols. Tell me what you want me to do with it... -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 12:18:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26945 for freebsd-stable-outgoing; Sun, 24 May 1998 12:18:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [207.149.232.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26925 for ; Sun, 24 May 1998 12:18:17 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.8/8.8.8) id MAA26450; Sun, 24 May 1998 12:17:43 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199805241917.MAA26450@GndRsh.aac.dev.com> Subject: Re: more 2.2.6-stable crashes In-Reply-To: <87lnrrbjob.fsf@karma.uchicago.edu> from "sfarrell@farrell.org" at "May 24, 98 01:36:20 pm" To: sfarrell@farrell.org Date: Sun, 24 May 1998 12:17:42 -0700 (PDT) Cc: stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > so I'm still having serious stability problems with 2.2.6-Stable. My > last message was not very information-packed, but I'll do better this > time. One suggestion I had was to rebuild my linux LKM (as the > problem happened 100% when running linux stuff)... I've done this, and > it has not helped. > > sources are spanking new 2.2.6-stable. World was last made, um, > may 11. M/B is an ASUS with BX chipset. RAM is SDRAM, non-parity. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^ Are you using 8nS PC-100 Compliant SDRAM? If not your going to have a problem.... > Disks are seagate cheetah and an old 1 GB conner from a sun. > > Here's my dmesg: > > FreeBSD 2.2.6-STABLE #0: Sun May 24 12:37:04 CDT 1998 > root@couatl.uchicago.edu:/usr/src/sys/compile/COUATL > CPU: Pentium Pro (400.91-MHz 686-class CPU) ^^^^^^^^^^ Running this board with the 100mHz bus requires the highest of quality when it comes to the memory components. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 12:48:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01788 for freebsd-stable-outgoing; Sun, 24 May 1998 12:48:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles313.castles.com [208.214.167.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01777 for ; Sun, 24 May 1998 12:48:32 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA07589; Sun, 24 May 1998 11:43:24 -0700 (PDT) Message-Id: <199805241843.LAA07589@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sfarrell@farrell.org cc: freebsd-stable Subject: Re: more 2.2.6-stable crashes In-reply-to: Your message of "24 May 1998 13:36:20 CDT." <87lnrrbjob.fsf@karma.uchicago.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 May 1998 11:43:24 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > so I'm still having serious stability problems with 2.2.6-Stable. My > last message was not very information-packed, but I'll do better this > time. One suggestion I had was to rebuild my linux LKM (as the > problem happened 100% when running linux stuff)... I've done this, and > it has not helped. ... > the trace didn't seem to useful to me, so i didn't bother to include > all the addresses: (i'm doing something wrong, right?) > > _end() > _execv() > _syscall() > _Xsyscall() > ---syscall() The trace is actually pretty critical - it would be very useful to know whereabouts in execv() it's actually exploding. > I have a 128MB core file with debugging symbols. Tell me what you > want me to do with it... Feed it to gdb, and tell us where in execv() it's falling over. Find out what it's trying to exec. If you have the core and the matching kernel executable, gzip them and put them somewhere we can get at them. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 13:17:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06026 for freebsd-stable-outgoing; Sun, 24 May 1998 13:17:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (lee@host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05993 for ; Sun, 24 May 1998 13:17:35 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.7/8.8.7) id QAA03631; Sun, 24 May 1998 16:17:27 -0400 (EDT) (envelope-from lee) Message-ID: <19980524161727.45315@st-lcremean.tidalwave.net> Date: Sun, 24 May 1998 16:17:27 -0400 From: Lee Cremeans To: Satoshi Asami Cc: stable@FreeBSD.ORG Subject: Re: chipset identification code merge from -current Reply-To: lcremean@tidalwave.net References: <199805240956.CAA01969@baloon.mimi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <199805240956.CAA01969@baloon.mimi.com>; from Satoshi Asami on Sun, May 24, 1998 at 02:56:25AM -0700 X-OS: FreeBSD 2.2.5-STABLE (soon to be 3.0-CURRENT) X-Evil: microsoft.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > May 23 13:54:10 baloon /kernel: Probing for devices on PCI bus 0: > May 23 13:54:10 baloon /kernel: chip0 rev 6 on pci0:0:0 > May 23 13:54:10 baloon /kernel: chip1 rev 39 on pci0:7:0 > May 23 13:54:10 baloon /kernel: pci0:7:1: VIA Technologies, device=0x0571, class=storage (ide) [no driver assigned] > === > > I guess the IDE controller is not there yet. It isn't: > + case 0x05861106: /* south bridge section -- IDE is covered in ide_pci.c */ > + return("VIA 82C586 PCI-ISA bridge"); and AFAIK, ide_pci.c has not been merged into -stable yet. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 13:39:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08380 for freebsd-stable-outgoing; Sun, 24 May 1998 13:39:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from couatl.uchicago.edu (couatl.uchicago.edu [128.135.21.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08374 for ; Sun, 24 May 1998 13:39:00 -0700 (PDT) (envelope-from sfarrell@couatl.uchicago.edu) Received: (from sfarrell@localhost) by couatl.uchicago.edu (8.9.0.Beta5/8.9.0.Beta5) id PAA00404; Sun, 24 May 1998 15:38:01 -0500 (CDT) To: "Rodney W. Grimes" Cc: stable@FreeBSD.ORG Subject: Re: more 2.2.6-stable crashes References: <199805241917.MAA26450@GndRsh.aac.dev.com> From: sfarrell+lists@farrell.org Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 24 May 1998 15:38:01 -0500 Message-ID: <877m3bxv4m.fsf@couatl.uchicago.edu> Lines: 30 X-Mailer: Gnus v5.6.9/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk "Rodney W. Grimes" writes: > > > > so I'm still having serious stability problems with 2.2.6-Stable. My > > last message was not very information-packed, but I'll do better this > > time. One suggestion I had was to rebuild my linux LKM (as the > > problem happened 100% when running linux stuff)... I've done this, and > > it has not helped. > > > > sources are spanking new 2.2.6-stable. World was last made, um, > > may 11. M/B is an ASUS with BX chipset. RAM is SDRAM, non-parity. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^ > Are you using 8nS PC-100 Compliant SDRAM? If not your going to > have a problem.... Hmm... I bought it at necx and it was listed as 100Mhz RAM... but going back to it is is no longer listed as such. And it is 10ns, not 8ns. I've placed an new order for explicitely "pc100" certified sdram already. ... however, setting the system down to 66Mhz actually makes it amazingly unstable (won't run for more than 5 minutes), whereas it is relatively stable at 100Mhz. Like I said, the crash seems to be linked to running linux programs. I'm not even certain it is unstable otherwise. -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 13:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08773 for freebsd-stable-outgoing; Sun, 24 May 1998 13:40:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tbone.agouron.com (tbone.agouron.com [198.182.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08715; Sun, 24 May 1998 13:40:09 -0700 (PDT) (envelope-from barry@Lustig.COM) Received: (from gproxy@localhost) by tbone.agouron.com (8.8.7/8.8.7) id NAA19823; Sun, 24 May 1998 13:40:08 -0700 (PDT) Received: from unknown(10.0.7.236) by tbone via smap (3.2) id xma019804; Sun, 24 May 98 13:40:04 -0700 Received: from Lustig.COM (dns5.agouron.com [10.0.7.206]) by dns3.agouron.com (8.8.8/8.8.8) with ESMTP id NAA09179; Sun, 24 May 1998 13:40:04 -0700 (PDT) (envelope-from barry@Lustig.COM) Message-ID: <356885A4.BD207C7D@Lustig.COM> Date: Sun, 24 May 1998 13:40:04 -0700 From: Barry Lustig X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: Gary Palmer CC: stable@FreeBSD.ORG Subject: Re: Releng 2.2.6 and P2-266 References: <21799.895886358@gjp.erols.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Double check all of the motherboard jumper settings. I just finished installing my 3rd system P2L97 system with 2940 without a hitch. barry Gary Palmer wrote: > > Hi, > > I'm trying to install 2.2.6 onto an ASUS P2L97 motherboard with a > 2940AU and a 266MHz PII and running into problems. It get so far > through the install then panics. Trying to boot the resulting install > fails just after it tries mounting the root filesystem with a kernel > pagefault. > > Before I go trying to debug this, anyone else seen this or got any > hints? Trying to debug a system which won't boot is going to be > insteresting :( > > Thanks, > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 13:41:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09019 for freebsd-stable-outgoing; Sun, 24 May 1998 13:41:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail1.i1.net (mturpin@mail1.i1.net [207.230.32.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08954 for ; Sun, 24 May 1998 13:41:15 -0700 (PDT) (envelope-from mturpin@mail1.i1.net) From: mturpin@mail1.i1.net Received: from localhost (mturpin@localhost) by mail1.i1.net (8.8.5/8.8.5) with SMTP id PAA29092 for ; Sun, 24 May 1998 15:43:37 -0500 (CDT) Date: Sun, 24 May 1998 15:43:36 -0500 (CDT) To: stable@FreeBSD.ORG Subject: Trouble compiling 2.2.6-stable kernel Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk after config, and make depend, i run make, and get this: loading kernel isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment *** Error code 1 In isa.c I see for (tmpdvp = isa_devtab_cam; tmpdvp->id_driver; tmpdvp++) { status |= haveseen(dvp, tmpdvp, checkbits); if (status) return status; } but, I'm not following why its having problems.. -mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 14:29:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15604 for freebsd-stable-outgoing; Sun, 24 May 1998 14:29:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from couatl.uchicago.edu (couatl.uchicago.edu [128.135.21.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15597 for ; Sun, 24 May 1998 14:28:52 -0700 (PDT) (envelope-from sfarrell@couatl.uchicago.edu) Received: (from sfarrell@localhost) by couatl.uchicago.edu (8.9.0.Beta5/8.9.0.Beta5) id QAA06871; Sun, 24 May 1998 16:28:51 -0500 (CDT) To: mturpin@mail1.i1.net Cc: stable@FreeBSD.ORG Subject: Re: Trouble compiling 2.2.6-stable kernel References: From: sfarrell+lists@farrell.org Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 24 May 1998 16:28:50 -0500 In-Reply-To: mturpin@mail1.i1.net's message of "Sun, 24 May 1998 15:43:36 -0500 (CDT)" Message-ID: <87k97bcq99.fsf@couatl.uchicago.edu> Lines: 29 X-Mailer: Gnus v5.6.9/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk mturpin@mail1.i1.net writes: > after config, and make depend, i run make, and get this: > > loading kernel > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > *** Error code 1 > > In isa.c I see > for (tmpdvp = isa_devtab_cam; tmpdvp->id_driver; tmpdvp++) { > status |= haveseen(dvp, tmpdvp, checkbits); > if (status) > return status; > } > but, I'm not following why its having problems.. rebuild config from latest sources and reconfig your kernel. -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 15:12:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21828 for freebsd-stable-outgoing; Sun, 24 May 1998 15:12:41 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (lee@host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21809 for ; Sun, 24 May 1998 15:12:22 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.7/8.8.7) id SAA03888; Sun, 24 May 1998 18:12:16 -0400 (EDT) (envelope-from lee) Message-ID: <19980524181216.59289@st-lcremean.tidalwave.net> Date: Sun, 24 May 1998 18:12:16 -0400 From: Lee Cremeans To: mturpin@mail1.i1.net Cc: stable@FreeBSD.ORG Subject: Re: Trouble compiling 2.2.6-stable kernel Reply-To: lcremean@tidalwave.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: ; from mturpin@mail1.i1.net on Sun, May 24, 1998 at 03:43:36PM -0500 X-OS: FreeBSD 2.2.5-STABLE (soon to be 3.0-CURRENT) X-Evil: microsoft.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, May 24, 1998 at 03:43:36PM -0500, mturpin@mail1.i1.net wrote: > after config, and make depend, i run make, and get this: > > loading kernel > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > *** Error code 1 This is a FAQ...the fix is to rebuild src/usr.sbin/config, then use the new config to remake your kernel. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 15:44:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25573 for freebsd-stable-outgoing; Sun, 24 May 1998 15:44:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt053nd2.san.rr.com [204.210.34.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25548 for ; Sun, 24 May 1998 15:44:22 -0700 (PDT) (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id PAA09160; Sun, 24 May 1998 15:44:20 -0700 (PDT) (envelope-from Studded@san.rr.com) Message-ID: <3568A2C3.A1B8A481@san.rr.com> Date: Sun, 24 May 1998 15:44:19 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE-0507 i386) MIME-Version: 1.0 To: Dave Hummel CC: freebsd-stable@FreeBSD.ORG Subject: Re: /usr/src/share/info.i386 References: <01IXETAT4Q6E9PRCXQ@BUFFALOSTATE.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Dave Hummel wrote: > > This is an error I haven't encountered before. I supped stable > this morning, and I got the following error. Previous build was > April 4. Apologies if this has been discussed: I've been away > for a bit, but I did search the archives and came up with > nothing. Thank you for taking that step. :) > -------------------------------------------------------------- > Cleaning up the obj tree > ----------------------------------------------------- > > ===> share/info.i386 > cd: can't cd to /usr/src/share/info.i386 > *** Error code 2 This looks like the dreaded stale dependencies problem. Did you try wiping out /usr/obj/* and start the make world again? cd /usr/obj chflags -R noschg * rm -rf * cd /usr/src make world (or elaborate as normal) Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud designer and maintainer of one of the world's largest *** Internet Relay Chat server with 5,328 simultaneous connections *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 15:50:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26388 for freebsd-stable-outgoing; Sun, 24 May 1998 15:50:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from couatl.uchicago.edu (couatl.uchicago.edu [128.135.21.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26376 for ; Sun, 24 May 1998 15:50:34 -0700 (PDT) (envelope-from sfarrell@couatl.uchicago.edu) Received: (from sfarrell@localhost) by couatl.uchicago.edu (8.9.0.Beta5/8.9.0.Beta5) id RAA00337; Sun, 24 May 1998 17:50:31 -0500 (CDT) To: freebsd-stable Subject: 2.2.6-stable problems: probable false alarm From: sfarrell@farrell.org Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 24 May 1998 17:50:31 -0500 Message-ID: <87n2c71dxk.fsf@couatl.uchicago.edu> Lines: 10 X-Mailer: Gnus v5.6.9/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hmm... redid make world and now running linux binaries doesn't cause panic. haven't tested too much yet but looks 100x better so far. -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 16:45:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04070 for freebsd-stable-outgoing; Sun, 24 May 1998 16:45:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles212.castles.com [208.214.165.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04045 for ; Sun, 24 May 1998 16:45:06 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA08535; Sun, 24 May 1998 15:41:07 -0700 (PDT) Message-Id: <199805242241.PAA08535@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sfarrell@farrell.org cc: freebsd-stable Subject: Re: 2.2.6-stable problems: probable false alarm In-reply-to: Your message of "24 May 1998 17:50:31 CDT." <87n2c71dxk.fsf@couatl.uchicago.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 May 1998 15:41:06 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > Hmm... redid make world and now running linux binaries doesn't cause > panic. > > haven't tested too much yet but looks 100x better so far. Thanks for the update. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 19:00:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24762 for freebsd-stable-outgoing; Sun, 24 May 1998 19:00:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from firewall.scitec.com.au (firewall-user@fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24719 for ; Sun, 24 May 1998 19:00:05 -0700 (PDT) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id LAA20089; Mon, 25 May 1998 11:59:52 +1000 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma020070; Mon, 25 May 98 11:59:44 +1000 Received: from hydra.scitec.com.au (hydra.scitec.com.au [203.17.182.101]) by mailhub.scitec.com.au (8.6.12/8.6.9) with ESMTP id LAA21959; Mon, 25 May 1998 11:59:33 +1000 Received: from saruman (saruman.scitec.com.au) by hydra.scitec.com.au with SMTP (1.40.112.8/16.2) id AA100381571; Mon, 25 May 1998 11:59:31 +1000 Message-Id: <00a101bd8780$c29dd850$6cb611cb@saruman.scitec.com.au> From: "John Saunders" To: , "Dan Swartzendruber" Subject: Re: make buildworld/installworld question Date: Mon, 25 May 1998 11:59:31 +1000 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Dan Swartzendruber wrote: >Until now, when I've been updating, I been doing like the "Making the world" >your own tutorial on www.freebsd.org. I.e. for the build server, going to >single-user mode, doing make buildworld, make installworld, building a new >kernel and rebooting. For the clients, going single-user, mounting /usr/src >and /usr/obj via NFS and doing make reinstall. Here's my question: do I >really need to go single-user? It makes the downtime significantly greater >(particularly for the build server). Will Bad Things happen if I do the >make installworld on a live box? I've done 'make world' in both single user mode and multi user . One thing to watch is that the /usr/libexec/ld.so file gets updated. The last time I did 'make world' in multi user mode it didn't. I tend to 'ls -lt' in the standard directories to check on what didn't get updated. Probably the best way is... In multi user mode: # (cd /usr/obj ; chflags -R noschg usr ; rm -rf usr) # cd /usr/src ; make includes # make buildworld In single user mode: # make installworld # cd /sys/i386/conf ; config KERNELFILE # cd ../../compile/KERNELFILE ; make kernel install For a machine where uptime isn't critical I just shutdown to single user mode and do the entire sequence. Of course you can't do single user mode remotely so the only way is to do the entire upgrade from multi user mode. Just check on the files that don't get updated and copy them over from the /usr/obj directories. To update ld.so was a bit tricky. I used. # cp /usr/obj/.../ld.so ld.so.new # chown bin.bin ld.so.new # chflags noschg ld.so # ln ld.so ld.so.old # ln -f ld.so.new ld.so # rm ld.so.new # chflags noschg ld.so Then reboot and delete ld.so.old. Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 23:21:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29567 for freebsd-stable-outgoing; Sun, 24 May 1998 23:21:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles213.castles.com [208.214.165.213]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29539 for ; Sun, 24 May 1998 23:21:08 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA10436; Sun, 24 May 1998 22:16:45 -0700 (PDT) Message-Id: <199805250516.WAA10436@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "John Saunders" cc: freebsd-stable@FreeBSD.ORG, "Dan Swartzendruber" Subject: Re: make buildworld/installworld question In-reply-to: Your message of "Mon, 25 May 1998 11:59:31 +1000." <00a101bd8780$c29dd850$6cb611cb@saruman.scitec.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 May 1998 22:16:44 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > I've done 'make world' in both single user mode and multi user > .. One thing to watch is that the /usr/libexec/ld.so file gets > updated. The last time I did 'make world' in multi user mode it > didn't. I tend to 'ls -lt' in the standard directories to check > on what didn't get updated. ld.so is installed using '-C', so if the new version is the same as the old one, it's not changed. It's debatable as to whether the use of -C is justifiable (it's not a performance improvement, and it makes the use of timestamps for identifying stale files unworkable). > Probably the best way is... ... much unuseful stuff elided. The 'installworld' target is almost always successful without any help. The 'install' utility knows how to work around most of the problems that can normally occur when installing files, and should not need any assistance. The only problems that normally occur during 'installworld' are related to the non-atomicity of the process, and these are generally avoided by the order of installation. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 23:44:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04892 for freebsd-stable-outgoing; Sun, 24 May 1998 23:44:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mh2.cts.com (root@mh2.cts.com [205.163.24.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04879 for ; Sun, 24 May 1998 23:44:25 -0700 (PDT) (envelope-from mdavis@io.cts.com) Received: from io.cts.com (io.cts.com [198.68.174.34]) by mh2.cts.com (8.8.7/8.8.5) with ESMTP id XAA29956 for ; Sun, 24 May 1998 23:44:25 -0700 (PDT) Received: from iopc (iopc.cts.com [198.68.174.36]) by io.cts.com (8.8.8/8.8.8) with SMTP id XAA23047 for ; Sun, 24 May 1998 23:44:27 -0700 (PDT) (envelope-from mdavis@io.cts.com) From: "Morgan Davis" To: Subject: Upgrading from BSDI 2.1 -> FreeBSD 2.2.6 Date: Sun, 24 May 1998 23:44:09 -0700 Message-ID: <000c01bd87a8$84e7ef50$24ae44c6@iopc.cts.com> 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 8.5, Build 4.71.2173.0 X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I inherited the duty of upgrading a working BSDI 2.1 system to FreeBSD 2.2.6, but am having trouble getting sysinstall to come up properly. First, here's the BSDI 2.1 dmesg output: BSDI BSD/OS 2.1 Kernel #1: Mon Jan 6 16:49:23 PST 1997 cpu = Pentium (about 133 MHz) model 2, stepping 12 delay multiplier 3384 real mem = 134217728 avail mem = 130179072 buffer cache = 16777216 isa0 (root) pci0 at root: configuration mechanism 1 pccons0 at isa0 iobase 0x60 irq 1: color, 8 screens com0 at isa0 iobase 0x3f8 irq 4: buffered (16550AF) com1 at isa0 iobase 0x2f8 irq 3: buffered (16550AF) lp0 at isa0 iobase 0x378 irq 7 fdc0 at isa0 iobase 0x3f0 irq 6 drq 2: floppy controller fd0 at fdc0 slave 0: 1.44M HD 3.5 floppy npx0 at isa0 iobase 0xf0: math coprocessor vga0 at isa0 iobase 0x3c0 maddr 0xa0000-0xaffff: VGA graphics bha0 at isa0 iobase 0x330 irq 9: Buslogic EISA/PCI/VLB rev 42 (32-bit) Delaying for SCSI bus reset and device self tests bha0: synch negotiation, parity tg0 at bha0 target 0 sd0 at tg0 unit 0: disk: SEAGATE ST51080N rev 0943 (SCSI-2) 2109840*512 tg0: synch transfer period 200 ns, offset 15 (10 MB/s) tg1 at bha0 target 6 st0 at tg1 unit 0: SONY SDT-5200 rev 3.26 (SCSI-2) DDS cassette streaming (512) tape tg1: synch transfer period 200 ns, offset 8 (10 MB/s) de0 at pci0 iobase 0x6000 irq 10: DC21140 [10-100Mb/s] pass 1.2 de0: address 00:00:c0:5b:8b:e4 de0: enabling 10baseT UTP port de1 at pci0 iobase 0x6200 irq 5: DC21140 [10-100Mb/s] pass 1.2 de1: address 00:00:c0:71:8b:e4 de1: enabling 10baseT UTP port bha0: warning, interrupts not working, using polling Of note, BSDI uses bha0 where FreeBSD prefers bt0, apparently. If I start the boot floppy with the default kernel, it gets confused about aha0 and bt0. So I use the visual kernel editor to remove the aha0 support so it won't conflict with the bt0 PCI support. Everything else is left as-is (though I've tried removing everything other non-essential item, as well). Only when it gets to "Probing devices, one moment..." it sits there all day. Looking at console on F2, it gets (something like): bt0: Abort fail bt0: Timed out ... If I let it sit long enough (several minutes), about four of these error message pairs show up. Eventually, it'll get to the main sysinstall screen. However, it is unable to see any drives in the system, so I can't proceed with an install. Yet, the initial kernel probes do reveal the Buslogic SCSI adapter, the Seagate SCSI drive, and a Sony SCSI DAT drive. Any hints? Might that BSDI bha0 warning about interrupts be significant with FreeBSD? --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 24 23:54:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06892 for freebsd-stable-outgoing; Sun, 24 May 1998 23:54:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from firewall.scitec.com.au (firewall-user@fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06869 for ; Sun, 24 May 1998 23:54:29 -0700 (PDT) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id QAA01063; Mon, 25 May 1998 16:54:22 +1000 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma001057; Mon, 25 May 98 16:54:20 +1000 Received: from hydra.scitec.com.au (hydra.scitec.com.au [203.17.182.101]) by mailhub.scitec.com.au (8.6.12/8.6.9) with ESMTP id QAA24117; Mon, 25 May 1998 16:54:15 +1000 Received: from saruman (saruman.scitec.com.au) by hydra.scitec.com.au with SMTP (1.40.112.8/16.2) id AA186379247; Mon, 25 May 1998 16:54:07 +1000 Message-Id: <038c01bd87a9$ee6dadb0$6cb611cb@saruman.scitec.com.au> From: "John Saunders" To: "Mike Smith" Cc: , "Dan Swartzendruber" Subject: Re: make buildworld/installworld question Date: Mon, 25 May 1998 16:54:07 +1000 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >> I've done 'make world' in both single user mode and multi user >> .. One thing to watch is that the /usr/libexec/ld.so file gets >> updated. The last time I did 'make world' in multi user mode it >> didn't. I tend to 'ls -lt' in the standard directories to check >> on what didn't get updated. > >ld.so is installed using '-C', so if the new version is the same as the >old one, it's not changed. It's debatable as to whether the use of -C >is justifiable (it's not a performance improvement, and it makes the >use of timestamps for identifying stale files unworkable). The timestamp first caused me to notice the file. Upon closer inspection the size between old and new was different, 69K vs 70K if memory serves (I did check stripped sizes). So if install really does work around the file being in use then something else must have failed. I must admit it has only happened once as I do check the timestamps after every 'make world'. Do the include files get installed with -C as well? Until I did a 'make -DCLOBBER includes' I had timestamps from Oct 22 (which appears to be the 2.2.5-RELEASE build date) for most of my include files. >The 'installworld' target is almost always successful without any help. I like the words "almost always", I use them a lot myself :) Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 25 08:34:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06016 for freebsd-stable-outgoing; Mon, 25 May 1998 08:34:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fledge.watson.org (root@COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05992 for ; Mon, 25 May 1998 08:34:27 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id LAA12277 for ; Mon, 25 May 1998 11:34:27 -0400 (EDT) Date: Mon, 25 May 1998 11:34:27 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: stable@FreeBSD.ORG Subject: vnconfig + swap with sparse files Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I recently had to move my swap space from a hard disk rapidly failing to a file on another partition (until the drive can be replacd). As there were no free partitions, the easiest route seemed to be to use a swapfile (although I'm not sure what the performance costs are). However, I assumed (correctly?) that I'd need to size the file to the right size so that the it would be known at vnconfig time, so I stuck together an instance C program that lseek'd to the appropriate size (128M), then wrote a \0 there. This, of course, creates a sparse file which returns 0's normally whenever you seek to an unused portion of the file, but doesn't consume disk space until you write to it. The swap pager began complaining almost immediately after I turned on the swapfile. A few sample error messages are attached: May 24 16:17:16 fledge /kernel: swap_pager: I/O error - async pageout failed; blkno 144, size 8192, error 0 May 24 16:17:16 fledge /kernel: swap_pager_finish: I/O error, clean of page 5757000 failed May 24 16:17:17 fledge /kernel: swap_pager_finish: I/O error, clean of page 56d8000 failed May 24 16:17:17 fledge /kernel: swap_pager: I/O error - async pageout failed; blkno 144, size 8192, error 0 May 24 16:17:17 fledge /kernel: swap_pager_finish: I/O error, clean of page 5757000 failed May 24 16:17:17 fledge /kernel: swap_pager_finish: I/O error, clean of page 56d8000 failed May 24 16:17:17 fledge /kernel: swap_pager: I/O error - async pageout failed; blkno 192, size 4096, error 0 I rebooted to stop swapping on the file, and modified my creation program to drop a \0 at the beginning of each block. Sure enough, starting swapping this time worked fine. While I managed to figure it out, the error message was not all that enlightening. It does make sense not to try and use a sparse file as the backing store (after all, that a sparse file claims to be 100mb is not a guarantee that the space will be available). Maybe vnconfig should notice when a file is sparse and warn the user? swapon might not be able to tell as it just sees it as vn0b, though. Or maybe the sparseness of the file should just be transparent as it is elsewhere? Robert N Watson ---- Carnegie Mellon University http://www.cmu.edu/ Trusted Information Systems http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 25 11:19:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06552 for freebsd-stable-outgoing; Mon, 25 May 1998 11:19:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06030 for ; Mon, 25 May 1998 11:17:44 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from bilskirnir.ifi.uio.no (2602@bilskirnir.ifi.uio.no [129.240.64.135]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id UAA15650; Mon, 25 May 1998 20:17:38 +0200 (MET DST) Received: (from dag-erli@localhost) by bilskirnir.ifi.uio.no ; Mon, 25 May 1998 20:17:35 +0200 (MET DST) Mime-Version: 1.0 To: Robert Watson Cc: stable@FreeBSD.ORG Subject: Re: vnconfig + swap with sparse files References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 25 May 1998 20:17:26 +0200 In-Reply-To: Robert Watson's message of "Mon, 25 May 1998 11:34:27 -0400 (EDT)" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Robert Watson writes: > I rebooted to stop swapping on the file, and modified my creation program > to drop a \0 at the beginning of each block. Sure enough, starting > swapping this time worked fine. What you should have done in the first place was: # dd if=/dev/zero of=swapfile bs=1048576 count=128 A sparse file cannot possibly work as swap since it does not have any space allocate to it on the disk, and you *want* to allocate space on the disk - where else are you going to swap out your data? -- Noone else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 25 12:55:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23051 for freebsd-stable-outgoing; Mon, 25 May 1998 12:55:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles348.castles.com [208.214.167.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23019 for ; Mon, 25 May 1998 12:55:07 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id AAA11268; Mon, 25 May 1998 00:28:02 -0700 (PDT) Message-Id: <199805250728.AAA11268@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "John Saunders" cc: "Mike Smith" , freebsd-stable@FreeBSD.ORG, "Dan Swartzendruber" Subject: Re: make buildworld/installworld question In-reply-to: Your message of "Mon, 25 May 1998 16:54:07 +1000." <038c01bd87a9$ee6dadb0$6cb611cb@saruman.scitec.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 May 1998 00:28:02 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > >> I've done 'make world' in both single user mode and multi user > >> .. One thing to watch is that the /usr/libexec/ld.so file gets > >> updated. The last time I did 'make world' in multi user mode it > >> didn't. I tend to 'ls -lt' in the standard directories to check > >> on what didn't get updated. > > > >ld.so is installed using '-C', so if the new version is the same as the > >old one, it's not changed. It's debatable as to whether the use of -C > >is justifiable (it's not a performance improvement, and it makes the > >use of timestamps for identifying stale files unworkable). > > The timestamp first caused me to notice the file. Upon closer > inspection the size between old and new was different, 69K vs 70K > if memory serves (I did check stripped sizes). So if install > really does work around the file being in use then something else > must have failed. I must admit it has only happened once as I do > check the timestamps after every 'make world'. Sounds pretty bogus to me. If the compare fails and the new version is installed, and the install fails, installworld should stop at that point. > Do the include files get installed with -C as well? Until I did > a 'make -DCLOBBER includes' I had timestamps from Oct 22 (which > appears to be the 2.2.5-RELEASE build date) for most of my > include files. See /usr/src/includes/Makefile. Yes. > >The 'installworld' target is almost always successful without any help. > > I like the words "almost always", I use them a lot myself :) Just like "should". Note that the build process in -stable has been relatively unchanged for quite a while. Bruce tunes the -current process, but doesn't bring anything back. What does come back is usually the work of others, and often only deals with critical problems. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 25 14:16:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06376 for freebsd-stable-outgoing; Mon, 25 May 1998 14:16:17 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cyrus.watson.org (BERLIOZ.CODA.CS.CMU.EDU [128.2.242.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06192 for ; Mon, 25 May 1998 14:16:00 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from localhost (robert@localhost) by cyrus.watson.org (8.8.8/8.8.5) with SMTP id RAA06091; Mon, 25 May 1998 17:15:58 -0400 (EDT) Date: Mon, 25 May 1998 17:15:57 -0400 (EDT) From: Robert Watson To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: stable@FreeBSD.ORG Subject: Re: vnconfig + swap with sparse files In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id OAA06265 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 25 May 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > Robert Watson writes: > > I rebooted to stop swapping on the file, and modified my creation program > > to drop a \0 at the beginning of each block. Sure enough, starting > > swapping this time worked fine. > > What you should have done in the first place was: > > # dd if=/dev/zero of=swapfile bs=1048576 count=128 > > A sparse file cannot possibly work as swap since it does not have any > space allocate to it on the disk, and you *want* to allocate space on > the disk - where else are you going to swap out your data? I would argue that more intuitive behavior would be for the pager to get back 0'd pages, as all other users of sparse files do. When I mmap my sparse file, I get 0's :). While this is more intuitive, it may not in reality be feasible. However, a note in vn(4) under BUGS indicating that the vn driver does not automatically allocate pages for sparse files when used, or documenting its error return on attempting to read or write an unallocated block in a sparse file would make sense. Indeed, I did not expect the pager to swap to my sparse file -- I expected the file to become un-sparse as it went along. Robert Watson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 25 15:09:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16117 for freebsd-stable-outgoing; Mon, 25 May 1998 15:09:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16112 for ; Mon, 25 May 1998 15:09:18 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA03323; Mon, 25 May 1998 22:09:01 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA04966; Tue, 26 May 1998 00:08:50 +0200 (MET DST) Message-ID: <19980526000847.42533@follo.net> Date: Tue, 26 May 1998 00:08:47 +0200 From: Eivind Eklund To: Morgan Davis , freebsd-stable@FreeBSD.ORG Subject: Re: Upgrading from BSDI 2.1 -> FreeBSD 2.2.6 References: <000c01bd87a8$84e7ef50$24ae44c6@iopc.cts.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <000c01bd87a8$84e7ef50$24ae44c6@iopc.cts.com>; from Morgan Davis on Sun, May 24, 1998 at 11:44:09PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, May 24, 1998 at 11:44:09PM -0700, Morgan Davis wrote: > If I let it sit long enough (several minutes), about four of these error > message pairs show up. Eventually, it'll get to the main sysinstall screen. > However, it is unable to see any drives in the system, so I can't proceed > with an install. Yet, the initial kernel probes do reveal the Buslogic SCSI > adapter, the Seagate SCSI drive, and a Sony SCSI DAT drive. > > Any hints? Might that BSDI bha0 warning about interrupts be significant > with FreeBSD? Yes. It is damning with FreeBSD, and probably should have been with BSDi, too. The problem probably is that you haven't setup your ISA interrupt reservation correctly (though I'm not quite certain you really can screw a PCI bus doing that wrong...) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 25 15:41:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23174 for freebsd-stable-outgoing; Mon, 25 May 1998 15:41:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23140 for ; Mon, 25 May 1998 15:41:42 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA10934; Mon, 25 May 1998 17:39:51 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805252239.RAA10934@dyson.iquest.net> Subject: Re: vnconfig + swap with sparse files In-Reply-To: from Robert Watson at "May 25, 98 05:15:57 pm" To: robert@cyrus.watson.org (Robert Watson) Date: Mon, 25 May 1998 17:39:51 -0500 (EST) Cc: dag-erli@ifi.uio.no, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > On 25 May 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > > > Robert Watson writes: > > > I rebooted to stop swapping on the file, and modified my creation program > > > to drop a \0 at the beginning of each block. Sure enough, starting > > > swapping this time worked fine. > > > > What you should have done in the first place was: > > > > # dd if=/dev/zero of=swapfile bs=1048576 count=128 > > > > A sparse file cannot possibly work as swap since it does not have any > > space allocate to it on the disk, and you *want* to allocate space on > > the disk - where else are you going to swap out your data? > > I would argue that more intuitive behavior would be for the pager to get > back 0'd pages, as all other users of sparse files do. When I mmap my > sparse file, I get 0's :). While this is more intuitive, it may not in > reality be feasible. However, a note in vn(4) under BUGS indicating that > the vn driver does not automatically allocate pages for sparse files when > used, or documenting its error return on attempting to read or write an > unallocated block in a sparse file would make sense. > > Indeed, I did not expect the pager to swap to my sparse file -- I expected > the file to become un-sparse as it went along. > It is a problematical issue to allocate space during swap pager pageouts. In order to minimize the deadlock issues, the file has to be pre-allocated. When I get swapoff working, I will also make swapon check for files to be properly preallocated. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 25 17:58:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14523 for freebsd-stable-outgoing; Mon, 25 May 1998 17:58:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles201.castles.com [208.214.165.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14342 for ; Mon, 25 May 1998 17:56:17 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA14532; Mon, 25 May 1998 16:52:12 -0700 (PDT) Message-Id: <199805252352.QAA14532@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Morgan Davis" cc: freebsd-stable@FreeBSD.ORG Subject: Re: Upgrading from BSDI 2.1 -> FreeBSD 2.2.6 In-reply-to: Your message of "Sun, 24 May 1998 23:44:09 PDT." <000c01bd87a8$84e7ef50$24ae44c6@iopc.cts.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 May 1998 16:52:11 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > I inherited the duty of upgrading a working BSDI 2.1 system to FreeBSD > 2.2.6, but am having trouble getting sysinstall to come up properly. First, > here's the BSDI 2.1 dmesg output: ... > bha0: warning, interrupts not working, using polling This is fatal; we require interrupts to work for the Buslogic controller. Check the controller configuration, and also check the FreeBSD verbose boot probe output (boot with -v). You can scroll back to see this once sysinstall comes up - hit Scroll Lock and use the cursor keys... The controller may be faulty, or you may have disabled PCI interrupts for the slot it's in (depending on the system in question). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 25 19:13:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25936 for freebsd-stable-outgoing; Mon, 25 May 1998 19:13:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.kersur.net (root@mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25928 for ; Mon, 25 May 1998 19:13:43 -0700 (PDT) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.8.8/8.8.8) with SMTP id WAA15723; Mon, 25 May 1998 22:13:32 -0400 (EDT) Message-Id: <3.0.5.32.19980525221330.0092b610@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 25 May 1998 22:13:30 -0400 To: Mike Smith From: Dan Swartzendruber Subject: Re: Upgrading from BSDI 2.1 -> FreeBSD 2.2.6 Cc: "Morgan Davis" , freebsd-stable@FreeBSD.ORG In-Reply-To: <199805252352.QAA14532@antipodes.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk At 04:52 PM 5/25/98 -0700, Mike Smith wrote: >> I inherited the duty of upgrading a working BSDI 2.1 system to FreeBSD >> 2.2.6, but am having trouble getting sysinstall to come up properly. First, >> here's the BSDI 2.1 dmesg output: >... >> bha0: warning, interrupts not working, using polling > >This is fatal; we require interrupts to work for the Buslogic >controller. Check the controller configuration, and also check the >FreeBSD verbose boot probe output (boot with -v). You can scroll back >to see this once sysinstall comes up - hit Scroll Lock and use the >cursor keys... > >The controller may be faulty, or you may have disabled PCI interrupts >for the slot it's in (depending on the system in question). Check your motherboard also. I've been burned by a motherboard where not all of the PCI slots supported busmastering, and saw this same problem (albeit with Linux, not FreeBSD, but the basic outcome was the same anyway...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 25 20:31:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07763 for freebsd-stable-outgoing; Mon, 25 May 1998 20:31:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hcs.harvard.edu (hcs.harvard.edu [140.247.73.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07754 for ; Mon, 25 May 1998 20:31:24 -0700 (PDT) (envelope-from kemiller@hcs.harvard.edu) Received: (from kemiller@localhost) by hcs.harvard.edu (8.8.5/8.8.3) id XAA30001; Mon, 25 May 1998 23:31:16 -0400 (EDT) Message-ID: <19980525233116.10709@hcs.harvard.edu> Date: Mon, 25 May 1998 23:31:16 -0400 From: Kenneth Miller To: freebsd-stable@FreeBSD.ORG Subject: improper shutdown Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I've had a minor (?) but irritating problem ever since moving to stable from 2.2.5. When I reboot, the disks don't have their clean flags set and need fscking. If I shutdown to singer user mode and manually unmount the disks, and remount / readonly, it's fine. But using the shutdown program to go all the way doesn't work. I will assume this is some misconfiguration on my part, but I was a little perplexed that it began only when I moved to stable. Any suggestions or answers appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 25 20:42:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09567 for freebsd-stable-outgoing; Mon, 25 May 1998 20:42:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09553 for ; Mon, 25 May 1998 20:42:32 -0700 (PDT) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.8.5/8.8.5) id LAA02975 for freebsd-stable@freebsd.org; Tue, 26 May 1998 11:42:26 +0800 (GMT) Date: Tue, 26 May 1998 11:42:26 +0800 (GMT) From: Michael Robinson Message-Id: <199805260342.LAA02975@public.bta.net.cn> To: freebsd-stable@FreeBSD.ORG Subject: Bug in wd driver Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I wrote a message related to this problem to freebsd-questions yesterday, but upon further investigation, I have decided this is a bug, not a feature. I have a Tecra 510CDT (running 2.2.6-RELEASE) that suffered a corrupted disk when the battery power failed as it was trying to halt. I have identified seven contiguous sectors on the disk that cause the following problem: 1. Any I/O access to the affected sectors will cause the following message: wd0: interrupt timeout wd0: status 58 error 0 followed by seeking noises, and the following message: wd0: interrupt timeout wd0: status 50 error 1 2. After this, the process requesting the I/O will be completely locked, but the disk will continue to make seeking noises continuously until the system is powered off. Other processes are able to access the affected slice/partition (ls, cat, etc.) without any difficulty, as long as they avoid the 7 affected sectors. Any process which requires privileged kernel calls (halt, ps, etc.) will lock immediately and completely. 3. Other than the two messages above, wd produces no error messages. 4. Hard reset is the only way to recover. I tried to work around this problem with bad144, but rapidly discovered that bad144 is something of a bad joke in FreeBSD. Does anyone have any recommendations for how to fix the wd driver or otherwise recover from this fault? -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 01:01:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11835 for freebsd-stable-outgoing; Tue, 26 May 1998 01:01:37 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles305.castles.com [208.214.167.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11830 for ; Tue, 26 May 1998 01:01:32 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00702; Mon, 25 May 1998 23:57:36 -0700 (PDT) Message-Id: <199805260657.XAA00702@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Kenneth Miller cc: freebsd-stable@FreeBSD.ORG Subject: Re: improper shutdown In-reply-to: Your message of "Mon, 25 May 1998 23:31:16 EDT." <19980525233116.10709@hcs.harvard.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 May 1998 23:57:35 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > I've had a minor (?) but irritating problem ever since moving to stable > from 2.2.5. When I reboot, the disks don't have their clean flags set > and need fscking. If I shutdown to singer user mode and manually > unmount the disks, and remount / readonly, it's fine. But using the > shutdown program to go all the way doesn't work. I will assume this is > some misconfiguration on my part, but I was a little perplexed that it > began only when I moved to stable. Are you seeing a diagnostic at boot time telling you to update /etc/fstab? Have you done so? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 01:02:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11955 for freebsd-stable-outgoing; Tue, 26 May 1998 01:02:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles305.castles.com [208.214.167.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11815 for ; Tue, 26 May 1998 01:01:04 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00687; Mon, 25 May 1998 23:56:55 -0700 (PDT) Message-Id: <199805260656.XAA00687@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Robinson cc: freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-reply-to: Your message of "Tue, 26 May 1998 11:42:26 +0800." <199805260342.LAA02975@public.bta.net.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 May 1998 23:56:54 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > I wrote a message related to this problem to freebsd-questions > yesterday, but upon further investigation, I have decided this is > a bug, not a feature. Actually, it's almost certainly a hardware fault. > I have a Tecra 510CDT (running 2.2.6-RELEASE) that suffered a > corrupted disk when the battery power failed as it was trying to > halt. I have identified seven contiguous sectors on the disk that > cause the following problem: > > 1. Any I/O access to the affected sectors will cause the following > message: > > wd0: interrupt timeout > wd0: status 58 error 0 The disk has failed to respond to the access request. You may be able to recover by dd'ing zeroes over the whole partition (forcing a block reallocation), however the disk may be damaged beyond repair. > 4. Hard reset is the only way to recover. > > I tried to work around this problem with bad144, but rapidly discovered > that bad144 is something of a bad joke in FreeBSD. Does anyone have > any recommendations for how to fix the wd driver or otherwise recover > from this fault? You could use 'badsect' to isolate the sectors. This is more effective than bad144 (which was a joke long ago). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 03:15:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00228 for freebsd-stable-outgoing; Tue, 26 May 1998 03:15:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gmxlx2.gmx.net (qmailr@gmxlx2.gmx.net [194.97.64.132]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA00201 for ; Tue, 26 May 1998 03:14:54 -0700 (PDT) (envelope-from walterd@gmx.net) Received: (qmail 32622 invoked from network); 26 May 1998 10:14:53 -0000 Received: from wp15port05.highway.telekom.at (HELO artemis) (195.3.66.101) by gmxlx2.gmx.net with SMTP; 26 May 1998 10:14:53 -0000 Message-Id: <3.0.5.32.19980526121825.007a46f0@pop.gmx.net> X-Sender: walterd@pop.gmx.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 26 May 1998 12:18:25 +0200 To: freebsd-stable@FreeBSD.ORG From: "w.d." Subject: what is the cdrom volume label of 2.2.6? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I've downloaded the 2.2.6 files from the ftp and written to CD-R with bootimage. The layout I got from www.cdrom.com (226_cd1.txt, ...). When I specify the cdrom as the filesource, the program mentions the volume label to be incorrect. Continueing the installation is possible, though I have to answer 2 (?) times "yes". Nevertheless how can I circumvent that question? Walter Deuerling Vienna/Austria To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 03:24:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01634 for freebsd-stable-outgoing; Tue, 26 May 1998 03:24:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01615 for ; Tue, 26 May 1998 03:24:17 -0700 (PDT) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.8.5/8.8.5) id SAA11951; Tue, 26 May 1998 18:23:58 +0800 (GMT) Date: Tue, 26 May 1998 18:23:58 +0800 (GMT) From: Michael Robinson Message-Id: <199805261023.SAA11951@public.bta.net.cn> To: mike@smith.net.au Subject: Re: Bug in wd driver Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Mike Smith writes: >> I wrote a message related to this problem to freebsd-questions >> yesterday, but upon further investigation, I have decided this is >> a bug, not a feature. > >Actually, it's almost certainly a hardware fault. Actually, the bug is that the driver does not recover gracefully from a recoverable hardware fault. It instead goes into an infinite loop, taking significant pieces of the kernel with it. >> 1. Any I/O access to the affected sectors will cause the following >> message: >> >> wd0: interrupt timeout >> wd0: status 58 error 0 > >The disk has failed to respond to the access request. You may be able >to recover by dd'ing zeroes over the whole partition (forcing a block >reallocation), however the disk may be damaged beyond repair. I repeat, any attempted access to the affected sectors locks up that process. Unless dd has the ability to circumvent the wd driver, I don't see how I would be able to dd zeroes over the whole partition. >You could use 'badsect' to isolate the sectors. This is more effective >than bad144 (which was a joke long ago). Unfortunately, the sectors in question contain inodes, not data. This means, at the very least, that I would have to newfs the partition, and then, if newfs in any way, shape, or form, attempted to access those sectors, it, too, would fail. What I will probably end up having to do is repartition around that track. However, this seems like an unecessarily crude solution to me, considering how minor the damage is. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 05:28:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15554 for freebsd-stable-outgoing; Tue, 26 May 1998 05:28:33 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from salmon.maths.tcd.ie (mmdf@salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA15191 for ; Tue, 26 May 1998 05:27:25 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from hamilton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 26 May 98 13:27:01 +0100 (BST) To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: Robert Watson , stable@FreeBSD.ORG Subject: Re: vnconfig + swap with sparse files In-reply-to: Your message of "25 May 1998 20:17:26 +0200." Date: Tue, 26 May 1998 13:26:58 +0100 From: David Malone Message-ID: <9805261327.aa21737@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > A sparse file cannot possibly work as swap since it does not have any > space allocate to it on the disk, and you *want* to allocate space on > the disk - where else are you going to swap out your data? Actually - it will work if you are swaping over NFS, (or at least did the last time I made swap files for our xterminals). Though I admit this is quite different. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 06:03:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19673 for freebsd-stable-outgoing; Tue, 26 May 1998 06:03:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cesit1.unifi.it (cesit1.unifi.it [150.217.1.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19655 for ; Tue, 26 May 1998 06:03:18 -0700 (PDT) (envelope-from ugo@dsi.UNIFI.IT) Received: from aguirre.dsi.unifi.it by CESIT1.UNIFI.IT (PMDF V5.1-10 #23168) with SMTP id <01IXHRYFQ5220000TI@CESIT1.UNIFI.IT> for stable@freeBSD.org; Tue, 26 May 1998 15:03:42 MET Received: from dsi.unifi.it (ppp-firenze71-115.iol.it) by aguirre.dsi.unifi.it (4.1/SMI-4.1) id AA21522; Sun, 24 May 1998 10:57:09 +0200 Received: from pegasus.home.net (pegasus.home.net [192.168.1.3]) by dsi.unifi.it (8.8.8/8.8.8) with ESMTP id PAA07037; Tue, 26 May 1998 15:01:37 +0200 (MET DST envelope-from ugo) Received: (from ugo@localhost) by pegasus.home.net (8.8.8/8.8.8) id PAA00322; Tue, 26 May 1998 15:01:37 +0200 (MET DST envelope-from ugo) Date: Tue, 26 May 1998 15:01:37 +0200 (MET DST) From: Ugo Paternostro Subject: RE: chipset identification code merge from -current In-reply-to: <199805240956.CAA01969@baloon.mimi.com> To: asami@cs.berkeley.edu (Satoshi Asami) Cc: stable@FreeBSD.ORG Message-id: Organization: Not an organization MIME-version: 1.0 X-Mailer: XFMail 1.2 [p0] on FreeBSD Content-type: multipart/mixed; boundary="_=XFMail.1.2.p0.FreeBSD:980526150137:243=_" X-Priority: 3 (Normal) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk This message is in MIME format --_=XFMail.1.2.p0.FreeBSD:980526150137:243=_ Content-Type: text/plain; charset=us-ascii On 24-May-98 Satoshi Asami wrote about "chipset identification code merge from -current": > I've made a diff to bring -stable's PCI chipset identification code > almost up to par to -current's. Can people test it? It didn't change much with my M/B (ASUS SP98AGP-X). If you commit your patch, please consider including the following one too: it simply moves all SiS entries together and adds two 5591 entries, so that now I get: ---- Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0:0 pci0:0:1: Silicon Integrated Systems, device=0x5513, class=storage (ide) int a i rq 14 [no driver assigned] chip1 rev 1 on pci0:1:0 pci0:1:1: Silicon Integrated Systems, device=0x0009, class=0xff, subclass=0x00 [ no driver assigned] pci0:1:2: Silicon Integrated Systems, device=0x7001, class=serial, subclass=0x03 int a irq 9 [no driver assigned] chip2 rev 0 on pci0:2:0 vga0 rev 2 int a irq 12 on pci0:10:0 ---- BTW, I don't have an 85c503 chip on my M/B. Just a 5591/5595 pair... P.S.: it applies on top of pcisupport.c previously patched with your own patch. Bye, UP --_=XFMail.1.2.p0.FreeBSD:980526150137:243=_ Content-Disposition: attachment; filename="pcisupport.c.post.satoshi.diff" Content-Transfer-Encoding: base64 Content-Description: pcisupport.c.post.satoshi.diff Content-Type: application/octet-stream; name=pcisupport.c.post.satoshi.diff; SizeOnDisk=1250 LS0tIHBjaXN1cHBvcnQuYy5zYXRvc2hpCVR1ZSBNYXkgMjYgMTQ6Mjk6MjcgMTk5OAorKysgcGNp c3VwcG9ydC5jCVR1ZSBNYXkgMjYgMTQ6Mzc6MTEgMTk5OApAQCAtMTI4LDggKzEyOCw2IEBACiAJ CXJldHVybiAoIkludGVsIDgyNDI0WlggKFNhdHVybikgY2FjaGUgRFJBTSBjb250cm9sbGVyIik7 CiAJY2FzZSAweDA0ODI4MDg2OgogCQlyZXR1cm4gKCJJbnRlbCA4MjM3NUVCIFBDSS1FSVNBIGJy aWRnZSIpOwotCWNhc2UgMHgwNDk2MTAzOToKLQkJcmV0dXJuICgiU2lTIDg1YzQ5NiIpOwogCWNh c2UgMHgwNGEzODA4NjoKIAkJcmV2ID0gKHVuc2lnbmVkKSBwY2lfY29uZl9yZWFkICh0YWcsIFBD SV9DTEFTU19SRUcpICYgMHhmZjsKIAkJaWYgKHJldiA9PSAxNiB8fCByZXYgPT0gMTcpCkBAIC0x NDcsMTIgKzE0NSw2IEBACiAJCXJldHVybiAoIkludGVsIDgyNDM3TVggbW9iaWxlIFBDSSBjYWNo ZSBtZW1vcnkgY29udHJvbGxlciIpOwogCWNhc2UgMHgxMjUwODA4NjoKIAkJcmV0dXJuICgiSW50 ZWwgODI0MzkiKTsKLQljYXNlIDB4MDQwNjEwMzk6Ci0JCXJldHVybiAoIlNpUyA4NWM1MDEiKTsK LQljYXNlIDB4MDAwODEwMzk6Ci0JCXJldHVybiAoIlNpUyA4NWM1MDMiKTsKLQljYXNlIDB4MDYw MTEwMzk6Ci0JCXJldHVybiAoIlNpUyA4NWM2MDEiKTsKIAljYXNlIDB4NzAwMDgwODY6CiAJCXJl dHVybiAoIkludGVsIDgyMzcxU0IgUENJIHRvIElTQSBicmlkZ2UiKTsKIAljYXNlIDB4NzAyMDgw ODY6CkBAIC0yMzIsNiArMjI0LDIwIEBACiAJCXJldHVybiAoIk5FQyAwMDJDIFBDSSB0byBQQy05 OCBDLWJ1cyBicmlkZ2UiKTsKIAljYXNlIDB4MDAzYjEwMzM6CiAJCXJldHVybiAoIk5FQyAwMDNC IFBDSSB0byBQQy05OCBDLWJ1cyBicmlkZ2UiKTsKKworCS8qIFNpUyAtLSB2ZW5kb3IgMHgxMDM5 ICovCisJY2FzZSAweDA0OTYxMDM5OgorCQlyZXR1cm4gKCJTaVMgODVjNDk2Iik7CisJY2FzZSAw eDA0MDYxMDM5OgorCQlyZXR1cm4gKCJTaVMgODVjNTAxIik7CisJY2FzZSAweDAwMDgxMDM5Ogor CQlyZXR1cm4gKCJTaVMgODVjNTAzIik7CisJY2FzZSAweDA2MDExMDM5OgorCQlyZXR1cm4gKCJT aVMgODVjNjAxIik7CisJY2FzZSAweDU1OTExMDM5OgorCQlyZXR1cm4gKCJTaVMgNTU5MSBQQ0kg YnJpZGdlIik7CisJY2FzZSAweDAwMDExMDM5OgorCQlyZXR1cm4gKCJTaVMgNTU5MSBBR1AgYnJp ZGdlIik7CiAJfTsKIAogCWlmIChkZXNjciA9IGdlbmVyaWNfcGNpX2JyaWRnZSh0YWcpKQo= --_=XFMail.1.2.p0.FreeBSD:980526150137:243=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 06:05:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20136 for freebsd-stable-outgoing; Tue, 26 May 1998 06:05:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA20111 for ; Tue, 26 May 1998 06:04:56 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA21948; Tue, 26 May 1998 13:16:15 +0200 From: Luigi Rizzo Message-Id: <199805261116.NAA21948@labinfo.iet.unipi.it> Subject: Re: vnconfig + swap with sparse files To: dwmalone@maths.tcd.ie (David Malone) Date: Tue, 26 May 1998 13:16:15 +0200 (MET DST) Cc: dag-erli@ifi.uio.no, robert+freebsd@cyrus.watson.org, stable@FreeBSD.ORG In-Reply-To: <9805261327.aa21737@salmon.maths.tcd.ie> from "David Malone" at May 26, 98 01:26:39 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > A sparse file cannot possibly work as swap since it does not have any > > space allocate to it on the disk, and you *want* to allocate space on > > the disk - where else are you going to swap out your data? > > Actually - it will work if you are swaping over NFS, (or at least did > the last time I made swap files for our xterminals). Though I admit > this is quite different. if i remember well there was a problem with sparse files and nfs as well, and it was related to block sizes. My understanding of the problem was the following: If the swapper has to save only one page (4K) and the NFS blocksize is 8K, the process involves reading an 8K block from the file, "updating" the 4K half of interest, and writing back to the file. The first read might return some kind of notification that the page did not exist and somehow this caused problems. I may be totally wrong, or the problem might have been fixed (or it could be fixed using 4K NFS blocks) cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 06:49:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26359 for freebsd-stable-outgoing; Tue, 26 May 1998 06:49:21 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles214.castles.com [208.214.165.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26120 for ; Tue, 26 May 1998 06:48:09 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id FAA00386; Tue, 26 May 1998 05:43:42 -0700 (PDT) Message-Id: <199805261243.FAA00386@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Robinson cc: mike@smith.net.au, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-reply-to: Your message of "Tue, 26 May 1998 18:23:58 +0800." <199805261023.SAA11951@public.bta.net.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 05:43:42 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Mike Smith writes: > >> I wrote a message related to this problem to freebsd-questions > >> yesterday, but upon further investigation, I have decided this is > >> a bug, not a feature. > > > >Actually, it's almost certainly a hardware fault. > > Actually, the bug is that the driver does not recover gracefully from a > recoverable hardware fault. It instead goes into an infinite loop, taking > significant pieces of the kernel with it. Actually, an interrupt timeout is not a "recoverable hardware fault". This is a basic failure in the driver:controller protocol on the part of the drive. > >> 1. Any I/O access to the affected sectors will cause the following > >> message: > >> > >> wd0: interrupt timeout > >> wd0: status 58 error 0 > > > >The disk has failed to respond to the access request. You may be able > >to recover by dd'ing zeroes over the whole partition (forcing a block > >reallocation), however the disk may be damaged beyond repair. > > I repeat, any attempted access to the affected sectors locks up that > process. Unless dd has the ability to circumvent the wd driver, I don't > see how I would be able to dd zeroes over the whole partition. With the level of detail you provided, it was not possible to determine whether "any access" referred to read or write operations. If the disk can recover the sector(s) involved, and is not required to read from them first, a dd operation will put it in a position to do so. The fault is fairly likely related to scribble which occurred when you powered down during a write operation. You may have damaged non-recoverable metadata in the process, and the drive may not handle this case well. It is also possible that the drive is taking an inordinate amount of time before returning an error, and the interrupt timeout is preempting this return (that isn't actually likely, given the drive status above). The fact that an unrecoverable disk error locks other parts of the kernel is understandable, if not desirable. There isn't a lot that can trivially be done about this though. > What I will probably end up having to do is repartition around that track. > However, this seems like an unecessarily crude solution to me, considering > how minor the damage is. Disk metadata damage that causes the drive firmware to fail doesn't strike me as "minor" in any common usage of the term. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 07:01:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27854 for freebsd-stable-outgoing; Tue, 26 May 1998 07:01:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hcs.harvard.edu (hcs.harvard.edu [140.247.73.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27842 for ; Tue, 26 May 1998 07:01:02 -0700 (PDT) (envelope-from kemiller@hcs.harvard.edu) Received: (from kemiller@localhost) by hcs.harvard.edu (8.8.5/8.8.3) id KAA30996; Tue, 26 May 1998 10:00:31 -0400 (EDT) Message-ID: <19980526100031.47594@hcs.harvard.edu> Date: Tue, 26 May 1998 10:00:31 -0400 From: Kenneth Miller To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: improper shutdown References: <19980525233116.10709@hcs.harvard.edu> <199805260657.XAA00702@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199805260657.XAA00702@antipodes.cdrom.com>; from Mike Smith on Mon, May 25, 1998 at 11:57:35PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Monday, 05/25/98 at 11:57:35 PM, Mike Smith wrote: > > > > I've had a minor (?) but irritating problem ever since moving to stable > > from 2.2.5. When I reboot, the disks don't have their clean flags set > > and need fscking. If I shutdown to singer user mode and manually > > unmount the disks, and remount / readonly, it's fine. But using the > > shutdown program to go all the way doesn't work. I will assume this is > > some misconfiguration on my part, but I was a little perplexed that it > > began only when I moved to stable. > > Are you seeing a diagnostic at boot time telling you to update > /etc/fstab? Have you done so? if you're referring to the sd0a vs sd03a thing, that's not it. the only diagnostic i'm getting is CLEAN BIT NOT SET IN SUPERBLOCK. if you're referring to anything else, i don't think i've seen it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 07:06:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28909 for freebsd-stable-outgoing; Tue, 26 May 1998 07:06:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hcs.harvard.edu (hcs.harvard.edu [140.247.73.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28902 for ; Tue, 26 May 1998 07:06:23 -0700 (PDT) (envelope-from kemiller@hcs.harvard.edu) Received: (from kemiller@localhost) by hcs.harvard.edu (8.8.5/8.8.3) id KAA19773; Tue, 26 May 1998 10:06:17 -0400 (EDT) Message-ID: <19980526100616.03028@hcs.harvard.edu> Date: Tue, 26 May 1998 10:06:16 -0400 From: Kenneth Miller To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: improper shutdown References: <19980525233116.10709@hcs.harvard.edu> <199805260657.XAA00702@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199805260657.XAA00702@antipodes.cdrom.com>; from Mike Smith on Mon, May 25, 1998 at 11:57:35PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Monday, 05/25/98 at 11:57:35 PM, Mike Smith wrote: > > > > I've had a minor (?) but irritating problem ever since moving to stable > > from 2.2.5. When I reboot, the disks don't have their clean flags set > > and need fscking. If I shutdown to singer user mode and manually > > unmount the disks, and remount / readonly, it's fine. But using the > > shutdown program to go all the way doesn't work. I will assume this is > > some misconfiguration on my part, but I was a little perplexed that it > > began only when I moved to stable. > > Are you seeing a diagnostic at boot time telling you to update > /etc/fstab? Have you done so? (I said this in private email too.) If you're referring to the sd0a/sd03a root partition thing, i've already updated that. But in any case I've seen no such message, just fsck reporting CLEAN FLAG NOT SET IN SUPERBLOCK for all my ufs partitions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 07:15:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00636 for freebsd-stable-outgoing; Tue, 26 May 1998 07:15:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00609 for ; Tue, 26 May 1998 07:15:10 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.8/8.7.3) with ESMTP id JAA10716; Tue, 26 May 1998 09:12:29 -0400 (EDT) Message-Id: <199805261312.JAA10716@whizzo.transsys.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Robert Watson cc: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= , stable@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: vnconfig + swap with sparse files References: In-reply-to: Your message of "Mon, 25 May 1998 17:15:57 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 26 May 1998 09:12:29 -0400 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA00614 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Indeed, I did not expect the pager to swap to my sparse file -- I expected > the file to become un-sparse as it went along. Even if you *could* make this work, would you want to? From my experience years ago using a NeXTSTEP computer with a Mach OS which generally *only* used a swapfile, you want to preallocate the file. This gives the filesystem the opportunity to make better (and perhaps continguous or within the same CG) block allocation. In fact, the installation procedure allocated the swapfile very early on in the software installation process before the disk space became fragmented. On the NeXT, they used a dedicated program rather than dd as suggested before, mostly because they didn't have a /dev/zero I think. That being said, the NeXTSTEP OS did dynamically grow the swapfile as required, and when the system was booted, it truncated the file at some pre-configured size. The "holy grail" that everyone wanted was the ability of the OS to contract a swapfile it had grown beyond it's initial (preallocated) size, but as far as I know, this never happened. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 08:04:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10041 for freebsd-stable-outgoing; Tue, 26 May 1998 08:04:06 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09880 for ; Tue, 26 May 1998 08:03:55 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA20466; Tue, 26 May 1998 09:02:27 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA05071; Tue, 26 May 1998 09:02:19 -0600 Date: Tue, 26 May 1998 09:02:19 -0600 Message-Id: <199805261502.JAA05071@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Michael Robinson , freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-Reply-To: <199805261243.FAA00386@antipodes.cdrom.com> References: <199805261023.SAA11951@public.bta.net.cn> <199805261243.FAA00386@antipodes.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > >> I wrote a message related to this problem to freebsd-questions > > >> yesterday, but upon further investigation, I have decided this is > > >> a bug, not a feature. > > > > > >Actually, it's almost certainly a hardware fault. > > > > Actually, the bug is that the driver does not recover gracefully from a > > recoverable hardware fault. It instead goes into an infinite loop, taking > > significant pieces of the kernel with it. > > Actually, an interrupt timeout is not a "recoverable hardware fault". Sure it is. You're being silly now Mike, this is indeed a 'bug' in the driver, but it's probably not one that's going to be fixed unless the submitter fixes it himself. Fixing it is non-trivial but possible to do. Having a bad spot on a disk shouldn't make the disk *totally* unusable, as every other 'significant' OS can deal with fine. This is also why I was w/out a laptop for 5 months, since our driver couldn't get past the bad sector on the boot partition when it went bad and everytime fsck tried to read it it locked up the computer. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 08:57:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20981 for freebsd-stable-outgoing; Tue, 26 May 1998 08:57:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA20918 for ; Tue, 26 May 1998 08:57:13 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 17153 invoked by uid 1000); 26 May 1998 16:58:53 -0000 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 In-Reply-To: Date: Tue, 26 May 1998 12:58:53 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Raul Zighelboim Subject: RE: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Tom , Charles Owens Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 22-May-98 Raul Zighelboim wrote: > > My 0.02 cents: > I did not installed FreeBSd on a DPT controller, but with an > Adaptec controller. Nevertheless, I have a DPT controller on a system > with a large fs (71780140 1K blocks). The system works, works well and > has been up for 4 days as a very busy usenet news spool directory. > This is running 2.2-RELENG from last sunday. This confirms my observations. Thanx. > As a sidebar; the DOS configuration software can only create arrays with > up to 1 mbyte interleave. Is this a limitation on the hardware or the > software ? Is (will there be) a way to create an array with a larger > interleave (32 megs comes to mind). An interleave factor larger than 1MB will be very inefficient: a. The SCSI bus will be used (locked) for long periods. This will cause poor multi-tasking response. b. The cache memory will be able to contain very few stripes. Also notice that in the context of FreeBSD, anything larger than 64K is sort of mute, as the O/S limits all SCSI transfers to that size. I do not know yet how CAM will do, but suspect it to be the same. Ideally, stripe size should be such that the latency in setting up a transfer + the latency in completeing a DPT-Host transfer are about equal to the time to transfer one block (the reality is a bit more complex than that); In this manner, the DPT can continue to ``feed'' blocks to the system (or the other way around) without pausing for disk. This is why a multiple-bus equipped DPT can achive transfer rates that are limited by the PCI bus and/or the O/S. This takes some careful tuning and experimentation. > Thanks, Simon, for a job well done. Thanx. I am going to get started on CAM port in the next few days. > > ================================================== > Raul Zighelboim rzig@verio.net > >> -----Original Message----- >> From: Charles Owens [SMTP:owensc@enc.edu] >> Sent: Friday, May 22, 1998 2:43 PM >> To: Simon Shapiro >> Cc: Tom; freebsd-stable@FreeBSD.ORG; freebsd-scsi@FreeBSD.ORG >> Subject: RE: DPT install problem >> >> On Fri, 22 May 1998, Simon Shapiro wrote: >> >> > >> > On 21-May-98 Tom wrote: >> > > >> > > I'm trying to use the boot-dpt 2.2.6-RELEASE floppy to bootstrap >> a new >> > > DPT based system. However, sysinstall hangs after newfs'ing the >> > > filesystems. >> > > >> > > I'm using a 21GB array, with auto-defaults for the filesystems, >> so /usr >> > > is over 20GB in size. If I delete /usr and replace it with a >> 500MB >> > > filesystem, leaving the remaining space unallocated, sysinstall >> has no >> > > problem completing the newfs step. >> > > >> > > Anyone else had problems with sysinstall on a mid-sized array >> like >> > > this? >> > >> > Yup. Me :-) >> > But not on 3.0-current. I noticed that 2.2 does not like huge >> partitions, >> > but this is not consnstent. >> > >> > Simon >> >> This has me a bit nervous. This July I will be implementing an NFS >> server >> with a 60GB DTP-based array. My plan has been to use 2.2-stable... >> but >> perhaps 3.0-current is my only choice? Is this -stable problem >> understood, with a fix coming any time soon? >> >> Any other concerns that I should be sweating about as I'm planning on >> building an array of this size? (and it will probably double in size >> the >> following summer) >> >> Thanks, >> --- >> ---------------------------------------------------------------------- >> --- >> Charles N. Owens Email: >> owensc@enc.edu >> >> http://www.enc.edu/~owensc >> Network & Systems Administrator >> Information Technology Services "Outside of a dog, a book is a >> man's >> Eastern Nazarene College best friend. Inside of a dog it's >> too dark to read." - Groucho Marx >> ---------------------------------------------------------------------- >> --- >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-scsi" in the body of the message --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 09:05:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22903 for freebsd-stable-outgoing; Tue, 26 May 1998 09:05:41 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA22751 for ; Tue, 26 May 1998 09:04:36 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 17921 invoked by uid 1000); 26 May 1998 17:06:15 -0000 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 In-Reply-To: <199805222221.PAA02816@dingo.cdrom.com> Date: Tue, 26 May 1998 13:06:15 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Smith Subject: Re: DPT install problem Cc: Tom , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 22-May-98 Mike Smith wrote: >> >> > However, there are a couple of things that you personally (and other >> > concerned users) can do to help the situation. >> > >> > - Contribute commentary (as you have), documentation and source/ >> > procedural fixes. Remeber that FreeBSD is a volunteer project - >> > your support means that it will continue to improve. >> > - Donate a DPT controller to our testing pool so that we can test >> > with it. Chances are we can scrape enough disks together in one >> > place to meet the 20GB mark if we have one. >> >> I recently donated TWO DPT controllers and FIVE disk drives. They went >> to >> two separate FreeBSD prominent figures, but still do not add up to 20GB. > > Then we need some accountability from these prominent figures. Where > is their feedback on this discussion? I should not speak for others but I belive their systems are up and coming. Alas, they have been supplied with only few drives each. There are only few of us with large enough arrays to notice these problems. >> An ajacent problem, is that fsck will fail on such filesystems. >> The failure mode is fsck -p in /etc/rc. It does not have, by default >> enough resources to run a large parallel fsck. I added the following to >> /etc/rc: > > You should update the daemon class in /etc/login.conf. Can you verify > that the current settings there (/usr/src/etc/login.conf) are adequate? I am using (as of today, still to be tried): # # Settings used by /etc/rc # daemon:\ :coredumpsize@:\ :coredumpsize-cur=0:\ :datasize=infinity:\ :datasize-cur@:\ :maxproc=512:\ :maxproc-cur@:\ :memoryuse-cur=infinity:\ :memorylocked-cur=infinity:\ :openfiles=1024:\ :openfiles-cur@:\ :stacksize=infinity:\ :stacksize-cur@:\ :tc=default: as opposed to: ulimit -t unlimited ulimit -f unlimited ulimit -d unlimited ulimit -s unlimited ulimit -c unlimited ulimit -m unlimited ulimit -l unlimited BTW, what is foo@ in this file? > > (Note that a normal build does not update /etc, so you may be suffering > needlessly...) > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 09:06:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23172 for freebsd-stable-outgoing; Tue, 26 May 1998 09:06:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA22891 for ; Tue, 26 May 1998 09:05:30 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 17931 invoked by uid 1000); 26 May 1998 17:07:10 -0000 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 In-Reply-To: Date: Tue, 26 May 1998 13:07:10 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: RE: DPT install problem Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 22-May-98 Tom wrote: > > On Fri, 22 May 1998, Simon Shapiro wrote: > >> >> I agree, but I do virtually most of my new installs on 3.0 and with >> filesystems of 4GB or smaller. Some 16GB filesystems seem to work fine. >> >> It may very well be that the problem is in the fact that the swap device >> may or may not be activated at the time of newfs. Does anyone know the >> answer to this question? > > I'm pretty sure swap is enabled at that point. > > It is doesn't seem like an out of memory issue, becuase I would expect > newfs to die with an error. Also, newfs seems to run to completion > (prints a new line after the last line of sector numbers). Not a memory, but a ulimit problem. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 09:11:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24452 for freebsd-stable-outgoing; Tue, 26 May 1998 09:11:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA24392 for ; Tue, 26 May 1998 09:11:29 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 18024 invoked by uid 1000); 26 May 1998 17:13:10 -0000 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 In-Reply-To: Date: Tue, 26 May 1998 13:13:10 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: Re: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Eivind Eklund Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 23-May-98 Tom wrote: > > On Fri, 22 May 1998, Eivind Eklund wrote: > >> On Fri, May 22, 1998 at 10:41:41AM -0700, Tom wrote: >> > Yes, it seems to be a sysinstall interaction. If I leave the space >> > unallocated, and then disklabel and newfs it later, it works fine. >> > >> > Currently it is pretty hard to bootstrap a new DPT system. You have >> > to >> > be able to build a kernel somewhere else as sysinstall will install a >> > non-DPT kernel, and you can't use sysinstall to allocate large DPT >> > partitions. I fear for the new user. >> >> sysinstall doesn't do this anymore. The DPT driver is activated as >> part of the standard sysinstall now. > > I've noticed that. But this won't help anyone until 2.2.7 is released, > or somone makes a 2.2.6 snapshot with the new GENERIC kernel. I should have a kernel image in ftp://ftp.simon-shapiro.org/FreeBSD. >> As for large arrays: I think that will have to be left to you that >> actually have those large arrays - it is kind of difficult for us >> others to find out where the problem is. I suspect libdisk might be >> the culprit; it interact with the slice code using different IOCTLs >> than disklabel, IIRC. > > So you think that sysinstall makes a bogus label? Remember, sysinstall > hangs basically right after newfs'ing the large filesystem. Either newfs > hangs while cleaning up, or something that sysinstall does after > newfs'ing > all the filesystems hangs. > > Another interesting tibbit, is that sysinstall seems to be generating > once a second disk i/o requests during this hung state. Could be stuck > in > loop. > >> Eivind. > > Tom > --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 09:18:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25724 for freebsd-stable-outgoing; Tue, 26 May 1998 09:18:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25497; Tue, 26 May 1998 09:17:38 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA09118; Tue, 26 May 1998 16:17:37 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA15943; Tue, 26 May 1998 18:17:36 +0200 (MET DST) Message-ID: <19980526181726.17568@follo.net> Date: Tue, 26 May 1998 18:17:26 +0200 From: Eivind Eklund To: shimon@simon-shapiro.org, Tom Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: DPT install problem References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Simon Shapiro on Tue, May 26, 1998 at 01:13:10PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, May 26, 1998 at 01:13:10PM -0400, Simon Shapiro wrote: > > On 23-May-98 Tom wrote: > > > > On Fri, 22 May 1998, Eivind Eklund wrote: > > > >> On Fri, May 22, 1998 at 10:41:41AM -0700, Tom wrote: > >> > Yes, it seems to be a sysinstall interaction. If I leave the space > >> > unallocated, and then disklabel and newfs it later, it works fine. > >> > > >> > Currently it is pretty hard to bootstrap a new DPT system. You have > >> > to > >> > be able to build a kernel somewhere else as sysinstall will install a > >> > non-DPT kernel, and you can't use sysinstall to allocate large DPT > >> > partitions. I fear for the new user. > >> > >> sysinstall doesn't do this anymore. The DPT driver is activated as > >> part of the standard sysinstall now. > > > > I've noticed that. But this won't help anyone until 2.2.7 is released, > > or somone makes a 2.2.6 snapshot with the new GENERIC kernel. > > I should have a kernel image in ftp://ftp.simon-shapiro.org/FreeBSD. This shouldn't be necessary any more - there are daily snapshots at ftp://releng22.freebsd.org/pub/FreeBSD including the DPT driver. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 09:19:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26229 for freebsd-stable-outgoing; Tue, 26 May 1998 09:19:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26149; Tue, 26 May 1998 09:19:42 -0700 (PDT) (envelope-from owensc@enc.edu) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id MAA17648; Tue, 26 May 1998 12:11:17 -0400 (EDT) Date: Tue, 26 May 1998 12:11:17 -0400 (EDT) From: Charles Owens Reply-To: Charles Owens To: Simon Shapiro cc: Raul Zighelboim , freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Tom Subject: RE: DPT install problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, 26 May 1998, Simon Shapiro wrote: > > On 22-May-98 Raul Zighelboim wrote: > > > > My 0.02 cents: > > I did not installed FreeBSd on a DPT controller, but with an > > Adaptec controller. Nevertheless, I have a DPT controller on a system > > with a large fs (71780140 1K blocks). The system works, works well and > > has been up for 4 days as a very busy usenet news spool directory. > > This is running 2.2-RELENG from last sunday. > > This confirms my observations. Thanx. > > > As a sidebar; the DOS configuration software can only create arrays with > > up to 1 mbyte interleave. Is this a limitation on the hardware or the > > software ? Is (will there be) a way to create an array with a larger > > interleave (32 megs comes to mind). > > An interleave factor larger than 1MB will be very inefficient: > > a. The SCSI bus will be used (locked) for long periods. This will > cause poor multi-tasking response. > > b. The cache memory will be able to contain very few stripes. > > Also notice that in the context of FreeBSD, anything larger than 64K is > sort of mute, as the O/S limits all SCSI transfers to that size. I do not > know yet how CAM will do, but suspect it to be the same. > > Ideally, stripe size should be such that the latency in setting up a > transfer + the latency in completeing a DPT-Host transfer are about equal > to the time to transfer one block (the reality is a bit more complex than > that); In this manner, the DPT can continue to ``feed'' blocks to the > system (or the other way around) without pausing for disk. This is why a > multiple-bus equipped DPT can achive transfer rates that are limited by the > PCI bus and/or the O/S. This takes some careful tuning and experimentation. The setup I'm planning consists of 14 4.5GB UW (probably Seagate Cheetahs) drives split across two busses (using the DPT 3334UW/2). If you don't mind, could you comment a bit further as to what this tuning would entail in my case? The array will be at the heart of a file server cluster housing user and group home directories for 1300 or so users. Also, how much cache RAM on the controller is practically useful? Thanks, Charles > > > > ================================================== > > Raul Zighelboim rzig@verio.net > > > >> -----Original Message----- > >> From: Charles Owens [SMTP:owensc@enc.edu] > >> Sent: Friday, May 22, 1998 2:43 PM > >> To: Simon Shapiro > >> Cc: Tom; freebsd-stable@FreeBSD.ORG; freebsd-scsi@FreeBSD.ORG > >> Subject: RE: DPT install problem > >> > >> On Fri, 22 May 1998, Simon Shapiro wrote: > >> > >> > > >> > On 21-May-98 Tom wrote: > >> > > > >> > > I'm trying to use the boot-dpt 2.2.6-RELEASE floppy to bootstrap > >> a new > >> > > DPT based system. However, sysinstall hangs after newfs'ing the > >> > > filesystems. > >> > > > >> > > I'm using a 21GB array, with auto-defaults for the filesystems, > >> so /usr > >> > > is over 20GB in size. If I delete /usr and replace it with a > >> 500MB > >> > > filesystem, leaving the remaining space unallocated, sysinstall > >> has no > >> > > problem completing the newfs step. > >> > > > >> > > Anyone else had problems with sysinstall on a mid-sized array > >> like > >> > > this? > >> > > >> > Yup. Me :-) > >> > But not on 3.0-current. I noticed that 2.2 does not like huge > >> partitions, > >> > but this is not consnstent. > >> > > >> > Simon > >> > >> This has me a bit nervous. This July I will be implementing an NFS > >> server > >> with a 60GB DTP-based array. My plan has been to use 2.2-stable... > >> but > >> perhaps 3.0-current is my only choice? Is this -stable problem > >> understood, with a fix coming any time soon? > >> > >> Any other concerns that I should be sweating about as I'm planning on > >> building an array of this size? (and it will probably double in size > >> the > >> following summer) > >> > >> Thanks, > >> --- > >> ---------------------------------------------------------------------- > >> --- > >> Charles N. Owens Email: > >> owensc@enc.edu > >> > >> http://www.enc.edu/~owensc > >> Network & Systems Administrator > >> Information Technology Services "Outside of a dog, a book is a > >> man's > >> Eastern Nazarene College best friend. Inside of a dog it's > >> too dark to read." - Groucho Marx > >> ---------------------------------------------------------------------- > >> --- > >> > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-scsi" in the body of the message > > --- > > > Sincerely Yours, > > Simon Shapiro Shimon@Simon-Shapiro.ORG > 770.265.7340 > --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 10:16:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07743 for freebsd-stable-outgoing; Tue, 26 May 1998 10:16:22 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07633 for ; Tue, 26 May 1998 10:16:03 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA20027; Tue, 26 May 1998 12:14:23 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805261714.MAA20027@dyson.iquest.net> Subject: Re: vnconfig + swap with sparse files In-Reply-To: <199805261116.NAA21948@labinfo.iet.unipi.it> from Luigi Rizzo at "May 26, 98 01:16:15 pm" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Tue, 26 May 1998 12:14:22 -0500 (EST) Cc: dwmalone@maths.tcd.ie, dag-erli@ifi.uio.no, robert+freebsd@cyrus.watson.org, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > > A sparse file cannot possibly work as swap since it does not have any > > > space allocate to it on the disk, and you *want* to allocate space on > > > the disk - where else are you going to swap out your data? > > > > Actually - it will work if you are swaping over NFS, (or at least did > > the last time I made swap files for our xterminals). Though I admit > > this is quite different. > > if i remember well there was a problem with sparse files and nfs as > well, and it was related to block sizes. > > My understanding of the problem was the following: > > If the swapper has to save only one page (4K) and the NFS blocksize > is 8K, the process involves reading an 8K block from the file, > "updating" the 4K half of interest, and writing back to the file. The > first read might return some kind of notification that the page did not > exist and somehow this caused problems. > > I may be totally wrong, or the problem might have been fixed (or it > could be fixed using 4K NFS blocks) > That code is a nightmare, and needs work. It might be better in -current, but is still a mess. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 10:17:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08104 for freebsd-stable-outgoing; Tue, 26 May 1998 10:17:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from keaggy.canonware.com (canonware.com [206.184.206.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08078 for ; Tue, 26 May 1998 10:17:40 -0700 (PDT) (envelope-from jasone@canonware.com) Received: from localhost (jasone@localhost) by keaggy.canonware.com (8.8.8/8.8.7) with SMTP id KAA21518; Tue, 26 May 1998 10:16:35 -0700 (PDT) (envelope-from jasone@canonware.com) Date: Tue, 26 May 1998 10:16:34 -0700 (PDT) From: Jason Evans To: Mike Smith cc: Kenneth Miller , freebsd-stable@FreeBSD.ORG Subject: Re: improper shutdown In-Reply-To: <199805260657.XAA00702@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Kenneth Miller probably wrote: > > > > I've had a minor (?) but irritating problem ever since moving to stable > > from 2.2.5. When I reboot, the disks don't have their clean flags set > > and need fscking. If I shutdown to singer user mode and manually > > unmount the disks, and remount / readonly, it's fine. But using the > > shutdown program to go all the way doesn't work. I will assume this is > > some misconfiguration on my part, but I was a little perplexed that it > > began only when I moved to stable. I've been seeing this recently too. The first kernel I can guarantee had the problem was one built on April 25th. I too have updated my fstab as was required (to move away from the compatibility slice, right?). My /etc/fstab: ======================================================================== # Device Mountpoint FStype Options Dump Pass# /dev/wd0s2b none swap sw 0 0 /dev/wd0s2a / ufs rw 1 1 /dev/wd0s2f /usr ufs rw 2 2 /dev/wd0s2e /var ufs rw 2 2 proc /proc procfs rw 0 0 /dev/wcd0c /cdrom cd9660 ro,noauto 0 0 /dev/sd0s1 /syjet ufs rw,noauto 0 0 keaggy:/usr/home /usr/home nfs rw 0 0 keaggy:/space /space nfs rw 0 0 keaggy:/var/mail /var/mail nfs rw 0 0 keaggy:/usr /keaggy_usr nfs rw 0 0 ======================================================================== I built a new kernel yesterday (as well as doing a 'make world'), and when I rebooted to use the new kernel, I saw something like: Syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Giving up. The machine is a P5-166, 128 MB RAM, Seagate 2.1GB(?) EIDE HDD, 2940UW with a Syjet drive (no cartridge in it at shutdown), 3COM 3C509B ethernet. Jason Jason Evans Email: [jasone@canonware.com] Web: [http://www.canonware.com/~jasone] Home phone: [(650) 856-8204] Work phone: [(408) 774-8007] Quote: ["Invention is 1% inspiration and 99% perspiration" - Thomas Edison] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 10:22:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09284 for freebsd-stable-outgoing; Tue, 26 May 1998 10:22:17 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA09242 for ; Tue, 26 May 1998 10:22:06 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 18792 invoked by uid 1000); 26 May 1998 18:23:47 -0000 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 In-Reply-To: Date: Tue, 26 May 1998 14:23:47 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Charles Owens Subject: RE: DPT install problem Cc: Tom , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, Raul Zighelboim Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 26-May-98 Charles Owens wrote: > On Tue, 26 May 1998, Simon Shapiro wrote: > >> >> On 22-May-98 Raul Zighelboim wrote: >> > >> > My 0.02 cents: >> > I did not installed FreeBSd on a DPT controller, but with an >> > Adaptec controller. Nevertheless, I have a DPT controller on a system >> > with a large fs (71780140 1K blocks). The system works, works well >> > and >> > has been up for 4 days as a very busy usenet news spool directory. >> > This is running 2.2-RELENG from last sunday. >> >> This confirms my observations. Thanx. >> >> > As a sidebar; the DOS configuration software can only create arrays >> > with >> > up to 1 mbyte interleave. Is this a limitation on the hardware or the >> > software ? Is (will there be) a way to create an array with a larger >> > interleave (32 megs comes to mind). >> >> An interleave factor larger than 1MB will be very inefficient: >> >> a. The SCSI bus will be used (locked) for long periods. This will >> cause poor multi-tasking response. >> >> b. The cache memory will be able to contain very few stripes. >> >> Also notice that in the context of FreeBSD, anything larger than 64K is >> sort of mute, as the O/S limits all SCSI transfers to that size. I do >> not >> know yet how CAM will do, but suspect it to be the same. >> >> Ideally, stripe size should be such that the latency in setting up a >> transfer + the latency in completeing a DPT-Host transfer are about >> equal >> to the time to transfer one block (the reality is a bit more complex >> than >> that); In this manner, the DPT can continue to ``feed'' blocks to the >> system (or the other way around) without pausing for disk. This is why >> a >> multiple-bus equipped DPT can achive transfer rates that are limited by >> the >> PCI bus and/or the O/S. This takes some careful tuning and >> experimentation. > > The setup I'm planning consists of 14 4.5GB UW (probably Seagate > Cheetahs) > drives split across two busses (using the DPT 3334UW/2). If you don't > mind, could you comment a bit further as to what this tuning would entail > in my case? > > The array will be at the heart of a file server cluster housing user and > group home directories for 1300 or so users. > > Also, how much cache RAM on the controller is practically useful? Use the default stripe size (32k-64K). When selecting drives, alternate between the busses. Use top quality cabling and termination. Leave 1 drive as a hot spare. Experiment with your application and stripe sizes (although for home directories, anything 16K and above will work. Try to split the array into several filesystems; fsck on 50GB takes a while. AS much cache as possible. Cannot have too much. Play with the percentage of read-ahead and the percentage of dirty pages in dptmgr. Play with individual drives' cache parameters too. Post the results (or at least send them to me). Seriously consider using DPT drives, and DPT ECC memory, if possible, in DPT cabinets. You will get a much more reliable setup, with easier maintenance. Simon > > Thanks, > Charles > >> > >> > ================================================== >> > Raul Zighelboim rzig@verio.net >> > >> >> -----Original Message----- >> >> From: Charles Owens [SMTP:owensc@enc.edu] >> >> Sent: Friday, May 22, 1998 2:43 PM >> >> To: Simon Shapiro >> >> Cc: Tom; freebsd-stable@FreeBSD.ORG; freebsd-scsi@FreeBSD.ORG >> >> Subject: RE: DPT install problem >> >> >> >> On Fri, 22 May 1998, Simon Shapiro wrote: >> >> >> >> > >> >> > On 21-May-98 Tom wrote: >> >> > > >> >> > > I'm trying to use the boot-dpt 2.2.6-RELEASE floppy to >> >> > > bootstrap >> >> a new >> >> > > DPT based system. However, sysinstall hangs after newfs'ing the >> >> > > filesystems. >> >> > > >> >> > > I'm using a 21GB array, with auto-defaults for the filesystems, >> >> so /usr >> >> > > is over 20GB in size. If I delete /usr and replace it with a >> >> 500MB >> >> > > filesystem, leaving the remaining space unallocated, sysinstall >> >> has no >> >> > > problem completing the newfs step. >> >> > > >> >> > > Anyone else had problems with sysinstall on a mid-sized array >> >> like >> >> > > this? >> >> > >> >> > Yup. Me :-) >> >> > But not on 3.0-current. I noticed that 2.2 does not like huge >> >> partitions, >> >> > but this is not consnstent. >> >> > >> >> > Simon >> >> >> >> This has me a bit nervous. This July I will be implementing an NFS >> >> server >> >> with a 60GB DTP-based array. My plan has been to use 2.2-stable... >> >> but >> >> perhaps 3.0-current is my only choice? Is this -stable problem >> >> understood, with a fix coming any time soon? >> >> >> >> Any other concerns that I should be sweating about as I'm planning on >> >> building an array of this size? (and it will probably double in size >> >> the >> >> following summer) >> >> >> >> Thanks, >> >> --- >> >> ---------------------------------------------------------------------- >> >> --- >> >> Charles N. Owens Email: >> >> owensc@enc.edu >> >> >> >> http://www.enc.edu/~owensc >> >> Network & Systems Administrator >> >> Information Technology Services "Outside of a dog, a book is a >> >> man's >> >> Eastern Nazarene College best friend. Inside of a dog it's >> >> too dark to read." - Groucho Marx >> >> ---------------------------------------------------------------------- >> >> --- >> >> >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> >> with "unsubscribe freebsd-scsi" in the body of the message >> >> --- >> >> >> Sincerely Yours, >> >> Simon Shapiro >> Shimon@Simon-Shapiro.ORG >> 770.265.7340 >> > > --- > ------------------------------------------------------------------------- > Charles N. Owens Email: owensc@enc.edu > http://www.enc.edu/~owensc > Network & Systems Administrator > Information Technology Services "Outside of a dog, a book is a man's > Eastern Nazarene College best friend. Inside of a dog it's > too dark to read." - Groucho Marx > ------------------------------------------------------------------------- > > --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 10:40:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12556 for freebsd-stable-outgoing; Tue, 26 May 1998 10:40:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12355; Tue, 26 May 1998 10:39:34 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA20179; Tue, 26 May 1998 12:39:04 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805261739.MAA20179@dyson.iquest.net> Subject: Re: DPT install problem In-Reply-To: from Simon Shapiro at "May 26, 98 01:06:15 pm" To: shimon@simon-shapiro.org Date: Tue, 26 May 1998 12:39:04 -0500 (EST) Cc: mike@smith.net.au, tom@sdf.com, freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > On 22-May-98 Mike Smith wrote: > >> > >> > However, there are a couple of things that you personally (and other > >> > concerned users) can do to help the situation. > >> > > >> > - Contribute commentary (as you have), documentation and source/ > >> > procedural fixes. Remeber that FreeBSD is a volunteer project - > >> > your support means that it will continue to improve. > >> > - Donate a DPT controller to our testing pool so that we can test > >> > with it. Chances are we can scrape enough disks together in one > >> > place to meet the 20GB mark if we have one. > >> > >> I recently donated TWO DPT controllers and FIVE disk drives. They went > >> to > >> two separate FreeBSD prominent figures, but still do not add up to 20GB. > > > > Then we need some accountability from these prominent figures. Where > > is their feedback on this discussion? > Do you want working kernel threads and SMP or DPT support? I am working feverishly on the SMP and kernel threads stuff, and physically cannot do any more in the day. I do plan to work on the DPT stuff, but I can only do one type of thing at a time... John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 10:53:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15005 for freebsd-stable-outgoing; Tue, 26 May 1998 10:53:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from paleale.cisco.com (paleale.cisco.com [171.69.95.88]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14990; Tue, 26 May 1998 10:53:10 -0700 (PDT) (envelope-from narana@cisco.com) Received: from nkannapp-ss20.cisco.com (nkannapp-ss20.cisco.com [171.69.194.242]) by paleale.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id KAA09899; Tue, 26 May 1998 10:52:40 -0700 (PDT) Received: (narana@localhost) by nkannapp-ss20.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id KAA11764; Tue, 26 May 1998 10:52:42 -0700 (PDT) Date: Tue, 26 May 1998 10:52:42 -0700 (PDT) Message-Id: <199805261752.KAA11764@nkannapp-ss20.cisco.com> From: Narana Kannappan MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-stable@FreeBSD.ORG CC: Narana Kannappan , ache@FreeBSD.ORG Subject: problems with speak-freely X-Mailer: VM 6.22 under 19.15p7 XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hi, I have problems using the package. I'm running 2.2.6, I have a SB64 awe, I am running Luigi's code. Can someone give me any suggestions ? Thanks, -Narana ----------------------- ~% env SPEAKFREE_LWL_TELL SPEAKFREE_LWL_TELL=lwl.fourmilab.ch ~% sfspeaker & [1] 1616 ~% sflwl -hlwl.fourmilab.ch narana@pvs-ms1.csl.sri.com 130.107.4.159:2074 narana@pvs-ms1.csl.sri.com (Narana Kannappan) ~% sfmike pvs-ms1.csl.sri.com Space bar switches talk/pause, Esc or "q" to quit Talk: sfmike: unable to initialise audio. Unable to initialise audio. %~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 11:09:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18241 for freebsd-stable-outgoing; Tue, 26 May 1998 11:09:26 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hcs.harvard.edu (hcs.harvard.edu [140.247.73.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18205 for ; Tue, 26 May 1998 11:09:15 -0700 (PDT) (envelope-from kemiller@hcs.harvard.edu) Received: (from kemiller@localhost) by hcs.harvard.edu (8.8.5/8.8.3) id OAA21502; Tue, 26 May 1998 14:09:06 -0400 (EDT) Message-ID: <19980526140906.30830@hcs.harvard.edu> Date: Tue, 26 May 1998 14:09:06 -0400 From: Kenneth Miller To: freebsd-stable@FreeBSD.ORG Subject: Re: improper shutdown References: <19980525233116.10709@hcs.harvard.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980525233116.10709@hcs.harvard.edu>; from Kenneth Miller on Mon, May 25, 1998 at 11:31:16PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Monday, 05/25/98 at 11:31:16 PM, Kenneth Miller wrote: > > I've had a minor (?) but irritating problem ever since moving to stable > from 2.2.5. When I reboot, the disks don't have their clean flags set > and need fscking. If I shutdown to singer user mode and manually > unmount the disks, and remount / readonly, it's fine. But using the > shutdown program to go all the way doesn't work. I will assume this is > some misconfiguration on my part, but I was a little perplexed that it > began only when I moved to stable. > > Any suggestions or answers appreciated. OK. After a little more poking, it became apparent that what was happening was that certain filesystems were still busy, causing the reboot syscall to give up and halt without unmounting the filesystems. Why, then, would they be busy? All other processes should have been terminated, and no error message appeared indicating anything else. I also noticed that nothing is done with the RB_POWEROFF flag, even though APM support has been in there for a while. Any particular reason that anyone knows of? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 12:54:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07690 for freebsd-stable-outgoing; Tue, 26 May 1998 12:54:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07631; Tue, 26 May 1998 12:54:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00549; Tue, 26 May 1998 11:47:18 -0700 (PDT) Message-Id: <199805261847.LAA00549@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "John S. Dyson" cc: shimon@simon-shapiro.org, mike@smith.net.au, tom@sdf.com, freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT install problem In-reply-to: Your message of "Tue, 26 May 1998 12:39:04 CDT." <199805261739.MAA20179@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 11:47:18 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > > > On 22-May-98 Mike Smith wrote: > > >> > > >> > However, there are a couple of things that you personally (and other > > >> > concerned users) can do to help the situation. > > >> > > > >> > - Contribute commentary (as you have), documentation and source/ > > >> > procedural fixes. Remeber that FreeBSD is a volunteer project - > > >> > your support means that it will continue to improve. > > >> > - Donate a DPT controller to our testing pool so that we can test > > >> > with it. Chances are we can scrape enough disks together in one > > >> > place to meet the 20GB mark if we have one. > > >> > > >> I recently donated TWO DPT controllers and FIVE disk drives. They went > > >> to > > >> two separate FreeBSD prominent figures, but still do not add up to 20GB. > > > > > > Then we need some accountability from these prominent figures. Where > > > is their feedback on this discussion? > > > Do you want working kernel threads and SMP or DPT support? I am working > feverishly on the SMP and kernel threads stuff, and physically cannot do > any more in the day. I just want to know what these people are doing if not answering questions. Guessing and begging users for input is traditional stuff, but if there's a better alternative, I'm all for it. > I do plan to work on the DPT stuff, but I can only do one type of thing > at a time... Sounds reasonable to me. What we need are some underlings for you to boss around doing your grunt work. JD and the moonshine gang? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 13:59:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19302 for freebsd-stable-outgoing; Tue, 26 May 1998 13:59:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19238 for ; Tue, 26 May 1998 13:58:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00933; Tue, 26 May 1998 12:52:47 -0700 (PDT) Message-Id: <199805261952.MAA00933@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Kenneth Miller cc: Mike Smith , freebsd-stable@FreeBSD.ORG Subject: Re: improper shutdown In-reply-to: Your message of "Tue, 26 May 1998 10:00:31 EDT." <19980526100031.47594@hcs.harvard.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 12:52:47 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > On Monday, 05/25/98 at 11:57:35 PM, Mike Smith wrote: > > > > > > I've had a minor (?) but irritating problem ever since moving to stable > > > from 2.2.5. When I reboot, the disks don't have their clean flags set > > > and need fscking. If I shutdown to singer user mode and manually > > > unmount the disks, and remount / readonly, it's fine. But using the > > > shutdown program to go all the way doesn't work. I will assume this is > > > some misconfiguration on my part, but I was a little perplexed that it > > > began only when I moved to stable. > > > > Are you seeing a diagnostic at boot time telling you to update > > /etc/fstab? Have you done so? > > if you're referring to the sd0a vs sd03a thing, that's not it. the only > diagnostic i'm getting is CLEAN BIT NOT SET IN SUPERBLOCK. if you're > referring to anything else, i don't think i've seen it. Sorry then, no ideas. I'm not seeing it on any systems here. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 14:37:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25094 for freebsd-stable-outgoing; Tue, 26 May 1998 14:37:26 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25082; Tue, 26 May 1998 14:37:16 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id PAA00792; Tue, 26 May 1998 15:37:04 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805262137.PAA00792@panzer.plutotech.com> Subject: Re: DPT install problem In-Reply-To: from Simon Shapiro at "May 26, 98 12:58:53 pm" To: shimon@simon-shapiro.org Date: Tue, 26 May 1998 15:37:03 -0600 (MDT) Cc: rzig@verio.net, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, tom@sdf.com, owensc@enc.edu X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Simon Shapiro wrote... > On 22-May-98 Raul Zighelboim wrote: > > As a sidebar; the DOS configuration software can only create arrays with > > up to 1 mbyte interleave. Is this a limitation on the hardware or the > > software ? Is (will there be) a way to create an array with a larger > > interleave (32 megs comes to mind). > > An interleave factor larger than 1MB will be very inefficient: > > a. The SCSI bus will be used (locked) for long periods. This will > cause poor multi-tasking response. > > b. The cache memory will be able to contain very few stripes. > > Also notice that in the context of FreeBSD, anything larger than 64K is > sort of mute, as the O/S limits all SCSI transfers to that size. I do not > know yet how CAM will do, but suspect it to be the same. It will be the same. The 64K limitation is a generic FreeBSD limitation, so CAM won't change it. CAM won't limit it, though. Here at Pluto, we've been running large chunks (> 64K) through CAM and the Adaptec driver by passing physical memory addresses in through the passthrough driver. (and therefore you bypass the whole struct buf thing and physio) If we ever get a buffer chaining (or similar) scheme in place, it'll be possible to do any size I/O without jumping through hoops. > > Thanks, Simon, for a job well done. > > Thanx. I am going to get started on CAM port in the next few days. Good deal. Contact me via private email about getting access to the CAM source repository. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 14:48:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27937 for freebsd-stable-outgoing; Tue, 26 May 1998 14:48:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27760; Tue, 26 May 1998 14:48:03 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id VAA17993; Tue, 26 May 1998 21:48:01 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id XAA29607; Tue, 26 May 1998 23:47:56 +0200 (MET DST) Message-ID: <19980526234755.44290@follo.net> Date: Tue, 26 May 1998 23:47:55 +0200 From: Eivind Eklund To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT install problem References: <199805261739.MAA20179@dyson.iquest.net> <199805261847.LAA00549@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805261847.LAA00549@dingo.cdrom.com>; from Mike Smith on Tue, May 26, 1998 at 11:47:18AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, May 26, 1998 at 11:47:18AM -0700, Mike Smith wrote: > > Do you want working kernel threads and SMP or DPT support? I am working > > feverishly on the SMP and kernel threads stuff, and physically cannot do > > any more in the day. > > I just want to know what these people are doing if not answering > questions. Guessing and begging users for input is traditional stuff, > but if there's a better alternative, I'm all for it. I'm answering all questions I can. I can't answer questions about true 20GB DPT arrays with more than guesses for at the absolute mimimum four more months. Every question you've had I've tried to answer if I could give any information :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 14:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29603 for freebsd-stable-outgoing; Tue, 26 May 1998 14:54:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from apollo.ptway.com (apollo.ptway.com [199.176.148.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29490 for ; Tue, 26 May 1998 14:54:12 -0700 (PDT) (envelope-from haskin@ptway.com) Received: from brianjr (210R1.infinitecom.com [199.176.148.77] (may be forged)) by apollo.ptway.com (8.8.7/8.8.7) with SMTP id QAA13736; Tue, 26 May 1998 16:56:51 -0400 Message-ID: <003901bd88f0$d7250ca0$0b00000a@brianjr.haskin.org> From: "Brian Haskin" To: Cc: "Michael Robinson" Subject: Re: Bug in wd driver Date: Tue, 26 May 1998 17:54:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk -----Original Message----- From: Nate Williams To: Mike Smith Cc: Michael Robinson ; freebsd-stable@FreeBSD.ORG Date: Tuesday, May 26, 1998 12:09 PM Subject: Re: Bug in wd driver >> > >> I wrote a message related to this problem to freebsd-questions >> > >> yesterday, but upon further investigation, I have decided this is >> > >> a bug, not a feature. >> > > >> > >Actually, it's almost certainly a hardware fault. >> > >> > Actually, the bug is that the driver does not recover gracefully from a >> > recoverable hardware fault. It instead goes into an infinite loop, taking >> > significant pieces of the kernel with it. >> >> Actually, an interrupt timeout is not a "recoverable hardware fault". > >Sure it is. You're being silly now Mike, this is indeed a 'bug' in the >driver, but it's probably not one that's going to be fixed unless the >submitter fixes it himself. Fixing it is non-trivial but possible to >do. > >Having a bad spot on a disk shouldn't make the disk *totally* unusable, >as every other 'significant' OS can deal with fine. > >This is also why I was w/out a laptop for 5 months, since our driver >couldn't get past the bad sector on the boot partition when it went bad >and everytime fsck tried to read it it locked up the computer. :( > Nate, I think what Mike is saying is that at least in this case the bad spot doesn't seem to be the real problem. The problem appears to be that the disk firmware is crashing, which is certainly an unrecoverable error. Brian Haskin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 15:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08846 for freebsd-stable-outgoing; Tue, 26 May 1998 15:39:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08760; Tue, 26 May 1998 15:39:07 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01429; Tue, 26 May 1998 14:32:33 -0700 (PDT) Message-Id: <199805262132.OAA01429@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: shimon@simon-shapiro.org cc: Mike Smith , Tom , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT install problem In-reply-to: Your message of "Tue, 26 May 1998 13:06:15 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 14:32:33 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > >> An ajacent problem, is that fsck will fail on such filesystems. > >> The failure mode is fsck -p in /etc/rc. It does not have, by default > >> enough resources to run a large parallel fsck. I added the following to > >> /etc/rc: > > > > You should update the daemon class in /etc/login.conf. Can you verify > > that the current settings there (/usr/src/etc/login.conf) are adequate? > > I am using (as of today, still to be tried): > > # > # Settings used by /etc/rc > # > daemon:\ > :coredumpsize@:\ > :coredumpsize-cur=0:\ > :datasize=infinity:\ > :datasize-cur@:\ > :maxproc=512:\ > :maxproc-cur@:\ > :memoryuse-cur=infinity:\ > :memorylocked-cur=infinity:\ > :openfiles=1024:\ > :openfiles-cur@:\ > :stacksize=infinity:\ > :stacksize-cur@:\ > :tc=default: untried ie. you haven't verified whether this configuration works or fails, correct? > BTW, what is foo@ in this file? from 'man 3 getcap' (whence you are referred from login.conf(5)) When a database is searched for a capability record, the first matching record in the search is returned. When a record is scanned for a capa- bility, the first matching capability is returned; the capability :nameT@: will hide any following definition of a value of type T for name; and the capability :name@: will prevent any following values of name from being seen. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 15:53:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12452 for freebsd-stable-outgoing; Tue, 26 May 1998 15:53:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12398 for ; Tue, 26 May 1998 15:53:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01571; Tue, 26 May 1998 14:46:58 -0700 (PDT) Message-Id: <199805262146.OAA01571@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nate Williams cc: Mike Smith , Michael Robinson , freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-reply-to: Your message of "Tue, 26 May 1998 09:02:19 MDT." <199805261502.JAA05071@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 14:46:58 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > > >> I wrote a message related to this problem to freebsd-questions > > > >> yesterday, but upon further investigation, I have decided this is > > > >> a bug, not a feature. > > > > > > > >Actually, it's almost certainly a hardware fault. > > > > > > Actually, the bug is that the driver does not recover gracefully from a > > > recoverable hardware fault. It instead goes into an infinite loop, taking > > > significant pieces of the kernel with it. > > > > Actually, an interrupt timeout is not a "recoverable hardware fault". > > Sure it is. You're being silly now Mike, this is indeed a 'bug' in the > driver, but it's probably not one that's going to be fixed unless the > submitter fixes it himself. Fixing it is non-trivial but possible to > do. I guess it's a matter of semantics. You're suggesting we should have a workaround, which is fair enough. I'm inclined to think that if your hardware screws that badly you're better off losing it. > Having a bad spot on a disk shouldn't make the disk *totally* unusable, > as every other 'significant' OS can deal with fine. This isn't a "bad spot" in the traditional sense - this is the disk firmware failing. A "bad spot" gives you a recognisable, and recoverable, error. We handle that just fine. What we don't handle are cases where the disk:controller protocol fails. IMHO, the value in handling this case is small - the only times I've seen this reported over the last few years has been with disks that are basically screwed. Note that DOS-derived operating systems will often dump their cookies in a similar fashion under the same circumstances (exact results seem to vary, and I don't have a drive I can test this with anymore, having consigned my last one to the dump before moving). > This is also why I was w/out a laptop for 5 months, since our driver > couldn't get past the bad sector on the boot partition when it went bad > and everytime fsck tried to read it it locked up the computer. :( So don't fsck it; I talked you through solving that problem, and you ignored me. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 15:59:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13998 for freebsd-stable-outgoing; Tue, 26 May 1998 15:59:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13942 for ; Tue, 26 May 1998 15:58:56 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA23813; Tue, 26 May 1998 16:58:45 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA09021; Tue, 26 May 1998 16:58:27 -0600 Date: Tue, 26 May 1998 16:58:27 -0600 Message-Id: <199805262258.QAA09021@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Nate Williams , Michael Robinson , freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-Reply-To: <199805262146.OAA01571@dingo.cdrom.com> References: <199805261502.JAA05071@mt.sri.com> <199805262146.OAA01571@dingo.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > Having a bad spot on a disk shouldn't make the disk *totally* unusable, > > as every other 'significant' OS can deal with fine. > > This isn't a "bad spot" in the traditional sense - this is the disk > firmware failing. No, this is a bad spot on the disk. > A "bad spot" gives you a recognisable, and recoverable, error. Only if the bad spot can be remapped 'magically' behind the scenes, or the spot is 'recoverable. When your bad-sector table is filled, the hard-disk is saying 'I can't read this anymore, so quit trying'. The FreeBSD driver says 'Please, try again', and again, and again, and again... > Note that DOS-derived operating systems will often dump their cookies in > a similar fashion under the same circumstances (exact results seem to > vary, and I don't have a drive I can test this with anymore, having > consigned my last one to the dump before moving). Not in my case. Win95/DOS was able to recognize this and map it out. > > This is also why I was w/out a laptop for 5 months, since our driver > > couldn't get past the bad sector on the boot partition when it went bad > > and everytime fsck tried to read it it locked up the computer. :( > > So don't fsck it; I talked you through solving that problem, and you > ignored me. 8) I couldn't *NOT* fsck it since init was were the bad-blocks was located. (I think it was the inode). All attempts to fix it or workaround it didn't work, so I punted on it. By the time I got DOS to remap it, I gave up on using FreeBSD on it, since I figured it was only a matter of time before another bad-spot showed up and I'd be in the same boat. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 15:59:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14061 for freebsd-stable-outgoing; Tue, 26 May 1998 15:59:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA13961 for ; Tue, 26 May 1998 15:59:01 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1524 invoked by uid 1000); 27 May 1998 00:00:11 -0000 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 In-Reply-To: <199805261847.LAA00549@dingo.cdrom.com> Date: Tue, 26 May 1998 20:00:11 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Smith Subject: Re: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, tom@sdf.com, "John S.Dyson" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 26-May-98 Mike Smith wrote: ... >> Do you want working kernel threads and SMP or DPT support? I am working >> feverishly on the SMP and kernel threads stuff, and physically cannot do >> any more in the day. > > I just want to know what these people are doing if not answering > questions. Guessing and begging users for input is traditional stuff, > but if there's a better alternative, I'm all for it. I will have my home lab up and running in the next few days (week?). Any offer of help in unpacking 200 boxes is welcome. Once this is done, I'll have a bit more in DPT hardware for testing. I only can test large arrays on 3.0, as Sendero is the only really large array I have here. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 16:13:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17278 for freebsd-stable-outgoing; Tue, 26 May 1998 16:13:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17229 for ; Tue, 26 May 1998 16:12:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA01738; Tue, 26 May 1998 15:06:34 -0700 (PDT) Message-Id: <199805262206.PAA01738@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nate Williams cc: Mike Smith , Michael Robinson , freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-reply-to: Your message of "Tue, 26 May 1998 16:58:27 MDT." <199805262258.QAA09021@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 15:06:33 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > > Having a bad spot on a disk shouldn't make the disk *totally* unusable, > > > as every other 'significant' OS can deal with fine. > > > > This isn't a "bad spot" in the traditional sense - this is the disk > > firmware failing. > > No, this is a bad spot on the disk. I'm sorry Nate, but if it was a bad spot the error register would be nonzero. Please check the originally quoted diagnostic for the actual status/error register values. Also note that DRQ would not be set if the timeout had occurred too soon. The drive has failed to deliver an interrupt upon completion. As far as I am able to determine (given no access to the system or other data) this is a disk firmware fault. The most reasonable justification for this is catastrophic failure due to corrupted firmware-level metadata. > > A "bad spot" gives you a recognisable, and recoverable, error. > > Only if the bad spot can be remapped 'magically' behind the scenes, or > the spot is 'recoverable. When your bad-sector table is filled, the > hard-disk is saying 'I can't read this anymore, so quit trying'. The > FreeBSD driver says 'Please, try again', and again, and again, and > again... Actually, it eventually gives up. (Check the source if you don't believe me.) But that's not the error we're seeing here, as you would know if you were familiar with the original report and the interface in question. > > Note that DOS-derived operating systems will often dump their cookies in > > a similar fashion under the same circumstances (exact results seem to > > vary, and I don't have a drive I can test this with anymore, having > > consigned my last one to the dump before moving). > > Not in my case. Win95/DOS was able to recognize this and map it out. We're not talking about your case, in this case. > > > This is also why I was w/out a laptop for 5 months, since our driver > > > couldn't get past the bad sector on the boot partition when it went bad > > > and everytime fsck tried to read it it locked up the computer. :( > > > > So don't fsck it; I talked you through solving that problem, and you > > ignored me. 8) > > I couldn't *NOT* fsck it since init was were the bad-blocks was > located. (I think it was the inode). All attempts to fix it or > workaround it didn't work, so I punted on it. That's the same response : "fixing it is too hard". I suggested another machine, as well as sources for the connectors involved. > By the time I got DOS to remap it, I gave up on using FreeBSD on it, > since I figured it was only a matter of time before another bad-spot > showed up and I'd be in the same boat. Just wait 'till one shows up in one of DOS' critial areas. It's all relative. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 16:32:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19410 for freebsd-stable-outgoing; Tue, 26 May 1998 16:32:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA19276 for ; Tue, 26 May 1998 16:31:44 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1878 invoked by uid 1000); 27 May 1998 00:32:55 -0000 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 In-Reply-To: <199805262132.OAA01429@dingo.cdrom.com> Date: Tue, 26 May 1998 20:32:55 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Smith Subject: Re: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Tom Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 26-May-98 Mike Smith wrote: >> >> An ajacent problem, is that fsck will fail on such filesystems. >> >> The failure mode is fsck -p in /etc/rc. It does not have, by default >> >> enough resources to run a large parallel fsck. I added the following >> >> to >> >> /etc/rc: >> > >> > You should update the daemon class in /etc/login.conf. Can you verify >> > that the current settings there (/usr/src/etc/login.conf) are >> > adequate? >> >> I am using (as of today, still to be tried): >> >> # >> # Settings used by /etc/rc >> # >> daemon:\ >> :coredumpsize@:\ >> :coredumpsize-cur=0:\ >> :datasize=infinity:\ >> :datasize-cur@:\ >> :maxproc=512:\ >> :maxproc-cur@:\ >> :memoryuse-cur=infinity:\ >> :memorylocked-cur=infinity:\ >> :openfiles=1024:\ >> :openfiles-cur@:\ >> :stacksize=infinity:\ >> :stacksize-cur@:\ >> :tc=default: > > untried ie. you haven't verified whether this configuration works or > fails, correct? Seems to work under 3.0-current as of last week. No idea about 2.2 :-( > >> BTW, what is foo@ in this file? > > from 'man 3 getcap' (whence you are referred from login.conf(5)) > > When a database is searched for a capability record, the first > matching > record in the search is returned. When a record is scanned for a > capa- > bility, the first matching capability is returned; the capability > :nameT@: will hide any following definition of a value of type T for > name; and the capability :name@: will prevent any following values > of > name from being seen. Sounds elaborate. An example will help (I am slower than usual today :-) Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 16:33:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19607 for freebsd-stable-outgoing; Tue, 26 May 1998 16:33:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA19553 for ; Tue, 26 May 1998 16:33:29 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1905 invoked by uid 1000); 27 May 1998 00:34:42 -0000 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 In-Reply-To: <199805262137.PAA00792@panzer.plutotech.com> Date: Tue, 26 May 1998 20:34:42 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Kenneth D. Merry" Subject: Re: DPT install problem Cc: owensc@enc.edu, tom@sdf.com, freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, rzig@verio.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 26-May-98 Kenneth D. Merry wrote: > Simon Shapiro wrote... >> On 22-May-98 Raul Zighelboim wrote: >> > As a sidebar; the DOS configuration software can only create arrays >> > with >> > up to 1 mbyte interleave. Is this a limitation on the hardware or the >> > software ? Is (will there be) a way to create an array with a larger >> > interleave (32 megs comes to mind). >> >> An interleave factor larger than 1MB will be very inefficient: >> >> a. The SCSI bus will be used (locked) for long periods. This will >> cause poor multi-tasking response. >> >> b. The cache memory will be able to contain very few stripes. >> >> Also notice that in the context of FreeBSD, anything larger than 64K is >> sort of mute, as the O/S limits all SCSI transfers to that size. I do >> not >> know yet how CAM will do, but suspect it to be the same. > > It will be the same. The 64K limitation is a generic FreeBSD > limitation, so CAM won't change it. CAM won't limit it, though. Here at > Pluto, we've been running large chunks (> 64K) through CAM and the > Adaptec > driver by passing physical memory addresses in through the passthrough > driver. (and therefore you bypass the whole struct buf thing and physio) Ugly :-) We need this type of support in raw devices, though, so userland can pass it in reasonable manner. > If we ever get a buffer chaining (or similar) scheme in place, > it'll be possible to do any size I/O without jumping through hoops. > >> > Thanks, Simon, for a job well done. >> >> Thanx. I am going to get started on CAM port in the next few days. > > Good deal. Contact me via private email about getting access to > the CAM source repository. > > Ken > -- > Kenneth Merry > ken@plutotech.com --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 17:23:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28976 for freebsd-stable-outgoing; Tue, 26 May 1998 17:23:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28840; Tue, 26 May 1998 17:22:50 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA07565; Wed, 27 May 1998 10:22:38 +1000 Date: Wed, 27 May 1998 10:22:38 +1000 From: Bruce Evans Message-Id: <199805270022.KAA07565@godzilla.zeta.org.au> To: ken@plutotech.com, shimon@simon-shapiro.org Subject: Re: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, owensc@enc.edu, rzig@verio.net, tom@sdf.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > It will be the same. The 64K limitation is a generic FreeBSD >limitation, so CAM won't change it. CAM won't limit it, though. Here at Except in theory anyone can recompile the kernel with a higher limit, and the limit is actually 124K for IDE... Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 17:33:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01318 for freebsd-stable-outgoing; Tue, 26 May 1998 17:33:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29783 for ; Tue, 26 May 1998 17:27:22 -0700 (PDT) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.8.5/8.8.5) id IAA10055; Wed, 27 May 1998 08:27:16 +0800 (GMT) Date: Wed, 27 May 1998 08:27:16 +0800 (GMT) From: Michael Robinson Message-Id: <199805270027.IAA10055@public.bta.net.cn> To: mike@smith.net.au Subject: Re: Bug in wd driver Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Mike Smith writes: >Actually, an interrupt timeout is not a "recoverable hardware fault". >This is a basic failure in the driver:controller protocol on the part >of the drive. If this is a basic failure, why does the driver continue to function normally for other processes, and for access to other sectors of the same partition, at the same time it has succumbed to a non-recoverable error? If an interrupt times out, it is the responsibility of the driver to detect the timeout, and return an error to the requesting system call. This did not happen, so I reported a bug. >Disk metadata damage that causes the drive firmware to fail doesn't >strike me as "minor" in any common usage of the term. Minor, in the sense that only seven sectors were affected out of an otherwise perfectly healthy filesystem, and metadata at that. Had bad144 been functional, I could have remapped the sectors, fsck'd, recovered the orphaned files, and been on my merry way. Instead, I stuck with a major partition reallocation project. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 17:44:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00358 for freebsd-stable-outgoing; Tue, 26 May 1998 17:44:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00340 for ; Tue, 26 May 1998 17:44:26 -0700 (PDT) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.8.5/8.8.5) id IAA12575; Wed, 27 May 1998 08:42:55 +0800 (GMT) Date: Wed, 27 May 1998 08:42:55 +0800 (GMT) From: Michael Robinson Message-Id: <199805270042.IAA12575@public.bta.net.cn> To: freebsd-stable@FreeBSD.ORG, haskin@ptway.com Subject: Re: Bug in wd driver Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk "Brian Haskin" writes: >I think what Mike is saying is that at least in this case the bad spot >doesn't seem to be the real problem. The problem appears to be that the disk >firmware is crashing, which is certainly an unrecoverable error. He may be saying this, but, quoting from my original message: 2. After this, the process requesting the I/O will be completely locked, but the disk will continue to make seeking noises continuously until the system is powered off. Other processes are able to access the affected slice/partition ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ (ls, cat, etc.) without any difficulty, as long as they avoid ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the 7 affected sectors. Any process which requires privileged ^^^^^^^^^^^^^^^^^^^^^^^ kernel calls (halt, ps, etc.) will lock immediately and completely. The disk firmware absolutely did not crash. Nor, in fact, did the disk controller, nor even the driver itself. Not even the kernel (mostly). No crashes. A queued I/O request that never timed out, yes. Crash, no. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 17:44:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28976 for freebsd-stable-outgoing; Tue, 26 May 1998 17:23:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28840; Tue, 26 May 1998 17:22:50 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA07565; Wed, 27 May 1998 10:22:38 +1000 Date: Wed, 27 May 1998 10:22:38 +1000 From: Bruce Evans Message-Id: <199805270022.KAA07565@godzilla.zeta.org.au> To: ken@plutotech.com, shimon@simon-shapiro.org Subject: Re: DPT install problem Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org, owensc@enc.edu, rzig@verio.net, tom@sdf.com Sender: owner-freebsd-stable@freebsd.org Precedence: bulk > It will be the same. The 64K limitation is a generic FreeBSD >limitation, so CAM won't change it. CAM won't limit it, though. Here at Except in theory anyone can recompile the kernel with a higher limit, and the limit is actually 124K for IDE... Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 18:07:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01318 for freebsd-stable-outgoing; Tue, 26 May 1998 17:33:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29783 for ; Tue, 26 May 1998 17:27:22 -0700 (PDT) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.8.5/8.8.5) id IAA10055; Wed, 27 May 1998 08:27:16 +0800 (GMT) Date: Wed, 27 May 1998 08:27:16 +0800 (GMT) From: Michael Robinson Message-Id: <199805270027.IAA10055@public.bta.net.cn> To: mike@smith.net.au Subject: Re: Bug in wd driver Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org Precedence: bulk > Mike Smith writes: >Actually, an interrupt timeout is not a "recoverable hardware fault". >This is a basic failure in the driver:controller protocol on the part >of the drive. If this is a basic failure, why does the driver continue to function normally for other processes, and for access to other sectors of the same partition, at the same time it has succumbed to a non-recoverable error? If an interrupt times out, it is the responsibility of the driver to detect the timeout, and return an error to the requesting system call. This did not happen, so I reported a bug. >Disk metadata damage that causes the drive firmware to fail doesn't >strike me as "minor" in any common usage of the term. Minor, in the sense that only seven sectors were affected out of an otherwise perfectly healthy filesystem, and metadata at that. Had bad144 been functional, I could have remapped the sectors, fsck'd, recovered the orphaned files, and been on my merry way. Instead, I stuck with a major partition reallocation project. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 18:09:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05097 for freebsd-stable-outgoing; Tue, 26 May 1998 18:09:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tweetie.online.barbour-index.co.uk (tweetie-pipex.online.barbour-index.co.uk [194.129.192.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04979 for ; Tue, 26 May 1998 18:08:10 -0700 (PDT) (envelope-from scot@poptart.org) Received: from localhost (scot@localhost) by tweetie.online.barbour-index.co.uk (8.8.8/8.8.8) with SMTP id CAA09497 for ; Wed, 27 May 1998 02:08:00 +0100 (BST) (envelope-from scot@poptart.org) X-Authentication-Warning: tweetie.online.barbour-index.co.uk: scot owned process doing -bs Date: Wed, 27 May 1998 02:07:59 +0100 (BST) From: Scot Elliott X-Sender: scot@tweetie.online.barbour-index.co.uk To: stable@FreeBSD.ORG Subject: Changes to /etc/mail/sendmail.cf.additions Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hi all. I recently CVSupped stable and noticed changes to /usr/src/etc/mail/sendmail.cf.additions. I keep this file as an m4-hack so I just copied it over the top of my current one, as I didn't see any new class files added. Mistake, but hey, sendmail rules are pretty over my head to be honest. Anyway - I noticed a few days later that I was refusing mail for domains that I was a secondary MX for... where as I wasn't before. Seems there are some class name changes that didn't make it into the top of the file. My diffs are: --- /etc/mail/sendmail.cf.additions Mon May 25 19:47:35 1998 +++ /etc/mail/sendmail.cf.additions Wed May 27 02:04:35 1998 @@ -1,7 +1,8 @@ # list of hosts and domains for whom we relay mail. # all .forward hosts, domains must be listed in this file. # same for hosts and domains in /etc/aliases -FR-o /etc/sendmail.cR +F{LocalIP}-o /etc/mail/Local-IP +F{RelayTo}-o /etc/mail/Relay-Hosts # database declarations Kdenyip hash -o -a.REJECT /etc/mail/denyip.db Also, I noticed that relaying is allowed by default. Do we think that's a good idea... ie. Seeing as the reason people stick these rules in is to protect against spam, shouldn't anty-relaying be un-commented by default? Cheers. Scot. ----------------------------------------------------------------------------- Scot Elliott (scot@poptart.org) | Work: +44 (0)171 7046777 PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 ----------------------------------------------------------------------------- Public key available by finger at: finger scot@poptart.org or at: http://www.poptart.org/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 18:26:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07596 for freebsd-stable-outgoing; Tue, 26 May 1998 18:26:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07509 for ; Tue, 26 May 1998 18:26:27 -0700 (PDT) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.8.5/8.8.5) id JAA20637; Wed, 27 May 1998 09:26:18 +0800 (GMT) Date: Wed, 27 May 1998 09:26:18 +0800 (GMT) From: Michael Robinson Message-Id: <199805270126.JAA20637@public.bta.net.cn> To: mike@smith.net.au, nate@mt.sri.com Subject: Re: Bug in wd driver Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Mike Smith writes: >I'm sorry Nate, but if it was a bad spot the error register would be >nonzero. Please check the originally quoted diagnostic for the actual >status/error register values. Also note that DRQ would not be set if >the timeout had occurred too soon. This is from the originally quoted diagnostic: wd0: interrupt timeout wd0: status 50 error 1 I am not an expert, but it looks to me like a nonzero error code. >Actually, it eventually gives up. (Check the source if you don't >believe me.) I looked at the source, and it gives up after five errors. Unfortunately, the driver only gets to the second retry before it wedges itself. As for unwedging itself, this seems to be pretty suspicious: -----/usr/src/sys/i386/isa/wd.c----- /* * XXX this loop may never terminate. The code to handle * counting down of retries and eventually failing the i/o * is in wdintr() and we can't get there from here. */ ------------------------------------ In real time, I waited as long as twenty minutes without it giving up. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 18:28:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08074 for freebsd-stable-outgoing; Tue, 26 May 1998 18:28:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08067; Tue, 26 May 1998 18:28:07 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199805270128.SAA08067@hub.freebsd.org> Subject: Re: Changes to /etc/mail/sendmail.cf.additions In-Reply-To: from Scot Elliott at "May 27, 98 02:07:59 am" To: scot@poptart.org (Scot Elliott) Date: Tue, 26 May 1998 18:28:07 -0700 (PDT) Cc: stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Scot Elliott wrote: > Hi all. > > I recently CVSupped stable and noticed changes to > /usr/src/etc/mail/sendmail.cf.additions. I keep this file as an m4-hack > so I just copied it over the top of my current one, as I didn't see any > new class files added. Mistake, but hey, sendmail rules are pretty over > my head to be honest. > > Anyway - I noticed a few days later that I was refusing mail for domains > that I was a secondary MX for... where as I wasn't before. Seems there > are some class name changes that didn't make it into the top of the file. > you are absolutely right about the file declarations being missing. i'll fix that immediately. the anti-relaying rules are commented out by default. to change this would be to break people's existing configurations....i agree that people should relay blindly, but i cant take this step for them. sendmail-8.9 will solve this problem and obsolete sendmail.cf.additions, i expect. please dont blindly grab sendmail.cf.additions and add it in. i try to make it "good for everyone" but any sites have specific sendmail needs which i may not have forseen. jmb > My diffs are: > > --- /etc/mail/sendmail.cf.additions Mon May 25 19:47:35 1998 > +++ /etc/mail/sendmail.cf.additions Wed May 27 02:04:35 1998 > @@ -1,7 +1,8 @@ > # list of hosts and domains for whom we relay mail. > # all .forward hosts, domains must be listed in this file. > # same for hosts and domains in /etc/aliases > -FR-o /etc/sendmail.cR > +F{LocalIP}-o /etc/mail/Local-IP > +F{RelayTo}-o /etc/mail/Relay-Hosts > > # database declarations > Kdenyip hash -o -a.REJECT /etc/mail/denyip.db > > > Also, I noticed that relaying is allowed by default. Do we think that's a > good idea... ie. Seeing as the reason people stick these rules in is to > protect against spam, shouldn't anty-relaying be un-commented by default? > > > Cheers. > > > Scot. > > ----------------------------------------------------------------------------- > Scot Elliott (scot@poptart.org) | Work: +44 (0)171 7046777 > PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 > ----------------------------------------------------------------------------- > Public key available by finger at: finger scot@poptart.org > or at: http://www.poptart.org/pgpkey.html > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 18:31:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08678 for freebsd-stable-outgoing; Tue, 26 May 1998 18:31:21 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from firewall.scitec.com.au (firewall-user@fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08595 for ; Tue, 26 May 1998 18:31:00 -0700 (PDT) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id LAA24398; Wed, 27 May 1998 11:30:48 +1000 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma024380; Wed, 27 May 98 11:30:33 +1000 Received: from hydra.scitec.com.au (hydra.scitec.com.au [203.17.182.101]) by mailhub.scitec.com.au (8.6.12/8.6.9) with ESMTP id LAA09296; Wed, 27 May 1998 11:30:29 +1000 Received: from saruman (saruman.scitec.com.au) by hydra.scitec.com.au with SMTP (1.40.112.8/16.2) id AA239962626; Wed, 27 May 1998 11:30:27 +1000 Message-Id: <06b301bd890f$084498f0$6cb611cb@saruman.scitec.com.au> From: "John Saunders" To: "Michael Robinson" Cc: Subject: Re: Bug in wd driver Date: Wed, 27 May 1998 11:30:26 +1000 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Given the state the disk is in I'd try 2 things (after backing up all data, or as much as possible). First would be to fdisk/format the disk under MSDOS and see how that handles things. If it works then re-install FreeBSD on it. More likely is that MSDOS will suffer a hang which it might or might not recover from. If it does recover you may get a sector not found error. If your not back in business then the next step would be a lowlevel format of the drive. There are 3 outcomes to this. The best is that the drive re-writes all the lowlevel sector information and it comes good. The second is that nothing happens as the drive ignores lowlevel formatting. The third is that the drive proceeds to destroy the servo information rendering the drive totally unusable (until it gets shipped back to the manufacturer who may or may not still have the equipment to fix it depending on drive age). :( Check up with the drive manufacturer (web site maybe) to see if lowlevel formatting is an allowable thing to do by the user. Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 18:52:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12321 for freebsd-stable-outgoing; Tue, 26 May 1998 18:52:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12212 for ; Tue, 26 May 1998 18:52:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA02455; Tue, 26 May 1998 17:46:05 -0700 (PDT) Message-Id: <199805270046.RAA02455@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Robinson cc: mike@smith.net.au, nate@mt.sri.com, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-reply-to: Your message of "Wed, 27 May 1998 09:26:18 +0800." <199805270126.JAA20637@public.bta.net.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 17:46:05 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Mike Smith writes: > >I'm sorry Nate, but if it was a bad spot the error register would be > >nonzero. Please check the originally quoted diagnostic for the actual > >status/error register values. Also note that DRQ would not be set if > >the timeout had occurred too soon. > > This is from the originally quoted diagnostic: > > wd0: interrupt timeout > wd0: status 50 error 1 > > I am not an expert, but it looks to me like a nonzero error code. ERR is not set in the status register. As far as I can tell, ATA4 (T13/ 1153D revision 16, which is the only reference I have to hand) clause 7.15.6.6 says "When the ERR bit is cleared to zero at the end of a command: a) the content of the error register shall be ignored by the host.". There are other conditions that could cause ERR to be cleared, and there are other anomalies. The error report I was referring to when I was studying the reference earlier gave the status as 0x58 and error as zero. This indicates data ready to be transferred and no error. 0x50 indicates no data, ready for a command, and no error. > >Actually, it eventually gives up. (Check the source if you don't > >believe me.) > > I looked at the source, and it gives up after five errors. Unfortunately, > the driver only gets to the second retry before it wedges itself. I was actually referring to Nate's problem here. He threw in a relatively unrelated situation where he had a normal error in a critical disk region. > As for unwedging itself, this seems to be pretty suspicious: Yes. If the disk fails to interrupt, and continues to fail to interrupt, the caller will remain wedged. This is unarguably a defect, and if you believe you have reason to want to rework this, please talk with Soren (sos@freebsd.org) so that you can coordinate your efforts. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 18:58:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13665 for freebsd-stable-outgoing; Tue, 26 May 1998 18:58:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13649 for ; Tue, 26 May 1998 18:58:15 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA02519; Tue, 26 May 1998 17:52:42 -0700 (PDT) Message-Id: <199805270052.RAA02519@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Robinson cc: mike@smith.net.au, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-reply-to: Your message of "Wed, 27 May 1998 08:27:16 +0800." <199805270027.IAA10055@public.bta.net.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 17:52:42 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > Mike Smith writes: > >Actually, an interrupt timeout is not a "recoverable hardware fault". > >This is a basic failure in the driver:controller protocol on the part > >of the drive. > > If this is a basic failure, why does the driver continue to function > normally for other processes, and for access to other sectors of the > same partition, at the same time it has succumbed to a non-recoverable > error? Because the firmware fails soft (perhaps resets, perhaps traps and restarts). > If an interrupt times out, it is the responsibility of the driver to > detect the timeout, and return an error to the requesting system call. > This did not happen, so I reported a bug. I'll grant you that a more graceful failure is called for. bad144 is not really applicable, inasmuch as it's not adequate for many uses. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 19:02:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14685 for freebsd-stable-outgoing; Tue, 26 May 1998 19:02:55 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14494; Tue, 26 May 1998 19:02:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA02549; Tue, 26 May 1998 17:56:23 -0700 (PDT) Message-Id: <199805270056.RAA02549@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: shimon@simon-shapiro.org cc: Mike Smith , freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Tom Subject: cap-format databases (was Re: DPT install problem ) In-reply-to: Your message of "Tue, 26 May 1998 20:32:55 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 17:56:23 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > > >> BTW, what is foo@ in this file? > > > > from 'man 3 getcap' (whence you are referred from login.conf(5)) > > > > When a database is searched for a capability record, the first > > matching > > record in the search is returned. When a record is scanned for a > > capa- > > bility, the first matching capability is returned; the capability > > :nameT@: will hide any following definition of a value of type T for > > name; and the capability :name@: will prevent any following values > > of > > name from being seen. > > Sounds elaborate. An example will help (I am slower than usual today :-) Read the getcap(3) manpage. A simple example: foo: :bar#33:baz: fish: :zog#1:bar@:tc=foo: Retrieving the 'foo' entry gives the capabilities: bar = 33 baz = true Retrieving the 'fish' entry gives the capabilities: zog = 1 baz = true ie. the presence of the 'bar@' entry in 'fish' suppresses the 'bar' capibility when 'foo' is included. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 19:17:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18039 for freebsd-stable-outgoing; Tue, 26 May 1998 19:17:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18008 for ; Tue, 26 May 1998 19:17:23 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id UAA25066; Tue, 26 May 1998 20:16:58 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA09944; Tue, 26 May 1998 20:16:51 -0600 Date: Tue, 26 May 1998 20:16:51 -0600 Message-Id: <199805270216.UAA09944@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Michael Robinson , nate@mt.sri.com, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-Reply-To: <199805270046.RAA02455@dingo.cdrom.com> References: <199805270126.JAA20637@public.bta.net.cn> <199805270046.RAA02455@dingo.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > I looked at the source, and it gives up after five errors. Unfortunately, > > the driver only gets to the second retry before it wedges itself. > > I was actually referring to Nate's problem here. He threw in a > relatively unrelated situation where he had a normal error in a > critical disk region. Except that the driver wedges itself totally like it does with Mike. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 20:12:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00556 for freebsd-stable-outgoing; Tue, 26 May 1998 20:12:46 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fourier.physics.purdue.edu (fourier.physics.purdue.edu [128.210.146.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00528 for ; Tue, 26 May 1998 20:12:38 -0700 (PDT) (envelope-from jonsmith@physics.purdue.edu) Received: from localhost (jonsmith@localhost) by fourier.physics.purdue.edu (8.8.7/8.8.8) with SMTP id WAA16000 for ; Tue, 26 May 1998 22:12:19 -0500 (EST) Date: Tue, 26 May 1998 22:12:19 -0500 (EST) From: Jonathan Smith To: freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-Reply-To: <199805262146.OAA01571@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Well, I received a brand new hard drive that began within a month giving very similar errors. I sent it back in, Seagate graciously replaced the drive. Now I am getting the same error again. I cannot use bsd on this (brand new) drive. As no soloution is presenting itself, that leaves me with two options. Continue using Windows95 (which did do a similar song and dance, only it did NOT tell me error like FreeBSD did ;) or go SCSI. My mom, a friednly Windows user, is happy to get my brand new 3.2 gig hard drive. I had thought Seagate better than to make drives that would get bad spots this easily, till the point it locks up an OS. I guess SCSI is worth the money. j. "Mach was dich wuenschen." Die Unendliche Geschichte, von Michael Ende "Do as you wish." The Neverending Story, by Michael Ende The Microsoft Soloution, "newfs && make reinstall" Jon C. Smith (765)49-45551 PHYS 19c jonsmith@fourier.physics.purdue.edu 1396 Physics Building, West lafayette Purdue Univesity, Indiana 47906-1396 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 22:15:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26088 for freebsd-stable-outgoing; Tue, 26 May 1998 22:15:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wankers.net (root@host-209-214-83-11.ath.bellsouth.net [209.214.83.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25972 for ; Tue, 26 May 1998 22:15:18 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id BAA17871; Wed, 27 May 1998 01:14:26 -0400 (EDT) (envelope-from dex@wankers.net) Date: Wed, 27 May 1998 01:14:25 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: Michael Robinson cc: mike@smith.net.au, nate@mt.sri.com, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-Reply-To: <199805270126.JAA20637@public.bta.net.cn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > wd0: interrupt timeout > wd0: status 50 error 1 this will amuse you: I have a machine that reports that on wd0 and wd1 every single time it boots, recovers gracefully, and proceeds to boot... my $.02 -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 26 22:19:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26968 for freebsd-stable-outgoing; Tue, 26 May 1998 22:19:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wankers.net (root@host-209-214-83-11.ath.bellsouth.net [209.214.83.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26872 for ; Tue, 26 May 1998 22:18:39 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id BAA17900; Wed, 27 May 1998 01:18:23 -0400 (EDT) (envelope-from dex@wankers.net) Date: Wed, 27 May 1998 01:18:18 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: Michael Robinson cc: mike@smith.net.au, nate@mt.sri.com, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-Reply-To: <199805270126.JAA20637@public.bta.net.cn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > wd0: interrupt timeout > wd0: status 50 error 1 Part 2: the truely amusing thing is that this is the same machine that randomly locks up (usually somewhere in the night), and needs a manual reset...this happens between 2 hours and 2 days of uptime...I lost sed, awk, and a few other critical things to unexplained SIGSEGV's, and vanishings (yes...while sed cores, awk literally ceased to exist, eventually). *cough* sounds like something's buggy, somewhere... my $.009 of gasoline tax... Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 00:14:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19453 for freebsd-stable-outgoing; Wed, 27 May 1998 00:14:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19356 for ; Wed, 27 May 1998 00:13:50 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id QAA24615 for ; Wed, 27 May 1998 16:43:40 +0930 (CST) Message-Id: <199805270713.QAA24615@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: stable@FreeBSD.ORG Subject: Linux emulator bogons :( Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 16:43:39 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hi, I just upgraded a system to 2.2.6 (from 2.2.5) and the Linux emulator now causes SIGSEGV's whenever you run a Linux binary (all of them, eg ldconfig). This was a source upgrade (ie check out 2.2-STABLE and make world). I have a slightly older setup done the same way, and the Linux emulator works on it, and when I copy the LKM over and use it instead, that works also. Well, it seems that the working version had v1.9 of linux_sysvec.c, and the bad version had v1.9.2.1 of linux_sysvec.c (that was the only difference) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 07:03:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06191 for freebsd-stable-outgoing; Wed, 27 May 1998 07:03:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06184 for ; Wed, 27 May 1998 07:02:56 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id OAA25344; Wed, 27 May 1998 14:02:44 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA02866; Wed, 27 May 1998 16:02:39 +0200 (MET DST) Message-ID: <19980527160239.63405@follo.net> Date: Wed, 27 May 1998 16:02:39 +0200 From: Eivind Eklund To: "Daniel O'Connor" , stable@FreeBSD.ORG Subject: Re: Linux emulator bogons :( References: <199805270713.QAA24615@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805270713.QAA24615@cain.gsoft.com.au>; from Daniel O'Connor on Wed, May 27, 1998 at 04:43:39PM +0930 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Wed, May 27, 1998 at 04:43:39PM +0930, Daniel O'Connor wrote: > Hi, > I just upgraded a system to 2.2.6 (from 2.2.5) and the Linux emulator now > causes SIGSEGV's whenever you run a Linux binary (all of them, eg ldconfig). The change you describe is not in 2.2.6. > This was a source upgrade (ie check out 2.2-STABLE and make world). > I have a slightly older setup done the same way, and the Linux emulator works > on it, and when I copy the LKM over and use it instead, that works also. > > Well, it seems that the working version had v1.9 of linux_sysvec.c, and the > bad version had v1.9.2.1 of linux_sysvec.c (that was the only difference) This is intended to do trap translation to make e.g. Franz' Allegro Common Lisp work. However, the Linux emulator LKM should not work at _all_ across versions. It sounds like you've gotten your LKMs and your kernel out of sync. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 08:20:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17724 for freebsd-stable-outgoing; Wed, 27 May 1998 08:20:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.double-barrel.be (root@mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17642 for ; Wed, 27 May 1998 08:19:52 -0700 (PDT) (envelope-from mvergall@alpha.double-barrel.be) Received: from alpha.double-barrel.be (mvergall@ns.double-barrel.be [194.7.102.18]) by mail.double-barrel.be (8.8.8/8.8.8) with ESMTP id RAA20348; Wed, 27 May 1998 17:18:49 +0200 Received: from localhost (mvergall@localhost) by alpha.double-barrel.be (8.8.8/8.8.8) with SMTP id RAA07787; Wed, 27 May 1998 17:19:37 +0200 Date: Wed, 27 May 1998 17:19:37 +0200 (MEST) From: "Michael C. Vergallen" To: Dexnation Holodream cc: Michael Robinson , mike@smith.net.au, nate@mt.sri.com, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hi, I've found an other bug in the 2.2.6-stable release : namely : Device wd0: name slot allocation failed (Errno=17) Device rwd0: name slot allocation failed (Errno=17) What does this mean... I have encountered this error ever since I installed the /dev/pt0 driver in the kernel. Also the pt0 driver has still some problems working with the aha0 driver there it gives me a : aha0: Invalid bus phase/sequence. Wierd thing is that they work but still it wories me. Regards, Michael --- Michael C. Vergallen A.k.A. Mad Mike, Sportstraat 28 http://www.double-barrel.be/mvergall/ B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ Belgium tel : 32-9-2227764 Fax : 32-9-2224976 On Wed, 27 May 1998, Dexnation Holodream wrote: > > wd0: interrupt timeout > > wd0: status 50 error 1 > > this will amuse you: > > I have a machine that reports that on wd0 and wd1 every single time it > boots, recovers gracefully, and proceeds to boot... > > my $.02 > > -Jon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 08:40:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23436 for freebsd-stable-outgoing; Wed, 27 May 1998 08:40:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA22839 for ; Wed, 27 May 1998 08:38:38 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 21913 invoked by uid 1000); 27 May 1998 16:39:56 -0000 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 In-Reply-To: <199805270022.KAA07565@godzilla.zeta.org.au> Date: Wed, 27 May 1998 12:39:56 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Bruce Evans Subject: Re: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, owensc@enc.edu, rzig@verio.net, tom@sdf.com, ken@plutotech.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 27-May-98 Bruce Evans wrote: >> It will be the same. The 64K limitation is a generic FreeBSD >>limitation, so CAM won't change it. CAM won't limit it, though. Here at > > Except in theory anyone can recompile the kernel with a higher limit, > and the limit is actually 124K for IDE... I am not so sure this is really a good thing to do. Except as necessary for particular applications. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 11:31:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27470 for freebsd-stable-outgoing; Wed, 27 May 1998 11:31:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27444; Wed, 27 May 1998 11:31:24 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id LAA11461; Wed, 27 May 1998 11:29:22 -0700 (MST) From: "Chad R. Larson" Message-Id: <199805271829.LAA11461@freebie.dcfinc.com> Subject: Re: DPT install problem To: bde@zeta.org.au (Bruce Evans) Date: Wed, 27 May 1998 11:29:21 -0700 (MST) Cc: ken@plutotech.com, shimon@simon-shapiro.org, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, owensc@enc.edu, rzig@verio.net, tom@sdf.com In-Reply-To: <199805270022.KAA07565@godzilla.zeta.org.au> from Bruce Evans at "May 27, 98 10:22:38 am" Reply-to: chad@dcfinc.com 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-freebsd-stable@FreeBSD.ORG Precedence: bulk > It will be the same. The 64K limitation is a generic FreeBSD > limitation, so CAM won't change it. CAM won't limit it, though. I feel like I walked into the middle of a conversation. What, exactly, is CAM? Why would I be interested in it? -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 11:38:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28639 for freebsd-stable-outgoing; Wed, 27 May 1998 11:38:37 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA28623; Wed, 27 May 1998 11:38:16 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA24460; Wed, 27 May 1998 18:57:03 +0200 From: Luigi Rizzo Message-Id: <199805271657.SAA24460@labinfo.iet.unipi.it> Subject: Re: problems with speak-freely To: narana@cisco.com (Narana Kannappan) Date: Wed, 27 May 1998 18:57:02 +0200 (MET DST) Cc: freebsd-stable@FreeBSD.ORG, narana@cisco.com, ache@FreeBSD.ORG In-Reply-To: <199805261752.KAA11764@nkannapp-ss20.cisco.com> from "Narana Kannappan" at May 26, 98 10:52:23 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Hi, > I have problems using the package. I'm running 2.2.6, I have a > SB64 awe, I am running Luigi's code. > > Can someone give me any suggestions ? the code is almost untested. I am pretty sure you have to patch the audio module in speak freely to make it work right. obviously if you get some good result please send back your patches :) cheers luigi > > Thanks, > -Narana > > ----------------------- > ~% env SPEAKFREE_LWL_TELL > SPEAKFREE_LWL_TELL=lwl.fourmilab.ch > ~% sfspeaker & > [1] 1616 > ~% sflwl -hlwl.fourmilab.ch narana@pvs-ms1.csl.sri.com > 130.107.4.159:2074 narana@pvs-ms1.csl.sri.com (Narana Kannappan) > ~% sfmike pvs-ms1.csl.sri.com > Space bar switches talk/pause, Esc or "q" to quit > Talk: sfmike: unable to initialise audio. > Unable to initialise audio. > %~ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 11:53:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01625 for freebsd-stable-outgoing; Wed, 27 May 1998 11:53:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gw.jmrodgers.com (gw.jmrodgers.com [205.247.224.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01574; Wed, 27 May 1998 11:52:49 -0700 (PDT) (envelope-from meuston@jmrodgers.com) Received: from max.jmrodgers.com (max.jmrodgers.com [205.247.224.209]) by gw.jmrodgers.com (8.8.8/8.8.8) with SMTP id OAA04153; Wed, 27 May 1998 14:51:41 -0400 (EDT) (envelope-from meuston@jmrodgers.com) Received: by localhost with Microsoft MAPI; Wed, 27 May 1998 14:51:40 -0400 Message-ID: <01BD897E.F511A1E0.meuston@jmrodgers.com> From: Max Euston To: "'chad@dcfinc.com'" Cc: "freebsd-scsi@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: RE: DPT install problem Date: Wed, 27 May 1998 14:51:37 -0400 Organization: J.M. Rodgers Co., Inc. X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Wednesday, May 27, 1998 2:29 PM, Chad R. Larson [SMTP:chad@freebie.dcfinc.com] wrote: > I feel like I walked into the middle of a conversation. What, exactly, > is CAM? Why would I be interested in it? See: ftp://ftp.freebsd.org/pub/FreeBSD/cam/README Max --- Max Euston To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 12:14:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06293 for freebsd-stable-outgoing; Wed, 27 May 1998 12:14:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06269; Wed, 27 May 1998 12:14:16 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id NAA05934; Wed, 27 May 1998 13:13:34 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805271913.NAA05934@panzer.plutotech.com> Subject: Re: DPT install problem In-Reply-To: <199805271829.LAA11461@freebie.dcfinc.com> from "Chad R. Larson" at "May 27, 98 11:29:21 am" To: chad@dcfinc.com Date: Wed, 27 May 1998 13:13:34 -0600 (MDT) Cc: bde@zeta.org.au, ken@plutotech.com, shimon@simon-shapiro.org, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, owensc@enc.edu, rzig@verio.net, tom@sdf.com X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Chad R. Larson wrote... > > It will be the same. The 64K limitation is a generic FreeBSD > > limitation, so CAM won't change it. CAM won't limit it, though. > > I feel like I walked into the middle of a conversation. What, exactly, > is CAM? Why would I be interested in it? See: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/README or ftp://ftp.kdm.org/pub/FreeBSD/cam/README Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 12:20:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07716 for freebsd-stable-outgoing; Wed, 27 May 1998 12:20:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07539; Wed, 27 May 1998 12:19:46 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id TAA07000; Wed, 27 May 1998 19:19:43 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA05352; Wed, 27 May 1998 21:19:36 +0200 (MET DST) Message-ID: <19980527211935.63164@follo.net> Date: Wed, 27 May 1998 21:19:35 +0200 From: Eivind Eklund To: chad@dcfinc.com Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: What CAM is (was Re: DPT install problem) References: <199805270022.KAA07565@godzilla.zeta.org.au> <199805271829.LAA11461@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805271829.LAA11461@freebie.dcfinc.com>; from Chad R. Larson on Wed, May 27, 1998 at 11:29:21AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Wed, May 27, 1998 at 11:29:21AM -0700, Chad R. Larson wrote: > > It will be the same. The 64K limitation is a generic FreeBSD > > limitation, so CAM won't change it. CAM won't limit it, though. > > I feel like I walked into the middle of a conversation. What, exactly, > is CAM? Why would I be interested in it? CAM is the new disk subsystem, being implemented to follow the CAM specification. This system is used by Digital Unix at least, but I don't remember/know if that was where it originated. An API specification and guideline to writing CAM-based drivers is at http://www.partner.digital.com/www-swdev/pages/Home/TECH/documents/Digital_UNIX/V4.0/AA-PS3GD-TET1_html/TOC.html Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 12:33:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10344 for freebsd-stable-outgoing; Wed, 27 May 1998 12:33:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dart.sr.se (dart.SR.SE [193.12.91.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10259 for ; Wed, 27 May 1998 12:32:51 -0700 (PDT) (envelope-from gunnar@pluto.sr.se) Received: (from smap@localhost) by dart.sr.se (8.8.2/8.7.3) id VAA05413 for ; Wed, 27 May 1998 21:32:44 +0200 (MET DST) Received: from unknown(134.25.188.196) by dart.sr.se via smap (V1.3) id sma005407; Wed May 27 21:32:43 1998 Received: (from gunnar@localhost) by pluto.sr.se (8.8.8/8.8.7) id VAA17607; Wed, 27 May 1998 21:32:43 +0200 (CEST) (envelope-from gunnar) Message-ID: <19980527213242.16768@sr.se> Date: Wed, 27 May 1998 21:32:42 +0200 From: Gunnar Flygt To: freebsd-stable@FreeBSD.ORG Subject: Getting source Reply-To: flygt@sr.se Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk My FreeBSD 2.2.6 is placed behind a fire wall, and when using ports I set the environment variables FTP_PROXY and FTP_PASSWORD. Will this work for cvsup also? -- regards, Gunnar email: flygt@sr.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 12:46:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12634 for freebsd-stable-outgoing; Wed, 27 May 1998 12:46:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA12439 for ; Wed, 27 May 1998 12:45:57 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 4887 invoked by uid 1000); 27 May 1998 20:47:16 -0000 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 In-Reply-To: <199805271829.LAA11461@freebie.dcfinc.com> Date: Wed, 27 May 1998 16:47:16 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: chad@dcfinc.com Subject: Re: DPT install problem Cc: tom@sdf.com, rzig@verio.net, owensc@enc.edu, freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, ken@plutotech.com, (Bruce Evans) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 27-May-98 Chad R. Larson wrote: >> It will be the same. The 64K limitation is a generic FreeBSD >> limitation, so CAM won't change it. CAM won't limit it, though. > > I feel like I walked into the middle of a conversation. What, exactly, > is CAM? Why would I be interested in it? Like I say to my kids ``If you do not know, you do not need to know... ;-)'' Now seriously, from my perspective (Justin and others wrote and support it): It is a new, replacement kernel layer code that sits between the kernel lowest I/O abstraction layer and SCSI device drivers. It implements this layer according to some SCSI ANSI specifications as to how such layers should be written. If you are outside kernel internals, you should not care, except that it is totally incompatible with the existing way FreeBSD does the SCSI interfacing. This means that someone has to re-write the drivers so they work again. Quoted advantages to this move are many and best explained by those who wrote this code. The current DPT driver is not conpatible with this layer and will not be for several weeks to come. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 13:11:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17305 for freebsd-stable-outgoing; Wed, 27 May 1998 13:11:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17260 for ; Wed, 27 May 1998 13:11:30 -0700 (PDT) (envelope-from kline@tera.tera.com) Received: from athena.tera.com (athena.tera.com [207.224.230.127]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id MAA27050; Wed, 27 May 1998 12:03:47 -0700 (PDT) From: Gary Kline Received: (from kline@localhost) by athena.tera.com (8.7.5/8.7.3) id MAA27071; Wed, 27 May 1998 12:03:46 -0700 (PDT) Message-Id: <199805271903.MAA27071@athena.tera.com> Subject: Re: improper shutdown In-Reply-To: <199805261952.MAA00933@dingo.cdrom.com> from Mike Smith at "May 26, 98 12:52:47 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 27 May 1998 12:03:45 -0700 (PDT) Cc: kemiller@hcs.harvard.edu, mike@smith.net.au, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL23 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk According to Mike Smith: > > On Monday, 05/25/98 at 11:57:35 PM, Mike Smith wrote: > > > > > > > > I've had a minor (?) but irritating problem ever since moving to stable > > > > from 2.2.5. When I reboot, the disks don't have their clean flags set > > > > and need fscking. If I shutdown to singer user mode and manually > > > > unmount the disks, and remount / readonly, it's fine. But using the > > > > shutdown program to go all the way doesn't work. I will assume this is > > > > some misconfiguration on my part, but I was a little perplexed that it > > > > began only when I moved to stable. > > > > > > Are you seeing a diagnostic at boot time telling you to update > > > /etc/fstab? Have you done so? > > > > if you're referring to the sd0a vs sd03a thing, that's not it. the only > > diagnostic i'm getting is CLEAN BIT NOT SET IN SUPERBLOCK. if you're > > referring to anything else, i don't think i've seen it. > > Sorry then, no ideas. I'm not seeing it on any systems here. I had similar problems with my 10GB 2.2.5 6x86 box. The solution was to write a simple script which fsck'd my three SCSI drives twice; then called shutdown. It's been .LT. a week since I've upgraded to 2.2.6 but so far I haven't seen the same problem. If I didn't know better, I'd guess it was a problem with the ordering of /filesystems in fstab. But what was usually ``UNCLEAN'' was /home. So... Hoping that it was one of those mysterious bugs. gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 13:42:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24784 for freebsd-stable-outgoing; Wed, 27 May 1998 13:42:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from leo.asahi-net.or.jp (leo.asahi-net.or.jp [202.224.39.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24753 for ; Wed, 27 May 1998 13:42:37 -0700 (PDT) (envelope-from tfuruya@dilemma.tf.or.jp@ppp129167.asahi-net.or.jp) Received: from dilemma.tf.or.jp (ppp129167.asahi-net.or.jp [202.213.129.167]) by leo.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id FAA18825; Thu, 28 May 1998 05:42:21 +0900 (JST) Received: from dilemma.tf.or.jp (localhost [127.0.0.1]) by dilemma.tf.or.jp (8.8.8/3.6W-CF3.6W-dilemma-tf.or.jp-9805) with ESMTP id FAA17668; Thu, 28 May 1998 05:45:12 +0900 (JST) Message-Id: <199805272045.FAA17668@dilemma.tf.or.jp> To: robinson@public.bta.net.cn Cc: freebsd-stable@FreeBSD.ORG Cc: Tetsuro FURUYA Subject: Re: Bug in wd driver From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Tue, 26 May 1998 11:42:26 +0800 (GMT)" References: <199805260342.LAA02975@public.bta.net.cn> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg="pgp-md5"; boundary="--Security_Multipart(Thu_May_28_05:44:51_1998)--" Date: Thu, 28 May 1998 05:45:07 +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Security_Multipart(Thu_May_28_05:44:51_1998)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit In Message-ID: <199805260342.LAA02975@public.bta.net.cn> Michael Robinson wrote: >I have a Tecra 510CDT (running 2.2.6-RELEASE) that suffered a >corrupted disk when the battery power failed as it was trying to >halt. > > 1. Any I/O access to the affected sectors will cause the following > message: > > wd0: interrupt timeout > wd0: status 58 error 0 > > followed by seeking noises, and the following message: > > wd0: interrupt timeout > wd0: status 50 error 1 > > 2. After this, the process requesting the I/O will be completely > locked, but the disk will continue to make seeking noises > continuously until the system is powered off. > Other processes are able to access the affected slice/partition > (ls, cat, etc.) without any difficulty, as long as they avoid > the 7 affected sectors. Any process which requires privileged > kernel calls (halt, ps, etc.) will lock immediately and > completely. > > 3. Other than the two messages above, wd produces no error messages. > > 4. Hard reset is the only way to recover. > > I tried to work around this problem with bad144, but rapidly discovered > that bad144 is something of a bad joke in FreeBSD. Does anyone have > any recommendations for how to fix the wd driver or otherwise recover > from this fault? > > -Michael Robinson I have been encountered at the same defaults in using Panasonic AL-N1, and FreeBSD-2.2.2. And bad144 was hangupped. But I have found out how to manipulate bad144, or fsck , or badsect. My kernel has kernel-debugger installed in it. So, listening to the hamming sound of wd0 drive, and when wd drive is hangupped, invoke kernel-debugger by typing ESC-ctrl-alt keys. A while after stopping of disk access, type 'c' or 'continue', and go back to bad144 or fsck. Several attempts may complete the identification of bad clusters. As for my machine, this was worked. ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 E-Mail: ht5t-fry@asahi-net.or.jp tfu@ff.iij4u.or.jp pgp-fingerprint: pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= ----Security_Multipart(Thu_May_28_05:44:51_1998)-- Content-Type: Application/Pgp-Signature Content-Transfer-Encoding: 7bit -----BEGIN PGP MESSAGE----- Version: 2.6.3i iQCVAwUANWx7STzkiNBZ20qpAQGQmAQAhO7577gPnGTy+aIO1g4af4h/aF0lOIzT uftJOMz0YM5BhcyeL+fwqxFa6ZVaZeYfnoixHHWJW6e55rHVhoLCfkPxRD/8Ns/a TSR7oSY0FAXkqxnwjqVkcE4gAVygH9Ap9Z2hPf89CT+VqbEN+GiXiSihaUWkuN2g cxCw1o8sEd8= =O57U -----END PGP MESSAGE----- ----Security_Multipart(Thu_May_28_05:44:51_1998)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 14:07:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00680 for freebsd-stable-outgoing; Wed, 27 May 1998 14:07:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from versa.eng.comsat.com (versa.eng.comsat.com [134.133.169.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00533 for ; Wed, 27 May 1998 14:06:45 -0700 (PDT) (envelope-from marc@versa.eng.comsat.com) Received: (from marc@localhost) by versa.eng.comsat.com (8.8.8/8.7.3) id SAA03577 for freebsd-stable@freebsd.org; Wed, 27 May 1998 18:05:59 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 27 May 1998 17:54:09 -0400 (EDT) Organization: Comsat Mobile Communications From: Marc Giannoni To: freebsd-stable@FreeBSD.ORG Subject: Kernel building problems Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: Suddenly, I'm unable to build a kernel! <(*GHASP*)> ... [{the horror}] I recently ran 'cvsup' with tag=RELENG_2_2. Now it looks like I may need the new CAM code. (Prior to posting, I tested a kernel config file which has been know to compile OK!) ============================= cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Ws trict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../. . -I../../../include -DNDGBPORTS=32 -DBROKEN_KEYBOARD_RESET -DFAILSAFE -DCOMPAT_ 43 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL -c vers.c loading kernel isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment *** Error code 1 Stop. ============================= I searched 'everywhere' for the declaration of 'isa_devtab_cam' but it didn't appear to be delcared anywhere. ============================= orca# find /usr/src/sys -name \*.\[ch\] -exec grep isa_devtab_cam {} \; -print for (tmpdvp = isa_devtab_cam; tmpdvp->id_driver; tmpdvp++) { for (dvp = isa_devtab_cam; dvp->id_driver; dvp++) for (dvp = isa_devtab_cam; dvp->id_driver; dvp++) for (dvp = isa_devtab_cam; dvp->id_driver; dvp++) /usr/src/sys/i386/isa/isa.c extern struct isa_device isa_devtab_cam[]; /usr/src/sys/i386/isa/isa_device.h for (tmpdvp = isa_devtab_cam; tmpdvp->id_driver; tmpdvp++) { for (dvp = isa_devtab_cam; dvp->id_driver; dvp++) for (dvp = isa_devtab_cam; dvp->id_driver; dvp++) for (dvp = isa_devtab_cam; dvp->id_driver; dvp++) /usr/src/sys/pc98/pc98/pc98.c orca# ============================= Hmmm... (I love X cut-buffers) Do I need the CAM patches? -OR- Is this something else? (and I'm and idiot!) Marc Giannoni Software Engineer Comsat Mobile Communications To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 14:18:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03301 for freebsd-stable-outgoing; Wed, 27 May 1998 14:18:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.mauswerks.net (root@ns.mauswerks.com [204.152.96.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03212; Wed, 27 May 1998 14:18:31 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@[209.54.254.2]) by ns.mauswerks.net (8.8.0/8.6.9) with ESMTP id OAA14725; Wed, 27 May 1998 14:20:17 -0700 Received: (from mjacob@localhost) by feral.com (8.8.6/8.8.6) id OAA12696; Wed, 27 May 1998 14:18:17 -0700 Date: Wed, 27 May 1998 14:18:17 -0700 From: Matthew Jacob Message-Id: <199805272118.OAA12696@feral.com> To: chad@dcfinc.com, eivind@yes.no Subject: Re: What CAM is (was Re: DPT install problem) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try also: http://www.symbios.com/x3t10/io/t10/drafts/cam/cam-r12b.pdf for the 'close to' formal ANSI specification. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 14:38:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07761 for freebsd-stable-outgoing; Wed, 27 May 1998 14:38:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07668 for ; Wed, 27 May 1998 14:37:30 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id VAA11676; Wed, 27 May 1998 21:37:19 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id XAA07324; Wed, 27 May 1998 23:37:08 +0200 (MET DST) Message-ID: <19980527233707.28932@follo.net> Date: Wed, 27 May 1998 23:37:07 +0200 From: Eivind Eklund To: flygt@sr.se, freebsd-stable@FreeBSD.ORG Subject: Re: Getting source References: <19980527213242.16768@sr.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980527213242.16768@sr.se>; from Gunnar Flygt on Wed, May 27, 1998 at 09:32:42PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 27, 1998 at 09:32:42PM +0200, Gunnar Flygt wrote: > My FreeBSD 2.2.6 is placed behind a fire wall, and when using ports I set the > environment variables FTP_PROXY and FTP_PASSWORD. Will this work for cvsup > also? No. If you're behind a pure proxy firewall (limited number of services) you'll probably have to change to using CTM to get the source. If you're just behind a filter, you can do by using the passive mode for cvsup - see the man page for details. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 15:07:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13023 for freebsd-stable-outgoing; Wed, 27 May 1998 15:07:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12955 for ; Wed, 27 May 1998 15:06:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01902; Wed, 27 May 1998 14:01:47 -0700 (PDT) Message-Id: <199805272101.OAA01902@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tetsuro FURUYA cc: robinson@public.bta.net.cn, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-reply-to: Your message of "Thu, 28 May 1998 05:45:07 +0900." <199805272045.FAA17668@dilemma.tf.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 14:01:47 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My kernel has kernel-debugger installed in it. > So, listening to the hamming sound of wd0 drive, and when wd drive > is hangupped, invoke kernel-debugger by typing ESC-ctrl-alt keys. > A while after stopping of disk access, type 'c' or 'continue', > and go back to bad144 or fsck. > Several attempts may complete the identification of bad clusters. > As for my machine, this was worked. This would tend to imply that the timeout value is too short. Can you try increasing the timeout counter and provoking your disk? In sys/i386/isa/wd.c, in this section: /* * Schedule wdtimeout() to wake up after a few seconds. Retrying * unmarked bad blocks can take 3 seconds! Then it is not good that * we retry 5 times. * * On the first try, we give it 10 seconds, for drives that may need * to spin up. * * XXX wdtimeout() doesn't increment the error count so we may loop * forever. More seriously, the loop isn't forever but causes a * crash. * * TODO fix b_resid bug elsewhere (fd.c....). Fix short but positive * counts being discarded after there is an error (in physio I * think). Discarding them would be OK if the (special) file offset * was not advanced. */ if (wdtab[ctrlr].b_errcnt == 0) du->dk_timeout = 1 + 10; else du->dk_timeout = 1 + 3; Increase the 10 and 3 values (first and subsequent timeouts). Try raising them lots, then come down slowly. Also, what are the status and error values that you see in the "interrupt timeout" messages? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 15:49:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24132 for freebsd-stable-outgoing; Wed, 27 May 1998 15:49:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23850 for ; Wed, 27 May 1998 15:47:27 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id XAA27141; Wed, 27 May 1998 23:40:40 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199805272240.XAA27141@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Lutz Albers cc: Brian Somers , freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 ppp breaks compatability with T-Online ppp In-reply-to: Your message of "Mon, 18 May 1998 07:46:54 +0200." <355FCB4E.24D58FC9@muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 23:40:39 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops - this got lost in my piles of email :-( Sorry. Can you remove the ``set ifaddr 0 0'' and see if things get better ? Thanks. > Brian Somers wrote: > > > I just upgraded my server from 2.2.5 to 2.2.6. After this upgrade ppp > > > (user level) is no longer able to connect to the german ISP T-Online. > > > The 2.2.5 version worked just fine (I have recompiled the version from > > > the 2.2.5 sources and it works again). Here is the output from ppp.log: > > [.....] > > > If someone wants more info's, then just contact. > > > > I think we need to see the LCP and IPCP logs too. This looks like > > failed negotiation :-/ > > No problem, here it comes: > > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: default: set timeout > 70 > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: default: set server > 3000 > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: default: set dial > ABORT NO\sB-CHANNEL ABORT BUSY ABORT NO\sCARRIER ABORT NO\sDIALTONE > TIMEOUT 10 "" AT&B54\\P3 OK-AT-OK \dATD\T TIMEOUT 40 CONNECT > May 18 07:43:06 morranon ppp.2.2.6[5188]: Phase: Using interface: tun0 > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set phone > 0191011 > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: deny chap > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: accept pap > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set authname > ***** > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set authkey > ******** > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set ifaddr 0 0 > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set afilter 0 > deny icmp > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set afilter 1 > deny udp src eq 53 > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set afilter 2 > deny udp dst eq 53 > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set afilter 3 > deny udp src eq 520 > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set afilter 4 > deny udp dst eq 520 > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set afilter 5 > permit 0/0 0/0 > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set dfilter 0 > deny icmp > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set dfilter 1 > deny tcp src eq 25 > May 18 07:43:06 morranon ppp.2.2.6[5188]: Command: tol: set dfilter 2 > deny tcp dst eq 25 > May 18 07:43:07 morranon ppp.2.2.6[5188]: Command: tol: set dfilter 3 > permit 0/0 0/0 > May 18 07:43:07 morranon ppp.2.2.6[5188]: Phase: PPP Started. > May 18 07:43:08 morranon ppp.2.2.6[5188]: Command: dial > May 18 07:43:09 morranon ppp.2.2.6[5188]: Phase: Connected! > May 18 07:43:09 morranon ppp.2.2.6[5188]: Connect: AT&B54\P3^M^M > May 18 07:43:09 morranon ppp.2.2.6[5188]: Connect: OK > May 18 07:43:11 morranon ppp.2.2.6[5188]: Phase: Phone: 0191011 > May 18 07:43:11 morranon ppp.2.2.6[5188]: Connect: ^M > May 18 07:43:13 morranon ppp.2.2.6[5188]: Connect: ATD0191011^M^M > May 18 07:43:13 morranon ppp.2.2.6[5188]: Connect: CONNECT > May 18 07:43:13 morranon ppp.2.2.6[5188]: LCP: State change Initial --> > Closed > May 18 07:43:13 morranon ppp.2.2.6[5188]: LCP: State change Closed --> > Stopped > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: LcpSendConfigReq > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: ACFCOMP[2] > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: PROTOCOMP[2] > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: ACCMAP[6] 0x00000000 > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: MRU[4] 1500 > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: MAGICNUM[6] 0x6e3a18f9 > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: State change Stopped --> > Req-Sent > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: Received Configure > Request (1) state = Req-Sent (6) > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: MRU[4] 1524 > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: AUTHPROTO[4] 0xc023 > (PAP) > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: MULTIED[9] > 0300c07b6bee4f > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: SendConfigRej(Req-Sent) > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: MULTIED[9] > 0300c07b6bee4f > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: Received Configure Reject > (1) state = Req-Sent (6) > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: RecvConfigRej. > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: ACFCOMP[2] > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: PROTOCOMP[2] > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: LcpSendConfigReq > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: ACCMAP[6] 0x00000000 > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: MRU[4] 1500 > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: MAGICNUM[6] 0x6e3a18f9 > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: Received Configure > Request (2) state = Req-Sent (6) > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: MRU[4] 1524 > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: AUTHPROTO[4] 0xc023 > (PAP) > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: SendConfigAck(Req-Sent) > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: MRU[4] 1524 > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: AUTHPROTO[4] 0xc023 > (PAP) > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: State change Req-Sent --> > Ack-Sent > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: Received Configure Ack > (2) state = Ack-Sent (8) > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: State change Ack-Sent --> > Opened > May 18 07:43:14 morranon ppp.2.2.6[5188]: LCP: LcpLayerUp > May 18 07:43:14 morranon ppp.2.2.6[5188]: Phase: NewPhase: Authenticate > May 18 07:43:14 morranon ppp.2.2.6[5188]: Phase: his = PAP, mine = none > May 18 07:43:14 morranon ppp.2.2.6[5188]: Phase: PAP: > 00011761267008993940363#1 > May 18 07:43:15 morranon ppp.2.2.6[5188]: Phase: PapInput: ACK > May 18 07:43:15 morranon ppp.2.2.6[5188]: Phase: Received PAP_ACK () > May 18 07:43:15 morranon ppp.2.2.6[5188]: Phase: NewPhase: Network > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: State change Initial --> > Closed > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPCP Up event!! > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IpcpSendConfigReq > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] 0.0.0.0 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: COMPPROTO[6] 16 VJ > slots with slot compres > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: State change Closed --> > Req-Sent > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Configure > Request (1) state = Req-Sent (6) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: COMPPROTO[6] 16 VJ > slots with slot compression > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] > 193.158.131.193 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: SendConfigNak(Req-Sent) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] 0.0.0.0 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Configure Nak > (1) state = Req-Sent (6) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] > 193.159.108.3 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] changing > address: 0.0.0.0 --> 193.159.108.3 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IpcpSendConfigReq > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] 193.159.108.3 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: COMPPROTO[6] 16 VJ > slots with slot compres > May 18 07:43:15 morranon ppp.2.2.6[5188]: LCP: Received Protocol Reject > (3) state = Opened (9) > May 18 07:43:15 morranon ppp.2.2.6[5188]: LCP: -- Protocol (80fd) was > rejected. > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Configure > Request (1) state = Req-Sent (6) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: COMPPROTO[6] 16 VJ > slots with slot compression > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] > 193.158.131.193 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: SendConfigNak(Req-Sent) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] 0.0.0.0 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Configure Ack > (2) state = Req-Sent (6) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: State change Req-Sent > --> Ack-Rcvd > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Configure > Request (1) state = Ack-Rcvd (7) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: COMPPROTO[6] 16 VJ > slots with slot compression > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] > 193.158.131.193 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: SendConfigNak(Ack-Rcvd) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] 0.0.0.0 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Configure > Request (1) state = Ack-Rcvd (7) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: COMPPROTO[6] 16 VJ > slots with slot compression > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] > 193.158.131.193 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: SendConfigNak(Ack-Rcvd) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] 0.0.0.0 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Configure > Request (1) state = Ack-Rcvd (7) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: COMPPROTO[6] 16 VJ > slots with slot compression > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] > 193.158.131.193 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: SendConfigNak(Ack-Rcvd) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] 0.0.0.0 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Configure > Request (1) state = Ack-Rcvd (7) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: COMPPROTO[6] 16 VJ > slots with slot compression > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] > 193.158.131.193 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: SendConfigNak(Ack-Rcvd) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] 0.0.0.0 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Configure > Request (1) state = Ack-Rcvd (7) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: COMPPROTO[6] 16 VJ > slots with slot compression > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] > 193.158.131.193 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: SendConfigNak(Ack-Rcvd) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] 0.0.0.0 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Configure > Request (1) state = Ack-Rcvd (7) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: COMPPROTO[6] 16 VJ > slots with slot compression > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] > 193.158.131.193 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: SendConfigNak(Ack-Rcvd) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IPADDR[6] 0.0.0.0 > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Terminate > Request (2) state = Ack-Rcvd (7) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IpcpSendTerminateAck > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: State change Ack-Rcvd > --> Req-Sent > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: Received Terminate > Request (3) state = Req-Sent (6) > May 18 07:43:15 morranon ppp.2.2.6[5188]: IPCP: IpcpSendTerminateAck > May 18 07:43:15 morranon ppp.2.2.6[5188]: LCP: Received Terminate > Request (1) state = Opened (9) > May 18 07:43:15 morranon ppp.2.2.6[5188]: LCP: LcpLayerDown > May 18 07:43:15 morranon ppp.2.2.6[5188]: LCP: LcpSendTerminateAck. > May 18 07:43:15 morranon ppp.2.2.6[5188]: LCP: State change Opened --> > Stopping > May 18 07:43:16 morranon ppp.2.2.6[5188]: Phase: Disconnected! > May 18 07:43:16 morranon ppp.2.2.6[5188]: LCP: State change Stopping --> > Starting > May 18 07:43:16 morranon ppp.2.2.6[5188]: LCP: LcpLayerFinish > May 18 07:43:16 morranon ppp.2.2.6[5188]: Phase: Modem: Connect time: 7 > secs: 427 octets in, 600 octets out > May 18 07:43:16 morranon ppp.2.2.6[5188]: Phase: total 146 bytes/sec > May 18 07:43:16 morranon ppp.2.2.6[5188]: Phase: NewPhase: Dead > May 18 07:43:25 morranon ppp.2.2.6[5188]: Command: qiot > May 18 07:43:27 morranon ppp.2.2.6[5188]: Command: quit > May 18 07:43:28 morranon ppp.2.2.6[5188]: Phase: PPP Terminated > (normal). > > > -- > Lutz Albers, lutz@muc.de > Do not take life too seriously, you will never get out of it alive. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 17:03:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09776 for freebsd-stable-outgoing; Wed, 27 May 1998 17:03:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hale.ifa.hawaii.edu (hale.IFA.Hawaii.Edu [128.171.2.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA09578 for ; Wed, 27 May 1998 17:01:41 -0700 (PDT) (envelope-from yamada@newton.IfA.Hawaii.Edu) Received: from newton.ifa.hawaii.edu.ifa.hawaii.edu by hale.ifa.hawaii.edu (4.1/hale1.1) id AA25880; Wed, 27 May 98 14:01:25 HST Received: by newton.ifa.hawaii.edu.ifa.hawaii.edu (4.1/SMI-4.1) id AA11083; Wed, 27 May 98 14:01:23 HST Message-Id: <9805280001.AA11083@newton.ifa.hawaii.edu.ifa.hawaii.edu> From: yamada@newton.IfA.Hawaii.Edu (Hubert Yamada) Date: Wed, 27 May 1998 14:01:23 -1000 In-Reply-To: marc@versa.eng.comsat.com's message of May 27, 5:54pm Reply-To: yamada@newton.IfA.Hawaii.Edu (Hubert Yamada) X-Mailer: Mail User's Shell (7.2.3 5/22/91) To: freebsd-stable@FreeBSD.ORG Subject: Re: Kernel building problems Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- On May 27, 1998, marc@versa.eng.comsat.com (Marc Giannoni) wrote -- Subject: Kernel building problems > I recently ran 'cvsup' with tag=RELENG_2_2. > Now it looks like I may need the new CAM code. > > (Prior to posting, I tested a kernel config file which > has been know to compile OK!) [...] > I searched 'everywhere' for the declaration of 'isa_devtab_cam' but it > didn't appear to be delcared anywhere. I just ran into the same problem. The missing declarations are in a file that is automatically generated by 'config'. You need to cd into the config directory (/usr/src/usr.sbin/config (?)) and do a make and make install. Then run the new version of config on your config file. (Of course, there may be other, related problems. It might be worth rebuilding the entire source tree, just to be on the safe side.) -- Hubert Yamada, University of Hawaii, Institute for Astronomy phone: (808) 956-6648 e-mail: yamada@newton.ifa.hawaii.edu WWW: http://ccd.ifa.hawaii.edu/~yamada/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 17:57:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20400 for freebsd-stable-outgoing; Wed, 27 May 1998 17:57:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20179 for ; Wed, 27 May 1998 17:55:37 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA03713; Thu, 28 May 1998 10:25:20 +0930 (CST) Message-Id: <199805280055.KAA03713@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: stable@FreeBSD.ORG Subject: Re: Linux emulator bogons :( In-reply-to: Your message of "Wed, 27 May 1998 16:02:39 +0200." <19980527160239.63405@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 10:25:20 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The change you describe is not in 2.2.6. Oh dear :-/ > Common Lisp work. > However, the Linux emulator LKM should not work at _all_ across > versions. It sounds like you've gotten your LKMs and your kernel out > of sync. Argh :( Oh well, time to figure out what is wrong :( --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 18:41:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27865 for freebsd-stable-outgoing; Wed, 27 May 1998 18:41:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (0@passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27720 for ; Wed, 27 May 1998 18:40:03 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id SAA06485; Wed, 27 May 1998 18:40:00 -0700 (PDT) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdaaDdea; Wed May 27 18:39:51 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.0/8.6.10) id SAA04134; Wed, 27 May 1998 18:38:57 -0700 (PDT) Message-Id: <199805280138.SAA04134@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdgp4115; Wed May 27 18:38:06 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: Kenneth Miller cc: freebsd-stable@FreeBSD.ORG Subject: Re: improper shutdown In-reply-to: Your message of "Tue, 26 May 1998 14:09:06 EDT." <19980526140906.30830@hcs.harvard.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 18:38:04 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Monday, 05/25/98 at 11:31:16 PM, Kenneth Miller wrote: > > > > I've had a minor (?) but irritating problem ever since moving to stable > > from 2.2.5. When I reboot, the disks don't have their clean flags set > > and need fscking. If I shutdown to singer user mode and manually > > unmount the disks, and remount / readonly, it's fine. But using the > > shutdown program to go all the way doesn't work. I will assume this is > > some misconfiguration on my part, but I was a little perplexed that it > > began only when I moved to stable. > > > > Any suggestions or answers appreciated. > > OK. After a little more poking, it became apparent that what was > happening was that certain filesystems were still busy, causing the > reboot syscall to give up and halt without unmounting the filesystems. > Why, then, would they be busy? All other processes should have been > terminated, and no error message appeared indicating anything else. I've had this problem on one of my FreeBSD systems at home, a small system I use as an X Terminal. It doesn't always occur, about once every 5-10 shutdowns. The problem's been there since 2.2.5. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed May 27 22:04:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01109 for freebsd-stable-outgoing; Wed, 27 May 1998 22:04:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from titus.stade.co.uk (root@stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01012 for ; Wed, 27 May 1998 22:03:30 -0700 (PDT) (envelope-from aw1@titus.stade.co.uk) Received: (from aw1@localhost) by titus.stade.co.uk (8.8.8/8.8.3) id EAA05436; Thu, 28 May 1998 04:38:12 +0100 (BST) Message-ID: <19980528043812.A5133@stade.co.uk> Date: Thu, 28 May 1998 04:38:12 +0100 From: Adrian Wontroba To: freebsd-stable@FreeBSD.ORG Subject: Re: improper shutdown Reply-To: aw1@stade.co.uk Mail-Followup-To: freebsd-stable@freebsd.org References: <199805260657.XAA00702@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Jason Evans on Tue, May 26, 1998 at 10:16:34AM -0700 Organization: Stade Computers Ltd, UK X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 26, 1998 at 10:16:34AM -0700, Jason Evans wrote: > keaggy:/usr/home /usr/home nfs rw 0 0 > when I rebooted to use the new kernel, I saw something like: > Syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Giving up. I seem to recall something like this. The symptoms went away if I unmounted the nfs mounts before closing down. -- Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 Mail info@accu.org for information about the Association of C and C++ Users or see To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 06:30:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13214 for freebsd-stable-outgoing; Thu, 28 May 1998 06:30:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13051; Thu, 28 May 1998 06:30:03 -0700 (PDT) (envelope-from tfuruya@dilemma.tf.or.jp@ppp129166.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp129166.asahi-net.or.jp [202.213.129.166]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id WAA09854; Thu, 28 May 1998 22:34:45 +0900 Received: from dilemma.tf.or.jp (dilemma.tf.or.jp [192.168.1.3]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id WAA04632; Thu, 28 May 1998 22:29:23 +0900 (JST) Received: from dilemma.tf.or.jp (localhost [127.0.0.1]) by dilemma.tf.or.jp (8.8.8/3.6W-CF3.6W-dilemma-tf.or.jp-9805) with ESMTP id WAA00669; Thu, 28 May 1998 22:24:13 +0900 (JST) Message-Id: <199805281324.WAA00669@dilemma.tf.or.jp> To: robinson@public.bta.net.cn, Mike Smith Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Tetsuro FURUYA Subject: Re: Bug in wd driver From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Tue, 26 May 1998 11:42:26 +0800 (GMT)" References: <199805260342.LAA02975@public.bta.net.cn> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 28 May 1998 22:24:07 +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My mail does not reach mailing lists. So, this is a resend. In Message-ID: <199805260342.LAA02975@public.bta.net.cn> Michael Robinson wrote: >I wrote a message related to this problem to freebsd-questions >yesterday, but upon further investigation, I have decided this is >a bug, not a feature. >I have a Tecra 510CDT (running 2.2.6-RELEASE) that suffered a >corrupted disk when the battery power failed as it was trying to >halt. > > 1. Any I/O access to the affected sectors will cause the following > message: > > wd0: interrupt timeout > wd0: status 58 error 0 > > followed by seeking noises, and the following message: > > wd0: interrupt timeout > wd0: status 50 error 1 > > 2. After this, the process requesting the I/O will be completely > locked, but the disk will continue to make seeking noises > continuously until the system is powered off. > Other processes are able to access the affected slice/partition > (ls, cat, etc.) without any difficulty, as long as they avoid > the 7 affected sectors. Any process which requires privileged > kernel calls (halt, ps, etc.) will lock immediately and > completely. > > 3. Other than the two messages above, wd produces no error messages. > > 4. Hard reset is the only way to recover. > > I tried to work around this problem with bad144, but rapidly discovered > that bad144 is something of a bad joke in FreeBSD. Does anyone have > any recommendations for how to fix the wd driver or otherwise recover > from this fault? > > -Michael Robinson I have been encountered at the same defaults in using Panasonic AL-N1, and FreeBSD-2.2.2. And bad144 was hangupped. But I have found out how to manipulate bad144, or fsck , or badsect. My kernel has kernel-debugger ddb(4) installed in it. ^^^^^^ So, listening to the hamming sound of wd0 drive, and when wd drive is hangupped, invoke kernel-debugger by typing ctrl-alt-ESC keys. ^^^^^^^^^^^^ A while after stopping of disk access, type 'c' or 'continue', and go back to bad144 or fsck. Several attempts may complete the identification of bad clusters. As for my machine, this was worked. ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 E-Mail: ht5t-fry@asahi-net.or.jp tfu@ff.iij4u.or.jp pgp-fingerprint: pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 08:06:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26010 for freebsd-stable-outgoing; Thu, 28 May 1998 08:06:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25991 for ; Thu, 28 May 1998 08:06:30 -0700 (PDT) (envelope-from tfuruya@dilemma.tf.or.jp@ppp129137.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp129137.asahi-net.or.jp [202.213.129.137]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id AAA11802; Fri, 29 May 1998 00:11:25 +0900 Received: from dilemma.tf.or.jp (dilemma.tf.or.jp [192.168.1.3]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id AAA06744; Fri, 29 May 1998 00:06:03 +0900 (JST) Received: from dilemma.tf.or.jp (localhost [127.0.0.1]) by dilemma.tf.or.jp (8.8.8/3.6W-CF3.6W-dilemma-tf.or.jp-9805) with ESMTP id AAA04056; Fri, 29 May 1998 00:08:56 +0900 (JST) Message-Id: <199805281508.AAA04056@dilemma.tf.or.jp> To: mike@smith.net.au Cc: Tetsuro FURUYA , robinson@public.bta.net.cn, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Wed, 27 May 1998 14:01:47 -0700" References: <199805272101.OAA01902@dingo.cdrom.com> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 29 May 1998 00:08:53 +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Message-ID: <199805272101.OAA01902@dingo.cdrom.com> Mike Smith worte: > Also, what are the status and error values that you see in the > "interrupt timeout" messages? My output of fsck and ddb(4) is: >fsck /usr >..... >wd0: interrupt timeout: >wd0: status 50 error 0 >wd0: interrupt timeout: >wd0: status 50 error 1 >===> hang up >===> type 'cntrl-alt-esc' >db>wd0s1f: hard error reading fsbn 1152850 of 1152850-1152851(wd0s1 bn >1279826; cn 317 tn 26 sn 44) >wd0: status 59 error 40 >===> type 'c' or 'continue' >cannot read: BLK 1152850 >.... After this, fsck completes successfully ^^) These are the same in bad144. bad144 says "marked bad" instead of "cannot read". And, moreover there is cron message (these are diffenrent blocks ?), dilemma kernel log messages: > wd0: interrupt timeout: > wd0: status 50 error 1 > swap_pager: indefinite wait buffer: device: 131073, blkno: 3224, size: 20480 > swap_pager: indefinite wait buffer: device: 131073, blkno: 3224, size: 20480 > swap_pager: indefinite wait buffer: device: 131073, blkno: 26752, size: 4096 > swap_pager: indefinite wait buffer: device: 131073, blkno: 3224, size: 20480 > swap_pager: indefinite wait buffer: device: 131073, blkno: 26752, size: 4096 ..... these messages are repeating several times. As for wd.c source, I will try to experiment :) =================================================================== It seems that this message has not reached mailing list. So, I write again. In Message-ID: <199805260342.LAA02975@public.bta.net.cn> Michael Robinson wrote: >I wrote a message related to this problem to freebsd-questions >yesterday, but upon further investigation, I have decided this is >a bug, not a feature. >I have a Tecra 510CDT (running 2.2.6-RELEASE) that suffered a >corrupted disk when the battery power failed as it was trying to >halt. > > 1. Any I/O access to the affected sectors will cause the following > message: > > wd0: interrupt timeout > wd0: status 58 error 0 > > followed by seeking noises, and the following message: > > wd0: interrupt timeout > wd0: status 50 error 1 > > 2. After this, the process requesting the I/O will be completely > locked, but the disk will continue to make seeking noises > continuously until the system is powered off. > Other processes are able to access the affected slice/partition > (ls, cat, etc.) without any difficulty, as long as they avoid > the 7 affected sectors. Any process which requires privileged > kernel calls (halt, ps, etc.) will lock immediately and > completely. > > 3. Other than the two messages above, wd produces no error messages. > > 4. Hard reset is the only way to recover. > > I tried to work around this problem with bad144, but rapidly discovered > that bad144 is something of a bad joke in FreeBSD. Does anyone have > any recommendations for how to fix the wd driver or otherwise recover > from this fault? > > -Michael Robinson I have been encountered at the same defaults in using Panasonic AL-N1, and FreeBSD-2.2.2. And bad144 was hangupped. But I have found out how to manipulate bad144, or fsck , or badsect. My kernel has kernel-debugger ddb(4) installed in it. ^^^^^^ So, listening to the hamming sound of wd0 drive, and when wd drive is hangupped, invoke kernel-debugger by typing ctrl-alt-ESC keys. ^^^^^^^^^^^^ A while after stopping of disk access, type 'c' or 'continue', and go back to bad144 or fsck. Several attempts may complete the identification of bad clusters. As for my machine, this was worked. ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 E-Mail: ht5t-fry@asahi-net.or.jp tfu@ff.iij4u.or.jp pgp-fingerprint: pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 08:07:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26115 for freebsd-stable-outgoing; Thu, 28 May 1998 08:07:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26071 for ; Thu, 28 May 1998 08:07:03 -0700 (PDT) (envelope-from tfuruya@ppp129137.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp129137.asahi-net.or.jp [202.213.129.137]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id AAA25270; Fri, 29 May 1998 00:12:07 +0900 Received: from galois.tf.or.jp (localhost.tf.or.jp [127.0.0.1]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id AAA06761; Fri, 29 May 1998 00:06:45 +0900 (JST) Message-Id: <199805281506.AAA06761@galois.tf.or.jp> To: mike@smith.net.au Cc: robinson@public.bta.net.cn, Tetsuro FURUYA , freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA Erros-To: Tetsuro FURUYA In-Reply-To: Your message of "Wed, 27 May 1998 14:01:47 -0700" References: <199805272101.OAA01902@dingo.cdrom.com> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 29 May 1998 00:06:45 +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Message-ID: <199805272101.OAA01902@dingo.cdrom.com> Mike Smith worte: > Also, what are the status and error values that you see in the > "interrupt timeout" messages? My output of fsck and ddb(4) is: >fsck /usr >..... >wd0: interrupt timeout: >wd0: status 50 error 0 >wd0: interrupt timeout: >wd0: status 50 error 1 >===> hang up >===> type 'cntrl-alt-esc' >db>wd0s1f: hard error reading fsbn 1152850 of 1152850-1152851(wd0s1 bn >1279826; cn 317 tn 26 sn 44) >wd0: status 59 error 40 >===> type 'c' or 'continue' >cannot read: BLK 1152850 >.... After this, fsck completes successfully ^^) These are the same in bad144. bad144 says "marked bad" instead of "cannot read". And, moreover there is cron message (these are diffenrent blocks ?), dilemma kernel log messages: > wd0: interrupt timeout: > wd0: status 50 error 1 > swap_pager: indefinite wait buffer: device: 131073, blkno: 3224, size: 20480 > swap_pager: indefinite wait buffer: device: 131073, blkno: 3224, size: 20480 > swap_pager: indefinite wait buffer: device: 131073, blkno: 26752, size: 4096 > swap_pager: indefinite wait buffer: device: 131073, blkno: 3224, size: 20480 > swap_pager: indefinite wait buffer: device: 131073, blkno: 26752, size: 4096 ..... these messages are repeating several times. As for wd.c source, I will try to experiment :) =================================================================== It seems that this message has not reached mailing list. So, I write again. In Message-ID: <199805260342.LAA02975@public.bta.net.cn> Michael Robinson wrote: >I wrote a message related to this problem to freebsd-questions >yesterday, but upon further investigation, I have decided this is >a bug, not a feature. >I have a Tecra 510CDT (running 2.2.6-RELEASE) that suffered a >corrupted disk when the battery power failed as it was trying to >halt. > > 1. Any I/O access to the affected sectors will cause the following > message: > > wd0: interrupt timeout > wd0: status 58 error 0 > > followed by seeking noises, and the following message: > > wd0: interrupt timeout > wd0: status 50 error 1 > > 2. After this, the process requesting the I/O will be completely > locked, but the disk will continue to make seeking noises > continuously until the system is powered off. > Other processes are able to access the affected slice/partition > (ls, cat, etc.) without any difficulty, as long as they avoid > the 7 affected sectors. Any process which requires privileged > kernel calls (halt, ps, etc.) will lock immediately and > completely. > > 3. Other than the two messages above, wd produces no error messages. > > 4. Hard reset is the only way to recover. > > I tried to work around this problem with bad144, but rapidly discovered > that bad144 is something of a bad joke in FreeBSD. Does anyone have > any recommendations for how to fix the wd driver or otherwise recover > from this fault? > > -Michael Robinson I have been encountered at the same defaults in using Panasonic AL-N1, and FreeBSD-2.2.2. And bad144 was hangupped. But I have found out how to manipulate bad144, or fsck , or badsect. My kernel has kernel-debugger ddb(4) installed in it. ^^^^^^ So, listening to the hamming sound of wd0 drive, and when wd drive is hangupped, invoke kernel-debugger by typing ctrl-alt-ESC keys. ^^^^^^^^^^^^ A while after stopping of disk access, type 'c' or 'continue', and go back to bad144 or fsck. Several attempts may complete the identification of bad clusters. As for my machine, this was worked. ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 E-Mail: ht5t-fry@asahi-net.or.jp tfu@ff.iij4u.or.jp pgp-fingerprint: pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 08:23:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28475 for freebsd-stable-outgoing; Thu, 28 May 1998 08:23:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mercury.acs.unt.edu (mercury.acs.unt.edu [129.120.220.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28448 for ; Thu, 28 May 1998 08:23:41 -0700 (PDT) (envelope-from john@mailhost.cas.unt.edu) Received: from www.cas.unt.edu (www.cas.unt.edu [129.120.3.150]) by mercury.acs.unt.edu (8.8.8/8.8.8) with ESMTP id KAA03830 for ; Thu, 28 May 1998 10:23:29 -0500 (CDT) Received: from purgatory (purgatory.cascss.unt.edu [129.120.32.82]) by www.cas.unt.edu (8.8.8/8.6.9) with SMTP id KAA18698 for ; Thu, 28 May 1998 10:20:04 -0500 (CDT) Message-Id: <199805281520.KAA18698@www.cas.unt.edu> Comments: Authenticated sender is From: john@unt.edu To: stable@FreeBSD.ORG Date: Thu, 28 May 1998 10:23:26 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Config program In-reply-to: <19980524181216.59289@st-lcremean.tidalwave.net> References: ; from mturpin@mail1.i1.net on Sun, May 24, 1998 at 03:43:36PM -0500 X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could the caretaker of config create something so that if an old config is used on a newer source tree (ie the config needs updated) it returns a good error like "You need an updated config program"? Wasn't a problem cause I'm on the -stable list and I just found some old letters about the problem but I do think it would help out. -------------------------------------------------- John A. Booth University of North Texas College of Arts & Sciences Computer Support Specialist GW address: CAS.PO7.JOHN Internet: john@unt.edu Office: 940-565-4498 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 08:34:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00142 for freebsd-stable-outgoing; Thu, 28 May 1998 08:34:21 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from adam.framatome.fr (ubc@adam.framatome.fr [192.44.46.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00102 for ; Thu, 28 May 1998 08:34:06 -0700 (PDT) (envelope-from ubc@paris.framatome.fr) Received: from localhost (ubc@localhost) by adam.framatome.fr (8.8.8/8.8.8) with SMTP id RAA27213 for ; Thu, 28 May 1998 17:34:00 +0200 (CEST) Date: Thu, 28 May 1998 17:34:00 +0200 (CEST) From: Claude Buisson X-Sender: ubc@adam.framatome.fr To: FreeBSD-stable@FreeBSD.ORG Subject: How to make a release ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I just upgraded my 2.2.2-RELEASE test machine to 2.2.6-STABLE with no problem, and tried to make a release to upgrade other machines via ftp. After reading the FAQ Section 13.2, I did a make release ... in /usr/src/release. After making the distrib-dirs then distribution into CHROOTDIR, the cd ${.CURDIR}/.. && ${MAKE} install DESTDIR=${CHROOTDIR} NOMAN=1 stopped for a number of reasons: - no osreldate.h, - no *.h in include/rpcsvc which I tried to correct by hand from /usr/include, then - no crt0.o where I gave up. Any hint ? TIA Claude Buisson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 08:48:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01384 for freebsd-stable-outgoing; Thu, 28 May 1998 08:48:55 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hcs.harvard.edu (hcs.harvard.edu [140.247.73.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01268 for ; Thu, 28 May 1998 08:47:38 -0700 (PDT) (envelope-from kemiller@hcs.harvard.edu) Received: (from kemiller@localhost) by hcs.harvard.edu (8.8.5/8.8.3) id LAA07869; Thu, 28 May 1998 11:47:35 -0400 (EDT) Message-ID: <19980528114735.39085@hcs.harvard.edu> Date: Thu, 28 May 1998 11:47:35 -0400 From: Kenneth Miller To: freebsd-stable@FreeBSD.ORG Subject: Re: improper shutdown [Resolution?] References: <199805260657.XAA00702@antipodes.cdrom.com> <19980528043812.A5133@stade.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980528043812.A5133@stade.co.uk>; from Adrian Wontroba on Thu, May 28, 1998 at 04:38:12AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 05/28/98 at 04:38:12 AM, Adrian Wontroba wrote: > On Tue, May 26, 1998 at 10:16:34AM -0700, Jason Evans wrote: > > > keaggy:/usr/home /usr/home nfs rw 0 0 > > > when I rebooted to use the new kernel, I saw something like: > > Syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Giving up. > > I seem to recall something like this. The symptoms went away if I > unmounted the nfs mounts before closing down. it's sounding like certain fs types don't respond properly to the halt-time dismount request. i managed to fix my problem by umounting all the ext2fs disks before shutdown, and now have them set to noauto in my fstab so i don't have to. is this a known problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 13:11:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14297 for freebsd-stable-outgoing; Thu, 28 May 1998 13:11:10 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14145 for ; Thu, 28 May 1998 13:10:35 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id QAA10549 for ; Thu, 28 May 1998 16:10:27 -0400 (EDT) Date: Thu, 28 May 1998 16:10:26 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: stable@FreeBSD.ORG Subject: NFS file locking Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's the current status of file locking over NFS on FreeBSD-stable? I have an application that uses dot-file locking, and I'd love to switch it over to a FreeBSD NFS server. The clients are NeXTStep, if that makes a difference. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 13:44:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22160 for freebsd-stable-outgoing; Thu, 28 May 1998 13:44:50 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.mexcom.net (ver2-101.uninet.net.mx [200.38.135.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22039 for ; Thu, 28 May 1998 13:44:14 -0700 (PDT) (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (telmex@sunix.mexcom.net [206.103.64.3]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id PAA27761; Thu, 28 May 1998 15:39:44 -0500 (CDT) Message-ID: <356DCBD2.15E6717B@ver1.telmex.net.mx> Date: Thu, 28 May 1998 15:40:50 -0500 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Claude Buisson CC: FreeBSD-stable@FreeBSD.ORG Subject: Re: How to make a release ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Claude Buisson wrote: > > Hi all, > > I just upgraded my 2.2.2-RELEASE test machine to 2.2.6-STABLE with > no problem, and tried to make a release to upgrade other machines > via ftp. You might also contemplate mounting /usr/src /usr/obj and do a make installworld. I just make a new kernel, which I assume that you did after your make world. # cd /usr/src/release # make release CHROOTDIR=/var/ftp/release CVSROOT=/home/ncvs \ RELEASETAG=RELENG_2_2 BUILDNAME=FreeBSD_2.2.6 > /tmp/mr2_2.log 2>&1 & I then go on my merry way or add a tail -f /tmp/mr2_2.log if I want to worry:-) I very seldom have a problem. Of course I'm pretty sure that the comand line variables can be environment variables. ed > > After reading the FAQ Section 13.2, I did a > > make release ... > > in /usr/src/release. > > After making the distrib-dirs then distribution into CHROOTDIR, the > > cd ${.CURDIR}/.. && ${MAKE} install DESTDIR=${CHROOTDIR} NOMAN=1 > > stopped for a number of reasons: > > - no osreldate.h, > - no *.h in include/rpcsvc > > which I tried to correct by hand from /usr/include, then > > - no crt0.o > > where I gave up. > > Any hint ? > > TIA > > Claude Buisson > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 14:03:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25547 for freebsd-stable-outgoing; Thu, 28 May 1998 14:03:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25542 for ; Thu, 28 May 1998 14:03:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA01309; Thu, 28 May 1998 12:57:14 -0700 (PDT) Message-Id: <199805281957.MAA01309@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tetsuro FURUYA cc: mike@smith.net.au, robinson@public.bta.net.cn, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-reply-to: Your message of "Fri, 29 May 1998 00:06:45 +0900." <199805281506.AAA06761@galois.tf.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 12:57:14 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In Message-ID: <199805272101.OAA01902@dingo.cdrom.com> > Mike Smith worte: > > > > Also, what are the status and error values that you see in the > > "interrupt timeout" messages? > > My output of fsck and ddb(4) is: > > >fsck /usr > >..... > >wd0: interrupt timeout: > >wd0: status 50 error 0 > >wd0: interrupt timeout: > >wd0: status 50 error 1 > > >===> hang up > >===> type 'cntrl-alt-esc' This defers the interrupt timeout... > >db>wd0s1f: hard error reading fsbn 1152850 of 1152850-1152851(wd0s1 bn > >1279826; cn 317 tn 26 sn 44) > >wd0: status 59 error 40 ... but not the interrupt, which finally arrives and contains real error information. Note that the interrupt timeouts in your case *don't* have DRQ set. Are you running in multi-block mode? > As for wd.c source, I will try to experiment :) Please do. It looks like your information may lead to a result here. Thanks! -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 14:19:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27865 for freebsd-stable-outgoing; Thu, 28 May 1998 14:19:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27852 for ; Thu, 28 May 1998 14:18:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA01444; Thu, 28 May 1998 13:13:53 -0700 (PDT) Message-Id: <199805282013.NAA01444@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: john@unt.edu cc: stable@FreeBSD.ORG Subject: Re: Config program In-reply-to: Your message of "Thu, 28 May 1998 10:23:26 -0000." <199805281520.KAA18698@www.cas.unt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 13:13:52 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Could the caretaker of config create something so that if an old config is > used on a newer source tree (ie the config needs updated) it returns a > good error like "You need an updated config program"? > > Wasn't a problem cause I'm on the -stable list and I just found some old letters > about the problem but I do think it would help out. It's already been done, but not brought back to -stable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 16:48:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25693 for freebsd-stable-outgoing; Thu, 28 May 1998 16:48:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25642 for ; Thu, 28 May 1998 16:48:05 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id QAA12966; Thu, 28 May 1998 16:47:55 -0700 (PDT) (envelope-from jdp) Message-Id: <199805282347.QAA12966@austin.polstra.com> To: eivind@yes.no Subject: Re: Getting source In-Reply-To: <19980527233707.28932@follo.net> References: <19980527213242.16768@sr.se> <19980527233707.28932@follo.net> Organization: Polstra & Co., Seattle, WA Cc: flygt@sr.se, freebsd-stable@FreeBSD.ORG Date: Thu, 28 May 1998 16:47:55 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980527233707.28932@follo.net>, Eivind Eklund wrote: > On Wed, May 27, 1998 at 09:32:42PM +0200, Gunnar Flygt wrote: > > My FreeBSD 2.2.6 is placed behind a fire wall, and when using ports I set the > > environment variables FTP_PROXY and FTP_PASSWORD. Will this work for cvsup > > also? > > No. If you're behind a pure proxy firewall (limited number of > services) you'll probably have to change to using CTM to get the > source. Or, if the firewall runs SOCKS then that should work for CVSup. There's a section in the cvsup man page about how to do it. > If you're just behind a filter, you can do by using the > passive mode for cvsup - see the man page for details. Yes, that almost always works through a filter. But the most sure-fire mode is "multiplexed" mode, which is enabled by "-P m" on the command line. While I'm here, let me just put in a plug for the new CVSup FAQ at: http://www.polstra.com/projects/freeware/CVSup/faq.html Suggestions, corrections, and additional questions for the FAQ are always welcomed. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 18:37:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17392 for freebsd-stable-outgoing; Thu, 28 May 1998 18:37:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from paris.dppl.com (exim@paris.dppl.com [205.230.74.150]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17381; Thu, 28 May 1998 18:37:24 -0700 (PDT) (envelope-from yds@ingress.com) Received: from ichiban.ingress.com (ichiban) [205.230.64.31] by paris.dppl.com with smtp (Exim 1.82 #1) id 0yfE6l-0005op-00; Thu, 28 May 1998 21:37:23 -0400 Message-ID: <045901bd8aa2$5269ea90$1f40e6cd@ichiban.ingress.com> From: "Yarema" To: Cc: , Subject: Re: [can not execute /usr/local/libexec/amanda/runtar: Permission denied] Date: Thu, 28 May 1998 21:37:20 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I just installed amanda-2.4.0 on a FreeBSD 2.2.6 machine from the FreeBSD >> ports collection. and I'm getting the above error. I've verified that runtar >> is setuid root: >> >> -r-sr-x--- 1 root operator 8192 May 27 20:48 runtar > > >Well, if your amanda user is not in group "operator", then you >will get a permission denied. Hopefully I am not being to basic >here. Please excuse me if I am. Argh!! No, you're not being to basic. For some strange reason user operator on FreeBSD 2.2.6 is in group staff and not in group operator. As far as I can tell user Operator should be in group operator out of the box if the Amanda port is configured to build --with-user=operator --with-group=operator Unless this breaks anything someone at FreeBSD should commit the following patch: --- /usr/src/etc/master.passwd.orig Wed Oct 8 07:34:14 1997 +++ /usr/src/etc/master.passwd Thu May 28 21:32:15 1998 @@ -1,7 +1,7 @@ root::0:0::0:0:Charlie &:/root:/bin/csh toor:*:0:0::0:0:Bourne-again Superuser:/root: daemon:*:1:1::0:0:Owner of many system processes:/root:/nonexistent -operator:*:2:20::0:0:System &:/usr/guest/operator:/bin/csh +operator:*:2:5::0:0:System &:/usr/guest/operator:/bin/csh bin:*:3:7::0:0:Binaries Commands and Source,,,:/:/nonexistent games:*:7:13::0:0:Games pseudo-user:/usr/games:/nonexistent news:*:8:8::0:0:News Subsystem:/:/nonexistent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 28 19:59:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02376 for freebsd-stable-outgoing; Thu, 28 May 1998 19:59:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02368 for ; Thu, 28 May 1998 19:59:01 -0700 (PDT) (envelope-from kline@tera.tera.com) Received: from athena.tera.com (athena.tera.com [207.224.230.127]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id TAA28598 for ; Thu, 28 May 1998 19:58:20 -0700 (PDT) From: Gary Kline Received: (from kline@localhost) by athena.tera.com (8.7.5/8.7.3) id TAA28096 for freebsd-stable@freebsd.org; Thu, 28 May 1998 19:58:14 -0700 (PDT) Message-Id: <199805290258.TAA28096@athena.tera.com> Subject: 2.2.6, xterm, netscape, chimera.... To: freebsd-stable@FreeBSD.ORG Date: Thu, 28 May 1998 19:58:13 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL23 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A couple days ago I found that a script to create new xterms failed with my DISPLAY set to `localhost:0.0'.... but after I set the DISPLAY to tao:0.0 or unix:0.0 the script worked. Up popped two preconfigured xterms. Okay, no big deal. Yesterday and today I've run into snags with netscape and a newer version of chimera.. When pointing to certain sites, my screen goes black and a moment later I am thrown back to my xdm login screen. This happens both with external html sites and certain of my own private pages, e.g.:: file://localhost/home/kline/writing/articles/bsd1.html Does anybody know what's messed up??! gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 29 02:46:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29849 for freebsd-stable-outgoing; Fri, 29 May 1998 02:46:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29509 for ; Fri, 29 May 1998 02:45:08 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id MAA00967; Fri, 29 May 1998 12:44:27 +0300 (EEST) (envelope-from ru) Message-ID: <19980529124427.A29838@ucb.crimea.ua> Date: Fri, 29 May 1998 12:44:27 +0300 From: Ruslan Ermilov To: stable@FreeBSD.ORG Subject: Problem installing 2.2.6 in dangerously dedicated mode Mail-Followup-To: stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i X-Operating-System: FreeBSD 2.2.6-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Yesterday I tried to install FreeBSD 2.2.6-STABLE on the following hardware: Intel X-Series Deskside/MX Server (P90, 64Mb of ram) PhoenixBIOS(TM) E486 Version 1.00.19.AM0 aic7770 on-board SCSI (Bios v2.11 S3) Seagate ST32155N (2Gb, 2049/64/32 in Adaptec's >1G geometry translation mode) This machine intended for use only with FreeBSD and will act as an ip-router and dialup access server via ppp. So, as always, I started to install FreeBSD in `dangerously-dedicated' mode. The installation process was smooth, but after it has finished and rebooted, I got ``Read error'' message from FreeBSD bootblocks (start.S, I think?). At the end of it all I successfully installed FreeBSD in standard compatible mode. Of course, this mode wasted some space of my HD, about 0.5Mb ;-( Then I read the section 8.10 of the FAQ about dangerously dedicated mode, in particular, about HP Netservers' BIOS weirdness, then I read the README.386BSD and README.MACH from sys/i386/boot/biosboot, and now I have a few questions: 1. When ``sysinstall'' first runs, what disk geometry it detects? What the system bios tells or SCSI bios or ...? It saw me some weird geometry with 16 heads and 17 sectors, when I expected something like 2049/64/32 or even though magic/63/255. Well, maybe I need to follow FAQ advise and setup fake DOS partition first... 2. From what I've read in README.386BSD, when I install FreeBSD in DD mode: | Boot 1 also contains a compiled in DOS partition table | (in case it is at block 0), which contains a 386bsd partition starting | at 0. This ensures that the same code can work whether or not | boot1 is at block 0. What this table looks like, I wonder? Any good pointer to the source code in sys/i386/*boot will be satisfied ;-) Unfortunately, I have no more *re-installation* access to that server as it has to work now and it works fine (as always ;-), but it dos-fdisk-mode. Any help would be greatly appreciated. Reagrds, -- Ruslan Ermilov System Administrator ru@ucb.crimea.ua United Commercial Bank +380-652-247647 Simferopol, Crimea 2426679 ICQ Network, UIN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 29 10:45:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22954 for freebsd-stable-outgoing; Fri, 29 May 1998 10:45:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA22843 for ; Fri, 29 May 1998 10:45:06 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA28058 for stable@freebsd.org; Fri, 29 May 1998 18:04:39 +0200 From: Luigi Rizzo Message-Id: <199805291604.SAA28058@labinfo.iet.unipi.it> Subject: IDE busmaster patches for -stable ? To: stable@FreeBSD.ORG Date: Fri, 29 May 1998 18:04:39 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think i saw some time ago a message for patches to implement (E)IDE busmastering on -stable. Cannot find the message anymore, can someone pass me the pointer ? thanks luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 29 20:01:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02421 for freebsd-stable-outgoing; Fri, 29 May 1998 20:01:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02405; Fri, 29 May 1998 20:01:34 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA05097; Fri, 29 May 1998 22:00:59 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805300300.WAA05097@dyson.iquest.net> Subject: Re: DPT install problem In-Reply-To: <199805261847.LAA00549@dingo.cdrom.com> from Mike Smith at "May 26, 98 11:47:18 am" To: mike@smith.net.au (Mike Smith) Date: Fri, 29 May 1998 22:00:59 -0500 (EST) Cc: toor@dyson.iquest.net, shimon@simon-shapiro.org, mike@smith.net.au, tom@sdf.com, freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > On 22-May-98 Mike Smith wrote: > > > >> > > > >> > However, there are a couple of things that you personally (and other > > > >> > concerned users) can do to help the situation. > > > >> > > > > >> > - Contribute commentary (as you have), documentation and source/ > > > >> > procedural fixes. Remeber that FreeBSD is a volunteer project - > > > >> > your support means that it will continue to improve. > > > >> > - Donate a DPT controller to our testing pool so that we can test > > > >> > with it. Chances are we can scrape enough disks together in one > > > >> > place to meet the 20GB mark if we have one. > > > >> > > > >> I recently donated TWO DPT controllers and FIVE disk drives. They went > > > >> to > > > >> two separate FreeBSD prominent figures, but still do not add up to 20GB. > > > > > > > > Then we need some accountability from these prominent figures. Where > > > > is their feedback on this discussion? > > > > > Do you want working kernel threads and SMP or DPT support? I am working > > feverishly on the SMP and kernel threads stuff, and physically cannot do > > any more in the day. > > I just want to know what these people are doing if not answering > questions. Guessing and begging users for input is traditional stuff, > but if there's a better alternative, I'm all for it. > > > I do plan to work on the DPT stuff, but I can only do one type of thing > > at a time... > > Sounds reasonable to me. What we need are some underlings for you to > boss around doing your grunt work. JD and the moonshine gang? > I have worked in mgmt before, I make a much better 'grunt'. :-). Also, if we can find someone who can do things more quickly or efficiently, and Simon agrees, I am willing to ship the equipment to someone else. I consider the equipment as a project resource donated by Simon, and am willing to do what I can do to make things move more quickly as needed and agreed by everyone concerned!!! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat May 30 04:30:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03880 for freebsd-stable-outgoing; Sat, 30 May 1998 04:30:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from colin.muc.de (root@colin.muc.de [193.174.4.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA03867 for ; Sat, 30 May 1998 04:30:10 -0700 (PDT) (envelope-from lutz@muc.de) Received: from tavari.muc.de ([193.174.4.22]) by colin.muc.de with SMTP id <140564-2>; Sat, 30 May 1998 11:03:01 +0200 Received: from abraxas.tavari.muc.de (abraxas [192.168.42.5]) by tavari.muc.de (8.8.8/8.8.7) with SMTP id KAA28951; Sat, 30 May 1998 10:53:25 +0200 (CEST) Date: Sat, 30 May 1998 10:53:27 +0200 From: lutz albers To: Brian Somers cc: Lutz Albers , freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 ppp breaks compatability with T-Online ppp In-Reply-To: <199805272240.XAA27141@awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 May 1998, Brian Somers wrote: > Oops - this got lost in my piles of email :-( Sorry. > > Can you remove the ``set ifaddr 0 0'' and see if things get better ? Yes, that did it. Thanks, but why did it worked with the old code in 2.2.5 ? ciao lutz > > Brian Somers wrote: > > > > I just upgraded my server from 2.2.5 to 2.2.6. After this upgrade ppp > > > > (user level) is no longer able to connect to the german ISP T-Online. > > > > The 2.2.5 version worked just fine (I have recompiled the version from > > > > the 2.2.5 sources and it works again). Here is the output from ppp.log: > > > [.....] > > > > If someone wants more info's, then just contact. > > > > > > I think we need to see the LCP and IPCP logs too. This looks like > > > failed negotiation :-/ > > (log deleted) -- Lutz Albers, lutz@muc.de Do not take life too seriously, you will never get out of it alive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat May 30 04:30:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03894 for freebsd-stable-outgoing; Sat, 30 May 1998 04:30:21 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from colin.muc.de (root@colin.muc.de [193.174.4.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA03874 for ; Sat, 30 May 1998 04:30:13 -0700 (PDT) (envelope-from lutz@muc.de) Received: from tavari.muc.de ([193.174.4.22]) by colin.muc.de with SMTP id <140573-2>; Sat, 30 May 1998 12:45:47 +0200 Received: from muc.de (abraxas [192.168.42.5]) by tavari.muc.de (8.8.8/8.8.7) with ESMTP id LAA29145; Sat, 30 May 1998 11:32:08 +0200 (CEST) Message-ID: <356FD21A.B3B551E0@muc.de> Date: Sat, 30 May 1998 11:32:10 +0200 From: Lutz Albers X-Mailer: Mozilla 4.04 [en] (X11; U; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: aw1@stade.co.uk, freebsd-stable@FreeBSD.ORG Subject: Re: improper shutdown References: <199805260657.XAA00702@antipodes.cdrom.com> <19980528043812.A5133@stade.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adrian Wontroba wrote: > > On Tue, May 26, 1998 at 10:16:34AM -0700, Jason Evans wrote: > > > keaggy:/usr/home /usr/home nfs rw 0 0 > > > when I rebooted to use the new kernel, I saw something like: > > Syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Giving up. > > I seem to recall something like this. The symptoms went away if I > unmounted the nfs mounts before closing down. Just exit all programs/shell which are cwd'd to a nfs-mounted directory. At least thats what I do. This 'feature' has been introduced somewhere between 2.2.2 and 2.2.5 :-( ciao lutz -- Lutz Albers, lutz@muc.de Do not take life too seriously, you will never get out of it alive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat May 30 05:45:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09544 for freebsd-stable-outgoing; Sat, 30 May 1998 05:45:06 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from eden-backend.rutgers.edu (0@eden-backend.rutgers.edu [165.230.180.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09529 for ; Sat, 30 May 1998 05:44:46 -0700 (PDT) (envelope-from damascus@eden.rutgers.edu) Received: from athena (adderley-a-asy-16.rutgers.edu [165.230.224.84]) by eden-backend.rutgers.edu (8.8.8/8.8.8) with SMTP id IAA09403 for ; Sat, 30 May 1998 08:44:42 -0400 (EDT) Message-Id: <199805301244.IAA09403@eden-backend.rutgers.edu> X-Sender: damascus@eden-backend.rutgers.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 30 May 1998 08:45:55 -0400 To: freebsd-stable@FreeBSD.ORG From: Carroll Kong Subject: NATD, Intermittent Problems. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys. I just setup NATD, I got a cable modem, and 3 computers... although the problem, (at least I think it does...) only refers to two computers. I think I set it up right, both computers (as well as the gateway / router / caching DNS server with two NICs), can access the network. However, I noticed a few oddities. I use the software, "Eudora Pro" email client on one of the other machines. When I try to send mail to some mailing lists, it will say "thisemail@addr.com was not accept by your SMTP Server, change the recipient name." Okay... I am a bit fuzzy on natd... I thought it forwarded everything all fine and dandy. But I can RECEIVE mail, but I cannot SEND mail from the other computers. I am going to further test different combinations. But all in all, there is something amiss. I tried eliminating sendmail on the other machine. (the natd / gateway / router / caching DNS machine...) but I am uncertain why it would need sendmail to forward the POP3 mail that eudora is sending out? Seems like a port issue? (oh yeah /var/log/maillog shows NO errors... just sendmail starting up.... and having a few DNS errors first before i got the caching DNS server up) Second Problem.... one of the computers is trying to hook into "battle.net" which requires a "6112 UDP" port. What I tried doing is, "natd -permanent_link udp LAN_IP:6112 0:0 6112 -interface de0" It seems to work, but three times in a row, (same day), I "lose" connection. Is something wrong with the permanent link command I did? It seems to work for at least 30 mins... then it "loses" connection. Is that the right idea? Because without that command, the "battle.net" complains that "my server is not processing UDP packets." (and it uses port 6112 packets). I can think of a few potential problems. One... sendmail. Do I need it? I killed it, still having the same email problem. Two... my DNS server is setup wrong? It seems to be working, it is just a caching server. Three.... the ISP with the Cable modem has a bad connect to battle.net. Thanks in advance guys. This is my first REAL work in FreeBSD, and I like it alot. -Carroll Kong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat May 30 12:51:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23420 for freebsd-stable-outgoing; Sat, 30 May 1998 12:51:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles195.castles.com [208.214.165.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23378 for ; Sat, 30 May 1998 12:50:50 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA06981; Sat, 30 May 1998 11:45:37 -0700 (PDT) Message-Id: <199805301845.LAA06981@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ruslan Ermilov cc: stable@FreeBSD.ORG Subject: Re: Problem installing 2.2.6 in dangerously dedicated mode In-reply-to: Your message of "Fri, 29 May 1998 12:44:27 +0300." <19980529124427.A29838@ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 11:45:36 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yesterday I tried to install FreeBSD 2.2.6-STABLE on the following hardware: > > Intel X-Series Deskside/MX Server (P90, 64Mb of ram) > PhoenixBIOS(TM) E486 Version 1.00.19.AM0 > aic7770 on-board SCSI (Bios v2.11 S3) > Seagate ST32155N (2Gb, 2049/64/32 in Adaptec's >1G geometry translation mode) > > This machine intended for use only with FreeBSD and will act as an ip-router > and dialup access server via ppp. > > So, as always, I started to install FreeBSD in `dangerously-dedicated' mode. > The installation process was smooth, but after it has finished and rebooted, > I got ``Read error'' message from FreeBSD bootblocks (start.S, I think?). "Dangerously dedicated" should probably be called "stupidly dedicated". It is almost never a better idea to use this mode than the "normal" mode. > Then I read the section 8.10 of the FAQ about dangerously dedicated mode, > in particular, about HP Netservers' BIOS weirdness, then I read the > README.386BSD and README.MACH from sys/i386/boot/biosboot, and now I have > a few questions: > > 1. When ``sysinstall'' first runs, what disk geometry it detects? > What the system bios tells or SCSI bios or ...? The geometry source varies depending on the disk and the data on the disk. The BIOS geometry may be used, as may the geometry in the MBR on the disk, as may the geometry from a hardware probe. > 2. From what I've read in README.386BSD, when I install FreeBSD in DD mode: > > | Boot 1 also contains a compiled in DOS partition table > | (in case it is at block 0), which contains a 386bsd partition starting > | at 0. This ensures that the same code can work whether or not > | boot1 is at block 0. > > What this table looks like, I wonder? > Any good pointer to the source code in sys/i386/*boot will be satisfied ;-) at the bottom of start.S -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat May 30 23:02:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09180 for freebsd-stable-outgoing; Sat, 30 May 1998 23:02:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hamptons.com (hamptons.com [204.141.112.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09166 for ; Sat, 30 May 1998 23:02:31 -0700 (PDT) (envelope-from gms@hamptons.com) Received: from [204.141.112.238] ([204.141.112.238]) by hamptons.com with ESMTP (IPAD 2.03) id 4030100 ; Sun, 31 May 1998 02:02:28 EST X-Sender: gms@mail.hamptons.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 31 May 1998 02:01:16 -0500 To: freebsd-stable@FreeBSD.ORG From: GMS Subject: subscribe Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message