From owner-freebsd-stable Sun Aug 9 06:43:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19132 for freebsd-stable-outgoing; Sun, 9 Aug 1998 06:43:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.wsg.net (ns1.wsg.net [206.97.122.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA19125 for ; Sun, 9 Aug 1998 06:43:09 -0700 (PDT) (envelope-from gilem@wsg.net) Message-Id: <199808091343.GAA19125@hub.freebsd.org> Received: (qmail 6102 invoked by uid 0); 9 Aug 1998 13:49:41 -0000 Received: from mike.wsg.net (HELO tc) (206.97.122.31) by mail.wsg.net with SMTP; 9 Aug 1998 13:49:41 -0000 X-Sender: mikemail@mail.wsg.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Sun, 09 Aug 1998 09:42:05 -0400 To: freebsd-stable@FreeBSD.ORG From: "Michael R. Gile" Subject: threads bug Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There appears to be a recurring bug in libc_r that is causing Mysql not to respond to a shutdown. The author claims that he helped the development group fix this bug some time ago, but that it has recurred. Any suggestions on where to find this documentation would be helpful. thanks. At 12:55 PM 8/9/98 +0300, monty@analytikerna.se wrote: > >Michael> 2.2.7 >Michael> i just tried it >Michael> i wasn't clear that it would work, since the manual only mentions this for >Michael> it doesn't exhibit the problem above, but doesn't respond to mysqladmin shutdown. >Michael> any suggestions? > >This is a bug with the latest freebsd thread implementation. I >really suggest you should mail the freebsd developers about this; This >worked in a previous freebsd thread version (I helped freebsd to fix >that bug) but they have apparently managed to get the bug back again. > ====================================================== Michael Gile gilem@wsg.net President (518)435-0682 Web Services Group http://www.wsg.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 9 20:33:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03734 for freebsd-stable-outgoing; Sun, 9 Aug 1998 20:33:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kendra.ne.mediaone.net (kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03728 for ; Sun, 9 Aug 1998 20:33:14 -0700 (PDT) (envelope-from ahd@kew.com) Received: from ffactory.uucp.kew.com (ffactory.hh.kew.com [192.168.203.131]) by kendra.ne.mediaone.net (8.9.0/8.9.0) with SMTP id XAA20054 for ; Sun, 9 Aug 1998 23:32:53 -0400 (EDT) Received: from kew.com by ffactory.uucp.kew.com (UUPC/extended 1.13c) with UUCP for stable@freebsd.org; Sun, 09 Aug 1998 23:32:53 -0500 Received: from kew.com by ffactory.uucp.kew.com (UUPC/extended 1.13c) with ESMTP for stable@freebsd.org; Sun, 09 Aug 1998 23:32:52 -0500 Message-ID: <35CE69E3.DF0367FB@kew.com> Date: Sun, 09 Aug 1998 23:32:52 -0400 From: Drew Derbyshire Reply-To: software@kew.com Organization: Kendra Electronic Wonderworks, Stoneham MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.05 [en] (WinNT; U) MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: zp0 not receiving under 2.2.7? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone seen a condition where zp0 (3COM PC-Card, rev C) can send but not receive under 2.2.7? Card/machine/etc work fine under Windows 95. Card is seen at boot and dumps packets into network, does not see responses. -ahd- -- Internet: ahd@kew.com Voice: 781-279-9812 Nuke 'em till they glow and shoot 'em in dark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 9 22:30:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12027 for freebsd-stable-outgoing; Sun, 9 Aug 1998 22:30:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles217.castles.com [208.214.165.217]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12022 for ; Sun, 9 Aug 1998 22:30:27 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA09831; Sun, 9 Aug 1998 22:28:56 -0700 (PDT) Message-Id: <199808100528.WAA09831@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: software@kew.com cc: stable@FreeBSD.ORG Subject: Re: zp0 not receiving under 2.2.7? In-reply-to: Your message of "Sun, 09 Aug 1998 23:32:52 EDT." <35CE69E3.DF0367FB@kew.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Aug 1998 22:28:56 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anyone seen a condition where zp0 (3COM PC-Card, rev C) can send but not > receive under 2.2.7? Card/machine/etc work fine under Windows 95. Card is > > seen at boot and dumps packets into network, does not see responses. Incorrect interrupt setting is the most likely cause. If this isn't for an install, you should be using the pccard support and the 'ep' driver. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 9 23:55:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19799 for freebsd-stable-outgoing; Sun, 9 Aug 1998 23:55:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19792 for ; Sun, 9 Aug 1998 23:55:46 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id IAA10143; Mon, 10 Aug 1998 08:55:25 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Mon, 10 Aug 1998 08:55:24 +0200 (MET DST) Mime-Version: 1.0 To: Andre Albsmeier Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Why did these files change on -STABLE? References: <199808081511.RAA26771@internal> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 10 Aug 1998 08:55:23 +0200 In-Reply-To: Andre Albsmeier's message of "Sat, 8 Aug 1998 17:11:42 +0200 (CEST)" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA19794 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andre Albsmeier writes: > After applying src-2.2.0824.gz I found that, among others, the > following files were intoduced into -STABLE: I suspect pilot error; either you grabbed the wrong file, or someone f*d up generating it. My -stable box (cvsupped right this instant) doesn't have /sys/alpha. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 00:22:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22010 for freebsd-stable-outgoing; Mon, 10 Aug 1998 00:22:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22005 for ; Mon, 10 Aug 1998 00:22:13 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id JAA09857 for ; Mon, 10 Aug 1998 09:21:40 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id JAA21425 for ; Mon, 10 Aug 1998 09:21:39 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id JAA29644 for ; Mon, 10 Aug 1998 09:21:41 +0200 (CEST) From: Andre Albsmeier Message-Id: <199808100721.JAA04761@internal> Subject: Re: Why did these files change on -STABLE? In-Reply-To: from =?ISO-8859-1?Q?Dag=2DErling_Coidan_Sm=F8rgrav?= at "Aug 10, 98 08:55:23 am" To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Mon, 10 Aug 1998 09:21:38 +0200 (CEST) Cc: andre.albsmeier@mchp.siemens.de, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Andre Albsmeier writes: > > After applying src-2.2.0824.gz I found that, among others, the > > following files were intoduced into -STABLE: > > I suspect pilot error; either you grabbed the wrong file, or someone No, definetely not :-). It was sent to be by ctm, applied cleanly and was removed by 1 or 2 ctm files later... > f*d up generating it. My -stable box (cvsupped right this instant) > doesn't have /sys/alpha. Maybe it was because you cvsupped and I use ctm... > > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 01:11:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28775 for freebsd-stable-outgoing; Mon, 10 Aug 1998 01:11:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alcatel.fr (ns.rfs.tm.fr [194.133.58.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28746 for ; Mon, 10 Aug 1998 01:11:53 -0700 (PDT) (envelope-from Thierry.Herbelot@alcatel.fr) From: Thierry.Herbelot@alcatel.fr Received: from alcatel.fr (gatekeeper-ssn.alcatel.fr [155.132.180.244]) by mailgate.alcatel.fr (ALCANET/SMTP) with ESMTP id KAA15385; Mon, 10 Aug 1998 10:13:00 +0200 Received: from aifhs1.alcatel.fr (aifhs1.alcatel.fr [155.132.180.86]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id JAA08101; Mon, 10 Aug 1998 09:59:57 +0200 (MET DST) Received: from aifhs2.alcatel.fr (localhost [127.0.0.1]) by aifhs1.alcatel.fr (8.8.8/8.8.8) with ESMTP id KAA18075; Mon, 10 Aug 1998 10:02:12 +0200 (MET DST) Received: from lune.telspace.alcatel.fr (lune.telspace.alcatel.fr [155.132.144.65]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id JAA08080; Mon, 10 Aug 1998 09:59:54 +0200 (MET DST) Received: from telss1 (telss1.telspace.alcatel.fr [155.132.51.4]) by lune.telspace.alcatel.fr (8.7.6/8.7.3) with SMTP id KAA24442; Mon, 10 Aug 1998 10:09:13 +0200 (MET DST) Received: from telspace.alcatel.fr by telss1 (4.1/SMI-4.1) id AA21978; Mon, 10 Aug 98 09:57:26 +0200 Received: from localhost by telspace.alcatel.fr with SMTP (1.40.112.12/16.2) id AA101335543; Mon, 10 Aug 1998 09:52:23 +0200 X-Openmail-Hops: 1 Date: Mon, 10 Aug 98 09:51:01 +0200 Message-Id: In-Reply-To: Subject: Re: Why did these files change on -STABLE? Mime-Version: 1.0 To: dag-erli@ifi.uio.no Cc: andre.albsmeier@mchp.siemens.de, freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset=ISO-8859-1; name="Re:" Content-Disposition: inline; filename="Re:" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA28763 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I CVSupped last week (on my home box - I don't have the files at hand) and also got the "alpha" source sub-tree. I have made the world with no problem, though. TfH > Andre Albsmeier writes: > > After applying src-2.2.0824.gz I found that, among others, the > > following files were intoduced into -STABLE: > > I suspect pilot error; either you grabbed the wrong file, or someone > f*d up generating it. My -stable box (cvsupped right this instant) > doesn't have /sys/alpha. > > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 05:16:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01091 for freebsd-stable-outgoing; Mon, 10 Aug 1998 05:16:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kendra.ne.mediaone.net (kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01086 for ; Mon, 10 Aug 1998 05:15:58 -0700 (PDT) (envelope-from software@kew.com) Received: from ffactory.uucp.kew.com (ffactory.hh.kew.com [192.168.203.131]) by kendra.ne.mediaone.net (8.9.0/8.9.0) with SMTP id IAA21515; Mon, 10 Aug 1998 08:15:26 -0400 (EDT) Received: from kew.com by ffactory.uucp.kew.com (UUPC/extended 1.13c) with UUCP for multiple addressees; Mon, 10 Aug 1998 08:15:25 -0500 Received: from kew.com by ffactory.uucp.kew.com (UUPC/extended 1.13c) with ESMTP for multiple addresses; Mon, 10 Aug 1998 08:15:23 -0500 Message-ID: <35CEE45B.ECF5E90E@kew.com> Date: Mon, 10 Aug 1998 08:15:23 -0400 From: Drew Derbyshire Organization: Kendra Electronic Wonderworks, Stoneham, MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.05 [en] (WinNT; U) MIME-Version: 1.0 To: Mike Smith CC: stable@FreeBSD.ORG Subject: Re: zp0 not receiving under 2.2.7? References: <199808100528.WAA09831@antipodes.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Anyone seen a condition where zp0 (3COM PC-Card, rev C) can send but not > > receive under 2.2.7? Card/machine/etc work fine under Windows 95. Card is > > seen at boot and dumps packets into network, does not see responses. > > Incorrect interrupt setting is the most likely cause. > > If this isn't for an install, you should be using the pccard support > and the 'ep' driver. No doubt I should use ep0 and in fact tried to do so. However, configuration failed under pccardd. The error message reported by pccardd was not sufficient to debug the problem, and I don't have full source loaded on the target system. Hence, I left off this chapter of the saga since I didn't feel like getting flamed for reporting the error message was incomplete. As it is, however, the pccardd message doesn't tell me what the problem is. I presume zp0 should at least get the system on to my network. I don't swap cards, really. -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9812 This message intentionally left almost blank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 06:10:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA09110 for freebsd-stable-outgoing; Mon, 10 Aug 1998 06:10:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kendra.ne.mediaone.net (kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09105 for ; Mon, 10 Aug 1998 06:10:32 -0700 (PDT) (envelope-from software@kew.com) Received: from ffactory.uucp.kew.com (ffactory.hh.kew.com [192.168.203.131]) by kendra.ne.mediaone.net (8.9.0/8.9.0) with SMTP id JAA21660; Mon, 10 Aug 1998 09:09:41 -0400 (EDT) Received: from kew.com by ffactory.uucp.kew.com (UUPC/extended 1.13c) with UUCP for multiple addressees; Mon, 10 Aug 1998 09:09:41 -0500 Received: from kew.com by ffactory.uucp.kew.com (UUPC/extended 1.13c) with ESMTP for multiple addresses; Mon, 10 Aug 1998 09:09:40 -0500 Message-ID: <35CEF113.557FFDAE@kew.com> Date: Mon, 10 Aug 1998 09:09:39 -0400 From: Drew Derbyshire Organization: Kendra Electronic Wonderworks, Stoneham, MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.05 [en] (WinNT; U) MIME-Version: 1.0 To: Gregory Bond Subject: Re: zp0 not receiving under 2.2.7? References: <199808100429.OAA10731@melba.bby.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gregory Bond wrote: > looks like IRQ in the kernel is not matching the card.... I just went in again and verified via the DOS configuration utility for the card that it was set to IRQ 10, same as the kernel. I then tried both at IRQ 5. No joy. (Someone also suggested bad cables, so I walked the machine to the hub and used a new cable on a different port. No joy. I had found this doubtful, since the card does work on Win 95, but didn't want to exclude any suggestions.) -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9812 This message intentionally left almost blank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 08:59:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24067 for freebsd-stable-outgoing; Mon, 10 Aug 1998 08:59:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24061 for ; Mon, 10 Aug 1998 08:59:42 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id IAA02491; Mon, 10 Aug 1998 08:58:19 -0700 (PDT) (envelope-from jdp) Message-Id: <199808101558.IAA02491@austin.polstra.com> To: andre.albsmeier@mchp.siemens.de Subject: Re: Why did these files change on -STABLE? In-Reply-To: <199808081511.RAA26771@internal> References: <199808081511.RAA26771@internal> Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Mon, 10 Aug 1998 08:58:19 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808081511.RAA26771@internal>, Andre Albsmeier wrote: > After applying src-2.2.0824.gz I found that, among others, the > following files were intoduced into -STABLE: > > > DM sys/alpha > > DM sys/alpha/include > > FM sys/alpha/include/console.h ... > Do they really belong there? I didn't find anything in the CVS messages > confirming this, e.g.: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/alpha/include/console.h > > 1.39 Thu Aug 6 9:15:52 1998 UTC by dfr > CVS Tags: HEAD > Diffs to 1.38 > > Port syscons to the alpha. The driver itself has moved to sys/isa as it will > hopefully become a portable driver usable by all architectures. The api > support files have had to be copied to sys/alpha/include since userland > programs expect to find them in . > > All the revision history of the i386 syscons has been retained by a > repository copy. No, they do not belong there. Whoever did the repository copy didn't do it correctly. This is an example of why committers are strictly forbidden from doing repository copies (or anything else directly in the repository) themselves. The only people allowed to do repository copies are: peter@freebsd.org jdp@freebsd.org asami@freebsd.org (for ports) -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 09:22:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26577 for freebsd-stable-outgoing; Mon, 10 Aug 1998 09:22:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles176.castles.com [208.214.165.176]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26553 for ; Mon, 10 Aug 1998 09:22:23 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA12498; Mon, 10 Aug 1998 09:20:39 -0700 (PDT) Message-Id: <199808101620.JAA12498@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Drew Derbyshire cc: Mike Smith , stable@FreeBSD.ORG Subject: Re: zp0 not receiving under 2.2.7? In-reply-to: Your message of "Mon, 10 Aug 1998 08:15:23 EDT." <35CEE45B.ECF5E90E@kew.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 09:20:38 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > Anyone seen a condition where zp0 (3COM PC-Card, rev C) can send but not > > > receive under 2.2.7? Card/machine/etc work fine under Windows 95. Card is > > > seen at boot and dumps packets into network, does not see responses. > > > > Incorrect interrupt setting is the most likely cause. > > > > If this isn't for an install, you should be using the pccard support > > and the 'ep' driver. > > No doubt I should use ep0 and in fact tried to do so. > > However, configuration failed under pccardd. The error message reported by > pccardd was not sufficient to debug the problem, and I don't have full source > loaded on the target system. Hence, I left off this chapter of the saga since > I didn't feel like getting flamed for reporting the error message was > incomplete. As it is, however, the pccardd message doesn't tell me what the > problem is. No, but it can often tell us what's going on (most of the time). There are three messages you're likely to get: - "no driver found for ..." meaning your pccard.conf file entry is wrong. - "resource allocation failed for ..." meaning that the resource information in your pccard.conf file conflicts with the configuration entry you've selected from the card - "driver allocation failed for ..." meaning that the driver probe failed, or the kernel disagrees with you as to the resources that you've assigned to the card (ie. they're in use elsewhere). > I presume zp0 should at least get the system on to my network. I don't swap > cards, really. It *should* work, yes. The lack of incoming packets does suggest an interrupt problem of some sort though. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 12:30:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20542 for freebsd-stable-outgoing; Mon, 10 Aug 1998 12:30:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA20521 for ; Mon, 10 Aug 1998 12:30:13 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z5xdZ-0005rq-00; Mon, 10 Aug 1998 12:29:45 -0700 Date: Mon, 10 Aug 1998 12:29:43 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Michael R. Gile" cc: freebsd-stable@FreeBSD.ORG Subject: Re: threads bug In-Reply-To: <199808091343.GAA19125@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 9 Aug 1998, Michael R. Gile wrote: > There appears to be a recurring bug in libc_r that is causing > Mysql not to respond to a shutdown. The author claims that > he helped the development group fix this bug some time ago, > but that it has recurred. Any suggestions on where to find this > documentation would be helpful. I don't believe this bug was ever fixed. You can look at the cvslogs to see all changes to libc_r. > thanks. > > At 12:55 PM 8/9/98 +0300, monty@analytikerna.se wrote: > > > >Michael> 2.2.7 > >Michael> i just tried it > >Michael> i wasn't clear that it would work, since the manual only mentions this for > >Michael> it doesn't exhibit the problem above, but doesn't respond to mysqladmin shutdown. > >Michael> any suggestions? > > > >This is a bug with the latest freebsd thread implementation. I > >really suggest you should mail the freebsd developers about this; This > >worked in a previous freebsd thread version (I helped freebsd to fix > >that bug) but they have apparently managed to get the bug back again. > > > ====================================================== > Michael Gile gilem@wsg.net > President (518)435-0682 > Web Services Group http://www.wsg.net/ Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 14:04:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01336 for freebsd-stable-outgoing; Mon, 10 Aug 1998 14:04:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01330 for ; Mon, 10 Aug 1998 14:04:11 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id RAA27314; Mon, 10 Aug 1998 17:03:45 -0400 (EDT) Date: Mon, 10 Aug 1998 17:03:45 -0400 (EDT) Message-Id: <199808102103.RAA27314@highwind.com> From: HighWind Software Information To: tom@uniserve.com CC: gilem@wsg.net, freebsd-stable@FreeBSD.ORG In-reply-to: (message from Tom on Mon, 10 Aug 1998 12:29:43 -0700 (PDT)) Subject: Re: threads bug Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone have details on that libc_r.a problem with Mysql. We (at HighWind) have had a few issues with libc_r and John Birrell has been fast to address them. HOWEVER, we still have some nagging problem calling "pthread_create" where the call never returns and the application starts spinning at and getting nowhere. Looks like we nuked the threads scheduler or something like that. We are trying to isolate it to a test program. However, it is difficult since the application is complex. Rob Fleischman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 14:32:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03884 for freebsd-stable-outgoing; Mon, 10 Aug 1998 14:32:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA03876 for ; Mon, 10 Aug 1998 14:32:56 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z5zYG-00037l-00; Mon, 10 Aug 1998 14:32:25 -0700 Date: Mon, 10 Aug 1998 14:32:22 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: HighWind Software Information cc: gilem@wsg.net, freebsd-stable@FreeBSD.ORG Subject: Re: threads bug In-Reply-To: <199808102103.RAA27314@highwind.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Aug 1998, HighWind Software Information wrote: > Anyone have details on that libc_r.a problem with Mysql. We (at > HighWind) have had a few issues with libc_r and John Birrell has been > fast to address them. mysql hangs upon giving it a shutdown command. It doesn't seem to spinning, as CPU usage is low. mysql requires a kill -9 to stop. > HOWEVER, we still have some nagging problem calling "pthread_create" > where the call never returns and the application starts spinning at > and getting nowhere. > > Looks like we nuked the threads scheduler or something like that. > We are trying to isolate it to a test program. However, it is difficult > since the application is complex. Well, the thr_alarm test program in mysql exhibits the same problem as mysql. However, the mysql problem appears to be signal handling. > Rob Fleischman Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 15:11:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07899 for freebsd-stable-outgoing; Mon, 10 Aug 1998 15:11:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.wsg.net (ns1.wsg.net [206.97.122.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA07892 for ; Mon, 10 Aug 1998 15:11:07 -0700 (PDT) (envelope-from gilem@wsg.net) Message-Id: <199808102211.PAA07892@hub.freebsd.org> Received: (qmail 18976 invoked by uid 0); 10 Aug 1998 22:17:39 -0000 Received: from mike.wsg.net (HELO tc) (206.97.122.31) by mail.wsg.net with SMTP; 10 Aug 1998 22:17:39 -0000 X-Sender: mikemail@mail.wsg.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Mon, 10 Aug 1998 18:03:15 -0400 To: Tom From: "Michael R. Gile" Subject: Re: threads bug Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: References: <199808091343.GAA19125@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:29 PM 8/10/98 -0700, Tom wrote: > >On Sun, 9 Aug 1998, Michael R. Gile wrote: > >> There appears to be a recurring bug in libc_r that is causing >> Mysql not to respond to a shutdown. The author claims that >> he helped the development group fix this bug some time ago, >> but that it has recurred. Any suggestions on where to find this >> documentation would be helpful. > > I don't believe this bug was ever fixed. You can look at the cvslogs to >see all changes to libc_r. i tend to agree, but monty insists that he mailed the necessary fixes to the freebsd team months ago. >> thanks. >> >> At 12:55 PM 8/9/98 +0300, monty@analytikerna.se wrote: >> > >> >Michael> 2.2.7 >> >Michael> i just tried it >> >Michael> i wasn't clear that it would work, since the manual only mentions this for >> >Michael> it doesn't exhibit the problem above, but doesn't respond to mysqladmin shutdown. >> >Michael> any suggestions? >> > >> >This is a bug with the latest freebsd thread implementation. I >> >really suggest you should mail the freebsd developers about this; This >> >worked in a previous freebsd thread version (I helped freebsd to fix >> >that bug) but they have apparently managed to get the bug back again. >> > >> ====================================================== >> Michael Gile gilem@wsg.net >> President (518)435-0682 >> Web Services Group http://www.wsg.net/ > >Tom > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > ====================================================== Michael Gile gilem@wsg.net President (518)435-0682 Web Services Group http://www.wsg.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 15:28:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09980 for freebsd-stable-outgoing; Mon, 10 Aug 1998 15:28:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA09975 for ; Mon, 10 Aug 1998 15:28:22 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z60Q1-0000ly-00; Mon, 10 Aug 1998 15:27:58 -0700 Date: Mon, 10 Aug 1998 15:27:55 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Michael R. Gile" cc: freebsd-stable@FreeBSD.ORG Subject: Re: threads bug In-Reply-To: <199808102211.PAA07892@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Aug 1998, Michael R. Gile wrote: > At 12:29 PM 8/10/98 -0700, Tom wrote: > > > >On Sun, 9 Aug 1998, Michael R. Gile wrote: > > > >> There appears to be a recurring bug in libc_r that is causing > >> Mysql not to respond to a shutdown. The author claims that > >> he helped the development group fix this bug some time ago, > >> but that it has recurred. Any suggestions on where to find this > >> documentation would be helpful. > > > > I don't believe this bug was ever fixed. You can look at the cvslogs to > >see all changes to libc_r. > > i tend to agree, but monty insists that he mailed the necessary fixes > to the freebsd team months ago. Who is the "freebsd team"? It didn't appear on freebsd-current or freebsd-stable. You shoul ask who he sent them to, because they didn't make it to any of the committers. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 15:40:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11100 for freebsd-stable-outgoing; Mon, 10 Aug 1998 15:40:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from infowest.com (infowest.com [204.17.177.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11089; Mon, 10 Aug 1998 15:40:06 -0700 (PDT) (envelope-from agifford@infowest.com) Received: from infowest.com (eq.net [207.49.60.250]) by infowest.com (8.8.8/8.8.8) with ESMTP id QAA02081; Mon, 10 Aug 1998 16:39:38 -0600 (MDT) Message-ID: <35CF769F.68C80A22@infowest.com> Date: Mon, 10 Aug 1998 16:39:27 -0600 From: "Aaron D. Gifford" X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: questions@FreeBSD.ORG, stable@FreeBSD.ORG Subject: ipfw problem??? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Something's weird with my ipfw setup. It seems to work perfectly as I expected except for this tiny bit of weirdness. My ipfw setup lets me ping and traceroute and telnet to my heart's content EXCEPT when the remote address is within the same class C address space as my own dynamically assigned IP number. Then I get "sendto: Permission denied." errors left and right. Why is this? I checked my netmask via 'netstat -in' and sure enough, my netmask is 255.255.255.255. What's going on here? Looking at the output of 'ipfw -at list' shows me that the packets are hitting the FINAL deny statement. But when I ping/traceroute/telnet to other addresses, everything works just fine. I'm running 2.2.7-STABLE as of July 25th. I've included my /etc/rc.firewall script below that shows my configuration, but I really don't think this is an ipfw config problem. Puzzled, Aaron out. ---------/etc/rc.firewall---------- # Is the ipfw_mod module already loaded: mod=`/usr/bin/modstat -n ipfw_mod | /usr/bin/grep ipfw_mod | /usr/bin/awk '{print $8;}'` if [ "X${mod}" != "Xipfw_mod" ]; then # Load the ipfw kernel module /sbin/modload /lkm/ipfw_mod.o fi # Flush out the list before we begin. /sbin/ipfw -f flush # Learn what IP address our ISP has assigned (we dial out on tun0): ip=`/usr/bin/netstat -in | /usr/bin/perl -ne 'print $1 if( /^tun0\s+[0-9]+\s+[0-9\.]+\s+([0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3})\s+/ );'` # My external interface: extern="tun0" # My loopback interface: loop="lo0" # Deny obviously spoofed packets: /sbin/ipfw add deny log all from 127.0.0.1 to any via ${extern} /sbin/ipfw add deny log all from ${ip} to any in via ${extern} /sbin/ipfw add deny log all from 192.168.0.0:255.255.0.0 to any /sbin/ipfw add deny log all from 172.16.0.0:255.240.0.0 to any /sbin/ipfw add deny log all from 10.0.0.0:255.0.0.0 to any # Pass normal localhost traffic: /sbin/ipfw add pass all from 127.0.0.1 to 127.0.0.1 via ${loop} /sbin/ipfw add pass all from ${ip} to 127.0.0.1 via ${loop} /sbin/ipfw add pass all from 127.0.0.1 to ${ip} via ${loop} /sbin/ipfw add pass all from ${ip} to ${ip} via ${loop} # Deny everything else via the loopback: /sbin/ipfw add deny all from any to any via ${loop} # Pass established TCP connections: /sbin/ipfw add pass tcp from any to ${ip} in via ${extern} established /sbin/ipfw add pass tcp from ${ip} to any out via ${extern} established # Pass outgoing new TCP session setup packets: /sbin/ipfw add pass tcp from ${ip} to any setup # Deny all other TCP connection setup attempts: /sbin/ipfw add deny log tcp from any to any setup # Pass outgoing DNS queries: /sbin/ipfw add pass udp from ${ip} to any 53 out via ${extern} # Pass incoming DNS replies: # (This sure is ugly! It allows someone to do a udp portscan from port 53.) /sbin/ipfw add pass udp from any 53 to ${ip} in via ${extern} # Pass outgoing NTP queries: /sbin/ipfw add pass udp from ${ip} to any 123 out via ${extern} # Pass incoming NTP replies: # (This sure is ugly! It allows someone to do a udp portscan from port 123.) /sbin/ipfw add pass udp from any 123 to ${ip} in via ${extern} # Pass any UDP we decide to send (ala ping): /sbin/ipfw add pass udp from ${ip} to any out via ${extern} # Pass outgoing ICMP packets: /sbin/ipfw add pass icmp from ${ip} to any out via ${extern} # Pass incoming ICMP packets: /sbin/ipfw add pass icmp from any to ${ip} in via ${extern} # Toast EVERYTHING else: /sbin/ipfw add deny log all from any to any To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 15:46:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12181 for freebsd-stable-outgoing; Mon, 10 Aug 1998 15:46:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12175 for ; Mon, 10 Aug 1998 15:46:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA00391; Mon, 10 Aug 1998 15:44:16 -0700 (PDT) Message-Id: <199808102244.PAA00391@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Michael R. Gile" cc: Tom , freebsd-stable@FreeBSD.ORG Subject: Re: threads bug In-reply-to: Your message of "Mon, 10 Aug 1998 18:03:15 EDT." <199808102211.PAA07892@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 15:44:16 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 12:29 PM 8/10/98 -0700, Tom wrote: > > > >On Sun, 9 Aug 1998, Michael R. Gile wrote: > > > >> There appears to be a recurring bug in libc_r that is causing > >> Mysql not to respond to a shutdown. The author claims that > >> he helped the development group fix this bug some time ago, > >> but that it has recurred. Any suggestions on where to find this > >> documentation would be helpful. > > > > I don't believe this bug was ever fixed. You can look at the cvslogs to > >see all changes to libc_r. > > i tend to agree, but monty insists that he mailed the necessary fixes > to the freebsd team months ago. To whom? The correct thing do to would be to file a PR, and then use the PR when referring to this. It wouldn't be surprising if the patches are rotting in someone's inbox where nobody else can get at them. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 16:31:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18660 for freebsd-stable-outgoing; Mon, 10 Aug 1998 16:31:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from iworks.interworks.org (iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18638; Mon, 10 Aug 1998 16:31:25 -0700 (PDT) (envelope-from deischen@iworks.interworks.org) Received: (from deischen@localhost) by iworks.interworks.org (8.8.7/8.8.7) id SAA20138; Mon, 10 Aug 1998 18:35:30 -0500 (CDT) Date: Mon, 10 Aug 1998 18:35:30 -0500 (CDT) From: "Daniel M. Eischen" Message-Id: <199808102335.SAA20138@iworks.interworks.org> To: info@highwind.com, owner-freebsd-stable@FreeBSD.ORG Subject: Re: threads bug Cc: freebsd-stable@FreeBSD.ORG, gilem@wsg.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Anyone have details on that libc_r.a problem with Mysql. We (at > > HighWind) have had a few issues with libc_r and John Birrell has been > > fast to address them. > > mysql hangs upon giving it a shutdown command. It doesn't seem to > spinning, as CPU usage is low. mysql requires a kill -9 to stop. I was recently having problems porting the run-time of the latest version of GNAT to FreeBSD/pthreads. I figured out the problem to be related to priorities. Ada was assuming priorities in the range of 0 .. 31, so all tasks were getting created with priorities within this range. (An Ada task is created as a thread). But the main program was never having it's priority explicitly set, so it was defaulting to a priority of 64 (the FreeBSD pthreads default priority). When trying to terminate an application, the main program signals (cond_signal) two tasks created at run-time to terminate. One of these tasks is an interrupt manager task and runs at the highest priority (31). The main program assumes that this task will see the signal and properly terminate. But because the main programs priority was higher (64 vs 31), the interrupt manager was never getting a chance to run and terminate. Hence the main program waited indefinitely. The solution was to base Ada priorities around FreeBSDs default thread priority of 64. It was a one-line fix to the GNAT run-time, but it took a while to figure out. Could Mysql be having a similar problem? Dan Eischen deischen@iworks.InterWorks.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 16:56:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23629 for freebsd-stable-outgoing; Mon, 10 Aug 1998 16:56:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23623 for ; Mon, 10 Aug 1998 16:56:27 -0700 (PDT) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.8.8/8.8.8) with SMTP id TAA26887 for ; Mon, 10 Aug 1998 19:56:06 -0400 (EDT) Message-Id: <3.0.5.32.19980810195557.00962a10@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 10 Aug 1998 19:55:57 -0400 To: freebsd-stable@FreeBSD.ORG From: Dan Swartzendruber Subject: quota doesn't work for SUID root... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tracked down the PR I opened (vis-a-vis the SUID root issue I emailed about several days ago). The PR is kern/5285. It was opened back in December, is still open, and has never been updated :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 17:42:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01266 for freebsd-stable-outgoing; Mon, 10 Aug 1998 17:42:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pn.wagsky.com (wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01244 for ; Mon, 10 Aug 1998 17:42:41 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id RAA00307 for ; Mon, 10 Aug 1998 17:42:12 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: mailman@mail.pn.wagsky.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 10 Aug 1998 17:42:07 -0700 To: freebsd-stable@FreeBSD.ORG From: Jeff Kletsky Subject: XF86_SVGA hangs 2.2.7-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just rebuilt the XFree86 distribution on a 2.2.7-STABLE machine (last CVsup of stable, Aug 8, 7:18 AM, ports, Aug 10, 9:33 AM) and find that the entire machine hangs when SVGA server is started. (no keyboard or network response -- forcing the dreaded reset-button approach). The video card is a Diamond Stealth 64 DRAM PCI. Things seemed to be ok running the package as distributed with 2.2.6-RELEASE under this build of 2.2.7-STABLE. Configuration files and the X -> XF86_SVGA link do not appear modified by the build. XF86Setup *does* run using the simple driver but also freezes when it tries to start the selected driver. Restoring the "original" XF86_SVGA (dated Mar 1 02:10) does not solve the problem. Restoring the original /usr/X11R6 heirarchy *does* restore functionality. There is not a version of the package on ftp.FreeBSD.org in the packages-STABLE area that I could find at this time. Any suggestions? (other than stick with what works ;-) Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 18:19:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07328 for freebsd-stable-outgoing; Mon, 10 Aug 1998 18:19:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wankers.net (user-37kbnid.dialup.mindspring.com [207.69.222.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07322 for ; Mon, 10 Aug 1998 18:19:33 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost.mindspring.com [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id VAA09802; Mon, 10 Aug 1998 21:21:47 -0400 (EDT) (envelope-from dex@wankers.net) Date: Mon, 10 Aug 1998 21:21:46 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: Jeff Kletsky cc: freebsd-stable@FreeBSD.ORG Subject: Re: XF86_SVGA hangs 2.2.7-STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Aug 1998, Jeff Kletsky wrote: [*snip*] > Any suggestions? > (other than stick with what works ;-) Try using the right server? (XF86_S3) -Jon ;P~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 18:55:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11171 for freebsd-stable-outgoing; Mon, 10 Aug 1998 18:55:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from infid.detour.net (nw52.netwave.ca [204.101.215.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11162 for ; Mon, 10 Aug 1998 18:54:56 -0700 (PDT) (envelope-from takkala@netwave.ca) Received: from localhost (localhost [127.0.0.1]) by infid.detour.net (8.9.0/8.9.0) with SMTP id VAA00365 for ; Mon, 10 Aug 1998 21:54:27 -0400 (EDT) Date: Mon, 10 Aug 1998 21:54:26 -0400 (EDT) From: Takkala X-Sender: takkala@infid.detour.net To: freebsd-stable@FreeBSD.ORG Subject: more ipfw stuff (problems?) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While were on the topic of ipfw problems, here's another one. I'm not sure if its a bug in ipfw or not, but here goes. I got this in my logs a few days ago: Aug 7 19:35:09 ns1 /kernel: ipfw: -1 Refuse TCP 207.179.186.25:1341 160.79.218.4:80 in via ed1 Aug 7 19:35:14 ns1 /kernel: ipfw: -1 Refuse TCP 207.179.186.25:2592 160.79.218.4:80 in via ed1 Now, I do not have any TCP deny rules on my server, the only rules i have are to deny icmp echo request / reply packets. Also, after examining the web server logs, I was able to determine that the above person was in fact able to access documents on our web server. I just find the "ipfw: -1" odd, and the fact that these packets are being refused. Does anyone know if this is a bug in ipfw, or if the client was running something like Windows, and was spewing bad TCP packets? I'm running 2.2.7-STABLE, cvsupped somewhere around July 27. This is a very isolated incident, considering that we serve around 60,000 ppl a day, and 83 million TCP packets on average pass through this system a day. Jari Takkala - [takkalaNOSPAM@netwave.ca] [Hint: take out the NOSPAM when replying] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 19:43:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16410 for freebsd-stable-outgoing; Mon, 10 Aug 1998 19:43:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA16404 for ; Mon, 10 Aug 1998 19:43:33 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id TAA29096; Mon, 10 Aug 1998 19:43:11 -0700 (PDT) Message-ID: <19980810194311.A29027@nuxi.com> Date: Mon, 10 Aug 1998 19:43:11 -0700 From: "David O'Brien" To: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.7 crash Reply-To: obrien@NUXI.com References: <199808060128.SAA08679@tao.thought.org> <000101bdc1dc$4f08bae0$0a00a8c0@uptight.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <000101bdc1dc$4f08bae0$0a00a8c0@uptight.student.utwente.nl>; from laurens van alphen on Fri, Aug 07, 1998 at 10:20:59AM +0200 X-Operating-System: FreeBSD 2.2.7-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 07, 1998 at 10:20:59AM +0200, laurens van alphen wrote: > > Fatal trap 12: page fault while in kernel mode Yet more VM panics. I'm at the point I can't even build the gcc28 port, or even ``make install'' it if I get past the build of it. gdb "where" output from From two different pannics are below. What's the next step to figuring out this problem? (kgdb) core-file /var/crash/vmcore.1 IdlePTD 223000 current pcb at 1e11f8 panic: pmap_release: freeing held page table page #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 266 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 #1 0xf01166a3 in panic ( fmt=0xf019f529 "pmap_release: freeing held page table page") at ../../kern/kern_shutdown.c:400 #2 0xf019f604 in pmap_release_free_page (pmap=0xf0d11c64, p=0xf0317028) at ../../i386/i386/pmap.c:1074 #3 0xf019f8d7 in pmap_release (pmap=0xf0d11c64) at ../../i386/i386/pmap.c:1262 #4 0xf0187762 in vmspace_free (vm=0xf0d11c00) at ../../vm/vm_map.c:262 #5 0xf01a8db6 in cpu_wait (p=0xf0944000) at ../../i386/i386/vm_machdep.c:650 #6 0xf010f54a in wait1 (q=0xf0c5ce00, uap=0xefbfff94, retval=0xefbfff84, compat=0) at ../../kern/kern_exit.c:460 #7 0xf010f376 in wait4 (p=0xf0c5ce00, uap=0xefbfff94, retval=0xefbfff84) at ../../kern/kern_exit.c:357 #8 0xf01a3816 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 1, tf_esi = 3, tf_ebp = -272641820, tf_isp = -272629788, tf_ebx = 537477216, tf_edx = 5775, tf_ecx = 73920, tf_eax = 7, tf_trapno = 12, tf_err = 7, tf_eip = 537228193, tf_cs = 31, tf_eflags = 534, tf_esp = -272641844, tf_ss = 39}) at ../../i386/i386/trap.c:920 #9 0x200573a1 in ?? () >From the second: (kgdb) core-file /var/crash/vmcore.2 IdlePTD 223000 current pcb at 1e11f8 panic: vref used where vget required #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 266 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 #1 0xf01166a3 in panic (fmt=0xf013a5ec "vref used where vget required") at ../../kern/kern_shutdown.c:400 #2 0xf013a627 in vref (vp=0xf0862d80) at ../../kern/vfs_subr.c:833 #3 0xf5041c80 in ?? () #4 0xf504411a in ?? () #5 0xf01390a0 in lookup (ndp=0xefbffea8) at ../../kern/vfs_lookup.c:482 #6 0xf0138a0d in namei (ndp=0xefbffea8) at ../../kern/vfs_lookup.c:156 #7 0xf013d3c4 in stat (p=0xf07aee00, uap=0xefbfff94, retval=0xefbfff84) at ../../kern/vfs_syscalls.c:1293 #8 0xf01a3816 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 201728, tf_esi = 0, tf_ebp = -272643916, tf_isp = -272629788, tf_ebx = 14336, tf_edx = 0, tf_ecx = 201728, tf_eax = 188, tf_trapno = 12, tf_err = 7, tf_eip = 537409649, tf_cs = 31, tf_eflags = 582, tf_esp = -272644048, tf_ss = 39}) at ../../i386/i386/trap.c:920 #9 0x20083871 in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 19:47:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17187 for freebsd-stable-outgoing; Mon, 10 Aug 1998 19:47:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from amor.wcs.uq.edu.au (amor.wcs.uq.edu.au [130.102.222.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17174 for ; Mon, 10 Aug 1998 19:47:18 -0700 (PDT) (envelope-from garyr@amor.wcs.uq.edu.au) Received: (from garyr@localhost) by amor.wcs.uq.edu.au (8.8.8/8.8.8) id MAA08569 for freebsd-stable@FreeBSD.ORG; Tue, 11 Aug 1998 12:44:02 +1000 (EST) (envelope-from garyr) From: Gary Roberts Message-Id: <199808110244.MAA08569@amor.wcs.uq.edu.au> Subject: Is Intel EtherExpress PRO/100 Mobile Adapter supported? To: freebsd-stable@FreeBSD.ORG Date: Tue, 11 Aug 1998 12:44:02 +1000 (EST) Organisation: Well Control Australia Phone: +617 3844 0400 Fax: +617 3844 0444 Reply-To: garyr@wcs.uq.edu.au (Gary Roberts) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to load 2.2.7-RELEASE on a new Toshiba notebook which has the above PCMCIA card but it doesn't seem to be detected by the GENERIC kernel. I assumed that since the Intel EtherExpress PRO/10 is reported as supported, it would probably also be in the PC card format as well. Can anyone advise whether there is any support now or in the near future for this card? Thanks, -- Gary Roberts (garyr@wcs.uq.edu.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 19:48:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17397 for freebsd-stable-outgoing; Mon, 10 Aug 1998 19:48:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kendra.ne.mediaone.net (kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17362 for ; Mon, 10 Aug 1998 19:48:02 -0700 (PDT) (envelope-from software@kew.com) Received: from ffactory.uucp.kew.com (ffactory.hh.kew.com [192.168.203.131]) by kendra.ne.mediaone.net (8.9.0/8.9.0) with SMTP id WAA24193; Mon, 10 Aug 1998 22:46:25 -0400 (EDT) Received: from kew.com by ffactory.uucp.kew.com (UUPC/extended 1.13c) with UUCP for multiple addressees; Mon, 10 Aug 1998 22:46:25 -0500 Received: from kew.com by ffactory.uucp.kew.com (UUPC/extended 1.13c) with ESMTP for multiple addresses; Mon, 10 Aug 1998 22:46:23 -0500 Message-ID: <35CFB07F.C786C7BA@kew.com> Date: Mon, 10 Aug 1998 22:46:23 -0400 From: Drew Derbyshire Organization: Kendra Electronic Wonderworks, Stoneham, MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.05 [en] (WinNT; U) MIME-Version: 1.0 To: Mike Smith CC: stable@FreeBSD.ORG Subject: Re: zp0 not receiving under 2.2.7? References: <199808101620.JAA12498@antipodes.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm .... (read entire message before responding!) Mike Smith wrote: > > As it is, however, the pccardd message doesn't tell me what the > > problem is. > > No, but it can often tell us what's going on (most of the time). There > are three messages you're likely to get: > > - "no driver found for ..." meaning your pccard.conf file entry is > wrong. > - "resource allocation failed for ..." meaning that the resource > information in your pccard.conf file conflicts with the > configuration entry you've selected from the card > - "driver allocation failed for ..." meaning that the driver probe > failed, or the kernel disagrees with you as to the resources that > you've assigned to the card (ie. they're in use elsewhere). Bingo. > > I presume zp0 should at least get the system on to my network. I don't swap > > cards, really. > > It *should* work, yes. The lack of incoming packets does suggest an > interrupt problem of some sort though. Windows claims the card is using 0x300 and IRQ 5 (my new home for it), the card configuration program claims I'm using same, and FreeBSD is configured for same. No joy. pccardc dumpcis reporting amusing things, I can't seem to pick the actual configuration out of it. (pccardc is missing a man page, BTW) I am able to get the system see my USR PC Card modem at SIO2/IRQ 11, via a nice fresh entry. Hmmm. One more try, change the "?" to the explicit IRQ I want ... WHAMMO, ep0 works. Well, *was* "?" legal? -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9812 This message intentionally left almost blank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 19:57:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18551 for freebsd-stable-outgoing; Mon, 10 Aug 1998 19:57:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18541 for ; Mon, 10 Aug 1998 19:57:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA01735; Mon, 10 Aug 1998 19:54:35 -0700 (PDT) Message-Id: <199808110254.TAA01735@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Drew Derbyshire cc: Mike Smith , stable@FreeBSD.ORG Subject: Re: zp0 not receiving under 2.2.7? In-reply-to: Your message of "Mon, 10 Aug 1998 22:46:23 EDT." <35CFB07F.C786C7BA@kew.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 19:54:34 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmmm .... (read entire message before responding!) Wilco. I was waiting for your reply, because this morning I left the dongle for my NE2000 at home, so I was forced to use my backup '589. It sucked; I had to build a new kernel, then some new userland utils (because the userland on my laptop is horribly old and my sources are up to date so I can tinker). But once I had everything in sync, it all "just worked". > Hmmm. One more try, change the "?" to the explicit IRQ I want ... WHAMMO, > ep0 works. Well, *was* "?" legal? It's not so much whether it's legal as whether it works. I don't like ? because the smarts behind the auto-IRQ allocation aren't good. We don't do enough PnP by far for it to be reliable. eg. I use: # 3com 3c589D card "3Com Corporation" "3C589D" config 0x1 "ep0" 9 insert /etc/pccard_ether ep0 -link0 remove /sbin/ifconfig ep0 delete and that "just works" (both on the card I had partially stolen giving me BNC, and on this card giving me UTP). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 19:57:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18596 for freebsd-stable-outgoing; Mon, 10 Aug 1998 19:57:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18588 for ; Mon, 10 Aug 1998 19:57:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA01751; Mon, 10 Aug 1998 19:55:52 -0700 (PDT) Message-Id: <199808110255.TAA01751@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: garyr@wcs.uq.edu.au (Gary Roberts) cc: freebsd-stable@FreeBSD.ORG Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? In-reply-to: Your message of "Tue, 11 Aug 1998 12:44:02 +1000." <199808110244.MAA08569@amor.wcs.uq.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 19:55:52 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying to load 2.2.7-RELEASE on a new Toshiba notebook which > has the above PCMCIA card but it doesn't seem to be detected by > the GENERIC kernel. > > I assumed that since the Intel EtherExpress PRO/10 is reported as > supported, it would probably also be in the PC card format as well. The PRO/10 and the PRO/100 mobile are completely different cards. The latter is likely to be a CardBus card as well. We don't support either. > Can anyone advise whether there is any support now or in the near > future for this card? We need more driver authors, and particularly CardBus support authors. Until that happens, there'll be no support for that card, no. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 20:05:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20081 for freebsd-stable-outgoing; Mon, 10 Aug 1998 20:05:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA20059 for ; Mon, 10 Aug 1998 20:05:00 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z64jj-0001UW-00; Mon, 10 Aug 1998 20:04:35 -0700 Date: Mon, 10 Aug 1998 20:04:32 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "David O'Brien" cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.7 crash In-Reply-To: <19980810194311.A29027@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Aug 1998, David O'Brien wrote: > On Fri, Aug 07, 1998 at 10:20:59AM +0200, laurens van alphen wrote: > > > Fatal trap 12: page fault while in kernel mode > > Yet more VM panics. I'm at the point I can't even build the gcc28 port, > or even ``make install'' it if I get past the build of it. gdb "where" > output from From two different pannics are below. > > What's the next step to figuring out this problem? Well, since you are getting different kinds of panics, you should start by using some kind of error detecting memory. Either parity or ECC SIMM or DIMM modules will do, with a supporting motherboard. What you are seeing is almost certainly a hardware failure. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 20:22:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21925 for freebsd-stable-outgoing; Mon, 10 Aug 1998 20:22:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ha1.rdc1.nj.home.com (ha1.rdc1.nj.home.com [24.3.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21920 for ; Mon, 10 Aug 1998 20:22:34 -0700 (PDT) (envelope-from garycor@home.com) Received: from home.com ([24.3.185.85]) by ha1.rdc1.nj.home.com (Netscape Mail Server v2.02) with ESMTP id AAA6418; Mon, 10 Aug 1998 20:22:10 -0700 Message-ID: <35CFB92F.F2A23952@home.com> Date: Mon, 10 Aug 1998 23:23:27 -0400 From: "Gary T. Corcoran" X-Mailer: Mozilla 4.05 [en] (Win95; U) MIME-Version: 1.0 To: Dexnation Holodream CC: Jeff Kletsky , freebsd-stable@FreeBSD.ORG Subject: Re: XF86_SVGA hangs 2.2.7-STABLE References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dexnation Holodream wrote: > > On Mon, 10 Aug 1998, Jeff Kletsky wrote: > > [*snip*] > > > Any suggestions? > > (other than stick with what works ;-) > > Try using the right server? (XF86_S3) I know it's counter-intuitive, but the XF86_SVGA server is NOT just a "super VGA" (800x600) server. It's actually the more advanced X server for some of the chips, including the S3 chips. Check the docs for the details... Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 20:26:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22475 for freebsd-stable-outgoing; Mon, 10 Aug 1998 20:26:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22465 for ; Mon, 10 Aug 1998 20:26:50 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id UAA29235 for freebsd-stable@FreeBSD.ORG; Mon, 10 Aug 1998 20:26:22 -0700 (PDT) Message-ID: <19980810202621.B29027@nuxi.com> Date: Mon, 10 Aug 1998 20:26:21 -0700 From: "David O'Brien" To: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.7 crash Reply-To: obrien@NUXI.com References: <199808060128.SAA08679@tao.thought.org> <000101bdc1dc$4f08bae0$0a00a8c0@uptight.student.utwente.nl> <19980810194311.A29027@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19980810194311.A29027@nuxi.com>; from David O'Brien on Mon, Aug 10, 1998 at 07:43:11PM -0700 X-Operating-System: FreeBSD 2.2.7-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 10, 1998 at 07:43:11PM -0700, David O'Brien wrote: > On Fri, Aug 07, 1998 at 10:20:59AM +0200, laurens van alphen wrote: > > > Fatal trap 12: page fault while in kernel mode > > Yet more VM panics. I'm at the point I can't even build the gcc28 port, Forgot to mention the date of the CVS check out and build: FreeBSD 2.2.7-STABLE #1: Thu Jul 23 10:30:01 PDT 1998 -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 20:28:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22739 for freebsd-stable-outgoing; Mon, 10 Aug 1998 20:28:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22734 for ; Mon, 10 Aug 1998 20:28:22 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id UAA29251; Mon, 10 Aug 1998 20:27:58 -0700 (PDT) Message-ID: <19980810202758.A29238@nuxi.com> Date: Mon, 10 Aug 1998 20:27:58 -0700 From: "David O'Brien" To: Tom Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.7 crash Reply-To: obrien@NUXI.com References: <19980810194311.A29027@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Tom on Mon, Aug 10, 1998 at 08:04:32PM -0700 X-Operating-System: FreeBSD 2.2.7-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What's the next step to figuring out this problem? > > What you are seeing is almost certainly a hardware failure. Would memory just start going bad? This machine has been stable running the 2.2-STABLE branch for over a year not. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 20:40:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25032 for freebsd-stable-outgoing; Mon, 10 Aug 1998 20:40:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wankers.net (user-37kbnid.dialup.mindspring.com [207.69.222.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25011 for ; Mon, 10 Aug 1998 20:40:40 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost.mindspring.com [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id XAA12000; Mon, 10 Aug 1998 23:42:49 -0400 (EDT) (envelope-from dex@wankers.net) Date: Mon, 10 Aug 1998 23:42:48 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: Gary Roberts cc: freebsd-stable@FreeBSD.ORG Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? In-Reply-To: <199808110244.MAA08569@amor.wcs.uq.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Aug 1998, Gary Roberts wrote: > I'm trying to load 2.2.7-RELEASE on a new Toshiba notebook which > has the above PCMCIA card but it doesn't seem to be detected by > the GENERIC kernel. > > I assumed that since the Intel EtherExpress PRO/10 is reported as > supported, it would probably also be in the PC card format as well. > > Can anyone advise whether there is any support now or in the near > future for this card? ok...first off...the PRO/10 driver is PCI only. #2 only NEW revisions of the card work...I have the OLD revision, and am considering writing a driver, but intel's documentation is VERY hard to find on the chip that drives it (the 82596)...I've found documentation to port to the NEW chip from the OLD, but none on the 82596...now...the pcmcia card doesn't use the PCI bus calls, it uses the PCCARD calls, which is a complete other ball of wax. now...if I can get the specs, I'll code a driver for the OLD one (fps driver, for fscking piece of spam...) anyway, I don't know how common it is, but the 82595 is the chip on the ISA cards, which is very common...the 82596 is a local bus chip...and has a second chip for the bus (which handle the PCI stuff)...later, they designed a new chip (used on the NEW Pro10+'s, and the Pro10/100's...fxp driver) which has all of the PCI stuff on-chip, and has a reduced instruction set, and adds a reset instruction (I'm not going to go into details here, as this isn't a technical list). Anyway, if people are interested in the 82596 driver, and would like to support the effort, I'd appreciate any help they can offer (documentation you may have, spare cards that are based on it for testing, RAM for the test machine if you can spare it (cooked a 32meg 72-pin SIMM...lost my test machine), anything else you may want to contribute to the effort). I would write a driver for the PCCARD version, but I have neither a test card, nor a test machine for it, so, unless someone wants a driver badly enough to supply both of the above, you're out of luck on getting it from me. Lemme know what's up, folks :) -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 21:01:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28301 for freebsd-stable-outgoing; Mon, 10 Aug 1998 21:01:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28267 for ; Mon, 10 Aug 1998 21:01:17 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id VAA27672; Mon, 10 Aug 1998 21:01:23 -0700 (PDT) Message-Id: <199808110401.VAA27672@implode.root.com> To: obrien@NUXI.com cc: Tom , freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.7 crash In-reply-to: Your message of "Mon, 10 Aug 1998 20:27:58 PDT." <19980810202758.A29238@nuxi.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 10 Aug 1998 21:01:23 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > What's the next step to figuring out this problem? >> >> What you are seeing is almost certainly a hardware failure. > >Would memory just start going bad? This machine has been stable running >the 2.2-STABLE branch for over a year not. Memory errors can often go unnoticed if they happend to occur in bits that previously were unused. The layout of the 2.2.7 kernel could have moved the defective bits to a sensitive spot. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 21:25:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02842 for freebsd-stable-outgoing; Mon, 10 Aug 1998 21:25:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02821 for ; Mon, 10 Aug 1998 21:24:53 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA24064; Mon, 10 Aug 1998 22:24:15 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA04178; Mon, 10 Aug 1998 22:24:12 -0600 Date: Mon, 10 Aug 1998 22:24:12 -0600 Message-Id: <199808110424.WAA04178@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Drew Derbyshire , stable@FreeBSD.ORG Subject: Re: zp0 not receiving under 2.2.7? In-Reply-To: <199808110254.TAA01735@dingo.cdrom.com> References: <35CFB07F.C786C7BA@kew.com> <199808110254.TAA01735@dingo.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hmmm. One more try, change the "?" to the explicit IRQ I want ... WHAMMO, > > ep0 works. Well, *was* "?" legal? > > It's not so much whether it's legal as whether it works. I don't like > ? because the smarts behind the auto-IRQ allocation aren't good. We > don't do enough PnP by far for it to be reliable. However, they're do a better job of guessing an available IRQ than most users. :) :) :) (I'm being both serious and attempting to be funny at the same time...) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 21:26:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03234 for freebsd-stable-outgoing; Mon, 10 Aug 1998 21:26:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from athena.bfmni.com (www.bfmni.com [206.172.20.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03212 for ; Mon, 10 Aug 1998 21:26:31 -0700 (PDT) (envelope-from bsmith@bfmni.com) Received: from whatzit ([206.172.20.156]) by athena.bfmni.com (post.office MTA v2.0 0813 ID# 0-30094U35) with SMTP id AAA191; Tue, 11 Aug 1998 00:26:03 -0400 Message-ID: <003901bdc4e0$2443bf60$6403a8c0@comstyle.com> From: bsmith@bfmni.com (Brad Smith) To: "Dexnation Holodream" Cc: Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? Date: Tue, 11 Aug 1998 00:25:54 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0518.4 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0518.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a couple of these Intel EtherExpress PRO 10 PCI cards, but all I could do is some testing of the driver and thats about it ... dont know howto code in C (wish I could). Brad >On Tue, 11 Aug 1998, Gary Roberts wrote: > >> I'm trying to load 2.2.7-RELEASE on a new Toshiba notebook which >> has the above PCMCIA card but it doesn't seem to be detected by >> the GENERIC kernel. >> >> I assumed that since the Intel EtherExpress PRO/10 is reported as >> supported, it would probably also be in the PC card format as well. >> >> Can anyone advise whether there is any support now or in the near >> future for this card? > >ok...first off...the PRO/10 driver is PCI only. #2 only NEW revisions of >the card work...I have the OLD revision, and am considering writing a >driver, but intel's documentation is VERY hard to find on the chip that >drives it (the 82596)...I've found documentation to port to the NEW chip >from the OLD, but none on the 82596...now...the pcmcia card doesn't use >the PCI bus calls, it uses the PCCARD calls, which is a complete other >ball of wax. > >now...if I can get the specs, I'll code a driver for the OLD one (fps >driver, for fscking piece of spam...) anyway, I don't know how common it >is, but the 82595 is the chip on the ISA cards, which is very common...the >82596 is a local bus chip...and has a second chip for the bus (which >handle the PCI stuff)...later, they designed a new chip (used on the >NEW Pro10+'s, and the Pro10/100's...fxp driver) which has all of the PCI >stuff on-chip, and has a reduced instruction set, and adds a reset >instruction (I'm not going to go into details here, as this isn't a >technical list). > >Anyway, if people are interested in the 82596 driver, and would like to >support the effort, I'd appreciate any help they can offer (documentation >you may have, spare cards that are based on it for testing, RAM for the >test machine if you can spare it (cooked a 32meg 72-pin SIMM...lost my >test machine), anything else you may want to contribute to the effort). > >I would write a driver for the PCCARD version, but I have neither a test >card, nor a test machine for it, so, unless someone wants a driver badly >enough to supply both of the above, you're out of luck on getting it from >me. Lemme know what's up, folks :) > >-Jon > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 21:28:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03574 for freebsd-stable-outgoing; Mon, 10 Aug 1998 21:28:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from superior.mooseriver.com (superior.mooseriver.com [208.138.27.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03569 for ; Mon, 10 Aug 1998 21:28:32 -0700 (PDT) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id VAA03294; Mon, 10 Aug 1998 21:26:56 -0700 (PDT) (envelope-from jgrosch) Message-ID: <19980810212646.A3278@mooseriver.com> Date: Mon, 10 Aug 1998 21:26:46 -0700 From: Josef Grosch To: obrien@NUXI.com, Tom Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.7 crash Reply-To: jgrosch@mooseriver.com References: <19980810194311.A29027@nuxi.com> <19980810202758.A29238@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980810202758.A29238@nuxi.com>; from David O'Brien on Mon, Aug 10, 1998 at 08:27:58PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 10, 1998 at 08:27:58PM -0700, David O'Brien wrote: > > > What's the next step to figuring out this problem? > > > > What you are seeing is almost certainly a hardware failure. > > Would memory just start going bad? This machine has been stable running > the 2.2-STABLE branch for over a year not. Entropy, man. It's everywhere! Josef "Wow, trails!" Grosch -- Josef Grosch | Another day closer to a | FreeBSD 2.2.7 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 22:34:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10686 for freebsd-stable-outgoing; Mon, 10 Aug 1998 22:34:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wankers.net (user-38lc10b.dialup.mindspring.com [209.86.4.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10681 for ; Mon, 10 Aug 1998 22:34:51 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost.mindspring.com [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id BAA13728; Tue, 11 Aug 1998 01:36:21 -0400 (EDT) (envelope-from dex@wankers.net) Date: Tue, 11 Aug 1998 01:36:21 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: Brad Smith cc: freebsd-stable@FreeBSD.ORG Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? In-Reply-To: <003901bdc4e0$2443bf60$6403a8c0@comstyle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the 82596 one, or the newer one? On Tue, 11 Aug 1998, Brad Smith wrote: > I have a couple of these Intel EtherExpress PRO 10 PCI cards, but all I > could do is some testing of the driver and thats about it ... dont know > howto code in C (wish I could). > > Brad > > >On Tue, 11 Aug 1998, Gary Roberts wrote: > > > >> I'm trying to load 2.2.7-RELEASE on a new Toshiba notebook which > >> has the above PCMCIA card but it doesn't seem to be detected by > >> the GENERIC kernel. > >> > >> I assumed that since the Intel EtherExpress PRO/10 is reported as > >> supported, it would probably also be in the PC card format as well. > >> > >> Can anyone advise whether there is any support now or in the near > >> future for this card? > > > >ok...first off...the PRO/10 driver is PCI only. #2 only NEW revisions of > >the card work...I have the OLD revision, and am considering writing a > >driver, but intel's documentation is VERY hard to find on the chip that > >drives it (the 82596)...I've found documentation to port to the NEW chip > >from the OLD, but none on the 82596...now...the pcmcia card doesn't use > >the PCI bus calls, it uses the PCCARD calls, which is a complete other > >ball of wax. > > > >now...if I can get the specs, I'll code a driver for the OLD one (fps > >driver, for fscking piece of spam...) anyway, I don't know how common it > >is, but the 82595 is the chip on the ISA cards, which is very common...the > >82596 is a local bus chip...and has a second chip for the bus (which > >handle the PCI stuff)...later, they designed a new chip (used on the > >NEW Pro10+'s, and the Pro10/100's...fxp driver) which has all of the PCI > >stuff on-chip, and has a reduced instruction set, and adds a reset > >instruction (I'm not going to go into details here, as this isn't a > >technical list). > > > >Anyway, if people are interested in the 82596 driver, and would like to > >support the effort, I'd appreciate any help they can offer (documentation > >you may have, spare cards that are based on it for testing, RAM for the > >test machine if you can spare it (cooked a 32meg 72-pin SIMM...lost my > >test machine), anything else you may want to contribute to the effort). > > > >I would write a driver for the PCCARD version, but I have neither a test > >card, nor a test machine for it, so, unless someone wants a driver badly > >enough to supply both of the above, you're out of luck on getting it from > >me. Lemme know what's up, folks :) > > > >-Jon > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 22:42:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11697 for freebsd-stable-outgoing; Mon, 10 Aug 1998 22:42:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11691 for ; Mon, 10 Aug 1998 22:42:09 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA13021; Mon, 10 Aug 1998 23:41:31 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <35CFD98B.A73F9477@softweyr.com> Date: Mon, 10 Aug 1998 23:41:31 -0600 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Gary Roberts CC: freebsd-stable@FreeBSD.ORG Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? References: <199808110244.MAA08569@amor.wcs.uq.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Roberts wrote: > > I'm trying to load 2.2.7-RELEASE on a new Toshiba notebook which > has the above PCMCIA card but it doesn't seem to be detected by > the GENERIC kernel. > > I assumed that since the Intel EtherExpress PRO/10 is reported as > supported, it would probably also be in the PC card format as well. > > Can anyone advise whether there is any support now or in the near > future for this card? I believe if you check really closely, the Intel PCMCIA ethernet cards are OEM'd from Xircom. (Intel owns a big chunk of Xircom.) If you can locate some Xircom PCMCIA drivers, you might want to give them a whirl. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 10 22:59:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13519 for freebsd-stable-outgoing; Mon, 10 Aug 1998 22:59:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA13511 for ; Mon, 10 Aug 1998 22:59:44 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z67Si-0000MW-00; Mon, 10 Aug 1998 22:59:12 -0700 Date: Mon, 10 Aug 1998 22:59:08 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "David O'Brien" cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.7 crash In-Reply-To: <19980810202758.A29238@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Aug 1998, David O'Brien wrote: > > > What's the next step to figuring out this problem? > > > > What you are seeing is almost certainly a hardware failure. > > Would memory just start going bad? This machine has been stable running > the 2.2-STABLE branch for over a year not. Why not? Memory doesn't exactly give you warning signs before it fails, it just fails. Probably just a marginal component to begin within. Could also be a contact problem (ex. corrosion). > -- > -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 00:32:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21423 for freebsd-stable-outgoing; Tue, 11 Aug 1998 00:32:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from SchematiX.net (schematix.net [24.234.31.158]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21418 for ; Tue, 11 Aug 1998 00:32:52 -0700 (PDT) (envelope-from scott@SchematiX.net) Received: from localhost (scott@localhost) by SchematiX.net (8.8.8/8.8.8) with SMTP id AAA00268 for ; Tue, 11 Aug 1998 00:31:03 -0700 (PDT) (envelope-from scott@SchematiX.net) Date: Tue, 11 Aug 1998 00:31:03 -0700 (PDT) From: Scott To: FreeBSD-stable@FreeBSD.ORG Subject: Huge Bug in FreeBSD not fixed? Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1205284948-902820663=:216" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1205284948-902820663=:216 Content-Type: TEXT/PLAIN; charset=US-ASCII I ran across this bug a while back on rootshell, and then again by a user on IRC who offered to take down my box. Soon after that, the bug was fixed and things were fine. But just out of boredom, i decided to run the exploit again. Sure enough, i had a kernel panic and that was it. All of this from a normal user account. The bug has reoccured recently and may cause problems on my server if the users find out about the vulnerability. I am running FreeBSD 2.2.7-STABLE (Last compiled on August 5th early in the morning). The system is running on a PII233 with 64MB RAM. This bug REALLY needs to be fixed ASAP. I would like to know if other systes are vulnerable as well. I discussed this matter on IRC and everyone said they had similar problems. This bug needs to be addressed soon. I would HATE switching to linux because my system keeps crashing. --------------- Scott Swindells, SchematiX.NET --0-1205284948-902820663=:216 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="bsdbug.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="bsdbug.c" LyogY3Jhc2hic2QuYw0KKioNCioqIFRISVMgUFJPR1JBTSBDQVVTRVMgS0VS TkVMIFBBTklDIE9OIFNPTUUgU1lTVEVNUw0KKioNCioqIFVzYWdlOiBjcmFz aG1lIFstLWhhcmRlcl0NCioqDQoqKiAtLWhhcmRlciBvcHRpb24gY2F1c2Vz IHRoaXMgcHJvZ3JhbSB0byBsZWF2ZSBvcGVuZWQgZmlsZSBkZXNjcmlwdG9y cyBoYW5naW5nDQoqKiB0aHVzIGluY3JlYXNpbmcgdGhlIHByb2JhYmlsaXR5 IG9mIHRoZSBjcmFzaC4NCioqDQoqLw0KDQojaW5jbHVkZSA8c3RkaW8uaD4N CiNpbmNsdWRlIDxmY250bC5oPg0KI2luY2x1ZGUgPHVuaXN0ZC5oPg0KI2lu Y2x1ZGUgPGVycm5vLmg+DQojaW5jbHVkZSA8c3lzL3R5cGVzLmg+DQojaW5j bHVkZSA8c3lzL3VuLmg+DQojaW5jbHVkZSA8c3lzL3Vpby5oPg0KI2luY2x1 ZGUgPHN5cy9zb2NrZXQuaD4NCiNpbmNsdWRlIDxzeXMvd2FpdC5oPg0KDQpp bnQgbWFpbihpbnQgYXJnYyxjaGFyICoqYXJndikgew0KaW50IGhhcmRlcj0w LHAsbnByb2MsaCxpLHNvY2tldGZkc1syXTsNCmNoYXIgYVsxMF07DQpzdHJ1 Y3QgaW92ZWMgaW92MT17YSwxfTsNCnN0cnVjdCBjbXNnaGRyICpjbTsNCnN0 cnVjdCBtc2doZHIgbXNnOw0KY2hhciBiYnVmZmVyW3NpemVvZihzdHJ1Y3Qg Y21zZ2hkcikrc2l6ZW9mKGludCkqMjRdOw0KDQppZihhcmdjPj0yJiYhc3Ry Y21wKGFyZ3ZbMV0sIi0taGFyZGVyIikpIGhhcmRlcj0xOw0KDQpucHJvYz0t MTsNCmZvcihpPTA7aTwxMDA7aSsrKXsNCiBpZighKHA9Zm9yaygpKSl7DQog IGlmKHNvY2tldHBhaXIoQUZfVU5JWCxTT0NLX1NUUkVBTSwwLHNvY2tldGZk cykpew0KICAgcGVycm9yKCJzb2NrZXRwYWlyIik7DQogICB9ZWxzZXsNCiAg IGNtPShzdHJ1Y3QgY21zZ2hkciopYmJ1ZmZlcjsNCiAgIGNtLT5jbXNnX2xl dmVsPVNPTF9TT0NLRVQ7DQogICBjbS0+Y21zZ190eXBlPVNDTV9SSUdIVFM7 DQogICBjbS0+Y21zZ19sZW49c2l6ZW9mKHN0cnVjdCBjbXNnaGRyKStzaXpl b2YoaW50KTsNCiAgIG1zZy5tc2dfbmFtZT0oY2FkZHJfdCkwOw0KICAgbXNn Lm1zZ19uYW1lbGVuPTA7DQogICBtc2cubXNnX2ZsYWdzPTA7DQogICBtc2cu bXNnX2lvdj0maW92MTsNCiAgIG1zZy5tc2dfaW92bGVuPTE7DQogICBtc2cu bXNnX2NvbnRyb2w9KGNhZGRyX3QpY207DQogICBtc2cubXNnX2NvbnRyb2xs ZW49Y20tPmNtc2dfbGVuOw0KICAgaWYoZm9yaygpKXsNCiAgICBjbG9zZShz b2NrZXRmZHNbMF0pOw0KICAgICooaW50KikoYmJ1ZmZlcitzaXplb2Yoc3Ry dWN0IGNtc2doZHIpKT1vcGVuKCIvZGV2L251bGwiLE9fUkRPTkxZKTsNCiAg ICBmb3IoaT0wO2k8MjA0ODtpKyspew0KICAgICBmcHJpbnRmKHN0ZGVyciwi JWQ+ICIsaSsxKTsNCiAgICAgd2hpbGUoc2VuZG1zZyhzb2NrZXRmZHNbMV0s Jm1zZywwKSE9MSl7DQogICAgICBpZihlcnJubyE9RUFHQUlOKXsNCiAgICAg ICBwZXJyb3IoIlxuc2VuZG1zZyIpOw0KICAgICAgIH0NCiAgICAgIH0NCiAg ICAgfQ0KICAgIH1lbHNlew0KICAgIGNsb3NlKHNvY2tldGZkc1sxXSk7DQog ICAgZm9yKGk9MDtpPDIwNDg7aSsrKXsNCiAgICAgKihpbnQqKShiYnVmZmVy K3NpemVvZihzdHJ1Y3QgY21zZ2hkcikpPS0xOw0KICAgICBmcHJpbnRmKHN0 ZGVyciwiPiVkICIsaSsxKTsNCiAgICAgY209KHN0cnVjdCBjbXNnaGRyKili YnVmZmVyOw0KICAgICBjbS0+Y21zZ19sZXZlbD1TT0xfU09DS0VUOw0KICAg ICBjbS0+Y21zZ190eXBlPVNDTV9SSUdIVFM7DQogICAgIGNtLT5jbXNnX2xl bj1zaXplb2Yoc3RydWN0IGNtc2doZHIpK3NpemVvZihpbnQpKjI0Ow0KICAg ICBtc2cubXNnX25hbWU9KGNhZGRyX3QpMDsNCiAgICAgbXNnLm1zZ19uYW1l bGVuPTA7DQogICAgIGlvdjEuaW92X2xlbj0xMDsNCiAgICAgbXNnLm1zZ19p b3Y9JmlvdjE7DQogICAgIG1zZy5tc2dfaW92bGVuPTE7DQogICAgIG1zZy5t c2dfY29udHJvbD0oY2FkZHJfdCljbTsNCiAgICAgbXNnLm1zZ19jb250cm9s bGVuPWNtLT5jbXNnX2xlbjsNCg0KICAgICBpZihyZWN2bXNnKHNvY2tldGZk c1swXSwmbXNnLDApIT0xKXsNCiAgICAgIHBlcnJvcigiXG5yZWN2bXNnIik7 DQogICAgICB9ZWxzZXsNCiAgICAgIGZwcmludGYoc3RkZXJyLCIoJWQpICIs KihpbnQqKShiYnVmZmVyK3NpemVvZihzdHJ1Y3QgY21zZ2hkcikpKTsNCiAg ICAgIGlmKCFoYXJkZXIpew0KICAgICAgIGNsb3NlKCooaW50KikoYmJ1ZmZl citzaXplb2Yoc3RydWN0IGNtc2doZHIpKSk7DQogICAgICAgfQ0KICAgICAg fQ0KICAgICB9DQogICAgZXhpdCgwKTsNCiAgICB9DQogICB3YWl0KCZoKTsN CiAgIH0NCiAgZXhpdCgwKTsNCiAgfWVsc2V7DQogIGlmKHA8MCl7DQogICBu cHJvYz1pOw0KICAgaT0xMDA7DQogICB9DQogIH0NCiB9DQppZihucHJvYzww KSBucHJvYz0xMDA7DQpmb3IoaT0wO2k8bnByb2M7aSsrKSB3YWl0KCZoKTsN CmZwcmludGYoc3RkZXJyLCJcbiVkIHByb2Nlc3NlcyBmaW5pc2hlZFxuIixu cHJvYyk7DQpyZXR1cm4gMDsNCn0NCg== --0-1205284948-902820663=:216-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 00:46:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22518 for freebsd-stable-outgoing; Tue, 11 Aug 1998 00:46:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles197.castles.com [208.214.165.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22386 for ; Tue, 11 Aug 1998 00:45:58 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id AAA00271; Tue, 11 Aug 1998 00:39:17 -0700 (PDT) Message-Id: <199808110739.AAA00271@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nate Williams cc: Mike Smith , Drew Derbyshire , stable@FreeBSD.ORG Subject: Re: zp0 not receiving under 2.2.7? In-reply-to: Your message of "Mon, 10 Aug 1998 22:24:12 MDT." <199808110424.WAA04178@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Aug 1998 00:39:13 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Hmmm. One more try, change the "?" to the explicit IRQ I want ... WHAMMO, > > > ep0 works. Well, *was* "?" legal? > > > > It's not so much whether it's legal as whether it works. I don't like > > ? because the smarts behind the auto-IRQ allocation aren't good. We > > don't do enough PnP by far for it to be reliable. > > However, they're do a better job of guessing an available IRQ than most > users. :) :) :) > > (I'm being both serious and attempting to be funny at the same time...) 8) One of the contributing factors is that people expect laptops to somehow be simpler and more "integrated" than desktop systems. (Everyone who has worked on laptops laughs; the gallery looks puzzled...) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 00:55:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23285 for freebsd-stable-outgoing; Tue, 11 Aug 1998 00:55:37 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA23265 for ; Tue, 11 Aug 1998 00:55:33 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z69Gw-00043u-00; Tue, 11 Aug 1998 01:55:10 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id BAA27200; Tue, 11 Aug 1998 01:56:26 -0600 (MDT) Message-Id: <199808110756.BAA27200@harmony.village.org> To: Scott Subject: Re: Huge Bug in FreeBSD not fixed? Cc: FreeBSD-stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Aug 1998 00:31:03 PDT." References: Date: Tue, 11 Aug 1998 01:56:25 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Scott writes: : I ran across this bug a while back on rootshell, and then again by a user : on IRC who offered to take down my box. Soon after that, the bug was fixed : and things were fine. But just out of boredom, i decided to run the : exploit again. Sure enough, i had a kernel panic and that was it. All of : this from a normal user account. The bug has reoccured recently and may : cause problems on my server if the users find out about the vulnerability. This program won't even compile for me :-(. However, fixing the obvious bugs, I was able to run it 20 times in a row w/o any problems that I could detect. This was on my -current system.... That will give you an alternative to running Linux. Can you enable ddb and/or crash dumps to find out where things are crashing? What are the messages that you getting? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 00:56:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23447 for freebsd-stable-outgoing; Tue, 11 Aug 1998 00:56:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA23429 for ; Tue, 11 Aug 1998 00:56:20 -0700 (PDT) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id HGSXZTZJ; Tue, 11 Aug 98 07:55:47 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19980811095340.0092e900@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 11 Aug 1998 09:53:40 +0200 To: Scott From: Marius Bendiksen Subject: Re: Huge Bug in FreeBSD not fixed? Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I would like to know if other systes are vulnerable as well. I discussed >this matter on IRC and everyone said they had similar problems. This bug >needs to be addressed soon. I would HATE switching to linux because my >system keeps crashing. I experienced the same thing, with someone on IRC threatening to take down my box. Of course, I laughed at him, but then my box went down. He also said he was going to attack freefall, and that would _certainly_ be bad news. He was running Linux, as I recall. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 01:05:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24789 for freebsd-stable-outgoing; Tue, 11 Aug 1998 01:05:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles197.castles.com [208.214.165.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24780 for ; Tue, 11 Aug 1998 01:05:04 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id BAA00532; Tue, 11 Aug 1998 01:03:24 -0700 (PDT) Message-Id: <199808110803.BAA00532@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Marius Bendiksen cc: Scott , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-reply-to: Your message of "Tue, 11 Aug 1998 09:53:40 +0200." <3.0.5.32.19980811095340.0092e900@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Aug 1998 01:03:24 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I would like to know if other systes are vulnerable as well. I discussed > >this matter on IRC and everyone said they had similar problems. This bug > >needs to be addressed soon. I would HATE switching to linux because my > >system keeps crashing. > > I experienced the same thing, with someone on IRC threatening to take down > my box. Of course, I laughed at him, but then my box went down. He also > said he was going to attack freefall, and that would _certainly_ be bad > news. He was running Linux, as I recall. freefall.freebsd.org:~>uptime 1:00AM up 12 days, 9:14, 9 users, load averages: 0.16, 0.19, 0.18 hub.freebsd.org:~>uptime 1:01AM up 12 days, 6:52, 5 users, load averages: 0.37, 0.23, 0.13 ftp.freebsd.org:~>uptime 1:02AM up 7 days, 22:39, 7 users, load averages: 62.89, 52.34, 46.41 Someone's talkin' loud, but ain't saying nothin. >From your point of view; I would suspect that you're just not playing safe enough. Check all your small servers are off, and that you're protected from massive DOS attacks. Likewise make sure you're up to date, and that you haven't been compromised. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 01:35:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28697 for freebsd-stable-outgoing; Tue, 11 Aug 1998 01:35:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28692 for ; Tue, 11 Aug 1998 01:35:31 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id BAA00309; Tue, 11 Aug 1998 01:32:55 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Marius Bendiksen cc: Scott , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-reply-to: Your message of "Tue, 11 Aug 1998 09:53:40 +0200." <3.0.5.32.19980811095340.0092e900@mail.scancall.no> Date: Tue, 11 Aug 1998 01:32:55 -0700 Message-ID: <305.902824375@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I experienced the same thing, with someone on IRC threatening to take down > my box. Of course, I laughed at him, but then my box went down. He also > said he was going to attack freefall, and that would _certainly_ be bad > news. He was running Linux, as I recall. I ran this thing 20 times, with and without the -harder option, and it did absolutely nothing to my box. Just goes to show, these things generally constitute fairly apocryphal evidence without a lot more details. Also, just for the record, people have attacked freefall many times. Just because someone said he was going to nuke you one day and it worked (and I have no idea how seriously well-maintained your systems are from a security fascist's perspective) is by no means an indication that it works every time or in every circumstance. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 01:47:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00720 for freebsd-stable-outgoing; Tue, 11 Aug 1998 01:47:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mh2.cts.com (mh2.cts.com [209.68.192.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00714 for ; Tue, 11 Aug 1998 01:47:29 -0700 (PDT) (envelope-from mdavis@io.cts.com) Received: from io.cts.com (io.cts.com [198.68.174.34]) by mh2.cts.com (8.8.7/8.8.5) with ESMTP id BAA05628 for ; Tue, 11 Aug 1998 01:47:07 -0700 (PDT) Received: (from mdavis@localhost) by io.cts.com (8.8.8/8.8.8) id BAA02282 for stable@freebsd.org; Tue, 11 Aug 1998 01:47:06 -0700 (PDT) (envelope-from mdavis) From: Morgan Davis Message-Id: <199808110847.BAA02282@io.cts.com> Subject: FP exception in df To: stable@FreeBSD.ORG Date: Tue, 11 Aug 1998 01:47:06 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed that swapinfo returns what looks exactly like a df entry but for the swap device. Seeing as how this might be useful to aggregate that information with one df command, I thought I'd add the swap device to df's argument list. But this gives: # df /dev/sd0s1b Filesystem 1K-blocks Used Avail Capacity Mounted on Floating point exception Using the -t option doesn't seem to allow for an fstype of "swap". Of course, the work around is to get the desired result is: df; swapinfo | tail -1 which lines up everything nice and neat. Just seems that df should (or might) be able to do this itself (or at least not throw an FP exception). --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 02:02:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03404 for freebsd-stable-outgoing; Tue, 11 Aug 1998 02:02:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sussie.datadesign.se (ns.datadesign.se [194.23.109.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03375 for ; Tue, 11 Aug 1998 02:02:17 -0700 (PDT) (envelope-from kaj@interbizz.se) Received: from localhost (sussie.datadesign.se [194.23.109.130]) by sussie.datadesign.se (8.8.5/8.8.7) with ESMTP id LAA13110; Tue, 11 Aug 1998 11:01:32 +0200 (MET DST) To: obrien@NUXI.com Cc: tom@uniserve.com, freebsd-stable@FreeBSD.ORG Cc: kaj@interbizz.se Subject: Re: 2.2.7 crash From: Rasmus Kaj In-Reply-To: Your message of "Mon, 10 Aug 1998 20:27:58 -0700" <19980810202758.A29238@nuxi.com> References: <19980810202758.A29238@nuxi.com> X-Mailer: Mew version 1.92.4 on XEmacs 20.4 (Emerald) X-URL: http://www.e.kth.se/~kaj/ X-Phone: +46 (0)8 - 692 35 09 / +46 (0)70 640 49 14 X-Attribution: Kaj X-Face: M9cR~WYav<"fu%MaslX0`43PAYY?uIsM8[#E(0\Xuy9rj>4gE\h3jm.7DD?]R8*^7T\o&vT U@[53Dwkuup4[0@gw#~kyu>`unH?kVj9CJa02(h>Ki\+i=%rn%sDf^KC.!?IHkKjMAbkd\jgmphp^' d|Q;OeXEAhq?ybGqOs1CHb6TJT42'C`Krnk61//AOfXtNjj/t'`5>Vw0QX!dKfOL$.f+S"LIuwR<;I Z0Qnnx(F^F]o@*V%TUtEV'1Z[TkOl^FFV9Z~A[b19%}uP*,huCU Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980811110131U.kaj@interbizz.se> Date: Tue, 11 Aug 1998 11:01:31 +0200 X-Dispatcher: imput version 971024 Lines: 22 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "DO" == David O'Brien writes: >> > What's the next step to figuring out this problem? >> >> What you are seeing is almost certainly a hardware failure. DO> Would memory just start going bad? This machine has been stable DO> running the 2.2-STABLE branch for over a year not. Hardware goes bad quite randomly ... I recently had a few crashes during tough load (make buildworld + other simultaneous compilations). It turned out my CPU fan had stopped spinning. The only crash I _ever_ experienced on FreeBSD before that was due to interference between the power chord and my foot. :-) // Rasmus -- kaj@cityonline.se --------------- Rasmus Kaj - http://www.e.kth.se/~kaj/ \ CityOnLine IB Production AB - http://www.CityOnLine.se/ \------------------- The more things change, the more they stay insane To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 02:05:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03896 for freebsd-stable-outgoing; Tue, 11 Aug 1998 02:05:17 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from SchematiX.net (schematix.net [24.234.31.158]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03878 for ; Tue, 11 Aug 1998 02:05:12 -0700 (PDT) (envelope-from scott@SchematiX.net) Received: from localhost (scott@localhost) by SchematiX.net (8.8.8/8.8.8) with SMTP id CAA00690; Tue, 11 Aug 1998 02:03:11 -0700 (PDT) (envelope-from scott@SchematiX.net) Date: Tue, 11 Aug 1998 02:03:10 -0700 (PDT) From: Scott To: "Jordan K. Hubbard" cc: Marius Bendiksen , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: <305.902824375@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Which version of FreeBSD were you running? As i mentioned, a previous compile didn't have the problems, but it seems to have resurfaced (for me at least). This isn't a remote exploit my any means. One must have an account then run the exploit. I should have dumps from the crashes. Maybe limiting user processes would take care of this problem? On Tue, 11 Aug 1998, Jordan K. Hubbard wrote: > > I experienced the same thing, with someone on IRC threatening to take down > > my box. Of course, I laughed at him, but then my box went down. He also > > said he was going to attack freefall, and that would _certainly_ be bad > > news. He was running Linux, as I recall. > > I ran this thing 20 times, with and without the -harder option, and it > did absolutely nothing to my box. Just goes to show, these things > generally constitute fairly apocryphal evidence without a lot more > details. Also, just for the record, people have attacked freefall > many times. Just because someone said he was going to nuke you one > day and it worked (and I have no idea how seriously well-maintained > your systems are from a security fascist's perspective) is by no means > an indication that it works every time or in every circumstance. :-) > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 02:18:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05318 for freebsd-stable-outgoing; Tue, 11 Aug 1998 02:18:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05308 for ; Tue, 11 Aug 1998 02:18:40 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA01826; Tue, 11 Aug 1998 02:18:49 -0700 (PDT) Message-Id: <199808110918.CAA01826@implode.root.com> To: Morgan Davis cc: stable@FreeBSD.ORG Subject: Re: FP exception in df In-reply-to: Your message of "Tue, 11 Aug 1998 01:47:06 PDT." <199808110847.BAA02282@io.cts.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 11 Aug 1998 02:18:48 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I noticed that swapinfo returns what looks exactly like a df entry but >for the swap device. Seeing as how this might be useful to aggregate >that information with one df command, I thought I'd add the swap >device to df's argument list. But this gives: > ># df /dev/sd0s1b >Filesystem 1K-blocks Used Avail Capacity Mounted on >Floating point exception > >Using the -t option doesn't seem to allow for an fstype of "swap". > >Of course, the work around is to get the desired result is: > > df; swapinfo | tail -1 > >which lines up everything nice and neat. Just seems that df should >(or might) be able to do this itself (or at least not throw an FP >exception). The information is displayed similarly, but the way that the system gets the info is entirely different - "swap" in FreeBSD isn't a filesystem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 02:46:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07543 for freebsd-stable-outgoing; Tue, 11 Aug 1998 02:46:10 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from odyssey.apana.org.au (odyssey.apana.org.au [203.11.114.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07538 for ; Tue, 11 Aug 1998 02:46:07 -0700 (PDT) (envelope-from dean@odyssey.apana.org.au) Received: from localhost (dean@localhost) by odyssey.apana.org.au (8.8.8/8.8.8) with SMTP id RAA14832; Tue, 11 Aug 1998 17:45:16 +0800 (WST) (envelope-from dean@odyssey.apana.org.au) Date: Tue, 11 Aug 1998 17:45:16 +0800 (WST) From: Dean Hollister To: "Jordan K. Hubbard" cc: Marius Bendiksen , Scott , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: <305.902824375@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Aug 1998, Jordan K. Hubbard wrote: > I ran this thing 20 times, with and without the -harder option, and it > did absolutely nothing to my box. Just goes to show, these things > generally constitute fairly apocryphal evidence without a lot more > details. Also, just for the record, people have attacked freefall > many times. Just because someone said he was going to nuke you one > day and it worked (and I have no idea how seriously well-maintained > your systems are from a security fascist's perspective) is by no means > an indication that it works every time or in every circumstance. :-) I did the same on odyssey, running 2.2.7-STABLE and make build/installworld done 7 days ago. On all executions, lots of scrolling text... ...no kernel panicks. Then again, these sorts of hoaxes can be entertaining. ;-) Regards, d. +-------------------------------------------------------+ | Dean Hollister, | dean@mushka.ml.org | | Perth, Western Australia. | dean@wa.apana.org.au | +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 04:35:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17697 for freebsd-stable-outgoing; Tue, 11 Aug 1998 04:35:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17662 for ; Tue, 11 Aug 1998 04:35:17 -0700 (PDT) (envelope-from tg@ghpc8.ihf.rwth-aachen.de) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.8/8.8.6) with ESMTP id NAA19376; Tue, 11 Aug 1998 13:33:58 +0200 (CEST) Received: (from tg@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.8/8.8.5) id NAA15761; Tue, 11 Aug 1998 13:33:56 +0200 (CEST) To: "Jordan K. Hubbard" Cc: Marius Bendiksen , Scott , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? References: <305.902824375@time.cdrom.com> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Thomas Gellekum Date: 11 Aug 1998 13:33:56 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of "Tue, 11 Aug 1998 01:32:55 -0700" Message-ID: <87yasvsqfv.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 86 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > > I experienced the same thing, with someone on IRC threatening to take down > > my box. Of course, I laughed at him, but then my box went down. He also > > said he was going to attack freefall, and that would _certainly_ be bad > > news. He was running Linux, as I recall. > > I ran this thing 20 times, with and without the -harder option, and it > did absolutely nothing to my box. Just goes to show, these things I have run this program five times and it finished once. The other four occasions I got Fatal trap 12: page fault while in kernel mode fault virtual address = 0x18 fault code = supervisor write, page ot present instruction pointer = 0x8:0xf0126d21 stack pointer = 0x10:0xefbffe50 frame pointer = 0x10:0xefbffe74 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 = 395 (crashbsd) interrupt mask = kernel: type 12 trap, code=0 Stopped at _sosend+0x391: movl $0, 0x18(%ebx) After saving the core dump and recompiling a few object files with -g: Script started on Tue Aug 11 13:19:09 1998 p0:tibatong:TIBATONG 26# gdb -k GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc. (kgdb) symbol-file kernel Reading symbols from kernel...done. (kgdb) exec-file /tmp/kernel.0 (kgdb) core-file /tmp/vmcore.0 IdlePTD 236000 current pcb at 1f762c panic: from debugger #0 0xf0112447 in boot () (kgdb) where #0 0xf0112447 in boot () #1 0xf0112733 in panic () #2 0xf0101475 in db_panic () #3 0xf0101365 in db_command () #4 0xf01014e2 in db_command_loop () #5 0xf0103c38 in db_trap () #6 0xf01b6dab in kdb_trap () #7 0xf01c12db in trap_fatal (frame=0xefbffe14) at ../../i386/i386/trap.c:768 #8 0xf01c0dac in trap_pfault (frame=0xefbffe14, usermode=0) at ../../i386/i386/trap.c:681 #9 0xf01c0a37 in trap (frame={tf_es = -2147483632, tf_ds = -272695280, tf_edi = -272630136, tf_esi = -2147483648, tf_ebp = -272630156, tf_isp = -272630212, tf_ebx = 0, tf_edx = 2147483647, tf_ecx = -1073277766, tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -267227871, tf_cs = 8, tf_eflags = 66198, tf_esp = 0, tf_ss = 1}) at ../../i386/i386/trap.c:324 #10 0xf0126d21 in sosend (so=0xf0937f00, addr=0x0, uio=0xefbffeb0, top=0x0, control=0xf06fff00, flags=0) at ../../kern/uipc_socket.c:432 #11 0xf0129a91 in sendit (p=0xf0921800, s=4, mp=0xefbfff38, flags=0, retsize=0xefbfff84) at ../../kern/uipc_syscalls.c:488 #12 0xf0129d20 in sendmsg (p=0xf0921800, uap=0xefbfff94, retval=0xefbfff84) at ../../kern/uipc_syscalls.c:640 #13 0xf01c1593 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272639748, tf_esi = -1, tf_ebp = -272639708, tf_isp = -272629788, tf_ebx = 163, ---Type to continue, or q to quit--- tf_edx = -272640728, tf_ecx = -272641804, tf_eax = 28, tf_trapno = 12, tf_err = 7, tf_eip = 537128897, tf_cs = 31, tf_eflags = 646, tf_esp = -272639908, tf_ss = 39}) at ../../i386/i386/trap.c:920 #14 0x2003efc1 in ?? () #15 0x1095 in ?? () (kgdb) q p0:tibatong:TIBATONG 27# exit Script done on Tue Aug 11 13:20:11 1998 Once, the system had the chance to send a log message: Aug 11 13:03:10 tibatong /kernel: Out of mbuf clusters - increase maxusers! Anything else I can do? tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 04:46:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18910 for freebsd-stable-outgoing; Tue, 11 Aug 1998 04:46:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA18905 for ; Tue, 11 Aug 1998 04:46:27 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA03859; Tue, 11 Aug 1998 04:44:57 -0700 (PDT) Message-Id: <199808111144.EAA03859@implode.root.com> To: Thomas Gellekum cc: "Jordan K. Hubbard" , Marius Bendiksen , Scott , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-reply-to: Your message of "11 Aug 1998 13:33:56 +0200." <87yasvsqfv.fsf@ghpc6.ihf.rwth-aachen.de> From: David Greenman Reply-To: dg@root.com Date: Tue, 11 Aug 1998 04:44:57 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Once, the system had the chance to send a log message: > >Aug 11 13:03:10 tibatong /kernel: Out of mbuf clusters - increase maxusers! > >Anything else I can do? What the system really wants is more mbuf clusters (NMBCLUSTERS kernel option). I suspect the difference between systems that crash with the program and those that don't is in how they are configured. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 04:48:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19163 for freebsd-stable-outgoing; Tue, 11 Aug 1998 04:48:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from stcgate.statcan.ca (stcgate.statcan.ca [142.206.192.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19150 for ; Tue, 11 Aug 1998 04:48:49 -0700 (PDT) (envelope-from jeays@statcan.ca) Received: from stcinet (stcinet.statcan.ca [142.206.128.146]) by stcgate.statcan.ca (8.9.1/8.6.9) with SMTP id HAA18279; Tue, 11 Aug 1998 07:53:40 -0400 (EDT) Received: from statcan.ca by statcan.ca (SMI-8.6/SMI-SVR4) id HAA20967; Tue, 11 Aug 1998 07:51:46 -0400; sender jeays@statcan.ca Date: Tue, 11 Aug 1998 07:47:46 -0400 (EDT) From: Mike Jeays X-Sender: jeays@austral To: Scott cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a 'me too'. This program crashed my Pentium 120 (48MB) each time I ran it from within an X-term, but not when I ran it from another TTY. In the latter case it reported '38 processes' or '47 processes' terminated normally. It was a hard crash - the cursor froze for a few moments, then the screen went black and the machine rebooted. The first time it crashed, fsck produced a number of 'salvaging...' messages; the second time, it just had to reset the clean flag in the superblock, on each of my filesystems. Version is 2.2.7, as installed from the CheapBytes CD. Jordan - maybe this should not be dismissed too quickly? On Tue, 11 Aug 1998, Scott wrote: > I ran across this bug a while back on rootshell, and then again by a user > on IRC who offered to take down my box. Soon after that, the bug was fixed > and things were fine. But just out of boredom, i decided to run the > exploit again. Sure enough, i had a kernel panic and that was it. All of > this from a normal user account. The bug has reoccured recently and may > cause problems on my server if the users find out about the vulnerability. > > I am running FreeBSD 2.2.7-STABLE (Last compiled on August 5th early in > the morning). The system is running on a PII233 with 64MB RAM. This bug > REALLY needs to be fixed ASAP. > > I would like to know if other systes are vulnerable as well. I discussed > this matter on IRC and everyone said they had similar problems. This bug > needs to be addressed soon. I would HATE switching to linux because my > system keeps crashing. > > > --------------- > Scott Swindells, SchematiX.NET > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 06:47:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01928 for freebsd-stable-outgoing; Tue, 11 Aug 1998 06:47:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.craxx.com (craxx.com [195.108.198.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01921 for ; Tue, 11 Aug 1998 06:47:22 -0700 (PDT) (envelope-from lva@dds.nl) Received: from uptight (classless.student.utwente.nl [130.89.230.96]) by mail.craxx.com (8.9.1/8.9.1) with SMTP id PAA05395 for ; Tue, 11 Aug 1998 15:46:56 +0200 From: "laurens van alphen" To: Subject: RE: Huge Bug in FreeBSD not fixed? Date: Tue, 11 Aug 1998 15:46:54 +0200 Message-ID: <000101bdc52e$7ff4f790$0a00a8c0@uptight.student.utwente.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My 2c, My server is running 2.2.7-STABLE (kernel compiled just now, other stuff is from 2.2.7-RELEASE). First I tried running the bsdbug program under a normal user account. Alot of scrolling text and nothing happened. I then redirected the stderr to /dev/null (./bsdbug 2>/dev/null) since the slow terminal i was using couldn't keep up. On another terminal I saw around 75 processes. I figured the default resource limits in /etc/login.conf prevent the server from crashing. So after removing those (or running the program as root) the number of process shot up and the server crashed: the console where top was running got mangled and the thing rebooted. This wasn't even --harder. Get it fixed plz, -- laurens van alphen craxx e-consultants alphen@craxx.com http://craxx.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 08:55:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24853 for freebsd-stable-outgoing; Tue, 11 Aug 1998 08:55:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24816 for ; Tue, 11 Aug 1998 08:55:48 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id RAA00468; Tue, 11 Aug 1998 17:54:51 +0200 (CEST) Received: from localhost (blaz@localhost) by gold.amis.net (8.8.8/8.8.8) with SMTP id RAA02313; Tue, 11 Aug 1998 17:53:49 +0200 (CEST) Date: Tue, 11 Aug 1998 17:53:49 +0200 (CEST) From: Blaz Zupan To: Scott cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am running FreeBSD 2.2.7-STABLE (Last compiled on August 5th early in > the morning). The system is running on a PII233 with 64MB RAM. This bug > REALLY needs to be fixed ASAP. I ran the attached program on my box, it printed a big bunch of numbers and then finished with: 27 processes finished I'm writing this mail on the same machine, without any panic or reboot. Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 10:57:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08848 for freebsd-stable-outgoing; Tue, 11 Aug 1998 10:57:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08840 for ; Tue, 11 Aug 1998 10:56:58 -0700 (PDT) (envelope-from stb@freebsd.org) Received: from d254.promo.de (d254.Promo.DE [194.45.188.254]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id TAA13192; Tue, 11 Aug 1998 19:52:29 +0200 (CEST) Date: Tue, 11 Aug 1998 19:54:49 +0200 From: Stefan Bethke To: Thomas Gellekum , "Jordan K. Hubbard" cc: freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? Message-ID: <1682190.3111854089@d254.promo.de> In-Reply-To: <87yasvsqfv.fsf@ghpc6.ihf.rwth-aachen.de> Originator-Info: login-token=Mulberry:01QcdaV7Q7v73gNoD93fDe X-Mailer: Mulberry Demo (MacOS) [1.4.0a8, s/n Evaluation] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Die, 11. Aug 1998 13:33 Uhr +0200 Thomas Gellekum wrote: > I have run this program five times and it finished once. The other > four occasions I got > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x18 > fault code = supervisor write, page ot present > instruction pointer = 0x8:0xf0126d21 > stack pointer = 0x10:0xefbffe50 > frame pointer = 0x10:0xefbffe74 > 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 = 395 (crashbsd) > interrupt mask = > kernel: type 12 trap, code=0 > Stopped at _sosend+0x391: movl $0, 0x18(%ebx) > > After saving the core dump and recompiling a few object files with -g: > #9 0xf01c0a37 in trap (frame={tf_es = -2147483632, tf_ds = -272695280, > tf_edi = -272630136, tf_esi = -2147483648, tf_ebp = -272630156, > tf_isp = -272630212, tf_ebx = 0, tf_edx = 2147483647, > tf_ecx = -1073277766, tf_eax = 0, tf_trapno = 12, tf_err = 2, > tf_eip = -267227871, tf_cs = 8, tf_eflags = 66198, tf_esp = 0, > tf_ss = 1}) at ../../i386/i386/trap.c:324 > #10 0xf0126d21 in sosend (so=0xf0937f00, addr=0x0, uio=0xefbffeb0, > top=0x0, control=0xf06fff00, flags=0) at ../../kern/uipc_socket.c:432 Looking at kern/uipc_socket.c:sosend(), one can easily spot the problem (which IIRC even Stevens mentions?) sosend() uses MGETHDR() to get a fresh mbuf, and expect it to always succeed. Looking through MGETHDR (in sys/mbuf.h) and m_mballoc() and m_retryhdr() (in kern/uipc_mbuf.c), the following can happen: The free list mmbfree is empty. MGETHDR calls m_mballoc, which in turn calls kmem_malloc(). kmem_malloc() fails because the map mb_map is full (this is where the message is logged), and returns NULL. MGETHDR then calls m_retryhdr(). m_retryhdr() tries to get mbufs from the protocols by calling m_reclaim(). If no mbufs can be recovered this way, m_retry() returns NULL. Because sosend() expects a MGET(m, M_WAIT, MT_DATA) to always succeed, it pagefaults while trying to manipulate the non-allocated mbuf (m->m_pkthdr.len at 0+0x18). As a relief you can try to increase the number of mbufs; however, this will only make the case less likely to occur. The solution would be either to make MGET() and MGETHRD() to always succeed (or sleep indefinitly), or check the result of any of those calls (as many callers already do). This in both -stable and -current. A patch might be trivial for someone who understands sosend() fully; I currently don't :-( > Anything else I can do? Fix the bug :-) ? Stefan -- Hamburg | Voice: +49-177-3504009 Germany | e-mail: stb@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 11:43:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15041 for freebsd-stable-outgoing; Tue, 11 Aug 1998 11:43:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from SchematiX.net (schematix.net [24.234.31.158]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15031 for ; Tue, 11 Aug 1998 11:43:54 -0700 (PDT) (envelope-from scott@SchematiX.net) Received: from localhost (scott@localhost) by SchematiX.net (8.8.8/8.8.8) with SMTP id LAA01849; Tue, 11 Aug 1998 11:41:39 -0700 (PDT) (envelope-from scott@SchematiX.net) Date: Tue, 11 Aug 1998 11:41:39 -0700 (PDT) From: Scott To: Dean Hollister cc: "Jordan K. Hubbard" , Marius Bendiksen , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Aug 1998, Dean Hollister wrote: > On Tue, 11 Aug 1998, Jordan K. Hubbard wrote: > > > I ran this thing 20 times, with and without the -harder option, and it > > did absolutely nothing to my box. Just goes to show, these things > > generally constitute fairly apocryphal evidence without a lot more > > details. Also, just for the record, people have attacked freefall > > many times. Just because someone said he was going to nuke you one > > day and it worked (and I have no idea how seriously well-maintained > > your systems are from a security fascist's perspective) is by no means > > an indication that it works every time or in every circumstance. :-) > > I did the same on odyssey, running 2.2.7-STABLE and make > build/installworld done 7 days ago. > > On all executions, lots of scrolling text... > > ...no kernel panicks. > > Then again, these sorts of hoaxes can be entertaining. ;-) Well its not a hoax by any means. I ran the program, it took down my machine and that was it. I ran the exploit 3 times to make sure. I also had someone else run it, and their machine crashed. > > Regards, > > d. > > +-------------------------------------------------------+ > | Dean Hollister, | dean@mushka.ml.org | > | Perth, Western Australia. | dean@wa.apana.org.au | > +-------------------------------------------------------+ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 11:44:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15250 for freebsd-stable-outgoing; Tue, 11 Aug 1998 11:44:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15223 for ; Tue, 11 Aug 1998 11:44:19 -0700 (PDT) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.1/8.6.10) id LAA03484; Tue, 11 Aug 1998 11:43:06 -0700 (PDT) Message-Id: <199808111843.LAA03484@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdbk3475; Tue Aug 11 11:42:41 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: Blaz Zupan cc: Scott , FreeBSD-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-reply-to: Your message of "Tue, 11 Aug 1998 17:53:49 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Aug 1998 11:42:41 -0700 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC > > I am running FreeBSD 2.2.7-STABLE (Last compiled on August 5th early in > > the morning). The system is running on a PII233 with 64MB RAM. This bug > > REALLY needs to be fixed ASAP. > > I ran the attached program on my box, it printed a big bunch of numbers > and then finished with: > > 27 processes finished > > I'm writing this mail on the same machine, without any panic or reboot. I ran two tests. The first test had the following limits set (bash ulimit -a output) and panicked the system. core file size (blocks) 0 data seg size (kbytes) 22528 file size (blocks) unlimited max locked memory (kbytes) 10240 max memory size (kbytes) 30720 open files 128 pipe size (512 bytes) 1 stack size (kbytes) 8192 cpu time (seconds) unlimited max user processes 128 virtual memory (kbytes) 30720 The second test I used the following: max user processes 32 It exploit application printed "30 processes finished". I am running a 2.2.6-STABLE (980617) system with CAM SCSI patches. I have maxusers set to 10. Following is what I consider relevant sysctl output. kern.maxproc: 180 kern.maxprocperuid: 179 This system is used as my desktop X station, which explains the goofy maxprocperuid value. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 12:33:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21903 for freebsd-stable-outgoing; Tue, 11 Aug 1998 12:33:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from NIH2WAAE (smtp5.site1.csi.com [149.174.183.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21883 for ; Tue, 11 Aug 1998 12:33:39 -0700 (PDT) (envelope-from berend@pobox.com) Received: from mail pickup service by csi.com with Microsoft SMTPSVC; Tue, 11 Aug 1998 15:33:14 -0400 Received: from auke.deboer (pd14-207.par.compuserve.com [195.232.78.207]) by hil-img-ims-2.compuserve.com (8.8.6/8.8.6/IMS-1.4) with ESMTP id PAA25630 for ; Tue, 11 Aug 1998 15:32:04 -0400 (EDT) Received: from bmach (bmach.deboer [192.168.33.3]) by auke.deboer (8.8.8/8.8.7) with SMTP id VAA28116 for ; Tue, 11 Aug 1998 21:29:20 +0200 (CEST) (envelope-from berend@pobox.com) Received: by localhost with Microsoft MAPI; Tue, 11 Aug 1998 21:29:14 +0200 Message-ID: <01BDC56F.163B51F0.berend@pobox.com> From: Berend de Boer To: "FreeBSD-stable@FreeBSD.ORG" Subject: Change in pw: should be root Date: Tue, 11 Aug 1998 21:29:11 +0200 Organization: NederWare X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hai All, I noticed that pw has changed its behaviour. You need to be root now, even if you only query things. Why is this? Why can't root access not be checked when actually changing things? Groetjes, Berend. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 13:09:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26660 for freebsd-stable-outgoing; Tue, 11 Aug 1998 13:09:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA26647; Tue, 11 Aug 1998 13:09:35 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z6Khu-0006Ft-00; Tue, 11 Aug 1998 13:07:46 -0700 Date: Tue, 11 Aug 1998 13:07:44 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Stefan Bethke cc: Thomas Gellekum , "Jordan K. Hubbard" , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: <1682190.3111854089@d254.promo.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Aug 1998, Stefan Bethke wrote: ... > As a relief you can try to increase the number of mbufs; however, this will > only make the case less likely to occur. ... Actually, if you limit the number of processes per user, you can almost completely prevent it from happening (at least for regular users anyhow). Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 13:10:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26885 for freebsd-stable-outgoing; Tue, 11 Aug 1998 13:10:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA26879 for ; Tue, 11 Aug 1998 13:10:39 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z6Kjs-0006Sc-00; Tue, 11 Aug 1998 13:09:48 -0700 Date: Tue, 11 Aug 1998 13:09:46 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Marius Bendiksen cc: Scott , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: <3.0.5.32.19980811095340.0092e900@mail.scancall.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Aug 1998, Marius Bendiksen wrote: > >I would like to know if other systes are vulnerable as well. I discussed > >this matter on IRC and everyone said they had similar problems. This bug > >needs to be addressed soon. I would HATE switching to linux because my > >system keeps crashing. > > I experienced the same thing, with someone on IRC threatening to take down > my box. Of course, I laughed at him, but then my box went down. He also This bug requires shell access to your box to be exploited. > said he was going to attack freefall, and that would _certainly_ be bad > news. He was running Linux, as I recall. Not without shell access to freefall, which only the developers have. > --- > Marius Bendiksen, IT-Trainee, ScanCall AS Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 13:12:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27117 for freebsd-stable-outgoing; Tue, 11 Aug 1998 13:12:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA27100 for ; Tue, 11 Aug 1998 13:12:10 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z6Klk-0006do-00; Tue, 11 Aug 1998 13:11:44 -0700 Date: Tue, 11 Aug 1998 13:11:42 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Scott cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-615793131-902866302=:22030" Content-ID: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-615793131-902866302=:22030 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: On Tue, 11 Aug 1998, Scott wrote: ... > this matter on IRC and everyone said they had similar problems. This bug > needs to be addressed soon. I would HATE switching to linux because my > system keeps crashing. This bug requires shell access. So if you system is crashing because of this bug, it is because of your users. Limiting the number of processes per user, will stop regular users from exploiting this bug. > --------------- > Scott Swindells, SchematiX.NET Tom --0-615793131-902866302=:22030-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 13:43:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00901 for freebsd-stable-outgoing; Tue, 11 Aug 1998 13:43:41 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.wsg.net (ns1.wsg.net [206.97.122.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA00879 for ; Tue, 11 Aug 1998 13:43:33 -0700 (PDT) (envelope-from gilem@wsg.net) Message-Id: <199808112043.NAA00879@hub.freebsd.org> Received: (qmail 27049 invoked by uid 0); 11 Aug 1998 20:34:34 -0000 Received: from mike.wsg.net (HELO tc) (206.97.122.31) by mail.wsg.net with SMTP; 11 Aug 1998 20:34:34 -0000 X-Sender: mikemail@mail.wsg.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Tue, 11 Aug 1998 16:19:23 -0400 To: Mike Smith From: "Michael R. Gile" Subject: Re: threads bug [and mysql] (large) Cc: Tom , freebsd-stable@FreeBSD.ORG In-Reply-To: <199808102244.PAA00391@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:44 PM 8/10/98 -0700, Mike Smith wrote: >> At 12:29 PM 8/10/98 -0700, Tom wrote: >> > >> >On Sun, 9 Aug 1998, Michael R. Gile wrote: >> > >> >> There appears to be a recurring bug in libc_r that is causing >> >> Mysql not to respond to a shutdown. The author claims that >> >> he helped the development group fix this bug some time ago, >> >> but that it has recurred. Any suggestions on where to find this >> >> documentation would be helpful. >> > >> > I don't believe this bug was ever fixed. You can look at the cvslogs to >> >see all changes to libc_r. >> >> i tend to agree, but monty insists that he mailed the necessary fixes >> to the freebsd team months ago. > >To whom? The correct thing do to would be to file a PR, and then use >the PR when referring to this. It wouldn't be surprising if the >patches are rotting in someone's inbox where nobody else can get at >them. >-- i have attached all the relevant documentation that the author had in his sentmail box. I wouldn't normally post such a large message, but i wanted to make sure that this stuff made it into the mail archives. If anyone else wants to help me try to sort through it and find what the current signal problem with mysql & freebsd, then let me know. -mike ============== ----------- To: jb@cimlogic.com.au cc: pauls@locust.etext.org Subject: Freebsd 3.0 threads Reply-To: monty@analytikerna.se Hi. Sorry to mail you directly, but I got your name from pauls@locust.etext.org and he said that you usually answer questions about the FreeBSD pthread implementation. I am the author of MySQL, a 'almost free' SQL implementation. MySQL uses Posix threads and is currently running with native threads on Solaris, Linux (with Linuxthreads), AIX, IRIX and OSF1. I also maintain much updated version of MIT threads and with this MySQL is known to run on SunOS, FreeBSD 2.0 and BSD 2.#. This MIT thread version is distrubted with the MySQL source distribution. I am now trying to help pauls out on FreeBSD 3.0 but I have now got into some trouble and I thought that maybe you can help me on the right track. 1) There isn't a sched.h file. pthread.h have prototypes for some functions that uses sched_param but it's a little problem to use them now :) 2) I looked into /usr/src/lib/libc_r/uthread/pthread_priv.h and found the following: ---- struct sched_param { int prio; /* Should be named sched_priority */ void *no_data; }; enum schedparam_policy { SCHED_RR, SCHED_IO, SCHED_FIFO, SCHED_OTHER }; ---- Shouldn't this be in a sched.h file ? It would also be nice if 'prio' would be renamed 'sched_priority'. I think this is the standard slot name (at least all other pthread implementation uses this) 3) The following functions are not defined: pthread_setprio(), pthread_attr_setprio(),pthread_attr_setscope() When do you think these will be available? 4) I have now fixed workarounds for the above cases. All code compiles and links clean but when run a test program, pthread_create doesn't start a thread. Should threads work at all in FreeBSD 3.0 ? Yours, Monty ************************************ To: pauls@locust.etext.org cc: jb@cimlogic.com.au Subject: Info about mysql porting and fixed bugs in the libc_r library Reply-To: monty@analytikerna.se John Birrell hasn't answered my yet about my problems with the pthread library (I assume he is very busy like the rest of us). Because I couldn't get -lpthread to work I compiled the source version with -g and some things started to work. I can only assume that the libc_r that you have installed isn't the newest one or then something has gone wrong in your installation. I have now started getting some things to work. Here follows a list of bugs I have fixed in the pthread library. I really hope that John will have time to at least examine them and hopefully add some of them to the next distribution. I haven't yet get everything to work, so there will be more patches. Yours, Monty ------------- Bugs found in the Freebsd 3.0 pthread implementation: ---------------------------------------- - sigsuspend should replace the callers mask to the given mask, not add the given mask to the old mask. The signals should also be handled and not as with SIGWAIT where the signal function is ignored. Fix: uthread_sigsuspend.c: /* Save the current sigmal mask: */ oset = _thread_run->sigmask; ! /* Replace the caller's mask with the current one: */ ! _thread_run->sigmask= *set; /* Patched by Monty */ /* Wait for a signal: */ ! _thread_kern_sched_state(PS_SIGSUSPEND, __FILE__, __LINE__); uthread_kern.c: case PS_FDR_WAIT: case PS_FDW_WAIT: case PS_SLEEP_WAIT: + case PS_SIGSUSPEND: And of course add a definition for PS_SIGSUSPEND. ---------------------------------------- - Signals that are not waited for with sigwait() should be handled before they are returned. Fix: - Add a separate 'sigwait_waiting' mask in the thread structure and handle the signal in uthread_kern.c for SIGWAIT if the signal isn't in the sigwait_waiting mask. ---------------------------------------- - It almost impossible to debug threads because all signals are masked in the threads library. Fix: uthread_kern.c, line 53 - static sigset_t sig_to_block = 0xffffffff; + static sigset_t sig_to_block = ~((1 << 5) | (1 << 6) | (1 << 4)); ---------------------------------------- The sigwait function is in the library but it isn't exported. Fix: Add uthread_sigwait.c to libc_r/uthread/Makefile.inc Fix: Add uthread_sigwait.c to libc_r/uthread/Makefile.inc ---------------------------------------- sigwait returns 'random' value: Fix: uthread_sigwait.c, line 42: - int ret; + int ret=EINTR; ---------------------------------------- *********************************' >From monty Sun Aug 10 23:52:21 1997 Date: Sun, 10 Aug 97 23:52:21 EET DST From: To: Paul Southworth Subject: Re: Info about mysql porting and fixed bugs in the libc_r library In-Reply-To: References: <199708101719.UAA21091@monty.pp.sci.fi> Reply-To: monty@analytikerna.se >>>>> "Paul" == Paul Southworth writes: Paul> My mail sent to " jb@cimlogic.com.au" has been bouncing -- timed out. Paul> Perhaps there is something wrong with that site. I took the questions you Paul> asked him and sent them to the freebsd-hackers mailing list. Paul> I can send your patches there as well if that's OK with you. Here is the 'newest' compleate patch that appears to work: (At least sigwait() now works according to Posix and MySQL really neads this): Please mail a copy of this to the freebsd-hackers list. This mails ends with a compleat patch that fixes everything except the pthread.h problem with struct sched_param, but I was able to handle this with configure. Yours, Monty ------- Bugs found in Freebsd's pthread implementation: ---------------------------------------- - sigsuspend should replace the callers mask to the given mask, not add the given mask to the old mask. The signals should also be handled and not as with SIGWAIT where the signal function is ignored. Fix: uthread_sigsuspend.c: /* Save the current sigmal mask: */ oset = _thread_run->sigmask; ! /* Replace the caller's mask with the current one: */ ! _thread_run->sigmask= *set; /* Patched by Monty */ /* Wait for a signal: */ ! _thread_kern_sched_state(PS_SIGSUSPEND, __FILE__, __LINE__); uthread_kern.c: case PS_FDR_WAIT: case PS_FDW_WAIT: case PS_SLEEP_WAIT: + case PS_SIGSUSPEND: And of course add a definition for PS_SIGSUSPEND. ---------------------------------------- - It almost impossible to debug threads because all signals are masked in the threads library. Fix: uthread_kern.c, line 53 - static sigset_t sig_to_block = 0xffffffff; + static sigset_t sig_to_block = ~((1 << 5) | (1 << 6) | (1 << 4)); ---------------------------------------- - The sigwait function is in the library but it isn't exported. - A signal to a thread in sigwait doesn't set the thread 'runnable'. This is because the arguments to sigwait() is put to sigmask which doesn't work because the signal must be sent to _thread_signal(). - Signals that are not waited for with sigwait() should be handled before they are returned. - sigwait returns 'random' value: Fix: Add uthread_sigwait.c to libc_r/uthread/Makefile.inc Change sigwait to: In pthread_privat.h PS_DEAD, ! PS_STATE_MAX, + PS_SIGSUSPEND }; ---- /* * Current signal mask and array of pending signals. */ ! sigset_t sigmask,sigwaitmask; int sigpend[NSIG]; uthread_kern.c: Change: /* Waiting on a signal: */ case PS_SIGWAIT: /* Change the state of the thread to run: */ PTHREAD_NEW_STATE(pthread,PS_RUNNING); /* Return the signal number: */ pthread->signo = sig; /* Flag the signal as dealt with: */ done = 1; break; } to /* Waiting on a signal: */ case PS_SIGWAIT: /* Change the state of the thread to run: */ PTHREAD_NEW_STATE(pthread,PS_RUNNING); if (sigismember(&pthread->sigwaitmask, sig)) { /* Return the signal number: */ pthread->signo = sig; /* Flag the signal as dealt with: */ done = 1; } break; ---------------------------------------- Because one needs to access the struct sched_param slots this must be defined when one includes pthread.h. One should also change the slot name from 'prior' to 'sched_priority' according to Posix. Fix: Move definition of structs sched_param from pthread_private.h to pthread.h. Change: struct sched_param { int prio; void *no_data; }; to struct sched_param { int sched_priority; void *no_data; }; Empty definition of the schedparam functions would also be nice.. ******************************************************************************* Complete patch of the above with some small additions for sigsuspend: diff of Makefile.inc in /usr/src/lib/libc_r/uthread/ and . 85a86 > uthread_sigwait.c \ diff of pthread_private.h in /usr/src/lib/libc_r/uthread/ and . 243c243,244 < PS_STATE_MAX --- > PS_STATE_MAX, > PS_SIGSUSPEND 344c345 < sigset_t sigmask; --- > sigset_t sigmask,sigwaitmask; diff of uthread_kern.c in /usr/src/lib/libc_r/uthread/ and . 53c53,54 < static sigset_t sig_to_block = 0xffffffff; --- > /* Changed by monty for easy debugging of pthreads with gdb */ > static sigset_t sig_to_block = ~((1 << 5) | (1 << 6) | (1 << 4)); 893a895 > case PS_SIGSUSPEND: 909a912,913 > if (sigismember(&pthread->sigwaitmask, sig)) > { 914a919 > } 1100a1106 > case PS_SIGSUSPEND: 1449a1456 > case PS_SIGSUSPEND: diff of uthread_sigsuspend.c in /usr/src/lib/libc_r/uthread/ and . 50,51c50,51 < /* Combine the caller's mask with the current one: */ < _thread_run->sigmask |= *set; --- > /* Replace the caller's mask with the current one: */ > _thread_run->sigmask= *set;/* Patched by Monty */ 54c54 < _thread_kern_sched_state(PS_SIGWAIT, __FILE__, __LINE__); --- > _thread_kern_sched_state(PS_SIGSUSPEND, __FILE__, __LINE__); diff of uthread_sigwait.c in /usr/src/lib/libc_r/uthread/ and . 38a39,40 > /* This version of sigwait is modifed by monty@tcx.se to work properly */ > 42c44 < int ret; --- > int ret=0; 49,51d50 < /* Save the current sigmal mask: */ < oset = _thread_run->sigmask; < 53c52,56 < _thread_run->sigmask |= *set; --- > _thread_run->sigmask &= ~*set; > _thread_run->sigwaitmask = *set; > > /* Clear for easy error check */ > _thread_run->signo=0; 62a66,68 > > /* Reset the sigwait mask for debugging */ > _thread_run->sigwaitmask = 0; **************************************************************** From: John Birrell To: edmond@shaman.lycaeum.org (Andrew N. Edmond) Cc: jb@cimlogic.com.au, monty@tcx.se, ross@flyingcroc.com Subject: Re: is libc_r broken in 980520-SNAP? Date: Wed, 17 Jun 1998 15:22:39 +1000 (EST) Andrew N. Edmond wrote: > We are specifically looking for something for monty to be able to put in > his INSTALL-SOURCE doc on how to compile MySQL 3.22.1-alpha and beyond on > FreeBSD 3.0-current past march or so... (including optimizing it with > egcc -O6). Monty also has assembler code for i386 platforms for the > string functions that we are trying to compile in here as well... > (--enable-assembler) > > ... you'd be willing to help with this? MySQL was one of the packages mentioned when people complained about performance differences between libc_r and MIT pthreads. An attempt has been made to address those issues, but nobody has commented on any performance change. Since I'm also working on FreeBSD/Alpha, I'm choosing packages to checkout with that too. MySQL might be worth trying provided that the tests are good enough to indicate if the package actually works. Is the FreeBSD i386 asm code for the string functions no good? ***************************' From: John Birrell To: tom@uniserve.com (Tom) Cc: jb@cimlogic.com.au, edmond@shaman.lycaeum.org, stable@FreeBSD.ORG, monty@tcx.se Subject: Re: is libc_r broken in 980520-SNAP (and stable?)? Date: Thu, 18 Jun 1998 07:55:55 +1000 (EST) Tom wrote: > One thing that confuses me is that how does libc_r from 2.2.6-stable and > -current compare these days? They used to be identical, but now that > -current is getting kernel support for threads and alpha stuff, I assume > that they must be quite different now. Primarily, is libc_r from > 2.2.6-stable just as usable as libc_r from current? Highwind Software > (www.highwind.com) has a beta version of their news software that it is > statically linked to a libc_r with fixes they say they got from you. > Would this be a -stable libc_r or a -current libc_r that they are using? Highwind are only using 2.2.6 with libc_r built from the RELENG_2_2 branch. The -current libc_r differs substantially from the -stable implementation because it supports just the POSIX style of signal handling where there are one set of signal handlers declared for the threaded process, not one set per thread. This allows -current to avoid blocking signals as part of it's scheduler. This is what drains performance for some applications. The version of libc_r in the RELENG_2_2 contains fixes for all bugs that people have reported. In Highwind's case, they have code that did things like read/write with zero bytes; and write to a read only file. These caused libc_r to hang waiting on a file descriptor to become ready when it never would. Most software doesn't do this sort of thing. It seems to come from C++ code. 8-) Kernel threads in 3.0 actually have nothing to do with libc_r. They require a libpthread and a thread-aware libc. The -current libc_r implementation works on FreeBSD/Alpha. ************************** From: John Birrell To: tom@uniserve.com (Tom) Cc: jb@cimlogic.com.au, edmond@shaman.lycaeum.org, stable@FreeBSD.ORG, monty@tcx.se Subject: Re: is libc_r broken in 980520-SNAP (and stable?)? Date: Thu, 18 Jun 1998 08:27:37 +1000 (EST) Tom wrote: > Are you aware of the problems with MySQL? I have 2.2.6-stable of May > 21, and a signal/alarm test program (thr_alarm) hangs. No, I wasn't aware of that. > Also, how should -stable threaded applications be compiled and linked? > You mentioned before that "-pthread" should be used rather than linking > with libc_r? Does that apply to -stable too? I think -stable thread apps > need to be compiled with "-D_THREAD_SAFE" and linked with "-lc_r" but I'm > not sure anymore. -stable thread apps need to be compiled with -D_THREAD_SAFE to get a thread-safe errno. -current does not require that. Linking both -current and -stable uses -pthread to get the right libraries because people don't seem to be able to use -nostdlib. I'm going to try building MySQL on -current this morning. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ *******************************************' After this I haven't got anything from 'jb@cimlogic.com.au'. I suspect that the new alarm handling that he mentions in the second last mail has breaked something. Regards, Monty ====================================================== Michael Gile gilem@wsg.net President (518)435-0682 Web Services Group http://www.wsg.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 14:36:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09888 for freebsd-stable-outgoing; Tue, 11 Aug 1998 14:36:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07481; Tue, 11 Aug 1998 14:22:05 -0700 (PDT) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.1/8.6.10) id OAA06041; Tue, 11 Aug 1998 14:21:41 -0700 (PDT) Message-Id: <199808112121.OAA06041@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdXC6030; Tue Aug 11 14:21:28 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: Tom cc: Stefan Bethke , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-reply-to: Your message of "Tue, 11 Aug 1998 13:07:44 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Aug 1998 14:21:28 -0700 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, if you limit the number of processes per user, you can almost > completely prevent it from happening (at least for regular users anyhow). Has anyone tested this to determine where the break point might be? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 14:44:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11112 for freebsd-stable-outgoing; Tue, 11 Aug 1998 14:44:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10824; Tue, 11 Aug 1998 14:43:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01202; Tue, 11 Aug 1998 14:41:45 -0700 (PDT) Message-Id: <199808112141.OAA01202@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Cy Schubert - ITSD Open Systems Group cc: Tom , Stefan Bethke , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-reply-to: Your message of "Tue, 11 Aug 1998 14:21:28 PDT." <199808112121.OAA06041@passer.osg.gov.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Aug 1998 14:41:45 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Actually, if you limit the number of processes per user, you can almost > > completely prevent it from happening (at least for regular users anyhow). > > Has anyone tested this to determine where the break point might be? This is a feature of the exploit. Others exist which aren't subject to the constraints that you're encountering here. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 14:51:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12387 for freebsd-stable-outgoing; Tue, 11 Aug 1998 14:51:46 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12322; Tue, 11 Aug 1998 14:50:46 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id XAA12739; Tue, 11 Aug 1998 23:44:27 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id XAA28004; Tue, 11 Aug 1998 23:51:04 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id XAA11659; Tue, 11 Aug 1998 23:50:12 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Tue, 11 Aug 1998 23:50:11 +0200 (CEST) From: Stefan Bethke To: Cy Schubert - ITSD Open Systems Group cc: Tom , Stefan Bethke , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: <199808112121.OAA06041@passer.osg.gov.bc.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Aug 1998, Cy Schubert wrote: > > Actually, if you limit the number of processes per user, you can almost > > completely prevent it from happening (at least for regular users anyhow). > > Has anyone tested this to determine where the break point might be? This point is moot. The bug is totally unrelated to the number of FDs or processes; you only conceal it *to this particular program*. The bug needs to be fixed. Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 15:03:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13559 for freebsd-stable-outgoing; Tue, 11 Aug 1998 15:03:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13542; Tue, 11 Aug 1998 15:03:36 -0700 (PDT) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.1/8.6.10) id PAA06533; Tue, 11 Aug 1998 15:03:01 -0700 (PDT) Message-Id: <199808112203.PAA06533@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdam6516; Tue Aug 11 15:02:03 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: Stefan Bethke cc: Cy Schubert - ITSD Open Systems Group , Tom , Stefan Bethke , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-reply-to: Your message of "Tue, 11 Aug 1998 23:50:11 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Aug 1998 15:02:03 -0700 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 11 Aug 1998, Cy Schubert wrote: > > > > Actually, if you limit the number of processes per user, you can almost > > > completely prevent it from happening (at least for regular users anyhow). > > > > Has anyone tested this to determine where the break point might be? > > This point is moot. The bug is totally unrelated to the number of FDs or > processes; you only conceal it *to this particular program*. > > The bug needs to be fixed. I suppose when it does get fixed, would an advisory (or even a note to this list) be possible? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 16:42:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29551 for freebsd-stable-outgoing; Tue, 11 Aug 1998 16:42:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [207.149.232.62] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29413 for ; Tue, 11 Aug 1998 16:42:13 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.8/8.8.8) id QAA17433; Tue, 11 Aug 1998 16:40:20 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199808112340.QAA17433@GndRsh.aac.dev.com> Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? In-Reply-To: from Dexnation Holodream at "Aug 10, 98 11:42:48 pm" To: dex@wankers.net (Dexnation Holodream) Date: Tue, 11 Aug 1998 16:40:20 -0700 (PDT) Cc: garyr@wcs.uq.edu.au, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 11 Aug 1998, Gary Roberts wrote: > > > I'm trying to load 2.2.7-RELEASE on a new Toshiba notebook which > > has the above PCMCIA card but it doesn't seem to be detected by > > the GENERIC kernel. > > > > I assumed that since the Intel EtherExpress PRO/10 is reported as > > supported, it would probably also be in the PC card format as well. > > > > Can anyone advise whether there is any support now or in the near > > future for this card? > > ok...first off...the PRO/10 driver is PCI only. #2 only NEW revisions of > the card work...I have the OLD revision, and am considering writing a > driver, but intel's documentation is VERY hard to find on the chip that > drives it (the 82596)...I've found documentation to port to the NEW chip > from the OLD, but none on the 82596...now...the pcmcia card doesn't use > the PCI bus calls, it uses the PCCARD calls, which is a complete other > ball of wax. You will find the 82596 data sheets in the 1993 Intel Connectivity data book, or atleast that is one place I found it. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 17:29:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08073 for freebsd-stable-outgoing; Tue, 11 Aug 1998 17:29:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wankers.net (user-37kbu2h.dialup.mindspring.com [207.69.248.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08067 for ; Tue, 11 Aug 1998 17:29:35 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost.mindspring.com [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id UAA22089; Tue, 11 Aug 1998 20:31:31 -0400 (EDT) (envelope-from dex@wankers.net) Date: Tue, 11 Aug 1998 20:31:29 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: "Rodney W. Grimes" cc: garyr@wcs.uq.edu.au, freebsd-stable@FreeBSD.ORG Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? In-Reply-To: <199808112340.QAA17433@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unfortunately, I don't have this book...do you have a spare copy you could send me? -Jon On Tue, 11 Aug 1998, Rodney W. Grimes wrote: > > On Tue, 11 Aug 1998, Gary Roberts wrote: > > > > > I'm trying to load 2.2.7-RELEASE on a new Toshiba notebook which > > > has the above PCMCIA card but it doesn't seem to be detected by > > > the GENERIC kernel. > > > > > > I assumed that since the Intel EtherExpress PRO/10 is reported as > > > supported, it would probably also be in the PC card format as well. > > > > > > Can anyone advise whether there is any support now or in the near > > > future for this card? > > > > ok...first off...the PRO/10 driver is PCI only. #2 only NEW revisions of > > the card work...I have the OLD revision, and am considering writing a > > driver, but intel's documentation is VERY hard to find on the chip that > > drives it (the 82596)...I've found documentation to port to the NEW chip > > from the OLD, but none on the 82596...now...the pcmcia card doesn't use > > the PCI bus calls, it uses the PCCARD calls, which is a complete other > > ball of wax. > > You will find the 82596 data sheets in the 1993 Intel Connectivity data > book, or atleast that is one place I found it. > > > -- > Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com > Accurate Automation, Inc. Reliable computers for FreeBSD > http://www.aai.dnsmgr.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 17:30:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08377 for freebsd-stable-outgoing; Tue, 11 Aug 1998 17:30:26 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bamboo.verinet.com (bamboo.verinet.com [204.144.246.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08303 for ; Tue, 11 Aug 1998 17:30:12 -0700 (PDT) (envelope-from allenc@verinet.com) Received: from struct. (tulip1.verinet.com [199.45.181.193]) by bamboo.verinet.com (8.8.8/8.7.1) with ESMTP id SAA08497; Tue, 11 Aug 1998 18:29:47 -0600 Received: from verinet.com (localhost [127.0.0.1]) by struct. (8.8.8/8.8.8) with ESMTP id SAA03797; Tue, 11 Aug 1998 18:28:47 -0600 (MDT) (envelope-from allenc@verinet.com) Message-ID: <35D0E1BF.3CF787D8@verinet.com> Date: Tue, 11 Aug 1998 18:28:47 -0600 From: Allen Campbell X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: garycor@home.com CC: freebsd-stable@FreeBSD.ORG Subject: Re: XF86_SVGA hangs 2.2.7-STABLE References: <35CFB92F.F2A23952@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary T. Corcoran wrote: > > Dexnation Holodream wrote: > > > > On Mon, 10 Aug 1998, Jeff Kletsky wrote: > > > > [*snip*] > > > > > Any suggestions? > > > (other than stick with what works ;-) > > > > Try using the right server? (XF86_S3) > > I know it's counter-intuitive, but the XF86_SVGA server is > NOT just a "super VGA" (800x600) server. It's actually the more > advanced X server for some of the chips, including the S3 chips. > Check the docs for the details... > > Gary > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Although this is the case, the SVGA driver is quite a bit newer and, as documented, not as stable as the S3 driver when used in this way. How much could it take to try it out? -- Allen Campbell allenc@verinet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 18:08:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14935 for freebsd-stable-outgoing; Tue, 11 Aug 1998 18:08:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14921 for ; Tue, 11 Aug 1998 18:08:11 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (dial-56-090.easystreet.com [206.103.56.90]) by mail.easystreet.com (8.8.7/8.8.7) with SMTP id SAA13487; Tue, 11 Aug 1998 18:06:21 -0700 (PDT) Message-ID: <007901bdc595$73e33130$0d787880@apex> From: "Carlos C. Tapang" To: "Rodney W. Grimes" , "Dexnation Holodream" Cc: , Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? Date: Tue, 11 Aug 1998 19:03:50 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The 82596 is an older chip that was used in several LAN cards (Pro/100A, PRO/10 PCI, Flash32). These cards had problems and were very difficult to get to work. The newer chip, the 82557 is the one now used in the PRO/100B and the new version of PRO/10 PCI. You may order the data sheet of the 82596 from the Intel Literature department, but that won't be enough. What you need is the technical spec. of the particular card you are using. Because it's an old card, I doubt whether you can get the details on it. At any rate, try visiting support.intel.com or calling 800-525-3019 (faxback) or 800-321-4044. The Intel support personnel are very helpful, just tell them you are writing a device driver. --Carlos -----Original Message----- From: Rodney W. Grimes To: Dexnation Holodream Cc: garyr@wcs.uq.edu.au ; freebsd-stable@FreeBSD.ORG Date: Tuesday, August 11, 1998 5:23 PM Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? >> On Tue, 11 Aug 1998, Gary Roberts wrote: >> >> > I'm trying to load 2.2.7-RELEASE on a new Toshiba notebook which >> > has the above PCMCIA card but it doesn't seem to be detected by >> > the GENERIC kernel. >> > >> > I assumed that since the Intel EtherExpress PRO/10 is reported as >> > supported, it would probably also be in the PC card format as well. >> > >> > Can anyone advise whether there is any support now or in the near >> > future for this card? >> >> ok...first off...the PRO/10 driver is PCI only. #2 only NEW revisions of >> the card work...I have the OLD revision, and am considering writing a >> driver, but intel's documentation is VERY hard to find on the chip that >> drives it (the 82596)...I've found documentation to port to the NEW chip >> from the OLD, but none on the 82596...now...the pcmcia card doesn't use >> the PCI bus calls, it uses the PCCARD calls, which is a complete other >> ball of wax. > >You will find the 82596 data sheets in the 1993 Intel Connectivity data >book, or atleast that is one place I found it. > > >-- >Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com >Accurate Automation, Inc. Reliable computers for FreeBSD >http://www.aai.dnsmgr.com > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 20:39:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09676 for freebsd-stable-outgoing; Tue, 11 Aug 1998 20:39:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rachel.glenatl.glenayre.com (mail.glenatl.glenayre.com [157.230.160.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA09642 for ; Tue, 11 Aug 1998 20:39:01 -0700 (PDT) (envelope-from jhicks@glenatl.glenayre.com) Received: from jhicks.glenatl.glenayre.com by rachel.glenatl.glenayre.com (SMI-8.6/SMI-SVR4) id XAA24509; Tue, 11 Aug 1998 23:31:48 -0400 Received: from jhicks.glenatl.glenayre.com (localhost.glenatl.glenayre.com [127.0.0.1]) by jhicks.glenatl.glenayre.com (8.8.8/8.8.5) with ESMTP id XAA09287 for ; Tue, 11 Aug 1998 23:31:46 -0400 (EDT) Message-Id: <199808120331.XAA09287@jhicks.glenatl.glenayre.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? In-reply-to: Your message of "Tue, 11 Aug 1998 19:03:50 PDT." <007901bdc595$73e33130$0d787880@apex> Date: Tue, 11 Aug 1998 23:31:46 -0400 From: Jerry Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The good, the bad, and the ugly: http://developer.intel.com/design/network/datashts/ Cheers, Jerry Hicks jhicks@glenatl.glenayre.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 11 21:04:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13823 for freebsd-stable-outgoing; Tue, 11 Aug 1998 21:04:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA13816 for ; Tue, 11 Aug 1998 21:04:37 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z6S8z-0004c6-00; Tue, 11 Aug 1998 22:04:13 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id WAA04420; Tue, 11 Aug 1998 22:05:38 -0600 (MDT) Message-Id: <199808120405.WAA04420@harmony.village.org> To: Dexnation Holodream Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Aug 1998 20:31:29 EDT." References: Date: Tue, 11 Aug 1998 22:05:38 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Dexnation Holodream writes: : unfortunately, I don't have this book...do you have a spare copy you could : send me? What is Intel's policy on datasheet copying? I know that I've photocopied several w/o guilt under the fair use doctorine, but I was wondering if they had an official policy... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 12 00:21:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07400 for freebsd-stable-outgoing; Wed, 12 Aug 1998 00:21:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07387; Wed, 12 Aug 1998 00:21:45 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id AAA08737; Wed, 12 Aug 1998 00:21:20 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 12 Aug 1998 00:21:19 -0700 (PDT) From: Doug White To: "Aaron D. Gifford" cc: questions@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: ipfw problem??? In-Reply-To: <35CF769F.68C80A22@infowest.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Aug 1998, Aaron D. Gifford wrote: > Something's weird with my ipfw setup. It seems to work perfectly as I > expected except for this tiny bit of weirdness. My ipfw setup lets me > ping and traceroute and telnet to my heart's content EXCEPT when the > remote address is within the same class C address space as my own > dynamically assigned IP number. Then I get "sendto: Permission denied." > errors left and right. Why is this? I checked my netmask via 'netstat > -in' and sure enough, my netmask is 255.255.255.255. What's going on > here? Your netmask is wrong. 255.255.255.255 is not a valid netmask for a standard class C, it should be 255.255.255.0. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 12 00:55:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13170 for freebsd-stable-outgoing; Wed, 12 Aug 1998 00:55:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA13141 for ; Wed, 12 Aug 1998 00:55:38 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z6VkU-0004kj-00; Wed, 12 Aug 1998 01:55:10 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id BAA05643; Wed, 12 Aug 1998 01:56:37 -0600 (MDT) Message-Id: <199808120756.BAA05643@harmony.village.org> To: Jerry Hicks Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Aug 1998 23:31:46 EDT." <199808120331.XAA09287@jhicks.glenatl.glenayre.com> References: <199808120331.XAA09287@jhicks.glenatl.glenayre.com> Date: Wed, 12 Aug 1998 01:56:37 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808120331.XAA09287@jhicks.glenatl.glenayre.com> Jerry Hicks writes: : The good, the bad, and the ugly: : : http://developer.intel.com/design/network/datashts/ well, the ugly isn't there. I don't see a 82586 nor a 82593 datasheet in the whole lot of them :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 12 01:54:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22632 for freebsd-stable-outgoing; Wed, 12 Aug 1998 01:54:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22561 for ; Wed, 12 Aug 1998 01:53:57 -0700 (PDT) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id JAA01112; Wed, 12 Aug 1998 09:53:18 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.8/8.8.7) id JAA13478; Wed, 12 Aug 1998 09:52:33 +0100 (BST) Message-ID: <19980812095233.A13318@iii.co.uk> Date: Wed, 12 Aug 1998 09:52:33 +0100 To: "Michael R. Gile" , Mike Smith Cc: Tom , freebsd-stable@FreeBSD.ORG Subject: Re: threads bug [and mysql] (large) References: <199808102244.PAA00391@dingo.cdrom.com> <199808112043.NAA00879@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808112043.NAA00879@hub.freebsd.org>; from Michael R. Gile on Tue, Aug 11, 1998 at 04:19:23PM -0400 Organization: interactive investor Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 11, 1998 at 04:19:23PM -0400, Michael R. Gile wrote: > i have attached all the relevant documentation that the author had in > his sentmail box. I've just taken this and wrapped it up as a PR. kern/7586 for anyone that wants to take a look. N -- "So it does!" said Pooh. "It goes in!" "So it does!" said Piglet. "And it comes out!" "Doesn't it?" said Eeyore. "It goes in and out like anything." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 12 03:10:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04165 for freebsd-stable-outgoing; Wed, 12 Aug 1998 03:10:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from server2.rad.net.id (server2.rad.net.id [202.154.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04131 for ; Wed, 12 Aug 1998 03:10:44 -0700 (PDT) (envelope-from Leonard_Ong@iname.com) Received: from ZhugeLiang (dyn2170a.dialin.rad.net.id [202.154.7.170]) by server2.rad.net.id (8.8.5/RADNET) with SMTP id RAA02493 for ; Wed, 12 Aug 1998 17:10:14 +0700 (WIB) From: "Leonard Ong" To: Subject: RE: stable-digest V4 #163 Date: Wed, 12 Aug 1998 17:08:24 +0700 Message-ID: <000a01bdc5d9$242c4ca0$aa079aca@ZhugeLiang.ong.net.id> 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 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal In-Reply-To: <199808120721.AAA07412@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Friends, I used to be Windows and Linux User, now I am learning the ropes of FreeBSD. I have read the FreeBSD FAQ completely and still reading the Handbook. Meanwhile I have some questions regarding my previous systems with FreeBSD. Anyone who has installed Linux, played around with it and using FreeBSD now, Please email me personally. I would like to ask several questions regarding the stable version I just have in hand. Thank you Regards, Leonard Ong Leonard Ong Advanced Research,Inc Leonard Ong| Confusious said : " The Journey of thousands miles (Íõ¶°ºÀ) | begins with a small single step " | Leonard_Ong@iname.com - Share Knowledge together! Linux/Win98| UIN : 1041402 == http://www.poboxes.com/Leonard_Ong Powered | 68FB C87E 8A0D EC9F EC82 A6FC C547 B4E4 CA46 94DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 12 03:17:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA05103 for freebsd-stable-outgoing; Wed, 12 Aug 1998 03:17:06 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from amalthea.salford.ac.uk (amalthea.salford.ac.uk [146.87.255.61]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA05067 for ; Wed, 12 Aug 1998 03:16:53 -0700 (PDT) (envelope-from freebsd-stable-list@salford.ac.uk) From: freebsd-stable-list@salford.ac.uk Received: (qmail 28293 invoked by alias); 12 Aug 1998 10:16:25 -0000 Received: (qmail 28287 invoked from network); 12 Aug 1998 10:16:25 -0000 Received: from ananke.salford.ac.uk (146.87.255.67) by amalthea.salford.ac.uk with SMTP; 12 Aug 1998 10:16:25 -0000 Received: (qmail 19984 invoked by alias); 12 Aug 1998 10:16:18 -0000 Delivered-To: catchall-freebsd-stable@freebsd.org Received: (qmail 19976 invoked by uid 6); 12 Aug 1998 10:16:17 -0000 Message-ID: <19980812101617.19975.qmail@ananke.salford.ac.uk> Reply-To: mark@nospam.salford.ac.uk (Mark Powell) Subject: Re: Huge Bug in FreeBSD not fixed? To: freebsd-stable@FreeBSD.ORG Date: 12 Aug 1998 11:16:15 +0100 X-Gated-To-News-By: NewsMaster Xref: ananke.salford.ac.uk salford.mailing-lists.freebsd.stable:5465 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <6qqbve$ptd$1@ananke.salford.ac.uk>, Tom wrote: > >On Tue, 11 Aug 1998, Stefan Bethke wrote: > >... >> As a relief you can try to increase the number of mbufs; however, this will >> only make the case less likely to occur. >... > > Actually, if you limit the number of processes per user, you can almost >completely prevent it from happening (at least for regular users anyhow). I posted a similar article a month or so ago, see: Subject: 2.2.6 net performance and panic with 1000's of sockets open in freebsd-net. I had a test program that was opening 1000's of sockets to another FreeBSD box and leaving them open. This would panic both FreeBSD boxes consistently. It only used one process. Thus limiting processes will have no effect. Limiting open files would though. I realise the other exploit uses the fact that it can, in total, open n*u (n = maximum number of open file descriptors & u the maximum number of user processes), whereas mine can only open n. However, it's still there. Seems like a bug to me. I could post my program to rootshell too :) The advice I received was to increase maxusers (to increase mbufs) and options "NMBCLUSTERS=8192" options MSIZE="256" This cured the problem. However, I realise that it is simply making it less likely happen. As Stefan pointed out the system panics if it doesn't get it's mbuf. -- Mark Powell - System Administrator (UNIX) - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 Email: M.S.Powell@ais.salfrd.ac.uk finger mark@ucsalf.ac.uk (for PGP key) NO SPAM please: Spell salford correctly to reply to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 12 08:40:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12821 for freebsd-stable-outgoing; Wed, 12 Aug 1998 08:40:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dfw-ix9.ix.netcom.com (dfw-ix9.ix.netcom.com [206.214.98.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12463 for ; Wed, 12 Aug 1998 08:38:01 -0700 (PDT) (envelope-from a.conrad@ix.netcom.com) Received: (from smap@localhost) by dfw-ix9.ix.netcom.com (8.8.4/8.8.4) id KAA06011; Wed, 12 Aug 1998 10:34:11 -0500 (CDT) Received: from rtp-nc2-07.ix.netcom.com(199.35.214.71) by dfw-ix9.ix.netcom.com via smap (V1.3) id rma005979; Wed Aug 12 10:33:57 1998 Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <000a01bdc5d9$242c4ca0$aa079aca@ZhugeLiang.ong.net.id> Date: Wed, 12 Aug 1998 11:38:14 -0500 (EST) Reply-To: a.conrad@ix.netcom.com From: Aaron Springer To: Leonard Ong Subject: RE: stable-digest V4 #163 Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leonard, I use Linux and FreeBSD extensively. Feel free to contact me for help. acs On 12-Aug-98 Leonard Ong wrote: > Dear Friends, > > I used to be Windows and Linux User, now I am learning the ropes of FreeBSD. > I have read the FreeBSD FAQ completely and still reading the Handbook. > Meanwhile I have some questions regarding my previous systems with FreeBSD. > > Anyone who has installed Linux, played around with it and using FreeBSD now, > Please email me personally. I would like to ask several questions regarding > the stable version I just have in hand. > > Thank you > > > Regards, > Leonard Ong > Leonard Ong Advanced Research,Inc > > Leonard Ong| Confusious said : " The Journey of thousands miles > (Íõ¶°ºÀ) | begins with a small single step " > | Leonard_Ong@iname.com - Share Knowledge together! > Linux/Win98| UIN : 1041402 == http://www.poboxes.com/Leonard_Ong > Powered | 68FB C87E 8A0D EC9F EC82 A6FC C547 B4E4 CA46 94DB > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---------------------------------- E-Mail: Aaron Springer Date: 12-Aug-98 Time: 11:37:24 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 12 08:44:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13562 for freebsd-stable-outgoing; Wed, 12 Aug 1998 08:44:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dfw-ix5.ix.netcom.com (dfw-ix5.ix.netcom.com [206.214.98.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13251 for ; Wed, 12 Aug 1998 08:42:58 -0700 (PDT) (envelope-from Aaron.Springer.a.conrad@ix.netcom.com) From: Aaron.Springer.a.conrad@ix.netcom.com Received: (from smap@localhost) by dfw-ix5.ix.netcom.com (8.8.4/8.8.4) id KAA25653; Wed, 12 Aug 1998 10:29:46 -0500 (CDT) Received: from rtp-nc2-07.ix.netcom.com(199.35.214.71) by dfw-ix5.ix.netcom.com via smap (V1.3) id rma025629; Wed Aug 12 10:29:24 1998 Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <000a01bdc5d9$242c4ca0$aa079aca@ZhugeLiang.ong.net.id> Date: Wed, 12 Aug 1998 11:33:42 -0500 (EST) To: Leonard Ong Subject: RE: stable-digest V4 #163 Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leonard, I use FreeBSD and Linux extensively. Feel free to contact me if you need help. acs On 12-Aug-98 Leonard Ong wrote: > Dear Friends, > > I used to be Windows and Linux User, now I am learning the ropes of FreeBSD. > I have read the FreeBSD FAQ completely and still reading the Handbook. > Meanwhile I have some questions regarding my previous systems with FreeBSD. > > Anyone who has installed Linux, played around with it and using FreeBSD now, > Please email me personally. I would like to ask several questions regarding > the stable version I just have in hand. > > Thank you > > > Regards, > Leonard Ong > Leonard Ong Advanced Research,Inc > > Leonard Ong| Confusious said : " The Journey of thousands miles > (Íõ¶°ºÀ) | begins with a small single step " > | Leonard_Ong@iname.com - Share Knowledge together! > Linux/Win98| UIN : 1041402 == http://www.poboxes.com/Leonard_Ong > Powered | 68FB C87E 8A0D EC9F EC82 A6FC C547 B4E4 CA46 94DB > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---------------------------------- E-Mail: Aaron Springer a.conrad@ix.netcom.com Date: 12-Aug-98 Time: 11:32:24 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 12 08:55:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16053 for freebsd-stable-outgoing; Wed, 12 Aug 1998 08:55:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16047 for ; Wed, 12 Aug 1998 08:55:46 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (dial-56-032.easystreet.com [206.103.56.32]) by mail.easystreet.com (8.8.7/8.8.7) with SMTP id IAA01739; Wed, 12 Aug 1998 08:54:44 -0700 (PDT) Message-ID: <002801bdc611$8d2444f0$0d787880@apex> From: "Carlos C. Tapang" To: "Jerry Hicks" , "Warner Losh" Cc: Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? Date: Wed, 12 Aug 1998 09:52:10 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The 82586 is an old, old ethernet chip. What you are looking for is the 82596, and I just saw it on that page. --Carlos -----Original Message----- From: Warner Losh To: Jerry Hicks Cc: freebsd-stable@FreeBSD.ORG Date: Wednesday, August 12, 1998 1:27 AM Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? >In message <199808120331.XAA09287@jhicks.glenatl.glenayre.com> Jerry Hicks writes: >: The good, the bad, and the ugly: >: >: http://developer.intel.com/design/network/datashts/ > >well, the ugly isn't there. I don't see a 82586 nor a 82593 datasheet >in the whole lot of them :-) > >Warner > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 12 14:16:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12736 for freebsd-stable-outgoing; Wed, 12 Aug 1998 14:16:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sequoia.lituus.fr (dij8-159.abo.wanadoo.fr [193.252.183.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12731 for ; Wed, 12 Aug 1998 14:16:42 -0700 (PDT) (envelope-from root@smtp.wanadoo.fr) Received: (from root@localhost) by sequoia.lituus.fr (8.9.1/8.8.8) id XAA00425; Wed, 12 Aug 1998 23:05:27 +0200 (CEST) (envelope-from root) Date: Wed, 12 Aug 1998 23:05:27 +0200 (CEST) Message-Id: <199808122105.XAA00425@sequoia.lituus.fr> From: Stephane Legrand MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD-stable@FreeBSD.ORG Subject: Huge Bug in FreeBSD not fixed? In-Reply-To: References: X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott writes: > I ran across this bug a while back on rootshell, and then again by a user > on IRC who offered to take down my box. Soon after that, the bug was fixed > and things were fine. But just out of boredom, i decided to run the > exploit again. Sure enough, i had a kernel panic and that was it. All of > this from a normal user account. The bug has reoccured recently and may > cause problems on my server if the users find out about the vulnerability. > > I am running FreeBSD 2.2.7-STABLE (Last compiled on August 5th early in > the morning). The system is running on a PII233 with 64MB RAM. This bug > REALLY needs to be fixed ASAP. > > I would like to know if other systes are vulnerable as well. I discussed > this matter on IRC and everyone said they had similar problems. This bug > needs to be addressed soon. I would HATE switching to linux because my > system keeps crashing. > Just for information, this piece of code perfectly crash my freebsd current box. I must to specify that the "/etc" directory hasn't been updated to current one except for the "rc.conf" file. But it shows that this bug doesn't belong only to stable version. Stephane Legrand. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 12 14:23:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14295 for freebsd-stable-outgoing; Wed, 12 Aug 1998 14:23:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from madcow.borg.com (madcow.borg.com [205.217.206.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14278 for ; Wed, 12 Aug 1998 14:23:39 -0700 (PDT) (envelope-from mark@mail.borg.com) Received: from mail.borg.com (mail.borg.com [205.217.206.192]) by madcow.borg.com (8.9.0/8.8.8) with ESMTP id RAA02665 for ; Wed, 12 Aug 1998 17:22:51 -0400 (EDT) Received: from mark (L237B.borg.com [206.98.37.237]) by mail.borg.com (8.8.7/8.7.3) with SMTP id RAA06169 for ; Wed, 12 Aug 1998 17:22:51 -0400 (EDT) Message-Id: <3.0.32.19980812173336.00696fd0@mail.borg.com> X-Sender: mark@mail.borg.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 12 Aug 1998 17:33:38 -0400 To: FreeBSD-stable@FreeBSD.ORG From: "Mark S. Reichman" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe - Mark *********************************************************************** We are Intel. Division is futile. You will be approximated. *********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 12 14:43:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18202 for freebsd-stable-outgoing; Wed, 12 Aug 1998 14:43:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rachel.glenatl.glenayre.com (mail.glenatl.glenayre.com [157.230.160.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA18197 for ; Wed, 12 Aug 1998 14:43:42 -0700 (PDT) (envelope-from jhicks@glenatl.glenayre.com) Received: from jhicks.glenatl.glenayre.com by rachel.glenatl.glenayre.com (SMI-8.6/SMI-SVR4) id RAA15596; Wed, 12 Aug 1998 17:36:01 -0400 Received: from jhicks.glenatl.glenayre.com (localhost.glenatl.glenayre.com [127.0.0.1]) by jhicks.glenatl.glenayre.com (8.8.8/8.8.5) with ESMTP id RAA10602; Wed, 12 Aug 1998 17:35:52 -0400 (EDT) Message-Id: <199808122135.RAA10602@jhicks.glenatl.glenayre.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Carlos C. Tapang" cc: "Jerry Hicks" , "Warner Losh" , freebsd-stable@FreeBSD.ORG Subject: Re: Is Intel EtherExpress PRO/100 Mobile Adapter supported? In-reply-to: Your message of "Wed, 12 Aug 1998 09:52:10 PDT." <002801bdc611$8d2444f0$0d787880@apex> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Aug 1998 17:35:52 -0400 From: Jerry Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah, but the 82596 is bad... the 82586 is the one that's _REALLLY_ ugly ;-) J. Hicks > The 82586 is an old, old ethernet chip. What you are looking for is the > 82596, and I just saw it on that page. > --Carlos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 01:06:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24038 for freebsd-stable-outgoing; Thu, 13 Aug 1998 01:06:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24032; Thu, 13 Aug 1998 01:06:33 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.7/8.7.3) with SMTP id BAA08861; Thu, 13 Aug 1998 01:06:02 -0700 (PDT) Date: Thu, 13 Aug 1998 01:06:02 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: vmopar state in 2.2.7? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having a problem with my INN 2.1 newsreader machines NFS mounting the spool. The nnrpd's are occasionally getting stuck in what top shows as the vmopar state. ps shows the process in Ds state. No kill (obviously) will get it unstuck, and nothing else I do seems to make it come back to life. The NFS server is a Network Appliance, running latest released code, UDP mounts, v2 NFS. Any tip appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 10:30:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02925 for freebsd-stable-outgoing; Thu, 13 Aug 1998 10:30:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02885 for ; Thu, 13 Aug 1998 10:30:23 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id TAA15896 for ; Thu, 13 Aug 1998 19:29:54 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id TAA24139 for ; Thu, 13 Aug 1998 19:29:54 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id TAA26333 for ; Thu, 13 Aug 1998 19:29:50 +0200 (CEST) From: Andre Albsmeier Message-Id: <199808131729.TAA14703@internal> Subject: Can lpr/lpd remove the symlink AND the source file? To: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Date: Thu, 13 Aug 1998 19:29:45 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lets assume the following scenario: We have a big file that is the output of an application which has to be printed. After printing, the file is no longer needed, and for this reason we want the file to get automatically removed after printing. 1. We do a "lpr -r -Pprinter filename" ==> The file is removed after printing 2. We do a "lpr -s -r -Pprinter filename" ==> The symlink is removed after printing, the file remains While doing 1. the file has to be copied which might be unacceptable if it is very large. By using 2. we avoid the copying but the file remains and has to be removed manually. Would it make sense to invent a new option for lpr which allows symlinking AND removal of the symlink together with the input file? Or is this already possible with -STABLE's lpr/lpd and I am simply to stupid... What do you think? Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 10:37:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04602 for freebsd-stable-outgoing; Thu, 13 Aug 1998 10:37:50 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from lepton.nuc.net (lepton.nuc.net [204.49.61.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04589 for ; Thu, 13 Aug 1998 10:37:46 -0700 (PDT) (envelope-from wheelman@nuc.net) Received: from electron.nuc.net (dhcp1.nuc.net [204.49.61.49]) by lepton.nuc.net (8.8.8/8.7.3) with SMTP id MAA01724 for ; Thu, 13 Aug 1998 12:37:19 -0500 (CDT) From: "Jaime Bozza" To: Subject: Questions about Port fixes Date: Thu, 13 Aug 1998 12:35:33 -0500 Message-ID: <000201bdc6e0$c61ff900$313d31cc@electron.nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, While updating PERL as well as the modules I use with PERL, I realized that a few of the ports are broken (won't install at all), have invalid PLIST's, old version or something else that isn't allowing the port to install correctly (or deinstall correctly) ... I have make fixes to the following to bring them up to date: p5-SNMP p5-Mail-Tools p5-MIME-Base64 I also noticed that there are a few others that, while install and deinstall work correctly, rely on the PERL version being 5.005. While this is minor, I would assume using %%PERL_VER%% would be preferable in the PLIST file? I have the files ready to go if anyone's wants them. (Obviously, I don't have CVS access, nor do I feel comfortable getting into that sort of thing right now ) Jaime Bozza Nucleus Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 11:34:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13692 for freebsd-stable-outgoing; Thu, 13 Aug 1998 11:34:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from staff.sirius.com (staff.sirius.com [205.134.226.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13682; Thu, 13 Aug 1998 11:34:57 -0700 (PDT) (envelope-from peter@staff.sirius.com) Received: (from peter@localhost) by staff.sirius.com (8.8.7/Sirius-Inhouse) id LAA14961; Thu, 13 Aug 1998 11:34:01 -0700 (PDT) From: peter@sirius.com Message-Id: <199808131834.LAA14961@staff.sirius.com> Subject: Re: vmopar state in 2.2.7? In-Reply-To: from Jaye Mathisen at "Aug 13, 98 01:06:02 am" To: mrcpu@internetcds.com (Jaye Mathisen) Date: Thu, 13 Aug 1998 11:34:00 -0700 (PDT) Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I'm having a problem with my INN 2.1 newsreader machines NFS mounting > the spool. > > The nnrpd's are occasionally getting stuck in what top shows as > the vmopar state. ps shows the process in Ds state. > > > No kill (obviously) will get it unstuck, and nothing else I do seems to > make it come back to life. > > The NFS server is a Network Appliance, running latest released code, > UDP mounts, v2 NFS. > > Any tip appreciated. > We worked around a similar problem (processes left immortal, here in the context of several processes [httpd] writing to the same NFS mounted file [http log file]) by adjusting the timeout value from 0 (never) to 2 * hz (2 seconds). Details are posted as follow-up to kern/4588 in FreeBSD.org's gnats problem report database. It looks like other parts of the kernel (here the vm subsystem) suffer similar problems. It appears to me that an overly optimistic use of tsleep() with both, interrupts disabled and time-out set to infinity, leaves immortal yet paralyzed processes around. >From /usr/src/sys/vm/vm_object.c (a second, similar occurence around line 1261): 1218 /* 1219 * The busy flags are only cleared at 1220 * interrupt -- minimize the spl transitions 1221 */ 1222 if ((p->flags & PG_BUSY) || p->busy) { 1223 s = splvm(); 1224 if ((p->flags & PG_BUSY) || p->busy) { 1225 p->flags |= PG_WANTED; 1226 tsleep(p, PVM, "vmopar", 0); 1227 splx(s); 1228 goto again; 1229 } 1230 splx(s); 1231 } The code in line 1224 checks a condition to see whether somebody else is already performing an operation on object p; in this case it wants to ensure that a wakeup() for the following tsleep() is delivered by setting a flag in line 1225. But what ensures that the world did not change between lines 1224 and 1225? Could the wakeup() happen after 1224 has determined to issue the tsleep() but before the flagging in 1225 was registered? Then it would be missed. Is this a race condition biting heavily hit machines? Try changing lines 1226 and 1261 to something like: tsleep(p, PVM, "vmopar", 5 * hz); >From the tsleep man page: Tsleep is the general sleep call. Suspends the current process until a wakeup is performed on the specified identifier. The process will then be made runnable with the specified priority. Sleeps at most timo / hz seconds (0 means no timeout). If pri includes the PCATCH flag, signals are checked before and after sleeping, else signals are not checked. Re- turns 0 if awakened, EWOULDBLOCK if the timeout expires. If PCATCH is set and a signal needs to be delivered, ERESTART is returned if the cur- rent system call should be restarted if possible, and EINTR is returned if the system call should be interrupted by the signal (return EINTR). This function would return "EWOULDBLOCK" after the time-out expires then, no clue what that will do to your system or apps ;) -- I would expect the blocked process to go away within 5 seconds... Peter Preuss Sirius Connections, San Francisco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 11:43:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15354 for freebsd-stable-outgoing; Thu, 13 Aug 1998 11:43:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from chain.freebsd.os.org.za (chain.freebsd.os.org.za [196.7.74.174]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15345 for ; Thu, 13 Aug 1998 11:43:34 -0700 (PDT) (envelope-from khetan@chain.freebsd.os.org.za) X-Disclaimer: Contents of this e-mail are the writer's opinion X-Disclaimer2: and may not be quoted, re-produced or forwarded X-Disclaimer3: (in part or whole) without the author's permission. Received: from localhost (khetan@localhost) by chain.freebsd.os.org.za (8.9.1+3.0W/8.9.1) with SMTP id UAA19901 for ; Thu, 13 Aug 1998 20:43:21 +0200 (SAT) (envelope-from khetan@chain.freebsd.os.org.za) Date: Thu, 13 Aug 1998 20:43:20 +0200 (SAT) From: Khetan Gajjar X-Sender: khetan@chain Reply-To: Khetan Gajjar To: stable@FreeBSD.ORG Subject: su problem with freebsd 2.2.7-stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I've noticed a very strange problem with the "su" command on my PC, running 2.2.7-stable from Aug 1 (this problem is recent). Every time I run su (and I have normally never had a problem), the process just starts to grow, and around roughly 10Mb's of resident memory, seg faults. I've rebuilt su from the source tree, but it appears that the command is fine. Any ideas, or debugging that I can do ? It doesn't create a core file, which is a bit limiting. Aug 13 20:40:46 chain /kernel: pid 19854 (su), uid 0: exited on signal 11 --- Khetan Gajjar (!kg1779) * khetan@iafrica.com ; khetan@os.org.za http://www.os.org.za/~khetan * Talk/Finger khetan@chain.freebsd.os.org.za UUNET Internet Africa Support * FreeBSD enthusiast-www2.za.freebsd.org FreeBSD: Because rebooting is for adding new hardware To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 12:52:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28746 for freebsd-stable-outgoing; Thu, 13 Aug 1998 12:52:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sussie.datadesign.se (ns.datadesign.se [194.23.109.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28741 for ; Thu, 13 Aug 1998 12:52:40 -0700 (PDT) (envelope-from kaj@interbizz.se) Received: from localhost (sussie.datadesign.se [194.23.109.130]) by sussie.datadesign.se (8.8.5/8.8.7) with ESMTP id VAA08133; Thu, 13 Aug 1998 21:51:31 +0200 (MET DST) To: khetan@iafrica.com, khetan@chain.freebsd.os.org.za Cc: stable@FreeBSD.ORG Cc: kaj@interbizz.se Subject: Re: su problem with freebsd 2.2.7-stable From: Rasmus Kaj In-Reply-To: Your message of "Thu, 13 Aug 1998 20:43:20 +0200 (SAT)" References: X-Mailer: Mew version 1.92.4 on XEmacs 20.4 (Emerald) X-URL: http://www.e.kth.se/~kaj/ X-Phone: +46 (0)8 - 692 35 09 / +46 (0)70 640 49 14 X-Attribution: Kaj X-Face: M9cR~WYav<"fu%MaslX0`43PAYY?uIsM8[#E(0\Xuy9rj>4gE\h3jm.7DD?]R8*^7T\o&vT U@[53Dwkuup4[0@gw#~kyu>`unH?kVj9CJa02(h>Ki\+i=%rn%sDf^KC.!?IHkKjMAbkd\jgmphp^' d|Q;OeXEAhq?ybGqOs1CHb6TJT42'C`Krnk61//AOfXtNjj/t'`5>Vw0QX!dKfOL$.f+S"LIuwR<;I Z0Qnnx(F^F]o@*V%TUtEV'1Z[TkOl^FFV9Z~A[b19%}uP*,huCU Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980813215130D.kaj@interbizz.se> Date: Thu, 13 Aug 1998 21:51:30 +0200 X-Dispatcher: imput version 971024 Lines: 17 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "KG" == Khetan Gajjar writes: KG> Every time I run su (and I have normally never had a problem), KG> the process just starts to grow, and around roughly 10Mb's of KG> resident memory, seg faults. I've rebuilt su from the source KG> tree, but it appears that the command is fine. A guess: This sounds to me like you have something that creates a new shell in the shell startup files in /root (or whereever the account you su to lives), and thus run an infinite recurse. // Rasmus -- kaj@cityonline.se --------------- Rasmus Kaj - http://www.e.kth.se/~kaj/ \ CityOnLine IB Production AB - http://www.CityOnLine.se/ \---------------------------- Pro is to con as progress is to Congress To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 13:02:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01275 for freebsd-stable-outgoing; Thu, 13 Aug 1998 13:02:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01258; Thu, 13 Aug 1998 13:02:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00604; Thu, 13 Aug 1998 12:59:45 -0700 (PDT) Message-Id: <199808131959.MAA00604@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: peter@sirius.com cc: mrcpu@internetcds.com (Jaye Mathisen), hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: vmopar state in 2.2.7? In-reply-to: Your message of "Thu, 13 Aug 1998 11:34:00 PDT." <199808131834.LAA14961@staff.sirius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 12:59:45 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We worked around a similar problem (processes left immortal, here in > the context of several processes [httpd] writing to the same NFS mounted > file [http log file]) by adjusting the timeout value from 0 (never) to > 2 * hz (2 seconds). Details are posted as follow-up to kern/4588 in > FreeBSD.org's gnats problem report database. As this is an NFS-related issue, you should follow this up with Poul Henning (phk@freebsd.org). I understand he's working on NFS amongst other things at the moment (I know he's working on FreeBSD for us, as he keeps sending us invoices... 8). > It looks like other parts of the kernel (here the vm subsystem) suffer > similar problems. It appears to me that an overly optimistic use of > tsleep() with both, interrupts disabled and time-out set to infinity, > leaves immortal yet paralyzed processes around. I don't think you mean interrupts disabled. > >From /usr/src/sys/vm/vm_object.c (a second, similar occurence around > line 1261): > > 1218 /* > 1219 * The busy flags are only cleared at > 1220 * interrupt -- minimize the spl transitions > 1221 */ > 1222 if ((p->flags & PG_BUSY) || p->busy) { > 1223 s = splvm(); > 1224 if ((p->flags & PG_BUSY) || p->busy) { > 1225 p->flags |= PG_WANTED; > 1226 tsleep(p, PVM, "vmopar", 0); > 1227 splx(s); > 1228 goto again; > 1229 } > 1230 splx(s); > 1231 } > > The code in line 1224 checks a condition to see whether somebody else > is already performing an operation on object p; in this case it wants > to ensure that a wakeup() for the following tsleep() is delivered by > setting a flag in line 1225. > > But what ensures that the world did not change between lines 1224 and > 1225? Could the wakeup() happen after 1224 has determined to issue > the tsleep() but before the flagging in 1225 was registered? Then it > would be missed. Is this a race condition biting heavily hit machines? It shouldn't. the splvm() call should mask vm-related activities from its return through to the call to tsleep (where the mask is saved and the mask for the new context is restored). There is a risk that the assumption in the comment is invalid; you would want to look for any likely operations involving PG_BUSY. To track this one further, you would want to look at the code that's responsible for for dealing with pages with PG_WANTED set, and work out why it's never satisfying this request (or if it is, why it's not waking the above caller up). > Try changing lines 1226 and 1261 to something like: > tsleep(p, PVM, "vmopar", 5 * hz); ... > This function would return "EWOULDBLOCK" after the time-out expires then, > no clue what that will do to your system or apps ;) -- I would expect the > blocked process to go away within 5 seconds... I dont' have 2.2 sources to hand, and the above is now just a call to vm_page_sleep, but if the timeout expires, the entire operation is retried, so it should be harmless (although it is masking a legitimate bug). This might be a candidate for a bandaid patch for 2.2 systems, as 2.2 goes into life-support mode. BTW, thanks for looking at this at all, and thanks for making your findings generally known. If you can roll a patch and put it out for general testing, we'd be very interested in hearing about the feedback you get. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 14:27:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20466 for freebsd-stable-outgoing; Thu, 13 Aug 1998 14:27:55 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from user1.channel1.com (user1.channel1.com [199.1.13.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20445 for ; Thu, 13 Aug 1998 14:27:47 -0700 (PDT) (envelope-from admin@channel1.com) Received: from ntadmin (ntadmin.channel1.com [204.96.33.24]) by user1.channel1.com (8.8.8/8.8.8) with SMTP id RAA19142 for ; Thu, 13 Aug 1998 17:27:16 -0400 (EDT) Message-Id: <3.0.5.32.19980813172702.01091c50@pop.channel1.com> X-Sender: deepblue@pop.channel1.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 13 Aug 1998 17:27:02 -0400 To: freebsd-stable@FreeBSD.ORG From: Mail Handler Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All -- I posted this make world problem about 3 weeks ago to -stable and c.u.b.f.m and received no response: cc -O -I/usr/src/gnu/lib/libgmp/../../../contrib/libgmp -I/usr/src/gnu/lib/libgmp/../../../contrib/libgmp/mpn/generic -I/usr/src/gnu/lib/libgmp/../../../contrib/libgmp/mpn/x86 -DBROKEN_ALIGN -I/usr/obj/usr/src/gnu/lib/libgmp -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libgmp/../../../contrib/libgmp/mpn/mp_bases.c -o mp_bases.o /usr/src/gnu/lib/libgmp/../../../contrib/libgmp/mpn/mp_bases.c:263: parse error before `}' *** Error code 1 Stop. *** Error code 1 This is a P200MMX that has been running CVSUP/make world weekly since 2.2.5. The problem started appearing several weeks before the 2.2.7 release. I tried the usual escalation of solutions for make world issues: 1. Re-running CVSUP; 1a. running make clean in the problem directory; 1b. running make clean, make cleandir, make cleandepend in /usr/src; 2. deleting /usr/sup and re-CVSUP'ing; 3. deleting /usr/sup, /usr/obj and /usr/src and re-CVSUP'ing. Nothing worked, so I decided to wait for the 2.2.7 CDROMs to arrive. They did, so I 4. upgraded and tried make world again. I got other make world failures, but after totally cleaning, I usually ended up with the /libgmp parse error message. So, I 5. clean-installed 2.2.7 with new partitions, reinstalled CVSUP from ports, re-CVSUP'd, made world again and got the same error. Normally, I'd suspect hardware (memory) in a situation like this, but I don't see how make world can run for hours and fail repeatably in exactly the same place. Any suggestions before I give up and put the box out to Windows pasture? Thanks, Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 14:27:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20485 for freebsd-stable-outgoing; Thu, 13 Aug 1998 14:27:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from chain.freebsd.os.org.za (chain.freebsd.os.org.za [196.7.74.174]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20444 for ; Thu, 13 Aug 1998 14:27:47 -0700 (PDT) (envelope-from khetan@chain.freebsd.os.org.za) X-Disclaimer: Contents of this e-mail are the writer's opinion X-Disclaimer2: and may not be quoted, re-produced or forwarded X-Disclaimer3: (in part or whole) without the author's permission. Received: from localhost (khetan@localhost) by chain.freebsd.os.org.za (8.9.1+3.0W/8.9.1) with SMTP id XAA27324; Thu, 13 Aug 1998 23:27:21 +0200 (SAT) (envelope-from khetan@chain.freebsd.os.org.za) Date: Thu, 13 Aug 1998 23:27:20 +0200 (SAT) From: Khetan Gajjar X-Sender: khetan@chain Reply-To: Khetan Gajjar To: Rasmus Kaj cc: stable@FreeBSD.ORG Subject: Re: su problem with freebsd 2.2.7-stable In-Reply-To: <19980813215130D.kaj@interbizz.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 Aug 1998, Rasmus Kaj wrote: >A guess: This sounds to me like you have something that creates a new >shell in the shell startup files in /root (or whereever the account >you su to lives), and thus run an infinite recurse. I haven't changed anything in the shell startup files. That's the weird thing. It's just started yesterday, for no apparent reason. I can sudo bash, and that works, but I'd still prefer to su when I need to :-( --- Khetan Gajjar (!kg1779) * khetan@iafrica.com ; khetan@os.org.za http://www.os.org.za/~khetan * Talk/Finger khetan@chain.freebsd.os.org.za UUNET Internet Africa Support * FreeBSD enthusiast-www2.za.freebsd.org FreeBSD: Because rebooting is for adding new hardware To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 17:16:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15394 for freebsd-stable-outgoing; Thu, 13 Aug 1998 17:16:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15359; Thu, 13 Aug 1998 17:16:13 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA17635; Thu, 13 Aug 1998 17:15:44 -0700 (PDT) Message-Id: <199808140015.RAA17635@implode.root.com> To: peter@sirius.com cc: mrcpu@internetcds.com (Jaye Mathisen), hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: vmopar state in 2.2.7? In-reply-to: Your message of "Thu, 13 Aug 1998 11:34:00 PDT." <199808131834.LAA14961@staff.sirius.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 13 Aug 1998 17:15:44 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >We worked around a similar problem (processes left immortal, here in >the context of several processes [httpd] writing to the same NFS mounted >file [http log file]) by adjusting the timeout value from 0 (never) to >2 * hz (2 seconds). Details are posted as follow-up to kern/4588 in >FreeBSD.org's gnats problem report database. > >It looks like other parts of the kernel (here the vm subsystem) suffer >similar problems. It appears to me that an overly optimistic use of >tsleep() with both, interrupts disabled and time-out set to infinity, >leaves immortal yet paralyzed processes around. No, there's just a missing or unprotected wakeup() somewhere. >>From /usr/src/sys/vm/vm_object.c (a second, similar occurence around >line 1261): > > 1218 /* > 1219 * The busy flags are only cleared at > 1220 * interrupt -- minimize the spl transitions > 1221 */ > 1222 if ((p->flags & PG_BUSY) || p->busy) { > 1223 s = splvm(); > 1224 if ((p->flags & PG_BUSY) || p->busy) { > 1225 p->flags |= PG_WANTED; > 1226 tsleep(p, PVM, "vmopar", 0); > 1227 splx(s); > 1228 goto again; > 1229 } > 1230 splx(s); > 1231 } > >The code in line 1224 checks a condition to see whether somebody else >is already performing an operation on object p; in this case it wants >to ensure that a wakeup() for the following tsleep() is delivered by >setting a flag in line 1225. > >But what ensures that the world did not change between lines 1224 and >1225? Could the wakeup() happen after 1224 has determined to issue >the tsleep() but before the flagging in 1225 was registered? Then it >would be missed. Is this a race condition biting heavily hit machines? No. The wakeup occurs as a function of IO rundown which occurs in an interrupt context. The purpose of splvm() is to block interrupts to prevent the race condition. >Try changing lines 1226 and 1261 to something like: > tsleep(p, PVM, "vmopar", 5 * hz); > >>From the tsleep man page: > > Tsleep is the general sleep call. Suspends the current process until a > wakeup is performed on the specified identifier. The process will then > be made runnable with the specified priority. Sleeps at most timo / hz > seconds (0 means no timeout). If pri includes the PCATCH flag, signals > are checked before and after sleeping, else signals are not checked. Re- > turns 0 if awakened, EWOULDBLOCK if the timeout expires. If PCATCH is > set and a signal needs to be delivered, ERESTART is returned if the cur- > rent system call should be restarted if possible, and EINTR is returned > if the system call should be interrupted by the signal (return EINTR). > >This function would return "EWOULDBLOCK" after the time-out expires then, >no clue what that will do to your system or apps ;) -- I would expect the >blocked process to go away within 5 seconds... It would do bad things. There's a bug, but not there and that isn't the fix. I think this is another manifestation of the lack of NFSnode locking in the kernel, but that's just a guess. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 17:24:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16910 for freebsd-stable-outgoing; Thu, 13 Aug 1998 17:24:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16897; Thu, 13 Aug 1998 17:24:20 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA17790; Thu, 13 Aug 1998 17:23:38 -0700 (PDT) Message-Id: <199808140023.RAA17790@implode.root.com> To: Mike Smith cc: peter@sirius.com, mrcpu@internetcds.com (Jaye Mathisen), hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: vmopar state in 2.2.7? In-reply-to: Your message of "Thu, 13 Aug 1998 12:59:45 PDT." <199808131959.MAA00604@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 13 Aug 1998 17:23:38 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Try changing lines 1226 and 1261 to something like: >> tsleep(p, PVM, "vmopar", 5 * hz); >... >> This function would return "EWOULDBLOCK" after the time-out expires then, >> no clue what that will do to your system or apps ;) -- I would expect the >> blocked process to go away within 5 seconds... > >I dont' have 2.2 sources to hand, and the above is now just a call to >vm_page_sleep, but if the timeout expires, the entire operation is >retried, so it should be harmless (although it is masking a legitimate >bug). I said in my last reply on this that it would do bad things, but you're probably right that it should be harmless. There are other parts of the code where premature wakeups would be bad, so one must be careful about making this assumption. If that "fixes" the problem, then this probably indicates a problem with a missing wakeup somewhere. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 17:43:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19123 for freebsd-stable-outgoing; Thu, 13 Aug 1998 17:43:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA19118 for ; Thu, 13 Aug 1998 17:43:01 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 4256 invoked by uid 1003); 14 Aug 1998 00:42:19 -0000 Message-ID: <19980814024219.A22731@rucus.ru.ac.za> Date: Fri, 14 Aug 1998 02:42:19 +0200 From: Neil Blakey-Milner To: Khetan Gajjar Cc: stable@FreeBSD.ORG Subject: Re: su problem with freebsd 2.2.7-stable References: <19980813215130D.kaj@interbizz.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Khetan Gajjar on Thu, Aug 13, 1998 at 11:27:20PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu 1998-08-13 (23:27), Khetan Gajjar wrote: > I can sudo bash, and that works, but I'd still prefer to > su when I need to :-( Khetan, Are you su -m'ing? If not, try that. Or try -l if you're using -m. Also, does a ps show the new shell starting at all? Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 17:46:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19808 for freebsd-stable-outgoing; Thu, 13 Aug 1998 17:46:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19781; Thu, 13 Aug 1998 17:46:11 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id CAA05986; Fri, 14 Aug 1998 02:40:08 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id CAA13310; Fri, 14 Aug 1998 02:46:45 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id CAA10173; Fri, 14 Aug 1998 02:45:46 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Fri, 14 Aug 1998 02:45:46 +0200 (CEST) From: Stefan Bethke To: freebsd-stable@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: <1682190.3111854089@d254.promo.de> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1089576808-903055546=:9883" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1089576808-903055546=:9883 Content-Type: TEXT/PLAIN; charset=US-ASCII [ please followup technical discussions to -current. ] On Tue, 11 Aug 1998, Stefan Bethke wrote: > On Die, 11. Aug 1998 13:33 Uhr +0200 Thomas Gellekum > wrote: > > > I have run this program five times and it finished once. The other > > four occasions I got > > > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x18 > > fault code = supervisor write, page ot present > > instruction pointer = 0x8:0xf0126d21 > > stack pointer = 0x10:0xefbffe50 > > frame pointer = 0x10:0xefbffe74 > > 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 = 395 (crashbsd) > > interrupt mask = > > kernel: type 12 trap, code=0 > > Stopped at _sosend+0x391: movl $0, 0x18(%ebx) > > > > After saving the core dump and recompiling a few object files with -g: > > > #9 0xf01c0a37 in trap (frame={tf_es = -2147483632, tf_ds = -272695280, > > tf_edi = -272630136, tf_esi = -2147483648, tf_ebp = -272630156, > > tf_isp = -272630212, tf_ebx = 0, tf_edx = 2147483647, > > tf_ecx = -1073277766, tf_eax = 0, tf_trapno = 12, tf_err = 2, > > tf_eip = -267227871, tf_cs = 8, tf_eflags = 66198, tf_esp = 0, > > tf_ss = 1}) at ../../i386/i386/trap.c:324 > > #10 0xf0126d21 in sosend (so=0xf0937f00, addr=0x0, uio=0xefbffeb0, > > top=0x0, control=0xf06fff00, flags=0) at ../../kern/uipc_socket.c:432 > > Looking at kern/uipc_socket.c:sosend(), one can easily spot the problem > Because sosend() expects a MGET(m, M_WAIT, MT_DATA) to always succeed, it > pagefaults while trying to manipulate the non-allocated mbuf > (m->m_pkthdr.len at 0+0x18). > The solution would be either to make MGET() and MGETHRD() to always succeed > (or sleep indefinitly), or check the result of any of those calls (as many > callers already do). > This in both -stable and -current. I've made a simple patch to uipc_mbuf.c that makes sure M_GET() and M_GETHDR() always succeed when called with M_WAIT. The patch (attached) is against -current about 48 hrs ago. I've done a little testing (slightly modified version of the test program, also attached). It *seems* to work. I'd really appreciate comments from those more knowledgable... Cheers, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany --0-1089576808-903055546=:9883 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="m_retry.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: SW5kZXg6IHVpcGNfbWJ1Zi5jDQo9PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpS Q1MgZmlsZTogL2hvbWUvbmN2cy9zcmMvc3lzL2tlcm4vdWlwY19tYnVmLmMs dg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjM3DQpkaWZmIC11IC1yMS4zNyB1 aXBjX21idWYuYw0KLS0tIHVpcGNfbWJ1Zi5jCTE5OTgvMDcvMjcgMDM6NTk6 NDgJMS4zNw0KKysrIHVpcGNfbWJ1Zi5jCTE5OTgvMDgvMTQgMDA6MzQ6NTMN CkBAIC0yNTAsNiArMjUwLDcgQEANCiAJaW50IGksIHQ7DQogew0KIAlyZWdp c3RlciBzdHJ1Y3QgbWJ1ZiAqbTsNCisJc3RhdGljIGludCBoYXZlX3dhcm5l ZCA9IDA7DQogDQogCS8qDQogCSAqIE11c3Qgb25seSBkbyB0aGUgcmVjbGFp bSBpZiBub3QgaW4gYW4gaW50ZXJydXB0IGNvbnRleHQuDQpAQCAtMjY0LDkg KzI2NSwzMCBAQA0KIAl9IGVsc2Ugew0KIAkJaWYgKGkgPT0gTV9ET05UV0FJ VCkNCiAJCQltYnN0YXQubV9kcm9wcysrOw0KLQkJZWxzZQ0KLQkJCXBhbmlj KCJPdXQgb2YgbWJ1ZiBjbHVzdGVycyIpOw0KKwkJZWxzZSB7DQorCQkJaWYg KCFoYXZlX3dhcm5lZCkgew0KKwkJCQlwcmludGYgKCJPdXQgb2YgbWJ1ZnMg LS0gaW5jcmVhc2UgTUFYVVNFUlNcbiIpOw0KKwkJCQloYXZlX3dhcm5lZCA9 IDE7DQorCQkJfQ0KKwkJCS8qDQorCQkJICogQmVjYXVzZSB0aGUgY2FsbGVy IHBhc3NlZCBNX1dBSVQsIHdlJ3JlIGFsbG93ZWQgdG8NCisJCQkgKiB0c2xl ZXAoKS4NCisJCQkgKi8NCisJCQl3aGlsZSAobSA9PSBOVUxMKSB7DQorCQkJ CSh2b2lkKXRzbGVlcCgoY2FkZHJfdCkmbW1iZnJlZSwgUFNPQ0ssICJtbWJm cmVlIiwgMTAwKTsNCisJCQkJLyogWFhYIHdlIHNob3VsZCBkbyBzb21ldGhp bmcgd2l0aCB0aGUgcmV0dXJuIHZhbHVlPyAqLw0KKwkJCQltX3JlY2xhaW0o KTsNCisJCQkJTUdFVChtLCBpLCB0KTsNCisJCQl9DQorCQl9DQogCX0NCisN CisJLyogU2hvdWxkIGFub3RoZXIgY2FsbGVyIGNvbWUgYnkgYW5kIG1fcmVj bGFpbSgpIGFjdHVhbGx5DQorCSAqIGZyZWUnZCBzb21lIG1idWZzLCB3YWtl IHVwIHRoZSBvdGhlcnMgc2xlZXBpbmcuDQorCSAqLw0KKwlpZiAobW1iZnJl ZSkNCisJCXdha2V1cCAoJm1tYmZyZWUpOw0KKw0KIAlyZXR1cm4gKG0pOw0K IH0NCiANCkBAIC0yNzgsNiArMzAwLDcgQEANCiAJaW50IGksIHQ7DQogew0K IAlyZWdpc3RlciBzdHJ1Y3QgbWJ1ZiAqbTsNCisJc3RhdGljIGludCBoYXZl X3dhcm5lZCA9IDA7DQogDQogCS8qDQogCSAqIE11c3Qgb25seSBkbyB0aGUg cmVjbGFpbSBpZiBub3QgaW4gYW4gaW50ZXJydXB0IGNvbnRleHQuDQpAQCAt MjkyLDkgKzMxNSwzMCBAQA0KIAl9IGVsc2Ugew0KIAkJaWYgKGkgPT0gTV9E T05UV0FJVCkNCiAJCQltYnN0YXQubV9kcm9wcysrOw0KLQkJZWxzZQ0KLQkJ CXBhbmljKCJPdXQgb2YgbWJ1ZiBjbHVzdGVycyIpOw0KKwkJZWxzZSB7DQor CQkJaWYgKCFoYXZlX3dhcm5lZCkgew0KKwkJCQlwcmludGYgKCJPdXQgb2Yg bWJ1ZnMgLS0gaW5jcmVhc2UgTUFYVVNFUlNcbiIpOw0KKwkJCQloYXZlX3dh cm5lZCA9IDE7DQorCQkJfQ0KKwkJCS8qDQorCQkJICogQmVjYXVzZSB0aGUg Y2FsbGVyIHBhc3NlZCBNX1dBSVQsIHdlJ3JlIGFsbG93ZWQgdG8NCisJCQkg KiB0c2xlZXAoKS4NCisJCQkgKi8NCisJCQl3aGlsZSAobSA9PSBOVUxMKSB7 DQorCQkJCSh2b2lkKXRzbGVlcCgoY2FkZHJfdCkmbW1iZnJlZSwgUFNPQ0ss ICJtbWJmcmVlIiwgMTAwKTsNCisJCQkJLyogWFhYIHdlIHNob3VsZCBkbyBz b21ldGhpbmcgd2l0aCB0aGUgcmV0dXJuIHZhbHVlPyAqLw0KKwkJCQltX3Jl Y2xhaW0oKTsNCisJCQkJTUdFVChtLCBpLCB0KTsNCisJCQl9DQorCQl9DQog CX0NCisNCisJLyogU2hvdWxkIGFub3RoZXIgY2FsbGVyIGNvbWUgYnkgYW5k IG1fcmVjbGFpbSgpIGFjdHVhbGx5DQorCSAqIGZyZWUnZCBzb21lIG1idWZz LCB3YWtlIHVwIHRoZSBvdGhlcnMgc2xlZXBpbmcuDQorCSAqLw0KKwlpZiAo bW1iZnJlZSkNCisJCXdha2V1cCAoJm1tYmZyZWUpOw0KKw0KIAlyZXR1cm4g KG0pOw0KIH0NCiANCg== --0-1089576808-903055546=:9883 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="bsdbug.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: LyogY3Jhc2hic2QuYw0KKioNCioqIFRISVMgUFJPR1JBTSBDQVVTRVMgS0VS TkVMIFBBTklDIE9OIFNPTUUgU1lTVEVNUw0KKioNCioqIFVzYWdlOiBjcmFz aG1lIFstLWhhcmRlcl0NCioqDQoqKiAtLWhhcmRlciBvcHRpb24gY2F1c2Vz IHRoaXMgcHJvZ3JhbSB0byBsZWF2ZSBvcGVuZWQgZmlsZSBkZXNjcmlwdG9y cyBoYW5naW5nDQoqKiB0aHVzIGluY3JlYXNpbmcgdGhlIHByb2JhYmlsaXR5 IG9mIHRoZSBjcmFzaC4NCioqDQoqLw0KDQojaW5jbHVkZSA8c3RkaW8uaD4N CiNpbmNsdWRlIDxmY250bC5oPg0KI2luY2x1ZGUgPHVuaXN0ZC5oPg0KI2lu Y2x1ZGUgPGVycm5vLmg+DQojaW5jbHVkZSA8c3lzL3R5cGVzLmg+DQojaW5j bHVkZSA8c3lzL3VuLmg+DQojaW5jbHVkZSA8c3lzL3Vpby5oPg0KI2luY2x1 ZGUgPHN5cy9zb2NrZXQuaD4NCiNpbmNsdWRlIDxzeXMvd2FpdC5oPg0KDQpp bnQgbWFpbihpbnQgYXJnYyxjaGFyICoqYXJndikgew0KCWludCBoYXJkZXI9 MCwgcCwgbnByb2MsIGgsIGksIHNvY2tldGZkc1syXTsNCgljaGFyIGFbMTBd Ow0KCXN0cnVjdCBpb3ZlYyBpb3YxPXthLDF9Ow0KCXN0cnVjdCBjbXNnaGRy ICpjbTsNCglzdHJ1Y3QgbXNnaGRyIG1zZzsNCgljaGFyIGJidWZmZXJbc2l6 ZW9mKHN0cnVjdCBjbXNnaGRyKStzaXplb2YoaW50KSoyNF07DQoNCglpZihh cmdjPj0yJiYhc3RyY21wKGFyZ3ZbMV0sIi0taGFyZGVyIikpIGhhcmRlcj0x Ow0KDQoJbnByb2M9LTE7DQoJZm9yKGk9MDtpPDYwO2krKykgew0KCQlpZiAo KHA9Zm9yaygpKT09MCkgew0KCQkJaWYgKHNvY2tldHBhaXIoQUZfVU5JWCxT T0NLX1NUUkVBTSwwLHNvY2tldGZkcykpIHsNCgkJCQlwZXJyb3IoInNvY2tl dHBhaXIiKTsNCgkJCX0gZWxzZSB7DQoJCQkJY209KHN0cnVjdCBjbXNnaGRy KiliYnVmZmVyOw0KCQkJCWNtLT5jbXNnX2xldmVsPVNPTF9TT0NLRVQ7DQoJ CQkJY20tPmNtc2dfdHlwZT1TQ01fUklHSFRTOw0KCQkJCWNtLT5jbXNnX2xl bj1zaXplb2Yoc3RydWN0IGNtc2doZHIpK3NpemVvZihpbnQpOw0KCQkJCW1z Zy5tc2dfbmFtZT0oY2FkZHJfdCkwOw0KCQkJCW1zZy5tc2dfbmFtZWxlbj0w Ow0KCQkJCW1zZy5tc2dfZmxhZ3M9MDsNCgkJCQltc2cubXNnX2lvdj0maW92 MTsNCgkJCQltc2cubXNnX2lvdmxlbj0xOw0KCQkJCW1zZy5tc2dfY29udHJv bD0oY2FkZHJfdCljbTsNCgkJCQltc2cubXNnX2NvbnRyb2xsZW49Y20tPmNt c2dfbGVuOw0KCQkJCWlmICgocD1mb3JrKCkpID4gMCkgew0KCQkJCQljbG9z ZShzb2NrZXRmZHNbMF0pOw0KCQkJCQkqKGludCopKGJidWZmZXIrc2l6ZW9m KHN0cnVjdCBjbXNnaGRyKSk9b3BlbigiL2Rldi9udWxsIixPX1JET05MWSk7 DQoJCQkJCWZvcihpPTA7aTwyMDQ4O2krKykgew0KCQkJCQkJZnByaW50Zihz dGRvdXQsIiVkPiAiLGkrMSk7DQoJCQkJCQl3aGlsZShzZW5kbXNnKHNvY2tl dGZkc1sxXSwmbXNnLDApIT0xKSB7DQoJCQkJCQkJaWYoZXJybm8hPUVBR0FJ Tikgew0KCQkJCQkJCQlwZXJyb3IoIlxuc2VuZG1zZyIpOw0KCQkJCQkJCX0N CgkJCQkgCQl9DQoJCQkJIAl9DQoJCQkJfSBlbHNlIHsNCgkJCQkJaWYgKHAg PCAwKSB7DQoJCQkJCQlwZXJyb3IoImZvcmsiKTsNCgkJCQkJCWV4aXQgKDAp Ow0KCQkJCQl9DQoJCQkJCWNsb3NlKHNvY2tldGZkc1sxXSk7DQoJCQkJCWZv cihpPTA7aTwyMDQ4O2krKykgew0KCQkJCQkJKihpbnQqKShiYnVmZmVyK3Np emVvZihzdHJ1Y3QgY21zZ2hkcikpPS0xOw0KCQkJCQkJZnByaW50ZihzdGRv dXQsIj4lZCAiLGkrMSk7DQoJCQkJCQljbT0oc3RydWN0IGNtc2doZHIqKWJi dWZmZXI7DQoJCQkJCQljbS0+Y21zZ19sZXZlbD1TT0xfU09DS0VUOw0KCQkJ CQkJY20tPmNtc2dfdHlwZT1TQ01fUklHSFRTOw0KCQkJCQkJY20tPmNtc2df bGVuPXNpemVvZihzdHJ1Y3QgY21zZ2hkcikrc2l6ZW9mKGludCkqMjQ7DQoJ CQkJCQltc2cubXNnX25hbWU9KGNhZGRyX3QpMDsNCgkJCQkJCW1zZy5tc2df bmFtZWxlbj0wOw0KCQkJCQkJaW92MS5pb3ZfbGVuPTEwOw0KCQkJCQkJbXNn Lm1zZ19pb3Y9JmlvdjE7DQoJCQkJCQltc2cubXNnX2lvdmxlbj0xOw0KCQkJ CQkJbXNnLm1zZ19jb250cm9sPShjYWRkcl90KWNtOw0KCQkJCQkJbXNnLm1z Z19jb250cm9sbGVuPWNtLT5jbXNnX2xlbjsNCg0KCQkJCQkJaWYocmVjdm1z Zyhzb2NrZXRmZHNbMF0sJm1zZywwKSE9MSl7DQoJCQkJCSAJCXBlcnJvcigi XG5yZWN2bXNnIik7DQoJCQkJCSAJfSBlbHNlIHsNCgkJCQkJIAkJZnByaW50 ZihzdGRvdXQsIiglZCkgIiwqKGludCopKGJidWZmZXIrc2l6ZW9mKHN0cnVj dCBjbXNnaGRyKSkpOw0KCQkJCQkJIAlpZighaGFyZGVyKSB7DQoJCQkJCQkJ CWNsb3NlKCooaW50KikoYmJ1ZmZlcitzaXplb2Yoc3RydWN0IGNtc2doZHIp KSk7DQoJCQkJCQkJfQ0KCQkJCQkJfQ0KCQkJCQl9DQoJCQkJCWV4aXQoMCk7 DQoJCQkJfQ0KCQkJCXdhaXQoJmgpOw0KCQkJfQ0KCQkJZXhpdCgwKTsNCgkJ fSBlbHNlIHsNCgkJCWlmKHA8MCkgew0KCQkJCW5wcm9jPWk7DQoJCQkJYnJl YWs7DQoJCQl9DQoJCX0NCgl9DQoJaWYobnByb2M8MCkNCgkJbnByb2M9NjA7 DQoJZm9yKGk9MDtpPG5wcm9jO2krKykgDQoJCXdhaXQoJmgpOw0KCWZwcmlu dGYoc3RkZXJyLCJcbiVkIHByb2Nlc3NlcyBmaW5pc2hlZFxuIixucHJvYyk7 DQoJcmV0dXJuIDA7DQp9DQo= --0-1089576808-903055546=:9883-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 18:42:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27490 for freebsd-stable-outgoing; Thu, 13 Aug 1998 18:42:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27474 for ; Thu, 13 Aug 1998 18:42:07 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA04505 for ; Fri, 14 Aug 1998 11:11:25 +0930 (CST) Message-Id: <199808140141.LAA04505@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: stable@FreeBSD.ORG Subject: Adaptec 7895? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 11:11:25 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was wondering if FreeBSD had support for the 7895, which is an on-board SCSI controller with 1 Ultra SCSI channel and 2 Ultra Wide SCSI channels. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 19:22:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02934 for freebsd-stable-outgoing; Thu, 13 Aug 1998 19:22:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02922 for ; Thu, 13 Aug 1998 19:22:21 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA04833; Fri, 14 Aug 1998 11:51:50 +0930 (CST) Message-Id: <199808140221.LAA04833@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: stable@FreeBSD.ORG Subject: Re: Adaptec 7895? In-reply-to: Your message of "Fri, 14 Aug 1998 11:11:25 +0930." <199808140141.LAA04505@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 11:51:50 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was wondering if FreeBSD had support for the 7895, which is an on-board > SCSI controller with 1 Ultra SCSI channel and 2 Ultra Wide SCSI channels. Well, to answer my own question, no it doesn't :-/ Hmm.. it appears as 2 controllers. I tried tricking the driver, by adding the PCI ID to its list of know ID's, but (big suprise) that didn't work. If anyone has some info on these, or (even better) has some patches, I'd be interested :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 19:27:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03501 for freebsd-stable-outgoing; Thu, 13 Aug 1998 19:27:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03481; Thu, 13 Aug 1998 19:27:52 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id TAA25648; Thu, 13 Aug 1998 19:27:21 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd025613; Thu Aug 13 19:27:16 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id TAA25476; Thu, 13 Aug 1998 19:27:05 -0700 (MST) From: Terry Lambert Message-Id: <199808140227.TAA25476@usr02.primenet.com> Subject: Re: vmopar state in 2.2.7? To: dg@root.com Date: Fri, 14 Aug 1998 02:27:05 +0000 (GMT) Cc: mike@smith.net.au, peter@sirius.com, mrcpu@internetcds.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199808140023.RAA17790@implode.root.com> from "David Greenman" at Aug 13, 98 05:23:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Try changing lines 1226 and 1261 to something like: > >> tsleep(p, PVM, "vmopar", 5 * hz); > >... > >> This function would return "EWOULDBLOCK" after the time-out expires then, > >> no clue what that will do to your system or apps ;) -- I would expect the > >> blocked process to go away within 5 seconds... > > > >I dont' have 2.2 sources to hand, and the above is now just a call to > >vm_page_sleep, but if the timeout expires, the entire operation is > >retried, so it should be harmless (although it is masking a legitimate > >bug). > > I said in my last reply on this that it would do bad things, but you're > probably right that it should be harmless. There are other parts of the code > where premature wakeups would be bad, so one must be careful about making > this assumption. > If that "fixes" the problem, then this probably indicates a problem with > a missing wakeup somewhere. It will do bad things. Or rather, it will increase the frequency of bad things; the code itself is broken. I have sent them patches, which are wrong because I neglected the non-increment case. If it sleeps on the first iteration, the page will be bogusly freed twice. 8-(. This may very well be the nasty VM bug no one has fixed... Here is the analysis I sent them, which is correct: ----------------------------------------------------------------------------- > But what ensures that the world did not change between lines 1224 and > 1225? Could the wakeup() happen after 1224 has determined to issue > the tsleep() but before the flagging in 1225 was registered? Then it > would be missed. Is this a race condition biting heavily hit machines? There is a race condition here, but only for SMP systems. Since this is vm_object.c from the 2.2.x stream, it will never hit. If the process is in the kernel, the only way for the kernel to be reentered is via interrupt. Since this code is never called at interrupt level (it's in vm_object_page_remove()), it will never be reentered. FreeBSD, unfortunately, does not support kernel preemption (it's necessary for hard realtime, which is why it's unfortunate). Basically, the race that would exist in the SMP case, if the code was even vaguely similar under 3.x, is between 1222 and 1223; there is no race between 1224 and 1225, since the vm_page object p is present and buys, and the flags modification occurs at splvm. Timing out the tsleep would certianly be harmless; I would expect it to do nothing in the 1226 case. That is, if you ever hit a condition where this was an issue, you would merely increase the size of your infinite loop. In the second case, 1261, the consequences could be bad. In fact, the consequences of sleeping at all could be bad. The reason it seems to work around the problem for you is that the page causing the problem is not the first page on the list and start has been incremented. Because start is not decremented before the "goto again", the calculation on line 1207: again: size = end - start; if (size > 4 || size >= object->size / 4) { Bogusly omits the page which was just obtained. This means that vm_page_protect(p, VM_PROT_NONE); PAGE_WAKEUP(p); vm_page_free(p); is never called. The net result is that pages are left hanging out in space, but the system thinks they have been reclaimed. ----------------------------------------------------------------------------- Here is a patch for 3.1, which has the same bug; I didn't change the while to a for because I still need to know if start was incremented: ----------------------------------------------------------------------------- *** vm_object.c Thu May 21 07:47:58 1998 --- vm_object.c.good Fri Aug 14 02:08:15 1998 *************** *** 1348,1353 **** --- 1348,1354 ---- } } } else { + s = 0; while (size > 0) { if ((p = vm_page_lookup(object, start)) != 0) { *************** *** 1356,1361 **** --- 1357,1363 ---- vm_page_protect(p, VM_PROT_NONE); start += 1; size -= 1; + s = 1; continue; } *************** *** 1363,1376 **** * The busy flags are only cleared at * interrupt -- minimize the spl transitions */ ! if (vm_page_sleep(p, "vmopar", &p->busy)) goto again; if (clean_only && p->valid) { vm_page_test_dirty(p); if (p->valid & p->dirty) { start += 1; size -= 1; continue; } } --- 1365,1381 ---- * The busy flags are only cleared at * interrupt -- minimize the spl transitions */ ! if (vm_page_sleep(p, "vmopar", &p->busy)) { ! start -= s; goto again; + } if (clean_only && p->valid) { vm_page_test_dirty(p); if (p->valid & p->dirty) { start += 1; size -= 1; + s = 1; continue; } } *************** *** 1381,1386 **** --- 1386,1392 ---- } start += 1; size -= 1; + s = 1; } } vm_object_pip_wakeup(object); ----------------------------------------------------------------------------- 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-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 22:04:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20850 for freebsd-stable-outgoing; Thu, 13 Aug 1998 22:04:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20842 for ; Thu, 13 Aug 1998 22:04:44 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id OAA06251 for ; Fri, 14 Aug 1998 14:34:14 +0930 (CST) Message-Id: <199808140504.OAA06251@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: stable@FreeBSD.ORG Subject: Adaptec Controller (following up my previous 2 posts) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 14:34:14 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here I am answering my own email _again_ It seems CAM has support for the 7895, so I'll try that.. Sorry for the noise =) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 22:28:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23163 for freebsd-stable-outgoing; Thu, 13 Aug 1998 22:28:46 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23158 for ; Thu, 13 Aug 1998 22:28:45 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca1-94.ix.netcom.com [209.109.232.94]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id WAA29848; Thu, 13 Aug 1998 22:28:17 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id WAA12863; Thu, 13 Aug 1998 22:28:14 -0700 (PDT) Date: Thu, 13 Aug 1998 22:28:14 -0700 (PDT) Message-Id: <199808140528.WAA12863@silvia.hip.berkeley.edu> To: wheelman@nuc.net CC: freebsd-stable@FreeBSD.ORG In-reply-to: <000201bdc6e0$c61ff900$313d31cc@electron.nuc.net> (wheelman@nuc.net) Subject: Re: Questions about Port fixes From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * While updating PERL as well as the modules I use with PERL, I realized * that a few of the ports are broken (won't install at all), have invalid * PLIST's, old version or something else that isn't allowing the port to * install correctly (or deinstall correctly) ... I have make fixes to the * following to bring them up to date: * * p5-SNMP * p5-Mail-Tools * p5-MIME-Base64 * * I also noticed that there are a few others that, while install and * deinstall work correctly, rely on the PERL version being 5.005. While this * is minor, I would assume using %%PERL_VER%% would be preferable in the * PLIST file? Absolutely. Those were `fixed' before we could decide what to do with the perl version stuff. * I have the files ready to go if anyone's wants them. (Obviously, I don't * have CVS access, nor do I feel comfortable getting into that sort of thing * right now ) Be careful what you wish for.... :) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 23:13:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28140 for freebsd-stable-outgoing; Thu, 13 Aug 1998 23:13:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from link.cpt.nsc.iafrica.com (link.cpt.nsc.iafrica.com [196.31.1.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28110 for ; Thu, 13 Aug 1998 23:13:40 -0700 (PDT) (envelope-from khetan@link.freebsd.os.org.za) X-Disclaimer: Contents of this e-mail are the writer's opinion X-Disclaimer2: and may not be quoted, re-produced or forwarded X-Disclaimer3: (in part or whole) without the author's permission. Received: from localhost (khetan@localhost) by link.cpt.nsc.iafrica.com (8.9.1+3.0W/8.9.1) with SMTP id IAA28454; Fri, 14 Aug 1998 08:12:57 +0200 (SAT) (envelope-from khetan@link.freebsd.os.org.za) Date: Fri, 14 Aug 1998 08:12:57 +0200 (SAT) From: Khetan Gajjar X-Sender: khetan@link.cpt.nsc.iafrica.com Reply-To: Khetan Gajjar To: Neil Blakey-Milner cc: stable@FreeBSD.ORG Subject: Re: su problem with freebsd 2.2.7-stable In-Reply-To: <19980814024219.A22731@rucus.ru.ac.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Aug 1998, Neil Blakey-Milner wrote: >Are you su -m'ing? If not, try that. Or try -l if you're using -m. Also, >does a ps show the new shell starting at all? No, ps doesn't show the new shell starting at all. The su process just grows in size until it seg faults (appears to hit a login.conf problem). My login.conf is stock standard, and my limits are : 1=[khetan@chain] ~$ su Segmentation fault 2=[khetan@chain] ~$ su -m Segmentation fault 3=[khetan@chain] ~$ su -l Segmentation fault 4=[khetan@chain] ~$ ulimit -a core file size (blocks) unlimited data seg size (kbytes) 22528 file size (blocks) unlimited max locked memory (kbytes) 10240 max memory size (kbytes) 30720 open files 64 pipe size (512 bytes) 1 stack size (kbytes) 8192 cpu time (seconds) unlimited max user processes 64 virtual memory (kbytes) 30720 --- Khetan Gajjar (!kg1779) * khetan@iafrica.com ; khetan@os.org.za http://www.os.org.za/~khetan * Talk/Finger khetan@chain.freebsd.os.org.za UUNET Internet Africa Support * FreeBSD enthusiast-www2.za.freebsd.org FreeBSD: Because rebooting is for adding new hardware To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 13 23:31:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01703 for freebsd-stable-outgoing; Thu, 13 Aug 1998 23:31:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from link.cpt.nsc.iafrica.com (link.cpt.nsc.iafrica.com [196.31.1.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01694 for ; Thu, 13 Aug 1998 23:31:38 -0700 (PDT) (envelope-from khetan@link.freebsd.os.org.za) X-Disclaimer: Contents of this e-mail are the writer's opinion X-Disclaimer2: and may not be quoted, re-produced or forwarded X-Disclaimer3: (in part or whole) without the author's permission. Received: from localhost (khetan@localhost) by link.cpt.nsc.iafrica.com (8.9.1+3.0W/8.9.1) with SMTP id IAA28816 for ; Fri, 14 Aug 1998 08:31:01 +0200 (SAT) (envelope-from khetan@link.freebsd.os.org.za) Date: Fri, 14 Aug 1998 08:30:59 +0200 (SAT) From: Khetan Gajjar X-Sender: khetan@link.cpt.nsc.iafrica.com Reply-To: Khetan Gajjar To: stable@FreeBSD.ORG Subject: Re: su problem with freebsd 2.2.7-stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Aug 1998, Khetan Gajjar wrote: >On Fri, 14 Aug 1998, Neil Blakey-Milner wrote: > >>Are you su -m'ing? If not, try that. Or try -l if you're using -m. Also, >>does a ps show the new shell starting at all? The problem appears to be related to kerberos. I nulled the /etc/kerberosIV directory, and it started segfaulting. I put back the entries, and now it works fine. Any idea how to get a "empty" kerberosIV configuration, but still have the libraries installed in case I ever need to use it (I need to occasionally). --- Khetan Gajjar (!kg1779) * khetan@iafrica.com ; khetan@os.org.za http://www.os.org.za/~khetan * Talk/Finger khetan@chain.freebsd.os.org.za UUNET Internet Africa Support * FreeBSD enthusiast-www2.za.freebsd.org FreeBSD: Because rebooting is for adding new hardware To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 00:17:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08526 for freebsd-stable-outgoing; Fri, 14 Aug 1998 00:17:39 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08497 for ; Fri, 14 Aug 1998 00:17:30 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id DAA00465; Fri, 14 Aug 1998 03:16:12 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Daniel O'Connor" cc: stable@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Adaptec 7895? In-reply-to: Your message of "Fri, 14 Aug 1998 11:11:25 +0930." <199808140141.LAA04505@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 03:16:11 -0400 Message-ID: <462.903078971@gjp.erols.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel O'Connor" wrote in message ID <199808140141.LAA04505@cain.gsoft.com.au>: > Hi, > I was wondering if FreeBSD had support for the 7895, which is an on-board > SCSI controller with 1 Ultra SCSI channel and 2 Ultra Wide SCSI channels. You need to get the CAM patches from ftp://ftp.freebsd.org/pub/FreeBSD/CAM for the 7895 chips to work. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 01:02:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16210 for freebsd-stable-outgoing; Fri, 14 Aug 1998 01:02:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16205; Fri, 14 Aug 1998 01:02:23 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.7/8.7.3) with SMTP id BAA18050; Fri, 14 Aug 1998 01:01:43 -0700 (PDT) Date: Fri, 14 Aug 1998 01:01:43 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: David Greenman cc: peter@sirius.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: More info: Re: vmopar state in 2.2.7? In-Reply-To: <199808140015.RAA17635@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a tad more info that may shed some light. After much wailing and gnashing of teeth, I realized I had copied my INN 2.1 config files built on a 3.0 box to a 2.2 box, and one of the settings was to mmap() the overview files. mmap() for the active file has always had problems with file truncation under the 2.2.x series, as has been well documented. I'm suspicious that mmap() on an NFS mounted file is the culprit here more than anythingelse. Changing it to not mmap() the overfile seems to have corrected the problem, at least so far. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 03:08:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29811 for freebsd-stable-outgoing; Fri, 14 Aug 1998 03:08:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29803 for ; Fri, 14 Aug 1998 03:08:06 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id MAA17602; Fri, 14 Aug 1998 12:07:37 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 14 Aug 1998 12:07:36 +0200 (MET DST) Mime-Version: 1.0 To: Mail Handler Cc: freebsd-stable@FreeBSD.ORG Subject: Re: none References: <3.0.5.32.19980813172702.01091c50@pop.channel1.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 14 Aug 1998 12:07:36 +0200 In-Reply-To: Mail Handler's message of "Thu, 13 Aug 1998 17:27:02 -0400" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA29807 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mail Handler writes: > I posted this make world problem about 3 weeks ago to -stable and c.u.b.f.m > and received no response: Because nobody else is seeing this. The obvious thing to do is try to find out *why* make world fails instead of just blowing everything away, don't you think? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 04:48:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10245 for freebsd-stable-outgoing; Fri, 14 Aug 1998 04:48:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10240; Fri, 14 Aug 1998 04:48:13 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA23436; Fri, 14 Aug 1998 04:47:10 -0700 (PDT) Message-Id: <199808141147.EAA23436@implode.root.com> To: Terry Lambert cc: mike@smith.net.au, peter@sirius.com, mrcpu@internetcds.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: vmopar state in 2.2.7? In-reply-to: Your message of "Fri, 14 Aug 1998 02:27:05 -0000." <199808140227.TAA25476@usr02.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 14 Aug 1998 04:47:10 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In the second case, 1261, the consequences could be bad. In fact, >the consequences of sleeping at all could be bad. The reason it >seems to work around the problem for you is that the page causing >the problem is not the first page on the list and start has been >incremented. Because start is not decremented before the "goto again", >the calculation on line 1207: > > again: > size = end - start; > if (size > 4 || size >= object->size / 4) { > >Bogusly omits the page which was just obtained. This means that > > vm_page_protect(p, VM_PROT_NONE); > PAGE_WAKEUP(p); > vm_page_free(p); > >is never called. > >The net result is that pages are left hanging out in space, but the system >thinks they have been reclaimed. Err, it doesn't "omit the page which was just obtained". First off, pages aren't obtained; all that happens is a pointer to them is gotten - they are still on the object page list. For optimal performance, there are two ways that the code will traverse the resident pages in the object. The first is the case where the object either contains a small number of pages or if all the pages should be removed. In this case, it just accesses the unsorted object resident page list. Since this list contains all of the pages in a resident object, the code must check the offset of the pages to ensure that they are within the proper range that is being removed. Pages that are wired or dirty are skipped. If while doing this a busy page is encountered, then the system must wait for the page to become not busy. While sleeping, the order of pages might have changed in the list, however, so it is necessary to start over again from the beginning of the object page list. "start" isn't and can't be updated since the order of pages that are removed is random. The second method is to look up the page on the object page hash list. This has somewhat higher overhead, but is more efficient when dealing with a small number of pages in an object that has a large number of resident pages. Since in this case we process the pages sequentially in the start to end range, we can increment start as each page is removed (or skipped as the case may be). If the page is busy, then start isn't incremented and thus the 'goto again' will begin with the page which was just slept on. Once again, the bug isn't in the code there. The effects that have been described suggest a missing wakeup. I believe the attached patches should fix the problem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project Index: nfs/nfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_bio.c,v retrieving revision 1.28.2.7 diff -c -r1.28.2.7 nfs_bio.c *** nfs_bio.c 1998/01/28 00:26:54 1.28.2.7 --- nfs_bio.c 1998/08/14 11:42:02 *************** *** 131,136 **** --- 131,140 ---- m->flags |= PG_BUSY; m->busy--; + if (m->busy == 0 && (m->flags & PG_WANTED)) { + m->flags &= ~PG_WANTED; + wakeup(m); + } if (error && (auio.uio_resid == MAXBSIZE)) return VM_PAGER_ERROR; Index: vm/vnode_pager.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vnode_pager.c,v retrieving revision 1.65.2.2 diff -c -r1.65.2.2 vnode_pager.c *** vnode_pager.c 1997/05/28 18:26:46 1.65.2.2 --- vnode_pager.c 1998/08/14 11:43:06 *************** *** 963,970 **** if (i < ncount) { rtvals[i] = VM_PAGER_OK; } ! if ((m[i]->busy == 0) && (m[i]->flags & PG_WANTED)) wakeup(m[i]); } return rtvals[0]; } --- 963,972 ---- if (i < ncount) { rtvals[i] = VM_PAGER_OK; } ! if ((m[i]->busy == 0) && (m[i]->flags & PG_WANTED)) { ! m[i]->flags &= ~PG_WANTED; wakeup(m[i]); + } } return rtvals[0]; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 05:32:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15537 for freebsd-stable-outgoing; Fri, 14 Aug 1998 05:32:55 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.ukconnect.net (mail.ukconnect.net [195.219.13.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA15531 for ; Fri, 14 Aug 1998 05:32:53 -0700 (PDT) (envelope-from phil@virtek.com) Received: from gsi.ukconnect.net (gsi.ukconnect.net [195.219.13.179]) by mail.virtek.com (NTMail 3.03.0017/1.aa3h) with ESMTP id ea012120 for ; Fri, 14 Aug 1998 12:30:27 +0100 Message-Id: <3.0.3.32.19980814133144.00f06574@mail.virtek.com> X-Sender: phil@mail.virtek.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 14 Aug 1998 13:31:44 +0100 To: freebsd-stable@FreeBSD.ORG From: Phil Allsopp Subject: 3COM ethernet cards 3c905b-tx Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I used to succesfully use 3Com 3c905 cards in a FreeBSD 2.2.5 box as vx0 but the new 3COM 3c905b-tx cards don't work and unfortunately every supplier now only supplies the 3c905b-tx cards. Has anyone got the 3C905b-tx cards to succesfully work under 2.2.5 and if so how ? Regards Phil. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 07:30:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03430 for freebsd-stable-outgoing; Fri, 14 Aug 1998 07:30:39 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from enya.hilink.com.au (enya.hilink.com.au [203.8.14.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03425 for ; Fri, 14 Aug 1998 07:30:36 -0700 (PDT) (envelope-from danny@enya.hilink.com.au) Received: from localhost (danny@localhost) by enya.hilink.com.au (8.8.8/8.8.7) with SMTP id AAA04223; Sat, 15 Aug 1998 00:30:06 +1000 (EST) (envelope-from danny@enya.hilink.com.au) Date: Sat, 15 Aug 1998 00:30:06 +1000 (EST) From: "Daniel O'Callaghan" Reply-To: "Daniel O'Callaghan" To: Phil Allsopp cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3COM ethernet cards 3c905b-tx In-Reply-To: <3.0.3.32.19980814133144.00f06574@mail.virtek.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Aug 1998, Phil Allsopp wrote: > I used to succesfully use 3Com 3c905 cards in a FreeBSD 2.2.5 box as vx0 but > the new 3COM 3c905b-tx cards don't work and unfortunately every > supplier now only supplies the 3c905b-tx cards. > Has anyone got the 3C905b-tx cards to succesfully work under 2.2.5 > and if so how ? The tx will never work under 2.2.5. It needs a new version of the vx driver, which is under development, and has been for some time. I don't hold out hopes that the new vx driver will make it into 2.2.8!!! Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 07:49:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05940 for freebsd-stable-outgoing; Fri, 14 Aug 1998 07:49:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.ukconnect.net (mail.ukconnect.net [195.219.13.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA05931 for ; Fri, 14 Aug 1998 07:49:05 -0700 (PDT) (envelope-from phil@virtek.com) Received: from gsi.ukconnect.net (gsi.ukconnect.net [195.219.13.179]) by mail.virtek.com (NTMail 3.03.0017/1.aa3h) with ESMTP id ka012126 for ; Fri, 14 Aug 1998 14:47:06 +0100 Message-Id: <3.0.3.32.19980814154822.00dbb794@mail.virtek.com> X-Sender: phil@mail.virtek.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 14 Aug 1998 15:48:22 +0100 To: "Daniel O'Callaghan" From: Phil Allsopp Subject: Re: 3COM ethernet cards 3c905b-tx Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.19980814133144.00f06574@mail.virtek.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:30 AM 8/15/98 +1000, you wrote: > > >On Fri, 14 Aug 1998, Phil Allsopp wrote: > >> I used to succesfully use 3Com 3c905 cards in a FreeBSD 2.2.5 box as vx0 but >> the new 3COM 3c905b-tx cards don't work and unfortunately every >> supplier now only supplies the 3c905b-tx cards. >> Has anyone got the 3C905b-tx cards to succesfully work under 2.2.5 >> and if so how ? > >The tx will never work under 2.2.5. It needs a new version of the vx >driver, which is under development, and has been for some time. >I don't hold out hopes that the new vx driver will make it into 2.2.8!!! Ok, worth a try and thanks for the help.. Regards Phil. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 08:05:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07940 for freebsd-stable-outgoing; Fri, 14 Aug 1998 08:05:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07933 for ; Fri, 14 Aug 1998 08:05:19 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id RAA29734; Fri, 14 Aug 1998 17:04:30 +0200 (CEST) Received: from localhost (blaz@localhost) by gold.amis.net (8.8.8/8.8.8) with SMTP id RAA02399; Fri, 14 Aug 1998 17:04:37 +0200 (CEST) Date: Fri, 14 Aug 1998 17:04:37 +0200 (CEST) From: Blaz Zupan To: Phil Allsopp cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3COM ethernet cards 3c905b-tx In-Reply-To: <3.0.3.32.19980814133144.00f06574@mail.virtek.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Has anyone got the 3C905b-tx cards to succesfully work under 2.2.5 > and if so how ? Go to http://www.freebsd.org/~wpaul/3Com and install the driver that is available there. Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 08:29:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11705 for freebsd-stable-outgoing; Fri, 14 Aug 1998 08:29:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from lepton.nuc.net (lepton.nuc.net [204.49.61.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11696; Fri, 14 Aug 1998 08:29:14 -0700 (PDT) (envelope-from wheelman@nuc.net) Received: from electron.nuc.net (dhcp1.nuc.net [204.49.61.49]) by lepton.nuc.net (8.8.8/8.7.3) with SMTP id KAA09676; Fri, 14 Aug 1998 10:28:46 -0500 (CDT) From: "Jaime Bozza" To: "Satoshi Asami" Cc: Subject: RE: Questions about Port fixes Date: Fri, 14 Aug 1998 10:27:05 -0500 Message-ID: <000601bdc797$fe226ce0$313d31cc@electron.nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-Reply-To: <199808140528.WAA12863@silvia.hip.berkeley.edu> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * is minor, I would assume using %%PERL_VER%% would be preferable in the > * PLIST file? > > Absolutely. Those were `fixed' before we could decide what to do with > the perl version stuff. Ok, good enough explanation. I'll remember that for the future. (That's how I fixed the ones I did yesterday) > * have CVS access, nor do I feel comfortable getting into that > sort of thing > * right now ) > > Be careful what you wish for.... :) Hmmm... Sounds like I might want to start reading more on cvs. :) Jaime Bozza Nucleus Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 08:38:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13016 for freebsd-stable-outgoing; Fri, 14 Aug 1998 08:38:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wankers.net (user-38lc99b.dialup.mindspring.com [209.86.37.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13010 for ; Fri, 14 Aug 1998 08:38:16 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost.mindspring.com [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id LAA20110; Fri, 14 Aug 1998 11:15:33 -0400 (EDT) (envelope-from dex@wankers.net) Date: Fri, 14 Aug 1998 11:15:32 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: "Daniel O'Callaghan" cc: Phil Allsopp , freebsd-stable@FreeBSD.ORG Subject: Re: 3COM ethernet cards 3c905b-tx In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, if you want some help with it, and Phil has some spare cards, and I can get the docs and specs on the cards, I'll help out with that, too (why do I get the feeling I'm going to be renamed driver-boy). I did a bunch of network card/driver testing and benchmarking at Sun, so I've kinda been there, done that *sigh*. I'm perfectly willing to help :) -Jon On Sat, 15 Aug 1998, Daniel O'Callaghan wrote: > > > On Fri, 14 Aug 1998, Phil Allsopp wrote: > > > I used to succesfully use 3Com 3c905 cards in a FreeBSD 2.2.5 box as vx0 but > > the new 3COM 3c905b-tx cards don't work and unfortunately every > > supplier now only supplies the 3c905b-tx cards. > > Has anyone got the 3C905b-tx cards to succesfully work under 2.2.5 > > and if so how ? > > The tx will never work under 2.2.5. It needs a new version of the vx > driver, which is under development, and has been for some time. > I don't hold out hopes that the new vx driver will make it into 2.2.8!!! > > Danny > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 08:54:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14873 for freebsd-stable-outgoing; Fri, 14 Aug 1998 08:54:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ucthpx.uct.ac.za (ucthpx.uct.ac.za [137.158.128.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14868 for ; Fri, 14 Aug 1998 08:54:54 -0700 (PDT) (envelope-from dks@its.uct.ac.za) Received: from dks.its.uct.ac.za ([137.158.27.4] helo=its.uct.ac.za) by ucthpx.uct.ac.za with esmtp (Exim 2.01 #2) for freebsd-stable@freebsd.org id 0z7MBH-0006if-00; Fri, 14 Aug 1998 17:54:19 +0200 Message-ID: <35D45D09.CA73E188@its.uct.ac.za> Date: Fri, 14 Aug 1998 17:51:37 +0200 From: Daniel Smith X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Wide to Narrow conversion on ncr0? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We're getting errors installing 2.2.7-RELEASE onto a SD39173W 9Gb Baracuda plugged onto a Symbios 53C876e narrow bus with a wide-to-narrow converter (the economics of scale - we had to get another 4 of them anyway :-) The ncr driver picks up as two 53c875 buses as expected but then appears to try using the Baracuda in wide mode (possibly due to negotiation responses from the drive?) (The disk verifies fine and *wince* Windows 95 can boot OK...) The last two errors before a long pause are... sd4(ncr1:0:0): COMMAND FAILED (9 ff) 0f12b0000. ncr1: aborting job ncr1:0: ERROR (90:0) (8-a6-0) (0/5) @ (script a0:43000060). ncr1: script cmd = 078ab0000 ncr1: regdump: da 00 00 05 47 00 00 0f 71 08 00 a6 80 00 00 02. ncr1: restart (fatal error). sd4(ncr1:0:0): COMMAND FAILED (9 ff) 0f12b0000. sd4 could not mode sense(4). Using fictitious geometry 0MB (0 512 byte sectors) ncr1: aborting job Any help most appreciated Cheers, Daniel. ----------------------------------------------------------- Daniel Smith Senior Systems Software Programmer University of Cape Town Systems Administrator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 09:37:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21712 for freebsd-stable-outgoing; Fri, 14 Aug 1998 09:37:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from word.smith.net.au (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21694 for ; Fri, 14 Aug 1998 09:37:56 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id JAA13061; Fri, 14 Aug 1998 09:35:45 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808140935.JAA13061@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Callaghan" cc: Phil Allsopp , freebsd-stable@FreeBSD.ORG Subject: Re: 3COM ethernet cards 3c905b-tx In-reply-to: Your message of "Sat, 15 Aug 1998 00:30:06 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 09:35:44 +0000 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Fri, 14 Aug 1998, Phil Allsopp wrote: > > > I used to succesfully use 3Com 3c905 cards in a FreeBSD 2.2.5 box as vx0 but > > the new 3COM 3c905b-tx cards don't work and unfortunately every > > supplier now only supplies the 3c905b-tx cards. > > Has anyone got the 3C905b-tx cards to succesfully work under 2.2.5 > > and if so how ? > > The tx will never work under 2.2.5. It needs a new version of the vx > driver, which is under development, and has been for some time. > I don't hold out hopes that the new vx driver will make it into 2.2.8!!! The xl driver, which is what you're talking about, will definitely be in 2.2.8. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 09:40:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22409 for freebsd-stable-outgoing; Fri, 14 Aug 1998 09:40:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from word.smith.net.au (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22391 for ; Fri, 14 Aug 1998 09:40:42 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id JAA13084; Fri, 14 Aug 1998 09:38:44 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808140938.JAA13084@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Daniel Smith cc: freebsd-stable@FreeBSD.ORG Subject: Re: Wide to Narrow conversion on ncr0? In-reply-to: Your message of "Fri, 14 Aug 1998 17:51:37 +0200." <35D45D09.CA73E188@its.uct.ac.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 09:38:43 +0000 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Drop into the BIOS on the card and set the device(s) in question to 8-bit mode. > > We're getting errors installing 2.2.7-RELEASE onto a SD39173W 9Gb > Baracuda plugged onto a Symbios 53C876e narrow bus with a wide-to-narrow > converter (the economics of scale - we had to get another 4 of them > anyway :-) > > The ncr driver picks up as two 53c875 buses as expected but then appears > to try using the Baracuda in wide mode (possibly due to negotiation > responses from the drive?) > > (The disk verifies fine and *wince* Windows 95 can boot OK...) > > The last two errors before a long pause are... > > sd4(ncr1:0:0): COMMAND FAILED (9 ff) 0f12b0000. > ncr1: aborting job > ncr1:0: ERROR (90:0) (8-a6-0) (0/5) @ (script a0:43000060). > ncr1: script cmd = 078ab0000 > ncr1: regdump: da 00 00 05 47 00 00 0f 71 08 00 a6 80 00 00 02. > ncr1: restart (fatal error). > > sd4(ncr1:0:0): COMMAND FAILED (9 ff) 0f12b0000. > sd4 could not mode sense(4). Using fictitious geometry > 0MB (0 512 byte sectors) > ncr1: aborting job > > Any help most appreciated > > Cheers, > > Daniel. > > ----------------------------------------------------------- > Daniel Smith Senior Systems Software Programmer > University of Cape Town Systems Administrator > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 09:42:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22877 for freebsd-stable-outgoing; Fri, 14 Aug 1998 09:42:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22784 for ; Fri, 14 Aug 1998 09:42:06 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA06248; Fri, 14 Aug 1998 09:41:32 -0700 (PDT) (envelope-from jdp) Message-Id: <199808141641.JAA06248@austin.polstra.com> To: stable@FreeBSD.ORG Subject: Re: Adaptec 7895? In-Reply-To: <462.903078971@gjp.erols.com> References: <462.903078971@gjp.erols.com> Organization: Polstra & Co., Seattle, WA Cc: doconnor@gsoft.com.au Date: Fri, 14 Aug 1998 09:41:31 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <462.903078971@gjp.erols.com>, Gary Palmer wrote: > You need to get the CAM patches from ftp://ftp.freebsd.org/pub/FreeBSD/CAM for > the 7895 chips to work. Yes, with CAM these chips work flawlessly. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 09:46:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24087 for freebsd-stable-outgoing; Fri, 14 Aug 1998 09:46:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24072 for ; Fri, 14 Aug 1998 09:46:11 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id MAA13559; Fri, 14 Aug 1998 12:45:26 -0400 (EDT) Date: Fri, 14 Aug 1998 12:45:26 -0400 (EDT) From: "Matthew N. Dodd" To: Phil Allsopp cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3COM ethernet cards 3c905b-tx In-Reply-To: <3.0.3.32.19980814133144.00f06574@mail.virtek.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Aug 1998, Phil Allsopp wrote: > I used to succesfully use 3Com 3c905 cards in a FreeBSD 2.2.5 box as vx0 but > the new 3COM 3c905b-tx cards don't work and unfortunately every > supplier now only supplies the 3c905b-tx cards. > > Has anyone got the 3C905b-tx cards to succesfully work under 2.2.5 > and if so how ? You might try http://www.freebsd.org/~wpaul/3Com/2.2/ Quoted from http://www.freebsd.org/~wpaul/3Com/ === This directory contains pre-release drivers for the 3Com 3c900, 3c905 and 3c905B Etherlink XL and Fast Etherlink XL ethernet adapters. There are separate drivers for FreeBSD 3.0-current and FreeBSD 2.2.x (should work with 2.2.5, 2.2.6 and 2.2.7). Both versions support the same devices and offer the same performance. ... === -- | Matthew N. Dodd |This space | '78 Datsun 280Z | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net |is for rent| '84 Volvo 245DL | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 09:48:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24598 for freebsd-stable-outgoing; Fri, 14 Aug 1998 09:48:26 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24578 for ; Fri, 14 Aug 1998 09:48:18 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id MAA13583; Fri, 14 Aug 1998 12:47:40 -0400 (EDT) Date: Fri, 14 Aug 1998 12:47:40 -0400 (EDT) From: "Matthew N. Dodd" To: "Daniel O'Callaghan" cc: Phil Allsopp , freebsd-stable@FreeBSD.ORG Subject: Re: 3COM ethernet cards 3c905b-tx In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Aug 1998, Daniel O'Callaghan wrote: > The tx will never work under 2.2.5. It needs a new version of the vx > driver, which is under development, and has been for some time. I > don't hold out hopes that the new vx driver will make it into 2.2.8!!! It appears the Bill Paul has the 900/905/905B driver in the final stages of testing. This is not a 'new version of the vx driver' but a completly new driver using the 'xl' name. For more details see http://www.freebsd.org/~wpaul/3Com/ I'm sure he wouldn't mind more people beating on it before he commits it. -- | Matthew N. Dodd |This space | '78 Datsun 280Z | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net |is for rent| '84 Volvo 245DL | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 11:08:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10227 for freebsd-stable-outgoing; Fri, 14 Aug 1998 11:08:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10171 for ; Fri, 14 Aug 1998 11:07:58 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id UAA26626 for ; Fri, 14 Aug 1998 20:07:32 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id UAA01666 for ; Fri, 14 Aug 1998 20:07:30 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id UAA14015 for ; Fri, 14 Aug 1998 20:07:26 +0200 (CEST) From: Andre Albsmeier Message-Id: <199808141807.UAA13224@internal> Subject: Found reason why lpr -r -s doesn't work as expected To: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Date: Fri, 14 Aug 1998 20:07:22 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While trying to find out why the temporay files made by samba for printing aren't removed, I found that this is due to the following code in usr.sbin/lpr/lpd/printjob.c: case 'U': if (strchr(line+1, '/')) continue; (void) unlink(line+1); and fseek(cfp, 0L, 0); while (getline(cfp)) if (line[0] == 'U' && !strchr(line+1, '/')) (void) unlink(line+1); This disables the removement of files starting with '/'. This was introduced in version 1.14 according to the CVS log. However, I didn't find an explanation why this change was made. Is it a security hole? If this behaviour is considered, maybe we should not in the manual page that 'lpr -s -r' only removes the symlink and is equal to 'lpr -s'... What do you think? Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 11:51:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19599 for freebsd-stable-outgoing; Fri, 14 Aug 1998 11:51:06 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from i-planet.i-planet.com (iplanet-T1-gw.mv.best.net [206.86.192.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19583 for ; Fri, 14 Aug 1998 11:50:57 -0700 (PDT) (envelope-from chris@i-planet.com) Received: from i-planet.com (mochila [10.0.0.221]) by i-planet.i-planet.com (8.8.6/8.8.7) with ESMTP id CAA09605; Sat, 15 Aug 1998 02:50:26 +0800 (SGT) From: "Chris Andrichak" Message-Id: <199808141850.CAA09605@i-planet.i-planet.com> Date: Fri, 14 Aug 1998 11:50:33 -0700 To: Cc: Reply-To: "chris" Subject: Re: su problem with freebsd 2.2.7-stable X-Mailer: PonyEspresso 3.1beta MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ]On Fri, 14 Aug 1998, Khetan Gajjar wrote: ]>On Fri, 14 Aug 1998, Neil Blakey-Milner wrote: ]>>Are you su -m'ing? If not, try that. Or try -l if you're using -m. Also, ]>>does a ps show the new shell starting at all? ] ]The problem appears to be related to kerberos. I nulled the /etc/kerberosIV ]directory, and it started segfaulting. I put back the entries, and now ]it works fine. Any idea how to get a "empty" kerberosIV configuration, ]but still have the libraries installed in case I ever need to use ]it (I need to occasionally). I had the same problem with a 2.2.6 install. I installed kerberos on a lark, and at first all was ok, i'd just get the 'root not in kerberos acl' or something when i su'd. But after a while (and i don't know what i did - removing the /etc/kerberosIV directory sounds like something dumb that i'd do) it started core'ing like yours is. Rather than deal, i just reinstalled without kerberos, since i didn't really need it anyway. ------------------------------------------<>------------------------------- chris chris@i-planet.com ------------------------------------------<>------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 13:24:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06620 for freebsd-stable-outgoing; Fri, 14 Aug 1998 13:24:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA06611; Fri, 14 Aug 1998 13:24:43 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z7QOO-0006Uy-00; Fri, 14 Aug 1998 14:24:08 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id OAA17025; Fri, 14 Aug 1998 14:26:05 -0600 (MDT) Message-Id: <199808142026.OAA17025@harmony.village.org> To: Andre Albsmeier Subject: Re: Found reason why lpr -r -s doesn't work as expected Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Fri, 14 Aug 1998 20:07:22 +0200." <199808141807.UAA13224@internal> References: <199808141807.UAA13224@internal> Date: Fri, 14 Aug 1998 14:26:05 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808141807.UAA13224@internal> Andre Albsmeier writes: : if (strchr(line+1, '/')) : continue; : This disables the removement of files starting with '/'. This was : introduced in version 1.14 according to the CVS log. However, I didn't : find an explanation why this change was made. Is it a security hole? Without this fix, people could remove any file on your system by having remote print access. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 15:20:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27556 for freebsd-stable-outgoing; Fri, 14 Aug 1998 15:20:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from beavis.inetdirect.net (beavis.inetdirect.net [204.120.164.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27424 for ; Fri, 14 Aug 1998 15:20:05 -0700 (PDT) (envelope-from timsarver@netdirect.net) From: timsarver@netdirect.net Received: from tim (tech6.netdirect.net [204.120.164.16]) by beavis.inetdirect.net (8.8.5/8.7.3) with SMTP id RAA10613 for ; Fri, 14 Aug 1998 17:19:35 -0500 (EST) Message-Id: <199808142219.RAA10613@beavis.inetdirect.net> X-Sender: timsarver@netdirect.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 14 Aug 1998 17:20:36 -0500 To: freebsd-stable@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-questions subscribe freebsd-announce END To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 16:27:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13244 for freebsd-stable-outgoing; Fri, 14 Aug 1998 16:27:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from helium.hilink.com.au (helium.hilink.com.au [203.8.14.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13238 for ; Fri, 14 Aug 1998 16:27:47 -0700 (PDT) (envelope-from danny@hilink.com.au) Received: from localhost (danny@localhost) by helium.hilink.com.au (8.8.8/8.8.8) with SMTP id JAA03886; Sat, 15 Aug 1998 09:27:01 +1000 (EST) (envelope-from danny@hilink.com.au) X-Authentication-Warning: helium.hilink.com.au: danny owned process doing -bs Date: Sat, 15 Aug 1998 09:27:01 +1000 (EST) From: "Daniel O'Callaghan" To: Mike Smith cc: Phil Allsopp , freebsd-stable@FreeBSD.ORG Subject: Re: 3COM ethernet cards 3c905b-tx In-Reply-To: <199808140935.JAA13061@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Aug 1998, Mike Smith wrote: > > The tx will never work under 2.2.5. It needs a new version of the vx > > driver, which is under development, and has been for some time. > > I don't hold out hopes that the new vx driver will make it into 2.2.8!!! > > The xl driver, which is what you're talking about, will definitely be > in 2.2.8. Oh? Great. I'm happy to be corrected on that point. Thanks Mike. Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 14 18:40:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01579 for freebsd-stable-outgoing; Fri, 14 Aug 1998 18:40:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01493 for ; Fri, 14 Aug 1998 18:39:59 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA157635163; Fri, 14 Aug 1998 21:39:23 -0400 Date: Fri, 14 Aug 1998 21:39:23 -0400 (EDT) From: Bill Fumerola To: timsarver@netdirect.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <199808142219.RAA10613@beavis.inetdirect.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG try sending mail to majordomo@freebsd.org next time, dimwit. On Fri, 14 Aug 1998 timsarver@netdirect.net wrote: > subscribe freebsd-questions > > subscribe freebsd-announce > > END > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 15 00:37:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00938 for freebsd-stable-outgoing; Sat, 15 Aug 1998 00:37:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [36.118.0.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00933 for ; Sat, 15 Aug 1998 00:37:26 -0700 (PDT) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.8.8/8.8.5) id AAA15377; Sat, 15 Aug 1998 00:36:45 -0700 (PDT) Date: Sat, 15 Aug 1998 00:36:45 -0700 (PDT) From: Bob Vaughan Message-Id: <199808150736.AAA15377@tantivy.stanford.edu> To: billf@chc-chimes.com, timsarver@netdirect.net Subject: Re: your mail Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG more to the point, why isn't majordomo@freebsd.org configured to catch administrative crap?? it isn't hard.. -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@w6yx.stanford.edu | kc6sxc@w6yx.ampr.org | techie@t.stanford.edu | KC6SXC@W6YX.#NCA.CA.USA.NOAM | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 15 05:21:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21921 for freebsd-stable-outgoing; Sat, 15 Aug 1998 05:21:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21916 for ; Sat, 15 Aug 1998 05:21:04 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id OAA23083 for ; Sat, 15 Aug 1998 14:20:38 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id OAA09297 for ; Sat, 15 Aug 1998 14:20:38 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id OAA19581 for ; Sat, 15 Aug 1998 14:20:34 +0200 (CEST) From: Andre Albsmeier Message-Id: <199808151220.OAA17442@internal> Subject: Re: Found reason why lpr -r -s doesn't work as expected In-Reply-To: <199808142026.OAA17025@harmony.village.org> from Warner Losh at "Aug 14, 98 02:26:05 pm" To: imp@village.org (Warner Losh) Date: Sat, 15 Aug 1998 14:20:25 +0200 (CEST) Cc: andre.albsmeier@mchp.siemens.de, freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199808141807.UAA13224@internal> Andre Albsmeier writes: > : if (strchr(line+1, '/')) > : continue; > : This disables the removement of files starting with '/'. This was > : introduced in version 1.14 according to the CVS log. However, I didn't > : find an explanation why this change was made. Is it a security hole? > > Without this fix, people could remove any file on your system by > having remote print access. OK, and if remote access is disabled would it be safe? Have you got any references how this exploit exactly works so I can figure out what to do in order to be able to remove both files and without making my machine insecure... Thanks a lot, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 15 07:05:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00330 for freebsd-stable-outgoing; Sat, 15 Aug 1998 07:05:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00311; Sat, 15 Aug 1998 07:05:49 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id GAA28885; Sat, 15 Aug 1998 06:32:36 -0700 (PDT) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdJ28878; Sat Aug 15 06:32:14 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.1/8.6.10) id GAA01035; Sat, 15 Aug 1998 06:31:59 -0700 (PDT) Message-Id: <199808151331.GAA01035@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdzo1026; Sat Aug 15 06:31:56 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: Andre Albsmeier cc: imp@village.org (Warner Losh), freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Found reason why lpr -r -s doesn't work as expected In-reply-to: Your message of "Sat, 15 Aug 1998 14:20:25 +0200." <199808151220.OAA17442@internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Aug 1998 06:31:54 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In message <199808141807.UAA13224@internal> Andre Albsmeier writes: > > : if (strchr(line+1, '/')) > > : continue; > > : This disables the removement of files starting with '/'. This was > > : introduced in version 1.14 according to the CVS log. However, I didn't > > : find an explanation why this change was made. Is it a security hole? > > > > Without this fix, people could remove any file on your system by > > having remote print access. > > OK, and if remote access is disabled would it be safe? Have you got > any references how this exploit exactly works so I can figure out > what to do in order to be able to remove both files and without > making my machine insecure... No. By revoking remote access to your lpd, e.g. firewall, you would still have an exposure that local users could exploit, which in this case revoking access to local users would solve the problem. I think you get the picture... Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 15 13:00:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02901 for freebsd-stable-outgoing; Sat, 15 Aug 1998 13:00:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fani.fidata.fi (fani.fidata.fi [193.64.102.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02893 for ; Sat, 15 Aug 1998 13:00:49 -0700 (PDT) (envelope-from tomppa@fidata.fi) Received: from zeta.fidata.fi (zeta.fidata.fi [193.64.103.213]) by fani.fidata.fi (8.8.8/8.8.8) with ESMTP id XAA04875 for ; Sat, 15 Aug 1998 23:00:16 +0300 (EET DST) Received: (from tomppa@localhost) by zeta.fidata.fi (8.9.1/8.9.1) id XAA23444 for freebsd-stable@freebsd.org; Sat, 15 Aug 1998 23:00:16 +0300 (EET DST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13778.5497.881819.859280@zeta.fidata.fi> From: Tomi Vainio To: freebsd-scsi@FreeBSD.ORG Subject: How to stay tuned with 2.2 stable and CAM? Date: Thu, 13 Aug 1998 01:21:45 +0300 (EET DST) Reply-To: tomppa@fidata.fi X-Mailer: VM 6.47 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have used CAM code with stable about two months now. Last time I upgraded to 2.2.7 and over that I installed CAM 19980716-SNAP. If I use cvsup to get latest stable I'll lose all modifications from source tree that CAM SNAP added there. If I run patches again it will complain about lot of CAM stuff that is already on the system. Is there any easy way to get these to work together? Tomppa -- SUN Microsystems Oy PL 102, Niittymentie 9, 02201 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-stable" in the body of the message From owner-freebsd-stable Sat Aug 15 14:01:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11136 for freebsd-stable-outgoing; Sat, 15 Aug 1998 14:01:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11110 for ; Sat, 15 Aug 1998 14:01:21 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id OAA17532 for stable@freebsd.org; Sat, 15 Aug 1998 14:00:47 -0700 (MST) From: "Chad R. Larson" Message-Id: <199808152100.OAA17532@freebie.dcfinc.com> Subject: filesystem layout To: stable@FreeBSD.ORG Date: Sat, 15 Aug 1998 14:00:46 -0700 (MST) Reply-to: chad@dcfinc.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is probably a nit, but... On my 2.1-stable systems, the contents of /usr/obj mirror /usr/src very closely. But on a 2.2 system, there is an extra layer of dirctories before you get to the objects. That is, /usr/obj/usr/src/* matches /usr/src instead of /usr/obj matching /usr/src. I noticed this while pondering making /usr/obj a seperate filesystem so I could mount it async and make builds go faster. Anyway, is this intentional or did I goof something? And if it is the way it should be, why the change from the 2.1 method? -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 15 17:19:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07929 for freebsd-stable-outgoing; Sat, 15 Aug 1998 17:19:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07924; Sat, 15 Aug 1998 17:19:00 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA21108; Sat, 15 Aug 1998 17:18:21 -0700 (PDT) Message-Id: <199808160018.RAA21108@implode.root.com> To: Jaye Mathisen cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: vmopar state in 2.2.7? From: David Greenman Reply-To: dg@root.com Date: Sat, 15 Aug 1998 17:18:21 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The nnrpd's are occasionally getting stuck in what top shows as >the vmopar state. ps shows the process in Ds state. Should be fixed in rev 1.28.2.8 of nfs_bio.c. Let me know if you have any further trouble. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message