From owner-freebsd-current Sun Apr 29 2:20: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 58DAD37B423 for ; Sun, 29 Apr 2001 02:20:04 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id LAA18631 for freebsd-current@freebsd.org; Sun, 29 Apr 2001 11:20:03 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3T8q2K75150; Sun, 29 Apr 2001 10:52:02 +0200 (MET DST) (envelope-from j) Date: Sun, 29 Apr 2001 10:52:02 +0200 (MET DST) Message-Id: <200104290852.f3T8q2K75150@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: camcontrol stop / restart broken X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tomi Vainio - Sun Finland - wrote: > My source disk is quite noisy so normally I stop it after building the > world and restart it once a week. Couple weeks this restart hasn't > worked as before. Oh, now that you mention it, i've seen that before, too. I didn't pay too much attention then since i initially thought that particular disk wasn't quite OK together with my new controller (the Tekram BIOS also has problems if the drive isn't spun-up at boot time). But now that i've seen the same kind of behaviour for other devices (like a scanner that has been power-cycled), i see the correlation to the CAM error handling changes here as well. If you don't get a reply here, please repost to freebsd-scsi@freebsd.org. If you look into the archives of that list, you can see some other discussions about the new error handling. Note that it's most likely not the rewritten error handling itself, but rather that the rewrite uncovered bugs in the top-layer SCSI drivers. > Only way to start disk again is reboot. Disconnecting (or powering off the drive), "camcontrol rescan", reconnect, "camcontrol rescan" would probably work as well. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 4:48:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (Postfix) with ESMTP id 16F5737B422 for ; Sun, 29 Apr 2001 04:48:00 -0700 (PDT) (envelope-from Tomi.Vainio@finland.sun.com) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA21343; Sun, 29 Apr 2001 04:47:55 -0700 (PDT) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.9) with ESMTP id OAA00770; Sun, 29 Apr 2001 14:47:50 +0300 (EET DST) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id OAA10751; Sun, 29 Apr 2001 14:47:47 +0300 (EEST) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> Date: Sun, 29 Apr 2001 14:47:47 +0300 To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: camcontrol stop / restart broken In-Reply-To: <20010428224047.A37268@panzer.kdm.org> References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> X-Mailer: VM 6.92 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry writes: > > Can you do the following: > > camcontrol stop da1 > camcontrol tur da1 -v > [ then you can start it back up with camcontrol start ] > > What I want to see here is the sense information coming back from the drive > when it is spun down. > > The new error recovery code should be doing the same thing as the old error > recovery code -- sending a start unit. For some reason it isn't doing the > right thing, though. > cat:~(10)# camcontrol stop da1 Unit stopped successfully cat:~(11)# camcontrol tur da1 -v Unit is not ready (pass1:ahc0:0:2:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass1:ahc0:0:2:0): CAM Status: SCSI Status Error (pass1:ahc0:0:2:0): SCSI Status: Check Condition (pass1:ahc0:0:2:0): NOT READY asc:4,2 (pass1:ahc0:0:2:0): Logical unit not ready, initializing cmd. required field replaceable unit: 2 cat:~(12)# mount /f mount: /dev/da1s1e: Input/output error cat:~(13)# camcontrol tur da1 -v Unit is not ready (pass1:ahc0:0:2:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass1:ahc0:0:2:0): CAM Status: SCSI Status Error (pass1:ahc0:0:2:0): SCSI Status: Check Condition (pass1:ahc0:0:2:0): NOT READY asc:4,2 (pass1:ahc0:0:2:0): Logical unit not ready, initializing cmd. required field replaceable unit: 2 cat:~(15)# camcontrol start da1 Unit started successfully cat:~(16)# mount /f mount: /dev/da1s1e: Input/output error cat:~(17)# camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus1 target 2 lun 0 (probe0,pass1,da1) Also messages file is full of these: Apr 29 00:55:42 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue Apr 29 00:55:43 cat last message repeated 26 times Apr 29 00:57:43 cat last message repeated 359 times Apr 29 01:07:43 cat last message repeated 1793 times Apr 29 01:17:43 cat last message repeated 1794 times Apr 29 01:27:43 cat last message repeated 1793 times Apr 29 01:34:13 cat last message repeated 1122 times Apr 29 01:34:13 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue Apr 29 01:34:13 cat last message repeated 43 times Apr 29 01:36:02 cat last message repeated 322 times Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 10:10:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 94BFE37B423 for ; Sun, 29 Apr 2001 10:10:48 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f3THAaU39802 for ; Sun, 29 Apr 2001 19:10:36 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: World is broken... From: Poul-Henning Kamp Date: Sun, 29 Apr 2001 19:10:36 +0200 Message-ID: <39800.988564236@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG make buildworld: gzip -cn /flat/src/sys/boot/i386/loader/../../common/loader.8 > loader.8.gz sh /flat/src/sys/boot/i386/loader/../../common/newvers.sh /flat/src/sys/boot/i386/loader/version "bootstrap loader" i386 cc -c vers.c /flat/src/sys/boot/i386/loader/../../common/interp_forth.c: In function `bf_init': /flat/src/sys/boot/i386/loader/../../common/interp_forth.c:246: warning: passing arg 1 of `ficlBuild' discards qualifiers from pointer target type /flat/src/sys/boot/i386/loader/../../common/load_elf.c: In function `fake_modname': /flat/src/sys/boot/i386/loader/../../common/load_elf.c:549: warning: assignment discards qualifiers from pointer target type /flat/src/sys/boot/i386/loader/../../common/load_elf.c:557: warning: assignment discards qualifiers from pointer target type cc -nostdlib -static -Ttext 0x0 -o loader.sym /usr/obj/flat/src/sys/boot/i386/loader/../btx/lib/crt0.o main.o conf.o bcache.o boot.o commands.o cons ole.o devopen.o interp.o interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic.o isapnp.o pnp.o interp_forth.o vers.o /usr/obj/flat/src/sys/boot/i386/loader/../../ficl/libficl.a /usr/obj/flat/src/sys/boot/i386/loader/../libi386/libi386.a /usr/obj/flat/src/sys/boot/ i386/loader/../../../../lib/libstand/libstand.a /usr/obj/flat/src/sys/boot/i386/loader/../../ficl/libficl.a(words.o): In function `ficlParseNumber': words.o(.text+0x1ae): undefined reference to `isalnum' *** Error code 1 1 error *** Error code 2 1 error -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 10:19:27 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 5D7F137B43F for ; Sun, 29 Apr 2001 10:19:25 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f3THJP726340 for current@FreeBSD.ORG; Sun, 29 Apr 2001 10:19:25 -0700 (PDT) Date: Sun, 29 Apr 2001 10:19:25 -0700 (PDT) From: David Wolfskill Message-Id: <200104291719.f3THJP726340@bunrab.catwhisker.org> To: current@FreeBSD.ORG Subject: Re: World is broken... In-Reply-To: <39800.988564236@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Poul-Henning Kamp >Date: Sun, 29 Apr 2001 19:10:36 +0200 > /usr/obj/flat/src/sys/boot/i386/loader/../../ficl/libficl.a /usr/obj/flat/src/sys/boot/i386/loader/../libi386/libi386.a /usr/obj/flat/src/sys/boot/ >i386/loader/../../../../lib/libstand/libstand.a >/usr/obj/flat/src/sys/boot/i386/loader/../../ficl/libficl.a(words.o): In function `ficlParseNumber': >words.o(.text+0x1ae): undefined reference to `isalnum' >*** Error code 1 >1 error >*** Error code 2 >1 error Likewise (I was just about to send my report in when I saw phk's). Most recent CVSups done: CVSup started from cvsup14.freebsd.org at Sat Apr 28 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Sat Apr 28 03:54:18 PDT 2001 CVSup started from cvsup14.freebsd.org at Sun Apr 29 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Sun Apr 29 03:53:14 PDT 2001 and yesterday's -CURRENT (and -STABLE) built & ran fine. The only reference to isalnum() I see is in boot/ficl/words.c:274, and appears to replace a couple of references, one to isdigit() and the other to isalpha(). Perhaps something was omitted in the upgrade to ficl 2.05? Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 10:26:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 9B91F37B424 for ; Sun, 29 Apr 2001 10:26:23 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA08789; Sun, 29 Apr 2001 11:26:21 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id LAA28217; Sun, 29 Apr 2001 11:26:21 -0600 (MDT) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15084.20156.785173.734583@nomad.yogotech.com> Date: Sun, 29 Apr 2001 11:26:20 -0600 (MDT) To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: ipfw: several equal rules under same number bug In-Reply-To: <20010429063345.A48717@nagual.pp.ru> References: <20010429063345.A48717@nagual.pp.ru> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How it can be possible? ipfw -a l: > > 07001 40 1680 deny tcp from any to any 7006 > 07001 0 0 deny tcp from any to any 7006 > 07001 0 0 deny tcp from any to any 7006 > > I use equal "ipfw add" several times from the script, but the rule number > was the same all times. I expect that rule is replaced, not added with > same number several times. > > Who is our ipfw guru at this moment? This is the way it's been since day one in ipfw. A rule is not an atomic entity, so you can have every rule in your entire list with the same number if you so desire. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 12: 1:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B23E737B446 for ; Sun, 29 Apr 2001 12:01:03 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f3TJ0v000618; Sun, 29 Apr 2001 12:00:57 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f3TJ0uS39289; Sun, 29 Apr 2001 12:00:56 -0700 (PDT) (envelope-from jdp) Date: Sun, 29 Apr 2001 12:00:56 -0700 (PDT) Message-Id: <200104291900.f3TJ0uS39289@vashon.polstra.com> To: current@freebsd.org From: John Polstra Cc: david@catwhisker.org Subject: Re: World is broken... In-Reply-To: <200104291719.f3THJP726340@bunrab.catwhisker.org> References: <200104291719.f3THJP726340@bunrab.catwhisker.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200104291719.f3THJP726340@bunrab.catwhisker.org>, David Wolfskill wrote: > >From: Poul-Henning Kamp > >Date: Sun, 29 Apr 2001 19:10:36 +0200 > > > /usr/obj/flat/src/sys/boot/i386/loader/../../ficl/libficl.a /usr/obj/flat/src/sys/boot/i386/loader/../libi386/libi386.a /usr/obj/flat/src/sys/boot/ > >i386/loader/../../../../lib/libstand/libstand.a > >/usr/obj/flat/src/sys/boot/i386/loader/../../ficl/libficl.a(words.o): In function `ficlParseNumber': > >words.o(.text+0x1ae): undefined reference to `isalnum' > >*** Error code 1 > >1 error > >*** Error code 2 > >1 error [...] > > The only reference to isalnum() I see is in boot/ficl/words.c:274, and > appears to replace a couple of references, one to isdigit() and the > other to isalpha(). > > Perhaps something was omitted in the upgrade to ficl 2.05? It's because words.c uses instead of , and is missing the #define for isalnum(). I imagine adding something like this to would fix it: #define isalnum(c) (isalpha(c) || isdigit(c)) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 12: 7:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id AC5F437B623 for ; Sun, 29 Apr 2001 12:07:05 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f3TJBw801041; Sun, 29 Apr 2001 12:11:59 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104291911.f3TJBw801041@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Polstra Cc: current@freebsd.org, david@catwhisker.org Subject: Re: World is broken... In-reply-to: Your message of "Sun, 29 Apr 2001 12:00:56 PDT." <200104291900.f3TJ0uS39289@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Sun, 29 Apr 2001 12:11:58 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The only reference to isalnum() I see is in boot/ficl/words.c:274, an= d > > appears to replace a couple of references, one to isdigit() and the > > other to isalpha(). > > = > > Perhaps something was omitted in the upgrade to ficl 2.05? > = > It's because words.c uses instead of , and > is missing the #define for isalnum(). I imagine adding > something like this to would fix it: > = > #define isalnum(c) (isalpha(c) || isdigit(c)) Just FWIW, you can't use in the loader; it's too incestuously = entangled with the rest of libc. I suspect that Daniel forgot to update = libstand. I've stuck this in for now. -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 12:55:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id 6D07837B42C for ; Sun, 29 Apr 2001 12:55:41 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.138] (helo=mx0.freenet.de) by mout1.freenet.de with esmtp (Exim 3.22 #1) id 14txIC-0003TZ-00 for current@freebsd.org; Sun, 29 Apr 2001 21:55:40 +0200 Received: from b8413.pppool.de ([213.7.132.19] helo=Magelan.Leidinger.net) by mx0.freenet.de with esmtp (Exim 3.22 #1) id 14txIB-0002gN-00 for current@freebsd.org; Sun, 29 Apr 2001 21:55:39 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.3/8.11.3) with ESMTP id f3TJqT565732 for ; Sun, 29 Apr 2001 21:52:30 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200104291952.f3TJqT565732@Magelan.Leidinger.net> Date: Sun, 29 Apr 2001 21:52:28 +0200 (CEST) From: Alexander Leidinger Subject: {id,rt}prio broken (at syscall level?) To: current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, -current from yesterday: ---snip--- (45) root@ttyp0 # idprio 31 /bin/sleep 10 idprio: idprio: Invalid argument (46) root@ttyp0 # rtprio 31 /bin/sleep 10 rtprio: rtprio: Invalid argument ---snip--- isdnd is also affected (if you use its rtprio keyword in isdnd.rc). Bye, Alexander. -- Press every key to continue. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 13: 9:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id E066837B443 for ; Sun, 29 Apr 2001 13:09:10 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f3TK99f18437 for ; Sun, 29 Apr 2001 16:09:09 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 29 Apr 2001 16:09:09 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-current@FreeBSD.org Subject: panic: vm_page_alloc: free/cache page 0xc092fab8 was dirty Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Got this on an April 14 -CURRENT, while rebuilding a kernel: panic: vm_page_alloc: free/cache page 0xc092fab8 was dirty Debugger("panic") Stopped at Debugger+0x44 pushl %ebx db> trace Debugger(c0412b7b) at Debugger+0x44 panic(c0432160,c092fab8,0,c8a98ca0,c7b1bce0) at panic+0x70 vm_page_alloc(c8bfd720,23,3,c8a98dbc,c8a98ca9) at vm_page_alloc+0x1bb vm_fault(c7b1bce0,8090000,2,8,0) at vm_fault+0x2ec trap_pfault(c8af7fa8,1,8090000,2000,20) at trap_pfault+0x2f9 trap(2f,2f,2f,8090000,20) at trap+0x444 calltrap() at calltrap_0x5 --- trap 0xc, eip = 0x8063d5b, esp = 0xbfbfeb7c, ebp = 0xbfbfebb4 --- Haven't seen it before on this kernel version, so don't think it's reproduceable per se. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 13:24: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 303EB37B42C; Sun, 29 Apr 2001 13:23:57 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f3TKNu000939; Sun, 29 Apr 2001 13:23:56 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f3TKNqK39533; Sun, 29 Apr 2001 13:23:52 -0700 (PDT) (envelope-from jdp) Date: Sun, 29 Apr 2001 13:23:52 -0700 (PDT) Message-Id: <200104292023.f3TKNqK39533@vashon.polstra.com> To: current@freebsd.org From: John Polstra Reply-To: current@freebsd.org Cc: msmith@freebsd.org Subject: dirpref: a new form of rm -rf * (was: World is broken...) In-Reply-To: <200104291911.f3TJBw801041@mass.dis.org> References: <200104291911.f3TJBw801041@mass.dis.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200104291911.f3TJBw801041@mass.dis.org>, Mike Smith wrote: > > #define isalnum(c) (isalpha(c) || isdigit(c)) > > Just FWIW, you can't use in the loader; it's too incestuously > entangled with the rest of libc. I suspect that Daniel forgot to update > libstand. > > I've stuck this in for now. Thanks. I wish it had just stayed broken. Running this morning's kernel has immediately trashed my entire root filesystem. I updated the kernel and modules and rebooted. Double-checked UPDATING, which assured me that the "old fsck and new kernel interactions appear to have been fixed." Started a make buildworld. It hung almost immediately, in the "rm -rf /usr/obj/local0/src/i386" step of "Rebuilding the temporary build tree". No response to the keyboard, no response to pings. It wouldn't escape into DDB, and there were no messages of any kind. Upon rebooting, fsck complained about many unexpected soft-updates inconsistencies and other problems. By the time it had finished having its way with me, I was left with nothing but "/lost+found". It's a single-CPU system, SCSI disks, nothing special. Obviously I can't give you the kernel config file or dmesg output at this point. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 14: 6:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 711DD37B443 for ; Sun, 29 Apr 2001 14:06:25 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f3TL6Of19289 for ; Sun, 29 Apr 2001 17:06:24 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 29 Apr 2001 17:06:24 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Subject: recent -CURRENT and boot loader / kernel problems? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Dell Latitude CPi notebook, and recently ran into some nastiness involving the boot process. The machine is using an April 24th world, and up until now had been using an April 24th kernel. Leaving aside problems with pcm hanging the kernel at boot, things seemed to work largely fine. Yesterday, I decided to copy over an April 28th kernel with some custom network hackery to the notebook -- this kernel works fine on a number of other machines. However, when I attempted to boot the kernel, I ran into the following problem: ok load /boot/kernel.bad/kernel don't know how to load module '/boot/kernel.bad/kernel' Reverting back to an April 24 kernel seems to work fine. Interestingly, I also had some problems booting some other kernels from floppy -- the kernel seemed to load ok, but then hung during the twiddling line bit of the boot process. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 15:29: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from cr66388-a.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id 8602B37B422 for ; Sun, 29 Apr 2001 15:28:59 -0700 (PDT) (envelope-from jburkholder0829@home.com) Received: from k7.rchrd1.on.wave.home.com (k7.rchrd1.on.wave.home.com [10.0.0.253]) by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP id B33A5196; Sun, 29 Apr 2001 18:28:46 -0400 (EDT) Received: from k7.rchrd1.on.wave.home.com (localhost [127.0.0.1]) by k7.rchrd1.on.wave.home.com (Postfix) with ESMTP id 91B9D22A5; Sun, 29 Apr 2001 18:31:35 -0400 (EDT) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: {id,rt}prio broken (at syscall level?) In-Reply-To: Message from Alexander Leidinger of "Sun, 29 Apr 2001 21:52:28 +0200." <200104291952.f3TJqT565732@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Apr 2001 18:31:35 -0400 From: Jake Burkholder Message-Id: <20010429223135.91B9D22A5@k7.rchrd1.on.wave.home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > -current from yesterday: > ---snip--- > (45) root@ttyp0 # idprio 31 /bin/sleep 10 > idprio: idprio: Invalid argument > > (46) root@ttyp0 # rtprio 31 /bin/sleep 10 > rtprio: rtprio: Invalid argument > ---snip--- > > isdnd is also affected (if you use its rtprio keyword in isdnd.rc). Thanks, this should be fixed now. A break; was forgotten in some recent proc locking changes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 16:11:56 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 9DDDF37B423 for ; Sun, 29 Apr 2001 16:11:52 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f3TNBqp26845 for current@FreeBSD.ORG; Sun, 29 Apr 2001 16:11:52 -0700 (PDT) Date: Sun, 29 Apr 2001 16:11:52 -0700 (PDT) From: David Wolfskill Message-Id: <200104292311.f3TNBqp26845@bunrab.catwhisker.org> To: current@FreeBSD.ORG Subject: Re: dirpref: a new form of rm -rf * (was: World is broken...) In-Reply-To: <200104292023.f3TKNqK39533@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sun, 29 Apr 2001 13:23:52 -0700 (PDT) >From: John Polstra >In article <200104291911.f3TJBw801041@mass.dis.org>, >Mike Smith wrote: >> > #define isalnum(c) (isalpha(c) || isdigit(c)) Actually, following the lead of the definition of isalpha(), the version I used had the last term of the disjunction wrapped in parens. I suppose there may be some pathological cases where that could be significant. :-} But inserting that definition of isalnum() into /usr/src/lib/libstand/stand.h allowed the build of today's -CURRENT to succeed for me. >> Just FWIW, you can't use in the loader; it's too incestuously >> entangled with the rest of libc. I suspect that Daniel forgot to update >> libstand. Thanks for the insight as to why that is.... >Thanks. I wish it had just stayed broken. Running this morning's >kernel has immediately trashed my entire root filesystem. Given the fore-warning you provided, I was a little more cautious than usual: after mergemaster completed, I first booted single-user, did a manual "fsck -p". No weirdnesses found. (More on config stuff below.) Then I did a (manual) "mount -a"; again, nothing strange. So I rebooted, allowing the system to come up multi-user as usual. No problems observed. >I updated the kernel and modules and rebooted. Double-checked >UPDATING, which assured me that the "old fsck and new kernel >interactions appear to have been fixed." Started a make buildworld. >It hung almost immediately, in the "rm -rf /usr/obj/local0/src/i386" >step of "Rebuilding the temporary build tree". No response to the >keyboard, no response to pings. It wouldn't escape into DDB, and >there were no messages of any kind. Blecch. :-( >Upon rebooting, fsck complained about many unexpected soft-updates >inconsistencies and other problems. By the time it had finished >having its way with me, I was left with nothing but "/lost+found". Urggh. Sympathy. :-( I haven't tried a "make buildworld" yet -- I'd normally do that after updating my sources, and after the problem with isalnum(), I had re-CVSupped: CVSup started from cvsup14.freebsd.org at Sat Apr 28 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Sat Apr 28 03:54:18 PDT 2001 CVSup started from cvsup14.freebsd.org at Sun Apr 29 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Sun Apr 29 03:53:14 PDT 2001 CVSup started from cvsup14.freebsd.org at Sun Apr 29 10:00:22 PDT 2001 CVSup ended from cvsup14.freebsd.org at Sun Apr 29 10:06:31 PDT 2001 and did the "cvs update" in the /usr/src I use for -CURRENT. >It's a single-CPU system, SCSI disks, nothing special. Obviously I >can't give you the kernel config file or dmesg output at this point. On my side, I'm using my laptop -- single-CPU, single IDE drive; everything mounted with soft updates turned on. It's set up to boot any of 3 (FreeBSD) environments (so an FS that's root for one would be mounted elsewhere for others, which is one of the reasons I have soft updates on everywhere). Hope your system is recovered soon, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 16:13:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id CF14E37B422 for ; Sun, 29 Apr 2001 16:13:49 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA41830; Sun, 29 Apr 2001 17:13:47 -0600 (MDT) (envelope-from ken) Date: Sun, 29 Apr 2001 17:13:47 -0600 From: "Kenneth D. Merry" To: Tomi Vainio - Sun Finland - Cc: freebsd-current@FreeBSD.ORG Subject: Re: camcontrol stop / restart broken Message-ID: <20010429171347.B41755@panzer.kdm.org> References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <15083.65379.523173.371122@ultrahot.Finland.Sun.COM>; from Tomi.Vainio@Sun.COM on Sun, Apr 29, 2001 at 02:47:47PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 29, 2001 at 14:47:47 +0300, Tomi Vainio - Sun Finland - wrote: > Kenneth D. Merry writes: > > > > Can you do the following: > > > > camcontrol stop da1 > > camcontrol tur da1 -v > > [ then you can start it back up with camcontrol start ] > > > > What I want to see here is the sense information coming back from the drive > > when it is spun down. > > > > The new error recovery code should be doing the same thing as the old error > > recovery code -- sending a start unit. For some reason it isn't doing the > > right thing, though. > > > cat:~(10)# camcontrol stop da1 > Unit stopped successfully > cat:~(11)# camcontrol tur da1 -v > Unit is not ready > (pass1:ahc0:0:2:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (pass1:ahc0:0:2:0): CAM Status: SCSI Status Error > (pass1:ahc0:0:2:0): SCSI Status: Check Condition > (pass1:ahc0:0:2:0): NOT READY asc:4,2 > (pass1:ahc0:0:2:0): Logical unit not ready, initializing cmd. required field replaceable unit: 2 > cat:~(12)# mount /f > mount: /dev/da1s1e: Input/output error > cat:~(13)# camcontrol tur da1 -v > Unit is not ready > (pass1:ahc0:0:2:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (pass1:ahc0:0:2:0): CAM Status: SCSI Status Error > (pass1:ahc0:0:2:0): SCSI Status: Check Condition > (pass1:ahc0:0:2:0): NOT READY asc:4,2 > (pass1:ahc0:0:2:0): Logical unit not ready, initializing cmd. required field replaceable unit: 2 That's the normal error message, so I'm not sure what's going on here. This will probably have to wait 'till tomorrow when I can get on a -current test box. There's definitely something odd going on. > cat:~(15)# camcontrol start da1 > Unit started successfully > cat:~(16)# mount /f > mount: /dev/da1s1e: Input/output error At this point the pack has probably already been invalidated, so it won't let you mount the drive. > cat:~(17)# camcontrol devlist > at scbus0 target 0 lun 0 (pass0,da0) > at scbus1 target 2 lun 0 (probe0,pass1,da1) > > > > Also messages file is full of these: > > Apr 29 00:55:42 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue > Apr 29 00:55:43 cat last message repeated 26 times > Apr 29 00:57:43 cat last message repeated 359 times > Apr 29 01:07:43 cat last message repeated 1793 times > Apr 29 01:17:43 cat last message repeated 1794 times > Apr 29 01:27:43 cat last message repeated 1793 times > Apr 29 01:34:13 cat last message repeated 1122 times > Apr 29 01:34:13 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue > Apr 29 01:34:13 cat last message repeated 43 times > Apr 29 01:36:02 cat last message repeated 322 times That's not good; it means malloc is failing. Did this happen right after boot, or after a 'camcontrol rescan' or what? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 16:39:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from beastie.saturn-tech.com (beastie.saturn-tech.com [207.229.19.136]) by hub.freebsd.org (Postfix) with ESMTP id 878EF37B440 for ; Sun, 29 Apr 2001 16:39:09 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by beastie.saturn-tech.com (8.11.1/8.11.0) with ESMTP id f3UDXBk77849; Mon, 30 Apr 2001 07:33:11 -0600 (MDT) (envelope-from drussell@saturn-tech.com) X-Authentication-Warning: beastie.saturn-tech.com: drussell owned process doing -bs Date: Mon, 30 Apr 2001 07:33:11 -0600 (MDT) From: Doug Russell To: "Kenneth D. Merry" Cc: Tomi Vainio - Sun Finland - , freebsd-current@FreeBSD.ORG Subject: Re: camcontrol stop / restart broken In-Reply-To: <20010429171347.B41755@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Apr 2001, Kenneth D. Merry wrote: > (pass1:ahc0:0:2:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (pass1:ahc0:0:2:0): CAM Status: SCSI Status Error > (pass1:ahc0:0:2:0): SCSI Status: Check Condition > (pass1:ahc0:0:2:0): NOT READY asc:4,2 > (pass1:ahc0:0:2:0): Logical unit not ready, initializing cmd. required field replaceable unit: 2 > cat:~(12)# mount /f > mount: /dev/da1s1e: Input/output error Just curious, but, does it still bomb if you manually camcontrol stop da1 camcontrol start da1 camcontrol start da1 (do it two or three times to be sure...) camcontrol start da1 mount whatever Does it still stick whenever the drive is manually powered up, or does it only stick when FreeBSD should be automatically restarting a stopped drive? I'm assuming the camcontrol start da1 just always returns an error? No? Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 17:28:12 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 6388737B43E for ; Sun, 29 Apr 2001 17:28:08 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 KAA25706; Mon, 30 Apr 2001 10:27:52 +1000 Date: Mon, 30 Apr 2001 10:26:47 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Polstra Cc: current@FreeBSD.ORG, david@catwhisker.org Subject: Re: World is broken... In-Reply-To: <200104291900.f3TJ0uS39289@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Apr 2001, John Polstra wrote: > It's because words.c uses instead of , and > is missing the #define for isalnum(). I imagine adding > something like this to would fix it: > > #define isalnum(c) (isalpha(c) || isdigit(c)) That would be broken, since it would make isalnum() evaluate its arg more than once, but the other ctype macros in and already have this quality, although libstand.3 claims that these functions have the same behaviour as the non-broken libc ones. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 29 17:32:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.6.200.230]) by hub.freebsd.org (Postfix) with ESMTP id E7D6437B43C for ; Sun, 29 Apr 2001 17:32:49 -0700 (PDT) (envelope-from mdharnois@home.com) Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id 5752A14A11; Sun, 29 Apr 2001 19:33:09 -0500 (CDT) To: John Polstra Cc: current@FreeBSD.ORG, david@catwhisker.org Subject: Re: World is broken... Keywords: isalnum,stand References: <200104291719.f3THJP726340@bunrab.catwhisker.org> <200104291900.f3TJ0uS39289@vashon.polstra.com> From: Michael Harnois Date: 29 Apr 2001 19:33:08 -0500 In-Reply-To: <200104291900.f3TJ0uS39289@vashon.polstra.com> (John Polstra's message of "Sun, 29 Apr 2001 12:00:56 -0700 (PDT)") Message-ID: <867l03cjln.fsf@mharnois.workgroup.net> Lines: 25 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) XEmacs/21.5 (alfalfa) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Apr 2001 12:00:56 -0700 (PDT), John Polstra said: > I imagine adding something like this to would fix it: > #define isalnum(c) (isalpha(c) || isdigit(c)) This suggestion was posted this morning in cvs-all; The file 'sys/boot/ficl/words.c' contains the "call" to 'isalnum' (macro) whic is not defined in header file. To fix world breakage you can drfine 'isalnum' in '' or use 'isxdigit' in the sys/boot/ficl/words.c instead of 'isalnum'. N.Dudorov I don't have any idea if the latter is correct, but I can tell you it works here (and I am experiencing none of the errors others in this thread have noted ...). -- Michael D. Harnois mdharnois@home.com Redeemer Lutheran Church Washburn, Iowa Make everything as simple as possible, but not simpler. -- Einstein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 0:36:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 3200037B423 for ; Mon, 30 Apr 2001 00:36:40 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14u8EU-0000Gb-00; Mon, 30 Apr 2001 09:36:34 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id JAA18626; Mon, 30 Apr 2001 09:36:31 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 18474; Mon Apr 30 09:35:50 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14u8Dm-0003EC-00; Mon, 30 Apr 2001 09:35:50 +0200 To: Yoshihiro Koya Cc: freebsd-current@freebsd.org Subject: Re: A question about max_uid In-reply-to: Your message of "Fri, 27 Apr 2001 00:15:55 +0900." <20010427001555G.koya@pluto.math.yokohama-cu.ac.jp> Date: Mon, 30 Apr 2001 09:35:50 +0200 Message-ID: <12411.988616150@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Apr 2001 00:15:55 +0900, Yoshihiro Koya wrote: > Currently, I have nobody (uid = 65534) account as a default account on > my box. It might be easy to guess that the maximum is greater than > 65533. My question is why such a restricion still remains. From what I remember from my communication with Bruce Evans, the "restrictions" (mostly unenforced" in our tree are there to protect old software compiled to use 16-bit UID values. By allowing unsigned 32-bit UID values in the system, you open the door for problems with software that uses smaller UID values. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 0:56:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id D486637B422 for ; Mon, 30 Apr 2001 00:56:36 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14u8Xq-0000Wv-00; Mon, 30 Apr 2001 09:56:34 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id JAA22940; Mon, 30 Apr 2001 09:56:31 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 22797; Mon Apr 30 09:56:09 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14u8XR-0003TX-00; Mon, 30 Apr 2001 09:56:09 +0200 To: Jeroen Ruigrok/Asmodai Cc: current@freebsd.org Subject: Re: cp -u patch In-reply-to: Your message of "Thu, 26 Apr 2001 22:21:32 +0200." <20010426222132.B55566@daemon.ninth-circle.org> Date: Mon, 30 Apr 2001 09:56:09 +0200 Message-ID: <13362.988617369@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 26 Apr 2001 22:21:32 +0200, Jeroen Ruigrok/Asmodai wrote: > Question is, do we want to add this to our cp? Bleh. :-) for i in `find /path/to/src`; do if [ $i -nt /path/to/dst/$i ]; then cp $i /path/to/dst/ fi done And the people who question the efficiency of such shell scripts would do well to 1) Think about the frequency with which these special cases are actually required. 2) Think about the existence of perl(1) and cc(1) on their systems. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 1:21: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id BCD2937B423 for ; Mon, 30 Apr 2001 01:21:01 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.11.3/8.11.3) with ESMTP id f3U8Ktc16019 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Mon, 30 Apr 2001 10:20:55 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.11.2/8.11.2) id f3U8KsJ07475; Mon, 30 Apr 2001 10:20:54 +0200 (CEST) Date: Mon, 30 Apr 2001 10:20:54 +0200 From: Cejka Rudolf To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Experiences with new dir allocation on FFS? Message-ID: <20010430102054.A4474@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Sat, Apr 28, 2001 at 02:34:12PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote (2001/04/28): > This is probably caused by write caching now being off by default > in the ata driver, possibly amplified by not using soft updates. > Without the new dir allocation, -current would be even slower :(. Yes, thanks. I really forgot on this change. My rough results are now: Old s./wc enabled New s./wc enabled New s./wc disabled tar xvfz 8 minutes 4 minutes 14 minutes rm -r 5 minutes 1 minute 2 minutes There is another reason for tar "slowness": Current version of tar seems to be faster than our old system tar: 3m23 against 3m44 for tar xvfz with wc enabled. I think there are even bigger differences with tar cvfz and tar xvfz with wc disabled. -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 2:39:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from localhost.my.domain (cobu-d930d331.pool.mediaWays.net [217.48.211.49]) by hub.freebsd.org (Postfix) with ESMTP id 631F137B422 for ; Mon, 30 Apr 2001 02:39:17 -0700 (PDT) (envelope-from revolution@inorbit.com) Received: from inorbit.com (localhost [127.0.0.1]) by localhost.my.domain (8.11.1/8.11.1) with ESMTP id f3U9cXX00389 for ; Mon, 30 Apr 2001 11:38:35 +0200 (CEST) (envelope-from revolution@inorbit.com) Message-ID: <3AED3298.50B1328E@inorbit.com> Date: Mon, 30 Apr 2001 11:38:33 +0200 From: Georg Funk X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: sio overflows Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! So, I've recompiled my Kernel, and if I connect to the internet, my console is flooded by lots of sio overflows(on sio1), and my connection is very slow. My Modem(Elsa Microlink 56k internet) is on com2. Who can help me ? Thx in advance, Georg Funk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 3: 0:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by hub.freebsd.org (Postfix) with ESMTP id 434DA37B424 for ; Mon, 30 Apr 2001 03:00:02 -0700 (PDT) (envelope-from gwk@hunter.munich.sgi.com) Received: from sgiger.munich.sgi.com (sgiger.munich.sgi.com [144.253.192.2]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id LAA164447; Mon, 30 Apr 2001 11:59:55 +0200 (CEST) mail_from (gwk@hunter.munich.sgi.com) Received: from cuckoo.munich.sgi.com (cuckoo.munich.sgi.com [144.253.192.109]) by sgiger.munich.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id LAA03782; Mon, 30 Apr 2001 11:58:48 +0200 Received: from hunter.munich.sgi.com (hunter.munich.sgi.com [144.253.197.18]) by cuckoo.munich.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id LAA16909; Mon, 30 Apr 2001 11:58:48 +0200 (CEST) Received: (from gwk@localhost) by hunter.munich.sgi.com (8.11.3/8.11.3) id f3U9xcI08275; Mon, 30 Apr 2001 11:59:38 +0200 (CEST) (envelope-from gwk) Date: Mon, 30 Apr 2001 11:59:38 +0200 From: "Georg-W. Koltermann" To: Andrew Gallatin Cc: current@freebsd.org Subject: Re: Linux JDK 1.3 and hotspot (native threads) Message-ID: <20010430115936.A1525@hunter.munich.sgi.com> Mail-Followup-To: Andrew Gallatin , current@freebsd.org References: <20010426185450.B10195@hunter.munich.sgi.com> <15082.7626.656950.951816@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15082.7626.656950.951816@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Fri, Apr 27, 2001 at 09:32:58PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 27, 2001 at 09:32:58PM -0400, Andrew Gallatin wrote: > > Georg-W. Koltermann writes: > > <...> > > In order to get real performance I would like to run either the SUN > > JDK with -hotspot, or the IBM 1.3 JVM. Both of these use native linux > > threads. With a recent -current I can successfully execute small JAVA > > test programs, but when I start a real application (e.g. Together from > > togethersoft.com), it fails with a core dump. > > <...> > > Can you try the kernel patch in > http://www.freebsd.org/cgi/query-pr.cgi?pr=26705 > > It sounds like this is going to get committed soon, but I'd like to > know if it has any affect on your problem. Hi Drew, I tried the patch and found it makes no difference. The current SUN JVM (1.3.0_02) gives the SIG11 as I indicated before. The latest IBM JVM (IBM build cx130-20010329) hangs around and eats up CPU time. It mostly eats system time (usage is about 8% user, 91% system). A normal kill is ineffective, I have to send it a -9 in order to terminate. > Also, are there any non commercial apps that demonstrate the problem? > Or at least things that I don't have to sign my life away to get > access to? Hmm, I don't use any. We are developing a large-scale JAVA servlet application, and that one provokes the SIG11, too. Moneydance, a shareware finance manager that I once evaluated (http://www.seanreilly.com), seems to run ok. If you really want to invest the time, you might go to togethersoft.com and download their product. They will send you an evaluation license as soon as you download the product, without any further request. But it's a big application, and you won't have any use for it unless you develop a large-scale JAVA application. -- Regards, Georg. ---------------------------------------------------------------------- Who in the world needs 2000 Windows? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 4:41:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id 6E47D37B43C for ; Mon, 30 Apr 2001 04:41:56 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout1.freenet.de with esmtp (Exim 3.22 #1) id 14uC3v-0000GA-00; Mon, 30 Apr 2001 13:41:55 +0200 Received: from b8162.pppool.de ([213.7.129.98] helo=Magelan.Leidinger.net) by mx2.freenet.de with esmtp (Exim 3.22 #1) id 14uC3v-0002ys-00; Mon, 30 Apr 2001 13:41:55 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.3/8.11.3) with ESMTP id f3UBd2g00866; Mon, 30 Apr 2001 13:39:03 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200104301139.f3UBd2g00866@Magelan.Leidinger.net> Date: Mon, 30 Apr 2001 13:39:00 +0200 (CEST) From: Alexander Leidinger Subject: Re: {id,rt}prio broken (at syscall level?) To: jburkholder0829@home.com Cc: current@FreeBSD.ORG In-Reply-To: <20010429223135.91B9D22A5@k7.rchrd1.on.wave.home.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29 Apr, Jake Burkholder wrote: > Thanks, this should be fixed now. A break; was forgotten in > some recent proc locking changes. I will test it after "softdep_update_inodeblock: bwrite: got error 22 while accessing filesystem" is fixed (I made a backup of / after reading the bugreport and before trying it myself). Bye, Alexander. -- I believe the technical term is "Oops!" http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 4:47:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id 4F1DA37B423 for ; Mon, 30 Apr 2001 04:47:19 -0700 (PDT) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id VAA10823 for ; Mon, 30 Apr 2001 21:47:11 +1000 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id VAA04333; Mon, 30 Apr 2001 21:47:11 +1000 (EST) Message-Id: <200104301147.VAA04333@lightning.itga.com.au> From: Gregory Bond To: current@freebsd.org Subject: Can't boot installer: integer divide fault MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0" Content-ID: <4310.988631179.0@itga.com.au> Date: Mon, 30 Apr 2001 21:47:11 +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4310.988631179.1@itga.com.au> [Please CC me as I am a stable user and not on the -current list] I'm running stable on a box at home and wanted to check if the -current kernel fixed a problem with my CD-RW drive. So I downloaded the boot floppies from current.freebsd.org, the 20010419 snap (which John B. tells me installs OK on his system). I disabled nearly everything from the visual config, then quit from that. It got as far as PnP detection then failed with an integer divide fault. The following was on the screen (copied by hand!): sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc03085f5 stack pointer = 0x10:0xc080671c frame pointer = 0x10:0xc0806768 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor flags = Interrupts enabled, IOPL = 0 current process = 0 (swapper) trap number = 18 panic: integer divide fault I've attached a dmesg from a verbose boot of 4.3 on the same hardware. If there is any other info I can provide, please yell. Greg. ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4310.988631179.2@itga.com.au> 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 4.3-BETA2 #0: Tue Mar 13 23:31:29 GMT 2001 jkh@narf:/usr/src/sys/compile/GENERIC Calibrating clock(s) ... TSC clock: 398261307 Hz, i8254 clock: 1193160 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Pentium II Xeon/Celeron (398.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00472000 - 0x040fcfff, 63483904 bytes (15499 pages) 0x04100000 - 0x07ff7fff, 66027520 bytes (16120 pages) avail memory = 126283776 (123324K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f6a90 bios32: Entry = 0xfd7b0 (c00fd7b0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x203 pnpbios: Found PnP BIOS data at 0xc00f6ae0 pnpbios: Entry = f0000:9fea Rev = 1.0 Other BIOS signatures found: ACPI: 000f6ac0 Preloaded elf kernel "kernel" at 0xc044c000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base f8000000, size 26 found-> vendor=0x8086, dev=0x7191, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 00001000, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=9 map[20]: type 1, range 32, base 00001020, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 00007000, size 4 found-> vendor=0x1013, dev=0x6001, revid=0x01 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x12d2, dev=0x0018, revid=0x10 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base f5000000, size 24 map[14]: type 1, range 32, base fc000000, size 24 pci1: on pcib1 pci1: (vendor=0x12d2, dev=0x0018) at 0.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1000-0x100f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x1000 ata0: mask=03 status0=50 status1=50 ata0: mask=03 ostat0=50 ostat2=50 ata0-master: ATAPI probe a=00 b=00 ata0-slave: ATAPI probe a=14 b=eb ata0: mask=03 status0=50 status1=00 ata0-master: ATA probe a=01 b=a5 ata0: devices=09 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x1008 ata1: mask=03 status0=50 status1=50 ata1: mask=03 ostat0=50 ostat2=50 ata1-master: ATAPI probe a=00 b=00 ata1-slave: ATAPI probe a=14 b=eb ata1: mask=03 status0=52 status1=00 ata1-master: ATA probe a=01 b=a5 ata1: devices=09 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x1020-0x103f irq 9 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: port 0x7000-0x700f at device 7.3 on pci0 pci0: (vendor=0x1013, dev=0x6001) at 11.0 irq 10 ex_isa_identify() ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number Trying Read_Port at 203 CSC0000: start dependant CSC0000: adding dma mask 0x2 CSC0000: adding dma mask 0x9 CSC0000: adding irq mask 0x20 CSC0000: adding io range 0x534-0x537, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x38b, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x22f, size=0x10, align=0x20 CSC0000: start dependant CSC0000: adding dma mask 0xa CSC0000: adding dma mask 0xb CSC0000: adding irq mask 0xcb8 CSC0000: adding io range 0x534-0xfff, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x38b, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x26f, size=0x10, align=0x20 CSC0000: start dependant CSC0000: adding dma mask 0xb CSC0000: adding irq mask 0xcb8 CSC0000: adding io range 0x534-0xfff, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x3cb, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x30f, size=0x10, align=0x20 CSC0000: end dependant CSC0001: start dependant CSC0001: adding io range 0x200-0x207, size=0x8, align=0x8 CSC0001: start dependant CSC0001: adding io range 0x208-0x20f, size=0x8, align=0x8 CSC0001: end dependant CSC0010: adding io range 0x120-0x3af, size=0x8, align=0x8 CSC0003: start dependant CSC0003: adding irq mask 0x400 CSC0003: adding io range 0x330-0x331, size=0x2, align=0x8 CSC0003: start dependant CSC0003: adding irq mask 0xcb8 CSC0003: adding io range 0x330-0x361, size=0x2, align=0x8 CSC0003: start dependant CSC0003: adding io range 0x330-0x3e1, size=0x2, align=0x8 CSC0003: end dependant isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata2 failed to probe at port 0x1f0 irq 14 on isa0 ata3 failed to probe at port 0x170 irq 15 on isa0 adv0 failed to probe at port 0x330 on isa0 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x330 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x334 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x230 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x234 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x130 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x134 bt0 failed to probe at port 0x134-0x137 on isa0 aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0 failed to probe at port 0x134-0x137 on isa0 aic0 failed to probe at port 0x140-0x15f on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 psm0: current command byte:0047 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:4 psm0: syncmask:08, syncbits:08 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 pcic1: not probed (disabled) sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: irq maps: 0x41 0x41 0x41 0x41 sio0: probe failed test(s): 0 1 2 4 6 7 9 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: irq maps: 0x41 0x41 0x41 0x41 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) ppc0: parallel port not found. ppc0: failed to probe at irq 7 on isa0 ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 bpf: ed0 attached ed0: address 00:00:c0:74:38:bf, type SMC8216T (16 bit) fe0 failed to probe at port 0x300-0x31f on isa0 ie0 failed to probe at port 0x300 iomem 0xd0000 irq 10 on isa0 isa_compat: didn't get ports for lnc isa_compat: didn't get irq for lnc lnc0 failed to probe at port 0x280 irq 10 drq 0 on isa0 cs0 failed to probe at port 0x300-0x31f on isa0 sn0 failed to probe at port 0x300-0x30f irq 10 on isa0 isa_probe_children: probing PnP devices adv1: Invalid baseport of 0x534 specified. Nearest valid baseport is 0x330. Failing probe. unknown: failed to probe at port 0x534-0x543,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 adv1: Invalid baseport of 0x200 specified. Nearest valid baseport is 0x210. Failing probe. unknown: failed to probe at port 0x200-0x20f on isa0 unknown: failed to probe at port 0x120 on isa0 unknown: failed to probe at port 0x330 irq 3 on isa0 BIOS Geometries: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 1:020afe3f 0..522=523 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: lo0 attached bpf: ppp0 attached new masks: bio 68c240, tty 631012, net 671412 bpf: sl0 attached bpf: faith0 attached ata0-master: success setting UDMA2 on PIIX4 chip Creating DISK ad0 Creating DISK wd0 ad0: ATA-5 disk at ata0-master ad0: 19092MB (39102336 sectors), 38792 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=5 cblid=1 ad0: 19092MB [38792/16/63] at ata0-master UDMA33 ata1-master: success setting UDMA2 on PIIX4 chip Creating DISK ad2 Creating DISK wd2 ad2: ATA-3 disk at ata1-master ad2: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 ad2: piomode=4 dmamode=2 udmamode=2 cblid=0 ad2: 4110MB [14848/9/63] at ata1-master UDMA33 ata0-slave: piomode=4 dmamode=2 udmamode=2 dmaflag=1 ata0-slave: success setting PIO4 on generic chip acd0: CDROM drive at ata0 as slave acd0: read 2412KB/s (2412KB/s), 256KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ata1-slave: piomode=3 dmamode=1 udmamode=-1 dmaflag=1 ata1-slave: timeout waiting for command=ef s=00 e=00 ata1-slave: failed setting PIO3 on generic chip ata1-slave: using PIO mode set by BIOS ata1-slave: CDROM device - NO DRIVER! Mounting root from ufs:/dev/ad0s2a ad0s1: type 0xc, start 63, end = 24579449, size 24579387 : OK ad0s2: type 0xa5, start 24579450, end = 39102209, size 14522760 : OK WARNING: /mnt was not properly dismounted start_init: trying /sbin/init ------- =_aaaaaaaaaa0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 5:34: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.6.200.230]) by hub.freebsd.org (Postfix) with ESMTP id 601BE37B423 for ; Mon, 30 Apr 2001 05:34:04 -0700 (PDT) (envelope-from mdharnois@home.com) Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id 6324014A11; Mon, 30 Apr 2001 07:34:22 -0500 (CDT) To: freebsd-current@freebsd.org Subject: ACPI: table load failed Keywords: table,signature,load From: Michael Harnois Date: 30 Apr 2001 07:34:21 -0500 Message-ID: <86bspea7n6.fsf@mharnois.workgroup.net> Lines: 15 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) XEmacs/21.5 (alfalfa) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this a bug? It's on an ASUS CUSL-2. ACPI debug layer 0x0 debug level 0x0 tbutils-0299: *** Warning: Invalid table signature found tbxface-0170: *** Error: AcpiLoadTables: Could not load RSDT: AE_BAD_SIGNATURE tbxface-0202: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATUR E ACPI: table load failed: AE_BAD_SIGNATURE Using $PIR table, 10 entries at 0xc00f1310 -- Michael D. Harnois mdharnois@home.com Redeemer Lutheran Church Washburn, Iowa There are four kinds of homicide: felonious, excusable, justifiable and praiseworthy... -- Ambrose Bierce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 8:25: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from pluto.senet.com.au (pluto.senet.com.au [203.56.239.150]) by hub.freebsd.org (Postfix) with ESMTP id 0096337B43F for ; Mon, 30 Apr 2001 08:25:01 -0700 (PDT) (envelope-from linux@senet.com.au) Received: from bytes4u.nodomain.yet (c1-p87.senet.com.au [203.56.237.88]) by pluto.senet.com.au (8.11.0/8.11.0) with ESMTP id f3UFQBZ88686 for ; Tue, 1 May 2001 00:56:11 +0930 (CST) (envelope-from linux@senet.com.au) Received: from localhost (linux@localhost) by bytes4u.nodomain.yet (8.11.1/8.11.1) with ESMTP id f3UFNaM00764 for ; Tue, 1 May 2001 00:53:37 +0930 (CST) (envelope-from linux@bytes4u.nodomain.yet) Date: Tue, 1 May 2001 00:53:33 +0930 (CST) From: Benjamin Close To: Subject: WinModem Support/Learning the kernel Internals Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, Is anyone looking into converting the Linux winmodem driver ( Lucent Technologies binary object file compiled together with the linux kernel serial driver) into a freebsd device? And another question, is there some documentation (other than the code) on how to use things like timers for devices, the kernel debugger, other useful kernel device development things :) Cheers, -- * Benjamin Close * Benjsc@senet.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 8:47:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.wanadoo.nl (smtp.wanadoo.nl [194.134.193.6]) by hub.freebsd.org (Postfix) with ESMTP id 49DC937B422 for ; Mon, 30 Apr 2001 08:47:32 -0700 (PDT) (envelope-from steveo@eircom.net) Received: from ams-gw.sohara.org (p616.vcu.wanadoo.nl [194.134.201.144]) by smtp.wanadoo.nl (8.11.2/8.11.2) with SMTP id f3UFlQq10374; Mon, 30 Apr 2001 17:47:26 +0200 (MET DST) Date: Mon, 30 Apr 2001 17:47:23 +0200 From: "Steve O'Hara-Smith" To: Benjamin Close Cc: freebsd-current@freebsd.org Subject: Re: WinModem Support/Learning the kernel Internals Message-Id: <20010430174723.616fe388.steveo@eircom.net> In-Reply-To: References: X-Mailer: Sylpheed version 0.4.63cvs15 (GTK+ 1.2.10; i386-unknown-freebsdelf4.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 May 2001 00:53:33 +0930 (CST) Benjamin Close wrote: BC> Hi All, BC> Is anyone looking into converting the Linux winmodem driver ( I'm pretty certain not, although there was a post on USENET recently by someone claiming to have their LT Winmodem running - I have asked for details. -- Optimal hardware acceleration for Windows PC (Mac). 9.81 m/s/s applied for (at least) 2s followed by impact with solid object. Optimal software upgrade FreeBSD (OS-X). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 9: 4: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.64.180.171]) by hub.freebsd.org (Postfix) with ESMTP id 7126A37B43C for ; Mon, 30 Apr 2001 09:04:00 -0700 (PDT) (envelope-from richw@wyattearp.stanford.edu) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id JAA45725; Mon, 30 Apr 2001 09:03:25 -0700 (PDT) (envelope-from richw) Date: Mon, 30 Apr 2001 09:03:25 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-current@freebsd.org Subject: Re: sio overflows Message-ID: <20010430154428.44707.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Georg Funk wrote: > I've recompiled my Kernel, and if I connect to the internet, > my console is flooded by lots of sio overflows (on sio1), > and my connection is very slow. They're probably "silo" overflows; "silo" (a word which refers to a tall, cylinder-shaped building for storing grain on a farm) is one name for the input buffer of a serial I/O chip (another name is "FIFO", an acronym for "First In, First Out"). Anyway . . . a few questions about your setup: Are you using a serial cable that is set up to use hardware (CTS/RTS) flow control? Is your modem configured to use hardware flow control? If the answer to either of these questions is "no", then you aren't using hardware flow control (even if you thought you were), and you are =very= likely to lose data. Fix the cable and/or modem settings. Is your serial port (sio1) identified as a "16550A" (the "A" suffix is very important here) when FreeBSD starts up? If not, then you're at risk of losing data at high communication rates (especially if your computer is not extremely fast). Get a new serial card with 16550A support. Are you running the X Window System (XFree86) on the same computer while you are connected to the Internet? If so, which version? Does the serial I/O problem go away if you get out of X and work directly with the plain-text console? There is a known problem with serial I/O and version 4 of XFree86 -- though this problem doesn't seem to exist with the XFree86 version (3.3.6) that is included by default in FreeBSD. If you are using XFree86-4 and aren't willing to go back to version 3.3.6, there may be a workaround for the serial I/O problem; go to http://www.FreeBSD.org/cgi/query-pr.cgi and look up PR #26261 for more details. Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 9:12:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 0169837B422 for ; Mon, 30 Apr 2001 09:12:41 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA46888; Mon, 30 Apr 2001 10:12:14 -0600 (MDT) (envelope-from ken) Date: Mon, 30 Apr 2001 10:12:14 -0600 From: "Kenneth D. Merry" To: Tomi Vainio - Sun Finland - Cc: freebsd-current@FreeBSD.ORG Subject: Re: camcontrol stop / restart broken Message-ID: <20010430101214.A46826@panzer.kdm.org> References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <15083.65379.523173.371122@ultrahot.Finland.Sun.COM>; from Tomi.Vainio@Sun.COM on Sun, Apr 29, 2001 at 02:47:47PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 29, 2001 at 14:47:47 +0300, Tomi Vainio - Sun Finland - wrote: > Kenneth D. Merry writes: > > > > Can you do the following: > > > > camcontrol stop da1 > > camcontrol tur da1 -v > > [ then you can start it back up with camcontrol start ] > > > > What I want to see here is the sense information coming back from the drive > > when it is spun down. > > > > The new error recovery code should be doing the same thing as the old error > > recovery code -- sending a start unit. For some reason it isn't doing the > > right thing, though. > > > cat:~(10)# camcontrol stop da1 > Unit stopped successfully > cat:~(11)# camcontrol tur da1 -v > Unit is not ready > (pass1:ahc0:0:2:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (pass1:ahc0:0:2:0): CAM Status: SCSI Status Error > (pass1:ahc0:0:2:0): SCSI Status: Check Condition > (pass1:ahc0:0:2:0): NOT READY asc:4,2 > (pass1:ahc0:0:2:0): Logical unit not ready, initializing cmd. required field replaceable unit: 2 This should be fixed as of rev 1.22 of scsi_all.c. There was an errant search and replace that caused the 'start' bit in the start/stop unit to always be set to 0 (stop). So automatic spinups wouldn't work, and 'camcontrol start' wouldn't work. > Also messages file is full of these: > > Apr 29 00:55:42 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue > Apr 29 00:55:43 cat last message repeated 26 times > Apr 29 00:57:43 cat last message repeated 359 times > Apr 29 01:07:43 cat last message repeated 1793 times > Apr 29 01:17:43 cat last message repeated 1794 times > Apr 29 01:27:43 cat last message repeated 1793 times > Apr 29 01:34:13 cat last message repeated 1122 times > Apr 29 01:34:13 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue > Apr 29 01:34:13 cat last message repeated 43 times > Apr 29 01:36:02 cat last message repeated 322 times I'd still like to know when these messages are cropping up. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 9:30:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id DDC2637B422 for ; Mon, 30 Apr 2001 09:30:41 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f3UGUVs13476; Mon, 30 Apr 2001 09:30:31 -0700 (PDT) (envelope-from obrien) Date: Mon, 30 Apr 2001 09:30:27 -0700 From: "David O'Brien" To: Sheldon Hearn Cc: Jeroen Ruigrok/Asmodai , current@freebsd.org Subject: Re: cp -u patch Message-ID: <20010430093027.A13451@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010426222132.B55566@daemon.ninth-circle.org> <13362.988617369@axl.fw.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <13362.988617369@axl.fw.uunet.co.za>; from sheldonh@uunet.co.za on Mon, Apr 30, 2001 at 09:56:09AM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 30, 2001 at 09:56:09AM +0200, Sheldon Hearn wrote: > > Question is, do we want to add this to our cp? > > Bleh. :-) Blah. > for i in `find /path/to/src`; do > if [ $i -nt /path/to/dst/$i ]; then > cp $i /path/to/dst/ > fi > done Do you also suggest we get rid of `more' as its functionality can be implimented using cat and sed? I personally find this option useful enough that I have to keep `gcp' around. I guess I got used to using a simular utility under M$-DOS and thus it makes sense to me. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 9:36:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id A3E8837B43F; Mon, 30 Apr 2001 09:36:17 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14uGej-0006ML-00; Mon, 30 Apr 2001 18:36:13 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id SAA25763; Mon, 30 Apr 2001 18:36:12 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 25654; Mon Apr 30 18:35:08 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14uGdg-0005g2-00; Mon, 30 Apr 2001 18:35:08 +0200 To: obrien@freebsd.org Cc: Jeroen Ruigrok/Asmodai , current@freebsd.org Subject: Re: cp -u patch In-reply-to: Your message of "Mon, 30 Apr 2001 09:30:27 MST." <20010430093027.A13451@dragon.nuxi.com> Date: Mon, 30 Apr 2001 18:35:08 +0200 Message-ID: <21825.988648508@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Apr 2001 09:30:27 MST, "David O'Brien" wrote: > Do you also suggest we get rid of `more' as its functionality can be > implimented using cat and sed? I personally find this option useful > enough that I have to keep `gcp' around. That's part of my concern. A lot of our feature creep seems to come from folks who have one particular thing they do a lot, but that lots of other folks don't. Personally, I've _never_ needed such a feature in cp(1) _once_ in the 3 or 4 years that I've been using BSD UNIX. That doesn't make me right. It just makes me skeptical. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 11:22:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (Postfix) with ESMTP id 8A75437B422 for ; Mon, 30 Apr 2001 11:22:18 -0700 (PDT) (envelope-from Tomi.Vainio@finland.sun.com) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA22924; Mon, 30 Apr 2001 11:22:13 -0700 (PDT) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.9) with ESMTP id VAA17652; Mon, 30 Apr 2001 21:22:05 +0300 (EET DST) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id VAA11660; Mon, 30 Apr 2001 21:22:02 +0300 (EEST) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15085.44361.206744.404170@ultrahot.Finland.Sun.COM> Date: Mon, 30 Apr 2001 21:22:01 +0300 To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: camcontrol stop / restart broken In-Reply-To: <20010430101214.A46826@panzer.kdm.org> References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> <20010430101214.A46826@panzer.kdm.org> X-Mailer: VM 6.92 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry writes: > > This should be fixed as of rev 1.22 of scsi_all.c. There was an errant > search and replace that caused the 'start' bit in the start/stop unit to > always be set to 0 (stop). So automatic spinups wouldn't work, and > 'camcontrol start' wouldn't work. > Thanks, I'll test this soon. > I'd still like to know when these messages are cropping up. > I scanned messages files and it seems to start ~2 hours after I have tried to spin up the disk first time. Apr 28 23:01:40 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 28 23:08:10 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 29 00:49:42 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate CCB, can't continue Apr 29 14:40:00 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 29 14:44:31 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 29 16:34:04 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 12:31:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id A768E37B53A for ; Mon, 30 Apr 2001 12:31:08 -0700 (PDT) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.11.2/8.11.2) with ESMTP id f3UJV1g16519; Mon, 30 Apr 2001 13:31:01 -0600 (MDT) (envelope-from lyndon@orthanc.ab.ca) Message-Id: <200104301931.f3UJV1g16519@orthanc.ab.ca> From: Lyndon Nerenberg Organization: The Frobozz Magic Homing Pigeon Company To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: ipfw: several equal rules under same number bug In-reply-to: Your message of "Sun, 29 Apr 2001 08:11:32 +0400." <20010429081131.A49808@nagual.pp.ru> Date: Mon, 30 Apr 2001 13:31:01 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Andrey" == Andrey A Chernov writes: Andrey> I think it is very contr-intuitive way, better action will Andrey> be "replace" if number is the same. Nonsense. This is what 'add' and 'delete' are for. Andrey> For example "ipfw delete" takes number as an argument, Andrey> what rule it suppose to delete, if the number is the same? Andrey> I.e. how can I delete specific rule if all have the same Andrey> number? Etc, etc. You can't, in which case you shouldn't use that facility. However, for those cases where you *do* want to act on a grouped set of rules, sharing rulesnumbers provides that ability. For example, I have a set of rules that count all in- and out-bound traffic to each IP address on an internal network. All of these are under a single rule number. This makes it trivial to do things like take periodic snapshots of the counters: ipfw show 2000 > $somefile; ipfw reset 2000 This takes care of 512 individual rule entries in one simple operation. Now if you want to make some useful changes to ipfw, find someone to commit the fix in bin/18550. And get rid of the needlessly verbose usage message ipfw spits out when it fails to parse a command. It would be a lot more useful if ipfw printed (only) the failed command. At least I might have a chance of seeing what the error is, instead of having the usage message cause any useful information to scroll off the console while the machine boots. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 14:50: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from mgate10.so-net.ne.jp (mgate10.so-net.ne.jp [210.139.254.157]) by hub.freebsd.org (Postfix) with ESMTP id A704F37B422 for ; Mon, 30 Apr 2001 14:49:55 -0700 (PDT) (envelope-from koya@math.yokohama-cu.ac.jp) Received: from mail.ya3.so-net.ne.jp (mspool11.so-net.ne.jp [210.139.248.11]) by mgate10.so-net.ne.jp (8.9.3/3.7W01041612) with ESMTP id GAA14588; Tue, 1 May 2001 06:48:42 +0900 (JST) Received: from localhost (p84ea86.ykhmpc00.ap.so-net.ne.jp [210.132.234.134]) by mail.ya3.so-net.ne.jp (8.9.3/3.7W01022316) with ESMTP id GAA17337; Tue, 1 May 2001 06:48:40 +0900 (JST) To: sheldonh@uunet.co.za Cc: Yoshihiro.Koya@math.yokohama-cu.ac.jp, freebsd-current@freebsd.org Subject: Re: A question about max_uid In-Reply-To: <12411.988616150@axl.fw.uunet.co.za> References: <20010427001555G.koya@pluto.math.yokohama-cu.ac.jp> <12411.988616150@axl.fw.uunet.co.za> From: Yoshihiro Koya X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010501065656R.koya@math.yokohama-cu.ac.jp> Date: Tue, 01 May 2001 06:56:56 +0900 X-Dispatcher: imput version 990905(IM130) Lines: 100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, From: Sheldon Hearn Subject: Re: A question about max_uid Date: Mon, 30 Apr 2001 09:35:50 +0200 > On Fri, 27 Apr 2001 00:15:55 +0900, Yoshihiro Koya wrote: > > > Currently, I have nobody (uid = 65534) account as a default account on > > my box. It might be easy to guess that the maximum is greater than > > 65533. My question is why such a restricion still remains. > > >From what I remember from my communication with Bruce Evans, the > "restrictions" (mostly unenforced" in our tree are there to protect old > software compiled to use 16-bit UID values. By allowing unsigned 32-bit > UID values in the system, you open the door for problems with software > that uses smaller UID values. Thanks for your reply. The following is extracted from /usr/src/usr.bin/chpass/field.c > /* ARGSUSED */ > int > p_uid(p, pw, ep) > char *p; > struct passwd *pw; > ENTRY *ep; > { > uid_t id; > char *np; > > if (!*p) { > warnx("empty uid field"); > return (1); > } > if (!isdigit(*p)) { > warnx("illegal uid"); > return (1); > } > errno = 0; > id = strtoul(p, &np, 10); > if (*np || (id == ULONG_MAX && errno == ERANGE)) { > warnx("illegal uid"); > return (1); > } > pw->pw_uid = id; > return (0); > } The system already seems to allow to use 32-bit UID. Indeed, I can add user with UID = 2147483647 = 0x7fffffff. # chpass foo /etc/pw.6mhYUR: 15 lines, 294 characters. chpass: 2147483647 > recommended max uid value (65535) chpass: updating the database... pwd_mkdb: 2147483647 > recommended max uid value (65535) chpass: done # cat /etc/passwd | grep foo foo:*:2147483647:20:some user:/tmp:/bin/csh BTW, I would like to point out that chpass command or pwd_mkdb command made some strange behaviour as follows: # chpass foo (I change the user foo's uid to 4294967295 = 0xffffffff here.) /etc/pw.qVOUaT: 15 lines, 294 characters. chpass: -1 > recommended max uid value (65535) chpass: updating the database... pwd_mkdb: -1 > recommended max uid value (65535) chpass: done # cat /etc/passwd | grep foo foo:*:4294967295:20:some user:/tmp:/bin/csh # cat /etc/master.passwd | grep foo foo:*:-1:20::0:0:some user:/tmp:/bin/csh It might be better to fix if possible. The user with minus UID has potential problems, and commands allow such minus uid are obviously wrong. Added to this, the above pwd_mkdb commands tells me that the recommended max uid value is 65535, which is a 16-bit UID, and this value 65535 differs from the restricted value of pw command. It might be better to unify such a recommended UID value on the system. Finally, I would like to mention my system on which I made the above tests. The system is FreeBSD vaio.my.domain 5.0-20010112-SNAP FreeBSD 5.0-20010112-SNAP #4: Mon Feb 26 15:32:20 JST 2001 root@vaio.my.domain:/usr/src/sys/compile/vaio i386 That system is somewhat old. But I guess that the current source codes of pw, chpass and pwd_mkdb aren't so far from those on my system, maybe. I cannot check the latest sources now because I'm on travel. Thanks for your reading. koya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 15: 1: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 86B3637B424 for ; Mon, 30 Apr 2001 15:01:00 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14uLiy-0000o8-00; Tue, 01 May 2001 00:00:56 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id AAA02661; Tue, 1 May 2001 00:00:55 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 2516; Tue May 1 00:00:02 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14uLi5-0006ln-00; Tue, 01 May 2001 00:00:01 +0200 To: Yoshihiro Koya Cc: freebsd-current@freebsd.org Subject: Re: A question about max_uid In-reply-to: Your message of "Tue, 01 May 2001 06:56:56 +0900." <20010501065656R.koya@math.yokohama-cu.ac.jp> Date: Tue, 01 May 2001 00:00:01 +0200 Message-ID: <26026.988668001@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 01 May 2001 06:56:56 +0900, Yoshihiro Koya wrote: > Hello, > chpass: updating the database... > pwd_mkdb: 2147483647 > recommended max uid value (65535) Gee, that message looks familiar. ;-) The warning was a concession that I implemented after discussions with BDE. The way we want to go for now is to have the entire system uid_t-clean (currently unsigned 32-bit) but to issue warnings from appropriate utilities when values that can't be represented by an unsigned short. > Added to this, the above pwd_mkdb commands tells me that > the recommended max uid value is 65535, which is > a 16-bit UID, and this value 65535 differs from the restricted value > of pw command. > It might be better to unify such a recommended UID value on the > system. Absolutely. If you have the time, that'd be great! Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 16:13:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (Postfix) with ESMTP id B230637B423 for ; Mon, 30 Apr 2001 16:13:22 -0700 (PDT) (envelope-from Tomi.Vainio@finland.sun.com) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA29990; Mon, 30 Apr 2001 16:13:16 -0700 (PDT) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.9) with ESMTP id CAA08924; Tue, 1 May 2001 02:13:08 +0300 (EET DST) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id CAA11830; Tue, 1 May 2001 02:13:05 +0300 (EEST) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15085.61825.708944.271219@ultrahot.Finland.Sun.COM> Date: Tue, 1 May 2001 02:13:05 +0300 To: Benjamin Close Cc: Subject: WinModem Support/Learning the kernel Internals In-Reply-To: References: X-Mailer: VM 6.92 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Benjamin Close writes: > Is anyone looking into converting the Linux winmodem driver ( > Lucent Technologies binary object file compiled together with the linux > kernel serial driver) into a freebsd device? > Please check http://www.geocities.com/wtnbkysh/ . It should work under 4.2R. There is also some 5.0C patches but still some problems probably with interrupts. Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: port 0x1c00-0x1cff,0x2f8-0x2ff mem 0xffefff00-0xffefffff irq 11 at device 2.0 on pci0 Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: using SHARED IRQ. Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: unable to activate interrupt in fast mode - using normal modeltmdm0: type Virtual 16550A Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 22:26:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.wanadoo.nl (smtp.wanadoo.nl [194.134.193.6]) by hub.freebsd.org (Postfix) with ESMTP id 4F57337B423 for ; Mon, 30 Apr 2001 22:26:45 -0700 (PDT) (envelope-from steveo@eircom.net) Received: from ams-gw.sohara.org (p1301.vcu.wanadoo.nl [194.134.170.26]) by smtp.wanadoo.nl (8.11.2/8.11.2) with SMTP id f415Qcq28174; Tue, 1 May 2001 07:26:38 +0200 (MET DST) Date: Tue, 1 May 2001 07:26:37 +0200 From: "Steve O'Hara-Smith" To: Tomi.Vainio@Sun.COM Cc: linux@senet.com.au, freebsd-current@FreeBSD.ORG Subject: Re: WinModem Support/Learning the kernel Internals Message-Id: <20010501072637.2689e886.steveo@eircom.net> In-Reply-To: <15085.61825.708944.271219@ultrahot.Finland.Sun.COM> References: <15085.61825.708944.271219@ultrahot.Finland.Sun.COM> X-Mailer: Sylpheed version 0.4.63cvs15 (GTK+ 1.2.10; i386-unknown-freebsdelf4.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 May 2001 02:13:05 +0300 Tomi Vainio - Sun Finland - wrote: TF> Please check http://www.geocities.com/wtnbkysh/ . It should work I stand corrected - and impressed. -- Optimal hardware acceleration for Windows PC (Mac). 9.81 m/s/s applied for (at least) 2s followed by impact with solid object. Optimal software upgrade FreeBSD (OS-X). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 30 22:38:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id BBC3737B43C for ; Mon, 30 Apr 2001 22:38:49 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id E6157193BC; Tue, 1 May 2001 00:38:48 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.11.3/8.9.3) id f415cmQ00855; Tue, 1 May 2001 00:38:48 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Tue, 1 May 2001 00:38:48 -0500 From: "Jacques A. Vidrine" To: Tomi Vainio - Sun Finland - Cc: Benjamin Close , freebsd-current@FreeBSD.ORG Subject: Re: WinModem Support/Learning the kernel Internals Message-ID: <20010501003848.A734@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , Tomi Vainio - Sun Finland - , Benjamin Close , freebsd-current@FreeBSD.ORG References: <15085.61825.708944.271219@ultrahot.Finland.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15085.61825.708944.271219@ultrahot.Finland.Sun.COM>; from Tomi.Vainio@Sun.COM on Tue, May 01, 2001 at 02:13:05AM +0300 X-Url: http://www.nectar.com/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 01, 2001 at 02:13:05AM +0300, Tomi Vainio - Sun Finland - wrote: > Benjamin Close writes: > > Is anyone looking into converting the Linux winmodem driver ( > > Lucent Technologies binary object file compiled together with the linux > > kernel serial driver) into a freebsd device? > > > Please check http://www.geocities.com/wtnbkysh/ . It should work > under 4.2R. There is also some 5.0C patches but still some problems > probably with interrupts. > > Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: port 0x1c00-0x1cff,0x2f8-0x2ff mem 0xffefff00-0xffefffff irq 11 at device 2.0 on pci0 > Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: using SHARED IRQ. > Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: unable to activate interrupt in fast mode - using normal modeltmdm0: type Virtual 16550A Also I've used PPP with the following on a ThinkPad X20 running 4.3-RELEASE + wtnbkysh patches: ltmdm0: port 0x1810-0x1817 mem 0xf4011000-0xf4011fff irq 9 at device 10.1 on pci 0 ltmdm0: using SHARED IRQ. ltmdm0: type Virtual 16550A This is on the EtherJet Mini-PCI card (combo: fxp + ltmdm). Cheers, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 6:56:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 65D6E37B422 for ; Tue, 1 May 2001 06:56:41 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f41DuGf47179; Tue, 1 May 2001 09:56:18 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 1 May 2001 09:56:16 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Sheldon Hearn Cc: Yoshihiro Koya , freebsd-current@freebsd.org Subject: Re: A question about max_uid In-Reply-To: <26026.988668001@axl.fw.uunet.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Note that you have to be careful to avoid the value of VNOVAL (-1) for a uid or a gid, or you'll run into trouble with the VFS layer; this is arguably due to poor design of VFS. NFSv2 also had problems with reserved values (as the NFSv2 interface greatly resembles the VFS interface, for the obvious reasons), but NFSv3 correct most of these. I'd really like to get VFS's overloading of vop_setattr() un-overloaded someday, perhaps by introducing an EXTATTR_NAMESPACE_UFS and having the changes be submitted via vop_setextattr(), but there's probably some non-atomicity concerns there that would have to be addressed. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Tue, 1 May 2001, Sheldon Hearn wrote: > On Tue, 01 May 2001 06:56:56 +0900, Yoshihiro Koya wrote: > > > Hello, > > chpass: updating the database... > > pwd_mkdb: 2147483647 > recommended max uid value (65535) > > Gee, that message looks familiar. ;-) > > The warning was a concession that I implemented after discussions with > BDE. The way we want to go for now is to have the entire system > uid_t-clean (currently unsigned 32-bit) but to issue warnings from > appropriate utilities when values that can't be represented by an > unsigned short. > > > Added to this, the above pwd_mkdb commands tells me that > > the recommended max uid value is 65535, which is > > a 16-bit UID, and this value 65535 differs from the restricted value > > of pw command. > > It might be better to unify such a recommended UID value on the > > system. > > Absolutely. If you have the time, that'd be great! > > Ciao, > Sheldon. > > 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 Tue May 1 9: 9:36 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 SMTP id 9384D37B422 for ; Tue, 1 May 2001 09:09:34 -0700 (PDT) (envelope-from tomdean@speakeasy.org) Received: (qmail 96581 invoked from network); 1 May 2001 16:09:34 -0000 Received: from unknown (HELO celebris.tddhome) ([64.81.20.229]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 1 May 2001 16:09:34 -0000 Received: (from tomdean@localhost) by celebris.tddhome (8.11.3/8.11.1) id f41G9X555662; Tue, 1 May 2001 09:09:33 -0700 (PDT) (envelope-from tomdean@speakeasy.org) Date: Tue, 1 May 2001 09:09:33 -0700 (PDT) Message-Id: <200105011609.f41G9X555662@celebris.tddhome> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: freebsd-current@FreeBSD.ORG Subject: Strangeness with newsyslog/wtmp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I notice that my /var/log/wtmp has strange renewal times. I don't know when it was not like this. newsyslog.conf is set to renew this once per week. What is causing this? # ls -l /var/log/wtmp* -rw-rw-r-- 1 root wheel 0 Apr 29 12:00 /var/log/wtmp -rw-rw-r-- 1 root wheel 27 Apr 27 16:00 /var/log/wtmp.0.gz -rw-rw-r-- 1 root wheel 27 Apr 22 12:00 /var/log/wtmp.1.gz -rw-rw-r-- 1 root wheel 27 Apr 20 16:00 /var/log/wtmp.2.gz -rw-rw-r-- 1 root wheel 27 Apr 15 12:00 /var/log/wtmp.3.gz -rw-rw-r-- 1 root wheel 244 Apr 13 15:52 /var/log/wtmp.4.gz -rw-rw-r-- 1 root wheel 176 Apr 8 12:12 /var/log/wtmp.5.gz -rw-rw-r-- 1 root wheel 148 Apr 3 10:51 /var/log/wtmp.6.gz -rw-rw-r-- 1 root wheel 280 Mar 30 21:16 /var/log/wtmp.7.gz It looks like there are several cycles of renewal, Apr 8, 15, 22, 29 & Apr 13, 20, 27. # grep wtmp /etc/newsyslog.conf /var/log/wtmp 644 7 * 168 ZB # uptime 8:57AM up 17 days, 17:06, 5 users, load averages: 0.07, 0.05, 0.02 I am running -current of April 12. # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0:\ Thu Apr 12 19:30:44 PDT 2001\ root@celebris:/usr/src/sys/compile/CELEBRIS i386 tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 11:46:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id D736237B43C for ; Tue, 1 May 2001 11:46:10 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA55614; Tue, 1 May 2001 12:46:08 -0600 (MDT) (envelope-from ken) Date: Tue, 1 May 2001 12:46:08 -0600 From: "Kenneth D. Merry" To: Tomi Vainio - Sun Finland - Cc: freebsd-current@FreeBSD.ORG Subject: Re: camcontrol stop / restart broken Message-ID: <20010501124608.A55572@panzer.kdm.org> References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> <20010430101214.A46826@panzer.kdm.org> <15085.44361.206744.404170@ultrahot.Finland.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <15085.44361.206744.404170@ultrahot.Finland.Sun.COM>; from Tomi.Vainio@Sun.COM on Mon, Apr 30, 2001 at 09:22:01PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 30, 2001 at 21:22:01 +0300, Tomi Vainio - Sun Finland - wrote: > Kenneth D. Merry writes: > > > > This should be fixed as of rev 1.22 of scsi_all.c. There was an errant > > search and replace that caused the 'start' bit in the start/stop unit to > > always be set to 0 (stop). So automatic spinups wouldn't work, and > > 'camcontrol start' wouldn't work. > > > Thanks, I'll test this soon. > > > I'd still like to know when these messages are cropping up. > > > I scanned messages files and it seems to start ~2 hours after I have tried > to spin up the disk first time. > > Apr 28 23:01:40 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack > Apr 28 23:08:10 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack > Apr 29 00:49:42 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate CCB, can't continue > > Apr 29 14:40:00 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack > Apr 29 14:44:31 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack > Apr 29 16:34:04 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue > Hmm. Well, I definitely haven't seen this before. The only thing I can figure is that we got into some sort of infinite rescan loop. I don't know how spinning up the disk (or trying to) would trigger a rescan. If it happens again, could you try to drop into the debugger and get a stack trace? If the stack trace doesn't show anything, perhaps setting a breakpoint in xpt_scan_lun would work. (You may want to have remote gdb setup for that.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 12: 3:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by hub.freebsd.org (Postfix) with ESMTP id A446737B423 for ; Tue, 1 May 2001 12:03:47 -0700 (PDT) (envelope-from tomppa@finland.sun.com) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA09713; Tue, 1 May 2001 12:03:44 -0700 (PDT) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.10.2+Sun/8.10.2/ENSMAIL,v2.1p1) with ESMTP id f41J3ek00481; Tue, 1 May 2001 22:03:40 +0300 (EEST) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id WAA12229; Tue, 1 May 2001 22:03:37 +0300 (EEST) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15087.2185.477972.105555@ultrahot.Finland.Sun.COM> Date: Tue, 1 May 2001 22:03:37 +0300 To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: camcontrol stop / restart broken In-Reply-To: <20010501124608.A55572@panzer.kdm.org> References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> <20010430101214.A46826@panzer.kdm.org> <15085.44361.206744.404170@ultrahot.Finland.Sun.COM> <20010501124608.A55572@panzer.kdm.org> X-Mailer: VM 6.92 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry writes: > > Hmm. Well, I definitely haven't seen this before. The only thing I can > figure is that we got into some sort of infinite rescan loop. I don't know > how spinning up the disk (or trying to) would trigger a rescan. > My system has been up and running 21 hours since world rebuild and reboot. During this time I have stopped and started disk multiple times and these errors are history now. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 12: 5:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 441ED37B424 for ; Tue, 1 May 2001 12:05:34 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA55842; Tue, 1 May 2001 13:05:32 -0600 (MDT) (envelope-from ken) Date: Tue, 1 May 2001 13:05:32 -0600 From: "Kenneth D. Merry" To: Tomi Vainio - Sun Finland - Cc: freebsd-current@FreeBSD.ORG Subject: Re: camcontrol stop / restart broken Message-ID: <20010501130532.A55823@panzer.kdm.org> References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> <20010430101214.A46826@panzer.kdm.org> <15085.44361.206744.404170@ultrahot.Finland.Sun.COM> <20010501124608.A55572@panzer.kdm.org> <15087.2185.477972.105555@ultrahot.Finland.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <15087.2185.477972.105555@ultrahot.Finland.Sun.COM>; from Tomi.Vainio@Sun.COM on Tue, May 01, 2001 at 10:03:37PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 01, 2001 at 22:03:37 +0300, Tomi Vainio - Sun Finland - wrote: > Kenneth D. Merry writes: > > > > Hmm. Well, I definitely haven't seen this before. The only thing I can > > figure is that we got into some sort of infinite rescan loop. I don't know > > how spinning up the disk (or trying to) would trigger a rescan. > > > My system has been up and running 21 hours since world rebuild and > reboot. During this time I have stopped and started disk multiple > times and these errors are history now. Ahh, cool. Well, if you see them again, let me know. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 12:15:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id D243A37B423 for ; Tue, 1 May 2001 12:15:34 -0700 (PDT) (envelope-from peter@wemm.org) 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 f41JFYM91100 for ; Tue, 1 May 2001 12:15:34 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 96E1A380C for ; Tue, 1 May 2001 12:15:34 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: current@freebsd.org Subject: HEADS UP! bad bug in -current. Date: Tue, 01 May 2001 12:15:34 -0700 From: Peter Wemm Message-Id: <20010501191534.96E1A380C@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any -current kernel built over the weekend is a likely victim of this bug. In a nutshell, it will eat your root filesystem at the very least, leaving you with maybe one or two files in /lost+found. spec_vnops.c rev 1.156 is should be avoided at all costs. BEWARE: there are some snapshots on current.freebsd.org with this bug. They will self destruct after install. ------- Forwarded Messages phk 2001/04/29 04:48:42 PDT Modified files: ...[other files in commit trimmed] sys/miscfs/specfs spec_vnops.c Log: Add a vop_stdbmap(), and make it part of the default vop vector. Make 7 filesystems which don't really know about VOP_BMAP rely on the default vector, rather than more or less complete local vop_nopbmap() implementations. Revision Changes Path 1.156 +1 -2 src/sys/miscfs/specfs/spec_vnops.c ------- Message 2 bde 2001/04/30 07:35:37 PDT Modified files: sys/miscfs/specfs spec_vnops.c Log: Backed out previous commit. It cause massive filesystem corruption, not to mention a compile-time warning about the critical function becoming unused, by replacing spec_bmap() with vop_stdbmap(). ntfs seems to have the same bug. The factor for converting specfs block numbers to physical block numbers is 1, but vop_stdbmap() uses the bogus factor btodb(ap->a_vp->v_mount->mnt_stat.f_iosize), which is 16 for ffs with the default block size of 8K. This factor is bogus even for vop_stdbmap() -- the correct factor is related to the filesystem blocksize which is not necessarily the same to the optimal i/o size. vop_stdbmap() was apparently cloned from nfs where these sizes happen to be the same. There may also be a problem with a_vp->v_mount being null. spec_bmap() still checks for this, but I think the checks in specfs are dead code which used to support block devices. Revision Changes Path 1.157 +2 -1 src/sys/miscfs/specfs/spec_vnops.c ------- End of Forwarded Messages To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 13:38:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id D8DFF37B423 for ; Tue, 1 May 2001 13:38:47 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from salmon.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 1 May 2001 21:38:47 +0100 (BST) To: "Thomas D. Dean" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Strangeness with newsyslog/wtmp In-Reply-To: Your message of "Tue, 01 May 2001 09:09:33 PDT." <200105011609.f41G9X555662@celebris.tddhome> Date: Tue, 01 May 2001 21:38:45 +0100 From: Ian Dowse Message-ID: <200105012138.aa83492@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200105011609.f41G9X555662@celebris.tddhome>, "Thomas D. Dean" write s: >I notice that my /var/log/wtmp has strange renewal times. I don't >know when it was not like this. newsyslog.conf is set to renew this >once per week. What is causing this? -rw-rw-r-- 1 root wheel 27 Apr 15 12:00 /var/log/wtmp.3.gz -rw-rw-r-- 1 root wheel 244 Apr 13 15:52 /var/log/wtmp.4.gz -rw-rw-r-- 1 root wheel 176 Apr 8 12:12 /var/log/wtmp.5.gz -rw-rw-r-- 1 root wheel 148 Apr 3 10:51 /var/log/wtmp.6.gz -rw-rw-r-- 1 root wheel 280 Mar 30 21:16 /var/log/wtmp.7.gz Gzip by default preserves the last-modified time of a file when gzipping, so these times are actually the times at which the wtmp file was previously modified before being rotated. Try "ls -lc", which will show up the rotation time. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 13:57:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 972A537B422; Tue, 1 May 2001 13:57:53 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA56670; Tue, 1 May 2001 14:57:52 -0600 (MDT) (envelope-from ken) Date: Tue, 1 May 2001 14:57:52 -0600 From: "Kenneth D. Merry" To: current@FreeBSD.org Cc: jlemon@FreeBSD.org Subject: panic in fxp driver Message-ID: <20010501145752.B56581@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm updating a machine (Pentium II 350, 128MB RAM) to -current, and ran into this panic in the fxp driver. Sources are from today (5/1/2001). I believe the chip is an 82557. I compiled and installed a kernel, rebooted and started running an installworld over NFS. The installworld stopped here: ===> usr.bin/basename install -c -s -o root -g wheel -m 555 basename /usr/bin install -c -o root -g wheel -m 444 basename.1.gz /usr/share/man/man1 /usr/share/man/man1/dirname.1.gz -> /usr/share/man/man1/basename.1.gz ===> usr.bin/biff install -c -s -o root -g wheel -m 555 biff /usr/bin install -c -o root -g wheel -m 444 biff.1.gz /usr/share/man/man1 ===> usr.bin/brandelf install -c -s -o root -g wheel -m 555 brandelf /usr/bin The stack trace: (kgdb) where #0 m_freem (m=0xc0b84d00) at ../../kern/uipc_mbuf.c:572 #1 0xc018ef76 in fxp_intr (xsc=0xc1372800) at ../../dev/fxp/if_fxp.c:993 #2 0xc01fe533 in ithread_loop (arg=0xc136be80) at ../../kern/kern_intr.c:517 #3 0xc01fd0e0 in fork_exit (callout=0xc01fe1c8 , arg=0xc136be80, frame=0xc926ffa8) at ../../kern/kern_fork.c:731 It blew up on line 572 of uipc_mbuf: (kgdb) list 567 /* 568 * we do need to check non-first mbuf, since some of existing 569 * code does not call M_PREPEND properly. 570 * (example: call to bpf_mtap from drivers) 571 */ 572 if ((m->m_flags & M_PKTHDR) != 0 && m->m_pkthdr.aux) { 573 m_freem(m->m_pkthdr.aux); 574 m->m_pkthdr.aux = NULL; 575 } 576 MFREE(m, n); It looks like the mbuf pointer is bogus: (kgdb) print m $2 = (struct mbuf *) 0xf0006b00 (kgdb) print *m Cannot access memory at address 0xf0006b00. Although in the next frame up the stack, the mbuf pointer looks okay: (kgdb) up #1 0xc018ef76 in fxp_intr (xsc=0xc1372800) at ../../dev/fxp/if_fxp.c:993 (kgdb) print txp->mb_head $3 = (struct mbuf *) 0xc0b84d00 (kgdb) print *txp->mb_head $4 = {m_hdr = {mh_next = 0xc0b8ea00, mh_nextpkt = 0x0, mh_data = 0xc0b84dd6 "", mh_len = 42, mh_type = 0, mh_flags = 2}, M_dat = { MH = {MH_pkthdr = {rcvif = 0x0, len = 178, header = 0xcb90adb, csum_flags = 0, csum_data = 6, aux = 0x0}, MH_dat = {MH_ext = { ext_buf = 0x1f943403
, ext_free = 0, ext_args = 0x2000000, ext_size = 2743468288, ref_cnt = 0x3000000, ext_type = 50331648}, MH_databuf = "\0034\224\037\000\000\000\000\000\000\000\002\000\001\206£\000\000\000\003\000\000\000\003\000\000\000\001\000\000\0000", '\000' , "\a\000\000\000\000\000\000\000\002\000\000\000\003\000\000\000\004\000\000\000\005\000\000\000\024\000\000\000\037\000\000\000\000\000\000\000\000C\235(J¡àaëÏ\220V¦ý\037\002#¹­Î3+\005\233üñôç\036D\a\212wõR, "°Ð{Ñ\036\000 É³¼G\b\000E\000\000¤¸\233\000\000@\021RÅ¢>\2256¢>\2255\003õ\b\001\000\220ÜC"}}, M_databuf = "\000\000\000\000²\000\000\000Û\n¹\f\000\000\000\000\006\000\000\000\000\000\000\000\0034\224\037\000\000\000\000\000\000\000\002\000\001\206£\000\000\000\003\000\000\000\003\000\000\000\001\000\000\0000", '\000' , "\a\000\000\000\000\000\000\000\002\000\000\000\003\000\000\000\004\000\000\000\005\000\000\000\024\000\000\000\037\000\000\000\000\000\000\000\000C\235(J¡àaëÏ\220V¦ý\037\002#¹­Î3+\005\233üñôç\036D\a\212wõR, "°Ð{Ñ\036\000 É³¼G\b\000E\000\000¤¸\233"...}} (kgdb) list 988 989 for (txp = sc->cbl_first; sc->tx_queued && 990 (txp->cb_status & FXP_CB_STATUS_C) != 0; 991 txp = txp->next) { 992 if (txp->mb_head != NULL) { 993 m_freem(txp->mb_head); 994 txp->mb_head = NULL; 995 } 996 sc->tx_queued--; 997 } (kgdb) So I'm not sure what's going on here. Anyone seen anything like this recently? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 14:16:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 5608837B422; Tue, 1 May 2001 14:16:33 -0700 (PDT) (envelope-from peter@wemm.org) 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 f41LGXM91453; Tue, 1 May 2001 14:16:33 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 2369E380C; Tue, 1 May 2001 14:16:33 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: "Kenneth D. Merry" Cc: current@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: panic in fxp driver In-Reply-To: <20010501145752.B56581@panzer.kdm.org> Content-Transfer-Encoding: 8bit Date: Tue, 01 May 2001 14:16:33 -0700 From: Peter Wemm Message-Id: <20010501211633.2369E380C@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > It looks like the mbuf pointer is bogus: > > (kgdb) print m > $2 = (struct mbuf *) 0xf0006b00 > (kgdb) print *m > Cannot access memory at address 0xf0006b00. > > Although in the next frame up the stack, the mbuf pointer looks okay: > > (kgdb) up > #1 0xc018ef76 in fxp_intr (xsc=0xc1372800) at ../../dev/fxp/if_fxp.c:993 > (kgdb) print txp->mb_head This is a well known problem, and a real gotcha. kgdb does not know how and when variables are stored in registers. It *always* reads the stack values, not the registers. You can disassemble the code and find out what register is currently holding 'm' and either look at the current registers or the trap frame if there is one. I suspect we are missing some magic in our kernel interface code for gdb and it is not running in 'gcc generated .stabs' mode. On the other hand, you might try using dwarf2 debugging, that is pretty complete. 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 Tue May 1 14:23:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 15B5137B423; Tue, 1 May 2001 14:23:31 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f41LNHw51838; Tue, 1 May 2001 14:23:17 -0700 (PDT) (envelope-from obrien) Date: Tue, 1 May 2001 14:23:17 -0700 From: "David O'Brien" To: Peter Wemm Cc: "Kenneth D. Merry" , current@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: panic in fxp driver Message-ID: <20010501142317.A51637@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010501145752.B56581@panzer.kdm.org> <20010501211633.2369E380C@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: <20010501211633.2369E380C@overcee.netplex.com.au>; from peter@wemm.org on Tue, May 01, 2001 at 02:16:33PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 01, 2001 at 02:16:33PM -0700, Peter Wemm wrote: > On the other hand, > you might try using dwarf2 debugging, that is pretty complete. And what we'll be using when GCC 3.0 is imported. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 15:32:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 6C20237B422 for ; Tue, 1 May 2001 15:32:46 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id SAA12697; Tue, 1 May 2001 18:32:09 -0400 (EDT) Date: Tue, 1 May 2001 18:32:09 -0400 (EDT) From: Daniel Eischen To: current@freebsd.org Subject: Rfork'd threads, signals, and LDTs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why are %fs and %gs set back to default (_udata_sel) when posting signals? I am planning on using %fs for TSD/KSD and want it to be valid in signal handlers. A test program is at: http://people.freebsd.org/~deischen/test_tsd.c Compile it with -DDEBUG on an unpatched kernel to show more details. This following seems to fix it. Any reason it would cause problems? Index: machdep.c =================================================================== RCS file: /opt/FreeBSD/cvs/src/sys/i386/i386/machdep.c,v retrieving revision 1.447 diff -u -r1.447 machdep.c --- machdep.c 2001/04/27 19:28:19 1.447 +++ machdep.c 2001/05/01 22:20:52 @@ -745,8 +745,6 @@ regs->tf_cs = _ucodesel; regs->tf_ds = _udatasel; regs->tf_es = _udatasel; - regs->tf_fs = _udatasel; - load_gs(_udatasel); regs->tf_ss = _udatasel; } -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 16:24: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from draco.over-yonder.net (draco.over-yonder.net [198.78.58.61]) by hub.freebsd.org (Postfix) with ESMTP id A248137B43C for ; Tue, 1 May 2001 16:23:59 -0700 (PDT) (envelope-from gh@over-yonder.net) Received: by draco.over-yonder.net (Postfix, from userid 1012) id 454F462D0A; Tue, 1 May 2001 18:23:59 -0500 (CDT) Date: Tue, 1 May 2001 18:23:59 -0500 From: GH To: current@freebsd.org Subject: Re: HEADS UP! bad bug in -current. Message-ID: <20010501182359.A22707@over-yonder.net> References: <20010501191534.96E1A380C@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: <20010501191534.96E1A380C@overcee.netplex.com.au>; from peter@wemm.org on Tue, May 01, 2001 at 12:15:34PM -0700 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 01, 2001 at 12:15:34PM -0700, some SMTP stream spewed forth: > Any -current kernel built over the weekend is a likely victim of this bug. > In a nutshell, it will eat your root filesystem at the very least, leaving > you with maybe one or two files in /lost+found. spec_vnops.c rev 1.156 > is should be avoided at all costs. > > BEWARE: there are some snapshots on current.freebsd.org with this bug. They > will self destruct after install. > > ------- Forwarded Messages *snip* Say, FreeBSD is usually pretty safe, even in CURRENT. Has something near this magnitude of Really Bad Stuffage snuck into the codebase before? (This is just for my personal knowledge. I don't remeber anything this bad in recent times.) gh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 16:57: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 20A7537B422 for ; Tue, 1 May 2001 16:57:04 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f41Nus332880; Tue, 1 May 2001 16:56:54 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: grasshacker@over-yonder.net Cc: current@FreeBSD.ORG Subject: Re: HEADS UP! bad bug in -current. In-Reply-To: <20010501182359.A22707@over-yonder.net> References: <20010501191534.96E1A380C@overcee.netplex.com.au> <20010501182359.A22707@over-yonder.net> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010501165654K.jkh@osd.bsdi.com> Date: Tue, 01 May 2001 16:56:54 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Say, FreeBSD is usually pretty safe, even in CURRENT. > Has something near this magnitude of Really Bad Stuffage snuck into the > codebase before? No, it's not common, and it generally takes a Dane swinging something sharp to inflict quite this much damage on our user base. ;-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 16:58:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id CC2A537B423 for ; Tue, 1 May 2001 16:58:50 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 399E510F40F; Tue, 1 May 2001 18:58:55 -0500 (CDT) Message-ID: <021701c0d29a$a9dcf2c0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: , "Jordan Hubbard" Cc: References: <20010501191534.96E1A380C@overcee.netplex.com.au><20010501182359.A22707@over-yonder.net> <20010501165654K.jkh@osd.bsdi.com> Subject: Re: HEADS UP! bad bug in -current. Date: Tue, 1 May 2001 18:58:48 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It was almost like that dirpref problem I ran into a few weeks ago, I upgraded from -stable to -current and I had to reinstall because of it, but this usually doesn't happen. ----- Original Message ----- From: "Jordan Hubbard" To: Cc: Sent: Tuesday, May 01, 2001 6:56 PM Subject: Re: HEADS UP! bad bug in -current. > > Say, FreeBSD is usually pretty safe, even in CURRENT. > > Has something near this magnitude of Really Bad Stuffage snuck into the > > codebase before? > > No, it's not common, and it generally takes a Dane swinging something > sharp to inflict quite this much damage on our user base. ;-) > > - Jordan > > 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 Tue May 1 17: 1:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 55A4837B424 for ; Tue, 1 May 2001 17:01:31 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4201IG16503; Tue, 1 May 2001 17:01:18 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010501165654K.jkh@osd.bsdi.com> Date: Tue, 01 May 2001 17:00:38 -0700 (PDT) From: John Baldwin To: Jordan Hubbard Subject: Re: HEADS UP! bad bug in -current. Cc: current@FreeBSD.org, grasshacker@over-yonder.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 01-May-01 Jordan Hubbard wrote: >> Say, FreeBSD is usually pretty safe, even in CURRENT. >> Has something near this magnitude of Really Bad Stuffage snuck into the >> codebase before? > > No, it's not common, and it generally takes a Dane swinging something > sharp to inflict quite this much damage on our user base. ;-) > > - Jordan I dunno, certain Berkeley professors have pretty close as well. ;) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 17:10: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-27.dsl.lsan03.pacbell.net [63.207.60.27]) by hub.freebsd.org (Postfix) with ESMTP id 7680C37B422 for ; Tue, 1 May 2001 17:10:00 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5C0A666B75; Tue, 1 May 2001 17:09:59 -0700 (PDT) Date: Tue, 1 May 2001 17:09:59 -0700 From: Kris Kennaway To: GH Cc: current@freebsd.org Subject: Re: HEADS UP! bad bug in -current. Message-ID: <20010501170959.B13736@xor.obsecurity.org> References: <20010501191534.96E1A380C@overcee.netplex.com.au> <20010501182359.A22707@over-yonder.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="s/l3CgOIzMHHjg/5" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010501182359.A22707@over-yonder.net>; from grasshacker@over-yonder.net on Tue, May 01, 2001 at 06:23:59PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --s/l3CgOIzMHHjg/5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 01, 2001 at 06:23:59PM -0500, GH wrote: > On Tue, May 01, 2001 at 12:15:34PM -0700, some SMTP stream spewed forth:= =20 > > Any -current kernel built over the weekend is a likely victim of this b= ug. > > In a nutshell, it will eat your root filesystem at the very least, leav= ing > > you with maybe one or two files in /lost+found. spec_vnops.c rev 1.156 > > is should be avoided at all costs. > >=20 > > BEWARE: there are some snapshots on current.freebsd.org with this bug. = They > > will self destruct after install. > >=20 > > ------- Forwarded Messages > *snip* >=20 > Say, FreeBSD is usually pretty safe, even in CURRENT. > Has something near this magnitude of Really Bad Stuffage snuck into the > codebase before? >=20 > (This is just for my personal knowledge. I don't remeber anything this > bad in recent times.) It happens from time to time. VM was really unstable for a period a few years ago (3.0-CURRENT timeframe) when John Dyson was dinking with it. This is why you need to be extra-careful when running -current on systems with data you care about :-) Kris --s/l3CgOIzMHHjg/5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE671BWWry0BWjoQKURAnAEAKDjIeDEWVK23xfGLoR3RkKEVFyNmQCgmeMb VfrQRZd+xVKcFHP4+G+MJCs= =75Bc -----END PGP SIGNATURE----- --s/l3CgOIzMHHjg/5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 18:45:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from areilly.bpc-users.org (CPE-144-132-234-126.nsw.bigpond.net.au [144.132.234.126]) by hub.freebsd.org (Postfix) with SMTP id E5C3637B423 for ; Tue, 1 May 2001 18:45:15 -0700 (PDT) (envelope-from areilly@bigpond.net.au) Received: (qmail 1940 invoked by uid 1000); 2 May 2001 01:45:16 -0000 From: "Andrew Reilly" Date: Wed, 2 May 2001 11:45:16 +1000 To: Rik van Riel Cc: Bruce Evans , Cejka Rudolf , freebsd-current@FreeBSD.ORG Subject: Re: Experiences with new dir allocation on FFS? Message-ID: <20010502114516.C1059@gurney.reilly.home> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from riel@conectiva.com.br on Sun, Apr 29, 2001 at 12:50:08AM -0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 29, 2001 at 12:50:08AM -0300, Rik van Riel wrote: > For the people wanting to turn on write caching ... it WILL break > the write ordering needed by softupdates and journaling filesystems, > so don't do it unless you know what you're doing. > > I guess it would be better to do this kind of write caching at the > kernel level, because the OS has a much better idea of when to write > which data to platter than a harddisk can ever have. However, on ATA without tagged queuing, turning off write caching (on my own UDMA33 system) reduces write performance by a factor of two. From 12MB/s to 6MB/s on my system. That is almost certainly because (a) ATA limits individual transfers to 64k, and (b) you can't get the next 64k into the drive before you miss the opportunity to stream the data into the next sector, so you lose a revolution _every_ write. I think I'll rely on the power system and my nightly backups, and leave .wc=1, thanks. Sure, on my next system I'll either go back to SCSI or find some ATA tagged queuing drives, but at the moment, I have to use what I've got... -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 18:52:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp-server.maine.rr.com (smtp-server.maine.rr.com [204.210.65.66]) by hub.freebsd.org (Postfix) with ESMTP id DBBD337B423 for ; Tue, 1 May 2001 18:52:48 -0700 (PDT) (envelope-from dick@helpful.com) Received: from mail.maine.rr.com (mail.maine.rr.com [204.210.65.65]) by smtp-server.maine.rr.com (Postfix) with ESMTP id 56E4B3C801 for ; Tue, 1 May 2001 21:58:05 -0400 (EDT) Received: from eagle ([66.30.201.81]) by mail.maine.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with SMTP id com for ; Tue, 1 May 2001 21:56:18 -0400 From: "Dick Petersen" To: Subject: Date: Tue, 1 May 2001 21:53:54 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 1 22:57: 2 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 0E26137B423 for ; Tue, 1 May 2001 22:56:59 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 PAA23102; Wed, 2 May 2001 15:56:51 +1000 Date: Wed, 2 May 2001 15:55:43 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Daniel Eischen Cc: current@FreeBSD.ORG Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 May 2001, Daniel Eischen wrote: > Why are %fs and %gs set back to default (_udata_sel) when posting > signals? All segment registers are set to a default state so that signal handlers have some chance of running when they interrupt code that has changed the segment registers to unusual values. > I am planning on using %fs for TSD/KSD and want it to be valid > in signal handlers. Imagine doing the same thing with %ds, or better yet, %ss. %ss must be set to the default for the kernel to even provide a "normal" stack for the signal handler. Similarly for %ds, except it is possible for signal handlers to set up their own %ds as necessary provided both the user code and the signal trampoline is written to avoid using %ds before initializing it. > This following seems to fix it. Any reason it would cause > problems? > > Index: machdep.c > =================================================================== > RCS file: /opt/FreeBSD/cvs/src/sys/i386/i386/machdep.c,v > retrieving revision 1.447 > diff -u -r1.447 machdep.c > --- machdep.c 2001/04/27 19:28:19 1.447 > +++ machdep.c 2001/05/01 22:20:52 > @@ -745,8 +745,6 @@ > regs->tf_cs = _ucodesel; > regs->tf_ds = _udatasel; > regs->tf_es = _udatasel; > - regs->tf_fs = _udatasel; > - load_gs(_udatasel); > regs->tf_ss = _udatasel; > } There is also the osendsig() case, and corresponding code in several emulators. The problem has some similarites to ones for handling floating point state. We should be setting the FPU to a clean state so that signal handlers can use floating point. (We don't do this on i386's because signal handlers rarely use floating point and it is difficiult to do without pessimizing delivery of all signals.) OTOH, I believe C99 says that the floating point environment (things like rounding control) is inherited by signal handlers. This seems to be even more difficult to implement on i386's. Changes in the enviroment made by fesetenv() should apply to signal handlers, but temporary ones made by the compiler and library functions should not. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 3:39: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 6802537B422 for ; Wed, 2 May 2001 03:39:04 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 14uu2A-00083r-0K; Wed, 2 May 2001 10:39:02 +0000 Received: from herring (herring [10.0.0.2]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f42Abk754391; Wed, 2 May 2001 11:37:46 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 2 May 2001 11:37:45 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: Subject: Re: HEADS UP! bad bug in -current. In-Reply-To: <20010501191534.96E1A380C@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 May 2001, Peter Wemm wrote: > Any -current kernel built over the weekend is a likely victim of this bug. > In a nutshell, it will eat your root filesystem at the very least, leaving > you with maybe one or two files in /lost+found. spec_vnops.c rev 1.156 > is should be avoided at all costs. > > BEWARE: there are some snapshots on current.freebsd.org with this bug. They > will self destruct after install. Too late - I'm just rebuilding one of my scratch machines right now :-( -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 3:52:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id D9B2737B423 for ; Wed, 2 May 2001 03:52:49 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id GAA25527; Wed, 2 May 2001 06:52:10 -0400 (EDT) Date: Wed, 2 May 2001 06:52:09 -0400 (EDT) From: Daniel Eischen To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 May 2001, Bruce Evans wrote: > On Tue, 1 May 2001, Daniel Eischen wrote: > > > Why are %fs and %gs set back to default (_udata_sel) when posting > > signals? > > All segment registers are set to a default state so that signal handlers > have some chance of running when they interrupt code that has changed > the segment registers to unusual values. OK. > > > I am planning on using %fs for TSD/KSD and want it to be valid > > in signal handlers. > > Imagine doing the same thing with %ds, or better yet, %ss. %ss must > be set to the default for the kernel to even provide a "normal" stack > for the signal handler. Similarly for %ds, except it is possible for > signal handlers to set up their own %ds as necessary provided both > the user code and the signal trampoline is written to avoid using %ds > before initializing it. Well, we're not using %ds or %ss for TSD. It was discussed on -arch some time ago that we would reserve %fs for TSD, so we really on care about that case. I threw in %gs because that was also an option except that WINE used it. [ patch snipped ] > There is also the osendsig() case, and corresponding code in several > emulators. I don't think we care too much about osendsig() since anything that uses a new threads library will have to be recompiled and wouldn't use the old routines. I think the same is true for emulators; an application that used the new threads library wouldn't be running in emulation would it? > The problem has some similarites to ones for handling floating point > state. We should be setting the FPU to a clean state so that signal > handlers can use floating point. (We don't do this on i386's because > signal handlers rarely use floating point and it is difficiult to do > without pessimizing delivery of all signals.) OTOH, I believe C99 > says that the floating point environment (things like rounding control) > is inherited by signal handlers. This seems to be even more difficult > to implement on i386's. Changes in the enviroment made by fesetenv() > should apply to signal handlers, but temporary ones made by the compiler > and library functions should not. So, what if we just make the change for %fs. Or is there a way to tell the kernel "Hey, I don't want %fs to be changed" when setting up the signal handler? A flag to sigaction sa_flags? The other option is for the userland signal handler to fetch the value for %fs out of the sigcontext^Wucontext and manually set it. But this gets icky because now the threads library has to have arch-dependent signal handlers. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 7:54:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.total.net (rossine.total.net [154.11.89.167]) by hub.freebsd.org (Postfix) with SMTP id 6CF6537B422 for ; Wed, 2 May 2001 07:54:29 -0700 (PDT) (envelope-from oh@ca.inter.net) Received: (qmail 17038 invoked from network); 2 May 2001 14:53:38 -0000 Received: from unknown (HELO hong) (154.20.99.99) by smtp.total.net with SMTP; 2 May 2001 14:53:38 -0000 Reply-To: From: To: Subject: Date: Wed, 2 May 2001 10:50:23 -0400 Message-ID: <000001c0d317$3b6d47e0$1600000a@ultranettelecom.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Salve, Con DirectLine potrai riferirti ad un unico operatore per tutte le tue chiamate urbane, interurbane, internazionali e verso cellulari a tariffe MAI VISTE... Inoltre, con la semplice iscrizione gratuita, avrai diritto ad inviare i tuoi fax in tutta Italia a costo zero grazie al servizio freefax Il segreto di DirectLine è che non ha spese gestionali (che ricadono, inevitabilmente, sull'utente): le bollette, i pagamenti, l'assistenza transitano esclusivamente via email. Segnalando il Club ai tuoi amici, arriverai ad eliminare del tutto la bolletta telefonica, e se gli amici sono tanti... potrai addirittura guadagnare denaro! il Club DirectLine è lieto di annunciarLe nuovi ribassi di tariffe in vigore dal 1 Aprile 2001 NUOVE TARIFFE IN VIGORE DAL 1 APRILE 2001 +----------------------+-----------+---------+ | Destinazione | Fascia | Fascia | | | Ord. | Rid. | +----------------------+-----------+---------+ |Italia " Urbano " * | 50 | 50 | |Italia " Inter. " * | 85 | 70 | |Italia Cell. * | 449 | 449 | +----------------------+-----------+---------+ * Con Scatto alla risposta di Lire 50 per il primo minuto IL GIRO DEL MONDO CON POCHE LIRE !!!! +----------------------+-----------+ | Destinazione | Tariffa | | | al min/Lre| +----------------------+-----------+ |Francia | 199 | |Germania | 199 | |Grecia | 499 | |Hong Kong | 419 | |Ungheria | 629 | |India | 1399 | |Iran | 1609 | |Irelanda | 199 | |Israele | 419 | |Giappone | 349 | |Kenya | 1399 | |Korea del Sud | 419 | |Libano | 1329 | |Libia | 221 | |Olanda | 199 | |Filippine | 839 | |Polonia | 489 | |Portogallo | 419 | |Romania | 699 | |Russia | 629 | |Spain | 199 | |Svizzera | 221 | |U.S.A | 199 | |UK | 199 | |Venezula | 699 | |Canada | 199 | +----------------------+-----------+ Con Scatto alla risposta di Lire 250 per il primo minuto per visualizzare la tabella, impostare il carattere Courier TUTTE LE TARIFFE ELENCATE SONO TASSE COMPRESE Cordiali saluti ******************************************************** ---------------- ISCRIZIONE ----------------- ******************************************************** Per iscrizione al servzio invia un messaggio a : mailto:oh@ca.inter.net?Subject=iscrizione ed sarete contattati +----------IL CONCETTO DI DIRECTlINE-----------------+ | | | |Per ciascun nuovo membro entrato a far parte | |del club grazie a tua segnalazione con | |click di mouse guadagnerai una royalty mensile | |pari al 5% dell'importo della sua bolletta | |telefonica. Detto guadagno avverrà OGNI MESE | |e per OGNI CLIENTE cui avrai fatto conoscere al | |club | +----------------------------------------------------+ +--------------------FREE FAX---------------------------------+ | | | FREEFAX~FREEFAX~ FREEFAX~FREEFAX~FREEFAX | | | | Il Club offre FreeFax ogni | | mese per un importo pari al 20% della vostra bolletta | | telefonica del mese precedente. | | Vi ricordiamo che: | | Il credito viene calcolato ogni mese esclusivamente | | in base al traffico telefonico generato nel mese precedente.| | Il credito non è cumulabile con quelli dei mesi successivi, | | quindi se il credito a cui si ha diritto non viene esaurito | | entro la fine del mese lo stesso va perduto. | | Il credito può essere utilizzato solo per trasmissioni fax | | nazionali. Se l'utilizzo di FreeFax nel mese supera il | | credito a cui si ha diritto, la differenza verrà fatturata | | sul conto del cliente. | | | +-------------------------------------------------------------+ °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° ° DirectLine ° ° NUMERO VERDE 800 791405 ° ° NUMERO VERDE 800 791006 ° ° mailto:oh@ca.inter.net ° °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° +-----------------------------------------------------------------+ |Questo messaggio e' stato inviato in seguito alla vostra | |iscrizione alla newsletter di europhoneclub e se pertanto | |non avete richiesto informazioni al rigurado c'e' la possibilita'| |che qualcuno abbia inserito in errore il suo indirizzo email | | | +-----------------------------------------------------------------+ Per cancellarVi dalla lista mandateci un e-mail all`indirizzo: mailto:oh@ca.inter.net?Subject=cancellami ed invia l'email Volete ricevere in futuro maggiori informazioni via email ? mailto:oh@ca.inter.net?Subject=info ed sarete contattati ******************************************************** ---------------- FINE NEWSLETTER ---------------- ******************************************************** [dpc_v01_0502] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 8:27:43 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 6750C37B43F for ; Wed, 2 May 2001 08:27:39 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f42FRac34026 for current@freebsd.org; Wed, 2 May 2001 08:27:36 -0700 (PDT) Date: Wed, 2 May 2001 08:27:36 -0700 (PDT) From: David Wolfskill Message-Id: <200105021527.f42FRac34026@bunrab.catwhisker.org> To: current@freebsd.org Subject: -CURRENT broken in gnu/usr.bin/perl/perl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just glanced through cvs-all; didn't see commits more recent than my last CVSup: CVSup started from cvsup14.freebsd.org at Tue May 1 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Tue May 1 03:55:45 PDT 2001 CVSup started from cvsup14.freebsd.org at Wed May 2 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Wed May 2 03:53:01 PDT 2001 The error occurred during "stage 4: make dependencies": ===> gnu/usr.bin/perl/libperl ===> gnu/usr.bin/perl/perl Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Extracting myconfig (with variable substitutions) Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of line syntax error at lib/SelfLoader.pm line 69, at EOF Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm line 17. Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line 37. Compilation failed in require at /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. *** Error code 255 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 Hmm.... SelfLoader.pm was last modified: m133[3] ls -l SelfLoader.pm -rw-rw-r-- 1 david wheel 12043 Jun 25 2000 SelfLoader.pm It's at revision 1.1.... Hmmm..., david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 9:28:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id 1FAEE37B43C; Wed, 2 May 2001 09:28:23 -0700 (PDT) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id 299E35411; Wed, 2 May 2001 18:28:18 +0200 (CEST) Date: Wed, 2 May 2001 18:28:18 +0200 From: Anton Berezin To: David Wolfskill Cc: current@freebsd.org, joe@freebsd.org Subject: Re: -CURRENT broken in gnu/usr.bin/perl/perl Message-ID: <20010502182818.A76959@heechee.tobez.org> Mail-Followup-To: Anton Berezin , David Wolfskill , current@freebsd.org, joe@freebsd.org References: <200105021527.f42FRac34026@bunrab.catwhisker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105021527.f42FRac34026@bunrab.catwhisker.org>; from david@catwhisker.org on Wed, May 02, 2001 at 08:27:36AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001 at 08:27:36AM -0700, David Wolfskill wrote: > Just glanced through cvs-all; didn't see commits more recent than my last > CVSup: > > CVSup started from cvsup14.freebsd.org at Tue May 1 03:47:00 PDT 2001 > CVSup ended from cvsup14.freebsd.org at Tue May 1 03:55:45 PDT 2001 Did you do another buildworld between these CVSup's? > CVSup started from cvsup14.freebsd.org at Wed May 2 03:47:00 PDT 2001 > CVSup ended from cvsup14.freebsd.org at Wed May 2 03:53:01 PDT 2001 The suspected commit is <200105010925.f419PP491985@freefall.freebsd.org> It looks like the recent BSDPAN change has a problem - I am looking into it. > The error occurred during "stage 4: make dependencies": > > ===> gnu/usr.bin/perl/libperl > ===> gnu/usr.bin/perl/perl > Extracting config.h (with variable substitutions) > Extracting cflags (with variable substitutions) > Extracting writemain (with variable substitutions) > Extracting myconfig (with variable substitutions) > Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of line > syntax error at lib/SelfLoader.pm line 69, at EOF > Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm line 17. > Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. > BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line 37. > Compilation failed in require at /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. > *** Error code 255 > > Stop in /usr/src/gnu/usr.bin/perl/perl. > *** Error code 1 > > > Hmm.... SelfLoader.pm was last modified: > m133[3] ls -l SelfLoader.pm > -rw-rw-r-- 1 david wheel 12043 Jun 25 2000 SelfLoader.pm > > It's at revision 1.1.... > > Hmmm..., Cheers, +Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 9:33:45 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 7762737B422; Wed, 2 May 2001 09:33:42 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f42GXaw34203; Wed, 2 May 2001 09:33:36 -0700 (PDT) Date: Wed, 2 May 2001 09:33:36 -0700 (PDT) From: David Wolfskill Message-Id: <200105021633.f42GXaw34203@bunrab.catwhisker.org> To: tobez@tobez.org Subject: Re: -CURRENT broken in gnu/usr.bin/perl/perl Cc: current@freebsd.org, joe@freebsd.org In-Reply-To: <20010502182818.A76959@heechee.tobez.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Wed, 2 May 2001 18:28:18 +0200 >From: Anton Berezin >> CVSup started from cvsup14.freebsd.org at Tue May 1 03:47:00 PDT 2001 >> CVSup ended from cvsup14.freebsd.org at Tue May 1 03:55:45 PDT 2001 >Did you do another buildworld between these CVSup's? >> CVSup started from cvsup14.freebsd.org at Wed May 2 03:47:00 PDT 2001 >> CVSup ended from cvsup14.freebsd.org at Wed May 2 03:53:01 PDT 2001 Yes. Built OK; seemed to run OK (though I mostly run -STABLE on the box). >The suspected commit is > <200105010925.f419PP491985@freefall.freebsd.org> >It looks like the recent BSDPAN change has a problem - I am looking into >it. OK; thanks! Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 10:36:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from webimprovement.com (webimprovement.com [161.58.166.156]) by hub.freebsd.org (Postfix) with ESMTP id 0DE5137B424 for ; Wed, 2 May 2001 10:36:45 -0700 (PDT) (envelope-from webimpro@webimprovement.com) Received: (webimpro@localhost) by webimprovement.com (8.8.8) id NAA37965; Wed, 2 May 2001 13:36:44 -0400 (EDT) Date: Wed, 2 May 2001 13:36:44 -0400 (EDT) Message-Id: <200105021736.NAA37965@webimprovement.com> Content-type: text/html To: current@freebsd.org From: "BlackOffers.com Newsletters" Reply-To: "BlackOffers.com Newsletters" Subject: BlackOffers.com Newsletters Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG
BlackOffers.com - Newsletters for the African American

Subscribe to our free newsletters and get the latest information you need to know!

BlackOffers.com exclusive newsletters targets African Americans online looking for the latest information relating to the black experience. Although not all content is black related, we bring it to you from a black perspective.

Enter your email and select from our newsletters below.

YOUR E-MAIL:  

Inspirational Motivations Contests & Sweepstakes
Black History New Black Web Sites
Black Headlines Doing Business Online
Free Offers Specials & Promotions

Click here for information about the Newsletters

Visit these other fine black destinations:

Important Notes:
1. There is no cost to join, all lists are free.
2. Your privacy is guaranteed. Your information will never be sold to any third parties.
3. Easy process to unsubscribe.
4. Newsletters are sent in rich media html format.
Home About Us Partner Contact Us
Copyright © 2001, BlackOffers.com
www.blackoffers.com
 webmaster@blackcontests.com

---------------------------------------------------------------------------
To be unsubscribed from the BlackOffers.com Newsletters mailing list, simply click on the link below:
Unsubscribe current@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 May 2 12:30:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 8AE7E37B424; Wed, 2 May 2001 12:29:49 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [3ffe:1200:301b:0:290:27ff:fed1:576b]) by quack.kfu.com (8.11.3/8.11.3) with ESMTP id f42JTf058525 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Wed, 2 May 2001 12:29:47 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: (from nsayer@localhost) by medusa.kfu.com (8.11.3/8.11.3) id f42JTfs08425; Wed, 2 May 2001 12:29:41 -0700 (PDT) (envelope-from nsayer) Date: Wed, 2 May 2001 12:29:41 -0700 (PDT) From: nsayer@quack.kfu.com Message-Id: <200105021929.f42JTfs08425@medusa.kfu.com> To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: RFD: SRA telnet PAM patch Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem noted was that telnetd was allowing root logins. This patch doesn'tt directly address that, but by making SRA use PAM the hope is that it will be easier to have policy changes take place with PAM rather than all over the place. Suggestions on either how to imrpove this patch or what should be done to bar root logins are welcome. Index: src/etc/pam.conf =================================================================== RCS file: /home/ncvs/src/etc/pam.conf,v retrieving revision 1.13 diff -u -r1.13 pam.conf --- src/etc/pam.conf 2001/04/06 05:52:53 1.13 +++ src/etc/pam.conf 2001/05/02 19:26:35 @@ -86,6 +86,10 @@ # "csshd" is for challenge-based authentication with sshd (TIS auth, etc.) csshd auth required pam_skey.so +# SRA telnet. Non-SRA telnet uses 'login'. +telnetd auth required pam_unix.so try_first_pass +telnetd account required pam_unix.so + # Don't break startx xserver auth required pam_permit.so Index: crypto/telnet/libtelnet/sra.c =================================================================== RCS file: /home/ncvs/src/crypto/telnet/libtelnet/sra.c,v retrieving revision 1.1.2.1 diff -u -r1.1.2.1 sra.c --- crypto/telnet/libtelnet/sra.c 2000/09/20 02:32:05 1.1.2.1 +++ crypto/telnet/libtelnet/sra.c 2001/05/02 19:26:36 @@ -13,6 +13,10 @@ #include #endif +#if !defined(NOPAM) +#include +#endif + #include "auth.h" #include "misc.h" #include "encrypt.h" @@ -447,6 +451,7 @@ return (&save); } +#ifdef NOPAM char *crypt(); int check_user(name, pass) @@ -474,7 +479,135 @@ } return(0); } +#else + +/* + * The following is stolen from ftpd, which stole it from the imap-uw + * PAM module and login.c. It is needed because we can't really + * "converse" with the user, having already gone to the trouble of + * getting their username and password through an encrypted channel. + */ + +#define COPY_STRING(s) (s ? strdup(s):NULL) + +struct cred_t { + const char *uname; + const char *pass; +}; +typedef struct cred_t cred_t; + +auth_conv(int num_msg, const struct pam_message **msg, + struct pam_response **resp, void *appdata) +{ + int i; + cred_t *cred = (cred_t *) appdata; + struct pam_response *reply = + malloc(sizeof(struct pam_response) * num_msg); + + for (i = 0; i < num_msg; i++) { + switch (msg[i]->msg_style) { + case PAM_PROMPT_ECHO_ON: /* assume want user name */ + reply[i].resp_retcode = PAM_SUCCESS; + reply[i].resp = COPY_STRING(cred->uname); + /* PAM frees resp. */ + break; + case PAM_PROMPT_ECHO_OFF: /* assume want password */ + reply[i].resp_retcode = PAM_SUCCESS; + reply[i].resp = COPY_STRING(cred->pass); + /* PAM frees resp. */ + break; + case PAM_TEXT_INFO: + case PAM_ERROR_MSG: + reply[i].resp_retcode = PAM_SUCCESS; + reply[i].resp = NULL; + break; + default: /* unknown message style */ + free(reply); + return PAM_CONV_ERR; + } + } + + *resp = reply; + return PAM_SUCCESS; +} + +/* + * The PAM version as a side effect may put a new username in *user. + */ +int check_user(const char *name, const char *pass) +{ + pam_handle_t *pamh = NULL; + const char *tmpl_user; + const void *item; + int rval; + int e; + cred_t auth_cred = { name, pass }; + struct pam_conv conv = { &auth_conv, &auth_cred }; + + e = pam_start("telnetd", name, &conv, &pamh); + if (e != PAM_SUCCESS) { + syslog(LOG_ERR, "pam_start: %s", pam_strerror(pamh, e)); + return 0; + } + +#if 0 /* Where can we find this value? */ + e = pam_set_item(pamh, PAM_RHOST, remotehost); + if (e != PAM_SUCCESS) { + syslog(LOG_ERR, "pam_set_item(PAM_RHOST): %s", + pam_strerror(pamh, e)); + return 0; + } +#endif + + e = pam_authenticate(pamh, 0); + switch (e) { + case PAM_SUCCESS: + /* + * With PAM we support the concept of a "template" + * user. The user enters a login name which is + * authenticated by PAM, usually via a remote service + * such as RADIUS or TACACS+. If authentication + * succeeds, a different but related "template" name + * is used for setting the credentials, shell, and + * home directory. The name the user enters need only + * exist on the remote authentication server, but the + * template name must be present in the local password + * database. + * + * This is supported by two various mechanisms in the + * individual modules. However, from the application's + * point of view, the template user is always passed + * back as a changed value of the PAM_USER item. + */ + if ((e = pam_get_item(pamh, PAM_USER, &item)) == + PAM_SUCCESS) { + strcpy(user, (const char *) item); + } else + syslog(LOG_ERR, "Couldn't get PAM_USER: %s", + pam_strerror(pamh, e)); + rval = 1; + break; + + case PAM_AUTH_ERR: + case PAM_USER_UNKNOWN: + case PAM_MAXTRIES: + rval = 0; + break; + + default: + syslog(LOG_ERR, "auth_pam: %s", pam_strerror(pamh, e)); + rval = 0; + break; + } + + if ((e = pam_end(pamh, e)) != PAM_SUCCESS) { + syslog(LOG_ERR, "pam_end: %s", pam_strerror(pamh, e)); + rval = 0; + } + return rval; +} +#endif #endif Index: secure/src/secure/libexec/telnetd/Makefile =================================================================== RCS file: /home/ncvs/src/secure/libexec/telnetd/Makefile,v retrieving revision 1.22 diff -u -r1.22 Makefile --- secure/src/secure/libexec/telnetd/Makefile 2001/03/28 12:08:19 1.22 +++ secure/src/secure/libexec/telnetd/Makefile 2001/05/02 19:26:37 @@ -15,7 +15,7 @@ DPADD= ${LIBUTIL} ${LIBTERMCAP} ${LIBTELNET} ${LIBCRYPTO} ${LIBMP} \ ${LIBCRYPT} -LDADD= -lutil -ltermcap ${LIBTELNET} -lcrypto -lcrypt -lmp +LDADD= -lutil -ltermcap ${LIBTELNET} -lcrypto -lcrypt -lmp -lpam .include Index: secure/src/secure/usr.bin/telnet/Makefile =================================================================== RCS file: /home/ncvs/src/secure/usr.bin/telnet/Makefile,v retrieving revision 1.24 diff -u -r1.24 Makefile --- secure/src/secure/usr.bin/telnet/Makefile 2001/03/28 12:08:19 1.24 +++ secure/src/secure/usr.bin/telnet/Makefile 2001/05/02 19:26:37 @@ -12,7 +12,7 @@ DPADD= ${LIBTERMCAP} ${LIBTELNET} ${LIBCRYPTO} ${LIBCRYPT} ${LIBMP} DPADD+= ${LIBIPSEC} LDADD= -ltermcap ${LIBTELNET} -lcrypto -lcrypt -lmp -LDADD+= -lipsec +LDADD+= -lipsec -lpam .include To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 12:32:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by hub.freebsd.org (Postfix) with ESMTP id 773F337B424; Wed, 2 May 2001 12:32:44 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 0B6EE17D82; Wed, 2 May 2001 21:32:42 +0200 (CEST) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.11.3/8.11.3) id f42J3Rg04912; Wed, 2 May 2001 21:03:27 +0200 (CEST) (envelope-from schweikh) Date: Wed, 2 May 2001 21:03:26 +0200 From: Jens Schweikhardt To: freebsd-current@freebsd.org Cc: hm@freebsd.org Subject: isdn stops working when load increases Message-ID: <20010502210326.F1280@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello, world\n I've seen some recent mails related to rtprio oddity which seemed to also affect the isdnd. My -current is cvsupped May 1st (and survived; I've still got a fully populated root fs :-) However, as soon as I do a find / or buildworld or some other commands increasing the load significantly (about 1 or more), isdnd seems to take a nap. No more packets transmitted. If I suspend the running programs, isdnd awakes and continues. Is anybody else observing the same behavior? Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 14:25:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id D891A37B422 for ; Wed, 2 May 2001 14:25:01 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.3/8.11.3) with ESMTP id f42LOup61232 for ; Wed, 2 May 2001 23:24:58 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200105022124.f42LOup61232@gratis.grondar.za> To: current@freebsd.org Subject: HEADS UP! Breakage in Perl/BSDPAN Date: Wed, 02 May 2001 23:26:49 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Those who made a buildworld without NO_PERL="true" with sources newer than Tue, 1 May 2001 02:25:25 -0700 (PDT), but older than 2001/05/02 14:18:33 PDT, must apply the following patch as root in /usr/libdata/perl/BSDPAN directory. (If you are tracking CURRENT, then CVSup and/or "cvs update" after this message will get you the same fix.) A patch: (by Anton Berezin ) diff -u -ru /usr/src/gnu/usr.bin/perl/BSDPAN/BSDPAN/Override.pm ./BSDPAN/Override.pm --- /usr/src/gnu/usr.bin/perl/BSDPAN/BSDPAN/Override.pm Tue May 1 11:25:24 2001 +++ ./BSDPAN/Override.pm Wed May 2 20:38:12 2001 @@ -13,9 +13,8 @@ # use strict; use Carp; +use BSDPAN; require Exporter; -require SelfLoader; # XXX 2nd-order magic over SelfLoader's magic :-) -# require AutoLoader; # XXX do we need to do similar hoop-la with it? use vars qw(@ISA @EXPORT); @ISA = qw(Exporter); @@ -77,8 +76,11 @@ # do we need to protect against SelfLoader? my $sl_autoload = eval "*$pkg\::AUTOLOAD{CODE}"; - $sl_autoload = 0 - if $sl_autoload && $sl_autoload != \&SelfLoader::AUTOLOAD; + if ($sl_autoload) { + require SelfLoader; + $sl_autoload = 0 + if $sl_autoload != \&SelfLoader::AUTOLOAD; + } # get the reference to the original sub my $name_addr = eval "*$name\{CODE}"; diff -u -ru /usr/src/gnu/usr.bin/perl/BSDPAN/BSDPAN.pm ./BSDPAN.pm --- /usr/src/gnu/usr.bin/perl/BSDPAN/BSDPAN.pm Tue May 1 11:25:23 2001 +++ ./BSDPAN.pm Wed May 2 20:39:39 2001 @@ -11,7 +11,6 @@ # # The pod documentation for this module is at the end of this file. # -use Config; my $bsdpan_path; # Directory pathname of BSDPAN itself @@ -34,19 +33,22 @@ } sub perl_version { - return $Config{version}; + require Config; + return $Config::Config{version}; } sub perl_ver { + require Config; # pre-5.6.0 perls - return $Config{apiversion} if exists $Config{apiversion}; + return $Config::Config{apiversion} if exists $Config::Config{apiversion}; # post-5.6.0 perls - return $Config{version}; + return $Config::Config{version}; } sub perl_arch { + require Config; # pre-5.6.0 perls - return $Config{archname} if exists $Config{apiversion}; + return $Config::Config{archname} if exists $Config::Config{apiversion}; # post-5.6.0 perls return 'mach'; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 14:35:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id CB6F737B423 for ; Wed, 2 May 2001 14:35:24 -0700 (PDT) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id D6035540B; Wed, 2 May 2001 23:35:23 +0200 (CEST) Date: Wed, 2 May 2001 23:35:23 +0200 From: Anton Berezin To: Mark Murray Cc: current@freebsd.org Subject: Re: HEADS UP! Breakage in Perl/BSDPAN Message-ID: <20010502233523.A862@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Mark Murray , current@freebsd.org References: <200105022124.f42LOup61232@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105022124.f42LOup61232@gratis.grondar.za>; from mark@grondar.za on Wed, May 02, 2001 at 11:26:49PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001 at 11:26:49PM +0200, Mark Murray wrote: > Hi > > Those who made a buildworld without NO_PERL="true" with sources > newer than Tue, 1 May 2001 02:25:25 -0700 (PDT), but older than > 2001/05/02 14:18:33 PDT, must apply the following patch as root in > /usr/libdata/perl/BSDPAN directory. > > (If you are tracking CURRENT, then CVSup and/or "cvs update" after this > message will get you the same fix.) But for those who built world in the above timeframe, it is still necessary to apply the patch: this is one of the unfortunate cases where the state of currently installed perl modules affects the buildworld. \Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 14:40:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id A30C137B422 for ; Wed, 2 May 2001 14:40:12 -0700 (PDT) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id 441CC540B; Wed, 2 May 2001 23:40:07 +0200 (CEST) Date: Wed, 2 May 2001 23:40:07 +0200 From: Anton Berezin To: David Wolfskill Cc: current@freebsd.org Subject: Re: -CURRENT broken in gnu/usr.bin/perl/perl Message-ID: <20010502234007.B862@heechee.tobez.org> Mail-Followup-To: Anton Berezin , David Wolfskill , current@freebsd.org References: <200105021527.f42FRac34026@bunrab.catwhisker.org> <20010502182818.A76959@heechee.tobez.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010502182818.A76959@heechee.tobez.org>; from tobez@tobez.org on Wed, May 02, 2001 at 06:28:18PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001 at 06:28:18PM +0200, Anton Berezin wrote: > On Wed, May 02, 2001 at 08:27:36AM -0700, David Wolfskill wrote: > It looks like the recent BSDPAN change has a problem - I am looking into > it. > > The error occurred during "stage 4: make dependencies": > > > > ===> gnu/usr.bin/perl/libperl > > ===> gnu/usr.bin/perl/perl > > Extracting config.h (with variable substitutions) > > Extracting cflags (with variable substitutions) > > Extracting writemain (with variable substitutions) > > Extracting myconfig (with variable substitutions) > > Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of line > > syntax error at lib/SelfLoader.pm line 69, at EOF > > Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm line 17. > > Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. > > BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line 37. > > Compilation failed in require at /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. > > *** Error code 255 > > > > Stop in /usr/src/gnu/usr.bin/perl/perl. > > *** Error code 1 The fix has been committed. Please also see a HEADS UP message on this list. Thanks, David, for reporting this. +Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 15: 0:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id A01E237B423; Wed, 2 May 2001 14:59:59 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id OAA00163; Wed, 2 May 2001 14:52:30 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpdAAABQaira; Wed May 2 14:52:24 2001 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id PAA25967; Wed, 2 May 2001 15:00:48 -0700 (MST) From: Terry Lambert Message-Id: <200105022200.PAA25967@usr01.primenet.com> Subject: PATCH: partial fix for broken "make release"... To: current@freebsd.org Date: Wed, 2 May 2001 22:00:37 +0000 (GMT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The "make release" stuff is broken, at least in 4.3, and possibly before that. There are several obviously broken things: o The libssh stuff is not installed, and it is not built during a "make release"; I don't know why that is; the workaround is to wait for it to bomb out, and then manuall copy /usr/obj/usr/src/secure/lib/libssh/lib*.a into your ${CHROOTDIR}/usr/obj, and do a "make rerelease" to restart things (without this, the pam_ssh module build fails). o The files jade_1.2.1-13.diff.gz and pdf_sec.ps are not available from any of the listed mirros in the "ports" hierarchy, so they can not be correctly installed, and a "doc" build can not complete. The workaround is to let the above fail, and then: cd ${CHROOT}/usr/ports/distfiles GOTO=ftp://sunsite.doc.ic.ac.uk/Mirrors/FreeBSD/ports/distfiles" fetch ${GOTO}/jade_1.2.1-13.diff.gc fetch ${GOTO}/pdf_sec.ps Then restart again... but this time: make rerelease RELEASENOUPDATE=Y ... o If you set KERNCONF to a non-default value ("GENERIC" is the default value), then sysinstall can't find it to install it during the installation process; the attached patch works for RELENG_4, and would have to be reflected into /usr/src/release AND /usr/src/usr.sbin/sysinstall for -current. Can someone at least apply the patch to RELENG_4??? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. Index: Makefile =================================================================== RCS file: /home/cvs/FreeBSD/src/release/Makefile,v retrieving revision 1.536.2.41 diff -u -r1.536.2.41 Makefile --- Makefile 2001/04/14 22:29:49 1.536.2.41 +++ Makefile 2001/05/02 22:04:14 @@ -268,6 +268,7 @@ echo "#!/bin/sh" > ${CHROOTDIR}/mk echo "set -ex" >> ${CHROOTDIR}/mk echo "_RELTARGET=\$${1:-doRELEASE}" >> ${CHROOTDIR}/mk + echo "export KERNCONF=${KERNCONF}" >> ${CHROOTDIR}/mk echo "export CFLAGS='-O -pipe'" >> ${CHROOTDIR}/mk echo "export NO_X=YES" >> ${CHROOTDIR}/mk echo "export DISTRIBUTIONS=\"${DISTRIBUTIONS}\"" >> ${CHROOTDIR}/mk Index: sysinstall/Makefile =================================================================== RCS file: /home/cvs/FreeBSD/src/release/sysinstall/Attic/Makefile,v retrieving revision 1.92.2.10 diff -u -r1.92.2.10 Makefile --- sysinstall/Makefile 2001/03/12 12:10:28 1.92.2.10 +++ sysinstall/Makefile 2001/05/02 22:06:52 @@ -17,7 +17,7 @@ system.c tape.c tcpip.c termcap.c ufs.c usb.c user.c variable.c \ wizard.c keymap.h -CFLAGS+= -Wall -I${.CURDIR}/../../gnu/lib/libdialog -I${.OBJDIR} +CFLAGS+= -Wall -I${.CURDIR}/../../gnu/lib/libdialog -I${.OBJDIR} -DKERNCONF=\"${KERNCONF}\" .if ${MACHINE} == "pc98" CFLAGS+= -DPC98 .endif Index: sysinstall/install.c =================================================================== RCS file: /home/cvs/FreeBSD/src/release/sysinstall/Attic/install.c,v retrieving revision 1.268.2.22 diff -u -r1.268.2.22 install.c --- sysinstall/install.c 2001/03/12 22:50:04 1.268.2.22 +++ sysinstall/install.c 2001/05/02 22:20:06 @@ -750,7 +750,11 @@ if (RunningAsInit) { /* Fix up kernel first */ if (!file_readable("/kernel")) { +#ifdef KERNCONF + char *generic_kernel = "/kernel." KERNCONF; +#else char *generic_kernel = "/kernel.GENERIC"; +#endif if (file_readable(generic_kernel)) { if (vsystem("cp -p %s /kernel", generic_kernel)) { msgConfirm("Unable to copy /kernel into place!"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 15:10:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by hub.freebsd.org (Postfix) with ESMTP id ED73337B43C for ; Wed, 2 May 2001 15:10:51 -0700 (PDT) (envelope-from bmah@cisco.com) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f42MBKK29699; Wed, 2 May 2001 15:11:20 -0700 (PDT) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.3/8.11.1) id f42MAps18950; Wed, 2 May 2001 15:10:51 -0700 (PDT) (envelope-from bmah) Message-Id: <200105022210.f42MAps18950@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.3.1 01/19/2001 with nmh-1.0.4 To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: PATCH: partial fix for broken "make release"... In-Reply-To: <200105022200.PAA25967@usr01.primenet.com> References: <200105022200.PAA25967@usr01.primenet.com> Comments: In-reply-to Terry Lambert message dated "Wed, 02 May 2001 22:00:37 -0000." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-101993744P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Wed, 02 May 2001 15:10:51 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-101993744P Content-Type: text/plain; charset=us-ascii If memory serves me right, Terry Lambert wrote: > o The files jade_1.2.1-13.diff.gz and pdf_sec.ps are not > available from any of the listed mirros in the "ports" > hierarchy, so they can not be correctly installed, and > a "doc" build can not complete. The workaround is to > let the above fail, and then: Yes. Ran into this when testing RELNOTESng. Grrrr. > cd ${CHROOT}/usr/ports/distfiles > GOTO=ftp://sunsite.doc.ic.ac.uk/Mirrors/FreeBSD/ports/distfiles" > fetch ${GOTO}/jade_1.2.1-13.diff.gc s/gc/gz > fetch ${GOTO}/pdf_sec.ps > > Then restart again... but this time: > > make rerelease RELEASENOUPDATE=Y ... Another way to do this is to fetch the files into /usr/ports/distfiles and then do the release (this works for all distfiles, not just the unfetchable ones). Part of the release process copies /usr/ports/ distfiles to ${CHROOT}/usr/ports/distfiles. In other words: # Do this once cd /usr/ports/distfiles GOTO=ftp://sunsite.doc.ic.ac.uk/Mirros/FreeBSD/ports/distfiles fetch ${GOTO}/jade_1.2.1-13.diff.gz fetch ${GOTO}/pdf_sec.ps # make release works normally Cheers, Bruce. --==_Exmh_-101993744P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE68IXr2MoxcVugUsMRAsmdAJ0YDj/DKjQ0QmIl7GSgid7P6jSUOQCglg7b Ci0mIZFJtg2p4r8uuH+DAn4= =gL8e -----END PGP SIGNATURE----- --==_Exmh_-101993744P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 15:41:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 3734337B424 for ; Wed, 2 May 2001 15:41:21 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f42Mf8342320; Wed, 2 May 2001 15:41:09 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: tlambert@primenet.com Cc: current@FreeBSD.ORG Subject: Re: PATCH: partial fix for broken "make release"... In-Reply-To: <200105022200.PAA25967@usr01.primenet.com> References: <200105022200.PAA25967@usr01.primenet.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010502154108Q.jkh@osd.bsdi.com> Date: Wed, 02 May 2001 15:41:08 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 32 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Terry Lambert Subject: PATCH: partial fix for broken "make release"... Date: Wed, 2 May 2001 22:00:37 +0000 (GMT) > The "make release" stuff is broken, at least in 4.3, and possibly > before that. > > There are several obviously broken things: > > o The libssh stuff is not installed, and it is not built That would be a failure in make world, not make release. > o The files jade_1.2.1-13.diff.gz and pdf_sec.ps are not > available from any of the listed mirros in the "ports" That would be a failure in the ports collection, not make release. I don't make both observations to be pedantic, but to simply make it clear that the correct fixes need to happen somewhere else. > o If you set KERNCONF to a non-default value ("GENERIC" is > the default value), then sysinstall can't find it to I'm not clear as to why you'd want to? GENERIC is the best kernel for creating generally useable releases, but I imagine you have some other reason for chosing a specific configuration for which I also expect you're copying the config file into ${CHROOTDIR}/usr/src/sys/${ARCH}/conf from somewhere else? I can't see how this change by itself makes what appears to be the desired functionality a reality. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 15:49: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D522D37B423 for ; Wed, 2 May 2001 15:48:56 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f42MmhG48763; Wed, 2 May 2001 15:48:43 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010502154108Q.jkh@osd.bsdi.com> Date: Wed, 02 May 2001 15:48:01 -0700 (PDT) From: John Baldwin To: Jordan Hubbard Subject: Re: PATCH: partial fix for broken "make release"... Cc: current@FreeBSD.org, tlambert@primenet.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-May-01 Jordan Hubbard wrote: > From: Terry Lambert > Subject: PATCH: partial fix for broken "make release"... > Date: Wed, 2 May 2001 22:00:37 +0000 (GMT) > >> The "make release" stuff is broken, at least in 4.3, and possibly >> before that. >> >> There are several obviously broken things: >> >> o The libssh stuff is not installed, and it is not built > > That would be a failure in make world, not make release. He probably doesn't have src-crypto or cvs-crypto in his cvsup file. *shrug* Works fine here and worked fine for the 4.3 release build. >> o The files jade_1.2.1-13.diff.gz and pdf_sec.ps are not >> available from any of the listed mirros in the "ports" > > That would be a failure in the ports collection, not make release. Yes. Haven't seen this locally though, but I may have these files prefetched to /usr/docdistfiles on the local snap building machine. >> o If you set KERNCONF to a non-default value ("GENERIC" is >> the default value), then sysinstall can't find it to > > I'm not clear as to why you'd want to? GENERIC is the best kernel for > creating generally useable releases, but I imagine you have some other > reason for chosing a specific configuration for which I also expect > you're copying the config file into ${CHROOTDIR}/usr/src/sys/${ARCH}/conf > from somewhere else? I can't see how this change by itself makes what > appears to be the desired functionality a reality. You could use LOCAL_PATCHES to do it if your patch created a new config file. This would be appropriate if you were rolling an internal release using your own kernel config. In that case his patches make sense. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 17:11:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 9CB7337B422 for ; Wed, 2 May 2001 17:11:07 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id RAA09836 for ; Wed, 2 May 2001 17:11:04 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp05.primenet.com, id smtpdAAAq1aWet; Wed May 2 17:10:51 2001 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA26306 for current@FreeBSD.org; Wed, 2 May 2001 17:11:50 -0700 (MST) From: Terry Lambert Message-Id: <200105030011.RAA26306@usr01.primenet.com> Subject: Re: PATCH: partial fix for broken "make release"... To: current@FreeBSD.org Date: Thu, 3 May 2001 00:11:40 +0000 (GMT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ] On 02-May-01 Jordan Hubbard wrote: ] > From: Terry Lambert ] >> The "make release" stuff is broken, at least in 4.3, and possibly ] >> before that. ] >> ] >> There are several obviously broken things: ] >> ] >> o The libssh stuff is not installed, and it is not built ] > ] > That would be a failure in make world, not make release. ] ] He probably doesn't have src-crypto or cvs-crypto in his cvsup file. ] *shrug* Works fine here and worked fine for the 4.3 release build. I have src-crypto and cvs-crypto; the _ONLY_ thing that breaks is the pam_ssh, when it goes to link against libssh, which is not a shared object, and is not an installed target as a result of "make release". A "make world" works perfectly fine, and builds everything, including the "pam_ssh", just fine. Examining the "/usr/obj" and the CHROOT version of "/usr/obj" indicates that the difference is that the libssh isn't built in the chroot case, and is referenced via a relative path, instead of being referenced from where it _is_ built. Copying _just_ those libraries allows the "pam_ssh" build to complete successfully, and nothing else uses them. ] >> o The files jade_1.2.1-13.diff.gz and pdf_sec.ps are not ] >> available from any of the listed mirros in the "ports" ] > ] > That would be a failure in the ports collection, not make release. ] ] Yes. Haven't seen this locally though, but I may have these files ] prefetched to /usr/docdistfiles on the local snap building machine. The main problem here is that none of the mirrors listed in the "ports" have them, and the FreeBSD FTP server is presently in limbo or pushing up daisies, depending on who you ask. Copying them into the local /usr/ports/distfiles works (as was alluded to in Bruce A. Mah's message), and is a better workaround than waiting for the failure and restarting things, but is a much less useful thing than correcting the "ports" for these things to point to mirrors that work... ] >> o If you set KERNCONF to a non-default value ("GENERIC" is ] >> the default value), then sysinstall can't find it to ] > ] > I'm not clear as to why you'd want to? GENERIC is the best kernel for ] > creating generally useable releases, but I imagine you have some other ] > reason for chosing a specific configuration for which I also expect ] > you're copying the config file into ${CHROOTDIR}/usr/src/sys/${ARCH}/conf ] > from somewhere else? I can't see how this change by itself makes what ] > appears to be the desired functionality a reality. ] ] You could use LOCAL_PATCHES to do it if your patch created a new config ] file. This would be appropriate if you were rolling an internal release ] using your own kernel config. In that case his patches make sense. Exactly what I'm doing: I'm _not_ rolling a boxed set of CDROMs, I'm rolling an internal release using my own kernel config, which I want to be installed by default as a result of an "upgrade" procedure, so that I can upgrade machines from a coaster after I've burnt it and verified that it passes acceptance testing. Actually, the "boxed set of CDROMs" thing is really hard to do entirely correctly, since the ports build process is so arcane, which seems to be because the ports themselves are not "DESTDIR" clean, so they have to be built serially. There's also the "tools" directory, which I guess is copied in magically, because some of the CDROM distribution is built on (bletch!) DOS, instead of being 100% FreeBSD hosted. To elaborate on Jordan's guess, I'm actually _replacing_ the entire /usr/src/sys directory (and using a LOCAL_SCRIPT to do the same to the /usr/src/sys directory in the CHROOT environment at the right time during the build process. If I were truly a grumpy guy, I'd insist that the cvs checkout of the kernel sources be capable of using a different repository and a different tag. My next challenge will be to get my personal packages to show up as options in sysinstall, and to make their installation default for a particular installation set name... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 18:19:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id E512E37B422 for ; Wed, 2 May 2001 18:19:34 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f431JJG52023; Wed, 2 May 2001 18:19:20 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105030011.RAA26306@usr01.primenet.com> Date: Wed, 02 May 2001 18:18:39 -0700 (PDT) From: John Baldwin To: Terry Lambert Subject: Re: PATCH: partial fix for broken "make release"... Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-May-01 Terry Lambert wrote: > A "make world" works perfectly fine, and builds everything, including > the "pam_ssh", just fine. Examining the "/usr/obj" and the CHROOT > version of "/usr/obj" indicates that the difference is that the > libssh isn't built in the chroot case, and is referenced via a > relative path, instead of being referenced from where it _is_ built. > > Copying _just_ those libraries allows the "pam_ssh" build to complete > successfully, and nothing else uses them. make release does a make world in the chroot: rerelease release: ... .if make(release) echo " (cd etc; make distrib-dirs distribution)" >> ${CHROOTDIR}/mk echo " make ${WORLD_FLAGS} world && \\" >> ${CHROOTDIR}/mk .endif ... chroot ${CHROOTDIR} /mk I haven't ever seen this before. Are you using any other customizations besides LOCAL_SCRIPT? Are you specifying NO_CRYPTO or something? > ] Yes. Haven't seen this locally though, but I may have these files > ] prefetched to /usr/docdistfiles on the local snap building machine. > > The main problem here is that none of the mirrors listed in the > "ports" have them, and the FreeBSD FTP server is presently in > limbo or pushing up daisies, depending on who you ask. Well, then as Jordan stated, the ports need to be fixed. The actual release process itself is not broken in this respect, however. > There's also the "tools" directory, which I guess is copied in > magically, because some of the CDROM distribution is built on > (bletch!) DOS, instead of being 100% FreeBSD hosted. AFAIK, it's just copied off of the previous CD-ROM each time. I don't think it's been updated in quite some time. :) DOS is not used though. I think that the tools/ subdir on the CD is considered a WC/BSDi addon though, not part of the base system. > If I were truly a grumpy guy, I'd insist that the cvs checkout of > the kernel sources be capable of using a different repository and > a different tag. That's what LOCAL_SCRIPT is for in this case. make release isn't really designed to patch together various source collections, it's designed to build a release from one source collection. > My next challenge will be to get my personal packages to show up > as options in sysinstall, and to make their installation default > for a particular installation set name... Just add the appropriate lines to the INDEX file and they will show up fine. If you actually add ports directories for them to /usr/ports and rebuild the INDEX (via 'make index') it will DTRT. Note that you don't need all of ports/ to do this, just ports/Mk and ports/tlambert (or whatever) and a suitable modified list of directories in ports/Makefile. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 18:41: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail2.mco.bellsouth.net (mail2.mco.bellsouth.net [205.152.111.14]) by hub.freebsd.org (Postfix) with ESMTP id 290A237B424 for ; Wed, 2 May 2001 18:40:57 -0700 (PDT) (envelope-from PublicRelations@magian10s.com) Received: from c6zl20b (host-209-214-132-139.jax.bellsouth.net [209.214.132.139]) by mail2.mco.bellsouth.net (3.3.5alt/0.75.2) with SMTP id VAA19391; Wed, 2 May 2001 21:28:19 -0400 (EDT) Date: Wed, 2 May 2001 21:28:19 -0400 (EDT) Message-Id: <200105030128.VAA19391@mail2.mco.bellsouth.net> From: MAGIAN WORLD CLASS TENNIS To: Free Online Virtual Tennis Game Reply-To: Subject: Free Online Virtual Tennis Game Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello: Please enjoy the free, new Virtual Tennis Game at www.maxpages.com/magian10s/VirtualTennis?ace. The entire family will enjoy it. Morris King, Jr. Director MAGIAN WORLD CLASS TENNIS www.magian10s.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 18:57:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp10.phx.gblx.net (smtp10.phx.gblx.net [206.165.6.140]) by hub.freebsd.org (Postfix) with ESMTP id 0FFD837B423 for ; Wed, 2 May 2001 18:57:34 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp10.phx.gblx.net (8.9.3/8.9.3) id SAA40120 for ; Wed, 2 May 2001 18:57:32 -0700 Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp10.phx.gblx.net, id smtpdt5Fsqa; Wed May 2 18:57:30 2001 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id SAA29983 for current@FreeBSD.org; Wed, 2 May 2001 18:58:22 -0700 (MST) From: Terry Lambert Message-Id: <200105030158.SAA29983@usr09.primenet.com> Subject: Re: panic in fxp driver To: current@FreeBSD.org Date: Thu, 3 May 2001 01:58:22 +0000 (GMT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The fxp driver is broken in a lot of places. For example, in fxp_intr(): for (txp = sc->cbl_first; sc->tx_queued && (txp->cb_status & FXP_CB_STATUS_C) != 0; txp = txp->next) { if (txp->mb_head != NULL) { m_freem(txp->mb_head); txp->mb_head = NULL; } sc->tx_queued--; } ...notice the "for" loop doesn't check to see if "txp = txp->next" ends up being NULL? You can get this, if you put your system under extreme load. If you can repeat the problem with another card, it's a real problem, otherwise it's probably just FXP driver brain damage... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 19: 9:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 7B01737B422 for ; Wed, 2 May 2001 19:09:51 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f4329dR74591; Wed, 2 May 2001 21:09:39 -0500 (CDT) (envelope-from jlemon) Date: Wed, 2 May 2001 21:09:39 -0500 (CDT) From: Jonathan Lemon Message-Id: <200105030209.f4329dR74591@prism.flugsvamp.com> To: tlambert@primenet.com, current@freebsd.org Subject: Re: panic in fxp driver X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >The fxp driver is broken in a lot of places. > >For example, in fxp_intr(): > > for (txp = sc->cbl_first; sc->tx_queued && > (txp->cb_status & FXP_CB_STATUS_C) != 0; > txp = txp->next) { > if (txp->mb_head != NULL) { > m_freem(txp->mb_head); > txp->mb_head = NULL; > } > sc->tx_queued--; > } > >...notice the "for" loop doesn't check to see if "txp = txp->next" >ends up being NULL? You can get this, if you put your system >under extreme load. I would be quite interested in knowing just how you manage to accomplish that, given that all the transmit control buffers are arranged in a circular linked list: fxp_init(void *xsc) { ... for (i = 0; i < FXP_NTXCB; i++) { ... txp[i].next = &txp[(i + 1) & FXP_TXCB_MASK]; } I would suggest actually examining the rest of the code to see how it works before making erroneous proclamations based on the myopic examination of a single statement. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 20:22:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 6C71A37B423 for ; Wed, 2 May 2001 20:22:46 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f433MNf76517; Wed, 2 May 2001 23:22:31 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 2 May 2001 23:22:23 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jordan Hubbard Cc: grasshacker@over-yonder.net, current@FreeBSD.ORG Subject: Re: HEADS UP! bad bug in -current. In-Reply-To: <20010501165654K.jkh@osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 May 2001, Jordan Hubbard wrote: > > Say, FreeBSD is usually pretty safe, even in CURRENT. > > Has something near this magnitude of Really Bad Stuffage snuck into the > > codebase before? > > No, it's not common, and it generally takes a Dane swinging something > sharp to inflict quite this much damage on our user base. ;-) Obviously I haven't been playing in the right bits of the system, I'll have to start hacking the low-level stuff in FFS some more... I tend not to cause permanent damage to file systems, sadly. I think we can all take lessons from phk here -- he achieves a level of destructiveness that makes even the pro's marvel in wonder. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 21:59:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from webimprovement.com (webimprovement.com [161.58.166.156]) by hub.freebsd.org (Postfix) with ESMTP id 5FBD137B43F for ; Wed, 2 May 2001 21:59:14 -0700 (PDT) (envelope-from webimpro@webimprovement.com) Received: (webimpro@localhost) by webimprovement.com (8.8.8) id NAA39755; Wed, 2 May 2001 13:38:48 -0400 (EDT) Date: Wed, 2 May 2001 13:38:48 -0400 (EDT) Message-Id: <200105021738.NAA39755@webimprovement.com> To: current@freebsd.org From: "BlackOffers.com Newsletters" Reply-To: "BlackOffers.com Newsletters" Subject: You've Been Removed! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is to confirm the removal of your email address: current@freebsd.org from the BlackOffers.com Newsletters Subscribe Me mailing list. We're sorry to see you go! If you feel you have received this notice in error, please visit the BlackOffers.com Newsletters Subscribe Me mailing list at our website: http://www.mybmail.com to add yourself automatically, or click on the link below to automatically re-subscribe yourself: http://mybmail.com/cgi-bin/info/s.pl?a=1&l=16&e=current=:freebsd.org Thank you, BlackOffers.com Newsletters To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 2 23:45:13 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 16FE337B424; Wed, 2 May 2001 23:45:02 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f436iw141659; Thu, 3 May 2001 09:44:58 +0300 (EEST) (envelope-from ru) Date: Thu, 3 May 2001 09:44:58 +0300 From: Ruslan Ermilov To: Assar Westerlund Cc: Nick Sayer , current@FreeBSD.org Subject: Re: telnet -a the default Message-ID: <20010503094458.A40729@sunbay.com> Mail-Followup-To: Assar Westerlund , Nick Sayer , current@FreeBSD.org References: <20010428162045.E72985@sunbay.com> <3AEAE5AC.4090209@quack.kfu.com> <20010428191737.A93577@sunbay.com> <3AEAF10E.4030003@quack.kfu.com> <20010428213536.C1010@sunbay.com> <3AEB24CA.90203@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AEB24CA.90203@quack.kfu.com>; from nsayer@quack.kfu.com on Sat, Apr 28, 2001 at 01:15:06PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 28, 2001 at 01:15:06PM -0700, Nick Sayer wrote: > Ruslan Ermilov wrote: > > > On Sat, Apr 28, 2001 at 09:34:22AM -0700, Nick Sayer wrote: > > > >> Ruslan Ermilov wrote: > >> > >> > >>> On Sat, Apr 28, 2001 at 08:45:48AM -0700, Nick Sayer wrote: > >>> > >>> > >>>> Ruslan Ermilov wrote: > >>>> > >>>> > >>>> > >>>>> Hi! > >>>>> > >>>>> Any reason why revisions 1.6 and 1.7 of crypto/telnet/telnet/main.c > >>>>> are not propagated to usr.bin/telnet/main.c? > >>>> > >>>> Well, because it's meaningless without having encryption compiled in. > >>>> All of the authentication methods require encryption. > >>>> > >>> > >>> Sorry, I meant making -a the default. > >>> > >>> > >>> Cheers, > >> > >> Again, making -a the default is meaningless without crypto. > >> > > > > I just found it inconvenient to supply -K to telnet(1) every time > > now, and you know that secure/ telnet is installed by default. > > > > Could you please then tell me why -a was made the default for > > crypto telnet(1), and why it is meaningless without crypto? > > I didn't make -a the default for telnet, but I did MFC it just so that > both branches would have the same sources. > > -a without an authentication method ends up just giving you a login: > prompt from the other end. It's functionally no different than just > doing it the old fashioned way. > Assar, What is the reason why -a was made the default for crypto/ telnet? Is it the prerequisite for "auto-negotiation of encrypt and decrypt" committed in crypto/telnet/telnet/main.c,v 1.6 or could it be made optional? 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 May 3 2:25:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from zuerich02.bluecobalt.net (zuerich02.bluecobalt.net [193.0.232.29]) by hub.freebsd.org (Postfix) with ESMTP id 81F0E37B422 for ; Thu, 3 May 2001 02:25:09 -0700 (PDT) (envelope-from plm@mutsaers.com) Received: from mutsaers.com (adsl-unlimited.callino.ch [217.20.193.18] (may be forged)) by zuerich02.bluecobalt.net (8.9.3/8.9.3) with ESMTP id LAA19658 for ; Thu, 3 May 2001 11:25:05 +0200 Received: (from plm@localhost) by mutsaers.com (8.11.3/8.11.1) id f439Oa319781; Thu, 3 May 2001 11:24:36 +0200 (CEST) (envelope-from plm) To: freebsd-current@freebsd.org Subject: Re: Linux JDK 1.3 and hotspot (native threads) From: Peter Mutsaers Date: 03 May 2001 11:24:36 +0200 In-Reply-To: "Georg-W. Koltermann"'s message of "Mon, 30 Apr 2001 11:59:38 +0200" Message-ID: <87ae4urdij.fsf@mutsaers.com> Lines: 17 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "Georg-W" =3D=3D Georg-W Koltermann writes: Georg-W> I tried the patch and found it makes no difference. The curre= nt SUN Georg-W> JVM (1.3.0_02) gives the SIG11 as I indicated before. The lat= est IBM Georg-W> JVM (IBM build cx130-20010329) hangs around and eats up CPU ti= me. It Georg-W> mostly eats system time (usage is about 8% user, 91% system). = A Georg-W> normal kill is ineffective, I have to send it a -9 in order to Georg-W> terminate.=20=20 Running SUn JVM 1.3.0_02 on Solaris 2.6 gives me exactly the same error once in a while, but only (I think) when using with -server, i.e. the hotspot server. This might well be a JVM problem, not a problem of the Linux emulation. --=20 Peter Mutsaers | D=FCbendorf | UNIX - Live free or die plm@gmx.li | Switzerland | Sent via FreeBSD 4.3-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 3:38:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id 5F7CF37B43F for ; Thu, 3 May 2001 03:38:33 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout1.freenet.de with esmtp (Exim 3.22 #1) id 14vGVA-0002VN-00 for current@freebsd.org; Thu, 03 May 2001 12:38:28 +0200 Received: from b806a.pppool.de ([213.7.128.106] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.22 #1) id 14vGV9-0001Lo-00 for current@freebsd.org; Thu, 03 May 2001 12:38:28 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.3/8.11.3) with ESMTP id f43AaOK00912 for ; Thu, 3 May 2001 12:36:25 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200105031036.f43AaOK00912@Magelan.Leidinger.net> Date: Thu, 3 May 2001 12:36:23 +0200 (CEST) From: Alexander Leidinger Subject: /usr/bin/login buserror with pam_ssh.so & _malloc_options="JR" To: current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, ---snip--- (1) root@ttyp2 # grep ^login /etc/pam.conf login auth sufficient pam_ssh.so try_first_pass login auth required pam_unix.so try_first_pass login account required pam_unix.so login session sufficient pam_ssh.so try_first_pass login password required pam_permit.so login session required pam_permit.so (2) root@ttyp2 # ll /etc/malloc.conf lrwxr-xr-x 1 root wheel 2 Sep 5 2000 /etc/malloc.conf@ -> aj ---snip--- Logging in on the console starts the ssh-agent for users which authenticate via pam_ssh (as expected), but the SSH env vars (SSH_AGENT_PID, SSH_AUTH_SOCK) aren't set (I think because export_pam_environment() is called before the pflag check and before pam_open_session(), but moving it behind pam_open_session() didn't work). Because I also get some "warning: chunk already free" with pam_ssh.so at logout I compiled login with _malloc_options="JR" (and ="JRX"). Now I get a buserror if I try to authenticate via pam_ssh.so. I expected to find a coredump in / or in /home/$user (or at least somewhere in the root fs or in /tmp), but I can't find it. What am I doing wrong (I didn't have a coredump limit)? Bye, Alexander. -- I believe the technical term is "Oops!" http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 5:35:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id A6BD337B423; Thu, 3 May 2001 05:35:34 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout1.freenet.de with esmtp (Exim 3.22 #1) id 14vIKT-00047e-00; Thu, 03 May 2001 14:35:33 +0200 Received: from b8170.pppool.de ([213.7.129.112] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.22 #1) id 14vIKK-0002Au-00; Thu, 03 May 2001 14:35:33 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.3/8.11.3) with ESMTP id f43BdrK02953; Thu, 3 May 2001 13:39:54 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200105031139.f43BdrK02953@Magelan.Leidinger.net> Date: Thu, 3 May 2001 13:39:50 +0200 (CEST) From: Alexander Leidinger Subject: Re: isdn stops working when load increases To: schweikh@schweikhardt.net Cc: freebsd-current@FreeBSD.ORG, hm@FreeBSD.ORG, ru@FreeBSD.org In-Reply-To: <20010502210326.F1280@schweikhardt.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2 Mai, Jens Schweikhardt wrote: [Ruslan: I CCed you because of the second part of the mail] > I've seen some recent mails related to rtprio oddity which seemed > to also affect the isdnd. My -current is cvsupped May 1st (and Yes, it didn't started with the broken version of rtprio (I had to remove the rtprio keyword). > survived; I've still got a fully populated root fs :-) I got a kernel panic with no coredump, I hope the npx commit fixed this, will test later. > However, as soon as I do a find / or buildworld or some other > commands increasing the load significantly (about 1 or more), > isdnd seems to take a nap. No more packets transmitted. If I > suspend the running programs, isdnd awakes and continues. > Is anybody else observing the same behavior? Not with my Apr 29 kernel (no rtprio keyword in isdnd.rc), at least I didn't noticed it. BTW: What about dial-on-demand? I need this patch from Ruslan (attention, will not apply because of tab->space conversation by cut&paste!) ---snip--- Index: raw_ip.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/raw_ip.c,v retrieving revision 1.75 diff -u -p -r1.75 raw_ip.c --- raw_ip.c 2001/03/16 20:00:53 1.75 +++ raw_ip.c 2001/03/30 14:09:20 @@ -398,7 +398,9 @@ rip_ctlinput(cmd, sa, vip) * thing to do, but at least if we are running * a routing process they will come back. */ +#if 0 in_ifadown(&ia->ia_ifa); +#endif break; } } ---snip--- to get a working dial-on-demand (the defaultroute vanishes after the first "ifconfig down", but stays after readding the defaultroute). Bye, Alexander. -- 0 and 1. Now what could be so hard about that? http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 7:31:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1553B37B422 for ; Thu, 3 May 2001 07:31:52 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id HAA03719 for ; Thu, 3 May 2001 07:31:51 -0700 Date: Thu, 3 May 2001 07:31:50 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: lock order reversals, anyone? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG T-o-T about 24 hours ago: > lock order reversal > 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239 > 2nd 0xfffffe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542 > 3rd 0xfffffe0000aab8d0 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 > acquiring duplicate lock of same type: "allproc" > 1st @ /usr/src/sys/kern/kern_proc.c:609 > 2nd @ /usr/src/sys/kern/kern_proc.c:146 > lock order reversal > 1st vnode interlock last acquired @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:397 > 2nd 0xfffffc000080f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464 > 3rd 0xfffffe0026918080 vnode interlock @ /usr/src/sys/kern/vfs_subr.c:1881 > pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped) (oh, yeah, a 4.1 built executable is dying, charming) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 7:48:15 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 09D2137B422; Thu, 3 May 2001 07:48:11 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f43Em8q37301; Thu, 3 May 2001 07:48:08 -0700 (PDT) Date: Thu, 3 May 2001 07:48:08 -0700 (PDT) From: David Wolfskill Message-Id: <200105031448.f43Em8q37301@bunrab.catwhisker.org> To: obrien@freebsd.org Subject: Re: cvs commit: src/contrib/binutils/ld/emultempl elf32.em Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Ref. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=574034+0+current/cvs-all] Just had a build of today's -CURRENT die during the "stage 3: cross tools" part: ===> ld ln -sf /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/emultempl/astring.sed stringify.sed sh /usr/src/gnu/usr.bin/binutils/ld/genscripts.sh /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld \"/usr/lib\" i386-unknown-freebsd i386-unknown-freebsd i386-unknown-freebsd elf_i386 "" elf_i386 i386-unknown-freebsd echo " extern ld_emulation_xfer_type ld_elf_i386_emulation;" > ldemul-list.h echo "#define EMULATION_LIST &ld_elf_i386_emulation, 0" >> ldemul-list.h yacc -d -o ldgram.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldgram.y lex -t /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlex.l > ldlex.c rm -f .depend mkdep -f .depend -a -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/ld/i386 -I/usr/src/gnu/usr.bin/binutils/ld -I/usr/src/gnu/usr.bin/binutils/ld/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/include -DDEFAULT_EMULATION=\"elf_i386\" -DTARGET=\"i386-unknown-freebsd\" -DSCRIPTDIR=\"/usr/obj/usr/src/i386/usr/libdata\" -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld -DVERSION=\"2.10.1\" -DBFD_VERSION=\"2.10.1\" -I/usr/obj/usr/src/i386/usr/include eelf_i386.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldcref.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldctor.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldemul.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldexp.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldfile.c ldgram.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlang.c ldlex.c /usr/src! /gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldmain.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldmisc.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldver.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldwrite.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/lexsup.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/mri.c eelf_i386.c:158: elf-hints.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/ld. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. This is on: FreeBSD localhost 5.0-CURRENT FreeBSD 5.0-CURRENT #51: Wed May 2 16:24:51 PDT 2001 root@m133.whistle.com:/common/C/obj/usr/src/sys/compile/LAPTOP_30W i386 Recent CVSups: CVSup started from cvsup14.freebsd.org at Wed May 2 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Wed May 2 03:53:01 PDT 2001 CVSup started from cvsup14.freebsd.org at Thu May 3 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Thu May 3 03:52:25 PDT 2001 A "find" from /usr/src showed that elf-hints.h is in /usr/src/include, with a timestamp of 05:34 this morning (when I ran the "cvs update"). A similar check of /usr/obj turns up empty... should it be getting copied somewhere, perhaps? Thanks, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 7:52:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by hub.freebsd.org (Postfix) with ESMTP id A7B4F37B43C for ; Thu, 3 May 2001 07:52:40 -0700 (PDT) (envelope-from bmah@cisco.com) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-4.cisco.com (8.11.3/8.9.1) with ESMTP id f43Eqkd01132; Thu, 3 May 2001 07:52:46 -0700 (PDT) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.3/8.11.1) id f43EqeX32443; Thu, 3 May 2001 07:52:40 -0700 (PDT) (envelope-from bmah) Message-Id: <200105031452.f43EqeX32443@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.3.1 01/19/2001 with nmh-1.0.4 To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: lock order reversals, anyone? In-Reply-To: References: Comments: In-reply-to Matthew Jacob message dated "Thu, 03 May 2001 07:31:50 -0700." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-1575829560P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 03 May 2001 07:52:40 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-1575829560P Content-Type: text/plain; charset=us-ascii If memory serves me right, Matthew Jacob wrote: > T-o-T about 24 hours ago: ??? > > lock order reversal > > 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239 > > 2nd 0xfffffe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542 > > 3rd 0xfffffe0000aab8d0 lockmgr interlock @ > /usr/src/sys/kern/kern_lock.c:239 > > acquiring duplicate lock of same type: "allproc" > > 1st @ /usr/src/sys/kern/kern_proc.c:609 > > 2nd @ /usr/src/sys/kern/kern_proc.c:146 > > lock order reversal > > 1st vnode interlock last acquired @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:397 > > 2nd 0xfffffc000080f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464 > > 3rd 0xfffffe0026918080 vnode interlock @ /usr/src/sys/kern/vfs_subr.c:1881 I saw something similar on my 5-CURRENT box built around 27 April. No core dumps that I know of. These showed up at boot time, shortly after my machine's SCSI devices were probed. From /var/log/messages: May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: da0: Fixed Direct Access SCSI-3 device May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: lock order reversal May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239 May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 2nd 0xcb64665c process lock @ /usr/src/sys/kern/kern_exit.c:542 May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 3rd 0xc0e3f988 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: acquiring duplicate lock of same type: "allproc" May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 1st @ /usr/src/sys/kern/kern_proc.c:607 May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 2nd @ /usr/src/sys/kern/kern_proc.c:144 May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: lock order reversal May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 1st vnode interlock last acquired @ /usr/src/sys/kern/vfs_vnops.c:636 May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 2nd 0xc050d060 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:975 May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 3rd 0xccf9c52c vnode interlock @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:984 May 2 10:19:12 bmah-freebsd-1 ntpd[355]: ntpd 4.0.99b Fri Apr 27 16:43:30 PDT 2001 (1) May 2 10:19:12 bmah-freebsd-1 ntpd[355]: using kernel phase-lock loop 2040 May 2 10:19:12 bmah-freebsd-1 ntpd[355]: using kernel phase-lock loop 2041 My machine is running a GENERIC kernel. Bruce. --==_Exmh_-1575829560P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE68XC42MoxcVugUsMRArYQAJ9l5KCvoGNlRZKe7cZeZfKoinZH7QCg2aUO Kbg3w+Mz/tj2jg7xaDe3GCo= =uWfu -----END PGP SIGNATURE----- --==_Exmh_-1575829560P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 7:56: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id CE42D37B43C for ; Thu, 3 May 2001 07:55:46 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.22 #1) id 14vKW9-0001TE-00 for current@freebsd.org; Thu, 03 May 2001 16:55:45 +0200 Received: from b8314.pppool.de ([213.7.131.20] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.22 #1) id 14vKW7-0007PA-00 for current@freebsd.org; Thu, 03 May 2001 16:55:44 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.3/8.11.3) with ESMTP id f43EYrG00732 for ; Thu, 3 May 2001 16:34:54 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200105031434.f43EYrG00732@Magelan.Leidinger.net> Date: Thu, 3 May 2001 16:34:51 +0200 (CEST) From: Alexander Leidinger Subject: trap12: page fault To: current@freebsd.org MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="0-1804289383-988900495=:729" Content-Transfer-Encoding: BINARY Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-1804289383-988900495=:729 Content-Type: TEXT/plain; charset=us-ascii Hi, /sys from cvsup around 2pm CEST from cvsup3.de.freebsd.org (contains npx.c fix). Fatal trap 12: page fault while in kernel mode fault virtual address = 0x54 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01de7c3 stack pointer = 0x10:0xd51cfd98 frame pointer = 0x10:0xd51cfd98 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 = 6 (sh) trap number = 12 panic: page fault syncing disks... No syncing of the disks happens, no coredump (dump device not configured at this stage), hangs hard (need to press the reset button) after printing "syncing disks...". Happens after printing "Routing Daemons:.", before "Additional daemons: syslogd." It showed up the first time after the "eats FFS partitions for breakfast" problem was fixed. I already removed /sys/compile/, so it didn't seems to be a stale object file. dmesg from a working kernel and kernel config attached. Bye, Alexander. -- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 --0-1804289383-988900495=:729 Content-Type: TEXT/plain; name="dmesg.txt" Content-Disposition: attachment; filename="dmesg.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 #21: Sun Apr 29 15:54:35 CEST 2001 root@Magelan.Leidinger.net:/big/usr/src/sys/compile/WORK Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (400.94-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183f9ff real memory = 268423168 (262132K bytes) avail memory = 256954368 (250932K bytes) Preloaded elf kernel "kernel" at 0xc041e000. Preloaded elf module "vesa.ko" at 0xc041e09c. Preloaded elf module "cd9660.ko" at 0xc041e138. Preloaded elf module "mfs.ko" at 0xc041e1d8. Preloaded elf module "msdos.ko" at 0xc041e274. Preloaded elf module "procfs.ko" at 0xc041e314. Preloaded elf module "linux.ko" at 0xc041e3b4. Preloaded elf module "snd_pcm.ko" at 0xc041e454. Preloaded elf module "snd_sbc.ko" at 0xc041e4f4. Preloaded elf module "snd_sb16.ko" at 0xc041e594. Preloaded elf module "usb.ko" at 0xc041e634. Preloaded elf module "agp.ko" at 0xc041e6d0. Preloaded elf module "accf_data.ko" at 0xc041e76c. Preloaded elf module "accf_http.ko" at 0xc041e810. Preloaded elf module "random.ko" at 0xc041e8b4. Preloaded elf module "atspeaker.ko" at 0xc041e954. Preloaded elf module "joy.ko" at 0xc041e9f8. Pentium Pro MTRR support enabled VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc036f2d7 (1000117) VESA: 3dfx Interactive, Inc. Using $PIR table, 7 entries at 0xc00f0d10 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 agp0: mem 0xe0000000-0xe7ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xb400-0xb41f irq 9 at device 4.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 intpm0: port 0xe800-0xe80f irq 9 at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 ahc0: port 0xb000-0xb0ff mem 0xd9800000-0xd9800fff irq 9 at device 6.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs ed0: port 0xa800-0xa81f irq 9 at device 10.0 on pci0 ed0: address 00:80:ad:40:bd:e7, type NE2000 (16 bit) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x6 on isa0 sc0: VGA <16 virtual consoles, flags=0x206> 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 sio0 at port 0x3f8-0x3ff irq 4 flags 0x20010 on isa0 sio0: type ST16650A sio1 at port 0x2e8-0x2ef irq 10 flags 0x20000 on isa0 sio1: type ST16650A pca0 at port 0x40 on isa0 isic0 at port 0x1b00-0x1b1f,0x16e0-0x16ff,0x6e0-0x6ff,0xee0-0xeff,0x1300-0x131f,0x300-0x31f,0xb00-0xb1f irq 3 flags 0x4 on isa0 isic0: passive stack unit 0 isic0: AVM A1 or Fritz!Card Classic ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port pcfclock0: on ppbus0 ppi0: on ppbus0 pps0: on ppbus0 sc1: on isa0 sc1: MDA <16 virtual consoles, flags=0x0> WARNING: Driver mistake: repeat make_dev("consolectl") vga1: at port 0x3b0-0x3bb iomem 0xb0000-0xb7fff on isa0 sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 pcm0: on sbc0 joy0: at port 0x200-0x207 on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources pca1: at port 0x61 on isa0 WARNING: Driver mistake: repeat make_dev("pcaudio") WARNING: Driver mistake: repeat make_dev("pcaudioctl") i4bctl: ISDN system control port attached i4brbch: 2 raw B channel access device(s) attached i4bisppp: 2 ISDN SyncPPP device(s) attached (VJ header compression) IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 100 packets/entry by default i4b: ISDN call control device attached i4btrc: 2 ISDN trace device(s) attached ad0: 19547MB [39714/16/63] at ata0-master UDMA33 afd0: 96MB [32/64/96] at ata1-master PIO0 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s2a cd0 at ahc0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 2 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present --0-1804289383-988900495=:729 Content-Type: TEXT/plain; name=WORK Content-Disposition: attachment; filename=WORK machine i386 ident WORK maxusers 40 makeoptions DEBUG=-g makeoptions CONF_CFLAGS=-fno-builtin hints "WORK.hints" # Options for the VM subsystem options PQ_CACHESIZE=512 # color for 512k/16k cache cpu I686_CPU # aka Pentium Pro(tm) options CPU_FASTER_5X86_FPU options CPU_SUSP_HLT options "NO_F00F_HACK" options CPU_UPGRADE_HW_CACHE options PERFMON options COMPAT_43 options SYSVSHM options SHMMAXPGS=8192 options SYSVSEM options SYSVMSG options DDB options DDB_UNATTENDED options GDB_REMOTE_CHAT options KTRACE #kernel tracing options UCONSOLE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #Internet communications protocols device ether #Generic Ethernet device sppp #Generic Synchronous PPP device loop 1 #Network loopback device device bpf #Berkeley packet filter # # The INVARIANTS option is used in a number of source files to enable # extra sanity checking of internal structures. This support is not # enabled by default because of the extra time it would take to check # for these conditions, which can only occur as a result of # programming errors. # options INVARIANTS options INVARIANT_SUPPORT options DIAGNOSTIC #options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options FFS #Fast filesystem options SOFTUPDATES options ENABLE_VFS_IOOPT options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L device scbus #base SCSI code #device ch #SCSI media changers device da #SCSI direct access devices (aka disks) #device sa #SCSI tapes device cd #SCSI CD-ROMs device pass #CAM passthrough driver device ses #SCSI SES/SAF-TE driver options CAM_MAX_HIGHPOWER=4 options SCSI_DELAY=5000# Be pessimistic about Joe SCSI device options SES_ENABLE_PASSTHROUGH device pty #Pseudo ttys device gzip #Exec gzipped a.out's #device snp 3 #Snoop device - to look at pty/vty/etc.. options MSGBUF_SIZE=40960 device isa # Enable support for the kernel PLL to use an external PPS signal, # under supervision of [x]ntpd(8) # More info in ntpd documentation: http://www.eecis.udel.edu/~ntp options PPS_SYNC device atkbdc 1 device atkbd options ATKBD_DFLT_KEYMAP # specify the built-in keymap makeoptions ATKBD_DFLT_KEYMAP="german.iso" #options KBD_DISABLE_KEYMAP_LOAD # refuse to load a keymap options KBD_INSTALL_CDEV # install a CDEV entry in /dev device psm device vga device splash device sc 1 options MAXCONS=16 # number of virtual consoles options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT="iso" options SC_HISTORY_SIZE=800 # number of history buffer lines device npx device ata device atadisk # ATA disk drives #device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives device fdc device sio 2 device ed device miibus #device wb #device midi #device seq device pca device apm #device acpi device pci device ahc options AHC_ALLOW_MEMIO device smbus device intpm device smb device iicbus device iicbb device ic device iic device iicsmb options AVM_A1 device isic device "i4bq921" device "i4bq931" device "i4b" device "i4btrc" 2 device "i4bctl" device "i4brbch" 2 #device "i4btel" 1 #device "i4bipr" 2 options IPR_VJ device "i4bisppp" 2 options PERIPH_1284 # Makes your computer act as a IEEE1284 # compliant peripheral device ppbus device lpt #device plip device ppi device pps device lpbb #options PCFCLOCK_VERBOSE device pcfclock options PPC_PROBE_CHIPSET device ppc #options CLK_CALIBRATION_LOOP #options CLK_USE_I8254_CALIBRATION options CLK_USE_TSC_CALIBRATION --0-1804289383-988900495=:729-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 7:57:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 96DE737B424 for ; Thu, 3 May 2001 07:57:25 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by peitho.fxp.org (Postfix, from userid 1501) id CEDE11360C; Thu, 3 May 2001 10:57:24 -0400 (EDT) Date: Thu, 3 May 2001 10:57:24 -0400 From: Chris Faulhaber To: Matthew Jacob Cc: current@freebsd.org Subject: Re: lock order reversals, anyone? Message-ID: <20010503105724.A14089@peitho.fxp.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Thu, May 03, 2001 at 07:31:50AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 03, 2001 at 07:31:50AM -0700, Matthew Jacob wrote: >=20 > T-o-T about 24 hours ago: >=20 > > lock order reversal > > 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239 > > 2nd 0xfffffe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542 > > 3rd 0xfffffe0000aab8d0 lockmgr interlock @ > /usr/src/sys/kern/kern_lock.c:239 > > acquiring duplicate lock of same type: "allproc" > > 1st @ /usr/src/sys/kern/kern_proc.c:609 > > 2nd @ /usr/src/sys/kern/kern_proc.c:146 > > lock order reversal > > 1st vnode interlock last acquired @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:= 397 > > 2nd 0xfffffc000080f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464 > > 3rd 0xfffffe0026918080 vnode interlock @ /usr/src/sys/kern/vfs_subr.c:= 1881 > > pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped) >=20 > (oh, yeah, a 4.1 built executable is dying, charming) >=20 Don't know about your 4.1 executable, but the lock order reversals are a well known issue: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=3D161827+165415+/usr/local/www/= db/text/2001/freebsd-current/20010429.freebsd-current and http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=3D91622+94620+/usr/local/www/db= /text/2001/freebsd-current/20010422.freebsd-current --=20 Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: FreeBSD: The Power To Serve iEYEARECAAYFAjrxcdQACgkQObaG4P6BelAlFgCeO3VKm05LAGF/M1La+o5UsFDP orwAnj0y5QizLrgo9AYkAJtKI2bKABk5 =kGlC -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 7:57:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7295037B422; Thu, 3 May 2001 07:57:46 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id HAA03855; Thu, 3 May 2001 07:57:46 -0700 Date: Thu, 3 May 2001 07:57:45 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Bruce A. Mah" Cc: current@FreeBSD.ORG Subject: Re: lock order reversals, anyone? In-Reply-To: <200105031452.f43EqeX32443@bmah-freebsd-0.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 May 2001, Bruce A. Mah wrote: > If memory serves me right, Matthew Jacob wrote: > > > T-o-T about 24 hours ago: > > ??? Top of Tree > > > acquiring duplicate lock of same type: "allproc" > > > 1st @ /usr/src/sys/kern/kern_proc.c:609 > > > 2nd @ /usr/src/sys/kern/kern_proc.c:146 > > > lock order reversal > > > 1st vnode interlock last acquired @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:397 > > > 2nd 0xfffffc000080f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464 > > > 3rd 0xfffffe0026918080 vnode interlock @ /usr/src/sys/kern/vfs_subr.c:1881 > > I saw something similar on my 5-CURRENT box built around 27 April. No > core dumps that I know of. These showed up at boot time, shortly after > my machine's SCSI devices were probed. From /var/log/messages: > > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: da0: Fixed Direct Access SCSI-3 device > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: lock order reversal > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 2nd 0xcb64665c process lock @ /usr/src/sys/kern/kern_exit.c:542 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 3rd 0xc0e3f988 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: acquiring duplicate lock of same type: "allproc" > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 1st @ /usr/src/sys/kern/kern_proc.c:607 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 2nd @ /usr/src/sys/kern/kern_proc.c:144 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: lock order reversal > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 1st vnode interlock last acquired @ /usr/src/sys/kern/vfs_vnops.c:636 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 2nd 0xc050d060 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:975 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 3rd 0xccf9c52c vnode interlock @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:984 > May 2 10:19:12 bmah-freebsd-1 ntpd[355]: ntpd 4.0.99b Fri Apr 27 16:43:30 PDT 2001 (1) > May 2 10:19:12 bmah-freebsd-1 ntpd[355]: using kernel phase-lock loop 2040 > May 2 10:19:12 bmah-freebsd-1 ntpd[355]: using kernel phase-lock loop 2041 > > My machine is running a GENERIC kernel. > > Bruce. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 7:59: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A2E0437B424 for ; Thu, 3 May 2001 07:58:59 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id HAA03864; Thu, 3 May 2001 07:58:57 -0700 Date: Thu, 3 May 2001 07:58:56 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Chris Faulhaber Cc: current@freebsd.org Subject: Re: lock order reversals, anyone? In-Reply-To: <20010503105724.A14089@peitho.fxp.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=161827+165415+/usr/local/www/db/text/2001/freebsd-current/20010429.freebsd-current > Right- sorry to trouble you all. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 9:15:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id F117D37B424 for ; Thu, 3 May 2001 09:15:49 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f43GFdX30316 for ; Thu, 3 May 2001 18:15:39 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: make world börked ? From: Poul-Henning Kamp Date: Thu, 03 May 2001 18:15:38 +0200 Message-ID: <30314.988906538@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> ld echo " extern ld_emulation_xfer_type ld_elf_i386_emulation;" > ldemul-list.h echo "#define EMULATION_LIST &ld_elf_i386_emulation, 0" >> ldemul-list.h ln -sf /flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/emultempl/astring.sed stringify.sed yacc -d -o ldgram.c /flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldgram.y lex -t /flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlex.l > ldlex.c sh /flat/src/gnu/usr.bin/binutils/ld/genscripts.sh /flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld \"/usr/l ib\" i386-unknown-freebsd i386-unknown-freebsd i386-unknown-freebsd elf_i386 "" elf_i386 i386-unknown-freebsd rm -f .depend mkdep -f .depend -a -D_GNU_SOURCE -I- -I. -I/flat/src/gnu/usr.bin/binutils/ld/i386 -I/flat/src/gnu/usr.bin/binutils/ld -I/ flat/src/gnu/usr.bin/binutils/ld/../libbfd/i386 -I/flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/include -DDE FAULT_EMULATION=\"elf_i386\" -DTARGET=\"i386-unknown-freebsd\" -DSCRIPTDIR=\"/usr/obj/flat/src/i386/usr/libdata\" -I/flat/src /gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld -DVERSION=\"2.10.1\" -DBFD_VERSION=\"2.10.1\" -I/usr/obj/flat/src/i3 86/usr/include eelf_i386.c /flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldcref.c /flat/src/gnu/usr.bin/ binutils/ld/../../../../contrib/binutils/ld/ldctor.c /flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldemul .c /flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldexp.c /flat/src/gnu/usr.bin/binutils/ld/../../../../co ntrib/binutils/ld/ldfile.c ldgram.c /flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlang.c ldlex.c /flat/ src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldmain.c /flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/bi nutils/ld/ldmisc.c /flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldver.c /flat/src/gnu/usr.bin/binutils/l d/../../../../contrib/binutils/ld/ldwrite.c /flat/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/lexsup.c /flat/ src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/mri.c eelf_i386.c:158: elf-hints.h: No such file or directory mkdep: compile failed *** Error code 1 1 error *** Error code 2 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 9:51:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D4ED137B424 for ; Thu, 3 May 2001 09:51:39 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f43GpXG71885; Thu, 3 May 2001 09:51:34 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 03 May 2001 09:50:48 -0700 (PDT) From: John Baldwin To: Matthew Jacob Subject: RE: lock order reversals, anyone? Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-May-01 Matthew Jacob wrote: > > T-o-T about 24 hours ago: > >> lock order reversal >> 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239 >> 2nd 0xfffffe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542 >> 3rd 0xfffffe0000aab8d0 lockmgr interlock @ > /usr/src/sys/kern/kern_lock.c:239 This is new. We shouldn't be holding the proc lock and dinking with lockmgr at the same time. (Well, in theory at least.) >> acquiring duplicate lock of same type: "allproc" >> 1st @ /usr/src/sys/kern/kern_proc.c:609 >> 2nd @ /usr/src/sys/kern/kern_proc.c:146 This is old. This is really a case of recursion, I'm currently hacking on witness some more which will fix this. >> lock order reversal >> 1st vnode interlock last acquired @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:397 >> 2nd 0xfffffc000080f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464 >> 3rd 0xfffffe0026918080 vnode interlock @ /usr/src/sys/kern/vfs_subr.c:1881 This is quite old. I have some h0h0 patches to fix these, but I'm not sure that they are actually right: http://www.FreeBSD.org/~jhb/patches/mntvnode.patch >> pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped) > > (oh, yeah, a 4.1 built executable is dying, charming) Cute. :-/ -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 9:52:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id B2FE937B423 for ; Thu, 3 May 2001 09:52:31 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f43GpYG71889; Thu, 3 May 2001 09:51:35 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105031434.f43EYrG00732@Magelan.Leidinger.net> Date: Thu, 03 May 2001 09:50:48 -0700 (PDT) From: John Baldwin To: Alexander Leidinger Subject: RE: trap12: page fault Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-May-01 Alexander Leidinger wrote: > Hi, > > /sys from cvsup around 2pm CEST from cvsup3.de.freebsd.org (contains > npx.c fix). > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x54 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc01de7c3 > stack pointer = 0x10:0xd51cfd98 > frame pointer = 0x10:0xd51cfd98 > 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 = 6 (sh) > trap number = 12 > panic: page fault > syncing disks... > > No syncing of the disks happens, no coredump (dump device not configured > at this stage), hangs hard (need to press the reset button) after > printing "syncing disks...". Happens after printing "Routing Daemons:.", > before "Additional daemons: syslogd." > > It showed up the first time after the "eats FFS partitions for > breakfast" problem was fixed. I already removed > /sys/compile/, so it didn't seems to be a stale object > file. > > dmesg from a working kernel and kernel config attached. Can you get a trace next time via the 'trace' command? The virtual fault address indicates a likely NULL pointer dereference. Also, have you built your kernel with debug symnbols (config -g or makeoptions DEBUG=-g do this)? If so, can you go to /sys/compile/, run 'gdb -k kernel.debug' and then type 'l *0xc01de7c3' to see what source line it panic'd at? You may not need the '*' char in that. Thanks. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 10: 8:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 8EF4A37B422 for ; Thu, 3 May 2001 10:08:22 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f43H8DU66076; Thu, 3 May 2001 10:08:13 -0700 (PDT) (envelope-from obrien) Date: Thu, 3 May 2001 10:08:13 -0700 From: "David O'Brien" To: David Wolfskill Cc: current@freebsd.org Subject: Re: cvs commit: src/contrib/binutils/ld/emultempl elf32.em Message-ID: <20010503100813.A66013@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200105031448.f43Em8q37301@bunrab.catwhisker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105031448.f43Em8q37301@bunrab.catwhisker.org>; from david@catwhisker.org on Thu, May 03, 2001 at 07:48:08AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 03, 2001 at 07:48:08AM -0700, David Wolfskill wrote: > [Ref. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=574034+0+current/cvs-all] ... > eelf_i386.c:158: elf-hints.h: No such file or directory Crap,crap,crap,crap,crap!!! I thought I had gotten my systems clean enough when I did the post-commit ``make buildworld'' test. *sigh* a nice bootstrap issue here. Problem is elf-hints.h is a new header and a buildtool uses it. I guess a -I/usr/src/include is needed (or an install of headers into /usr/obj). To get over this hump if you aren't interested in debugging the bootstrap issue: cd /usr/src/include make obj make install -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 10:23:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 40EE337B423; Thu, 3 May 2001 10:23:52 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f43HNmb65803; Thu, 3 May 2001 11:23:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200105031723.f43HNmb65803@harmony.village.org> To: obrien@FreeBSD.ORG Subject: Re: cvs commit: src/contrib/binutils/ld/emultempl elf32.em Cc: David Wolfskill , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 03 May 2001 10:08:13 PDT." <20010503100813.A66013@dragon.nuxi.com> References: <20010503100813.A66013@dragon.nuxi.com> <200105031448.f43Em8q37301@bunrab.catwhisker.org> Date: Thu, 03 May 2001 11:23:48 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010503100813.A66013@dragon.nuxi.com> "David O'Brien" writes: : On Thu, May 03, 2001 at 07:48:08AM -0700, David Wolfskill wrote: : > [Ref. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=574034+0+current/cvs-all] : ... : > eelf_i386.c:158: elf-hints.h: No such file or directory : : Crap,crap,crap,crap,crap!!! : I thought I had gotten my systems clean enough when I did the post-commit : ``make buildworld'' test. *sigh* a nice bootstrap issue here. Problem : is elf-hints.h is a new header and a buildtool uses it. I guess a : -I/usr/src/include is needed (or an install of headers into /usr/obj). You would have to add -I/usr/include before the -I/usr/src/include. Otherwise things will compile with the host's stdio and friends, which could be bad if there were a mismatch between them (like in FILE definitions, say). Sometimes I think that adding a "cross update install" target which would put new .h files into /usr/obj/mumble/include might not be a bad thing.... : To get over this hump if you aren't interested in debugging the bootstrap : issue: : : cd /usr/src/include : make obj : make install This is kinda hard when compiling current on a stable system that you wish to remain stable system after the compile :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 10:57:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 5589F37B43F for ; Thu, 3 May 2001 10:57:42 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id KAA25784 for ; Thu, 3 May 2001 10:57:41 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpdAAAozaGvY; Thu May 3 10:57:33 2001 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id LAA28955 for current@freebsd.org; Thu, 3 May 2001 11:02:10 -0700 (MST) From: Terry Lambert Message-Id: <200105031802.LAA28955@usr05.primenet.com> Subject: Re: panic in fxp driver To: current@freebsd.org Date: Thu, 3 May 2001 18:02:10 +0000 (GMT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ] I would be quite interested in knowing just how you manage ] to accomplish that, given that all the transmit control buffers ] are arranged in a circular linked list: ] ] fxp_init(void *xsc) ] { ] ... ] for (i = 0; i < FXP_NTXCB; i++) { ] ... ] txp[i].next = &txp[(i + 1) & FXP_TXCB_MASK]; ] } ] ] ] I would suggest actually examining the rest of the code to see ] how it works before making erroneous proclamations based on the ] myopic examination of a single statement. I would suggest a less than myopic examination of the subject line. In particular, I saw a repeatable panic under extremely heavy load. Please consider the case where there are two mbuf chains being transmitted, which look like this: A B header O O \ / \ / \ / data 1 O | data 2 O | data 3 O Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 11:28:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id AC51937B422 for ; Thu, 3 May 2001 11:28:45 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f43ISSi06097; Thu, 3 May 2001 13:28:28 -0500 (CDT) (envelope-from jlemon) Date: Thu, 3 May 2001 13:28:28 -0500 (CDT) From: Jonathan Lemon Message-Id: <200105031828.f43ISSi06097@prism.flugsvamp.com> To: tlambert@primenet.com, current@freebsd.org Subject: Re: panic in fxp driver X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >] I would be quite interested in knowing just how you manage >] to accomplish that, given that all the transmit control buffers >] are arranged in a circular linked list: >] >] fxp_init(void *xsc) >] { >] ... >] for (i = 0; i < FXP_NTXCB; i++) { >] ... >] txp[i].next = &txp[(i + 1) & FXP_TXCB_MASK]; >] } >] >] >] I would suggest actually examining the rest of the code to see >] how it works before making erroneous proclamations based on the >] myopic examination of a single statement. > >I would suggest a less than myopic examination of the subject >line. I'm quite aware of the subject line; but you're changing the subject here. Any panic has nothing to do with the "next" pointer being NULL, as you stated in the previous email, since this is not possible, assuming correct operation of the code. >In particular, I saw a repeatable panic under extremely heavy >load. I'm sorry, my MTA must have dropped your bug report, as it appears to be missing. Can you please resend? In particular, a stack backtrace and preferably a crashdump, and leave off any wild hypothesis of where the bugs are, unless you have supporting evidence. >Please consider the case where there are two mbuf chains being >transmitted, which look like this: Um. "Not Possible". -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 11:44:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail3.intermedia.net (mail3.intermedia.net [206.40.48.153]) by hub.freebsd.org (Postfix) with ESMTP id 547A537B59E for ; Thu, 3 May 2001 11:43:45 -0700 (PDT) (envelope-from tonyg@crazynickels.com) Received: from mail.crazynickels.com (unverified [64.78.44.128]) by mail3.intermedia.net (Rockliffe SMTPRA 4.2.4) with ESMTP id for ; Thu, 3 May 2001 11:37:28 -0700 Message-ID: Content-type: text/plain Date: Thu, 03 May 2001 11:42:31 -0700 From: tonyg@crazynickels.com Subject: Web Development To: freebsd-current@FreeBSD.org X-mailer: CrazyNickels.Com Email Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Hi, I do web development and database work out of Las Vegas. I was wondering if you needed any development done. I have been doing web work for 6 years. I know Cold Fusion, ASP, Oracle, SQL and Flash. Tony Grijalva 702.951.3051 Here's some the sites I've worked on: http://www.crazynickels.com - Complete site. Turned out in 3 days. http://www.woodtrim.com - Complete sites along with www.brushed aluminum.com as a content manager, shopping cart, FAQ, Referral Program. http://www.SchoolCity.com - Pre-IPO Company I did the Complete site. I can send you a complete document about this site. http://www.codernet.com - My own site with a bunch of guys here. I did the graphics. http://www.antennas.com - The graphics were given to me in PhotoShop format. I have to make them web ready and add functions. http://www.momentisgroup.com - Backend Cold Fusion work. http://www.isecinc.com - Their print company in Arizona sent me the project and related functions. I can walk you through a back door process. http://www.reoinc.com - Working on Now. http://www.arraybiopharma.com - Needed the site before they went public... I didn't do the flash but everything else and some cgi. http://www.linworth.com - Got PhotoShop files. Added Cold Fusion functions. Please let me know if you need any help...... Thank You for your time and consideration, Tony Grijalva 702.951.3051 tonyg@codernet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 12:18:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by hub.freebsd.org (Postfix) with ESMTP id 4A16037B422; Thu, 3 May 2001 12:18:48 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id D37EC17D38; Thu, 3 May 2001 21:18:46 +0200 (CEST) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.11.3/8.11.3) id f43JHae05283; Thu, 3 May 2001 21:17:36 +0200 (CEST) (envelope-from schweikh) Date: Thu, 3 May 2001 21:17:36 +0200 From: Jens Schweikhardt To: Alexander Leidinger Cc: freebsd-current@FreeBSD.ORG, hm@FreeBSD.ORG, ru@FreeBSD.org Subject: Re: isdn stops working when load increases Message-ID: <20010503211736.E1024@schweikhardt.net> References: <20010502210326.F1280@schweikhardt.net> <200105031139.f43BdrK02953@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105031139.f43BdrK02953@Magelan.Leidinger.net>; from Alexander@Leidinger.net on Thu, May 03, 2001 at 01:39:50PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 03, 2001 at 01:39:50PM +0200, Alexander Leidinger wrote: # On 2 Mai, Jens Schweikhardt wrote: # # [Ruslan: I CCed you because of the second part of the mail] # # > I've seen some recent mails related to rtprio oddity which seemed # > to also affect the isdnd. My -current is cvsupped May 1st (and # # Yes, it didn't started with the broken version of rtprio (I had to # remove the rtprio keyword). # # > survived; I've still got a fully populated root fs :-) # # I got a kernel panic with no coredump, I hope the npx commit fixed this, # will test later. # # > However, as soon as I do a find / or buildworld or some other # > commands increasing the load significantly (about 1 or more), # > isdnd seems to take a nap. No more packets transmitted. If I # > suspend the running programs, isdnd awakes and continues. # > Is anybody else observing the same behavior? # # Not with my Apr 29 kernel (no rtprio keyword in isdnd.rc), at least I # didn't noticed it. # # BTW: What about dial-on-demand? Still ok. I have rtprio 25 (as from the isdnd.rc.sample, should I tune this? Remove the line?) in my isdnd.rc and this at the end of /etc/rc.isdn: echo 'removing previous isp0 config' ifconfig isp0 delete -link1 down echo 'setting sppp options' ispppcontrol isp0 myauthproto=pap myauthname=xxxxxxxx myauthsecret=xxxxxxxx hisauthproto=none callin echo 'configuring isp0' ifconfig isp0 1.2.3.4 5.6.7.8 netmask 0xffffffff link1 2>/dev/null Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 12:44:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id 6357337B422; Thu, 3 May 2001 12:44:49 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-194-8-205-7.netcologne.de [194.8.205.7]) by mr200.netcologne.de (Mirapoint) with ESMTP id AER15512; Thu, 3 May 2001 21:44:45 +0200 (CEST) Received: (from marc@localhost) by oranje.my.domain (8.11.3/8.11.3) id f43JigM58905; Thu, 3 May 2001 21:44:42 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Thu, 3 May 2001 21:44:42 +0200 (CEST) Message-Id: <200105031944.f43JigM58905@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: obrien@freebsd.org, freebsd-current@freebsd.org Subject: -current breaks Reply-To: van.woerkom@netcologne.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried to compile and got this one: ===> ld ln -sf /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/emultempl/astring.sed stringify.sed sh /usr/src/gnu/usr.bin/binutils/ld/genscripts.sh /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld \"/usr/lib\" i386-unknown-freebsd i386-unknown-freebsd i386-unknown-freebsd elf_i386 "" elf_i386 i386-unknown-freebsd echo " extern ld_emulation_xfer_type ld_elf_i386_emulation;" > ldemul-list.h echo "#define EMULATION_LIST &ld_elf_i386_emulation, 0" >> ldemul-list.h yacc -d -o ldgram.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldgram.y lex -t /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlex.l > ldlex.c rm -f .depend mkdep -f .depend -a -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/ld/i386 -I/usr/src/gnu/usr.bin/binutils/ld -I/usr/src/gnu/usr.bin/binutils/ld/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/include -DDEFAULT_EMULATION=\"elf_i386\" -DTARGET=\"i386-unknown-freebsd\" -DSCRIPTDIR=\"/usr/obj/usr/src/i386/usr/libdata\" -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld -DVERSION=\"2.10.1\" -DBFD_VERSION=\"2.10.1\" -I/usr/obj/usr/src/i386/usr/include eelf_i386.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldcref.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldctor.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldemul.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldexp.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldfile.c ldgram.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlang.c ldlex.c /usr/src! /gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldmain.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldmisc.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldver.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldwrite.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/lexsup.c /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/mri.c eelf_i386.c:158: elf-hints.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/ld. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Thu May 3 20:22:08 CEST 2001 Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 13:50:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 0483D37B422; Thu, 3 May 2001 13:50:56 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id NAA23966; Thu, 3 May 2001 13:43:27 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpdAAAaua4VU; Thu May 3 13:43:22 2001 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id NAA01895; Thu, 3 May 2001 13:55:26 -0700 (MST) From: Terry Lambert Message-Id: <200105032055.NAA01895@usr05.primenet.com> Subject: Any chance of release patch being committed? To: current@freebsd.org Date: Thu, 3 May 2001 20:55:26 +0000 (GMT) Cc: jkh@freebsd.org X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello? I thought I had defended the reasons for my wanting the patch so that the KERNCONF in /usr/src/release/Makefile actually worked with sysinstall well enough that the patch should be committed... I haven't seen a commit go by... any chance of that change being committed? It doesn't really change the resulting code, unless KERNCONF is set to something other than GENERIC. Isn't anyone but me and Walnut Creek cum BSDI cum Windriver Systems using "make release"?!? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 15: 1: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.6.200.230]) by hub.freebsd.org (Postfix) with ESMTP id 3AA9637B422; Thu, 3 May 2001 15:01:02 -0700 (PDT) (envelope-from mdharnois@home.com) Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id 4ED2A14A11; Thu, 3 May 2001 17:01:24 -0500 (CDT) To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: make world bXrked ? Keywords: error References: <30314.988906538@critter> From: Michael Harnois Date: 03 May 2001 17:01:23 -0500 In-Reply-To: <30314.988906538@critter> (Poul-Henning Kamp's message of "Thu, 03 May 2001 18:15:38 +0200") Message-ID: <86oftat7m4.fsf@mharnois.workgroup.net> Lines: 14 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.5 (alfalfa) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 03 May 2001 18:15:38 +0200, Poul-Henning Kamp said: > eelf_i386.c:158: elf-hints.h: No such file or directory mkdep: > compile failed *** Error code 1 1 error *** Error code 2 I puzzled over this, and finally found that beginning the magical incantations with "make includes" would get me past the problem. -- Michael D. Harnois mdharnois@home.com Redeemer Lutheran Church Washburn, Iowa When the outcome of a meeting is to have another meeting, it has been a lousy meeting. -- Herbert Clark Hoover To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 15: 3: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A1F0D37B424; Thu, 3 May 2001 15:03:02 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA05791; Thu, 3 May 2001 15:03:01 -0700 Date: Thu, 3 May 2001 15:03:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Michael Harnois Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: make world bXrked ? In-Reply-To: <86oftat7m4.fsf@mharnois.workgroup.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes- And David has checked in a hack to avoid this for now too. > On Thu, 03 May 2001 18:15:38 +0200, Poul-Henning Kamp said: > > > > eelf_i386.c:158: elf-hints.h: No such file or directory mkdep: > > compile failed *** Error code 1 1 error *** Error code 2 > > I puzzled over this, and finally found that beginning the magical > incantations with "make includes" would get me past the problem. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 15:19:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 15E5437B423 for ; Thu, 3 May 2001 15:19:25 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id AAA03085 for freebsd-current@freebsd.org; Fri, 4 May 2001 00:19:23 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f43M0wD89227; Fri, 4 May 2001 00:00:58 +0200 (MET DST) (envelope-from j) Date: Fri, 4 May 2001 00:00:58 +0200 (MET DST) Message-Id: <200105032200.f43M0wD89227@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <200105032055.NAA01895@usr05.primenet.com> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Any chance of release patch being committed? X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > Isn't anyone but me and Walnut Creek cum BSDI cum Windriver > Systems using "make release"?!? We are, but why would we use anything else than GENERIC for it, seriously? I'd never roll a `release' for my current machine. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 18:57:47 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 D06F937B423; Thu, 3 May 2001 18:57:43 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 LAA12136; Fri, 4 May 2001 11:57:25 +1000 Date: Fri, 4 May 2001 11:56:15 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: obrien@FreeBSD.ORG, David Wolfskill , current@FreeBSD.ORG Subject: Re: cvs commit: src/contrib/binutils/ld/emultempl elf32.em In-Reply-To: <200105031723.f43HNmb65803@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 May 2001, Warner Losh wrote: > In message <20010503100813.A66013@dragon.nuxi.com> "David O'Brien" writes: > ... > : I thought I had gotten my systems clean enough when I did the post-commit > : ``make buildworld'' test. *sigh* a nice bootstrap issue here. Problem > : is elf-hints.h is a new header and a buildtool uses it. I guess a > : -I/usr/src/include is needed (or an install of headers into /usr/obj). ^^^^ should be a relative path. Fixed in the committed version > You would have to add -I/usr/include before the -I/usr/src/include. > Otherwise things will compile with the host's stdio and friends, which > could be bad if there were a mismatch between them (like in FILE > definitions, say). The committed version has this bug. > Sometimes I think that adding a "cross update install" target which > would put new .h files into /usr/obj/mumble/include might not be a bad > thing.... This has essentially the same problems as putting /usr/src/include before /usr/include. Very few headers outside of /usr/include are certain to work on the host for _all_ cross-tools. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 3 21:28:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 7B6B537B423; Thu, 3 May 2001 21:28:39 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f444SQf96606; Fri, 4 May 2001 00:28:26 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 4 May 2001 00:28:26 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Joerg Wunsch Cc: freebsd-current@freebsd.org, imp@freebsd.org Subject: Re: Any chance of release patch being committed? In-Reply-To: <200105032200.f43M0wD89227@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 May 2001, J Wunsch wrote: > Terry Lambert wrote: > > > Isn't anyone but me and Walnut Creek cum BSDI cum Windriver > > Systems using "make release"?!? > > We are, but why would we use anything else than GENERIC for it, > seriously? I'd never roll a `release' for my current machine. Actually, I'd love to see a release rolled using NEWCARD for current.freebsd.org, so we can install using cardbus notebooks. This came up today actually... Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 0:29: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1E27337B422; Fri, 4 May 2001 00:29:01 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f447Ssb74387; Fri, 4 May 2001 01:29:00 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200105040729.f447Ssb74387@harmony.village.org> To: Robert Watson Subject: Re: Any chance of release patch being committed? Cc: Joerg Wunsch , freebsd-current@freebsd.org In-reply-to: Your message of "Fri, 04 May 2001 00:28:26 EDT." References: Date: Fri, 04 May 2001 01:28:54 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Robert Watson writes: : Actually, I'd love to see a release rolled using NEWCARD for : current.freebsd.org, so we can install using cardbus notebooks. This came : up today actually... CARDBUS still has issues on a number of laptops. However, the number of laptops for which it is useful is interestingly large. I've never tried to install off of cardbus devices... If anybody has or tries it, let me know. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 0:48:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 793BF37B422 for ; Fri, 4 May 2001 00:48:46 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14vaKQ-0006X4-00; Fri, 04 May 2001 09:48:42 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id JAA27193; Fri, 4 May 2001 09:48:41 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 26888; Fri May 4 09:46:49 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14vaIb-0008Mh-00; Fri, 04 May 2001 09:46:49 +0200 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@freebsd.org Subject: Re: Any chance of release patch being committed? In-reply-to: Your message of "Fri, 04 May 2001 00:00:58 +0200." <200105032200.f43M0wD89227@uriah.heep.sax.de> Date: Fri, 04 May 2001 09:46:49 +0200 Message-ID: <32158.988962409@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 04 May 2001 00:00:58 +0200, J Wunsch wrote: > We are, but why would we use anything else than GENERIC for it, > seriously? I'd never roll a `release' for my current machine. When you get commitment to a fixed hardware configuration for two years and you want to leave your datacenter full of hosts ready to power up and play off a custom CDROM, a release that uses a custom kernel is desirable. That said, I don't think that the release should pick up KERNCONF. I think a middle-ground option is to have the release pick up RELEASE_KERNCONF. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 1:22:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from webimprovement.com (webimprovement.com [161.58.166.156]) by hub.freebsd.org (Postfix) with ESMTP id C3FAC37B43C for ; Fri, 4 May 2001 01:22:44 -0700 (PDT) (envelope-from webimpro@webimprovement.com) Received: (webimpro@localhost) by webimprovement.com (8.8.8) id EAA03644; Fri, 4 May 2001 04:22:44 -0400 (EDT) Date: Fri, 4 May 2001 04:22:44 -0400 (EDT) Message-Id: <200105040822.EAA03644@webimprovement.com> To: current@freebsd.org From: "BlackOffers.com Newsletters" Reply-To: "BlackOffers.com Newsletters" Subject: You've Been Added! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is to confirm the addition of your email address: current@freebsd.org to the BlackOffers.com Newsletters Subscribe Me mailing list. If you feel you have received this notice in error, please visit the BlackOffers.com Newsletters Subscribe Me mailing list at our website: http://www.mybmail.com to remove yourself automatically, or click the link below: http://mybmail.com/cgi-bin/info/s.pl?r=1&l=16&e=current=:freebsd.org Thank you, BlackOffers.com Newsletters To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 1:23:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from webimprovement.com (webimprovement.com [161.58.166.156]) by hub.freebsd.org (Postfix) with ESMTP id 19B6737B423 for ; Fri, 4 May 2001 01:23:44 -0700 (PDT) (envelope-from webimpro@webimprovement.com) Received: (webimpro@localhost) by webimprovement.com (8.8.8) id EAA03707; Fri, 4 May 2001 04:23:43 -0400 (EDT) Date: Fri, 4 May 2001 04:23:43 -0400 (EDT) Message-Id: <200105040823.EAA03707@webimprovement.com> To: current@freebsd.org From: "BlackOffers.com Newsletters" Reply-To: "BlackOffers.com Newsletters" Subject: You've Been Removed! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is to confirm the removal of your email address: current@freebsd.org from the BlackOffers.com Newsletters Subscribe Me mailing list. We're sorry to see you go! If you feel you have received this notice in error, please visit the BlackOffers.com Newsletters Subscribe Me mailing list at our website: http://www.mybmail.com to add yourself automatically, or click on the link below to automatically re-subscribe yourself: http://mybmail.com/cgi-bin/info/s.pl?a=1&l=16&e=current=:freebsd.org Thank you, BlackOffers.com Newsletters To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 1:46:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from hall.mail.mindspring.net (hall.mail.mindspring.net [207.69.200.60]) by hub.freebsd.org (Postfix) with ESMTP id D1C9337B423 for ; Fri, 4 May 2001 01:46:24 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0075.cvx7-bradley.dialup.earthlink.net [209.178.164.75]) by hall.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id EAA20675; Fri, 4 May 2001 04:46:20 -0400 (EDT) Message-ID: <3AF26C70.B8470992@mindspring.com> Date: Fri, 04 May 2001 01:46:40 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Joerg Wunsch Cc: freebsd-current@FreeBSD.ORG Subject: Re: Any chance of release patch being committed? References: <200105032055.NAA01895@usr05.primenet.com> <200105032200.f43M0wD89227@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG J Wunsch wrote: > Terry Lambert wrote: > > > Isn't anyone but me and Walnut Creek cum BSDI cum Windriver > > Systems using "make release"?!? > > We are, but why would we use anything else than GENERIC for it, > seriously? I'd never roll a `release' for my current machine. Examples abound: 1) Licensed commercial drivers not present in GENERIC 2) Cut down kernel for low memory systems 3) Kernel without support for 686/586/386 in an embedded system 4) Kernel without most of the disk controllers, e.g. a Compaq-specific "Jump Start" disk for FreeBSD Etc. It shouldn't matter anyway; it doesn't change the normal default sysinstall behaviour, image, or image size at all (the image is identical), unless KERNCONF is overridden. If that's so unreasonable, I suggest you remove the "?" before the "=" in /usr/src/release/Makefile in the KERNCONF assignment, which looks like: KERNCONF?=GENERIC Since it makes damn little sense to allow it to be overridden, if the resulting CDROM will fail to install /kernel, and the resulting system will not be able to boot without an explict "load kernel.MYKERNEL" command to the boot loader. Doing that would reduce functionality; making my change would increase it... but make one or the other of them, please: in it's current state, the code _pretends_ that an override will work, when it will not. I hate code that lies to me, even if by omission; don't you? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 2:53:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 448CD37B422; Fri, 4 May 2001 02:53:51 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.22 #1) id 14vcHW-0000X0-00; Fri, 04 May 2001 11:53:50 +0200 Received: from b85d3.pppool.de ([213.7.133.211] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.22 #1) id 14vcHV-0005xf-00; Fri, 04 May 2001 11:53:50 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.3/8.11.3) with ESMTP id f449rgh44495; Fri, 4 May 2001 11:53:43 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200105040953.f449rgh44495@Magelan.Leidinger.net> Date: Fri, 4 May 2001 11:53:41 +0200 (CEST) From: Alexander Leidinger Subject: Re: isdn stops working when load increases To: schweikh@schweikhardt.net Cc: freebsd-current@FreeBSD.ORG, hm@FreeBSD.ORG, ru@FreeBSD.ORG In-Reply-To: <20010503211736.E1024@schweikhardt.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3 Mai, Jens Schweikhardt wrote: > # > However, as soon as I do a find / or buildworld or some other > # > commands increasing the load significantly (about 1 or more), > # > isdnd seems to take a nap. No more packets transmitted. If I > # > suspend the running programs, isdnd awakes and continues. > # > Is anybody else observing the same behavior? > # > # Not with my Apr 29 kernel (no rtprio keyword in isdnd.rc), at least I > # didn't noticed it. > # > # BTW: What about dial-on-demand? > > Still ok. I have rtprio 25 (as from the isdnd.rc.sample, should I tune this? > Remove the line?) in my isdnd.rc and this at the end of /etc/rc.isdn: I think Hellmuth choosed a good value for rtprio, and I didn't think it solves your problem if you increase the value, but feel free to play a little bit with it (I think isdnd slowes down because of a lot of interrupts, and if I didn't have a wrong understanding of the system, rtprio didn't helps in this case). > echo 'removing previous isp0 config' > ifconfig isp0 delete -link1 down > echo 'setting sppp options' > ispppcontrol isp0 myauthproto=pap myauthname=xxxxxxxx myauthsecret=xxxxxxxx hisauthproto=none callin > echo 'configuring isp0' > ifconfig isp0 1.2.3.4 5.6.7.8 netmask 0xffffffff link1 2>/dev/null What's your defaultroute? I use "-interface isp1". BTW: I use /etc/start_if.isp1 to configure the interface, no need to modify rc.isdn, e.g.: ---snip--- (11) root@ttyp0 # less /etc/start_if.isp1 ifconfig isp1 link1 0.0.0.0 0.0.0.1 netmask 255.255.0.0 ispppcontrol isp1 $(cat /etc/isdn/connect-CBC.parameters) enable-vj ifconfig isp1 down ---snip---. While we're at it, maybe someone wants to commit something like this: ---snip--- --- /usr/src/etc/rc.isdn Sat Apr 28 14:49:22 2001 +++ /etc/rc.isdn Sun Apr 29 15:37:04 2001 @@ -38,6 +38,23 @@ [Yy][Ee][Ss]) echo -n 'ISDN subsystem setup:' + # Terminal type for fullscreen mode, default to syscons driver + # + if [ ! -n "${isdn_ttype}" ]; then + isdn_ttype=cons25 + fi + if [ -n "${isdn_screenflags}" ]; then + /usr/sbin/vidcontrol < ${isdn_fsdev} > ${isdn_fsdev} 2>&1 ${isdn_screenflags} + fi + + # Check for pcvt driver (VT100/VT220 emulator) + # + if [ -x /usr/sbin/ispcvt ]; then + if /usr/sbin/ispcvt; then + isdn_ttype=pcvt25 + fi + fi + case ${isdn_flags} in [Nn][Oo]) isdn_flags='' ---snip--- (I think the isdn_ttype part isn't needed anymore, someone committed something like this already, but the screenflags part is useful for me) Bye, Alexander. -- Loose bits sink chips. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 4:38:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id A2BBD37B422 for ; Fri, 4 May 2001 04:38:25 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f44BcM898163 for ; Fri, 4 May 2001 20:38:23 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <3AF26C70.B8470992@mindspring.com> References: <200105032055.NAA01895@usr05.primenet.com> <200105032200.f43M0wD89227@uriah.heep.sax.de> <3AF26C70.B8470992@mindspring.com> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.5 (alfalfa) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 11 From: Makoto MATSUSHITA To: current@freebsd.org Subject: Re: Any chance of release patch being committed? Date: Fri, 04 May 2001 20:38:06 +0900 Message-Id: <20010504203806U.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tlambert2> Examples abound: All of examples are just "we want yet another *generic* kernel for specific machines". Why you don't replace src/sys/${arch}/conf/GENERIC file to your own (customized) version? It is too simple, and matches your requirements. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 5: 2:28 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 5750437B424 for ; Fri, 4 May 2001 05:02:24 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 WAA05727; Fri, 4 May 2001 22:02:17 +1000 Date: Fri, 4 May 2001 21:59:45 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Daniel Eischen Cc: current@FreeBSD.ORG Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 May 2001, Daniel Eischen wrote: > On Wed, 2 May 2001, Bruce Evans wrote: > > > I am planning on using %fs for TSD/KSD and want it to be valid > > > in signal handlers. > > > > Imagine doing the same thing with %ds, or better yet, %ss. %ss must > > be set to the default for the kernel to even provide a "normal" stack > > for the signal handler. Similarly for %ds, except it is possible for > > signal handlers to set up their own %ds as necessary provided both > > the user code and the signal trampoline is written to avoid using %ds > > before initializing it. > > Well, we're not using %ds or %ss for TSD. It was discussed on Someone else might :-). > -arch some time ago that we would reserve %fs for TSD, so we > really on care about that case. I threw in %gs because that > was also an option except that WINE used it. > > [ patch snipped ] > > > There is also the osendsig() case, and corresponding code in several > > emulators. > > I don't think we care too much about osendsig() since anything > that uses a new threads library will have to be recompiled > and wouldn't use the old routines. I think the same is true > for emulators; an application that used the new threads library > wouldn't be running in emulation would it? A library running under an emulator might. Non-emulated Linux seems to pass %fs and %gs to signal handlers unchanged, so there is a precedent for doing things like you want. Go ahead. The Linux emulator certainly needs to do it the same as Linux. > So, what if we just make the change for %fs. Or is there a way > to tell the kernel "Hey, I don't want %fs to be changed" when > setting up the signal handler? A flag to sigaction sa_flags? > > The other option is for the userland signal handler to fetch > the value for %fs out of the sigcontext^Wucontext and manually > set it. But this gets icky because now the threads library has > to have arch-dependent signal handlers. Setting arch-dependent sigaction flags might be icky too. Add some later if the default behaviour causes problems. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 5:39:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by hub.freebsd.org (Postfix) with ESMTP id CEBFD37B424 for ; Fri, 4 May 2001 05:39:37 -0700 (PDT) (envelope-from gwk@hunter.munich.sgi.com) Received: from sgiger.munich.sgi.com (sgiger.munich.sgi.com [144.253.192.2]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id OAA819498; Fri, 4 May 2001 14:39:30 +0200 (CEST) mail_from (gwk@hunter.munich.sgi.com) Received: from cuckoo.munich.sgi.com (cuckoo.munich.sgi.com [144.253.192.109]) by sgiger.munich.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id OAA25126; Fri, 4 May 2001 14:39:28 +0200 Received: from hunter.munich.sgi.com (hunter.munich.sgi.com [144.253.197.18]) by cuckoo.munich.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id OAA20941; Fri, 4 May 2001 14:39:28 +0200 (CEST) Received: (from gwk@localhost) by hunter.munich.sgi.com (8.11.3/8.11.3) id f44CdCQ11482; Fri, 4 May 2001 14:39:12 +0200 (CEST) (envelope-from gwk) Date: Fri, 4 May 2001 14:39:12 +0200 From: "Georg-W. Koltermann" To: Dag-Erling Smorgrav Cc: current@freebsd.org, David Wolfskill Subject: Re: lockup after resume Message-ID: <20010504143910.B11325@hunter.munich.sgi.com> Mail-Followup-To: Dag-Erling Smorgrav , current@freebsd.org, David Wolfskill References: <20010328212426.A32322@hunter.munich.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Mon, Apr 09, 2001 at 11:10:54AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 11:10:54AM +0200, Dag-Erling Smorgrav wrote: > "Georg-W. Koltermann" writes: > > I am experiencing a strange lockup with -current as of about a week > > ago: It will suspend and resume, but after the resume the console is > > dead and the system hangs after a short while. > > I'm seeing this too on my laptop. Used to work fine, no longer does. > I'll try the latest & greatest and see if the problem goes away. > > DES Dag-Erling, I CVSuped twice since my initial report, and the problem is still there. On the other hand I have a report from David Wolfskill that suspend/resume works fine for him. a) Does suspend/resume now work for you? b) What hardware/firmware do you have (mine is a DELL Inspiron 7500 with BIOS rev A12)? c) David, since it seems to work for you, what hardware/firmware do you have? One surprising observation: If I disable APM in /boot/device.hints, my machine suspends and resumes JUST FINE. The BIOS alone seems to be able to suspend and awake the hardware behind FreeBSD's back. The system only hangs if FreeBSD is involved in the process. -- Regards, Georg. ---------------------------------------------------------------------- Who in the world needs 2000 Windows? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 6: 1:31 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 B9BAB37B422 for ; Fri, 4 May 2001 06:01:27 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f44D1RS40539; Fri, 4 May 2001 06:01:27 -0700 (PDT) Date: Fri, 4 May 2001 06:01:27 -0700 (PDT) From: David Wolfskill Message-Id: <200105041301.f44D1RS40539@bunrab.catwhisker.org> To: des@ofug.org, gwk@sgi.com Subject: Re: lockup after resume Cc: current@freebsd.org In-Reply-To: <20010504143910.B11325@hunter.munich.sgi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Fri, 4 May 2001 14:39:12 +0200 >From: "Georg-W. Koltermann" >I CVSuped twice since my initial report, and the problem is still >there. On the other hand I have a report from David Wolfskill that >suspend/resume works fine for him. Right. >c) David, since it seems to work for you, what hardware/firmware do > you have? It's similar to a Dell Inspiron 5000e (I suspect it's made by the same folks). http://www.catwhisker.org/~david/FreeBSD/laptop.html for more detail than folks are likely to want (though it does include a link to a floppy image that I used to update the BIOS; note that said BIOS claims to be for either my (type of) machine or a Dell Inspiron 5000e). >One surprising observation: If I disable APM in /boot/device.hints, my >machine suspends and resumes JUST FINE. The BIOS alone seems to be >able to suspend and awake the hardware behind FreeBSD's back. The >system only hangs if FreeBSD is involved in the process. Curiouser and curiouser.... Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 6:21:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id D7D7D37B422 for ; Fri, 4 May 2001 06:21:17 -0700 (PDT) (envelope-from sheldonh@uunet.co.za) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14vfWE-00037x-00; Fri, 04 May 2001 15:21:14 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id PAA23270; Fri, 4 May 2001 15:20:57 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 22916; Fri May 4 15:19:35 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.22 #1) id 14vfUd-0009Jr-00; Fri, 04 May 2001 15:19:35 +0200 To: Makoto MATSUSHITA Cc: current@freebsd.org Subject: Re: Any chance of release patch being committed? In-reply-to: Your message of "Fri, 04 May 2001 20:38:06 +0900." <20010504203806U.matusita@jp.FreeBSD.org> Date: Fri, 04 May 2001 15:19:35 +0200 Message-ID: <35826.988982375@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 04 May 2001 20:38:06 +0900, Makoto MATSUSHITA wrote: > All of examples are just "we want yet another *generic* kernel for > specific machines". > > Why you don't replace src/sys/${arch}/conf/GENERIC file to your own > (customized) version? It is too simple, and matches your requirements. Because that's a repo-backed file. Why make me manage CVS conflicts on update? Why not just allow something like RELEASE_KERNCONF? What's the real objection to it? So far, all I've heard is "Gee, I've never needed that". :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 7:35:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.zilium.de (plattgetrampelt.von.zilium.de [195.88.176.132]) by hub.freebsd.org (Postfix) with ESMTP id 24C5637B424 for ; Fri, 4 May 2001 07:35:30 -0700 (PDT) (envelope-from joerg@zilium.de) Received: by mail.zilium.de (Postfix, from userid 1003) id E77B3F855; Fri, 4 May 2001 16:35:30 +0200 (CEST) Date: Fri, 4 May 2001 16:35:30 +0200 From: Joerg Bornschein To: freebsd-current@freebsd.org Subject: Re: isdn stops working when load increases Message-ID: <20010504163530.A41236@plattwurst.zilium.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001 at 09:03:26PM +0200, Jens Schweikhardt wrote: Hello, > I've seen some recent mails related to rtprio oddity which seemed > to also affect the isdnd. My -current is cvsupped May 1st (and > survived; I've still got a fully populated root fs :-) > > However, as soon as I do a find / or buildworld or some other > commands increasing the load significantly (about 1 or more), > isdnd seems to take a nap. No more packets transmitted. If I > suspend the running programs, isdnd awakes and continues. > Is anybody else observing the same behavior? I'm having similar problems: Some minutes/hours (depends on the workload) after each boot 'top' reports about 12% of my CPU time are used for interrupt processing. The interrupt time stays at about 10% even when there's nothing to do (no disk io, no network traffic, no sound). Running FBSD 4.2 on the same box reports about 0.2-1% interrupt usage; the same value which is shown on CURRENT just after a reboot. At the same time the packet loss rate of my isdn interface raises to about 70% while transfering files. (a simple ping does *not* trigger this problem). This behavior seems not related to rtprio oddity since i first noticed it on Apr 9th. (the date this box switched to CURRENT) joerg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 7:57:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 860ED37B43F for ; Fri, 4 May 2001 07:57:33 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id QAA34831; Fri, 4 May 2001 16:57:19 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Georg-W. Koltermann" Cc: current@freebsd.org, David Wolfskill Subject: Re: lockup after resume References: <20010328212426.A32322@hunter.munich.sgi.com> <20010504143910.B11325@hunter.munich.sgi.com> From: Dag-Erling Smorgrav Date: 04 May 2001 16:57:19 +0200 In-Reply-To: <20010504143910.B11325@hunter.munich.sgi.com> Message-ID: Lines: 25 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Georg-W. Koltermann" writes: > a) Does suspend/resume now work for you? No, but I haven't upgraded my kernel since right before Easter. > b) What hardware/firmware do you have (mine is a DELL Inspiron 7500 > with BIOS rev A12)? IBM ThinkPad 600E, don't remember the firmware revision but it's very recent. > One surprising observation: If I disable APM in /boot/device.hints, my > machine suspends and resumes JUST FINE. The BIOS alone seems to be > able to suspend and awake the hardware behind FreeBSD's back. The > system only hangs if FreeBSD is involved in the process. Hmm, I might try that. BTW, last time I asked Warner about this his reply was (I paraphrase) "it's not supposed to work, and if it ever worked for you it was out of sheer luck", which I find surprising. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 8:36:17 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 9536E37B424 for ; Fri, 4 May 2001 08:36:14 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f44FaBa40792 for current@freebsd.org; Fri, 4 May 2001 08:36:11 -0700 (PDT) Date: Fri, 4 May 2001 08:36:11 -0700 (PDT) From: David Wolfskill Message-Id: <200105041536.f44FaBa40792@bunrab.catwhisker.org> To: current@freebsd.org Subject: -CURRENT buildworld broken.... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In: >>> stage 4: make dependencies ... ===> secure/usr.bin/ssh-keyscan rm -f .depend mkdep -f .depend -a -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include /usr/src/secure/usr.bin/ssh-keyscan/../../../crypto/openssh/ssh-keyscan.c cd /usr/src/secure/usr.bin/ssh-keyscan; make _EXTRADEPEND echo ssh-keyscan: /usr/obj/usr/src/i386/usr/lib/libc.a /common/C/obj/usr/src/secure/usr.bin/ssh-keyscan/../../lib/libssh/libssh.a /usr/obj/usr/src/i386/usr/lib/libcrypto.a >> .depend ===> secure/usr.sbin ===> secure/usr.sbin/sshd make: don't know how to make pty.c. Stop *** Error code 2 Stop in /usr/src/secure/usr.sbin. *** Error code 1 Stop in /usr/src/secure. *** Error code 1 Recent CVSup history: CVSup begin from cvsup14.freebsd.org at Wed May 2 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Wed May 2 03:53:01 PDT 2001 CVSup begin from cvsup14.freebsd.org at Thu May 3 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Thu May 3 03:52:25 PDT 2001 CVSup begin from cvsup14.freebsd.org at Thu May 3 15:31:18 PDT 2001 CVSup ended from cvsup14.freebsd.org at Thu May 3 15:36:51 PDT 2001 CVSup begin from cvsup14.freebsd.org at Fri May 4 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Fri May 4 03:53:47 PDT 2001 uname: FreeBSD m133.whistle.com 5.0-CURRENT FreeBSD 5.0-CURRENT #52: Thu May 3 18:52:06 PDT 2001 root@localhost:/common/C/obj/usr/src/sys/LAPTOP_30W i386 [What was that that Kris wrote about "turbulence on this flight...?" :-)] Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 8:49:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id DB55B37B422; Fri, 4 May 2001 08:49:51 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f44Fno029625; Fri, 4 May 2001 08:49:51 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f44Fnop54245; Fri, 4 May 2001 08:49:50 -0700 (PDT) (envelope-from jdp) Date: Fri, 4 May 2001 08:49:50 -0700 (PDT) Message-Id: <200105041549.f44Fnop54245@vashon.polstra.com> To: current@freebsd.org From: John Polstra Cc: rwatson@freebsd.org Subject: Re: HEADS UP! bad bug in -current. In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Robert Watson wrote: > > I think we can all take lessons from phk here -- he achieves a level of > destructiveness that makes even the pro's marvel in wonder. Your criticism is grossly unfair. Throughout the very long time he's been active in this project, PHK's contribution/breakage ratio has been unsurpassed. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 9:35:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 7258B37B423 for ; Fri, 4 May 2001 09:35:56 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f44GZ0G03543; Fri, 4 May 2001 09:35:00 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <32158.988962409@axl.fw.uunet.co.za> Date: Fri, 04 May 2001 09:30:44 -0700 (PDT) From: John Baldwin To: Sheldon Hearn Subject: Re: Any chance of release patch being committed? Cc: freebsd-current@FreeBSD.org, (Joerg Wunsch) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-May-01 Sheldon Hearn wrote: > > > On Fri, 04 May 2001 00:00:58 +0200, J Wunsch wrote: > >> We are, but why would we use anything else than GENERIC for it, >> seriously? I'd never roll a `release' for my current machine. > > When you get commitment to a fixed hardware configuration for two years > and you want to leave your datacenter full of hosts ready to power up > and play off a custom CDROM, a release that uses a custom kernel is > desirable. > > That said, I don't think that the release should pick up KERNCONF. I > think a middle-ground option is to have the release pick up > RELEASE_KERNCONF. That is fine, but do note that Terry didn't add a new KERNCONF variable, it was already called that to begin with. We don't use buildkernel/installkernel in release, so it doesn't actually cause any conflicts. But anyways. Anyone have any reasonable objections to Terry's patch? If not I'll test it out for sanity and then commit it. > Ciao, > Sheldon. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 9:38:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 138F937B422; Fri, 4 May 2001 09:38:36 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f44GcWG03686; Fri, 4 May 2001 09:38:32 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 04 May 2001 09:34:15 -0700 (PDT) From: John Baldwin To: current@FreeBSD.org Subject: FW: Snapshot Log - world broken Cc: green@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> libpam/modules/pam_tacplus cc -O -pipe -Wall -I/usr/src/lib/libpam/modules/pam_tacplus/../../../../contrib/libpam/libpam/incl ude -I/usr/src/lib/libpam/mo dules/pam_tacplus/../../libpam -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpam/modules/pam_tacplus/pam_tacplus.c -o pam_tacplus.o cc -fpic -DPIC -O -pipe -Wall -I/usr/src/lib/libpam/modules/pam_tacplus/../../../../contrib/libpam/libpam/incl ude -I/usr/src/l ib/libpam/modules/pam_tacplus/../../libpam -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpam/modules/pam_tacplus/pam_t acplus.c -o pam_tacplus.So building static pam_tacplus library building shared library pam_tacplus.so ranlib libpam_tacplus.a ===> libpam/modules/pam_unix cc -O -pipe -Wall -I/usr/src/lib/libpam/modules/pam_unix/../../../../contrib/libpam/libpam/include -I/usr/src/lib/libpam/modul es/pam_unix/../../libpam -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpam/modules/pam_unix/pam_unix.c -o pam_unix.o cc -fpic -DPIC -O -pipe -Wall -I/usr/src/lib/libpam/modules/pam_unix/../../../../contrib/libpam/libpam/include -I/usr/src/lib/ libpam/modules/pam_unix/../../libpam -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpam/modules/pam_unix/pam_unix.c -o pam_unix.So building static pam_unix library building shared library pam_unix.so ranlib libpam_unix.a ===> libpam/libpam make: don't know how to make ../modules/pam_ssh/libpam_ssh.a. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error 1 error*** Error code 2 *** Error code 2 Stop in /usr/src/release. ---------------------------------------- release started at 06:00:00 on 05/04/01 release died at 08:21:12 on 05/04/01 ---------------------------------------- --------------End of forwarded message------------------------- -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 9:39:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from infres.enst.fr (infres-192.enst.fr [137.194.192.1]) by hub.freebsd.org (Postfix) with ESMTP id 0586137B43F for ; Fri, 4 May 2001 09:39:33 -0700 (PDT) (envelope-from quinot@inf.enst.fr) Received: by infres.enst.fr (Postfix, from userid 11117) id AFCCC18A4; Fri, 4 May 2001 18:39:30 +0200 (MET DST) Date: Fri, 4 May 2001 18:39:28 +0200 From: Thomas Quinot To: current@freebsd.org Subject: world broken (sshd) Message-ID: <20010504183926.A1569@infres.enst.fr> Reply-To: Thomas Quinot Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1us Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like world does not currently compile: some files have been removed from src/crypto/openssh/ a few hours ago, but are still listed in SRCS in secure/usr.sbin/sshd/Makefile. Possible workaround: --- secure/usr.sbin/sshd/Makefile.dist Fri May 4 17:10:19 2001 +++ secure/usr.sbin/sshd/Makefile Fri May 4 18:14:35 2001 @@ -5,8 +5,8 @@ PROG= sshd SRCS= sshd.c auth-rhosts.c auth-passwd.c auth-rsa.c auth-rh-rsa.c \ - pty.c log-server.c login.c servconf.c serverloop.c \ - auth.c auth1.c auth2.c auth-options.c session.c login_access.c dh.c \ + log-server.c servconf.c serverloop.c \ + auth.c auth1.c auth2.c auth-options.c session.c dh.c \ auth-pam.c MAN= sshd.8 -- Thomas Quinot ** Département Informatique & Réseaux ** quinot@inf.enst.fr ENST // 46 rue Barrault // 75634 PARIS CEDEX 13 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 11:49:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 7EB2D37B440 for ; Fri, 4 May 2001 11:49:22 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id UAA23798 for freebsd-current@freebsd.org; Fri, 4 May 2001 20:49:21 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f44IT1T92630; Fri, 4 May 2001 20:29:01 +0200 (MET DST) (envelope-from j) Date: Fri, 4 May 2001 20:29:01 +0200 (MET DST) Message-Id: <200105041829.f44IT1T92630@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <200105041549.f44Fnop54245@vashon.polstra.com> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: HEADS UP! bad bug in -current. X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > Your criticism is grossly unfair. Throughout the very long time he's > been active in this project, PHK's contribution/breakage ratio has > been unsurpassed. And btw., the recent stdio breakage wasn't all that bad either, and it completely happened in userland. I ended up in reinstalling a system from backup tapes, so the effect is not different to the specfs bug. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 11:49:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 1914337B422 for ; Fri, 4 May 2001 11:49:25 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id UAA23799 for freebsd-current@freebsd.org; Fri, 4 May 2001 20:49:24 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f44ITOp92637; Fri, 4 May 2001 20:29:24 +0200 (MET DST) (envelope-from j) Date: Fri, 4 May 2001 20:29:24 +0200 (MET DST) Message-Id: <200105041829.f44ITOp92637@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <200105032200.f43M0wD89227@uriah.heep.sax.de> <32158.988962409@axl.fw.uunet.co.za> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Any chance of release patch being committed? X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > That said, I don't think that the release should pick up KERNCONF. I > think a middle-ground option is to have the release pick up > RELEASE_KERNCONF. That sounds best to me. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 12:45:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from proxon.bnc.net (proxon.bnc.net [62.225.99.6]) by hub.freebsd.org (Postfix) with ESMTP id 6520C37B43C for ; Fri, 4 May 2001 12:45:52 -0700 (PDT) (envelope-from noses@proxon.bnc.net) Received: (from root@localhost) by proxon.bnc.net (8.11.3/8.11.3) id f44JjTe16865; Fri, 4 May 2001 21:45:29 +0200 (CEST) (envelope-from noses) Received: (from noses@localhost) by proxon.bnc.net (8.11.3/8.11.3) id f44JjPD16856; Fri, 4 May 2001 21:45:25 +0200 (CEST) (envelope-from noses) Date: Fri, 4 May 2001 21:45:25 +0200 (CEST) Message-Id: <200105041945.f44JjPD16856@proxon.bnc.net> From: Noses To: jdp@polstra.com, current@freebsd.org Subject: Re: HEADS UP! bad bug in -current. Organization: Noses' cave In-Reply-To: <200105041549.f44Fnop54245@vashon.polstra.com> User-Agent: tin/1.5.6-20000803 ("Dust") (UNIX) (FreeBSD/4.3-RC (i386)) X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200105041549.f44Fnop54245@vashon.polstra.com> you wrote: > In article , > Robert Watson wrote: >> >> I think we can all take lessons from phk here -- he achieves a level of >> destructiveness that makes even the pro's marvel in wonder. > > Your criticism is grossly unfair. Too much snipping; that wasn't critizism. It was pure jealousy. 8-) He also said "obviously I haven't been playing in the right bits of the system, I'll have to start hacking the low-level stuff in FFS some more..." And - who knows - it might be that phk's real middle name is "Haegar" 8-))). (Am I the only one making back up copies before "make installkernel; make installworld"?) Achim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 15:59:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 6A40B37B422 for ; Fri, 4 May 2001 15:59:43 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id SAA19339; Fri, 4 May 2001 18:59:04 -0400 (EDT) Date: Fri, 4 May 2001 18:59:02 -0400 (EDT) From: Daniel Eischen To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 May 2001, Bruce Evans wrote: > On Wed, 2 May 2001, Daniel Eischen wrote: > > On Wed, 2 May 2001, Bruce Evans wrote: > > > > > > There is also the osendsig() case, and corresponding code in several > > > emulators. > > > > I don't think we care too much about osendsig() since anything > > that uses a new threads library will have to be recompiled > > and wouldn't use the old routines. I think the same is true > > for emulators; an application that used the new threads library > > wouldn't be running in emulation would it? > > A library running under an emulator might. Non-emulated Linux seems > to pass %fs and %gs to signal handlers unchanged, so there is a precedent > for doing things like you want. Go ahead. The Linux emulator certainly > needs to do it the same as Linux. OK, thanks. Here's my guess at what should be changed for the Linux emulator. If this looks correct, I'll commit it. Hmm, I wonder how linuxthreads works under FreeBSD without this change... -- Dan Eischen Index: linux/linux_sysvec.c =================================================================== RCS file: /home/ncvs/src/sys/i386/linux/linux_sysvec.c,v retrieving revision 1.78 diff -u -r1.78 linux_sysvec.c --- linux/linux_sysvec.c 2001/05/01 08:12:52 1.78 +++ linux/linux_sysvec.c 2001/05/04 22:49:41 @@ -338,8 +338,6 @@ regs->tf_cs = _ucodesel; regs->tf_ds = _udatasel; regs->tf_es = _udatasel; - regs->tf_fs = _udatasel; - load_gs(_udatasel); regs->tf_ss = _udatasel; } @@ -472,8 +470,6 @@ regs->tf_cs = _ucodesel; regs->tf_ds = _udatasel; regs->tf_es = _udatasel; - regs->tf_fs = _udatasel; - load_gs(_udatasel); regs->tf_ss = _udatasel; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 19: 7:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 44D4737B43F for ; Fri, 4 May 2001 19:07:24 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA04139; Fri, 4 May 2001 22:07:23 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f4526rZ67587; Fri, 4 May 2001 22:06:53 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15091.24637.184377.619873@grasshopper.cs.duke.edu> Date: Fri, 4 May 2001 22:06:53 -0400 (EDT) To: Daniel Eischen Cc: current@FreeBSD.ORG Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen writes: > > OK, thanks. Here's my guess at what should be changed for the Linux > emulator. If this looks correct, I'll commit it. > > Hmm, I wonder how linuxthreads works under FreeBSD without this > change... > Well, they've never worked perfectly, by any means. Perhaps this will improve the stability problems people have been reporting with the various linux jdks under FreeBSD/i386. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 4 19:48:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id DB45E37B424 for ; Fri, 4 May 2001 19:48:11 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f452lqf11417; Fri, 4 May 2001 22:47:52 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 4 May 2001 22:47:52 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: John Polstra Cc: current@freebsd.org Subject: Re: HEADS UP! bad bug in -current. In-Reply-To: <200105041549.f44Fnop54245@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 May 2001, John Polstra wrote: > In article , > Robert Watson wrote: > > > > I think we can all take lessons from phk here -- he achieves a level of > > destructiveness that makes even the pro's marvel in wonder. > > Your criticism is grossly unfair. Throughout the very long time he's > been active in this project, PHK's contribution/breakage ratio has been > unsurpassed. I think my sarcasm may have gotten lost in transit; please re-read the message with a big blinking "Sarcasm Follows" post-it note reattached. I have great respect for Poul-Henning's work, especially with regards to his expertise in the device and buffering mechanisms in FreeBSD. The degree to which this is the case will becomes more clear in the near future. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 3:35:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.musha.org (daemon.musha.org [61.122.44.178]) by hub.freebsd.org (Postfix) with ESMTP id 87D1837B423; Sat, 5 May 2001 03:35:16 -0700 (PDT) (envelope-from knu@iDaemons.org) Received: from archon.local.idaemons.org (archon.local.idaemons.org [192.168.1.32]) by mail.musha.org (Postfix) with ESMTP id 135154E31A; Sat, 5 May 2001 19:35:15 +0900 (JST) Date: Sat, 05 May 2001 19:35:15 +0900 Message-ID: <86g0ekxevw.wl@archon.local.idaemons.org> From: "Akinori MUSHA" To: FreeBSD-current , "Brian F. Feldman" Subject: OpenSSH 2.9 problems User-Agent: Wanderlust/2.5.4 (Smooth) SEMI/1.14.2 (=?ISO-8859-1?Q?Daish=F2?= =?ISO-8859-1?Q?ji?=) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 081D 099C 1705 861D 4B70 B04A 920B EFC7 9FD9 E1EE MIME-Version: 1.0 (generated by SEMI 1.14.2 - =?ISO-8859-1?Q?=22Daish=F2ji=22?=) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have some problems with the newly updated OpenSSH 2.9. 1. Sshd fails to authenticate via PAM. May 5 19:18:07 archon sshd[803]: fatal: PAM setcred failed[6]: Permission denied 2. << ln -s hostname `which ssh`; ./hostname >> doesn't work anymore. It used to slogin to the host in the previous versions but now it just shows the help screen. 3. Somehow the default location of the ssh host key files has been changed from /etc/ssh to /etc. Was it intentional? Any ideas? -- / /__ __ Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "Freeze this moment a little bit longer, make each impression a little bit stronger.. Experience slips away -- Time stand still" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 4:56:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by hub.freebsd.org (Postfix) with ESMTP id 1D4CA37B423; Sat, 5 May 2001 04:56:32 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 932C417D80; Sat, 5 May 2001 13:56:30 +0200 (CEST) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.11.3/8.11.3) id f45BqWQ52612; Sat, 5 May 2001 13:52:32 +0200 (CEST) (envelope-from schweikh) Date: Sat, 5 May 2001 13:52:32 +0200 From: Jens Schweikhardt To: Alexander Leidinger Cc: freebsd-current@FreeBSD.ORG, hm@FreeBSD.ORG Subject: Re: isdn stops working when load increases Message-ID: <20010505135231.C14786@schweikhardt.net> References: <20010503211736.E1024@schweikhardt.net> <200105040953.f449rgh44495@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105040953.f449rgh44495@Magelan.Leidinger.net>; from Alexander@Leidinger.net on Fri, May 04, 2001 at 11:53:41AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander et al, # > Still ok. I have rtprio 25 (as from the isdnd.rc.sample, should I tune this? # > Remove the line?) in my isdnd.rc and this at the end of /etc/rc.isdn: # # I think Hellmuth choosed a good value for rtprio, and I didn't think it # solves your problem if you increase the value, but feel free to play a *De*creasing gives it higher priority, according to rtprio(1). # little bit with it (I think isdnd slowes down because of a lot of # interrupts, and if I didn't have a wrong understanding of the system, # rtprio didn't helps in this case). # # > echo 'removing previous isp0 config' # > ifconfig isp0 delete -link1 down # > echo 'setting sppp options' # > ispppcontrol isp0 myauthproto=pap myauthname=xxxxxxxx myauthsecret=xxxxxxxx hisauthproto=none callin # > echo 'configuring isp0' # > ifconfig isp0 1.2.3.4 5.6.7.8 netmask 0xffffffff link1 2>/dev/null # # What's your defaultroute? I use "-interface isp1". 5.6.7.8 (modified for the purpose of this mail :-) # BTW: I use /etc/start_if.isp1 to configure the interface, no need to # modify rc.isdn, e.g.: # ---snip--- # (11) root@ttyp0 # less /etc/start_if.isp1 # ifconfig isp1 link1 0.0.0.0 0.0.0.1 netmask 255.255.0.0 # ispppcontrol isp1 $(cat /etc/isdn/connect-CBC.parameters) enable-vj # ifconfig isp1 down # ---snip---. Ah, so that's how it's done properly. # While we're at it, maybe someone wants to commit something like this: # ---snip--- # --- /usr/src/etc/rc.isdn Sat Apr 28 14:49:22 2001 # +++ /etc/rc.isdn Sun Apr 29 15:37:04 2001 # @@ -38,6 +38,23 @@ # [Yy][Ee][Ss]) # echo -n 'ISDN subsystem setup:' # # + # Terminal type for fullscreen mode, default to syscons driver # + # # + if [ ! -n "${isdn_ttype}" ]; then # + isdn_ttype=cons25 # + fi # + if [ -n "${isdn_screenflags}" ]; then # + /usr/sbin/vidcontrol < ${isdn_fsdev} > ${isdn_fsdev} 2>&1 ${isdn_screenflags} # + fi ... # ---snip--- # (I think the isdn_ttype part isn't needed anymore, someone committed # something like this already, but the screenflags part is useful for me) Yup, that was me :-) Can you provide a patch against -current and also a patch adding isdn_screenflags to /etc/defaults/rc.conf and rc.conf(5)? It's important to document all the knobs there. Should be easy. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 7: 0: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from chunky.cacheboy.net (chunky.cacheboy.net [203.56.168.70]) by hub.freebsd.org (Postfix) with ESMTP id 8762D37B423; Sat, 5 May 2001 07:00:00 -0700 (PDT) (envelope-from adrian@chunky.cacheboy.net) Received: (from adrian@localhost) by chunky.cacheboy.net (8.11.3/8.11.3) id f45Dxjl13292; Sat, 5 May 2001 15:59:45 +0200 (CEST) (envelope-from adrian) Date: Sat, 5 May 2001 15:59:45 +0200 From: Adrian Chadd To: Robert Watson Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP! bad bug in -current. Message-ID: <20010505155945.A8812@chunky.cacheboy.net> References: <20010501165654K.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.ORG on Wed, May 02, 2001 at 11:22:23PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001, Robert Watson wrote: > On Tue, 1 May 2001, Jordan Hubbard wrote: > > > > Say, FreeBSD is usually pretty safe, even in CURRENT. > > > Has something near this magnitude of Really Bad Stuffage snuck into the > > > codebase before? > > > > No, it's not common, and it generally takes a Dane swinging something > > sharp to inflict quite this much damage on our user base. ;-) > > Obviously I haven't been playing in the right bits of the system, I'll > have to start hacking the low-level stuff in FFS some more... I tend not > to cause permanent damage to file systems, sadly. > > I think we can all take lessons from phk here -- he achieves a level of > destructiveness that makes even the pro's marvel in wonder. *grin* Its ok. phk has just reminded us of what -current really is .. :-) Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 8:18:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id DF7A837B422 for ; Sat, 5 May 2001 08:18:53 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA10376; Sat, 5 May 2001 11:18:32 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f45FI9l71418; Sat, 5 May 2001 11:18:09 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15092.6577.733823.946525@grasshopper.cs.duke.edu> Date: Sat, 5 May 2001 11:18:09 -0400 (EDT) To: Daniel Eischen Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen writes: > > OK, thanks. Here's my guess at what should be changed for the Linux > emulator. If this looks correct, I'll commit it. > > Hmm, I wonder how linuxthreads works under FreeBSD without this > change... > This breaks at least one version of the IBM JDK that I have laying around.. If anything, we may have two errors (at least partially) canceling each other out. I think it needs more work/thought prior to committing. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 11:39:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id BDD0B37B422 for ; Sat, 5 May 2001 11:39:20 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id OAA17559; Sat, 5 May 2001 14:38:40 -0400 (EDT) Date: Sat, 5 May 2001 14:38:40 -0400 (EDT) From: Daniel Eischen To: Andrew Gallatin Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: <15092.6577.733823.946525@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 May 2001, Andrew Gallatin wrote: > > Daniel Eischen writes: > > > > OK, thanks. Here's my guess at what should be changed for the Linux > > emulator. If this looks correct, I'll commit it. > > > > Hmm, I wonder how linuxthreads works under FreeBSD without this > > change... > > > > This breaks at least one version of the IBM JDK that I have > laying around.. > > If anything, we may have two errors (at least partially) canceling > each other out. I think it needs more work/thought prior to > committing. We're still OK with the change to FreeBSDs native signal trampoline though, right? I'll hold off on the Linux emulator changes until we can figure out what the problem is. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 14:37:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id A442F37B424 for ; Sat, 5 May 2001 14:37:36 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Received: from localhost (dennisg@localhost) by btw.plaintalk.bellevue.wa.us (8.11.3/8.11.3) with ESMTP id f45Lb8v00632; Sat, 5 May 2001 14:37:12 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Date: Sat, 5 May 2001 14:37:07 -0700 (PDT) From: Dennis Glatting X-X-Sender: To: Cc: Subject: pgm to kill 4.3 via vm Message-ID: <20010505143035.O613-100000@btw.plaintalk.bellevue.wa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote a trivial program to fill vm and found I can reliably freeze my system. It may not work on the first attempt, but certainly within three. My command line is: a.out&;a.out&;a.out&;a.out&;a.out& The goal of my program is simply to see how the system behaves under memory exhaustion which, as it turns out on two similar systems, the systems freeze. Specifically, I can switch between consoles but the login prompts do not respond and the system does not respond on the network. I am running 4.3 on a dual processor system. Below are some things. First, the program. Second, dmesg. Finally, my /etc/rc.config. LOL #include #include #include int main( void ) { int rd = open( "/dev/random", O_RDONLY ); char* mem = 0; int cnt = 0; if( rd < 0 ) { fprintf( stderr, "unable to open random device\n" ); exit( 1 ); } while( mem = malloc( 1024 )) { int i, j, k; for( i = 1024, j = 0; i > 0; ) { while(( j = read( rd, mem + ( 1024 - i ), i )) <= 0 ) ; i =- j; } if(( ++cnt % 1024 ) == 0 ) { putchar( '.' ); fflush( stdout ); } if(( cnt % ( 10 * 1024 )) == 0 ) { system( "/bin/sync" ); sleep( 2 ); } } putchar( '\n' ); return 0; } 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 4.3-STABLE #6: Wed May 2 19:57:42 PDT 2001 root@btw:/usr/src/sys/compile/BTW Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (860.89-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383fbff real memory = 268034048 (261752K bytes) avail memory = 254472192 (248508K bytes) Changing APIC ID for IO APIC #0 from 0 to 2 on chip Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170020, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc049e000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard IOAPIC #0 intpin 19 -> irq 2 IOAPIC #0 intpin 17 -> irq 13 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 16 pcib2: at device 30.0 on pci0 IOAPIC #0 intpin 18 -> irq 17 pci2: on pcib2 pci2: (vendor=0x1102, dev=0x0002) at 7.0 irq 16 pci2: (vendor=0x1102, dev=0x7002) at 7.1 ahc0: port 0xe800-0xe8ff mem 0xfafff000-0xfaffffff irq 13 at device 8.0 on pci2 aic7892: Wide Channel A, SCSI Id=7, 32/255 SCBs xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xec80-0xecbf irq 16 at device 11.0 on pci2 xl0: Ethernet address: 00:60:08:b0:3d:a6 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: <3Com 3c905C-TX Fast Etherlink XL> port 0xec00-0xec7f mem 0xfaffec00-0xfaffec7f irq 17 at device 12.0 on pci2 xl1: Ethernet address: 00:b0:d0:a2:62:ac miibus1: on xl1 xlphy0: <3c905C 10/100 internal PHY> on miibus1 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xff80-0xff9f irq 2 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 ums0: Microsoft Microsoft Wheel Mouse Optical\M-., rev 1.10/1.21, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 13 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 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 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 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 512 packets/entry by default IPsec: Initialized Security Association Processing. IP Filter: v3.4.16 initialized. Default = pass all, Logging = enabled SMP: AP CPU #1 Launched! acd0: CDROM at ata1-master using PIO4 Waiting 2 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 8683MB (17783239 512 byte sectors: 255H 63S/T 1106C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 17501MB (35843671 512 byte sectors: 255H 63S/T 2231C) WARNING: / was not properly dismounted xl0: promiscuous mode enabled # This file now contains just the overrides from /etc/defaults/rc.conf # please make all changes to this file. hostname="btw" tcp_extensions="YES" #log_in_vain="YES" #tcp_drop_synfin="YES" #tcp_restrict_rst="YES" icmp_log_redirect="YES" inetd_flags="-Wwl" defaultrouter="206.129.5.129" linux_enable="YES" rand_irqs="0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15" clear_tmp_enable="YES" ntpdate_enable="YES" ntpdate_flags="-b tick.usnogps.navy.mil tock.usnogps.navy.mil" xntpd_enable="YES" #sendmail_enable="NO" named_enable="YES" named_flags="-c /etc/namedb/named.conf" firewall_enable="YES" firewall_quiet="YES" firewall_type="simple" ifconfig_xl0="inet 206.129.5.145 netmask 255.255.255.240" ifconfig_xl1="inet 206.129.5.130 netmask 255.255.255.248" ifconfig_xl1_alias0="inet 206.129.5.131 netmask 255.255.255.248" ifconfig_xl1_alias1="inet 206.129.5.132 netmask 255.255.255.248" gateway_enable="YES" nfs_server_enable="YES" usbd_enable="YES" lpd_enable="YES" syslogd_flags="" ipv6_enable="YES" pv6_network_interfaces="xl0" -- Dennis Glatting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 15:46:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7B28F37B423 for ; Sat, 5 May 2001 15:46:27 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f45MkH039211; Sat, 5 May 2001 15:46:17 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f45MkFW59939; Sat, 5 May 2001 15:46:15 -0700 (PDT) (envelope-from jdp) Date: Sat, 5 May 2001 15:46:15 -0700 (PDT) Message-Id: <200105052246.f45MkFW59939@vashon.polstra.com> To: current@freebsd.org From: John Polstra Reply-To: current@freebsd.org Cc: knu@iDaemons.org Subject: Re: OpenSSH 2.9 problems In-Reply-To: <86g0ekxevw.wl@archon.local.idaemons.org> References: <86g0ekxevw.wl@archon.local.idaemons.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <86g0ekxevw.wl@archon.local.idaemons.org>, Akinori MUSHA wrote: > I have some problems with the newly updated OpenSSH 2.9. > > 1. Sshd fails to authenticate via PAM. > > May 5 19:18:07 archon sshd[803]: fatal: PAM setcred failed[6]: Permission denied I am seeing this same problem. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 15:57: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 487E337B423 for ; Sat, 5 May 2001 15:57:06 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f45Mv5039292 for ; Sat, 5 May 2001 15:57:05 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f45Mv5F60011; Sat, 5 May 2001 15:57:05 -0700 (PDT) (envelope-from jdp) Date: Sat, 5 May 2001 15:57:05 -0700 (PDT) Message-Id: <200105052257.f45Mv5F60011@vashon.polstra.com> To: current@freebsd.org From: John Polstra Reply-To: current@freebsd.org Subject: Re: OpenSSH 2.9 problems In-Reply-To: <200105052246.f45MkFW59939@vashon.polstra.com> References: <86g0ekxevw.wl@archon.local.idaemons.org> <200105052246.f45MkFW59939@vashon.polstra.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200105052246.f45MkFW59939@vashon.polstra.com>, John Polstra wrote: > In article <86g0ekxevw.wl@archon.local.idaemons.org>, > Akinori MUSHA wrote: > > I have some problems with the newly updated OpenSSH 2.9. > > > > 1. Sshd fails to authenticate via PAM. > > > > May 5 19:18:07 archon sshd[803]: fatal: PAM setcred failed[6]: Permission denied > > I am seeing this same problem. Here's another one: blake$ slogin localhost socket: Protocol not supported <=== Eh? jdp@localhost's password: John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 16: 5:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id ACC1537B422 for ; Sat, 5 May 2001 16:05:13 -0700 (PDT) (envelope-from archie@dellroad.org) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id QAA81192; Sat, 5 May 2001 16:05:13 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f45N4RO00676; Sat, 5 May 2001 16:04:27 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200105052304.f45N4RO00676@arch20m.dellroad.org> Subject: Re: panic in fxp driver In-Reply-To: <200105031828.f43ISSi06097@prism.flugsvamp.com> "from Jonathan Lemon at May 3, 2001 01:28:28 pm" To: Jonathan Lemon Date: Sat, 5 May 2001 16:04:27 -0700 (PDT) Cc: tlambert@primenet.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Lemon writes: > >Please consider the case where there are two mbuf chains being > >transmitted, which look like this: > > Um. "Not Possible". I thought m_copypacket() of a cluster mbuf would yield exactly this situation (two headers pointing to the same data region). -Arcihe __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 17:17:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 2ED6637B423 for ; Sat, 5 May 2001 17:17:17 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f460GdJ05790; Sat, 5 May 2001 19:16:39 -0500 (CDT) (envelope-from jlemon) Date: Sat, 5 May 2001 19:16:39 -0500 From: Jonathan Lemon To: Archie Cobbs Cc: Jonathan Lemon , tlambert@primenet.com, current@FreeBSD.ORG Subject: Re: panic in fxp driver Message-ID: <20010505191639.N670@prism.flugsvamp.com> References: <200105031828.f43ISSi06097@prism.flugsvamp.com> <200105052304.f45N4RO00676@arch20m.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200105052304.f45N4RO00676@arch20m.dellroad.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 05, 2001 at 04:04:27PM -0700, Archie Cobbs wrote: > Jonathan Lemon writes: > > >Please consider the case where there are two mbuf chains being > > >transmitted, which look like this: > > > > Um. "Not Possible". > > I thought m_copypacket() of a cluster mbuf would yield exactly > this situation (two headers pointing to the same data region). Well, only external mbufs can be shared, not mbuf chains; and clusters are accessed through the (unused) mbuf that comprises the chain. I believe Terry may have been referring to some local modifications that is in his code, which permits the scenario he describes. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 18:34:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 1077437B424 for ; Sat, 5 May 2001 18:34:41 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA15511; Sat, 5 May 2001 21:34:36 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f461Y6o72220; Sat, 5 May 2001 21:34:06 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15092.43534.763282.601897@grasshopper.cs.duke.edu> Date: Sat, 5 May 2001 21:34:06 -0400 (EDT) To: Daniel Eischen Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: References: <15092.6577.733823.946525@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen writes: > > We're still OK with the change to FreeBSDs native signal trampoline > though, right? I'll hold off on the Linux emulator changes until > we can figure out what the problem is. Yes, I was just commenting on the linulator patch you posted. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 19:52:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-108.dsl.lsan03.pacbell.net [63.207.60.108]) by hub.freebsd.org (Postfix) with ESMTP id 0157737B424 for ; Sat, 5 May 2001 19:52:37 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 83CFF67283; Sat, 5 May 2001 19:52:30 -0700 (PDT) Date: Sat, 5 May 2001 19:52:30 -0700 From: Kris Kennaway To: current@FreeBSD.org Subject: OpenSSL 0.9.6a for testing Message-ID: <20010505195229.A12407@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, Please test binary compatibility of the OpenSSL 0.9.6a release available from the below address. By this, I mean: test whether your SSL applications such as webservers, etc, continue to work without a recompile after making world. Since 0.9.6a is a point release along the 0.9.6-STABLE branch, I expect compatibility to be maintained for all users. I'd like to import this into -current later this week. http://www.freebsd.org/~kris/openssl-0.9.6a.tar.bz2 http://www.freebsd.org/~kris/openssl-0.9.6a.diff (Untar the .tar.bz2 file, and apply the patch, and it should build fine). Kris --J/dobhs11T7y2rNN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE69LxtWry0BWjoQKURAp+jAJ976fjjKZdPHEcwZo13XK64kSsk6gCgrsF+ 4OoGUdX+jbLzb1KZtOKL+fE= =a8Rk -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 5 21:12: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.noos.fr (aragon.noos.net [212.198.2.75]) by hub.freebsd.org (Postfix) with ESMTP id 0D80937B423 for ; Sat, 5 May 2001 21:12:01 -0700 (PDT) (envelope-from clefevre@poboxes.com) Received: (qmail 6751020 invoked by uid 0); 6 May 2001 04:11:59 -0000 Received: from d165.dhcp212-198-231.noos.fr (HELO gits.dyndns.org) ([212.198.231.165]) (envelope-sender ) by aragon.noos.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 6 May 2001 04:11:59 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.3/8.11.3) id f464Bwv19965; Sun, 6 May 2001 06:11:58 +0200 (CEST) (envelope-from clefevre@poboxes.com) To: Jeroen Ruigrok/Asmodai Cc: current@freebsd.org Subject: Re: cp -u patch References: <20010426222132.B55566@daemon.ninth-circle.org> X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C Reply-To: Cyrille Lefevre In-Reply-To: <20010426222132.B55566@daemon.ninth-circle.org> Mail-Copies-To: never From: Cyrille Lefevre Date: 06 May 2001 06:11:56 +0200 Message-ID: Lines: 25 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai writes: > Question is, do we want to add this to our cp? > > I found it handy for stuff like: please, what is the difference between this : > cp -Ruv mozilla mozilla-test and that : cd mozzila; find . | cpio -pdm ../mozzila-test ? thanks. > so that my mozilla CVS tree [not touched] only overwrites the > mozilla-test files which are older. Cyrille. -- home: mailto:clefevre@poboxes.com UNIX is user-friendly; it's just particular work: mailto:Cyrille.Lefevre@edf.fr about who it chooses to be friends with. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message