From owner-freebsd-current Sun Dec 16 4:43:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from premiumshells.com (enigma.premiumshells.com [199.79.160.2]) by hub.freebsd.org (Postfix) with SMTP id 1220237B417 for ; Sun, 16 Dec 2001 04:43:28 -0800 (PST) Received: (qmail 90999 invoked from network); 16 Dec 2001 12:43:21 -0000 Received: from unknown (HELO exodus) (216.210.171.162) by mx1.premiumshells.com with SMTP; 16 Dec 2001 12:43:21 -0000 From: "Jon Christopherson" To: "'KT Sin'" , "Jon T. Christopherson" Cc: Subject: RE: current doesnt see ps2 port with acpi enabled on intel vc820 Date: Sun, 16 Dec 2001 04:43:20 -0800 Message-ID: <6529DF071451F545B92CD5CBCF6171021E88@nexus.jons.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_003E_01C185EC.306A6660" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <20011216032404.GA3951@nutty.Singapore.Sun.COM> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_003E_01C185EC.306A6660 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello, That patch worked like a charm! Ps2 port seen fine both in acpi mode and non-acpi mode. Thanks a lot. Perhaps this should be imported to the driver in the source tree? Attached is the new dmesg output. Regards, Jon Christopherson -----Original Message----- From: KT Sin [mailto:ktsin@acm.org] Sent: Saturday, December 15, 2001 7:24 PM To: Jon T. Christopherson Cc: freebsd-current@FreeBSD.ORG Subject: Re: current doesnt see ps2 port with acpi enabled on intel vc820 Hi I'm seeing the same problem on my MSI bookpc. For some reasons, the psm device will fail to get an IRQ when ACPI is enabled. Can you try the attached patch and see if it helps? kt On Sat, Dec 15, 2001 at 09:16:07AM -0800, Jon Christopherson wrote: > Hello, > > I have just compiled and installed -current from this morning > 7AMPST, and have noticed that when acpi is enabled in loader.conf the OS > does not see the ps2 mouse port. When I turn off ACPI the mouse port > shows up fine. Other than not seeing the ps2 port when in ACPI enabled > mode, the OS works without a hitch on my motherboard. Any ideas? IF this > is a known problem please let me know, as I have been off this list for > a month or so. > > On another note .. when doing a make distribution in > /usr/src/etc, the process will fail when trying to install MAKEDEV and > MAKEDEV.local into /dev both in single user and multiuser. I got around > this by telling it to not install them. > > I have attached dmesg output from both ACPI and non ACPI enabled > boots. > > Thanks in advance, > > Jon Christopherson > > Copyright (c) 1992-2001 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 #1: Sat Dec 15 08:04:04 PST 2001 > jon@genesis.jons.org:/usr/obj/usr/src/sys/GENESIS > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0438000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04380a8. > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 598476354 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (598.48-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > Features=0x383f9ff > real memory = 133955584 (130816K bytes) > avail memory = 125849600 (122900K bytes) > pnpbios: Bad PnP BIOS data checksum > Pentium Pro MTRR support enabled > VESA: v3.0, 16320k memory, flags:0x1, mode table:0xc03788a2 (1000022) > VESA: NVidia > Using $PIR table, 11 entries at 0xc00f2f60 > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI" frequency 3579545 Hz > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > acpi_cpu0: on acpi0 > acpi_button0: on acpi0 > acpi_pcib0: port 0xcf8-0xcff on acpi0 > pci0: on acpi_pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at device 0.0 (no driver attached) > pcib2: at device 30.0 on pci0 > pci2: on pcib2 > pcm0: port 0xdf00-0xdf3f irq 11 at device 7.0 on pci2 > fxp0: port 0xdf80-0xdf9f mem 0xfe900000-0xfe9fffff,0xf43ff000-0xf43fffff irq 10 at device 9.0 on pci2 > fxp0: Ethernet address 00:a0:c9:69:49:b4 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ahc0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeafffff irq 9 at device 10.0 on pci2 > aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs > pci2: at device 12.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > uhci0: port 0xef80-0xef9f irq 11 at device 31.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: at device 31.3 (no driver attached) > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 on acpi0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0 port 0x3f8-0x3ff irq 4 on acpi0 > sio0: type 16550A > sio1 port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > ppc0 port 0x378-0x37f irq 7 on acpi0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ata-: ata0 already exists, skipping it > ata-: ata1 already exists, skipping it > atkbdc-: atkbdc0 already exists, skipping it > fdc-: fdc0 already exists, skipping it > ppc-: ppc0 already exists, skipping it > sio-: sio0 already exists, skipping it > sio-: sio1 already exists, skipping it > sc-: sc0 already exists, skipping it > vga-: vga0 already exists, skipping it > pmtimer0 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ad0: 39082MB [79406/16/63] at ata0-master UDMA66 > acd0: CDROM at ata1-master PIO4 > Waiting 5 seconds for SCSI devices to settle > Mounting root from ufs:/dev/ad0s1a > Copyright (c) 1992-2001 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 #1: Sat Dec 15 08:04:04 PST 2001 > jon@genesis.jons.org:/usr/obj/usr/src/sys/GENESIS > Preloaded elf kernel "/boot/kernel/kernel" at 0xc03f4000. > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 598476017 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (598.48-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > Features=0x383f9ff > real memory = 133955584 (130816K bytes) > avail memory = 126128128 (123172K bytes) > pnpbios: Bad PnP BIOS data checksum > Pentium Pro MTRR support enabled > VESA: v3.0, 16320k memory, flags:0x1, mode table:0xc03788a2 (1000022) > VESA: NVidia > Using $PIR table, 11 entries at 0xc00f2f60 > npx0: on motherboard > npx0: INT 16 interface > pcib0: at pcibus 0 on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at device 0.0 (no driver attached) > pcib2: at device 30.0 on pci0 > pci2: on pcib2 > pcm0: port 0xdf00-0xdf3f irq 11 at device 7.0 on pci2 > pcm0: ac97 codec invalid or not present (id == 0) > device_probe_and_attach: pcm0 attach returned 6 > fxp0: port 0xdf80-0xdf9f mem 0xfe900000-0xfe9fffff,0xf43ff000-0xf43fffff irq 10 at device 9.0 on pci2 > fxp0: Ethernet address 00:a0:c9:69:49:b4 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ahc0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeafffff irq 9 at device 10.0 on pci2 > aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs > pci2: at device 12.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > uhci0: port 0xef80-0xef9f irq 11 at device 31.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: at device 31.3 (no driver attached) > ata-: ata0 already exists, skipping it > ata-: ata1 already exists, skipping it > sc-: sc0 already exists, skipping it > vga-: vga0 already exists, skipping it > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > 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 > pmtimer0 on isa0 > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ad0: 39082MB [79406/16/63] at ata0-master UDMA66 > acd0: CDROM at ata1-master PIO4 > Waiting 5 seconds for SCSI devices to settle > Mounting root from ufs:/dev/ad0s1a ------=_NextPart_000_003E_01C185EC.306A6660 Content-Type: text/plain; name="dmesg.acpi.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.acpi.txt" Copyright (c) 1992-2001 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 Dec 16 04:23:49 PST 2001 jon@genesis.jons.org:/usr/obj/usr/src/sys/GENESIS Preloaded elf kernel "/boot/kernel/kernel" at 0xc043b000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc043b0a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 598477126 Hz CPU: Pentium III/Pentium III Xeon/Celeron (598.48-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x673 Stepping =3D 3 = Features=3D0x383f9ff real memory =3D 133955584 (130816K bytes) avail memory =3D 125837312 (122888K bytes) pnpbios: Bad PnP BIOS data checksum Pentium Pro MTRR support enabled VESA: v3.0, 16320k memory, flags:0x1, mode table:0xc037bd22 (1000022) VESA: NVidia Using $PIR table, 11 entries at 0xc00f2f60 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 acpi_pcib0: port 0xcf8-0xcff on acpi0 pci0: on acpi_pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 pcm0: port 0xdf00-0xdf3f irq 11 at device 7.0 on = pci2 fxp0: port 0xdf80-0xdf9f mem = 0xfe900000-0xfe9fffff,0xf43ff000-0xf43fffff irq 10 at device 9.0 on pci2 fxp0: Ethernet address 00:a0:c9:69:49:b4 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: port 0xd800-0xd8ff mem = 0xfeaff000-0xfeafffff irq 9 at device 10.0 on pci2 aic7880: Ultra Wide Channel A, SCSI Id=3D7, 16/255 SCBs pci2: at device 12.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 = on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xef80-0xef9f irq 11 at = device 31.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: at device 31.3 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq resource info is missing; assuming irq 12 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: port = 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ata-: ata0 already exists, skipping it ata-: ata1 already exists, skipping it atkbdc-: atkbdc0 already exists, skipping it fdc-: fdc0 already exists, skipping it ppc-: ppc0 already exists, skipping it sio-: sio0 already exists, skipping it sio-: sio1 already exists, skipping it sc-: sc0 already exists, skipping it vga-: vga0 already exists, skipping it pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 ad0: 39082MB [79406/16/63] at ata0-master UDMA66 acd0: CDROM at ata1-master PIO4 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s1a ------=_NextPart_000_003E_01C185EC.306A6660-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 16 7:29:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from tank.siteone.net (pop.siteone.net [209.246.218.77]) by hub.freebsd.org (Postfix) with SMTP id 85E8C37B405 for ; Sun, 16 Dec 2001 07:29:06 -0800 (PST) Received: (qmail 90293 invoked by uid 0); 16 Dec 2001 15:35:01 -0000 Received: from cc1833539-a.vron1.nj.home.com (HELO brianhome) (24.253.240.158) by smtp.siteone.net with SMTP; 16 Dec 2001 15:35:01 -0000 Message-ID: <008e01c18645$f2a1f410$6400000a@brianhome> From: "Brian K. White" To: "KT Sin" , "Jon Christopherson" Cc: References: <6529DF071451F545B92CD5CBCF61710284E3@nexus.jons.org> <20011216032404.GA3951@nutty.Singapore.Sun.COM> Subject: Re: current doesnt see ps2 port with acpi enabled on intel vc820 Date: Sun, 16 Dec 2001 10:25:52 -0500 Organization: Aljex Software 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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "KT Sin" To: "Jon Christopherson" Cc: Sent: Saturday, December 15, 2001 10:24 PM Subject: Re: current doesnt see ps2 port with acpi enabled on intel vc820 > > I have just compiled and installed -current from this morning > > 7AMPST, and have noticed that when acpi is enabled in loader.conf the OS > > does not see the ps2 mouse port. When I turn off ACPI the mouse port > > shows up fine. Other than not seeing the ps2 port when in ACPI enabled > > mode, the OS works without a hitch on my motherboard. Any ideas? IF this > > is a known problem please let me know, as I have been off this list for > > a month or so. > I'm seeing the same problem on my MSI bookpc. For some reasons, the psm > device will fail to get an IRQ when ACPI is enabled. > > Can you try the attached patch and see if it helps? Hey I had the same problem but I assumed it was because I was slightly overclocking an amd k6-2 500 to 550 on a cheap old e-machine via-based motherboard. I applied your patch and now my mouse works. thanks! although, partially in response to the mouse problem, I never use my kvm switch anymore anyways, just vnc on the rare occasion I feel like playing with x on this box. Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/ +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 16 10:24:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id D131337B41A for ; Sun, 16 Dec 2001 10:24:39 -0800 (PST) Received: (qmail 15649 invoked by uid 0); 16 Dec 2001 18:24:37 -0000 Received: from p50870b29.dip.t-dialin.net (HELO mephisto.cthulhu.net) (80.135.11.41) by mail.gmx.net (mp012-rz3) with SMTP; 16 Dec 2001 18:24:37 -0000 Received: (from widersacher@localhost) by mephisto.cthulhu.net (8.11.6/8.11.6) id fBGII5F00338 for freebsd-current@freebsd.org; Sun, 16 Dec 2001 19:18:05 +0100 (CET) (envelope-from widersacher) Date: Sun, 16 Dec 2001 19:18:04 +0100 From: Christopher Sharp To: freebsd-current@freebsd.org Subject: pcm: lock order reversal Message-ID: <20011216181804.GA285@home.pablotron.org> Mail-Followup-To: Christopher Sharp , freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline User-Agent: Mutt/1.3.24i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello everybody, I'm getting a lock order reversal from pcm over last days, which look like this: Dec 15 16:47:54 mephisto kernel: lock order reversal Dec 15 16:47:54 mephisto kernel: 1st 0xc390e640 pcm0 @ ../../../dev/sound/pcm/sound.c:132 Dec 15 16:47:54 mephisto kernel: 2nd 0xc390e500 pcm0:play:0 @ ../../../dev/sound/pcm/sound.c:189 I don't know if this is important, but I also get complete freezes of my box somtimes and I don't know if there is a connection between this two things Here are some additional information: # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: at io 0xdf80 irq 9 (4p/2r/0v channels duplex default) # uname -a FreeBSD mephisto.cthulhu.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Dec 13 17:48:44 CET 2001 *cut* my dmesg ouput is attached. if this is irrelevant please ignore this mail and sorry for my bad english, it isn't my native language ... Christopher Sharp -- FreeBSD the Power for Everything ! Christopher Sharp --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.output" Copyright (c) 1992-2001 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 Dec 13 17:48:44 CET 2001 widersacher@mephisto.cthulhu.net:/usr/src/sys/i386/compile/KERNEL Preloaded elf kernel "/boot/kernel/kernel" at 0xc054b000. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 350798022 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 268435456 (262144K bytes) avail memory = 255389696 (249404K bytes) K6-family MTRR support enabled (2 registers) Using $PIR table, 7 entries at 0xc00f7c00 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci0: at device 3.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 ahc0: port 0xdc00-0xdcff mem 0xdffff000-0xdfffffff irq 10 at device 14.0 on pci0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs atapci0: port 0xffa0-0xffaf irq 0 at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pcm0: port 0xdf80-0xdf9f irq 9 at device 16.0 on pci0 ed0: port 0xdf40-0xdf5f irq 5 at device 18.0 on pci0 ed0: address 00:50:ba:bc:f0:77, type NE2000 (16 bit) ata-: ata0 already exists, skipping it ata-: ata1 already exists, skipping it ed-: ed0 already exists, skipping it sc-: sc0 already exists, skipping it vga-: vga0 already exists, skipping it orm0:
=1B$BFMA3$N%a!<%k$r:9$7>e$2$?$3$H!"$4MF=1B$BM-1= W$J>&IJ$r$40FFb$7$^$9%a!<%k%^%,%8%s$rH/4)CW$7$F$*$j$^$9!#=1B(B
=1B$B>&= IJ>pJs$K6=3DL#$r$*;}$A$G$7$?$i!"@'Hs9XFI!JL5NA!K$r$*4j$$CW$7$^$9!#=1B(B=1B$BITI,MW$G$7$?$i!"$*=1B$B>!
 
=1B$B9XFIEPO?!!!!!!=1B(Bhttp://www.ec-inter.com/mk/u= ef.html
 
=1B$B%^%,%8%sG[?.$O!"=3D5#12s$G$9!#!!NW;~$KH/4)$9$k>l9g$b$"$j$^$9!#=1B= (B
=1B$B>&IJ%8%c%s%k$O!"7r9/!&H~MF$,Cf?4$G$9$,!"B>$N%8%c%s%k$N>&IJ$b>R= 2p=1B(B
=1B$B$7$F$$$^$9!#=1B(B
 
=1B$B0J2<$O!"%a!<%k%^%,%8%s$N:G?7HG$G$9!#=1B(B
 

=1B$B!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!!>&IJ>R2p!!!a!a!a!a!a!a!a!a!= a!a!a!a!a!a!a=1B(B
 

=1B$B!Z7r9/![!!7r9/$rB%?J$9$k%U%!%C%7%g%s<'5$%0%C%:!!#M#O#M#A=1B= (B
 
=1B$B!!!!8*$3$j2r>C!!!&!!9xDK2r>C!!!&!!7l9TB%?J!!!&!!BND40];}=1B(B=1B$B!!!!!|%V%l%9%l%C%H!!!|%M%C%/%l%9!!!|%Y%k%H!!!|%$%s%=3D!<%k=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.com/moma/<= /DIV>
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z%@%$%(%C%H![!!%5%W%j%a%s%H=1B(B =1B$B#B#O#W#S=1B(B
 
=1B$B!!!!!X?)$Y$F$b?)$Y$F$bB@$i$J$$!Y!&!&!&13$G$7$g$&!)=1B(B
=1B$= B!!!!!X$$$$$(!"K\Ev$G$9!*!Y!&!&!&?);v$N8e!"OCBj$N=1B(B((=1B$B#B#O#W#S=1B(= B))=1B$B$r#1B^0{$`$@=1B(B
=1B$B!!!!$1!#"*"*"*!!!cHnK~!d$NMWAG$H$J$k@.J= ,$N#8#0!s$rD6HyN3;R$K$7$F%i%C%T%s=1B(B
=1B$B!!!!%0$7$FBN30$KGS=3DP$7$F= $7$^$&!"@$3&=3Di$N=1B(B((=1B$B%+%m%j!=1B$= B!!!!%H!?#B#O#W#S=1B(B))=1B$B$,F|K\Cf$GBg%R%C%HCf!*!&!&!&AG:`$,E7A3@.J,$@= $+$i0B?4!*=1B(B
=1B$B!!!!!!!z!z!!G/KvG/;O$OIJGv>uBV$K$J$j$^$9$N$G!"$4C= mJ8$O$*Aa$a$K!!!z!z=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/cap-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z%@%$%(%C%H![!!%O%j%&%C%I!&%;%l%V%l%$%H!&%@%$%(%C%H=1B(B
=
 
=1B$B!!!!!V=3D5Kv$N=1B(B2=1B$BF|4V$G=1B(B3=1B$B!A=1B(B5=1B$B%-%mAi$;= $k!*!W$H%O%j%&%C%I$GOCBj$N!"=1B(B100=1B$B!s%J%A%e%i=1B(B
=1B$B!!!!%k!&= %@%$%(%C%H!&%8%e!<%9L#$b$$$$!*E7A3@.J,!*BNFb>t2=3D$7!"$=3D$7$F8:NL!*=1B(B=
=1B$B!!!!$3$N#2F|4V$NFCJL%8%e!<%9%@%$%(%C%H$,Hh$l$?FbB!$dBN$NFGAG$rGS= =3DP$7$J$,=1B(B
=1B$B!!!!$i=1B(B(=1B$BBNFb>t2=3D=1B(B)=1B$B%(%M%k%.!<$= r9b$a!";iKCG3>FB%?J$r%5%]!<%H$7$^$9!#=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/can-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z@83h![!!6L
 
=1B$B!!!!6L=1B$B!!!!%5%s%W%kL5NAAwIU
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/cam-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z7r9/![!!9ZAG=3DhM}%"%,%j%/%96];eBN=1B(B-Z
 
=1B$B!!!!9ZAG=3DhM}%"%,%j%/%96];eBN!]#Z!?#A#B#P#C=1B(B(Agaricus = Blazei=20 acticalCompound/
=1B$B!!!!=1B(BABPC)=1B$B$OFH<+$NFC5v=3DP4j@=3DB$5;=3D= Q$K$h$j!"%"%,%j%/%9$N6];eBNItJ,$+$iM-8z@.J,=1B(B
=1B$B!!!!$r9bG;EY$GCj= =3DP$9$k$3$H$K@.8y$$$?$7$^$7$?!#99$K9ZAG=3DhM}$9$k$3$H$K$h$j?MBN=1B(B
= =1B$B!!!!$K5[<}2DG=3D$J?eMO@-$N&B=1B(B-=1B$B%0%k%+%sNL$,=3D>Mh$N%"%,%j%/%= 9>&IJ$KHf$YHtLvE*$KA}=1B(B
=1B$B!!!!2C$$$?$7$^$7$?!#=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/cac-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z?)IJ![!!L>8E20%3!<%A%sCO7\$b$bFy=1B(B500g=1B$BF~=1B(B
 
=1B$B!!!!D94|;t0i$G5f6K$NL#!*!!L>8E20%3!<%A%sCO7\Fy9q;:=3Dc7O=1B$B!!!!$K$F!V0BA4!'0B?4!W@N$J$D$+$7$$CO7\K\Mh$N= L#$G$9!#=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/cae-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z7r9/![!!%-%c%Y%DH/9Z%(%-%9!&%^%$%?%1#D!]%U%i%/%7%g%s4^M-!*CmL= \$NJ#9g7r9/?)IJ!&=1B(B
=1B$B!!!!!!!!!!%(%N%C%/#D!*=1B(B
 
=1B$B!!!!%(%N%C%/#D$O:#!":G$bCmL\$5$l$F$$$kJ#9g7r9/?)IJ$G$9!#=1B(B=1B$B!!!!%^%$%?%1#D!]%U%i%/%7%g%s!"%-%c%Y%DH/9Z%(%-%9!"%"%,%m%*%j%4E|!"= %S%?%_%s#C=1B(B
=1B$B!!!!$J$I!"M-8z@.J,$r%P%i%s%9$h$/G[9g$7$??)IJ$G$9!= #=1B$B!!!!3h@-;@AG$r=1B$B!!!!$IB?5!G=3D= $rM-$7$F$^$9!#=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/cab-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z2[;R![!!E7MwIJ$N>oN&IwEZ5-=1B(B
 
=1B$B!!!!$D$/$PK|Gn0JMhFsEY$KEO$jE7Mw$NIJ$H$7$FA*$P$l$?0q>kLC2[$N>oN= &IwEZ5-!#KL3$=1B(B
=1B$B!!!!F;;:$N6K>eBgG<8@$K=3D@$i$+$J$*L_$rF~$l$?@8= 2[;R%?%$%W$N$_$:$_$:$7$$OB2[;R$G=1B(B
=1B$B!!!!$9!#=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/cah-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z7r9/![!!#A#S#C#A%W%m%]%j%9=1B(B
 
=1B$B!!!!OCBj$N7r9/Jd=3Du?)IJ%W%m%]%j%9$O%V%i%8%k;:$r$*A&$a$7$^$9!#9= bG;EY#4#8!s$GE7=1B(B
=1B$B!!!!A3@.J,#1#0#0!s$N=1B(BASCA=1B$BM"F~$7$FBgJQ$*Gc$$F@$J2A3J$G$40FFb=1B(B
=1B$B!!!!$$$?$7$^$9!#=1B= (B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/cad-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!ZH~MF![!!%+%W%;%kH~MF1U%^%O%m#P#E!]-6=1B(B
 
=1B$B!!!!%^%O%m#P#E!]-6$O:G?7$NH~MFM}O@$K$h$C$FA*$P$l$?#7=1B$B!!!!%;%s%9$NAj>h8z2L$K$h$j=3Dw@-$,5a$a$kA4$F$N= H~MF8z2L$KBP1~$9$k%9!<%Q!<%(%C%;=1B(B
=1B$B!!!!%s%9$G$9!#FC$KCf9bG/=3D= w@-:GBg$NG:$_!HCP$_8=3D>]!I$r2r7h$9$k@Z$j;%$H$7$FCmL\=1B(B
=1B$B!!!!$5= $l$F$$$^$9!#%+%W%;%kF~$j$G$9$+$i9g@.J]B8NAEy40A4L5E:2C$b4r$7$$$G$9$M!#=1B= (B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/cag-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z#P#C![!!=1B(BDynaBook Satellite 6000 = SA113P/5=1B$B!J%Y!<%9%b%G%k=1B(BXP=1B$B!K=1B(B
 
=1B$B!!!!=1B(BWinXP=1B$BEk:\$N%N!<%H=1B(BPC=1B$B!J4k6H8~$1!K$,H/Gd$5= $l$^$7$?!#=1B(B
=1B$B!!!!4k6H8~$1$G$9$N$G!"NLHNE9Ey$G$OHNGd$5$l$F$$$^$= ;$s!#=1B(B
=1B$B!!!!$b$A$m$s8D?M$G$N9XF~$b2DG=3D$G$9!#=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/caf-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z%@%$%(%C%H![!!%/%$!<%s%-%c%s%Y%k%F%#!<=1B(B
 
=1B$B!!!!"#7n4V=1B(B20000=1B$B8DHNGdW7b$N%9!<%Q!<%@%$%(%C%H%F= %#!<$G$9!#?M5$$NHkL)$O=1B(B
=1B$B!!!!B>$G$O!"%^%M$N=3DPMh$J$$G[9g$H0{$= _0W$5!yC;4|4V%@%$%(%C%H7W2hCf$NJ}!y$=3D$N=1B(B
=1B$B!!!!B(8z@-$r=1B$B!!!!$l$PJVIJ2DG=3D"#=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/cai-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z7r9/![!!7r9/?)IJ!J%$%A%g%&MU%(%-%9!KAjGOH/855$$A$+$i!&6d0I#4#= 0=1B(B
 
=1B$B!!!!F|K\%$%A%g%&%U%!!<%`$O@$3&$,CmL\$9$k7r9/?)IJ!J%$%A%g%&MU%(%= -%9!K$N86NA@8=1B(B
=1B$B!!!!;:$+$i>&IJ@=3DB$!&HNGd$^$G0l4S$7$F9T$J$C$F= $$$k2q=1B$B!!!!$?$$J}$O$*;n$7$/$@$5$$!= #=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/ca7-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!ZH~MF![!!#S#I#L#K4pAC2=3D>QIJ=1B(B
 
=1B$B!!!!!X;W$$$d$j%1%"$GAGH)?<8F5[!Y$"$N%7%k%/$N2?$H$b8@$($J$$H)$6$= o$j$r@8$+$7$?=1B(B
=1B$B!!!!4pAC2=3D>QIJ!#%"%H%T!=1B$B!!!!$O$*;n$7%;%C%H$+$i$I$= &$>!#B~:#!"$*;n$7%;%C%HFCJL2A3J
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/cak-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z@83h![!!E7A3$N%P%$%"%0%i!!!H%^%+%Q%o!l=1B(B
 
=1B$B!!!!FnJF%"%s%G%986;:HkAp!H%^%+!I!#@.J,$O6C0[E*$G!"CK@-$K$OE7A3$= N%P%$%"%0%i$H=1B(B
=1B$B!!!!8@$o$l!"@8?#NO8~>e$KMj$b$7$$F/$-$r$7!"%Q%o= !<%"%C%WH472!*%^%+$r=1B$B!!!!CKC#$,B3=3DP!*=3Dw@-$K$O?= M$K8@$($J$$FCM-$N%*%s%J$NG:$_!JIT46>I!&@8M}IT=3Dg!&99=1B(B
=1B$B!!!!G/= 4|>c32!&Nd$(@-!&ITG%>IB>!K$K8z2LH/4x!*IWIX1_K~$NHkAp$H$7$F9%I>!#I{:nMQ=1B= (B
=1B$B!!!!0l@Z$J$7!*=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/cal-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z7r9/![!!%9!<%Q!<%k%Y%k%9#5#6#0=1B(B
 
=1B$B!!!!2q0wFCJL2A3J$GHNGdCf!*AwNA$bL5NA!*#T#V!";(;o$J$I$GOCBj$N%_%= _%:9ZAG!*=1B(B
=1B$B!!!!7*K\?50lO:Cx!VG>9<:I!&E|G"IB$r5_$&!W%W%l%<%s%H= !*$b$"$j!#!!!!@83h=3D,47IBM=3D=1B(B
=1B$B!!!!KI$K!*!*=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/caa-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!ZH~MF![!!%"%H%T!<$dH)9S$l$G$*G:$_$N$"$J$?$X:G?7$N4AJ}%/%j!<%`$= N$4>R2p=1B(B
 
=1B$B!!!!%"%H%T!?>$J$I$,860x$GM+]5$JKhF|$r2a$4$5$l$F$O$*$j$^$;$= s$+!)=1B(B
=1B$B!!!!<+A3$JAGH)$KLa$90Y$KD9G/$N8&5f$r=3DE$M3+H/$5$l$?:#= $^$G$KL5$$%/%j!<%`$G=1B(B
=1B$B!!!!$9!#!!%"%H%T!<$NJ}$,$4;HMQ$5$l$k0J3= 0$K!"2=3D>Q8e$N%1%"!"@v$$J*$N0Y$N=1B$B!!!!9S$l!"$K$-$S$J$I?'!9= $JLL$G$4MxMQ$7$FD:$1$k;I7cJ*$N4^$^$l$J$$H)$K$d$5=1B(B
=1B$B!!!!$7$$%/%= j!<%`$G$9!#=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/ca5-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z%@%$%(%C%H![!!6/NO%@%$%(%C%H%F%#!
 
=1B$B!!!!#1#0#0!sE7A3%O!<%V;HMQ$ND2Fb@v>tCc!*!!0{$`$@$1$GHnK~$HJXHk$= r2r>C$G$-=1B(B
=1B$B!!!!$^$9!*!!86NA$OE7A3%O!<%V#1#0#0!s$J$N$G6K$a$F0B= A4$G$9!#=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/ca6-001.html
 
=1B$B!!!!!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!]!= ]!]!]!]!]=1B(B
 
=1B$B!Z7r9/![!!%U%k!<%D%O!<%V!V%N%K%8%e!<%9!W=1B(B
 
=1B$B!!!!%]%j%M%7%"%s$+$i$NB#$jJ*!*!!%F%l%S!V@$3&$U$7$.H/8+!W$G>R2p$= 5$l$?1IM\=1B(B
=1B$B!!!!AG$,#1#4#0e$b4^$^$l$F$$$kH~$H7r9/$NK|G=3D= Lt!!=1B(B
 
=1B$B!!!!=1B(Bhttp://www.ec-inter.= com/mk/gds/ca1-001.html
 

=1B$B!a!a!a!a!a!a!a!a!a!a!a!a!a!!EPO?!!!&!!2r=3D|!!!a!a!a!a!a!a!= a!a!a!a!a!a!a!a=1B(B
 
           &n= bsp; =1B$B!!=1B(B=20 =1B$B!!=1B(B   =1B$B!!=1B(B http://www.ec-inter.com/mk/u= ef.html
 
=1B$B!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!a!= a!a!a!a!a=1B(B
 
=1B$B!!!!!!!!!!!!!!!!!!!!!!!!#A#1#S#h#o#p=1B(B
=1B$B!!!!!!!!!!!!!= !!!!!!!!!!!El5~ET?7=3DI6h9bEDGO>l#4!]#1!]#4=1B(B
=1B$B!!!!!!!!!!!!!!!!= !!!!!!!!=1B(Buser@ec-inter.com
 
 
------=_NextPart_000_0023_01C188E1.BBDC9860-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 10:37:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id C2CD837B41A for ; Wed, 19 Dec 2001 10:37:23 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 411002AD; Wed, 19 Dec 2001 18:37:15 +0000 (GMT) Date: Wed, 19 Dec 2001 18:37:15 +0000 From: Josef Karthauser To: Matthew Dillon Cc: freebsd-current@freebsd.org Subject: Re: cvs commit: src/sys/kern vfs_subr.c vfs_vnops.c src/sys/sys vnode.h Message-ID: <20011219183715.A9679@tao.org.uk> References: <200112182048.fBIKmsw61056@freefall.freebsd.org> <20011218233427.C412@tao.org.uk> <200112190103.fBJ134885760@apollo.backplane.com> <20011219010928.A3769@tao.org.uk> <200112190118.fBJ1IZQ85907@apollo.backplane.com> <20011219012344.A4024@tao.org.uk> <200112190802.fBJ82n387037@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112190802.fBJ82n387037@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Dec 19, 2001 at 12:02:49AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 19, 2001 at 12:02:49AM -0800, Matthew Dillon wrote: > hmm.. ok, there are some subsystems using sbuf's: >=20 > linprocfs > procfs > pseudofs >=20 > I think someone may have broken something in pseudofs, procfs, > and/or linprocfs that is causing the VFS cache and sbuf MALLOC > area to run away. >=20 > Anybody have any ideas? This certainly appear to be the case. I've unmounted procfs and linprocfs and I've got an uptime of 5 hours now. Result! :) Joe --UugvWAfsgieZRqgk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwg3loACgkQXVIcjOaxUBaEsQCdFnJWI2Sqx5m2GeovpyqhuwOs 4ZAAoJ3TP7ie72BZuXyLda4SXdw5gcOd =i+bx -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 11: 5:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6F32337B416 for ; Wed, 19 Dec 2001 11:05:25 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBJJ5M190050; Wed, 19 Dec 2001 11:05:22 -0800 (PST) (envelope-from dillon) Date: Wed, 19 Dec 2001 11:05:22 -0800 (PST) From: Matthew Dillon Message-Id: <200112191905.fBJJ5M190050@apollo.backplane.com> To: Josef Karthauser Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern vfs_subr.c vfs_vnops.c src/sys/sys vnode.h References: <200112182048.fBIKmsw61056@freefall.freebsd.org> <20011218233427.C412@tao.org.uk> <200112190103.fBJ134885760@apollo.backplane.com> <20011219010928.A3769@tao.org.uk> <200112190118.fBJ1IZQ85907@apollo.backplane.com> <20011219012344.A4024@tao.org.uk> <200112190802.fBJ82n387037@apollo.backplane.com> <20011219183715.A9679@tao.org.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> hmm.. ok, there are some subsystems using sbuf's: :>=20 :> linprocfs :> procfs :> pseudofs :>=20 :> I think someone may have broken something in pseudofs, procfs, :> and/or linprocfs that is causing the VFS cache and sbuf MALLOC :> area to run away. :>=20 :> Anybody have any ideas? : :This certainly appear to be the case. I've unmounted procfs and :linprocfs and I've got an uptime of 5 hours now. Result! :) : :Joe Excellent! Can you narrow the problem down further, to either procfs or linprocfs? I think I *may* have found it. Or at least I've found one error. There could be more: void sbuf_delete(struct sbuf *s) { assert_sbuf_integrity(s); /* don't care if it's finished or not */ if (SBUF_ISDYNAMIC(s)) SBFREE(s->s_buf); bzero(s, sizeof *s); if (SBUF_ISDYNSTRUCT(s)) SBFREE(s); } The structure is being bzero()'d before its dynamic flag gets checked. I've included a patch below. Josef, I would appreciate it if you would apply the patch and try your system with the various procfs devices mounted again. It's an obvious bug so I'm comitting it to -current now, the question is: Is it the *only* bug? -Matt Index: kern/subr_sbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/subr_sbuf.c,v retrieving revision 1.13 diff -u -r1.13 subr_sbuf.c --- kern/subr_sbuf.c 10 Dec 2001 05:51:45 -0000 1.13 +++ kern/subr_sbuf.c 19 Dec 2001 19:01:26 -0000 @@ -461,12 +461,15 @@ void sbuf_delete(struct sbuf *s) { + int isdyn; + assert_sbuf_integrity(s); /* don't care if it's finished or not */ if (SBUF_ISDYNAMIC(s)) SBFREE(s->s_buf); + isdyn = SBUF_ISDYNSTRUCT(s); bzero(s, sizeof *s); - if (SBUF_ISDYNSTRUCT(s)) + if (isdyn) SBFREE(s); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 11: 9:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id 6C54A37B405 for ; Wed, 19 Dec 2001 11:09:06 -0800 (PST) Received: (qmail 20204 invoked from network); 19 Dec 2001 19:09:06 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 19 Dec 2001 19:09:06 -0000 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: <200112191905.fBJJ5M190050@apollo.backplane.com> Date: Wed, 19 Dec 2001 11:08:51 -0800 (PST) From: John Baldwin To: Matthew Dillon Subject: Re: cvs commit: src/sys/kern vfs_subr.c vfs_vnops.c src/sys/sys Cc: freebsd-current@FreeBSD.ORG, Josef Karthauser Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 19-Dec-01 Matthew Dillon wrote: > >:> hmm.. ok, there are some subsystems using sbuf's: >:>=20 >:> linprocfs >:> procfs >:> pseudofs >:>=20 >:> I think someone may have broken something in pseudofs, procfs, >:> and/or linprocfs that is causing the VFS cache and sbuf MALLOC >:> area to run away. >:>=20 >:> Anybody have any ideas? >: >:This certainly appear to be the case. I've unmounted procfs and >:linprocfs and I've got an uptime of 5 hours now. Result! :) >: >:Joe > > Excellent! Can you narrow the problem down further, to either procfs or > linprocfs? > > I think I *may* have found it. Or at least I've found one error. There > could be more: > > void > sbuf_delete(struct sbuf *s) > { > assert_sbuf_integrity(s); > /* don't care if it's finished or not */ > > if (SBUF_ISDYNAMIC(s)) > SBFREE(s->s_buf); > bzero(s, sizeof *s); > if (SBUF_ISDYNSTRUCT(s)) > SBFREE(s); > } > > The structure is being bzero()'d before its dynamic flag gets checked. > I've included a patch below. Josef, I would appreciate it if you would > apply the patch and try your system with the various procfs devices > mounted again. It's an obvious bug so I'm comitting it to -current now, > the question is: Is it the *only* bug? > > -Matt Hmm, why bzero at all if you are just going to free it? Why not move the bzero to an else after the ISDYNSTRUCT check? (Not that this is really all that important, but... :) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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 Dec 19 11:10:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from 24sextv.com (catv-kwangjoo-210205028145.usr2.hananet.net [210.205.28.145]) by hub.freebsd.org (Postfix) with SMTP id 8B6BE37B405 for ; Wed, 19 Dec 2001 11:10:08 -0800 (PST) Reply-To: 24sextv@24sextv.com From: 24sextv <24sextv@24sextv.com> To: Subject: [] . . Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Thu, 20 Dec 2001 04:11:59 +0900 X-Priority: 3 X-Mailer: Mailtouch 1.0 Message-Id: <20011219191008.8B6BE37B405@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG

.  

.

.
 

.

http://24sextv.wo.to   .

.

[]

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 11:13:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6352A37B417; Wed, 19 Dec 2001 11:13:12 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBJJDBu90110; Wed, 19 Dec 2001 11:13:11 -0800 (PST) (envelope-from dillon) Date: Wed, 19 Dec 2001 11:13:11 -0800 (PST) From: Matthew Dillon Message-Id: <200112191913.fBJJDBu90110@apollo.backplane.com> To: John Baldwin Cc: freebsd-current@FreeBSD.org, Josef Karthauser Subject: Re: cvs commit: src/sys/kern vfs_subr.c vfs_vnops.c src/sys/sys References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> The structure is being bzero()'d before its dynamic flag gets checked. :> I've included a patch below. Josef, I would appreciate it if you would :> apply the patch and try your system with the various procfs devices :> mounted again. It's an obvious bug so I'm comitting it to -current now, :> the question is: Is it the *only* bug? :> :> -Matt : :Hmm, why bzero at all if you are just going to free it? Why not move the bzero :to an else after the ISDYNSTRUCT check? (Not that this is really all that :important, but... :) : :-- : :John Baldwin <>< http://www.FreeBSD.org/~jhb/ He is invalidating the structure to catch references to deleted sbufs. (see assert_sbuf_integrity() calls). Josef, I take back my last request... I think there's another bug. Your vmstat -m output showed that both the sbuf pool and the VFS cache pool were blown up. The fix I just made will probably only solve the sbuf pool issue. If you still want to test it, observe both pools in the vmstat -m output carefully! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 11:13:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 8C0D337B416 for ; Wed, 19 Dec 2001 11:13:17 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 1C8752AD; Wed, 19 Dec 2001 19:13:09 +0000 (GMT) Date: Wed, 19 Dec 2001 19:13:09 +0000 From: Josef Karthauser To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern vfs_subr.c vfs_vnops.c src/sys/sys vnode.h Message-ID: <20011219191309.A10531@tao.org.uk> References: <200112182048.fBIKmsw61056@freefall.freebsd.org> <20011218233427.C412@tao.org.uk> <200112190103.fBJ134885760@apollo.backplane.com> <20011219010928.A3769@tao.org.uk> <200112190118.fBJ1IZQ85907@apollo.backplane.com> <20011219012344.A4024@tao.org.uk> <200112190802.fBJ82n387037@apollo.backplane.com> <20011219183715.A9679@tao.org.uk> <200112191905.fBJJ5M190050@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112191905.fBJJ5M190050@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Dec 19, 2001 at 11:05:22AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 19, 2001 at 11:05:22AM -0800, Matthew Dillon wrote: >=20 > The structure is being bzero()'d before its dynamic flag gets checked. > I've included a patch below. Josef, I would appreciate it if you wou= ld > apply the patch and try your system with the various procfs devices > mounted again. It's an obvious bug so I'm comitting it to -current n= ow, > the question is: Is it the *only* bug? Patching now - I'll let you know how it fairs. Thanks :) Joe --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwg5sQACgkQXVIcjOaxUBaUrgCeKSq/GhR+vYUYZgSgOgaLM1IW HOkAn15eFbc19Erqwr9q9orevnU+3RqI =QHfl -----END PGP SIGNATURE----- --5vNYLRcllDrimb99-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 11:17:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 4417337B417 for ; Wed, 19 Dec 2001 11:17:07 -0800 (PST) Received: (qmail 5714 invoked from network); 19 Dec 2001 19:17:04 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 19 Dec 2001 19:17:04 -0000 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: <200112191913.fBJJDBu90110@apollo.backplane.com> Date: Wed, 19 Dec 2001 11:16:41 -0800 (PST) From: John Baldwin To: Matthew Dillon Subject: Re: cvs commit: src/sys/kern vfs_subr.c vfs_vnops.c src/sys/sys Cc: Josef Karthauser , freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 19-Dec-01 Matthew Dillon wrote: >:> The structure is being bzero()'d before its dynamic flag gets checked. >:> I've included a patch below. Josef, I would appreciate it if you would >:> apply the patch and try your system with the various procfs devices >:> mounted again. It's an obvious bug so I'm comitting it to -current >:> now, >:> the question is: Is it the *only* bug? >:> >:> -Matt >: >:Hmm, why bzero at all if you are just going to free it? Why not move the >:bzero >:to an else after the ISDYNSTRUCT check? (Not that this is really all that >:important, but... :) >: >:-- >: >:John Baldwin <>< http://www.FreeBSD.org/~jhb/ > > He is invalidating the structure to catch references to deleted sbufs. > (see assert_sbuf_integrity() calls). Fair enough. In theory an INVARIANTS kernel with 0xdeadc0de should do that for you though. :) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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 Dec 19 13: 2: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from net2.gendyn.com (nat2.gendyn.com [204.60.171.12]) by hub.freebsd.org (Postfix) with ESMTP id 42BA737B41A; Wed, 19 Dec 2001 13:01:42 -0800 (PST) Received: from [153.11.11.3] (helo=plunger.gdeb.com) by net2.gendyn.com with esmtp (Exim 2.12 #1) id 16GnqO-000L2i-00; Wed, 19 Dec 2001 16:01:40 -0500 Received: from clcrtr.gdeb.com ([153.11.109.11]) by plunger.gdeb.com with SMTP id PAA29836; Wed, 19 Dec 2001 15:47:50 -0500 (EST) Received: from vigrid.com (gpz.clc.gdeb.com [192.168.3.12]) by clcrtr.gdeb.com (8.11.4/8.11.4) with ESMTP id fBJL9tK15272; Wed, 19 Dec 2001 16:10:11 -0500 (EST) (envelope-from eischen@vigrid.com) Message-ID: <3C21000F.994BD53D@vigrid.com> Date: Wed, 19 Dec 2001 16:01:03 -0500 From: Daniel Eischen X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Cc: alpha@freebsd.org Subject: Munging jmp_bufs on alpha Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG libc_r seems to be broke on alpha and I'm trying to fix it. We munge jmp_bufs to create new contexts for threads and for the thread scheduler. It seems that sometime over the last few weeks/months something broke that. It doesn't look like _setjmp of _longjmp have changed at all, though. Included is a sample program that includes the jmp_buf-munging macros that use to work and that no longer work. [ Drew, you out there? You got these to work before ;-) ] Any help would be appreciated. Thanks, -- Dan Eischen -------------- #include #include #include /* for PAGE_SIZE */ #include #include #include #if defined(__i386__) #define SET_STACK_JB(jb, stk) (jb)[0]._jb[2] = (int)(stk) #define GET_STACK_JB(jb) ((unsigned long)((jb)[0]._jb[2])) #define SET_RETURN_ADDR_JB(jb, ra) (jb)[0]._jb[0] = (int)(ra) #elif defined(__alpha__) #include #define SET_STACK_JB(jb, stk) (jb)[0]._jb[R_SP + 4] = (long)(stk) #define GET_STACK_JB(jb) ((unsigned long)((jb)[0]._jb[R_SP + 4])) #define SET_RETURN_ADDR_JB(jb, ra) do { \ (jb)[0]._jb[2] = (unsigned long)(ra) + 8UL; \ (jb)[0]._jb[R_RA + 4] = 0; \ (jb)[0]._jb[R_T12 + 4] = (long)(ra); \ } while (0) #else #error "Don't recognize this architecture!" #endif static jmp_buf retjb; static jmp_buf schedjb; static void dump_jmpbuf(jmp_buf jb) { long *larr = (long *)jb[0]._jb; int i; for (i = 0; i < (sizeof(jmp_buf) / sizeof(long)); i++) { printf(" 0x%lx\n", larr[i]); } } static void scheduler() { int tmp; printf("Entered scheduler, stack is %p\n", &tmp); _longjmp(retjb, 1); } int main(int argc, char *argv[]) { long schedstack; long stacktop; int i; /* Create a stack for the scheduler: */ assert((schedstack = (long)malloc (PAGE_SIZE)) != NULL); /* Stack starts high and grows up/low: */ stacktop = schedstack + PAGE_SIZE - sizeof (double); /* Initialize the context for the scheduler: */ _setjmp(schedjb); printf("Scheduler jmp_buf after _setjmp:\n"); dump_jmpbuf(schedjb); SET_STACK_JB(schedjb, stacktop); SET_RETURN_ADDR_JB(schedjb, scheduler); printf("\nScheduler jmp_buf after tamporing:\n"); dump_jmpbuf(schedjb); printf("\n"); for (i = 0; i < 10; i++) { if (_setjmp(retjb) == 0) { printf("Switching to scheduler, count %d.\n", i); _longjmp(schedjb, 1); } } return (0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 14: 8: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id E3E9637B405; Wed, 19 Dec 2001 14:07:59 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.6/8.11.6) with ESMTP id fBJM7wR01201; Wed, 19 Dec 2001 14:07:58 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.1.0.14.2.20011219135833.00af0c60@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 19 Dec 2001 14:07:28 -0800 To: current@FreeBSD.ORG From: Manfred Antar Subject: New mail dumps core on current Cc: mikeh@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG mail dumps core on current with latest /usr/src/usr.bin/mail updates: (root)502}mail manfred Subject: test test test EOT Segmentation fault (core dumped) (root)503} This is from a current built today, although i think the changes were made yesterday. I noticed that I did not get mail from the daily periodic output. If I run periodic daily from shell i get: (root)503}periodic daily Segmentation fault - core dumped This happens on two different machines. one is an SMP box, the other is a laptop. world current as of noon today same with kernel. Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 14:14:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from green.bikeshed.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 59ACE37B416 for ; Wed, 19 Dec 2001 14:14:50 -0800 (PST) Received: from localhost (green@localhost) by green.bikeshed.org (8.11.6/8.11.6) with ESMTP id fBJMEUn33561 for ; Wed, 19 Dec 2001 17:14:44 -0500 (EST) (envelope-from green@green.bikeshed.org) Message-Id: <200112192214.fBJMEUn33561@green.bikeshed.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: current@FreeBSD.org Subject: CD-ROM installation of -CURRENT broken? From: Brian Fundakowski Feldman Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Dec 2001 17:14:29 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone know when installation of -CURRENT from CD-ROM got broken or a solution thereof? We end up having two problems: the fixit shell doesn't work, but before that an actual installation doesn't work because sysinstall's attempt to mount /dev/acd0c on /dist returns ENOENT. I havne't determined yet why this could be; anyone have clues? -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 14:39:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 8B35237B416; Wed, 19 Dec 2001 14:39:33 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id fBJMdWU46508; Wed, 19 Dec 2001 14:39:32 -0800 (PST) (envelope-from david) Date: Wed, 19 Dec 2001 14:39:32 -0800 (PST) From: David Wolfskill Message-Id: <200112192239.fBJMdWU46508@bunrab.catwhisker.org> To: current@FreeBSD.ORG, null@pozo.com Subject: Re: New mail dumps core on current Cc: mikeh@FreeBSD.ORG, obrien@FreeBSD.ORG In-Reply-To: <5.1.0.14.2.20011219135833.00af0c60@pozo.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Wed, 19 Dec 2001 14:07:28 -0800 >From: Manfred Antar >mail dumps core on current with latest /usr/src/usr.bin/mail updates: Yeah; I was able to reproduce that result. I then re-made mail, this time with the -g flag, and tried again; problem is detected in fixhead() (send.c:419). Running it under gdb, I see some weird stuff happening (or maybe I'm just confused). Here's the first part of fixhead(): /* * Fix the header by glopping all of the expanded names from * the distribution list into the appropriate fields. */ void fixhead(hp, tolist) struct header *hp; struct name *tolist; { struct name *np; hp->h_to = NULL; hp->h_cc = NULL; hp->h_bcc = NULL; for (np = tolist; np != NULL; np = np->n_flink) /* Don't copy deleted addresses to the header */ if (np->n_type & GDEL) continue; if ((np->n_type & GMASK) == GTO) The failure is on the first conditional in the for loop. Watch this: freebeast[22] gdb `which mail` GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (gdb) b fixhead Breakpoint 1 at 0x80545af: file /usr/src/usr.bin/mail/send.c, line 419. (gdb) set args -v david (gdb) r Starting program: /usr/bin/mail -v david Subject: Test 3 ??!!!!? . Cc: Breakpoint 1, fixhead (hp=0xbfbff808, tolist=0x805f000) at /usr/src/usr.bin/mail/send.c:419 419 { (gdb) p hp $1 = (struct header *) 0x805f000 (gdb) p tolist $2 = (struct name *) 0x1 (gdb) n 422 hp->h_to = NULL; (gdb) p hp $3 = (struct header *) 0xbfbff808 (gdb) p tolist $4 = (struct name *) 0x805f000 (gdb) OK, I realize that "constants aren't; variables won't," but this is getting a bit much. Is, perhaps, something screwy happening with the stack pointer (or some such thing; it's been ~8 years since I looked at the insides of gcc)? Cheers, david -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 14:59:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4EC1537B416 for ; Wed, 19 Dec 2001 14:59:22 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBJMxMF90892; Wed, 19 Dec 2001 14:59:22 -0800 (PST) (envelope-from dillon) Date: Wed, 19 Dec 2001 14:59:22 -0800 (PST) From: Matthew Dillon Message-Id: <200112192259.fBJMxMF90892@apollo.backplane.com> To: freebsd-current@freebsd.org Subject: Seeing a lot of 'microuptime() went backwards' messages during heavy disk I/O Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm seeing a lot of this during heavy disk I/O (5 postmark benchmarks running in parallel): microuptime() went backwards (44525.3954411 -> 44524.563978) microuptime() went backwards (57425.4282241 -> 57424.766121) microuptime() went backwards (57425.4282241 -> 57424.845844) microuptime() went backwards (60724.4427887 -> 60724.686232) microuptime() went backwards (60724.4427887 -> 60724.768808) microuptime() went backwards (61685.4418845 -> 61685.102724) microuptime() went backwards (61924.3906516 -> 61924.246151) microuptime() went backwards (62344.3800035 -> 62344.415407) Anyone know what's up? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 15:13:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 871A937B416 for ; Wed, 19 Dec 2001 15:13:25 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id fBJNDgt44059; Wed, 19 Dec 2001 15:13:42 -0800 (PST) Date: Wed, 19 Dec 2001 15:13:42 -0800 (PST) From: Doug White To: Matthew Dillon Cc: Subject: Re: Seeing a lot of 'microuptime() went backwards' messages during heavy disk I/O In-Reply-To: <200112192259.fBJMxMF90892@apollo.backplane.com> Message-ID: X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 19 Dec 2001, Matthew Dillon wrote: > I'm seeing a lot of this during heavy disk I/O (5 postmark benchmarks > running in parallel): > > microuptime() went backwards (44525.3954411 -> 44524.563978) > microuptime() went backwards (57425.4282241 -> 57424.766121) > microuptime() went backwards (57425.4282241 -> 57424.845844) > microuptime() went backwards (60724.4427887 -> 60724.686232) > microuptime() went backwards (60724.4427887 -> 60724.768808) > microuptime() went backwards (61685.4418845 -> 61685.102724) > microuptime() went backwards (61924.3906516 -> 61924.246151) > microuptime() went backwards (62344.3800035 -> 62344.415407) > > Anyone know what's up? This has been asked on just about every FreeBSD list since the printf was added. Use the archives, man! :) This is when you have a device generating too much interrupt latency -- enough to stall the RTC. Usually the offender is video cards, but in this case it could be your IDE controller. The usual fix is to try changing timecounters; sysctl kern.timecounter.hardware tells you what you're currently using. If you're on CURRENT, it's probably using ACPI. If you want to override it back to TSC, put 'hint.acpi_timer.0.disabled="1"' in your /boot/device.hints. Also try compiling with or without apm since this influences the timecounter as well (although if you're on SMP you might be stuck with the i8254). phk can clarify. :) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Dec 19 16: 0: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1E14437B405 for ; Wed, 19 Dec 2001 15:59:51 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBJNxlb21845; Wed, 19 Dec 2001 15:59:47 -0800 (PST) (envelope-from dillon) Date: Wed, 19 Dec 2001 15:59:47 -0800 (PST) From: Matthew Dillon Message-Id: <200112192359.fBJNxlb21845@apollo.backplane.com> To: Josef Karthauser Cc: freebsd-current@FreeBSD.ORG Subject: Found second pseudofs bug... References: <200112182048.fBIKmsw61056@freefall.freebsd.org> <20011218233427.C412@tao.org.uk> <200112190103.fBJ134885760@apollo.backplane.com> <20011219010928.A3769@tao.org.uk> <200112190118.fBJ1IZQ85907@apollo.backplane.com> <20011219012344.A4024@tao.org.uk> <200112190802.fBJ82n387037@apollo.backplane.com> <20011219183715.A9679@tao.org.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Really easy to reproduce. ls -lR /proc vmstat -m | fgrep vfscache ls -lR /proc vmstat -m | fgrep vfscache ls -lR /proc vmstat -m | fgrep vfscache The pseudofs code is using the wrong VOP descriptor, but I'll let DES fix it when he gets back. In the mean time I have added appropriate comments and cache_purge() calls and committed the interim fix to -current. I also adding a missing cache_purge() call to the reclaim code which is required to be there regardless of the VOP descriptor issue. Josef, I believe that this plus the last patch, both of which are now in -current, will solve your problem. Note: cvsup repositories may not have been updated as of the time of this posting. -Matt Index: fs/pseudofs//pseudofs_vncache.c =================================================================== RCS file: /home/ncvs/src/sys/fs/pseudofs/pseudofs_vncache.c,v retrieving revision 1.9 diff -u -r1.9 pseudofs_vncache.c --- fs/pseudofs//pseudofs_vncache.c 3 Nov 2001 03:07:09 -0000 1.9 +++ fs/pseudofs//pseudofs_vncache.c 19 Dec 2001 23:49:48 -0000 @@ -105,9 +105,11 @@ { struct pfs_vdata *pvd; int error; - - /* see if the vnode is in the cache */ - /* XXX linear search... not very efficient */ + + /* + * See if the vnode is in the cache. + * XXX linear search is not very efficient. + */ mtx_lock(&pfs_vncache_mutex); for (pvd = pfs_vncache; pvd; pvd = pvd->pvd_next) { if (pvd->pvd_pn == pn && pvd->pvd_pid == pid) { @@ -115,6 +117,8 @@ ++pfs_vncache_hits; *vpp = pvd->pvd_vnode; mtx_unlock(&pfs_vncache_mutex); + /* XXX see comment at top of pfs_lookup() */ + cache_purge(*vpp); return (0); } /* XXX if this can happen, we're in trouble */ @@ -176,6 +180,8 @@ pfs_vncache_free(struct vnode *vp) { struct pfs_vdata *pvd; + + cache_purge(vp); mtx_lock(&pfs_vncache_mutex); pvd = (struct pfs_vdata *)vp->v_data; Index: fs/pseudofs//pseudofs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/fs/pseudofs/pseudofs_vnops.c,v retrieving revision 1.20 diff -u -r1.20 pseudofs_vnops.c --- fs/pseudofs//pseudofs_vnops.c 11 Dec 2001 20:48:20 -0000 1.20 +++ fs/pseudofs//pseudofs_vnops.c 19 Dec 2001 23:52:06 -0000 @@ -293,6 +293,15 @@ /* * Look up a file or directory + * + * XXX NOTE! pfs_lookup() has been hooked into vop_lookup_desc! This + * will result in a lookup operation for a vnode which may already be + * cached, therefore we have to be careful to purge the VFS cache when + * reusing a vnode. + * + * This code will work, but is not really correct. Normally we would hook + * vfs_cache_lookup() into vop_lookup_desc and hook pfs_lookup() into + * vop_cachedlookup_desc. */ static int pfs_lookup(struct vop_lookup_args *va) @@ -385,6 +394,9 @@ error = pfs_vncache_alloc(vn->v_mount, vpp, pn, pid); if (error) PFS_RETURN (error); + /* + * XXX See comment at top of the routine. + */ if (cnp->cn_flags & MAKEENTRY) cache_enter(vn, *vpp, cnp); PFS_RETURN (0); @@ -693,7 +705,7 @@ pfs_reclaim(struct vop_reclaim_args *va) { PFS_TRACE((((struct pfs_vdata *)va->a_vp->v_data)->pvd_pn->pn_name)); - + return (pfs_vncache_free(va->a_vp)); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 16: 1:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B212A37B417 for ; Wed, 19 Dec 2001 16:01:39 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBK01c721879; Wed, 19 Dec 2001 16:01:38 -0800 (PST) (envelope-from dillon) Date: Wed, 19 Dec 2001 16:01:38 -0800 (PST) From: Matthew Dillon Message-Id: <200112200001.fBK01c721879@apollo.backplane.com> To: Doug White Cc: Subject: Re: Seeing a lot of 'microuptime() went backwards' messages during heavy disk I/O References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :This has been asked on just about every FreeBSD list since the printf was :added. Use the archives, man! :) : :This is when you have a device generating too much interrupt latency -- :enough to stall the RTC. Usually the offender is video cards, but in this :case it could be your IDE controller. This is on a SCSI machine, but I get your drift. :The usual fix is to try changing timecounters; sysctl :kern.timecounter.hardware tells you what you're currently using. If :you're on CURRENT, it's probably using ACPI. If you want to override it :back to TSC, put 'hint.acpi_timer.0.disabled="1"' in your :/boot/device.hints. Also try compiling with or without apm since this :influences the timecounter as well (although if you're on SMP you might be :stuck with the i8254). : :phk can clarify. :) : :Doug White | FreeBSD: The Power to Serve I would prefer that it figure out the correct time counter itself rather then plague us with fraggin microuptime messages for the last N years :-( -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 16:40:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 3518B37B41B for ; Wed, 19 Dec 2001 16:40:08 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011220004007.EILD6450.rwcrmhc52.attbi.com@InterJet.elischer.org>; Thu, 20 Dec 2001 00:40:07 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA47792; Wed, 19 Dec 2001 16:24:07 -0800 (PST) Date: Wed, 19 Dec 2001 16:24:06 -0800 (PST) From: Julian Elischer To: Matthew Dillon Cc: freebsd-current@freebsd.org Subject: Re: Seeing a lot of 'microuptime() went backwards' messages during heavy disk I/O In-Reply-To: <200112192259.fBJMxMF90892@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been seeing them a lot too on a "recent" (NOV) -current On Wed, 19 Dec 2001, Matthew Dillon wrote: > I'm seeing a lot of this during heavy disk I/O (5 postmark benchmarks > running in parallel): > > microuptime() went backwards (44525.3954411 -> 44524.563978) > microuptime() went backwards (57425.4282241 -> 57424.766121) > microuptime() went backwards (57425.4282241 -> 57424.845844) > microuptime() went backwards (60724.4427887 -> 60724.686232) > microuptime() went backwards (60724.4427887 -> 60724.768808) > microuptime() went backwards (61685.4418845 -> 61685.102724) > microuptime() went backwards (61924.3906516 -> 61924.246151) > microuptime() went backwards (62344.3800035 -> 62344.415407) > > Anyone know what's up? > > -Matt > Matthew Dillon > > > 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 Wed Dec 19 18:21:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by hub.freebsd.org (Postfix) with ESMTP id BDA9F37B41A; Wed, 19 Dec 2001 18:21:32 -0800 (PST) Received: from dagger.cc.vt.edu (IDENT:mirapoint@dagger-lb.cc.vt.edu [10.1.1.11]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id fBK2LV7518036; Wed, 19 Dec 2001 21:21:31 -0500 (EST) Received: from enterprise.muriel.penguinpowered.com (hc652647d.dhcp.vt.edu [198.82.100.125]) by dagger.cc.vt.edu (Mirapoint) with ESMTP id ARV33771; Wed, 19 Dec 2001 21:21:30 -0500 (EST) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.5.2.FreeBSD:20011219212130:5476=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <5.1.0.14.2.20011219135833.00af0c60@pozo.com> Date: Wed, 19 Dec 2001 21:21:30 -0500 (EST) From: Mike Heffner To: Manfred Antar Subject: Re: New mail dumps core on current Cc: mikeh@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.5.2.FreeBSD:20011219212130:5476=_ Content-Type: text/plain; charset=us-ascii On 19-Dec-2001 Manfred Antar wrote: | mail dumps core on current with latest /usr/src/usr.bin/mail updates: | Argh, I forgot braces around a 'for' loop. This has been fixed by Andrey in rev. 1.12 of send.c. Mike -- Mike Heffner Blacksburg, VA --_=XFMail.1.5.2.FreeBSD:20011219212130:5476=_ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8IUspFokZQs3sv5kRAhAnAJ9QHvYIDBSJq8E8hBREHxpA+F971gCfUE5g 4qRTvnsd8HKtXrA6hfYanOg= =Gq9y -----END PGP SIGNATURE----- --_=XFMail.1.5.2.FreeBSD:20011219212130:5476=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 19:11:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 03D3A37B416 for ; Wed, 19 Dec 2001 19:11:56 -0800 (PST) Received: from attbi.com ([12.237.33.57]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011220031155.OBTW20122.rwcrmhc53.attbi.com@attbi.com> for ; Thu, 20 Dec 2001 03:11:55 +0000 Message-ID: <3C215712.2C982D08@attbi.com> Date: Wed, 19 Dec 2001 21:12:18 -0600 From: Joe Halpin X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: Trying to build CURRENT Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm getting the following error when running 'make buildworld' perl -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/des/asm:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/perlasm /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/bf/asm/bf-586.pl elf 386 > bf-586.cmt /usr/libexec/ld-elf.so.1: Shared object "libperl.so.3" not found *** Error code 1 Stop in /usr/src/secure/lib/libcrypto. *** Error code 1 Stop in /usr/src/secure/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I'm running 4.4-RELEASE right now, and trying to go to -CURRENT. I did a cvsup to get the source, and ran make buildworld I just updated the source tree tonight. Should I wait to try again, or am I doing something wrong? I've got the complete make output in a file if that would help. Thanks Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 19 22:18:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from matrix.potatoslicer.com (matrix.potatoslicer.com [65.85.56.14]) by hub.freebsd.org (Postfix) with ESMTP id A529337B41B for ; Wed, 19 Dec 2001 22:18:14 -0800 (PST) Received: (from pinky@localhost) by matrix.potatoslicer.com (8.11.6/8.11.6) id fBK6KKS05204 for freebsd-current@FreeBSD.org; Thu, 20 Dec 2001 06:20:20 GMT Date: Thu, 20 Dec 2001 06:20:20 +0000 From: Mike Bernardo To: freebsd-current@FreeBSD.org Subject: subscribe freebsd-current Message-ID: <20011220062020.D20240@potatoslicer.com> 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 0:31:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id CF23A37B405 for ; Thu, 20 Dec 2001 00:31:22 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id fBK8V5075106; Thu, 20 Dec 2001 10:31:05 +0200 (EET) (envelope-from ru) Date: Thu, 20 Dec 2001 10:31:05 +0200 From: Ruslan Ermilov To: Joe Halpin Cc: "current@FreeBSD.ORG" Subject: Re: Trying to build CURRENT Message-ID: <20011220103105.A67452@sunbay.com> References: <3C215712.2C982D08@attbi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C215712.2C982D08@attbi.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Dec 19, 2001 at 09:12:18PM -0600, Joe Halpin wrote: > I'm getting the following error when running 'make buildworld' > > perl > -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/des/asm:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/perlasm > /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/bf/asm/bf-586.pl > elf 386 > bf-586.cmt > /usr/libexec/ld-elf.so.1: Shared object "libperl.so.3" not found > *** Error code 1 > > Stop in /usr/src/secure/lib/libcrypto. > *** Error code 1 > > Stop in /usr/src/secure/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > I'm running 4.4-RELEASE right now, and trying to go to -CURRENT. I did a > cvsup to get the source, and ran make buildworld > > I just updated the source tree tonight. Should I wait to try again, or > am I doing something wrong? > > I've got the complete make output in a file if that would help. > Your host environment is screwed, you lost /usr/lib/libperl.so.3. Watch ``ldd /usr/bin/perl'' output. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 0:51:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta08.onebox.com (mta08.onebox.com [64.68.76.143]) by hub.freebsd.org (Postfix) with ESMTP id CAB5337B417; Thu, 20 Dec 2001 00:51:48 -0800 (PST) Received: from onebox.com ([10.1.111.10]) by mta06.onebox.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20011219160336.WBSB29423.mta06.onebox.com@onebox.com>; Wed, 19 Dec 2001 08:03:36 -0800 Received: from [198.187.174.15] by onebox.com with HTTP; Wed, 19 Dec 2001 08:03:36 -0800 Date: Wed, 19 Dec 2001 08:03:36 -0800 Subject: Re: Buildworld broken on _FBSDID in xinstall.c ?? From: "Glenn Gombert" To: Warner Losh Cc: Mike Barcroft , Michel Oosterhof , freebsd-current@FreeBSD.ORG, markm@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Message-Id: <20011219160336.WBSB29423.mta06.onebox.com@onebox.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thats what I did yesterday, and buildworld/installworld worked fine after that :)) ---- Warner Losh wrote: > In message <20011219004309.D93504@espresso.q9media.com> Mike Barcroft > writes: > : > Any suggestions? > : > : I would recommend removing the __FBSD() line locally until this has > : been resolved. > > cvsup might be better :-) > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 1: 7: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from deathrow.mail.pas.earthlink.net (deathrow.mail.pas.earthlink.net [207.217.120.19]) by hub.freebsd.org (Postfix) with ESMTP id 20DB637B417; Thu, 20 Dec 2001 01:07:06 -0800 (PST) Received: from hawk.mail.pas.earthlink.net ([207.217.120.22] helo=hawk.prod.itd.earthlink.net) by deathrow.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16GQ0q-0005OC-00; Tue, 18 Dec 2001 11:34:52 -0800 Received: from [209.179.200.2] (helo=mindspring.com) by hawk.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16GPzH-0002se-00; Tue, 18 Dec 2001 11:33:15 -0800 Message-ID: <3C1F99E0.7D488222@mindspring.com> Date: Tue, 18 Dec 2001 11:32:48 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: current@FreeBSD.org Subject: Re: Object now: man(1) -m option is going away References: <20011218193941.A9895@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > I'd like to drop the support for the man(1)'s -m option, > which is almost undocumented and is of little interest. > Unless I hear any valid objections, I am going to nuke > it on Friday. How do you propose we look at Alpha specific man pages on x86 boxes, after this change? Thanks, -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 1:14:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 2135937B405 for ; Thu, 20 Dec 2001 01:14:19 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id fBK9E1o81235; Thu, 20 Dec 2001 11:14:01 +0200 (EET) (envelope-from ru) Date: Thu, 20 Dec 2001 11:14:01 +0200 From: Ruslan Ermilov To: Terry Lambert Cc: current@FreeBSD.org Subject: Re: Object now: man(1) -m option is going away Message-ID: <20011220111401.E67452@sunbay.com> References: <20011218193941.A9895@sunbay.com> <3C1F99E0.7D488222@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1F99E0.7D488222@mindspring.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Dec 18, 2001 at 11:32:48AM -0800, Terry Lambert wrote: > Ruslan Ermilov wrote: > > I'd like to drop the support for the man(1)'s -m option, > > which is almost undocumented and is of little interest. > > Unless I hear any valid objections, I am going to nuke > > it on Friday. > > How do you propose we look at Alpha specific man pages on x86 > boxes, after this change? > I suppose you have them installed in standard places, like /usr/share/man/man4/alpha/. If so, use the MACHINE environment variable, as documented in the man(1) manpage. If you have then installed in a separate tree, use the MANPATH environment variable, or the -M option to man(1). Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 5:36:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id C3AA337B416; Thu, 20 Dec 2001 05:36:11 -0800 (PST) Received: from attbi.com ([12.237.33.57]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011220133611.WYVQ19716.rwcrmhc51.attbi.com@attbi.com>; Thu, 20 Dec 2001 13:36:11 +0000 Message-ID: <3C21E962.E8837812@attbi.com> Date: Thu, 20 Dec 2001 07:36:34 -0600 From: Joe Halpin X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: "current@FreeBSD.ORG" Subject: Re: Trying to build CURRENT References: <3C215712.2C982D08@attbi.com> <20011220103105.A67452@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > > On Wed, Dec 19, 2001 at 09:12:18PM -0600, Joe Halpin wrote: > > I'm getting the following error when running 'make buildworld' > > > > perl > > -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/des/asm:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/perlasm > > /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/bf/asm/bf-586.pl > > elf 386 > bf-586.cmt > > /usr/libexec/ld-elf.so.1: Shared object "libperl.so.3" not found > > *** Error code 1 > > > > Stop in /usr/src/secure/lib/libcrypto. > > *** Error code 1 > > > > Stop in /usr/src/secure/lib. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > > > I'm running 4.4-RELEASE right now, and trying to go to -CURRENT. I did a > > cvsup to get the source, and ran make buildworld > > > > I just updated the source tree tonight. Should I wait to try again, or > > am I doing something wrong? > > > > I've got the complete make output in a file if that would help. > > > Your host environment is screwed, you lost /usr/lib/libperl.so.3. > Watch ``ldd /usr/bin/perl'' output. Yep. See my response to Mike. I got going again by manually copying it from the build directory. Thanks Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 6: 0:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from mustard.heime.net (mustard.heime.net [194.234.65.222]) by hub.freebsd.org (Postfix) with ESMTP id A43D437B416 for ; Thu, 20 Dec 2001 06:00:50 -0800 (PST) Received: from localhost (roy@localhost) by mustard.heime.net (8.11.6/8.9.3) with ESMTP id fBKE0TT30012 for ; Thu, 20 Dec 2001 15:00:29 +0100 Date: Thu, 20 Dec 2001 15:00:29 +0100 (CET) From: Roy Sigurd Karlsbakk X-Sender: To: Subject: Intel 82544GC Gigabit support? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi does anyone know if this is/will be supported? roy -- Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA Computers are like air conditioners. They stop working when you open Windows. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 6: 9:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from jester.ti.com (jester.ti.com [192.94.94.1]) by hub.freebsd.org (Postfix) with ESMTP id 44B6B37B416 for ; Thu, 20 Dec 2001 06:09:10 -0800 (PST) Received: from dlep6.itg.ti.com ([157.170.188.9]) by jester.ti.com (8.11.6/8.11.6) with ESMTP id fBKE98T21934 for ; Thu, 20 Dec 2001 08:09:09 -0600 (CST) Received: from dlep6.itg.ti.com (localhost [127.0.0.1]) by dlep6.itg.ti.com (8.9.3/8.9.3) with ESMTP id IAA11299 for ; Thu, 20 Dec 2001 08:09:07 -0600 (CST) Received: from ffab.tide.ti.com (selenium.ffab.tide.ti.com [137.167.200.28]) by dlep6.itg.ti.com (8.9.3/8.9.3) with ESMTP id IAA11272 for ; Thu, 20 Dec 2001 08:09:06 -0600 (CST) Received: from ishtar.ffab.tide.ti.com (IDENT:89tQzFMiPpweErYqKj8A1nXBfYyia5rE@ishtar.ffab.tide.ti.com [137.167.222.71]) by ffab.tide.ti.com (8.12.1/8.12.1) with ESMTP id fBKE95O9000452 for ; Thu, 20 Dec 2001 15:09:05 +0100 (MET) Received: from ti.com (IDENT:vhjTe4rVu6PDjWPHklyZ0pccFq6RB8cu@ishtar.ffab.tide.ti.com [137.167.222.71]) by ishtar.ffab.tide.ti.com (8.11.6/8.11.6) with ESMTP id fBKE95726364 for ; Thu, 20 Dec 2001 15:09:05 +0100 Message-ID: <3C21F100.499C699C@ti.com> Date: Thu, 20 Dec 2001 15:09:04 +0100 From: Jean Louis Ntakpe Reply-To: ntakpe@ti.com Organization: TI Freising - Automation Group X-Sender: "Jean Louis Ntakpe" <@ishtar.ffab.tide.ti.com> (Unverified) X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.9-13enterprise i686) X-Accept-Language: en,zh-CN,zh-TW MIME-Version: 1.0 To: current@freebsd.org Subject: Merry Christmas and Happy New Year Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I know, this is not the right place, but my best wishes to the whole freebsd community for doing such a great job. To all of you *** merry christmas and happy new year *** regards, -- Jean Louis Ntakpe Texas Instruments - Freising Wafer Fab Automation Group Haggerty Str. 1 85350 Freising Telefon +49 (8161) 80-3816 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 6:14:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from web20801.mail.yahoo.com (web20801.mail.yahoo.com [216.136.226.190]) by hub.freebsd.org (Postfix) with SMTP id C6EC937B416 for ; Thu, 20 Dec 2001 06:14:15 -0800 (PST) Message-ID: <20011220141414.5987.qmail@web20801.mail.yahoo.com> Received: from [66.72.162.172] by web20801.mail.yahoo.com via HTTP; Thu, 20 Dec 2001 06:14:14 PST Date: Thu, 20 Dec 2001 06:14:14 -0800 (PST) From: north star Subject: __stdoutp causing hassle ;) To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Heyas After upgrading directly to CURRENT from 4.3- RELEASE I've been presented with a rather loud and whiney bug (I thought it at first to be my ex- girlfriend somehow manifested via `festival` but thk god it was not). Every shared library on the system drops via ld-elf.so.1 regarding the symbol __stdoutp. This pretty much kills everything as I m sure u can imagine :) Does anyone have any idea why the libs arent being pointed to libc.so.5 properly? (That is where __stdoutp should be (and is) defined.) Any input is appreciated. north_ http://blessedchildren.virtualave.net/ __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 7:41:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id D914F37B419 for ; Thu, 20 Dec 2001 07:41:48 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id fBKFfmb48922; Thu, 20 Dec 2001 07:41:48 -0800 (PST) (envelope-from david) Date: Thu, 20 Dec 2001 07:41:48 -0800 (PST) From: David Wolfskill Message-Id: <200112201541.fBKFfmb48922@bunrab.catwhisker.org> To: freebsd-current@FreeBSD.ORG, northern_snow78@yahoo.com Subject: Re: __stdoutp causing hassle ;) In-Reply-To: <20011220141414.5987.qmail@web20801.mail.yahoo.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Thu, 20 Dec 2001 06:14:14 -0800 (PST) >From: north star > After upgrading directly to CURRENT from 4.3- >RELEASE I've been presented with a rather loud and >whiney bug (I thought it at first to be my ex- >girlfriend somehow manifested via `festival` but >thk god it was not). Every shared library on the >system drops via ld-elf.so.1 regarding the symbol >__stdoutp.... I suspect that you failed to include COMPAT4X= yes in /etc/make.conf (as a review of the -current archives should have indicated). Cheers, david -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 8: 7:27 2001 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 3402D37B447; Thu, 20 Dec 2001 08:07:15 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id DAA20874; Fri, 21 Dec 2001 03:07:13 +1100 Date: Fri, 21 Dec 2001 03:07:11 +1100 (EST) From: Bruce Evans X-X-Sender: To: Brian Fundakowski Feldman Cc: Subject: Re: CD-ROM installation of -CURRENT broken? In-Reply-To: <200112192214.fBJMEUn33561@green.bikeshed.org> Message-ID: <20011221025513.S1790-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 19 Dec 2001, Brian Fundakowski Feldman wrote: > Does anyone know when installation of -CURRENT from CD-ROM got broken or a > solution thereof? We end up having two problems: the fixit shell doesn't > work, but before that an actual installation doesn't work because > sysinstall's attempt to mount /dev/acd0c on /dist returns ENOENT. I havne't > determined yet why this could be; anyone have clues? The 'c' partition of acd0 devices was broken for the non-DEVFS case in rev.104 of atapi-cd.c. (The errno for this is ENXIO.) DEVFS is not in GENERIC and "make release" doesn't seem to add it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 8:27:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from green.bikeshed.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 84CC537B416; Thu, 20 Dec 2001 08:27:10 -0800 (PST) Received: from localhost (green@localhost) by green.bikeshed.org (8.11.6/8.11.6) with ESMTP id fBKGR6H40338; Thu, 20 Dec 2001 11:27:07 -0500 (EST) (envelope-from green@green.bikeshed.org) Message-Id: <200112201627.fBKGR6H40338@green.bikeshed.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: CD-ROM installation of -CURRENT broken? In-Reply-To: Message from Bruce Evans of "Fri, 21 Dec 2001 03:07:11 +1100." <20011221025513.S1790-100000@gamplex.bde.org> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Dec 2001 11:27:06 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Wed, 19 Dec 2001, Brian Fundakowski Feldman wrote: > > > Does anyone know when installation of -CURRENT from CD-ROM got broken or a > > solution thereof? We end up having two problems: the fixit shell doesn't > > work, but before that an actual installation doesn't work because > > sysinstall's attempt to mount /dev/acd0c on /dist returns ENOENT. I havne't > > determined yet why this could be; anyone have clues? > > The 'c' partition of acd0 devices was broken for the non-DEVFS case in > rev.104 of atapi-cd.c. (The errno for this is ENXIO.) DEVFS is not > in GENERIC and "make release" doesn't seem to add it. Well, really, all we should care about is the devfs case since anything else is meant to be deprecated; I'd rather fix this at the source... DEVFS is no longer optional, so it is in GENERIC for certain. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 8:46:32 2001 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 81D8E37B422; Thu, 20 Dec 2001 08:46:27 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id DAA22585; Fri, 21 Dec 2001 03:46:24 +1100 Date: Fri, 21 Dec 2001 03:46:23 +1100 (EST) From: Bruce Evans X-X-Sender: To: "Brian F. Feldman" Cc: Subject: Re: CD-ROM installation of -CURRENT broken? In-Reply-To: <200112201627.fBKGR6H40338@green.bikeshed.org> Message-ID: <20011221034203.X2138-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 20 Dec 2001, Brian F. Feldman wrote: > Bruce Evans wrote: > > The 'c' partition of acd0 devices was broken for the non-DEVFS case in > > rev.104 of atapi-cd.c. (The errno for this is ENXIO.) DEVFS is not > > in GENERIC and "make release" doesn't seem to add it. > > Well, really, all we should care about is the devfs case since anything else > is meant to be deprecated; I'd rather fix this at the source... DEVFS is no > longer optional, so it is in GENERIC for certain. Oops, DEVFS is in GENERIC, but not because it isn't optional. It is controlled by a bogus negative option (NODEVFS). The NODEVFS case has rotted a bit, but it isn't as broken as DEVFS yet. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 9:20:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id C5E6E37B405 for ; Thu, 20 Dec 2001 09:20:11 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id fBKHH5h54189 for current@FreeBSD.org; Thu, 20 Dec 2001 19:17:05 +0200 (EET) (envelope-from ru) Date: Thu, 20 Dec 2001 19:17:05 +0200 From: Ruslan Ermilov To: current@FreeBSD.org Subject: Dropping bsd.man.mk support from bsd.kmod.mk Message-ID: <20011220191705.B47953@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I'd like to drop bsd.man.mk support from bsd.kmod.mk, because I was told by someone (peter?) that this is the right direction. :-) Objections? Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 11:13:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 43C9437B41A for ; Thu, 20 Dec 2001 11:13:30 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011220191329.DRKE6450.rwcrmhc52.attbi.com@peter3.wemm.org> for ; Thu, 20 Dec 2001 19:13:29 +0000 Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fBKJDRs78611 for ; Thu, 20 Dec 2001 11:13:27 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 9119538CC; Thu, 20 Dec 2001 11:13:27 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Luigi Rizzo Cc: current@freebsd.org Subject: Re: vm_zeropage priority problems. In-Reply-To: <20011218160949.B89864@iguana.aciri.org> Date: Thu, 20 Dec 2001 11:13:27 -0800 From: Peter Wemm Message-Id: <20011220191327.9119538CC@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > [Cc peter because he introduced this code] > > Hi, > i was trying the following code in -current (basically copied from > vm_zeropage.c), to implement device polling in the idle loop, and > noticed that the process would take all of the CPU time. Being > suspicious that something was wrong with priorities, I added a > couple of printfs, and to my surprise, the priority of the process > (pri_level) after the first tsleep() becomes 104 instead of staying > at 255 as it was originally initialized. > > A quick scan of the files in sys/sys shows that 104 is PPAUSE, > and this is the source of the problem. Excellent catch! This particular problem was one of the main reasons why this is still defaulting to 'off'. I have a couple of other changes to it pending commit to fix some of Bruce's complaints, but I hadn't noticed the cause of this. Part of the problem is that tsleep temporarily elevates the priority for wakeup, and it is normally returned back to "normal" level when the process returns to userland (see the *_userpri stuff). Changing the tlseep PPAUSE value isn't necessarily the right thing either because the priority propagation mechanism will elevate us if we hold a lock that something else *needs*. (This is so that when it yields, we will run and do what we need to do and presumably release the lock.) > I guess this is a bug in vm_zeropage.c, the second parameter > in tsleep should be td->td_ksegrp->kg_pri.pri_level instead > of PPAUSE, or at least the priority should be reset to the > original value after returning from the tsleep ? Possibly both of these. Let me do some checking. > cheers > luigi > > static void > poll_idle(void) > { > struct thread *td = curthread; > struct rtprio rtp; > > rtp.prio = RTP_PRIO_MAX; /* lowest priority */ > rtp.type = RTP_PRIO_IDLE; > mtx_lock_spin(&sched_lock); > rtp_to_pri(&rtp, &td->td_ksegrp->kg_pri); > mtx_unlock_spin(&sched_lock); > > printf("idlepoll start and sleep, pri is %d native %d user %d\n", > td->td_ksegrp->kg_pri.pri_level, > td->td_ksegrp->kg_pri.pri_native, > td->td_ksegrp->kg_pri.pri_user); > for (;;) { > if (poll_in_idle && poll_handlers > 0) { > idlepoll_sleeping = 0; > mtx_lock(&Giant); > ether_poll(poll_each_burst); > mtx_unlock(&Giant); > mtx_assert(&Giant, MA_NOTOWNED); > mtx_lock_spin(&sched_lock); > setrunqueue(td); > td->td_proc->p_stats->p_ru.ru_nvcsw++; > mi_switch(); > mtx_unlock_spin(&sched_lock); > } else { > printf("idlepoll goes to sleep, " > "pri is %d native %d user %d\n", > td->td_ksegrp->kg_pri.pri_level, > td->td_ksegrp->kg_pri.pri_native, > td->td_ksegrp->kg_pri.pri_user); > idlepoll_sleeping = 1; > tsleep(&idlepoll_sleeping, PPAUSE, "pollid", hz * 3); > } > } > } > > static struct proc *idlepoll; > static struct kproc_desc idlepoll_kp = { > "idlepoll", > poll_idle, > &idlepoll > }; > SYSINIT(idlepoll, SI_SUB_KTHREAD_VM, SI_ORDER_ANY, kproc_start, &idlepoll_kp) > > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 11:24:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 9780A37B41A for ; Thu, 20 Dec 2001 11:24:16 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id fBKJOGT08373; Thu, 20 Dec 2001 11:24:16 -0800 (PST) (envelope-from rizzo) Date: Thu, 20 Dec 2001 11:24:15 -0800 From: Luigi Rizzo To: Peter Wemm Cc: current@freebsd.org Subject: Re: vm_zeropage priority problems. Message-ID: <20011220112415.B8230@iguana.aciri.org> References: <20011218160949.B89864@iguana.aciri.org> <20011220191327.9119538CC@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011220191327.9119538CC@overcee.netplex.com.au> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 20, 2001 at 11:13:27AM -0800, Peter Wemm wrote: ... > Excellent catch! This particular problem was one of the main reasons > why this is still defaulting to 'off'. I have a couple of other changes > to it pending commit to fix some of Bruce's complaints, but I hadn't > noticed the cause of this. > > Part of the problem is that tsleep temporarily elevates the priority for > wakeup, and it is normally returned back to "normal" level when the process > returns to userland (see the *_userpri stuff). ah, ok, kernel threads never return to userland... so, i presume one should also make sure that after the process is scheduled, the priority is restored to the 'native' level; this should also solve the problem with the priority propagation mechanism (though... I have the feeling that if you have nested locks, this cannot scale...) cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 12:16:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id 7AB4E37B41A for ; Thu, 20 Dec 2001 12:16:25 -0800 (PST) Received: (qmail 22249 invoked from network); 20 Dec 2001 20:16:25 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Dec 2001 20:16:25 -0000 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: <20011220112415.B8230@iguana.aciri.org> Date: Thu, 20 Dec 2001 12:16:03 -0800 (PST) From: John Baldwin To: Luigi Rizzo Subject: Re: vm_zeropage priority problems. Cc: current@freebsd.org, Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 20-Dec-01 Luigi Rizzo wrote: > On Thu, Dec 20, 2001 at 11:13:27AM -0800, Peter Wemm wrote: > ... >> Excellent catch! This particular problem was one of the main reasons >> why this is still defaulting to 'off'. I have a couple of other changes >> to it pending commit to fix some of Bruce's complaints, but I hadn't >> noticed the cause of this. >> >> Part of the problem is that tsleep temporarily elevates the priority for >> wakeup, and it is normally returned back to "normal" level when the process >> returns to userland (see the *_userpri stuff). > > ah, ok, kernel threads never return to userland... > > so, i presume one should also make sure that after the process is > scheduled, the priority is restored to the 'native' level; this > should also solve the problem with the priority propagation mechanism > (though... I have the feeling that if you have nested locks, this > cannot scale...) Priority propagation will already handle things ok. We drop to pri_native after we drop a lock (although if we still hold a contested lock we bump our priority to the min(nativepri, highest priority of threads on contested locks we hold and drop to nativepri after dropping the last contested lock). However, kthreads should tsleep() with their current priority, not PPAUSE. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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 Thu Dec 20 12:36: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 6282B37B417; Thu, 20 Dec 2001 12:36:02 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id fBKKa2m08943; Thu, 20 Dec 2001 12:36:02 -0800 (PST) (envelope-from rizzo) Date: Thu, 20 Dec 2001 12:36:02 -0800 From: Luigi Rizzo To: John Baldwin Cc: current@FreeBSD.org, Peter Wemm Subject: Re: vm_zeropage priority problems. Message-ID: <20011220123602.H8230@iguana.aciri.org> References: <20011220112415.B8230@iguana.aciri.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 20, 2001 at 12:16:03PM -0800, John Baldwin wrote: ... > Priority propagation will already handle things ok. We drop to pri_native > after we drop a lock (although if we still hold a contested lock we bump our > priority to the min(nativepri, highest priority of threads on contested locks > we hold and drop to nativepri after dropping the last contested lock). ok, thanks for the clarification > However, kthreads should tsleep() with their current priority, not PPAUSE. "current" meaning pri_level or pri_native ? What if one tries to tsleep() while holding a lock and so its pri_level is raised ? In the device polling code i did a tsleep on the "original" pri_level, but maybe pri_native is good enough. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 12:41:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 7B29C37B419 for ; Thu, 20 Dec 2001 12:41:29 -0800 (PST) Received: (qmail 22774 invoked from network); 20 Dec 2001 20:41:28 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Dec 2001 20:41:28 -0000 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: <20011220123602.H8230@iguana.aciri.org> Date: Thu, 20 Dec 2001 12:41:11 -0800 (PST) From: John Baldwin To: Luigi Rizzo Subject: Re: vm_zeropage priority problems. Cc: Peter Wemm , current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 20-Dec-01 Luigi Rizzo wrote: > On Thu, Dec 20, 2001 at 12:16:03PM -0800, John Baldwin wrote: > ... >> Priority propagation will already handle things ok. We drop to pri_native >> after we drop a lock (although if we still hold a contested lock we bump our >> priority to the min(nativepri, highest priority of threads on contested >> locks >> we hold and drop to nativepri after dropping the last contested lock). > > ok, thanks for the clarification > >> However, kthreads should tsleep() with their current priority, not PPAUSE. > > "current" meaning pri_level or pri_native ? What if one tries to > tsleep() while holding a lock and so its pri_level is raised ? pri_level. Calling tsleep() while holding a lock is a bug though. :) Unless you are calling msleep() with a lock that will be released. > In the device polling code i did a tsleep on the "original" pri_level, > but maybe pri_native is good enough. pri_level is more correct. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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 Thu Dec 20 13: 4:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 01BF537B419 for ; Thu, 20 Dec 2001 13:04:19 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id IAA02097; Fri, 21 Dec 2001 08:04:16 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01KC4FM3BBQ8VMI1AU@cim.alcatel.com.au>; Fri, 21 Dec 2001 08:04:14 +1100 Received: from cirb503493.alcatel.com.au (pj1592 [192.168.123.159]) by gsmx07.alcatel.com.au (8.11.6/8.11.6) with ESMTP id fBKL4At64143; Fri, 21 Dec 2001 08:04:10 +1100 Received: (from jeremyp@localhost) by cirb503493.alcatel.com.au (8.11.6/8.11.6) id fBK7VpT38045; Thu, 20 Dec 2001 18:31:51 +1100 (EST envelope-from jeremyp) Date: Thu, 20 Dec 2001 18:31:51 +1100 From: Peter Jeremy Subject: Re: My naive addendum to Matt's recommended dev/test env In-reply-to: <20011214120624.A1153@hda.hda.com>; from dufault@hda.com on Fri, Dec 14, 2001 at 12:06:24PM -0500 To: Peter Dufault Cc: current@FreeBSD.ORG Message-id: <20011220183151.A37290@cirb503493.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20011214120624.A1153@hda.hda.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Dec 14, 2001 at 12:06:24PM -0500, Peter Dufault wrote: ... >> # cd /FreeBSD/FreeBSD-stable/src >> # make installworld > >(Lot's of noise as the stable kernel installs the stable world. Then reboot) You've missed a critical step here: Before you "reboot" you need to run mergemaster. You might be lucky and not need it for the -RELEASE to -STABLE upgrade, but you can be certain that the one time you don't bother, it'll come back and bite you in some obscure manner. >> # sync The sync isn't necessary (and has never been necessary for FreeBSD). >> # reboot Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 16:33:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from web20802.mail.yahoo.com (web20802.mail.yahoo.com [216.136.226.191]) by hub.freebsd.org (Postfix) with SMTP id 0278C37B405 for ; Thu, 20 Dec 2001 16:33:14 -0800 (PST) Message-ID: <20011221003312.17315.qmail@web20802.mail.yahoo.com> Received: from [66.72.165.138] by web20802.mail.yahoo.com via HTTP; Thu, 20 Dec 2001 16:33:12 PST Date: Thu, 20 Dec 2001 16:33:12 -0800 (PST) From: north star Subject: Re: __stdoutp causing hassle ;) To: David Wolfskill , freebsd-current@FreeBSD.ORG In-Reply-To: <200112201541.fBKFfmb48922@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I suspect that you failed to include > > COMPAT4X= yes > > in /etc/make.conf (as a review of the -current > archives should have > indicated). > > Cheers, > david Ah, worked beautifully! Thanks, David, I appreciate it. I did look at the mail archives quickly but usually if I don't see anything within the past week or so I assume either I'm being ignorant of something or there is a new bug. I don't mind admitting when its my ignorance at fault :) north_ http://blessedchildren.virtualave.net/ __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 18: 2:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from infoviaplus.net.ar (adv18.infoviaplus.net.ar [200.9.212.60]) by hub.freebsd.org (Postfix) with ESMTP id 0319A37B416; Thu, 20 Dec 2001 18:02:02 -0800 (PST) Received: from Windows ([200.63.137.113]) by infoviaplus.net.ar (Tid InfoMail Exchanger v2.20) with SMTP id #1008898760.080420001; Thu, 20 Dec 2001 22:39:20 -0300 From: rssa To: "Y ahora que.....????????????" Reply-To: proyarge@yahoo.com.ar X-Mailer: MultiMailer (3.1.0) Subject: y ahora que Mime-Version: 1.0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable X-Infomail-Spawn: rssa@speedy.com.ar a 200 destinos X-Infomail-Id: 1008898761.1F6A01AC1E039F.58761 Message-Id: <20011221020202.0319A37B416@hub.freebsd.org> Date: Thu, 20 Dec 2001 18:02:02 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ;EL PUEBLO TENDRA QUE VOLVER A= SALIR A LA CALLE

AHORA COMIENZA EL REPARTO DE= LA TORTA

SE FUE CAVALLO Y de la= RUA, AHORA EMPIEZA LA VERDADERA BATALLA ENTRE LOS UD. NO= VOTO.-
AHORA ES EL MOMENTO EN QUE PUERTA NO SABE= DURANTE CUANTO TIEMPO GOBERNARA

AHORA ES EL MOMENTO EN QUE= RUCKAUFT, DUHALDE, de la SOTA, RODRIGUEZ SAA, REUTEMAN Y DEMAS= CON LA COMPLACENCIA DE LOS CORRUPTOS Y CILENTELISTAS DIPUTADOS Y= SENADORES DEBEN DECIDIR CUANDO SE LLAMA A ELECCIONES: EN UN MES;= DOS MESES; SEIS MESES; UN AÑO O RECIEN EN EL= 2003???????????????
Y EN TANTO EL PUEBLO QUE= HACE?????????
MIRA, USADO Y ESPERA A VER= SI LE DEVALUAN EL PESO Y EN CONSECUENCIA LE DEVALUAN EL SALARIO= PORQUE YA ESTAN NEGOCIANDO LOS LEGISLADORES JUSITICIALISTAS CON= LA UNION INDUSTRIAL.-
LA BOLSA SOLO HOY SUBE MAS DEL= 17 %.-
CUAL ES EL FUTURO SI NO HAY
UN PROYECTO DE PAIS

MIENTRAS NO SE REUNA UNA= NUEVA CONVENCION CONSTITUYENTE CON DIRIGENTES NUEVOS A NIVEL= NACIONAL Y DE CADA PROVINCIA; MIENTRAS NO SE IMPLEMENTE UN= SISTEMA DE GOBIERNO PALAMENTARIO; MIENTRAS NO SE RECONFIGURE LA= DISTRIBUICION GEOPOLITICA CON MENOS DE PROVINCIAS; MIENTRAS NO= SE DISMINUYAN LA CANTIDAD DE MUNICIPIOS Y OTRAS MUCHAS= CUESTIONES MAS
EL PUEBLO DEBERA NECESARIAMENTE SALIR A LAS PLAZAS CON SUS= CACEROLAS

FUTURO ARGENTINO
 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 18:18:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 2A32B37B405; Thu, 20 Dec 2001 18:18:36 -0800 (PST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2:206:5bff:fe05:7829]) by white.imgsrc.co.jp (Postfix) with ESMTP id 1286D24D2C; Fri, 21 Dec 2001 11:18:35 +0900 (JST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [2001:218:422:2:230:48ff:fe41:161b]) by black.imgsrc.co.jp (Postfix) with ESMTP id 246291E4811; Fri, 21 Dec 2001 11:18:33 +0900 (JST) Date: Fri, 21 Dec 2001 11:18:33 +0900 Message-ID: <7mu1ul9uyu.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: ache@FreeBSD.org Cc: Current Subject: Broken at share/colldef User-Agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ===> share ===> share/colldef colldef -I /usr/src/share/colldef -o bg_BG.CP1251.out /usr/src/share/colldef/bg_BG.CP1251.src ... /sv_SE.ISO8859-1.src colldef -I /usr/src/share/colldef -o uk_UA.ISO8859-5.out /usr/src/share/colldef/uk_UA.ISO8859-5.src colldef: Char 0xcd duplicated near line 36 *** Error code 69 Stop in /usr/src/share/colldef. *** Error code 1 Stop in /usr/src/share. *** Error code 1 -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 18:46: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id D357C37B41B for ; Thu, 20 Dec 2001 18:45:54 -0800 (PST) Received: from attbi.com ([12.237.33.57]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011221024553.SYPB19716.rwcrmhc51.attbi.com@attbi.com> for ; Fri, 21 Dec 2001 02:45:53 +0000 Message-ID: <3C22A278.32AE9EB@attbi.com> Date: Thu, 20 Dec 2001 20:46:16 -0600 From: Joe Halpin X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: spam Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm starting to get spam since I joined this list, and the spam is coming from freebsd.org. If I'm reading the headers right, it's coming in through a freebsd.org mail server. Return-Path: Received: from mx2.freebsd.org ([216.136.204.119]) by rwcrgwc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011221020219.DAHA2770.rwcrgwc54.attbi.com@mx2.freebsd.org>; Fri, 21 Dec 2001 02:02:19 +0000 Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 2BD2E559AE; Thu, 20 Dec 2001 18:02:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: by hub.freebsd.org (Postfix, from userid 538) id E83FF37B405; Thu, 20 Dec 2001 18:02:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id 3319E2E8209; Thu, 20 Dec 2001 18:02:08 -0800 (PST) Received: by hub.freebsd.org (bulk_mailer v1.12); Thu, 20 Dec 2001 18:02:08 -0800 Delivered-To: freebsd-current@freebsd.org Received: from infoviaplus.net.ar (adv18.infoviaplus.net.ar [200.9.212.60]) by hub.freebsd.org (Postfix) with ESMTP id 0319A37B416; Thu, 20 Dec 2001 18:02:02 -0800 (PST) Received: from Windows ([200.63.137.113]) by infoviaplus.net.ar (Tid InfoMail Exchanger v2.20) with SMTP id #1008898760.080420001; Thu, 20 Dec 2001 22:39:20 -0300 From: rssa To: "Y ahora que.....????????????" Reply-To: proyarge@yahoo.com.ar X-Mailer: MultiMailer (3.1.0) Subject: y ahora que Mime-Version: 1.0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable X-Infomail-Spawn: rssa@speedy.com.ar a 200 destinos X-Infomail-Id: 1008898761.1F6A01AC1E039F.58761 Message-Id: <20011221020202.0319A37B416@hub.freebsd.org> Date: Thu, 20 Dec 2001 18:02:02 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Precedence: bulk X-Mozilla-Status: 8001 X-Mozilla-Status2: 00000000 X-UIDL: <20011221020202.0319A37B416@hub.freebsd.org> Is this just a normal part of being on the list? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 18:50: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-d.strhg1.mi.home.com [24.13.43.207]) by hub.freebsd.org (Postfix) with ESMTP id 04BC237B417 for ; Thu, 20 Dec 2001 18:49:59 -0800 (PST) Received: by turtle.looksharp.net (Postfix, from userid 1003) id 7238B3EC1; Thu, 20 Dec 2001 21:52:03 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by turtle.looksharp.net (Postfix) with ESMTP id 6507BBAA5; Thu, 20 Dec 2001 21:52:03 -0500 (EST) Date: Thu, 20 Dec 2001 21:52:03 -0500 (EST) From: "Brandon D. Valentine" To: Joe Halpin Cc: "current@FreeBSD.ORG" Subject: Re: spam In-Reply-To: <3C22A278.32AE9EB@attbi.com> Message-ID: <20011220214950.V28481-100000@turtle.looksharp.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 20 Dec 2001, Joe Halpin wrote: >I'm starting to get spam since I joined this list, and the spam is >coming from freebsd.org. If I'm reading the headers right, it's coming >in through a freebsd.org mail server. >Is this just a normal part of being on the list? You're not getting the spam directly. The spam is sent to the mailing list and then sent to you as a subscriber. This is an unfortunate side effect of the fact that the mailing lists are open to posting from non-subscribers. Brandon D. Valentine -- "Iam mens praetrepidans avet vagari." - G. Valerius Catullus, Carmina, XLVI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 18:51: 8 2001 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 8AEE437B41A for ; Thu, 20 Dec 2001 18:51:04 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id fBL2p1f02040; Thu, 20 Dec 2001 21:51:01 -0500 (EST) (envelope-from wollman) Date: Thu, 20 Dec 2001 21:51:01 -0500 (EST) From: Garrett Wollman Message-Id: <200112210251.fBL2p1f02040@khavrinen.lcs.mit.edu> To: Joe Halpin Cc: "current@FreeBSD.ORG" Subject: spam In-Reply-To: <3C22A278.32AE9EB@attbi.com> References: <3C22A278.32AE9EB@attbi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: > Is this just a normal part of being on the list? Yes, lots of spammers spew at FreeBSD mailing-lists. If you can identify a persistent source of spam, the postmaster is fairly responsive in filtering them. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 21:24:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 80F1C37B419 for ; Thu, 20 Dec 2001 21:24:17 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id fBL5O7q08462; Thu, 20 Dec 2001 21:24:07 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id fBL5O6H26667; Thu, 20 Dec 2001 21:24:06 -0800 (PST) (envelope-from jdp) Date: Thu, 20 Dec 2001 21:24:06 -0800 (PST) Message-Id: <200112210524.fBL5O6H26667@vashon.polstra.com> To: current@freebsd.org From: John Polstra Cc: roy@karlsbakk.net Subject: Re: Intel 82544GC Gigabit support? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article , Roy Sigurd Karlsbakk wrote: > > does anyone know if this is/will be supported? I believe it is supported by the "em" driver, which has been in -current for a few weeks and was recently merged into -stable. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chgyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 20 21:40:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8C2DF37B41B for ; Thu, 20 Dec 2001 21:40:08 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBL5e7584983; Thu, 20 Dec 2001 21:40:07 -0800 (PST) (envelope-from dillon) Date: Thu, 20 Dec 2001 21:40:07 -0800 (PST) From: Matthew Dillon Message-Id: <200112210540.fBL5e7584983@apollo.backplane.com> To: Joe Halpin Cc: "current@FreeBSD.ORG" Subject: Re: spam References: <3C22A278.32AE9EB@attbi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I'm starting to get spam since I joined this list, and the spam is :coming from freebsd.org. If I'm reading the headers right, it's coming :in through a freebsd.org mail server. Ha. In the last two weeks the amount of personal spam I receive has gone up exponentially. I'm getting around 60 a day now. I'm not surprised that the list is seeing a big increase. I can only hope that our illustrious congress has grown as tired of spam as I have and will fix the law to simply ban it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 0: 1:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from mgate12.so-net.ne.jp (mgate12.so-net.ne.jp [210.139.254.159]) by hub.freebsd.org (Postfix) with ESMTP id B93A737B405; Fri, 21 Dec 2001 00:01:47 -0800 (PST) Received: from mail.bd6.so-net.ne.jp (mspool18.so-net.ne.jp [210.139.248.18]) by mgate12.so-net.ne.jp (8.9.3/3.7W01120319) with ESMTP id RAA07007; Fri, 21 Dec 2001 17:01:42 +0900 (JST) Received: from fun03 (p293658.tokynt01.ap.so-net.ne.jp [218.41.54.88]) by mail.bd6.so-net.ne.jp with SMTP id fBL81fK21848; Fri, 21 Dec 2001 17:01:41 +0900 (JST) Message-Id: <200112210801.fBL81fK21848@mail.bd6.so-net.ne.jp> Reply-To: "#fun-club@docomo.ne.jp" <#fun-club@docomo.ne.jp> From: "#fun-club@docomo.ne.jp" <#fun-club@docomo.ne.jp> Subject: http://www.fun-club.net Date: Fri, 21 Dec 2001 15:53:09 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit To: undisclosed-recipients:; Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG g 18f }jAKaJgGb`GAL`lC y300zy''Gb`z ^tOrAwZ} rfIs^s! yENO1i}jAbNz x A vhttp://www.fun-club.net aJt@Nu I` yHzyz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 5:46:45 2001 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 D8CA237B419; Fri, 21 Dec 2001 05:46:42 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id AAA06426; Sat, 22 Dec 2001 00:46:38 +1100 Date: Sat, 22 Dec 2001 00:46:40 +1100 (EST) From: Bruce Evans X-X-Sender: To: John Baldwin Cc: Luigi Rizzo , Peter Wemm , Subject: Re: vm_zeropage priority problems. In-Reply-To: Message-ID: <20011222003639.B4708-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 20 Dec 2001, John Baldwin wrote: > On 20-Dec-01 Luigi Rizzo wrote: > > On Thu, Dec 20, 2001 at 12:16:03PM -0800, John Baldwin wrote: > >> However, kthreads should tsleep() with their current priority, not PPAUSE. > > > > "current" meaning pri_level or pri_native ? What if one tries to > > tsleep() while holding a lock and so its pri_level is raised ? > > pri_level. Calling tsleep() while holding a lock is a bug though. :) Unless > you are calling msleep() with a lock that will be released. > > > In the device polling code i did a tsleep on the "original" pri_level, > > but maybe pri_native is good enough. > > pri_level is more correct. I think pri_native is just an implementation detail which shouldn't be used or visible to threads. It used used by the priority propagation mechanism to hold the original pri_level. Threads should just use their original priority (or a different one if they want to temporarily change thier priority). Even pri_level probably shouldn't be used or visible to threads. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 5:51:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 866CC37B419; Fri, 21 Dec 2001 05:51:20 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id fBLDpHo15390; Fri, 21 Dec 2001 05:51:17 -0800 (PST) (envelope-from rizzo) Date: Fri, 21 Dec 2001 05:51:17 -0800 From: Luigi Rizzo To: Bruce Evans Cc: John Baldwin , Peter Wemm , current@FreeBSD.ORG Subject: Re: vm_zeropage priority problems. Message-ID: <20011221055117.A15321@iguana.aciri.org> References: <20011222003639.B4708-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011222003639.B4708-100000@gamplex.bde.org> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Dec 22, 2001 at 12:46:40AM +1100, Bruce Evans wrote: > I think pri_native is just an implementation detail which shouldn't > be used or visible to threads. It used used by the priority propagation > mechanism to hold the original pri_level. Threads should just use their > original priority (or a different one if they want to temporarily change > thier priority). Even pri_level probably shouldn't be used or visible > to threads. the original priority should be somewhere and accessible, either directly or through some function. Otherwise how do we know what to pass to tsleep() ? In any case I wonder if this is a bug new in -current; -stable uses three separate data structures for realtime, user and idle tasks so even specifying the wrong priority in tsleep should not cause crossing classes there. -current has only one array, hence the chance of doing the wrong thing. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 6:38:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 7548737B405 for ; Fri, 21 Dec 2001 06:38:44 -0800 (PST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2:206:5bff:fe05:7829]) by white.imgsrc.co.jp (Postfix) with ESMTP id 30A8224D2C for ; Fri, 21 Dec 2001 23:38:43 +0900 (JST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [2001:218:422:2:230:48ff:fe41:161b]) by black.imgsrc.co.jp (Postfix) with ESMTP id 506D11E4814 for ; Fri, 21 Dec 2001 23:38:40 +0900 (JST) Date: Fri, 21 Dec 2001 23:38:42 +0900 Message-ID: <7mk7vgfxjh.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: FYI: Panic at in_pcbremlists() User-Agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I got a panic with today's current. I don't know I can reproduce this panic or not... Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 01000000 fault virtual address = 0x14 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0214186 stack pointer = 0x10:0xe519cc88 frame pointer = 0x10:0xe519cc8c 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 = 13 (swi6: tty:sio clock) kernel: type 12 trap, code=0 Stopped at in_pcbremlists+0x82: movl %eax,0x4(%edx) db> Context switches not allowed in the debugger. db> trace in_pcbremlists(e9fb11e0,e9fb11e0,0,e9fb12a0,e9fb11e0) at in_pcbremlists+0x82 in_pcbdetach(e9fb11e0,6,e9fb12a0,c0225f0c,e9fb12a0) at in_pcbdetach+0x35 tcp_close(e9fb12a0,e519ccf8,c01c4246,e9fb12a0,c386c2c0) at tcp_close+0x236 tcp_timer_2msl(e9fb12a0) at tcp_timer_2msl+0x52 softclock(0) at softclock+0x136 ithread_loop(c386d180,e519cd48,c386d180,c01aeef0,0) at ithread_loop+0x12e fork_exit(c01aeef0,c386d180,e519cd48) at fork_exit+0x9c fork_trampoline() at fork_trampoline+0x8 -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 7:45:33 2001 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 0F60737B491; Fri, 21 Dec 2001 07:45:19 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id CAA11904; Sat, 22 Dec 2001 02:45:12 +1100 Date: Sat, 22 Dec 2001 02:45:14 +1100 (EST) From: Bruce Evans X-X-Sender: To: Luigi Rizzo Cc: John Baldwin , Peter Wemm , Subject: Re: vm_zeropage priority problems. In-Reply-To: <20011221055117.A15321@iguana.aciri.org> Message-ID: <20011222023741.P5064-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 21 Dec 2001, Luigi Rizzo wrote: > On Sat, Dec 22, 2001 at 12:46:40AM +1100, Bruce Evans wrote: > > I think pri_native is just an implementation detail which shouldn't > > be used or visible to threads. It used used by the priority propagation > > mechanism to hold the original pri_level. Threads should just use their > > original priority (or a different one if they want to temporarily change > > thier priority). Even pri_level probably shouldn't be used or visible > > to threads. > > the original priority should be somewhere and accessible, > either directly or through some function. Otherwise how > do we know what to pass to tsleep() ? It's whatever the thread set itself. There is no good way of setting this either (vm_pagezero() and poll_idle() hack it into td->td_ksegrp->kg_pri). Userland would use rtprio(2) instead. Unfortunately, this gives priorities in different units than the ones for tsleep(). > In any case I wonder if this is a bug new in -current; -stable > uses three separate data structures for realtime, user and idle tasks > so even specifying the wrong priority in tsleep should not cause > crossing classes there. -current has only one array, hence the > chance of doing the wrong thing. The 3 classes are a design bug in -stable. Crossing classes is sometimes right and 3 classes mainly make it harder and force triplication of code. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 7:50:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by hub.freebsd.org (Postfix) with SMTP id 618F337B41B for ; Fri, 21 Dec 2001 07:50:36 -0800 (PST) Received: (qmail 12225 invoked from network); 21 Dec 2001 15:49:47 -0000 Received: from ken.yumyumyum.org (HELO there) (192.168.0.2) by dsl092-171-091.wdc1.dsl.speakeasy.net with SMTP; 21 Dec 2001 15:49:47 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Kenneth Culver To: freebsd-current@freebsd.org Subject: panic on 12/20/01 current Date: Fri, 21 Dec 2001 10:50:51 -0500 X-Mailer: KMail [version 1.3.1] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011221155036.618F337B41B@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have just managed to repetedly panic -CURRENT... How you ask? I'll tell you :-D The short story is "Run a linux version of XFree86," here's the long story: first, I got the linux version of XFree86, along with all it's driver modules (compliled under linux of course). Then in /usr/compat/linux/dev, I created tty entries using mknod (mknod tty0 c 12 0, etc.. for each tty up to 5) then I did this: /usr/compat/linux/usr/X11R6/bin/XFree86 the XFree86 said "error switching terminal's" or something similar, and immediately after that, FreeBSD panics with the following: Fatal trap 12 while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8: 0xc0204f57 stack pointer = 0x10:0xf94dfaf8 frame pointer = 0x10:0xf94dfb14 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 = 262 (XFree86) kernel: type 12 trap, code = 0 I didn't write all the argument adresses down because my computer was stuck beeping at me... just one constant beeeeeeep until I restart the computer so I wanted to reboot it as fast as possible, if these are needed, I can go back and get them. They all appeared valid anyway (none of them were NULL) db> trace scioctl + 0xa33 spec_ioctl + 0x26 ufs_vnoperatespec + 0x15 vn_ioctl + 0x10f ioctl + 0x288 linux_ioctl_console + 0x209 linux_ioctl + 0x54 That's basically the end, there was more but I think this is all that's relevant... Anyway, If anyone reproduces this or fixes this or even reads this and has more questions, please let me know. Thanks. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 8: 6:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (66-188-92-95.mad.wi.charter.com [66.188.92.95]) by hub.freebsd.org (Postfix) with ESMTP id 794ED37B416 for ; Fri, 21 Dec 2001 08:06:54 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.6/8.11.6) id fBLG6cf73267; Fri, 21 Dec 2001 10:06:38 -0600 (CST) (envelope-from jlemon) Date: Fri, 21 Dec 2001 10:06:38 -0600 (CST) From: Jonathan Lemon Message-Id: <200112211606.fBLG6cf73267@prism.flugsvamp.com> To: kuriyama@imgsrc.co.jp, current@freebsd.org Subject: Re: FYI: Panic at in_pcbremlists() X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article you write: > >I got a panic with today's current. I don't know I can reproduce this >panic or not... This probably is in: 1015 if (LIST_FIRST(&phd->phd_pcblist) == NULL) { 1016 LIST_REMOVE(phd, phd_hash); 1017 free(phd, M_PCB); but without the structure pointers, there isn't much to debug. Is there a crash dump available? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 8:15:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id F0C1537B417 for ; Fri, 21 Dec 2001 08:15:08 -0800 (PST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2:206:5bff:fe05:7829]) by white.imgsrc.co.jp (Postfix) with ESMTP id 08BC724D32 for ; Sat, 22 Dec 2001 01:15:08 +0900 (JST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [2001:218:422:2:230:48ff:fe41:161b]) by black.imgsrc.co.jp (Postfix) with ESMTP id 20A1F1E46E8 for ; Sat, 22 Dec 2001 01:15:05 +0900 (JST) Date: Sat, 22 Dec 2001 01:15:07 +0900 Message-ID: <7melloft2s.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: current@freebsd.org Subject: Re: FYI: Panic at in_pcbremlists() In-Reply-To: <200112211606.fBLG6cf73267@prism.flugsvamp.com> References: <200112211606.fBLG6cf73267@prism.flugsvamp.com> User-Agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At Fri, 21 Dec 2001 10:06:38 -0600 (CST), Jonathan Lemon wrote: > >I got a panic with today's current. I don't know I can reproduce this > >panic or not... > > This probably is in: > > 1015 if (LIST_FIRST(&phd->phd_pcblist) == NULL) { > 1016 LIST_REMOVE(phd, phd_hash); > 1017 free(phd, M_PCB); > > but without the structure pointers, there isn't much to debug. > Is there a crash dump available? Yes, I have. But this machine have 2GB memory and dump is 2GB, too. So it is difficult to send dump. If you can instruct how I should do, I'll follow you. -- Jun Kuriyama // IMG SRC, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 9: 7:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 15F9F37B42B for ; Fri, 21 Dec 2001 09:07:23 -0800 (PST) Received: (qmail 8830 invoked from network); 21 Dec 2001 17:07:22 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 21 Dec 2001 17:07:22 -0000 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: <20011222023741.P5064-100000@gamplex.bde.org> Date: Fri, 21 Dec 2001 09:07:05 -0800 (PST) From: John Baldwin To: Bruce Evans Subject: Re: vm_zeropage priority problems. Cc: current@FreeBSD.ORG, Peter Wemm , Luigi Rizzo Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 21-Dec-01 Bruce Evans wrote: > On Fri, 21 Dec 2001, Luigi Rizzo wrote: > >> On Sat, Dec 22, 2001 at 12:46:40AM +1100, Bruce Evans wrote: >> > I think pri_native is just an implementation detail which shouldn't >> > be used or visible to threads. It used used by the priority propagation >> > mechanism to hold the original pri_level. Threads should just use their >> > original priority (or a different one if they want to temporarily change >> > thier priority). Even pri_level probably shouldn't be used or visible >> > to threads. >> >> the original priority should be somewhere and accessible, >> either directly or through some function. Otherwise how >> do we know what to pass to tsleep() ? > > It's whatever the thread set itself. There is no good way of setting > this either (vm_pagezero() and poll_idle() hack it into > td->td_ksegrp->kg_pri). Userland would use rtprio(2) instead. > Unfortunately, this gives priorities in different units than the ones > for tsleep(). pri_level is the current priority of the thread. The actual priority level is going to move back into the thread and out of the KSE group so that tsleep and priority propagation work properly, but pri_native, pri_user, and nice will stay in the KSE group. The "normal" priorities for tsleep() are just a subset of the priorities available to a thread. Thus, they are using the same unit, but perhaps a wider range. >> In any case I wonder if this is a bug new in -current; -stable >> uses three separate data structures for realtime, user and idle tasks >> so even specifying the wrong priority in tsleep should not cause >> crossing classes there. -current has only one array, hence the >> chance of doing the wrong thing. > > The 3 classes are a design bug in -stable. Crossing classes is sometimes > right and 3 classes mainly make it harder and force triplication of code. Agreed. In current we basically have one large priority array. At the top (low priorities) are realtime kernel priorities including interrupt thread priorities. Below those are other top-half kernel priorities including the normal sleep priorities. Below that are real-time user priorities, followed by time sharing user priorities, and finally idle user priorities. Possibly real-time user priorities should move up into the real-time kernel range, and it should be noted that the idle priorites are for idle kernel threads, not just user threads (so sys/priority.h may need a bit of updating). This is a simpler model esp. when you consider a thread of one priority class blocking on a lock held by a thread of a "lower" priority class as you only have to update pri_level for priority propagation rather than comparing classes and having to manage that extra gunk. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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 Dec 21 9:51: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 11E2337B416; Fri, 21 Dec 2001 09:50:59 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id fBLHowu18046; Fri, 21 Dec 2001 09:50:58 -0800 (PST) (envelope-from rizzo) Date: Fri, 21 Dec 2001 09:50:58 -0800 From: Luigi Rizzo To: John Baldwin Cc: Bruce Evans , current@FreeBSD.org, Peter Wemm Subject: Re: vm_zeropage priority problems. Message-ID: <20011221095058.A17968@iguana.aciri.org> References: <20011222023741.P5064-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Don't know how interesting this can be, but i am writing (no plans to commit it, unless people find it interesting) some code to implement a weight-based instead of priority-based scheduler. The code is basically the WF2Q+ scheme which is already part of dummynet, adapted to processes. It is quite compact, and i think i can make it reasonably compatible with the old scheme, i.e. a sysctl var can be used to switch between one and the other with reasonably little overhead. This would help removing the ugly property that priority-based have, which is that one process can starve the rest of the system. cheers luigi On Fri, Dec 21, 2001 at 09:07:05AM -0800, John Baldwin wrote: ... > > It's whatever the thread set itself. There is no good way of setting > > this either (vm_pagezero() and poll_idle() hack it into > > td->td_ksegrp->kg_pri). Userland would use rtprio(2) instead. > > Unfortunately, this gives priorities in different units than the ones > > for tsleep(). > > pri_level is the current priority of the thread. The actual priority level is > going to move back into the thread and out of the KSE group so that tsleep and > priority propagation work properly, but pri_native, pri_user, and nice will > stay in the KSE group. The "normal" priorities for tsleep() are just a subset > of the priorities available to a thread. Thus, they are using the same unit, > but perhaps a wider range. > > >> In any case I wonder if this is a bug new in -current; -stable > >> uses three separate data structures for realtime, user and idle tasks > >> so even specifying the wrong priority in tsleep should not cause > >> crossing classes there. -current has only one array, hence the > >> chance of doing the wrong thing. > > > > The 3 classes are a design bug in -stable. Crossing classes is sometimes > > right and 3 classes mainly make it harder and force triplication of code. > > Agreed. In current we basically have one large priority array. At the top > (low priorities) are realtime kernel priorities including interrupt thread > priorities. Below those are other top-half kernel priorities including the > normal sleep priorities. Below that are real-time user priorities, followed by > time sharing user priorities, and finally idle user priorities. > > Possibly real-time user priorities should move up into the real-time kernel > range, and it should be noted that the idle priorites are for idle kernel > threads, not just user threads (so sys/priority.h may need a bit of updating). > > This is a simpler model esp. when you consider a thread of one priority class > blocking on a lock held by a thread of a "lower" priority class as you only > have to update pri_level for priority propagation rather than comparing classes > and having to manage that extra gunk. > > -- > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "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 Dec 21 11:50: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from go4.ext.ti.com (dlezb.ext.ti.com [192.91.75.132]) by hub.freebsd.org (Postfix) with ESMTP id C334D37B41E for ; Fri, 21 Dec 2001 11:49:45 -0800 (PST) Received: from dlep7.itg.ti.com ([157.170.134.103]) by go4.ext.ti.com (8.11.6/8.11.6) with ESMTP id fBLJni614668 for ; Fri, 21 Dec 2001 13:49:45 -0600 (CST) Received: from dlep7.itg.ti.com (localhost [127.0.0.1]) by dlep7.itg.ti.com (8.9.3/8.9.3) with ESMTP id NAA23855 for ; Fri, 21 Dec 2001 13:49:44 -0600 (CST) Received: from ffab.tide.ti.com (selenium.ffab.tide.ti.com [137.167.200.28]) by dlep7.itg.ti.com (8.9.3/8.9.3) with ESMTP id NAA23832 for ; Fri, 21 Dec 2001 13:49:43 -0600 (CST) Received: from ishtar.ffab.tide.ti.com (IDENT:KlZC97HlMqDk7ID5pDRNyum8gx7vkX9O@ishtar.ffab.tide.ti.com [137.167.222.71]) by ffab.tide.ti.com (8.12.1/8.12.1) with ESMTP id fBLJngO9020470 for ; Fri, 21 Dec 2001 20:49:42 +0100 (MET) Received: (from ntakpe@localhost) by ishtar.ffab.tide.ti.com (8.11.6/8.11.6) id fBLJngn28739 for current@freebsd.org; Fri, 21 Dec 2001 20:49:42 +0100 From: Jean Louis Ntakpe Message-Id: <200112211949.fBLJngn28739@ishtar.ffab.tide.ti.com> Subject: /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol "__stdoutp" To: current@freebsd.org Date: Fri, 21 Dec 2001 20:49:41 +0100 (CET) X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Some binaries, especially from the ports tree on my system just failed to start, bringing the message: /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol "__stdoutp" Could somebody give me a hint what I'm missing here. Since I couldn't start "cvsup", my system ist somewhat out of sync. (freebsd-current). regards, Jean Louis Ntakpe ntakpe@ntakpe.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 11:53:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id E4D9437B41A for ; Fri, 21 Dec 2001 11:53:28 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id fBLJrnb35781; Fri, 21 Dec 2001 11:53:49 -0800 (PST) Date: Fri, 21 Dec 2001 11:53:49 -0800 (PST) From: Doug White To: Jean Louis Ntakpe Cc: Subject: Re: /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol "__stdoutp" In-Reply-To: <200112211949.fBLJngn28739@ishtar.ffab.tide.ti.com> Message-ID: X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 21 Dec 2001, Jean Louis Ntakpe wrote: > Some binaries, especially from the ports tree on my > system just failed to start, bringing the message: > > /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol "__stdoutp" > > Could somebody give me a hint what I'm missing here. /usr/src/UPDATING is your friend. Hint: echo "COMPAT4X=yes" >> /etc/make.conf; make world Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Dec 21 12: 5:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 2874F37B405; Fri, 21 Dec 2001 12:05:14 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id fBLK4qq52572; Fri, 21 Dec 2001 22:04:52 +0200 (EET) (envelope-from ru) Date: Fri, 21 Dec 2001 22:04:52 +0200 From: Ruslan Ermilov To: Doug White , Warner Losh , Peter Wemm Cc: current@FreeBSD.org Subject: Re: /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol "__stdoutp" Message-ID: <20011221220452.E47284@sunbay.com> References: <200112211949.fBLJngn28739@ishtar.ffab.tide.ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Dec 21, 2001 at 11:53:49AM -0800, Doug White wrote: > On Fri, 21 Dec 2001, Jean Louis Ntakpe wrote: > > > Some binaries, especially from the ports tree on my > > system just failed to start, bringing the message: > > > > /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol "__stdoutp" > > > > Could somebody give me a hint what I'm missing here. > > /usr/src/UPDATING is your friend. > > Hint: echo "COMPAT4X=yes" >> /etc/make.conf; make world > Actually, there's not enough context in src/UPDATING to find these entries. Warner, could you please add "__stdoutp" to the 20010919 entry, and a hint to put COMPAT4X=true to /etc/make.conf to the 20010924 entry? Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 16:20:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 60F6E37B416 for ; Fri, 21 Dec 2001 16:20:08 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011222002008.SJHP6450.rwcrmhc52.attbi.com@InterJet.elischer.org> for ; Sat, 22 Dec 2001 00:20:08 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA59509 for ; Fri, 21 Dec 2001 16:15:07 -0800 (PST) Date: Fri, 21 Dec 2001 16:15:06 -0800 (PST) From: Julian Elischer To: current@freebsd.org Subject: KSE changes available Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The latest round of KSE changes are available from http://www.freebsd.org/~julian/thediff These changes represent a work in progress. Basically the state is: GENERIC compiles (I don't know yet if it runs but I doubt it.) The following changes have been made: The 'thread' structure is no longer a built-in part of the proc structure. There is an infrastructure to independently crfeate and reap threads. The infrastructure is used to create and destroy the 'usual' single thread associated with each process. It should eventually be used to create more threads per process.. The 'state' variable associated with the process has been raped and now each thread, and process and KSE has it's own state. This last part is the bit that is broken because a LOT of the kernel doesn't expect the state of a thread to be spread across several structures. For example: switch (p->p_stat) { case SRUN: ... case SSTOP: .. has to be completely rewritten because SRUN is a per-thread property and is accessed as: FOREACH_THREAD_IN_PROC(p, td) { switch(td->td_state) { case TDS_RUNNING: case TDS_RUNQ: case TDS_SLP: ... } ... } wheras STOP is still a per-process state. obviously any code that tries to assume the same scope for these tow states will break violently in the new code. I have replaced some of the logic where there seems to be a simple answer, but there are plenty of places where the answer is not clear. Such places include signal delivery, selection of process (thread?) to deliver a signal to, collection of scheduling statistics, handling FORK run by one of several threads, handling EXIT run by one of several threads, handling when the user types ^Z and suspends the process. If anyone is feeling adventurous they can stat with the code that is there and start fixing things :-) send me patches but let me know ahead of time what you will be doing so we don't duplicate, and so I can send you notes on where I'm going in that part.. I'll be working on the scheduler for the next few days I think. Note: if ((p->p_flag & P_KSES) == 0) a process should act exactly as it does now.. :-) REGARDS JULIAN (bloody capslock key) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 16:20:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from jhs.muc.de (jhs.muc.de [193.149.49.84]) by hub.freebsd.org (Postfix) with ESMTP id B5FB637B41A for ; Fri, 21 Dec 2001 16:20:15 -0800 (PST) Received: from park.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id fBLGATc85876; Fri, 21 Dec 2001 16:10:29 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200112211610.fBLGATc85876@jhs.muc.de> To: Matthew Dillon Cc: Joe Halpin , "current@FreeBSD.ORG" Subject: Re: spam In-Reply-To: Message from Matthew Dillon of "Thu, 20 Dec 2001 21:40:07 PST." <200112210540.fBL5e7584983@apollo.backplane.com> Date: Fri, 21 Dec 2001 17:10:29 +0100 From: Julian Stacey Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I can only hope that our illustrious congress has grown as tired of > spam as I have and will fix the law to simply ban it. > -Matt That would help, (most SPAM I receive even in Germany is from USA), but spammers would move offshore from USA & still target us, just as most German language spamming is now from countries outside Germany, so presumably German language spammers pay foreign intermediaries or subsidiaries to spam. Hostile counter attacks could supplement laws & filtering ... - I got a panic stricken international phone call from a UK spammer near where I used to live, after I mailed & threatened to report him to local police &/or launch net attacks on his facilities. - Anyone know of PD sourced tools & indexes that automate co-ordination of hostile counter attacks on identified spammers ? PS Maybe if we were to regularly automatically scramble all email addresses in our web searchable mail archives ? just inserting ._ErAsE_ThIs_. in every email address would protect us from easy harvesting by simple spammer robots. Julian J.Stacey Munich Unix (FreeBSD, Linux etc) Independent Consultant Reduce costs to secure jobs: Use free software: http://bim.bsn.com/~jhs/free/ Ihr Rauchen = mein allergischer Kopfschmerz ! Schnupftabak probieren ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 16:35: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta7.pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8]) by hub.freebsd.org (Postfix) with ESMTP id C9FB037B405 for ; Fri, 21 Dec 2001 16:35:02 -0800 (PST) Received: from pacbell.net ([64.163.12.132]) by mta7.pltn13.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GOP008B9YYEGN@mta7.pltn13.pbi.net> for freebsd-current@FreeBSD.org; Fri, 21 Dec 2001 16:35:02 -0800 (PST) Date: Fri, 21 Dec 2001 16:36:53 -0800 From: Tony Sterrett Subject: subscribe To: freebsd-current@FreeBSD.org Message-id: <3C23D5A5.A19105B9@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.10-4GB i686) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe -- We got a thousand points of light, For the homeless man We got a kinder gentler machine gun hand - Neil Young To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 18:27:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 21B1137B416 for ; Fri, 21 Dec 2001 18:27:15 -0800 (PST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2:206:5bff:fe05:7829]) by white.imgsrc.co.jp (Postfix) with ESMTP id 10D2D24D32 for ; Sat, 22 Dec 2001 11:27:14 +0900 (JST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [2001:218:422:2:230:48ff:fe41:161b]) by black.imgsrc.co.jp (Postfix) with ESMTP id DEF821E4812 for ; Sat, 22 Dec 2001 11:27:12 +0900 (JST) Date: Sat, 22 Dec 2001 11:27:11 +0900 Message-ID: <7md718f0qo.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: Forward: if_fxp.c typo? References: <86y9kzqjlr.wl@keiichi01.osaka.iij.ad.jp> User-Agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: multipart/mixed; boundary="Multipart_Sat_Dec_22_11:27:11_2001-2" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Multipart_Sat_Dec_22_11:27:11_2001-2 Content-Type: text/plain; charset=US-ASCII Hmm, -current has same problem. It should fix in -current... --Multipart_Sat_Dec_22_11:27:11_2001-2 Content-Type: multipart/digest; boundary="Multipart_Sat_Dec_22_11:27:11_2001-1" Content-Transfer-Encoding: 7bit --Multipart_Sat_Dec_22_11:27:11_2001-1 Content-Type: message/rfc822 From: Keiichi SHIMA / =?ISO-2022-JP?B?GyRCRWc3RDBsGyhC?= Subject: if_fxp.c typo? Date: Thu, 22 Nov 2001 08:47:09 +0000 (UTC) Sender: owner-freebsd-stable@FreeBSD.ORG Message-ID: <86y9kzqjlr.wl@keiichi01.osaka.iij.ad.jp> Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@freebsd.org X-Original-Date: Thu, 22 Nov 2001 17:45:52 +0900 User-Agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.2 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Precedence: bulk Hi all, fxp_stop() of the latest fxp driver do SOFTWARE_RESET when called. Shouldn't this be SELECTIVE_RESET? As I'm not familiar with fxp, would someone check and commit it to the repositry? The current code clears all the hardware mc filters already set, as a result, the box can't receive any multicast packets (this is a serious problem especially when using ipv6). --- Keiichi SHIMA IIJ Research Laboratory KAME Project --- orig/if_fxp.c Thu Nov 8 18:30:10 2001 +++ if_fxp.c Thu Nov 22 17:22:38 2001 @@ -1429,7 +1429,7 @@ * Issue software reset, which also unloads the microcode. */ sc->flags &= ~FXP_FLAG_UCODE; - CSR_WRITE_4(sc, FXP_CSR_PORT, FXP_PORT_SOFTWARE_RESET); + CSR_WRITE_4(sc, FXP_CSR_PORT, FXP_PORT_SELECTIVE_RESET); DELAY(50); /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message --Multipart_Sat_Dec_22_11:27:11_2001-1 Content-Type: message/rfc822 From: Jun Kuriyama Subject: Re: if_fxp.c typo? Date: Wed, 19 Dec 2001 23:32:50 +0000 (UTC) Sender: owner-freebsd-stable@FreeBSD.ORG Message-ID: <7mn10ebxbp.wl@waterblue.imgsrc.co.jp> References: <86y9kzqjlr.wl@keiichi01.osaka.iij.ad.jp> Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=ISO-2022-JP To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@freebsd.org X-Original-Date: Thu, 20 Dec 2001 08:32:26 +0900 In-Reply-To: <86y9kzqjlr.wl@keiichi01.osaka.iij.ad.jp> User-Agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Precedence: bulk I noticed this fixes my problem, but I don't know this patch is logically correct or not. I think we should commit this before 4.5-RELEASE if this is correct way. Can someone comment this? At Thu, 22 Nov 2001 08:47:09 +0000 (UTC), Keiichi SHIMA / 島慶一 wrote: > fxp_stop() of the latest fxp driver do SOFTWARE_RESET when called. > Shouldn't this be SELECTIVE_RESET? > > As I'm not familiar with fxp, would someone check and commit it to the > repositry? The current code clears all the hardware mc filters > already set, as a result, the box can't receive any multicast packets > (this is a serious problem especially when using ipv6). ... > --- orig/if_fxp.c Thu Nov 8 18:30:10 2001 > +++ if_fxp.c Thu Nov 22 17:22:38 2001 > @@ -1429,7 +1429,7 @@ > * Issue software reset, which also unloads the microcode. > */ > sc->flags &= ~FXP_FLAG_UCODE; > - CSR_WRITE_4(sc, FXP_CSR_PORT, FXP_PORT_SOFTWARE_RESET); > + CSR_WRITE_4(sc, FXP_CSR_PORT, FXP_PORT_SELECTIVE_RESET); > DELAY(50); > > /* -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message --Multipart_Sat_Dec_22_11:27:11_2001-1-- --Multipart_Sat_Dec_22_11:27:11_2001-2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 19:26:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 51F9D37B416 for ; Fri, 21 Dec 2001 19:26:46 -0800 (PST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2:206:5bff:fe05:7829]) by white.imgsrc.co.jp (Postfix) with ESMTP id 97D3D24D29 for ; Sat, 22 Dec 2001 12:26:45 +0900 (JST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [2001:218:422:2:230:48ff:fe41:161b]) by black.imgsrc.co.jp (Postfix) with ESMTP id 3CDB91E46E8 for ; Sat, 22 Dec 2001 12:26:44 +0900 (JST) Date: Sat, 22 Dec 2001 12:26:45 +0900 Message-ID: <7mn10cgcju.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: Yet another panic at pgfind() User-Agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is yesterday's -current. Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 00000000 fault virtual address = 0x114 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01b6c40 stack pointer = 0x10:0xf1947cd8 frame pointer = 0x10:0xf1947cd8 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 = 76144 (cron) kernel: type 12 trap, code=0 Stopped at pgfind+0x1c: cmpl %ecx,0x14(%eax) db> Context switches not allowed in the debugger. db> trace pgfind(12970) at pgfind+0x1c setsid(f10ab604,f1947d20,8058000,8051060,805514a) at setsid+0x3f syscall(2f,2f,2f,805514a,8051060) at syscall+0x257 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (147, FreeBSD ELF, setsid), eip = 0x280b5a43, esp =0xbfbff700, ebp = 0xbfbffcac --- -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 21: 8:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.acns.ab.ca (h24-64-56-135.cg.shawcable.net [24.64.56.135]) by hub.freebsd.org (Postfix) with ESMTP id B362C37B417 for ; Fri, 21 Dec 2001 21:08:44 -0800 (PST) Received: from colnta.acns.ab.ca (colnta.acns.ab.ca [192.168.1.2]) by mail.acns.ab.ca (8.11.6/8.11.3) with ESMTP id fBM58h611208 for ; Fri, 21 Dec 2001 22:08:43 -0700 (MST) (envelope-from davidc@colnta.acns.ab.ca) Received: (from davidc@localhost) by colnta.acns.ab.ca (8.11.6/8.11.3) id fBM58hH95549 for current@freebsd.org; Fri, 21 Dec 2001 22:08:43 -0700 (MST) (envelope-from davidc) Date: Fri, 21 Dec 2001 22:08:43 -0700 From: Chad David To: current@freebsd.org Subject: MULTI_DRIVER_MODULE Message-ID: <20011221220843.A85088@colnta.acns.ab.ca> 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anybody have an example of how to call MULTI_DRIVER_MODULE? It looks broken to me, but I could of course be wrong... Thanks. -- Chad David davidc@acns.ab.ca ACNS Inc. Calgary, Alberta Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 21:55:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 2181337B416 for ; Fri, 21 Dec 2001 21:55:43 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011222055537.ZZFI6450.rwcrmhc52.attbi.com@peter3.wemm.org> for ; Sat, 22 Dec 2001 05:55:37 +0000 Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fBM5tbs84332 for ; Fri, 21 Dec 2001 21:55:37 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 8FA7538CC; Fri, 21 Dec 2001 21:55:37 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Chad David Cc: current@FreeBSD.ORG Subject: Re: MULTI_DRIVER_MODULE In-Reply-To: <20011221220843.A85088@colnta.acns.ab.ca> Date: Fri, 21 Dec 2001 21:55:37 -0800 From: Peter Wemm Message-Id: <20011222055537.8FA7538CC@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chad David wrote: > Does anybody have an example of how to call MULTI_DRIVER_MODULE? It > looks broken to me, but I could of course be wrong... I would not recommend using it. Just use several DRIVER_MODULE declarations as required. In fact, I think I might remove it since nothing uses it yet. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 22: 8:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.acns.ab.ca (h24-64-56-135.cg.shawcable.net [24.64.56.135]) by hub.freebsd.org (Postfix) with ESMTP id 7F18637B405 for ; Fri, 21 Dec 2001 22:08:25 -0800 (PST) Received: from colnta.acns.ab.ca (colnta.acns.ab.ca [192.168.1.2]) by mail.acns.ab.ca (8.11.6/8.11.3) with ESMTP id fBM68O611313; Fri, 21 Dec 2001 23:08:25 -0700 (MST) (envelope-from davidc@colnta.acns.ab.ca) Received: (from davidc@localhost) by colnta.acns.ab.ca (8.11.6/8.11.3) id fBM68On04326; Fri, 21 Dec 2001 23:08:24 -0700 (MST) (envelope-from davidc) Date: Fri, 21 Dec 2001 23:08:24 -0700 From: Chad David To: Peter Wemm Cc: Chad David , current@FreeBSD.ORG Subject: Re: MULTI_DRIVER_MODULE Message-ID: <20011221230824.A4308@colnta.acns.ab.ca> References: <20011221220843.A85088@colnta.acns.ab.ca> <20011222055537.8FA7538CC@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011222055537.8FA7538CC@overcee.netplex.com.au>; from peter@wemm.org on Fri, Dec 21, 2001 at 09:55:37PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Dec 21, 2001 at 09:55:37PM -0800, Peter Wemm wrote: > Chad David wrote: > > Does anybody have an example of how to call MULTI_DRIVER_MODULE? It > > looks broken to me, but I could of course be wrong... > > I would not recommend using it. Just use several DRIVER_MODULE > declarations as required. In fact, I think I might remove it since nothing > uses it yet. Actually, my use of it is to verify the correctness of the man page, which I have been unable to do. If you are going to remove it then I will just remove the reference to it all together. I'll watch for the commit :). Thanks. -- Chad David davidc@acns.ab.ca ACNS Inc. Calgary, Alberta Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 23:48:32 2001 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 860CE37B405; Fri, 21 Dec 2001 23:48:27 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id SAA24907; Sat, 22 Dec 2001 18:48:21 +1100 Date: Sat, 22 Dec 2001 18:48:26 +1100 (EST) From: Bruce Evans X-X-Sender: To: Luigi Rizzo Cc: John Baldwin , , Peter Wemm Subject: Re: vm_zeropage priority problems. In-Reply-To: <20011221095058.A17968@iguana.aciri.org> Message-ID: <20011222183040.E7393-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 21 Dec 2001, Luigi Rizzo wrote: > Don't know how interesting this can be, but i am writing > (no plans to commit it, unless people find it interesting) > some code to implement a weight-based instead of priority-based > scheduler. The code is basically the WF2Q+ scheme which is > already part of dummynet, adapted to processes. > It is quite compact, and i think i can make it reasonably > compatible with the old scheme, i.e. a sysctl var can be > used to switch between one and the other with reasonably > little overhead. > > This would help removing the ugly property that priority-based > have, which is that one process can starve the rest of the system. Only broken priority-based schedulers have that property. One of my incomplete fixes uses weights: Index: kern_synch.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_synch.c,v retrieving revision 1.167 diff -u -2 -r1.167 kern_synch.c --- kern_synch.c 18 Dec 2001 00:27:17 -0000 1.167 +++ kern_synch.c 19 Dec 2001 16:01:26 -0000 @@ -936,18 +1058,18 @@ struct thread *td; { - struct kse *ke = td->td_kse; - struct ksegrp *kg = td->td_ksegrp; + struct ksegrp *kg; - if (td) { - ke->ke_cpticks++; - kg->kg_estcpu = ESTCPULIM(kg->kg_estcpu + 1); - if ((kg->kg_estcpu % INVERSE_ESTCPU_WEIGHT) == 0) { - resetpriority(td->td_ksegrp); - if (kg->kg_pri.pri_level >= PUSER) - kg->kg_pri.pri_level = kg->kg_pri.pri_user; - } - } else { + if (td == NULL) panic("schedclock"); - } + td->td_kse->ke_cpticks++; + kg = td->td_ksegrp; +#ifdef NEW_SCHED + kg->kg_estcpu += niceweights[kg->kg_nice - PRIO_MIN]; +#else + kg->kg_estcpu++; +#endif + resetpriority(kg); + if (kg->kg_pri.pri_level >= PUSER) + kg->kg_pri.pri_level = kg->kg_pri.pri_user; } Most of the changes here are to fix style bugs. In the NEW_SCHED case, the relative weights for each priority are determined by the niceweights[] table. kg->kg_estcpu is limited only by INT_MAX and priorities are assigned according to relative values of kg->kg_estcpu (code for this is not shown). The NEW_SCHED case has not been tried since before SMPng broke scheduling some more by compressing the priority ranges. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 21 23:54:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.acns.ab.ca (h24-64-56-135.cg.shawcable.net [24.64.56.135]) by hub.freebsd.org (Postfix) with ESMTP id BC21037B419 for ; Fri, 21 Dec 2001 23:54:17 -0800 (PST) Received: from colnta.acns.ab.ca (colnta.acns.ab.ca [192.168.1.2]) by mail.acns.ab.ca (8.11.6/8.11.3) with ESMTP id fBM7sG611437 for ; Sat, 22 Dec 2001 00:54:16 -0700 (MST) (envelope-from davidc@colnta.acns.ab.ca) Received: (from davidc@localhost) by colnta.acns.ab.ca (8.11.6/8.11.3) id fBM7sGD70813 for current@freebsd.org; Sat, 22 Dec 2001 00:54:16 -0700 (MST) (envelope-from davidc) Date: Sat, 22 Dec 2001 00:54:16 -0700 From: Chad David To: current@freebsd.org Subject: MEXTFREE Message-ID: <20011222005416.A61391@colnta.acns.ab.ca> 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG MEXTFREE results in a call to _mext_free() which is only defined within subr_mbuf.c, and is not static. Should the prototype be moved into sys/mbuf.h, or should MEXTFREE be moved into subr_mbuf.c, or is it ok like this? Thanks. -- Chad David davidc@acns.ab.ca ACNS Inc. Calgary, Alberta Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 0: 6:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 468A937B405; Sat, 22 Dec 2001 00:06:42 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id fBM86dq22709; Sat, 22 Dec 2001 00:06:39 -0800 (PST) (envelope-from rizzo) Date: Sat, 22 Dec 2001 00:06:39 -0800 From: Luigi Rizzo To: Bruce Evans Cc: John Baldwin , current@FreeBSD.org, Peter Wemm Subject: Re: vm_zeropage priority problems. Message-ID: <20011222000639.A22666@iguana.aciri.org> References: <20011221095058.A17968@iguana.aciri.org> <20011222183040.E7393-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011222183040.E7393-100000@gamplex.bde.org> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Dec 22, 2001 at 06:48:26PM +1100, Bruce Evans wrote: > On Fri, 21 Dec 2001, Luigi Rizzo wrote: ... > > This would help removing the ugly property that priority-based > > have, which is that one process can starve the rest of the system. > > Only broken priority-based schedulers have that property. One of > my incomplete fixes uses weights: which makes it weight based, doesn't it :) > Most of the changes here are to fix style bugs. In the NEW_SCHED case, > the relative weights for each priority are determined by the niceweights[] > table. kg->kg_estcpu is limited only by INT_MAX and priorities are > assigned according to relative values of kg->kg_estcpu (code for this is > not shown). i guess the latter is the hard part... what kind of complexity does it have ? The nice feature of the scheduling code used in dummynet/Wf2Q+ is that it has O(log N) complexity where N is the number of active flows (processes in this case) and the basic scheduling operation is just one or two heap insert/delete, so it's really fast. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 0:10: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by hub.freebsd.org (Postfix) with ESMTP id D8FBA37B405; Sat, 22 Dec 2001 00:09:57 -0800 (PST) Received: (from jake@localhost) by k6.locore.ca (8.11.6/8.11.6) id fBM8DnS72767; Sat, 22 Dec 2001 03:13:49 -0500 (EST) (envelope-from jake) Date: Sat, 22 Dec 2001 03:13:49 -0500 From: Jake Burkholder To: Bruce Evans Cc: Luigi Rizzo , John Baldwin , current@FreeBSD.ORG, Peter Wemm Subject: Re: vm_zeropage priority problems. Message-ID: <20011222031349.B62219@locore.ca> References: <20011221095058.A17968@iguana.aciri.org> <20011222183040.E7393-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011222183040.E7393-100000@gamplex.bde.org>; from bde@zeta.org.au on Sat, Dec 22, 2001 at 06:48:26PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Apparently, On Sat, Dec 22, 2001 at 06:48:26PM +1100, Bruce Evans said words to the effect of; > On Fri, 21 Dec 2001, Luigi Rizzo wrote: > > > Don't know how interesting this can be, but i am writing > > (no plans to commit it, unless people find it interesting) > > some code to implement a weight-based instead of priority-based > > scheduler. The code is basically the WF2Q+ scheme which is > > already part of dummynet, adapted to processes. > > It is quite compact, and i think i can make it reasonably > > compatible with the old scheme, i.e. a sysctl var can be > > used to switch between one and the other with reasonably > > little overhead. > > > > This would help removing the ugly property that priority-based > > have, which is that one process can starve the rest of the system. > > Only broken priority-based schedulers have that property. One of > my incomplete fixes uses weights: > > Index: kern_synch.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/kern_synch.c,v > retrieving revision 1.167 > diff -u -2 -r1.167 kern_synch.c > --- kern_synch.c 18 Dec 2001 00:27:17 -0000 1.167 > +++ kern_synch.c 19 Dec 2001 16:01:26 -0000 > @@ -936,18 +1058,18 @@ > struct thread *td; > { > - struct kse *ke = td->td_kse; > - struct ksegrp *kg = td->td_ksegrp; > + struct ksegrp *kg; > > - if (td) { > - ke->ke_cpticks++; > - kg->kg_estcpu = ESTCPULIM(kg->kg_estcpu + 1); > - if ((kg->kg_estcpu % INVERSE_ESTCPU_WEIGHT) == 0) { > - resetpriority(td->td_ksegrp); > - if (kg->kg_pri.pri_level >= PUSER) > - kg->kg_pri.pri_level = kg->kg_pri.pri_user; > - } > - } else { > + if (td == NULL) > panic("schedclock"); > - } > + td->td_kse->ke_cpticks++; > + kg = td->td_ksegrp; > +#ifdef NEW_SCHED > + kg->kg_estcpu += niceweights[kg->kg_nice - PRIO_MIN]; > +#else > + kg->kg_estcpu++; > +#endif > + resetpriority(kg); > + if (kg->kg_pri.pri_level >= PUSER) > + kg->kg_pri.pri_level = kg->kg_pri.pri_user; > } I'm curious why you removed the ESTCPULIM and INVERSE_ESTCPU_WEIGHT calculations even in the OLD_SCHED case. Do these turn out to have no effect in general? > > Most of the changes here are to fix style bugs. In the NEW_SCHED case, > the relative weights for each priority are determined by the niceweights[] > table. kg->kg_estcpu is limited only by INT_MAX and priorities are > assigned according to relative values of kg->kg_estcpu (code for this is > not shown). The NEW_SCHED case has not been tried since before SMPng > broke scheduling some more by compressing the priority ranges. It is relatively easy to uncompress the priority ranges if that is desirable. What range is best? Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 0:13:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (0x3ef31288.albnxx2.adsl.tele.dk [62.243.18.136]) by hub.freebsd.org (Postfix) with ESMTP id B6C6637B417 for ; Sat, 22 Dec 2001 00:13:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.6/8.11.6) with ESMTP id fBM8ETd42171; Sat, 22 Dec 2001 09:14:29 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sat, 22 Dec 2001 09:14:29 +0100 (CET) From: Leif Neland To: Julian Stacey Cc: Matthew Dillon , Joe Halpin , "current@FreeBSD.ORG" Subject: Re: spam In-Reply-To: <200112211610.fBLGATc85876@jhs.muc.de> Message-ID: <20011222090542.E95956-100000@arnold.neland.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 21 Dec 2001, Julian Stacey wrote: > > I can only hope that our illustrious congress has grown as tired of > > spam as I have and will fix the law to simply ban it. > > -Matt > > That would help, (most SPAM I receive even in Germany is from USA), but > spammers would move offshore from USA & still target us, just as most German > language spamming is now from countries outside Germany, so presumably German > language spammers pay foreign intermediaries or subsidiaries to spam. > > Hostile counter attacks could supplement laws & filtering ... > - I got a panic stricken international phone call from a UK > spammer near where I used to live, after I mailed & threatened > to report him to local police &/or launch net attacks on his facilities. > - Anyone know of PD sourced tools & indexes that automate co-ordination > of hostile counter attacks on identified spammers ? > Don't counterattack, you have to be 250% sure the server is the spammers own, and his alone. What if the spammer either is just a client, or has broken into the server? It is not legal to break your neigbours house, even if it is to shut down his 500W stereo. I believe somebody got into serious trouble by launching a worm, which closed holes other worms could use. > PS Maybe if we were to regularly automatically scramble all email addresses > in our web searchable mail archives ? just inserting ._ErAsE_ThIs_. in every > email address would protect us from easy harvesting by simple spammer robots. Yeah, that would help for 3 months or so. Then the harvesters will be adapted. The way to go, I think is procmail based content filters, and dnsbl, like spamcop. I report many spams to spamcop. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 0:26:14 2001 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 82C8837B417; Sat, 22 Dec 2001 00:26:11 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA26681; Sat, 22 Dec 2001 19:26:07 +1100 Date: Sat, 22 Dec 2001 19:26:12 +1100 (EST) From: Bruce Evans X-X-Sender: To: John Baldwin Cc: , Peter Wemm , Luigi Rizzo Subject: Re: vm_zeropage priority problems. In-Reply-To: Message-ID: <20011222191517.M7478-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 21 Dec 2001, John Baldwin wrote: > On 21-Dec-01 Bruce Evans wrote: > > On Fri, 21 Dec 2001, Luigi Rizzo wrote: > >> the original priority should be somewhere and accessible, > >> either directly or through some function. Otherwise how > >> do we know what to pass to tsleep() ? > > > > It's whatever the thread set itself. There is no good way of setting > > this either (vm_pagezero() and poll_idle() hack it into > > td->td_ksegrp->kg_pri). Userland would use rtprio(2) instead. > > Unfortunately, this gives priorities in different units than the ones > > for tsleep(). > > pri_level is the current priority of the thread. The actual priority level is > going to move back into the thread and out of the KSE group so that tsleep and > priority propagation work properly, but pri_native, pri_user, and nice will > stay in the KSE group. The "normal" priorities for tsleep() are just a subset This will make encapsulating priority stuff on a struct more obviously wrong. > of the priorities available to a thread. Thus, they are using the same unit, > but perhaps a wider range. They are offset by PRI_MIN_IDLE too, due to vestiges of the rtprio() misimplementation. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 2: 1:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from technokratis.com (modemcable099.144-201-24.mtl.mc.videotron.ca [24.201.144.99]) by hub.freebsd.org (Postfix) with ESMTP id 453EE37B405 for ; Sat, 22 Dec 2001 02:01:25 -0800 (PST) Received: (from bmilekic@localhost) by technokratis.com (8.11.4/8.11.3) id fBMA3Lh77224; Sat, 22 Dec 2001 05:03:21 -0500 (EST) (envelope-from bmilekic) Date: Sat, 22 Dec 2001 05:03:20 -0500 From: Bosko Milekic To: Chad David Cc: current@FreeBSD.ORG Subject: Re: MEXTFREE Message-ID: <20011222050320.A77143@technokratis.com> References: <20011222005416.A61391@colnta.acns.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011222005416.A61391@colnta.acns.ab.ca>; from davidc@acns.ab.ca on Sat, Dec 22, 2001 at 12:54:16AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Dec 22, 2001 at 12:54:16AM -0700, Chad David wrote: > MEXTFREE results in a call to _mext_free() which is only defined within > subr_mbuf.c, and is not static. Should the prototype be moved into > sys/mbuf.h, or should MEXTFREE be moved into subr_mbuf.c, or is it ok > like this? It should stay like this. The easy (macro) case deals with only the reference count issue. We only call the function if we really have to free the object (i.e. ref count is dropped to zero). > Thanks. > > -- > Chad David davidc@acns.ab.ca > ACNS Inc. Calgary, Alberta Canada -- Bosko Milekic bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 2:25:25 2001 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 0012B37B405; Sat, 22 Dec 2001 02:25:21 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA32210; Sat, 22 Dec 2001 21:25:11 +1100 Date: Sat, 22 Dec 2001 21:25:16 +1100 (EST) From: Bruce Evans X-X-Sender: To: Luigi Rizzo Cc: John Baldwin , , Peter Wemm Subject: Re: vm_zeropage priority problems. In-Reply-To: <20011222000639.A22666@iguana.aciri.org> Message-ID: <20011222211250.E7836-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 22 Dec 2001, Luigi Rizzo wrote: > On Sat, Dec 22, 2001 at 06:48:26PM +1100, Bruce Evans wrote: > > Most of the changes here are to fix style bugs. In the NEW_SCHED case, > > the relative weights for each priority are determined by the niceweights[] > > table. kg->kg_estcpu is limited only by INT_MAX and priorities are > > assigned according to relative values of kg->kg_estcpu (code for this is > > not shown). > > i guess the latter is the hard part... what kind of complexity does > it have ? Not too bad. I use an extra loop in schedcpu() to find the current maximum of all kg->kg_estcpu, and convert the divison by this maximum (for scaling individual kg->kg_estcpu's) to a multiplication and a shift. This can probably be done better in loadav(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 2:36: 3 2001 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 5606C37B41B for ; Sat, 22 Dec 2001 02:36:00 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA32754; Sat, 22 Dec 2001 21:35:45 +1100 Date: Sat, 22 Dec 2001 21:35:50 +1100 (EST) From: Bruce Evans X-X-Sender: To: Bosko Milekic Cc: Chad David , Subject: Re: MEXTFREE In-Reply-To: <20011222050320.A77143@technokratis.com> Message-ID: <20011222213422.P7862-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 22 Dec 2001, Bosko Milekic wrote: > On Sat, Dec 22, 2001 at 12:54:16AM -0700, Chad David wrote: > > MEXTFREE results in a call to _mext_free() which is only defined within > > subr_mbuf.c, and is not static. Should the prototype be moved into > > sys/mbuf.h, or should MEXTFREE be moved into subr_mbuf.c, or is it ok > > like this? > > It should stay like this. The easy (macro) case deals with only the > reference count issue. We only call the function if we really have to > free the object (i.e. ref count is dropped to zero). But clients that use MEXTFREE (if any) see the function call, so they need a prototype in scope. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 4:15:51 2001 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 F0D2437B419; Sat, 22 Dec 2001 04:15:40 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id XAA04636; Sat, 22 Dec 2001 23:13:58 +1100 Date: Sat, 22 Dec 2001 23:14:04 +1100 (EST) From: Bruce Evans X-X-Sender: To: Jake Burkholder Cc: Luigi Rizzo , John Baldwin , , Peter Wemm Subject: Re: vm_zeropage priority problems. In-Reply-To: <20011222031349.B62219@locore.ca> Message-ID: <20011222213623.J7890-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 22 Dec 2001, Jake Burkholder wrote: > Apparently, On Sat, Dec 22, 2001 at 06:48:26PM +1100, > Bruce Evans said words to the effect of; > > Index: kern_synch.c > > =================================================================== > > RCS file: /home/ncvs/src/sys/kern/kern_synch.c,v > > retrieving revision 1.167 > > diff -u -2 -r1.167 kern_synch.c > > --- kern_synch.c 18 Dec 2001 00:27:17 -0000 1.167 > > +++ kern_synch.c 19 Dec 2001 16:01:26 -0000 > > @@ -936,18 +1058,18 @@ > > struct thread *td; > > { > > - struct kse *ke = td->td_kse; > > - struct ksegrp *kg = td->td_ksegrp; > > + struct ksegrp *kg; > > > > - if (td) { > > - ke->ke_cpticks++; > > - kg->kg_estcpu = ESTCPULIM(kg->kg_estcpu + 1); > > - if ((kg->kg_estcpu % INVERSE_ESTCPU_WEIGHT) == 0) { > > - resetpriority(td->td_ksegrp); > > - if (kg->kg_pri.pri_level >= PUSER) > > - kg->kg_pri.pri_level = kg->kg_pri.pri_user; > > - } > > - } else { > > + if (td == NULL) > > panic("schedclock"); > > - } > > + td->td_kse->ke_cpticks++; > > + kg = td->td_ksegrp; > > +#ifdef NEW_SCHED > > + kg->kg_estcpu += niceweights[kg->kg_nice - PRIO_MIN]; > > +#else > > + kg->kg_estcpu++; > > +#endif > > + resetpriority(kg); > > + if (kg->kg_pri.pri_level >= PUSER) > > + kg->kg_pri.pri_level = kg->kg_pri.pri_user; > > } > > I'm curious why you removed the ESTCPULIM and INVERSE_ESTCPU_WEIGHT > calculations even in the OLD_SCHED case. Do these turn out to have > no effect in general? ESTCPULIM basically breaks scheduling if it is are hit (clipping to it prevents accumulation of hog points that would cause cpu hogs to be run less). This is a problem in practice. I use dynamic limits even in the !NEW_SCHED case. I forgot that I did this or I would have included more context to show it (see below). kg->kg_estcpu is allowed to grow without explicit limit and scaled to fit in the priority range. This requires fixing sorcerer's-apprentice growth of kg_estcpu in fork() and exit(). kg_estcpu has natural limits but they are quite large (a constant multiple of the load average). INVERSE_ESTCPU_WEIGHT is not used because it goes with static scaling, and "% INVERSE_ESTCPU_WEIGHT" optimization (which depends on the internals of resetpriority()) is not so easy to do. Here are the corresponding changes for resetpriority(): %%% Index: kern_synch.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_synch.c,v retrieving revision 1.167 diff -u -2 -r1.167 kern_synch.c --- kern_synch.c 18 Dec 2001 00:27:17 -0000 1.167 +++ kern_synch.c 22 Dec 2001 07:34:15 -0000 @@ -844,15 +949,32 @@ register struct ksegrp *kg; { + u_int estcpu; register unsigned int newpriority; mtx_lock_spin(&sched_lock); if (kg->kg_pri.pri_class == PRI_TIMESHARE) { - newpriority = PUSER + kg->kg_estcpu / INVERSE_ESTCPU_WEIGHT + + estcpu = kg->kg_estcpu; + if (estcpu > estcpumax) + estcpu = estcpumax; +#ifdef NEW_SCHED + newpriority = PUSER + + (((u_int64_t)estcpu * estcpumul) >> ESTCPU_SHIFT); +#else + newpriority = PUSER + + (((u_int64_t)estcpu * estcpumul) >> ESTCPU_SHIFT) + NICE_WEIGHT * (kg->kg_nice - PRIO_MIN); - newpriority = min(max(newpriority, PRI_MIN_TIMESHARE), - PRI_MAX_TIMESHARE); +#endif + if (newpriority < PUSER) + newpriority = PUSER; + if (newpriority > PRI_MAX_TIMESHARE) { + Debugger("newpriority botch"); + newpriority = PRI_MAX_TIMESHARE; + } kg->kg_pri.pri_user = newpriority; - } - maybe_resched(kg); + maybe_resched(kg, newpriority); + } else + /* XXX doing anything here is dubious. */ + /* XXX was: need_resched(). */ + maybe_resched(kg, kg->kg_pri.pri_user); mtx_unlock_spin(&sched_lock); } %%% > > Most of the changes here are to fix style bugs. In the NEW_SCHED case, > > the relative weights for each priority are determined by the niceweights[] > > table. kg->kg_estcpu is limited only by INT_MAX and priorities are > > assigned according to relative values of kg->kg_estcpu (code for this is > > not shown). The NEW_SCHED case has not been tried since before SMPng > > broke scheduling some more by compressing the priority ranges. > > It is relatively easy to uncompress the priority ranges if that is > desirable. What range is best? The original algorithm works best with something close to the old range of 50-127 (PUSER = 50, MAXPRI = 127) for positively niced processes alone. This gives unniced processes a priority range of 50-127 and permits nice -20'ed processes to have a much larger (numerically) base priority than unniced ones while still allowing room for their priority to grow (range 90-127). Negatively niced processes were handled dubiously at best (they ran into the kernel priorities). Brian Feldman reduced the priority range for unniced processes to 68-127 and you reduced it some more to 180-223. The main problem with the reduced rangesis that the algorithm gives approximately an exponential dependency of the cpu cycles allocated to a process on the process's niceness. The base for the exponential is invisible and hard to change, so decreasing the range by a factor of 78/44 significantly reduces the effects of niceness. I think my nicewights[] algorithm can handle this. It supports almost any dependency of cycles on niceness. However, I don't know how it can be made to work right for the entire priority range. An exponential dependency would grow too fast for the range 0-255 if it grows fast enough for the user range 180-233. I used the following program to generate (old) niceweights[] tables. Defining EXP gives an exponential table with niceness 0 haveing 32 times as much priority as niceness 20. The default approximates the old -current behaviour (which isn't actually exponential). %%% #include main() { int i; for (i = 0; i <= 40; i++) { if (i % 8 == 0) printf("\t"); #ifdef EXP printf("%d,", (int)floor(2 * 3 * pow(2.0, i / 4.0) + 0.5)); #else if (i == 40) printf("65536\n"); else printf("%d,", 2 * 2 * 2 * 3 * 3 * 5 * 7 / (40 - i)); #endif if (i % 8 == 7) printf("\n"); else printf(" "); } } %%% Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 7: 2:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from cheer.mahoroba.org (flets-c0109.kamome.or.jp [211.8.151.237]) by hub.freebsd.org (Postfix) with ESMTP id 498D337B405; Sat, 22 Dec 2001 07:02:21 -0800 (PST) Received: from fiva.mahoroba.org (ume@piano-wi.mahoroba.org [IPv6:2001:200:301:0:260:1dff:fe22:dd55]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.1/8.12.1) with ESMTP/inet6 id fBMF2BBF054263; Sun, 23 Dec 2001 00:02:12 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sun, 23 Dec 2001 00:02:11 +0900 Message-ID: From: Hajimu UMEMOTO To: John Hay Cc: mheffner@vt.edu (Mike Heffner), mikeh@FreeBSD.ORG (Mike Heffner), cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, FreeBSD-current@FreeBSD.ORG (FreeBSD-current) Subject: Re: cvs commit: src/usr.bin/ftp Makefile cmds.c cmdtab.c complet In-Reply-To: <200112140643.fBE6hod26370@zibbi.icomtek.csir.co.za> References: <200112140643.fBE6hod26370@zibbi.icomtek.csir.co.za> User-Agent: xcite1.38> Wanderlust/2.9.0 (Unchained Melody) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) X-Operating-System: FreeBSD 5.0-CURRENT MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, >>>>> On Fri, 14 Dec 2001 08:43:49 +0200 (SAT) >>>>> John Hay said: > On 13-Dec-2001 Mike Heffner wrote: > | mikeh 2001/12/13 15:46:45 PST jhay> ... > | Log: > | Connect lukemftp to the build as the default ftp client. Lukemftp > | supports most of the previous features of FreeBSD ftp, but has been > | better maintained and includes new features. > > Short summary of differences: > jhay> ... > Differences/Losses: > > *) FTP_PASSIVE_MODE vs. FTP_MODE > *) -4/-6 for forcing IPV4/IPV6 jhay> Any chance of getting -4/-6 or something like it, back? It is very useful jhay> here in our environment that have a lot of dual-stack machines. I think it is still useful in the environment where IPv6 link is relatively slow than IPv4 link. How about this patch? Index: contrib/lukemftp/src/fetch.c =================================================================== RCS file: /home/ncvs/src/contrib/lukemftp/src/fetch.c,v retrieving revision 1.1.1.1 diff -u -u -r1.1.1.1 fetch.c --- contrib/lukemftp/src/fetch.c 19 Jul 2001 16:26:13 -0000 1.1.1.1 +++ contrib/lukemftp/src/fetch.c 22 Dec 2001 14:47:28 -0000 @@ -617,7 +617,7 @@ memset(&hints, 0, sizeof(hints)); hints.ai_flags = 0; - hints.ai_family = AF_UNSPEC; + hints.ai_family = family; hints.ai_socktype = SOCK_STREAM; hints.ai_protocol = 0; error = getaddrinfo(host, NULL, &hints, &res0); Index: contrib/lukemftp/src/ftp.1 =================================================================== RCS file: /home/ncvs/src/contrib/lukemftp/src/ftp.1,v retrieving revision 1.1.1.1 diff -u -u -r1.1.1.1 ftp.1 --- contrib/lukemftp/src/ftp.1 19 Jul 2001 16:26:13 -0000 1.1.1.1 +++ contrib/lukemftp/src/ftp.1 22 Dec 2001 14:47:29 -0000 @@ -77,7 +77,7 @@ Internet file transfer program .Sh SYNOPSIS .Nm "" -.Op Fl AadefginpRtvV +.Op Fl 46AadefginpRtvV .Bk -words .Op Fl o Ar output .Ek @@ -146,6 +146,14 @@ Options may be specified at the command line, or to the command interpreter. .Bl -tag -width "port " +.It Fl 4 +Forces +.Nm +to use IPv4 addresses only. +.It Fl 6 +Forces +.Nm +to use IPv6 addresses only. .It Fl A Force active mode ftp. By default, Index: contrib/lukemftp/src/ftp.c =================================================================== RCS file: /home/ncvs/src/contrib/lukemftp/src/ftp.c,v retrieving revision 1.1.1.1 diff -u -u -r1.1.1.1 ftp.c --- contrib/lukemftp/src/ftp.c 19 Jul 2001 16:26:14 -0000 1.1.1.1 +++ contrib/lukemftp/src/ftp.c 22 Dec 2001 14:47:31 -0000 @@ -149,7 +149,7 @@ memset(&hints, 0, sizeof(hints)); portnum = parseport(port, FTP_PORT); hints.ai_flags = AI_CANONNAME; - hints.ai_family = AF_UNSPEC; + hints.ai_family = family; hints.ai_socktype = SOCK_STREAM; hints.ai_protocol = 0; error = getaddrinfo(host, NULL, &hints, &res0); Index: contrib/lukemftp/src/ftp_var.h =================================================================== RCS file: /home/ncvs/src/contrib/lukemftp/src/ftp_var.h,v retrieving revision 1.1.1.1 diff -u -u -r1.1.1.1 ftp_var.h --- contrib/lukemftp/src/ftp_var.h 19 Jul 2001 16:26:14 -0000 1.1.1.1 +++ contrib/lukemftp/src/ftp_var.h 22 Dec 2001 14:47:31 -0000 @@ -279,6 +279,8 @@ GLOBAL char remotepwd[MAXPATHLEN]; /* remote dir */ GLOBAL char *username; /* name of user logged in as. (dynamic) */ +GLOBAL sa_family_t family; /* address family to use for connections */ + GLOBAL char *ftpport; /* port number to use for FTP connections */ GLOBAL char *httpport; /* port number to use for HTTP connections */ GLOBAL char *gateport; /* port number to use for gateftp connections */ Index: contrib/lukemftp/src/main.c =================================================================== RCS file: /home/ncvs/src/contrib/lukemftp/src/main.c,v retrieving revision 1.1.1.1 diff -u -u -r1.1.1.1 main.c --- contrib/lukemftp/src/main.c 19 Jul 2001 16:26:14 -0000 1.1.1.1 +++ contrib/lukemftp/src/main.c 22 Dec 2001 14:47:32 -0000 @@ -171,6 +171,7 @@ upload_path = NULL; isupload = 0; reply_callback = NULL; + family = AF_UNSPEC; /* * Get the default socket buffer sizes if we don't already have them. @@ -255,8 +256,16 @@ } } - while ((ch = getopt(argc, argv, "Aadefgino:pP:r:RtT:u:vV")) != -1) { + while ((ch = getopt(argc, argv, "46Aadefgino:pP:r:RtT:u:vV")) != -1) { switch (ch) { + case '4': + family = AF_INET; + break; + + case '6': + family = AF_INET6; + break; + case 'A': activefallback = 0; passivemode = 0; -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 8:30:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from meta.lo-res.org (meta.lo-res.org [195.58.189.92]) by hub.freebsd.org (Postfix) with ESMTP id 9A3C337B419 for ; Sat, 22 Dec 2001 08:30:50 -0800 (PST) Received: from localhost (aaron@localhost) by meta.lo-res.org (8.11.6/8.11.6) with ESMTP id fBMGUa262335; Sat, 22 Dec 2001 17:30:36 +0100 (CET) (envelope-from aaron@meta.lo-res.org) Date: Sat, 22 Dec 2001 17:30:35 +0100 (CET) From: aaron To: Matthew Dillon Cc: Joe Halpin , "current@FreeBSD.ORG" Subject: Re: spam In-Reply-To: <200112210540.fBL5e7584983@apollo.backplane.com> Message-ID: <20011222171949.K62162-100000@meta.lo-res.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 20 Dec 2001, Matthew Dillon wrote: > > :I'm starting to get spam since I joined this list, and the spam is > :coming from freebsd.org. If I'm reading the headers right, it's coming > :in through a freebsd.org mail server. > > Ha. In the last two weeks the amount of personal spam I receive has > gone up exponentially. I'm getting around 60 a day now. I'm not > surprised that the list is seeing a big increase. > > I can only hope that our illustrious congress has grown as tired of > spam as I have and will fix the law to simply ban it. I doubt it: a) the have secretaries (if at all!) to read the mail b) spam = money the solution must lie in something with authentication. E.g. everyone subscribing to this list has to submit his/her pub key and every message should be signed. I image this as something like a quasi-moderated list. If you post something to the list it will first be read by a moderator. If the moderator agrees on the fact that this is not spam, it _must_ be accepted to the list and thereby the sig / pub key is inserted into a DB. Future mails arriving from the just included submitter will be sent to the list without moderation. Thus the moderator is a a one time check for submitters. only people interested in the subject will pass. spammers wont have the time to get interested in -current internals. (usually). After passing once you are free to post as before. I know many people wont like the idea presented above. But it is the only reasonable check I can think of that would exclude spam while at the same time permitting reasonable open access. Of course I am open to better ideas. greetings, aaron (Vienna) --- COSHER = Completely Open Source, Headers, Engineering, and Research To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 9:32:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 3F16E37B405 for ; Sat, 22 Dec 2001 09:32:54 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.4/8.11.4) id fBMHWrw59883 for freebsd-current@freebsd.org; Sat, 22 Dec 2001 09:32:53 -0800 (PST) (envelope-from sgk) Date: Sat, 22 Dec 2001 09:32:53 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Subject: msgdef breaks world Message-ID: <20011222093218.A59848@troutmask.apl.washington.edu> 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG install -C -c -m 644 -o root -g wheel tr_TR.ISO8859-9.out /usr/share/locale/tr_ TR.ISO8859-9/LC_MESSAGES/SYS_LC_MESSAGES install -C -c -m 644 -o root -g wheel uk_UA.ISO8859-5.out /usr/share/locale/uk_ UA.ISO8859-5/LC_MESSAGES/SYS_LC_MESSAGES install: /usr/share/locale/uk_UA.ISO8859-5/LC_MESSAGES/SYS_LC_MESSAGES: No such file or directory *** Error code 71 Stop in /usr/src/share/msgdef. *** Error code 1 Stop in /usr/src/share. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 9:47:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id CE0A237B416 for ; Sat, 22 Dec 2001 09:47:37 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.4/8.11.4) id fBMHlbm60026 for freebsd-current@FreeBSD.ORG; Sat, 22 Dec 2001 09:47:37 -0800 (PST) (envelope-from sgk) Date: Sat, 22 Dec 2001 09:47:37 -0800 From: Steve Kargl To: freebsd-current@FreeBSD.ORG Subject: Re: msgdef breaks world Message-ID: <20011222094737.A59973@troutmask.apl.washington.edu> References: <20011222093218.A59848@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011222093218.A59848@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Sat, Dec 22, 2001 at 09:32:53AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Dec 22, 2001 at 09:32:53AM -0800, Steve Kargl wrote: > UA.ISO8859-5/LC_MESSAGES/SYS_LC_MESSAGES > install: /usr/share/locale/uk_UA.ISO8859-5/LC_MESSAGES/SYS_LC_MESSAGES: \ > No such > file or directory > *** Error code 71 > > Stop in /usr/src/share/msgdef. > *** Error code 1 > > Stop in /usr/src/share. > Nevermind. This appears to be fixed. Now, for the problem: ===> share/termcap install -C -c -o root -g wheel -m 444 /usr/src/share/termcap/map3270 /usr/share/misc/map3270 TERM=dumb ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder ex: not found *** Error code 127 Stop in /usr/src/share/termcap. *** Error code 1 -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 11:40:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 5BB0F37B41B for ; Sat, 22 Dec 2001 11:40:07 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011222194006.LHNX6450.rwcrmhc52.attbi.com@InterJet.elischer.org>; Sat, 22 Dec 2001 19:40:06 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA63636; Sat, 22 Dec 2001 11:34:25 -0800 (PST) Date: Sat, 22 Dec 2001 11:34:24 -0800 (PST) From: Julian Elischer To: aaron Cc: Matthew Dillon , Joe Halpin , "current@FreeBSD.ORG" Subject: Re: spam In-Reply-To: <20011222171949.K62162-100000@meta.lo-res.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I would suggest that we use a 'modified' subscription method, where simply being mentionned in the list is enough to subscribe.. Now, before you laugh.. there's a twist.. any address found in the archives is automatically subscribed and that includes in the text.. also any mail not subscribed it treated as if it were a moderated list. i.e. sent for OK to someone. once that peson OKs it the person can send mail. I'd suggest that there be a mailing list of 'moderators' maybe 20 or so people to take the load (I'm talking about -current and -hackers here) the people just 'forward the mail to -current or -hackers if they think it's ok, and delete it if it's spam or if they already saw it go through.. The act of forwarding the mail will subscribe the sender. On Sat, 22 Dec 2001, aaron wrote: > On Thu, 20 Dec 2001, Matthew Dillon wrote: > > > > > :I'm starting to get spam since I joined this list, and the spam is > > :coming from freebsd.org. If I'm reading the headers right, it's coming > > :in through a freebsd.org mail server. > > > > Ha. In the last two weeks the amount of personal spam I receive has > > gone up exponentially. I'm getting around 60 a day now. I'm not > > surprised that the list is seeing a big increase. > > > > I can only hope that our illustrious congress has grown as tired of > > spam as I have and will fix the law to simply ban it. > > I doubt it: > a) the have secretaries (if at all!) to read the mail > b) spam = money > > the solution must lie in something with authentication. E.g. everyone > subscribing to this list has to submit his/her pub key and every message > should be signed. > I image this as something like a quasi-moderated list. If you post > something to the list it will first be read by a moderator. If the > moderator agrees on the fact that this is not spam, it _must_ be accepted > to the list and thereby the sig / pub key is inserted into a DB. Future mails > arriving from the just included submitter will be sent to the list without > moderation. > > Thus the moderator is a a one time check for submitters. only people > interested in the subject will pass. spammers wont have the time to get > interested in -current internals. (usually). After passing once you are > free to post as before. > > I know many people wont like the idea presented above. But it is the only > reasonable check I can think of that would exclude spam while at the same > time permitting reasonable open access. > Of course I am open to better ideas. > > greetings, > aaron (Vienna) > > --- > COSHER = Completely Open Source, Headers, Engineering, and Research > > > > 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 Sat Dec 22 14:23:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from meta.lo-res.org (meta.lo-res.org [195.58.189.92]) by hub.freebsd.org (Postfix) with ESMTP id 7377537B416 for ; Sat, 22 Dec 2001 14:23:37 -0800 (PST) Received: from localhost (aaron@localhost) by meta.lo-res.org (8.11.6/8.11.6) with ESMTP id fBMMNO363066; Sat, 22 Dec 2001 23:23:25 +0100 (CET) (envelope-from aaron@meta.lo-res.org) Date: Sat, 22 Dec 2001 23:23:24 +0100 (CET) From: aaron To: Julian Elischer Cc: Matthew Dillon , Joe Halpin , "current@FreeBSD.ORG" Subject: Re: spam In-Reply-To: Message-ID: <20011222225555.G62982-100000@meta.lo-res.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 22 Dec 2001, Julian Elischer wrote: > I would suggest that we use a 'modified' subscription method, > where simply being mentionned in the list is enough to subscribe.. > > Now, before you laugh.. there's a twist.. > any address found in the archives is automatically subscribed > and that includes in the text.. also any mail not subscribed it treated > as if it were a moderated list. i.e. sent for OK to someone. > once that peson OKs it the person can send mail. I'd suggest that there be (...) > the mail will subscribe the sender. Julian, I think your idea and mine were pretty close. I believe the goals are: a) not to slow down -current or -hackers by moderation (=> use many moderators as you noted) b) distribute power of moderation (*) c) use technology as much as possible for automation of subscription (thats why I suggested public keys and signatures, since they are a safe indicator that somebody is not imposting as someone else via mail headers) and finally d) keep it as simple as possible I believe your idea would work out great and it would not force people to use gpg/pgp (cf point d). On the other hand signatures seem to be the only way to make sure a certain mail is in fact coming from a subscribed person. Given the current load on -current a process checking each incoming mail for 1) having a sig 2) having a valid sig 3) checking if a certain pub key of a certain subscriber maches the sig - should not be such a problem. Anyway.... I would like to hear how others feel about that. ---- (*) I could imagine something like: there are n moderators and when the mail arrives m (m << n) random moderators are forwarded the new mail. It is sufficient if one of the m moderators accepts the message as not being spam. So if a submitter feels left out by some moderator chances are higher his/her message will be accepted the next time by a different moderator - as long as it is not spam :) If the -current subscribers would want such a scheme I would be happy to help in any way needed. Let me know. greetings, Aaron Kaplan. --- COSHER = Completely Open Source, Headers, Engineering, and Research To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 22 15:39:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from imntmail01.immc.org (imntmail01.immc.org [216.90.127.205]) by hub.freebsd.org (Postfix) with ESMTP id B5F4937B419; Sat, 22 Dec 2001 15:39:13 -0800 (PST) Received: from dumpfbacke.de ([196.40.33.200]) by imntmail01.immc.org (Lotus Domino Release 5.0.5) with SMTP id 2001122217373337:28374 ; Sat, 22 Dec 2001 17:37:33 -0600 Message-Id: X-Priority: 3 (Normal) MIME-Version: 1.0 X-Encoding: MIME Subject: Copy DVD's to CDR -dqofclpjlc From: garth2284@cgxybyom.yahoo.com Date: Sat, 22 Dec 2001 16:27:39 +0800 X-MSMail-Priority: Normal To: dan@yogxf.freebsddiary.org Reply-To: hank2597@yahoo.com Importance: Normal X-MIMETrack: Itemize by SMTP Server on imntmail01/IMMC(Release 5.0.5 |September 22, 2000) at 12/22/2001 05:37:40 PM, Serialize by Router on imntmail01/IMMC(Release 5.0.5 |September 22, 2000) at 12/22/2001 05:37:44 PM, Serialize complete at 12/22/2001 05:37:44 PM Content-Type: multipart/alternative; boundary="----=_NextPart_568633474653" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_568633474653 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=us-ascii Wish You Could Copy DVD Movies? Now You Can! Click Here For Details http://www.whammyweb.org/dvd2/index1.html ------=_NextPart_568633474653 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 dvd-ad

 =
 
Wish You Could Copy DVD Movies?

Now You Can!
 =
Click Here For Details
 =
 =
 =
 =
 =
=3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D==3D=

REMOVE ME

------=_NextPart_568633474653-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message