From owner-freebsd-current Sun Oct 3 1:50:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id DAF7E14F84 for ; Sun, 3 Oct 1999 01:50:15 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id JAA89637; Sun, 3 Oct 1999 09:50:11 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 3 Oct 1999 09:45:41 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 3 Oct 1999 09:45:43 +0000 To: Julian Elischer From: Bob Bishop Subject: Re: panic: free vnode isn't Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 1:13 pm -0700 2/10/99, Julian Elischer wrote: >[...] >Unfortunatly with this sort of panic, the panic is correct. The actual >dammage was done some (possibly considerable) time before. So a traceback >isn't so useful. OK, so how do I proceed to get some more useful info? It's still happening. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 3:18:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id E355414C48 for ; Sun, 3 Oct 1999 03:18:32 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem34.masternet.it [194.184.65.44]) by kirk.giovannelli.it (8.9.3/8.9.3) with ESMTP id MAA21515; Sun, 3 Oct 1999 12:18:19 +0200 (CEST) (envelope-from gmarco@giovannelli.it) Message-Id: <4.2.0.58.19991003121853.012efcb0@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sun, 03 Oct 1999 12:22:55 +0200 To: current@freebsd.org From: Gianmarco Giovannelli Subject: Netscape core dump, happily :-) Cc: freebsd@masternet.it Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there anyone who is experienced Netscape crashes with 4.0-CURRENT when the close button is pressed (not always, but very often) ? It happens to me with 4.61 and 4.70 , it doesn't happen with 3.2-STABLE I have at work. Thanks ... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 3:57:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.utexas.edu (wb1-a.mail.utexas.edu [128.83.126.134]) by hub.freebsd.org (Postfix) with SMTP id 68B6014C0A for ; Sun, 3 Oct 1999 03:56:22 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: (qmail 28081 invoked from network); 3 Oct 1999 10:56:20 -0000 Received: from dial-51-54.ots.utexas.edu (HELO nomad.dataplex.net) (128.83.113.150) by umbs-smtp-1 with SMTP; 3 Oct 1999 10:56:20 -0000 From: Richard Wackerbarth To: Steve Kargl Subject: Re: new sigset_t and upgrading: a proposal Date: Sun, 3 Oct 1999 05:07:41 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <199910030505.WAA18797@troutmask.apl.washington.edu> In-Reply-To: <199910030505.WAA18797@troutmask.apl.washington.edu> Cc: current@FreeBSD.org MIME-Version: 1.0 Message-Id: <99100305544700.81357@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 03 Oct 1999, you wrote: > Richard Wackerbarth wrote: > > Why isn't the kernel BUILT automatically as a part of "buildworld"? > > Except for the fact that the object directory is in the wrong place, why isn't > > a kernel just like any other module? > > > > This may be difficult. Which kernel do you build? I use > the same source tree for two very different machines. So, > should it build GENERIC, CUSTOM1, or CUSTOM2? I suggest all of the above. If you wish otherwise, you can turn them off by adding the appropriate entries in the subdir control files (See share/mk/bsd.subdir.mk) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 4:10: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mechv.me.tuns.ca (mechv.me.TUNS.Ca [134.190.50.152]) by hub.freebsd.org (Postfix) with ESMTP id 60CD514C0A for ; Sun, 3 Oct 1999 04:10:03 -0700 (PDT) (envelope-from bbursey@mechv.me.tuns.ca) Received: from localhost (bbursey@localhost) by mechv.me.tuns.ca (8.8.8/8.8.5) with SMTP id IAA21931 for ; Sun, 3 Oct 1999 08:09:49 -0300 (ADT) Date: Sun, 3 Oct 1999 08:09:49 -0300 (ADT) From: Bryan Bursey To: current@FreeBSD.ORG Subject: Issues with xl0 In-Reply-To: <37F6EC46.5C7E4EA4@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I attempted to move from -STABLE to -CURRENT last night, but without any luck. I decided to start with a current snapshot (19990928), but was unable to install using the floppies provided on releng3.freebsd.org. Thinking it might have been a floppy issue, I used my 3.3-STABLE floppies and simply changed the install options so that I'd get 4.0. This worked until I restarted my machine at the end of the install. It came back up ok, but I was again unable to connect to the network. Can anyone tell me if there are known issues with the xl0 driver in 4.0, or if it has been superceded by another driver which works with 3Com 3C900B. Thanks for any help (or other random thoughts). Cheers, Bryan ________________________________ Bryan Bursey, DEng Dept. of Mechanical Engineering DalTech (TUNS) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 5:20:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 96FB314CA3; Sun, 3 Oct 1999 05:20:10 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id NAA32518; Sun, 3 Oct 1999 13:24:11 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 3 Oct 1999 13:24:11 +0100 (BST) From: Doug Rabson To: Thomas David Rivers Cc: jdp@polstra.com, obrien@freebsd.org, alc@cs.rice.edu, current@freebsd.org Subject: Re: Now that sigcontext is gone ... In-Reply-To: <199910022104.RAA07287@lakes.dignus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 2 Oct 1999, Thomas David Rivers wrote: > > > > > Just how much code will break? > > > > Boehm-gc, maybe. Modula-3, maybe. I can't remember whether it > > catches both signals or just SIGBUS. > > I believe electric-fence would change as well. It would change (by removing a freebsd-specific patch I think). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 6:36:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id BFA6D14CBF for ; Sun, 3 Oct 1999 06:36:46 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id GAA10018; Sun, 3 Oct 1999 06:36:43 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199910031336.GAA10018@freeway.dcfinc.com> Subject: Re: New CVSup mirror sites In-Reply-To: from John Polstra at "Oct 2, 99 05:48:35 pm" To: jdp@polstra.com (John Polstra) Date: Sun, 3 Oct 1999 06:36:42 -0700 (MST) Cc: current@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, John Polstra wrote: > In the US, cvsup[1-3] are very busy; clients get turned away from them > on a regular basis because they are already at their limit. The other > 4 mirrors are practically idle in comparison. These are all screaming > fast, well-connected, well-maintained mirrors. Give them a try if you > haven't already! I've been using cvsup5 for some time now. And yes, it screams. John, do you have usage statistics broken out for each server? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 7:46:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 62A5114A2E for ; Sun, 3 Oct 1999 07:46:43 -0700 (PDT) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id KAA00281 for ; Sun, 3 Oct 1999 10:45:39 -0400 (EDT) (envelope-from culverk@culverk.student.umd.edu) Date: Sun, 3 Oct 1999 10:45:39 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: ata driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alright, this is the dmesg that Soren asked for to help with the timeout problem. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Sun Oct 3 10:43:26 EDT 1999 culverk@culverk.student.umd.edu:/usr/src/sys/compile/MYKERNEL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134152192 (131008K bytes) avail memory = 127344640 (124360K bytes) Preloaded elf kernel "kernel" at 0xc029f000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: irq 11 at device 7.2 on pci0 intpm0: at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 pci0: unknown card (vendor=0x121a, dev=0x0002) at 13.0 pci0: unknown card (vendor=0x121a, dev=0x0002) at 15.0 bktr0: irq 9 at device 17.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus1: on bti2c0 smb1: on smbus1 bktr0: Hauppauge Model 61291 D110 Hauppauge WinCast/TV, Philips NTSC tuner, remote control. pci0: unknown card (vendor=0x109e, dev=0x0878) at 17.1 irq 9 de0: irq 10 at device 19.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:1f:21:02 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 vpo0: on ppbus 0 vpo0: EPP 1.9 mode sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: isa_compat: didn't get drq for sbxvi sbxvi0 at port 0xffffffff drq 1 on isa0 isa_compat: didn't get ports for sbxvi isa_compat: didn't get drq for sbxvi snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] sbmidi0 at port 0x330 on isa0 snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] opl0 at port 0x388 on isa0 snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] ad0: ATA-4 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ad1: ATA-3 disk at ata0 as slave ad1: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad1 Creating DISK wd1 ad2: ATA-3 disk at ata1 as master ad2: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad2 Creating DISK wd2 acd0: CDROM drive at ata1 as slave , 128KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data/audio disc loaded, unlocked Creating DISK da0 da0 at vpo0 bus 0 target 6 lun 0 da0: Removable Direct Access SCSI-2 device da0: Attempt to query device size failed: NOT READY, Medium not present changing root device to wd1s1a de0: enabling 10baseT port Thanks Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 8:23:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from umd5.umd.edu (umd5.umd.edu [128.8.10.5]) by hub.freebsd.org (Postfix) with ESMTP id E885614DE0 for ; Sun, 3 Oct 1999 08:23:09 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from wolfe.umd.edu (wolfe.umd.edu [128.8.10.52]) by umd5.umd.edu (8.9.1/8.9.1) with ESMTP id LAA08912; Sun, 3 Oct 1999 11:22:50 -0400 (EDT) Received: from localhost (howardjp@localhost) by wolfe.umd.edu (8.9.1/8.9.1) with SMTP id LAA19653; Sun, 3 Oct 1999 11:22:50 -0400 (EDT) X-Authentication-Warning: wolfe.umd.edu: howardjp owned process doing -bs Date: Sun, 3 Oct 1999 11:22:50 -0400 (EDT) From: James Howard X-Sender: howardjp@wolfe.umd.edu To: Gianmarco Giovannelli Cc: current@FreeBSD.ORG, freebsd@masternet.it Subject: Re: Netscape core dump, happily :-) In-Reply-To: <4.2.0.58.19991003121853.012efcb0@194.184.65.4> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 3 Oct 1999, Gianmarco Giovannelli wrote: > Is there anyone who is experienced Netscape crashes with 4.0-CURRENT when > the close button is pressed (not always, but very often) ? > It happens to me with 4.61 and 4.70 , it doesn't happen with 3.2-STABLE I > have at work. I have had problems using the combination of Netscape 4.61, Afterstep 1.7.25, and Slashdot. Nearly every other click will cause Netscape to crash whereas if I change the browser, the website, or the WM, I have no problems at all. Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 8:27: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from filer4.isc.rit.edu (filer4.isc.rit.edu [129.21.3.73]) by hub.freebsd.org (Postfix) with ESMTP id ECC2A14DE0 for ; Sun, 3 Oct 1999 08:26:58 -0700 (PDT) (envelope-from jcptch@osfmail.isc.rit.edu) Received: from grace ("port 3703"@[129.21.3.102]) by osfmail.isc.rit.edu (PMDF V5.2-32 #21576) with SMTP id <0FJ1007TP9ICQA@osfmail.isc.rit.edu> for current@freebsd.org; Sun, 3 Oct 1999 11:25:24 -0400 (EDT) Received: by grace (5.65v4.0/1.1.19.2/21Sep98-0910AM) id AA27542; Sun, 03 Oct 1999 11:25:23 -0400 Date: Sun, 03 Oct 1999 11:25:23 -0400 From: Jon Parise Subject: Re: Netscape core dump, happily :-) In-reply-to: <4.2.0.58.19991003121853.012efcb0@194.184.65.4>; from gmarco@giovannelli.it on Sun, Oct 03, 1999 at 12:22:55PM +0200 To: current@freebsd.org Mail-followup-to: current@freebsd.org Message-id: <19991003112523.A27331@osfmail.isc.rit.edu> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i X-Operating-System: OSF1 V4.0 (alpha) References: <4.2.0.58.19991003121853.012efcb0@194.184.65.4> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 03, 1999 at 12:22:55PM +0200, Gianmarco Giovannelli wrote: > Is there anyone who is experienced Netscape crashes with 4.0-CURRENT when > the close button is pressed (not always, but very often) ? > It happens to me with 4.61 and 4.70 , it doesn't happen with 3.2-STABLE I > have at work. Yes, I've been experiencing that as well. It writes a zero length core file in my home directory and exits with signal 10: Oct 1 16:20:53 void /kernel: pid 18518 (navigator-4.61.b), uid 1000: exited on signal 10 It's incredibly annoying, but I haven't bothered to track it down in any great detail. -- Jon Parise (parise@pobox.com) . Rochester Inst. of Technology http://www.pobox.com/~parise/ : Computer Science House Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 9:43:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 8BEF414BE3 for ; Sun, 3 Oct 1999 09:43:27 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem04.masternet.it [194.184.65.14]) by scotty.masternet.it (8.9.3/8.9.3) with ESMTP id SAA83303; Sun, 3 Oct 1999 18:43:01 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.2.0.58.19991003184312.01301f00@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sun, 03 Oct 1999 18:47:16 +0200 To: James Howard From: Gianmarco Giovannelli Subject: Re: Netscape core dump, happily :-) Cc: current@FreeBSD.ORG In-Reply-To: References: <4.2.0.58.19991003121853.012efcb0@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03/10/99, James Howard wrote: >On Sun, 3 Oct 1999, Gianmarco Giovannelli wrote: > > > Is there anyone who is experienced Netscape crashes with 4.0-CURRENT when > > the close button is pressed (not always, but very often) ? > > It happens to me with 4.61 and 4.70 , it doesn't happen with 3.2-STABLE I > > have at work. > >I have had problems using the combination of Netscape 4.61, Afterstep >1.7.25, and Slashdot. Nearly every other click will cause Netscape to >crash whereas if I change the browser, the website, or the WM, I have no >problems at all. I am using Xaccel 5.0.2 with windowmaker 0.61 but my crashes happening also on local file browsing ... It is very annoying because when you begin to surf you always open multiple window and you can't close them without the fear to crash everything (with downloads too)... I am using the FreeBSD version, perhaps the other versions (linux, bsdi) are immune... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 9:47: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id CEE4014EA3 for ; Sun, 3 Oct 1999 09:46:58 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from vigrid.com (pm3-pt44.pcnet.net [206.105.29.118]) by pcnet1.pcnet.com (8.8.7/PCNet) with ESMTP id MAA26401; Sun, 3 Oct 1999 12:45:45 -0400 (EDT) Message-ID: <37F78874.F7B86582@vigrid.com> Date: Sun, 03 Oct 1999 12:46:44 -0400 From: "Daniel M. Eischen" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug Rabson Cc: freebsd-current@freebsd.org, winter@jurai.net Subject: Re: Recent kernel hangs during boot with pnp sio. References: <37F667B5.C09E163D@vigrid.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen wrote: > OK, I originally did that to no avail, but I didn't make the change to > the correct file (sys/isa/sio.c, not sys/dev/sio/sio.c)! So with the > following change: > > Index: sio.c > =================================================================== > RCS file: /opt/b/CVS/src/sys/isa/sio.c,v > retrieving revision 1.268 > diff -u -r1.268 sio.c > --- sio.c 1999/09/25 18:24:21 1.268 > +++ sio.c 1999/10/02 21:54:33 > @@ -568,6 +568,7 @@ > {0x1005d041, "Generic IRDA-compatible device"}, /* PNP0510 */ > {0x1105d041, "Generic IRDA-compatible device"}, /* PNP0511 */ > {0x31307256, "USR3031"}, /* USR3031 */ > + {0x8024b04e, "SupraExpress 56i Sp V.90"}, > {0} > }; > > the modem is detected as: > > sio-1: irq maps: 0x801 0x821 0x801 0x801 > sio3: at port 0x3e8-0x3ef irq 5 on isa0 > sio3: type 16550A Who's responsible for sio.c? Can I commit this change? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 9:50: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 77BF114EA3 for ; Sun, 3 Oct 1999 09:50:05 -0700 (PDT) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1002) id 1E70A97; Sun, 3 Oct 1999 09:50:05 -0700 (PDT) Date: Sun, 3 Oct 1999 09:50:05 -0700 From: Chris Piazza To: Jon Parise Cc: current@FreeBSD.ORG Subject: Re: Netscape core dump, happily :-) Message-ID: <19991003095005.K244@norn.ca.eu.org> References: <4.2.0.58.19991003121853.012efcb0@194.184.65.4> <19991003112523.A27331@osfmail.isc.rit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <19991003112523.A27331@osfmail.isc.rit.edu> X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 03, 1999 at 11:25:23AM -0400, Jon Parise wrote: > On Sun, Oct 03, 1999 at 12:22:55PM +0200, Gianmarco Giovannelli wrote: > > > Is there anyone who is experienced Netscape crashes with 4.0-CURRENT when > > the close button is pressed (not always, but very often) ? > > It happens to me with 4.61 and 4.70 , it doesn't happen with 3.2-STABLE I > > have at work. > > Yes, I've been experiencing that as well. It writes a zero length > core file in my home directory and exits with signal 10: > > Oct 1 16:20:53 void /kernel: pid 18518 (navigator-4.61.b), uid > 1000: exited on signal 10 > > It's incredibly annoying, but I haven't bothered to track it down > in any great detail. Disable Javascript and the problem will go away (ugh). I once had it crash over 30 times in a single day. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 9:54:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 0D3B814F52 for ; Sun, 3 Oct 1999 09:54:10 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id MAA12275; Sun, 3 Oct 1999 12:53:55 -0400 (EDT) Message-ID: <19991003125355.A11241@netmonger.net> Date: Sun, 3 Oct 1999 12:53:55 -0400 From: Christopher Masto To: current@freebsd.org, grog@lemis.com Subject: Can't start vinum with new kernels Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to do the latest "install kernel before building world" trick, and I'm running into some major problems getting vinum running. Basically, when I boot a new kernel (with new modules installed.. I didn't forget that), "vinum start" fails with "Can't allocate memory for drive list". At first I thought maybe I'd just picked a bad time to cvsup, but I've since tried it twice more and have the same problem. After futzing around with it for a while, I found that I was able to "vinum read /dev/daX" (though variations like "vinum read /dev/daXs1e", "vinum read daXs1e", and "vinum read daX" failed (unfortunately I don't have the exact message here, but I can reproduce it)). Although I was able to get the volumes back up by doing a "vinum read" on each of my drives, I ended up with a kernel panic when I tried to fsck them. Booting with the old kernel and module, everything still works fine. I'm currently wiping out /usr/src and /usr/obj just in case, and if that doesn't work I'll try to trace the code. I'm sending this now in case someone can say "you're doing this wrong, you idiot" and save me the time. I've appended some config information. Some of the subdisks are listed as "reborn" because as I mentioned abuve, I was playing with "vinum read". This is from a successful boot with the old kernel: Configuration summary Drives: 4 (8 configured) Volumes: 5 (8 configured) Plexes: 10 (16 configured) Subdisks: 10 (16 configured) D drive0 State: up Device /dev/da0s1e Avail: 0/7659 MB (0%) D drive2 State: up Device /dev/da1s1e Avail: 0/8683 MB (0%) D drive1 State: up Device /dev/da2s1e Avail: 0/7659 MB (0%) D drive3 State: up Device /dev/da3s1e Avail: 0/8683 MB (0%) V usr State: up Plexes: 2 Size: 2048 MB V var State: up Plexes: 2 Size: 512 MB V usr_local State: up Plexes: 2 Size: 5099 MB V var_mail State: up Plexes: 2 Size: 2048 MB V home State: up Plexes: 2 Size: 6635 MB P usr.p0 C State: up Subdisks: 1 Size: 2048 MB P usr.p1 C State: flaky Subdisks: 1 Size: 2048 MB P var.p0 C State: up Subdisks: 1 Size: 512 MB P var.p1 C State: flaky Subdisks: 1 Size: 512 MB P usr_local.p0 C State: up Subdisks: 1 Size: 5099 MB P usr_local.p1 C State: flaky Subdisks: 1 Size: 5099 MB P var_mail.p0 C State: up Subdisks: 1 Size: 2048 MB P var_mail.p1 C State: flaky Subdisks: 1 Size: 2048 MB P home.p0 C State: up Subdisks: 1 Size: 6635 MB P home.p1 C State: flaky Subdisks: 1 Size: 6635 MB S usr.p0.s0 State: up PO: 0 B Size: 2048 MB S usr.p1.s0 State: reborn PO: 0 B Size: 2048 MB S var.p0.s0 State: up PO: 0 B Size: 512 MB S var.p1.s0 State: reborn PO: 0 B Size: 512 MB S usr_local.p0.s0 State: up PO: 0 B Size: 5099 MB S usr_local.p1.s0 State: reborn PO: 0 B Size: 5099 MB S var_mail.p0.s0 State: up PO: 0 B Size: 2048 MB S var_mail.p1.s0 State: reborn PO: 0 B Size: 2048 MB S home.p0.s0 State: up PO: 0 B Size: 6635 MB S home.p1.s0 State: reborn PO: 0 B Size: 6635 MB /dev/da0s1a on / (local, soft-updates, writes: sync 3 async 122) /dev/vinum/home on /home (local, soft-updates, writes: sync 10 async 25) /dev/vinum/var on /var (local, soft-updates, writes: sync 107 async 256) /dev/vinum/var_mail on /var/mail (local, soft-updates, writes: sync 2 async= 0) /dev/vinum/usr on /usr (local, soft-updates, writes: sync 303 async 18984) /dev/vinum/usr_local on /usr/local (local, soft-updates, writes: sync 14 as= ync 2475) procfs on /proc (local) Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Aug 30 12:46:10 EDT 1999 root@wensleydale.netmonger.net:/usr/src/sys/compile/WENSLEYDALE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (397.95-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x652 Stepping =3D 2 Features=3D0x183fbff real memory =3D 268427264 (262136K bytes) avail memory =3D 257097728 (251072K bytes) Preloaded elf kernel "kernel.ok" at 0xc0317000. VESA: v2.0, 2048k memory, flags:0x0, mode table:0xc02c0b62 (1000022) VESA: ATI MACH64 Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: at device 0.0 on pci1 pcib2: at device 2.0 on p= ci0 pci2: on pcib2 ahc0: irq 14 at device 11.0 on pci2 BRDCTL =3D 0x2 ahc0: aic7890/91 Wide Channel A, SCSI Id=3D7, 16/255 SCBs isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x0170 irq 15 on ata-pci0 uhci0: irq 14 at device 7.2 on pc= i0 usb0: on uhci0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: at device 7.3 on pci0 intpm0: I/O mapped 850 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 800=20 fxp0: irq 11 at device 13.0 on pc= i0 fxp0: Ethernet address 00:90:27:b1:06:d1 ahc1: irq 10 at device 14.0 on pci0 BRDCTL =3D 0xc ahc1: aic7896/97 Wide Channel A, SCSI Id=3D7, 16/255 SCBs ahc2: irq 10 at device 14.1 on pci0 BRDCTL =3D 0xc ahc2: aic7896/97 Wide Channel B, SCSI Id=3D7, 16/255 SCBs Probing for PnP devices: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=3D0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 IP packet filtering initialized, divert enabled, rule-based forwarding disa= bled, logging limited to 100 packets/entry by default atapi: piomode=3D4, dmamode=3D2, udmamode=3D-1 ata0: master: setting up WDMA2 mode on PIIX3/4 chip OK atapi: DMA transfer mode set acd0: CDROM drive at ata0 as master acd0: drive speed 2412KB/sec, 128KB cache, DMA acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Waiting 2 seconds for SCSI devices to settle da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device=20 da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing En= abled da0: 8683MB (17783249 512 byte sectors: 255H 63S/T 1106C) da2 at ahc2 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI-3 device=20 da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing En= abled da2: 8683MB (17783249 512 byte sectors: 255H 63S/T 1106C) da3 at ahc2 bus 0 target 1 lun 0 da3: Fixed Direct Access SCSI-3 device=20 da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing En= abled da3: 8683MB (17783249 512 byte sectors: 255H 63S/T 1106C) da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device=20 da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing En= abled da1: 8683MB (17783249 512 byte sectors: 255H 63S/T 1106C) changing root device to da0s1a vinum: loaded vinum: reading configuration from /dev/da1s1e vinum: updating configuration from /dev/da2s1e vinum: updating configuration from /dev/da3s1e vinum: updating configuration from /dev/da0s1e dd results: IN VINOwensleydale.netmonger.netdrive09}7=177I7WEV<& Y=0Fvolume usr state = up volume var state up volume usr_local state up volume var_mail state up volume home state up plex name usr.p0 state up org concat vol usr=20 plex name usr.p1 state flaky org concat vol usr=20 plex name var.p0 state up org concat vol var=20 plex name var.p1 state flaky org concat vol var=20 plex name usr_local.p0 state up org concat vol usr_local=20 plex name usr_local.p1 state flaky org concat vol usr_local=20 plex name var_mail.p0 state up org concat vol var_mail=20 plex name var_mail.p1 state flaky org concat vol var_mail=20 plex name home.p0 state up org concat vol home=20 plex name home.p1 state flaky org concat vol home=20 sd name usr.p0.s0 drive drive0 plex usr.p0 state up len 4194304s driveoffse= t 265s plexoffset 0s sd name usr.p1.s0 drive drive1 plex usr.p1 state reborn len 4194304s driveo= ffset 265s plexoffset 0s sd name var.p0.s0 drive drive0 plex var.p0 state up len 1048576s driveoffse= t 4194569s plexoffset 0s sd name var.p1.s0 drive drive1 plex var.p1 state reborn len 1048576s driveo= ffset 4194569s plexoffset 0s sd name usr_local.p0.s0 drive drive0 plex usr_local.p0 state up len 1044275= 2s driveoffset 5243145s plexoffset 0s sd name usr_local.p1.s0 drive drive1 plex usr_local.p1 state reborn len 104= 42752s driveoffset 5243145s plexoffset 0s sd name var_mail.p0.s0 drive drive2 plex var_mail.p0 state up len 4194304s = driveoffset 265s plexoffset 0s sd name var_mail.p1.s0 drive drive3 plex var_mail.p1 state reborn len 41943= 04s driveoffset 265s plexoffset 0s sd name home.p0.s0 drive drive2 plex home.p0 state up len 13588480s driveof= fset 4194569s plexoffset 0s sd name home.p1.s0 drive drive3 plex home.p1 state reborn len 13588480s dri= veoffset 4194569s plexoffset 0s IN VINOwensleydale.netmonger.netdrive2V77I7=1EWEV<& Y=0Fvolume usr state up volume var state up volume usr_local state up volume var_mail state up volume home state up plex name usr.p0 state up org concat vol usr=20 plex name usr.p1 state flaky org concat vol usr=20 plex name var.p0 state up org concat vol var=20 plex name var.p1 state flaky org concat vol var=20 plex name usr_local.p0 state up org concat vol usr_local=20 plex name usr_local.p1 state flaky org concat vol usr_local=20 plex name var_mail.p0 state up org concat vol var_mail=20 plex name var_mail.p1 state flaky org concat vol var_mail=20 plex name home.p0 state up org concat vol home=20 plex name home.p1 state flaky org concat vol home=20 sd name usr.p0.s0 drive drive0 plex usr.p0 state up len 4194304s driveoffse= t 265s plexoffset 0s sd name usr.p1.s0 drive drive1 plex usr.p1 state reborn len 4194304s driveo= ffset 265s plexoffset 0s sd name var.p0.s0 drive drive0 plex var.p0 state up len 1048576s driveoffse= t 4194569s plexoffset 0s sd name var.p1.s0 drive drive1 plex var.p1 state reborn len 1048576s driveo= ffset 4194569s plexoffset 0s sd name usr_local.p0.s0 drive drive0 plex usr_local.p0 state up len 1044275= 2s driveoffset 5243145s plexoffset 0s sd name usr_local.p1.s0 drive drive1 plex usr_local.p1 state reborn len 104= 42752s driveoffset 5243145s plexoffset 0s sd name var_mail.p0.s0 drive drive2 plex var_mail.p0 state up len 4194304s = driveoffset 265s plexoffset 0s sd name var_mail.p1.s0 drive drive3 plex var_mail.p1 state reborn len 41943= 04s driveoffset 265s plexoffset 0s sd name home.p0.s0 drive drive2 plex home.p0 state up len 13588480s driveof= fset 4194569s plexoffset 0s sd name home.p1.s0 drive drive3 plex home.p1 state reborn len 13588480s dri= veoffset 4194569s plexoffset 0s IN VINOwensleydale.netmonger.netdrive19}7(7I7WEV<& Y=0Fvolume usr state up volume var state up volume usr_local state up volume var_mail state up volume home state up plex name usr.p0 state up org concat vol usr=20 plex name usr.p1 state flaky org concat vol usr=20 plex name var.p0 state up org concat vol var=20 plex name var.p1 state flaky org concat vol var=20 plex name usr_local.p0 state up org concat vol usr_local=20 plex name usr_local.p1 state flaky org concat vol usr_local=20 plex name var_mail.p0 state up org concat vol var_mail=20 plex name var_mail.p1 state flaky org concat vol var_mail=20 plex name home.p0 state up org concat vol home=20 plex name home.p1 state flaky org concat vol home=20 sd name usr.p0.s0 drive drive0 plex usr.p0 state up len 4194304s driveoffse= t 265s plexoffset 0s sd name usr.p1.s0 drive drive1 plex usr.p1 state reborn len 4194304s driveo= ffset 265s plexoffset 0s sd name var.p0.s0 drive drive0 plex var.p0 state up len 1048576s driveoffse= t 4194569s plexoffset 0s sd name var.p1.s0 drive drive1 plex var.p1 state reborn len 1048576s driveo= ffset 4194569s plexoffset 0s sd name usr_local.p0.s0 drive drive0 plex usr_local.p0 state up len 1044275= 2s driveoffset 5243145s plexoffset 0s sd name usr_local.p1.s0 drive drive1 plex usr_local.p1 state reborn len 104= 42752s driveoffset 5243145s plexoffset 0s sd name var_mail.p0.s0 drive drive2 plex var_mail.p0 state up len 4194304s = driveoffset 265s plexoffset 0s sd name var_mail.p1.s0 drive drive3 plex var_mail.p1 state reborn len 41943= 04s driveoffset 265s plexoffset 0s sd name home.p0.s0 drive drive2 plex home.p0 state up len 13588480s driveof= fset 4194569s plexoffset 0s sd name home.p1.s0 drive drive3 plex home.p1 state reborn len 13588480s dri= veoffset 4194569s plexoffset 0s IN VINOwensleydale.netmonger.netdrive3V77I7=1EWEV<& Y=0Fvolume usr state up volume var state up volume usr_local state up volume var_mail state up volume home state up plex name usr.p0 state up org concat vol usr=20 plex name usr.p1 state flaky org concat vol usr=20 plex name var.p0 state up org concat vol var=20 plex name var.p1 state flaky org concat vol var=20 plex name usr_local.p0 state up org concat vol usr_local=20 plex name usr_local.p1 state flaky org concat vol usr_local=20 plex name var_mail.p0 state up org concat vol var_mail=20 plex name var_mail.p1 state flaky org concat vol var_mail=20 plex name home.p0 state up org concat vol home=20 plex name home.p1 state flaky org concat vol home=20 sd name usr.p0.s0 drive drive0 plex usr.p0 state up len 4194304s driveoffse= t 265s plexoffset 0s sd name usr.p1.s0 drive drive1 plex usr.p1 state reborn len 4194304s driveo= ffset 265s plexoffset 0s sd name var.p0.s0 drive drive0 plex var.p0 state up len 1048576s driveoffse= t 4194569s plexoffset 0s sd name var.p1.s0 drive drive1 plex var.p1 state reborn len 1048576s driveo= ffset 4194569s plexoffset 0s sd name usr_local.p0.s0 drive drive0 plex usr_local.p0 state up len 1044275= 2s driveoffset 5243145s plexoffset 0s sd name usr_local.p1.s0 drive drive1 plex usr_local.p1 state reborn len 104= 42752s driveoffset 5243145s plexoffset 0s sd name var_mail.p0.s0 drive drive2 plex var_mail.p0 state up len 4194304s = driveoffset 265s plexoffset 0s sd name var_mail.p1.s0 drive drive3 plex var_mail.p1 state reborn len 41943= 04s driveoffset 265s plexoffset 0s sd name home.p0.s0 drive drive2 plex home.p0 state up len 13588480s driveof= fset 4194569s plexoffset 0s sd name home.p1.s0 drive drive3 plex home.p1 state reborn len 13588480s dri= veoffset 4194569s plexoffset 0s Here's the config file: machine i386 cpu I686_CPU ident WENSLEYDALE maxusers 100 #makeoptions DEBUG=3D-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=3D2 # number of CPUs #options NBUS=3D4 # number of busses #options NAPIC=3D1 # number of IO APICs #options NINTR=3D24 # number of INTs controller isa0 controller pnp0 # PnP support for ISA controller eisa0 controller pci0 # Floppy drives controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 # IDE/ATAPI devices controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives device atapifd0 # ATAPI floppy drives device atapist0 # ATAPI tape drives # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. controller ahc0 # AHA2940 and onboard AIC7xxx devices options AHC_ALLOW_MEMIO # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. controller scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? flags 0x0 # Advanced Power Management # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 # Printer device plip0 # TCP/IP over parallel device ppi0 # Parallel port interface device #controller vpo0 # Requires scbus and da0 # MII bus support, required for some 10/100 NICs controller miibus0 # PCI Ethernet NICs. device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel, for ppp(1) pseudo-device pty 256 # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's pseudo-device snp 3 # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support controller uhci0 # UHCI PCI->USB interface controller usb0 # USB Bus (required) device ugen0 # Generic device uhid0 # "Human Interface Devices" device ukbd0 # Keyboard device ulpt0 # Printer controller umass0 # Disks/Mass storage - Requires scbus and da0 device ums0 # Mouse # SMBUS stuff controller smbus0 controller intpm0 device smb0 at smbus? controller iicbus0 controller iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? options SOFTUPDATES options NETATALK options VESA options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=3D100 options IPDIVERT options ICMP_BANDLIM options QUOTA options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=3D199309L options MSGBUF_SIZE=3D40960 --=20 Christopher Masto Senior Network Monkey NetMonger Communicatio= ns chris@netmonger.net info@netmonger.net http://www.netmonger.n= et Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 9:56:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 4C7F4152A5 for ; Sun, 3 Oct 1999 09:56:21 -0700 (PDT) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=mistress) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11XoxD-0009sF-00 for freebsd-current@freebsd.org; Sun, 3 Oct 1999 16:57:43 +0000 Date: Sun, 3 Oct 1999 18:56:22 +0200 (CEST) From: Marc Schneiders To: freebsd-current@freebsd.org Subject: buildworld fails in gcc Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make installworld on freshly cvsupped current (today 18:00 h CET) source fails here in libgcc. Output: c++ -c -I/usr/obj/usr/src/tmp/usr/include/g++ -O -pipe -I/usr/src/gnu/lib/libgcc /../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/inc -nostdinc++ -DL_op_newnt -o_op_newnt.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc In file included from /usr/obj/usr/src/tmp/usr/include/g++/new:9, from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: /usr/obj/usr/src/tmp/usr/include/g++/exception:17: Internal compiler error 197. /usr/obj/usr/src/tmp/usr/include/g++/exception:17: Please submit a full bug report to `egcs-bugs@egcs.cygnus.com'. /usr/obj/usr/src/tmp/usr/include/g++/exception:17: See for details. *** Error code 1 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 -- Marc Schneiders marc@venster.nl marc@oldserver.demon.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 10:27:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 30DCB14CEA for ; Sun, 3 Oct 1999 10:27:35 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id SAA29916; Sun, 3 Oct 1999 18:29:08 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 3 Oct 1999 18:29:08 +0100 (BST) From: Doug Rabson To: "Daniel M. Eischen" Cc: freebsd-current@freebsd.org, winter@jurai.net Subject: Re: Recent kernel hangs during boot with pnp sio. In-Reply-To: <37F78874.F7B86582@vigrid.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 3 Oct 1999, Daniel M. Eischen wrote: > Daniel Eischen wrote: > > OK, I originally did that to no avail, but I didn't make the change to > > the correct file (sys/isa/sio.c, not sys/dev/sio/sio.c)! So with the > > following change: > > > > Index: sio.c > > =================================================================== > > RCS file: /opt/b/CVS/src/sys/isa/sio.c,v > > retrieving revision 1.268 > > diff -u -r1.268 sio.c > > --- sio.c 1999/09/25 18:24:21 1.268 > > +++ sio.c 1999/10/02 21:54:33 > > @@ -568,6 +568,7 @@ > > {0x1005d041, "Generic IRDA-compatible device"}, /* PNP0510 */ > > {0x1105d041, "Generic IRDA-compatible device"}, /* PNP0511 */ > > {0x31307256, "USR3031"}, /* USR3031 */ > > + {0x8024b04e, "SupraExpress 56i Sp V.90"}, > > {0} > > }; > > > > the modem is detected as: > > > > sio-1: irq maps: 0x801 0x821 0x801 0x801 > > sio3: at port 0x3e8-0x3ef irq 5 on isa0 > > sio3: type 16550A > > Who's responsible for sio.c? Can I commit this change? I think you should commit the change. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 10:33:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id BEC7814CEA for ; Sun, 3 Oct 1999 10:33:01 -0700 (PDT) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id TAA05691 for freebsd-current@freebsd.org; Sun, 3 Oct 1999 19:32:55 +0200 (CEST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id TAA57698 for freebsd-current@freebsd.org; Sun, 3 Oct 1999 19:29:41 +0200 (CEST) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: Netscape core dump, happily :-) Date: 3 Oct 1999 19:29:40 +0200 Message-ID: <7t83q4$1oan$1@bigeye.rhein-neckar.de> References: <4.2.0.58.19991003121853.012efcb0@194.184.65.4> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gianmarco Giovannelli wrote: > Is there anyone who is experienced Netscape crashes with 4.0-CURRENT when > the close button is pressed (not always, but very often) ? Same here. Navigator 4.61. Previous versions didn't show this behavior. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 11: 1: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 4D68C1521F for ; Sun, 3 Oct 1999 11:00:59 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac9.wam.umd.edu (root@rac9.wam.umd.edu [128.8.10.149]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA00829; Sun, 3 Oct 1999 14:00:55 -0400 (EDT) Received: from rac9.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac9.wam.umd.edu (8.9.3/8.9.3) with SMTP id OAA17493; Sun, 3 Oct 1999 14:00:49 -0400 (EDT) Received: from localhost (culverk@localhost) by rac9.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA17486; Sun, 3 Oct 1999 14:00:49 -0400 (EDT) X-Authentication-Warning: rac9.wam.umd.edu: culverk owned process doing -bs Date: Sun, 3 Oct 1999 14:00:49 -0400 (EDT) From: Kenneth Wayne Culver To: Jon Parise Cc: current@FreeBSD.ORG Subject: Re: Netscape core dump, happily :-) In-Reply-To: <19991003112523.A27331@osfmail.isc.rit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's odd, I have not been able to make netscape crash. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 3 Oct 1999, Jon Parise wrote: > On Sun, Oct 03, 1999 at 12:22:55PM +0200, Gianmarco Giovannelli wrote: > > > Is there anyone who is experienced Netscape crashes with 4.0-CURRENT when > > the close button is pressed (not always, but very often) ? > > It happens to me with 4.61 and 4.70 , it doesn't happen with 3.2-STABLE I > > have at work. > > Yes, I've been experiencing that as well. It writes a zero length > core file in my home directory and exits with signal 10: > > Oct 1 16:20:53 void /kernel: pid 18518 (navigator-4.61.b), uid > 1000: exited on signal 10 > > It's incredibly annoying, but I haven't bothered to track it down > in any great detail. > > -- > Jon Parise (parise@pobox.com) . Rochester Inst. of Technology > http://www.pobox.com/~parise/ : Computer Science House Member > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 11: 7:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from chain.freebsd.os.org.za (chain.freebsd.os.org.za [196.7.74.174]) by hub.freebsd.org (Postfix) with ESMTP id 901EE14DC7 for ; Sun, 3 Oct 1999 11:07:35 -0700 (PDT) (envelope-from khetan@chain.freebsd.os.org.za) X-Disclaimer: Contents of this e-mail are the writer's opinion X-Disclaimer2: and may not be quoted, re-produced or forwarded X-Disclaimer3: (in part or whole) without the author's permission. Received: from localhost (khetan@localhost) by chain.freebsd.os.org.za (8.9.3/8.9.3) with ESMTP id UAA02163 for ; Sun, 3 Oct 1999 20:07:33 +0200 (SAST) (envelope-from khetan@chain.freebsd.os.org.za) Date: Sun, 3 Oct 1999 20:07:33 +0200 (SAST) From: Khetan Gajjar Reply-To: Khetan Gajjar To: current@freebsd.org Subject: Trap 12's with various programs over the last 4 weeks Message-ID: X-Mobile: +27 82 9907663 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. In the last three weeks, I've been encountering trap 12 panics caused apparently by different programs, which is odd because this system has been running -current without a hiccup for at least a year. This occurs with a system built after Marcel's sigset_t changes, and manages to make world in single user mode, which makes me question hardware failure. I've included the output from gdb -k kernel.6 vmcore.6 and the dmesg output. If anything else needs to be done to diagnose this kind of crash, please let me know. I've had it crash due to gunzip and cron as well. In most cases, the machine is not in use, and it occurs at night. I rebuilt X as well. AMD and NFS are running, but are not used. The system is a Pentium I 200 with 114MB RAM, 3 IDE drives (using Soren's ATA code), an Adaptec 1542 which has two CD-ROM drives attached and softupdates enabled on two partitions. There is a Vibra 16 sound card, but this hasn't worked since newpcm. TIA. GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 3534848 initial pcb at 297a00 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0x22b274c0 stack pointer = 0x10:0xc985bc18 frame pointer = 0x10:0xc985bca8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0216340 stack pointer = 0x10:0xc985ba90 frame pointer = 0x10:0xc985ba94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0x22b274c0 stack pointer = 0x10:0xc985bc18 frame pointer = 0x10:0xc985bca8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0216340 stack pointer = 0x10:0xc985ba90 frame pointer = 0x10:0xc985ba94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0x22b274c0 stack pointer = 0x10:0xc985bc18 frame pointer = 0x10:0xc985bca8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0216340 stack pointer = 0x10:0xc985ba90 frame pointer = 0x10:0xc985ba94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0x22b274c0 stack pointer = 0x10:0xc985bc18 frame pointer = 0x10:0xc985bca8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0216340 stack pointer = 0x10:0xc985ba90 frame pointer = 0x10:0xc985ba94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0x22b274c0 stack pointer = 0x10:0xc985bc18 frame pointer = 0x10:0xc985bca8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0216340 stack pointer = 0x10:0xc985ba90 frame pointer = 0x10:0xc985ba94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0x22b274c0 stack pointer = 0x10:0xc985bc18 frame pointer = 0x10:0xc985bca8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0216340 stack pointer = 0x10:0xc985ba90 frame pointer = 0x10:0xc985ba94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0x22b274c0 stack pointer = 0x10:0xc985bc18 frame pointer = 0x10:0xc985bca8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0216340 stack pointer = 0x10:0xc985ba90 frame pointer = 0x10:0xc985ba94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0x22b274c0 stack pointer = 0x10:0xc985bc18 frame pointer = 0x10:0xc985bca8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0216340 stack pointer = 0x10:0xc985ba90 frame pointer = 0x10:0xc985ba94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none panic: from debugger Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22b274c0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0216340 stack pointer = 0x10:0xc985ba90 frame pointer = 0x10:0xc985ba94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 43623 (XF86_S3) interrupt mask = none panic: from debugger dumping to dev #wd/0x20001, offset 77824 dump 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=1886220131) at ../../kern/kern_shutdown.c:281 281 dumppcb.pcb_cr3 = rcr3(); (kgdb) quit Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Oct 2 14:33:56 SAST 1999 root@:/usr/src/sys/compile/CHAIN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200456082 Hz CPU: Pentium/P54C (200.46-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 117440512 (114688K bytes) config> en pcm0 config> ir pcm0 10 config> dr pcm0 3 config> f pcm0 0x17 config> q avail memory = 110256128 (107672K bytes) Preloaded elf kernel "kernel" at 0xc034d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc034d09c. Preloaded elf module "splash_bmp.ko" at 0xc034d0ec. Preloaded splash_image_data "/boot/splash.bmp" at 0xc034d190. Intel Pentium detected, installing workaround for F00F bug VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c1bfc (c0001bfc) VESA: S3 Incorporated. Trio64V+ ccd0-1: Concatenated disk drivers devclass_alloc_unit: pcib0 already exists, using next available unit number npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 ata-pci0: irq 14 at device 0.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: unknown card (vendor=0x1039, dev=0x0009) at 1.1 pcib2: at device 2.0 on pci0 pci1: on pcib2 vga-pci0: irq 5 at device 9.0 on pci0 de0: irq 9 at device 11.0 on pci0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:f9:2f:c8 devclass_alloc_unit: pci1 already exists, using next available unit number pcib1: on motherboard pci2: on pcib1 aha0 at port 0x330-0x333 irq 11 drq 6 on isa0 aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pcm0: at irq 10 drq 3 flags 0x17 on isa0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Winbond chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 de0: enabling 10baseT port IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging limited to 100 packets/entry by default ad0: ATA-4 disk at ata0 as master ad0: 8693MB (17803440 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 31 depth queue, PIO Creating DISK ad0 Creating DISK wd0 ad1: ATA-? disk at ata1 as master ad1: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue, PIO Creating DISK ad1 Creating DISK wd1 ad2: ATA-? disk at ata1 as slave ad2: 1039MB (2128896 sectors), 2112 cyls, 16 heads, 63 S/T, 512 B/S ad2: 8 secs/int, 0 depth queue, PIO Creating DISK ad2 Creating DISK wd2 Waiting 2 seconds for SCSI devices to settle Creating DISK cd0 Creating DISK cd1 changing root device to wd0s1a WARNING: / was not properly dismounted cd0 at aha0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at aha0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed #bus devices controller isa0 controller pnp0 controller pci0 #scsi code + adapter controller aha0 at isa? port ? irq ? controller scbus0 #processor stuff machine i386 #cpu I386_CPU #cpu I486_CPU cpu I586_CPU cpu I686_CPU ident CHAIN options MATH_EMULATE #Support for x87 emulation options PQ_LARGECACHE #enable 512kb+ l2 cache support device npx0 at nexus? port IO_NPX irq 13 #performance stuff maxusers 128 options NMBCLUSTERS=4096 #networking pseudo-device loop pseudo-device ether pseudo-device tun 2 options INET #InterNETworking #filesystems options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SOFTUPDATES #console stuff pseudo-device splash pseudo-device pty 128 options UCONSOLE #Allow users to grab the console options SYSVSHM options SYSVSEM options SYSVMSG options VESA options XSERVER # support for X server controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? #misc kernel tie ins pseudo-device gzip # Exec gzipped a.out's options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE options DDB options SPX_HACK options IBCS2 #build ibcs2 into kernel options COMPAT_LINUX #build linux into kernel makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #posix code options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L #security stuff options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPDIVERT options ICMP_BANDLIM options MD5 pseudo-device bpf 2 #Berkeley packet filter pseudo-device snp 2 #disk stuff pseudo-device ccd 2 options QUOTA #floppy controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 ##primary ide channel #controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #secondary ide channel #controller wdc1 at isa? port IO_WD2 irq 15 flags 0xa0ffa0ff #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 controller ata0 device atadisk0 # ATA disk drives #scsi devices device da0 device cd0 #options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device device pass0 #other devices #network card device de0 device ed0 at isa? port 0x300 irq 5 iomem 0xd8000 #sound card device pcm0 at isa? port ? irq 10 drq 3 flags 0x17 #serial port device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 #parallel port device ppc0 at isa? port? irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 11:18:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id E253214DC7 for ; Sun, 3 Oct 1999 11:18:27 -0700 (PDT) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id UAA08512 for freebsd-current@freebsd.org; Sun, 3 Oct 1999 20:18:26 +0200 (CEST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id TAA58425 for freebsd-current@freebsd.org; Sun, 3 Oct 1999 19:38:53 +0200 (CEST) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: Netscape core dump, happily :-) Date: 3 Oct 1999 19:38:52 +0200 Message-ID: <7t84bc$1p1e$1@bigeye.rhein-neckar.de> References: <4.2.0.58.19991003121853.012efcb0@194.184.65.4> <19991003112523.A27331@osfmail.isc.rit.edu> <19991003095005.K244@norn.ca.eu.org> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Piazza wrote: > Disable Javascript and the problem will go away (ugh). I have JavaScript disabled by default. Still, navigator frequently crashes on close or (I couldn't care less) exit. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 11:21:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from kg.ops.uunet.co.za (kg.ops.uunet.co.za [196.31.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 91BCE14DC7 for ; Sun, 3 Oct 1999 11:21:20 -0700 (PDT) (envelope-from khetan@link.freebsd.os.org.za) X-Disclaimer: Contents of this e-mail are the writer's opinion X-Disclaimer2: and may not be quoted, re-produced or forwarded X-Disclaimer3: (in part or whole) without the author's permission. Received: from localhost (khetan@localhost) by kg.ops.uunet.co.za (8.9.3/8.9.3) with ESMTP id UAA07117 for ; Sun, 3 Oct 1999 20:21:18 +0200 (SAST) (envelope-from khetan@link.freebsd.os.org.za) Date: Sun, 3 Oct 1999 20:21:18 +0200 (SAST) From: Khetan Gajjar X-Sender: khetan@kg.ops.uunet.co.za Reply-To: Khetan Gajjar To: current@FreeBSD.ORG Subject: Re: Trap 12's with various programs over the last 4 weeks In-Reply-To: Message-ID: X-Mobile: +27 82 9907663 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 3 Oct 1999, Khetan Gajjar wrote: >Vibra 16 sound card, but this hasn't worked since newpcm. I lied; I never noticed that was working again : >pcm0: at irq 10 drq 3 flags 0x17 on isa0 Missed it because I only use the soundcard occasionally . --- Khetan Gajjar (!kg1779) * khetan@iafrica.com ; khetan@os.org.za http://www.os.org.za/~khetan * Talk/Finger khetan@chain.freebsd.os.org.za FreeBSD enthusiast * http://www2.za.freebsd.org/ Stupidest quote heard : Who is this BSD, and why should we free him ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 11:33:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 9ABFB14D91 for ; Sun, 3 Oct 1999 11:32:50 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id TAA54452; Sun, 3 Oct 1999 19:34:17 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 3 Oct 1999 19:34:16 +0100 (BST) From: Doug Rabson To: "Daniel M. Eischen" Cc: freebsd-current@freebsd.org, winter@jurai.net Subject: Re: Recent kernel hangs during boot with pnp sio. In-Reply-To: <37F78874.F7B86582@vigrid.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 3 Oct 1999, Daniel M. Eischen wrote: > Daniel Eischen wrote: > > OK, I originally did that to no avail, but I didn't make the change to > > the correct file (sys/isa/sio.c, not sys/dev/sio/sio.c)! So with the > > following change: > > > > Index: sio.c > > =================================================================== > > RCS file: /opt/b/CVS/src/sys/isa/sio.c,v > > retrieving revision 1.268 > > diff -u -r1.268 sio.c > > --- sio.c 1999/09/25 18:24:21 1.268 > > +++ sio.c 1999/10/02 21:54:33 > > @@ -568,6 +568,7 @@ > > {0x1005d041, "Generic IRDA-compatible device"}, /* PNP0510 */ > > {0x1105d041, "Generic IRDA-compatible device"}, /* PNP0511 */ > > {0x31307256, "USR3031"}, /* USR3031 */ > > + {0x8024b04e, "SupraExpress 56i Sp V.90"}, > > {0} > > }; > > > > the modem is detected as: > > > > sio-1: irq maps: 0x801 0x821 0x801 0x801 > > sio3: at port 0x3e8-0x3ef irq 5 on isa0 > > sio3: type 16550A > > Who's responsible for sio.c? Can I commit this change? I looked at you pnpinfo again and I think this change might be better. It accepts the cards description instead of overriding it and adds another ID for SUP2080 which your card is compatible with. I also removed the bogus descriptions for the USR3031 since the pnpinfo for that also supplies a reasonable description. Index: sio.c =================================================================== RCS file: /home/ncvs/src/sys/isa/sio.c,v retrieving revision 1.268 diff -u -r1.268 sio.c --- sio.c 1999/09/25 18:24:21 1.268 +++ sio.c 1999/10/03 18:32:10 @@ -567,7 +567,9 @@ {0x0205d041, "Multiport serial device (non-intelligent 16550)"}, /* PNP0502 */ {0x1005d041, "Generic IRDA-compatible device"}, /* PNP0510 */ {0x1105d041, "Generic IRDA-compatible device"}, /* PNP0511 */ - {0x31307256, "USR3031"}, /* USR3031 */ + {0x31307256, NULL}, /* USR3031 */ + {0x8024b04e, NULL}, /* SUP2480 */ + {0x8020b04e, NULL}, /* SUP2080 */ {0} }; -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 11:59:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 40CE914DE6 for ; Sun, 3 Oct 1999 11:59:53 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA94593 for ; Sun, 3 Oct 1999 11:59:53 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA47245 for current@FreeBSD.ORG; Sun, 3 Oct 1999 11:59:53 -0700 (PDT) (envelope-from obrien) Date: Sun, 3 Oct 1999 11:59:53 -0700 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: HEADS UP: sigset_t changes committed Message-ID: <19991003115953.A47198@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19990929224847.A26394@foobar.franken.de> <19990929231253.B26394@foobar.franken.de> <37F30A88.2DF1D7C9@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <37F30A88.2DF1D7C9@scc.nl> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not working on changing the build/installworld. There's nothing > "broken" about having to install the kernel first, IMO. I don't see how > I can "fix" it then. In fact for OpenBSD (and I'll assume NetBSD) their `build world' procedure is to first compile a new config(8), then build and install a new kernel & reboot. THEN build and install the rest. from /usr/src/Makefile: # 3) It is strongly recommended that you build and install a new kernel # before rebuilding your system. Some of the new programs may use new # functionality or depend on API changes that your old kernel doesn't # have. # # 4) If you are reasonably sure that things will compile OK, use the # "make build" target supplied here. Good luck. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 12: 9:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id A040914DE6 for ; Sun, 3 Oct 1999 12:09:13 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id PAA17093; Sun, 3 Oct 1999 15:09:02 -0400 (EDT) Message-ID: <19991003150902.A15336@netmonger.net> Date: Sun, 3 Oct 1999 15:09:02 -0400 From: Christopher Masto To: current@FreeBSD.ORG, grog@lemis.com Subject: SOLVED (partly): Re: Can't start vinum with new kernels References: <19991003125355.A11241@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19991003125355.A11241@netmonger.net>; from Christopher Masto on Sun, Oct 03, 1999 at 12:53:55PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found out what was causing "Can't get device list: Cannot allocate memory".. libdevstat mismatch. Now I'm getting a panic, but hopefully I'll have a decent backtrace out of it soon. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 12:23:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (Postfix) with ESMTP id 6942B14EA3 for ; Sun, 3 Oct 1999 12:23:05 -0700 (PDT) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.3/8.9.1) with SMTP id TAA94243; Sun, 3 Oct 1999 19:22:58 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19991003121730.00933320@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 03 Oct 1999 12:17:30 -0700 To: Doug Rabson From: "Kurt D. Zeilenga" Subject: Re: Recent kernel hangs during boot with pnp sio. Cc: "Daniel M. Eischen" , freebsd-current@FreeBSD.ORG, winter@jurai.net In-Reply-To: References: <37F78874.F7B86582@vigrid.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I provided a patch for the USR2030 that likely could be committed at the same time. See kern/13983. Kurt At 07:34 PM 10/3/99 +0100, Doug Rabson wrote: >diff -u -r1.268 sio.c >--- sio.c 1999/09/25 18:24:21 1.268 >+++ sio.c 1999/10/03 18:32:10 >@@ -567,7 +567,9 @@ > {0x0205d041, "Multiport serial device (non-intelligent 16550)"}, /* PNP0502 */ > {0x1005d041, "Generic IRDA-compatible device"}, /* PNP0510 */ > {0x1105d041, "Generic IRDA-compatible device"}, /* PNP0511 */ >- {0x31307256, "USR3031"}, /* USR3031 */ >+ {0x31307256, NULL}, /* USR3031 */ + {0x30207256, NULL}, /* USR2030 */ >+ {0x8024b04e, NULL}, /* SUP2480 */ >+ {0x8020b04e, NULL}, /* SUP2080 */ > {0} > }; > $ pnpinfo -v Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID USR2030 (0x30207256), Serial Number 0xadacaa93 PnP Version 1.0, Vendor Version 0 Device Description: U.S.Robotics Inc. Sportster 56000 FAX Internal Logical Device ID: USR2030 0x30207256 #0 TAG Start DF Good Configuration I/O Range 0x2f8 .. 0x2f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 5 7 - only one type (true/edge) TAG Start DF Acceptable Configuration I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 2 3 4 5 7 - only one type (true/edge) TAG Start DF Acceptable Configuration I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 2 3 4 5 7 - only one type (true/edge) TAG Start DF Acceptable Configuration I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 2 3 4 5 7 - only one type (true/edge) TAG End DF End Tag Successfully got 16 resources, 1 logical fdevs -- card select # 0x0001 CSN USR2030 (0x30207256), Serial Number 0xadacaa93 Logical device #0 IO: 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 IRQ 5 0 DMA 4 4 IO range check 0x00 activate 0x01 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 12:42:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from io.yi.org (24.66.174.118.bc.wave.home.com [24.66.174.118]) by hub.freebsd.org (Postfix) with ESMTP id 134FE14DE6 for ; Sun, 3 Oct 1999 12:42:49 -0700 (PDT) (envelope-from jake@checker.org) Received: from io.yi.org (localhost [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id 5C2911FD7; Sun, 3 Oct 1999 12:42:54 -0700 (PDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Masto Cc: current@FreeBSD.ORG Subject: Re: SOLVED (partly): Re: Can't start vinum with new kernels In-reply-to: Your message of "Sun, 03 Oct 1999 15:09:02 EDT." <19991003150902.A15336@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Oct 1999 12:42:54 -0700 From: Jake Burkholder Message-Id: <19991003194254.5C2911FD7@io.yi.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I found out what was causing "Can't get device list: Cannot allocate > memory".. libdevstat mismatch. > > Now I'm getting a panic, but hopefully I'll have a decent backtrace > out of it soon. I ran into to that too and thought I was screwed, but vinum read worked. I built the new kernel rebuilt modules rebuilt /sbin/vinum rebooted...Can't get device list: Cannot allocate memory...single user mode vinum read /dev/wd0 /dev/wd1 exit then promptly rebuilt the world, and everything was fine. the panic could be from old /sbin/vinum with new kernel and/or vinum.ko, I'd suggest rebuilding that too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 12:49:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id A237C14EE0 for ; Sun, 3 Oct 1999 12:49:54 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id PAA18510; Sun, 3 Oct 1999 15:49:52 -0400 (EDT) Message-ID: <19991003154952.A18256@netmonger.net> Date: Sun, 3 Oct 1999 15:49:52 -0400 From: Christopher Masto To: Jake Burkholder Cc: current@FreeBSD.ORG Subject: Re: SOLVED (partly): Re: Can't start vinum with new kernels References: <19991003150902.A15336@netmonger.net> <19991003194254.5C2911FD7@io.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19991003194254.5C2911FD7@io.yi.org>; from Jake Burkholder on Sun, Oct 03, 1999 at 12:42:54PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 03, 1999 at 12:42:54PM -0700, Jake Burkholder wrote: > > I found out what was causing "Can't get device list: Cannot allocate > > memory".. libdevstat mismatch. > > > > Now I'm getting a panic, but hopefully I'll have a decent backtrace > > out of it soon. > > then promptly rebuilt the world, and everything was fine. > the panic could be from old /sbin/vinum with new kernel and/or vinum.ko, > I'd suggest rebuilding that too. Nope, I've been rebuilding them all along. Just got it again.. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x48 fault code = supervisor read, page not present instruction pointer = 0x8:0xc017cf0f stack pointer = 0x10:0xcdacfb9c frame pointer = 0x10:0xcdacfbcc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 16 (vinum) interrupt mask = bio kernel: type 12 trap, code=0 Stopped at getblk+0x21b: cmpl $0x3,0x48(%edx) db> trace getblk(0,8,1000,0,0) at getblk+0x21b bread(0,8,1000,0,cdacfc3c) at bread+0x22 _end(c1150800,c1151000,20000,1200,0) at 0xc108d0f3 _end(c1098284,4,0,c1062800,cdacfd74) at 0xc108e19e _end(c1062800,c109813c,0,0,cdacfd98) at 0xc108c009 _end(c1062800,c109813c,cdacfdf4,c106c580,cc734500) at 0xc108c063 _end(c106c580,c4004640,c1062800,3,cc734500) at 0xc1092658 spec_ioctl(cdacfdf4,cdacfdd8,c0206489,cdacfdf4,cdacfe84) at spec_ioctl+0x33 spec_vnoperate(cdacfdf4,cdacfe84,c0189a3c,cdacfdf4,c1081dc0) at spec_vnoperate+0x15 ufs_vnoperatespec(cdacfdf4,c1081dc0,0,400,0) at ufs_vnoperatespec+0x15 vn_ioctl(c1081dc0,c4004640,c1062800,cc734500,cc734500) at vn_ioctl+0x114 ioctl(cc734500,cdacff80,4,bfbfd4f0,4) at ioctl+0x20b syscall(2f,2f,2f,4,bfbfd4f0) at syscall+0x195 Xint0x80_syscall() at Xint0x80_syscall+0x26 Waiting for the dump now.. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 13:17:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 3AC4814EE0 for ; Sun, 3 Oct 1999 13:17:27 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id NAA83011; Sun, 3 Oct 1999 13:16:53 -0700 (PDT) From: Archie Cobbs Message-Id: <199910032016.NAA83011@bubba.whistle.com> Subject: Re: panic: free vnode isn't In-Reply-To: from Bob Bishop at "Oct 3, 1999 09:45:43 am" To: rb@gid.co.uk (Bob Bishop) Date: Sun, 3 Oct 1999 13:16:52 -0700 (PDT) Cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob Bishop writes: > >Unfortunatly with this sort of panic, the panic is correct. The actual > >dammage was done some (possibly considerable) time before. So a traceback > >isn't so useful. > > OK, so how do I proceed to get some more useful info? It's still happening. I'd suggest turining off soft-updates first. Then if the panic goes away, at least we have confirmed that soft updates is the likely culprit. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 13:20:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id EDAD815032 for ; Sun, 3 Oct 1999 13:20:39 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id WAA04433; Sun, 3 Oct 1999 22:20:32 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id WAA08246; Sun, 3 Oct 1999 22:20:31 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id WAA00870; Sun, 3 Oct 1999 22:19:55 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sun, 3 Oct 1999 22:19:55 +0200 (CEST) From: Michael Reifenberger To: "Daniel C. Sobral" Cc: Warner Losh , "Rodney W. Grimes" , "Jordan K. Hubbard" , dmaddox@conterra.com, Ollivier Robert , current@FreeBSD.ORG Subject: Re: Loss of Functionality with newpnp In-Reply-To: <37F586CB.EBFC8D26@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 2 Oct 1999, Daniel C. Sobral wrote: > Date: Sat, 02 Oct 1999 13:15:07 +0900 > From: Daniel C. Sobral > To: Warner Losh > Cc: Rodney W. Grimes , Jordan K. Hubbard , dmaddox@conterra.com, Ollivier Robert , current@FreeBSD.ORG > Subject: Re: Loss of Functionality with newpnp > > Warner Losh wrote: > > > > In message <37F1BA64.29B5251C@newsguy.com> "Daniel C. Sobral" writes: > > : Let me chime in here. We *DO* care about ancient AIC drivers as long > > : as no PCMCIA alternative exists. > > > > Justin has said that porting old scsi aic to cam wouldn't be too hard, > > but would still provide a level of buginess that is too high.. > > Otherwise, i'd have done that a long time ago... > > I don't know, I have never used the aic driver before. It would seem > that aic users were not that unhappy with the driver. Yes, it seemed to work for me with my Jaz-drive and my AHA-1460a. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 14: 0:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt011n66.san.rr.com (dt011n66.san.rr.com [204.210.13.102]) by hub.freebsd.org (Postfix) with ESMTP id 13DE714E06; Sun, 3 Oct 1999 14:00:17 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n66.san.rr.com (8.9.3/8.8.8) with ESMTP id OAA25240; Sun, 3 Oct 1999 14:00:17 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37F7C3E1.5D210852@gorean.org> Date: Sun, 03 Oct 1999 14:00:17 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: sigset_t changes committed References: <19990929224847.A26394@foobar.franken.de> <19990929231253.B26394@foobar.franken.de> <37F30A88.2DF1D7C9@scc.nl> <19991003115953.A47198@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > > I'm not working on changing the build/installworld. There's nothing > > "broken" about having to install the kernel first, IMO. I don't see how > > I can "fix" it then. > > In fact for OpenBSD (and I'll assume NetBSD) their `build world' > procedure is to first compile a new config(8), then build and install a > new kernel & reboot. THEN build and install the rest. I think Peter makes some good arguments inre building the kernel first, but as others have expressed I think that the chicken and egg problems are not yet solved. Perhaps what we need is a type of pre-world kernel target that will create a space somewhere in /usr/src/sys where it can build and install all the dependencies (gas, config, etc.) then build the new kernel with the new tools. So the "new" procedure would be something like: make kernel NAME Builds tools, builds new kernel, installs new kernel, (rebuilds libkvm & friends?) reboot (option to rebuild libkvm, et al here instead for those cases where world won't be built?) make world (insert things like rebuild kernel again to get sigset_t changes in) reboot Does this sound like the same things y'all are talking about? I realize that I haven't even addressed the cross platform problems, and I agree that it is necessary to solve those longstanding issues. However before we can start on those problems we need to come to agreement on the "best" method of performing the necessary steps, then hammer out the details. This has the potential to really go somewhere if people get behind it and commit to solving the problems with a long term view in mind. Excited, Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 14:39:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from www1.interdestination.net (www1.interdestination.net [209.12.127.2]) by hub.freebsd.org (Postfix) with ESMTP id F02FB15025 for ; Sun, 3 Oct 1999 14:39:21 -0700 (PDT) (envelope-from zapper@idsmail.com) Received: from idsmail.com (Zapper@home.zapper.org [209.136.139.35]) by www1.interdestination.net (8.9.1/8.9.1) with ESMTP id QAA14303 for ; Sun, 3 Oct 1999 16:36:19 -0500 (CDT) Message-ID: <37F7CC18.61221AC6@idsmail.com> Date: Sun, 03 Oct 1999 16:35:20 -0500 From: High Voltage Organization: home.zapper.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Current Subject: @Home connect. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Does anyone know where I can find info on how to set FreeBSD 3.3 Stable up for a @Home connect? I'm getting @Home installed this Friday and I'd like to be prepared. Thanx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 14:46:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 769D314D6D for ; Sun, 3 Oct 1999 14:46:47 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA22475; Sun, 3 Oct 1999 17:46:36 -0400 (EDT) Message-ID: <19991003174636.A22344@netmonger.net> Date: Sun, 3 Oct 1999 17:46:36 -0400 From: Christopher Masto To: current@FreeBSD.ORG, grog@lemis.com Subject: vinum panic References: <19991003125355.A11241@netmonger.net> <19991003150902.A15336@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19991003150902.A15336@netmonger.net>; from Christopher Masto on Sun, Oct 03, 1999 at 03:09:02PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 03, 1999 at 03:09:02PM -0400, Christopher Masto wrote: > Now I'm getting a panic, but hopefully I'll have a decent backtrace > out of it soon. Well... #0 0xc018a06b in getblk (vp=0x0, blkno=0x8, size=0x1000, slpflag=0x0, slptimeo=0x0) at ../../kern/vfs_bio.c:2110 #1 0xc0188346 in bread (vp=0x0, blkno=0x8, size=0x1000, cred=0x0, bpp=0xcda6fc3c) at ../../kern/vfs_bio.c:478 #2 0xc014b40f in read_drive (drive=0xc1083000, buf=0xc108b000, length=0x20000, offset=0x1200) at ../../dev/vinum/vinumio.c:284 #3 0xc014c4b2 in vinum_scandisk (devicename=0xc02c6824, drives=0x4) at ../../dev/vinum/vinumio.c:959 #4 0xc01494f5 in parse_config (cptr=0xc1063000 "read", keyset=0xc02a71d0, update=0x0) at ../../dev/vinum/vinumconfig.c:1516 #5 0xc014954f in parse_user_config (cptr=0xc1063000 "read", keyset=0xc02a71d0) at ../../dev/vinum/vinumconfig.c:1559 #6 0xc014c9d4 in vinumioctl (dev=0xc106e700, cmd=0xc4004640, data=0xc1063000 "read", flag=0x3, p=0xcc6e3500) at ../../dev/vinum/vinumioctl.c:110 #7 0xc019c8bf in spec_ioctl (ap=0xcda6fdf4) at ../../miscfs/specfs/spec_vnops.c:519 #8 0xc019c135 in spec_vnoperate (ap=0xcda6fdf4) at ../../miscfs/specfs/spec_vnops.c:125 #9 0xc02135e5 in ufs_vnoperatespec (ap=0xcda6fdf4) at ../../ufs/ufs/ufs_vnops.c:2313 #10 0xc0196b98 in vn_ioctl (fp=0xc10580c0, com=0xc4004640, data=0xc1063000 "read", p=0xcc6e3500) at vnode_if.h:425 #11 0xc01750df in ioctl (p=0xcc6e3500, uap=0xcda6ff80) at ../../sys/file.h:166 #12 0xc025ad01 in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x4, tf_esi = 0xbfbfd4a8, tf_ebp = 0xbfbfd8a8, tf_isp = 0xcda6ffd4, tf_ebx = 0x4, tf_edx = 0x8085da5, tf_ecx = 0xbfbfd4d0, tf_eax = 0x36, tf_trapno = 0x7, tf_err = 0x2, tf_eip = 0x8064f6c, tf_cs = 0x1f, tf_eflags = 0x246, tf_esp = 0xbfbfd488, tf_ss = 0x2f}) at ../../i386/i386/trap.c:1056 #13 0xc024cc36 in Xint0x80_syscall () #14 0x804cdd7 in ?? () #15 0x8048492 in ?? () #16 0x80482fd in ?? () #17 0x80480e9 in ?? () Obviously a NULL vp is being passed down from somewhere.. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 14:51: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id CFB22151BD for ; Sun, 3 Oct 1999 14:51:02 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id WAA94772; Sun, 3 Oct 1999 22:51:01 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 3 Oct 1999 22:48:16 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199910032016.NAA83011@bubba.whistle.com> References: from Bob Bishop at "Oct 3, 1999 09:45:43 am" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 3 Oct 1999 22:48:19 +0000 To: Archie Cobbs From: Bob Bishop Subject: Re: panic: free vnode isn't Cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 1:16 pm -0700 3/10/99, Archie Cobbs wrote: >I'd suggest turining off soft-updates first.[etc] Here's a thing. I'd forgotten that I'd borrowed the scratch drive (where /usr/obj is) out of this box a while back. It seems when I replaced it I forgot to enable softupdates (which had been on previously). So the failures occurred with softupdates off on /usr/obj but on on root, and /usr/src coming in on NFS. I reenabled softupdates on /usr/obj and I haven't seen the panic since. Go figure. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 15: 4:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 8403214D60 for ; Sun, 3 Oct 1999 15:04:17 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem11.masternet.it [194.184.65.21]) by scotty.masternet.it (8.9.3/8.9.3) with ESMTP id AAA85504; Mon, 4 Oct 1999 00:03:53 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.2.0.58.19991004000048.012d94b0@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 04 Oct 1999 00:08:15 +0200 To: Chris Piazza From: Gianmarco Giovannelli Subject: Re: Netscape core dump, happily :-) Cc: current@FreeBSD.ORG In-Reply-To: <19991003095005.K244@norn.ca.eu.org> References: <19991003112523.A27331@osfmail.isc.rit.edu> <4.2.0.58.19991003121853.012efcb0@194.184.65.4> <19991003112523.A27331@osfmail.isc.rit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03/10/99, Chris Piazza wrote: >On Sun, Oct 03, 1999 at 11:25:23AM -0400, Jon Parise wrote: > > On Sun, Oct 03, 1999 at 12:22:55PM +0200, Gianmarco Giovannelli wrote: > > > > > Is there anyone who is experienced Netscape crashes with 4.0-CURRENT > when > > > the close button is pressed (not always, but very often) ? > > > It happens to me with 4.61 and 4.70 , it doesn't happen with > 3.2-STABLE I > > > have at work. > > > > Yes, I've been experiencing that as well. It writes a zero length > > core file in my home directory and exits with signal 10: > > > > Oct 1 16:20:53 void /kernel: pid 18518 (navigator-4.61.b), uid > > 1000: exited on signal 10 > > > > It's incredibly annoying, but I haven't bothered to track it down > > in any great detail. > >Disable Javascript and the problem will go away (ugh). I once had >it crash over 30 times in a single day. It's not related to Javascript or at least not these cores ... Here it crashes also when browsing local files (without Javascript) and it DOESN'T happen with 3.3-STABLE... So it has to be a 4.0-CURRENT problem that perhaps worths to be investigate better... It is not kind to have the "default" browser crashes so heavily and couldn't rely on it... I'd like to know if people using other platforms (like Linux and BSDI) and/or other wm (I use windowmaker) has the same problem... Thanks for your time... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 15:27:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 6412B14D60 for ; Sun, 3 Oct 1999 15:27:48 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id SAA01336; Sun, 3 Oct 1999 18:26:34 -0400 (EDT) Date: Sun, 3 Oct 1999 18:26:34 -0400 (EDT) From: Daniel Eischen Message-Id: <199910032226.SAA01336@pcnet1.pcnet.com> To: Kurt@OpenLDAP.Org, dfr@nlsystems.com Subject: Re: Recent kernel hangs during boot with pnp sio. Cc: eischen@vigrid.com, freebsd-current@FreeBSD.ORG, winter@jurai.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > I looked at you pnpinfo again and I think this change might be better. It > accepts the cards description instead of overriding it and adds another ID > for SUP2080 which your card is compatible with. I also removed the bogus > descriptions for the USR3031 since the pnpinfo for that also supplies a > reasonable description. Kurt D. Zeilenga wrote: > I provided a patch for the USR2030 that likely could be > committed at the same time. See kern/13983. OK, I committed both of these changes. Thanks to you both. I'll look at closing PR kern/13983. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 15:28:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (dialin264.hamilton.globalserve.net [209.90.139.73]) by hub.freebsd.org (Postfix) with ESMTP id A00E114D60 for ; Sun, 3 Oct 1999 15:28:24 -0700 (PDT) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id SAA01733; Sun, 3 Oct 1999 18:28:45 -0400 (EDT) Date: Sun, 3 Oct 1999 18:28:45 -0400 From: Dan Moschuk To: Gianmarco Giovannelli Cc: current@FreeBSD.ORG, freebsd@masternet.it Subject: Re: Netscape core dump, happily :-) Message-ID: <19991003182845.A26799@spirit.jaded.net> References: <4.2.0.58.19991003121853.012efcb0@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <4.2.0.58.19991003121853.012efcb0@194.184.65.4> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Is there anyone who is experienced Netscape crashes with 4.0-CURRENT when | the close button is pressed (not always, but very often) ? | It happens to me with 4.61 and 4.70 , it doesn't happen with 3.2-STABLE I | have at work. | | Thanks ... I have two 4.0-CURRENT machines, one with netscape running natively, the other under linux "emulation". Surprisingly, the one running under linux emu is pretty stable. I have a few problems with netscape natively with java sites, but since disabling that it's been "pretty good". Of course, I still experience one of those random crashes every now and again. -- Dan Moschuk (TFreak!dan@freebsd.org) "Try not. Do, or do not. There is no try." -- Yoda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 15:30:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt011n66.san.rr.com (dt011n66.san.rr.com [204.210.13.102]) by hub.freebsd.org (Postfix) with ESMTP id 4C2D414D60 for ; Sun, 3 Oct 1999 15:30:27 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n66.san.rr.com (8.9.3/8.8.8) with ESMTP id PAA26260; Sun, 3 Oct 1999 15:30:23 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37F7D8FF.6E77494C@gorean.org> Date: Sun, 03 Oct 1999 15:30:23 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: High Voltage Cc: FreeBSD Current Subject: Re: @Home connect. References: <37F7CC18.61221AC6@idsmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG High Voltage wrote: > > Hi > > Does anyone know where I can find info on how to set FreeBSD 3.3 > Stable up for a @Home connect? I'm getting @Home installed this Friday > and I'd like to be prepared. http://freebsd.simplenet.com/dhcp.html Good luck, Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 15:49: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from news.rdc1.tn.home.com (ha2.rdc1.tn.home.com [24.2.7.67]) by hub.freebsd.org (Postfix) with ESMTP id 7DB871542B for ; Sun, 3 Oct 1999 15:49:00 -0700 (PDT) (envelope-from dakuntz@home.com) Received: from windows ([24.2.16.41]) by news.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19991003224859.QNYA13734.news.rdc1.tn.home.com@windows> for ; Sun, 3 Oct 1999 15:48:59 -0700 Message-ID: <003101bf0df2$059ec080$29100218@micronetinfo.com> Reply-To: "Douglas Kuntz" From: "Douglas Kuntz" Cc: "FreeBSD Current" References: <37F7CC18.61221AC6@idsmail.com> <37F7D8FF.6E77494C@gorean.org> Subject: Re: @Home connect. Date: Sun, 3 Oct 1999 18:52:51 -0400 Organization: MicroNet Information Services 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Or...if ya have a nice Cable company doin @home, and they give you an actual static IP...just set it up like a normal system on a network. Douglas Kuntz Systems Administrator PC Tech Reports http://www.pctechreports.com ---FreeBSD... The choice of the smart generation--- ----- Original Message ----- From: Doug To: High Voltage Cc: FreeBSD Current Sent: Sunday, October 03, 1999 6:30 PM Subject: Re: @Home connect. | High Voltage wrote: | > | > Hi | > | > Does anyone know where I can find info on how to set FreeBSD 3.3 | > Stable up for a @Home connect? I'm getting @Home installed this Friday | > and I'd like to be prepared. | | http://freebsd.simplenet.com/dhcp.html | | Good luck, | | Doug | -- | "Stop it, I'm gettin' misty." | | - Mel Gibson as Porter, "Payback" | | | To Unsubscribe: send mail to majordomo@FreeBSD.org | with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 16:16:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 8681514F0E for ; Sun, 3 Oct 1999 16:16:35 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id TAA25400; Sun, 3 Oct 1999 19:16:27 -0400 (EDT) Message-ID: <19991003191627.A24981@netmonger.net> Date: Sun, 3 Oct 1999 19:16:27 -0400 From: Christopher Masto To: current@FreeBSD.ORG, grog@lemis.com Subject: Re: vinum panic References: <19991003125355.A11241@netmonger.net> <19991003150902.A15336@netmonger.net> <19991003174636.A22344@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19991003174636.A22344@netmonger.net>; from Christopher Masto on Sun, Oct 03, 1999 at 05:46:36PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 03, 1999 at 05:46:36PM -0400, Christopher Masto wrote: [...] > #1 0xc0188346 in bread (vp=0x0, blkno=0x8, size=0x1000, cred=0x0, bpp=0xcda6fc3c) at ../../kern/vfs_bio.c:478 > #2 0xc014b40f in read_drive (drive=0xc1083000, buf=0xc108b000, length=0x20000, offset=0x1200) > at ../../dev/vinum/vinumio.c:284 [...] > Obviously a NULL vp is being passed down from somewhere.. I give up. Somehow vp ends up being NULL in read_drive: $1 = {state = drive_down, flags = 0, subdisks_allocated = 0, subdisks_used = 0, blocksize = 4096, pid = 9, sectors_available = 15685832, secsperblock = 8, lasterror = 0, driveno = 0, opencount = 0, reads = 0, writes = 0, bytes_read = 0, bytes_written = 0, devicename = "/dev/da0s1e", '\000' , vp = 0x0, p = 0xcc6e3500, label = { sysname = "wensleydale.netmonger.net\000\000\000\000\000\000", name = "drive0", '\000' , date_of_birth = { tv_sec = 935623993, tv_usec = 301079}, last_update = { tv_sec = 938976848, tv_usec = 800287}, drive_size = 8031281664}, partinfo = {disklab = 0xc0fc1800, part = 0xc0fc18d4}, freelist_size = 16, freelist_entries = 1, freelist = 0xc1054d00, lockfilename = "vinumio.c\000\000\000\000\000\000", lockline = 193} Beyond that, I can't figure it out. Dell has wisely decided to make their machines take about two minutes to POST, and I'm sick to death of staring at their logo (and then waiting for both Adaptec controllers to announce their presence and waste another 30 seconds of my life). And the device nodes all exist, BTW: brw-r----- 1 root operator 4, 0x00020002 Aug 25 15:22 /dev/da0s1 brw-r----- 1 root operator 4, 0x00020000 Aug 25 15:22 /dev/da0s1a brw-r----- 1 root operator 4, 0x00020001 Oct 3 16:07 /dev/da0s1b brw-r----- 1 root operator 4, 0x00020002 Aug 25 15:22 /dev/da0s1c brw-r----- 1 root operator 4, 0x00020003 Aug 25 15:22 /dev/da0s1d brw-r----- 1 root operator 4, 0x00020004 Aug 25 15:22 /dev/da0s1e brw-r----- 1 root operator 4, 0x00020005 Aug 25 15:22 /dev/da0s1f brw-r----- 1 root operator 4, 0x00020006 Aug 25 15:22 /dev/da0s1g brw-r----- 1 root operator 4, 0x00020007 Aug 25 15:22 /dev/da0s1h -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 16:51:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id F18B414DC2 for ; Sun, 3 Oct 1999 16:51:47 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper ([207.44.1.21]) by www.keycomp.net (8.8.5/SCO5) with SMTP id TAA07165 for ; Sun, 3 Oct 1999 19:58:23 -0400 (EDT) Message-ID: <008601bf0dfa$321cda40$01010101@bopper> From: "Bill A. K." To: Subject: Current Uncompilable? Date: Sun, 3 Oct 1999 19:51:21 -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 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Everybody, my -current dosen't want to build today. it's failing with a signal 12 on libgcc1.c (or could it be libgccl.c)? Anybody else have these problems today? As of about 30-45 minutes ago when I tried CVsuping again, there was so changes to the libs or anything that I think could be this. Thanks Bill billieakay@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 17: 2:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-51.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.51]) by hub.freebsd.org (Postfix) with ESMTP id 3D66914FF1 for ; Sun, 3 Oct 1999 17:02:16 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA00467; Mon, 4 Oct 1999 01:01:54 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA78708; Mon, 4 Oct 1999 00:35:44 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910032335.AAA78708@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: chad@DCFinc.com Cc: jdp@polstra.com (John Polstra), current@FreeBSD.ORG Subject: Re: New CVSup mirror sites In-reply-to: Your message of "Sun, 03 Oct 1999 06:36:42 PDT." <199910031336.GAA10018@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Oct 1999 00:35:37 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As I recall, John Polstra wrote: > > In the US, cvsup[1-3] are very busy; clients get turned away from them > > on a regular basis because they are already at their limit. The other > > 4 mirrors are practically idle in comparison. These are all screaming > > fast, well-connected, well-maintained mirrors. Give them a try if you > > haven't already! > > I've been using cvsup5 for some time now. And yes, it screams. > > John, do you have usage statistics broken out for each server? Hmm, that's interesting. Perhaps a cvsup-mirror-report port that provides stats to a ``list the servers by current capacity'' web page. If only I had the time :-/ > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > chad@dcfinc.com chad@larsons.org larson1@home.net > DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 17:27:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 3DA4E14FC9 for ; Sun, 3 Oct 1999 17:27:50 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA50524; Mon, 4 Oct 1999 09:57:42 +0930 (CST) Date: Mon, 4 Oct 1999 09:57:42 +0930 From: Greg Lehey To: Christopher Masto Cc: current@FreeBSD.ORG Subject: Re: vinum panic Message-ID: <19991004095742.W40186@freebie.lemis.com> References: <19991003125355.A11241@netmonger.net> <19991003150902.A15336@netmonger.net> <19991003174636.A22344@netmonger.net> <19991003191627.A24981@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991003191627.A24981@netmonger.net>; from Christopher Masto on Sun, Oct 03, 1999 at 07:16:27PM -0400 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 3 October 1999 at 19:16:27 -0400, Christopher Masto wrote: > On Sun, Oct 03, 1999 at 05:46:36PM -0400, Christopher Masto wrote: > [...] >> #1 0xc0188346 in bread (vp=0x0, blkno=0x8, size=0x1000, cred=0x0, bpp=0xcda6fc3c) at ../../kern/vfs_bio.c:478 >> #2 0xc014b40f in read_drive (drive=0xc1083000, buf=0xc108b000, length=0x20000, offset=0x1200) >> at ../../dev/vinum/vinumio.c:284 > [...] >> Obviously a NULL vp is being passed down from somewhere.. > > I give up. Somehow vp ends up being NULL in read_drive: > > $1 = {state = drive_down, flags = 0, subdisks_allocated = 0, > subdisks_used = 0, blocksize = 4096, pid = 9, sectors_available = 15685832, > secsperblock = 8, lasterror = 0, driveno = 0, opencount = 0, reads = 0, > writes = 0, bytes_read = 0, bytes_written = 0, > devicename = "/dev/da0s1e", '\000' , vp = 0x0, > p = 0xcc6e3500, label = { > sysname = "wensleydale.netmonger.net\000\000\000\000\000\000", > name = "drive0", '\000' , date_of_birth = { > tv_sec = 935623993, tv_usec = 301079}, last_update = { > tv_sec = 938976848, tv_usec = 800287}, drive_size = 8031281664}, > partinfo = {disklab = 0xc0fc1800, part = 0xc0fc18d4}, freelist_size = 16, > freelist_entries = 1, freelist = 0xc1054d00, > lockfilename = "vinumio.c\000\000\000\000\000\000", lockline = 193} I've seen this, and I thought I had fixed it in revision 1.44 of sys/dev/vinum/vinumio.c. Note also that the drive state is down, so it shouldn't be reading it in the first place. Which revision are you using? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 17:35:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 246C514FB9 for ; Sun, 3 Oct 1999 17:35:36 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id UAA27978; Sun, 3 Oct 1999 20:35:26 -0400 (EDT) Message-ID: <19991003203526.A27828@netmonger.net> Date: Sun, 3 Oct 1999 20:35:26 -0400 From: Christopher Masto To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: vinum panic References: <19991003125355.A11241@netmonger.net> <19991003150902.A15336@netmonger.net> <19991003174636.A22344@netmonger.net> <19991003191627.A24981@netmonger.net> <19991004095742.W40186@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19991004095742.W40186@freebie.lemis.com>; from Greg Lehey on Mon, Oct 04, 1999 at 09:57:42AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 04, 1999 at 09:57:42AM +0930, Greg Lehey wrote: > I've seen this, and I thought I had fixed it in revision 1.44 of > sys/dev/vinum/vinumio.c. Note also that the drive state is down, so > it shouldn't be reading it in the first place. Which revision are you > using? It's 1.44. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 17:55: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 6C84C14E04 for ; Sun, 3 Oct 1999 17:54:52 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA50620; Mon, 4 Oct 1999 10:24:45 +0930 (CST) Date: Mon, 4 Oct 1999 10:24:45 +0930 From: Greg Lehey To: "Bill A. K." Cc: freebsd-current@FreeBSD.ORG Subject: Re: Current Uncompilable? Message-ID: <19991004102444.Y40186@freebie.lemis.com> References: <008601bf0dfa$321cda40$01010101@bopper> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <008601bf0dfa$321cda40$01010101@bopper>; from Bill A. K. on Sun, Oct 03, 1999 at 07:51:21PM -0400 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 3 October 1999 at 19:51:21 -0400, Bill A. K. wrote: > Hi Everybody, > my -current dosen't want to build today. it's failing with a signal 12 > on libgcc1.c (or could it be libgccl.c)? Anybody else have these problems > today? As of about 30-45 minutes ago when I tried CVsuping again, there was > so changes to the libs or anything that I think could be this. Have you built a new kernel first? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 18: 6:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from garnet.sover.net (garnet.sover.net [209.198.87.53]) by hub.freebsd.org (Postfix) with ESMTP id F3A6014E04 for ; Sun, 3 Oct 1999 18:06:07 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc0a201.bf.sover.net [209.198.85.201]) by garnet.sover.net (8.9.3/8.9.3) with ESMTP id VAA28119; Sun, 3 Oct 1999 21:05:50 -0400 (EDT) Comments: SoVerNet Verification (on garnet.sover.net) nightfall.digitalspark.net from arc0a201.bf.sover.net [209.198.85.201] 209.198.85.201 Sun, 3 Oct 1999 21:05:50 -0400 (EDT) Date: Sun, 3 Oct 1999 21:09:56 +0000 (GMT) From: Adam Strohl To: Greg Lehey Cc: "Bill A. K." , freebsd-current@FreeBSD.ORG Subject: Re: Current Uncompilable? In-Reply-To: <19991004102444.Y40186@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just rebuilt from a system that was pre-sig update (cvsuped an hour or so ago) and everything worked perfectly. I did however build, install, and boot a new kernel before doing a make world. - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - On Mon, 4 Oct 1999, Greg Lehey wrote: > On Sunday, 3 October 1999 at 19:51:21 -0400, Bill A. K. wrote: > > Hi Everybody, > > my -current dosen't want to build today. it's failing with a signal 12 > > on libgcc1.c (or could it be libgccl.c)? Anybody else have these problems > > today? As of about 30-45 minutes ago when I tried CVsuping again, there was > > so changes to the libs or anything that I think could be this. > > Have you built a new kernel first? > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 19: 4:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from panix.com (panix.com [166.84.0.226]) by hub.freebsd.org (Postfix) with ESMTP id A650E14D84 for ; Sun, 3 Oct 1999 19:04:21 -0700 (PDT) (envelope-from rsi@panix.com) Received: (from rsi@localhost) by panix.com (8.8.5/8.8.8/PanixU1.4) id WAA04453; Sun, 3 Oct 1999 22:04:13 -0400 (EDT) Message-Id: <199910040204.WAA04453@panix.com> To: Adam Strohl Cc: Greg Lehey , "Bill A. K." , freebsd-current@FreeBSD.ORG Subject: Re: Current Uncompilable? References: From: Rajappa Iyer Date: 03 Oct 1999 22:04:12 -0400 Reply-To: rsi@panix.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adam Strohl writes: > I just rebuilt from a system that was pre-sig update (cvsuped an hour or > so ago) and everything worked perfectly. > > I did however build, install, and boot a new kernel before doing a make > world. I had the same problem, but only with make -j8 world. Plain "make world" worked fine for me. Rajappa -- a.k.a. Rajappa Iyer. New York, New York. We're too busy mopping the floor to turn off the faucet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 19:37:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [204.188.6.238]) by hub.freebsd.org (Postfix) with SMTP id 08AFE14FDA for ; Sun, 3 Oct 1999 19:37:26 -0700 (PDT) (envelope-from drbrain@magnesium.net) Received: (qmail 7378 invoked by uid 1100); 4 Oct 1999 02:37:24 -0000 Date: 3 Oct 1999 19:37:24 -0700 Date: Sun, 3 Oct 1999 19:37:24 -0700 From: "Dr. Brain" To: current@freebsd.org Subject: Re: Netscape core dump, happily :-) Message-ID: <19991003193724.A7303@toxic.magnesium.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have had Linux communicator 4.6 core dump on me (signal 10) with an empty core file a couple of times. However I hacked the linux_base port to install a redhat 6 libraries in order to get glibc 2.1, so I don't know if this will make any difference. -- Eric Hodel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 19:40:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from garnet.sover.net (garnet.sover.net [209.198.87.53]) by hub.freebsd.org (Postfix) with ESMTP id 4B71614F60 for ; Sun, 3 Oct 1999 19:40:48 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc0a201.bf.sover.net [209.198.85.201]) by garnet.sover.net (8.9.3/8.9.3) with ESMTP id WAA21757; Sun, 3 Oct 1999 22:40:05 -0400 (EDT) Comments: SoVerNet Verification (on garnet.sover.net) nightfall.digitalspark.net from arc0a201.bf.sover.net [209.198.85.201] 209.198.85.201 Sun, 3 Oct 1999 22:40:05 -0400 (EDT) Date: Sun, 3 Oct 1999 22:44:10 +0000 (GMT) From: Adam Strohl To: Rajappa Iyer Cc: Greg Lehey , "Bill A. K." , freebsd-current@FreeBSD.ORG Subject: Re: Current Uncompilable? In-Reply-To: <199910040204.WAA04453@panix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3 Oct 1999, Rajappa Iyer wrote: > I had the same problem, but only with make -j8 world. Plain "make > world" worked fine for me. I compiled with make -j 12 actually, dual processor madness and all :P (51 minutes on my Dual Celeron 450s UDMA 33 IDE disks /w SoftUpdates) I could hear my IDE disks begging for mercy. However, I have seen cases where some programs, and kernels wouldn't compile with the -j or -l (gmake only) options, this is a problem in the makefile organization, and generally any modern makefile should withstand being -j ed. - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 20:47:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id 222BC14FA5 for ; Sun, 3 Oct 1999 20:47:50 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper ([207.44.1.21]) by www.keycomp.net (8.8.5/SCO5) with SMTP id XAA08289 for ; Sun, 3 Oct 1999 23:54:25 -0400 (EDT) Message-ID: <008101bf0e1b$2c32dd20$01010101@bopper> From: "Bill A. K." To: Subject: Re: Current Uncompilable? Attn: Greg Lehey Date: Sun, 3 Oct 1999 23:47:24 -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 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg, Thanks, I'll try that.....However I was under the impression that I am supposed to make the world first......has this changed recently? I was following the instructions on how to make the world/ how to stay current in the handbook. I believe the make world document is based directly on "Making the World Your Own" (it is just about identical). Just to review the steps: i'm running 3.2-RELEASE i cvsup to 4.0-CURRENT i build a new kernel from the new 4.0 sources. i install the kernel and reboot i make and install the world Please let me know if this is correct. Thanks Bill billieakay@yahoo.com P.S. Is your lemis.com mail system set to reject mail from @yahoo.com addresses? ----- Original Message ----- From: Greg Lehey To: Bill A. K. Cc: Sent: Sunday, October 03, 1999 8:54 PM Subject: Re: Current Uncompilable? > On Sunday, 3 October 1999 at 19:51:21 -0400, Bill A. K. wrote: > > Hi Everybody, > > my -current dosen't want to build today. it's failing with a signal 12 > > on libgcc1.c (or could it be libgccl.c)? Anybody else have these problems > > today? As of about 30-45 minutes ago when I tried CVsuping again, there was > > so changes to the libs or anything that I think could be this. > > Have you built a new kernel first? > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 22: 5: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id F03E914CA3 for ; Sun, 3 Oct 1999 22:04:58 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA52252; Mon, 4 Oct 1999 14:34:49 +0930 (CST) Date: Mon, 4 Oct 1999 14:34:49 +0930 From: Greg Lehey To: "Bill A. K." Cc: freebsd-current@FreeBSD.ORG Subject: Re: Current Uncompilable? Attn: Greg Lehey Message-ID: <19991004143449.I40186@freebie.lemis.com> References: <008101bf0e1b$2c32dd20$01010101@bopper> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <008101bf0e1b$2c32dd20$01010101@bopper>; from Bill A. K. on Sun, Oct 03, 1999 at 11:47:24PM -0400 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] On Sunday, 3 October 1999 at 23:47:24 -0400, Bill A. K. wrote: > On Sunday, October 03, 1999 8:54 PM, Greg Lehey wrote: > >> On Sunday, 3 October 1999 at 19:51:21 -0400, Bill A. K. wrote: >>> Hi Everybody, >>> my -current dosen't want to build today. it's failing with a >>> signal 12 on libgcc1.c (or could it be libgccl.c)? Anybody else >>> have these problems today? As of about 30-45 minutes ago when I >>> tried CVsuping again, there was so changes to the libs or >>> anything that I think could be this. >> >> Have you built a new kernel first? > > Greg, > Thanks, I'll try that.....However I was under the impression > that I am supposed to make the world first......has this changed > recently? Yes. Didn't you read the HEADS UP from Marcel Moolenaar a few days ago? > I was following the instructions on how to make the world/ how to > stay current in the handbook. I believe the make world document is > based directly on "Making the World Your Own" (it is just about > identical). Well, one of the things about how to stay current is to read the messages posted on -CURRENT, especially if they have a subject line like "HEADS UP: sigset_t changes committed". > Just to review the steps: > > i'm running 3.2-RELEASE > > i cvsup to 4.0-CURRENT > > i build a new kernel from the new 4.0 sources. > > i install the kernel and reboot > > i make and install the world > > Please let me know if this is correct. You might have trouble upgrading at all. You've certainly chosen an unlucky time to upgrade to -CURRENT. At the moment you're supposed to build a new kernel first so that it understands the new signal system calls. Try it and see what it says. > P.S. Is your lemis.com mail system set to reject mail from @yahoo.com > addresses? Yes. It also says why: Oct 4 13:05:00 freebie sendmail[51972]: NAA51972: ruleset=check_mail, arg1=, relay=www.keycomp.net [207.44.1.33], reject=550 ... Mail rejected. See http://www.lemis.com/dontspam.html Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 3 23:16:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id BB4FB15210; Sun, 3 Oct 1999 23:16:35 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id XAA20216; Sun, 3 Oct 1999 23:35:06 -0700 (PDT) Date: Sun, 3 Oct 1999 23:35:06 -0700 (PDT) From: Alfred Perlstein To: Marcel Moolenaar Cc: current@FreeBSD.org Subject: new signal stuff breaks libc_r? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since the signal changes... I'm finding that it _seems_ since libc_r isn't including something that properly defines __inline to inline that i'm getting unresolved symbols when linking or running programs that depend on libc_r. Anyone else getting this? compiling a void main(void){} with -pthread will barf for me, using -static I'm able to see which files are missing which inlines. thanks, -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 1:11:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id D74F414D1B; Mon, 4 Oct 1999 01:11:29 -0700 (PDT) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11Y3En-000Ham-00; Mon, 4 Oct 1999 08:12:50 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id KAA13736; Mon, 4 Oct 1999 10:11:22 +0200 (CEST) (envelope-from marcel@scc.nl) Message-ID: <37F8612A.6E4546EE@scc.nl> Date: Mon, 04 Oct 1999 10:11:22 +0200 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Marcel Moolenaar , current@FreeBSD.org Subject: Re: new signal stuff breaks libc_r? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > Since the signal changes... > > I'm finding that it _seems_ since libc_r isn't including something > that properly defines __inline to inline that i'm getting unresolved > symbols when linking or running programs that depend on libc_r. > > Anyone else getting this? > > compiling a void main(void){} with -pthread will barf for me, > using -static I'm able to see which files are missing which > inlines. This isn't a problem report I can deal with. Please be very explicit. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 1:49: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 3FEF114F18 for ; Mon, 4 Oct 1999 01:48:48 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA18689; Mon, 4 Oct 1999 09:49:56 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 4 Oct 1999 09:49:56 +0100 (BST) From: Doug Rabson To: Daniel Eischen Cc: Kurt@OpenLDAP.Org, freebsd-current@FreeBSD.ORG, winter@jurai.net Subject: Re: Recent kernel hangs during boot with pnp sio. In-Reply-To: <199910032226.SAA01336@pcnet1.pcnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 3 Oct 1999, Daniel Eischen wrote: > Doug Rabson wrote: > > I looked at you pnpinfo again and I think this change might be better. It > > accepts the cards description instead of overriding it and adds another ID > > for SUP2080 which your card is compatible with. I also removed the bogus > > descriptions for the USR3031 since the pnpinfo for that also supplies a > > reasonable description. > > Kurt D. Zeilenga wrote: > > I provided a patch for the USR2030 that likely could be > > committed at the same time. See kern/13983. > > OK, I committed both of these changes. Thanks to you both. > I'll look at closing PR kern/13983. Thanks for picking this up Dan. I'm glad we got your system working. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 2:29: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id D61DE14D2B for ; Mon, 4 Oct 1999 02:28:54 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.037 #1) id 11Y4QB-000GPp-00; Mon, 04 Oct 1999 11:28:39 +0200 From: Sheldon Hearn To: Bryan Bursey Cc: current@FreeBSD.ORG Subject: Re: Issues with xl0 In-reply-to: Your message of "Sun, 03 Oct 1999 08:09:49 -0300." Date: Mon, 04 Oct 1999 11:28:39 +0200 Message-ID: <63104.939029319@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 03 Oct 1999 08:09:49 -0300, Bryan Bursey wrote: > Can anyone tell me if there are known issues with the xl0 driver in 4.0, > or if it has been superceded by another driver which works with 3Com > 3C900B. That's a pretty broad question. I know that lots of people use the xl0 driver in CURRENT quite happily. To me, it sounds more like you used a mismatched sysinstall to try to install FreeBSD. This is known to be problematic, because there are new things in later releases that older sysinstall's didn't know about. You'll want to look at your netowkr configuration in /etc/rc.conf. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 4:55:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 647031541C; Mon, 4 Oct 1999 04:55:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id NAA05482; Mon, 4 Oct 1999 13:55:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: committers@FreeBSD.org, current@FreeBSD.org Subject: Heads up! In-reply-to: Your message of "Mon, 04 Oct 1999 04:42:42 PDT." <199910041142.EAA17355@freefall.freebsd.org> Date: Mon, 04 Oct 1999 13:55:43 +0200 Message-ID: <5480.939038143@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have now come so far that we can start to kill cdevsw_add() calls and rely on make_dev() for most of the device drivers. Later today I will add a "nagging printf", which will trigger when a device is opened, which wasn't registered by the device driver with make_dev(). It will only trigger once per driver per boot. If you see messages along the line of: WARNING: driver foo should register devices with make_dev() Please let me and the drivers maintainer know. Disk drivers will still be treated slightly special treatment, so they will be exempt from this warning for now. Background Information: This is all part of the long push for DEVFS, before DEVFS can become a reality, we need all dev_t's to be created specifically with make_dev() so their name is available to DEVFS. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 5: 6: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from pa.scotland.net (pa2.scotland.net [194.247.65.132]) by hub.freebsd.org (Postfix) with ESMTP id 6FC7714D3E for ; Mon, 4 Oct 1999 05:06:01 -0700 (PDT) (envelope-from freebsd@timog.prestel.co.uk) Received: from [148.176.238.2] (helo=timog.prestel.co.uk) by pa.scotland.net with esmtp (Exim 2.12 #4) id 11Y6sU-0002uN-00 for freebsd-current@freebsd.org; Mon, 4 Oct 1999 13:06:03 +0100 Received: (qmail 19436 invoked by uid 1002); 4 Oct 1999 06:09:26 -0000 Date: Mon, 4 Oct 1999 07:09:25 +0100 From: Timo Geusch To: Soren Schmidt Cc: freebsd-current@freebsd.org Subject: Re: Recent kernel hangs during boot with pnp sio. Message-ID: <19991004070925.A19400@tabby.timog.prestel.co.uk> References: <37F4A7C9.31C0D752@vigrid.com> <199910011232.OAA63420@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199910011232.OAA63420@freebsd.dk>; from Soren Schmidt on Fri, Oct 01, 1999 at 02:32:11PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 01, 1999 at 02:32:11PM +0200, Soren Schmidt wrote: > Hmm, I also have severe problems with the PnP stuff and my 3C509 > cards, it just wont work as the pnp code finds and allocates > adresses for the card, but the card probe doesn't pick them up... Soren, AFAIK the ep driver does not interact with PnP, does it? Those cards do have two different methods for detecting the parameters, one of which is PnP. If the driver hasn't changed much in the last two-three months is doesn't know about PnP at all. PnP-like config entries used to work via the old 3Com- specific configuration mechanism. I do have an updated/changed driver that uses Pnp to configure the card but I am not able to work on it until mid next week. Also it exposes problems which I believe are in my changes or side-effects from the apparent buggyness of the original driver. If you're interested I can send you the source code for the driver but it is not clear if it works on -current at the moment as I haven't updated for some time. Timo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 5:10:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from darren2.lnk.telstra.net (darren2.lnk.telstra.net [139.130.53.33]) by hub.freebsd.org (Postfix) with ESMTP id 5C88914D3E; Mon, 4 Oct 1999 05:10:25 -0700 (PDT) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by darren2.lnk.telstra.net (8.9.1/8.8.7) id MAA10626; Mon, 4 Oct 1999 12:10:24 GMT Received: from avalon.reed.wattle.id.au(192.168.1.1) by firewall.reed.wattle.id.au via smap (V1.3) id sma010624; Mon Oct 4 12:10:11 1999 Received: from percival.reed.wattle.id.au. (percival.reed.wattle.id.au [192.168.1.5]) by avalon.reed.wattle.id.au (8.9.0.Beta3/8.9.0.Beta3) with SMTP id WAA11209; Mon, 4 Oct 1999 22:10:11 +1000 (EST) From: Darren Reed Message-Id: <199910041210.WAA11209@avalon.reed.wattle.id.au> Subject: Re: Heads up! To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Mon, 4 Oct 1999 22:10:10 +1000 (EST) Cc: committers@FreeBSD.org, current@FreeBSD.org In-Reply-To: <5480.939038143@critter.freebsd.dk> from "Poul-Henning Kamp" at Oct 4, 99 01:55:43 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some email I received from Poul-Henning Kamp, sie wrote: > > > We have now come so far that we can start to kill cdevsw_add() > calls and rely on make_dev() for most of the device drivers. [...] Is that make_dev() meant to make makedev() or is that a part of the transition you're helping along here ? Wonderfully distinct names... Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 5:13:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 549DA14F18; Mon, 4 Oct 1999 05:13:05 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id OAA05597; Mon, 4 Oct 1999 14:12:56 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Darren Reed Cc: committers@FreeBSD.org, current@FreeBSD.org Subject: Re: Heads up! In-reply-to: Your message of "Mon, 04 Oct 1999 22:10:10 +1000." <199910041210.WAA11209@avalon.reed.wattle.id.au> Date: Mon, 04 Oct 1999 14:12:56 +0200 Message-ID: <5595.939039176@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199910041210.WAA11209@avalon.reed.wattle.id.au>, Darren Reed writes : >In some email I received from Poul-Henning Kamp, sie wrote: >> >> >> We have now come so far that we can start to kill cdevsw_add() >> calls and rely on make_dev() for most of the device drivers. >[...] > >Is that make_dev() meant to make makedev() or is that a part of the >transition you're helping along here ? Wonderfully distinct names... make_dev() basically does a makedev() and registers the name and cdevsw on the dev_t. In addtion it transports the uid, gid and mode args to DEVFS if available. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 5:19:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8DC7515431 for ; Mon, 4 Oct 1999 05:19:28 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA82564; Mon, 4 Oct 1999 14:19:25 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910041219.OAA82564@freebsd.dk> Subject: Re: Recent kernel hangs during boot with pnp sio. In-Reply-To: <19991004070925.A19400@tabby.timog.prestel.co.uk> from Timo Geusch at "Oct 4, 1999 07:09:25 am" To: freebsd@timog.prestel.co.uk (Timo Geusch) Date: Mon, 4 Oct 1999 14:19:25 +0200 (CEST) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Timo Geusch wrote: > On Fri, Oct 01, 1999 at 02:32:11PM +0200, Soren Schmidt wrote: > > Hmm, I also have severe problems with the PnP stuff and my 3C509 > > cards, it just wont work as the pnp code finds and allocates > > adresses for the card, but the card probe doesn't pick them up... > > Soren, > AFAIK the ep driver does not interact with PnP, does it? Those cards do have > two different methods for detecting the parameters, one of which is PnP. > If the driver hasn't changed much in the last two-three months is doesn't know > about PnP at all. PnP-like config entries used to work via the old 3Com- > specific configuration mechanism. Correct, but if one has pnp0 in the kernel it doesn work no matter how you config it (or at least I cannot get it to work).. > I do have an updated/changed driver that uses Pnp to configure the card but I > am not able to work on it until mid next week. Also it exposes problems > which I believe are in my changes or side-effects from the apparent buggyness > of the original driver. > If you're interested I can send you the source code for the driver but it is > not clear if it works on -current at the moment as I haven't updated for > some time. Sure, I can try it out here, and maybe help a little (time permitting)... -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 5:37:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 8426D14C1B for ; Mon, 4 Oct 1999 05:37:41 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 99757 invoked from network); 4 Oct 1999 12:37:31 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 4 Oct 1999 12:37:31 -0000 Message-ID: <37F89F62.CB5FCA41@pipeline.ch> Date: Mon, 04 Oct 1999 14:36:50 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: current@freebsd.org Subject: panic: malloc type lacks magic Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello It looks like I fucked my -current box up during the sig_t changes. I tried made a new kernel before make world but after ifconfig'ing the network interfaces it panics with: panic: malloc type lacks magic Making a new world is of course not possible because of the sig_t changes. Any ideas what is going wrong? I'm a little bit lost at this. Thanks -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 5:41:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 8729C14C1B; Mon, 4 Oct 1999 05:40:52 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with ESMTP id OAA10155; Mon, 4 Oct 1999 14:40:37 +0200 (MET DST) Date: Mon, 4 Oct 1999 14:40:37 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Poul-Henning Kamp Cc: committers@FreeBSD.org, current@FreeBSD.org Subject: Re: Heads up! In-Reply-To: <5480.939038143@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And the crowd goes wild! Nick > > We have now come so far that we can start to kill cdevsw_add() > calls and rely on make_dev() for most of the device drivers. > > Later today I will add a "nagging printf", which will trigger when > a device is opened, which wasn't registered by the device driver > with make_dev(). It will only trigger once per driver per boot. > > If you see messages along the line of: > > WARNING: driver foo should register devices with make_dev() > > Please let me and the drivers maintainer know. > > Disk drivers will still be treated slightly special treatment, so > they will be exempt from this warning for now. > > Background Information: > > This is all part of the long push for DEVFS, before DEVFS can become > a reality, we need all dev_t's to be created specifically with > make_dev() so their name is available to DEVFS. > > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 6: 4: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1C2EA14BE0 for ; Mon, 4 Oct 1999 06:03:52 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id PAA05953 for ; Mon, 4 Oct 1999 15:03:50 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: panic(8) implementation... From: Poul-Henning Kamp Date: Mon, 04 Oct 1999 15:03:49 +0200 Message-ID: <5951.939042229@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While testing the new swopen() routine I found this panic(8) implementation on -current: hexdump -C < /dev/drum -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 7:16: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id D7C2415440 for ; Mon, 4 Oct 1999 07:15:44 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper (kc-rmt07.keycomp.net [207.44.1.9]) by www.keycomp.net (8.8.5/SCO5) with SMTP id KAA10745 for ; Mon, 4 Oct 1999 10:22:16 -0400 (EDT) Message-ID: <000901bf0e72$e19719e0$01010101@bopper> From: "Bill A. K." To: References: <008101bf0e1b$2c32dd20$01010101@bopper> <19991004143449.I40186@freebie.lemis.com> Subject: Re: Current Uncompilable? Attn: Greg Lehey Date: Mon, 4 Oct 1999 10:15:13 -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 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg, thanks for your help, no i didn't get the heads up because i just got onto the current list, but i should get them now if any occur. I'll try building current again Thanks Bill billieakay@yahoo.com ----- Original Message ----- From: Greg Lehey To: Bill A. K. Cc: Sent: Monday, October 04, 1999 1:04 AM Subject: Re: Current Uncompilable? Attn: Greg Lehey > [Format recovered--see http://www.lemis.com/email/email-format.html] > > On Sunday, 3 October 1999 at 23:47:24 -0400, Bill A. K. wrote: > > On Sunday, October 03, 1999 8:54 PM, Greg Lehey wrote: > > > >> On Sunday, 3 October 1999 at 19:51:21 -0400, Bill A. K. wrote: > >>> Hi Everybody, > >>> my -current dosen't want to build today. it's failing with a > >>> signal 12 on libgcc1.c (or could it be libgccl.c)? Anybody else > >>> have these problems today? As of about 30-45 minutes ago when I > >>> tried CVsuping again, there was so changes to the libs or > >>> anything that I think could be this. > >> > >> Have you built a new kernel first? > > > > Greg, > > Thanks, I'll try that.....However I was under the impression > > that I am supposed to make the world first......has this changed > > recently? > > Yes. Didn't you read the HEADS UP from Marcel Moolenaar a few days > ago? > > > I was following the instructions on how to make the world/ how to > > stay current in the handbook. I believe the make world document is > > based directly on "Making the World Your Own" (it is just about > > identical). > > Well, one of the things about how to stay current is to read the > messages posted on -CURRENT, especially if they have a subject line > like "HEADS UP: sigset_t changes committed". > > > Just to review the steps: > > > > i'm running 3.2-RELEASE > > > > i cvsup to 4.0-CURRENT > > > > i build a new kernel from the new 4.0 sources. > > > > i install the kernel and reboot > > > > i make and install the world > > > > Please let me know if this is correct. > > You might have trouble upgrading at all. You've certainly chosen an > unlucky time to upgrade to -CURRENT. At the moment you're supposed to > build a new kernel first so that it understands the new signal system > calls. Try it and see what it says. > > > P.S. Is your lemis.com mail system set to reject mail from @yahoo.com > > addresses? > > Yes. It also says why: > > Oct 4 13:05:00 freebie sendmail[51972]: NAA51972: ruleset=check_mail, arg1=, relay=www.keycomp.net [207.44.1.33], reject=550 ... Mail rejected. See http://www.lemis.com/dontspam.html > > Greg > -- > When replying to this message, please take care not to mutilate the > original text. > For more information, see http://www.lemis.com/email.html > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 7:33:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from weedcon1.cropsci.ncsu.edu (weedcon1.cropsci.ncsu.edu [152.1.207.51]) by hub.freebsd.org (Postfix) with ESMTP id 56B651545B for ; Mon, 4 Oct 1999 07:33:29 -0700 (PDT) (envelope-from fbsdbob@weedcon1.cropsci.ncsu.edu) Received: (from fbsdbob@localhost) by weedcon1.cropsci.ncsu.edu (8.9.3/8.9.3) id KAA35683; Mon, 4 Oct 1999 10:39:02 -0400 (EDT) (envelope-from fbsdbob) From: FreeBSD Bob Message-Id: <199910041439.KAA35683@weedcon1.cropsci.ncsu.edu> Subject: Why Adaptec 1540 bombing? To: freebsd-current@freebsd.org Date: Mon, 4 Oct 1999 10:39:00 -0400 (EDT) Cc: fbsdbob@weedcon1.cropsci.ncsu.edu (FreeBSD Bob) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone in the current folks know why I might be getting problems with FreeBSD on an Adaptec 1540 controller? The machine works fine on 2.2.8 and 2.2.6, but dies a horrible screeching halt when installing 3.3 or 4.0. It literally just locks up solid when 3.3 or 4.0 probes the machine during the install. No messages, no nothing. Using an IDE controller works fine. The blue screen with the grey probing window comes up and then the machine freezes, as if the probing got stuck somewhere. The machine is an Intel 486/33 with 485 cache board, 32 megs ram, Adaptec 1540 or generic IDE controller. It is a long shot, but I am curious if anyone knows of any problems in using the Adaptec 1540A on 3.x or 4.x machines? Any insights or suggestions are appreciated. Thanks Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 8:25: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 7797A14CE5 for ; Mon, 4 Oct 1999 08:24:48 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id LAA12800; Mon, 4 Oct 1999 11:29:01 -0400 From: Bill Paul Message-Id: <199910041529.LAA12800@skynet.ctr.columbia.edu> Subject: Re: Issues with xl0 To: bbursey@mechv.me.tuns.ca (Bryan Bursey) Date: Mon, 4 Oct 1999 11:28:59 -0400 (EDT) Cc: current@FreeBSD.ORG In-Reply-To: from "Bryan Bursey" at Oct 3, 99 08:09:49 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 5155 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG WARNING: the following reply contains Extreme Ranting which may be too intense for young audiences. Those not wishing to experience Extreme Ranting should #define NO_EXTREME_RANTING. Of all the gin joints in all the towns in all the world, Bryan Bursey had to walk into mine and say: > I attempted to move from -STABLE to -CURRENT last night, but without any > luck. I decided to start with a current snapshot (19990928), but was > unable to install using the floppies provided on releng3.freebsd.org. #ifndef NO_EXTREME_RANTING But the exact reason why you were unable to install is a secret, right? Clearly the details of the failure would be of no use to anyone, so you chose not to share them, yes? How many times do I have to say it: "it didn't work," "it failed," "I couldn't make it do blah" and similar vague descriptions don't help anybody. Don't start in with a vague statement about a problem and then expect to be asked for more details later: give the details first! It saves a lot of time! #endif > Thinking it might have been a floppy issue, #ifndef NO_EXTREME_RANTING It may as well have been an arthritis issue for all we know. #endif > I used my 3.3-STABLE floppies > and simply changed the install options so that I'd get 4.0. This worked > until I restarted my machine at the end of the install. It came back up > ok, but I was again unable to connect to the network. This is too vague. You're leaving out a ton of details, like: did you even see the xl0 probe messages in the kernel. You know, basic stuff which nobody else will know since we're not able to see over your shoulder. > Can anyone tell me if there are known issues with the xl0 driver in 4.0, > or if it has been superceded by another driver which works with 3Com > 3C900B. #ifndef NO_EXTREME_RANTING No no no. *You* tell *us* if there are any issues! *You* tell *us* if you're having any problems! And then *you* tell *us* in explicit detail what they are! How hard is it to understand that! No, there isn't any other driver. But because you didn't make eves the slightest effort to explain your problem, I can't begin to even help you. #endif You didn't specify which 3c900B card you have: there are several of them with different media options: - 3c900B-FL 10baseFL fiber-optic - 3c900B-TPO 10baseT "Twisted Pair Only" - 3c900B-TPC 10baseT and 10base2 "Twisted Pair and Coax" - 3c900B-COMBO 10baseT, 10base2 and 10base5 (AUI) #ifndef NO_EXTREME_RANTING If you'd bothered to watch what happens when the kernel boots, you would have been able to tell whether or not the 3c900B card was detected (and I know it was in spite of your unwillingless to say so). You would also have been able to tell what media was selected (10baseT, 10base5 or 10base2, depending a bit on exactly which model card you have, which you also didn't tell us). Then had you bothered to rub two brain cells together, you might have been able to tell if maybe the default media selection read from the EEPROM was incorrect and possibly tried to use ifconfig to set it correctly. #endif If you have a TPO or FL adapter, then there's only one media choice, and the driver should have selected it properly. If you have a TPC or a COMBO adapter, then somebody may have fiddled with the 3C90XCFG.EXE utility and selected the wrong default media in the EEPROM. The driver will only use what the EEPROM says; it doesn't autoprobe. If you used the 3C90XCFG.EXE utility to select the "auto" choice, then the driver will pick a reasonable default and expect you to be clever enough to change it with ifconfig if the choice is wrong. For example, for a COMBO card, it will choose 10baseT. If you don't like 10baseT, you can do the following: # ifconfig xl0 media 10base2/BNC # ifconfig xl0 media 10base5/AUI Or if you really want 10baseT: # ifconfig xl0 media 10baseT/UTP If you want to use this setting during the install, then enter the media option command in the box that says "extra options to ifconfig" in the TCP/IP configuration screen (i.e. "media 10base2/BNC"). > Thanks for any help (or other random thoughts). #ifndef NO_EXTREME_RANTING You want random thoughts? Fine: I wish it would stop raining, I hope the Mets make it to the playoffs, my shoes are too tight, you're ugly and your mother dresses you funny. I know what you're thinking: "why is he being so nasty?" Because I can't stand it when people expect me to play the "minimum information" game, and you are by no means the first. Some people may be able to read a chewing gum wrapper and divine the secrets of the universe, but I'm not one of them. #endif -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 8:37:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.rey.moz.com.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (Postfix) with ESMTP id 3267F14D46 for ; Mon, 4 Oct 1999 08:37:08 -0700 (PDT) (envelope-from jabc@webwizard.com.mx) Received: from webwizard.com.mx (dns.rey.moz.com.mx [192.168.1.1]) by dns.rey.moz.com.mx (8.9.3/8.9.3) with ESMTP id KAA93462 for ; Thu, 30 Sep 1999 10:24:09 -0500 (CDT) (envelope-from jabc@webwizard.com.mx) Message-ID: <37F38099.78E95151@webwizard.com.mx> Date: Thu, 30 Sep 1999 10:24:09 -0500 From: Juan Amado Becerril Castillo X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: my make world is broken ! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Suggestions ??? -------------------------------------------------------------- >>> elf make world started on Thu Sep 30 09:23:09 CDT 1999 -------------------------------------------------------------- -------------------------------------------------------------- >>> Cleaning up the temporary elf build tree -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp chflags -R noschg /usr/obj/usr/src/tmp/ rm -rf /usr/obj/usr/src/tmp -------------------------------------------------------------- >>> Making make -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp/usr/bin /usr/obj/usr/src/tmp/make ( cd /usr/src/usr.bin/make; MAKEOBJDIRPREFIX=""; unset MAKEOBJDIRPREFIX; BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin --- cut --- ===> c++filt /usr/obj/usr/src/gnu/usr.bin/cc/c++filt created for /usr/src/gnu/usr.bin/cc/c++filt ===> doc /usr/obj/usr/src/gnu/usr.bin/cc/doc created for /usr/src/gnu/usr.bin/cc/doc ===> f77 /usr/obj/usr/src/gnu/usr.bin/cc/f77 created for /usr/src/gnu/usr.bin/cc/f77 ===> f771 /usr/obj/usr/src/gnu/usr.bin/cc/f771 created for /usr/src/gnu/usr.bin/cc/f771 ===> f77doc /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS /usr/obj/usr/src/gnu/lib/libgcc/GSYMS /usr/obj/usr/src/gnu/lib/libgcc/GTAGS echo '#include ' > config.h echo '#include ' >> config.h echo '#include "i386/xm-i386.h"' > tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Signal 12 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 8:37:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.rey.moz.com.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (Postfix) with ESMTP id 8070B15522 for ; Mon, 4 Oct 1999 08:37:08 -0700 (PDT) (envelope-from jabc@dns.rey.moz.com.mx) Received: from rey.moz.com.mx (dns.rey.moz.com.mx [192.168.1.1]) by dns.rey.moz.com.mx (8.9.3/8.9.3) with ESMTP id KAA93430 for ; Thu, 30 Sep 1999 10:14:33 -0500 (CDT) (envelope-from jabc@dns.rey.moz.com.mx) Message-ID: <37F37E59.984D7598@rey.moz.com.mx> Date: Thu, 30 Sep 1999 10:14:33 -0500 From: Juan Amado Becerril Castillo X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: my make world is broken ! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Suggestions ??? -------------------------------------------------------------- >>> elf make world started on Thu Sep 30 09:23:09 CDT 1999 -------------------------------------------------------------- -------------------------------------------------------------- >>> Cleaning up the temporary elf build tree -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp chflags -R noschg /usr/obj/usr/src/tmp/ rm -rf /usr/obj/usr/src/tmp -------------------------------------------------------------- >>> Making make -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp/usr/bin /usr/obj/usr/src/tmp/make ( cd /usr/src/usr.bin/make; MAKEOBJDIRPREFIX=""; unset MAKEOBJDIRPREFIX; BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin --- cut --- ===> c++filt /usr/obj/usr/src/gnu/usr.bin/cc/c++filt created for /usr/src/gnu/usr.bin/cc/c++filt ===> doc /usr/obj/usr/src/gnu/usr.bin/cc/doc created for /usr/src/gnu/usr.bin/cc/doc ===> f77 /usr/obj/usr/src/gnu/usr.bin/cc/f77 created for /usr/src/gnu/usr.bin/cc/f77 ===> f771 /usr/obj/usr/src/gnu/usr.bin/cc/f771 created for /usr/src/gnu/usr.bin/cc/f771 ===> f77doc /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS /usr/obj/usr/src/gnu/lib/libgcc/GSYMS /usr/obj/usr/src/gnu/lib/libgcc/GTAGS echo '#include ' > config.h echo '#include ' >> config.h echo '#include "i386/xm-i386.h"' > tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Signal 12 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 8:37:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.rey.moz.com.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (Postfix) with ESMTP id 6735915306 for ; Mon, 4 Oct 1999 08:37:08 -0700 (PDT) (envelope-from jabc@dns.rey.moz.com.mx) Received: from rey.moz.com.mx (dns.rey.moz.com.mx [192.168.1.1]) by dns.rey.moz.com.mx (8.9.3/8.9.3) with ESMTP id IAA62509 for ; Thu, 30 Sep 1999 08:19:02 -0500 (CDT) (envelope-from jabc@dns.rey.moz.com.mx) Message-ID: <37F36345.4FA26151@rey.moz.com.mx> Date: Thu, 30 Sep 1999 08:19:02 -0500 From: Juan Amado Becerril Castillo X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: make world trouble Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anybody can help me, how I can fix this ! Thanks. ===> c++filt /usr/obj/usr/src/gnu/usr.bin/cc/c++filt created for /usr/src/gnu/usr.bin/cc/c++filt ===> doc /usr/obj/usr/src/gnu/usr.bin/cc/doc created for /usr/src/gnu/usr.bin/cc/doc ===> f77 /usr/obj/usr/src/gnu/usr.bin/cc/f77 created for /usr/src/gnu/usr.bin/cc/f77 ===> f771 /usr/obj/usr/src/gnu/usr.bin/cc/f771 created for /usr/src/gnu/usr.bin/cc/f771 ===> f77doc /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS /usr/obj/usr/src/gnu/lib/libgcc/GSYMS /usr/obj/usr/src/gnu/lib/libgcc/GTAGS echo '#include ' > config.h echo '#include ' >> config.h echo '#include "i386/xm-i386.h"' > tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Signal 12 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 9: 2:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C465114CE5; Mon, 4 Oct 1999 09:02:21 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p11-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.140]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id BAA17437; Tue, 5 Oct 1999 01:02:18 +0900 (JST) Message-ID: <37F8CF28.BD5903FA@newsguy.com> Date: Tue, 05 Oct 1999 01:00:40 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: current@freebsd.org, sos@freebsd.org, phk@freebsd.org Subject: maxphys = 0?? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A kernel from this weekend's sources is showing this warning message at boot: WARNING: #ad/0x30005 maxphys = 0 ??WARNING: #ad/0x30004 maxphys = 0 ?? These are: brw-r----- 1 root operator 30, 0x00030004 Apr 6 11:48 ad0s2e brw-r----- 1 root operator 30, 0x00030005 Apr 6 11:48 ad0s2f I had a crash during an overnight make world with this kernel, but I haven't been able to reproduce the crash. From the source code, it would seem the message is harmless. Nevertheless, it's a warning message, so I suppose I'm being warning about something. Why does it show this message for ad0s2[ef] but not for the other partitions? How do I "correct" the problem? Anyone wants me to provide any kind of further information? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Rule 69: Do unto other's code as you'd have it done unto yours To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 9:16:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8427F15172; Mon, 4 Oct 1999 09:16:33 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA06696; Mon, 4 Oct 1999 18:15:42 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Daniel C. Sobral" Cc: current@freebsd.org, sos@freebsd.org Subject: Re: maxphys = 0?? In-reply-to: Your message of "Tue, 05 Oct 1999 01:00:40 +0900." <37F8CF28.BD5903FA@newsguy.com> Date: Mon, 04 Oct 1999 18:15:42 +0200 Message-ID: <6694.939053742@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You need to move your sources further forward. In message <37F8CF28.BD5903FA@newsguy.com>, "Daniel C. Sobral" writes: >A kernel from this weekend's sources is showing this warning message >at boot: > >WARNING: #ad/0x30005 maxphys = 0 ??WARNING: #ad/0x30004 maxphys = 0 >?? > >These are: > >brw-r----- 1 root operator 30, 0x00030004 Apr 6 11:48 ad0s2e >brw-r----- 1 root operator 30, 0x00030005 Apr 6 11:48 ad0s2f > >I had a crash during an overnight make world with this kernel, but I >haven't been able to reproduce the crash. > >>From the source code, it would seem the message is harmless. >Nevertheless, it's a warning message, so I suppose I'm being warning >about something. Why does it show this message for ad0s2[ef] but not >for the other partitions? How do I "correct" the problem? Anyone >wants me to provide any kind of further information? > >-- >Daniel C. Sobral (8-DCS) >dcs@newsguy.com >dcs@freebsd.org > > Rule 69: Do unto other's code as you'd have it done unto yours > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 10: 9:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id D075415474; Mon, 4 Oct 1999 10:09:44 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id UAA02090; Mon, 4 Oct 1999 20:08:41 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Mon, 4 Oct 1999 20:08:41 +0300 (EEST) From: Adrian Penisoara To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... In-Reply-To: <199906140715.AAA06844@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Mon, 14 Jun 1999, Matthew Dillon wrote: > > :> > :> David, can you email this program to me please? > :> > :> Also, which FreeBSD release does this occur on? > :> > :> I've got about 6 mmap-related bugs on my plate at the moment. 3 of them > :> have been identified ( that is, I know why they deadlock the machine ), > :> but none have been fixed yet. > : > :Matt, I'll volunteer myself as a tester for this code under 3.2-STABLE, > :when you have it ready... > : > :Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy > :Systems Administrator @ hub.org > :primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > I'll let the lists know when patches are available. It may be a while > (like a week), I still have a lot of catching-up to do after being at > USENIX all last week and my commit privs still need to be resolved. > Excuse my intrusion, but could you be so kind to tell me whether you had the time to build patches for these MMAP-related freezes ? If not could you recommend me some workarounds ? I have a -stable production server that keeps (solidly) blocking pretty often (I don't get over 3 days uptimes). If you need details just let me know. > -Matt > Matthew Dillon > > Thanks, Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 10:21:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 790AF14BFD for ; Mon, 4 Oct 1999 10:21:08 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id KAA06273; Mon, 4 Oct 1999 10:39:32 -0700 (PDT) Date: Mon, 4 Oct 1999 10:39:32 -0700 (PDT) From: Alfred Perlstein To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: new signal stuff breaks libc_r? In-Reply-To: <37F8612A.6E4546EE@scc.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Oct 1999, Marcel Moolenaar wrote: > Alfred Perlstein wrote: > > > > Since the signal changes... > > > > I'm finding that it _seems_ since libc_r isn't including something > > that properly defines __inline to inline that i'm getting unresolved > > symbols when linking or running programs that depend on libc_r. > > > > Anyone else getting this? > > > > compiling a void main(void){} with -pthread will barf for me, > > using -static I'm able to see which files are missing which > > inlines. > > This isn't a problem report I can deal with. Please be very explicit. I think it's something I may have broken somehow, but i'm not exactly sure: ~ % cat t.c #include int main(void) { printf("hello world.\n"); } .(14:17:52)(bright@thumper) ~ % gcc -static t.c -pthread /usr/lib/libc_r.a(uthread_sig.o): In function `_dispatch_signals': /home/src/lib/libc_r/uthread/uthread_sig.c(.text+0xf05): undefined reference to `__sigisempty' For some reason it looks like __inline is being defined like: #define __inline so that when signalvar.h is included the inlines for __sigisempty aren't getting the "inline_ prefix and are assumed to be somewhere else. I asked phk about it and he's not having the problem with a recent -current so I'll be futzing around searching for the reason this is happening. I just deleted my source tree and I'm going to re-check it out, maybe something got corrupted? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 10:25:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 26E65154A5 for ; Mon, 4 Oct 1999 10:25:47 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 5B6761CC8; Tue, 5 Oct 1999 01:25:46 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Juan Amado Becerril Castillo Cc: "current@FreeBSD.ORG" Subject: Re: my make world is broken ! In-reply-to: Your message of "Thu, 30 Sep 1999 10:14:33 EST." <37F37E59.984D7598@rey.moz.com.mx> Date: Tue, 05 Oct 1999 01:25:46 +0800 From: Peter Wemm Message-Id: <19991004172546.5B6761CC8@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Juan Amado Becerril Castillo wrote: > Suggestions ??? 1: Read freebsd-current and it would have told you! 2: Build a new kernel first before 'make world'. 3: *always* build (or try to) and install a new kernel before a make world as that's a lot easier to back out of. [..] > echo '#include "i386/freebsd.h"' >> tm.h > echo '#include "i386/perform.h"' >> tm.h > cc -c -O -pipe > -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config > -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions > -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > *** Signal 12 > > Stop in /usr/src/gnu/lib/libgcc. > *** Error code 1 Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 10:27: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 23AF0154A5 for ; Mon, 4 Oct 1999 10:26:56 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 9F6521CC6; Tue, 5 Oct 1999 01:26:55 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Juan Amado Becerril Castillo Cc: "current@FreeBSD.ORG" Subject: Re: my make world is broken ! In-reply-to: Your message of "Thu, 30 Sep 1999 10:24:09 EST." <37F38099.78E95151@webwizard.com.mx> Date: Tue, 05 Oct 1999 01:26:55 +0800 From: Peter Wemm Message-Id: <19991004172655.9F6521CC6@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And *don't* post the same thing three times to the lists unless you want to find yourself filtered out! Juan Amado Becerril Castillo wrote: > Suggestions ??? > > -------------------------------------------------------------- > >>> elf make world started on Thu Sep 30 09:23:09 CDT 1999 > -------------------------------------------------------------- > > -------------------------------------------------------------- > >>> Cleaning up the temporary elf build tree > -------------------------------------------------------------- > mkdir -p /usr/obj/usr/src/tmp > chflags -R noschg /usr/obj/usr/src/tmp/ > rm -rf /usr/obj/usr/src/tmp > > -------------------------------------------------------------- > >>> Making make > -------------------------------------------------------------- > mkdir -p /usr/obj/usr/src/tmp/usr/bin /usr/obj/usr/src/tmp/make > ( cd /usr/src/usr.bin/make; MAKEOBJDIRPREFIX=""; unset > MAKEOBJDIRPREFIX; > BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple > COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin > > --- > cut > --- > > ===> c++filt > /usr/obj/usr/src/gnu/usr.bin/cc/c++filt created for > /usr/src/gnu/usr.bin/cc/c++filt > ===> doc > /usr/obj/usr/src/gnu/usr.bin/cc/doc created for > /usr/src/gnu/usr.bin/cc/doc > ===> f77 > /usr/obj/usr/src/gnu/usr.bin/cc/f77 created for > /usr/src/gnu/usr.bin/cc/f77 > ===> f771 > /usr/obj/usr/src/gnu/usr.bin/cc/f771 created for > /usr/src/gnu/usr.bin/cc/f771 > ===> f77doc > /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for > /usr/src/gnu/usr.bin/cc/f77doc > cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD > -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; > /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC > -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD > -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; > /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE > -DNOSHARED -B cleandir obj > rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH > /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS > /usr/obj/usr/src/gnu/lib/libgcc/GSYMS > /usr/obj/usr/src/gnu/lib/libgcc/GTAGS > echo '#include ' > config.h > echo '#include ' >> config.h > echo '#include "i386/xm-i386.h"' > tconfig.h > echo '#include "i386/i386.h"' > tm.h > echo '#include "i386/att.h"' >> tm.h > echo '#include "i386/freebsd.h"' >> tm.h > echo '#include "i386/perform.h"' >> tm.h > cc -c -O -pipe > -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config > -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions > -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > *** Signal 12 > > Stop in /usr/src/gnu/lib/libgcc. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 10:43:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id B3FCB14BF5 for ; Mon, 4 Oct 1999 10:43:43 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id TAA21332; Mon, 4 Oct 1999 19:39:19 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910041739.TAA21332@gratis.grondar.za> To: Peter Wemm Cc: Juan Amado Becerril Castillo , "current@FreeBSD.ORG" Subject: Re: my make world is broken ! Date: Mon, 04 Oct 1999 19:39:18 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 3: *always* build (or try to) and install a new kernel before a > make world as that's a lot easier to back out of. This badly bites the bum of anyone who uses KLD's regularly. I suspect that _now_ is the time to try to make thes build at kernel build time, and also move to some subdirectory that is not nuked straight away. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 10:53: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 579CD14BF5 for ; Mon, 4 Oct 1999 10:52:30 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id TAA21587 for ; Mon, 4 Oct 1999 19:52:29 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910041752.TAA21587@gratis.grondar.za> To: current@freebsd.org Subject: Re: A record? Date: Mon, 04 Oct 1999 19:52:28 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 7:46PM up 375 days, 20:09, 2 users, load averages: 0.00, 0.01, 0.00 > FreeBSD xxxxxx.xxxxxxx.xxx 2.2.6-STABLE FreeBSD 2.2.6-STABLE #0: Tue May 5 15:51:34 SAST 1998 xxxx@xxxxxxxxxx.xxxxxxx.xxx:/usr/src/sys/compile/XXX i38 6 This box was used as a shell server for more than a year; it was hardened for shell use, and served us admirably. We recently (with some sadness) closed down the shell service, but the actual box will live in some other (staff-serving) incarnation. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 11:21: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat194.229.mpoweredpc.net [142.177.194.229]) by hub.freebsd.org (Postfix) with ESMTP id 474B215184; Mon, 4 Oct 1999 11:21:00 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id PAA25985; Mon, 4 Oct 1999 15:19:53 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 4 Oct 1999 15:19:53 -0300 (ADT) From: The Hermit Hacker To: Adrian Penisoara Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Oct 1999, Adrian Penisoara wrote: > > Excuse my intrusion, but could you be so kind to tell me whether you had > the time to build patches for these MMAP-related freezes ? If not could > you recommend me some workarounds ? doubling the ram from 384 -> 768 meg appears to have fixed it for mme... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 11:25:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 47A3915562 for ; Mon, 4 Oct 1999 11:25:37 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p11-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.140]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA04860; Tue, 5 Oct 1999 03:24:22 +0900 (JST) Message-ID: <37F8EFF9.48286CA5@newsguy.com> Date: Tue, 05 Oct 1999 03:20:41 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Juan Amado Becerril Castillo Cc: "current@FreeBSD.ORG" Subject: Re: my make world is broken ! References: <37F37E59.984D7598@rey.moz.com.mx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Juan Amado Becerril Castillo wrote: > > Suggestions ??? Sure. Read the mailing list you are posting to. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Rule 69: Do unto other's code as you'd have it done unto yours To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 11:26:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 2AD1215184 for ; Mon, 4 Oct 1999 11:26:27 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Received: from MexComUSA.NET (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id LAA33879; Mon, 4 Oct 1999 11:26:11 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <37F8F148.296CB506@MexComUSA.NET> Date: Mon, 04 Oct 1999 18:26:16 +0000 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andre Oppermann Cc: current@FreeBSD.ORG Subject: Re: panic: malloc type lacks magic References: <37F89F62.CB5FCA41@pipeline.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andre, I had the same problem with my laptop and what worked for me was to boot it in single user with my old kernel, fsck all disk partitions, mount all partitions -w including root with -u -w, make a new kernel, reboot again in single user and remount everything and make world. I was then ok, but I still cvsuped and made a new worldand kernel just for good measure after everything was working :-) I did that Friday and have had good builds Saturday, Sunday and today. provecho, ed Andre Oppermann wrote: > Hello > > It looks like I fucked my -current box up during the sig_t changes. > I tried made a new kernel before make world but after ifconfig'ing > the network interfaces it panics with: > > panic: malloc type lacks magic > > Making a new world is of course not possible because of the sig_t > changes. > > Any ideas what is going wrong? I'm a little bit lost at this. > > Thanks > -- > Andre > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 11:32:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 2F1B914EFC for ; Mon, 4 Oct 1999 11:32:25 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 6FCA11CC6; Tue, 5 Oct 1999 02:32:24 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray Cc: Juan Amado Becerril Castillo , "current@FreeBSD.ORG" Subject: Re: my make world is broken ! In-reply-to: Your message of "Mon, 04 Oct 1999 19:39:18 +0200." <199910041739.TAA21332@gratis.grondar.za> Date: Tue, 05 Oct 1999 02:32:24 +0800 From: Peter Wemm Message-Id: <19991004183224.6FCA11CC6@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > 3: *always* build (or try to) and install a new kernel before a > > make world as that's a lot easier to back out of. > > This badly bites the bum of anyone who uses KLD's regularly. > > I suspect that _now_ is the time to try to make thes build at > kernel build time, and also move to some subdirectory that is > not nuked straight away. Hmm.. You've got me thinking now... Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 12: 4:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw1a.lmco.com (mailgw1a.lmco.com [192.31.106.7]) by hub.freebsd.org (Postfix) with ESMTP id DDBCE1552F for ; Mon, 4 Oct 1999 12:03:55 -0700 (PDT) (envelope-from George.W.Dinolt@lmco.com) Received: from emss02g01.ems.lmco.com (emss02g01.ems.lmco.com [198.7.15.39]) by mailgw1a.lmco.com (8.8.8/8.8.8) with ESMTP id NAA19750 for ; Mon, 4 Oct 1999 13:03:40 -0600 (MDT) Received: from CONVERSION-DAEMON by lmco.com (PMDF V5.2-32 #38887) id <0FJ300001E9OJM@lmco.com> for freebsd-current@freebsd.org; Mon, 4 Oct 1999 13:03:37 -0600 (MDT) Received: from wdl1.wdl.lmco.com ([137.249.32.1]) by lmco.com (PMDF V5.2-32 #38887) with ESMTP id <0FJ30070UE7689@lmco.com> for freebsd-current@freebsd.org; Mon, 04 Oct 1999 13:01:55 -0600 (MDT) Received: from lmco.com (ird45 [137.249.32.45]) by wdl1.wdl.lmco.com (8.8.8+Sun/8.8.8) with ESMTP id MAA08353 for ; Mon, 04 Oct 1999 12:01:53 -0700 (PDT) Date: Mon, 04 Oct 1999 12:01:55 -0700 From: "George W. Dinolt" Subject: Re: Netscape core dump, happily :-) To: freebsd-current@freebsd.org Message-id: <37F8F9A3.39A9446F@lmco.com> Organization: Lockheed Martin Mission Ground Systems MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running FreeBSD 4.0. I have been seeing the empty core files from netscape 4.61 and (as of last night) 4.7 for at least a week. I use fvwm2 and afterstep-devel. The behavior seems to be independant of the window manager. I rebuilt all my ports (including X and new X aout files) with the new kernel and world as of Saturday, but this has had no effect. Mostly this behavior is anoying, although occasionally I will see a crash when I try to read mail. Things seem a little stabler with netscape in linux emulation mode, but I haven't kept track closely enough to tell. -- George (George.W.Dinolt@lmco.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 12: 9:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 039211552A for ; Mon, 4 Oct 1999 12:09:24 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id PAA00401 for ; Mon, 4 Oct 1999 15:09:55 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Mon, 4 Oct 1999 15:09:54 -0400 (EDT) From: Chuck Robey To: current@freebsd.org Subject: Linux emulation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried to use my copy of WordPerfect 8 to decode an rtf document, like I've done before the signal change, and boy was I surprised. The machine locked up for 10 seconds, then spontaneously rebooted. Anyone else have this experience with Linux emulation? ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 12:13: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 26CF8150D0 for ; Mon, 4 Oct 1999 12:13:05 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id DBA131C23; Mon, 4 Oct 1999 14:16:26 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id CE2E23817; Mon, 4 Oct 1999 14:16:26 -0400 (EDT) Date: Mon, 4 Oct 1999 14:16:26 -0400 (EDT) From: Bill Fumerola To: Juan Amado Becerril Castillo Cc: "current@FreeBSD.ORG" Subject: Re: my make world is broken ! In-Reply-To: <37F38099.78E95151@webwizard.com.mx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Sep 1999, Juan Amado Becerril Castillo wrote: > Suggestions ??? Not mail the list 3 f'ing times, to start. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 12:29:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7B75A14DAC; Mon, 4 Oct 1999 12:29:40 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA68462; Mon, 4 Oct 1999 12:29:21 -0700 (PDT) (envelope-from dillon) Date: Mon, 4 Oct 1999 12:29:21 -0700 (PDT) From: Matthew Dillon Message-Id: <199910041929.MAA68462@apollo.backplane.com> To: Adrian Penisoara Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Excuse my intrusion, but could you be so kind to tell me whether you had :the time to build patches for these MMAP-related freezes ? If not could :you recommend me some workarounds ? : : I have a -stable production server that keeps (solidly) blocking pretty :often (I don't get over 3 days uptimes). If you need details just let me :know. : :> -Matt :> Matthew Dillon :> : Thanks, : Ady (@warpnet.ro) Well, your lockups may or may not be related to the remaining mmap problems. They could be related to the swap fragmentation problems in stable, or they could be related to something else entirely. In order to determine the cause of your lockup problems, some additional information is necessary. The easiest way to get the information is to enable DDB and kernel core dumps so you can panic the machine from the console and get a core. Once you have the core 'cd /var/crash; ps -M vmcore.X -N kernel.X' (where X is the latest dump number) can be used to determine what the processes were doing when they locked up. The two most common VM-related lockups in -stable are: (1) swap metadata fragmentation due to paging in the face of large running processes (system runs out of KVM), and (2) write()ing the mmap'd area of one file descriptor to another. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 13: 6:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id A470F15517 for ; Mon, 4 Oct 1999 13:06:15 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id VAA30530 for current@FreeBSD.org; Mon, 4 Oct 1999 21:50:34 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Mon, 04 Oct 1999 21:50:27 +0200 From: Marcel Moolenaar Message-ID: <37F90503.4A062872@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: Subject: Re: Linux emulation Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > I just tried to use my copy of WordPerfect 8 to decode an rtf document, > like I've done before the signal change, and boy was I surprised. The > machine locked up for 10 seconds, then spontaneously rebooted. > > Anyone else have this experience with Linux emulation? Some reports of crashes have come to me, but none contained the necessary information or simply weren't reproducable. If you think there's something wrong and you want me to take a look at it, you'll have to give me something to work on. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 13: 6:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 2932C1555D for ; Mon, 4 Oct 1999 13:06:15 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id VAA28543 for current@FreeBSD.org; Mon, 4 Oct 1999 21:42:57 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Mon, 04 Oct 1999 21:42:50 +0200 From: Marcel Moolenaar Message-ID: <37F9033A.42278634@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: HEADS UP: rebirth of sigcontext Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just committed the sigcontext changes. sigreturn can now again be called with an argument of type sigcontext but also with an argument of type ucontext_t. Also, signal handlers can define their third argument to be both of type struct sigcontext* and ucontext_t*. This should fix the source incompatibility introduced by the sigset_t changes. Alpha users are again advised to take precaution. Not that I expect filesystem crashes, but simply because I can't test those changes. Maybe in the future... NOTE: Recompilation of doscmd is required. For your convenience, the commit log message: Re-introduction of sigcontext. struct sigcontext and ucontext_t/mcontext_t are defined in such a way that both (ie struct sigcontext and ucontext_t) can be passed on to sigreturn. The signal handler is still given a ucontext_t for maximum flexibility. For backward compatibility sigreturn restores the state for the alternate signal stack from sigcontext.sc_onstack and not from ucontext_t.uc_stack. A good way to determine which value the application has set and thus which value to use, is still open for discussion. NOTE: This change should only affect those binaries that use sigcontext and/or ucontext_t. In the source tree itself this is only doscmd. Recompilation is required for those applications. This commit also fixes a lot of style bugs without hopefully adding new ones. NOTE: struct sigaltstack.ss_size now has type size_t again. For some reason I changed that into unsigned int. Parts submitted by: bde sigaltstack bug found by: bde -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 14:21:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id B062115299 for ; Mon, 4 Oct 1999 14:21:47 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id OAA11647; Mon, 4 Oct 1999 14:40:16 -0700 (PDT) Date: Mon, 4 Oct 1999 14:40:15 -0700 (PDT) From: Alfred Perlstein To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: new signal stuff breaks libc_r? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG replying to my own message but I think I found a solution... It seems that something was stale in /usr/include, I was able to fix the problem by: rm -rf /usr/include/* cd /usr/src make includes cd /usr/src/lib/libc_r make make install funny part is that two successive make worlds didn't seem to work, but this did. *shrug* sorry for the noise, -Alfred On Mon, 4 Oct 1999, Alfred Perlstein wrote: > > On Mon, 4 Oct 1999, Marcel Moolenaar wrote: > > > Alfred Perlstein wrote: > > > > > > Since the signal changes... > > > > > > I'm finding that it _seems_ since libc_r isn't including something > > > that properly defines __inline to inline that i'm getting unresolved > > > symbols when linking or running programs that depend on libc_r. > > > > > > Anyone else getting this? > > > > > > compiling a void main(void){} with -pthread will barf for me, > > > using -static I'm able to see which files are missing which > > > inlines. > > > > This isn't a problem report I can deal with. Please be very explicit. > > I think it's something I may have broken somehow, but i'm not > exactly sure: > > ~ % cat t.c > #include > > int main(void) { > > printf("hello world.\n"); > > } > > .(14:17:52)(bright@thumper) > ~ % gcc -static t.c -pthread > /usr/lib/libc_r.a(uthread_sig.o): In function `_dispatch_signals': > /home/src/lib/libc_r/uthread/uthread_sig.c(.text+0xf05): undefined reference to `__sigisempty' > > For some reason it looks like __inline is being defined like: > > #define __inline > > so that when signalvar.h is included the inlines for __sigisempty > aren't getting the "inline_ prefix and are assumed to be somewhere > else. > > I asked phk about it and he's not having the problem with a recent > -current so I'll be futzing around searching for the reason this > is happening. > > I just deleted my source tree and I'm going to re-check it out, > maybe something got corrupted? > > -Alfred > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 14:28:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id CCA6515563 for ; Mon, 4 Oct 1999 14:27:59 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id 7F776A84A; Mon, 4 Oct 1999 23:27:58 +0200 (CEST) Date: Mon, 4 Oct 1999 23:27:58 +0200 From: Guido van Rooij To: freebsd-current@freebsd.org Subject: make buildworld broken? Message-ID: <19991004232758.B39982@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a 3.3.-stable system and somehow I cannot make buildworld a current tree. The porblem is: cc -c -I/alt/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/alt/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/alt/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /alt/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Signal 12 Stop in /alt/usr/src/gnu/lib/libgcc. *** Error code 1 This system has been running and compilig a lot of other FreeBSD versions in the last 3 years, and has never had any memory problems at all. IIRC a couple of days ago a buildworld worked (but I had to reinstall due to a different disksetup) Is this a known problem? -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 15:23: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id 6C2341558F for ; Mon, 4 Oct 1999 15:22:11 -0700 (PDT) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.3/8.9.3) id GAA66415; Tue, 5 Oct 1999 06:21:55 +0800 (WST) (envelope-from mike) From: Michael Kennett Message-Id: <199910042221.GAA66415@laurasia.com.au> Subject: Re: make buildworld broken? In-Reply-To: <19991004232758.B39982@gvr.gvr.org> from Guido van Rooij at "Oct 4, 1999 11:27:58 pm" To: guido@gvr.org (Guido van Rooij) Date: Tue, 5 Oct 1999 06:21:55 +0800 (WST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Guido, > I have a 3.3.-stable system and somehow I cannot make buildworld > a current tree. > The porblem is: > cc -c -I/alt/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/alt/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/alt/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /alt/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > *** Signal 12 There have been some major changes in the '-current' tree allowing more than 32 signals. These changes were documented (very well) in a 'HEADS-UP' by Marcel when he committed his changes. I've included that HEADS-UP for your reference below. There is a long thread of discussions on -current about these changes. Check the archives for details. In particular, you'll find that it is necessary to build the kernel and *BOOT* the new kernel before a make world. There is continuing work being done on these changes. > This system has been running and compilig a lot of other FreeBSD versions > in the last 3 years, and has never had any memory problems at all. It is not a memory problem. It is a change in the signalling mechanism of the kernel. > Is this a known problem? Yes, and it is well documented in the -current mailing lists. Mike Kennett (mike@laurasia.com.au) -----Included: To: current@FreeBSD.ORG Date: Wed, 29 Sep 1999 17:29:40 +0200 From: Marcel Moolenaar Message-ID: <37F23064.98EEBC67@scc.nl> Subject: HEADS UP: sigset_t changes committed Sender: owner-freebsd-current@FreeBSD.ORG I just finished committing the sigset_t changes I worked on for the last 5 weeks. Before attempting to build world, you must make and install a new kernel. The new kernel will contain new syscalls that are needed during build world. doscmd is currently not being build because it needs fixing first. Alpha users are invited to test the changes since I've not been able to do that myself. I've done all I possibly could do to make this a success. I've attached the commit logs for everyone to see. Please report problems as soon as possible. Thanks, sigset_t change (part 1 of 5) ----------------------------- Rename sigaction, sigprocmask, sigpending and sigsuspend to osigaction, osigprocmask, osigpending and osigsuspend (resp) and add new syscalls for them to support the new sisgset_t without breaking existing binaries. Change the prototype of sigaltstack to use the typedef stack_t instead of struct sigaltstack to reflect that it is SUSv2 compliant. Also, rename sigreturn to osigreturn and add a new syscall to support the modified stackframe. The change is caused by sigreturn operating on ucontext_t now and the fact that siginfo_t has been updated to conform to SUSv2. sigset_t change (part 2 of 5) ----------------------------- The core of the signalling code has been rewritten to operate on the new sigset_t. No methodological changes have been made. Most references to a sigset_t object are through macros (see signalvar.h) to create a level of abstraction and to provide a basis for further improvements. The NSIG constant has not been changed to reflect the maximum number of signals possible. The reason is that it breaks programs (especially shells) which assume that all signals have a non-null name in sys_signame. See src/bin/sh/trap.c for an example. Instead _SIG_MAXSIG has been introduced to hold the maximum signal possible with the new sigset_t. struct sigprop has been moved from signalvar.h to kern_sig.c because a) it is only used there, and b) access must be done though function sigprop(). The latter because the table doesn't holds properties for all signals, but only for the first NSIG signals. signal.h has been reorganized to make reading easier and to add the new and/or modified structures. The "old" structures are moved to signalvar.h to prevent namespace polution. Especially the coda filesystem suffers from the change, because it contained lines like (p->p_sigmask == SIGIO), which is easy to do for integral types, but not for compound types. NOTE: kdump (and port linux_kdump) must be recompiled. Thanks to Garrett Wollman and Daniel Eischen for pressing the importance of changing sigreturn as well. sigset_t change (part 3 of 5) ----------------------------- By introducing a new sigframe so that the signal handler operates on the new siginfo_t and on ucontext_t instead of sigcontext, we now need two version of sendsig and sigreturn. A flag in struct proc determines whether the process expects an old sigframe or a new sigframe. The signal trampoline handles which sigreturn to call. It does this by testing for a magic cookie in the frame. The alpha uses osigreturn to implement longjmp. This means that osigreturn is not only used for compatibility with existing binaries. To handle the new sigset_t, setjmp saves it in sc_reserved (see NOTE). the struct sigframe has been moved from frame.h to sigframe.h to handle the complex header dependencies that was caused by the new sigframe. NOTE: For the i386, the size of jmp_buf has been increased to hold the new sigset_t. On the alpha this has been prevented by using sc_reserved in sigcontext. sigset_t change (part 4 of 5) ----------------------------- The compatibility code and/or emulators have been updated: iBCS2 now mostly uses the older syscalls. SVR4 now properly handles all signals. This has been achieved by using the new sigset_t throughout the emulator. The Linuxulator has been severely updated. Internally the new Linux sigset_t is made the default. These are then mapped to and from the new FreeBSD sigset_t. Also, rt_sigsuspend has been implemented in the Linuxulator. Implementing this syscall basicly caused all this sigset_t changing in the first place and the syscall has been used throughout the change as a means for testing. It basicly is too much work to undo the implementation so that it can later be added again. A special note on the use of sv_sigtbl and sv_sigsize in struct sysentvec: Every signal larger than sv_sigsize is not translated and is passed on to the signal handler unmodified. Signals in the range 1 upto and including sv_sigsize are translated. The rationale is that only the system defined signals need to be translated. The emulators also have been updated so that the translation tables are only indexed for valid (system defined) signals. This change also fixes the translation bug already in the SVR4 emulator. sigset_t change (part 5 of 5) ----------------------------- Most of the userland changes are in libc. For both the alpha and the i386 setjmp has been changed to accomodate for the new sigset_t. Internally, libc is mostly rewritten to use the new syscalls. The exception is in compat-43/sigcompat.c The POSIX thread library has also been rewritten to use the new sigset_t. Except, that it currently only handles NSIG signals instead of the maximum _SIG_MAXSIG. This should not be a problem because current applications don't use any signals higher than NSIG. There are version bumps for the following libraries: libdialog libreadline libc libc_r libedit libftpio libss These libraries either a) have one of the modified structures visible in the interface, or b) use sigset_t internally and may cause breakage if new binaries are used against libraries that don't have the sigset_t change. This not an immediate issue, but will be as soon as applications start using the new range to its fullest. NOTE: libncurses already had an version bump and has not been given one now. NOTE: doscmd is a real casualty and has been disconnected for the moment. Reconnection will eventually happen after doscmd has been fixed. I'm aware that being the last one to touch it, I'm automaticly promoted to being maintainer. According to good taste this means that I will receive a badge which either will be glued or mechanically stapled, drilled or otherwise violently forced onto me :-) NOTE: pcvt/vttest cannot be compiled with -traditional. The change cause sys/types to be included along the way which contains the const and volatile modifiers. I don't consider this a solution, but more a workaround. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 16: 9:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 190A71553B for ; Mon, 4 Oct 1999 16:08:49 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from d133.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id JAA04039; Tue, 5 Oct 1999 09:03:04 +1000 Date: Tue, 5 Oct 1999 09:01:28 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Mark Murray Cc: Peter Wemm , Juan Amado Becerril Castillo , "current@FreeBSD.ORG" Subject: Re: my make world is broken ! In-Reply-To: <199910041739.TAA21332@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 3: *always* build (or try to) and install a new kernel before a > > make world as that's a lot easier to back out of. > > This badly bites the bum of anyone who uses KLD's regularly. 4: Don't use modules in -current unless you know what you are doing. This normally means not using modules in -current except for ones that you are developing. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 16:16:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 528AB14FB7 for ; Mon, 4 Oct 1999 16:16:42 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id IAA13155; Tue, 5 Oct 1999 08:45:41 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199910042315.IAA13155@gizmo.internode.com.au> Subject: Re: A record? To: mark@grondar.za (Mark Murray) Date: Tue, 5 Oct 1999 08:45:40 +0930 (CST) Cc: current@FreeBSD.ORG In-Reply-To: <199910041752.TAA21587@gratis.grondar.za> from "Mark Murray" at Oct 4, 99 07:52:28 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > 7:46PM up 375 days, 20:09, 2 users, load averages: 0.00, 0.01, 0.00 > > FreeBSD xxxxxx.xxxxxxx.xxx 2.2.6-STABLE FreeBSD 2.2.6-STABLE #0: Tue May 5 15:51:34 SAST 1998 xxxx@xxxxxxxxxx.xxxxxxx.xxx:/usr/src/sys/compile/XXX i38 > 6 > > This box was used as a shell server for more than a year; it was > hardened for shell use, and served us admirably. We recently (with > some sadness) closed down the shell service, but the actual box > will live in some other (staff-serving) incarnation. A similar box which I rebooted (for an upgrade from 2.2.5 to 3.2) about a fortnight ago: 3:38PM up 471 days, 5:59, 1 user, load averages: 0.00, 0.02, 0.00 ... and, before this thread gets completely out of control, I direct posters to http://uptime.viper.net.au (warning: if you're easily offended, don't bother). - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 18:38:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5FDBF14CDF for ; Mon, 4 Oct 1999 18:38:27 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA16410; Mon, 4 Oct 1999 18:38:26 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA37679; Mon, 4 Oct 1999 18:38:26 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 4 Oct 1999 18:38:26 -0700 (PDT) Message-Id: <199910050138.SAA37679@vashon.polstra.com> To: chad@DCFinc.com Subject: Re: New CVSup mirror sites In-Reply-To: <199910031336.GAA10018@freeway.dcfinc.com> References: <199910031336.GAA10018@freeway.dcfinc.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199910031336.GAA10018@freeway.dcfinc.com>, Chad R. Larson wrote: > > John, do you have usage statistics broken out for each server? I don't, but I wish I did. It would be an interesting project for somebody to write tools that could analyze the cvsupd log files to get information like that. Wolfram Schneider's "cvsup2httplog" script in the contrib area of the CVSup source distribution might be a good start toward that. Unfortunately I don't have time to work on it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 19: 5:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.ihug.co.nz (tk2.ihug.co.nz [203.29.160.14]) by hub.freebsd.org (Postfix) with ESMTP id A09A9151AA for ; Mon, 4 Oct 1999 19:05:05 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (p35-max2.dun.ihug.co.nz [209.76.100.98]) by smtp2.ihug.co.nz (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA19922; Tue, 5 Oct 1999 15:04:27 +1300 Message-ID: <37F95CA9.A353FE73@es.co.nz> Date: Tue, 05 Oct 1999 15:04:25 +1300 From: Mike Muir X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Newton Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: A record? References: <199910042315.IAA13155@gizmo.internode.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Newton wrote: > A similar box which I rebooted (for an upgrade from 2.2.5 to 3.2) about > a fortnight ago: > > 3:38PM up 471 days, 5:59, 1 user, load averages: 0.00, 0.02, 0.00 > > ... and, before this thread gets completely out of control, I direct > posters to http://uptime.viper.net.au (warning: if you're easily offended, > don't bother). Using options HZ (without a value) you can make any system run as fast as it can, one p100 was elapsing days in 20 minutes.. i had its uptime around 1100days in about 2 weeks.. so nerr my dick is bigger than yours ;) P.S nothing BAD happened over the year 2000 ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 19:23:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 2544C15063 for ; Mon, 4 Oct 1999 19:23:11 -0700 (PDT) (envelope-from areilly@nsw.bigpond.net.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id MAA23984 for ; Tue, 5 Oct 1999 12:23:06 +1000 (EST) X-BPC-Relay-Envelope-From: areilly@nsw.bigpond.net.au X-BPC-Relay-Envelope-To: X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20] X-BPC-Relay-Info: Message delivered directly. Received: from areilly.bpc-users.org (CPE-24-192-49-170.nsw.bigpond.net.au [24.192.49.170]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id MAA26438 for ; Tue, 5 Oct 1999 12:23:00 +1000 (EST) Received: (qmail 82270 invoked by uid 1000); 5 Oct 1999 02:23:00 -0000 From: "Andrew Reilly" Date: Tue, 5 Oct 1999 12:23:00 +1000 To: Daniel Eischen Cc: des@flood.ping.uio.no, marcel@scc.nl, current@FreeBSD.ORG Subject: Re: new sigset_t and upgrading: a proposal Message-ID: <19991005122300.A79869@gurney.reilly.home> References: <199910011936.PAA11014@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199910011936.PAA11014@pcnet1.pcnet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 01, 1999 at 03:36:11PM -0400, Daniel Eischen wrote: > But this still doesn't entirely solve the problem. You still have > to build and install a new kernel before installing the world. Of course! Installing the world _is_ upgrading your operating system. I don't see anyone suggesting that ELF applications should work on kernels that only support a.out binaries. Neither should programs that use 64-bit file offsets work on kernels that predate that change. (Note that this is entirely different from the issue of being able to use such a system to _build_ the new world.) > While this is typically what most -current folks do anyways, it > still prevents backing up to a previous kernel after the install > world. Yes. That's what backup tapes are for. If you're going to nuke your entire operating system, you'd better be ready to recover from tores. > It seems like libc should be built to be compatible with the kernel > that is currently running. After installing world and testing the > new kernel, a subsequent make world (or some other target to get > just the libs) can be done to make the libs use the new syscalls. > I like to keep old known working kernels around just in case there > are some serious bugs with the current one. Once a kernel has > proven itself somewhat stable, you can then upgrade the libs. Or, you could do it the sensible way: upgrade the kernel to support the new syscalls, and test it for a while _before_ building and installing a world that depends on it. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 19:26: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id DA55814EDC for ; Mon, 4 Oct 1999 19:25:59 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA16603 for ; Mon, 4 Oct 1999 19:25:58 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA39110; Mon, 4 Oct 1999 19:25:57 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 4 Oct 1999 19:25:57 -0700 (PDT) Message-Id: <199910050225.TAA39110@vashon.polstra.com> To: current@freebsd.org Subject: Re: CVSup core dumps In-Reply-To: <199910012137.PAA04480@shambhala.cgd.ucar.edu> References: <199910012137.PAA04480@shambhala.cgd.ucar.edu> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen a few reports that CVSup has suddenly started dumping core on a segmentation violation under -current, but I need more information. For starters, I would like to know whether the static binary (ports/net/cvsup-bin) works or not under the very latest -current on the i386. Could somebody please check that and report back to the list? I can't sacrifice my i386 -current machine to the cause right now. Also, for those of you who are experiencing problems: Please state as precisely as possible: - which vintage of -current are you running? - what is the output from "cvsup -v"? - is "cvsup" a static binary or is it dynamically linked? - did you build it, or did you simply install a binary? - if you built it, when did you build it? Note, you are going to have trouble getting much out of the core dumps from the binaries, because they're a.out. I've placed an unstripped ELF binary here if you'd like to help out by getting a stack trace: http://www.freebsd.org/~jdp/cvsup-16.0.gz The compressed file is about 2.3 MB in size. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 20:12:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 81A8814D28 for ; Mon, 4 Oct 1999 20:12:16 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id XAA19811; Mon, 4 Oct 1999 23:12:11 -0400 (EDT) Date: Mon, 4 Oct 1999 23:12:10 -0400 (EDT) From: "Matthew N. Dodd" To: Timo Geusch Cc: Soren Schmidt , freebsd-current@FreeBSD.ORG Subject: Re: Recent kernel hangs during boot with pnp sio. In-Reply-To: <19991004070925.A19400@tabby.timog.prestel.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Oct 1999, Timo Geusch wrote: > If you're interested I can send you the source code for the driver but it is > not clear if it works on -current at the moment as I haven't updated for > some time. Send it here as I'm working on if_ep in some fashion. Someone find me a verified PnP 3c509 too. I'll pay shipping and $10 for one. I've got a normal 3c509 and a 3c579 in transit and a 3c529 in use. I'd be interested in a 3c589 for testing purposes but at this point it would be of little use has I've not yet put my hands on a ISA to PCMCIA reader. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 22: 1:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (Postfix) with ESMTP id 0EFFF151D1 for ; Mon, 4 Oct 1999 22:01:23 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (jbloom.ne.mediaone.net [24.128.100.196]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id BAA14300; Tue, 5 Oct 1999 01:01:13 -0400 (EDT) Message-ID: <37F985B4.237A48A1@acm.org> Date: Tue, 05 Oct 1999 00:59:32 -0400 From: Jim Bloom X-Mailer: Mozilla 4.61 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: CVSup core dumps References: <199910012137.PAA04480@shambhala.cgd.ucar.edu> <199910050225.TAA39110@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My machine is dual boot and I don't have time to reboot now. (I need to get some sleep.) I'll provide what information I can quickly and will test things further tomorrow evening. I was seeing the core dumps from gui cvsup. My current was a couple different cvsup runs on Saturday and Sunday. I am using the static binary installed from the ports collection. I don't have a date or version right now, but seem to recall it being 16.0. As others have mentioned, running cvsup under truss works. I'll let you know more tomorrow night if there is anything I can add. Jim Bloom bloom@acm.org John Polstra wrote: > > I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. Could somebody please check that and report > back to the list? I can't sacrifice my i386 -current machine to the > cause right now. > > Also, for those of you who are experiencing problems: Please state > as precisely as possible: > > - which vintage of -current are you running? > - what is the output from "cvsup -v"? > - is "cvsup" a static binary or is it dynamically linked? > - did you build it, or did you simply install a binary? > - if you built it, when did you build it? > > Note, you are going to have trouble getting much out of the core dumps > from the binaries, because they're a.out. I've placed an unstripped > ELF binary here if you'd like to help out by getting a stack trace: > > http://www.freebsd.org/~jdp/cvsup-16.0.gz > > The compressed file is about 2.3 MB in size. > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "No matter how cynical I get, I just can't keep up." -- Nora Ephron > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 22:55:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 1628E1532C for ; Mon, 4 Oct 1999 22:55:02 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id HAA32424; Tue, 5 Oct 1999 07:50:17 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910050550.HAA32424@gratis.grondar.za> To: Bruce Evans Cc: Peter Wemm , Juan Amado Becerril Castillo , "current@FreeBSD.ORG" Subject: Re: my make world is broken ! Date: Tue, 05 Oct 1999 07:50:17 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > 3: *always* build (or try to) and install a new kernel before a > > > make world as that's a lot easier to back out of. > > > > This badly bites the bum of anyone who uses KLD's regularly. > > 4: Don't use modules in -current unless you know what you are doing. > This normally means not using modules in -current except for ones > that you are developing. Sure. This either needs spelling out, or it needs better automation so as to "work as expected". M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 4 23:34:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 0122B153D4 for ; Mon, 4 Oct 1999 23:34:20 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA33418; Tue, 5 Oct 1999 08:33:55 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910050633.IAA33418@gratis.grondar.za> To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: CVSup core dumps Date: Tue, 05 Oct 1999 08:33:54 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. Could somebody please check that and report > back to the list? I can't sacrifice my i386 -current machine to the > cause right now. The static binary seems to be OK an a 3-day-old CURRENT. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 0:23:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 7E1BB1551F for ; Tue, 5 Oct 1999 00:23:08 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id KAA25541; Tue, 5 Oct 1999 10:22:47 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id CFD30F0; Tue, 5 Oct 1999 10:23:05 +0300 (EEST) Date: Tue, 5 Oct 1999 10:23:05 +0300 From: Vallo Kallaste To: Mark Murray Cc: John Polstra , current@FreeBSD.ORG Subject: Re: CVSup core dumps Message-ID: <19991005102305.A17963@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <199910050633.IAA33418@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199910050633.IAA33418@gratis.grondar.za>; from Mark Murray on Tue, Oct 05, 1999 at 08:33:54AM +0200 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 05, 1999 at 08:33:54AM +0200, Mark Murray wrote: > > I've seen a few reports that CVSup has suddenly started dumping > > core on a segmentation violation under -current, but I need more > > information. For starters, I would like to know whether the static > > binary (ports/net/cvsup-bin) works or not under the very latest > > -current on the i386. Could somebody please check that and report > > back to the list? I can't sacrifice my i386 -current machine to the > > cause right now. > > The static binary seems to be OK an a 3-day-old CURRENT. And as opposite, the cvsup 16.0 static a.out binary, downloaded a day ago from ftp.freebsd.org dumps reliably core for me. I'm sorry, can't provide any info yet because it's my home machine. The machine runs also 3 day old -current, perhaps with deviation of some 12 hours or so, can't remember. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 1:59:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id 00D7415550 for ; Tue, 5 Oct 1999 01:57:59 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id 6AAB8A84A; Tue, 5 Oct 1999 10:56:47 +0200 (CEST) Date: Tue, 5 Oct 1999 10:56:47 +0200 From: Guido van Rooij To: Michael Kennett Cc: freebsd-current@FreeBSD.ORG Subject: Re: make buildworld broken? Message-ID: <19991005105647.A44795@gvr.gvr.org> References: <19991004232758.B39982@gvr.gvr.org> <199910042221.GAA66415@laurasia.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199910042221.GAA66415@laurasia.com.au>; from Michael Kennett on Tue, Oct 05, 1999 at 06:21:55AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 05, 1999 at 06:21:55AM +0800, Michael Kennett wrote: > > > Is this a known problem? > > Yes, and it is well documented in the -current mailing lists. I feel embarrassed as I'v just spoken to Marcel a couple fo days ago. However I just resubscribed to -current. I did look in the UPDATING file and saw the sigset_t change but overlooked the 'build and boot a new kernel' part :-( -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 2:38:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 130F014DF2 for ; Tue, 5 Oct 1999 02:38:25 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA28158 for current@FreeBSD.org; Tue, 5 Oct 1999 11:11:30 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Tue, 05 Oct 1999 11:11:20 +0200 From: Marcel Moolenaar Message-ID: <37F9C0B8.B4E352D@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199910012137.PAA04480@shambhala.cgd.ucar.edu>, <199910050225.TAA39110@vashon.polstra.com> Subject: Re: CVSup core dumps Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. I received 3 reports on cvsup dumping core. At least 2 involved static aout binaries. The third was solved by changing which shell was running the script containing cvsup. (???) > For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. It coredumps. See below. > > - which vintage of -current are you running? FreeBSD scones.sup.scc.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #17: Mon Oct 4 10:33:12 CEST 1999 marcel@scones.sup.scc.nl:/usr/src/sys/compile/SCONES i386 > - what is the output from "cvsup -v"? *** *** runtime error: *** Segmentation violation - possible attempt to dereference NIL *** pc = 0x2f *** Abort trap (core dumped) > Note, you are going to have trouble getting much out of the core dumps > from the binaries, because they're a.out. I've placed an unstripped > ELF binary here if you'd like to help out by getting a stack trace: Great! I'll get to it. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 3:59:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 78EE4155CE for ; Tue, 5 Oct 1999 03:58:20 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p08-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.105]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id TAA16170; Tue, 5 Oct 1999 19:53:50 +0900 (JST) Message-ID: <37F9BD1B.94F78707@newsguy.com> Date: Tue, 05 Oct 1999 17:55:55 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Bruce Evans Cc: Mark Murray , Peter Wemm , Juan Amado Becerril Castillo , "current@FreeBSD.ORG" Subject: Re: my make world is broken ! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > > > 3: *always* build (or try to) and install a new kernel before a > > > make world as that's a lot easier to back out of. > > > > This badly bites the bum of anyone who uses KLD's regularly. > > 4: Don't use modules in -current unless you know what you are doing. > This normally means not using modules in -current except for ones > that you are developing. This is not actually relevant. If the procedure becomes first kernel then world, it will affect -stable sooner or later. Obviously, we have to deal with it _before_ 4.x becomes -stable. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Rule 69: Do unto other's code as you'd have it done unto yours To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 5: 2:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 5308714E97; Tue, 5 Oct 1999 05:01:59 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id PAA01540; Tue, 5 Oct 1999 15:02:07 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Tue, 5 Oct 1999 15:02:07 +0300 (EEST) From: Adrian Penisoara To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... In-Reply-To: <199910041929.MAA68462@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Mon, 4 Oct 1999, Matthew Dillon wrote: > : Excuse my intrusion, but could you be so kind to tell me whether you had > :the time to build patches for these MMAP-related freezes ? If not could > :you recommend me some workarounds ? > : > : I have a -stable production server that keeps (solidly) blocking pretty > :often (I don't get over 3 days uptimes). If you need details just let me > :know. > : > :> -Matt > :> Matthew Dillon > :> > : Thanks, > : Ady (@warpnet.ro) > > Well, your lockups may or may not be related to the remaining mmap > problems. They could be related to the swap fragmentation problems > in stable, or they could be related to something else entirely. In > order to determine the cause of your lockup problems, some additional > information is necessary. The easiest way to get the information is > to enable DDB and kernel core dumps so you can panic the machine from The problem is that the machine is completely locked, I can't get into the debugger with CTR-ALT-ESC; no panics so there are no coredumps catched. Any advise ? Could you escape in the debugger when you were hit by these bugs ? > the console and get a core. Once you have the core > 'cd /var/crash; ps -M vmcore.X -N kernel.X' (where X is the latest > dump number) can be used to determine what the processes were doing > when they locked up. > > The two most common VM-related lockups in -stable are: > > (1) swap metadata fragmentation due to paging in the face of large > running processes (system runs out of KVM), and I have: squid (20Mb), nntpcached (17Mb SIZE, 1Mb RES), apache, named, MFS, a few PPP processes and the rest of the standard menu. > > (2) write()ing the mmap'd area of one file descriptor to another. > OK, how about some workarounds, I can't wait anylonger for this to be fixed, my situation got critical. Should I downgrade to 3.1-RELEASE (that hadn't exhibit this way) or can I dare a 4.0-CURRENT (are these problems present in -current too ?) ? > -Matt > Matthew Dillon > > Thanks, Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 5: 8:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from pa.scotland.net (pa1.scotland.net [194.247.64.132]) by hub.freebsd.org (Postfix) with ESMTP id 4540A14D47 for ; Tue, 5 Oct 1999 05:08:38 -0700 (PDT) (envelope-from freebsd@timog.prestel.co.uk) Received: from [148.176.234.38] (helo=timog.prestel.co.uk) by pa.scotland.net with esmtp (Exim 2.12 #4) id 11YTOZ-00056O-00 for freebsd-current@freebsd.org; Tue, 5 Oct 1999 13:08:40 +0100 Received: (qmail 21379 invoked by uid 1002); 5 Oct 1999 05:57:18 -0000 Date: Tue, 5 Oct 1999 06:57:18 +0100 From: Timo Geusch To: "Matthew N. Dodd" Cc: freebsd-current@freebsd.org Subject: Re: Recent kernel hangs during boot with pnp sio. Message-ID: <19991005065717.A21367@tabby.timog.prestel.co.uk> References: <19991004070925.A19400@tabby.timog.prestel.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Matthew N. Dodd on Mon, Oct 04, 1999 at 11:12:10PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 04, 1999 at 11:12:10PM -0400, Matthew N. Dodd wrote: > On Mon, 4 Oct 1999, Timo Geusch wrote: > > If you're interested I can send you the source code for the driver but it is > > not clear if it works on -current at the moment as I haven't updated for > > some time. > > Send it here as I'm working on if_ep in some fashion. I'll send it once I verified that it (still) works with -current. The work dates from before newpnp, Also, some indication as to where you made changes would benice - my PnP changes are pretty self-contained but I made some more general changes that might cause problems. Anyway I'll get back to you end of next week (earliest I can manage). > Someone find me a verified PnP 3c509 too. I'll pay shipping and $10 for > one. I've got a normal 3c509 and a 3c579 in transit and a 3c529 in use. > I'd be interested in a 3c589 for testing purposes but at this point it > would be of little use has I've not yet put my hands on a ISA to PCMCIA > reader. Afaik all 3C509B's are PnP. At least here in the UK there is not shortage of those cards. Timo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 5:25:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 14AB7155BB for ; Tue, 5 Oct 1999 05:22:21 -0700 (PDT) (envelope-from jfh@jfh00.fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.3/8.9.3) id OAA31678; Tue, 5 Oct 1999 14:22:17 +0200 (CEST) (envelope-from jfh) To: freebsd-current@freebsd.org Subject: python-1.5.2 port broken with current From: Fritz Heinrichmeyer Date: 05 Oct 1999 14:22:16 +0200 Message-ID: Lines: 26 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) XEmacs/21.2 (Shinjuku) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG python-1.5.2 is broken with current this week when compiled with the "--with-fpectl" option (a hack using jmpbuf.h, signal.h etc.) which is default in the ports collection. Exponentiation fails i. e. Python 1.5.2 .... [GCC egcs-2.91.66 19990314 (egcs-1.1.2 on freebsd4 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam >>> 3**1.5 Traceback (innermost last): File "", line 1, in ? OverflowError: (14, 'Bad address') >>> (without --with-fpectl): make test output: 52 tests OK. 1 test failed: test_fcntl 8 tests skipped: test_al ... test_sunaudiodev Last week the fcntl-tests failed the first time but this does no harm to i.e. the "sketch" program. -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 5:35:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 3EDC9155C9 for ; Tue, 5 Oct 1999 05:35:00 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id OAA03176 for ; Tue, 5 Oct 1999 14:34:47 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma003172; Tue, 5 Oct 99 14:34:47 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id OAA13064 for ; Tue, 5 Oct 1999 14:34:45 +0200 (MET DST) Received: (qmail 73385 invoked by uid 666); 5 Oct 1999 12:35:05 -0000 Date: Tue, 5 Oct 1999 14:35:05 +0200 From: Jos Backus To: current@FreeBSD.org Subject: Re: CVSup core dumps Message-ID: <19991005143505.D610@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <199910012137.PAA04480@shambhala.cgd.ucar.edu>, <199910050225.TAA39110@vashon.polstra.com> <37F9C0B8.B4E352D@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <37F9C0B8.B4E352D@scc.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fwiw, the problem seems to have disappeared over here. I'll check at home later. FreeBSD hal.mpn.cp.philips.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Oct 5 09:36:29 CEST 1999 jos@hal.mpn.cp.philips.com:/usr/src/sys/compile/HAL i386 Cheers, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 5:52:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from panix.com (panix.com [166.84.0.226]) by hub.freebsd.org (Postfix) with ESMTP id D40C615015 for ; Tue, 5 Oct 1999 05:52:14 -0700 (PDT) (envelope-from rsi@panix.com) Received: (from rsi@localhost) by panix.com (8.8.5/8.8.8/PanixU1.4) id IAA29417; Tue, 5 Oct 1999 08:52:07 -0400 (EDT) Message-Id: <199910051252.IAA29417@panix.com> To: John Polstra Cc: current@freebsd.org Subject: Re: CVSup core dumps References: <199910012137.PAA04480@shambhala.cgd.ucar.edu> <199910050225.TAA39110@vashon.polstra.com> From: Rajappa Iyer Date: 05 Oct 1999 08:52:06 -0400 Reply-To: rsi@panix.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: > I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. Could somebody please check that and report > back to the list? I can't sacrifice my i386 -current machine to the > cause right now. I don't have access to the machine right now, but I installed the cvsup-bin (both GUI and non-GUI versions) and both core dumped for me. Both versions were obtained from ftp://ftp.freebsd.org/pub/FreeBSD/development/CVSup/binaries This is on the latest -current (as of 9PM Oct 4, 99). Running it under truss helps with the core dump, but runs out of swap space very quickly. Truss keeps complaining about free()'ing a pointer that does not point to allocated memory. If you want more details, I shall be happy to provide them this evening. Hope this helps, Regards, Rajappa -- a.k.a. Rajappa Iyer. New York, New York. We're too busy mopping the floor to turn off the faucet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 6: 1:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with SMTP id 584D514F74 for ; Tue, 5 Oct 1999 06:00:52 -0700 (PDT) (envelope-from matt@camtech.net.au) Received: from dialup-ad-16-74.camtech.net.au ([203.55.241.74]) by camtech.net.au ; Tue, 05 Oct 1999 22:30:47 +0930 Date: Tue, 5 Oct 1999 22:31:08 +0930 (CST) From: Matthew Thyer X-Sender: matt@localhost Reply-To: thyerm@camtech.net.au To: John Polstra Cc: current@freebsd.org Subject: Not for me. (was: CVSup core dumps) In-Reply-To: <199910050225.TAA39110@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just an anti-me too. Static cvsup works perfectly for me (installed from ports cvsup-bin on Sept 9th). I run it both on my dumb terminal and on my X display. (My X configuration is XFree86 3.3.5, Gnome/Enlightenment [all built Sept 9th after a make world]). My shell is tcsh 6.09 (built Sept 1st). I have never had cvsup-bin core dump. I have built the world twice since the signal changes and am currently running on my build which completed about 36 hours ago. localhost# {8} cvsup -v CVSup client, GUI version Software version: REL_16_0 Protocol version: 16.0 http://www.polstra.com/projects/freeware/CVSup/ Report problems to cvsup-bugs@polstra.com localhost# {9} On Mon, 4 Oct 1999, John Polstra wrote: > I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. Could somebody please check that and report > back to the list? I can't sacrifice my i386 -current machine to the > cause right now. > > Also, for those of you who are experiencing problems: Please state > as precisely as possible: > > - which vintage of -current are you running? > - what is the output from "cvsup -v"? > - is "cvsup" a static binary or is it dynamically linked? > - did you build it, or did you simply install a binary? > - if you built it, when did you build it? > > Note, you are going to have trouble getting much out of the core dumps > from the binaries, because they're a.out. I've placed an unstripped > ELF binary here if you'd like to help out by getting a stack trace: > > http://www.freebsd.org/~jdp/cvsup-16.0.gz > > The compressed file is about 2.3 MB in size. > > John > -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 6: 1:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id C537A15015 for ; Tue, 5 Oct 1999 06:01:06 -0700 (PDT) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11YUEY-000DMh-00; Tue, 5 Oct 1999 13:02:22 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id PAA02001; Tue, 5 Oct 1999 15:01:02 +0200 (CEST) (envelope-from marcel@scc.nl) Message-ID: <37F9F68D.CADE38B3@scc.nl> Date: Tue, 05 Oct 1999 15:01:02 +0200 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Cc: jdp@polstra.com Subject: CVSup segfaults identified/solved [PATCH] Content-Type: multipart/mixed; boundary="------------1EF75A6A56C460C556506C8D" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------1EF75A6A56C460C556506C8D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, It seems that the trampoline code got too long and resulted in the coredumps people reported. The following patch solves that. it basicly works as follows: o Simplify the trampoline code so that it doesn't have to distinguish between an old- and new sigframe and also restoring %gs in both cases. o Which sigreturn to use is now determined by the process flag that is used to determine which sendsig is to be used (symmetry) o restoring %gs is now handled in the proper sigreturn. I'll commit this if noone objects. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org --------------1EF75A6A56C460C556506C8D Content-Type: text/plain; charset=us-ascii; name="cvsup.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="cvsup.diff" Index: i386/i386/genassym.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/genassym.c,v retrieving revision 1.80 diff -u -r1.80 genassym.c --- genassym.c 1999/10/04 19:33:51 1.80 +++ genassym.c 1999/10/05 12:02:18 @@ -148,7 +148,6 @@ printf("#define\tTF_EFLAGS %#x\n", OS(trapframe, tf_eflags)); printf("#define\tSIGF_HANDLER %#x\n", OS(sigframe, sf_ahu.sf_handler)); - printf("#define\tSIGF_SIGRET %#x\n", OS(sigframe, sf_sigreturn)); printf("#define\tSIGF_SC %#x\n", OS(osigframe, sf_siginfo.si_sc)); printf("#define\tSIGF_UC %#x\n", OS(sigframe, sf_uc)); Index: i386/i386/locore.s =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/locore.s,v retrieving revision 1.128 diff -u -r1.128 locore.s --- locore.s 1999/09/29 15:06:19 1.128 +++ locore.s 1999/10/05 11:54:06 @@ -415,37 +415,14 @@ */ NON_GPROF_ENTRY(sigcode) call SIGF_HANDLER(%esp) /* call signal handler */ - movl SIGF_SIGRET(%esp),%eax /* Get sigreturn cookie */ - cmpl $0x0ABCDEF0,%eax /* New one? */ - jne 3f -/* New signalling code */ - lea SIGF_UC(%esp),%eax /* get ucontext */ + lea SIGF_UC(%esp),%eax /* get ucontext_t */ pushl %eax - testl $PSL_VM,UC_EFLAGS(%eax) - jne 1f - movl UC_GS(%eax),%gs /* restore %gs */ -1: movl $SYS_sigreturn,%eax pushl %eax /* junk to fake return addr. */ int $0x80 /* enter kernel with args */ - /* on stack */ -2: - jmp 2b -/* Old signalling code */ -3: - lea SIGF_SC(%esp),%eax /* get sigcontext */ - pushl %eax - testl $PSL_VM,SC_PS(%eax) - jne 4f - movl SC_GS(%eax),%gs /* restore %gs */ -4: - movl $SYS_osigreturn,%eax - pushl %eax /* junk to fake return addr. */ - int $0x80 /* enter kernel with args */ /* on stack */ -5: - jmp 5b - +1: + jmp 1b ALIGN_TEXT _esigcode: Index: i386/i386/machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v retrieving revision 1.366 diff -u -r1.366 machdep.c --- machdep.c 1999/10/04 19:33:51 1.366 +++ machdep.c 1999/10/05 12:47:23 @@ -725,8 +725,6 @@ tf->tf_eflags &= ~(PSL_VM|PSL_NT|PSL_T|PSL_VIF|PSL_VIP); } - sf.sf_sigreturn = 0x0ABCDEF0; - /* * Copy the sigframe out to the user's stack. */ @@ -789,6 +787,8 @@ struct trapframe_vm86 *tf = (struct trapframe_vm86 *)regs; struct vm86_kernel *vm86; + load_gs(scp->sc_gs); + /* * if pcb_ext == 0 or vm86_inited == 0, the user hasn't * set up the vm86 area, and we can't enter vm86 mode. @@ -888,6 +888,10 @@ ucontext_t *ucp; int cs, eflags; + if ((p->p_flag & P_NEWSIGSET) == 0) { + return osigreturn(p, (struct osigreturn_args *)uap); + } + regs = p->p_md.md_regs; ucp = uap->sigcntxp; eflags = ucp->uc_mcontext.mc_tf.tf_eflags; @@ -898,6 +902,8 @@ if (eflags & PSL_VM) { struct trapframe_vm86 *tf = (struct trapframe_vm86 *)regs; struct vm86_kernel *vm86; + + load_gs(ucp->uc_mcontext.mc_gs); /* * if pcb_ext == 0 or vm86_inited == 0, the user hasn't Index: i386/include/sigframe.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/sigframe.h,v retrieving revision 1.2 diff -u -r1.2 sigframe.h --- sigframe.h 1999/10/03 12:55:58 1.2 +++ sigframe.h 1999/10/05 11:53:53 @@ -86,9 +86,8 @@ __siginfohandler_t *sf_action; __sighandler_t *sf_handler; } sf_ahu; - register_t sf_sigreturn; /* sigreturn to use */ - siginfo_t sf_si; /* = *sf_siginfo (SA_SIGINFO case) */ ucontext_t sf_uc; /* = *sf_ucontext */ + siginfo_t sf_si; /* = *sf_siginfo (SA_SIGINFO case) */ }; #endif /* !_MACHINE_SIGFRAME_H_ */ --------------1EF75A6A56C460C556506C8D-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 6: 6:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 3984915015 for ; Tue, 5 Oct 1999 06:05:57 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p23-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.152]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id WAA12896; Tue, 5 Oct 1999 22:05:29 +0900 (JST) Message-ID: <37F9F663.7885D59A@newsguy.com> Date: Tue, 05 Oct 1999 22:00:19 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: maxphys = 0?? References: <6694.939053742@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > You need to move your sources further forward. Alas, it didn't help. What versions of what files I should have? The warnings are still appearing, at fsck time. > > In message <37F8CF28.BD5903FA@newsguy.com>, "Daniel C. Sobral" writes: > >A kernel from this weekend's sources is showing this warning message > >at boot: > > > >WARNING: #ad/0x30005 maxphys = 0 ??WARNING: #ad/0x30004 maxphys = 0 > >?? > > > >These are: > > > >brw-r----- 1 root operator 30, 0x00030004 Apr 6 11:48 ad0s2e > >brw-r----- 1 root operator 30, 0x00030005 Apr 6 11:48 ad0s2f -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 6:20:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 99062155F2 for ; Tue, 5 Oct 1999 06:19:11 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id PAA87988; Tue, 5 Oct 1999 15:07:33 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199910051307.PAA87988@zibbi.mikom.csir.co.za> Subject: Re: my make world is broken ! In-Reply-To: <37F9BD1B.94F78707@newsguy.com> from "Daniel C. Sobral" at "Oct 5, 1999 05:55:55 pm" To: dcs@newsguy.com (Daniel C. Sobral) Date: Tue, 5 Oct 1999 15:07:33 +0200 (SAT) Cc: bde@zeta.org.au (Bruce Evans), mark@grondar.za (Mark Murray), peter@netplex.com.au (Peter Wemm), jabc@rey.moz.com.mx (Juan Amado Becerril Castillo), current@FreeBSD.ORG (current@FreeBSD.ORG) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > 3: *always* build (or try to) and install a new kernel before a > > > > make world as that's a lot easier to back out of. > > > > > > This badly bites the bum of anyone who uses KLD's regularly. > > > > 4: Don't use modules in -current unless you know what you are doing. > > This normally means not using modules in -current except for ones > > that you are developing. > > This is not actually relevant. If the procedure becomes first kernel > then world, it will affect -stable sooner or later. Obviously, we > have to deal with it _before_ 4.x becomes -stable. And then there is the stuff in /boot. Although not as big a problem, once in a while it grows a new capabilty which is needed to boot a new kernel, so it probably have to be installed before booting with a new kernel? John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 6:21:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id 6DCE4155CB for ; Tue, 5 Oct 1999 06:21:25 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper (kc-rmt06.keycomp.net [207.44.1.8]) by www.keycomp.net (8.8.5/SCO5) with SMTP id JAA25631 for ; Tue, 5 Oct 1999 09:27:44 -0400 (EDT) Message-ID: <000001bf0f34$7005af40$01010101@bopper> From: "Bill A. K." To: Subject: 4.0-CURRENT from 3.2-RELEASE Date: Mon, 4 Oct 1999 21:48:41 -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 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying to upgrade my system from 3.2-RELEASE to 4.0-CURRENT, i CVsuped the source, but when I try to build it, (with cd /usr/src, make -j4 buildworld, but also with just make buildworld), it blows up on libgcc1.c (the one everybody's been complaining about.) Greg Lehey told me to build the kernel first, but the 3.2 config won't correctly run the 4.0 kernel config file. Any suggestions? What do you think of the problem Greg? I really want to get this up. Thanks Bill billieakay@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 6:41:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id C4B841560E for ; Tue, 5 Oct 1999 06:41:12 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper (kc-rmt06.keycomp.net [207.44.1.8]) by www.keycomp.net (8.8.5/SCO5) with SMTP id JAA25747 for ; Tue, 5 Oct 1999 09:46:13 -0400 (EDT) Message-ID: <003601bf0f37$08cc7c20$01010101@bopper> From: "Bill A. K." To: Subject: 4.0-CURRENT from 3.2-RELEASE Date: Tue, 5 Oct 1999 09:39:05 -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 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying to upgrade my system from 3.2-RELEASE to 4.0-CURRENT, i CVsuped the source, but when I try to build it, (with cd /usr/src, make -j4 buildworld, but also with just make buildworld), it blows up on libgcc1.c (the one everybody's been complaining about.) Greg Lehey told me to build the kernel first, but the 3.2 config won't correctly run the 4.0 kernel config file. Any suggestions? What do you think of the problem Greg? I really want to get this up. Thanks Bill billieakay@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 6:52: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 7408315635 for ; Tue, 5 Oct 1999 06:52:04 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-bn5k-39.mfi.net [209.26.31.55]) by pawn.primelocation.net (Postfix) with ESMTP id 785BB9B20; Tue, 5 Oct 1999 09:51:36 -0400 (EDT) Date: Tue, 5 Oct 1999 09:51:35 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: John Polstra Cc: current@freebsd.org Subject: Re: CVSup core dumps In-Reply-To: <199910050225.TAA39110@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Oct 1999, John Polstra wrote: > I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. Could somebody please check that and report > back to the list? I can't sacrifice my i386 -current machine to the > cause right now. > It works here with world/kernel built this morning from sources cvsup'd at 0100 EDT from cvsup6.freebsd.org. > - what is the output from "cvsup -v"? earth:~# cvsup -v CVSup client, GUI version Software version: REL_16_0 Protocol version: 16.0 http://www.polstra.com/projects/freeware/CVSup/ Report problems to cvsup-bugs@polstra.com earth:~# > - is "cvsup" a static binary or is it dynamically linked? earth:~# file /usr/local/bin/cvsup /usr/local/bin/cvsup: FreeBSD/i386 compact demand paged executable earth:~# ldd /usr/local/bin/cvsup ldd: /usr/local/bin/cvsup: not a dynamic executable (same on all versions) > - did you build it, or did you simply install a binary? no problems with the one retreived using /usr/ports/net/cvsup-bin: earth:/usr/ports/distfiles# md5 cvsup-freebsd-ix86-aout-16.0.tar.gz MD5 (cvsup-freebsd-ix86-aout-16.0.tar.gz) = 57c25981d3c1d82a79b9ae18aaea715b earth:/usr/ports/distfiles# nor from one pkg_add 'ed from ftp://ftp.freebsd.org/pub/FreeBSD/packages/All/cvsup-bin-16.0.tgz : earth:~# md5 cvsup-bin-16.0.tgz MD5 (cvsup-bin-16.0.tgz) = 3e60e196c8ed9f7dac3f145bd72ac536 earth:~# > Note, you are going to have trouble getting much out of the core dumps > from the binaries, because they're a.out. I've placed an unstripped > ELF binary here if you'd like to help out by getting a stack trace: > > http://www.freebsd.org/~jdp/cvsup-16.0.gz > This one works without fault also. ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 7:48:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 68D22150F6 for ; Tue, 5 Oct 1999 07:48:22 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA19616; Tue, 5 Oct 1999 10:48:21 -0400 (EDT) (envelope-from luoqi) Date: Tue, 5 Oct 1999 10:48:21 -0400 (EDT) From: Luoqi Chen Message-Id: <199910051448.KAA19616@lor.watermarkgroup.com> To: freebsd-current@FreeBSD.ORG, marcel@scc.nl Subject: Re: CVSup segfaults identified/solved [PATCH] Cc: jdp@polstra.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > It seems that the trampoline code got too long and resulted in the > coredumps people reported. The following patch solves that. it basicly > works as follows: > > o Simplify the trampoline code so that it doesn't have to distinguish > between an old- and new sigframe and also restoring %gs in both > cases. > o Which sigreturn to use is now determined by the process flag that > is used to determine which sendsig is to be used (symmetry) > o restoring %gs is now handled in the proper sigreturn. > > I'll commit this if noone objects. > > -- > Marcel Moolenaar mailto:marcel@scc.nl > SCC Internetworking & Databases http://www.scc.nl/ > The FreeBSD project mailto:marcel@FreeBSD.org Restoration of %gs should not be in the kernel because it comes from user application and maybe invalid, if you restore it inside the kernel it could be fatal to the whole system, and on the other hand just a core dump if done in the trampoline code which is still in user mode. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 8: 7:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from baynet.baynetworks.com (ns1.BayNetworks.COM [134.177.3.20]) by hub.freebsd.org (Postfix) with ESMTP id E24D914D67 for ; Tue, 5 Oct 1999 08:07:24 -0700 (PDT) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107]) by baynet.baynetworks.com (8.9.1/8.9.1) with ESMTP id IAA15018; Tue, 5 Oct 1999 08:04:53 -0700 (PDT) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with SMTP id IAA28878; Tue, 5 Oct 1999 08:04:51 -0700 (PDT) Received: from carrera.engwest (carrera.engwest.baynetworks.com) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id IAA10762; Tue, 5 Oct 1999 08:02:44 -0700 To: jdp@polstra.com Cc: current@FreeBSD.ORG Subject: Re: CVSup core dumps In-Reply-To: Your message of "Mon, 4 Oct 1999 19:25:57 -0700 (PDT)" <199910050225.TAA39110@vashon.polstra.com> References: <199910050225.TAA39110@vashon.polstra.com> X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991005080243K.thomma@baynetworks.com> Date: Tue, 05 Oct 1999 08:02:43 -0700 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 30 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John, > Also, for those of you who are experiencing problems: Please state > as precisely as possible: I have Oct 4 9pm PDT -current on K6 and SMP PPro machine. CVSup coredumps on K6 machine reliably(?) but it works on SMP PPro machine. I tried both 16.0/15.2(? previous one) packages. Both are the same result. Someone said that it works under truss. It did work with my K6 machine. It smells like something uninitialized is used? > Note, you are going to have trouble getting much out of the core dumps > from the binaries, because they're a.out. I've placed an unstripped > ELF binary here if you'd like to help out by getting a stack trace: > > http://www.freebsd.org/~jdp/cvsup-16.0.gz Great! I was trying to rebuild CVSup by myself, besides I misplaced aout gdb somewhere.... As your CVSup web page says, it wasn't that straightforward ;-) Thanks Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 8: 9: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 79ACE1562E for ; Tue, 5 Oct 1999 08:09:00 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA19887; Tue, 5 Oct 1999 11:07:22 -0400 (EDT) (envelope-from luoqi) Date: Tue, 5 Oct 1999 11:07:22 -0400 (EDT) From: Luoqi Chen Message-Id: <199910051507.LAA19887@lor.watermarkgroup.com> To: freebsd-current@FreeBSD.ORG, marcel@scc.nl Subject: Re: CVSup segfaults identified/solved [PATCH] Cc: jdp@polstra.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > It seems that the trampoline code got too long and resulted in the > coredumps people reported. The following patch solves that. it basicly > works as follows: > > o Simplify the trampoline code so that it doesn't have to distinguish > between an old- and new sigframe and also restoring %gs in both > cases. > o Which sigreturn to use is now determined by the process flag that > is used to determine which sendsig is to be used (symmetry) > o restoring %gs is now handled in the proper sigreturn. > > I'll commit this if noone objects. > > -- > Marcel Moolenaar mailto:marcel@scc.nl > SCC Internetworking & Databases http://www.scc.nl/ > The FreeBSD project mailto:marcel@FreeBSD.org Another comment, in mcontext_t structure it's best we list all registers individually like in sigcontext instead of using the struct trapframe. We might want to change trapframe in the future, but ucontext is part of the binary API and we don't want it to be affected. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 8:32:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 51D2D14E6E for ; Tue, 5 Oct 1999 08:32:28 -0700 (PDT) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11YWZZ-00031W-00; Tue, 5 Oct 1999 15:32:13 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id RAA02029; Tue, 5 Oct 1999 17:32:12 +0200 (CEST) (envelope-from marcel@scc.nl) Message-ID: <37FA19FC.7BFE60A3@scc.nl> Date: Tue, 05 Oct 1999 17:32:12 +0200 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Luoqi Chen Cc: freebsd-current@FreeBSD.ORG, jdp@polstra.com Subject: Re: CVSup segfaults identified/solved [PATCH] References: <199910051448.KAA19616@lor.watermarkgroup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen wrote: > > o restoring %gs is now handled in the proper sigreturn. > > Restoration of %gs should not be in the kernel because it comes from > user application and maybe invalid, if you restore it inside the kernel > it could be fatal to the whole system, and on the other hand just a core > dump if done in the trampoline code which is still in user mode. Hmmm... What if the application passes a (possibly handcrafted) sigcontext to an explicit call to sigreturn. %gs should be restored in that case too, right? Isn't it therefore better to have %gs in the trapframe? -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 9:14:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 9D2F81560A for ; Tue, 5 Oct 1999 09:14:31 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id MAA20723; Tue, 5 Oct 1999 12:12:48 -0400 (EDT) (envelope-from luoqi) Date: Tue, 5 Oct 1999 12:12:48 -0400 (EDT) From: Luoqi Chen Message-Id: <199910051612.MAA20723@lor.watermarkgroup.com> To: luoqi@watermarkgroup.com, marcel@scc.nl Subject: Re: CVSup segfaults identified/solved [PATCH] Cc: freebsd-current@FreeBSD.ORG, jdp@polstra.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luoqi Chen wrote: > > > > o restoring %gs is now handled in the proper sigreturn. > > > > Restoration of %gs should not be in the kernel because it comes from > > user application and maybe invalid, if you restore it inside the kernel > > it could be fatal to the whole system, and on the other hand just a core > > dump if done in the trampoline code which is still in user mode. > > Hmmm... What if the application passes a (possibly handcrafted) > sigcontext to an explicit call to sigreturn. %gs should be restored in > that case too, right? > > Isn't it therefore better to have %gs in the trapframe? > > -- > Marcel Moolenaar mailto:marcel@scc.nl > SCC Internetworking & Databases http://www.scc.nl/ > The FreeBSD project mailto:marcel@FreeBSD.org > The only place sigreturn is called explicitly is to enter VM86 mode, and in that case, %gs is restored inside kernel as part of vm86 trapframe. In fact, you may choose to restore %gs in the kernel, but you have to be prepared to take a fault on the load_gs operation and to recover from the fault properly. The reason why %gs is not in the trapframe is that trapframe is used at all entrances to the kernel (syscall/trap/intr), if %gs is included, then we need to save and restore %gs for each syscall/trap/intr, that's about 40 clock cycles wasted each time. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 9:37:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id BA9A214EC8 for ; Tue, 5 Oct 1999 09:37:19 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.037 #1) id 11YXaL-0005F8-00; Tue, 05 Oct 1999 18:37:05 +0200 From: Sheldon Hearn To: "Bill A. K." Cc: freebsd-current@FreeBSD.ORG Subject: Re: 4.0-CURRENT from 3.2-RELEASE In-reply-to: Your message of "Tue, 05 Oct 1999 09:39:05 -0400." <003601bf0f37$08cc7c20$01010101@bopper> Date: Tue, 05 Oct 1999 18:37:05 +0200 Message-ID: <20157.939141425@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 05 Oct 1999 09:39:05 -0400, "Bill A. K." wrote: > I'm trying to upgrade my system from 3.2-RELEASE to 4.0-CURRENT You're venturing into some virgin territory, but some old advice in the FreeBSD Handbook still applies -- if you intend to run CURRENT, subscribe to the freebsd-current mailing list a little while _before_ you intend to migrate. Recent discusssions on the freebsd-current mailing list would answer this question: > Greg Lehey told me to build the kernel first, but the 3.2 config won't > correctly run the 4.0 kernel config file. And the answer is... ;-) You'll need to build and install config(8) first. You might get away with this: cd /usr/src/usr.sbin/config make cleandir && make obj && make install Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 9:49:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 987C114D39 for ; Tue, 5 Oct 1999 09:49:33 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA19936 for ; Tue, 5 Oct 1999 09:47:20 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA40296; Tue, 5 Oct 1999 09:47:19 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 5 Oct 1999 09:47:19 -0700 (PDT) Message-Id: <199910051647.JAA40296@vashon.polstra.com> To: current@freebsd.org Subject: CVSup core dumps: a work-around In-Reply-To: <199910050225.TAA39110@vashon.polstra.com> References: <199910012137.PAA04480@shambhala.cgd.ucar.edu> <199910050225.TAA39110@vashon.polstra.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wow, you guys have been busy while I was asleep! Thanks for the reports, and for the diagnosis already done by Marcel, Luoqi, and others. If you are stuck with a kernel that can't run CVSup, I believe you can work around the problem by adding "@M3novm" to the cvsup command line. Add it anywhere on the command line -- its position doesn't matter. Also, I recommend that you _not_ try to rebuild CVSup and/or Modula-3 from the sources at this time. I suspect Modula-3 is broken because of the changed size of the jmp_buf type in -current. (The M3 runtime thinks it knows how big a jmp_buf is.) This shouldn't affect old binaries, but it will bite you if you try to rebuild from the sources. I'll commit a patch as soon as I can, but I am on some other deadlines and it might take me a day or two. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 10: 4:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 52DC0150EA; Tue, 5 Oct 1999 10:03:42 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id UAA08746; Tue, 5 Oct 1999 20:02:27 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Tue, 5 Oct 1999 20:02:26 +0300 (EEST) From: Adrian Penisoara To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Mon, 4 Oct 1999, Adrian Penisoara wrote: > > I have a -stable production server that keeps (solidly) blocking pretty > often (I don't get over 3 days uptimes). If you need details just let me > know. Just to let you know: syncing every second in a loop like this: while true do sync ; sleep 1 done doesn't prove to be a workaround -- the system still locks up. I tried this as per Mattew's suggestion in an e-mail on the list. BTW: I'll downgrade to 3.1-STABLE as of aprox. end of April; I'll let you know if it's stable for me. Thanks, Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 13:42:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A93C61564E for ; Tue, 5 Oct 1999 13:42:28 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA09836 for ; Tue, 5 Oct 1999 14:42:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA04644 for ; Tue, 5 Oct 1999 14:42:16 -0600 (MDT) Message-Id: <199910052042.OAA04644@harmony.village.org> To: current@freebsd.org Subject: make install trick Date: Tue, 05 Oct 1999 14:42:15 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have soft updates enabled on a fast machine at work. make installworld can fill up slash even though it has 15M free before the install. I think this is a bug in softupdates that it doesn't reclaim space quickly enough or in overflow situations. To work around it, I've used make INSTALL="/bin/sync && install" or make INSTALL="/bin/sync && install -C" Of course it takes longer this way, but it has worked 4 times in a row where the last 20 make installworlds failed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 14: 1:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BB81715651; Tue, 5 Oct 1999 14:01:01 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA79706; Tue, 5 Oct 1999 14:00:42 -0700 (PDT) (envelope-from dillon) Date: Tue, 5 Oct 1999 14:00:42 -0700 (PDT) From: Matthew Dillon Message-Id: <199910052100.OAA79706@apollo.backplane.com> To: Adrian Penisoara Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : The problem is that the machine is completely locked, I can't get into :the debugger with CTR-ALT-ESC; no panics so there are no coredumps :catched. Any advise ? Could you escape in the debugger when you were hit :by these bugs ? If it's completely locked up and ctl-alt-esc doesn't work (and normally does work - try it on a working system to make sure that you've compiled in the appropriate DDB options), and you aren't in an X display (ctl-alt-esc isn't useful when done from an X display)... then your lockup problem is unrelated to mmap. If you are running an X display on this box, you may be able to get more information in regards to the crash if you turn off X. : : I have: squid (20Mb), nntpcached (17Mb SIZE, 1Mb RES), apache, named, :MFS, a few PPP processes and the rest of the standard menu. The only programs known to cause the swap problem are innd and innxmit, both part of the inn news system. : OK, how about some workarounds, I can't wait anylonger for this to be :fixed, my situation got critical. Should I downgrade to 3.1-RELEASE (that :hadn't exhibit this way) or can I dare a 4.0-CURRENT (are these problems :present in -current too ?) ? : : Thanks, : Ady (@warpnet.ro) If the machine is locking up to the point where you cannot even drop into DDB, this bug is not related to the known mmap() bugs. At this point I have no idea what might be causing your lockup problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 14: 6:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 0CA9815689 for ; Tue, 5 Oct 1999 14:05:51 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id XAA27055 for current@freebsd.org; Tue, 5 Oct 1999 23:05:47 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id A9D65885C; Tue, 5 Oct 1999 23:04:49 +0200 (CEST) Date: Tue, 5 Oct 1999 23:04:49 +0200 From: Ollivier Robert To: current@freebsd.org Subject: Re: make install trick Message-ID: <19991005230449.A94293@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <199910052042.OAA04644@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <199910052042.OAA04644@harmony.village.org> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Warner Losh: > install. I think this is a bug in softupdates that it doesn't reclaim > space quickly enough or in overflow situations. Yes, it is a known issue Kirk know of AFAIK. It should probably reclaim the soon-to-be-freed blocks when it needs them. I've removed softupdates on / for the moment, it is not that written to on my machines anyway. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 14:32:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 6840D151E6 for ; Tue, 5 Oct 1999 14:32:24 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Tue, 5 Oct 1999 14:31:28 -0700 From: "David Schwartz" To: "Warner Losh" , Subject: RE: make install trick Date: Tue, 5 Oct 1999 14:31:28 -0700 Message-ID: <000101bf0f78$fbe58b40$021d85d1@youwant.to> 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.2377.0 In-Reply-To: <199910052042.OAA04644@harmony.village.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have soft updates enabled on a fast machine at work. make > installworld can fill up slash even though it has 15M free before the > install. I think this is a bug in softupdates that it doesn't reclaim > space quickly enough or in overflow situations. It's really not a bug, it's just a missing feature. There's no requirement that a filesystem reclaim empty space immediately. You really shouldn't be using fastupdates on nearly full filesystems -- it doesn't handle that situation particularly well. Once could even argue that it's preferable to force the make to abort than thrash the filesystem. Though a switch to allow it to thrash might be helpful in degenerate cases such as this. Fastupdates is great for the most common case -- a typical /usr or /home partition. That's where you care about write performance anyway. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 14:38:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C9F1D14DB7 for ; Tue, 5 Oct 1999 14:38:27 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA10057; Tue, 5 Oct 1999 15:37:04 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA05073; Tue, 5 Oct 1999 15:36:18 -0600 (MDT) Message-Id: <199910052136.PAA05073@harmony.village.org> To: John-Mark Gurney Subject: Re: HEADS UP: sigset_t changes committed Cc: Amancio Hasty , Marcel Moolenaar , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 30 Sep 1999 00:32:14 PDT." <19990930003214.58194@hydrogen.fircrest.net> References: <19990930003214.58194@hydrogen.fircrest.net> <37F30A88.2DF1D7C9@scc.nl> <199909300712.AAA18462@rah.star-gate.com> Date: Tue, 05 Oct 1999 15:36:18 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990930003214.58194@hydrogen.fircrest.net> John-Mark Gurney writes: : I thought we were working to the point that we could build a mips world : on an x86 box?? w/ this, it completely breaks it... the whole idea of : a buildworld is that the tools can be build on ANY platform and run, : (assuming the tools support it) and then be able to build the target... No. It won't built completely, but only through the first kernel files that are needed (at least in the checked in tree). I had things further, but lost them in a disk crash. I've not had the time to revisit it since then. I defintely will have to try this again after these changes. If it can't be made to work, this is a huge deal... However, the current build tree isn't careful enough to distinguish between host run programs and target programs, which is why we're having this problem. I suspect that making this work will make cross building easier (and vice versa). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 14:39:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 86B0E152E9 for ; Tue, 5 Oct 1999 14:38:38 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA10061; Tue, 5 Oct 1999 15:38:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA05086; Tue, 5 Oct 1999 15:37:56 -0600 (MDT) Message-Id: <199910052137.PAA05086@harmony.village.org> To: Marcel Moolenaar Subject: Re: HEADS UP: sigset_t changes committed Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 30 Sep 1999 09:49:40 +0200." <37F31614.95B0963A@scc.nl> References: <37F31614.95B0963A@scc.nl> , <99092922415900.64838@nomad.dataplex.net> Date: Tue, 05 Oct 1999 15:37:56 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37F31614.95B0963A@scc.nl> Marcel Moolenaar writes: : Yes, but if you need the tools you just compiled in your : cross-compilation for cross-compilation itself, you'll have a big : problem. And that's almost exacly what happens when building world... No. The cross build world takes care to build host runable binaries. It doesn't take sufficient care because your change highlights places where it doesn't. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 14:43:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D3ACD14E77 for ; Tue, 5 Oct 1999 14:43:49 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA10089; Tue, 5 Oct 1999 15:42:59 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA05137; Tue, 5 Oct 1999 15:42:39 -0600 (MDT) Message-Id: <199910052142.PAA05137@harmony.village.org> To: "David Schwartz" Subject: Re: make install trick Cc: current@freebsd.org In-reply-to: Your message of "Tue, 05 Oct 1999 14:31:28 PDT." <000101bf0f78$fbe58b40$021d85d1@youwant.to> References: <000101bf0f78$fbe58b40$021d85d1@youwant.to> Date: Tue, 05 Oct 1999 15:42:39 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <000101bf0f78$fbe58b40$021d85d1@youwant.to> "David Schwartz" writes: : It's really not a bug, it's just a missing feature. There's no requirement : that a filesystem reclaim empty space immediately. You really shouldn't be : using fastupdates on nearly full filesystems -- it doesn't handle that : situation particularly well. Nearly full? It is a 32M file system with 15M free. That's not nearly full. The problem is that the update rate is faster than the softupdate code can deal with. Running sync between each install shows that this is a bug. sync is supposed to be idempotent. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 15:50:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 289341568B for ; Tue, 5 Oct 1999 15:50:47 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40345>; Wed, 6 Oct 1999 08:46:24 +1000 Content-return: prohibited Date: Wed, 6 Oct 1999 08:49:43 +1000 From: Peter Jeremy Subject: Re: make install trick In-reply-to: <199910052142.PAA05137@harmony.village.org> To: Warner Losh Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct6.084624est.40345@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <000101bf0f78$fbe58b40$021d85d1@youwant.to> <199910052142.PAA05137@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-06 07:42:39 +1000, Warner Losh wrote: >Nearly full? It is a 32M file system with 15M free. That's not >nearly full. The problem is that the update rate is faster than the >softupdate code can deal with. Running sync between each install >shows that this is a bug. As Ollivier Robert pointed out, it is a known problem. Kirk says it's non-trivial to fix (though I'm sure he'll welcome your patches :-). The suggested work-around is not to run softupdates on root. In any case, you should not be doing lots of writes to root, so the lack of softupdates should not be a problem. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 16: 2:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 414AB15696 for ; Tue, 5 Oct 1999 16:02:20 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id SAA10672; Tue, 5 Oct 1999 18:59:55 -0400 (EDT) Date: Tue, 5 Oct 1999 18:59:55 -0400 (EDT) From: "Matthew N. Dodd" To: Timo Geusch Cc: freebsd-current@freebsd.org Subject: Re: Recent kernel hangs during boot with pnp sio. In-Reply-To: <19991005065717.A21367@tabby.timog.prestel.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Oct 1999, Timo Geusch wrote: > I'll send it once I verified that it (still) works with -current. The > work dates from before newpnp, Also, some indication as to where you > made changes would benice - my PnP changes are pretty self-contained > but I made some more general changes that might cause problems. Anyway > I'll get back to you end of next week (earliest I can manage). Just send me the code and I'll sort it out. This would be easiest for you. If I wanted easy it wouldn't be touching if_ep. > Afaik all 3C509B's are PnP. At least here in the UK there is not > shortage of those cards. If I can get a difinitive statement to this effect then I'll grab a 3c509B. There was some question as to them actually being PnP though. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 16: 3:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 2610E15642 for ; Tue, 5 Oct 1999 16:03:34 -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.9.3/8.9.3) with SMTP id RAA09207; Tue, 5 Oct 1999 17:02:13 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA21667; Tue, 5 Oct 1999 17:02:12 -0600 Date: Tue, 5 Oct 1999 17:02:12 -0600 Message-Id: <199910052302.RAA21667@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: peter.jeremy@alcatel.com.au Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: make install trick In-Reply-To: <99Oct6.084624est.40345@border.alcanet.com.au> References: <000101bf0f78$fbe58b40$021d85d1@youwant.to> <199910052142.PAA05137@harmony.village.org> <99Oct6.084624est.40345@border.alcanet.com.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In any case, you should not be doing lots of writes to root, so the > lack of softupdates should not be a problem. So, are you suggesting make /tmp it's own disk, otherwise anytime you do development alot of writes are done to /. And, if you do lots of development, then you'll have the same problem on /tmp as you did on / unless you waste a huge disk for /tmp. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 16:11: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 0BE21156A0 for ; Tue, 5 Oct 1999 16:10:47 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Tue, 5 Oct 1999 16:10:42 -0700 From: "David Schwartz" To: "Warner Losh" Cc: Subject: RE: make install trick Date: Tue, 5 Oct 1999 16:10:42 -0700 Message-ID: <000001bf0f86$d8d84670$021d85d1@youwant.to> 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.2377.0 In-reply-to: <199910052142.PAA05137@harmony.village.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <000101bf0f78$fbe58b40$021d85d1@youwant.to> "David > Schwartz" writes: > : It's really not a bug, it's just a missing feature. There's > no requirement > : that a filesystem reclaim empty space immediately. You really > shouldn't be > : using fastupdates on nearly full filesystems -- it doesn't handle that > : situation particularly well. > > Nearly full? It is a 32M file system with 15M free. That's not > nearly full. Whether that qualifies as 'nearly full' or not depends upon the update rate. > The problem is that the update rate is faster than the > softupdate code can deal with. I would say a filesystem that adds new files in an amount close to its free space is nearly full. > Running sync between each install > shows that this is a bug. sync is supposed to be idempotent. I think anybody reasonable familiar with softupdates understands what 'sync' does in this context. It's not a bug because it is documented behavior done for a specific reason. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 16:29: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id C4C96156C0 for ; Tue, 5 Oct 1999 16:28:43 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id SAA69829; Tue, 5 Oct 1999 18:28:42 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199910052328.SAA69829@celery.dragondata.com> Subject: Re: Recent kernel hangs during boot with pnp sio. To: winter@jurai.net (Matthew N. Dodd) Date: Tue, 5 Oct 1999 18:28:42 -0500 (CDT) Cc: freebsd@timog.prestel.co.uk (Timo Geusch), freebsd-current@FreeBSD.ORG In-Reply-To: from "Matthew N. Dodd" at Oct 05, 1999 06:59:55 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Afaik all 3C509B's are PnP. At least here in the UK there is not > > shortage of those cards. > > If I can get a difinitive statement to this effect then I'll grab a > 3c509B. There was some question as to them actually being PnP though. > Yes, the 3c509B can have PnP turned on or off through a DOS utility. Either you set an IO/IRQ setting, or you set it to PnP and let the system do it. (I believe they come with PnP enabled now, but before the default was off) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 16:35:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D247A15642 for ; Tue, 5 Oct 1999 16:34:42 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA10501; Tue, 5 Oct 1999 17:33:43 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA05806; Tue, 5 Oct 1999 17:33:24 -0600 (MDT) Message-Id: <199910052333.RAA05806@harmony.village.org> To: "David Schwartz" Subject: Re: make install trick Cc: current@freebsd.org In-reply-to: Your message of "Tue, 05 Oct 1999 16:10:42 PDT." <000001bf0f86$d8d84670$021d85d1@youwant.to> References: <000001bf0f86$d8d84670$021d85d1@youwant.to> Date: Tue, 05 Oct 1999 17:33:24 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <000001bf0f86$d8d84670$021d85d1@youwant.to> "David Schwartz" writes: : I think anybody reasonable familiar with softupdates understands what : 'sync' does in this context. It's not a bug because it is documented : behavior done for a specific reason. It is a bug. You've just said so. It isn't a bug that can be fixed trivially, yet it is still a bug. now that I know what's going on, I know why my kludg-eo-round works. Something that doesn't deal with reclaiming unused space is broken for that case, no matter how hard it is to fix. I also know how to work around it... Geeze, it isn't like I'm demanding you fix the bug. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 16:36:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id A8B8E156B5 for ; Tue, 5 Oct 1999 16:36:41 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id QAA27167; Tue, 5 Oct 1999 16:55:26 -0700 (PDT) Date: Tue, 5 Oct 1999 16:55:26 -0700 (PDT) From: Alfred Perlstein To: David Schwartz Cc: Warner Losh , current@FreeBSD.ORG Subject: RE: make install trick In-Reply-To: <000101bf0f78$fbe58b40$021d85d1@youwant.to> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Oct 1999, David Schwartz wrote: > > > I have soft updates enabled on a fast machine at work. make > > installworld can fill up slash even though it has 15M free before the > > install. I think this is a bug in softupdates that it doesn't reclaim > > space quickly enough or in overflow situations. > > It's really not a bug, it's just a missing feature. There's no requirement > that a filesystem reclaim empty space immediately. You really shouldn't be > using fastupdates on nearly full filesystems -- it doesn't handle that > situation particularly well. > > Once could even argue that it's preferable to force the make to abort than > thrash the filesystem. Though a switch to allow it to thrash might be > helpful in degenerate cases such as this. > > Fastupdates is great for the most common case -- a typical /usr or /home > partition. That's where you care about write performance anyway. Actually this becomes quite dangerous when used on tmp filesystems, it used to be that mfs was a good idea for /tmp, but now softupdates drastically improves performance... however given that a full /tmp can kill a system that places us in a dilemma now doesn't it? *shrug* I've seen softupdates nearly eliminate disk io for systems that used an abmornal amount of temp files, but the fact that it can destabilize a system worries me greatly. Of course I'm trying desperately to understand the softupdates code right now. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 17:21:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 6127914CE2 for ; Tue, 5 Oct 1999 17:21:08 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40351>; Wed, 6 Oct 1999 10:15:56 +1000 Content-return: prohibited Date: Wed, 6 Oct 1999 10:19:13 +1000 From: Peter Jeremy Subject: Re: make install trick In-reply-to: <199910052302.RAA21667@mt.sri.com> To: Nate Williams Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct6.101556est.40351@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <000101bf0f78$fbe58b40$021d85d1@youwant.to> <199910052142.PAA05137@harmony.village.org> <99Oct6.084624est.40345@border.alcanet.com.au> <199910052302.RAA21667@mt.sri.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-06 09:02:12 +1000, Nate Williams wrote: >> In any case, you should not be doing lots of writes to root, so the >> lack of softupdates should not be a problem. > >So, are you suggesting make /tmp it's own disk, otherwise anytime you do >development alot of writes are done to /. I've pretty well always used a separate /tmp partition. I've always used MFS with FreeBSD. This makes the root partition virtually read-only (which has robustness and security advantages). >And, if you do lots of development, then you'll have the same problem on >/tmp as you did on / unless you waste a huge disk for /tmp. :( Solutions: 1) Use -pipe 2) Don't use softupdates 3) Use a RAMdisk (eg MFS) instead of a physical disk (which makes the previous point irrelevant). I don't recall seeing anyone mention problems like this (though they might be on lists I don't read). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 17:39:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 5284414D41 for ; Tue, 5 Oct 1999 17:39:02 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40351>; Wed, 6 Oct 1999 10:35:24 +1000 Content-return: prohibited Date: Wed, 6 Oct 1999 10:38:49 +1000 From: Peter Jeremy Subject: Re: make install trick In-reply-to: To: Alfred Perlstein Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct6.103524est.40351@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <000101bf0f78$fbe58b40$021d85d1@youwant.to> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-06 09:55:26 +1000, Alfred Perlstein wrote: >I've seen softupdates nearly eliminate disk io for systems that used >an abmornal amount of temp files, but the fact that it can destabilize >a system worries me greatly. What do you mean by `destabilize'? There are bugs in softupdates which mean that an application may receive ENOSPC when writing to a filesystem even though space on that filesystem has been recently freed. Any application that cannot handle this situation is _broken_. Another option for /tmp - which I forgot last time, and seems to avoid the known problems with MFS and softupdates - it to mount /tmp async. Since you're going to blow it all away on the next reboot anyway, it doesn't really matter if the a crash trashes the FS (which is the major problem with async mounts). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 18:15:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 87F0A150D4 for ; Tue, 5 Oct 1999 18:15:06 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id SAA29735; Tue, 5 Oct 1999 18:33:51 -0700 (PDT) Date: Tue, 5 Oct 1999 18:33:51 -0700 (PDT) From: Alfred Perlstein To: peter.jeremy@alcatel.com.au Cc: freebsd-current@FreeBSD.ORG Subject: Re: make install trick In-Reply-To: <99Oct6.103524est.40351@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Oct 1999, Peter Jeremy wrote: > On 1999-Oct-06 09:55:26 +1000, Alfred Perlstein wrote: > >I've seen softupdates nearly eliminate disk io for systems that used > >an abmornal amount of temp files, but the fact that it can destabilize > >a system worries me greatly. > > What do you mean by `destabilize'? There are bugs in softupdates > which mean that an application may receive ENOSPC when writing to a > filesystem even though space on that filesystem has been recently > freed. Any application that cannot handle this situation is _broken_. Please read more of the thread before replying, the fact of the matter is that softupdates can crash the system when this happens, not a mere application, but the entire system can lock up. > Another option for /tmp - which I forgot last time, and seems to > avoid the known problems with MFS and softupdates - it to mount > /tmp async. Since you're going to blow it all away on the next > reboot anyway, it doesn't really matter if the a crash trashes the > FS (which is the major problem with async mounts). Which isn't an option unless you dedicate a partition for /tmp which is pretty wasteful imo. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 19:38:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 00336156A4 for ; Tue, 5 Oct 1999 19:38:33 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id WAA16879 for ; Tue, 5 Oct 1999 22:36:12 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA13641; Tue, 5 Oct 1999 22:35:42 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 5 Oct 1999 22:35:41 -0400 (EDT) To: current@freebsd.org Subject: installworld broken from R/O /usr/obj X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14330.45971.639580.378954@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG W`hile installworld is being discussed, I wanted to get this out there: Since rev 1.13 of usr.bin/make/arch.c, I've been seing a problem with ELF archive libraries being rebuilt unnecessarily. I believe that this problem can be traced to the RANLIBMAG string being set to "/". The reason I care about this is that its causing perl's libsdbm.a to get rebuilt during an installworld. This is causing installworlds to fail for me from R/O /usr/obj partitions. When make does its initial open of the library, Arch_LibOODate() calls ArchStatMember with the member arg equal to RANLIBMAG (or "/"). This in turn calls ArchStatMember() with member="/". This calls ArchFindMember() with member="/". ArchFindMember() will then return NULL because the strrchr() on line 809 of arch.c causes the pointer to be advanced past the last "/" in the member path, which makes it NULL. I have a hackish fix for this which just looks at the length of RANLIBMAG & the length of member. If they are both 1 && are equal, it fails to advance member past the trailing /. This allows the RANLIBMAG string to be found & prevents an up-to-date lib from being rebuilt: Index: usr.bin/make/arch.c =================================================================== RCS file: /usr/project/ari_scratch2/freebsd-cvs/src/usr.bin/make/arch.c,v retrieving revision 1.14 diff -u -b -B -r1.14 arch.c --- arch.c 1999/09/11 13:08:00 1.14 +++ arch.c 1999/09/21 13:25:39 @@ -807,7 +807,9 @@ * the comparisons easier... */ cp = strrchr (member, '/'); - if (cp != (char *) NULL) { + if ((cp != (char *) NULL) && + !((strlen(member) == 1) && (strlen(RANLIBMAG) == 1) && + strncmp(member, RANLIBMAG, 1) == 0)){ member = cp + 1; } len = tlen = strlen (member); Anybody interested in comitting this? I passed it by the person who committed 1.13 of arch.c & was ignored. I don't know make well enough to feel comfortable committing this myself. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 20:29:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id 4828715154 for ; Tue, 5 Oct 1999 20:29:10 -0700 (PDT) (envelope-from street@iname.com) Received: from mired.eh.local ([24.64.136.188]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991006032909.NNIA5795.mail.rdc2.on.home.com@mired.eh.local>; Tue, 5 Oct 1999 20:29:09 -0700 Received: (from kws@localhost) by mired.eh.local (8.9.3/8.9.3) id XAA49139; Tue, 5 Oct 1999 23:29:08 -0400 (EDT) (envelope-from kws) To: nate@mt.sri.com (Nate Williams) Cc: current@FreeBSD.ORG Subject: Re: make install trick References: <000101bf0f78$fbe58b40$021d85d1@youwant.to> <199910052142.PAA05137@harmony.village.org> <99Oct6.084624est.40345@border.alcanet.com.au> <199910052302.RAA21667@mt.sri.com> From: Kevin Street Date: 05 Oct 1999 23:29:08 -0400 In-Reply-To: Nate Williams's message of "Tue, 5 Oct 1999 17:02:12 -0600" Message-ID: <87yadhyxob.fsf@mired.eh.local> Lines: 27 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams writes: > > In any case, you should not be doing lots of writes to root, so the > > lack of softupdates should not be a problem. > > So, are you suggesting make /tmp it's own disk, otherwise anytime you do > development alot of writes are done to /. > > And, if you do lots of development, then you'll have the same problem on > /tmp as you did on / unless you waste a huge disk for /tmp. :( You could just symlink /tmp to someplace big and softupdateable. At least then you can share the free space with another big filesystem. The only problem then is that when you boot standalone you either need to be able to mount wherever you've symlinked it into or rm the symlink and mkdir /tmp while you're standalone (and remember to put it back before going multi user). In some ways symlinking is better than having /tmp as a mount point. If it's a real mount point you're likely to create stuff in /tmp while standalone that can't be seen while you're multi user with a file system mounted on top of it. Which leads to "...my / is full and I can't find the files that are using all the space!" -- Kevin Street street@iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 20:52:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id ED58014CE6; Tue, 5 Oct 1999 20:52:19 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA79744; Wed, 6 Oct 1999 13:21:57 +0930 (CST) Date: Wed, 6 Oct 1999 13:21:56 +0930 From: Greg Lehey To: Jia-Huang Chen Cc: FreeBSD current users Subject: Re: FTP daemon error messages when login Message-ID: <19991006132156.J78191@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moving from -questions to -current] On Tuesday, 5 October 1999 at 22:29:11 -0500, Jia-Huang Chen wrote: > Hi, > I'm running 4.0 current and using the default FTP server (Version 6.00LS). > Every time when I try ftp to the freebsd 4.0 box, the box always shows the > following similar messages in both root console and /var/log/messages: > > Oct 5 01:55:32 class ftpd[796]: no modules loaded for `ftpd' service > Oct 5 01:55:32 class ftpd[796]: no modules loaded for `ftpd' service > Oct 5 01:55:32 class ftpd[796]: no modules loaded for `ftpd' service > Oct 5 01:55:32 class ftpd[796]: auth_pam: Permission denied > Oct 5 01:55:32 class ftpd[796]: auth_pam: Permission denied > Oct 5 01:55:32 class ftpd[796]: auth_pam: Permission denied > > What's wrong and could I avoid it ? Well, for a start, either don't run -CURRENT, or send your messages to FreeBSD-current mailing list. > Anyone could give me some hints about how to set up my ftp service > correctly ? thanks alot, This looks like a recently introduced bogon. I'm seeing it too. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 21:58:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 2C4E9152DE for ; Tue, 5 Oct 1999 21:58:22 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40347>; Wed, 6 Oct 1999 14:53:59 +1000 Content-return: prohibited Date: Wed, 6 Oct 1999 14:57:23 +1000 From: Peter Jeremy Subject: Re: make install trick In-reply-to: To: Alfred Perlstein Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct6.145359est.40347@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <99Oct6.103524est.40351@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-06 11:33:51 +1000, Alfred Perlstein wrote: > >On Wed, 6 Oct 1999, Peter Jeremy wrote: > >> On 1999-Oct-06 09:55:26 +1000, Alfred Perlstein wrote: >> >I've seen softupdates nearly eliminate disk io for systems that used >> >an abmornal amount of temp files, but the fact that it can destabilize >> >a system worries me greatly. >> >> What do you mean by `destabilize'? ... > softupdates can crash the system when this >happens, not a mere application, but the entire system can lock up. I don't recall this coming up in this thread. Last I recall, that bug was supposed to be fixed (and Kirk(?) wanted anyone who still saw it to report it). Unfortunately, I can't find that thread in the archives :-(. >Which isn't an option unless you dedicate a partition for /tmp >which is pretty wasteful imo. I guess we disagree on this. My feeling is that write activity on root should be minimised to minimise the risk that root will be inconsistent following a crash. Secondly, there's a security viewpoint that users should not have write access anywhere in the root or /usr filesystems. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 23:21:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 06775156E5 for ; Tue, 5 Oct 1999 23:20:49 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA55492; Wed, 6 Oct 1999 08:18:33 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910060618.IAA55492@gratis.grondar.za> To: Greg Lehey Cc: Jia-Huang Chen , FreeBSD current users Subject: Re: FTP daemon error messages when login Date: Wed, 06 Oct 1999 08:18:28 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Anyone could give me some hints about how to set up my ftp service > > correctly ? thanks alot, > > This looks like a recently introduced bogon. I'm seeing it too. Hmmm. PAM Stuff. Have you fully updated (mergemaster) your etc area? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 23:51:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id EEC481570C for ; Tue, 5 Oct 1999 23:50:19 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id HAA35634; Wed, 6 Oct 1999 07:49:50 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id HAA26368; Wed, 6 Oct 1999 07:16:53 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910060616.HAA26368@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein Cc: peter.jeremy@alcatel.com.au, freebsd-current@FreeBSD.ORG Subject: Re: make install trick In-reply-to: Your message of "Tue, 05 Oct 1999 18:33:51 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Oct 1999 07:16:52 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > Please read more of the thread before replying, the fact of [.....] Now if everyone used mailers that actually wrote correct in-reply-to lines, this might be a realistic thing to suggest !.... -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 23:51:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id B63471571B for ; Tue, 5 Oct 1999 23:50:24 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id HAA35640; Wed, 6 Oct 1999 07:49:51 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id HAA15085; Wed, 6 Oct 1999 07:03:06 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910060603.HAA15085@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: nate@mt.sri.com (Nate Williams) Cc: peter.jeremy@alcatel.com.au, Warner Losh , current@FreeBSD.ORG Subject: Re: make install trick In-reply-to: Your message of "Tue, 05 Oct 1999 17:02:12 MDT." <199910052302.RAA21667@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Oct 1999 07:03:02 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In any case, you should not be doing lots of writes to root, so the > > lack of softupdates should not be a problem. > > So, are you suggesting make /tmp it's own disk, otherwise anytime you do > development alot of writes are done to /. > > And, if you do lots of development, then you'll have the same problem on > /tmp as you did on / unless you waste a huge disk for /tmp. :( Ah, but if you have /tmp on your root partition, you should really have more than 12M of free space: $ du -sk /bin /sbin 3247 /bin 8519 /sbin :-) Interestingly enough, I believe there's another ``bug'' here in the softupdates code. If softupdates is short on required disk space, it sould at least go through the todo list and optimise out what it can, possibly reducing the disk space requirements. If it did this, repeating the make install a few times should eventually work as it will ultimately end up overwriting things with exactly the same data and optimising the whole operation out - but this isn't currently the case. > Nate -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 5 23:51:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id 31D4C15713 for ; Tue, 5 Oct 1999 23:50:21 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id HAA35637; Wed, 6 Oct 1999 07:49:50 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id HAA24521; Wed, 6 Oct 1999 07:14:20 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910060614.HAA24521@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: peter.jeremy@alcatel.com.au Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: make install trick In-reply-to: Your message of "Wed, 06 Oct 1999 10:38:49 +1000." <99Oct6.103524est.40351@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Oct 1999 07:14:19 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 1999-Oct-06 09:55:26 +1000, Alfred Perlstein wrote: > >I've seen softupdates nearly eliminate disk io for systems that used > >an abmornal amount of temp files, but the fact that it can destabilize > >a system worries me greatly. > > What do you mean by `destabilize'? There are bugs in softupdates > which mean that an application may receive ENOSPC when writing to a > filesystem even though space on that filesystem has been recently > freed. Any application that cannot handle this situation is _broken_. [.....] :-] You're joking right ? Most applications don't even *notice* the situation let alone handle it. Whaddaya do when /var/log runs out of space ? Show me an app that handles it..... I guess you can argue the case, but in real life, running out of any machine resource can cause all sorts of possibly unrecoverable problems. IMHO the best way to deal with it in a generic way is to have the give-me-the-resource function block if it really thinks it's a temporary thing. In the case of softupdtes, I'd be surprised if it couldn't easily figure out that the problem is *probably* transient and block, but of course to figure out exactly how transient it is would probably involve about the same amount of effort as just processing the softupdates ``todo'' list there and then. Anyway, I'll shut up now :-I -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 1:26:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 87BC614E05 for ; Wed, 6 Oct 1999 01:26:21 -0700 (PDT) (envelope-from jfh@jfh00.fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.3/8.9.3) id KAA80470; Wed, 6 Oct 1999 10:26:18 +0200 (CEST) (envelope-from jfh) To: freebsd-current@freebsd.org Subject: try to build xfree under current siginfo_t From: Fritz Heinrichmeyer Date: 06 Oct 1999 10:26:17 +0200 Message-ID: Lines: 21 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) XEmacs/21.2 (Shinjuku) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG as i accidentally deleted my libc.so.3 i thought it would be a good time to rebuild xfree, but i came in a preprocessor hell due to siginfo_t _POSIX_SOURCE or not ... definition at the stage of building makedepend. In file included from main.c:41: /usr/include/signal.h:72: warning: `union sigval' declared inside parameter \ list /usr/include/signal.h:72: warning: its scope is only this definition \ or declaration, /usr/include/signal.h:72: warning: which is probably not what you want. /usr/include/signal.h:72: warning: parameter has incomplete type /usr/include/signal.h:73: syntax error before `siginfo_t' /usr/include/signal.h:74: syntax error before `siginfo_t' the offending code is between an #ifdef _P1003_1B_VISIBLE construct. Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 1:49:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 583D314D9C; Wed, 6 Oct 1999 01:49:20 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id LAA00833; Wed, 6 Oct 1999 11:49:26 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Wed, 6 Oct 1999 11:49:26 +0300 (EEST) From: Adrian Penisoara To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... In-Reply-To: <199910052100.OAA79706@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi again, On Tue, 5 Oct 1999, Matthew Dillon wrote: > : The problem is that the machine is completely locked, I can't get into > :the debugger with CTR-ALT-ESC; no panics so there are no coredumps > :catched. Any advise ? Could you escape in the debugger when you were hit > :by these bugs ? > > If it's completely locked up and ctl-alt-esc doesn't work (and normally > does work - try it on a working system to make sure that you've compiled > in the appropriate DDB options), and you aren't in an X display > (ctl-alt-esc isn't useful when done from an X display)... then your > lockup problem is unrelated to mmap. No X on the machine, but CTRL-ALT-ESC doesn't work. And another thing: I tried the MMAP "exploit"/test that has been floating around at that time on another 3.2-STABLE machine SMP with 2 Pentiums and it does lock the machine but you can switch consoles and escape to the debugger; on the production server (K6-2 300) everything goes dead when it happens (I haven't tried the MMAP test)... You're probably right, it's not the MMAP bug; but it's not faulty hardware -- I'll have an undeniable proof in a few days, I have downgraded to 3.1-STABLE as of 20th April... > > If you are running an X display on this box, you may be able to get > more information in regards to the crash if you turn off X. > > : > : I have: squid (20Mb), nntpcached (17Mb SIZE, 1Mb RES), apache, named, > :MFS, a few PPP processes and the rest of the standard menu. > > The only programs known to cause the swap problem are innd and innxmit, > both part of the inn news system. No such thing (yet); and I heard that innd-stable is OK (I have INND-stable running on that SMP box and had no problems with it) ?... > > : OK, how about some workarounds, I can't wait anylonger for this to be > :fixed, my situation got critical. Should I downgrade to 3.1-RELEASE (that > :hadn't exhibit this way) or can I dare a 4.0-CURRENT (are these problems > :present in -current too ?) ? > : > : Thanks, > : Ady (@warpnet.ro) > > If the machine is locking up to the point where you cannot even drop > into DDB, this bug is not related to the known mmap() bugs. > > At this point I have no idea what might be causing your lockup problem. Neither do I, dammit... :-( > > -Matt > Matthew Dillon > > I'll get back to you in a few days. Thanks a lot, Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 2:36:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id AF8CF14CB9 for ; Wed, 6 Oct 1999 02:36:50 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA83258 for current@FreeBSD.org; Wed, 6 Oct 1999 11:11:16 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Wed, 06 Oct 1999 11:11:09 +0200 From: Marcel Moolenaar Message-ID: <37FB122D.44077CD6@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: Subject: Re: try to build xfree under current siginfo_t Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fritz Heinrichmeyer wrote: > > as i accidentally deleted my libc.so.3 i thought it would be a good time > to rebuild xfree, but i came in a preprocessor hell due to siginfo_t > _POSIX_SOURCE or not ... definition at the stage of building makedepend. > In file included from main.c:41: > /usr/include/signal.h:72: warning: `union sigval' declared inside parameter \ > list > /usr/include/signal.h:72: warning: its scope is only this definition \ > or declaration, > /usr/include/signal.h:72: warning: which is probably not what you want. > /usr/include/signal.h:72: warning: parameter has incomplete type > /usr/include/signal.h:73: syntax error before `siginfo_t' > /usr/include/signal.h:74: syntax error before `siginfo_t' > > the offending code is between an #ifdef _P1003_1B_VISIBLE > construct. This caused by the recent namespace polution fixes. They were always defined before that, so this was not a problem. I think you should change #ifdef _P1003_1B_VISIBLE into #ifndef _POSIX_SOURCE for now. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 2:44:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 9357F14D76 for ; Wed, 6 Oct 1999 02:44:49 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA44011; Wed, 6 Oct 1999 10:45:42 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 6 Oct 1999 10:45:42 +0100 (BST) From: Doug Rabson To: Kevin Day Cc: "Matthew N. Dodd" , Timo Geusch , freebsd-current@freebsd.org Subject: Re: Recent kernel hangs during boot with pnp sio. In-Reply-To: <199910052328.SAA69829@celery.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Oct 1999, Kevin Day wrote: > > > > > Afaik all 3C509B's are PnP. At least here in the UK there is not > > > shortage of those cards. > > > > If I can get a difinitive statement to this effect then I'll grab a > > 3c509B. There was some question as to them actually being PnP though. > > > > Yes, the 3c509B can have PnP turned on or off through a DOS utility. Either > you set an IO/IRQ setting, or you set it to PnP and let the system do it. (I > believe they come with PnP enabled now, but before the default was off) If you find yourself with one of these and pnp is turned off, you can download the DOS utility from 3com. I recently had to do this for a friend (to turn pnp off). It was harder to find a DOS boot disk :-). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 4:25:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 3F48C150EE for ; Wed, 6 Oct 1999 04:25:30 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id NAA04442; Wed, 6 Oct 1999 13:25:13 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id NAA16666; Wed, 6 Oct 1999 13:25:11 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Wed, 6 Oct 1999 12:22:47 +0200 To: Alfred Perlstein , peter.jeremy@alcatel.com.au From: Brad Knowles Subject: Re: make install trick Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:33 PM -0700 1999/10/5, Alfred Perlstein wrote: > Which isn't an option unless you dedicate a partition for /tmp > which is pretty wasteful imo. Forgive me if I'm misunderstanding something here, but isn't having /tmp on the root filesystem just inviting a denial-of-service attack on yourself? It's bad enough when programs crap out when /tmp is full and they can't create the temporary files they demand (vi leaps to mind), but when you fill up the root filesystem and the whole machine falls over, that seems to be a really bad situation that everyone would want to avoid at virtually all costs. It was my understanding that it was standard recommended practice practice pretty much across the board to create the following separate filesystems: / /tmp (perhaps an mfs, perhaps softupdates, or whatever) /usr /var /var/tmp /home (or wherever you're going to store user directories) And that most people also then created a separate filesystem for /usr/local or /opt, or wherever they're going to store the additional system programs that they're going to be adding. This also allows you to do nice security things such as mounting /tmp, /var, /var/tmp nosuid, etc.... Is there something fundamental I'm missing here? I thought that this sort of thing was taught in SysAdmin 101.... -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 4:43:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 507C514EB9; Wed, 6 Oct 1999 04:43:35 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id NAA21153; Wed, 6 Oct 1999 13:43:32 +0200 (CEST) (envelope-from erik@habatech.no) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 06 Oct 1999 13:43:18 +0200 (CEST) From: "Erik H. Bakke" To: freebsd-current@freebsd.org, freebsd-alpha@freebsd.org Subject: Still ATA problems Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am still having problems with the ATA driver. I am seeing the same error messages as has been reported on the lists during the last few weeks, both on i386 and alpha platforms. On the i386, the problem is just an irritating itch, but it seems to be far more serious on the alpha, where the system reboots instantly when the problems occur. On reboot, the system stops at the probing of disks, reporting a timeout. Then, the system reboots again, probing and rebooting in an endless loop. I have the latest sources, as cvsupped today, October 6th. I can provide more information on the system configuration if needed, but I have no access to it right now. ===========================+================+=============================== Erik H. Bakke | | To be or not to be... Senior Consultant/Developer|erik@habatech.no| Is simply a question of Habatech AS | | binary logic ===========================+================+============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 5: 0:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 77F7D15313; Wed, 6 Oct 1999 05:00:07 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA22825; Wed, 6 Oct 1999 13:59:58 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910061159.NAA22825@freebsd.dk> Subject: Re: Still ATA problems In-Reply-To: from "Erik H. Bakke" at "Oct 6, 1999 01:43:18 pm" To: erik@habatech.no (Erik H. Bakke) Date: Wed, 6 Oct 1999 13:59:58 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Erik H. Bakke wrote: > I am still having problems with the ATA driver. > I am seeing the same error messages as has been reported on the lists during > the last few weeks, both on i386 and alpha platforms. > On the i386, the problem is just an irritating itch, but it seems to be > far more serious on the alpha, where the system reboots instantly when the > problems occur. > On reboot, the system stops at the probing of disks, reporting a timeout. > Then, the system reboots again, probing and rebooting in an endless loop. > > I have the latest sources, as cvsupped today, October 6th. > > I can provide more information on the system configuration if needed, but I > have no access to it right now. I have a new version almost ready that should fix this problem, including the panic on the alpha. It just a bit more testing then I'll commit it... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 6:22:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id CB3F914D07; Wed, 6 Oct 1999 06:22:01 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id PAA21827; Wed, 6 Oct 1999 15:21:52 +0200 (CEST) (envelope-from erik@habatech.no) 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: <199910061159.NAA22825@freebsd.dk> Date: Wed, 06 Oct 1999 15:21:38 +0200 (CEST) From: "Erik H. Bakke" To: Soren Schmidt Subject: Re: Still ATA problems Cc: freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Oct-99 Soren Schmidt wrote: > > I have a new version almost ready that should fix this problem, including > the panic on the alpha. It just a bit more testing then I'll commit it... > If you want, I can give it a test on a 164SX-based alpha... ===========================+================+=============================== Erik H. Bakke | | To be or not to be... Senior Consultant/Developer|erik@habatech.no| Is simply a question of Habatech AS | | binary logic ===========================+================+============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 7:53:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 802731522D for ; Wed, 6 Oct 1999 07:53:26 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA55673; Wed, 6 Oct 1999 10:51:32 -0400 (EDT) (envelope-from wollman) Date: Wed, 6 Oct 1999 10:51:32 -0400 (EDT) From: Garrett Wollman Message-Id: <199910061451.KAA55673@khavrinen.lcs.mit.edu> To: Brad Knowles Cc: Alfred Perlstein , peter.jeremy@alcatel.com.au, freebsd-current@FreeBSD.ORG Subject: Re: make install trick In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Forgive me if I'm misunderstanding something here, but isn't > having /tmp on the root filesystem just inviting a denial-of-service > attack on yourself? Only if you let random lusers log in to your machine. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 7:57:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 5052F14C8C for ; Wed, 6 Oct 1999 07:57:22 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id QAA11858; Wed, 6 Oct 1999 16:57:12 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id QAA05338; Wed, 6 Oct 1999 16:57:11 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199910061451.KAA55673@khavrinen.lcs.mit.edu> References: <199910061451.KAA55673@khavrinen.lcs.mit.edu> Date: Wed, 6 Oct 1999 16:56:39 +0200 To: Garrett Wollman From: Brad Knowles Subject: Re: make install trick Cc: Alfred Perlstein , peter.jeremy@alcatel.com.au, freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:51 AM -0400 on 1999/10/6, Garrett Wollman wrote: > Only if you let random lusers log in to your machine. That's not the way I interpret some of the previous comments on this thread. It seems to me that not having /tmp on a separate filesystem has, indeed, created quite a nice little self-inflicted denial-of-service attack on certain people. ;-) -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 8:53:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from okstate.edu (email.okstate.edu [139.78.96.96]) by hub.freebsd.org (Postfix) with SMTP id 509E91567C for ; Wed, 6 Oct 1999 08:53:16 -0700 (PDT) (envelope-from @x8b4e5067.dhcp.okstate.edu:p0n@dali.dhs.org) Received: from x8b4e5067.dhcp.okstate.edu by email.okstate.edu id aa80000; 6 Oct 99 10:36 CDT From: "Phil 0. Nature" To: freebsd-current@freebsd.org MMDF-Warning: Parse error in original version of preceding line at email.okstate.edu Subject: identd Date: Wed, 6 Oct 1999 10:44:15 -0500 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone else experienced problems with identd not working? -- Phil Nature To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 10: 8:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 5DA0615723 for ; Wed, 6 Oct 1999 10:08:38 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id TAA20461 for current@FreeBSD.ORG; Wed, 6 Oct 1999 19:07:17 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id D8673885C; Wed, 6 Oct 1999 06:48:23 +0200 (CEST) Date: Wed, 6 Oct 1999 06:48:23 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: make install trick Message-ID: <19991006064823.A97435@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <000101bf0f78$fbe58b40$021d85d1@youwant.to> <199910052142.PAA05137@harmony.village.org> <99Oct6.084624est.40345@border.alcanet.com.au> <199910052302.RAA21667@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <199910052302.RAA21667@mt.sri.com> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nate Williams: > So, are you suggesting make /tmp it's own disk, otherwise anytime you do > development alot of writes are done to /. Of course /tmp should NOT be on /. Either in its separate FS or on another partition through a symlink. / should be as small and as write-free as possible. Mine is too small now for a 4.0 system (/ has grown a bit since 2.0... :)) though. > And, if you do lots of development, then you'll have the same problem on > /tmp as you did on / unless you waste a huge disk for /tmp. :( It doesn't have to be that huge and -pipe helps a lot for C/C++ :) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 10:27: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 8FB2314C2F for ; Wed, 6 Oct 1999 10:26:45 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id TAA10265; Wed, 6 Oct 1999 19:26:42 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id TAA12607; Wed, 6 Oct 1999 19:26:41 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Wed, 6 Oct 1999 19:25:29 +0200 To: Alfred Perlstein , peter.jeremy@alcatel.com.au From: Brad Knowles Subject: Re: make install trick Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:22 PM +0200 1999/10/6, Brad Knowles wrote: > Is there something fundamental I'm missing here? I thought > that this sort of thing was taught in SysAdmin 101.... My sincerest (and public) apologies to Alfred. There is something pretty fundamental that I was missing -- this problem is not restricted to just a softupdates filesystem filling up, and if it's the root filesystem then there can be a crash. No, this problem appears to be that if *any* softupdates filesystem fills up, it can crash the system. Now that I understand what it was I was missing, I'm much more reluctant to use softupdates in general, at least until this problem is fixed. Thanks for understanding, and helping me to more clearly understand the problem! -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 12:27: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from nisser.com (c1870039.telekabel.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id D0024156E6 for ; Wed, 6 Oct 1999 12:27:00 -0700 (PDT) (envelope-from roelof@nisser.com) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id VAA19303; Wed, 6 Oct 1999 21:28:00 +0200 (CEST) (envelope-from roelof@nisser.com) Message-ID: <37FBA256.E7E2F148@nisser.com> Date: Wed, 06 Oct 1999 21:26:14 +0200 From: Roelof Osinga Organization: eboa - engineering buro Office Automation X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: New CVSup mirror sites References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > ... > One common misconception is that cvsup(N+1).FreeBSD.org is somehow > less up-to-date than or not as good as cvsup(N).FreeBSD.org. That's > not the case at all -- the numbers mean nothing. For example, all 7 > of the US mirror sites get their updates hourly from the same master > site. (So do most of the non-US mirrors.) The only reasons to choose Most, but not all. Is it possible to list that information too. As well as an on easily found place. The link on the mainform gives http://www.nl.freebsd.org/support.html#cvs which does not list that information. A search gives over 25 documents, one of which is http://www.freebsd.org/handbook/mirrors-cvsup.html which also does not list that tidbit. I switched from the dutch mirror to an UK one because the latter was more up to date. So now there is a new dutch mirror. However, it is not clear how up to date it is. Roelof -- ---------------------------------------------------------------- Het Slakke Huis op http://SlakkeHuis.com/ ---------------------------------------------------------------- Home is where the (@) http://eboa.com/ is. Telekabel home http://nisser.com/ Beveiligingsverwijzingen http://nisser.com/links.htm Chello lijn monitor http://nisser.com/~roelof/logs_chello.shtml ---------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 13:48: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 2BD511575E for ; Wed, 6 Oct 1999 13:48:03 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id PAA17979; Wed, 6 Oct 1999 15:44:19 -0500 (CDT) Date: Wed, 6 Oct 1999 15:44:19 -0500 From: "Matthew D. Fuller" To: Peter Jeremy Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: make install trick Message-ID: <19991006154419.O20768@futuresouth.com> References: <99Oct6.103524est.40351@border.alcanet.com.au> <99Oct6.145359est.40347@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <99Oct6.145359est.40347@border.alcanet.com.au> X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 06, 1999 at 02:57:23PM +1000, a little birdie told me that Peter Jeremy remarked > > I guess we disagree on this. My feeling is that write activity on > root should be minimised to minimise the risk that root will be > inconsistent following a crash. Indeed. Thus: /dev/da0s1a on / (local, synchronous, writes: sync 32 async 15100) ^^^^^^^^^^^ Though I'm still waiting for an explanation of WHY exactly I have async writes on a sync partition. Nobody yet has said anything but 'that's interesting...'. A direction to look would be helpful. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 14:18:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 84F1D14C84 for ; Wed, 6 Oct 1999 14:18:51 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id QAA90799; Wed, 6 Oct 1999 16:18:16 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199910062118.QAA90799@celery.dragondata.com> Subject: Re: make install trick To: fullermd@futuresouth.com (Matthew D. Fuller) Date: Wed, 6 Oct 1999 16:18:15 -0500 (CDT) Cc: peter.jeremy@alcatel.com.au (Peter Jeremy), bright@wintelcom.net (Alfred Perlstein), freebsd-current@FreeBSD.ORG In-Reply-To: <19991006154419.O20768@futuresouth.com> from "Matthew D. Fuller" at Oct 06, 1999 03:44:19 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Wed, Oct 06, 1999 at 02:57:23PM +1000, a little birdie told me > that Peter Jeremy remarked > > > > I guess we disagree on this. My feeling is that write activity on > > root should be minimised to minimise the risk that root will be > > inconsistent following a crash. > > Indeed. > Thus: > /dev/da0s1a on / (local, synchronous, writes: sync 32 async 15100) > ^^^^^^^^^^^ > > Though I'm still waiting for an explanation of WHY exactly I have async > writes on a sync partition. Nobody yet has said anything but 'that's > interesting...'. A direction to look would be helpful. > My understanding was that that was just a indication of writes that were able to be done asynchronously without any risk, so they were done async. (sync isn't purely sync, only synchronous when it's required for integrity) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 14:48:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B254F15773 for ; Wed, 6 Oct 1999 14:48:36 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA89132; Wed, 6 Oct 1999 14:48:29 -0700 (PDT) (envelope-from dillon) Date: Wed, 6 Oct 1999 14:48:29 -0700 (PDT) From: Matthew Dillon Message-Id: <199910062148.OAA89132@apollo.backplane.com> To: "Matthew D. Fuller" Cc: Peter Jeremy , Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: make install trick References: <99Oct6.103524est.40351@border.alcanet.com.au> <99Oct6.145359est.40347@border.alcanet.com.au> <19991006154419.O20768@futuresouth.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Indeed. :Thus: :/dev/da0s1a on / (local, synchronous, writes: sync 32 async 15100) : ^^^^^^^^^^^ : :Though I'm still waiting for an explanation of WHY exactly I have async :writes on a sync partition. Nobody yet has said anything but 'that's :interesting...'. A direction to look would be helpful. :... :Matthew Fuller (MF4839) | fullermd@over-yonder.net : Access time updates perhaps? Try mounting with the 'noatime' option. Also, note that softupdates is *safer* then a synchronous mount in regards to ensuring filesystem consistancy. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 14:52:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 10E231534E for ; Wed, 6 Oct 1999 14:52:14 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40324>; Thu, 7 Oct 1999 07:48:36 +1000 Content-return: prohibited Date: Thu, 7 Oct 1999 07:52:04 +1000 From: Peter Jeremy Subject: Re: make install trick In-reply-to: <199910060614.HAA24521@hak.lan.Awfulhak.org> To: Brian Somers Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct7.074836est.40324@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <99Oct6.103524est.40351@border.alcanet.com.au> <199910060614.HAA24521@hak.lan.Awfulhak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-06 16:14:19 +1000, Brian Somers wrote: >> On 1999-Oct-06 09:55:26 +1000, Alfred Perlstein wrote: >> >I've seen softupdates nearly eliminate disk io for systems that used >> >an abmornal amount of temp files, but the fact that it can destabilize >> >a system worries me greatly. >> >> What do you mean by `destabilize'? There are bugs in softupdates >> which mean that an application may receive ENOSPC when writing to a >> filesystem even though space on that filesystem has been recently >> freed. Any application that cannot handle this situation is _broken_. >[.....] > >:-] You're joking right ? Most applications don't even *notice* >the situation let alone handle it. I wasn't really joking. Applications _should_ handle this situation. Most coding standards tell you to check for error conditions. Most programmers (including myself most of the time) just don't bother. (One reason being that C suffers from extreme code bloat and substantial loss of readability. C++ exceptions are a definite improvement here). > Whaddaya do when /var/log runs >out of space ? Show me an app that handles it..... The only app that normally writes in /var/log is syslogd. And the behaviour you want in this case depends on the sysadmin's level of paranoia (anything from `ignore it' to `halt the system'). >I guess you can argue the case, but in real life, running out of any >machine resource can cause all sorts of possibly unrecoverable >problems. Agreed. One reason I (and presumably others) don't bother to check for some errors is that it's not clear what you can or should do if you get the error. > IMHO the best way to deal with it in a generic way is to >have the give-me-the-resource function block if it really thinks it's >a temporary thing. How do you work out whether the resource shortage is temporary or not? This situation is orthogonal to the ever-popular `out of swapspace' issue (normally brought up in conjunction with swap overcommit). The difficulty with any recovery strategy is avoiding deadlocks. (I suspect that a major reason why root is not constrained by UFS MINFREE was to try and avoid the situation where the _system_ (as against the users) ran out of disk space). >In the case of softupdtes, I'd be surprised if it couldn't easily >figure out that the problem is *probably* transient and block, To quote an excerpt from the response I got from Kirk when I asked him about this problem: : I experimented with keeping a count of space that was pending :removal. If the filesystem was about to return a space full message, :it would check the pending count for the filesystem and if there was :space that was going to show up in the future, it would request that :the space freeing be expedited then go to sleep and wait for it. The :problem is that the space freeing can take up to a minute (typically :more like 30 seconds) during which time the file's inode is :locked. If the locked file is say a log file, then you can get a :temporary lock race to the root which make for really terrible :perceived performance. If the inode is unlocked during the wait, then :file inconsistencies can sneak in. So, the short answer is that you :should not run soft updates on filesystems where you are running with :less than a 60 second reserve of free space. Note the last sentence... Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 14:56:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 8BF58152B5 for ; Wed, 6 Oct 1999 14:56:46 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id QAA23944; Wed, 6 Oct 1999 16:56:24 -0500 (CDT) Date: Wed, 6 Oct 1999 16:56:24 -0500 From: "Matthew D. Fuller" To: Kevin Day Cc: Peter Jeremy , Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: make install trick Message-ID: <19991006165624.Q20768@futuresouth.com> References: <19991006154419.O20768@futuresouth.com> <199910062118.QAA90799@celery.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199910062118.QAA90799@celery.dragondata.com> X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 06, 1999 at 04:18:15PM -0500, a little birdie told me that Kevin Day remarked > > > > /dev/da0s1a on / (local, synchronous, writes: sync 32 async 15100) > > My understanding was that that was just a indication of writes that were > able to be done asynchronously without any risk, so they were done async. > > (sync isn't purely sync, only synchronous when it's required for integrity) I was given to understand that while the default mountop follows these conventions, explicit 'sync' meant SYNC meant SYNC meant SYNC. This is my root filesystem. It gets written to when I edit a file under /etc or do an installworld. I don't *CARE* how slow it is, I want to know that it's solid, consistent, and complete. Just 'consistent' isn't enough. No write is able to be done async without risk when I'm explicitly saying 'write everything synchronously'. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 15:15:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 4444B151B1 for ; Wed, 6 Oct 1999 15:15:28 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40324>; Thu, 7 Oct 1999 08:10:28 +1000 Content-return: prohibited Date: Thu, 7 Oct 1999 08:13:03 +1000 From: Peter Jeremy Subject: Re: pfft Re: make install trick In-reply-to: To: Alfred Perlstein Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct7.081028est.40324@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-07 01:51:52 +1000, Alfred Perlstein wrote: >First post: > hey, anyone having crashes when doing installworld might like > my INSTALL="sync && install -C" trick I haven't kept that post. My recollection is that the problem was installworld dying, not the system crashing. If I misread or mis-remember the post, my apologies. >no matter which option you choose you can still get bitten by >softupdates when you do run out of space even by a trusted >user such as root. Softupdates reporting ENOSPC soon after a delete is a known bug. At this stage the recommended workaround (according to Kirk) is not to run softupdates on filesystems where this condition is likely. If anyone wants to fix it, patches would be welcomed by Kirk or Julian. If softupdates is causing panics, that is an extremely undesirable bug. I haven't been bitten (yet) and don't have a solution. My view is that the remainder of the thread has been discussing the relative merits of different ways to avoid the problem. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 15:46:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 56E4715793 for ; Wed, 6 Oct 1999 15:45:18 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id AAA19892; Thu, 7 Oct 1999 00:40:49 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id AAA93222; Thu, 7 Oct 1999 00:45:17 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id AAA00461; Thu, 7 Oct 1999 00:45:11 +0200 (CEST) (envelope-from ticso) Date: Thu, 7 Oct 1999 00:45:10 +0200 From: Bernd Walter To: freebsd-current@freebsd.org Cc: grog@lemis.com Subject: ahc panics and (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. Message-ID: <19991007004510.A393@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm getting this with a recent current (6. october): (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. (da2:ahc2:0:2:0): Have seen Data Phase. Length = 0. NumSGs = 1. (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. (da2:ahc2:0:2:0): Have seen Data Phase. Length = 0. NumSGs = 1. (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. (da2:ahc2:0:2:0): Have seen Data Phase. Length = 0. NumSGs = 1. Fatal trap 12: page fault while in kernel mode fault virtual address = 0xbfc00000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc020fa16 stack pointer = 0x10:0xc02600bc frame pointer = 0x10:0xc02601f4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = kernel: type 12 trap, code=0 Stopped at bus_dmamap_load+0x1ce: movl PTmap(,%eax,4),%edx (kgdb) bt #0 bus_dmamap_load (dmat=0xc0834340, map=0xc0293980, buf=0x0, buflen=0x0, callback=0xc013729c , callback_arg=0xc083a4a0, flags=0x0) at machine/pmap.h:172 #1 0xc013779f in ahc_setup_data (ahc=0xc0830600, csio=0xc09c6000, scb=0xc083a4a0) at ../../dev/aic7xxx/aic7xxx.c:5037 #2 0xc0136c15 in ahc_action (sim=0xc08341c0, ccb=0xc09c6000) at ../../dev/aic7xxx/aic7xxx.c:4530 #3 0xc011deef in xpt_run_dev_sendq (bus=0xc0834180) at ../../cam/cam_xpt.c:3685 #4 0xc011ea30 in xpt_release_devq_device (dev=0xc0878200, count=0x1, run_queue=0x1) at ../../cam/cam_xpt.c:4393 #5 0xc011e958 in xpt_release_devq (path=0xc08abcd0, count=0x1, run_queue=0x1) at ../../cam/cam_xpt.c:4346 #6 0xc011d9a4 in xpt_action (start_ccb=0xc02603e8) at ../../cam/cam_xpt.c:3275 #7 0xc0121aba in cam_release_devq (path=0xc08abcd0, relsim_flags=0x0, openings=0x0, timeout=0xc013729c, getcount_only=0x0) at ../../cam/cam_periph.c:864 #8 0xc01221c9 in cam_periph_error (ccb=0xc09c6000, camflags=CAM_FLAG_NONE, sense_flags=0x11, save_ccb=0xc0889e04) at ../../cam/cam_periph.c:1646 #9 0xc0124a9f in daerror (ccb=0xc09c6000, cam_flags=0x0, sense_flags=0x10) at ../../cam/scsi/scsi_da.c:1376 #10 0xc012463f in dadone (periph=0xc0882880, done_ccb=0xc09c6000) at ../../cam/scsi/scsi_da.c:1146 #11 0xc0120703 in camisr (queue=0xc027c094) at ../../cam/cam_xpt.c:6217 #12 0xc0120515 in swi_cambio () at ../../cam/cam_xpt.c:6124 #13 0xc02128e0 in splz_swi () I can reproduce this situation. It happened using vinum on a single Raid5 plex volume with 3 disks. Softupdates is enabled. I trigger this when copying the cvs-tree on it or removing it. The first time I saw this was with a world from 30th september. Remembering the last messages on the list I updated the kernel and the vinum.ko just to see the same thing happen. This time there were the data overrun messages on the console as shown, but sometimes it simply panics looking the same without any console output beside the panic itself. I don't know the timegap between the consoleoutput and the panic. I can't write a crash dump and produced this output using a live gdb-session so a quick response if further online informations are needed would be nice. Beside: is there any way to get a dump over the seriel-line? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 15:53:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id F153D15782 for ; Wed, 6 Oct 1999 15:51:45 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id SAA18925; Wed, 6 Oct 1999 18:54:00 -0400 (EDT) Date: Wed, 6 Oct 1999 18:54:00 -0400 (EDT) From: Ben Rosengart To: "Matthew D. Fuller" Cc: Peter Jeremy , Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: make install trick In-Reply-To: <19991006154419.O20768@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Oct 1999, Matthew D. Fuller wrote: > Indeed. > Thus: > /dev/da0s1a on / (local, synchronous, writes: sync 32 async 15100) > ^^^^^^^^^^^ > > Though I'm still waiting for an explanation of WHY exactly I have async > writes on a sync partition. Nobody yet has said anything but 'that's > interesting...'. A direction to look would be helpful. I believe "synchronous" refers only to metadata writes. So it would follow that the async writes are non-metadata writes. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 16: 0:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B77CD1578A for ; Wed, 6 Oct 1999 16:00:27 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40332>; Thu, 7 Oct 1999 08:55:36 +1000 Content-return: prohibited Date: Thu, 7 Oct 1999 08:59:00 +1000 From: Peter Jeremy Subject: Re: make install trick In-reply-to: <19991006154419.O20768@futuresouth.com> To: "Matthew D. Fuller" Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct7.085536est.40332@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <99Oct6.103524est.40351@border.alcanet.com.au> <99Oct6.145359est.40347@border.alcanet.com.au> <19991006154419.O20768@futuresouth.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-07 06:44:19 +1000, Matthew D. Fuller wrote: >/dev/da0s1a on / (local, synchronous, writes: sync 32 async 15100) > ^^^^^^^^^^^ > >Though I'm still waiting for an explanation of WHY exactly I have async >writes on a sync partition. Nobody yet has said anything but 'that's >interesting...'. A direction to look would be helpful. You get a synchronous mount by passing MNT_SYNCHRONOUS to mount(2). Within the kernel, MNT_SYNCHRONOUS is used (basically only) within kern/vfs_vnops.c:vn_write(). There it adds IO_SYNC to the write request (the same as if the file has O_FSYNC enabled). IO_SYNC will be ignored if MNT_ASYNC is specified (which it isn't here). The write request goes through ufs/ufs/ufs_readwrite.c:WRITE(), which passes it to bwrite() if it's IO_SYNC. Inode access time updates (controlled by MNT_NOATIME, which becomes ~IN_ACCESS, which becomes IN_MODIFIED) don't go through vn_write() and wind up in bdwrite(). As far as I can tell, the net effect is that inode access time updates will remain async writes into the filesystem. An easy way to tell would be to use NOATIME and see if you're still getting async writes. (Or any writes at all). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 16:16:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 2229F14EA4 for ; Wed, 6 Oct 1999 16:16:10 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id SAA29629; Wed, 6 Oct 1999 18:15:43 -0500 (CDT) Date: Wed, 6 Oct 1999 18:15:42 -0500 From: "Matthew D. Fuller" To: Peter Jeremy Cc: freebsd-current@FreeBSD.ORG Subject: {a}sync updates (was Re: make install trick) Message-ID: <19991006181542.S20768@futuresouth.com> References: <99Oct6.103524est.40351@border.alcanet.com.au> <99Oct6.145359est.40347@border.alcanet.com.au> <19991006154419.O20768@futuresouth.com> <99Oct7.085536est.40332@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <99Oct7.085536est.40332@border.alcanet.com.au> X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you, this is *EXACTLY* what I was looking for :) On Thu, Oct 07, 1999 at 08:59:00AM +1000, a little birdie told me that Peter Jeremy remarked > > As far as I can tell, the net effect is that inode access time updates > will remain async writes into the filesystem. > > An easy way to tell would be to use NOATIME and see if you're still > getting async writes. (Or any writes at all). This does appear to be it. Testing such things as (cat /kernel >> /dev/null && sync && sync) preceded and followed by a 'mount' call in another window does show the 'async' counter incrementing, and when I remount it noatime it no longer does. Is this good, bad, ugly, or just inconsistent? On the one hand, you can argue that 'sync should be sync should be sync, I don't bloody care, just don't do anything async at all', since that's what it's supposed to do: mount(8): sync All I/O to the file system should be done synchronously. On the gripping hand, you can say, 'this is an ATIME update, there's no way its presence or lack thereof can do anything bad to the filesystem, so let it be async since it takes extra work to make it sync'. Does anyone have any feeling either way on this? I, unfortunately, seem to have strong feelings BOTH ways... sync atime updates will slow it down, but on the flip side, if you're mounting sync in the first place you don't care much for speed anyway. Thoughts? -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 17:32:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E93DD14CB2 for ; Wed, 6 Oct 1999 17:32:23 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from d229.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id KAA00529; Thu, 7 Oct 1999 10:33:37 +1000 Date: Thu, 7 Oct 1999 10:31:46 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "Matthew D. Fuller" Cc: Peter Jeremy , Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: make install trick In-Reply-To: <19991006154419.O20768@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /dev/da0s1a on / (local, synchronous, writes: sync 32 async 15100) > ^^^^^^^^^^^ > > Though I'm still waiting for an explanation of WHY exactly I have async > writes on a sync partition. Nobody yet has said anything but 'that's > interesting...'. A direction to look would be helpful. The sync flag only affects data writes and block allocation for data writes. Metadata is normally always written synchronously, except for safe optimisations. Safe optimisations include never writing inode or block bitmaps (fsck can recover these), not writing some indirect blocks (correct block numbers are not very useful until the blocks have been written), and not writing inodes in many cases where only timestamps have changed. You seem to have a lot of async writes. This may be caused by using soft updates. Soft updates causes many (or most or all) metadata updates to be done using delayed writes. Using the sync flag with soft updates doesn't make much sense and may be harmfull (there doesn't seem to be anything to prevent data writes being done long before the metadata points to the data). Smaller number of async writes may be caused by metadata write optimisations. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 18:19:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4B0A815089 for ; Wed, 6 Oct 1999 18:19:35 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA90021; Wed, 6 Oct 1999 18:19:32 -0700 (PDT) (envelope-from dillon) Date: Wed, 6 Oct 1999 18:19:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199910070119.SAA90021@apollo.backplane.com> To: "Matthew D. Fuller" Cc: Peter Jeremy , freebsd-current@FreeBSD.ORG Subject: Re: {a}sync updates (was Re: make install trick) References: <99Oct6.103524est.40351@border.alcanet.com.au> <99Oct6.145359est.40347@border.alcanet.com.au> <19991006154419.O20768@futuresouth.com> <99Oct7.085536est.40332@border.alcanet.com.au> <19991006181542.S20768@futuresouth.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :mount(8): : sync All I/O to the file system should be done synchronously. : :On the gripping hand, you can say, 'this is an ATIME update, there's no :way its presence or lack thereof can do anything bad to the filesystem, :so let it be async since it takes extra work to make it sync'. : :Does anyone have any feeling either way on this? I, unfortunately, seem :to have strong feelings BOTH ways... sync atime updates will slow it :down, but on the flip side, if you're mounting sync in the first place :you don't care much for speed anyway. : :Thoughts? :Matthew Fuller (MF4839) | fullermd@over-yonder.net Well, you don't gain anything by making atime updates sync, and you lose a lot, so why do it? If you are worried about protecting the root drive from a crash, mount it read-only (and put /dev on an MFS mount) or mount it noatime. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 18:57:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id A24F315360 for ; Wed, 6 Oct 1999 18:57:40 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40324>; Thu, 7 Oct 1999 11:54:03 +1000 Content-return: prohibited Date: Thu, 7 Oct 1999 11:57:26 +1000 From: Peter Jeremy Subject: Re: {a}sync updates (was Re: make install trick) In-reply-to: <19991006181542.S20768@futuresouth.com> To: "Matthew D. Fuller" Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct7.115403est.40324@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <99Oct6.103524est.40351@border.alcanet.com.au> <99Oct6.145359est.40347@border.alcanet.com.au> <19991006154419.O20768@futuresouth.com> <99Oct7.085536est.40332@border.alcanet.com.au> <19991006181542.S20768@futuresouth.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-07 09:15:42 +1000, Matthew D. Fuller wrote: >Is this good, bad, ugly, or just inconsistent? On the one hand, you can >argue that 'sync should be sync should be sync, I don't bloody care, just >don't do anything async at all', since that's what it's supposed to do: >mount(8): > sync All I/O to the file system should be done synchronously. How detailed should the man page be? If it stated "all file data will be written synchronously, but inodes where the only update is atime and free block bitmaps are written asynchronously", would that be any clearer to a user who didn't have a detailed understanding of UFS? If you would like it to say something different, write some patches and send them in as a PR (keeping in mind phk's recent e-mail about green bikesheds). > sync atime updates will slow it >down, but on the flip side, if you're mounting sync in the first place >you don't care much for speed anyway. There should be fairly few writes to the root partition, so having these writes synchronous is not a big performance hit. On the other hand, there are probably a _lot_ of read accesses to devices in /dev and files in /bin (how many of your scripts begin #!/bin/sh?). Unless you specify NOATIME, each of these read accesses implies an atime update within the inode. Making these synchronous probably would be a big performance hit. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 23: 2:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat203.183.mpoweredpc.net [142.177.203.183]) by hub.freebsd.org (Postfix) with ESMTP id 2FAA514F01 for ; Wed, 6 Oct 1999 23:02:05 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id DAA11234 for ; Thu, 7 Oct 1999 03:00:53 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 7 Oct 1999 03:00:52 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: modules: how to use? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Figuring one of the things a friend of mine raves about Linux for is their kld's, I'd start playing with ours... Looking in /modules, I saw 'procfs', so, cool, a place to start...remove "options PROCFS" from kernel config, rebuild, install and reboot ... crashes... so, I figure that I somehow have to tell the kernel to load that module? checked the kld man page, and nothing in there appears to be appropriate...and just looked at my /usr/src/etc/rc* files to see if maybe it was something I was supposed to configure in there, but nothing appears to be in tehre either... Help? Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 23:11: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id E8C5C14F57 for ; Wed, 6 Oct 1999 23:10:46 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA12713; Thu, 7 Oct 1999 15:40:19 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [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: Thu, 07 Oct 1999 15:40:19 +0930 (CST) From: "Daniel O'Connor" To: The Hermit Hacker Subject: RE: modules: how to use? Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Oct-99 The Hermit Hacker wrote: > Looking in /modules, I saw 'procfs', so, cool, a place to start...remove > "options PROCFS" from kernel config, rebuild, install and reboot ... > so, I figure that I somehow have to tell the kernel to load that module? Well its a kld.. You don't have to reboot.. Since its a VFS module mount will load it automatically anyway.. Maybe a better place to start would be linux emulation.. The 'linux' shell script basically does a kldload linux Have a look at /boot/defaults/loader.conf for stuff you can load as a module before the kernel is executed. --- 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-current" in the body of the message From owner-freebsd-current Wed Oct 6 23:13:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 1F39114F57 for ; Wed, 6 Oct 1999 23:13:22 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA89750; Thu, 7 Oct 1999 15:42:58 +0930 (CST) Date: Thu, 7 Oct 1999 15:42:57 +0930 From: Greg Lehey To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? Message-ID: <19991007154257.I78191@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 7 October 1999 at 3:00:52 -0300, The Hermit Hacker wrote: > > Figuring one of the things a friend of mine raves about Linux for is their > kld's, I'd start playing with ours... Yes, it's funny how the Linuxers rave about loadable modules. It's a good idea, but I don't see anything that spectacular about it. > Looking in /modules, I saw 'procfs', so, cool, a place to start...remove > "options PROCFS" from kernel config, rebuild, install and reboot ... > > crashes... How? > so, I figure that I somehow have to tell the kernel to load that module? > > checked the kld man page, and nothing in there appears to be > appropriate...and just looked at my /usr/src/etc/rc* files to see if maybe > it was something I was supposed to configure in there, but nothing appears > to be in tehre either... > > Help? Well, the standard way to load a kld is with kldload(1) or kldload(2). I don't know if procfs works properly like this, though. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 23:16:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 7F7A414CAC for ; Wed, 6 Oct 1999 23:16:42 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA77410; Thu, 7 Oct 1999 08:16:08 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910070616.IAA77410@gratis.grondar.za> To: Greg Lehey Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? Date: Thu, 07 Oct 1999 08:16:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, the standard way to load a kld is with kldload(1) or kldload(2). > I don't know if procfs works properly like this, though. Procfs works just fine: [groovy] /usr/src.With_secure_NFS # kldstat Id Refs Address Size Name 1 7 0xc0100000 1a10cc kernel.debug 2 1 0xc09c1000 3000 mfs.ko 3 1 0xc09cd000 6000 procfs.ko 4 1 0xc09da000 8000 if_xl.ko 5 1 0xc09e3000 7000 miibus.ko 6 1 0xc09f9000 4b000 nfs.ko 7 1 0xc0a6a000 2000 green_saver.ko M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 6 23:18:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 5A4B414CAC for ; Wed, 6 Oct 1999 23:18:31 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA12764; Thu, 7 Oct 1999 15:48:17 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [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: <19991007154257.I78191@freebie.lemis.com> Date: Thu, 07 Oct 1999 15:48:17 +0930 (CST) From: "Daniel O'Connor" To: Greg Lehey Subject: Re: modules: how to use? Cc: freebsd-current@FreeBSD.ORG, The Hermit Hacker Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Oct-99 Greg Lehey wrote: > Well, the standard way to load a kld is with kldload(1) or kldload(2). > I don't know if procfs works properly like this, though. Well I would assume (aha) that when mount cannot find procfs in the list of FS's the kernel knows about it would try and load it just like all the others.. --- 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-current" in the body of the message From owner-freebsd-current Wed Oct 6 23:58:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 81EE614FC4 for ; Wed, 6 Oct 1999 23:58:19 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id BAA01933; Thu, 7 Oct 1999 01:57:53 -0500 (CDT) Date: Thu, 7 Oct 1999 01:57:53 -0500 From: "Matthew D. Fuller" To: Peter Jeremy Cc: freebsd-current@FreeBSD.ORG Subject: Re: {a}sync updates (was Re: make install trick) Message-ID: <19991007015753.C940@futuresouth.com> References: <99Oct6.103524est.40351@border.alcanet.com.au> <99Oct6.145359est.40347@border.alcanet.com.au> <19991006154419.O20768@futuresouth.com> <99Oct7.085536est.40332@border.alcanet.com.au> <19991006181542.S20768@futuresouth.com> <99Oct7.115403est.40324@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <99Oct7.115403est.40324@border.alcanet.com.au> X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 07, 1999 at 11:57:26AM +1000, a little birdie told me that Peter Jeremy remarked > > How detailed should the man page be? Exactly my query in writing this ;> > If it stated "all file data will > be written synchronously, but inodes where the only update is atime > and free block bitmaps are written asynchronously", would that be any > clearer to a user who didn't have a detailed understanding of UFS? > If you would like it to say something different, write some patches > and send them in as a PR (keeping in mind phk's recent e-mail about > green bikesheds). I'm still stewing on what should be with it; what we have works fine, if being slightly inconsistent in an obscure way. I'm trolling for ideas on whether well enough should be left alone (since there's obviously an incredibly small percentage of people USING sync as a mountop), or whether a footnote should be added somewhere (I lean toward mount(2) instead of mount(8) myself, with a possible xref in mount(8)). I'll see what I think of, and possibly have some diffs tomorrow. > There should be fairly few writes to the root partition, so having > these writes synchronous is not a big performance hit. On the other > hand, there are probably a _lot_ of read accesses to devices in /dev > and files in /bin (how many of your scripts begin #!/bin/sh?). Unless > you specify NOATIME, each of these read accesses implies an atime > update within the inode. Making these synchronous probably would > be a big performance hit. This is why I haven't screamed for them to be sync-tified... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 2:42:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id D96FE1584F for ; Thu, 7 Oct 1999 02:42:22 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p23-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.120]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id SAA20182; Thu, 7 Oct 1999 18:42:04 +0900 (JST) Message-ID: <37FC6A10.95E59914@newsguy.com> Date: Thu, 07 Oct 1999 18:38:24 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > > Figuring one of the things a friend of mine raves about Linux for is their > kld's, I'd start playing with ours... > > Looking in /modules, I saw 'procfs', so, cool, a place to start...remove > "options PROCFS" from kernel config, rebuild, install and reboot ... > > crashes... > > so, I figure that I somehow have to tell the kernel to load that module? fs modules are automagically loaded. Alas, that's the general direction for a lot of modules. The network ones, for instance. No more need to put in the device lines in the kernel configuration file, it will be automagically loaded by ifconfig. I don't know if this is working already or not, though. Now, how to tell the kernel to load modules. Well, some stuff you can set with rc.conf(5). Other stuff you may load explicitly through kldload. And, finally, you don't need to have the _kernel_ load it. You may edit loader.conf(5) to have it loaded at the same time the kernel is loaded by, well, the loader(8). :-) (the bootstrap loader) > checked the kld man page, and nothing in there appears to be > appropriate...and just looked at my /usr/src/etc/rc* files to see if maybe > it was something I was supposed to configure in there, but nothing appears > to be in tehre either... > > Help? Wild shot: are your kernel & world in sync? For isntance, you made a new kernel when you edited your kernel configuration file to remove the option line, right? If you just happened to have newer sources, the new kernel might have become incompatible with the older modules, which are not made automatically (except during world). cd /sys/modules; make all install. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 3:22:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id E598F15097 for ; Thu, 7 Oct 1999 03:21:40 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.037 #1) id 11ZAfm-000AtE-00; Thu, 07 Oct 1999 12:21:18 +0200 From: Sheldon Hearn To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? In-reply-to: Your message of "Thu, 07 Oct 1999 03:00:52 -0300." Date: Thu, 07 Oct 1999 12:21:18 +0200 Message-ID: <41863.939291678@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 07 Oct 1999 03:00:52 -0300, The Hermit Hacker wrote: > checked the kld man page, and nothing in there appears to be > appropriate... You should have checked the SEE ALSO secion of the manpage (I wonder whether Ruslan Ermilov is reading?) *grin* SEE ALSO kldfind(2), kldfirstmod(2), kldload(2), kldnext(2), kldstat(2), kldunload(2), kldload(8), kldstat(8), kldunload(8) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 5:53:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with SMTP id EF6DA15129 for ; Thu, 7 Oct 1999 05:53:34 -0700 (PDT) (envelope-from matt@camtech.net.au) Received: from dialup-ad-15-44.camtech.net.au ([203.55.243.44]) by camtech.net.au ; Thu, 07 Oct 1999 22:23:24 +0930 Date: Thu, 7 Oct 1999 22:23:49 +0930 (CST) From: Matthew Thyer X-Sender: matt@localhost Reply-To: thyerm@camtech.net.au To: Peter Jeremy Cc: "Matthew D. Fuller" , freebsd-current@FreeBSD.ORG Subject: Re: {a}sync updates (was Re: make install trick) In-Reply-To: <99Oct7.115403est.40324@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe the best solution is the following: - leave "sync" with its current behaviour - create a sysctl to make it truely synchronous (I was thinking of a new mount option but thats overkill) and have the documentation for that sysctl state the performance hit and recommend that the filesystem be mounted with "noatime" when this sysctl is on. The sysctl could have three levels: - off - on for atime updates - on for atime updates and free block bitmap updates On Thu, 7 Oct 1999, Peter Jeremy wrote: > On 1999-Oct-07 09:15:42 +1000, Matthew D. Fuller wrote: > >Is this good, bad, ugly, or just inconsistent? On the one hand, you can > >argue that 'sync should be sync should be sync, I don't bloody care, just > >don't do anything async at all', since that's what it's supposed to do: > >mount(8): > > sync All I/O to the file system should be done synchronously. > > How detailed should the man page be? If it stated "all file data will > be written synchronously, but inodes where the only update is atime > and free block bitmaps are written asynchronously", would that be any > clearer to a user who didn't have a detailed understanding of UFS? > If you would like it to say something different, write some patches > and send them in as a PR (keeping in mind phk's recent e-mail about > green bikesheds). > > > sync atime updates will slow it > >down, but on the flip side, if you're mounting sync in the first place > >you don't care much for speed anyway. > > There should be fairly few writes to the root partition, so having > these writes synchronous is not a big performance hit. On the other > hand, there are probably a _lot_ of read accesses to devices in /dev > and files in /bin (how many of your scripts begin #!/bin/sh?). Unless > you specify NOATIME, each of these read accesses implies an atime > update within the inode. Making these synchronous probably would > be a big performance hit. > > Peter > -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 8: 9:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 4D14D1514F for ; Thu, 7 Oct 1999 08:09:23 -0700 (PDT) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1001) id 79C3112F; Thu, 7 Oct 1999 17:09:16 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by shadowmere.student.utwente.nl (Postfix) with ESMTP id 3CDD4A9 for ; Thu, 7 Oct 1999 17:09:16 +0200 (CEST) Date: Thu, 7 Oct 1999 17:09:16 +0200 (CEST) From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: shell script trouble Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have for a while now (couple of weeks now I think) noticed that certain shell scripts all of a sudden don't work any longer (even though they did just fine earlier) ... the only thing that actually changed has been more recent updates of FreeBSD-current. The scripts I am having problems with are: /usr/local/etc/rc.d/rc5des.sh /usr/local/etc/postfix/postfix-script Both of these scripts still are as they were installed by their respective ports. And I know both have worked just fine for months without problems. The rc5des breakage I noticed about a weeks ago .. the postfix breakage I noticed today, while installing postfix on another system and finding out "postfix reload" no longer worked ... Is there anybody here that happens to know why these previously perfectly working shell-scripts all of a sudden are broken now ? -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 8:34: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B4B9615815 for ; Thu, 7 Oct 1999 08:33:51 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.037 #1) id 11ZFVA-000C1y-00; Thu, 07 Oct 1999 17:30:40 +0200 From: Sheldon Hearn To: Pascal Hofstee Cc: freebsd-current@FreeBSD.ORG Subject: Re: shell script trouble In-reply-to: Your message of "Thu, 07 Oct 1999 17:09:16 +0200." Date: Thu, 07 Oct 1999 17:30:40 +0200 Message-ID: <46249.939310240@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 07 Oct 1999 17:09:16 +0200, Pascal Hofstee wrote: > Is there anybody here that happens to know why these previously perfectly > working shell-scripts all of a sudden are broken now ? You'll greatly increase the chances of getting a useful answer if you show us _how_ they're breaking. :-) Cut'n'paste is your friend. Later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 8:48:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id BA7621522E; Thu, 7 Oct 1999 08:48:20 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id SAA16602; Thu, 7 Oct 1999 18:47:48 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Thu, 7 Oct 1999 18:47:47 +0300 (EEST) From: Adrian Penisoara To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, On Wed, 6 Oct 1999, Adrian Penisoara wrote: > hi again, > > On Tue, 5 Oct 1999, Matthew Dillon wrote: > > > : The problem is that the machine is completely locked, I can't get into > > :the debugger with CTR-ALT-ESC; no panics so there are no coredumps > > :catched. Any advise ? Could you escape in the debugger when you were hit > > :by these bugs ? > > > > If it's completely locked up and ctl-alt-esc doesn't work (and normally > > does work - try it on a working system to make sure that you've compiled > > in the appropriate DDB options), and you aren't in an X display > > (ctl-alt-esc isn't useful when done from an X display)... then your > > lockup problem is unrelated to mmap. > > No X on the machine, but CTRL-ALT-ESC doesn't work. > And another thing: I tried the MMAP "exploit"/test that has been floating > around at that time on another 3.2-STABLE machine SMP with 2 Pentiums and > it does lock the machine but you can switch consoles and escape to the > debugger; on the production server (K6-2 300) everything goes dead when > it happens (I haven't tried the MMAP test)... > > You're probably right, it's not the MMAP bug; but it's not faulty > hardware -- I'll have an undeniable proof in a few days, I have downgraded > to 3.1-STABLE as of 20th April... > Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault error (strange, it didn't look like a normal panic screen, just the message and the content of three registers, then the syncing disks message). It seems that I might be wrong about hardware not being the problem. I've changed the motherboard, CPU, memory and the video card and I'm waiting to see how much it's going to stay up (I have 1day 1hour uptime so far)... Thanks, Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 10: 7:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 4FDE814A0B for ; Thu, 7 Oct 1999 10:07:16 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id SAA50852 for current@FreeBSD.org; Thu, 7 Oct 1999 18:42:51 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 07 Oct 1999 18:42:49 +0200 From: Marcel Moolenaar Message-ID: <37FCCD89.9EF2EFFF@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: CVSup work again! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Before I completely forget: CVSup should work as before. The workaround is not needed anymore. Thanks for your patience, -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 10: 9:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B719E15274; Thu, 7 Oct 1999 10:09:38 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA95541; Thu, 7 Oct 1999 10:09:23 -0700 (PDT) (envelope-from dillon) Date: Thu, 7 Oct 1999 10:09:23 -0700 (PDT) From: Matthew Dillon Message-Id: <199910071709.KAA95541@apollo.backplane.com> To: Adrian Penisoara Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi again, : : Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault :error (strange, it didn't look like a normal panic screen, just the :message and the content of three registers, then the syncing disks :message). It seems that I might be wrong about hardware not being the :problem. : : I've changed the motherboard, CPU, memory and the video card and I'm :waiting to see how much it's going to stay up (I have 1day 1hour uptime so :far)... : : Thanks, : Ady (@warpnet.ro) One thing I do on all 'server' class machines that I buy (and this is also something that BEST instituted as policy in 1998) is to only buy motherboards with ECC support and only buy ECC memory to go along with that support. If you are using a non-ECC motherboard or non-ECC memory I would heartily recommend that you adopt the same policy. Not that your problem is necessarily memory related, but I've found that memory-related problems account for at least 80% of the 'difficult to locate' hardware problems that normally occur with PC technology. ECC gives you protection not only against hardware faults, but it also protects you against remarked dynamic ram chips and processors by catching the timing errors that usually occur with such chips relatively soon after purchase rather then weeks or months down the line. Being the commodity it is, memory is the most likely item on the motherboard to be out of spec. Intel's ECC implementation is not perfect (1), but it's good enough to catch these sorts of problems. note 1: Intel doesn't implement memory scrubbing properly outside of the Xeon line and FreeBSD does not scrub memory either. Scrubbing is a method of preventing bit errors from building up in memory by regenerating the ECC bits with a memory read followed by a memory write of the same data. Outside of the Xeon chipsets the OS must issue a read followed by a write. With the Xeon chipsets the OS need only issue a read and hardware will automatically rewrite a correction if it finds a bit error. This information is 6 months old so the situation may have changed. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 10:15:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0481A14A0B for ; Thu, 7 Oct 1999 10:15:07 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA00678; Thu, 7 Oct 1999 10:15:06 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA47282; Thu, 7 Oct 1999 10:15:06 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 7 Oct 1999 10:15:06 -0700 (PDT) Message-Id: <199910071715.KAA47282@vashon.polstra.com> To: marcel@scc.nl Subject: Re: CVSup work again! In-Reply-To: <37FCCD89.9EF2EFFF@scc.nl> References: <37FCCD89.9EF2EFFF@scc.nl> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <37FCCD89.9EF2EFFF@scc.nl>, Marcel Moolenaar wrote: > Before I completely forget: CVSup should work as before. The > workaround is not needed anymore. Thanks for your patience, Thanks for healing my problem child, Marcel. It's kind of, er, sensitive ... just like me. :-) Note, you still can't _build_ a working version under -current yet. That requires a lot of patches to the port. I'm working on it, but it will be a few days still before I commit anything. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 11:20:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3B919157EA for ; Thu, 7 Oct 1999 11:20:07 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA97037; Thu, 7 Oct 1999 11:20:07 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA58728; Thu, 7 Oct 1999 11:20:03 -0700 (PDT) (envelope-from obrien) Date: Thu, 7 Oct 1999 11:20:03 -0700 From: "David O'Brien" To: "Daniel C. Sobral" Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? Message-ID: <19991007112003.A58700@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <37FC6A10.95E59914@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <37FC6A10.95E59914@newsguy.com> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The network ones, for instance. No more need to put in the device lines > in the kernel configuration file, it will be automagically loaded by > ifconfig. I don't know if this is working already or not, though. It works in -CURRENT for most PCI network devices (`de' is one notable exception). ISA ones still need to be statically compiled into your kernel. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 11:28:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E2A6D14A27 for ; Thu, 7 Oct 1999 11:28:30 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA05422 for ; Thu, 7 Oct 1999 11:27:56 -0700 Date: Thu, 7 Oct 1999 11:27:56 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: i386 wierd one...... kernel stack frame pointer corruption(?) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This just started happening over the last day... It's blowing up during probing because the frame pointer is getting nuked... this is a 2xPPro machine. The code in question is: static u_int64_t isp_get_portname(isp, loopid, nodename) struct ispsoftc *isp; int loopid; int nodename; { u_int64_t wwn = 0; mbreg_t mbs; mbs.param[0] = MBOX_GET_PORT_NAME; mbs.param[1] = loopid << 8; if (nodename) mbs.param[1] |= 1; isp_mboxcmd(isp, &mbs); Which generates: 000012f0 : 12f0: 55 pushl %ebp 12f1: 89 e5 movl %esp,%ebp 12f3: 83 ec 10 subl $0x10,%esp 12f6: 56 pushl %esi 12f7: 53 pushl %ebx 12f8: bb 00 00 00 00 movl $0x0,%ebx 12fd: be 00 00 00 00 movl $0x0,%esi 1302: 66 c7 45 f0 6a movw $0x6a,0xfffffff0(%ebp) 1307: 00 1308: 8b 4d 0c movl 0xc(%ebp),%ecx 130b: 66 c1 e1 08 shlw $0x8,%cx 130f: 66 89 4d f2 movw %cx,0xfffffff2(%ebp) 1313: 83 7d 10 00 cmpl $0x0,0x10(%ebp) 1317: 74 04 je 131d 1319: 80 4d f2 01 orb $0x1,0xfffffff2(%ebp) 131d: 8d 45 f0 leal 0xfffffff0(%ebp),%eax 1320: 50 pushl %eax 1321: ff 75 08 pushl 0x8(%ebp) 1324: e8 b7 27 00 00 call 3ae0 1329: 66 81 7d f0 00 cmpw $0x4000,0xfffffff0(%ebp) <-- EBP is 0 132e: 40 There isn't anything in isp_mboxcmd that I can see would wipe the stack such that I can see in the C code or the generated output. This code itself hasn't changed in months. One thing that is possible is that it's a very deep callstack... It's during probing and it may have called completion on a completing command while down at the bottom of the stack starting another command. If you run out of kernel stack, don't you get some other kind of fault? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 12:11:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 2BCFC14C1A for ; Thu, 7 Oct 1999 12:11:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00921; Thu, 7 Oct 1999 12:01:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910071901.MAA00921@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: freebsd-current@freebsd.org Subject: Re: i386 wierd one...... kernel stack frame pointer corruption(?) In-reply-to: Your message of "Thu, 07 Oct 1999 11:27:56 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Oct 1999 12:01:42 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One thing that is possible is that it's a very deep callstack... It's > during probing and it may have called completion on a completing command > while down at the bottom of the stack starting another command. If you run > out of kernel stack, don't you get some other kind of fault? That kinda depends on how hard you hit the bottom of the stack. I'd typically expect a double fault though. Note that SMP systems are much better behaved in this case than the old UP kernel stack setup. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 12:12:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 5C92214C1A for ; Thu, 7 Oct 1999 12:12:15 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id MAA20498; Thu, 7 Oct 1999 12:12:09 -0700 (PDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id MAA26408; Thu, 7 Oct 1999 12:11:53 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id MAA05029; Thu, 7 Oct 1999 12:11:44 -0700 (PDT) Message-Id: <199910071911.MAA05029@mina.sr.hp.com> To: freebsd-current@FreeBSD.ORG Cc: The Hermit Hacker Subject: Re: modules: how to use? Reply-To: Darryl Okahata In-reply-to: Your message of "Thu, 07 Oct 1999 03:00:52 -0300." Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Thu, 07 Oct 1999 12:11:44 -0700 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > Figuring one of the things a friend of mine raves about Linux for is their > kld's, I'd start playing with ours... [ Going off on a slight tangent ... ] You may have gone beyond this, but a good introduction to klds is an article called, "Attacking FreeBSD with Kernel Modules", at: http://thc.pimmel.com Click on "Articles", followed by "Attacking FreeBSD with Kernel Modules (example modules)". I'm not sure how up-to-date it is, though. Strange, but true. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 12:19: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat203.183.mpoweredpc.net [142.177.203.183]) by hub.freebsd.org (Postfix) with ESMTP id B929615336 for ; Thu, 7 Oct 1999 12:18:59 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id QAA62825; Thu, 7 Oct 1999 16:18:10 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 7 Oct 1999 16:18:10 -0300 (ADT) From: The Hermit Hacker To: "Daniel C. Sobral" Cc: freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? In-Reply-To: <37FC6A10.95E59914@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 Oct 1999, Daniel C. Sobral wrote: > The Hermit Hacker wrote: > > > > Figuring one of the things a friend of mine raves about Linux for is their > > kld's, I'd start playing with ours... > > > > Looking in /modules, I saw 'procfs', so, cool, a place to start...remove > > "options PROCFS" from kernel config, rebuild, install and reboot ... > > > > crashes... > > > > so, I figure that I somehow have to tell the kernel to load that module? > > fs modules are automagically loaded. Alas, that's the general > direction for a lot of modules. The network ones, for instance. No > more need to put in the device lines in the kernel configuration > file, it will be automagically loaded by ifconfig. I don't know if > this is working already or not, though. > > Now, how to tell the kernel to load modules. Well, some stuff you > can set with rc.conf(5). Other stuff you may load explicitly through > kldload. And, finally, you don't need to have the _kernel_ load it. > You may edit loader.conf(5) to have it loaded at the same time the > kernel is loaded by, well, the loader(8). :-) (the bootstrap loader) > > > checked the kld man page, and nothing in there appears to be > > appropriate...and just looked at my /usr/src/etc/rc* files to see if maybe > > it was something I was supposed to configure in there, but nothing appears > > to be in tehre either... > > > > Help? > > Wild shot: are your kernel & world in sync? For isntance, you made a > new kernel when you edited your kernel configuration file to remove > the option line, right? If you just happened to have newer sources, > the new kernel might have become incompatible with the older > modules, which are not made automatically (except during world). cd > /sys/modules; make all install. This one is probably it *sigh* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 12:19:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat203.183.mpoweredpc.net [142.177.203.183]) by hub.freebsd.org (Postfix) with ESMTP id 56D7115326 for ; Thu, 7 Oct 1999 12:19:03 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id QAA62777; Thu, 7 Oct 1999 16:17:01 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 7 Oct 1999 16:17:00 -0300 (ADT) From: The Hermit Hacker To: "Daniel O'Connor" Cc: Greg Lehey , freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 Oct 1999, Daniel O'Connor wrote: > > On 07-Oct-99 Greg Lehey wrote: > > Well, the standard way to load a kld is with kldload(1) or kldload(2). > > I don't know if procfs works properly like this, though. > > Well I would assume (aha) that when mount cannot find procfs in the list of > FS's the kernel knows about it would try and load it just like all the others.. okay, I had started to write down the whole error message last night, until I saw that the process that died dealt with procfs and figured it was that I took the option out...I'll redo it tonight when I get home and write it all down and submit it... Just to confirm, *technically*, I should just have to comment out the options PROCFS in my kernel config, rebuild and reboot and since procfs isn't in the kernel, it will look for it as a module? Will report later tonight on what happens... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 13:11:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 232E614BD0 for ; Thu, 7 Oct 1999 13:11:04 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA89971 for ; Thu, 7 Oct 1999 22:11:02 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910072011.WAA89971@gratis.grondar.za> To: current@freebsd.org Subject: HEADS UP!! New telnet on the block Date: Thu, 07 Oct 1999 22:11:01 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all I have just committed Nick Sayer's SRA'ed telnet; this means that if you have the secure dist, and maybe Kerberos, you will have a telnet that attempts to do some encryption apart from the Kerberos stuff. Initial reports are that this encryption is weak, but it may be better than nothing. Investigate it carefully before committing your arms-smuggling business to its security :-). M To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 14: 7:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from web2101.mail.yahoo.com (web2101.mail.yahoo.com [128.11.68.245]) by hub.freebsd.org (Postfix) with SMTP id CCC3A14CFF for ; Thu, 7 Oct 1999 14:07:38 -0700 (PDT) (envelope-from valsho@yahoo.com) Message-ID: <19991007210520.846.rocketmail@web2101.mail.yahoo.com> Received: from [147.226.112.101] by web2101.mail.yahoo.com; Thu, 07 Oct 1999 14:05:20 PDT Date: Thu, 7 Oct 1999 14:05:20 -0700 (PDT) From: "Valentin S. Chopov" Subject: new PnP code and pcm and kernel userconfig To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The sound card is: ... unknown0: <4232> on isa0 pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 unknown1: at port 0x200-0x207 on isa0 unknown2: at port 0x330-0x331 irq 9 on isa0 ... Everything looks fine but in my case the CS4232 is a buggy and it can't work in duplex mode and I have to change drq0=drq1=1 Now I can't do this from the kernel userconfig (boot -c ) - pnp configuration is missing. Any ideas? Thanks, Val __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 15:12: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 86253153DE for ; Thu, 7 Oct 1999 15:11:59 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA98087 for ; Thu, 7 Oct 1999 15:11:01 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA76089 for freebsd-current@FreeBSD.ORG; Thu, 7 Oct 1999 15:11:00 -0700 (PDT) (envelope-from obrien) Date: Thu, 7 Oct 1999 15:11:00 -0700 From: "David O'Brien" To: freebsd-current@FreeBSD.ORG Subject: Re: {a}sync updates (was Re: make install trick) Message-ID: <19991007151100.C68920@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <99Oct6.103524est.40351@border.alcanet.com.au> <99Oct6.145359est.40347@border.alcanet.com.au> <19991006154419.O20768@futuresouth.com> <99Oct7.085536est.40332@border.alcanet.com.au> <19991006181542.S20768@futuresouth.com> <99Oct7.115403est.40324@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <99Oct7.115403est.40324@border.alcanet.com.au> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There should be fairly few writes to the root partition, so having An opionion. I use the HP workstation model where my / is 1800M. I have no use for /var and /usr and find them simply stupid in today's world. (except for ISP's where there is cause for a septerate /var). Lets stick to facts. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 15:13:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 14A051580B for ; Thu, 7 Oct 1999 15:13:13 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA98107; Thu, 7 Oct 1999 15:13:12 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA76486; Thu, 7 Oct 1999 15:13:12 -0700 (PDT) (envelope-from obrien) Date: Thu, 7 Oct 1999 15:13:12 -0700 From: "David O'Brien" To: Peter Jeremy Cc: freebsd-current@FreeBSD.ORG Subject: Re: {a}sync updates (was Re: make install trick) Message-ID: <19991007151312.D68920@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <99Oct6.103524est.40351@border.alcanet.com.au> <99Oct6.145359est.40347@border.alcanet.com.au> <19991006154419.O20768@futuresouth.com> <99Oct7.085536est.40332@border.alcanet.com.au> <19991006181542.S20768@futuresouth.com> <99Oct7.115403est.40324@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <99Oct7.115403est.40324@border.alcanet.com.au> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >mount(8): > > sync All I/O to the file system should be done synchronously. > > How detailed should the man page be? If it stated "all file data will > be written synchronously, but inodes where the only update is atime > and free block bitmaps are written asynchronously", would that be any > clearer to a user who didn't have a detailed understanding of UFS? Yes. I know the difference between sync/async and data/metadata. I haven't however, done a though wall-thru of the UFS code. If the manpage says "All I/O", then the system should do *ALL* I/O sync. This isn't Linux. Guess I go off editing mount(8) again. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 15:13:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 255D215444 for ; Thu, 7 Oct 1999 15:13:49 -0700 (PDT) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1001) id 6E1D0119; Fri, 8 Oct 1999 00:13:45 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by shadowmere.student.utwente.nl (Postfix) with ESMTP id 6A727110 for ; Fri, 8 Oct 1999 00:13:45 +0200 (CEST) Date: Fri, 8 Oct 1999 00:13:45 +0200 (CEST) From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: Re: shell script trouble In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 Oct 1999, Pascal Hofstee wrote: > The scripts I am having problems with are: > /usr/local/etc/rc.d/rc5des.sh > /usr/local/etc/postfix/postfix-script > > Both of these scripts still are as they were installed by their respective > ports. And I know both have worked just fine for months without problems. The rc5des breakage is in the fact that it seems to attempt to start the rc5des client but that never seems to get launched ... running rc5des manually does work .. so the rc5des bianry itself isn't broken. The postfix breakage is in the fact that no matter What command i try ... the postfix-script (which is called by postfix itself) always says the following: su-2.03# /usr/local/sbin/postfix reload postfix-script: fatal: the Postfix mail system is not running I Know the mail system IS running on Postfix though: su-2.03# ps -aux | egrep postfix postfix 205 0.0 0.7 928 612 ?? I 5:01PM 0:00.26 qmgr -l -t fifo postfix 1585 0.0 0.5 872 508 ?? I 11:39PM 0:00.02 pickup -l -t fif postfix 1809 0.0 0.8 952 724 ?? I 12:11AM 0:00.02 smtpd -n smtp -t postfix 1810 0.0 0.7 928 680 ?? I 12:11AM 0:00.02 cleanup -t unix postfix 1811 0.0 0.6 900 584 ?? I 12:11AM 0:00.02 trivial-rewrite postfix 1812 0.0 0.8 956 712 ?? I 12:11AM 0:00.02 local -t unix -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 15:15: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 8749F1585B; Thu, 7 Oct 1999 15:15:04 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Thu, 7 Oct 1999 15:15:03 -0700 From: "David Schwartz" To: , Subject: RE: {a}sync updates (was Re: make install trick) Date: Thu, 7 Oct 1999 15:15:03 -0700 Message-ID: <000001bf1111$674d5220$021d85d1@youwant.to> 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.2377.0 In-Reply-To: <19991007151100.C68920@dragon.nuxi.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There should be fairly few writes to the root partition, so having > > An opionion. I use the HP workstation model where my / is 1800M. I have > no use for /var and /usr and find them simply stupid in today's world. > (except for ISP's where there is cause for a septerate /var). > > Lets stick to facts. > > -- > -- David (obrien@NUXI.com) You are not disagreeing with him, David. You are just talking about another scenario other than the one under discussion. He was talking about the case where root is small. This whole discussion was about how softupdates behaves in the subcase of small root partitions. If you have a 1.8Gb root partition that also includes /var and /usr, this whole discussion is irrelevant. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 15:22:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 009DB14CF7 for ; Thu, 7 Oct 1999 15:22:22 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA98181; Thu, 7 Oct 1999 15:21:32 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA91680; Thu, 7 Oct 1999 15:21:32 -0700 (PDT) (envelope-from obrien) Date: Thu, 7 Oct 1999 15:21:32 -0700 From: "David O'Brien" To: Brad Knowles Cc: freebsd-current@FreeBSD.ORG Subject: Re: make install trick Message-ID: <19991007152132.F68920@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It was my understanding that it was standard recommended practice > practice pretty much across the board to create the following > separate filesystems: > > / > /tmp (perhaps an mfs, perhaps softupdates, or whatever) > /usr > /var > /var/tmp > /home (or wherever you're going to store user directories) > And that most people also then created a separate filesystem for > /usr/local or /opt, or wherever they're going to store the additional You are entering religion. I despise, HIGHLY DESPISE, all the partitions. I don't care for the fragmentation and PITA when upgrading it leads to. HP and SGI workstations have a single huge /. Why do you need /usr seperate from / when you aren't diskless (or /usr'less)? Look at the historic reasons for this division and see if it still makes sense to you today. (and before someone misreads this, yes, my /home is a seperate partition and my /tmp is MFS) -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 15:37:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 5746815114 for ; Thu, 7 Oct 1999 15:37:47 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 5768D9B20; Thu, 7 Oct 1999 18:35:25 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 48D70BA1C; Thu, 7 Oct 1999 18:35:25 -0400 (EDT) Date: Thu, 7 Oct 1999 18:35:25 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Pascal Hofstee Cc: freebsd-current@freebsd.org Subject: Re: shell script trouble In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Oct 1999, Pascal Hofstee wrote: > su-2.03# /usr/local/sbin/postfix reload > postfix-script: fatal: the Postfix mail system is not running > > I Know the mail system IS running on Postfix though: > su-2.03# ps -aux | egrep postfix > postfix 205 0.0 0.7 928 612 ?? I 5:01PM 0:00.26 qmgr -l -t > fifo > postfix 1585 0.0 0.5 872 508 ?? I 11:39PM 0:00.02 pickup -l > -t fif > postfix 1809 0.0 0.8 952 724 ?? I 12:11AM 0:00.02 smtpd -n > smtp -t > postfix 1810 0.0 0.7 928 680 ?? I 12:11AM 0:00.02 cleanup -t > unix > postfix 1811 0.0 0.6 900 584 ?? I 12:11AM 0:00.02 > trivial-rewrite > postfix 1812 0.0 0.8 956 712 ?? I 12:11AM 0:00.02 local -t > unix > > There are some of Postfix's daemons running above, but you seem to be missing: root 286 0.0 0.8 872 220 ?? Is 29Sep99 0:10.23 /usr/local/libexec/postfix/master Which is the actual process that listens on port 25. Since 'postfix reload' cannot communicate with master, it says that postfix is not running. Next step, find out where your master is? ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 15:59:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 1971814A2B for ; Thu, 7 Oct 1999 15:59:14 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id QAA26470; Thu, 7 Oct 1999 16:47:24 -0600 (MDT) Date: Thu, 7 Oct 1999 16:47:24 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199910072247.QAA26470@narnia.plutotech.com> To: Bernd Walter Cc: current@FreeBSD.org Subject: Re: ahc panics and (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. X-Newsgroups: pluto.freebsd.current In-Reply-To: <19991007004510.A393@cicely8.cicely.de> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19991007004510.A393@cicely8.cicely.de> you wrote: > > I'm getting this with a recent current (6. october): > > (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. > (da2:ahc2:0:2:0): Have seen Data Phase. Length = 0. NumSGs = 1. Someone is telling us to transmit data, but has not provided a buffer with any data in it. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 16: 6:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 8F777153DE for ; Thu, 7 Oct 1999 16:06:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA02098; Thu, 7 Oct 1999 15:56:27 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910072256.PAA02098@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Justin T. Gibbs" Cc: Bernd Walter , current@FreeBSD.org Subject: Re: ahc panics and (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. In-reply-to: Your message of "Thu, 07 Oct 1999 16:47:24 MDT." <199910072247.QAA26470@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Oct 1999 15:56:27 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <19991007004510.A393@cicely8.cicely.de> you wrote: > > > > I'm getting this with a recent current (6. october): > > > > (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. > > (da2:ahc2:0:2:0): Have seen Data Phase. Length = 0. NumSGs = 1. > > Someone is telling us to transmit data, but has not provided a > buffer with any data in it. This is probably the breakage that phk introduced; it's been fixed for days. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 16:44: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 8894314E03; Thu, 7 Oct 1999 16:43:56 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40352>; Fri, 8 Oct 1999 09:40:07 +1000 Content-return: prohibited Date: Fri, 8 Oct 1999 09:43:39 +1000 From: Peter Jeremy Subject: Re: {a}sync updates (was Re: make install trick) In-reply-to: <19991007151312.D68920@dragon.nuxi.com> To: David O'Brien Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct8.094007est.40352@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <99Oct6.103524est.40351@border.alcanet.com.au> <99Oct6.145359est.40347@border.alcanet.com.au> <19991006154419.O20768@futuresouth.com> <99Oct7.085536est.40332@border.alcanet.com.au> <19991006181542.S20768@futuresouth.com> <99Oct7.115403est.40324@border.alcanet.com.au> <19991007151312.D68920@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-08 08:13:12 +1000, David O'Brien wrote: >> >mount(8): >> > sync All I/O to the file system should be done synchronously. >> >> How detailed should the man page be? If it stated "all file data will >> be written synchronously, but inodes where the only update is atime >> and free block bitmaps are written asynchronously", would that be any >> clearer to a user who didn't have a detailed understanding of UFS? > >Yes. I know the difference between sync/async and data/metadata. My point was that the average user probably doesn't. I agree that the current description glosses over the difference (and probably shouldn't). We need to strike a balance between providing enough detail for the knowledgeable user (who wants to know exactly what a sync mount does to different types of writes within the FS) and the novice user (who doesn't understand the details of UFS and is more likely to become confused). IMHO, `sync' does behave in a reasonable manner. I'm not sure how I'd go about explaining its behaviour to someone who didn't understand the UFS though. > Guess I go off editing mount(8) again. I was going to suggest that the relationship between the sync option in mount(2,8) and O_FSYNC in open(2) be noted. Only problem is that O_FSYNC isn't documented :-(. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 17:10:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id E02C914D56 for ; Thu, 7 Oct 1999 17:10:29 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id CAA29427; Fri, 8 Oct 1999 02:04:53 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id CAA99069; Fri, 8 Oct 1999 02:09:24 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id CAA02499; Fri, 8 Oct 1999 02:09:33 +0200 (CEST) (envelope-from ticso) Date: Fri, 8 Oct 1999 02:09:33 +0200 From: Bernd Walter To: Mike Smith Cc: "Justin T. Gibbs" , Bernd Walter , current@FreeBSD.org Subject: Re: ahc panics and (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. Message-ID: <19991008020933.A2487@cicely8.cicely.de> References: <199910072247.QAA26470@narnia.plutotech.com> <199910072256.PAA02098@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199910072256.PAA02098@dingo.cdrom.com>; from Mike Smith on Thu, Oct 07, 1999 at 03:56:27PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 07, 1999 at 03:56:27PM -0700, Mike Smith wrote: > > In article <19991007004510.A393@cicely8.cicely.de> you wrote: > > > > > > I'm getting this with a recent current (6. october): > > > > > > (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. > > > (da2:ahc2:0:2:0): Have seen Data Phase. Length = 0. NumSGs = 1. > > > > Someone is telling us to transmit data, but has not provided a > > buffer with any data in it. > > This is probably the breakage that phk introduced; it's been fixed for > days. That's why I updated - but the panic happened after that. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 17:20:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id F0EF01541B for ; Thu, 7 Oct 1999 17:20:03 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id JAA10541; Fri, 8 Oct 1999 09:49:51 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [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: Fri, 08 Oct 1999 09:49:51 +0930 (CST) From: "Daniel O'Connor" To: The Hermit Hacker Subject: Re: modules: how to use? Cc: freebsd-current@FreeBSD.ORG, Greg Lehey Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Oct-99 The Hermit Hacker wrote: > Just to confirm, *technically*, I should just have to comment out the > options PROCFS in my kernel config, rebuild and reboot and since procfs > isn't in the kernel, it will look for it as a module? Yes.. That should work fine.. In fact you can have all your FS's as modules except what / is.. --- 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-current" in the body of the message From owner-freebsd-current Thu Oct 7 17:25:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 0A5E1153DE for ; Thu, 7 Oct 1999 17:25:47 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA02539; Thu, 7 Oct 1999 17:17:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910080017.RAA02539@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? In-reply-to: Your message of "Fri, 08 Oct 1999 09:49:51 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Oct 1999 17:17:38 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 07-Oct-99 The Hermit Hacker wrote: > > Just to confirm, *technically*, I should just have to comment out the > > options PROCFS in my kernel config, rebuild and reboot and since procfs > > isn't in the kernel, it will look for it as a module? > > Yes.. That should work fine.. > In fact you can have all your FS's as modules except what / is.. You can have / too, as long as you load it with the loader. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 17:32:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 5A15514BB7 for ; Thu, 7 Oct 1999 17:32:37 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA10840; Fri, 8 Oct 1999 10:02:35 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [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: <199910080017.RAA02539@dingo.cdrom.com> Date: Fri, 08 Oct 1999 10:02:34 +0930 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: modules: how to use? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Oct-99 Mike Smith wrote: > > Yes.. That should work fine.. > > In fact you can have all your FS's as modules except what / is.. > You can have / too, as long as you load it with the loader. 8) And providing / is UFS because thats all the loader understands (?) --- 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-current" in the body of the message From owner-freebsd-current Thu Oct 7 17:36:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id B127314BB7 for ; Thu, 7 Oct 1999 17:36:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA02626; Thu, 7 Oct 1999 17:27:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910080027.RAA02626@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? In-reply-to: Your message of "Fri, 08 Oct 1999 10:02:34 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Oct 1999 17:27:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 08-Oct-99 Mike Smith wrote: > > > Yes.. That should work fine.. > > > In fact you can have all your FS's as modules except what / is.. > > You can have / too, as long as you load it with the loader. 8) > > And providing / is UFS because thats all the loader understands (?) No, it could be a DOS filesystem too. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 18: 9:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 9F7E614C9A for ; Thu, 7 Oct 1999 18:09:17 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id TAA00370 for ; Thu, 7 Oct 1999 19:09:20 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199910080109.TAA00370@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.org Subject: How do I get a PCCARD modem to work? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Oct 1999 19:09:20 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like both nsio and sio have PCCARD support disabled at the moment. Is there any other way I can get the system to recognize my modem? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 20:21: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id CD9D814A29; Thu, 7 Oct 1999 20:20:57 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper (kc-rmt03.keycomp.net [207.44.1.5]) by www.keycomp.net (8.8.5/SCO5) with SMTP id XAA21526; Thu, 7 Oct 1999 23:26:45 -0400 (EDT) Message-ID: <00db01bf113c$01933dc0$01010101@bopper> From: "Bill A. K." To: , "FreeBSD Questions" Subject: My status with upgrade from 3.2 to 4.0 Date: Thu, 7 Oct 1999 23:19: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 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just wanted to let you know that I was finally able to upgrade to 4.0-current from 3.2-release. I cvsuped the 4.0 code, i compiled the 4.0 config command, i compiled the 4.0 kernel, installed the kernel, rebooted, and build and installed the world and it worked. Then i just made my custom kernel, and did some other stuff. I have a few questions though, my Voodoo Banshee makes the console display screw up wheneven i go into X (my version is 3.3.5), and then exit X. (BTW this also did this on 3.2-release) Anybody else see this? Another thing was syslogd was looking for /var/log/security and can't find it, how can i fix this? Thanks Bill billieakay@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 21:52:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from justice.zips.net (justice.zips.net [207.234.219.219]) by hub.freebsd.org (Postfix) with ESMTP id 0ACCD14BDE for ; Thu, 7 Oct 1999 21:52:37 -0700 (PDT) (envelope-from zips@zips.net) Received: from localhost (zips@localhost) by justice.zips.net (8.9.3/8.9.3) with ESMTP id AAA16308 for ; Fri, 8 Oct 1999 00:57:28 -0400 (EDT) (envelope-from zips@zips.net) Date: Fri, 8 Oct 1999 00:57:28 -0400 (EDT) From: Hector Colmenares To: freebsd-current@FreeBSD.ORG Subject: Email Acc. Only ! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What will be the best way to create an email acc. only ? without have to create a shell acc. ? Like virtual table or something like that ? Any Idea ? Thank You. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 21:56: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id BC88914F10 for ; Thu, 7 Oct 1999 21:56:01 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id OAA18077; Fri, 8 Oct 1999 14:24:13 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [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: Fri, 08 Oct 1999 14:24:13 +0930 (CST) From: "Daniel O'Connor" To: Hector Colmenares Subject: RE: Email Acc. Only ! Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Oct-99 Hector Colmenares wrote: > What will be the best way to create an email acc. only ? > without have to create a shell acc. ? Like virtual table or > something like that ? Use cyrus IMAPD (which does POP3 too). Its in the ports collection. --- 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-current" in the body of the message From owner-freebsd-current Thu Oct 7 22:47: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id 60D4A14A2A; Thu, 7 Oct 1999 22:46:58 -0700 (PDT) (envelope-from debtfreea@boom.com) Received: from [212.240.82.34] (helo=lachesis.fta.org.uk) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 11ZSqC-000LMZ-0C; Fri, 8 Oct 1999 05:45:16 +0000 Received: from smtp.boom.com ([152.204.92.66]) by lachesis.fta.org.uk (Netscape Messaging Server 3.5) with SMTP id 262; Fri, 8 Oct 1999 06:51:44 +0100 Date: Fri, 8 Oct 1999 01:50:51 From: Subject: Are you in Debt over your Head? Message-ID: <19991008055123856.AAA987.262@smtp.boom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Get Out Of Debt Now!!!!! ARE YOU DROWNING IN DEBT? ARE YOU RECEIVING HARASSING PHONE CALLS? Let our staff help you to eliminate your debts. WITH OUR PROGRAMS YOU WILL*: * Pay off all unsecured debt in 18-30 months * Cut your current debt payments by up to 50% * Cut Credit Card Balances 30-60% * Build savings each and every month * Stop creditor harassment if that is currently a problem. http://3626046468/nt/debtreduction/index2.html Click Here ***************************************************************** To be removed from our mailing list, please click enter your email address at the webpage with remove in the name field.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 22:58:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id EFF53153C4; Thu, 7 Oct 1999 22:58:24 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id WAA47842; Thu, 7 Oct 1999 22:57:47 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199910080557.WAA47842@gndrsh.dnsmgr.net> Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... In-Reply-To: <199910071709.KAA95541@apollo.backplane.com> from Matthew Dillon at "Oct 7, 1999 10:09:23 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 7 Oct 1999 22:57:47 -0700 (PDT) Cc: ady@warpnet.ro (Adrian Penisoara), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Hi again, > : > : Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault > :error (strange, it didn't look like a normal panic screen, just the > :message and the content of three registers, then the syncing disks > :message). It seems that I might be wrong about hardware not being the > :problem. > : > : I've changed the motherboard, CPU, memory and the video card and I'm > :waiting to see how much it's going to stay up (I have 1day 1hour uptime so > :far)... > : > : Thanks, > : Ady (@warpnet.ro) > > One thing I do on all 'server' class machines that I buy (and this is > also something that BEST instituted as policy in 1998) is to only buy > motherboards with ECC support and only buy ECC memory to go along with > that support. If you are using a non-ECC motherboard or non-ECC memory > I would heartily recommend that you adopt the same policy. Not that your > problem is necessarily memory related, but I've found that memory-related > problems account for at least 80% of the 'difficult to locate' hardware > problems that normally occur with PC technology. And to add support to this, AAI, the oldest vendor of FreeBSD specific systems, implemented a similiar policy on all system sold sometime in 1992. But at that time ECC was not avaliable so it was ``parity memory is required, and the chipset must support it''. As soon as ECC chipsets hit the market the policy was changed to refect this. We also require all memory that we purchase be backed by a no-fuss lifetime warranty, which we pass on to the end user. I strongly recommend that any one running Unix on a PC do the same, it will save you in the long run. Since implementing the policies we have seen a near 0 memory related problem after burnin with our systems. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 23:31:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4545C14E40 for ; Thu, 7 Oct 1999 23:31:41 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA27151; Fri, 8 Oct 1999 08:31:16 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910080631.IAA27151@freebsd.dk> Subject: Re: How do I get a PCCARD modem to work? In-Reply-To: <199910080109.TAA00370@caspian.plutotech.com> from "Justin T. Gibbs" at "Oct 7, 1999 07:09:20 pm" To: gibbs@caspian.plutotech.com (Justin T. Gibbs) Date: Fri, 8 Oct 1999 08:31:15 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Justin T. Gibbs wrote: > It looks like both nsio and sio have PCCARD support disabled at the > moment. Is there any other way I can get the system to recognize my > modem? Fix the broken sio, it might be KNF and all but it doesn't work... -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 7 23:56:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-159.birch.net [216.212.1.159]) by hub.freebsd.org (Postfix) with ESMTP id 3FD9414F83 for ; Thu, 7 Oct 1999 23:56:16 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id BAA53957; Fri, 8 Oct 1999 01:56:02 -0500 (CDT) From: Jim Bryant Message-Id: <199910080656.BAA53957@argus.tfs.net> Subject: Re: Email Acc. Only ! In-Reply-To: from Hector Colmenares at "Oct 8, 99 00:57:28 am" To: zips@zips.net (Hector Colmenares) Date: Fri, 8 Oct 1999 01:56:00 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > What will be the best way to create an email acc. only ? > without have to create a shell acc. ? Like virtual table or > something like that ? > > Any Idea ? > > Thank You. disable all but pop in /etc/inetd.conf then `killall -1 inetd` set all use shells to /nonexistant using vipw. take a unix class. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 0:28:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.rz.uni-karlsruhe.de (nz40.rz.uni-karlsruhe.de [129.13.197.4]) by hub.freebsd.org (Postfix) with ESMTP id D738A153FB for ; Fri, 8 Oct 1999 00:28:43 -0700 (PDT) (envelope-from un1i@rz.uni-karlsruhe.de) Received: from rz114s1.rz.uni-karlsruhe.de (exim@rz114s1-197.rz.uni-karlsruhe.de [129.13.197.190]) by mailgate.rz.uni-karlsruhe.de with esmtp (Exim 3.02 #2) id 11ZUQM-00054t-00; Fri, 08 Oct 1999 09:26:42 +0200 Received: from un1i by rz114s1.rz.uni-karlsruhe.de with local (Exim 2.12 #1) id 11ZUQL-0001VL-00; Fri, 8 Oct 1999 09:26:41 +0200 Message-ID: <19991008092640.A2499@rz.uni-karlsruhe.de> Date: Fri, 8 Oct 1999 09:26:40 +0200 From: Philipp Mergenthaler To: marcel@scc.nl Cc: freebsd-current@freebsd.org Subject: Make world broken in doscmd; patch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, the change in src/sys/i386/include/ucontext.h (in struct __mcontext), where "struct trapframe mc_tf;" was replaced by it's members broke doscmd. (The relevant files are $FreeBSD: src/sys/i386/include/ucontext.h,v 1.3 1999/10/07 12:40:34 marcel Exp $ $FreeBSD: src/usr.bin/doscmd/signal.c,v 1.5 1999/09/29 20:09:18 marcel Exp $ $FreeBSD: src/usr.bin/doscmd/trap.c,v 1.6 1999/09/29 20:09:19 marcel Exp $ ) The following patch should fix it. Bye, Philipp -- http://www.uni-karlsruhe.de/~un1i/ diff -u doscmd.orig/signal.c doscmd/signal.c --- doscmd.orig/signal.c Thu Sep 30 21:26:37 1999 +++ doscmd/signal.c Fri Oct 8 08:58:32 1999 @@ -66,7 +66,7 @@ static void generichandler(struct sigframe sf) { - if (sf.sf_uc.uc_mcontext.mc_tf.tf_eflags & PSL_VM) { + if (sf.sf_uc.uc_mcontext.mc_eflags & PSL_VM) { saved_sigframe = &sf; saved_regcontext = (regcontext_t *)&(sf.sf_uc.uc_mcontext); saved_valid = 1; diff -u doscmd.orig/trap.c doscmd/trap.c --- doscmd.orig/trap.c Thu Sep 30 21:26:37 1999 +++ doscmd/trap.c Fri Oct 8 08:59:11 1999 @@ -296,8 +296,8 @@ if ((int)sf->sf_siginfo != 0) { fatal("SIGBUS code %d, trapno: %d, err: %d\n", - (int)sf->sf_siginfo, sf->sf_uc.uc_mcontext.mc_tf.tf_trapno, - sf->sf_uc.uc_mcontext.mc_tf.tf_err); + (int)sf->sf_siginfo, sf->sf_uc.uc_mcontext.mc_trapno, + sf->sf_uc.uc_mcontext.mc_err); } addr = (u_char *)MAKEPTR(R_CS, R_IP); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 1: 0: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 4A89414F27 for ; Fri, 8 Oct 1999 01:00:05 -0700 (PDT) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1001) id 8A11878; Fri, 8 Oct 1999 08:57:27 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by shadowmere.student.utwente.nl (Postfix) with ESMTP id 57E286F; Fri, 8 Oct 1999 08:57:27 +0200 (CEST) Date: Fri, 8 Oct 1999 08:57:27 +0200 (CEST) From: Pascal Hofstee To: "Chris D. Faulhaber" Cc: freebsd-current@freebsd.org Subject: Re: shell script trouble In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 Oct 1999, Chris D. Faulhaber wrote: > There are some of Postfix's daemons running above, but you seem to be > missing: > > root 286 0.0 0.8 872 220 ?? Is 29Sep99 0:10.23 > /usr/local/libexec/postfix/master > > Which is the actual process that listens on port 25. Since 'postfix > reload' cannot communicate with master, it says that postfix is not > running. Next step, find out where your master is? master is located at: /usr/local/libexec/postfix/master -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 2:12:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id B88FC14F7D; Fri, 8 Oct 1999 02:12:18 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Oct 1999 10:12:17 +0100 (BST) Date: Fri, 8 Oct 1999 10:12:17 +0100 From: David Malone To: Matthew Dillon Cc: Adrian Penisoara , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... Message-ID: <19991008101217.A24152@gosset.maths.tcd.ie> References: <199910071709.KAA95541@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199910071709.KAA95541@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote: > Intel's ECC implementation is not perfect (1), but it's good enough to > catch these sorts of problems. Just as an interesting side note, we had a motherboard which supported ECC ram and had ECC ram in it and which was crashing. Eventually we discovered that every 8th byte in page aligned 4KB chunks was becomming corrupted. We replaced the ram and saw no improvement, and then got a replacement motherboard. As far as I could see the only significant difference between the new and old motherboard was the addition of a heat sink to the memory controler chip. The machine is now perfectly happy. So it seems that ECC isn't enough if your memory controler is too hot! David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 2:35:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 2766314BD2; Fri, 8 Oct 1999 02:35:34 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id CAA07195; Fri, 8 Oct 1999 02:34:25 -0700 (PDT) Message-Id: <199910080934.CAA07195@implode.root.com> To: David Malone Cc: Matthew Dillon , Adrian Penisoara , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... In-reply-to: Your message of "Fri, 08 Oct 1999 10:12:17 BST." <19991008101217.A24152@gosset.maths.tcd.ie> From: David Greenman Reply-To: dg@root.com Date: Fri, 08 Oct 1999 02:34:25 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote: > >> Intel's ECC implementation is not perfect (1), but it's good enough to >> catch these sorts of problems. > >Just as an interesting side note, we had a motherboard which >supported ECC ram and had ECC ram in it and which was crashing. >Eventually we discovered that every 8th byte in page aligned 4KB >chunks was becomming corrupted. > >We replaced the ram and saw no improvement, and then got a replacement >motherboard. As far as I could see the only significant difference >between the new and old motherboard was the addition of a heat sink >to the memory controler chip. The machine is now perfectly happy. > >So it seems that ECC isn't enough if your memory controler is too >hot! ECC doesn't protect against certain types of motherboard address line errors (since although the ECC is correct, the selected address is wrong, so thus the data is wrong). There's parity protection on parts of the CPU address bus, but I don't believe there is any protection between the memory controller and the DIMMs for this type of problem. A handful of metal filings is also known to cause problems when it is dispersed properly. :-) -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 3:38:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 8C4DA14CAF for ; Fri, 8 Oct 1999 03:38:11 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p13-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.142]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id TAA08588; Fri, 8 Oct 1999 19:38:06 +0900 (JST) Message-ID: <37FDC230.8E169A02@newsguy.com> Date: Fri, 08 Oct 1999 19:06:40 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > > Just to confirm, *technically*, I should just have to comment out the > options PROCFS in my kernel config, rebuild and reboot and since procfs > isn't in the kernel, it will look for it as a module? As long as the module is up to date. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 4:36:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id C403414E91 for ; Fri, 8 Oct 1999 04:36:31 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id NAA31858 for current@FreeBSD.org; Fri, 8 Oct 1999 13:35:53 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Fri, 08 Oct 1999 13:35:33 +0200 From: Marcel Moolenaar Message-ID: <37FDD705.FCCD2A0F@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19991008092640.A2499@rz.uni-karlsruhe.de> Subject: Re: Make world broken in doscmd; patch Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Philipp Mergenthaler wrote: > the change in src/sys/i386/include/ucontext.h (in struct __mcontext), > where "struct trapframe mc_tf;" was replaced by it's members > broke doscmd. Fixed. Thanks, -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 5:28:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat203.183.mpoweredpc.net [142.177.203.183]) by hub.freebsd.org (Postfix) with ESMTP id 4CD6C14D05 for ; Fri, 8 Oct 1999 05:28:05 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id JAA57635; Fri, 8 Oct 1999 09:28:17 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Oct 1999 09:28:17 -0300 (ADT) From: The Hermit Hacker To: "Daniel C. Sobral" Cc: freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? In-Reply-To: <37FDC230.8E169A02@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Worked like a charm, thanks...have fxp0 and procfs removed from my kernel config and using modules... On Fri, 8 Oct 1999, Daniel C. Sobral wrote: > The Hermit Hacker wrote: > > > > Just to confirm, *technically*, I should just have to comment out the > > options PROCFS in my kernel config, rebuild and reboot and since procfs > > isn't in the kernel, it will look for it as a module? > > As long as the module is up to date. > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "I always feel generous when I'm in the inner circle of a > conspiracy to subvert the world order and, with a small group of > allies, just defeated an alien invasion. Maybe I should value myself > a little more?" > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 5:51:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from out1.mx.skynet.be (out1.mx.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 8F82014C0B; Fri, 8 Oct 1999 05:51:35 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out1.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id OAA17267; Fri, 8 Oct 1999 14:51:36 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id OAA09291; Fri, 8 Oct 1999 14:51:33 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <19991007152132.F68920@dragon.nuxi.com> References: <19991007152132.F68920@dragon.nuxi.com> Date: Fri, 8 Oct 1999 13:42:44 +0200 To: obrien@FreeBSD.ORG From: Brad Knowles Subject: Re: make install trick Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:21 PM -0700 1999/10/7, David O'Brien wrote: > HP and SGI workstations have a single huge /. Why do you > need /usr seperate from / when you aren't diskless (or /usr'less)? If you've done your job right, it can be mounted read-only. This makes it harder for someone to break into the machine and obtain root access, because now they have to be root to unmount /usr and remount it read-write, so that they can put their trojan script on there that they're hoping you'll execute. I've admin'ed my share of HP and SGI machines in the past, and I've never used the standard partition configuration, just like I don't use the standard partition configuration for Solaris. IMO, none of them are right, and they're wrong for the wrong reasons. You're right that this is a somewhat religious issue, however, if you're going to run a huge root filesystem, then you are more likely to get what you deserve if /usr or one of the other directories on the root filesystem get trashed or fill up. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 9:19: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 2A87A1537D for ; Fri, 8 Oct 1999 09:19:04 -0700 (PDT) (envelope-from leif@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id SAA70363; Fri, 8 Oct 1999 18:17:19 +0200 (CEST) (envelope-from leif@neland.dk) Message-ID: <00e601bf11a8$902b54c0$0e00a8c0@neland.dk> From: "Leif Neland" To: "Bill A. K." , References: <00db01bf113c$01933dc0$01010101@bopper> Subject: Sv: My status with upgrade from 3.2 to 4.0 Date: Fri, 8 Oct 1999 18:17:03 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Another thing was > syslogd was looking for /var/log/security and can't find it, how can i = fix > this? Just touch /var/log/security syslogd can't/doesn't _create_ files, just _append_ to existing ones. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 9:27: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4F4D214FC2 for ; Fri, 8 Oct 1999 09:27:04 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA02405; Fri, 8 Oct 1999 09:27:03 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA17931; Fri, 8 Oct 1999 09:27:03 -0700 (PDT) (envelope-from obrien) Date: Fri, 8 Oct 1999 09:27:02 -0700 From: "David O'Brien" To: Brad Knowles Cc: current@freebsd.org Subject: Re: make install trick Message-ID: <19991008092702.L25125@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <19991007152132.F68920@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you've done your job right, it can be mounted read-only. This > makes it harder for someone to break into the machine and obtain root > access, because now they have to be root to unmount /usr and remount > it read-write, so that they can put their trojan script on there that > they're hoping you'll execute. AND just how are crackers going to write their trojan's in my root owned /usr (and remember root now owns the binaries in /usr) w/o *already* being root. This is just as weak as the argument that BPF makes a box more vulnerable to having a rouge sniffer running on it. > You're right that this is a somewhat religious issue, however, if > you're going to run a huge root filesystem, then you are more likely > to get what you deserve if /usr or one of the other directories on > the root filesystem get trashed or fill up. And just what do I "deserve"? Fuh! Yea, as some said, lets go with a 30MB / so you can't even have room for a second kernel. You should see how fscked up Beast.freebsd.org is because of all the /, /usr, /var, /tmp, etc, were mis-sized. If I "deserve" something, then what's the proper sizes for these? I can tell you I run out of space on / a lot less my way and have space where I need it, than I do on machines with the millions of partitions. Fuh! -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 9:34:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4D5DA15823 for ; Fri, 8 Oct 1999 09:34:34 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA02503; Fri, 8 Oct 1999 09:34:31 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA17978; Fri, 8 Oct 1999 09:34:30 -0700 (PDT) (envelope-from obrien) Date: Fri, 8 Oct 1999 09:34:30 -0700 From: "David O'Brien" To: David Schwartz Cc: freebsd-current@FreeBSD.ORG Subject: Re: {a}sync updates (was Re: make install trick) Message-ID: <19991008093430.A17955@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991007151100.C68920@dragon.nuxi.com> <000001bf1111$674d5220$021d85d1@youwant.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <000001bf1111$674d5220$021d85d1@youwant.to> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 07, 1999 at 03:15:03PM -0700, David Schwartz wrote: > > > There should be fairly few writes to the root partition, so having > > An opionion. I use the HP workstation model where my / is 1800M. I have > You are not disagreeing with him, David. You are just talking about > another scenario other than the one under discussion. > He was talking about the case where root is small. This whole discussion > was about how softupdates behaves in the subcase of small root partitions. This discussion was NOT about "how softupdates behaves in the subcase of small root partitions" Imp was having problems in the face of softupdates on a full /. The problem exists *reguardless* of how big / is, the issues is % free. > If you have a 1.8Gb root partition that also includes /var and /usr, this > whole discussion is irrelevant. Why?? Because / can now not fill up? I've installed enough KDE/GNOME/teTeX/etc... ports (plus /usr/{ports,src}) that I have acutally filled it up before. (And before I'm attacked for my organization -- if I can get it back from the CDROM and it lives in /usr, it is on the / file systems which I don't back up, as there is no use to.) -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 10:13: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 7432914BD2; Fri, 8 Oct 1999 10:13:01 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA49036; Fri, 8 Oct 1999 10:11:47 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199910081711.KAA49036@gndrsh.dnsmgr.net> Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... In-Reply-To: <199910080934.CAA07195@implode.root.com> from David Greenman at "Oct 8, 1999 02:34:25 am" To: dg@root.com Date: Fri, 8 Oct 1999 10:11:46 -0700 (PDT) Cc: dwmalone@maths.tcd.ie (David Malone), dillon@apollo.backplane.com (Matthew Dillon), ady@warpnet.ro (Adrian Penisoara), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote: > > > >> Intel's ECC implementation is not perfect (1), but it's good enough to > >> catch these sorts of problems. > > > >Just as an interesting side note, we had a motherboard which > >supported ECC ram and had ECC ram in it and which was crashing. > >Eventually we discovered that every 8th byte in page aligned 4KB > >chunks was becomming corrupted. > > > >We replaced the ram and saw no improvement, and then got a replacement > >motherboard. As far as I could see the only significant difference > >between the new and old motherboard was the addition of a heat sink > >to the memory controler chip. The machine is now perfectly happy. > > > >So it seems that ECC isn't enough if your memory controler is too > >hot! > > ECC doesn't protect against certain types of motherboard address line > errors (since although the ECC is correct, the selected address is wrong, so > thus the data is wrong). There's parity protection on parts of the CPU > address bus, but I don't believe there is any protection between the memory > controller and the DIMMs for this type of problem. A handful of metal > filings is also known to cause problems when it is dispersed properly. :-) Your suppose to remove the motherboard before drilling holes in your chassis!!! :-). And be careful when you strip them there screws out, that little bit of metal filings is enough to through one for some real loops. A good blast of 60psi dry air does wonders for ``fixing'' some of these really strange problems :-) Now if I could just find something that would get sheet rock sanding dust out of tape drive mechanisms, a dunk in the freon tank often works, but that also cleans out all the lubrication :-). -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 10:20: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id C2E2A14BD2; Fri, 8 Oct 1999 10:20:05 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Fri, 8 Oct 1999 10:20:04 -0700 From: "David Schwartz" To: Cc: Subject: RE: {a}sync updates (was Re: make install trick) Date: Fri, 8 Oct 1999 10:20:03 -0700 Message-ID: <000d01bf11b1$5bfca1f0$021d85d1@youwant.to> 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.2377.0 In-reply-to: <19991008093430.A17955@dragon.nuxi.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Oct 07, 1999 at 03:15:03PM -0700, David Schwartz wrote: > > > > There should be fairly few writes to the root partition, so having > > > An opionion. I use the HP workstation model where my / is > 1800M. I have > > > You are not disagreeing with him, David. You are just talking about > > another scenario other than the one under discussion. > > He was talking about the case where root is small. This > whole discussion > > was about how softupdates behaves in the subcase of small > root partitions. > > This discussion was NOT about "how softupdates behaves in the subcase of > small root partitions" Imp was having problems in the face of > softupdates on a full /. The problem exists *reguardless* of how big / > is, the issues is % free. No, this is a different issue. The problem was not that the filesystem was full, but that the fill rate was comparable to the amount of 'empty' space. > > If you have a 1.8Gb root partition that also includes /var > and /usr, this > > whole discussion is irrelevant. > > Why?? Because / can now not fill up? I've installed enough > KDE/GNOME/teTeX/etc... ports (plus /usr/{ports,src}) that I have acutally > filled it up before. Yes, but if you fill up your root partition, there's nothing that can be done. Full is full. We're talking about the special case of small root partitions, such that softupdates inability to make empty space available quickly can make the difference between a major operation's success or failure. This is almost impossible on a 1.8Gb root partition. And if you had a 1.8Gb partition with only 15Mb free, the last thing you'd care about is how softupdates will handle the situation. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 10:30: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 4D27714A1B for ; Fri, 8 Oct 1999 10:28:32 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.032 #1) id 11Zbwa-0001qp-00; Fri, 08 Oct 1999 16:28:28 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.032 #1) id 11Zbwa-0000f8-00; Fri, 08 Oct 1999 16:28:28 +0100 Date: Fri, 8 Oct 1999 16:28:28 +0100 From: Ben Smithurst To: "Phil 0. Nature" Cc: freebsd-current@freebsd.org Subject: Re: identd Message-ID: <19991008162828.A2517@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Phil 0. Nature wrote: > Has anyone else experienced problems with identd not working? Uh, you'd probably have to be more specific. What identd (pidentd from ports, or something else). What version. In what way doesn't it work. What error messages are being logged. What version of FreeBSD. -current, presumably, but how recent. The only small problem I've seen is this, with pidentd-2.8.5 from ports on a 3.2-stable system: Sep 30 21:54:20 scientia identd[75098]: getbuf: bad address (00000f80 not in c0116360-0xFFC00000) - ofile Sep 30 21:54:20 scientia identd[75098]: k_getuid retries: 1 Oct 3 12:48:00 scientia identd[93188]: getbuf: bad address (0000137b not in c0116360-0xFFC00000) - ofile Oct 3 12:48:00 scientia identd[93188]: k_getuid retries: 1 but I haven't got round to looking into it much. Other than those two errors, it works fine. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 10:52:37 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 8A45414EC4; Fri, 8 Oct 1999 10:52:34 -0700 (PDT) Date: Fri, 8 Oct 1999 10:52:34 -0700 From: David O'Brien To: David Schwartz Cc: freebsd-current@FreeBSD.ORG Subject: Re: {a}sync updates (was Re: make install trick) Message-ID: <19991008105234.A58223@hub.freebsd.org> Reply-To: obrien@freebsd.org References: <19991008093430.A17955@dragon.nuxi.com> <000d01bf11b1$5bfca1f0$021d85d1@youwant.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <000d01bf11b1$5bfca1f0$021d85d1@youwant.to>; from David Schwartz on Fri, Oct 08, 1999 at 10:20:03AM -0700 X-Operating-System: FreeBSD 3.3-RC Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We're talking about the special case of small root partitions, such that > softupdates inability to make empty space available quickly can make the > difference between a major operation's success or failure. > > This is almost impossible on a 1.8Gb root partition. Again why? What's the difference between a small / and a 1.8GB (byte not bit) one? There is nothing here to back this up. Not enough space is not enough space reguardless how much you started out with. > And if you had a 1.8Gb partition with only 15Mb free, the last thing > you'd care about is how softupdates will handle the situation. Why would I be so concerned? If I don't expect to need that 15M then, I've sized my partition just right. Don't put cares in my basket that don't need to be there. More uninstatiated opions. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 11:24: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 81CB914A29; Fri, 8 Oct 1999 11:24:06 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA03889; Fri, 8 Oct 1999 11:24:06 -0700 (PDT) (envelope-from dillon) Date: Fri, 8 Oct 1999 11:24:06 -0700 (PDT) From: Matthew Dillon Message-Id: <199910081824.LAA03889@apollo.backplane.com> To: "David O'Brien" Cc: David Schwartz , freebsd-current@FreeBSD.ORG Subject: Re: {a}sync updates (was Re: make install trick) References: <19991008093430.A17955@dragon.nuxi.com> <000d01bf11b1$5bfca1f0$021d85d1@youwant.to> <19991008105234.A58223@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> We're talking about the special case of small root partitions, such that :> softupdates inability to make empty space available quickly can make the :> difference between a major operation's success or failure. :> :> This is almost impossible on a 1.8Gb root partition. : :Again why? What's the difference between a small / and a 1.8GB (byte not :... :Why would I be so concerned? If I don't expect to need that 15M then, :I've sized my partition just right. Don't put cares in my basket that :... :-- :-- David (obrien@FreeBSD.org) I think the argument has become somewhat skewed. The softupdates bug occurs when a filesystem fills up, it doesn't really matter how small or large the filesystem is. What matters more is how often a partition is actually written to and how likely the chance of the partition filling up. Personally speaking, I tend to use small (64-128MB) root partitions with a separately mounted /usr and /var (and /tmp a softlink to /var/tmp). In fact, I usually separate out /var/tmp as well. I do this simply to reduce the amount of writing that occurs on the root partition in order to ensure that I don't lose it accidently. This has saved my butt on innumerable occassions... there is something to be said for being able to boot into a workable shell when you've blown up the rest of the system! With my configuration I feel perfectly safe enabling softupdates on root. In other configurations, such as having /usr and /var on the same partition as root, I might not feel as safe. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 11:28:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id CF81A14A25; Fri, 8 Oct 1999 11:28:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA03945; Fri, 8 Oct 1999 11:28:18 -0700 (PDT) (envelope-from dillon) Date: Fri, 8 Oct 1999 11:28:18 -0700 (PDT) From: Matthew Dillon Message-Id: <199910081828.LAA03945@apollo.backplane.com> To: "Rodney W. Grimes" Cc: dg@root.com, dwmalone@maths.tcd.ie (David Malone), ady@warpnet.ro (Adrian Penisoara), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... References: <199910081711.KAA49036@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> ECC doesn't protect against certain types of motherboard address line :> errors (since although the ECC is correct, the selected address is wrong, so :> thus the data is wrong). There's parity protection on parts of the CPU :> address bus, but I don't believe there is any protection between the memory :> controller and the DIMMs for this type of problem. A handful of metal :> filings is also known to cause problems when it is dispersed properly. :-) : :Your suppose to remove the motherboard before drilling holes in your :chassis!!! :-). And be careful when you strip them there screws out, :that little bit of metal filings is enough to through one for some : :Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net Forget the drilling! Blood conducts electricity... simply *installing* a motherboard in those fraggin sharp-edged sheet metal chassis is enough! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 17:29: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 466A614DE5 for ; Fri, 8 Oct 1999 17:29:00 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (root@rac2.wam.umd.edu [128.8.10.142]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id UAA02373 for ; Fri, 8 Oct 1999 20:28:54 -0400 (EDT) Received: from rac2.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id UAA18099 for ; Fri, 8 Oct 1999 20:28:58 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA18095 for ; Fri, 8 Oct 1999 20:28:58 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Fri, 8 Oct 1999 20:28:57 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: linux emu and quake3test Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IT seems that a recent change to the linux emulation code has caused q3 to have problems, whenever I try to go to an internet game, I get a message on the console: usage: ping [server] doing this operation worked fine yesterday. Kenneth Culver ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 21:17:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 7DA7414EC2 for ; Fri, 8 Oct 1999 21:17:29 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11Znwn-000FD7-00 for freebsd-current@freebsd.org; Fri, 08 Oct 1999 21:17:29 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: staroffice Message-Id: Date: Fri, 08 Oct 1999 21:17:29 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG anyone successful installing staroffice 5.1? is still the best hint? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 22:14:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id E86A914DF3 for ; Fri, 8 Oct 1999 22:14:38 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id BAA52339; Sat, 9 Oct 1999 01:14:22 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sat, 9 Oct 1999 01:14:21 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: "Daniel C. Sobral" Cc: Poul-Henning Kamp , current@FreeBSD.org Subject: Re: maxphys = 0?? In-Reply-To: <37F9F663.7885D59A@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Oct 1999, Daniel C. Sobral wrote: > Poul-Henning Kamp wrote: > > > > You need to move your sources further forward. > > Alas, it didn't help. What versions of what files I should have? The > warnings are still appearing, at fsck time. > Alas, similarly I get: changing root device to wd0s1a WARNING: #ad/0x20007 maxphys = 0 ??WARNING: #ad/0x20006 maxphys = 0 ??WARNING: #ad/0x20004 maxphys = 0 ??WARNING: #ad/0x20005 maxphys = 0 ??WARNING: #ad/2 maxphys = 0 ?? -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 8 23:57:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 35A8315283; Fri, 8 Oct 1999 23:57:26 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA09834; Sat, 9 Oct 1999 08:57:23 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Brian F. Feldman" Cc: "Daniel C. Sobral" , current@FreeBSD.org Subject: Re: maxphys = 0?? In-reply-to: Your message of "Sat, 09 Oct 1999 01:14:21 EDT." Date: Sat, 09 Oct 1999 08:57:22 +0200 Message-ID: <9832.939452242@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Bria n F. Feldman" writes: >On Tue, 5 Oct 1999, Daniel C. Sobral wrote: > >> Poul-Henning Kamp wrote: >> > >> > You need to move your sources further forward. >> >> Alas, it didn't help. What versions of what files I should have? The >> warnings are still appearing, at fsck time. The lastest. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 0: 2:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.unacom.com (www.lockes.net [206.113.48.50]) by hub.freebsd.org (Postfix) with SMTP id 964ED14DFA for ; Sat, 9 Oct 1999 00:02:21 -0700 (PDT) (envelope-from geniusj@phoenix.unacom.com) Received: (qmail 82070 invoked by uid 1016); 9 Oct 1999 07:02:20 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 Oct 1999 07:02:20 -0000 Date: Sat, 9 Oct 1999 03:02:20 -0400 (EDT) From: Jason DiCioccio To: current@freebsd.org Subject: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0 insists on detecting my ethernet card PnP at installation even though Id ont want it to.. When it does, it freezes up, and its much easier for me just to input the settings manually info the visual config.. I need to disable on install disk, or get a 4.0 floppy that doesn't freeze on 'unknown0', of course, not having it detected at all would be preferable :).. Thanks in advance, Jason DiCioccio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 0:14:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E7406158FD; Sat, 9 Oct 1999 00:14:16 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p20-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.149]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id QAA03000; Sat, 9 Oct 1999 16:14:10 +0900 (JST) Message-ID: <37FEEAD8.2683C6EE@newsguy.com> Date: Sat, 09 Oct 1999 16:12:24 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Poul-Henning Kamp Cc: "Brian F. Feldman" , current@FreeBSD.org Subject: Re: maxphys = 0?? References: <9832.939452242@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message , "Bria > n F. Feldman" writes: > >On Tue, 5 Oct 1999, Daniel C. Sobral wrote: > > > >> Poul-Henning Kamp wrote: > >> > > >> > You need to move your sources further forward. > >> > >> Alas, it didn't help. What versions of what files I should have? The > >> warnings are still appearing, at fsck time. > > The lastest. Well, I tried with the latest after you said the above. I'll try with a later latest again. But, really... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 0:20:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 80ADE158FD; Sat, 9 Oct 1999 00:20:27 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA09905; Sat, 9 Oct 1999 09:19:36 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Daniel C. Sobral" Cc: "Brian F. Feldman" , current@FreeBSD.ORG Subject: Re: maxphys = 0?? In-reply-to: Your message of "Sat, 09 Oct 1999 16:12:24 +0900." <37FEEAD8.2683C6EE@newsguy.com> Date: Sat, 09 Oct 1999 09:19:35 +0200 Message-ID: <9903.939453575@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37FEEAD8.2683C6EE@newsguy.com>, "Daniel C. Sobral" writes: >Poul-Henning Kamp wrote: >> >> In message , "Bria >> n F. Feldman" writes: >> >On Tue, 5 Oct 1999, Daniel C. Sobral wrote: >> > >> >> Poul-Henning Kamp wrote: >> >> > >> >> > You need to move your sources further forward. >> >> >> >> Alas, it didn't help. What versions of what files I should have? The >> >> warnings are still appearing, at fsck time. >> >> The lastest. > >Well, I tried with the latest after you said the above. I'll try >with a later latest again. But, really... Well, there are two options, either your sources are not up to date, or your config is very special in some way... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 0:59:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1D18715034 for ; Sat, 9 Oct 1999 00:59:31 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from d146.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id SAA25980; Sat, 9 Oct 1999 18:01:27 +1000 Date: Sat, 9 Oct 1999 17:59:15 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Andrew Gallatin Cc: current@FreeBSD.ORG Subject: Re: installworld broken from R/O /usr/obj In-Reply-To: <14330.45971.639580.378954@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > W`hile installworld is being discussed, I wanted to get this out there: > > Since rev 1.13 of usr.bin/make/arch.c, I've been seing a problem with > ELF archive libraries being rebuilt unnecessarily. I believe that > this problem can be traced to the RANLIBMAG string being set to "/". There's a PR about this now. The smaller fix in the PR seems to work. Rev.1.13 of arch.c also weakened aout support. RANLIBMAG is configured at compile time, so only one of elf and aout is supported by a given `make' binary. It's not clear that this is good enough for `make upgrade' where the same tools are expected to support both aout and elf. > The reason I care about this is that its causing perl's libsdbm.a to > get rebuilt during an installworld. This is causing installworlds to > fail for me from R/O /usr/obj partitions. There must be a bug in the perl makefiles for `install' to depend on anything. The bug in libgcc_r/Makefile that caused libraries to be rebuilt didn't affect your installworld, since the libgcc_r Makefile has correct dependencies for `install'. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 3:58:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 36EDE14EA3 for ; Sat, 9 Oct 1999 03:58:06 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id GAA59859; Sat, 9 Oct 1999 06:57:47 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sat, 9 Oct 1999 06:57:47 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Poul-Henning Kamp Cc: "Daniel C. Sobral" , current@FreeBSD.org Subject: Re: maxphys = 0?? In-Reply-To: <9903.939453575@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 9 Oct 1999, Poul-Henning Kamp wrote: > Well, there are two options, either your sources are not up to date, > or your config is very special in some way... I am absolutely certain that my sources are up-to-date. I'll attach my kernel config in case you can find something special there. > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.102 1998/01/11 02:16:38 jkh Exp $ machine i386 cpu I586_CPU ident GREEN maxusers 64 makeoptions DEBUG="-g" #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options IPX options NETATALK options FFS #Berkeley Fast Filesystem options FFS_ROOT options CD9660 #ISO 9660 Filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options NO_F00F_HACK options IPFIREWALL options IPFIREWALL_FORWARD #enable xparent proxy support options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 options IPDIVERT options IPSTEALTH #options IPFILTER options DUMMYNET options DDB options DDB_UNATTENDED options SOFTUPDATES options PQ_HUGECACHE # color for 1024k cache options ICMP_BANDLIM options MSGBUF_SIZE=16384 options INVARIANTS options INVARIANT_SUPPORT options CLK_USE_TSC_CALIBRATION #options ICMP_BANDLIM_SILENT options CPU_WT_ALLOC options NO_MEMORY_HOLE options MAXFILES=65536 controller pci0 at nexus? controller isa0 at nexus? controller pnp0 # Luigi's snd code. # You may also wish to enable the pnp controller with this, for pnp # sound cards. # #device pcm0 at isa? port 0x220 irq 5 drq 1 #flags 0x16 controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 6 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 device joy0 at isa? port IO_GAME #controller fdc0 at isa? port IO_FD1 irq 6 drq 2 #disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # for a PCI only system (most modern machines) controller ata0 device atadisk0 # ATA disks device atapicd0 # ATAPI CDROM's device atapist0 # ATAPI tapes device atapifd0 controller ncr0 controller scbus0 #base SCSI code device ch0 #SCSI media changers device da0 #SCSI direct access devices (aka disks) device sa0 #SCSI tapes device cd0 #SCSI CD-ROMs device pass0 #CAM passthrough driver device pt0 at scbus? # SCSI processor type options SCSI_DELAY=5000 # Be pessimistic about Joe SCSI device # The keyboard controller; it controlls the keyboard and the PS/2 mouse. controller atkbdc0 at isa? port IO_KBD # The AT keyboard device atkbd0 at atkbdc? irq 1 # PS/2 mouse device psm0 at atkbdc? irq 12 # The video card driver. device vga0 at isa? port ? conflicts # The syscons console driver (sco color console compatible). device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # #device apm0 at nexus? conflicts # Advanced Power Management # System Management Bus! controller smbus0 controller alpm0 device smb0 at smbus? device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 3 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device pps0 at ppbus? controller ppc0 at isa? port ? irq 7 drq 3 # USB support # UHCI controller #controller uhci0 # OHCI controller controller ohci0 # General USB code (mandatory for USB) controller usb0 pseudo-device loop pseudo-device ether #pseudo-device sl 2 #pseudo-device ppp 2 #pseudo-device tun 4 pseudo-device pty #pseudo-device gzip # Exec gzipped a.out's pseudo-device speaker pseudo-device snp 4 pseudo-device bpf 4 #Berkeley packet filter pseudo-device splash pseudo-device md # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=8200 options SYSVSHM options SYSVSEM options SYSVMSG options USER_LDT #allow user-level control of i386 ldt options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 4:24:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3B20815CA0; Sat, 9 Oct 1999 04:24:11 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id NAA10695; Sat, 9 Oct 1999 13:24:07 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Brian F. Feldman" Cc: "Daniel C. Sobral" , current@FreeBSD.org Subject: Re: maxphys = 0?? In-reply-to: Your message of "Sat, 09 Oct 1999 06:57:47 EDT." Date: Sat, 09 Oct 1999 13:24:06 +0200 Message-ID: <10693.939468246@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Bria n F. Feldman" writes: >On Sat, 9 Oct 1999, Poul-Henning Kamp wrote: > >> Well, there are two options, either your sources are not up to date, >> or your config is very special in some way... > >I am absolutely certain that my sources are up-to-date. I'll attach my >kernel config in case you can find something special there. What does your /etc/fstab look like ? I would also like to see a dmesg output. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 5:15:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id E1FB414E0A for ; Sat, 9 Oct 1999 05:15:11 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 1619F1925; Sat, 9 Oct 1999 14:15:01 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 131DC49DB; Sat, 9 Oct 1999 14:15:01 +0200 (CEST) Date: Sat, 9 Oct 1999 14:15:01 +0200 (CEST) From: Andrzej Bialecki To: Randy Bush Cc: FreeBSD Current Subject: Re: staroffice In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Oct 1999, Randy Bush wrote: > anyone successful installing staroffice 5.1? > > is still the best hint? The new Sun's version works for me out of the box. The only glitch during setup was that I had to unzip the setup.zip and ldconfig the libraries therein. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 5:48:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 6940414EE3 for ; Sat, 9 Oct 1999 05:48:35 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id NAA40336; Sat, 9 Oct 1999 13:51:16 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 9 Oct 1999 13:51:15 +0100 (BST) From: Doug Rabson To: Jason DiCioccio Cc: current@freebsd.org Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 9 Oct 1999, Jason DiCioccio wrote: > > Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0 > insists on detecting my ethernet card PnP at installation even though Id > ont want it to.. When it does, it freezes up, and its much easier for me > just to input the settings manually info the visual config.. I need to > disable on install disk, or get a 4.0 floppy that doesn't freeze on > 'unknown0', of course, not having it detected at all would be preferable > :).. There was a problem with the pnp code which caused freezes like this which I fixed. What date was the snap that you tried? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 6:42:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 39E1514ED7 for ; Sat, 9 Oct 1999 06:42:06 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11Zwl3-0000R4-00; Sat, 09 Oct 1999 06:41:57 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andrzej Bialecki , Luke Cc: FreeBSD Current Subject: Re: staroffice References: Message-Id: Date: Sat, 09 Oct 1999 06:41:57 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> anyone successful installing staroffice 5.1? >> is still the best hint? Andrzej Bialecki : > The new Sun's version works for me out of the box. The only glitch during > setup was that I had to unzip the setup.zip and ldconfig the libraries > therein. Luke : > I have the latest star office on a machine that was running a -current from > @july and then mid sept, now its got 3.3 on it and it still runs , > I have alot of linux stuff installed for oracle, I dont know if staroffice is > using stuff from it though. > this page was a little helpful but it is still was a pita to get to run. > http://www.serv.net/~mcglk/staroffice-install.html hmmmm. so i o add the posix options to my kernel o install linux_base port o but can not find linux_lib port o unzip setup.zip to someplace comfortable o echo `pwd` >> /compat/linux/etc/ld.so.conf o /compat/linux/sbin/ldconfig and whammie! Segmentation fault (core dumped) Core was generated by `ldconfig'. Program terminated with signal 11, Segmentation fault. #0 0x805c553 in ?? () (gdb) where #0 0x805c553 in ?? () #1 0x8057c0f in ?? () #2 0x805514c in ?? () #3 0x8052839 in ?? () so i delete the line resulting from "echo `pwd` ..." from the file /compat/linux/etc/ld.so.conf same result. so it probably is something stoopid in the linux install. content of /compat/linux/etc/ld.so.conf /usr/local/lib /usr/X11R6/lib /usr/i486-linuxaout/lib /usr/openwin/lib /usr/i486-linux-libc5/lib /usr/home/randy/sosetup some of the files are not there # ls -ld `cat /compat/linux/etc/ld.so.conf` ls: /usr/i486-linux-libc5/lib: No such file or directory ls: /usr/i486-linuxaout/lib: No such file or directory ls: /usr/openwin/lib: No such file or directory drwxr-xr-x 5 root wheel 1536 Sep 3 18:08 /usr/X11R6/lib/ drwxr-xr-x 2 root staff 1024 Oct 9 06:15 /usr/home/randy/sosetup/ drwxr-xr-x 17 root wheel 2048 Oct 8 21:07 /usr/local/lib/ so i delete them from /compat/linux/etc/ld.so.conf. and get the same core. i'm doing something pretty clueless, but coffee is not helping. randy Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Oct 9 05:53:03 PDT 1999 root@rip.psg.com:/usr/src/sys/compile/RIP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbff real memory = 134205440 (131060K bytes) avail memory = 126926848 (123952K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02fd000. Pentium Pro MTRR support enabled ccd0-5: Concatenated disk drivers npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 4.0 on pci0 isa0: on isab0 chip1: at device 4.1 on pci0 chip2: irq 19 at device 4.2 on pci0 Timecounter "PIIX" frequency 3579545 Hz intpm0: at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 ahc0: irq 19 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: irq 19 at device 9.0 on pci0 fxp0: Ethernet address 00:a0:c9:df:c8:4e bktr0: irq 18 at device 10.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only iicsmb0: on iicbus0 smbus1: on iicsmb0 smb1: on smbus1 WARNING: "iic" is usurping "iic"'s cdevsw[] iic0: on iicbus0 smbus2: on bti2c0 smb2: on smbus2 bktr0: Hauppauge Model 61111 A M bktr0: Detected a MSP3430G-A1 at 0x80 Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo. pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 10.1 irq 18 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <4 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A wl0 at port 0x300-0x30f irq 7 on isa0 wl0: address 08:00:6a:2b:dd:a7, NWID 0xaaaa pcm0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x620-0x623 on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 wl0 XXX: driver didn't set ifq_maxlen Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 8.333MB/s transfers (8.333MHz, offset 31) cd1: cd present [140956 x 2048 byte records] # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.freebsd.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.180 1999/08/08 19:28:57 phk Exp $ # This allows you to actually store this configuration file into # the kernel binary itself, where it may be later read by saying: # strings -aout -n 3 /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL # options INCLUDE_CONFIG_FILE # Include this file in kernel machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident RIP maxusers 96 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem #options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores # Soft updates is technique for improving file system speed and # making abrupt shutdown less risky. It is not enabled by default due # to copyright restraints on the code that implement it. # # Read ../../ufs/ffs/README.softupdates to learn what you need to # do to enable this. ../../contrib/softupdates/README gives # more details on how they actually work. # options SOFTUPDATES # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): options NCPU=2 # number of CPUs options NBUS=4 # number of busses options NAPIC=2 # number of IO APICs options NINTR=24 # number of INTs controller isa0 controller pnp0 # PnP support for ISA #controller eisa0 controller pci0 # Real time extensions added in the 1993 Posix # P1003_1B: Infrastructure # _KPOSIX_PRIORITY_SCHEDULING: Build in _POSIX_PRIORITY_SCHEDULING # _KPOSIX_VERSION: Version kernel is built for options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L # Floppy drives controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # IDE controller and disks #controller wdc0 at isa? port IO_WD1 irq 14 #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port IO_WD2 irq 15 #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 # ATAPI devices on wdc? #device wcd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) #device wst0 #IDE Tape (e.g. Travan) # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. #controller ncr0 # NCR/Symbios Logic #controller ahb0 # EISA AHA1742 family controller ahc0 # AHA2940 and onboard AIC7xxx devices #controller isp0 # Qlogic family #controller dpt0 # DPT Smartcache - See LINT for options! #controller adv0 at isa? port ? irq ? #controller adw0 #controller bt0 at isa? port ? irq ? #controller aha0 at isa? port ? irq ? # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. controller scbus0 at ahc0 # SCSI bus (required) #device da0 # Direct Access (disks) disk da0 at scbus0 target 0 unit 0 disk da1 at scbus0 target 1 unit 0 device sa0 # Sequential Access (tape etc) device cd0 device pass0 # Passthrough device (direct SCSI access) # Proprietary or custom CD-ROM Interfaces #device wt0 at isa? port 0x300 irq 5 drq 1 #device mcd0 at isa? port 0x300 irq 10 #device matcd0 at isa? port 0x230 #device scd0 at isa? port 0x230 # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? options MAXCONS=4 # number of virtual consoles # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 #device sio2 at isa? disable port IO_COM3 irq 5 #device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port #device ppc0 at isa? port? flags 0x40 irq 7 #controller ppbus0 # Parallel port bus (required) #device lpt0 # Printer #device plip0 # TCP/IP over parallel #device ppi0 # Parallel port interface device #controller vpo0 # Requires scbus and da0 # PCI Ethernet NICs. #device al0 # ADMtek AL981 (``Comet'') #device ax0 # ASIX AX88140A #device de0 # DEC/Intel DC21x4x (``Tulip'') device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) #device mx0 # Macronix 98713/98715/98725 (``PMAC'') #device pn0 # Lite-On 82c168/82c169 (``PNIC'') #device rl0 # RealTek 8129/8139 #device sf0 # Adaptec AIC-6915 (``Starfire'') #device tl0 # Texas Instruments ThunderLAN #device tx0 # SMC 9432TX (83c170 ``EPIC'') #device vr0 # VIA Rhine, Rhine II #device vx0 # 3Com 3c590, 3c595 (``Vortex'') #device wb0 # Winbond W89C840F #device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device ep0 at isa? port 0x300 irq 10 #device ex0 at isa? port? irq? #device fe0 at isa? port 0x300 irq ? #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 irq ? # requires PCCARD (PCMCIA) support to be activated #device xe0 at isa? port? irq ? # PCCARD NIC drivers. # ze and zp take over the pcic and cannot coexist with generic pccard # support, nor the ed and ep drivers they replace. #device ze0 at isa? port 0x300 irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 irq 10 iomem 0xd8000 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP #pseudo-device tun 1 # Packet tunnel, for ppp(1) pseudo-device pty 32 # Pseudo-ttys (telnet etc) #pseudo-device gzip # Exec gzipped a.out's pseudo-device ccd 6 #Concatenated disk driver # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf 4 #Berkeley packet filter # USB support #controller uhci0 # UHCI PCI->USB interface #controller ohci0 # OHCI PCI->USB interface #controller usb0 # USB Bus (required) #device ugen0 # Generic #device uhid0 # "Human Interface Devices" #device ukbd0 # Keyboard #device ulpt0 # Printer #controller umass0 # Disks/Mass storage - Requires scbus and da0 #device ums0 # Mouse device wl0 at isa? port 0x300 irq ? options WLCACHE # enables the signal-strength cache #options WLDEBUG # enables verbose debugging output # # SMB bus # # System Management Bus support provided by the 'smbus' device. # # Supported devices: # smb standard io # # Supported interfaces: # iicsmb I2C to SMB bridge with any iicbus interface # bktr brooktree848 I2C hardware interface # controller smbus0 controller intpm0 controller alpm0 device smb0 at smbus? # # I2C Bus # # Philips i2c bus support is provided by the `iicbus' device. # # Supported devices: # ic i2c network interface # iic i2c standard io # iicsmb i2c to smb bridge. Allow i2c i/o with smb commands. # # Supported interfaces: # pcf Philips PCF8584 ISA-bus controller # bktr brooktree848 I2C software interface # # Other: # iicbb generic I2C bit-banging code (needed by lpbb, bktr) # controller iicbus0 controller iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? # Brooktree driver has been ported to the new I2C framework. Thus, # you'll need at least iicbus, iicbb and smbus. iic/smb are only needed if you # want to control other I2C slaves connected to the external connector of # some cards. # device bktr0 # pcm: Luigi's sound driver #device pcm0 at isa? port ? irq 5 drq 1 flags 0x0 device pcm0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 7:10:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 0F0A814BD2 for ; Sat, 9 Oct 1999 07:10:52 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p25-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.122]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id XAA20279; Sat, 9 Oct 1999 23:10:26 +0900 (JST) Message-ID: <37FF3B68.2754FE27@newsguy.com> Date: Sat, 09 Oct 1999 21:56:08 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Jason DiCioccio Cc: current@FreeBSD.ORG Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason DiCioccio wrote: > > Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0 > insists on detecting my ethernet card PnP at installation even though Id > ont want it to.. When it does, it freezes up, and its much easier for me > just to input the settings manually info the visual config.. I need to > disable on install disk, or get a 4.0 floppy that doesn't freeze on > 'unknown0', of course, not having it detected at all would be preferable > :).. I don't get it... why is it that you'd prefer it not to detect your card, even if it did not freeze? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 7:54:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 72F4D14D3F for ; Sat, 9 Oct 1999 07:54:45 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 864F738 for ; Sat, 9 Oct 1999 18:54:43 +0400 (MSD) Date: Sat, 9 Oct 1999 18:54:43 +0400 (MSD) From: Osokin Sergey To: FreeBSD-current mail-list Subject: SB128PCI problem under -current... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I use SB128PCI under today-update -current & have a problem: play (from /usr/ports/audio) plays wav-files incorrectly: it james some part from the begining, then plays rest of the file and in the end plays that jammed part... Does anobody have similiar problems with SB 128 PCI? Rgdz, Osokin Sergey, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 8:47:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.unacom.com (www.lockes.net [206.113.48.50]) by hub.freebsd.org (Postfix) with SMTP id C9C0B14DE8 for ; Sat, 9 Oct 1999 08:47:15 -0700 (PDT) (envelope-from geniusj@phoenix.unacom.com) Received: (qmail 10895 invoked by uid 1016); 9 Oct 1999 15:47:15 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 Oct 1999 15:47:15 -0000 Date: Sat, 9 Oct 1999 11:47:15 -0400 (EDT) From: Jason DiCioccio To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org In-Reply-To: <37FF3B68.2754FE27@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I use visual_userconfig set ed0 to 0x240 and irq 7 and it detects it I dont need the PnP probe on ISA bus. On Sat, 9 Oct 1999, Daniel C. Sobral wrote: > Jason DiCioccio wrote: > > > > Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0 > > insists on detecting my ethernet card PnP at installation even though Id > > ont want it to.. When it does, it freezes up, and its much easier for me > > just to input the settings manually info the visual config.. I need to > > disable on install disk, or get a 4.0 floppy that doesn't freeze on > > 'unknown0', of course, not having it detected at all would be preferable > > :).. > > I don't get it... why is it that you'd prefer it not to detect your > card, even if it did not freeze? > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "I always feel generous when I'm in the inner circle of a > conspiracy to subvert the world order and, with a small group of > allies, just defeated an alien invasion. Maybe I should value myself > a little more?" > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 8:47:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.unacom.com (www.lockes.net [206.113.48.50]) by hub.freebsd.org (Postfix) with SMTP id 370AD1509C for ; Sat, 9 Oct 1999 08:47:24 -0700 (PDT) (envelope-from geniusj@phoenix.unacom.com) Received: (qmail 10902 invoked by uid 1016); 9 Oct 1999 15:47:24 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 Oct 1999 15:47:24 -0000 Date: Sat, 9 Oct 1999 11:47:24 -0400 (EDT) From: Jason DiCioccio To: Doug Rabson Cc: current@freebsd.org Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I shall try again :) On Sat, 9 Oct 1999, Doug Rabson wrote: > On Sat, 9 Oct 1999, Jason DiCioccio wrote: > > > > > Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0 > > insists on detecting my ethernet card PnP at installation even though Id > > ont want it to.. When it does, it freezes up, and its much easier for me > > just to input the settings manually info the visual config.. I need to > > disable on install disk, or get a 4.0 floppy that doesn't freeze on > > 'unknown0', of course, not having it detected at all would be preferable > > :).. > > There was a problem with the pnp code which caused freezes like this which > I fixed. What date was the snap that you tried? > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 8:59:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B10921509C for ; Sat, 9 Oct 1999 08:59:43 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p28-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.125]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id AAA08688; Sun, 10 Oct 1999 00:59:30 +0900 (JST) Message-ID: <37FF65EA.B2E54919@newsguy.com> Date: Sun, 10 Oct 1999 00:57:30 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Jason DiCioccio Cc: current@FreeBSD.ORG Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason DiCioccio wrote: > > I use visual_userconfig set ed0 to 0x240 and irq 7 and it detects it > I dont need the PnP probe on ISA bus. Well, I don't need C, I could program in assembly language, but I still think using C is easier. I'm asking why do you *object* to your card being recognized by the PnP probe instead of configured manually. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 9:42:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.unacom.com (www.lockes.net [206.113.48.50]) by hub.freebsd.org (Postfix) with SMTP id 06BE514BF3 for ; Sat, 9 Oct 1999 09:42:50 -0700 (PDT) (envelope-from geniusj@phoenix.unacom.com) Received: (qmail 13187 invoked by uid 1016); 9 Oct 1999 16:42:50 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 Oct 1999 16:42:50 -0000 Date: Sat, 9 Oct 1999 12:42:50 -0400 (EDT) From: Jason DiCioccio To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org In-Reply-To: <37FF65EA.B2E54919@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG as i've said, because it freezes my machine when it detects it PnP.. And, as you can imagine, I do not want my installation freezing on me :) On Sun, 10 Oct 1999, Daniel C. Sobral wrote: > Jason DiCioccio wrote: > > > > I use visual_userconfig set ed0 to 0x240 and irq 7 and it detects it > > I dont need the PnP probe on ISA bus. > > Well, I don't need C, I could program in assembly language, but I > still think using C is easier. > > I'm asking why do you *object* to your card being recognized by the > PnP probe instead of configured manually. > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "I always feel generous when I'm in the inner circle of a > conspiracy to subvert the world order and, with a small group of > allies, just defeated an alien invasion. Maybe I should value myself > a little more?" > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 10:36: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 19FFA15283 for ; Sat, 9 Oct 1999 10:36:05 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FJC0086WJIV6P@mta4.rcsntx.swbell.net> for freebsd-current@FreeBSD.ORG; Sat, 9 Oct 1999 12:35:59 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id MAA07279; Sat, 09 Oct 1999 12:34:41 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Sat, 09 Oct 1999 12:34:41 -0500 From: Chris Costello Subject: Re: SB128PCI problem under -current... In-reply-to: To: Osokin Sergey Cc: FreeBSD-current mail-list Reply-To: chris@calldei.com Message-id: <19991009123440.A86678@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 09, 1999, Osokin Sergey wrote: > > Hello! > I use SB128PCI under today-update -current & have a problem: > play (from /usr/ports/audio) plays wav-files incorrectly: it james some > part from the begining, then plays rest of the file and in the end plays > that jammed part... > Does anobody have similiar problems with SB 128 PCI? I run into problems with my SB 64 PCI card. This problem is known as ``-CURRENT''. :) Expect problems! It's the development branch. The newpcm code is still not fully perfect (or up to the working order oldpcm had), so you should give it time. -- |Chris Costello |Asking whether machines can think is like asking whether |submarines can swim. `-------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 12:43:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 2D31E14DB5 for ; Sat, 9 Oct 1999 12:43:14 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11a2Of-00042i-00 for freebsd-current@freebsd.org; Sat, 09 Oct 1999 12:43:13 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: Re: lconfig cores [ was: staroffice ] References: Message-Id: Date: Sat, 09 Oct 1999 12:43:13 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG # /compat/linux/sbin/ldconfig Segmentation fault (core dumped) could it be that i need more compat libs than 22? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 14:26:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 4F5E614A2D for ; Sat, 9 Oct 1999 14:26:07 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 62CEE1925; Sat, 9 Oct 1999 23:25:57 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 5FE5849CF; Sat, 9 Oct 1999 23:25:57 +0200 (CEST) Date: Sat, 9 Oct 1999 23:25:57 +0200 (CEST) From: Andrzej Bialecki To: Randy Bush Cc: FreeBSD Current Subject: Re: lconfig cores [ was: staroffice ] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 9 Oct 1999, Randy Bush wrote: > # /compat/linux/sbin/ldconfig > Segmentation fault (core dumped) > > could it be that i need more compat libs than 22? Usually when you're missing some lib, the program wouldn't start at all. It could be that you have some incompatible version of the libs, though... but overall it looks to me like screwed up installation of linux_base port. Try the standard IT solution: reinstall linux_base. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 14:29:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id 8794714E16; Sat, 9 Oct 1999 14:29:37 -0700 (PDT) (envelope-from dima@tejblum.pp.ru) Received: (from uucp@localhost) by arc.hq.cti.ru (8.9.3/8.9.3) with UUCP id BAA64032; Sun, 10 Oct 1999 01:29:31 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Received: from tejblum.pp.ru (localhost [127.0.0.1]) by tejblum.pp.ru (8.9.3/8.9.3) with ESMTP id BAA04136; Sun, 10 Oct 1999 01:34:14 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Message-Id: <199910092134.BAA04136@tejblum.pp.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: "David Schwartz" Cc: obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG From: Dmitrij Tejblum Subject: Re: {a}sync updates (was Re: make install trick) In-reply-to: Your message of "Fri, 08 Oct 1999 10:20:03 PDT." <000d01bf11b1$5bfca1f0$021d85d1@youwant.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Oct 1999 01:34:13 +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David Schwartz" wrote: > We're talking about the special case of small root partitions, such that > softupdates inability to make empty space available quickly can make the > difference between a major operation's success or failure. > > This is almost impossible on a 1.8Gb root partition. [sorry, cannot resist...] Once upon a time, a month or so ago, there were ~30G of free space on our 130G filesystem (with softupdates). An important application that was going to create a ~35G file was running. It already written out 1G or so. My colleague called me and sayed: "I removed a 10G of files TWO HOURS ago and the space didn't free up yet!!! The free space isn't going to appear!!! What do we do now???" Well, after I stopped the application with kill -STOP, and temporary killed off another I/O consuming program, the free space started to appear and after several minutes there were >40G of free space. I think that the problem in this particular case was inability of the syncer to run as fast as it supposed to. It is assummed that syncer fsync 1/30 of all files and process the softupdates worklist every second. If there are several I/O bound processes running, the syncer will not have enough I/O bandwidth to do this job in the required speed. Perhaps running several syncer processes could help. (OTOH, the machine in question is running a quite old version of FreeBSD-CURRENT, it is possible things are already better. I don't see serious changes in softupdates code from that moment, tough. It is also possible that the machine is mistuned in some way, but I don't know how :-() Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 14:58:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2A79314D75; Sat, 9 Oct 1999 14:58:24 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p29-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.126]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id GAA03718; Sun, 10 Oct 1999 06:58:13 +0900 (JST) Message-ID: <37FFB9FA.F2CBFF04@newsguy.com> Date: Sun, 10 Oct 1999 06:56:10 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Poul-Henning Kamp Cc: "Brian F. Feldman" , current@FreeBSD.ORG Subject: Re: maxphys = 0?? References: <10693.939468246@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message , "Bria > n F. Feldman" writes: > >On Sat, 9 Oct 1999, Poul-Henning Kamp wrote: > > > >> Well, there are two options, either your sources are not up to date, > >> or your config is very special in some way... I tried again. My sources are now dated from this morning's pnpparse.c breakage, so we can be sure of it's updatedness. > What does your /etc/fstab look like ? I would also like to see a > dmesg output. And here is fstab, dmesg and kernel configuration file. # Device Mountpoint FStype Options Dump Pass# /dev/ad0s2b none swap sw 0 0 /dev/ad0s2a / ufs rw 1 1 /dev/ad0s2f /usr ufs rw 1 3 /dev/ad0s2e /var ufs rw 2 2 /dev/ad0s1 /dos msdos rw 0 0 proc /proc procfs rw 0 0 kern /kern kernfs rw 0 0 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Fri Oct 8 18:11:32 JST 1999 root@daniel.sobral:/usr/src/sys/compile/DCS Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping = 0 Features=0x8001bf AMD Features=0x400<> real memory = 100663296 (98304K bytes) avail memory = 94580736 (92364K bytes) Preloaded elf kernel "kernel" at 0xc02b2000. Preloaded elf module "splash_bmp.ko" at 0xc02b209c. Preloaded elf module "vesa.ko" at 0xc02b2140. Preloaded splash_image_data "/boot/chuck_nebula.bmp" at 0xc02b21dc. VESA: v2.0, 1920k memory, flags:0x0, mode table:0xc02a0062 (1000022) VESA: MagicGraph 128XD 40K SVGA BIOS apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 pcic0: at device 10.0 on pci0 pcic1: at device 10.1 on pci0 vga-pci0: irq 11 at device 18.0 on pci0 ata-pci0: at device 20.0 on pci0 ata-pci0: Busmastering DMA not enabled ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pccard0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcm0: at irq 5 drq 1 flags 0x10 on isa0 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 pcic: pccard bridge VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 3 pccard: initalizing drivers: ad0: ATA-3 disk at ata0 as master ad0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, PIO Creating DISK ad0 Creating DISK wd0 acd0: CDROM drive at ata1 as master acd0: read 3445KB/s (3445KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked changing root device to wd0s2a WARNING: / was not properly dismounted pccard: card inserted, slot 1 WARNING: #ad/0x30005 maxphys = 0 ??WARNING: #ad/0x30004 maxphys = 0 ?? syncing disks... done Rebooting... Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Oct 10 06:20:59 JST 1999 root@daniel.sobral:/usr/src/sys/compile/DCS Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6tm w/ multimedia extensions (233.87-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping = 0 Features=0x8001bf AMD Features=0x400<> real memory = 100663296 (98304K bytes) avail memory = 94584832 (92368K bytes) Preloaded elf kernel "kernel" at 0xc02b2000. Preloaded elf module "splash_bmp.ko" at 0xc02b209c. Preloaded elf module "vesa.ko" at 0xc02b2140. Preloaded splash_image_data "/boot/chuck_nebula.bmp" at 0xc02b21dc. VESA: v2.0, 1920k memory, flags:0x0, mode table:0xc02a0062 (1000022) VESA: MagicGraph 128XD 40K SVGA BIOS apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 pcic0: at device 10.0 on pci0 pcic1: at device 10.1 on pci0 vga-pci0: irq 11 at device 18.0 on pci0 ata-pci0: at device 20.0 on pci0 ata-pci0: Busmastering DMA not enabled ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pccard0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcm0: at irq 5 drq 1 flags 0x10 on isa0 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A pcic: pccard bridge VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 3 pccard: initalizing drivers: ad0: ATA-3 disk at ata0 as master ad0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, PIO Creating DISK ad0 Creating DISK wd0 acd0: CDROM drive at ata1 as master acd0: read 3445KB/s (3445KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked changing root device to wd0s2a pccard: card inserted, slot 1 WARNING: #ad/0x30005 si_iosize_max=0, using DFLTPHYS. WARNING: #ad/0x30004 si_iosize_max=0, using DFLTPHYS. The above warnings are shown at fsck time. # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.141 1999/01/01 08:09:57 peter Exp $ machine "i386" cpu "I586_CPU" cpu "I686_CPU" ident DCS maxusers 32 makeoptions DEBUG="-g" #controller acpi0 options "CPU_WT_ALLOC" options "NO_F00F_HACK" options "NO_MEMORY_HOLE" options MSGBUF_SIZE=20480 options SC_ALT_MOUSE_IMAGE #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options KERNFS options SOFTUPDATES options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] #options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options _KPOSIX_VERSION=199309L options DDB # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 #controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" irq 6 drq 2 disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 #options "CMD640" # work around CMD640 chip deficiency #controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xe0ffe0ff #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller ata0 device atadisk0 device atapicd0 #controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xe0ffe0ff #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 #options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM #device acd0 #IDE CD-ROM #device wcd0 #device wfd0 #IDE Floppy (e.g. LS-120) # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. #controller ncr0 #controller ahb0 #controller ahc0 #controller isp0 # This controller offers a number of configuration options, too many to # document here - see the LINT file in this directory and look up the # dpt0 entry there for much fuller documentation on this. #controller dpt0 #controller adv0 at isa? port ? cam irq ? #controller adw0 #controller bt0 at isa? port ? cam irq ? #controller aha0 at isa? port ? cam irq ? #controller aic0 at isa? port 0x340 bio irq 11 #controller scbus0 #device da0 #device sa0 #device pass0 #device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 #device mcd0 at isa? port 0x300 bio irq 10 #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 options ATKBD_DFLT_KEYMAP makeoptions ATKBD_DFLT_KEYMAP="jp.106" device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? #options VESA options SC_HISTORY_SIZE=1000 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port IO_KBD conflicts irq 1 #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at nexus? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at nexus? flags 0x00 # 0x31 # Advanced Power Management controller pnp0 #controller snd0 #device sb0 at isa? port 0x220 irq 5 conflicts drq 1 #device sbxvi0 at isa? drq 5 conflicts #device sbmidi0 at isa? port 0x300 conflicts #device opl0 at isa? port 0x388 conflicts device pcm0 at isa? port ? irq 5 drq 1 flags 0x10 #device pcm0 device pca0 at isa? port IO_TIMER1 # PCCARD (PCMCIA) support controller card0 device pcic0 at card? device pcic1 at card? # You may need to reset all pccards after resuming options PCIC_RESUME_RESET # reset after resume device sio0 at isa? port "IO_COM1" flags 0x10 irq 4 #device sio1 at isa? port "IO_COM2" irq 3 #device sio2 at isa? disable port "IO_COM3" irq 5 #device sio3 at isa? disable port "IO_COM4" irq 9 # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device de0 #device fxp0 #device mx0 #device pn0 #device rl0 #device tl0 #device tx0 #device vr0 #device vx0 #device wb0 #device xl0 #device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 #device ep0 at isa? port 0x300 net irq 10 #device ex0 at isa? port? net irq? #device fe0 at isa? port 0x300 net irq ? #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 net irq 10 drq 0 #device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device cs0 at isa? port 0x300 net irq ? pseudo-device loop pseudo-device ether #pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 8 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn 2 # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # # The INVARIANTS option is used in a number of source files to enable # extra sanity checking of internal structures. This support is not # enabled by default because of the extra time it would take to check # for these conditions, which can only occur as a result of # programming errors. # options INVARIANTS # # The INVARIANT_SUPPORT option makes us compile in support for # verifying some of the internal structures. It is a prerequisite for # 'INVARIANTS', as enabling 'INVARIANTS' will make these functions be # called. The intent is that you can set 'INVARIANTS' for single # source files (by changing the source file or specifying it on the # command line) if you have 'INVARIANT_SUPPORT' enabled. # options INVARIANT_SUPPORT # This provides support for System V shared memory. # options SYSVSHM options SYSVSEM options SYSVMSG # The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpf 8 #Berkeley packet filter -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 15: 1:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 5B9C61508D; Sat, 9 Oct 1999 15:01:03 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id AAA12461; Sun, 10 Oct 1999 00:00:25 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Daniel C. Sobral" Cc: "Brian F. Feldman" , current@FreeBSD.ORG Subject: Re: maxphys = 0?? In-reply-to: Your message of "Sun, 10 Oct 1999 06:56:10 +0900." <37FFB9FA.F2CBFF04@newsguy.com> Date: Sun, 10 Oct 1999 00:00:25 +0200 Message-ID: <12459.939506425@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Meanwhile the mystery has been solved. I was a miscommunication between sos and me. He only committed one half of the fix for this issue. He has now committed the rest along with the latest version of his ata drivers (he claims :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 15: 3:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 0902C15431 for ; Sat, 9 Oct 1999 15:03:10 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id AAA07616 for freebsd-current@freebsd.org; Sun, 10 Oct 1999 00:03:06 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id B3C57885C; Sat, 9 Oct 1999 23:48:34 +0200 (CEST) Date: Sat, 9 Oct 1999 23:48:34 +0200 From: Ollivier Robert To: FreeBSD Current Subject: Re: staroffice Message-ID: <19991009234834.A32126@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Randy Bush: > o unzip setup.zip to someplace comfortable Don't both with that. use "export LD_LIBRARY_PATH=/tmp/sv001.tmp:." before running the setup binary. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 15:11:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 597B71555F for ; Sat, 9 Oct 1999 15:11:36 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11a4i8-0000B1-00; Sat, 09 Oct 1999 15:11:28 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Sean O'Connell" Cc: FreeBSD Current Subject: Re: lconfig cores [ was: staroffice ] References: <19991009155942.D795@stat.Duke.EDU> Message-Id: Date: Sat, 09 Oct 1999 15:11:28 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> # /compat/linux/sbin/ldconfig >>> Segmentation fault (core dumped) >>> >>> could it be that i need more compat libs than 22? >> >> I cannot swear (or attest) to this, but I recall there being >> a problem with the realtime threads and SMP... am I off-base? >> I thought that StarOffice was hosed on dual processor kernels >> (or at least the installation). Someone posted awhile back about >> doing the install on a UP kernel and then rebooting SMP... > > whoops! indeed, the host is smp. > > will try. nope. made non-smp kernel by commenting out # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): options NCPU=2 # number of CPUs options NBUS=4 # number of busses options NAPIC=2 # number of IO APICs options NINTR=24 # number of INTs rebooted that kernel # /compat/linux/sbin/ldconfig Segmentation fault (core dumped) randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 15:16:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from volatile.by-tor.tacorp.net (ppp78-220.cpis.net [206.155.220.107]) by hub.freebsd.org (Postfix) with ESMTP id 8A6A614D9B for ; Sat, 9 Oct 1999 15:16:31 -0700 (PDT) (envelope-from by-tor@volatile.by-tor.tacorp.net) Received: (from by-tor@localhost) by volatile.by-tor.tacorp.net (8.9.3/8.9.3) id SAA75841; Sat, 9 Oct 1999 18:16:28 -0400 (EDT) (envelope-from by-tor) Date: Sat, 9 Oct 1999 18:16:27 -0400 (EDT) From: Wes Morgan X-Sender: by-tor@volatile.by-tor.tacorp.net To: current@freebsd.org Subject: libpanel status Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently, the libncurses source tree was updated to a 5.0 prerelease snapshot, which is great. However, one app that I develop also uses the panels library on top of the regular ncurses lib. As it is, the panel library is incompatible with the ncurses 5.0 library (at least, the 5.0 panel lib) and its a bit of a pain to fix symlinks every time i make world. And FWIW I don't use the ncurses port because (as is the case with some ports) it installs into freakish locations and no sir I just don't like it (plus its only 4.2). So my question would be, how come it isnt updated? WM -- The difference between genius and stupidity is that genius has its limits. Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 17:50:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 2E91A150C3 for ; Sat, 9 Oct 1999 17:50:35 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11a7C7-0008jF-00 for freebsd-current@freebsd.org; Sat, 09 Oct 1999 17:50:35 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: breakage in libgcc? Message-Id: Date: Sat, 09 Oct 1999 17:50:35 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG just cvsupped echo '#include ' >> config.h echo '#include "i386/xm-i386.h"' > tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Signal 12 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 17:54:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles560.castles.com [208.214.165.124]) by hub.freebsd.org (Postfix) with ESMTP id D7B1D150C3 for ; Sat, 9 Oct 1999 17: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.9.3/8.8.8) with ESMTP id RAA02284; Sat, 9 Oct 1999 17:46:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910100046.RAA02284@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Randy Bush Cc: FreeBSD Current Subject: Re: breakage in libgcc? In-reply-to: Your message of "Sat, 09 Oct 1999 17:50:35 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Oct 1999 17:46:55 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > just cvsupped Your system; I just finished a world not five minutes ago. Suspect the usual. > echo '#include ' >> config.h > echo '#include "i386/xm-i386.h"' > tconfig.h > echo '#include "i386/i386.h"' > tm.h > echo '#include "i386/att.h"' >> tm.h > echo '#include "i386/freebsd.h"' >> tm.h > echo '#include "i386/perform.h"' >> tm.h > cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > *** Signal 12 > > Stop in /usr/src/gnu/lib/libgcc. > *** Error code 1 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 17:56:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 7B96614D92 for ; Sat, 9 Oct 1999 17:56:15 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11a7HR-00097M-00; Sat, 09 Oct 1999 17:56:05 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: FreeBSD Current Subject: Re: breakage in libgcc? References: <199910100046.RAA02284@dingo.cdrom.com> Message-Id: Date: Sat, 09 Oct 1999 17:56:05 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> just cvsupped > Your system; I just finished a world not five minutes ago. Suspect the > usual. ok. doing a make clean now randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 9 20:57:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 717E514D8C for ; Sat, 9 Oct 1999 20:57:24 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id XAA76886; Sat, 9 Oct 1999 23:57:13 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sat, 9 Oct 1999 23:57:12 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Mike Smith Cc: Randy Bush , FreeBSD Current Subject: Re: breakage in libgcc? In-Reply-To: <199910100046.RAA02284@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 9 Oct 1999, Mike Smith wrote: > > just cvsupped > > Your system; I just finished a world not five minutes ago. Suspect the > usual. > Suspect that you need a newer kernel before you can build the world. > > *** Signal 12 > > > > Stop in /usr/src/gnu/lib/libgcc. > > *** Error code 1 > > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message