From owner-freebsd-current Sun Nov 12 4:55:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 9A45537B479 for ; Sun, 12 Nov 2000 04:55:38 -0800 (PST) Received: by freesbee.wheel.dk (Postfix, from userid 1002) id 193693E59; Sun, 12 Nov 2000 13:55:37 +0100 (CET) Date: Sun, 12 Nov 2000 13:55:37 +0100 From: "Niels Chr. Bank-Pedersen" To: current@freebsd.org Subject: panic - probably aic7810/398X related Message-ID: <20001112135536.B11660@bank-pedersen.dk> Mail-Followup-To: "Niels Chr. Bank-Pedersen" , current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday I decided to upgrade my home server from it's PRE_SMPNG state to -current, but now it panics just after detecting the aic7810 RAID controller (though unsupported, the box booted happily on an PRE_SMPNG kernel). The 398X adapter is one of the cards that doesn't work with AHC_ALLOW_MEMIO (as I understand it because of the PCI-PCI bridge) so I don't know if the recent changes here has something to do with it. -current: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sun Nov 12 12:39:35 CET 2000 root@home.somewhere.dk:/usr/obj/usr/src/sys/MAIL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 166193999 Hz CPU: Pentium/P54C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 126603264 (123636K bytes) Preloaded elf kernel "kernel" at 0xc03d4000. Preloaded elf module "vinum.ko" at 0xc03d40a8. npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 7.1 pcib1: at device 9.0 on pci0 pci1: on pcib1 ahc0: port 0xd800-0xd8ff mem 0xf9000000-0xf9000fff irq 9 at device 4.0 on pci1 aic7870: Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: port 0xd400-0xd4ff mem 0xfb000000-0xfb1fffff,0xf8800000-0xf8800fff irq 11 at device 5.0 on pci1 RAID functionality unsupported Fatal trap 12: page fault while in kernel mode fault virtual address = 0x432 fault code = supervisor read, page not present instruction pointer = 0x8:0xc013656b stack pointer = 0x10:0xc03e8e30 frame pointer = 0x10:0xc03e8e38 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 = 0 (swapper) kernel: type 12 trap, code=0 Stopped at ahc_fini_scbdata+0xb: movzbl 0x432(%esi),%eax db> trace ahc_fini_scbdata(c0737000) at ahc_fini_scbdata+0xb ahc_free(c0737000,c0ec8080,c0efa380,c0efa180,c0283888) at ahc_free+0xd ahc_pci_attach(c0efa180,c0efa180,c0efa800,c0efa380,0) at ahc_pci_attach+0xea device_probe_and_attach(c0efa180) at device_probe_and_attach+0x8e bus_generic_attach(c0efa380,c0efa380,c0efac00,c0efa800,0) at bus_generic_attach+0x16 device_probe_and_attach(c0efa380) at device_probe_and_attach+0x8e bus_generic_attach(c0efa800,c0efa800,c0efa800,c026a65f,ffffffff) at bus_generic_attach+0x16 pcib_attach(c0efa800,c0efa800,c0efac80,c0efac00,0) at pcib_attach+0x9c device_probe_and_attach(c0efa800) at device_probe_and_attach+0x8e bus_generic_attach(c0efac00,c0efac00,c0efad80,c0efac80,0) at bus_generic_attach+0x16 device_probe_and_attach(c0efac00) at device_probe_and_attach+0x8e bus_generic_attach(c0efac80,c0efac80,c027a1b8,0,c0efac80) at bus_generic_attach+0x16 nexus_pcib_attach(c0efac80,c0efac80,c0efad80,c0efad80,0) at nexus_pcib_attach+0x1f device_probe_and_attach(c0efac80) at device_probe_and_attach+0x8e bus_generic_attach(c0efad80,c0ee4080,c0738e00,c03e8fc0,c016a6ca) at bus_generic_attach+0x16 nexus_attach(c0efad80,c0efad80,c02942d0,3ed000,0) at nexus_attach+0xe device_probe_and_attach(c0efad80) at device_probe_and_attach+0x8e root_bus_configure(c0738e00,c02737ac,0) at root_bus_configure+0x16 configure(0,3e6c00,3e6000,0,c011d232) at configure+0x33 mi_startup() at mi_startup+0x68 begin() at begin+0x29 db> From a working PRE_SMPNG kernel: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Thu Nov 9 02:18:13 CET 2000 root@home.somewhere.dk:/usr/obj/usr/src/sys/MAIL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 166193968 Hz CPU: Pentium/P54C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 127541248 (124552K bytes) Preloaded elf kernel "kernel.ko" at 0xc02f0000. Preloaded elf module "randomdev.ko" at 0xc02f00a0. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 7.1 pcib1: at device 9.0 on pci0 pci1: on pcib1 ahc0: port 0xd800-0xd8ff mem 0xf9000000-0xf9000fff irq 9 at device 4.0 on pci1 ahc0: aic7870 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: port 0xd400-0xd4ff mem 0xfb000000-0xfb1fffff,0xf8800000-0xf8800fff irq 11 at device 5.0 on pci1 RAID functionality unsupported device_probe_and_attach: ahc1 attach returned 6 ahc2: port 0xd000-0xd0ff mem 0xf8000000-0xf8000fff irq 9 at device 8.0 on pci1 ahc2: aic7870 Wide Channel B, SCSI Id=7, 16/255 SCBs ahc3: port 0xc800-0xc8ff mem 0xf7800000-0xf7800fff irq 9 at device 12.0 on pci1 ahc3: aic7870 Wide Channel C, SCSI Id=7, 16/255 SCBs pci0: at 10.0 irq 12 ahc4: port 0xb800-0xb8ff mem 0xf6800000-0xf6800fff irq 10 at device 11.0 on pci0 ahc4: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xb400-0xb47f mem 0xf6000000-0xf600007f irq 11 at device 12.0 on pci0 xl0: Ethernet address: 00:50:04:65:c5:3e miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources Waiting 5 seconds for SCSI devices to settle ahc4:A:6: refuses synchronous negotiation. Using asynchronous transfers ahc4:A:6: refuses synchronous negotiation. Using asynchronous transfers sa0 at ahc4 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers da7 at ahc4 bus 0 target 4 lun 0 da7: Fixed Direct Access SCSI-2 device da7: 10.000MB/s transfers (10.000MHz, offset 15) da7: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) [...] da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15) da1: 4303MB (8813870 512 byte sectors: 255H 63S/T 548C) Config: machine i386 cpu I586_CPU ident MAIL maxusers 128 #hints "MAIL.hints" options INET options FFS options FFS_ROOT options NFS options PROCFS options COMPAT_43 options SCSI_DELAY=5000 options UCONSOLE options SYSVSHM options SYSVMSG options SYSVSEM options NO_F00F_HACK options SOFTUPDATES options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options SC_HISTORY_SIZE=1024 options DDB device isa device pci device fdc device ahc device scbus device da device sa device cd device pass device atkbdc 1 device atkbd device vga device splash device sc 1 device npx device sio device ppc device ppbus device lpt device miibus device xl device loop device ether device pty device gzip device bpf device random TIA, /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 12 5: 9:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.ciac.jl.cn (unknown [202.98.16.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E8BE37B4C5 for ; Sun, 12 Nov 2000 05:08:37 -0800 (PST) Received: from 11 ([159.226.123.49]) by ns.ciac.jl.cn (8.9.1/8.9.1) with SMTP id VAA11908 for ; Sun, 12 Nov 2000 21:00:56 +0800 (CST) Message-ID: <005701c04caa$55127c40$317be29f@11> From: "S.W.Liu" To: Subject: How to set AC'97 on Board Sound sound card? Date: Sun, 12 Nov 2000 21:13:21 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG TXkgc3lzdGVtIGNhbiByZWNvZ25pemUgbXkgVklBIEFDOTcgb24gYm9hcmQgc291bmQgY2FyZC4g SSBjYW4gdXNlIGNhdCAvZGV2L3NuZHN0YXQgdG8gc2VlIG15IHNvdW5kIGNhcmQgaW5mb3JtYXRp b24uIEJ1dCB3aHkgaSBjYW5uJ3QgcGxheSBhbnkgc291bmQgPw0K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 12 5: 9:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from bsd.pbrun.com (sc-24-165-84-91.socal.rr.com [24.165.84.91]) by hub.freebsd.org (Postfix) with ESMTP id 6B1FB37B479 for ; Sun, 12 Nov 2000 05:09:54 -0800 (PST) Received: from localhost (gross@localhost) by bsd.pbrun.com (8.11.0/8.11.0) with ESMTP id eACDD5p03571 for ; Sun, 12 Nov 2000 05:13:07 -0800 (PST) Date: Sun, 12 Nov 2000 05:13:05 -0800 (PST) From: Glendon Gross To: current@freebsd.org Subject: AWE-64 no longer detected... 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 my last cvsup, my Soundblaster AWE-64 card is no longer detected. unknown: PXE build?

Does anyone know of any current issues with = PXE?  I've searched the mailing lists and I don't see any mention = of a problem similar to mine.

I'm running FreeBSD-CURRENT from 2000 09 15 on a = server.  The client has an Intel 21143 based ethernet card that = claims it has PXE 2.0 (Build 74) support. I've setup bootp/tftp on the = server which the client successfully uses to pull down the 'pxeboot' = file.  After the client retrieves pxeboot it just hangs.  = There is no further output from the machine.

Does anyone know which particular build of PXE 2.0 = works with pxeboot?  Or is this even a problem with my = firmware?

Thanks,
Jeff

------_=_NextPart_001_01C04E7D.5DFB5630-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 14 13: 4:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 955C137B479 for ; Tue, 14 Nov 2000 13:04:20 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAEL4IR13427 for ; Tue, 14 Nov 2000 14:04:19 -0700 (MST) (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 OAA50097 for ; Tue, 14 Nov 2000 14:04:18 -0700 (MST) Message-Id: <200011142104.OAA50097@harmony.village.org> To: current@FreeBSD.ORG Subject: Re: "make modules" kicks the first module directory twice In-reply-to: Your message of "Tue, 14 Nov 2000 12:47:04 PST." <20001114124704.A79356@dragon.nuxi.com> References: <20001114124704.A79356@dragon.nuxi.com> <20001114121237.A78808@dragon.nuxi.com> <3A10896D.E782256@cup.hp.com> <3A1030BA.D6CB42D0@cup.hp.com> <20001113144152.A39590@dragon.nuxi.com> <3A10896D.E782256@cup.hp.com> <200011140417.VAA37024@harmony.village.org> <20001114121237.A78808@dragon.nuxi.com> <200011142027.NAA49799@harmony.village.org> Date: Tue, 14 Nov 2000 14:04:18 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001114124704.A79356@dragon.nuxi.com> "David O'Brien" writes: : [stable dropped, this should have only been in a single list to start with!!] Agreed. My summary: o We disagree about the support impact o Peter's stuff may OBE this whole thread o My change shouldn't be committed until we know it will have no support impact, or it can be fixed to be more robust. : On Tue, Nov 14, 2000 at 01:27:32PM -0700, Warner Losh wrote: : > : I'd rather take a major compile time hit and be deterministic than not. : > : > I'd rather not. We don't do an implicit make obj in the rest of the : > tree. : : It is in `make world' if /usr/obj exists. Otherwise how does all the : .o's get in /usr/obj/ ? I should have stated this more clearly. We don't have an implicit make obj anywhere else in the tree for the default "all" target. We do have it for other, special targets. : > If I go build the world, and then someone adds a new program to : > the tree, you are in the same boat. : : Nope, `make world' will DTRT. No. Not if you compile that one file. Also, make all won't do the right thing. That's my point. We have extra special targets that are all singing all dancing that do the right thing, but the plain vanilla ones act in a plain vanilla way. Again, make world isn't the default target. It is an extra special target that does special things. I've been burned by the example that I sighted. : > If you cd to that program and type make it will wind up in . rather : > than /usr/obj. : : Yes, and how many times do we have to tell people to run : ``make cleandir && make cleandir'' or : ``rm -rf /usr/obj/* ; cd /usr/src ; make cleandir '' A few, but a lot less than I'd expect :-). : > Completely deterministic, the same thing will happen every time you do : > the scenario. : : Ok, completely deterministic given enough detail -- detail which 99% of : the time will not be provided in email to the lists saying this and that : is broken. True. But it would be rare enough that people would have two different kernels, with different revs of the sources in the same source tree and that those differences would cause problems. It would sure be hard to find it, I'll grant that. I think it would be rare enough that we won't get mail on it, but I could be wrong about that. : > But before making major changes to this, let's see Peter Wemm's new : > all singing all dancing config work does for us. I'd rather see what : > he's come up with than argue further on this. : : Earlier today, I too I was wondering if his plan makes all this OBE. He sure has been silent on all of this. :-) I do think that we're all in agreement that make obj all should be changed to make obj\n make all to make the parallel case work. The rest shouldn't be committed until we have it more robust. I'll take alook to see if there's a robust way to know if we need to run make obj or not. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 14 13:20:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 3B2AA37B479 for ; Tue, 14 Nov 2000 13:20:57 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 7EC343D5; Tue, 14 Nov 2000 13:20:54 -0800 (PST) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id NAA14004; Tue, 14 Nov 2000 13:20:54 -0800 (PST) Message-ID: <3A11ACB6.C11C5072@cup.hp.com> Date: Tue, 14 Nov 2000 16:20:54 -0500 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Cc: Makoto MATSUSHITA Subject: Re: RQ review: [was: Re: "make modules" kicks the first module directory twice] References: <20001113195111R.matusita@jp.FreeBSD.org> <20001113095855.C38404@dragon.nuxi.com> <3A103875.3555E3D4@cup.hp.com> <20001114095225T.matusita@jp.FreeBSD.org> <3A10B967.C3301113@cup.hp.com> <20001114121517.B78808@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: > > > > modules-depend: > > > @mkdir -p ${.OBJDIR}/modules > > > ! cd $S/modules; env ${MKMODULESENV} ${MAKE} obj > > > ! env ${MKMODULESENV} ${MAKE} depend > > This is broken for non -j case. Yes, this was known. The right diff was given at the beginning of the message including the comment that the original patch had this breakage :-) -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 14 13:27:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1FF4037B479; Tue, 14 Nov 2000 13:27:20 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA78999; Tue, 14 Nov 2000 14:27:18 -0700 (MST) (envelope-from ken) Date: Tue, 14 Nov 2000 14:27:18 -0700 From: "Kenneth D. Merry" To: net@FreeBSD.ORG Subject: new zero copy sockets and NFS snapshot Message-ID: <20001114142718.A78985@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ -arch and -current BCC'ed for wider coverage, please direct followups to -net and/or me ] I have put a new copy of the zero copy sockets and NFS patches, against -current as of early November 14th, 2000, here: http://people.FreeBSD.ORG/~ken/zero_copy/ Questions, comments and feedback are welcome. Besides being generated against a newer version of -current, the following things have changed in the new patches posted above: - The "localhost panic" problem has hopefully been fixed. The fix was to avoid page-flipping pages with a wire count greater than 0. I believe this is the right fix, but I would welcome feedback from someone more familiar with the VM system. - The new external mbuf code has been integrated. As of this release, there are no known problems with the code. If anyone wants to challenge that, I'll gladly accept bug reports, code comments, etc. :) For those of you who missed the previous messages about this code (that went out to -net, -arch and -current), here's a quick list of what is included in the code: - Zero copy send and receive code, written by Drew Gallatin . - Zero copy NFS code, written by Drew Gallatin. - Header splitting firmware for Alteon's Tigon II boards (written by me), based on version 12.4.11 of their firmware. This is used in combination with the zero copy receive code to guarantee that the payload of TCP or UDP packet is placed into a page-aligned buffer. - Alteon firmware debugging ioctls and supporting routines for the Tigon driver (also written by me). This will help anyone who is doing firmware development under FreeBSD for the Tigon boards. The Alteon header splitting and debugging code was written for Pluto Technologies (www.plutotech.com), which kindly agreed to let me release the code. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 14 13:34:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id A7E3C37B479 for ; Tue, 14 Nov 2000 13:34:18 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAELYGR13659 for ; Tue, 14 Nov 2000 14:34:17 -0700 (MST) (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 OAA50593 for ; Tue, 14 Nov 2000 14:34:16 -0700 (MST) Message-Id: <200011142134.OAA50593@harmony.village.org> To: current@freebsd.org Subject: Build errors in latest -current Date: Tue, 14 Nov 2000 14:34:16 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK. Maybe I'm just being stupid... But I've had a buildworld fail twice now in build secure/libcrypto with a syntax error. Is this known, or do I need a better bug report than this vauge message? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 14 13:51: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (roaming.cacheboy.net [203.56.168.69]) by hub.freebsd.org (Postfix) with ESMTP id 2365637B479; Tue, 14 Nov 2000 13:51:02 -0800 (PST) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id eAELoxr04292; Tue, 14 Nov 2000 22:50:59 +0100 (CET) (envelope-from adrian) Date: Tue, 14 Nov 2000 22:50:59 +0100 From: Adrian Chadd To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: Current has hosed the i8254 timecounter... Message-ID: <20001114225059.B4195@roaming.cacheboy.net> References: <4113.974156204@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <4113.974156204@critter>; from phk@FreeBSD.ORG on Mon, Nov 13, 2000 at 11:56:44PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 13, 2000, Poul-Henning Kamp wrote: > > It seems that something recently toasted the quasi-magic i8254 timecounter > code to the point of unusability. > > On my laptop I run a ntpdate every minute, and the result looks like this: > I'm seeing something similar with -current on this laptop here. Magically, if I jiggle the mouse whilst playing an mp3, things start to skip and the clock goes *way* off way (sometimes by a few seconds in a few seconds. :) Adrian -- Adrian Chadd "Programming is like sex: One mistake and you have to support for a lifetime." -- rec.humor.funny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 14 13:55:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id E1AED37B479; Tue, 14 Nov 2000 13:55:39 -0800 (PST) Received: from fwd03.sul.t-online.com by mailout06.sul.t-online.com with smtp id 13vo2y-0008FE-04; Tue, 14 Nov 2000 22:55:20 +0100 Received: from server.rock.net (340029380333-0001@[62.158.15.14]) by fwd03.sul.t-online.com with esmtp id 13vo2n-1CmCZsC; Tue, 14 Nov 2000 22:55:09 +0100 Received: from t-online.de (server [172.23.7.1]) by server.rock.net (8.9.3+Sun/8.9.3/Rock) with ESMTP id WAA06457; Tue, 14 Nov 2000 22:54:44 +0100 (MET) Message-ID: <3A11B4A4.6503FB73@t-online.de> Date: Tue, 14 Nov 2000 22:54:44 +0100 From: Daniel Rock X-Mailer: Mozilla 4.7 [de] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: Warner Losh Cc: current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: ISA PnP resource allocation References: <3A0B074D.4413FDB1@t-online.de> <200011122030.NAA00596@harmony.village.org> Content-Type: multipart/mixed; boundary="------------EDAA6796BB99784501A2885F" X-Sender: 340029380333-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dies ist eine mehrteilige Nachricht im MIME-Format. --------------EDAA6796BB99784501A2885F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Warner Losh schrieb: > > In message <3A0B074D.4413FDB1@t-online.de> Daniel Rock writes: > : I already filed a PR for this problem but my first solution was a real > : hack (kern/21461). > : > : [another solution would be to introduce another flag for > : rman_reserve_resource() not to search for alternate regions. > > Would the alignment stuff I added for cardbus help any? I think, my patch basically uses now the same alignment options from the resource manager like cardbus does now. I have cleaned up the code a little bit: Now the code uses the rman_get_XXX() macros and also checks if the region returned is below the end mark. Daniel --------------EDAA6796BB99784501A2885F Content-Type: text/plain; charset=us-ascii; name="sys.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="sys.diff" Index: sys/isa/isa_common.c =================================================================== RCS file: /data/cvs/src/sys/isa/isa_common.c,v retrieving revision 1.18 diff -u -r1.18 isa_common.c --- sys/isa/isa_common.c 2000/07/12 00:42:08 1.18 +++ sys/isa/isa_common.c 2000/11/14 21:27:34 @@ -133,31 +133,30 @@ result->ic_nmem = config->ic_nmem; for (i = 0; i < config->ic_nmem; i++) { u_int32_t start, end, size, align; - for (start = config->ic_mem[i].ir_start, - end = config->ic_mem[i].ir_end, - size = config->ic_mem[i].ir_size, - align = config->ic_mem[i].ir_align; - start + size - 1 <= end; - start += align) { - bus_set_resource(child, SYS_RES_MEMORY, i, - start, size); - res[i] = bus_alloc_resource(child, - SYS_RES_MEMORY, &i, - 0, ~0, 1, 0 /* !RF_ACTIVE */); - if (res[i]) { - result->ic_mem[i].ir_start = start; - result->ic_mem[i].ir_end = start + size - 1; - result->ic_mem[i].ir_size = size; - result->ic_mem[i].ir_align = align; + + start = config->ic_mem[i].ir_start; + end = config->ic_mem[i].ir_end; + size = config->ic_mem[i].ir_size; + align = config->ic_mem[i].ir_align; + if(!align) + align = 1; + bus_set_resource(child, SYS_RES_MEMORY, i, + start, size); + res[i] = bus_alloc_resource(child, + SYS_RES_MEMORY, &i, + 0, ~0, 1, + rman_make_alignment_flags(align)); + if (res[i]) { + if(rman_get_start(res[i]) > end) { + success = 0; break; } + result->ic_mem[i].ir_start = rman_get_start(res[i]); + result->ic_mem[i].ir_end = rman_get_end(res[i]); + result->ic_mem[i].ir_size = rman_get_size(res[i]); + result->ic_mem[i].ir_align = align; } - - /* - * If we didn't find a place for memory range i, then - * give up now. - */ - if (!res[i]) { + else { success = 0; break; } @@ -197,31 +196,31 @@ result->ic_nport = config->ic_nport; for (i = 0; i < config->ic_nport; i++) { u_int32_t start, end, size, align; - for (start = config->ic_port[i].ir_start, - end = config->ic_port[i].ir_end, - size = config->ic_port[i].ir_size, - align = config->ic_port[i].ir_align; - start + size - 1 <= end; - start += align) { - bus_set_resource(child, SYS_RES_IOPORT, i, - start, size); - res[i] = bus_alloc_resource(child, - SYS_RES_IOPORT, &i, - 0, ~0, 1, 0 /* !RF_ACTIVE */); - if (res[i]) { - result->ic_port[i].ir_start = start; - result->ic_port[i].ir_end = start + size - 1; - result->ic_port[i].ir_size = size; - result->ic_port[i].ir_align = align; + + start = config->ic_port[i].ir_start; + end = config->ic_port[i].ir_end; + size = config->ic_port[i].ir_size; + align = config->ic_port[i].ir_align; + if(!align) + align = 1; + + bus_set_resource(child, SYS_RES_IOPORT, i, + start, size); + res[i] = bus_alloc_resource(child, + SYS_RES_IOPORT, &i, + 0, ~0, 1, + rman_make_alignment_flags(align)); + if (res[i]) { + if(rman_get_start(res[i]) > end) { + success = 0; break; } + result->ic_port[i].ir_start = rman_get_start(res[i]); + result->ic_port[i].ir_end = rman_get_end(res[i]); + result->ic_port[i].ir_size = rman_get_size(res[i]); + result->ic_port[i].ir_align = align; } - - /* - * If we didn't find a place for port range i, then - * give up now. - */ - if (!res[i]) { + else { success = 0; break; } --------------EDAA6796BB99784501A2885F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 14 14:18:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id D283737B4C5; Tue, 14 Nov 2000 14:18:33 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp245.osd.bsdi.com [204.216.28.245]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAEMITB01664; Tue, 14 Nov 2000 14:18:29 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001114225059.B4195@roaming.cacheboy.net> Date: Tue, 14 Nov 2000 14:18:59 -0800 (PST) From: John Baldwin To: Adrian Chadd Subject: Re: Current has hosed the i8254 timecounter... Cc: freebsd-current@FreeBSD.org, Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Nov-00 Adrian Chadd wrote: > On Mon, Nov 13, 2000, Poul-Henning Kamp wrote: >> >> It seems that something recently toasted the quasi-magic i8254 timecounter >> code to the point of unusability. >> >> On my laptop I run a ntpdate every minute, and the result looks like this: >> > > I'm seeing something similar with -current on this laptop here. Magically, > if I jiggle the mouse whilst playing an mp3, things start to skip and the > clock goes *way* off way (sometimes by a few seconds in a few seconds. :) That is probably due to the random harvesting thread. Or rather, that the overhead of ithreads together with the random kthread and the load of playing mp3's is starving your CPU. Do you have any idle time at all when this happens? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 14 14:20:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn70.dh.casema.net [212.64.31.70]) by hub.freebsd.org (Postfix) with ESMTP id 2F1AE37B479 for ; Tue, 14 Nov 2000 14:20:37 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.9.3) with ESMTP id eAEMZp027927 for ; Tue, 14 Nov 2000 23:35:52 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20001114231548.00d47710@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 14 Nov 2000 23:19:20 +0100 To: freebsd-current@freebsd.org From: "Rogier R. Mulhuijzen" Subject: Re: Current has hosed the i8254 timecounter... In-Reply-To: <20001114225059.B4195@roaming.cacheboy.net> References: <4113.974156204@critter> <4113.974156204@critter> 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 >I'm seeing something similar with -current on this laptop here. Magically, >if I jiggle the mouse whilst playing an mp3, things start to skip and the >clock goes *way* off way (sometimes by a few seconds in a few seconds. :) I've had this for a few weeks now (the skipage). It has been explained as IRQ latency due to SMPNG code. Can someone make a guestimate on when this will be fixed? Also I was dd'ing the install floppies today, and when I was in X with xmms playing I got about 300-600 bytes/s transfer rate to fd0. After a reboot and being on the commandline I got 27K/s. Except when I moved my mouse, then the transfer top floppy would slow down straight away. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 14 14:59:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 6075537B4CF for ; Tue, 14 Nov 2000 14:59:42 -0800 (PST) Received: from gaborone-34.budapest.interware.hu ([195.70.52.162] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13vp37-0002kh-00; Tue, 14 Nov 2000 23:59:33 +0100 Message-ID: <3A119BFB.4F8C1A65@elischer.org> Date: Tue, 14 Nov 2000 12:09:31 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: eirvine Cc: "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: FreeBSD Foundation: Examples of FreeBSD as teaching aid/research plat References: <200011092026.eA9KQra92696@aslan.scsiguy.com> <3A0BF78E.F8FF06BB@tpgi.com.au> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG eirvine wrote: > > Hi Justin, > > You might like to take a look at some of the links > near the bottom of my (humble) home page. A little > dated, but never mind: > > http://www1.tpg.com.au/users/eirvine/ > > Eddie. > A collection of such 'good works' might not be out of place somewhere on the website once it's been collected. > > "Justin T. Gibbs" wrote: > > > > As some of you may know, I'm working on a 501(c)3 (tax exempt/non-profit) > > determination for the FreeBSD Foundation. The IRS seems to be a little > > confused about the nature of FreeBSD and we're currenlty working on > > a response to an initial determination from the IRS that was not > > favorable. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 14 20: 4:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.161.193]) by hub.freebsd.org (Postfix) with ESMTP id 7FC8237B4C5 for ; Tue, 14 Nov 2000 20:04:07 -0800 (PST) Received: from mail.vt.edu (gkar.cc.vt.edu [198.82.161.190]) by lennier.cc.vt.edu (8.11.0/8.11.0) with ESMTP id eAF446d440143 for ; Tue, 14 Nov 2000 23:04:06 -0500 (EST) Received: from muriel.penguinpowered.com ([198.82.100.195]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0G41004W7SMSWC@gkar.cc.vt.edu> for FreeBSD-current@freebsd.org; Tue, 14 Nov 2000 23:04:04 -0500 (EST) Date: Tue, 14 Nov 2000 23:04:04 -0500 (EST) From: Mike Heffner Subject: Typo in secure/lib/libcrypto/Makefile To: FreeBSD-current Message-id: MIME-version: 1.0 X-Mailer: XFMail 1.4.4 on FreeBSD Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 8bit X-Priority: 3 (Normal) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG =================================================================== RCS file: /home/ncvs/src/secure/lib/libcrypto/Makefile,v retrieving revision 1.26 retrieving revision 1.27 diff -u -p -r1.26 -r1.27 --- src/secure/lib/libcrypto/Makefile 2000/11/13 02:21:37 1.26 +++ src/secure/lib/libcrypto/Makefile 2000/11/14 22:12:02 1.27 @@ -1,4 +1,4 @@ -# $FreeBSD: src/secure/lib/libcrypto/Makefile,v 1.26 2000/11/13 +.# $FreeBSD: src/secure/lib/libcrypto/Makefile,v 1.27 2000/11/14 22:12 ^ A period before the comment somehow crept into the commit. -- Mike Heffner Blacksburg, VA ICQ# 882073 http://my.ispchannel.com/~mheffner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 14 20:24:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 5654737B4C5 for ; Tue, 14 Nov 2000 20:24:50 -0800 (PST) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.9.3/8.9.3) id XAA03848; Tue, 14 Nov 2000 23:24:43 -0500 (EST) Date: Tue, 14 Nov 2000 23:24:43 -0500 From: Mathew KANNER To: Jeff Roberson Cc: "'freebsd-current@freebsd.org'" Subject: Re: PXE build? Message-ID: <20001114232443.D1264@cs.mcgill.ca> References: <31E4B6337A4FD411BD45000102472E0C05E6DB@EMAIL_SERVER> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: Jeff Roberson's message [PXE build?] as of Tue, Nov 14, 2000 at 12:56:25PM -0800 Organization: SOCS, McGill University, Montreal, CANADA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 14, Jeff Roberson wrote: > Does anyone know of any current issues with PXE? I've searched the mailing > lists and I don't see any mention of a problem similar to mine. > > I'm running FreeBSD-CURRENT from 2000 09 15 on a server. The client has an > Intel 21143 based ethernet card that claims it has PXE 2.0 (Build 74) > support. I've setup bootp/tftp on the server which the client successfully > uses to pull down the 'pxeboot' file. After the client retrieves pxeboot it > just hangs. There is no further output from the machine. > > Does anyone know which particular build of PXE 2.0 works with pxeboot? Or > is this even a problem with my firmware? Hello Jeff, You didn't specify if you set-up NFS for the loader to fetch it's configuration and the kernel and such. Assuming you have an otherwise working PXE environment: I've had problems with Intel card at work. I'm at home now and don't remember off-hand what specific model of card or the flash version. Depending on what motherboard was used, I would see crashes and hangs in the loader when configured for tftp (with some), nfs (with others). However, recently someone on -questions referenced a flash upgrade available and I found it on the Intel web site. It fixed all my problems. --Mat > > Thanks, > Jeff -- Mathew Kanner SOCS McGill University Obtuse quote: He [not me] understands: "This field of perception is void of perception of man." -- The Quintessence of Buddhism To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 1:41:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 60ED637B479 for ; Wed, 15 Nov 2000 01:41:23 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id KAA05866; Wed, 15 Nov 2000 10:41:18 +0100 (MET) Date: Wed, 15 Nov 2000 10:41:17 +0100 (CET) From: Harti Brandt To: Ilya Naumov Cc: current@FreeBSD.ORG Subject: Re: Re[2]: if_tap and linprocfs modules are broken in -current In-Reply-To: <1410756737.20001114234750@avias.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, 14 Nov 2000, Ilya Naumov wrote: Hi, > >> when i try to kldload if_tap module, the kernel says "symbol lminor > >> undefined" and fails to load the module. for linprocfs module the > >> message is "symbol tsleep undefined". these modules are necessary for > >> VMWare 2.0 port. > >> > >> >How-To-Repeat: > >> > >> kldload if_tap > >> kldstat linprocfs > > HB> No problems here with source from today 6.00 MET. if_tap was > HB> fixed on 09/19. > > it's ok, i'm expiriencing them right now, with today's kernel/modules > (built on 13:07 MSK). > > HB> NB: there is a commit request pending for if_tap. It is currently unusable > HB> with devfs. Would be REALLY nice if a committer could look at the patch. > > i do not use devfs. anyway, the patch by Maksim Yevmenkin doesn't > help. kernel still reports "link_elf: symbol lminor undefined". > > and what's wrong with linprocfs? it seems to be broken too. Are you sure, that you don't have a stale linprocfs or if_tap in /modules or elsewhere? lminor was removed from if_tap two month ago as I already said. Go into you build directory and do a 'nm if_tap.ko | grep minor' - no lminor should be there. If it is, you have a stale source file. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 3:17:11 2000 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 29DBC37B4CF; Wed, 15 Nov 2000 03:17:06 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id WAA19098; Wed, 15 Nov 2000 22:16:51 +1100 Date: Wed, 15 Nov 2000 22:17:46 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: "make modules" kicks the first module directory twice In-Reply-To: <200011142027.NAA49799@harmony.village.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 On Tue, 14 Nov 2000, Warner Losh wrote: > make depend is already *REQUIRED* when you are updating a kernel from > an older version of the kernel. For config -r FOO kernels it isn't. It is neither necessary nor sufficient for updating. config -r removes conflicting garbage from previous builds. Removing the conflicting garbage is sufficient. `make clean' normally suffices to remove it, but there are cases where .depend itself is garbage and must be removed to unbreak `make depend'. > Even a make clean after a make depend will require that make depend be > run again. This was broken in rev.1.348 of sys/conf/files, etc. `make clean' removes the generated bus interface headers, and there are no longer enough dependencies for make(1) to know how to rebuild them. There are enough dependencies to rebuild them for `make depend', and for plain `make' when .depend doesn't exist (minor magic involving ${BEFORE_DEPEND}). .depend still doesn't contain all the dependencies on headers, because at least the generated bus interface .c files are handled too specially. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 3:24:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77]) by hub.freebsd.org (Postfix) with ESMTP id E3F8737B4C5 for ; Wed, 15 Nov 2000 03:24:49 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAFBV2F03014; Wed, 15 Nov 2000 03:31:14 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011151131.eAFBV2F03014@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jeff Roberson Cc: "'freebsd-current@freebsd.org'" Subject: Re: PXE build? In-reply-to: Your message of "Tue, 14 Nov 2000 12:56:25 PST." <31E4B6337A4FD411BD45000102472E0C05E6DB@EMAIL_SERVER> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Nov 2000 03:31:02 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does anyone know of any current issues with PXE? Some ROMs out there are pretty bad. > I've searched the mailing > lists and I don't see any mention of a problem similar to mine. > > I'm running FreeBSD-CURRENT from 2000 09 15 on a server. The client has an > Intel 21143 based ethernet card that claims it has PXE 2.0 (Build 74) > support. Are you *sure* the card is 21143-based? At any rate, the Intel PXE codebase is buggy for the 8255x chips up to build 082, so you're probably running bad code there. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 3:29: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 4040037B4C5 for ; Wed, 15 Nov 2000 03:29:01 -0800 (PST) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by avias.com (8.11.0/8.11.1) with ESMTP id eAFBSao25553; Wed, 15 Nov 2000 14:28:36 +0300 (MSK) (envelope-from camel@avias.com) Date: Wed, 15 Nov 2000 14:28:36 +0300 (MSK) From: Ilya Naumov To: Harti Brandt Cc: current@FreeBSD.ORG Subject: Re: Re[2]: if_tap and linprocfs modules are broken in -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 Wed, 15 Nov 2000, Harti Brandt wrote: > > i do not use devfs. anyway, the patch by Maksim Yevmenkin doesn't > > help. kernel still reports "link_elf: symbol lminor undefined". > > > > and what's wrong with linprocfs? it seems to be broken too. > > Are you sure, that you don't have a stale linprocfs or if_tap in /modules > or elsewhere? sorry, i forgot to remove obsolete /modules. everything's fine now. thank you. sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 3:39:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 6FB2F37B4C5 for ; Wed, 15 Nov 2000 03:39:27 -0800 (PST) Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id MAA04866 for ; Wed, 15 Nov 2000 12:39:00 +0100 From: Gilles.Guerrini@alcatel.fr Received: from frmail19.netfr.alcatel.fr (frmail19.netfr.alcatel.fr [155.132.251.19]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with SMTP id MAA14229 for ; Wed, 15 Nov 2000 12:36:01 +0100 (MET) Received: by frmail19.netfr.alcatel.fr(Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id C1256998.004004C2 ; Wed, 15 Nov 2000 12:39:15 +0100 X-Lotus-FromDomain: ALCATEL To: current@FreeBSD.ORG Message-ID: Date: Wed, 15 Nov 2000 11:51:07 +0100 Subject: fetch Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, i'm using libfetch. I want to get a file in passive mode in my local disk. If I read trace from the remote machine, the transfert is okay but i can't find my new imported file in the local disk. Can you help me to find it ? :o{ Please answer me directly, i'm not a subscriber of this list. Thank you Gilles Guerrini To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 5:45:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from hq.atm.com.pl (gate.atm.com.pl [157.25.180.50]) by hub.freebsd.org (Postfix) with ESMTP id 2E7CE37B4CF for ; Wed, 15 Nov 2000 05:45:37 -0800 (PST) Received: by gateway.hq.atm.com.pl id <14339>; Wed, 15 Nov 2000 14:45:47 +0100 From: Adam Obszynski X-Mailer: The Bat! (v1.46d) UNREG / CD5BF9353B3B7091 Reply-To: Adam Obszynski Organization: FreeBSD User! X-Priority: 3 (Normal) Message-Id: <00Nov15.144547met.14339@gateway.hq.atm.com.pl> To: freebsd-current@FreeBSD.ORG Subject: ATM - FORE PCA-200E Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit Date: Wed, 15 Nov 2000 14:45:43 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello freebsd-current, Is somebody here who using fore adapter (subject) in current tree ? how it is stable ? which signalisation are you using ? sigpvc ? spans ? uni ? maybe some LANE code were added ? -- Regards, Adam Obszyñski awo@freebsd.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 6:17:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 1AE2B37B657 for ; Wed, 15 Nov 2000 06:17:51 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAFEH9d00666; Wed, 15 Nov 2000 15:17:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Adam Obszynski Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATM - FORE PCA-200E In-Reply-To: Your message of "Wed, 15 Nov 2000 14:45:43 +0100." <00Nov15.144547met.14339@gateway.hq.atm.com.pl> Date: Wed, 15 Nov 2000 15:17:09 +0100 Message-ID: <664.974297829@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00Nov15.144547met.14339@gateway.hq.atm.com.pl>, Adam Obszynski writes: >Hello freebsd-current, > > Is somebody here who using fore adapter (subject) in current tree ? how it > is stable ? which signalisation are you using ? sigpvc ? spans ? uni ? > maybe some LANE code were added ? yes. yes. sigpvc. Not that I know off. PS: anyone looking to buy a bunch of these please contact me, I may know of a source for some cheap cards if bought in (minor) quantities. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 7:16: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id CC31D37B479 for ; Wed, 15 Nov 2000 07:15:57 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id QAA00729 for ; Wed, 15 Nov 2000 16:15:55 +0100 (MET) Date: Wed, 15 Nov 2000 16:15:55 +0100 (CET) From: Harti Brandt To: current@freebsd.org Subject: binutils commit breaks kernel builds? 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, with fresh sources from today 6:00 MET kernel builds fail. The victim is 'size' which is executed during the build and which dumps core in bfd_close() (after printing the sizes). The build breaks when done via make buildkernel, it works when I invoke make from the kernel build directory. This seem to indicate, that the 'size' built from the updated source via 'make buildworld' is broken. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 7:56:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id BBA9937B4CF for ; Wed, 15 Nov 2000 07:56:49 -0800 (PST) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "caerdonn.eurocontrol.fr", Issuer CN "CA ITM" (verified OK)) by matrix.eurocontrol.fr (Postfix/TLS) with ESMTP id 2788259F3 for ; Wed, 15 Nov 2000 16:56:49 +0100 (CET) Received: by caerdonn.eurocontrol.fr (Postfix/TLS, from userid 1193) id B58F54E14; Wed, 15 Nov 2000 16:56:48 +0100 (CET) Date: Wed, 15 Nov 2000 16:56:48 +0100 From: Ollivier Robert To: FreeBSD Current Users' list Subject: clock/apm broken in CURRENT ? Message-ID: <20001115165648.A39710@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Am I the only to have problem with the clock on a laptop using APM in CURRENT? Speaking with some people on #bsdcode apparently no. In short, the clock stops during suspend time... This is on a VAIO Z505SX running current from Nov, 8th. Any idea when this will be fixed? -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #6: Thu Aug 10 17:36:11 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 8:20:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from free.bsdshell.net (free.bsdshell.net [213.11.81.132]) by hub.freebsd.org (Postfix) with ESMTP id D23E537B4C5 for ; Wed, 15 Nov 2000 08:20:10 -0800 (PST) Received: by free.bsdshell.net (Postfix, from userid 2710) id 8947A5DF4; Wed, 15 Nov 2000 17:34:22 +0100 (CET) To: freebsd-current@freebsd.org Subject: vmwareport does not work Message-Id: <20001115163422.8947A5DF4@free.bsdshell.net> Date: Wed, 15 Nov 2000 17:34:22 +0100 (CET) From: urded@bsdshell.net (urded) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsuppped today to 4.2 beta the problem is that i cannot get the vmnet module to run properly if i issue (qfetr installation) : /usr/local/etc/rc.d/vmware.sh start i get kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon_up.ko: File exists sysctl: unknown oid 'net.link.ether.bridge_refresh' kldload: can't load if_tap.ko: File exists ifconfig: ioctl (SIOCAIFADDR): File exists what' s wrong then ? thanks a lot in advance To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 8:38: 7 2000 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 6DF6837B4CF for ; Wed, 15 Nov 2000 08:38:05 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAFGc3d20333; Wed, 15 Nov 2000 08:38:03 -0800 (PST) Date: Wed, 15 Nov 2000 08:38:03 -0800 From: Alfred Perlstein To: Gilles.Guerrini@alcatel.fr Cc: current@FreeBSD.ORG Subject: Re: fetch Message-ID: <20001115083803.H29448@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from Gilles.Guerrini@alcatel.fr on Wed, Nov 15, 2000 at 11:51:07AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Gilles.Guerrini@alcatel.fr [001115 03:39] wrote: > > > Hello, > i'm using libfetch. > I want to get a file in passive mode in my local disk. > If I read trace from the remote machine, the transfert is okay > but i can't find my new imported file in the local disk. > Can you help me to find it ? :o{ Not really, we don't have access to your system, disk or source. Perhaps if you posted a short code example we could help you find the problem. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 9:46:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (roaming.cacheboy.net [203.56.168.69]) by hub.freebsd.org (Postfix) with ESMTP id 2C80A37B4CF; Wed, 15 Nov 2000 09:46:48 -0800 (PST) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id eAFHklK06627; Wed, 15 Nov 2000 18:46:47 +0100 (CET) (envelope-from adrian) Date: Wed, 15 Nov 2000 18:46:46 +0100 From: Adrian Chadd To: John Baldwin Cc: Adrian Chadd , freebsd-current@FreeBSD.org, Poul-Henning Kamp Subject: Re: Current has hosed the i8254 timecounter... Message-ID: <20001115184646.A6612@roaming.cacheboy.net> References: <20001114225059.B4195@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from jhb@FreeBSD.org on Tue, Nov 14, 2000 at 02:18:59PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 14, 2000, John Baldwin wrote: > > I'm seeing something similar with -current on this laptop here. Magically, > > if I jiggle the mouse whilst playing an mp3, things start to skip and the > > clock goes *way* off way (sometimes by a few seconds in a few seconds. :) > > That is probably due to the random harvesting thread. Or rather, that the > overhead of ithreads together with the random kthread and the load of playing > mp3's is starving your CPU. Do you have any idle time at all when this happens? Yup, plenty. Its a fast laptop. I can get real numbers back again tomorrow. Adrian -- Adrian Chadd "Programming is like sex: One mistake and you have to support for a lifetime." -- rec.humor.funny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 10:30:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0F7F137B4CF for ; Wed, 15 Nov 2000 10:30:45 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAFIUdR18032; Wed, 15 Nov 2000 11:30:40 -0700 (MST) (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 LAA57387; Wed, 15 Nov 2000 11:30:38 -0700 (MST) Message-Id: <200011151830.LAA57387@harmony.village.org> To: Ollivier Robert Subject: Re: clock/apm broken in CURRENT ? Cc: "FreeBSD Current Users' list" In-reply-to: Your message of "Wed, 15 Nov 2000 16:56:48 +0100." <20001115165648.A39710@caerdonn.eurocontrol.fr> References: <20001115165648.A39710@caerdonn.eurocontrol.fr> Date: Wed, 15 Nov 2000 11:30:38 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001115165648.A39710@caerdonn.eurocontrol.fr> Ollivier Robert writes: : Am I the only to have problem with the clock on a laptop using APM in : CURRENT? Speaking with some people on #bsdcode apparently no. : : In short, the clock stops during suspend time... : : This is on a VAIO Z505SX running current from Nov, 8th. : : Any idea when this will be fixed? Add device pmtimer to your config file. Fixes it for me. Tell people on #bsdcode about this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 10:47:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 635A737B4C5 for ; Wed, 15 Nov 2000 10:47:09 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAFIl8R18134 for ; Wed, 15 Nov 2000 11:47:08 -0700 (MST) (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 LAA57606 for ; Wed, 15 Nov 2000 11:47:07 -0700 (MST) Message-Id: <200011151847.LAA57606@harmony.village.org> To: current@freebsd.org Subject: Bad commit? Date: Wed, 15 Nov 2000 11:47:07 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As near as I can tell on my laptop, the following change causes panics with kernel page faults. With it, my laptop panics every time on boot (although in slightly different places for my two different kernels) and without it I'm rock solid. Has anybody else seen this? Warner mckusick 2000/11/14 12:46:02 PST Modified files: sys/sys rman.h sys/kern subr_bus.c subr_rman.c Log: In preparation for deprecating CIRCLEQ macros in favor of TAILQ macros which provide the same functionality and are a bit more efficient, convert use of CIRCLEQ's in resource manager to TAILQ's. Approved by: Garrett Wollman Revision Changes Path 1.13 +3 -3 src/sys/sys/rman.h 1.83 +3 -5 src/sys/kern/subr_bus.c 1.14 +30 -35 src/sys/kern/subr_rman.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 10:53:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 78BCF37B479 for ; Wed, 15 Nov 2000 10:53:15 -0800 (PST) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.109]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id eAFIr7403502; Wed, 15 Nov 2000 20:53:08 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.1/8.9.3) with ESMTP id eAFIrB025890; Wed, 15 Nov 2000 20:53:11 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A12DB91.9186EE32@FreeBSD.org> Date: Wed, 15 Nov 2000 20:53:05 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Ollivier Robert Cc: "FreeBSD Current Users' list" Subject: Re: clock/apm broken in CURRENT ? References: <20001115165648.A39710@caerdonn.eurocontrol.fr> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert wrote: > Am I the only to have problem with the clock on a laptop using APM in > CURRENT? Speaking with some people on #bsdcode apparently no. > > In short, the clock stops during suspend time... > > This is on a VAIO Z505SX running current from Nov, 8th. > > Any idea when this will be fixed? There is entry in src/UPDATING: 20000914: The new pmtimer device is necessary for laptops. Failure to include the device will cause suspended laptops losing time when they resume. Include device pmtimer in your config file and hint.pmtimer.0.at="isa" to your /boot/device.hints file. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 11: 6: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0610837B479 for ; Wed, 15 Nov 2000 11:06:05 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAFJ63R18214; Wed, 15 Nov 2000 12:06:04 -0700 (MST) (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 MAA57753; Wed, 15 Nov 2000 12:06:03 -0700 (MST) Message-Id: <200011151906.MAA57753@harmony.village.org> Subject: Re: clock/apm broken in CURRENT ? To: Ollivier Robert , "FreeBSD Current Users' list" In-reply-to: Your message of "Wed, 15 Nov 2000 11:30:38 MST." <200011151830.LAA57387@harmony.village.org> References: <200011151830.LAA57387@harmony.village.org> <20001115165648.A39710@caerdonn.eurocontrol.fr> Date: Wed, 15 Nov 2000 12:06:03 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011151830.LAA57387@harmony.village.org> Warner Losh writes: : Add : device pmtimer : to your config file. Fixes it for me. Tell people on #bsdcode about : this. I've gone ahead and updated GENERIC with this fix. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 12:22:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from Sorcery.se (cvx-sto-1-165.ppp.netlink.se [212.242.103.69]) by hub.freebsd.org (Postfix) with ESMTP id 7BEF737B4C5 for ; Wed, 15 Nov 2000 12:22:51 -0800 (PST) Received: from localhost (nevyn@localhost) by Sorcery.se (8.11.1/8.11.1) with ESMTP id eAFLK7D36221 for ; Wed, 15 Nov 2000 21:20:08 GMT (envelope-from alastyr@home.se) X-Authentication-Warning: Sorcery.se: nevyn owned process doing -bs Date: Wed, 15 Nov 2000 21:20:06 +0000 (GMT) From: Joel Lindau X-Sender: nevyn@Sorcery.se To: FreeBSD-current@freebsd.org Subject: Unable to build world 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, When i try to build my -current world cvsupped today ( 15 nov ) i get the following errors: [ -- ] >>> stage 2: build tools -------------------------------------------------------------- cd /usr/current/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh /usr/current/src/tools/install.sh" PATH=/usr/obj/usr/current/src/i386/usr/sbin:/usr/obj/usr/current/src/i386/usr/bin:/usr/obj/usr/current/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 build-tools cd /usr/current/src/bin/sh; make build-tools cc -O2 -pipe -DSHELL -I. -I/usr/current/src/bin/sh -Wall -Wformat -c /usr/current/src/bin/sh/mkinit.c cc -O2 -pipe -DSHELL -I. -I/usr/current/src/bin/sh -Wall -Wformat -static mkinit.o -o mkinit /usr/lib/crt1.o: In function `_start': /usr/lib/crt1.o(.text+0x60): undefined reference to `_fini' /usr/lib/crt1.o(.text+0x6a): undefined reference to `_init' *** Error code 1 [ -- ] /usr/lib/crt1.o ? / Joel.L a.k.a Nevyn -- #FreeBSD.se, #unix.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 12:30:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from web-dev1.wanadoo.nl (web-dev1.wanadoo.nl [194.134.193.9]) by hub.freebsd.org (Postfix) with ESMTP id D80CE37B4CF for ; Wed, 15 Nov 2000 12:30:27 -0800 (PST) Received: (from nobody@localhost) by web-dev1.wanadoo.nl (8.9.3/8.9.3) id VAA21872; Wed, 15 Nov 2000 21:30:22 +0100 (MET) To: Subject: subscribe Message-ID: <974320222.3a12f25e76d3f@webmail.wanadoo.nl> Date: Wed, 15 Nov 2000 21:30:22 +00100 (MET) From: MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit User-Agent: Wanadoo Webmail 1.2 X-Originating-IP: 24.132.141.165 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 12:32:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77]) by hub.freebsd.org (Postfix) with ESMTP id B2ED937B4C5 for ; Wed, 15 Nov 2000 12:32:15 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAFKcYF04489; Wed, 15 Nov 2000 12:38:37 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011152038.eAFKcYF04489@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: current@freebsd.org Subject: Re: Bad commit? In-reply-to: Your message of "Wed, 15 Nov 2000 11:47:07 MST." <200011151847.LAA57606@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Nov 2000 12:38:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > As near as I can tell on my laptop, the following change causes panics > with kernel page faults. With it, my laptop panics every time on > boot (although in slightly different places for my two different > kernels) and without it I'm rock solid. > > Has anybody else seen this? Yes; I think it's broken the resource manager. > Warner > > mckusick 2000/11/14 12:46:02 PST > > Modified files: > sys/sys rman.h > sys/kern subr_bus.c subr_rman.c > Log: > In preparation for deprecating CIRCLEQ macros in favor of TAILQ > macros which provide the same functionality and are a bit more > efficient, convert use of CIRCLEQ's in resource manager to TAILQ's. > > Approved by: Garrett Wollman > > Revision Changes Path > 1.13 +3 -3 src/sys/sys/rman.h > 1.83 +3 -5 src/sys/kern/subr_bus.c > 1.14 +30 -35 src/sys/kern/subr_rman.c > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 12:37:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2045B37B4E5; Wed, 15 Nov 2000 12:37:34 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAFKbUR18728; Wed, 15 Nov 2000 13:37:31 -0700 (MST) (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 NAA58691; Wed, 15 Nov 2000 13:37:30 -0700 (MST) Message-Id: <200011152037.NAA58691@harmony.village.org> To: Mike Smith Subject: Re: Bad commit? Cc: current@freebsd.org In-reply-to: Your message of "Wed, 15 Nov 2000 12:38:34 PST." <200011152038.eAFKcYF04489@mass.osd.bsdi.com> References: <200011152038.eAFKcYF04489@mass.osd.bsdi.com> Date: Wed, 15 Nov 2000 13:37:30 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011152038.eAFKcYF04489@mass.osd.bsdi.com> Mike Smith writes: : Yes; I think it's broken the resource manager. I'm testing kirk's fix right now on the laptop in question... It boots one of the kernels that was always crashing before. Looks like we have a winner. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 13:43: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.griffel.se (mail.griffel.se [193.13.74.2]) by hub.freebsd.org (Postfix) with ESMTP id 2190737B4C5 for ; Wed, 15 Nov 2000 13:42:47 -0800 (PST) Received: from [194.47.111.210] (HELO chewie) by mail.griffel.se (CommuniGate Pro SMTP 3.3) with SMTP id 411556 for freebsd-current@freebsd.org; Wed, 15 Nov 2000 22:42:46 +0100 Message-ID: <002c01c04f44$8af29ce0$2a67a8c0@chewie.outherlimits.org> From: "Claes Leufven" To: Subject: APM problems with 5.0-20001112-CURRENT Date: Wed, 15 Nov 2000 21:42:17 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I have a Compaq Armada E500 and the apm support doesnt work. It seems that the kernel doesnt find the apm controller just that it is on the pci bus. I am using freebsd 5.0-20001112-current and have tried with both the generic kernel and my custom kernel. in the kernel configuration I have just "device apm" any one got any idea whats wrong? My dmesg output is in down under here... Regards Claes Leufven --dmesg output Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-20001112-CURRENT #4: Wed Nov 15 22:05:44 CET 2000 root@chewie.outherlimits.org:/usr/src/sys/compile/chewie Calibrating clock(s) ... TSC clock: 497464932 Hz, i8254 clock: 1193258 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 497435562 Hz CPU: Pentium III/Pentium III Xeon/Celeron (497.44-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383f9ff real memory = 67043328 (65472K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00312000 - 0x03fe7fff, 63791104 bytes (15574 pages) avail memory = 62279680 (60820K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fa000 bios32: Entry = 0xf0000 (c00f0000) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0x478 pnpbios: Found PnP BIOS data at 0xc00f5100 pnpbios: Entry = f0000:512e Rev = 1.0 pnpbios: Event flag at f5126 pnpbios: OEM ID 51b1110e Other BIOS signatures found: Preloaded elf kernel "kernel" at 0xc02f9000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02f90a8. null: random: mem: Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 00 01 00 01 00 00 00 00 22 00 00 01 7f 00 00 01 0b 01 00 01 21 01 00 01 2a 01 00 01 00 01 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 05 01 16 01 17 01 18 01 07 01 19 01 VESA: 40 mode(s) found VESA: v2.0, 8128k memory, flags:0x0, mode table:0xc029e3a2 (1000022) VESA: ATI MACH64 VESA: ATI Technologies Inc. MACH64RM 01.00 Using $PIR table, 268435454 entries at 0xc00f0970 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: physical bus=0 found-> vendor=0x8086, dev=0x7190, revid=0x03 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 3, range 32, base 50000000, size 26, enabled found-> vendor=0x8086, dev=0x7191, revid=0x03 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x104c, dev=0xac1c, revid=0x01 bus=0, slot=4, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=2 secondarybus=2 intpin=a, irq=11 map[10]: type 1, range 32, base 41100000, size 12, enabled found-> vendor=0x104c, dev=0xac1c, revid=0x01 bus=0, slot=4, func=1 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=3 secondarybus=3 intpin=a, irq=11 map[10]: type 1, range 32, base 41180000, size 12, enabled found-> vendor=0x8086, dev=0x7110, revid=0x02 bus=0, slot=7, func=0 class=06-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 bus=0, slot=7, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 4, range 32, base 00003420, size 4, enabled found-> vendor=0x8086, dev=0x7112, revid=0x01 bus=0, slot=7, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=11 map[20]: type 4, range 32, base 00003400, size 5, enabled found-> vendor=0x8086, dev=0x7113, revid=0x03 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 4, range 32, base 00004000, size 4, enabled found-> vendor=0x125d, dev=0x1978, revid=0x10 bus=0, slot=8, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 4, range 32, base 00003000, size 8, enabled found-> vendor=0x8086, dev=0x1229, revid=0x09 bus=0, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 41280000, size 12, enabled map[14]: type 4, range 32, base 00003440, size 6, enabled map[18]: type 1, range 32, base 41200000, size 17, enabled found-> vendor=0x11c1, dev=0x0445, revid=0x00 bus=0, slot=9, func=1 class=07-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 4, range 32, base 00003430, size 3, enabled map[14]: type 1, range 32, base 41300000, size 12, enabled pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: physical bus=1 found-> vendor=0x1002, dev=0x4c4d, revid=0x64 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 40000000, size 24, enabled map[14]: type 4, range 32, base 00002000, size 8, enabled map[18]: type 1, range 32, base 41000000, size 12, enabled pci1: on pcib1 pci1: (vendor=0x1002, dev=0x4c4d) at 0.0 irq 11 pcic-pci0: mem 0x41100000-0x41100fff irq 11 at device 4.0 on pci0 pcic-pci0: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq] pcic-pci0: Legacy address set to 0x3e0 PCI Config space: 00: ac1c104c 02100007 06070001 00824208 10: 41100000 020000a0 00020200 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 03c0010b 40: b1210e11 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 28049060 00000000 00000000 01001c72 90: 60640280 00000000 00000000 00000000 Cardbus Socket registers: 00: 00000000: 00000000: 30000306: 00000000: 10: 00000000: 00000000: 00000000: 00000000: ExCa registers: 00: 84 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10: 00 00 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 pcic-pci1: mem 0x41180000-0x41180fff irq 11 at device 4.1 on pci0 pcic-pci1: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq] PCI Config space: 00: ac1c104c 02100007 06070001 00824208 10: 41180000 020000a0 00030300 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 03c0010b 40: b1210e11 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 28449060 00000000 00000000 01001c72 90: 60640280 00000000 00000000 00000000 Cardbus Socket registers: 00: 00000000: 00000000: 30000306: 00000000: 10: 00000000: 00000000: 00000000: 00000000: ExCa registers: 00: 84 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10: 00 00 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x3420-0x342f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x3420 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x9 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x3428 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed uhci0: port 0x3400-0x341f irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: (vendor=0x8086, dev=0x7113) at 7.3 pci0: (vendor=0x125d, dev=0x1978) at 8.0 irq 11 fxp0: port 0x3440-0x347f mem 0x41200000-0x4121ffff,0x41280000-0x41280fff irq 11 at device 9.0 on pci0 fxp0: Ethernet address 00:d0:59:06:d5:99 bpf: fxp0 attached pci0: (vendor=0x11c1, dev=0x0445) at 9.1 irq 11 ata-: ata0 already exists, using ata2 instead ata-: ata1 already exists, using ata3 instead Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 pnpbios: 16 devices, largest 250 bytes PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0 PNP0c04: adding irq mask 0x2000 PNP0c04: end config pnpbios: handle 1 device ID PNP0c04 (040cd041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0xf0000-0xfffff, size=0x10000 PNP0c01: adding fixed memory32 range 0x100000-0x3ffffff, size=0x3f00000 PNP0c01: end config pnpbios: handle 2 device ID PNP0c01 (010cd041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 PNP0a03: end config pnpbios: handle 3 device ID PNP0a03 (030ad041) PNP0000: adding io range 0x20-0x21, size=0x2, align=0 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0 PNP0000: adding irq mask 0x4 PNP0000: end config pnpbios: handle 4 device ID PNP0000 (0000d041) PNP0200: adding io range 0-0xf, size=0x10, align=0 PNP0200: adding io range 0x80-0x8f, size=0x10, align=0 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0 PNP0200: adding dma mask 0x10 PNP0200: end config pnpbios: handle 5 device ID PNP0200 (0002d041) PNP0100: adding io range 0x40-0x43, size=0x4, align=0 PNP0100: adding irq mask 0x1 PNP0100: end config pnpbios: handle 6 device ID PNP0100 (0001d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0 PNP0800: end config pnpbios: handle 7 device ID PNP0800 (0008d041) PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 PNP0b00: adding io range 0x72-0x72, size=0x1, align=0 PNP0b00: adding io range 0x73-0x73, size=0x1, align=0 PNP0b00: adding irq mask 0x100 PNP0b00: end config pnpbios: handle 8 device ID PNP0b00 (000bd041) PNP0303: adding io range 0x60-0x60, size=0x1, align=0 PNP0303: adding io range 0x64-0x64, size=0x1, align=0 PNP0303: adding irq mask 0x2 PNP0303: end config pnpbios: handle 9 device ID PNP0303 (0303d041) PNP0f13: adding irq mask 0x1000 PNP0f13: end config pnpbios: handle 10 device ID PNP0f13 (130fd041) PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0 PNP0700: adding io range 0x3f7-0x3f7, size=0x1, align=0 PNP0700: end config pnpbios: handle 11 device ID PNP0700 (0007d041) PNP0401: adding irq mask 0x80 PNP0401: adding dma mask 0x8 PNP0401: adding io range 0x378-0x37f, size=0x8, align=0 PNP0401: adding io range 0x778-0x77a, size=0x3, align=0 PNP0401: end config pnpbios: handle 12 device ID PNP0401 (0104d041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 PNP0501: adding irq mask 0x10 PNP0501: end config pnpbios: handle 13 device ID PNP0501 (0105d041) SMCf010: adding io range 0x3e8-0x3ef, size=0x8, align=0 SMCf010: adding io range 0x100-0x107, size=0x8, align=0x10 SMCf010: adding irq mask 0x8 SMCf010: adding dma mask 0x20 SMCf010: end config pnpbios: handle 14 device ID SMCf010 (10f0a34d) PNP0e03: adding io range 0x3e0-0x3e1, size=0x2, align=0 PNP0e03: end config pnpbios: handle 15 device ID PNP0e03 (030ed041) PNP0c02: adding fixed memory32 range 0xfff80000-0xffffffff, size=0x80000 PNP0c02: adding io range 0x10-0x1f, size=0x10, align=0 PNP0c02: adding io range 0x22-0x3f, size=0x1e, align=0 PNP0c02: adding io range 0x44-0x5f, size=0x1c, align=0 PNP0c02: adding io range 0x62-0x63, size=0x2, align=0 PNP0c02: adding io range 0x65-0x6f, size=0xb, align=0 PNP0c02: adding io range 0x74-0x74, size=0x1, align=0 PNP0c02: adding io range 0x75-0x75, size=0x1, align=0 PNP0c02: adding io range 0x76-0x76, size=0x1, align=0 PNP0c02: adding io range 0x77-0x77, size=0x1, align=0 PNP0c02: adding io range 0x90-0x91, size=0x2, align=0 PNP0c02: adding io range 0x92-0x92, size=0x1, align=0 PNP0c02: adding io range 0x93-0x9f, size=0xd, align=0 PNP0c02: adding io range 0xa2-0xbf, size=0x1e, align=0 PNP0c02: adding io range 0xe0-0xe5, size=0x6, align=0 PNP0c02: adding io range 0xe7-0xe7, size=0x1, align=0 PNP0c02: adding io range 0xec-0xef, size=0x4, align=0 PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0 PNP0c02: adding io range 0x5000-0x5063, size=0x64, align=0 PNP0c02: adding io range 0x4000-0x400f, size=0x10, align=0 PNP0c02: adding io range 0x6004-0x6005, size=0x2, align=0 PNP0c02: adding io range 0x800-0x87f, size=0x80, align=0 PNP0c02: end config pnpbios: handle 16 device ID PNP0c02 (020cd041) sc-: sc0 already exists, using sc1 instead vga-: vga0 already exists, using vga1 instead isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata2 failed to probe at port 0x1f0 irq 14 on isa0 ata3: iobase=0x0170 altiobase=0x0376 bmaddr=0x0000 ata3: mask=00 status0=ff status1=ff ata3: probe allocation failed ata3 failed to probe at port 0x170-0x177,0x376 irq 15 on isa0 adv0 failed to probe on isa0 bt0 failed to probe on isa0 aha0 failed to probe on isa0 aic0 failed to probe at port 0x140-0x15f on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 00 00 psm: status 10 00 64 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k vga0: vga: WARNING: video mode switching is not fully supported on this adapter VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 e7 73 4f 4f 97 52 83 b4 1f 00 4f 0d 0e 00 00 07 80 91 87 8f 28 1f 8f b5 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 e7 73 4f 4f 97 52 83 b4 1f 00 4f 0d 0e 00 00 07 80 91 87 8f 28 1f 8f b5 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) vt0 failed to probe on isa0 pcic0: at port 0x3e0 iomem 0xd0000 on isa0 pcic0: Polling mode stat is 0 stat is 0 pccard0: on pcic0 pccard1: on pcic0 sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode vpo0: can't connect to the drive imm0: (disconnect) s1=0x38 s2=0x38, s3=0x38 imm0: (connect) s1=0x38 s2=0x38, s3=0x38 imm0: can't connect to the drive cs0 failed to probe at port 0x300 on isa0 ed0 failed to probe at port 0x280 iomem 0xd8000 irq 10 on isa0 fe0 failed to probe at port 0x300 on isa0 ie0 failed to probe at port 0x300 iomem 0xd0000 irq 10 on isa0 le0 failed to probe at port 0x300 iomem 0xd0000 irq 5 on isa0 lnc0 failed to probe at port 0x280 irq 10 drq 0 on isa0 pcic1: not probed (disabled) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: irq maps: 0x41 0x41 0x41 0x41 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0 failed to probe at port 0x300 irq 10 on isa0 sc1: no video adapter is found. sc1: failed to probe on isa0 vga1: failed to probe on isa0 isa_probe_children: probing PnP devices unknown: failed to probe at port 0x61 on isa0 unknown: can't assign resources unknown: at port 0x60 on isa0 unknown: can't assign resources unknown: at irq 12 on isa0 unknown: can't assign resources unknown: at port 0x3f0-0x3f5 on isa0 unknown: can't assign resources unknown: at port 0x378-0x37f on isa0 unknown: can't assign resources unknown: at port 0x3f8-0x3ff on isa0 unknown: failed to probe at port 0x3e8-0x3ef,0x100-0x107 irq 3 drq 5 on isa0 unknown: failed to probe at port 0x3e1-0x3e2 on isa0 BIOS Geometries: 0:03fdef3f 0..1021=1022 cylinders, 0..239=240 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: lo0 attached bpf: vlan0 attached bpf: vlan1 attached bpf: vlan2 attached bpf: vlan3 attached bpf: vlan4 attached bpf: vlan5 attached bpf: vlan6 attached bpf: vlan7 attached bpf: vlan8 attached bpf: vlan9 attached bpf: vlan10 attached bpf: vlan11 attached bpf: vlan12 attached bpf: vlan13 attached bpf: vlan14 attached bpf: vlan15 attached bpf: vlan16 attached bpf: vlan17 attached bpf: vlan18 attached bpf: vlan19 attached bpf: vlan20 attached bpf: vlan21 attached bpf: vlan22 attached bpf: vlan23 attached bpf: vlan24 attached bpf: vlan25 attached bpf: vlan26 attached bpf: vlan27 attached bpf: vlan28 attached bpf: vlan29 attached bpf: vlan30 attached bpf: vlan31 attached bpf: vlan32 attached bpf: vlan33 attached bpf: vlan34 attached bpf: vlan35 attached bpf: vlan36 attached bpf: vlan37 attached bpf: vlan38 attached bpf: vlan39 attached bpf: vlan40 attached bpf: vlan41 attached bpf: vlan42 attached bpf: vlan43 attached bpf: vlan44 attached bpf: vlan45 attached bpf: vlan46 attached bpf: vlan47 attached bpf: vlan48 attached bpf: vlan49 attached bpf: vlan50 attached bpf: vlan51 attached bpf: vlan52 attached bpf: vlan53 attached bpf: vlan54 attached bpf: vlan55 attached bpf: vlan56 attached bpf: vlan57 attached bpf: vlan58 attached bpf: vlan59 attached bpf: vlan60 attached bpf: vlan61 attached bpf: vlan62 attached bpf: vlan63 attached IP Filter: v3.4.13 initialized. Default = pass all, Logging = enabled ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable ata0-master: success setting UDMA2 on PIIX4 chip Creating DISK ad0 ad0: ATA-4 disk at ata0-master ad0: 11513MB (23579136 sectors), 23392 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=4 cblid=0 ad0: 11513MB [23392/16/63] at ata0-master UDMA33 ata0-slave: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata0-slave: success setting WDMA2 on PIIX4 chip acd0: CDROM drive at ata0 as slave acd0: read 4134KB/s (4134KB/s), 512KB buffer, WDMA2 acd0: Reads: CD-R, CD-DA stream acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad0s2a ad0s1: type 0xc, start 63, end = 4188239, size 4188177 : OK ad0s2: type 0xa5, start 4188240, end = 23572079, size 19383840 : OK start_init: trying /sbin/init To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 13:55: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn51.dh.casema.net [212.64.31.51]) by hub.freebsd.org (Postfix) with ESMTP id 50B8337B4C5 for ; Wed, 15 Nov 2000 13:55:02 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.9.3) with ESMTP id eAFMAL034389 for ; Wed, 15 Nov 2000 23:10:28 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20001115225006.00db8280@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 15 Nov 2000 22:53:35 +0100 To: freebsd-current@freebsd.org From: "Rogier R. Mulhuijzen" Subject: NTFS patch ready to be committed 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 NTFS is still broken in -CURRENT I've submitted a patch to gnats (and posted about it): http://www.freebsd.org/cgi/query-pr.cgi?pr=22756 I've been running it for a while now, without problems. Can someone commit it? DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 14:49:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 1916A37B479 for ; Wed, 15 Nov 2000 14:49:50 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA34506; Wed, 15 Nov 2000 14:49:41 -0800 (PST) (envelope-from obrien) Date: Wed, 15 Nov 2000 14:49:41 -0800 From: "David O'Brien" To: Harti Brandt Cc: current@freebsd.org Subject: Re: binutils commit breaks kernel builds? Message-ID: <20001115144941.A34327@dragon.nuxi.com> Reply-To: current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2.5i In-Reply-To: ; from brandt@fokus.gmd.de on Wed, Nov 15, 2000 at 04:15:55PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 15, 2000 at 04:15:55PM +0100, Harti Brandt wrote: > with fresh sources from today 6:00 MET kernel builds fail. The victim is I'm done with the upgrade - you may have easily CVSuped during the upgrade process. Can you wait an hour or so, CVSup again and see if you still see the problem? Is anyone else experience=1B[31~ing this? --=20 -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 14:50:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 22BAF37B479 for ; Wed, 15 Nov 2000 14:50:27 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAFMoPd03824 for ; Wed, 15 Nov 2000 23:50:26 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: Does floppies work with 384MByte RAM ? From: Poul-Henning Kamp Date: Wed, 15 Nov 2000 23:50:25 +0100 Message-ID: <3822.974328625@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have two reports about machines with 384MB RAM panicing when the floppies are accessed. I don't have the message right now except for a report that "it said something about bouncebuffers" Can somebody with 384MB ram check if the floppy works under current ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 14:51:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 1051937B479 for ; Wed, 15 Nov 2000 14:51:26 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA34536; Wed, 15 Nov 2000 14:51:22 -0800 (PST) (envelope-from obrien) Date: Wed, 15 Nov 2000 14:51:22 -0800 From: "David O'Brien" To: Joel Lindau Cc: FreeBSD-current@freebsd.org Subject: Re: Unable to build world Message-ID: <20001115145122.B34327@dragon.nuxi.com> Reply-To: current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from alastyr@home.se on Wed, Nov 15, 2000 at 09:20:06PM +0000 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 15, 2000 at 09:20:06PM +0000, Joel Lindau wrote: > When i try to build my -current world cvsupped today ( 15 nov ) i get the > following errors: When was the last time up built world? I'd like to know if this has anything to do with the Binutils upgrade, or if is something you would have experienced if you had tried to build world yesterday To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 16:14:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by hub.freebsd.org (Postfix) with ESMTP id 73C4537B479 for ; Wed, 15 Nov 2000 16:14:12 -0800 (PST) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.9.3/8.9.3) with ESMTP id QAA67817; Wed, 15 Nov 2000 16:14:11 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200011160014.QAA67817@beastie.mckusick.com> To: current@FreeBSD.ORG Subject: Re: Bad commit? Cc: dg@root.com, Warner Losh In-Reply-To: Your message of "Wed, 15 Nov 2000 11:43:06 PST." <200011151943.LAA26456@implode.root.com> Date: Wed, 15 Nov 2000 16:14:11 -0800 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Wed, 15 Nov 2000 11:47:07 -0700 From: Warner Losh Subject: Bad commit? Sender: owner-freebsd-current@FreeBSD.ORG As near as I can tell on my laptop, the following change causes panics with kernel page faults. With it, my laptop panics every time on boot (although in slightly different places for my two different kernels) and without it I'm rock solid. Has anybody else seen this? Warner mckusick 2000/11/14 12:46:02 PST Modified files: sys/sys rman.h sys/kern subr_bus.c subr_rman.c Log: In preparation for deprecating CIRCLEQ macros in favor of TAILQ macros which provide the same functionality and are a bit more efficient, convert use of CIRCLEQ's in resource manager to TAILQ's. Approved by: Garrett Wollman Revision Changes Path 1.13 +3 -3 src/sys/sys/rman.h 1.83 +3 -5 src/sys/kern/subr_bus.c 1.14 +30 -35 src/sys/kern/subr_rman.c I have checked in revision 1.15 for subr_rman.c which should fix the problems being experienced with version 1.14. If you continue to experience problems with version 1.15, please let me know. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 16:15:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3781237B479 for ; Wed, 15 Nov 2000 16:15:51 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAG0FiR19674; Wed, 15 Nov 2000 17:15:45 -0700 (MST) (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 RAA60454; Wed, 15 Nov 2000 17:15:44 -0700 (MST) Message-Id: <200011160015.RAA60454@harmony.village.org> To: Kirk McKusick Subject: Re: Bad commit? Cc: current@FreeBSD.ORG, dg@root.com In-reply-to: Your message of "Wed, 15 Nov 2000 16:14:11 PST." <200011160014.QAA67817@beastie.mckusick.com> References: <200011160014.QAA67817@beastie.mckusick.com> Date: Wed, 15 Nov 2000 17:15:44 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011160014.QAA67817@beastie.mckusick.com> Kirk McKusick writes: : I have checked in revision 1.15 for subr_rman.c which should fix : the problems being experienced with version 1.14. If you continue : to experience problems with version 1.15, please let me know. I've tested this and it appears to work. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 16:23:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from cae88-102-101.sc.rr.com (cae88-102-101.sc.rr.com [24.88.102.101]) by hub.freebsd.org (Postfix) with ESMTP id 6F47637B479; Wed, 15 Nov 2000 16:23:13 -0800 (PST) Received: (from myself@localhost) by cae88-102-101.sc.rr.com (8.11.1/8.9.3) id eAG0Sxm07009; Wed, 15 Nov 2000 19:28:59 -0500 (EST) (envelope-from myself) Date: Wed, 15 Nov 2000 19:28:59 -0500 From: "Donald J . Maddox" To: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Problems with stdbool.h... Message-ID: <20001115192859.A6948@cae88-102-101.sc.rr.com> Reply-To: dmaddox@sc.rr.com Mail-Followup-To: "Donald J . Maddox" , current@FreeBSD.ORG, ports@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As some of you may have noticed, apsfilter will no longer compile on -current. The reason is that the configure script checks for , and uses it if it exists; but this file, as I understand it, is intended only for use with C99, and unfortunately, if it is included by the standard compiler, the results are bad. An example: /* test.c */ #include int main() { return(0); } $ cc -o test test.c In file included from test.c:1: /usr/include/stdbool.h:51: conflicting types for `_Bool' /usr/include/stdbool.h:38: previous declaration of `_Bool' Apparently, stdbool.h defines _Bool, then redefines it if __STDC_VERSION__ < 199901L. Fixing the port to compile anyway would be simple enough, but I think the real problem is in stdbool.h, no? It shouldn't break the standard compiler like this, should it? Please forgive the cross-posting... Although this affects ports, I have no way of knowing if the maintainer of this file reads the ports mailing list... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 16:48:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 3408537B4C5; Wed, 15 Nov 2000 16:48:55 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAG0mlB39691; Wed, 15 Nov 2000 16:48:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 15 Nov 2000 16:49:26 -0800 (PST) From: John Baldwin To: smp@FreeBSD.org Subject: Patches to make witness work.. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Bcc'd to -current, send followups to -smp ] I've been spending my time recently trying to get the kernel to boot with witnees turned on. The witness code itself was not broken (with a tiny exception), but our kernel code did have some bugs. However, while fixing the problems witness pointed out, I ended up with a kernel that is not stable on SMP systems (go figure). Part of this may be due to a broken atkbd driver, whose interrupt thread seems to chew up a lot more CPU time than it should be. I've tried to commit as many of the safe changes as I could w/o actually breaking SMP systems. The rest of the patches that are needed are at http://www.FreeBSD.org/~jhb/patches/giant.patch. This patchset does two primary things: 1) It fixes msleep() and mawait() to release the sched_lock before calling CURSIG() and to pick the lock back up again afterwards. 2) It moves the dropping/reacquiring of Giant out of mi_switch() and out into the code that calls mi_switch(). This is needed because Giant needs to be released/reacquired when it is not under the sched_lock Any feedback, etc. is welcome. At the very least, UP systems (both x86 and alpha) appear to be fine with this patch, and can run kernels with witness enabled without any problems. Thus this patch can be used to debug deadlocks, etc. on UP systems at least. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 17:57:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from msa.hinet.net (msa.hinet.net [168.95.4.211]) by hub.freebsd.org (Postfix) with ESMTP id 8665B37B4C5; Wed, 15 Nov 2000 17:57:32 -0800 (PST) Received: from CoreBit.com (h4.s180.ts.hinet.net [168.95.180.4]) by msa.hinet.net (8.8.8/8.8.8) with ESMTP id JAA20400; Thu, 16 Nov 2000 09:57:29 +0800 (CST) Message-ID: <3A133F43.7103AB6C@CoreBit.com> Date: Thu, 16 Nov 2000 09:58:27 +0800 From: Donny Lee X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Cc: Poul-Henning Kamp Subject: Re: Does floppies work with 384MByte RAM ? References: <3822.974328625@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > I have two reports about machines with 384MB RAM panicing when > the floppies are accessed. I don't have the message right now > except for a report that "it said something about bouncebuffers" > > Can somebody with 384MB ram check if the floppy works under > current ? works fine on my current, i tried a mount, cp files in, rm files, and then a umount, all work normally. -- // Donny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 18:19:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 2867637B4CF; Wed, 15 Nov 2000 18:19:26 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAG2JHB42159; Wed, 15 Nov 2000 18:19:17 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200011160216.SAA29000@freefall.freebsd.org> Date: Wed, 15 Nov 2000 18:19:53 -0800 (PST) From: John Baldwin To: current@FreeBSD.org, smp@FreeBSD.org Subject: RE: cvs commit: src/sys/alpha/alpha trap.c src/sys/i386/i386 tra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Nov-00 John Baldwin wrote: > jhb 2000/11/15 18:16:45 PST > > Modified files: > sys/alpha/alpha trap.c > sys/i386/i386 trap.c > sys/ia64/ia64 trap.c > sys/kern kern_mutex.c kern_shutdown.c kern_sig.c > kern_subr.c kern_synch.c > Log: > Don't release and acquire Giant in mi_switch(). Instead, release and > acquire Giant as needed in functions that call mi_switch(). The releases > need to be done outside of the sched_lock to avoid potential deadlocks > from trying to acquire Giant while interrupts are disabled. > > Submitted by: witness It is now safe to turn on WITNESS in -current kernels without having the machine panic or lockup.... At least it is on my set of test boxes. As such, I plan to turn on the various debugging options in -current's GENERIC sometime tomorrow (including WITNESS, but without DIAGNOSTIC). -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 19:38:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id D559137B479; Wed, 15 Nov 2000 19:38:29 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.0/8.11.0) with ESMTP id eAG3cTG72325; Wed, 15 Nov 2000 22:38:29 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200011160338.eAG3cTG72325@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: Does floppies work with 384MByte RAM ? References: <3822.974328625@critter> In-reply-to: Your message of "Wed, 15 Nov 2000 23:50:25 +0100." <3822.974328625@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Nov 2000 22:38:29 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have two reports about machines with 384MB RAM panicing when > the floppies are accessed. I don't have the message right now > except for a report that "it said something about bouncebuffers" I apologize for the vagueness of this response, but perhaps it might help shed some light. I've got a Dell dual-Pentium-III XEON system at work that I was running -current on. Some time ago (didn't notice when exactly, sigh) when building new kernels, I started getting isa_dmainit(foo, bar) failed messages during the booting process for both the fdc device as well as my CS423x sound device. A cursory examination revealed that this was while trying to allocate bounce buffers for both the floppy and sound device DMA channels. On a lark, I rebuilt a kernel with MAXMEM=(256*1024) (the system has 512M of memory installed), and the isa_dmainit() failures stopped happening. Recently, I installed 4.1.1-STABLE on this machine because, well, I needed a stable system and didn't need to track the -current bleeding edge. It's probably hard for me currently to reproduce this problem myself right now. I'd suggest the MAXMEM hack to see if this mirrors my experience. Certainly this system was working just fine until sometime around the SMPNG milestone; but I can't really attribute the failure to any particular change. Again, sorry for the lack of detail; hope this might provide a hint. louie > Can somebody with 384MB ram check if the floppy works under > current ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 20:29:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 61C9637B479 for ; Wed, 15 Nov 2000 20:29:30 -0800 (PST) Received: by relay.butya.kz (Postfix, from userid 1000) id 611C328DBD; Thu, 16 Nov 2000 10:29:26 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 564C228A25; Thu, 16 Nov 2000 10:29:26 +0600 (ALMT) Date: Thu, 16 Nov 2000 10:29:26 +0600 (ALMT) From: Boris Popov To: "Rogier R. Mulhuijzen" Cc: freebsd-current@freebsd.org Subject: Re: NTFS patch ready to be committed In-Reply-To: <4.3.2.7.0.20001115225006.00db8280@mail.drwilco.net> 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, 15 Nov 2000, Rogier R. Mulhuijzen wrote: > NTFS is still broken in -CURRENT > > I've submitted a patch to gnats (and posted about it): > > http://www.freebsd.org/cgi/query-pr.cgi?pr=22756 > > I've been running it for a while now, without problems. Can someone commit it? Yes, patch is correct and matches the one in my tree. I'll commit it this evening if no one will do it before :) -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 21:54:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 24FA837B479 for ; Wed, 15 Nov 2000 21:54:47 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id eAG5sfZ93347 for freebsd-current@freebsd.org; Thu, 16 Nov 2000 06:54:41 +0100 (CET) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.0/8.11.0) with ESMTP id eAG5sNp41885 for ; Thu, 16 Nov 2000 06:54:29 +0100 (CET) (envelope-from leifn@neland.dk) Date: Thu, 16 Nov 2000 06:54:23 +0100 (CET) From: Leif Neland To: freebsd-current@freebsd.org Subject: Proper permissons on /tmp 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 Something keeps changing permissions on /tmp to 755, which causes pine to claim the mailbox is in use by another process. This change has occurred a couple of times lately, but I haven't found a pattern. When I reset the perms to 777, pine works normal again. What is the proper perms on /tmp? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 15 22: 1:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 9869937B4C5 for ; Wed, 15 Nov 2000 22:01:21 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eAG62aO41466; Wed, 15 Nov 2000 22:02:36 -0800 (PST) (envelope-from kris) Date: Wed, 15 Nov 2000 22:02:35 -0800 From: Kris Kennaway To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proper permissons on /tmp Message-ID: <20001115220235.A41392@citusc17.usc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from leifn@neland.dk on Thu, Nov 16, 2000 at 06:54:23AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Nov 16, 2000 at 06:54:23AM +0100, Leif Neland wrote: > What is the proper perms on /tmp? 1777 Kris --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoTeHsACgkQWry0BWjoQKW8VwCgmvNEgcxccFrFYigjPp2njar5 wx0AoOQDGWWCwEW5H69Fe7pSvkvh+TFc =PHVU -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 1: 2: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id 2C1E437B479; Thu, 16 Nov 2000 01:02:01 -0800 (PST) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by gatekeeper.radio-do.de (Postfix) with ESMTP id AC04316E20; Thu, 16 Nov 2000 10:01:52 +0100 (CET) Received: (from fn@localhost) by trinity.radio-do.de (8.11.1/8.9.3) id eAG91ql01589; Thu, 16 Nov 2000 10:01:52 +0100 (CET) (envelope-from fn@gatekeeper.radio-do.de) Date: Thu, 16 Nov 2000 10:01:52 +0100 From: Frank Nobis To: "Louis A. Mamakos" Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: Does floppies work with 384MByte RAM ? Message-ID: <20001116100152.A1561@radio-do.de> References: <3822.974328625@critter> <200011160338.eAG3cTG72325@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011160338.eAG3cTG72325@whizzo.transsys.com>; from louie@TransSys.COM on Wed, Nov 15, 2000 at 10:38:29PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 15, 2000 at 10:38:29PM -0500, Louis A. Mamakos wrote: > > I've got a Dell dual-Pentium-III XEON system at work that I was running > -current on. Some time ago (didn't notice when exactly, sigh) when > building new kernels, I started getting > > isa_dmainit(foo, bar) failed > For me it is a ASUS P2B-DS with 512M RAM. I see the same isa_dmainit failed with full ram utilized. With MAXMEM set to MAXMEM="(464*1024)" it is working under current. With 480M it is failing. I looked through the sources and found that contigousmalloc can't find a page of physical ram under the 16M margin. But I am not vm wizzard enough, to understand what the difference is with MAXMEM set to some lower value than the real amount of memory. Regards, Frank -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 1:26:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from jarrow.nanoteq.co.za (jarrow.nanoteq.co.za [196.37.91.33]) by hub.freebsd.org (Postfix) with ESMTP id D082337B479 for ; Thu, 16 Nov 2000 01:26:14 -0800 (PST) Received: from jarrow.dev.nanoteq.co.za (localhost [127.0.0.1]) by jarrow.nanoteq.co.za (8.11.1/8.9.3) with ESMTP id eAG9OOG20009; Thu, 16 Nov 2000 11:24:27 +0200 (SAST) (envelope-from rbezuide@oskar.nanoteq.co.za) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001115163422.8947A5DF4@free.bsdshell.net> Date: Thu, 16 Nov 2000 11:24:24 +0200 (SAST) Reply-To: rbezuide@oskar.nanoteq.co.za From: Reinier Bezuidenhout To: (urded) Subject: RE: vmwareport does not work Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... I'll give my worth of what the messages actually mean .. > i get > > kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon_up.ko: File > exists This means the vmmon_up is already loaded - do a kldstat > sysctl: unknown oid 'net.link.ether.bridge_refresh' Seems like you do not have bridging compiled into the kernel ?? > kldload: can't load if_tap.ko: File exists This also axists already - same as vmmon_up above > ifconfig: ioctl (SIOCAIFADDR): File exists The ifconfig fails because it has already been done on bootup with the vmnet device - that's why the error "File exists" > > what' s wrong then ? > There doesn't seem to be anything wrong ... except that bridging isn't on (I think), but depending on how you use vmware networking it is not a show stopper. Reinier ################################################################### # # # R.N. Bezuidenhout NetSeq Firewall # # rbezuide@oskar.nanoteq.co.za http://www.nanoteq.co.za # # # ################################################################### ---------------------------------- Date: 16-Nov-00 Time: 11:21:04 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 2:30:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from aps01.s2.ocv.ne.jp (aps01.ocv.ne.jp [210.238.14.22]) by hub.freebsd.org (Postfix) with ESMTP id C0E9637B479; Thu, 16 Nov 2000 02:30:32 -0800 (PST) Received: from copper (dlt205.ocv.ne.jp [211.7.183.205]) by aps01.s2.ocv.ne.jp (8.9.3/3.7W) with SMTP id SAA14903; Thu, 16 Nov 2000 18:10:00 +0900 (JST) Message-ID: <007901c04fac$ee4396b0$6701a8c0@copper> From: "=?iso-2022-jp?B?GyRCJWEhPCVrJTchPCUvSE5HZBsoQg==?=" To: Subject: =?iso-2022-jp?B?GyRCJWEhPCVrJSIlSSVsJTlITkdkIUpHL0ZiOEJEaiFLJE4kKkNOGyhC?= =?iso-2022-jp?B?GyRCJGkkOxsoQg==?= Date: Thu, 16 Nov 2000 18:06:45 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $BFMA3$N%a!<%k!"?=$7Lu$"$j$^$;$s!#8fITMW$N>l9g$O:o=|$7$F$/$@$5$$!#(B ====================================================================== $B!|!|!|%@%$%l%/%H%a!<%kMQ!!%a!<%k%"%I%l%94|4V8BDjHNGd$N$*CN$i$;!|!|!|(B ====================================================================== $B%a!<%k%"%I%l%9%G!<%?$rG/Fb8BDj$G!"3J0BHNGd$$$?$7$^$9!#(B $BEve$2$^$9!#(B ---------------------------------------------------------------------- $B!|%G!<%?%?%$%W!J#A!K!!!J0B2A$GBgNL$K;EF~$l$?$$J}$O!"$3$N#A%?%$%W$r!*!K(B ---------------------------------------------------------------------- $B!!!!#1K|7o!!(B 2,000$B1_!JC12A(B0.20$B1_!K(B $B!!#1#0K|7o!!(B 5,000$B1_!JC12A(B0.05$B1_!K(B $B!!#2#5K|7o!!(B10,000$B1_!JC12A(B0.04$B1_!K(B $B!!#5#0K|7o!!(B15,000$B1_!JC12A(B0.03$B1_!K(B $B#1#0#0K|7o!!(B20,000$B1_!JC12A(B0.02$B1_!K(B $B#3#0#0K|7o!!(B30,000$B1_!JC12A(B0.01$B1_!K(B ---------------------------------------------------------------------- $B!|%G!<%?%?%$%W!J#B!K!!!J%8%c%s%kJL$K8!:w!&Cj=P$7$?%a!<%k%"%I%l%9$G$9!K(B ---------------------------------------------------------------------- $B!!!!#1K|7o!!(B 8,000$B1_!JC12A(B0.80$B1_!K(B $B!!!!#3K|7o!!(B21,000$B1_!JC12A(B0.70$B1_!K(B $B!!#1#0K|7o!!(B60,000$B1_!JC12A(B0.60$B1_!K(B $B!!#1#5K|7o!!(B75,000$B1_!JC12A(B0.50$B1_!K(B $B!!#2#0K|7o!!(B80,000$B1_!JC12A(B0.40$B1_!K(B $B>e5-$NNA6b$O!J#A!K!J#B!K%?%$%W6&$K$9$Y$F!">CHq@G9~$_$N2A3J$G$9!#(B $B5$C$?>l9g$K$O!"#5#5K|7o$r$*5RMM$X$*EO$7$7$F$$$^$9!#(B ---------------------------------------------------------------------- $B!|%a!<%k%"%I%l%9%G!<%?$N$*0zEO$7J}K!!J#3l9g!"F~6b3NG'8e#3;~4V0JFb$KAw?.(B $B!!!!!!$7$F$*$j$^$9!#:GB.$G!"?69~8e#3#0J,$GAw?.$$$?$7$^$9!#(B $B#2!%6d9T8}:B$K$*?69~3NG'8e!"$4;XDj$N=;=j$X(B CD-ROM $B$^$?$O(B FD $B$rM9Aw!#(B $B!!!!!JJLES!"AwNA(B1,000$B1_$r?=$7&IJE~Ce;~$KBpG[JX6He5-$N$h$&$KJ]B8$5$l$F$$$^$9!#(B $BDL>o$O#C#S#V7A<0$N%U%!%$%k$K$F$4Ds6!$5$;$F$$$?$@$-$^$9$,!"$b$7$*5RMMB&(B $B$KITET9g$,$"$k>l9g$O!"B>$N%U%!%$%k7A<0$K$F$4Ds6!$9$k$3$H$b2DG=$G$4$6$$(B $B$^$9$N$G(B mailseek_support@h3.dion.ne.jp $B$^$G!"$*Ld$$9g$o$;$/$@$5$$!#(B ---------------------------------------------------------------------- $B!|%a!<%k%"%I%l%9%G!<%?$NFbMF$K$D$$$F(B ---------------------------------------------------------------------- $BEvo$K?7A/$G$9!*$^$?!"7HBSEEOC$d#P#H#S$N%a!<%k(B $B%"%I%l%9$O4^$^$l$F$*$j$^$;$s!#Ds6!$9$k%a!<%k%"%I%l%9$OF|K\9qFb$G$N;HMQ(B $B$rL\E*$H$7$?%G!<%?$G$9!#(B $B"(%G!<%?$NCf$K$O#1%u7n0JFb$K%W%m%P%$%@$NJQ99$d2rLsEy$K$h$jFO$+$J$/$J$C(B $B$F$$$k%"%I%l%9$b?t!s$O4^$^$l$F$$$k2DG=@-$,$"$k$3$H$r$4N;>5$/$@$5$$!#(B ---------------------------------------------------------------------- $B!|$49XF~J}K!(B ---------------------------------------------------------------------- $B2<5-;v9`$r5-:\$N>e(B mailseek_support@h3.dion.ne.jp $B$^$G%a!<%k$K$FAw?.$7(B $B$F$/$@$5$$!#(B $B#1!%$*L>A0(B $B!!!!!J?69~;~$NL>A0$HF10l$K$J$k$h$&$K$7$F$/$@$5$$!#%O%s%I%k%M!<%`$G$b9=(B $B!!!!!!$$$^$;$s!K(B $B#2!%O"Mm@h%a!<%k%"%I%l%9(B $B!!!!$4CmJ8D:$$$F$+$i!"FbMF$N3NG'%a!<%k$r$3$NO"Mm@h$KAw?.$$$?$7$^$9!#(B $B!!!!$=$N;~$K?69~@h$N6d9TL>!"8}:BHV9fEy$b0l=o$K$4O"Mm:9$7>e$2$^$9!#(B $B#3!%$*0zEO$7J}K!!J%a!<%k$G!"M9Aw$G!"Be6b0z49$G!K(B $B!!!!FC$K!"$*5RMMB&$G$4;XDj$NL5$$>l9g$O!">e5-!VO"Mm@h%a!<%k%"%I%l%9!W$X(B $B!!!!%a!<%k$K$F%G!<%?$rAw?.$5$;$F$$$?$@$-$^$9!#(B $B#4!%9XF~7o?t!J#1!$#1#0!$#2#5!$#5#0!$#1#0#0!$#3#0#0!KK|7o(B $B!!!!>e5-0J30$N7o?t$G$b!J#7#5K|7oEy!K>5$j$^$9$N$G!"$*?=$7IU$1$/$@$5$$!#(B $B#5!%9XF~%G!<%?%?%$%W!J#A$O!V%N!<%8%c%s%k!W#B$O!V%8%c%s%kJL!W%G!<%?$G$9!K(B $B!!!J#A!K%?%$%W(B $B!!!!#A%?%$%W$ONw2AHG$N%a!<%k%"%I%l%9$G$9!J0B$$$+$i8E$+$C$?$j!"H?1~$,0-(B $B!!!!$$$H$$$&$3$H$O$"$j$^$;$s!*!K0B$/$FBt;3M_$7$$J}$O!"$3$A$i$r$I$&$>!*(B $B!!!!NA6b$O!">e5-$N!J#A!K%?%$%WNA6bI=$r$4Mw$/$@$5$$!#(B $B!!!J#B!K%?%$%W(B $B!!!!#B%?%$%W$O$*5RMM$K$h$j!"%8%c%s%k$r;XDj$7$F$$$?$@$-$^$9!#(B $B!!!!Nc$($P!V/!9;~4V$N$+$+$k$3$H$,$4$6$$$^$9!#CmJ8;~(B $B!!!!$K!"8!:wJ}K!$H$"$o$;$F!"$*Ld$$9g$o$;$/$@$5$$!#(B $B!!!!NA6b$O!">e5-$N!J#B!K%?%$%WNA6bI=$r$4Mw$/$@$5$$(B ---------------------------------------------------------------------- $B!|:G8e$K(B ---------------------------------------------------------------------- $BF|K\$G$b%$%s%?!<%M%C%H$NGzH/E*$JIa5Z$K$h$j0l?M$G$R$H$D$N%a!<%k%"%I%l%9(B $B$r;}$D;~Be$K$J$C$F$-$^$7$?!#%$%s%?!<%M%C%H$rMxMQ$7$?%@%$%l%/%H%a!<%k$O(B $B0B$/!"Aa$/!"3Ne$O>e$,$k!*!W$,EE;R%a!<%k$r(B $BMxMQ$7$?;~$N!"%@%$%l%/%H%a!<%k8z2L$G$9!#(B $BEve$2D:$$$?$*5RMM$+$i$N5;=QE*$J$4AjCL$b>5$C$F$*$j$^$9!#(B $B!JEz$($i$l$kHO0O$G$9$,!KBgNL$N%@%$%l%/%H%a!<%k$r<+F0Aw?.$9$k%=%U%H$d8z(B $B2LE*$J#D#M$NAw?.J}K!!"$^$?%a!<%k%"%I%l%9$N%U%!%$%k$r;XDj$N7A<0$KJQ49$9(B $B$k%5!<%S%9$d!"%Q%=%3%sD6=i?4pJsDs6!4k6H$+$i$N0MMj$K$h$j%j%&%s%8%g%s(BCorp.$B$,G[?.$7$F$*$j(B $B$^$9!#(B ====================================================================== $B!!%$%s%?!<%M%C%H4XO"4k6H$r%5%]!<%H$9$kAm9g#I#T4k6H(B $B%j%&%s%8%g%s(BCorp. ---------------------------------------------------------------------- $B!!EE;R%a!<%k%"%I%l%9$N8!:w!&Cj=P!&HNGd$O(B $B%a!<%k%7!<%/HNGd3t<02q(B ====================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 4:20:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 4ABC337B479 for ; Thu, 16 Nov 2000 04:20:14 -0800 (PST) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "caerdonn.eurocontrol.fr", Issuer CN "CA ITM" (verified OK)) by matrix.eurocontrol.fr (Postfix/TLS) with ESMTP id 8C26D5B87; Thu, 16 Nov 2000 13:20:12 +0100 (CET) Received: by caerdonn.eurocontrol.fr (Postfix/TLS, from userid 1193) id 0AC424E14; Thu, 16 Nov 2000 13:20:06 +0100 (CET) Date: Thu, 16 Nov 2000 13:20:06 +0100 From: Ollivier Robert To: Warner Losh Cc: FreeBSD Current Users' list Subject: Re: clock/apm broken in CURRENT ? Message-ID: <20001116132006.B48307@caerdonn.eurocontrol.fr> References: <20001115165648.A39710@caerdonn.eurocontrol.fr> <200011151830.LAA57387@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011151830.LAA57387@harmony.village.org>; from imp@village.org on Wed, Nov 15, 2000 at 11:30:38AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Warner Losh: > to your config file. Fixes it for me. Tell people on #bsdcode about > this. Darn, I thought I remembered this one, sorry for being stupid. Works now. /me blames it on the flu -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #6: Thu Aug 10 17:36:11 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 5:50:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from Sorcery.se (cvx-sto-1-317.ppp.netlink.se [212.242.103.221]) by hub.freebsd.org (Postfix) with ESMTP id 1BBE537B4CF for ; Thu, 16 Nov 2000 05:50:16 -0800 (PST) Received: from localhost (nevyn@localhost) by Sorcery.se (8.11.1/8.11.1) with ESMTP id eAGElaT00698 for ; Thu, 16 Nov 2000 14:47:37 GMT (envelope-from alastyr@home.se) X-Authentication-Warning: Sorcery.se: nevyn owned process doing -bs Date: Thu, 16 Nov 2000 14:47:35 +0000 (GMT) From: Joel Lindau X-Sender: nevyn@Sorcery.se To: current@freebsd.org Subject: Re: Unable to build world In-Reply-To: <20001115145122.B34327@dragon.nuxi.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 The last time i built -current world was using 4.1-STABLE, about uhm 2:nd or 3:rd november. This is the first time i tried building world since the upgrade. / Joel.L a.k.a Nevyn -- #FreeBSD.se, #unix.se On Wed, 15 Nov 2000, David O'Brien wrote: > On Wed, Nov 15, 2000 at 09:20:06PM +0000, Joel Lindau wrote: > > When i try to build my -current world cvsupped today ( 15 nov ) i get the > > following errors: > > When was the last time up built world? I'd like to know if this has > anything to do with the Binutils upgrade, or if is something you would > have experienced if you had tried to build world yesterday > > > 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 Thu Nov 16 6:59: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from valcho.net (valcho.net [206.162.201.61]) by hub.freebsd.org (Postfix) with SMTP id 6522E37B4D7 for ; Thu, 16 Nov 2000 06:58:59 -0800 (PST) Received: (qmail 3242 invoked by uid 1000); 16 Nov 2000 14:59:00 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 16 Nov 2000 14:59:00 -0000 Date: Thu, 16 Nov 2000 09:58:59 -0500 (EST) From: Valentin Chopov To: current@freebsd.org Subject: CURRENT is freezing again ... 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, After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in 10 min after boot... Thanks, Val To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 7:18:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id BD3F437B4C5 for ; Thu, 16 Nov 2000 07:18:12 -0800 (PST) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13wQnh-00043K-00; Thu, 16 Nov 2000 15:18:09 +0000 Date: Thu, 16 Nov 2000 15:18:09 +0000 To: Leif Neland Cc: freebsd-current@freebsd.org Subject: Re: Proper permissons on /tmp Message-ID: <20001116151809.A15312@firedrake.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from leifn@neland.dk on Thu, Nov 16, 2000 at 06:54:23AM +0100 From: void Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 16, 2000 at 06:54:23AM +0100, Leif Neland wrote: > Something keeps changing permissions on /tmp to 755, which causes pine to > claim the mailbox is in use by another process. I have a similar problem -- every time I make world, perms on /var/mail get set to 775. Mutt considers my mailbox read-only until I change it to 1777. Is there a supported way to locally override BSD.var.dist, or do I need to install mutt setgid mail, or what? -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 7:41:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DD74237B4CF for ; Thu, 16 Nov 2000 07:41:47 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id QAA06150; Thu, 16 Nov 2000 16:40:40 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200011161540.QAA06150@freebsd.dk> Subject: Re: CURRENT is freezing again ... In-Reply-To: from Valentin Chopov at "Nov 16, 2000 09:58:59 am" To: valentin@valcho.net (Valentin Chopov) Date: Thu, 16 Nov 2000 16:40:40 +0100 (CET) Cc: current@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 Valentin Chopov wrote: > Hi, > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > 10 min after boot... You mean "is still freezing" right ? Current has been like this for longer than I care to think about, it seems those in charge doesn't take these problems seriously (enough)... I've started doing development on -stable instead, it goes nowhere on -current.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 8:36:42 2000 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 58A4E37B4CF for ; Thu, 16 Nov 2000 08:36:39 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA83126; Thu, 16 Nov 2000 11:36:13 -0500 (EST) (envelope-from wollman) Date: Thu, 16 Nov 2000 11:36:13 -0500 (EST) From: Garrett Wollman Message-Id: <200011161636.LAA83126@khavrinen.lcs.mit.edu> To: void Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proper permissons on /var/mail In-Reply-To: <20001116151809.A15312@firedrake.org> References: <20001116151809.A15312@firedrake.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I have a similar problem -- every time I make world, perms on /var/mail > get set to 775. Mutt considers my mailbox read-only until I change it > to 1777. It is misconfigured (or perhaps just broken). 1777 mode for /var/mail is insecure, but was necessary in the mists of ancient past, before UNIX learned to do file locking. Unless your mail spool is shared over NFS (don't do that), locking is reliable and .lock files should never be used or relied upon. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 8:54:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 333C237B479 for ; Thu, 16 Nov 2000 08:54:50 -0800 (PST) Received: by relay.butya.kz (Postfix, from userid 1000) id F230528D9F; Thu, 16 Nov 2000 22:54:47 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id E21B128D9E; Thu, 16 Nov 2000 22:54:47 +0600 (ALMT) Date: Thu, 16 Nov 2000 22:54:47 +0600 (ALMT) From: Boris Popov To: Soren Schmidt Cc: Valentin Chopov , current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... In-Reply-To: <200011161540.QAA06150@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 Thu, 16 Nov 2000, Soren Schmidt wrote: > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > > 10 min after boot... > > You mean "is still freezing" right ? > > Current has been like this for longer than I care to think about, it > seems those in charge doesn't take these problems seriously (enough)... I think info about where/how it freezing would be more helpful. > I've started doing development on -stable instead, it goes nowhere > on -current.... - works fine for me even with my new evil hacks :) -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 9: 1:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtpproxy1.mitre.org (mb-20-100.mitre.org [129.83.20.100]) by hub.freebsd.org (Postfix) with ESMTP id 69A3137B4E5 for ; Thu, 16 Nov 2000 09:01:25 -0800 (PST) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id MAA05506 for ; Thu, 16 Nov 2000 12:01:22 -0500 (EST) Received: from mailsrv2.mitre.org (mailsrv2.mitre.org [129.83.221.17]) by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id MAA01231 for ; Thu, 16 Nov 2000 12:01:21 -0500 (EST) Received: from mitre.org ([128.29.145.140]) by mailsrv2.mitre.org (Netscape Messaging Server 4.15) with ESMTP id G44NA800.0DU; Thu, 16 Nov 2000 12:01:20 -0500 Message-ID: <3A1412C1.96608727@mitre.org> Date: Thu, 16 Nov 2000 12:00:49 -0500 From: "Andresen,Jason R." Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Garrett Wollman Cc: void , freebsd-current@FreeBSD.ORG Subject: Re: Proper permissons on /var/mail References: <20001116151809.A15312@firedrake.org> <200011161636.LAA83126@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > > < said: > > > I have a similar problem -- every time I make world, perms on /var/mail > > get set to 775. Mutt considers my mailbox read-only until I change it > > to 1777. > > It is misconfigured (or perhaps just broken). 1777 mode for /var/mail > is insecure, but was necessary in the mists of ancient past, before > UNIX learned to do file locking. Unless your mail spool is shared > over NFS (don't do that), locking is reliable and .lock files should > never be used or relied upon. Not the FreeBSD's file locking works anyway. Here's the results from a test of the below program: (81 ~/bin/src): uname -a FreeBSD escaflowne.el.hazard 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Sat Oct 14 18:59:16 EDT 2000 root@escaflowne.el.hazard:/usr/obj/usr/src/sys/ESCAFLOWNE i386 (82 ~/bin/src): ./testflock flock(2) is implemented, but not functional. And another test: %kenshin (1 ~): uname -a IRIX kenshin 6.5 01221642 IP20 %kenshin (2 ~): ./testflock flock(2) is fully functional. I hope I'm doing something wrong here, and that flock really does work on FreeBSD. #include #include #include #include #include #include #define TMPFILENAME "/tmp/testflock.out" #define MESSLEN 8 #define CHILDSTR "Child \n" #define PARENTSTR "Parent\n" int main( int argc, char** argv) { char message[MESSLEN]; int pid; int fd; int foo; fd = open(TMPFILENAME, O_WRONLY | O_CREAT, 0644); pid = fork(); if ( pid == 0 ) { strcpy(message, CHILDSTR); sleep(1); } else strcpy(message, PARENTSTR); flock(fd, LOCK_EX); lseek(fd, 0, SEEK_END); write(fd, message, MESSLEN - 1); sleep(2); lseek(fd, 0, SEEK_END); write(fd, message, MESSLEN - 1); flock(fd, LOCK_UN); close(fd); if ( pid != 0 ) { wait(&foo); /* Test the file, see if flock works */ fd = open(TMPFILENAME, O_RDONLY); read(fd, (void*)message, MESSLEN - 1); /* Discard first */ read(fd, (void*)message, MESSLEN - 1); if (! strcmp(message, CHILDSTR)) printf("flock(2) is implemented, but not functional.\n"); else printf("flock(2) is fully functional.\n"); close(fd); } return 0; } -- _ _ _ ___ ____ ___ ______________________________________ / \/ \ | ||_ _|| _ \|___| | Jason Andresen -- jandrese@mitre.org / /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those /_/ \_\|_| |_| |_|\_\|___| | of the Mitre Corporation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 9:19: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2A4FA37B479 for ; Thu, 16 Nov 2000 09:19:00 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA30813; Thu, 16 Nov 2000 18:17:46 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200011161717.SAA30813@freebsd.dk> Subject: Re: CURRENT is freezing again ... In-Reply-To: from Boris Popov at "Nov 16, 2000 10:54:47 pm" To: bp@butya.kz (Boris Popov) Date: Thu, 16 Nov 2000 18:17:46 +0100 (CET) Cc: valentin@valcho.net (Valentin Chopov), current@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 Boris Popov wrote: > On Thu, 16 Nov 2000, Soren Schmidt wrote: > > > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > > > 10 min after boot... > > > > You mean "is still freezing" right ? > > > > Current has been like this for longer than I care to think about, it > > seems those in charge doesn't take these problems seriously (enough)... > > I think info about where/how it freezing would be more helpful. No idea, the system just freezes, no drob to DDB no remote gdb no nothing, so its really hard to tell where... As to how, just boot current on a fairly fast machine, make a kernel and it'll hang in minutes if not less, or just leave it alone and it will hang in 10-30 mins... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 9:27: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id CF85637B4CF for ; Thu, 16 Nov 2000 09:27:01 -0800 (PST) Received: from ny1wsh031 (blackhole.cioe.com [204.120.165.44]) (authenticated) by virtual-voodoo.com (8.11.1/8.11.1) with ESMTP id eAGHPSF52959; Thu, 16 Nov 2000 12:25:28 -0500 (EST) (envelope-from steve@virtual-voodoo.com) Message-ID: <027d01c04ff1$90d9cf40$8a1a050a@winstar.com> From: "Steven E. Ames" To: "Soren Schmidt" , "Boris Popov" Cc: "Valentin Chopov" , References: <200011161717.SAA30813@freebsd.dk> Subject: Re: CURRENT is freezing again ... Date: Thu, 16 Nov 2000 12:20:49 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems to only do it SMP... the same machine built with a non-SMP kernel (same source code) runs just fine for extended periods. -Steve ----- Original Message ----- From: "Soren Schmidt" To: "Boris Popov" Cc: "Valentin Chopov" ; Sent: Thursday, November 16, 2000 12:17 PM Subject: Re: CURRENT is freezing again ... > It seems Boris Popov wrote: > > On Thu, 16 Nov 2000, Soren Schmidt wrote: > > > > > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > > > > 10 min after boot... > > > > > > You mean "is still freezing" right ? > > > > > > Current has been like this for longer than I care to think about, it > > > seems those in charge doesn't take these problems seriously (enough)... > > > > I think info about where/how it freezing would be more helpful. > > No idea, the system just freezes, no drob to DDB no remote gdb no > nothing, so its really hard to tell where... > As to how, just boot current on a fairly fast machine, make a kernel > and it'll hang in minutes if not less, or just leave it alone and > it will hang in 10-30 mins... > > -Søren > > > 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 Thu Nov 16 9:46:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 83A2637B479 for ; Thu, 16 Nov 2000 09:46:40 -0800 (PST) Received: (qmail 64327 invoked by uid 100); 16 Nov 2000 17:46:39 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14868.7551.791920.252398@guru.mired.org> Date: Thu, 16 Nov 2000 11:46:39 -0600 (CST) To: "Andresen,Jason R." Cc: Garrett Wollman , void , freebsd-current@FreeBSD.ORG Subject: Re: Proper permissons on /var/mail In-Reply-To: <3A1412C1.96608727@mitre.org> References: <20001116151809.A15312@firedrake.org> <200011161636.LAA83126@khavrinen.lcs.mit.edu> <3A1412C1.96608727@mitre.org> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andresen,Jason R. types: > Garrett Wollman wrote: > > > > < said: > > > > > I have a similar problem -- every time I make world, perms on /var/mail > > > get set to 775. Mutt considers my mailbox read-only until I change it > > > to 1777. > > > > It is misconfigured (or perhaps just broken). 1777 mode for /var/mail > > is insecure, but was necessary in the mists of ancient past, before > > UNIX learned to do file locking. Unless your mail spool is shared > > over NFS (don't do that), locking is reliable and .lock files should > > never be used or relied upon. > > Not the FreeBSD's file locking works anyway. > Here's the results from a test of the below program: I can see at least two problems with the test program. 1) You're locking a shared descriptor. Possibly that should work, but it's not a case I normally see. Moving the open after the fork makes this behave better. 2) You're depending on a synchronization between the two process, but not doing anything to insure it. The correct test is not that the last message was the child string, but that the last two messages are the same. Actually, my first test was to change this to "lock, prompt, write, unlock, exit", then run it in two windows. The first process pauses - with the file locked - and the second hangs until the user responds to the prompt. (81 ~/bin/src): uname -a > FreeBSD escaflowne.el.hazard 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Sat > Oct 14 18:59:16 EDT 2000 > root@escaflowne.el.hazard:/usr/obj/usr/src/sys/ESCAFLOWNE i386 > (82 ~/bin/src): ./testflock > flock(2) is implemented, but not functional. > > And another test: > %kenshin (1 ~): uname -a > IRIX kenshin 6.5 01221642 IP20 > %kenshin (2 ~): ./testflock > flock(2) is fully functional. > > I hope I'm doing something wrong here, and that flock really does work > on FreeBSD. > > #include > #include > #include > #include > #include > #include > > #define TMPFILENAME "/tmp/testflock.out" > #define MESSLEN 8 > #define CHILDSTR "Child \n" > #define PARENTSTR "Parent\n" > > int main( int argc, char** argv) > { > char message[MESSLEN]; > int pid; > int fd; > int foo; > > fd = open(TMPFILENAME, O_WRONLY | O_CREAT, 0644); > > pid = fork(); > > if ( pid == 0 ) > { > strcpy(message, CHILDSTR); > sleep(1); > } > else > strcpy(message, PARENTSTR); > > > flock(fd, LOCK_EX); > > lseek(fd, 0, SEEK_END); > write(fd, message, MESSLEN - 1); > > sleep(2); > > lseek(fd, 0, SEEK_END); > write(fd, message, MESSLEN - 1); > > flock(fd, LOCK_UN); > > close(fd); > > if ( pid != 0 ) > { > wait(&foo); > > /* Test the file, see if flock works */ > fd = open(TMPFILENAME, O_RDONLY); > > read(fd, (void*)message, MESSLEN - 1); /* Discard first > */ > read(fd, (void*)message, MESSLEN - 1); > > if (! strcmp(message, CHILDSTR)) > printf("flock(2) is implemented, but not > functional.\n"); > else > printf("flock(2) is fully functional.\n"); > > close(fd); > } > > return 0; > } > > > -- > _ _ _ ___ ____ ___ ______________________________________ > / \/ \ | ||_ _|| _ \|___| | Jason Andresen -- jandrese@mitre.org > / /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those > /_/ \_\|_| |_| |_|\_\|___| | of the Mitre Corporation. > > > 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 Thu Nov 16 10:23:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from gmarco.ablia.net (freebsd.cofinco.it [194.243.20.91]) by hub.freebsd.org (Postfix) with ESMTP id 3386337B4CF for ; Thu, 16 Nov 2000 10:23:35 -0800 (PST) Received: (from gmarco@localhost) by gmarco.ablia.net (8.11.1/8.11.1) id eAGIEcY04692 for current@freebsd.org; Thu, 16 Nov 2000 19:14:38 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) X-Authentication-Warning: gmarco.ablia.net: gmarco set sender to gmarco@scotty.masternet.it using -f Date: Thu, 16 Nov 2000 19:14:38 +0100 From: Gianmarco Giovannelli To: current@freebsd.org Subject: Re: CURRENT is freezing again ... Message-ID: <20001116191438.B4629@gmarco.ablia.net> Reply-To: Gianmarco Giovannelli Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD gmarco.ablia.net 4.2-BETA i386 X-Organization: Ablia Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Boris Popov wrote: > > On Thu, 16 Nov 2000, Soren Schmidt wrote: > > > > > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > > > > 10 min after boot... > > > > > > You mean "is still freezing" right ? > > > > > > Current has been like this for longer than I care to think about, it > > > seems those in charge doesn't take these problems seriously (enough)... > > > > I think info about where/how it freezing would be more helpful. > > No idea, the system just freezes, no drob to DDB no remote gdb no > nothing, so its really hard to tell where... > As to how, just boot current on a fairly fast machine, make a kernel > and it'll hang in minutes if not less, or just leave it alone and > it will hang in 10-30 mins... I have the same problem on a dual PII 400mhz. I haven't tried to remove the SMP support, but I have not too much time to cvsup and to make anything else. I'll try to boot the GENERIC (damn !%&!& , I always repeat to myself that is a good habits to compile the GENERIC too after updates... but I never do... :-( ) -- Regards... Gianmarco "Unix expert since yesterday" http://www.giovannelli.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 10:44:27 2000 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 7430137B479 for ; Thu, 16 Nov 2000 10:44:25 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAGIgpi10148; Thu, 16 Nov 2000 10:42:51 -0800 (PST) Date: Thu, 16 Nov 2000 10:42:51 -0800 From: Alfred Perlstein To: "Steven E. Ames" Cc: Soren Schmidt , Boris Popov , Valentin Chopov , current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... Message-ID: <20001116104251.D830@fw.wintelcom.net> References: <200011161717.SAA30813@freebsd.dk> <027d01c04ff1$90d9cf40$8a1a050a@winstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <027d01c04ff1$90d9cf40$8a1a050a@winstar.com>; from steve@virtual-voodoo.com on Thu, Nov 16, 2000 at 12:20:49PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Steven E. Ames [001116 09:27] wrote: > It seems to only do it SMP... the same machine built with a non-SMP > kernel (same source code) runs just fine for extended periods. John just checked in some code last night that may address your problems. I would try a new kernel, and perhaps some collabaration with John to debug these problems rather than just complaining about the situation. I see at least two experianced developers in the CC list, there's no reason for these poor bug reports. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 16 10:51:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtpproxy1.mitre.org (mb-20-100.mitre.org [129.83.20.100]) by hub.freebsd.org (Postfix) with ESMTP id 63CE837B479 for ; Thu, 16 Nov 2000 10:51:29 -0800 (PST) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id NAA26084 for ; Thu, 16 Nov 2000 13:51:26 -0500 (EST) Received: from mailsrv2.mitre.org (mailsrv2.mitre.org [129.83.221.17]) by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id NAA20598 for ; Thu, 16 Nov 2000 13:51:25 -0500 (EST) Received: from mitre.org ([128.29.145.140]) by mailsrv2.mitre.org (Netscape Messaging Server 4.15) with ESMTP id G44SDO00.3IJ; Thu, 16 Nov 2000 13:51:24 -0500 Message-ID: <3A142C81.AE1A74F2@mitre.org> Date: Thu, 16 Nov 2000 13:50:41 -0500 From: "Andresen,Jason R." Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Meyer Cc: Garrett Wollman , void , freebsd-current@FreeBSD.ORG Subject: Re: Proper permissons on /var/mail References: <20001116151809.A15312@firedrake.org> <200011161636.LAA83126@khavrinen.lcs.mit.edu> <3A1412C1.96608727@mitre.org> <14868.7551.791920.252398@guru.mired.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > > Andresen,Jason R. types: > > Garrett Wollman wrote: > > > > > > < said: > > > > > > > I have a similar problem -- every time I make world, perms on /var/mail > > > > get set to 775. Mutt considers my mailbox read-only until I change it > > > > to 1777. > > > > > > It is misconfigured (or perhaps just broken). 1777 mode for /var/mail > > > is insecure, but was necessary in the mists of ancient past, before > > > UNIX learned to do file locking. Unless your mail spool is shared > > > over NFS (don't do that), locking is reliable and .lock files should > > > never be used or relied upon. > > > > Not the FreeBSD's file locking works anyway. > > Here's the results from a test of the below program: > > I can see at least two problems with the test program. > > 1) You're locking a shared descriptor. Possibly that should work, but > it's not a case I normally see. Moving the open after the fork > makes this behave better. Actually, it does work in Irix. I'll try that under FreeBSD.
Instructions for removal is at the bottom of this message.
If you have any questions regarding this e-mail, please send them to
emailto:info@afroconnections.com.
If you hit reply , you will automatically be removed from this list.
************************************************************************

Dear Friend,

We are AfroConnections.com  - leaders in providing African Americans
with the best way to meet each other for the purposes of friendship,
dating or joint activities.

Come and join tens of thousands of members who have already connected.

To get started "Today" and receive 3 FREE email contacts go to
http://www.afroconnections.com

Best Regards

Your Fri! ! ends at AfroConnections.com
(A member of SocialPlus.com network)

PS. Do not forget to tell a friend about us. Click here
http://www.afroconnections.com/recommend.asp
PPS. For more information, please contact us at
mailto:info@afroconnections.com



----------------------------------------------------------------------------
----------------------------------------------------------------------------

This email sent by http://www.EmailFactory.com
The Web-Based Precision Opt-In Email Marketing Solution.

----------------------------------------------------------------------------
----------------------------------------------------------------------------
To UNSUBSCRIBE from this mailing list:

Reply to this message with the w! ! ord 'unsubscribe' as the subject

OR

To UNSUBSCRIBE from this mailing list, go to:

http://UNSUBSCRIBE.EmailFactory.com/handler/default.cfm?action=optout&func=removeMe&idAddress=L5062566403%2E2910
----------------------------------------------------------------------------
----------------------------------------------------------------------------











Hi There! --00037DF1E4131A14A2D208058079B0F2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 1:13:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3AF4937B479; Fri, 17 Nov 2000 01:13:39 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA55095; Fri, 17 Nov 2000 10:12:40 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200011170912.KAA55095@freebsd.dk> Subject: Re: CURRENT is freezing again ... In-Reply-To: <20001116201426.A73761@peorth.iteration.net> from "Michael C . Wu" at "Nov 16, 2000 08:14:26 pm" To: keichii@peorth.iteration.net (Michael C . Wu) Date: Fri, 17 Nov 2000 10:12:40 +0100 (CET) Cc: jhb@FreeBSD.ORG (John Baldwin), valentin@valcho.net (Valentin Chopov), current@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 Michael C . Wu wrote: > I had those problems too a while ago on a UP p3-650 laptop. Finally I just > newfs'ed the machine and installed the 20001028 snapshot, then cvsupp'ed > to 20001122. The laptop now works well. What I saw was processes > forking and forking again until the machine runs out of memory and > swap. I think it may be some old libraries left over from > upgrades and make world. Hmm, this is a new installed box, so there is no old leftovers... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 1:36:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from doormat.odey.co.uk (doormat.odey.co.uk [195.13.88.6]) by hub.freebsd.org (Postfix) with ESMTP id AAAD937B479; Fri, 17 Nov 2000 01:36:07 -0800 (PST) Received: (from proxy@localhost) by doormat.odey.co.uk (8.9.3/8.9.3) id JAA06639; Fri, 17 Nov 2000 09:36:03 GMT Received: from (odeydom.odey.co.uk [194.70.107.4]) by doormat.odey.co.uk via smap (V2.1) id xma006622; Fri, 17 Nov 00 09:36:00 GMT To: stable@freebsd.org, current@freebsd.org Subject: subscribe X-Mailer: Lotus Notes Release 5.0.4a July 24, 2000 Message-ID: From: "Blair Sutton/Odey" Date: Fri, 17 Nov 2000 09:35:58 +0000 X-MIMETrack: Serialize by Router on odeydom/Odey(Release 5.0.5 |September 22, 2000) at 11/17/2000 09:35:59 AM, Serialize complete at 11/17/2000 09:35:59 AM MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 2:58:28 2000 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 7EB7037B4C5 for ; Fri, 17 Nov 2000 02:58:25 -0800 (PST) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 4F33D2CE38; Fri, 17 Nov 2000 12:58:12 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.1/8.11.1) id eAHAvhf22476; Fri, 17 Nov 2000 12:57:43 +0200 (EET) (envelope-from vallo) Date: Fri, 17 Nov 2000 12:57:43 +0200 From: Vallo Kallaste To: void Cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: Proper permissons on /tmp Message-ID: <20001117125743.A22423@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20001116151809.A15312@firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20001116151809.A15312@firedrake.org>; from float@firedrake.org on Thu, Nov 16, 2000 at 03:18:09PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 16, 2000 at 03:18:09PM +0000, void wrote: > I have a similar problem -- every time I make world, perms on /var/mail > get set to 775. Mutt considers my mailbox read-only until I change it > to 1777. Is there a supported way to locally override BSD.var.dist, or > do I need to install mutt setgid mail, or what? Be sure that mutt_dotlock is setgid mail and is a member of group mail. Just got the same thing yesterday while trying out CVS version of Mutt. -- 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 Fri Nov 17 3:50:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id BB1CB37B479 for ; Fri, 17 Nov 2000 03:50:24 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13wk1W-0006fj-00; Fri, 17 Nov 2000 13:49:42 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id NAA29610; Fri, 17 Nov 2000 13:49:49 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 29409; Fri Nov 17 13:48:36 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13wk0S-0000lt-00; Fri, 17 Nov 2000 13:48:36 +0200 From: Sheldon Hearn To: Alfred Perlstein Cc: "Steven E. Ames" , Soren Schmidt , Boris Popov , Valentin Chopov , current@freebsd.org Subject: Re: CURRENT is freezing again ... In-reply-to: Your message of "Thu, 16 Nov 2000 10:42:51 PST." <20001116104251.D830@fw.wintelcom.net> Date: Fri, 17 Nov 2000 13:48:35 +0200 Message-ID: <2967.974461715@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Nov 2000 10:42:51 PST, Alfred Perlstein wrote: > I would try a new kernel, and perhaps some collabaration with John > to debug these problems rather than just complaining about the > situation. I see at least two experianced developers in the CC > list, there's no reason for these poor bug reports. The problem with a hard lock-up out of which you can't escape into the debugger is that it makes meaningful bug reports impossible. My non-SMP workstation has exhibited apparently arbitrary lock-ups since the advent of SMPng. I thought I was the only one, since my question on the freebsd-current mailing list went unanswered. From my understanding, John's WITNESS code allows us to break into the debugger from within interrupt context. If the lock-ups are happening in there, then this may help us provide better bug reports. Oh, and a couple of deep breaths are probably in order. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 3:53:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id E9F7F37B4C5 for ; Fri, 17 Nov 2000 03:53:41 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13wk54-0006iO-00; Fri, 17 Nov 2000 13:53:22 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id NAA00379; Fri, 17 Nov 2000 13:53:30 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 213; Fri Nov 17 13:52:27 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13wk4B-0000nd-00; Fri, 17 Nov 2000 13:52:27 +0200 From: Sheldon Hearn To: void Cc: Leif Neland , freebsd-current@freebsd.org Subject: Re: Proper permissons on /tmp In-reply-to: Your message of "Thu, 16 Nov 2000 15:18:09 GMT." <20001116151809.A15312@firedrake.org> Date: Fri, 17 Nov 2000 13:52:27 +0200 Message-ID: <3076.974461947@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Nov 2000 15:18:09 GMT, void wrote: > I have a similar problem -- every time I make world, perms on /var/mail > get set to 775. Mutt considers my mailbox read-only until I change it > to 1777. Is there a supported way to locally override BSD.var.dist, or > do I need to install mutt setgid mail, or what? You get two answers here. 1) 1777 on /var/mail is bad, bad, bad. Don't do that. 2) The easiest way to override the permissions and ownerships enforced during a make world is to use CVS to update your sources so that your local hacks to src/etc/mtree/BSD.*.dist are not overwritten on update. There are other ways, but the bottom line is that you should find a way to ensure that those files are modified to your taste before every world update. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 3:57:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3832337B479 for ; Fri, 17 Nov 2000 03:57:12 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA92493; Fri, 17 Nov 2000 12:55:28 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200011171155.MAA92493@freebsd.dk> Subject: Re: CURRENT is freezing again ... In-Reply-To: <2967.974461715@axl.fw.uunet.co.za> from Sheldon Hearn at "Nov 17, 2000 01:48:35 pm" To: sheldonh@uunet.co.za (Sheldon Hearn) Date: Fri, 17 Nov 2000 12:55:28 +0100 (CET) Cc: bright@wintelcom.net (Alfred Perlstein), steve@virtual-voodoo.com (Steven E. Ames), bp@butya.kz (Boris Popov), valentin@valcho.net (Valentin Chopov), current@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 Sheldon Hearn wrote: > > I would try a new kernel, and perhaps some collabaration with John > > to debug these problems rather than just complaining about the > > situation. I see at least two experianced developers in the CC > > list, there's no reason for these poor bug reports. > > The problem with a hard lock-up out of which you can't escape into the > debugger is that it makes meaningful bug reports impossible. My non-SMP > workstation has exhibited apparently arbitrary lock-ups since the advent > of SMPng. > > I thought I was the only one, since my question on the freebsd-current > mailing list went unanswered. You are _not_ alone, there has been numerous complains about this on the list, but so far they have not been taken seriously :| > >From my understanding, John's WITNESS code allows us to break into the > debugger from within interrupt context. If the lock-ups are happening > in there, then this may help us provide better bug reports. It doesn't help here at least, the machine(s) just lock up solid only reset or a powercycle can bring them back... > Oh, and a couple of deep breaths are probably in order. :-) Yeah like *sigh* .... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 4:50:15 2000 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 D4C4637B479 for ; Fri, 17 Nov 2000 04:50:12 -0800 (PST) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id EFDDA2CE38; Fri, 17 Nov 2000 14:50:03 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.1/8.11.1) id eAHCnZG48740; Fri, 17 Nov 2000 14:49:35 +0200 (EET) (envelope-from vallo) Date: Fri, 17 Nov 2000 14:49:35 +0200 From: Vallo Kallaste To: Sheldon Hearn Cc: void , Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: Proper permissons on /tmp Message-ID: <20001117144935.A44763@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20001116151809.A15312@firedrake.org> <3076.974461947@axl.fw.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3076.974461947@axl.fw.uunet.co.za>; from sheldonh@uunet.co.za on Fri, Nov 17, 2000 at 01:52:27PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 17, 2000 at 01:52:27PM +0200, Sheldon Hearn wrote: > > I have a similar problem -- every time I make world, perms on /var/mail > > get set to 775. Mutt considers my mailbox read-only until I change it > > to 1777. Is there a supported way to locally override BSD.var.dist, or > > do I need to install mutt setgid mail, or what? > > You get two answers here. [snip] Don't install mutt setgid mail, the mutt_dotlock external program is supposed to be setgid mail. This is what it looks like in my system: 8 -rwxr-xr-x 1 vallo wheel 6740 Nov 16 10:48 flea* 480 -rwxr-xr-x 1 vallo wheel 460808 Nov 16 10:49 mutt* 8 -rwxr-sr-x 1 vallo mail 7288 Nov 16 10:49 mutt_dotlock* 2 -rwxr-xr-x 1 vallo wheel 26 Nov 16 10:48 muttbug* 2 -rwxr-xr-x 1 vallo wheel 274 Nov 16 10:48 pgpewrap* 24 -rwxr-xr-x 1 vallo wheel 22700 Nov 16 10:49 pgpring* -- 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 Fri Nov 17 5:12:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mharnois.workgroup.net (unknown [24.11.39.39]) by hub.freebsd.org (Postfix) with ESMTP id D8E0E37B4C5 for ; Fri, 17 Nov 2000 05:12:43 -0800 (PST) Received: (from mdharnois@localhost) by mharnois.workgroup.net (8.11.1/8.11.1) id eAHDChD56184; Fri, 17 Nov 2000 07:12:43 -0600 (CST) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... References: <200011171155.MAA92493@freebsd.dk> From: Michael Harnois Date: 17 Nov 2000 07:12:42 -0600 In-Reply-To: <200011171155.MAA92493@freebsd.dk> Message-ID: <86u296agj9.fsf@mharnois.workgroup.net> Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Notus) 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, 17 Nov 2000 12:55:28 +0100 (CET), Soren Schmidt said: > It doesn't help here at least, the machine(s) just lock up solid > only reset or a powercycle can bring them back... Same here ... as others noted, started with SMPng ... -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org There are things that are so serious that you can only joke about them. -- Werner Heisenberg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 5:55:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from castle.jp.freebsd.org (castle.jp.FreeBSD.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 6451437B479 for ; Fri, 17 Nov 2000 05:55:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id WAA16417 for ; Fri, 17 Nov 2000 22:55:35 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <20001114121517.B78808@dragon.nuxi.com> References: <3A10B967.C3301113@cup.hp.com> <3A10B967.C3301113@cup.hp.com> <20001114121517.B78808@dragon.nuxi.com> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Notus) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 399 From: Makoto MATSUSHITA To: current@FreeBSD.ORG Subject: Re: RQ review: [was: Re: "make modules" kicks the first module directory twice] Date: Fri, 17 Nov 2000 22:55:32 +0900 Message-Id: <20001117225532X.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG obrien> [its easier to read patches when they aren't quoted in their entirety ;-)] Attached below is a patch which I've made before. If nothing is going wrong, please commit this change.... current.jp.FreeBSD.org which employs 'make -j' option have missed -current release since the beginning of this month. -- - Makoto `MAR' MATSUSHITA Index: Makefile =================================================================== RCS file: /lab/FreeBSD/FreeBSD.cvs/src/release/Makefile,v retrieving revision 1.585 diff -c -r1.585 Makefile *** Makefile 2000/11/12 11:04:11 1.585 --- Makefile 2000/11/13 05:37:12 *************** *** 831,837 **** @rm -f ${RD}/kernels/*.ko @cd ${.CURDIR}/../sys/${MACHINE}/conf && config ${KERNEL} @cd ${.CURDIR}/../sys/compile/${KERNEL} && \ ! make kernel-depend && \ make ${KERNEL_FLAGS} modules && \ make modules-reinstall DESTDIR=${RD}/kernels && \ --- 831,837 ---- @rm -f ${RD}/kernels/*.ko @cd ${.CURDIR}/../sys/${MACHINE}/conf && config ${KERNEL} @cd ${.CURDIR}/../sys/compile/${KERNEL} && \ ! make modules-depend && \ make ${KERNEL_FLAGS} modules && \ make modules-reinstall DESTDIR=${RD}/kernels && \ Index: Makefile.alpha =================================================================== RCS file: /lab/FreeBSD/FreeBSD.cvs/src/sys/conf/Makefile.alpha,v retrieving revision 1.79 diff -c -r1.79 Makefile.alpha *** Makefile.alpha 2000/10/29 09:47:50 1.79 --- Makefile.alpha 2000/11/14 01:55:17 *************** *** 252,258 **** echo ${CFILES} | tr -s ' ' '\12' | sed 's/\.c/.o/' | \ sort -u | comm -23 - dontlink | \ sed 's,../.*/\(.*.o\),rm -f \1;ln -s ../GENERIC/\1 \1,' > makelinks ! sh makelinks && rm -f dontlink kernel-tags: @[ -f .depend ] || { echo "you must make depend first"; exit 1; } --- 252,258 ---- echo ${CFILES} | tr -s ' ' '\12' | sed 's/\.c/.o/' | \ sort -u | comm -23 - dontlink | \ sed 's,../.*/\(.*.o\),rm -f \1;ln -s ../GENERIC/\1 \1,' > makelinks ! sh makelinks; rm -f dontlink kernel-tags: @[ -f .depend ] || { echo "you must make depend first"; exit 1; } *************** *** 309,338 **** MKMODULESENV= MAKEOBJDIRPREFIX=${.OBJDIR}/modules KMODDIR=${KODIR} modules: ! @mkdir -p ${.OBJDIR}/modules ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj all modules-depend: @mkdir -p ${.OBJDIR}/modules ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj depend modules-clean: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} clean modules-cleandepend: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} cleandepend modules-cleandir: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} cleandir modules-tags: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} tags modules-install modules-install.debug: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} install modules-reinstall modules-reinstall.debug: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} install config.o: ${NORMAL_C} --- 309,342 ---- MKMODULESENV= MAKEOBJDIRPREFIX=${.OBJDIR}/modules KMODDIR=${KODIR} modules: ! @if [ ! -d ${.OBJDIR}/modules ]; then \ ! echo You must run make depend before building modules; \ ! exit 1; \ ! fi ! cd $S/modules; env ${MKMODULESENV} ${MAKE} all modules-depend: @mkdir -p ${.OBJDIR}/modules ! cd $S/modules; env ${MKMODULESENV} ${MAKE} obj; \ ! env ${MKMODULESENV} ${MAKE} depend modules-clean: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} clean modules-cleandepend: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} cleandepend modules-cleandir: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} cleandir modules-tags: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} tags modules-install modules-install.debug: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} install modules-reinstall modules-reinstall.debug: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} install config.o: ${NORMAL_C} Index: Makefile.i386 =================================================================== RCS file: /lab/FreeBSD/FreeBSD.cvs/src/sys/conf/Makefile.i386,v retrieving revision 1.212 diff -c -r1.212 Makefile.i386 *** Makefile.i386 2000/10/29 09:47:50 1.212 --- Makefile.i386 2000/11/14 01:55:15 *************** *** 212,218 **** echo ${CFILES} | tr -s ' ' '\12' | sed 's/\.c/.o/' | \ sort -u | comm -23 - dontlink | \ sed 's,../.*/\(.*.o\),rm -f \1;ln -s ../GENERIC/\1 \1,' > makelinks ! sh makelinks && rm -f dontlink kernel-tags: @[ -f .depend ] || { echo "you must make depend first"; exit 1; } --- 212,218 ---- echo ${CFILES} | tr -s ' ' '\12' | sed 's/\.c/.o/' | \ sort -u | comm -23 - dontlink | \ sed 's,../.*/\(.*.o\),rm -f \1;ln -s ../GENERIC/\1 \1,' > makelinks ! sh makelinks; rm -f dontlink kernel-tags: @[ -f .depend ] || { echo "you must make depend first"; exit 1; } *************** *** 270,299 **** MKMODULESENV= MAKEOBJDIRPREFIX=${.OBJDIR}/modules KMODDIR=${KODIR} modules: ! @mkdir -p ${.OBJDIR}/modules ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj all modules-depend: @mkdir -p ${.OBJDIR}/modules ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj depend modules-clean: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} clean modules-cleandepend: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} cleandepend modules-cleandir: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} cleandir modules-tags: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} tags modules-install modules-install.debug: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} install modules-reinstall modules-reinstall.debug: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} install config.o: ${NORMAL_C} --- 270,303 ---- MKMODULESENV= MAKEOBJDIRPREFIX=${.OBJDIR}/modules KMODDIR=${KODIR} modules: ! @if [ ! -d ${.OBJDIR}/modules ]; then \ ! echo You must run make depend before building modules; \ ! exit 1; \ ! fi ! cd $S/modules; env ${MKMODULESENV} ${MAKE} all modules-depend: @mkdir -p ${.OBJDIR}/modules ! cd $S/modules; env ${MKMODULESENV} ${MAKE} obj; \ ! env ${MKMODULESENV} ${MAKE} depend modules-clean: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} clean modules-cleandepend: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} cleandepend modules-cleandir: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} cleandir modules-tags: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} tags modules-install modules-install.debug: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} install modules-reinstall modules-reinstall.debug: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} install config.o: ${NORMAL_C} Index: Makefile.ia64 =================================================================== RCS file: /lab/FreeBSD/FreeBSD.cvs/src/sys/conf/Makefile.ia64,v retrieving revision 1.4 diff -c -r1.4 Makefile.ia64 *** Makefile.ia64 2000/10/29 09:47:50 1.4 --- Makefile.ia64 2000/11/14 01:55:27 *************** *** 217,223 **** echo ${CFILES} | tr -s ' ' '\12' | sed 's/\.c/.o/' | \ sort -u | comm -23 - dontlink | \ sed 's,../.*/\(.*.o\),rm -f \1;ln -s ../GENERIC/\1 \1,' > makelinks ! sh makelinks && rm -f dontlink kernel-tags: @[ -f .depend ] || { echo "you must make depend first"; exit 1; } --- 217,223 ---- echo ${CFILES} | tr -s ' ' '\12' | sed 's/\.c/.o/' | \ sort -u | comm -23 - dontlink | \ sed 's,../.*/\(.*.o\),rm -f \1;ln -s ../GENERIC/\1 \1,' > makelinks ! sh makelinks; rm -f dontlink kernel-tags: @[ -f .depend ] || { echo "you must make depend first"; exit 1; } *************** *** 274,303 **** MKMODULESENV= MAKEOBJDIRPREFIX=${.OBJDIR}/modules KMODDIR=${KODIR} modules: ! @mkdir -p ${.OBJDIR}/modules ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj all modules-depend: @mkdir -p ${.OBJDIR}/modules ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj depend modules-clean: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} clean modules-cleandepend: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} cleandepend modules-cleandir: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} cleandir modules-tags: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} tags modules-install modules-install.debug: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} install modules-reinstall modules-reinstall.debug: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} install config.o: ${NORMAL_C} --- 274,307 ---- MKMODULESENV= MAKEOBJDIRPREFIX=${.OBJDIR}/modules KMODDIR=${KODIR} modules: ! @if [ ! -d ${.OBJDIR}/modules ]; then \ ! echo You must run make depend before building modules; \ ! exit 1; \ ! fi ! cd $S/modules; env ${MKMODULESENV} ${MAKE} all modules-depend: @mkdir -p ${.OBJDIR}/modules ! cd $S/modules; env ${MKMODULESENV} ${MAKE} obj; \ ! env ${MKMODULESENV} ${MAKE} depend modules-clean: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} clean modules-cleandepend: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} cleandepend modules-cleandir: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} cleandir modules-tags: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} tags modules-install modules-install.debug: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} install modules-reinstall modules-reinstall.debug: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} install config.o: ${NORMAL_C} Index: Makefile.pc98 =================================================================== RCS file: /lab/FreeBSD/FreeBSD.cvs/src/sys/conf/Makefile.pc98,v retrieving revision 1.110 diff -c -r1.110 Makefile.pc98 *** Makefile.pc98 2000/11/05 14:31:17 1.110 --- Makefile.pc98 2000/11/14 01:55:50 *************** *** 215,221 **** echo ${CFILES} | tr -s ' ' '\12' | sed 's/\.c/.o/' | \ sort -u | comm -23 - dontlink | \ sed 's,../.*/\(.*.o\),rm -f \1;ln -s ../GENERIC/\1 \1,' > makelinks ! sh makelinks && rm -f dontlink kernel-tags: @[ -f .depend ] || { echo "you must make depend first"; exit 1; } --- 215,221 ---- echo ${CFILES} | tr -s ' ' '\12' | sed 's/\.c/.o/' | \ sort -u | comm -23 - dontlink | \ sed 's,../.*/\(.*.o\),rm -f \1;ln -s ../GENERIC/\1 \1,' > makelinks ! sh makelinks; rm -f dontlink kernel-tags: @[ -f .depend ] || { echo "you must make depend first"; exit 1; } *************** *** 273,302 **** MKMODULESENV= MAKEOBJDIRPREFIX=${.OBJDIR}/modules KMODDIR=${KODIR} modules: ! @mkdir -p ${.OBJDIR}/modules ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj all modules-depend: @mkdir -p ${.OBJDIR}/modules ! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj depend modules-clean: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} clean modules-cleandepend: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} cleandepend modules-cleandir: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} cleandir modules-tags: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} tags modules-install modules-install.debug: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} install modules-reinstall modules-reinstall.debug: ! cd $S/modules && env ${MKMODULESENV} ${MAKE} install config.o: ${NORMAL_C} --- 273,306 ---- MKMODULESENV= MAKEOBJDIRPREFIX=${.OBJDIR}/modules KMODDIR=${KODIR} modules: ! @if [ ! -d ${.OBJDIR}/modules ]; then \ ! echo You must run make depend before building modules; \ ! exit 1; \ ! fi ! cd $S/modules; env ${MKMODULESENV} ${MAKE} all modules-depend: @mkdir -p ${.OBJDIR}/modules ! cd $S/modules; env ${MKMODULESENV} ${MAKE} obj; \ ! env ${MKMODULESENV} ${MAKE} depend modules-clean: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} clean modules-cleandepend: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} cleandepend modules-cleandir: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} cleandir modules-tags: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} tags modules-install modules-install.debug: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} install modules-reinstall modules-reinstall.debug: ! cd $S/modules; env ${MKMODULESENV} ${MAKE} install config.o: ${NORMAL_C} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 6:47:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from liono.newc.com (c207-207-134-48.ip.newc.com [207.207.134.48]) by hub.freebsd.org (Postfix) with ESMTP id 9630037B479 for ; Fri, 17 Nov 2000 06:47:21 -0800 (PST) Received: from localhost (mail@localhost) by liono.newc.com (8.9.3/8.9.3) with SMTP id KAA24446 for ; Fri, 17 Nov 2000 10:50:46 -0500 Date: Fri, 17 Nov 2000 10:50:32 -0500 Message-Id: <200011171550.KAA24446@liono.newc.com> X-Authentication-Warning: liono.newc.com: mail@localhost didn't use HELO protocol From: afroconnection2@emailfactory.net To: current@freebsd.org Subject: Unsubscribed from AfroConnection2 Reply-To: afroconnection2@emailfactory.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear , You have just been removed from the following EmailFactory Mailing Lists: 1.- AfroConnection2 Thank You. Sincerely, EmailFactory.com staff. ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- This email sent by http://www.EmailFactory.com The Web-Based Precision Opt-In Email Marketing Solution. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 10:10:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from io.yi.org (h24-69-199-88.gv.shawcable.net [24.69.199.88]) by hub.freebsd.org (Postfix) with ESMTP id DBC2937B479 for ; Fri, 17 Nov 2000 10:10:56 -0800 (PST) Received: from io.yi.org (localhost.gvcl1.bc.wave.home.com [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id 3AD0EBA7A for ; Fri, 17 Nov 2000 10:10:57 -0800 (PST) X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: heads up: sizeof proc changed Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Nov 2000 10:10:57 -0800 From: Jake Burkholder Message-Id: <20001117181057.3AD0EBA7A@io.yi.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As usual, you'll have to recompile all libkvm using programs. Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 10:26:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0236E37B479 for ; Fri, 17 Nov 2000 10:26:13 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAHIQ6Q06264; Fri, 17 Nov 2000 11:26:07 -0700 (MST) (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 LAA75925; Fri, 17 Nov 2000 11:26:02 -0700 (MST) Message-Id: <200011171826.LAA75925@harmony.village.org> To: Sheldon Hearn Subject: Re: CURRENT is freezing again ... Cc: Alfred Perlstein , "Steven E. Ames" , Soren Schmidt , Boris Popov , Valentin Chopov , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 17 Nov 2000 13:48:35 +0200." <2967.974461715@axl.fw.uunet.co.za> References: <2967.974461715@axl.fw.uunet.co.za> Date: Fri, 17 Nov 2000 11:26:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <2967.974461715@axl.fw.uunet.co.za> Sheldon Hearn writes: : The problem with a hard lock-up out of which you can't escape into the : debugger is that it makes meaningful bug reports impossible. My non-SMP : workstation has exhibited apparently arbitrary lock-ups since the advent : of SMPng. You can also short IOCHK to ground to get an NMI which kicks you into the debugger, even in an interrupt context. I have a card I built from an old multi-function card to do this. I think it is A1 and A2, but I don't have my ISA bus spec handy. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 10:30:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 7B9D837B657 for ; Fri, 17 Nov 2000 10:30:31 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAHITLB96209; Fri, 17 Nov 2000 10:29:21 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <2967.974461715@axl.fw.uunet.co.za> Date: Fri, 17 Nov 2000 10:30:02 -0800 (PST) From: John Baldwin To: Sheldon Hearn Subject: Re: CURRENT is freezing again ... Cc: current@FreeBSD.org, Valentin Chopov , Boris Popov , Soren Schmidt , "Steven E. Ames" , Alfred Perlstein Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Nov-00 Sheldon Hearn wrote: > > > On Thu, 16 Nov 2000 10:42:51 PST, Alfred Perlstein wrote: > >> I would try a new kernel, and perhaps some collabaration with John >> to debug these problems rather than just complaining about the >> situation. I see at least two experianced developers in the CC >> list, there's no reason for these poor bug reports. > > The problem with a hard lock-up out of which you can't escape into the > debugger is that it makes meaningful bug reports impossible. My non-SMP > workstation has exhibited apparently arbitrary lock-ups since the advent > of SMPng. When I get a hard lock like this I usually try to see if I can reproduce it in single user mode. If I can, then I compile KTR into my kernel with the following options: KTR, KTR_EXTEND, KTR_COMPILE="0x3fffffff", KTR_MASK="(KTR_INTR|KTR_PROC)". Then I boot into single user (so I don't dirty filesystems), mount any needed fs's as read only if possible, and run the following command: # sysctl -w debug.ktr_verbose=1 ; command_that_makes_my_machine_go_boom And then stare at the tracing output on teh screen to see what the machine was doing when it hung. I.e., to see if it is still getting interrupts, and to see what process it died in, etc. > From my understanding, John's WITNESS code allows us to break into the > debugger from within interrupt context. If the lock-ups are happening > in there, then this may help us provide better bug reports. Err, not quite. It's BSD/OS's WITNESS code, and what the WITNESS code does is perform extra checks on mutex enter's and exit's to ensure that we aren't handling mutexes in such a way that a deadlock is possible. Thus, it verifies that you don't grab mutexes out of order, or that you don't grab sleep mutexes with interrupts disabled, etc. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 10:32:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 300BA37B479 for ; Fri, 17 Nov 2000 10:32:45 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAHIp7725638; Fri, 17 Nov 2000 19:51:07 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Sheldon Hearn , Alfred Perlstein , "Steven E. Ames" , Soren Schmidt , Boris Popov , Valentin Chopov , current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... In-Reply-To: Your message of "Fri, 17 Nov 2000 11:26:02 MST." <200011171826.LAA75925@harmony.village.org> Date: Fri, 17 Nov 2000 19:51:07 +0100 Message-ID: <25636.974487067@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011171826.LAA75925@harmony.village.org>, Warner Losh writes: >In message <2967.974461715@axl.fw.uunet.co.za> Sheldon Hearn writes: >: The problem with a hard lock-up out of which you can't escape into the >: debugger is that it makes meaningful bug reports impossible. My non-SMP >: workstation has exhibited apparently arbitrary lock-ups since the advent >: of SMPng. > >You can also short IOCHK to ground to get an NMI which kicks you into >the debugger, even in an interrupt context. Bad news for you warner: On a too large sample of my newer motherboards this doesn't work anymore :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 10:34:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5F50E37B4C5 for ; Fri, 17 Nov 2000 10:34:08 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAHIY6Q06373; Fri, 17 Nov 2000 11:34:07 -0700 (MST) (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 LAA76119; Fri, 17 Nov 2000 11:34:06 -0700 (MST) Message-Id: <200011171834.LAA76119@harmony.village.org> To: Poul-Henning Kamp Subject: Re: CURRENT is freezing again ... Cc: Sheldon Hearn , Alfred Perlstein , "Steven E. Ames" , Soren Schmidt , Boris Popov , Valentin Chopov , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 17 Nov 2000 19:51:07 +0100." <25636.974487067@critter> References: <25636.974487067@critter> Date: Fri, 17 Nov 2000 11:34:06 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <25636.974487067@critter> Poul-Henning Kamp writes: : In message <200011171826.LAA75925@harmony.village.org>, Warner Losh writes: : >In message <2967.974461715@axl.fw.uunet.co.za> Sheldon Hearn writes: : >: The problem with a hard lock-up out of which you can't escape into the : >: debugger is that it makes meaningful bug reports impossible. My non-SMP : >: workstation has exhibited apparently arbitrary lock-ups since the advent : >: of SMPng. : > : >You can also short IOCHK to ground to get an NMI which kicks you into : >the debugger, even in an interrupt context. : : Bad news for you warner: On a too large sample of my newer : motherboards this doesn't work anymore :-( There's also a pci signal that you can either pull up or pull down that's supposed to give you the same results. I've never really needed to know it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 10:36:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 01D5E37B479 for ; Fri, 17 Nov 2000 10:36:12 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13wqMt-0004pa-00; Fri, 17 Nov 2000 18:36:11 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eAH6duL01025; Fri, 17 Nov 2000 07:39:56 +0100 (CET) (envelope-from wkb) Date: Fri, 17 Nov 2000 07:39:56 +0100 From: Wilko Bulte To: Warner Losh Cc: Sheldon Hearn , Alfred Perlstein , "Steven E. Ames" , Soren Schmidt , Boris Popov , Valentin Chopov , current@freebsd.org Subject: Re: CURRENT is freezing again ... Message-ID: <20001117073956.C814@freebie.demon.nl> References: <2967.974461715@axl.fw.uunet.co.za> <200011171826.LAA75925@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200011171826.LAA75925@harmony.village.org>; from imp@village.org on Fri, Nov 17, 2000 at 11:26:02AM -0700 X-OS: FreeBSD 4.2-BETA X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 17, 2000 at 11:26:02AM -0700, Warner Losh wrote: > In message <2967.974461715@axl.fw.uunet.co.za> Sheldon Hearn writes: > : The problem with a hard lock-up out of which you can't escape into the > : debugger is that it makes meaningful bug reports impossible. My non-SMP > : workstation has exhibited apparently arbitrary lock-ups since the advent > : of SMPng. > > You can also short IOCHK to ground to get an NMI which kicks you into > the debugger, even in an interrupt context. I have a card I built > from an old multi-function card to do this. I think it is A1 and A2, > but I don't have my ISA bus spec handy. Just stick a metal pin (ballpoint works well) into the ISA connector between the pins closest to the back of the machine. That is IOCHKN and GND respectively. Wilko [hardware designer gone bad..] -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 13:26:15 2000 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 D0F8737B479 for ; Fri, 17 Nov 2000 13:26:11 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA01786; Fri, 17 Nov 2000 13:26:09 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eAHLQ4E26014; Fri, 17 Nov 2000 13:26:04 -0800 (PST) (envelope-from obrien) Date: Fri, 17 Nov 2000 13:26:02 -0800 From: "David O'Brien" To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: RQ review: [was: Re: "make modules" kicks the first module directory twice] Message-ID: <20001117132602.A25729@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <3A10B967.C3301113@cup.hp.com> <3A10B967.C3301113@cup.hp.com> <20001114121517.B78808@dragon.nuxi.com> <20001117225532X.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001117225532X.matusita@jp.FreeBSD.org>; from matusita@jp.freebsd.org on Fri, Nov 17, 2000 at 10:55:32PM +0900 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 17, 2000 at 10:55:32PM +0900, Makoto MATSUSHITA wrote: > Attached below is a patch which I've made before. If nothing is going > wrong, please commit this change.... I committed something simular. BTW, you made ``make depend'' a requirement, which we did not have agreement on. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 13:29:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id AF9EA37B479; Fri, 17 Nov 2000 13:29:42 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13wt23-0004EK-00; Fri, 17 Nov 2000 23:26:51 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id XAA23375; Fri, 17 Nov 2000 23:26:51 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 23180; Fri Nov 17 23:25:33 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13wt0m-000HFR-00; Fri, 17 Nov 2000 23:25:32 +0200 From: Sheldon Hearn To: John Baldwin Cc: current@freebsd.org, Valentin Chopov , Boris Popov , Soren Schmidt , "Steven E. Ames" , Alfred Perlstein Subject: Re: CURRENT is freezing again ... In-reply-to: Your message of "Fri, 17 Nov 2000 10:30:02 PST." Date: Fri, 17 Nov 2000 23:25:32 +0200 Message-ID: <66304.974496332@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Nov 2000 10:30:02 PST, John Baldwin wrote: > # sysctl -w debug.ktr_verbose=1 ; command_that_makes_my_machine_go_boom All very well and good once you've figured out which command makes your machine go boom. But as I said, the locks I'm getting appear completely arbitrary. I'm no hard-core hacker, but I'm not completely clueless when it comes to isolating problems by way of deductive reasoning, and I'm stumped as to what's causing these. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 14: 6:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 78C8537B479; Fri, 17 Nov 2000 14:06:16 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAHM62B04909; Fri, 17 Nov 2000 14:06:02 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001117132602.A25729@dragon.nuxi.com> Date: Fri, 17 Nov 2000 14:06:44 -0800 (PST) From: John Baldwin To: "David O'Brien" Subject: Re: RQ review: [was: Re: "make modules" kicks the first module d Cc: current@FreeBSD.org, Makoto MATSUSHITA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Nov-00 David O'Brien wrote: > On Fri, Nov 17, 2000 at 10:55:32PM +0900, Makoto MATSUSHITA wrote: >> Attached below is a patch which I've made before. If nothing is going >> wrong, please commit this change.... > > I committed something simular. BTW, you made ``make depend'' a > requirement, which we did not have agreement on. Erm: > config -g LAPTOP Don't forget to do a ``make depend'' Kernel build directory is ../../compile/LAPTOP make depend is already a requirement. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 14: 9: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 702FC37B479 for ; Fri, 17 Nov 2000 14:08:57 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAHM61B04905; Fri, 17 Nov 2000 14:06:01 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <66304.974496332@axl.fw.uunet.co.za> Date: Fri, 17 Nov 2000 14:06:43 -0800 (PST) From: John Baldwin To: Sheldon Hearn Subject: Re: CURRENT is freezing again ... Cc: Alfred Perlstein Cc: Alfred Perlstein , "Steven E. Ames" , Soren Schmidt , Boris Popov , Valentin Chopov , current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Nov-00 Sheldon Hearn wrote: > > > On Fri, 17 Nov 2000 10:30:02 PST, John Baldwin wrote: > >> # sysctl -w debug.ktr_verbose=1 ; command_that_makes_my_machine_go_boom > > All very well and good once you've figured out which command makes your > machine go boom. Yes, I know. I didn't say the method was perfect. I find it frustrating as well. :-/ > But as I said, the locks I'm getting appear completely arbitrary. I'm > no hard-core hacker, but I'm not completely clueless when it comes to > isolating problems by way of deductive reasoning, and I'm stumped as to > what's causing these. I have no idea either. :( I can't magically fix them, and if I don't commit any of this stuff which works on my boxes as far as I can tell, then others won't test it and we won't make progress. If a buildworld usually triggers, then try writing a small C program that beats on a file in /tmp or /var, then start up 10 copies of it in a script that you run as your 'command_that_makes_my_machine_go_boom' to see if it works. :-P > Ciao, > Sheldon. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 14:20:17 2000 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 E68ED37B4D7; Fri, 17 Nov 2000 14:20:11 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA02183; Fri, 17 Nov 2000 14:20:09 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eAHMK5h26546; Fri, 17 Nov 2000 14:20:05 -0800 (PST) (envelope-from obrien) Date: Fri, 17 Nov 2000 14:20:03 -0800 From: "David O'Brien" To: John Baldwin Cc: current@FreeBSD.org Subject: Re: RQ review: [was: Re: "make modules" kicks the first module d Message-ID: <20001117142003.A26512@dragon.nuxi.com> Reply-To: current@FreeBSD.org References: <20001117132602.A25729@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Fri, Nov 17, 2000 at 02:06:44PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 17, 2000 at 02:06:44PM -0800, John Baldwin wrote: > > I committed something simular. BTW, you made ``make depend'' a > > requirement, which we did not have agreement on. > > Erm: > > config -g LAPTOP > Don't forget to do a ``make depend'' > Kernel build directory is ../../compile/LAPTOP > > make depend is already a requirement. "Erm", that is a recommendation. It is not a requirement. The posted patch made it so you were forced to. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 15:48:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from liono.newc.com (c207-207-134-48.ip.newc.com [207.207.134.48]) by hub.freebsd.org (Postfix) with ESMTP id 4782137B479 for ; Fri, 17 Nov 2000 15:48:45 -0800 (PST) Received: from localhost (mail@localhost) by liono.newc.com (8.9.3/8.9.3) with SMTP id TAA23874 for ; Fri, 17 Nov 2000 19:52:12 -0500 Date: Fri, 17 Nov 2000 19:52:12 -0500 Message-Id: <200011180052.TAA23874@liono.newc.com> X-Authentication-Warning: liono.newc.com: mail@localhost didn't use HELO protocol From: afroconnection2@emailfactory.net To: current@freebsd.org Subject: Unsubscribed from AfroConnection2 Reply-To: afroconnection2@emailfactory.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear , You have just been removed from the following EmailFactory Mailing Lists: 1.- AfroConnection2 Thank You. Sincerely, EmailFactory.com staff. ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- This email sent by http://www.EmailFactory.com The Web-Based Precision Opt-In Email Marketing Solution. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 17:44: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2009E37B479; Fri, 17 Nov 2000 17:44:01 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id CAA12022; Sat, 18 Nov 2000 02:43:57 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: camel@avias.com Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: kern/22838: if_tap and linprocfs modules are brokern in -current References: <200011141057.eAEAvj300993@camel.avias.com> From: Dag-Erling Smorgrav Date: 18 Nov 2000 02:43:53 +0100 In-Reply-To: camel@avias.com's message of "Tue, 14 Nov 2000 13:57:45 +0300 (MSK)" Message-ID: Lines: 13 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG camel@avias.com writes: > when i try to kldload if_tap module, the kernel says "symbol lminor > undefined" and fails to load the module. for linprocfs module the > message is "symbol tsleep undefined". these modules are necessary > for VMWare 2.0 port. Your modules are out of synch with your kernel; tsleep() is now a macro wrapper for msleep(). Rebuild your modules and they'll be all right. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 18: 0:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 9BD7B37B479 for ; Fri, 17 Nov 2000 18:00:23 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eAI1wXe72483; Fri, 17 Nov 2000 17:58:34 -0800 (PST) (envelope-from kris) Date: Fri, 17 Nov 2000 17:58:30 -0800 From: Kris Kennaway To: Soren Schmidt Cc: Sheldon Hearn , Alfred Perlstein , "Steven E. Ames" , Boris Popov , Valentin Chopov , current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... Message-ID: <20001117175830.A65059@citusc17.usc.edu> References: <2967.974461715@axl.fw.uunet.co.za> <200011171155.MAA92493@freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011171155.MAA92493@freebsd.dk>; from sos@freebsd.dk on Fri, Nov 17, 2000 at 12:55:28PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 17, 2000 at 12:55:28PM +0100, Soren Schmidt wrote: > > I thought I was the only one, since my question on the freebsd-current > > mailing list went unanswered. >=20 > You are _not_ alone, there has been numerous complains about this > on the list, but so far they have not been taken seriously :| One of my non-SMP machines reliably wedges whenever I do heavy disk I/O. I can't break to debugger. Nov 4 15:46:41 mollari /boot/kernel/kernel: atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 Nov 4 15:46:41 mollari /boot/kernel/kernel: ata0: at 0x1f0 irq 14 on atapc= i0 Nov 4 15:46:41 mollari /boot/kernel/kernel: ahc0: port 0xfc00-0xfcff mem 0xffbeb000-0xffbebfff irq 15 at device 11.= 0 on pci0 Nov 4 15:46:41 mollari /boot/kernel/kernel: aic7880: Wide Channel A, SCSI = Id=3D7, 16/255 SCBs Kris --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoV4kYACgkQWry0BWjoQKXrxACfcY8ZNqm4yKRQztmHW5AKqKpQ 1XkAoLi7yWaoEvaITFgt0NRSltJFiu4t =CPMU -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 18: 9:13 2000 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 9611537B4C5 for ; Fri, 17 Nov 2000 18:09:11 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA21567 for ; Fri, 17 Nov 2000 21:09:11 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAI29Bt50968; Fri, 17 Nov 2000 21:09:11 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 17 Nov 2000 21:09:10 -0500 (EST) To: current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... In-Reply-To: <200011171826.LAA75925@harmony.village.org> References: <2967.974461715@axl.fw.uunet.co.za> <200011171826.LAA75925@harmony.village.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14869.58485.15187.975790@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > In message <2967.974461715@axl.fw.uunet.co.za> Sheldon Hearn writes: > : The problem with a hard lock-up out of which you can't escape into the > : debugger is that it makes meaningful bug reports impossible. My non-SMP > : workstation has exhibited apparently arbitrary lock-ups since the advent > : of SMPng. > > You can also short IOCHK to ground to get an NMI which kicks you into > the debugger, even in an interrupt context. I have a card I built > from an old multi-function card to do this. I think it is A1 and A2, > but I don't have my ISA bus spec handy. Or you can use an alpha; most of which have a halt button that will drop you into the SRM console. ;) Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 17 18:50:17 2000 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 7921437B4C5 for ; Fri, 17 Nov 2000 18:50:14 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA21976 for ; Fri, 17 Nov 2000 21:50:13 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAI2oDe51018; Fri, 17 Nov 2000 21:50:13 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 17 Nov 2000 21:50:13 -0500 (EST) To: current@freebsd.org Reply-To: current@freebsd.org Subject: missing interrupts (was Re: CURRENT is freezing again ...) In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14869.58648.34403.679348@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Valentin Chopov writes: > Hi, > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > 10 min after boot... > I've seen one similar problem on an alpha UP1000 that I'd like some input about. The UP1000 is essentially an alpha 21264 stuffed into an AMD Athlon system. It has an AMD-751 chipset and handles all device interrupts via an isa interrupt controller. I've noticed that under "heavy" load (gdb -k kernel.debug /dev/mem on an NFS filesystem), the network interface goes away, never to reappear. All I see is "fxp0: device timeout" on console. This started with SMPng. After a little bit of investigation with ddb, I discovered that the NIC's irq was pending. Eg: login: fxp0: device timeout Stopped at siointr1+0x17c: br zero,siointr1+0x32c db> call isa_irq_pending() 0x410 The fxp interface is at ir10, so 0x410 means there's an irq 10 pending. I then wrote a hack which sends an eoi. If I call my hack from ddb and send an eoi for irq10, everything goes back to normal and the network interface is back. So, is it a race in the interrupt code, or is it something about how the code is structured? On the alpha at least, we get the irq, mask the irq and set the ithread runnable. When the (isa) ithread runs, it calls the interrupt handler and then sends an eoi. The interrupt is then unmasked. I've peeked at the linux code and noticed that they do things differently. They first mask the interrupt, and then send the eoi immediately -- before the handler runs. They then run the handler and unmask the interrupt. The seem to do this both on i386 and alpha. Does anybody have any ideas about this? Does something bad happen if you don't send an eoi in a reasonable amount of time? 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 Fri Nov 17 23:27:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-210.dsl.snfc21.pacbell.net [63.202.177.210]) by hub.freebsd.org (Postfix) with ESMTP id 2464D37B479 for ; Fri, 17 Nov 2000 23:27:23 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAI7Y9F01088; Fri, 17 Nov 2000 23:34:13 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011180734.eAI7Y9F01088@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... In-reply-to: Your message of "Fri, 17 Nov 2000 11:34:06 MST." <200011171834.LAA76119@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Nov 2000 23:34:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : >You can also short IOCHK to ground to get an NMI which kicks you into > : >the debugger, even in an interrupt context. > : > : Bad news for you warner: On a too large sample of my newer > : motherboards this doesn't work anymore :-( > > There's also a pci signal that you can either pull up or pull down > that's supposed to give you the same results. I've never really > needed to know it. SERR behaviour is programmable and there is no standard for it. 8( -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 7:22:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mharnois.workgroup.net (c1030098-a.wtrlo1.ia.home.com [24.11.39.39]) by hub.freebsd.org (Postfix) with ESMTP id 44FA537B479; Sat, 18 Nov 2000 07:22:55 -0800 (PST) Received: (from mdharnois@localhost) by mharnois.workgroup.net (8.11.1/8.11.1) id eAIFMlN03169; Sat, 18 Nov 2000 09:22:47 -0600 (CST) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: John Baldwin Cc: Sheldon Hearn , current@FreeBSD.ORG, Valentin Chopov , Boris Popov , Soren Schmidt , "Steven E. Ames" , Alfred Perlstein Subject: Re: CURRENT is freezing again ... Keywords: debugger,pci,mutexes References: From: Michael Harnois Date: 18 Nov 2000 09:22:47 -0600 In-Reply-To: Message-ID: <86y9yhl2yg.fsf@mharnois.workgroup.net> Lines: 26 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Pan) 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, 17 Nov 2000 10:30:02 -0800 (PST), John Baldwin said: > what the WITNESS code does is perform extra checks on mutex > enter's and exit's to ensure that we aren't handling mutexes in > such a way that a deadlock is possible. Thus, it verifies that > you don't grab mutexes out of order, or that you don't grab > sleep mutexes with interrupts disabled, etc. Is this code meaningful on UP machines? Having been a victim of these seemingly random freezes since SMPng started, as others have noted, I decided to compile it in earlier this week. Twice now I've been dumped into the debugger with this output: lock order reversal 1st dc0 last acquired @ ../../pci/if_dc.c:2717 2nd 0xc0acdb3c dc1 @ ../../pci/if_dc.c: 2717 3rd 0xc0acab3c dc0 @ ../../pci/if_dc.c: 2929 Debugger ("witness_enter") Stopped at Debugger+0x39: movb $0, in.Debugger.639 -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org The atheist staring from the attic window is often nearer to God than the believer caught up in his own false image of God. -- Martin Buber To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 7:24: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mharnois.workgroup.net (c1030098-a.wtrlo1.ia.home.com [24.11.39.39]) by hub.freebsd.org (Postfix) with ESMTP id 1C7AD37B479; Sat, 18 Nov 2000 07:24:02 -0800 (PST) Received: (from mdharnois@localhost) by mharnois.workgroup.net (8.11.1/8.11.1) id eAIFMlN03169; Sat, 18 Nov 2000 09:22:47 -0600 (CST) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: John Baldwin Cc: Sheldon Hearn , current@FreeBSD.ORG, Valentin Chopov , Boris Popov , Soren Schmidt , "Steven E. Ames" , Alfred Perlstein Subject: Re: CURRENT is freezing again ... Keywords: debugger,pci,mutexes References: From: Michael Harnois Date: 18 Nov 2000 09:22:47 -0600 In-Reply-To: Message-ID: <86y9yhl2yg.fsf@mharnois.workgroup.net> Lines: 26 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Pan) 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, 17 Nov 2000 10:30:02 -0800 (PST), John Baldwin said: > what the WITNESS code does is perform extra checks on mutex > enter's and exit's to ensure that we aren't handling mutexes in > such a way that a deadlock is possible. Thus, it verifies that > you don't grab mutexes out of order, or that you don't grab > sleep mutexes with interrupts disabled, etc. Is this code meaningful on UP machines? Having been a victim of these seemingly random freezes since SMPng started, as others have noted, I decided to compile it in earlier this week. Twice now I've been dumped into the debugger with this output: lock order reversal 1st dc0 last acquired @ ../../pci/if_dc.c:2717 2nd 0xc0acdb3c dc1 @ ../../pci/if_dc.c: 2717 3rd 0xc0acab3c dc0 @ ../../pci/if_dc.c: 2929 Debugger ("witness_enter") Stopped at Debugger+0x39: movb $0, in.Debugger.639 -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org The atheist staring from the attic window is often nearer to God than the believer caught up in his own false image of God. -- Martin Buber To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 9:28: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id D13AC37B4CF for ; Sat, 18 Nov 2000 09:28:05 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAIKBO733164; Sat, 18 Nov 2000 21:11:25 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: David Malone Cc: current@freebsd.org Subject: Re: Typo in labpc.c In-Reply-To: Your message of "Sat, 18 Nov 2000 17:23:16 GMT." <200011181723.aa82033@salmon.maths.tcd.ie> Date: Sat, 18 Nov 2000 21:11:24 +0100 Message-ID: <33162.974578284@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011181723.aa82033@salmon.maths.tcd.ie>, David Malone writes: >I noticed the following while looking through the M_ZERO patches. >When you were cleaning up some dev stuff you made the following >change to labpc.c (revision 1.33): > > > labpcs = malloc(NLABPC * sizeof(struct ctlr *), M_DEVBUF, M_NOWAIT); > if (labpcs) > { > bzero(labpcs, NLABPC * sizeof(struct ctlr *)); > return 1; > } >+ cdevsw_add(&labpc_cdevsw); > return 0; > } > >This seems to only do the cdevsw_add if the malloc failed. I presume >this is the opposit of the intended sense. I'll fix it up if you also >think it looks wrong. If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says) that labpc doesn't work, the labpc driver should be killed, not fixed. Objections ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 9:40:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 2990F37B479 for ; Sat, 18 Nov 2000 09:40:52 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id eAIHeYt67854; Sat, 18 Nov 2000 11:40:34 -0600 (CST) (envelope-from jlemon) Date: Sat, 18 Nov 2000 11:40:34 -0600 (CST) From: Jonathan Lemon Message-Id: <200011181740.eAIHeYt67854@prism.flugsvamp.com> To: mdharnois@home.com, current@freebsd.org Subject: Re: CURRENT is freezing again ... X-Newsgroups: local.mail.freebsd-current In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >On Fri, 17 Nov 2000 10:30:02 -0800 (PST), John Baldwin said: > > > what the WITNESS code does is perform extra checks on mutex > > enter's and exit's to ensure that we aren't handling mutexes in > > such a way that a deadlock is possible. Thus, it verifies that > > you don't grab mutexes out of order, or that you don't grab > > sleep mutexes with interrupts disabled, etc. > >Is this code meaningful on UP machines? Having been a victim of these >seemingly random freezes since SMPng started, as others have noted, I >decided to compile it in earlier this week. Twice now I've been dumped >into the debugger with this output: > >lock order reversal >1st dc0 last acquired @ ../../pci/if_dc.c:2717 >2nd 0xc0acdb3c dc1 @ ../../pci/if_dc.c: 2717 >3rd 0xc0acab3c dc0 @ ../../pci/if_dc.c: 2929 This is on a UP machine? This looks like you're taking an interrupt on dc1 and then trying to call the dc0 start routine, which shouldn't be possible. (Unless I'm misunderstanding the witness code) What version of if_dc.c are you using? line 2929 doesn't correspond to an instance of "DC_LOCK" in my copy. -- Jonathan this should be released before anything else To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 9:45:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 638B637B479 for ; Sat, 18 Nov 2000 09:45:49 -0800 (PST) Received: from marakesh-10.budapest.interware.hu ([195.70.50.138] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13xC3b-0006go-00; Sat, 18 Nov 2000 18:45:44 +0100 Message-ID: <3A16C021.FAF9B3A9@elischer.org> Date: Sat, 18 Nov 2000 09:45:05 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: David Malone , current@freebsd.org Subject: Re: Typo in labpc.c References: <33162.974578284@critter> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <200011181723.aa82033@salmon.maths.tcd.ie>, David Malone writes: > >I noticed the following while looking through the M_ZERO patches. > >When you were cleaning up some dev stuff you made the following > >change to labpc.c (revision 1.33): > > > > > > labpcs = malloc(NLABPC * sizeof(struct ctlr *), M_DEVBUF, M_NOWAIT); > > if (labpcs) > > { > > bzero(labpcs, NLABPC * sizeof(struct ctlr *)); > > return 1; > > } > >+ cdevsw_add(&labpc_cdevsw); > > return 0; > > } > > > >This seems to only do the cdevsw_add if the malloc failed. I presume > >this is the opposit of the intended sense. I'll fix it up if you also > >think it looks wrong. > > If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says) > that labpc doesn't work, the labpc driver should be killed, not fixed. > > Objections ? What you are saying is that people who may be using this driver have not yet moved up to -current or 4.x and as such should not be allowed to? I see no harm in leaving it there.. leave that axe right where it is.... > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 9:49:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mharnois.workgroup.net (c1030098-a.wtrlo1.ia.home.com [24.11.39.39]) by hub.freebsd.org (Postfix) with ESMTP id B2FE837B479 for ; Sat, 18 Nov 2000 09:49:51 -0800 (PST) Received: (from mdharnois@localhost) by mharnois.workgroup.net (8.11.1/8.11.1) id eAIHnoG00673; Sat, 18 Nov 2000 11:49:50 -0600 (CST) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: Jonathan Lemon Cc: current@freebsd.org Subject: Re: CURRENT is freezing again ... References: <200011181740.eAIHeYt67854@prism.flugsvamp.com> From: Michael Harnois Date: 18 Nov 2000 11:49:49 -0600 In-Reply-To: <200011181740.eAIHeYt67854@prism.flugsvamp.com> Message-ID: <86g0kp6ugy.fsf@mharnois.workgroup.net> Lines: 11 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) 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, 18 Nov 2000 11:40:34 -0600 (CST), Jonathan Lemon said: > What version of if_dc.c 1.38 -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org "It's not what we don't know that hurts us, it's what we know for certain that just ain't so." -- Mark Twain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 9:51:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id B075837B479 for ; Sat, 18 Nov 2000 09:51:19 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAIKa2733307; Sat, 18 Nov 2000 21:36:02 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: David Malone , current@freebsd.org Subject: Re: Typo in labpc.c In-Reply-To: Your message of "Sat, 18 Nov 2000 09:45:05 PST." <3A16C021.FAF9B3A9@elischer.org> Date: Sat, 18 Nov 2000 21:36:02 +0100 Message-ID: <33305.974579762@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >This seems to only do the cdevsw_add if the malloc failed. I presume >> >this is the opposit of the intended sense. I'll fix it up if you also >> >think it looks wrong. >> >> If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says) >> that labpc doesn't work, the labpc driver should be killed, not fixed. >> >> Objections ? > >What you are saying is that people who may be using this driver have >not yet moved up to -current or 4.x and as such should not be allowed >to? I'm saying: "If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says) that labpc doesn't work, the labpc driver should be killed, not fixed." That's 1.5 year Julian, and if nobody *who is using it* objects it goes. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 10:27:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 06CC437B479 for ; Sat, 18 Nov 2000 10:27:29 -0800 (PST) Received: from marakesh-10.budapest.interware.hu ([195.70.50.138] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13xChu-0001YC-00; Sat, 18 Nov 2000 19:27:23 +0100 Message-ID: <3A16C9E9.D2A4D8A4@elischer.org> Date: Sat, 18 Nov 2000 10:26:49 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: David Malone , current@freebsd.org Subject: Re: Typo in labpc.c References: <33305.974579762@critter> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > >> >This seems to only do the cdevsw_add if the malloc failed. I presume > >> >this is the opposit of the intended sense. I'll fix it up if you also > >> >think it looks wrong. > >> > >> If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says) > >> that labpc doesn't work, the labpc driver should be killed, not fixed. > >> > >> Objections ? > > > >What you are saying is that people who may be using this driver have > >not yet moved up to -current or 4.x and as such should not be allowed > >to? > > I'm saying: > > "If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says) > that labpc doesn't work, the labpc driver should be killed, not fixed." > > That's 1.5 year Julian, and if nobody *who is using it* objects it goes. unless of course I bring it back... Poul, put the f*cking axe away and consider that it costs almost no time to keep it there, and we do not know who is using it in 3.x and may want to someday upgrade. It's not costing anything where it is. It's not as if it's holding back your next great leap forward or anything. If you really think no-one is using it then ask in -stable, the home-aoutmation lists etc, the newsgroups and all the places where REAL users hang out.. -current is almost by definition the WRONG place to ask. Then even if you get no answers, I'd almost say that since the cost of leaving it there is so low that the chances that someone may WANT to use it in the Future is worth keeping it there. Personally I haven't used my appendix for a while either..... > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 11:48:28 2000 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 E0C7437B479 for ; Sat, 18 Nov 2000 11:48:23 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id GAA21774 for ; Sun, 19 Nov 2000 06:48:19 +1100 Date: Sun, 19 Nov 2000 06:48:18 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: current@FreeBSD.ORG Subject: Re: missing interrupts (was Re: CURRENT is freezing again ...) In-Reply-To: <14869.58648.34403.679348@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 On Fri, 17 Nov 2000, Andrew Gallatin wrote: > [fxp isa irq pending but never occurs] > I then wrote a hack which sends an eoi. If I call my hack from ddb > and send an eoi for irq10, everything goes back to normal and the > network interface is back. > > So, is it a race in the interrupt code, or is it something about how > the code is structured? > > On the alpha at least, we get the irq, mask the irq and set the > ithread runnable. When the (isa) ithread runs, it calls the interrupt > handler and then sends an eoi. The interrupt is then unmasked. > > I've peeked at the linux code and noticed that they do things > differently. They first mask the interrupt, and then send the eoi > immediately -- before the handler runs. They then run the handler > and unmask the interrupt. The seem to do this both on i386 and > alpha. FreeBSD does the same thing on i386's as Linux, except for fast interrupts it delays the EOI until the handler returns so that the handler gets called as soon as possible. > Does anybody have any ideas about this? Does something bad > happen if you don't send an eoi in a reasonable amount of time? Delayed EOIs work normally, but lower priority interrupts (according to the ICU's priority scheme) are masked until the EIO is sent. This is bad mainly because the ICU's priority scheme is different from FreeBSD's priority scheme. Possible causes of the problem: 1) isa_handle_intr() claims to send specific EOIs (0x30 | irq) but actually sends non-specific ones (0x20 | garbage). Since interrupts may be handled in non-LIFO order, this results in EOIs being sent for the wrong interrupts. I think this just randomizes the brokenness caused by delaying sending of EOIs. I can't see how it would result in an EOI being lost -- the right number of EOIs will have been sent after all handlers have returned. 2) Insufficient locking for ICU accesses. Again, I can't see how this would affect EOIs. On i386's, some accesses are locked implicitly by sched_lock. 3) Enabling interrupts (and unlocking the ICU) before sending EOI seems to just make things more complicated. It requires the specific EOIs in (1). On alphas, interrupts aren't masked in the ICU while they are handled (the disable/enable args in the call to alpha_setup_intr() in isa_setup_intr() are NULL ...). They are masked by some combination of the CPU and ICU priorities. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 12:32:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.utep.edu (mail.cs.utep.edu [129.108.5.3]) by hub.freebsd.org (Postfix) with ESMTP id A563B37B479 for ; Sat, 18 Nov 2000 12:32:17 -0800 (PST) Received: from gecko (gecko [129.108.5.51]) by cs.utep.edu (8.10.1/8.10.1) with ESMTP id eAIKWC426448 for ; Sat, 18 Nov 2000 13:32:12 -0700 (MST) Date: Sat, 18 Nov 2000 13:32:12 -0700 (MST) From: X-Sender: janb@gecko To: freebsd-current@FreeBSD.ORG Subject: fonts won't show in Xfree86 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 reinstalled from the snap server. Now, whenever I go int Xwindows, I get wierd stuff instead of characters. It looks almost as if the fonts have been replaced with barcodes. If I go an move the window such that it is obstructed behind something and then move it back, sometimes the characters reappear correctly. I also just tried this with 4.2 BETA and I get the same problem. I did not have this problem with 4.1. I have a RAGE128 graphics card, in case this helps. Has anybody seen this type of behavior before? Thanks, JAn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 15:15:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from tplast.saratov.ru (big.ll.intercom.ru [213.242.6.46]) by hub.freebsd.org (Postfix) with ESMTP id 0ACAC37B68F for ; Sat, 18 Nov 2000 15:14:29 -0800 (PST) Received: from intercom.ru (localhost.saratov.ru [127.0.0.1]) by tplast.saratov.ru (8.9.3/8.9.3) with ESMTP id CAA01571 for ; Sun, 19 Nov 2000 02:17:56 +0300 (MSK) (envelope-from big@intercom.ru) Message-ID: <3A170E24.C86D9A2D@intercom.ru> Date: Sun, 19 Nov 2000 02:17:56 +0300 From: Serguei Skobkarev Reply-To: big@intercom.ru X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: current@FreeBSD.org Subject: subscribe Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 18:38:26 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 548A837B4E5; Sat, 18 Nov 2000 18:38:24 -0800 (PST) Date: Sat, 18 Nov 2000 18:38:24 -0800 From: "John W. De Boskey" To: Current List Subject: Highspeed serial consoles and -current Message-ID: <20001118183824.A64932@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying to increase the speed of the serial console on a -current box from 9600 to 38400. I've put the following in /etc/make.conf: BOOT_COMCONSOLE_SPEED=38400 # serial console speed Unfortunately, it doesn't work. It still runs at 9600. I remember seeing something about this (I thought) in one of the mailing lists, but I can't seem to find it. If anyone can shed some light, I'd appreciate it. I'll be happy to summarize and provide a doc update. Thanks, John ps: Just a note, I have serial console and login working on ttyd0 at 9600. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 21: 5:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 4B4F837B479; Sat, 18 Nov 2000 21:05:08 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eAJ552428239; Sat, 18 Nov 2000 22:05:07 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200011190505.eAJ552428239@aslan.scsiguy.com> To: jon@FreeBSD.org, imp@FreeBSD.org Cc: current@FreeBSD.org Subject: Cardbus fixes Date: Sat, 18 Nov 2000 22:05:01 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While working on getting the APA-1480 to work under FreeBSD's new cardbus support, I ran into several issues. 1) When mucking with mapping registers, it is best to *not* have io or memory space access enabled. This patch defers the setting of these bits until after all of the mapping registers are probed. It might be even better to defer this until a particular mapping is activated and to disable that type of access when a new register is activated. 2) The PCI spec is very explicit about how mapping registers and the expansion ROM mapping register should be probed. This patch makes cardbus_add_map() follow the spec. 3) The PCI spec allows a device to use the same address decoder for expansion ROM access as is used for memory mapped register access. This patch carefully enables and disables ROM access along with resource (de)activiation. 4) The cardbus CIS code treats the CIS_PTR as a mapping register if it is mentioned in the CIS. I don't have a spec handy to understand why the CIS_PTR is mentioned in the CIS, but allocating a memory range for it is certainly bogus. My patch ignores bar #6 to prevent the mapping. 5) The CIS code allocated duplicate resources to those already found by cardbus_add_resources(). The fix is to pass in the bar computed from the CIS instead of the particular resource ID for that bar, so bus_generic_alloc_resource succeeds in finding the old resource. It seems somewhat strange that we have to have two methods for finding and activating the mapping registers. Isn't one method sufficient? 6) cardbus_read_exrom_cis() failed to advance correctly to higer rom images. To effect the fix, the cis_ptr value must be provided to the different CIS reading methods, unaltered. 7) The CIS code seems to use the wrong bit to determine rather a particular register mapping is for I/O or memory space. From looking at the two cards I have, it seems TPL_BAR_REG_AS should be 0x10 instead of 0x08. Otherwise, all registers that should be I/O mapped gain a second mapping in memory space. 8) The cardbus bridge code leaves memory space prefetching enabled. Prefetching is only allowed if the target device indicates (through its mapping register) that prefetching is allowable. My patch simply disables prefetching and includes code to detect this capability and pass an RF flag to enable it, but nothing more. 9) The pccbb code was impoperly handling the I/O and mem range limit registers. The limit register indicates the highest valid address in the window, not the first invalid address outside the window. One last thing that is started here is an attempt to rely more heavily on PCI register definitions and eventually functions, to get things done. The cardbus code duplicates a lot of functionality that is already available in the pci code (mapping register size/type detection). One other thing that struck me while I was looking at this was that the resource manager should be providing the "resource pooling" that pccbb_cardbus_auto_open() emulates. Although the cardbus bridges we support only provide 4K granularity for memory mapped windows, things like external rom access often can be mapped on 2K boundaries. This could allow the resource manager to allocate a range that doesn't appear to overlap with another allocation but does due to the bridges constraints. I might look into adding the concept of hierarchical resource pools to the resource manager so that, for example, the cardbus bridges pool will always grow in 4K increments from its parent resource pool. The parent would then grow according to its own requirements, etc. -- Justin Index: dev/cardbus/cardbus.c =================================================================== RCS file: /usr/cvs/src/sys/dev/cardbus/cardbus.c,v retrieving revision 1.2 diff -c -r1.2 cardbus.c *** dev/cardbus/cardbus.c 2000/10/18 03:21:48 1.2 --- dev/cardbus/cardbus.c 2000/11/19 01:41:58 *************** *** 114,121 **** int rid, u_long start, u_long count); static int cardbus_get_resource_method(device_t dev, device_t child, int type, int rid, u_long *startp, u_long *countp); ! static void cardbus_add_map(device_t bdev, device_t dev, ! pcicfgregs *cfg, int reg); static void cardbus_add_resources(device_t dev, pcicfgregs* cfg); static void cardbus_release_all_resources(device_t dev, struct resource_list *rl); --- 114,121 ---- int rid, u_long start, u_long count); static int cardbus_get_resource_method(device_t dev, device_t child, int type, int rid, u_long *startp, u_long *countp); ! static int cardbus_add_map(device_t bdev, device_t dev, ! pcicfgregs *cfg, int reg); static void cardbus_add_resources(device_t dev, pcicfgregs* cfg); static void cardbus_release_all_resources(device_t dev, struct resource_list *rl); *************** *** 162,172 **** static void device_setup_regs(device_t bdev, int b, int s, int f, pcicfgregs *cfg) { - PCIB_WRITE_CONFIG(bdev, b, s, f, PCIR_COMMAND, - PCIB_READ_CONFIG(bdev, b, s, f, PCIR_COMMAND, 2) | - PCIM_CMD_MEMEN|PCIM_CMD_PORTEN|PCIM_CMD_BUSMASTEREN, - 2); - PCIB_WRITE_CONFIG(bdev, b, s, f, PCIR_INTLINE, pci_get_irq(device_get_parent(bdev)), 1); cfg->intline = PCIB_READ_CONFIG(bdev, b, s, f, PCIR_INTLINE, 1); --- 162,167 ---- *************** *** 537,543 **** struct cardbus_devinfo *dinfo = device_get_ivars(child); struct resource_list *rl = &dinfo->resources; resource_list_add(rl, type, rid, start, start + count - 1, count); - if (rid == CARDBUS_ROM_REG) start |= 1; if (device_get_parent(child) == dev) pci_write_config(child, rid, start, 4); return 0; --- 532,537 ---- *************** *** 607,630 **** BUS_DELETE_RESOURCE(device_get_parent(dev), child, type, rid); } ! static void cardbus_add_map(device_t cbdev, device_t dev, pcicfgregs *cfg, int reg) { struct cardbus_devinfo *dinfo = device_get_ivars(dev); struct resource_list *rl = &dinfo->resources; struct resource_list_entry *rle; device_t bdev = device_get_parent(cbdev); ! u_int32_t size; ! u_int32_t testval; int type; ! struct resource *res; PCIB_WRITE_CONFIG(bdev, cfg->bus, cfg->slot, cfg->func, ! reg, 0xfffffff0, 4); testval = PCIB_READ_CONFIG(bdev, cfg->bus, cfg->slot, cfg->func, reg, 4); ! if (testval == 0xfffffff0 || testval == 0) return; if ((testval&1) == 0) type = SYS_RES_MEMORY; --- 601,630 ---- BUS_DELETE_RESOURCE(device_get_parent(dev), child, type, rid); } ! static int cardbus_add_map(device_t cbdev, device_t dev, pcicfgregs *cfg, int reg) { struct cardbus_devinfo *dinfo = device_get_ivars(dev); struct resource_list *rl = &dinfo->resources; struct resource_list_entry *rle; + struct resource *res; device_t bdev = device_get_parent(cbdev); ! uint32_t size; ! uint32_t testval; int type; ! int prefetch; + if (reg == PCIR_ROM) + testval = PCIM_ROM_ADDR; + else + testval = ~0; PCIB_WRITE_CONFIG(bdev, cfg->bus, cfg->slot, cfg->func, ! reg, testval, 4); testval = PCIB_READ_CONFIG(bdev, cfg->bus, cfg->slot, cfg->func, reg, 4); ! if (testval == ~0 || testval == 0) ! return (0); if ((testval&1) == 0) type = SYS_RES_MEMORY; *************** *** 632,638 **** --- 632,640 ---- type = SYS_RES_IOPORT; size = CARDBUS_MAPREG_MEM_SIZE(testval); + prefetch = CARDBUS_MAPREG_MEM_PREFETCH(testval); res = bus_generic_alloc_resource(cbdev, dev, type, ®, 0, ~0, size, + (prefetch ? RF_PREFETCH : 0) | rman_make_alignment_flags(size)); if (res) { u_int32_t start = rman_get_start(res); *************** *** 642,672 **** rle->res = res; } else { device_printf(dev, "Unable to add map %02x\n", reg); } } static void cardbus_add_resources(device_t dev, pcicfgregs* cfg) { device_t cbdev = device_get_parent(dev); struct cardbus_devinfo *dinfo = device_get_ivars(dev); struct resource_list *rl = &dinfo->resources; struct cardbus_quirk *q; struct resource_list_entry *rle; struct resource *res; int i; for (i = 0; i < cfg->nummaps; i++) { ! cardbus_add_map(cbdev, dev, cfg, PCIR_MAPS + i*4); } ! cardbus_add_map(cbdev, dev, cfg, CARDBUS_ROM_REG); for (q = &cardbus_quirks[0]; q->devid; q++) { if (q->devid == ((cfg->device << 16) | cfg->vendor) ! && q->type == CARDBUS_QUIRK_MAP_REG) ! cardbus_add_map(cbdev, dev, cfg, q->arg1); } res = bus_generic_alloc_resource(cbdev, dev, SYS_RES_IRQ, 0, 0, ~0, 1, RF_SHAREABLE); --- 644,695 ---- rle->res = res; } else { device_printf(dev, "Unable to add map %02x\n", reg); + type = 0; } + return (type); } static void cardbus_add_resources(device_t dev, pcicfgregs* cfg) { device_t cbdev = device_get_parent(dev); + device_t bdev = device_get_parent(cbdev); struct cardbus_devinfo *dinfo = device_get_ivars(dev); struct resource_list *rl = &dinfo->resources; struct cardbus_quirk *q; struct resource_list_entry *rle; struct resource *res; + u_int command; + int type; + int types; int i; + types = 0; for (i = 0; i < cfg->nummaps; i++) { ! type = cardbus_add_map(cbdev, dev, cfg, PCIR_MAPS + i*4); ! types |= 0x1 << type; } ! type = cardbus_add_map(cbdev, dev, cfg, PCIR_ROM); ! types |= 0x1 << type; for (q = &cardbus_quirks[0]; q->devid; q++) { if (q->devid == ((cfg->device << 16) | cfg->vendor) ! && q->type == CARDBUS_QUIRK_MAP_REG) { ! type = cardbus_add_map(cbdev, dev, cfg, q->arg1); ! types |= 0x1 << type; ! } } + command = PCIB_READ_CONFIG(bdev, cfg->bus, cfg->slot, + cfg->func, PCIR_COMMAND, 2); + if ((types & (0x1 << SYS_RES_MEMORY)) != 0) + command |= PCIM_CMD_MEMEN; + if ((types & (0x1 << SYS_RES_IOPORT)) != 0) + command |= PCIM_CMD_PORTEN; + command |= PCIM_CMD_BUSMASTEREN; + PCIB_WRITE_CONFIG(bdev, cfg->bus, cfg->slot, cfg->func, + PCIR_COMMAND, command, 2); + res = bus_generic_alloc_resource(cbdev, dev, SYS_RES_IRQ, 0, 0, ~0, 1, RF_SHAREABLE); *************** *** 693,702 **** } } ! static struct ! resource* cardbus_alloc_resource(device_t self, device_t child, int type, ! int* rid, u_long start, u_long end, ! u_long count, u_int flags) { struct cardbus_devinfo *dinfo = device_get_ivars(child); struct resource_list *rl = &dinfo->resources; --- 716,725 ---- } } ! static struct resource* ! cardbus_alloc_resource(device_t self, device_t child, int type, ! int* rid, u_long start, u_long end, ! u_long count, u_int flags) { struct cardbus_devinfo *dinfo = device_get_ivars(child); struct resource_list *rl = &dinfo->resources; *************** *** 706,716 **** if (device_get_parent(child) == self || child == self) rle = resource_list_find(rl, type, *rid); if (rle) { ! if (flags & RF_ACTIVE) if (bus_activate_resource(child, type, *rid, rle->res)) { return NULL; } return rle->res; /* XXX: check if range within start/end */ } else { res = bus_generic_alloc_resource(self, child, type, rid, --- 729,747 ---- if (device_get_parent(child) == self || child == self) rle = resource_list_find(rl, type, *rid); if (rle) { ! if (flags & RF_ACTIVE) { if (bus_activate_resource(child, type, *rid, rle->res)) { return NULL; } + if (*rid == PCIR_ROM) { + uint32_t rom_reg; + + rom_reg = pci_read_config(child, *rid, 4); + rom_reg |= PCIM_ROM_ENABLE; + pci_write_config(child, *rid, rom_reg, 4); + } + } return rle->res; /* XXX: check if range within start/end */ } else { res = bus_generic_alloc_resource(self, child, type, rid, *************** *** 734,739 **** --- 765,783 ---- cardbus_release_resource(device_t dev, device_t child, int type, int rid, struct resource *r) { + /* + * According to the PCI 2.2 spec, devices may share an address + * decoder between memory mapped ROM access and memory + * mapped register access. To be safe, disable ROM access + * whenever it is released. + */ + if (rid == PCIR_ROM) { + uint32_t rom_reg; + + rom_reg = pci_read_config(child, rid, 4); + rom_reg &= ~PCIM_ROM_ENABLE; + pci_write_config(child, rid, rom_reg, 4); + } return bus_deactivate_resource(child, type, rid, r); } Index: dev/cardbus/cardbus_cis.c =================================================================== RCS file: /usr/cvs/src/sys/dev/cardbus/cardbus_cis.c,v retrieving revision 1.1 diff -c -r1.1 cardbus_cis.c *** dev/cardbus/cardbus_cis.c 2000/10/18 03:21:48 1.1 --- dev/cardbus/cardbus_cis.c 2000/11/19 00:04:55 *************** *** 44,49 **** --- 44,50 ---- #include #include + #include #include #include *************** *** 258,263 **** --- 259,266 ---- type = SYS_RES_MEMORY; } bar = (reg & TPL_BAR_REG_ASI_MASK) - 1; + if (bar == 6) + return EINVAL; if (bar < 0 || bar > 6) { device_printf(dev, "Invalid BAR number: %02x(%02x)\n", reg, bar); *************** *** 266,278 **** bar = CARDBUS_BASE0_REG + bar * 4; DEVPRINTF((dev, "Opening BAR: type=%s, bar=%02x, len=%04x\n", (type==SYS_RES_MEMORY)?"MEM":"IO", bar, len)); ! res = bus_generic_alloc_resource(child, child, type, ®, 0, ~0, len, rman_make_alignment_flags(len) | RF_ACTIVE); if (res == NULL) { device_printf(dev, "Cannot allocate BAR %02x\n", reg); } else { start = rman_get_start(res); - if (reg == CARDBUS_ROM_REG) start |= 1; pci_write_config(child, reg, start, 4); } } --- 269,280 ---- bar = CARDBUS_BASE0_REG + bar * 4; DEVPRINTF((dev, "Opening BAR: type=%s, bar=%02x, len=%04x\n", (type==SYS_RES_MEMORY)?"MEM":"IO", bar, len)); ! res = bus_generic_alloc_resource(child, child, type, &bar, 0, ~0, len, rman_make_alignment_flags(len) | RF_ACTIVE); if (res == NULL) { device_printf(dev, "Cannot allocate BAR %02x\n", reg); } else { start = rman_get_start(res); pci_write_config(child, reg, start, 4); } } *************** *** 290,297 **** return -1; } ! static int decode_tuples(device_t dev, device_t child, ! u_int8_t *tuples, int len) { int ret = 0; if (CISTPL_LINKTARGET != *tuples) { --- 292,299 ---- return -1; } ! static int ! decode_tuples(device_t dev, device_t child, u_int8_t *tuples, int len) { int ret = 0; if (CISTPL_LINKTARGET != *tuples) { *************** *** 332,338 **** #define READROM(rom, type, offset) \ (*((u_int ## type ##_t *)(((unsigned char*)rom) + offset))) - u_int32_t addr = 0; /* offset of current rom image */ int romnum = 0; unsigned char *data; u_int32_t imagesize; --- 334,339 ---- *************** *** 351,362 **** data = image + READROM(image, 16, CARDBUS_EXROM_DATA_PTR); imagesize = READROM(data, 16, CARDBUS_EXROM_DATA_IMAGE_LENGTH); ! if(imagesize == 0) /* * XXX some ROMs seem to have this as zero, * can we assume this means 1 block? */ imagesize = 1; imagesize <<= 9; if (imagenum == romnum) { --- 352,364 ---- data = image + READROM(image, 16, CARDBUS_EXROM_DATA_PTR); imagesize = READROM(data, 16, CARDBUS_EXROM_DATA_IMAGE_LENGTH); ! if (imagesize == 0) { /* * XXX some ROMs seem to have this as zero, * can we assume this means 1 block? */ imagesize = 1; + } imagesize <<= 9; if (imagenum == romnum) { *************** *** 365,371 **** return 0; } ! addr += imagesize; romnum++; } while ((READROM(data, 8, CARDBUS_EXROM_DATA_INDICATOR) & 0x80) == 0); device_printf(dev, "Cannot read CIS: Not enough images of rom\n"); --- 367,373 ---- return 0; } ! image += imagesize; romnum++; } while ((READROM(data, 8, CARDBUS_EXROM_DATA_INDICATOR) & 0x80) == 0); device_printf(dev, "Cannot read CIS: Not enough images of rom\n"); *************** *** 380,386 **** int i, j; DEVPRINTF((dev, "reading CIS data from configuration space\n")); ! for (i = cis_ptr, j = 0; i < len; i += 4) { u_int32_t e = pci_read_config(child, i, 4); tuples[j] = 0xff & e; e >>= 8; --- 382,388 ---- int i, j; DEVPRINTF((dev, "reading CIS data from configuration space\n")); ! for (i = cis_ptr & CARDBUS_CIS_ADDRMASK, j = 0; i < len; i += 4) { u_int32_t e = pci_read_config(child, i, 4); tuples[j] = 0xff & e; e >>= 8; *************** *** 402,409 **** int rid; int ret; ! if(space == CARDBUS_CIS_ASI_ROM) { ! rid = CARDBUS_ROM_REG; DEVPRINTF((dev, "reading CIS data from ROM\n")); } else { rid = CARDBUS_BASE0_REG + (space - 1) * 4; --- 404,411 ---- int rid; int ret; ! if (space == CARDBUS_CIS_ASI_ROM) { ! rid = PCIR_ROM; DEVPRINTF((dev, "reading CIS data from ROM\n")); } else { rid = CARDBUS_BASE0_REG + (space - 1) * 4; *************** *** 416,428 **** return ENOMEM; } ! if(space == CARDBUS_CIS_ASI_ROM) { int s; s = splhigh(); ret = cardbus_read_exrom_cis(dev, mem, cis_ptr, tuples, len); splx(s); } else { /* XXX byte order? */ memcpy(tuples, (unsigned char*)rman_get_virtual(mem)+cis_ptr, len); ret = 0; --- 418,431 ---- return ENOMEM; } ! if (space == CARDBUS_CIS_ASI_ROM) { int s; s = splhigh(); ret = cardbus_read_exrom_cis(dev, mem, cis_ptr, tuples, len); splx(s); } else { /* XXX byte order? */ + cis_ptr &= CARDBUS_CIS_ADDRMASK; memcpy(tuples, (unsigned char*)rman_get_virtual(mem)+cis_ptr, len); ret = 0; *************** *** 437,443 **** u_int32_t cis_ptr = pci_read_config(child, CARDBUS_CIS_REG, 4); int cardbus_space = cis_ptr & CARDBUS_CIS_ASIMASK; int ret = 0; - cis_ptr = cis_ptr & CARDBUS_CIS_ADDRMASK; switch(cardbus_space) { case CARDBUS_CIS_ASI_TUPLE: --- 440,445 ---- Index: dev/cardbus/cardbus_cis.h =================================================================== RCS file: /usr/cvs/src/sys/dev/cardbus/cardbus_cis.h,v retrieving revision 1.1 diff -c -r1.1 cardbus_cis.h *** dev/cardbus/cardbus_cis.h 2000/10/18 03:21:48 1.1 --- dev/cardbus/cardbus_cis.h 2000/11/17 18:55:01 *************** *** 79,85 **** /* BAR */ #define TPL_BAR_REG_ASI_MASK 0x07 ! #define TPL_BAR_REG_AS 0x08 /* CISTPL_FUNC */ #define TPL_FUNC_MF 0 /* multi function tuple */ --- 79,85 ---- /* BAR */ #define TPL_BAR_REG_ASI_MASK 0x07 ! #define TPL_BAR_REG_AS 0x10 /* CISTPL_FUNC */ #define TPL_FUNC_MF 0 /* multi function tuple */ Index: dev/cardbus/cardbusreg.h =================================================================== RCS file: /usr/cvs/src/sys/dev/cardbus/cardbusreg.h,v retrieving revision 1.2 diff -c -r1.2 cardbusreg.h *** dev/cardbus/cardbusreg.h 2000/10/18 03:21:48 1.2 --- dev/cardbus/cardbusreg.h 2000/11/18 03:20:17 *************** *** 55,61 **** # define CARDBUS_CIS_ASI_BAR4 0x05 # define CARDBUS_CIS_ASI_BAR5 0x06 # define CARDBUS_CIS_ASI_ROM 0x07 - #define CARDBUS_ROM_REG 0x30 /* EXROM offsets for reading CIS */ #define CARDBUS_EXROM_SIGNATURE 0x00 --- 55,60 ---- *************** *** 85,87 **** --- 84,88 ---- ((mr) & CARDBUS_MAPREG_MEM_ADDR_MASK) #define CARDBUS_MAPREG_MEM_SIZE(mr) \ (CARDBUS_MAPREG_MEM_ADDR(mr) & -CARDBUS_MAPREG_MEM_ADDR(mr)) + #define CARDBUS_MAPREG_MEM_PREFETCH(mr) \ + ((mr) & PCIM_MAP_PREFETCHABLE) Index: dev/pccbb/pccbb.c =================================================================== RCS file: /usr/cvs/src/sys/dev/pccbb/pccbb.c,v retrieving revision 1.5 diff -c -r1.5 pccbb.c *** dev/pccbb/pccbb.c 2000/10/22 04:37:57 1.5 --- dev/pccbb/pccbb.c 2000/11/19 03:42:52 *************** *** 317,323 **** /* Use PCI interrupt for interrupt routing */ PCI_MASK2_CONFIG(sc->sc_dev, PCCBBR_BRIDGECTRL, & ~(PCCBBM_BRIDGECTRL_MASTER_ABORT | ! PCCBBM_BRIDGECTRL_INTR_IREQ_EN), | PCCBBM_BRIDGECTRL_WRITE_POST_EN, 2); --- 317,325 ---- /* Use PCI interrupt for interrupt routing */ PCI_MASK2_CONFIG(sc->sc_dev, PCCBBR_BRIDGECTRL, & ~(PCCBBM_BRIDGECTRL_MASTER_ABORT | ! PCCBBM_BRIDGECTRL_INTR_IREQ_EN | ! PCCBBM_BRIDGECTRL_PREFETCH_0 | ! PCCBBM_BRIDGECTRL_PREFETCH_1), | PCCBBM_BRIDGECTRL_WRITE_POST_EN, 2); *************** *** 910,917 **** SLIST_FOREACH(rle, &sc->rl, entries) { if (rle->type != type) ! ; ! else if (starts[0] == 0xffffffff) { starts[0] = rle->start; ends[0] = rle->end; rle->win = 0; --- 912,919 ---- SLIST_FOREACH(rle, &sc->rl, entries) { if (rle->type != type) ! continue; ! if (starts[0] == 0xffffffff) { starts[0] = rle->start; ends[0] = rle->end; rle->win = 0; *************** *** 969,978 **** starts[0] -= starts[0] % align; if (starts[1] != 0xffffffff) starts[1] -= starts[1] % align; ! if (ends[0] % align != 0) ends[0] += align - ends[0]%align; ! if (ends[1] % align != 0) ends[1] += align - ends[1]%align; if (type == SYS_RES_MEMORY) { pccbb_cardbus_mem_open(sc->sc_dev, 0, starts[0], ends[0]); --- 971,984 ---- starts[0] -= starts[0] % align; if (starts[1] != 0xffffffff) starts[1] -= starts[1] % align; ! if (ends[0] % align != 0) { ends[0] += align - ends[0]%align; ! ends[0]--; ! } ! if (ends[1] % align != 0) { ends[1] += align - ends[1]%align; + ends[1]--; + } if (type == SYS_RES_MEMORY) { pccbb_cardbus_mem_open(sc->sc_dev, 0, starts[0], ends[0]); Index: pci/if_dc.c =================================================================== RCS file: /usr/cvs/src/sys/pci/if_dc.c,v retrieving revision 1.38 diff -c -r1.38 if_dc.c *** pci/if_dc.c 2000/11/14 19:35:22 1.38 --- pci/if_dc.c 2000/11/17 19:33:11 *************** *** 119,125 **** #include #include - #define DC_USEIOSPACE #ifdef __alpha__ #define SRM_MEDIA #endif --- 119,124 ---- Index: pci/if_fxp.c =================================================================== RCS file: /usr/cvs/src/sys/pci/if_fxp.c,v retrieving revision 1.99 diff -c -r1.99 if_fxp.c *** pci/if_fxp.c 2000/10/22 06:41:46 1.99 --- pci/if_fxp.c 2000/11/19 01:41:01 *************** *** 491,497 **** for (i=0; i<5; i++) sc->saved_maps[i] = pci_read_config(dev, PCIR_MAPS + i*4, 4); ! sc->saved_biosaddr = pci_read_config(dev, PCIR_BIOS, 4); sc->saved_intline = pci_read_config(dev, PCIR_INTLINE, 1); sc->saved_cachelnsz = pci_read_config(dev, PCIR_CACHELNSZ, 1); sc->saved_lattimer = pci_read_config(dev, PCIR_LATTIMER, 1); --- 491,497 ---- for (i=0; i<5; i++) sc->saved_maps[i] = pci_read_config(dev, PCIR_MAPS + i*4, 4); ! sc->saved_biosaddr = pci_read_config(dev, PCIR_ROM, 4); sc->saved_intline = pci_read_config(dev, PCIR_INTLINE, 1); sc->saved_cachelnsz = pci_read_config(dev, PCIR_CACHELNSZ, 1); sc->saved_lattimer = pci_read_config(dev, PCIR_LATTIMER, 1); *************** *** 521,527 **** /* better way to do this? */ for (i=0; i<5; i++) pci_write_config(dev, PCIR_MAPS + i*4, sc->saved_maps[i], 4); ! pci_write_config(dev, PCIR_BIOS, sc->saved_biosaddr, 4); pci_write_config(dev, PCIR_INTLINE, sc->saved_intline, 1); pci_write_config(dev, PCIR_CACHELNSZ, sc->saved_cachelnsz, 1); pci_write_config(dev, PCIR_LATTIMER, sc->saved_lattimer, 1); --- 521,527 ---- /* better way to do this? */ for (i=0; i<5; i++) pci_write_config(dev, PCIR_MAPS + i*4, sc->saved_maps[i], 4); ! pci_write_config(dev, PCIR_ROM, sc->saved_biosaddr, 4); pci_write_config(dev, PCIR_INTLINE, sc->saved_intline, 1); pci_write_config(dev, PCIR_CACHELNSZ, sc->saved_cachelnsz, 1); pci_write_config(dev, PCIR_LATTIMER, sc->saved_lattimer, 1); Index: pci/pcireg.h =================================================================== RCS file: /usr/cvs/src/sys/pci/pcireg.h,v retrieving revision 1.27 diff -c -r1.27 pcireg.h *** pci/pcireg.h 2000/10/02 00:41:43 1.27 --- pci/pcireg.h 2000/11/18 03:19:43 *************** *** 69,79 **** /* config registers for header type 0 devices */ #define PCIR_MAPS 0x10 #define PCIR_CARDBUSCIS 0x28 #define PCIR_SUBVEND_0 0x2c #define PCIR_SUBDEV_0 0x2e ! #define PCIR_BIOS 0x30 ! #define PCIM_BIOS_ENABLE 0x01 #define PCIR_INTLINE 0x3c #define PCIR_INTPIN 0x3d #define PCIR_MINGNT 0x3e --- 69,82 ---- /* config registers for header type 0 devices */ #define PCIR_MAPS 0x10 + #define PCIM_MAP_PREFETCHABLE 0x08 #define PCIR_CARDBUSCIS 0x28 #define PCIR_SUBVEND_0 0x2c #define PCIR_SUBDEV_0 0x2e ! #define PCIR_ROM 0x30 ! #define PCIM_ROM_ENABLE 0x01 ! #define PCIM_ROM_ADDR 0xFFFFF800 ! #define PCIR_CAP_PTR 0x34 #define PCIR_INTLINE 0x3c #define PCIR_INTPIN 0x3d #define PCIR_MINGNT 0x3e Index: sys/rman.h =================================================================== RCS file: /usr/cvs/src/sys/sys/rman.h,v retrieving revision 1.12 diff -c -r1.12 rman.h *** sys/rman.h 2000/11/09 15:42:05 1.12 --- sys/rman.h 2000/11/18 03:09:52 *************** *** 42,47 **** --- 42,48 ---- #define RF_TIMESHARE 0x0008 /* resource permits time-division sharing */ #define RF_WANTED 0x0010 /* somebody is waiting for this resource */ #define RF_FIRSTSHARE 0x0020 /* first in sharing list */ + #define RF_PREFETCH 0x0040 /* resource allows prefetching */ #define RF_ALIGNMENT_SHIFT 10 /* alignment size bit starts bit 10 */ #define RF_ALIGNMENT_MASK (0x003F << RF_ALIGNMENT_SHIFT) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 21:39:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2FD3537B4C5; Sat, 18 Nov 2000 21:39:37 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAJ5daQ16743; Sat, 18 Nov 2000 22:39:36 -0700 (MST) (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 WAA87209; Sat, 18 Nov 2000 22:39:35 -0700 (MST) Message-Id: <200011190539.WAA87209@harmony.village.org> To: "Justin T. Gibbs" Subject: Re: Cardbus fixes Cc: jon@FreeBSD.org, current@FreeBSD.org In-reply-to: Your message of "Sat, 18 Nov 2000 22:05:01 MST." <200011190505.eAJ552428239@aslan.scsiguy.com> References: <200011190505.eAJ552428239@aslan.scsiguy.com> Date: Sat, 18 Nov 2000 22:39:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011190505.eAJ552428239@aslan.scsiguy.com> "Justin T. Gibbs" writes: : 1) When mucking with mapping registers, it is best to *not* have : io or memory space access enabled. This patch defers the setting : of these bits until after all of the mapping registers are probed. : It might be even better to defer this until a particular mapping : is activated and to disable that type of access when a new : register is activated. Agreed. : 2) The PCI spec is very explicit about how mapping registers and : the expansion ROM mapping register should be probed. This patch : makes cardbus_add_map() follow the spec. OK. : 3) The PCI spec allows a device to use the same address decoder for : expansion ROM access as is used for memory mapped register access. : This patch carefully enables and disables ROM access along with : resource (de)activiation. Makes sense. : 4) The cardbus CIS code treats the CIS_PTR as a mapping register if : it is mentioned in the CIS. I don't have a spec handy to understand : why the CIS_PTR is mentioned in the CIS, but allocating a memory range : for it is certainly bogus. My patch ignores bar #6 to prevent the : mapping. I'll have to look up the CIS_PTR spec. I'm not sure I like hardwiring things like this. : 5) The CIS code allocated duplicate resources to those already found : by cardbus_add_resources(). The fix is to pass in the bar computed : from the CIS instead of the particular resource ID for that bar, : so bus_generic_alloc_resource succeeds in finding the old resource. : It seems somewhat strange that we have to have two methods for : finding and activating the mapping registers. Isn't one method : sufficient? I'd think so, but I'm not sure. : 6) cardbus_read_exrom_cis() failed to advance correctly to higer rom : images. To effect the fix, the cis_ptr value must be provided to : the different CIS reading methods, unaltered. OK. : 7) The CIS code seems to use the wrong bit to determine rather a particular : register mapping is for I/O or memory space. From looking at the : two cards I have, it seems TPL_BAR_REG_AS should be 0x10 instead : of 0x08. Otherwise, all registers that should be I/O mapped gain : a second mapping in memory space. I'll have look this one up as well. : 8) The cardbus bridge code leaves memory space prefetching enabled. : Prefetching is only allowed if the target device indicates (through : its mapping register) that prefetching is allowable. My patch : simply disables prefetching and includes code to detect this capability : and pass an RF flag to enable it, but nothing more. OK. : 9) The pccbb code was impoperly handling the I/O and mem range limit : registers. The limit register indicates the highest valid address : in the window, not the first invalid address outside the window. OK. : One last thing that is started here is an attempt to rely more heavily : on PCI register definitions and eventually functions, to get things : done. The cardbus code duplicates a lot of functionality that is : already available in the pci code (mapping register size/type detection). I'd love to see that as well. There's a lot of duplicated code that I'd like to see factored. This is especially true with the 16bit code. : One other thing that struck me while I was looking at this was that : the resource manager should be providing the "resource pooling" : that pccbb_cardbus_auto_open() emulates. Although the cardbus : bridges we support only provide 4K granularity for memory mapped : windows, things like external rom access often can be mapped on : 2K boundaries. This could allow the resource manager to allocate : a range that doesn't appear to overlap with another allocation but : does due to the bridges constraints. I might look into adding the : concept of hierarchical resource pools to the resource manager so : that, for example, the cardbus bridges pool will always grow in : 4K increments from its parent resource pool. The parent would then : grow according to its own requirements, etc. That might be interesting. Now, I'm off to try these patches... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 22: 2:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from espen.oysnet.eu.org (login.oysnet.eu.org [64.32.206.153]) by hub.freebsd.org (Postfix) with ESMTP id 42F5137B4C5 for ; Sat, 18 Nov 2000 22:02:28 -0800 (PST) Received: (from root@localhost) by espen.oysnet.eu.org (8.11.1/8.11.1) id eAJ62En66757; Sun, 19 Nov 2000 01:02:14 -0500 (EST) (envelope-from root) Date: Sun, 19 Nov 2000 01:02:14 -0500 (EST) Message-Id: <200011190602.eAJ62En66757@espen.oysnet.eu.org> To: current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-URL: http://www.freebsd.org/handbook/makeworld.html X-Mailer: Lynx, Version 2.8.3rel.1 From: oys@powertech.no Subject: subscribe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 18 22:25:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 3D09937B479; Sat, 18 Nov 2000 22:25:43 -0800 (PST) Received: from 149.211.6.64.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Sat, 18 Nov 2000 22:24:12 -0800 Received: (from cjc@localhost) by 149.211.6.64.reflexcom.com (8.11.0/8.11.0) id eAJ6PI140387; Sat, 18 Nov 2000 22:25:18 -0800 (PST) (envelope-from cjc) Date: Sat, 18 Nov 2000 22:25:18 -0800 From: "Crist J . Clark" To: "John W. De Boskey" Cc: Current List Subject: Re: Highspeed serial consoles and -current Message-ID: <20001118222518.D38109@149.211.6.64.reflexcom.com> Reply-To: cjclark@alum.mit.edu References: <20001118183824.A64932@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20001118183824.A64932@FreeBSD.org>; from jwd@FreeBSD.ORG on Sat, Nov 18, 2000 at 06:38:24PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 18, 2000 at 06:38:24PM -0800, John W. De Boskey wrote: > Hi, > > I'm trying to increase the speed of the serial console > on a -current box from 9600 to 38400. I've put the following > in /etc/make.conf: > > BOOT_COMCONSOLE_SPEED=38400 # serial console speed > > > Unfortunately, it doesn't work. It still runs at 9600. > I remember seeing something about this (I thought) in one > of the mailing lists, but I can't seem to find it. You did change /etc/ttys, right? I have a serial console (null modem to a notebook PC) running at 115200 just fine, $ grep CONSOLE /etc/make.conf BOOT_COMCONSOLE_SPEED= 115200 $ grep ttyd0 /etc/ttys ttyd0 "/usr/libexec/getty std.115200" vt100 on secure And it is a CURRENT box last made mid-week. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message