From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 00:36:10 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1947616A4CE for ; Sun, 7 Dec 2003 00:36:10 -0800 (PST) Received: from queue.paperwork.com (ns.place4us.com [206.8.93.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id B09D743FDD for ; Sun, 7 Dec 2003 00:36:08 -0800 (PST) (envelope-from denon@denon.cx) Received: from ONYX.denon.cx (unknown [206.8.93.100]) by queue.paperwork.com (CCS Enterprise SMTP) with ESMTP id 2954B75928 for ; Sun, 7 Dec 2003 02:45:26 -0600 (CST) Message-Id: <6.0.1.1.2.20031207022844.066a9008@mail.jon.com> X-Sender: denon@denon.cx (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Sun, 07 Dec 2003 02:35:59 -0600 To: freebsd-stable@freebsd.org From: denon Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2003 08:36:10 -0000 We've been doing more work with VMware and FreeBSD lately. Overall it's been going well, but we have a machine that's giving me grief, and I'm a bit concerned. It's running 4.8-Release, with a single virtual SCSI drive. It's been running fine for months, but as of recently, it's started locking up. When it locks up, this is what's in the messages: /kernel: (da0:bt0:0:0:0): CCB 0xca993340 - timed out /kernel: bt0: btdone - Attempt to free non-active BCCB 0xca9933c0 This is the scsi card it sees (from vmware) /kernel: bt0: port 0x1060-0x107f mem 0xfd000000-0xfd00001f irq 9 The host machine is running Windows 2003 Server, on an SMP Xeon host. The virtual machine's I/O is pretty minor, and it doesn't hit the cpu/etc much either. Pretty lightweight install. Any thoughts on the situation would be appreciated. -d From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 13:37:52 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A99416A4D0 for ; Sun, 7 Dec 2003 13:37:52 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C381C43F75 for ; Sun, 7 Dec 2003 13:37:50 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id B3F1172DB5; Sun, 7 Dec 2003 13:37:50 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id B1C0E72DAD; Sun, 7 Dec 2003 13:37:50 -0800 (PST) Date: Sun, 7 Dec 2003 13:37:50 -0800 (PST) From: Doug White To: michael In-Reply-To: <20031206101611.GA21554@brenner.msresearch.org> Message-ID: <20031207133651.I7085@carver.gumbysoft.com> References: <20031206101611.GA21554@brenner.msresearch.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: newsyslogwithdate-extension-logfiles X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2003 21:37:52 -0000 On Sat, 6 Dec 2003, michael wrote: > Hi, > > i widely use FreeBSD and his enhancement's vs. other OS'es. > > Now i have the wish that the 'newsyslog' uses date-extensions > in the 'rotated' logfiles. Note that this scheme has the potentially nasty side effect that if newsyslog did pruning by date, and somehow the system date got munged, it could erase all your old logfiles. In the current scheme that can't happen. And don't forget about ls -l for finding dates of things :-) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 13:41:55 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE9CE16A4D1 for ; Sun, 7 Dec 2003 13:41:55 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97F1E43FD7 for ; Sun, 7 Dec 2003 13:41:52 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 8A01A72DB8; Sun, 7 Dec 2003 13:41:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 8854F72DB5; Sun, 7 Dec 2003 13:41:52 -0800 (PST) Date: Sun, 7 Dec 2003 13:41:52 -0800 (PST) From: Doug White To: denon In-Reply-To: <6.0.1.1.2.20031207022844.066a9008@mail.jon.com> Message-ID: <20031207134057.Y7085@carver.gumbysoft.com> References: <6.0.1.1.2.20031207022844.066a9008@mail.jon.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2003 21:41:55 -0000 On Sun, 7 Dec 2003, denon wrote: > We've been doing more work with VMware and FreeBSD lately. Overall it's > been going well, but we have a machine that's giving me grief, and I'm a > bit concerned. > > It's running 4.8-Release, with a single virtual SCSI drive. It's been > running fine for months, but as of recently, it's started locking up. When > it locks up, this is what's in the messages: > /kernel: (da0:bt0:0:0:0): CCB 0xca993340 - timed out > /kernel: bt0: btdone - Attempt to free non-active BCCB 0xca9933c0 I wonder if the vmware environment is bug-for-bug compatible with the old buslogic hardware :-) I suspect this is a bug in vmware, where the emulated driver is suffering from long-term corruption. 43-day bug, perhaps? Does stopping and starting VMware clear this up? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 18:54:23 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC42316A4CF for ; Sun, 7 Dec 2003 18:54:23 -0800 (PST) Received: from ran.psg.com (ip166.usw253.dsl-acs2.sea.iinet.com [209.20.253.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2D8D43FB1 for ; Sun, 7 Dec 2003 18:54:22 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com) by ran.psg.com with esmtp (Exim 4.24; FreeBSD) id 1ATBXS-000E6N-AM for freebsd-stable@freebsd.org; Sun, 07 Dec 2003 18:54:22 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 7 Dec 2003 18:54:21 -0800 To: FreeBSD Stable Message-Id: Subject: tp40 screen blanks forever X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 02:54:23 -0000 thinkpad t40p 4.9-stable as of friday, all cvsupped and portupgraded to death SYMPTOM: if i leave the desktop alone for maybe an hour, the screen is blanked and i can not get it back, even by killing X. i have to reboot the machine to get the screen back bios has screen blanking turned off does not happen when X has not been started, i.e. running as a non-X user happens in gnome with screensaver set to DisableScreenSaver still happens if i kill the xscreensaver process xset has dpms disabled same with tvtwm as window mangler instead of gnome help, i am running out of goat entrails! randy From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 19:15:46 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBC3516A4CE for ; Sun, 7 Dec 2003 19:15:46 -0800 (PST) Received: from t40.swtch.com (node-40245942.bos.onnet.us.uu.net [64.36.89.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0AC843FDF for ; Sun, 7 Dec 2003 19:15:45 -0800 (PST) (envelope-from rsc@swtch.com) Received: from localhost ([127.0.0.1] helo=t40.swtch.com) by t40.swtch.com with esmtp (Exim 4.22) id 1ATBs6-0000Oc-4D; Sun, 07 Dec 2003 22:15:42 -0500 To: Randy Bush In-Reply-To: Your message of "Sun, 07 Dec 2003 18:54:21 PST." From: "Russ Cox" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1524.1070853339.1@t40.swtch.com> Date: Sun, 07 Dec 2003 22:15:39 -0500 Message-Id: cc: FreeBSD Stable Subject: Re: tp40 screen blanks forever X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 03:15:47 -0000 > thinkpad t40p > 4.9-stable as of friday, all cvsupped and portupgraded to death > > SYMPTOM: if i leave the desktop alone for maybe an hour, the screen > is blanked and i can not get it back, even by killing X. i have to > reboot the machine to get the screen back you can ctl-alt-f1 to switch to a text console, then fn-f7 to turn off the lcd, then fn-f7 to turn it back on, then alt-f9 to go back to x. at least, that's how i've been limping along on my t40 (not t40p). russ From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 21:30:26 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00AA716A4CE for ; Sun, 7 Dec 2003 21:30:26 -0800 (PST) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1C4C43F93 for ; Sun, 7 Dec 2003 21:30:24 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.12.10/8.12.9) with ESMTP id hB85UO7P019960; Mon, 8 Dec 2003 00:30:24 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20031206101611.GA21554@brenner.msresearch.org> References: <20031206101611.GA21554@brenner.msresearch.org> Date: Mon, 8 Dec 2003 00:30:22 -0500 To: michael , freebsd-stable@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Re: newsyslogwithdate-extension-logfiles X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 05:30:26 -0000 At 11:16 AM +0100 12/6/03, michael wrote: >Hi, > >I widely use FreeBSD and his enhancement's vs. other OS'es. > >Now i have the wish that the 'newsyslog' uses date-extensions >in the 'rotated' logfiles. >eg: > >messages.0.gz should be messages.20031206.gz and so on... > >or any other extension that will give the date in the >name of file? > >is this possible with the newsyslog? >I think no! And why? Right now there is no option in newsyslog which gives you that. There is a PR (problem-report) which has asked for this, and it is on the list of things I plan to do with newsyslog. Actually, I had planned to have that update done by now, but I had a few months of bad luck with some of my freebsd machines. (mostly hardware-related bad luck). -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 22:05:45 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7724116A4CE for ; Sun, 7 Dec 2003 22:05:45 -0800 (PST) Received: from ran.psg.com (ip166.usw253.dsl-acs2.sea.iinet.com [209.20.253.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AC8143FDF for ; Sun, 7 Dec 2003 22:05:44 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com) by ran.psg.com with esmtp (Exim 4.24; FreeBSD) id 1ATEWb-000J2j-3N; Sun, 07 Dec 2003 22:05:41 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 7 Dec 2003 22:05:40 -0800 To: "Russ Cox" References: Message-Id: cc: FreeBSD Stable Subject: Re: tp40 screen blanks forever X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 06:05:45 -0000 >> SYMPTOM: if i leave the desktop alone for maybe an hour, the screen >> is blanked and i can not get it back, even by killing X. i have to >> reboot the machine to get the screen back > you can ctl-alt-f1 to switch to a text console, > then fn-f7 to turn off the lcd, then fn-f7 to turn > it back on, then alt-f9 to go back to x. that is absolutely disgusting. but it works! thank you, thank you! now i wonder what the actual problem is. randy From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 04:47:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 551B216A4CE for ; Mon, 8 Dec 2003 04:47:00 -0800 (PST) Received: from nbh-gw.newchem.ru (novbytchem-2.ip.PeterStar.net [81.3.149.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DF5B43F75 for ; Mon, 8 Dec 2003 04:46:58 -0800 (PST) (envelope-from illich@newchem.ru) Received: from 127.0.0.1 ([192.168.204.4]) by nbh-gw.newchem.ru (8.12.9/8.12.7) with ESMTP id hB8CktAF009438 for ; Mon, 8 Dec 2003 15:46:56 +0300 (MSK) (envelope-from illich@newchem.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Date: Mon, 8 Dec 2003 15:46:55 +0300 From: Illia Baidakov X-Mailer: The Bat! (v1.62q) Personal X-Priority: 3 (Normal) Message-ID: <1069801150.20031208154655@newchem.ru> To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: 'long long' warning while compiling mit-kerberos on 4.9-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Illia Baidakov List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 12:47:00 -0000 X-List-Received-Date: Mon, 08 Dec 2003 12:47:00 -0000 Hello freebsd-stable, I'm thinking it's the right list about my problem. The exact messages while compiling mit-kerberos5-1.3.1 are: /usr/include/stdlib.h:111: warning: ANSI C does not support `long long' /usr/include/stdlib.h:117: warning: ANSI C does not suppotr `long long' I have gcc version 2.95.4 in my system. Trying to build gcc-3.3.2 from sources the above messages has repeated again right up to stopping the building proccess. What is the safest way to receive correct 'long long' type definition in C compiler? Tanks in advance, Illia Baidakov. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 10:16:32 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6F7716A4CE for ; Mon, 8 Dec 2003 10:16:32 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB16743FBD for ; Mon, 8 Dec 2003 10:16:30 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5187866C8E; Mon, 8 Dec 2003 10:16:30 -0800 (PST) Date: Mon, 8 Dec 2003 10:16:30 -0800 From: Kris Kennaway To: Illia Baidakov Message-ID: <20031208181630.GA49599@xor.obsecurity.org> References: <1069801150.20031208154655@newchem.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <1069801150.20031208154655@newchem.ru> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org Subject: Re: 'long long' warning while compiling mit-kerberos on 4.9-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 18:16:32 -0000 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 08, 2003 at 03:46:55PM +0300, Illia Baidakov wrote: > Hello freebsd-stable, >=20 > I'm thinking it's the right list about my problem. > The exact messages while compiling mit-kerberos5-1.3.1 are: > /usr/include/stdlib.h:111: warning: ANSI C does not support `long > long' > /usr/include/stdlib.h:117: warning: ANSI C does not suppotr `long > long' >=20 > I have gcc version 2.95.4 in my system. Trying to build gcc-3.3.2 > from sources the above messages has repeated again right up to > stopping the building proccess. >=20 > What is the safest way to receive correct 'long long' type > definition in C compiler? That's a warning, not an error. If you're seeing your compilation stop, that's because there's either an actual error being reported, or because you or the software developer has told gcc to treat warnings as errors (e.g. -pedantic or -Werror, etc). Kris --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/1L/+Wry0BWjoQKURAvZeAJ9dXMU3+iXw34PriLuldxk9IWuNQgCcCKbf DEO7SbgpgOpR8urJ3JUfduo= =wYii -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 10:41:53 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27E4516A4CF for ; Mon, 8 Dec 2003 10:41:53 -0800 (PST) Received: from be-well.no-ip.com (lowellg.ne.client2.attbi.com [66.30.200.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93DB143FA3 for ; Mon, 8 Dec 2003 10:41:42 -0800 (PST) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: by be-well.no-ip.com (Postfix, from userid 1147) id 9612274; Mon, 8 Dec 2003 13:41:41 -0500 (EST) Sender: lowell@be-well.ilk.org To: Illia Baidakov References: <1264617800.20031208170645@newchem.ru> From: Lowell Gilbert Date: 08 Dec 2003 13:41:41 -0500 In-Reply-To: <1264617800.20031208170645@newchem.ru> Message-ID: <448yln40ey.fsf@be-well.ilk.org> Lines: 186 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-stable@freebsd.org Subject: Re: Re2: 'long long' warning while compiling mit-kerberos on 4.9-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 18:41:53 -0000 Illia Baidakov writes: > > Those messages are not a problem. It's true that ANSI C doesn't > > support 'long long', but GCC does as an extension. In fact, GCC > > supports quite a few extensions to the C standard. Did some kind of > > error actually stop the build? If so, you need to show what the > > precise errors right at and just before the point where the build > > stopped. > I'm not sure but if it could shed light to the problem solving, > this is the it: > > gcc -L../../lib -Wl,-rpath -Wl,/usr/local/lib -g -O2 -Wall > -Wmissing-prototypes -Wcast-qual -Wcast-align -Wconversion -Wshadow > -Wno-comment -pedantic -o kshd krshd.o kcmd.o forward.o compat_recv.o > -lcrypt -lpty -ldes425 -lkrb5 -lk5crypto -lcom_err -lutil > ../../lib/libkrb5.so: warning: mktemp() possibly used unsafely; > consider using mkstemp() > gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" > -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DHAVE_BT_RSEQ=1 > -DKRB5_PRIVATE=1 -DKRB5_DEPRECATED=1 -DKRB5_DNS_LOOKUP_KDC=1 > -DKRB5_DNS_LOOKUP_REALM=1 -DKRB5_DNS_LOOKUP=1 -DHAVE_LIBUTIL=1 > -DHAVE_LIBCRYPT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 > -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 > -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_UNISTD_H=1 > -DHAVE_UNISTD_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 > -DHAVE_WORKING_FORK=1 -DHAVE_ISATTY=1 -DHAVE_INET_ATON=1 > -DHAVE_GETENV=1 -DHAVE_KILLPG=1 -DHAVE_INITGROUPS=1 -DHAVE_SETPRIORITY=1 > -DHAVE_SETREUID=1 -DHAVE_SETRESUID=1 -DHAVE_WAITPID=1 -DHAVE_SETSID=1 > -DHAVE_SETLOGIN=1 -DHAVE_TCGETPGRP=1 -DHAVE_TCSETPGRP=1 > -DHAVE_SETPGID=1 -DHAVE_UTIMES=1 -DHAVE_RRESVPORT_AF=1 > -DHAVE_UNISTD_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_FILIO_H=1 > -DHAVE_SYS_SOCKIO_H=1 -DHAVE_SYS_TTY_H=1 -DHAVE_TTYENT_H=1 > -DHAVE_SYS_SELECT_H=1 -DHAVE_UTMP_H=1 -DHAVE_SYS_TIME_H=1 > -DHAVE_SYS_IOCTL_COMPAT_H=1 -DHAVE_PATHS_H=1 -DHAVE_ARPA_NAMESER_H=1 > -DHAVE_STDARG_H=1 -DHAVE_GETDTABLESIZE=1 -DNEED_DAEMON_PROTO=1 > -DPOSIX_SIGTYPE=1 -Dkrb5_sigtype=void -DPOSIX_SIGNALS=1 > -DPOSIX_SETJMP=1 -DUSE_DIRENT_H=1 -DWAIT_USES_INT=1 -DPOSIX_TERMIOS=1 > -DNO_UT_PID=1 -DNO_UT_TYPE=1 -DNO_UT_EXIT=1 > -DGETSOCKNAME_ARG2_TYPE=struct\ sockaddr > -DGETSOCKNAME_ARG3_TYPE=size_t -DHAVE_SETOWN=1 -DSETPGRP_TWOARG=1 > -DHAVE_REGCOMP=1 -DKRB5_PATH_RLOGIN=\"/usr/local/bin/rlogin\" > -DUCB_RLOGIN=\"/usr/bin/rlogin\" -DUCB_RSH=\"/usr/bin/rsh\" > -DUCB_RCP=\"/bin/rcp\" -DKERBEROS > -DLOGIN_PROGRAM=\"/usr/local/sbin/login.krb5\" > -DKPROGDIR=\"/usr/local/bin\" -DHEIMDAL_FRIENDLY -I../../include > -I./../../include -I../../include/krb5 -I./../../include/krb5 -g > -O2 -Wall -Wmissing-prototypes -Wcast-qual -Wcast-align -Wconversion > -Wshadow -Wno-comment -pedantic -c krlogind.c > In file included from krlogind.c:128: > /usr/include/stdlib.h:111: warning: ANSI C does not support `long long' > /usr/include/stdlib.h:117: warning: ANSI C does not support `long long' > krlogind.c: In function `protocol': > krlogind.c:1055: warning: pointer targets in passing arg 2 of > `rcmd_stream_read' differ in signedness > krlogind.c:1085: warning: passing arg 3 of `write' as unsigned due to > prototype > krlogind.c:1125: warning: negative integer implicitly converted to > unsigned type > krlogind.c:1126: warning: negative integer implicitly converted to > unsigned type > krlogind.c:1144: warning: pointer targets in passing arg 2 of > `rcmd_stream_write' differ in signedness > krlogind.c:1144: warning: passing arg 3 of `rcmd_stream_write' as > unsigned due to prototype > gcc -L../../lib -Wl,-rpath -Wl,/usr/local/lib -g -O2 -Wall > -Wmissing-prototypes -Wcast-qual -Wcast-align -Wconversion -Wshadow > -Wno-comment -pedantic -o klogind krlogind.o kcmd.o forward.o > compat_recv.o -lpty -ldes425 -lkrb5 -lk5crypto -lcom_err -lutil > ../../lib/libkrb5.so: warning: mktemp() possibly used unsafely; > consider using mkstemp() > gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" > -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DHAVE_BT_RSEQ=1 > -DKRB5_PRIVATE=1 -DKRB5_DEPRECATED=1 -DKRB5_DNS_LOOKUP_KDC=1 > -DKRB5_DNS_LOOKUP_REALM=1 -DKRB5_DNS_LOOKUP=1 -DHAVE_LIBUTIL=1 > -DHAVE_LIBCRYPT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 > -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 > -DHAVE_UNISTD_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 > -DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_ISATTY=1 > -DHAVE_INET_ATON=1 -DHAVE_GETENV=1 -DHAVE_KILLPG=1 -DHAVE_INITGROUPS=1 > -DHAVE_SETPRIORITY=1 -DHAVE_SETREUID=1 -DHAVE_SETRESUID=1 > -DHAVE_WAITPID=1 -DHAVE_SETSID=1 -DHAVE_SETLOGIN=1 -DHAVE_TCGETPGRP=1 > -DHAVE_TCSETPGRP=1 -DHAVE_SETPGID=1 -DHAVE_UTIMES=1 > -DHAVE_RRESVPORT_AF=1 -DHAVE_UNISTD_H=1 -DHAVE_STDLIB_H=1 > -DHAVE_STRING_H=1 -DHAVE_SYS_FILIO_H=1 -DHAVE_SYS_SOCKIO_H=1 > -DHAVE_SYS_TTY_H=1 -DHAVE_TTYENT_H=1 -DHAVE_SYS_SELECT_H=1 > -DHAVE_UTMP_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_IOCTL_COMPAT_H=1 > -DHAVE_PATHS_H=1 -DHAVE_ARPA_NAMESER_H=1 -DHAVE_STDARG_H=1 > -DHAVE_GETDTABLESIZE=1 -DNEED_DAEMON_PROTO=1 -DPOSIX_SIGTYPE=1 > -Dkrb5_sigtype=void -DPOSIX_SIGNALS=1 -DPOSIX_SETJMP=1 > -DUSE_DIRENT_H=1 -DWAIT_USES_INT=1 -DPOSIX_TERMIOS=1 -DNO_UT_PID=1 > -DNO_UT_TYPE=1 -DNO_UT_EXIT=1 -DGETSOCKNAME_ARG2_TYPE=struct\ sockaddr > -DGETSOCKNAME_ARG3_TYPE=size_t -DHAVE_SETOWN=1 -DSETPGRP_TWOARG=1 > -DHAVE_REGCOMP=1 -DKRB5_PATH_RLOGIN=\"/usr/local/bin/rlogin\" > -DUCB_RLOGIN=\"/usr/bin/rlogin\" -DUCB_RSH=\"/usr/bin/rsh\" > -DUCB_RCP=\"/bin/rcp\" -DKERBEROS > -DLOGIN_PROGRAM=\"/usr/local/sbin/login.krb5\" > -DKPROGDIR=\"/usr/local/bin\" -DHEIMDAL_FRIENDLY -I../../include > -I./../../include -I../../include/krb5 -I./../../include/krb5 -g > -O2 -Wall -Wmissing-prototypes -Wcast-qual -Wcast-align -Wconversion > -Wshadow -Wno-comment -pedantic -c login.c > In file included from login.c:85: > /usr/include/stdlib.h:111: warning: ANSI C does not support `long long' > /usr/include/stdlib.h:117: warning: ANSI C does not support `long long' > login.c:516: warning: no previous prototype for `k_init' > login.c: In function `main': > login.c:1475: warning: passing arg 2 of `chmod' with different width > due to prototype > login.c:1551: warning: passing arg 2 of `initgroups' as signed due to > prototype > login.c: In function `motd': > login.c:2089: warning: passing arg 3 of `write' as unsigned due to > prototype > gcc -L../../lib -Wl,-rpath -Wl,/usr/local/lib -g -O2 -Wall > -Wmissing-prototypes -Wcast-qual -Wcast-align -Wconversion -Wshadow > -Wno-comment -pedantic -o login.krb5 login.o -lcrypt -lpty > -ldes425 -lkrb5 -lk5crypto -lcom_err -lutil ../../lib/libkrb5.so: > warning: mktemp() possibly used unsafely; consider using mkstemp() > making all in appl/gss-sample... > gcc -L../../lib -Wl,-rpath -Wl,/usr/local/lib -g -O2 -Wall > -Wmissing-prototypes -Wcast-qual -Wcast-align -Wconversion -Wshadow > -Wno-comment -pedantic -o gss-server gss-server.o gss-misc.o > -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err ../../lib/libkrb5.so: > warning: mktemp() possibly used unsafely; consider using mkstemp() > gcc -L../../lib -Wl,-rpath -Wl,/usr/local/lib -g -O2 -Wall > -Wmissing-prototypes -Wcast-qual -Wcast-align -Wconversion -Wshadow > -Wno-comment -pedantic -o gss-client gss-client.o gss-misc.o > -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err ../../lib/libkrb5.so: > warning: mktemp() possibly used unsafely; consider using mkstemp() > making all in appl/gssftp... > making all in appl/gssftp/ftp... > gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" > -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DHAVE_BT_RSEQ=1 > -DKRB5_PRIVATE=1 -DKRB5_DEPRECATED=1 -DKRB5_DNS_LOOKUP_KDC=1 > -DKRB5_DNS_LOOKUP_REALM=1 -DKRB5_DNS_LOOKUP=1 -DPOSIX_SIGTYPE=1 > -Dkrb5_sigtype=void -DPOSIX_SIGNALS=1 -DUSE_SIGPROCMASK=1 > -DPOSIX_SETJMP=1 -DWAIT_USES_INT=1 -DSYS_ERRLIST_DECLARED=1 > -DHAVE_SYS_ERRLIST=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 > -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 > -DHAVE_UNISTD_H=1 -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 > -DHAVE_STDARG_H=1 -DPOSIX_TERMIOS=1 -DHAVE_UNISTD_H=1 > -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_SELECT_H=1 > -DHAVE_SYS_SOCKIO_H=1 -DHAVE_PATHS_H=1 -DNO_UT_PID=1 -DNO_UT_TYPE=1 > -DNO_UT_EXIT=1 -DSYS_ERRLIST_DECLARED=1 -DHAVE_SYS_ERRLIST=1 > -DHAVE_GETDTABLESIZE=1 -DHAVE_GETCWD=1 -DHAVE_GETDTABLESIZE=1 > -DHAVE_GETUSERSHELL=1 -DHAVE_SETEUID=1 -DHAVE_SETREUID=1 > -DHAVE_SETRESUID=1 -DHAVE_STRERROR=1 -DHAVE_GETENV=1 -DHAVE_LIBCRYPT=1 > -DHAVE_LIBUTIL=1 -DHAVE_REGCOMP=1 -DGSSAPI -DFTP_BUFSIZ=10240 > -I../../../include -I./../../../include -I../../../include/krb5 > -I./../../../include/krb5 -I./.. -I. -g -O2 -Wall > -Wmissing-prototypes -Wcast-qual -Wcast-align -Wconversion -Wshadow > -Wno-comment -pedantic -c ./cmdtab.c > In file included from /usr/include/sys/param.h:98, > from ftp_var.h:111, > from ./cmdtab.c:39: > /usr/include/sys/signal.h:230: redefinition of `my_sig_t' > ftp_var.h:62: `my_sig_t' previously declared here > ./cmdtab.c:35: warning: `sccsid' defined but not used > *** Error code 1 > > Stop in > /usr/ports/distfiles/PKI/MIT-Kerberos/krb5-1.3.1/src/appl/gssftp/ftp. > *** Error code 1 > > Stop in > /usr/ports/distfiles/PKI/MIT-Kerberos/krb5-1.3.1/src/appl/gssftp. > *** Error code 1 > > Stop in /usr/ports/distfiles/PKI/MIT-Kerberos/krb5-1.3.1/src/appl. > *** Error code 1 > > Stop in /usr/ports/distfiles/PKI/MIT-Kerberos/krb5-1.3.1/src. > > > Please see the notes on installing and using Kerberos from the FreeBSD > > Handbook: > > http://www.ru.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kerberos5.html > Already I did. And not just it. An attempt to build MIT Kerberos is my > own curiosity. > Is it a best practise to use Heimdal Kerberos on FreeBSD? If it's so I > think I have no limits to orientate myself to use it. That is a very complicated piece of software to try to port on your own as a first effort. It should be quite possible to get it running, but it will require some understanding of programming and the use of compilers. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 11:34:57 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35D6216A4CE for ; Mon, 8 Dec 2003 11:34:57 -0800 (PST) Received: from bricore.com (adsl-64-168-71-68.dsl.snfc21.pacbell.net [64.168.71.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 800FE43D30 for ; Mon, 8 Dec 2003 11:34:35 -0800 (PST) (envelope-from lchen@briontech.com) Received: from lchenpc (lchen-pc.bricore.com [192.168.1.130]) (authenticated bits=0) by bricore.com (8.12.6/8.12.6) with ESMTP id hB8JOtCf064560; Mon, 8 Dec 2003 11:24:55 -0800 (PST) (envelope-from lchen@briontech.com) From: "Luoqi Chen" To: "Matthew Dillon" , Date: Mon, 8 Dec 2003 11:27:26 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <200312070413.hB74Dm7g058674@apollo.backplane.com> X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Subject: RE: Bug in i386/i386/trap.c %gs handling on stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 19:34:57 -0000 > In i386/i386/trap.c if %gs is invalid... for example, a process with a > USER_LDT takes an interrupt while exiting, or if %gs is set > through procfs, > the fault check must occur regardless of the interrupt nesting > level because > mainline code does not push and load a %gs for the kernel. > I don't quite get it. There'll be fault only when the kernel tries to load an invalid %gs. And there's only one place that the kernel would load a new %gs: during a context switch, which could not take place in an interrupt context. > FreeBSD-5.x has already moved this check to outside the nesting > level test. > > It may also be possible that %fs can cause the same problem to occur in > the situation with a process takes an interrupt while exiting and %fs is > set to a USER_LDT entry. I have not checked this, but if it is > true it would > be a problem in both -current and -stable for the exiting case. > It's different for %fs, it holds a valid kernel segment at all time inside the kernel. > > if (intr_nesting_level == 0) { > /* > * Invalid %fs's and %gs's can be created using > * procfs or PT_SETREGS or by invalidating the > * underlying LDT entry. This causes a fault > * in kernel mode when the kernel attempts to > * switch contexts. Lose the bad context > * (XXX) so that we can continue, and generate > * a signal. > */ > if (frame.tf_eip == (int)cpu_switch_load_gs) { <<< WRONG > curpcb->pcb_gs = 0; <<< > psignal(p, SIGBUS); <<< > return; <<< > } > MAYBE_DORETI_FAULT(doreti_iret, > doreti_iret_fault); > > -lq From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 13:26:39 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82B6E16A4CE for ; Mon, 8 Dec 2003 13:26:39 -0800 (PST) Received: from queue.paperwork.com (ns.place4us.com [206.8.93.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6401443D28 for ; Mon, 8 Dec 2003 13:26:30 -0800 (PST) (envelope-from denon@denon.cx) Received: from ONYX.denon.cx (unknown [206.8.93.100]) by queue.paperwork.com (CCS Enterprise SMTP) with ESMTP id C02E97C4D5; Mon, 8 Dec 2003 15:35:18 -0600 (CST) Message-Id: <6.0.1.1.2.20031208152409.09cfed60@mail.jon.com> X-Sender: denon@denon.cx (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Mon, 08 Dec 2003 15:25:49 -0600 To: Doug White From: denon In-Reply-To: <20031207134057.Y7085@carver.gumbysoft.com> References: <6.0.1.1.2.20031207022844.066a9008@mail.jon.com> <20031207134057.Y7085@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 21:26:39 -0000 Responses inline: At 03:41 PM 12/7/2003, you wrote: >On Sun, 7 Dec 2003, denon wrote: > > > We've been doing more work with VMware and FreeBSD lately. Overall it's > > been going well, but we have a machine that's giving me grief, and I'm a > > bit concerned. > > > > It's running 4.8-Release, with a single virtual SCSI drive. It's been > > running fine for months, but as of recently, it's started locking up. When > > it locks up, this is what's in the messages: > > /kernel: (da0:bt0:0:0:0): CCB 0xca993340 - timed out > > /kernel: bt0: btdone - Attempt to free non-active BCCB 0xca9933c0 > >I wonder if the vmware environment is bug-for-bug compatible with the old >buslogic hardware :-) Sure seems it .. though it was stable for a long time, so I don't know .. >I suspect this is a bug in vmware, where the emulated driver is suffering >from long-term corruption. 43-day bug, perhaps? > >Does stopping and starting VMware clear this up? Nope, apparently not .. I tried and its happened again today. Seems to happen about twice a day, but no pattern to it that I see.. -d From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 23:50:05 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2243B16A4CE for ; Mon, 8 Dec 2003 23:50:05 -0800 (PST) Received: from web13422.mail.yahoo.com (web13422.mail.yahoo.com [216.136.175.132]) by mx1.FreeBSD.org (Postfix) with SMTP id 18E8243D2C for ; Mon, 8 Dec 2003 23:50:04 -0800 (PST) (envelope-from h2g2_jimmiejaz@yahoo.com) Message-ID: <20031209075004.72395.qmail@web13422.mail.yahoo.com> Received: from [216.154.12.4] by web13422.mail.yahoo.com via HTTP; Mon, 08 Dec 2003 23:50:04 PST Date: Mon, 8 Dec 2003 23:50:04 -0800 (PST) From: jimmie james To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: strange log messages X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 07:50:05 -0000 Howdy, I just noticed these tonight after a cvsup/build world/kernel/install world around 2am EST on the 8th of dec. Dec 9 02:14:23 fortytwo /kernel: issignal Dec 9 02:16:17 fortytwo /kernel: issignal Dec 9 02:17:50 fortytwo /kernel: issignal after a man -k issignal turned up nothing, I hit the online manpages... http://www.freebsd.org/cgi/man.cgi?query=issignal&apropos=0&sektion=0&manpath=FreeBSD+4.9-stable&format=html shows nothing either, the 5.x series... http://www.freebsd.org/cgi/man.cgi?query=issignal&apropos=0&sektion=0&manpath=FreeBSD+5.0-RELEASE&format=html comes up with a page for it. Question is, with a stable-supfile with *default release=cvs tag=RELENG_4 and that message being there, A) should the man page be with it, or B) should /usr/src/UPDATING have some mention of it? Considering I can't code to save my life, what's up here? __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 02:21:47 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84D7616A4CE for ; Tue, 9 Dec 2003 02:21:47 -0800 (PST) Received: from nbh-gw.newchem.ru (novbytchem-2.ip.PeterStar.net [81.3.149.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47CAA43D20 for ; Tue, 9 Dec 2003 02:21:45 -0800 (PST) (envelope-from illich@newchem.ru) Received: from 127.0.0.1 ([192.168.204.4]) by nbh-gw.newchem.ru (8.12.9/8.12.7) with ESMTP id hB9ALhAF012239 for ; Tue, 9 Dec 2003 13:21:43 +0300 (MSK) (envelope-from illich@newchem.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Date: Tue, 9 Dec 2003 13:21:43 +0300 From: Illia Baidakov X-Mailer: The Bat! (v1.62q) Personal X-Priority: 3 (Normal) Message-ID: <92721135.20031209132143@newchem.ru> To: Lowell Gilbert In-Reply-To: <448yln40ey.fsf@be-well.ilk.org> References: <1264617800.20031208170645@newchem.ru> <448yln40ey.fsf@be-well.ilk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re[2]: Re2: 'long long' warning while compiling mit-kerberos on 4.9-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Illia Baidakov List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 10:21:47 -0000 Hello Lowell, >> In file included from /usr/include/sys/param.h:98, >> from ftp_var.h:111, >> from ./cmdtab.c:39: >> /usr/include/sys/signal.h:230: redefinition of `my_sig_t' >> ftp_var.h:62: `my_sig_t' previously declared here >> ./cmdtab.c:35: warning: `sccsid' defined but not used >> *** Error code 1 LG> That is a very complicated piece of software to try to port on your LG> own as a first effort. It should be quite possible to get it running, LG> but it will require some understanding of programming and the use of LG> compilers. There are a lot of documentation about this technology such as RFCs, user's and administrator's guides, papers over the net and guru advises. All that I did was commnted the string 230 in /usr/include/sys/signal.h After that the building process has complited succesfully. Equally as installing and checking ones. I hope this change will not cause any serious problems with running kerberos applications and will not open security breachs. At the end I have turned the changes back. So I trying to ask you ones again: Is it a best practise to use Heimdal Kerberos on FreeBSD? If it's so I think I have no limits to orientate myself to use it. -- Best regards, a mailto:a@newchem.ru From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 06:50:25 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDE9416A4CE for ; Tue, 9 Dec 2003 06:50:25 -0800 (PST) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E81243D29 for ; Tue, 9 Dec 2003 06:50:24 -0800 (PST) (envelope-from craig@meoqu.gank.org) Received: from localhost (ion.gank.org [69.55.238.164]) by ion.gank.org (mail) with ESMTP id AD9A52B24F; Tue, 9 Dec 2003 08:50:23 -0600 (CST) Received: from ion.gank.org ([69.55.238.164]) by localhost (ion.gank.org [69.55.238.164]) (amavisd-new, port 10024) with LMTP id 78936-05; Tue, 9 Dec 2003 08:50:22 -0600 (CST) Received: from owen1492.uf.corelab.com (pix.corelab.com [12.45.169.2]) by ion.gank.org (mail) with ESMTP id 2A4122B247; Tue, 9 Dec 2003 08:50:22 -0600 (CST) From: Craig Boston To: Illia Baidakov Date: Tue, 9 Dec 2003 08:50:16 -0600 User-Agent: KMail/1.5.4 References: <1264617800.20031208170645@newchem.ru> <448yln40ey.fsf@be-well.ilk.org> <92721135.20031209132143@newchem.ru> In-Reply-To: <92721135.20031209132143@newchem.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312090850.16651.craig@meoqu.gank.org> X-Virus-Scanned: by amavisd-new at gank.org cc: stable@freebsd.org Subject: Re: 'long long' warning while compiling mit-kerberos on 4.9-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 14:50:25 -0000 On Tuesday 09 December 2003 04:21 am, Illia Baidakov wrote: > So I trying to ask you ones again: > Is it a best practise to use Heimdal Kerberos on FreeBSD? If it's so I > think I have no limits to orientate myself to use it. I have no problems using MIT Kerberos on a number of FreeBSD servers / workstations. Cy Schubert does a great job of making sure that it works on FreeBSD and most ports that support Kerberos (cyrus-sasl, PostgreSQL, etc) support both the Heimdal and MIT implementations equally well. If you don't want the fuss of trying to port it manually, the work has already been done. See /usr/ports/security/krb5. HTH, Craig From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 10:55:38 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91B6016A4CE for ; Tue, 9 Dec 2003 10:55:38 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA1C143D37 for ; Tue, 9 Dec 2003 10:55:34 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) hB9ItRiF074505; Tue, 9 Dec 2003 10:55:27 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id hB9ItR6C074504; Tue, 9 Dec 2003 10:55:27 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Dec 2003 10:55:27 -0800 (PST) From: Matthew Dillon Message-Id: <200312091855.hB9ItR6C074504@apollo.backplane.com> To: "Luoqi Chen" References: cc: stable@freebsd.org Subject: RE: Bug in i386/i386/trap.c %gs handling on stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 18:55:38 -0000 : :> In i386/i386/trap.c if %gs is invalid... for example, a process with a :> USER_LDT takes an interrupt while exiting, or if %gs is set :> through procfs, :> the fault check must occur regardless of the interrupt nesting :> level because :> mainline code does not push and load a %gs for the kernel. :> :I don't quite get it. There'll be fault only when the kernel tries to :load an invalid %gs. And there's only one place that the kernel would :load a new %gs: during a context switch, which could not take place in :an interrupt context. Hmm. I think you are right. In FreeBSD-5 a context can occur at any time which presumably is why the %gs test was moved to outside the interrupt nesting level check. In FreeBSD-4 a context switch will only occur outside of an interrupt so I guess it can't happen. Well, that isn't entirely true... a context switch has been known to happen inside interrupts in 4.x but those are considered to be bugs :-). In DragonFly an interrupt preemption causes a context switch, then another switch back after the interrupt code finishes or blocks, which is why the problem occured in DFly. :> the situation with a process takes an interrupt while exiting and %fs is :> set to a USER_LDT entry. I have not checked this, but if it is :> true it would :> be a problem in both -current and -stable for the exiting case. :> :It's different for %fs, it holds a valid kernel segment at all time :inside the kernel. :.. :-lq Hmm. But it still must save and restore %fs. If a user program sets up a user LDT, loads %fs with a valid value, and then deletes the user LDT, %fs will be bad. The only thing that saves us in 4.x is the fact that the interrupt nesting level will be 0 when the first interrupt restores %fs. That is, it will have already decremented intr_nesting_level. It will take the fault but properly deal with the consequences, and a nested interrupt will be saving and restoring the kernel %fs that the first interrupt loaded up. In 5.x it looks a lot more fragile but I guess the same thing applies, just barely. -Matt Matthew Dillon From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 14:23:30 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFA3116A4CE for ; Tue, 9 Dec 2003 14:23:30 -0800 (PST) Received: from mail.evild.eu.org (27-moc-4.acn.waw.pl [212.76.43.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1534D43D28 for ; Tue, 9 Dec 2003 14:23:29 -0800 (PST) (envelope-from evild@acn.pl) Received: from n9 (nat-b.acn.pl [212.76.39.249]) by mail.evild.eu.org (Postfix) with ESMTP id B52361FC5 for ; Tue, 9 Dec 2003 23:22:05 +0100 (CET) From: "Michal Malanowicz" To: Date: Tue, 9 Dec 2003 23:23:23 +0100 Message-ID: <000101c3bea3$0edfcac0$ae07400a@n9> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: RE: Problem with Sil 680 RAID card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 22:23:30 -0000 Anyone who has problems with Silicon Image (Sil 680) based RAID cards (me till now) here is the solution: I needed 3 hard drives to create a mirror, one to boot the system from and 2 others connected to RAID controler. BIOS in controller card was left alone - no RAID created. I booted FreeBSD from first drive, used: atacontrol create RAID1 ad4 ad6 to create mirror from 2 disks connected to controler card. Then, after rebooting and disconecting the first hard drive (ad0) I started to install FreeBSD again - now on ar0. atacontrol must have written something to mbr on this disks or do something similar... I think. Now I have: blue# pciconf -l -v atapci1@pci0:9:0: class=0x010400 card=0x36801095 chip=0x06801095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'SiI 0680 (Was: PCI-0648) Ultra ATA133 EIDE Controller' class = mass storage subclass = RAID blue# mount /dev/ar0s1a on / (ufs, local) blue# atacontrol status ar0 ar0: ATA RAID1 subdisks: ad4 ad6 status: READY :) Mike Malanowicz From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 16:50:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B38316A4CE for ; Tue, 9 Dec 2003 16:50:00 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FA6A43D28 for ; Tue, 9 Dec 2003 16:49:59 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 8479972DC3; Tue, 9 Dec 2003 16:49:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 7F90672DB8; Tue, 9 Dec 2003 16:49:59 -0800 (PST) Date: Tue, 9 Dec 2003 16:49:59 -0800 (PST) From: Doug White To: jimmie james In-Reply-To: <20031209075004.72395.qmail@web13422.mail.yahoo.com> Message-ID: <20031209164633.N25346@carver.gumbysoft.com> References: <20031209075004.72395.qmail@web13422.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: strange log messages X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 00:50:00 -0000 On Mon, 8 Dec 2003, jimmie james wrote: > Howdy, > > I just noticed these tonight after a cvsup/build > world/kernel/install world around 2am EST on the 8th > of dec. > > Dec 9 02:14:23 fortytwo /kernel: issignal > Dec 9 02:16:17 fortytwo /kernel: issignal > Dec 9 02:17:50 fortytwo /kernel: issignal This is being generated by this chunk of code from src/sys/kern/kern_sig.c: case (int)SIG_IGN: /* * Masking above should prevent us ever trying * to take action on an ignored signal other * than SIGCONT, unless process is traced. */ if ((prop & SA_CONT) == 0 && (p->p_flag & P_TRACED) == 0) printf("issignal\n"); break; /* == ignore */ So you have a process being traced that is getting ignored signals. I suspect the message is a leftover debugging prinf and should be harmless. You can file a PR to get this removed if you like. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 17:48:36 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46E0716A4CE for ; Tue, 9 Dec 2003 17:48:36 -0800 (PST) Received: from sirius.firepipe.net (sirius.firepipe.net [69.13.116.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9E6343D1F for ; Tue, 9 Dec 2003 17:48:35 -0800 (PST) (envelope-from will@csociety.org) Received: by sirius.firepipe.net (Postfix, from userid 1000) id 48BA017A96; Tue, 9 Dec 2003 20:48:35 -0500 (EST) Date: Tue, 9 Dec 2003 20:48:35 -0500 From: Will Andrews To: stable@freebsd.org Message-ID: <20031210014835.GI431@sirius.firepipe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: -stable floppies broken... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 01:48:36 -0000 Hello, On both JPSNAP and SESNAP, the STABLE floppies don't build. Guess somebody made a driver too big or something. See: http://snapshots.jp.FreeBSD.org:8021/pub/FreeBSD/snapshots/i386/4.9-STABLE-20031210-JPSNAP.log http://snapshots.se.freebsd.org/i386/4.9-STABLE-20031209-SESNAP.log Anyone know what's going on? This has been broken since about 11/25... regards, -- wca (not subscribed to -stable) From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 20:08:55 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D781016A4CE for ; Tue, 9 Dec 2003 20:08:55 -0800 (PST) Received: from access.inet.co.th (access.inet.co.th [203.151.127.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E58743D09 for ; Tue, 9 Dec 2003 20:08:53 -0800 (PST) (envelope-from pirat@access.inet.co.th) Received: from firak.thai-aec.org (TruPPPv92-230-76.inet.co.th [203.151.230.76]) by access.inet.co.th (8.12.5/8.12.5) with ESMTP id hBA48lSi026459; Wed, 10 Dec 2003 11:08:48 +0700 (ICT) (envelope-from pirat@access.inet.co.th) Received: from firak.thai-aec.org (localhost.thai-aec.org [127.0.0.1]) by firak.thai-aec.org (8.12.10/8.12.10) with ESMTP id hBA491Vm003892; Wed, 10 Dec 2003 11:09:01 +0700 (ICT) (envelope-from pirat@access.inet.co.th) Received: (from pirat@localhost) by firak.thai-aec.org (8.12.10/8.12.10/Submit) id hBA48vnT003891; Wed, 10 Dec 2003 11:08:57 +0700 (ICT) (envelope-from pirat@access.inet.co.th) X-Authentication-Warning: firak.thai-aec.org: pirat set sender to pirat@access.inet.co.th using -f Date: Wed, 10 Dec 2003 11:08:57 +0700 From: pirat To: freebsd-stable@FreeBSD.ORG Message-ID: <20031210040857.GA960@thai-aec.org> Mime-Version: 1.0 Content-Type: text/plain; charset=tis-620 Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD firak.thai-aec.org 4.9-STABLE FreeBSD 4.9-STABLE www-home-page: http://www.thai-aec.org www-FreeBSD-page: http://www.thai.net/makham cc: Gregory Bond Subject: newfs for insufficient inodes file system X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 04:08:56 -0000 hi sirs, four months ago, i faced problem of insufficient inodes for /usr and one of solution for that, from Gregory Bond, was that to backup and do a newfs for that file system. today the situation become worst since i can not do any portupgrade even /usr/local is a separate file system though. am not an expert in FreeBSD but a plain user instead. i have backed /usr up already and going to do newfs on that. my questions are that 1) should i drop into a single mode first ? 2) what parameter for newfs to pass to (i used sysinstall to do that and did make world and friends to upgrade my machine) ? below are my uname and informations about /usr [firak] ~ # uname -a FreeBSD firak.thai-aec.org 4.9-STABLE FreeBSD 4.9-STABLE #7: Sun Dec 7 10:19:07 ICT 2003 firak@firak.thai-aec.org:/var/obj/var/src/sys/Firak i386 [firak] ~ # newfs -N /dev/ad0s1f Warning: Block size and bytes per inode restrict cylinders per group to 89. /dev/ad0s1f: 1740800 sectors in 425 cylinders of 1 tracks, 4096 sectors 850.0MB in 5 cyl groups (89 c/g, 178.00MB/g, 21504 i/g) super-block backups (for fsck -b #) at: 32, 364576, 729120, 1093664, 1458208 any helps and hints are welcome and appreciated. with best regards, psr http://www.thai-aec.org http://www.thai.net/makham From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 20:21:07 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFD8516A4CE for ; Tue, 9 Dec 2003 20:21:07 -0800 (PST) Received: from ns1.itga.com.au (ns1.itga.com.au [202.53.40.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 899C943D2B for ; Tue, 9 Dec 2003 20:21:05 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns1.itga.com.au (8.12.9/8.12.9) with ESMTP id hBA4KsR5054569; Wed, 10 Dec 2003 15:20:54 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (localhost [127.0.0.1]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id PAA05574; Wed, 10 Dec 2003 15:20:54 +1100 (EST) Message-Id: <200312100420.PAA05574@lightning.itga.com.au> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.4 From: Gregory Bond To: pirat In-reply-to: Your message of Wed, 10 Dec 2003 11:08:57 +0700. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Dec 2003 15:20:54 +1100 Sender: gnb@itga.com.au cc: freebsd-stable@FreeBSD.ORG Subject: Re: newfs for insufficient inodes file system X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 04:21:07 -0000 Urk, running newfs on /usr (or /) is major-league, heavy-duty, potential-foot-shooting time. Be VERY VERY careful. In fact, if you have to ask how, there is a pretty good chance you'll wind up hopping and bleeding. First step is to run "df -i" and see what the current space/inode usage is. Then check if the standard newfs params look OK (i.e. /usr currently has substantially fewer than the 5x21504 inodes newfs would create in use.) Overall the best bet is probably to back up all the data and re-install, using adjusted newfs parameters if necessary. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 04:06:13 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2192416A4CE for ; Wed, 10 Dec 2003 04:06:13 -0800 (PST) Received: from mail.physik.uni-mainz.de (mail.Physik.Uni-Mainz.DE [134.93.180.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 409F143D09 for ; Wed, 10 Dec 2003 04:06:04 -0800 (PST) (envelope-from ohartman@mail.physik.uni-mainz.de) Received: from mail.physik.uni-mainz.de (mail.physik.uni-mainz.de [134.93.180.161])hBAC62IK070570 for ; Wed, 10 Dec 2003 12:06:03 GMT (envelope-from ohartman@mail.physik.uni-mainz.de) Date: Wed, 10 Dec 2003 13:05:57 +0100 (CET) From: "Hartmann, O." To: freebsd-stable@freebsd.org Message-ID: <20031210124955.C70436@mail.physik.uni-mainz.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: lpd/filter problem since 5.1-p11 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 12:06:13 -0000 Dear Sirs. I will describe a horrible scenario and I need some help, if possible. We use a bunch of printers spread over the whole department and managed by one central FreeBSD 5.1 box via 'magicfilter'. Magicfilter and the queues for each printer worked very good before I did the last update to FreeBSD 5.1-RELEASE-p11. I can not say whether the update caused the problem, but it seems to me to be so. Before changing something to the print queueing system I did a backup (and by the way: the old printcap and magicfilter files also don't work anymore!). I set up queues for completely new printers (HP4600 color lasers with three trays) and for each a new magicfilter filter file. Now I can only print PS files. Each other type of file get unfiltered to the printer, it seems to me that the 'if=' statement of printcap gets never touched. Before the FBSD update to 5.1-p11 we used -p10 and used a bunch of software like ghostscript, psutils and a2ps for supplying conversters to the magicfilter queue. After the update I reinstalled magicfilter, a2ps-a4, psutils-a4 and ghostscript from the ports. So the software is up to date. Whe doing a command like this 'ls -la / | lpr -Ptestprinter' it should be parsed by magicfilter and the last line, default, should convert normal text via a2ps into postscript and reinject the data into the queue and it should be printed by our PS printers. But it didn't. I examined the file generated as a buffer file in the apporpriate spool directory and it is still ascii, that menas the if filter statement has never been touched or did no output. This file is the magicfilter for a testprinter (all others are the same): I also append the printcap file: ------------------------------------------------------------------------- #! /usr/local/bin/magicfilter # # Magic filter setup file for 600 dpi generic PostScript printers # # THIS FILE IS UNTESTED! # # This file is in the public domain. # # This file has been automatically adapted to your system. # ######################################################### # TESTPRINTER # ######################################################### # PostScript #0 %! postscript #0 \004%! postscript 0 %! filter /usr/local/bin/psset -q --setpagedevice="MediaType:(Plain)" 0 \004%! filter /usr/local/bin/psset -q --setpagedevice="MediaType:(Plain)" # TeX DVI 0 \367\002 ffilter /usr/local/bin/dvips -D 600 -R -q -f # compress'd data 0 \037\235 pipe /usr/bin/gzip -cdq # packed, gzipped, frozen and SCO LZH data 0 \037\036 pipe /usr/bin/gzip -cdq 0 \037\213 pipe /usr/bin/gzip -cdq 0 \037\236 pipe /usr/bin/gzip -cdq 0 \037\240 pipe /usr/bin/gzip -cdq # troff documents 0 .\?\?\040 ffilter `/usr/bin/grog -Tps $FILE` 0 .\\\" ffilter `/usr/bin/grog -Tps $FILE` 0 '\\\" ffilter `/usr/bin/grog -Tps $FILE` 0 '.\\\" ffilter `/usr/bin/grog -Tps $FILE` 0 \\\" ffilter `/usr/bin/grog -Tps $FILE` # ditroff 0 "x T ps" filter /usr/bin/grops 0 "x T dvi" pipe /usr/bin/grodvi 0 "x T ascii" pipe /usr/bin/grotty 0 "x T latin1" pipe /usr/bin/grotty 0 "x T lj4" reject Cannot print LaserJet 4 ditroff files. # Portable bit-, grey- and pixmaps 0 P1\n pipe /usr/local/bin/pnmtops -scale 1000 -dpi 600 2>/dev/null 0 P2\n pipe /usr/local/bin/pnmtops -scale 1000 -dpi 600 2>/dev/null 0 P3\n pipe /usr/local/bin/pnmtops -scale 1000 -dpi 600 2>/dev/null 0 P4\n pipe /usr/local/bin/pnmtops -scale 1000 -dpi 600 2>/dev/null 0 P5\n pipe /usr/local/bin/pnmtops -scale 1000 -dpi 600 2>/dev/null 0 P6\n pipe /usr/local/bin/pnmtops -scale 1000 -dpi 600 2>/dev/null # HP Printer Control Language (PCL) -- assume start with reset code 0 \033E\033 reject Cannot print PCL files on this printer. # HP Printer Job Language (PJL) #0 \033%-12345X reject Cannot print PJL files on this printer. #0 "@PJL " reject Cannot print PJL files on this printer. #0 @PJL\t reject Cannot print PJL files on this printer. #0 @PJL\r reject Cannot print PJL files on this printer. #0 @PJL\n reject Cannot print PJL files on this printer. 0 \033%-12345X cat 0 "@PJL " cat 0 @PJL\t cat 0 @PJL\r cat 0 @PJL\n cat # GIF files 0 GIF87a pipe /usr/local/bin/giftopnm 2>/dev/null 0 GIF89a pipe /usr/local/bin/giftopnm 2>/dev/null # JFIF (JPEG) files 0 \377\330\377\340\?\?JFIF\0 pipe /usr/local/bin/djpeg -pnm # TIFF files (the last two bytes of the "magic" is really a version number; # but the magic is really lame and as far as I have understood the version # number has never changed and never will, so we include it.) 0 MM\0\x2a pipe /usr/local/bin/tifftopnm 2>/dev/null 0 II\x2a\0 pipe /usr/local/bin/tifftopnm 2>/dev/null # BMP files (even lousier magic -- Microsoft strikes again!) 0 BM\?\?\?\?\?\?\?\?\?\?\?\?\x0c pipe \ /usr/local/bin/bmptoppm 2>/dev/null 0 BM\?\?\?\?\?\?\?\?\?\?\?\?\x40 pipe \ /usr/local/bin/bmptoppm 2>/dev/null 0 BM\?\?\?\?\?\?\?\?\?\?\?\?\x28 pipe \ /usr/local/bin/bmptoppm 2>/dev/null # Sun rasterfiles 0 \x59\xa6\x6a\x95 pipe /usr/local/bin/rasttopnm 2>/dev/null # SGI Imagelib (IRIS RGB) files 0 \x1\xda pipe /usr/local/bin/sgitopnm 2>/dev/null 0 \xda\x1 pipe /usr/local/bin/sgitopnm 2>/dev/null # FIG files; reported by Steven P. Hill 0 #FIG reject Cannot print FIG files on this printer. # # Standard rejects... things we don't want to print # # Various archive formats 257 ustar\0 reject Attempted to print a tar file. 257 "ustar \0" reject Attempted to print a tar file. 0 07070 reject Attempted to print a cpio file. 0 PK\3\4 reject Attempted to print a zip file. 20 \xdc\xa7\xc7\xfd reject Attempted to print a zoo file. # Binaries (Linux): reject with email message 0 \013\1d\0 reject Attempted to print a compiled binary. 0 \100\1d\0 reject Attempted to print a compiled binary. 0 \007\1d\0 reject Attempted to print a compiled binary. 0 \314\0d\0 reject Attempted to print a compiled binary. 0 \177ELF reject Attempted to print an ELF object. 0 \007\001\0 reject Attempted to print an object file. 216 \021\001\0\0 reject Attempted to print a core dump file. 0 ! reject Attempted to print an archive. 0 = reject Attempted to print an archive. # Don't confuse this one with troff! 0 .snd reject Attempted to print Sun/NeXT audio data. # optimistic troff magic 0 . ffilter `/usr/bin/grog -Tps $FILE` # wacko troff magic 0 ''' ffilter `/usr/bin/grog -Tps $FILE` # PDF files 0 %PDF ffilter `/usr/local/bin/pdf2ps $FILE - 2>/dev/null` # Default entry -- for normal (text) files. MUST BE LAST. default pipe /usr/local/bin/a2ps -q -R --columns=1 -B -j --ppd -k --prologue=color -o - -------------------------------------------------------------------------- This is the printcap file # @(#)printcap 5.3 (Berkeley) 6/30/90 #lp|local line printer:\ # :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: ################################################################################# # # # Drucker: HP LJ4000, Raum 05 273, 5. Stock # # # ################################################################################# ## lj4000 duplex automatische Schachtwahl lj4000-00-05-273-auto-d|lj4000d:\ :rm=134.93.181.145:\ :rp=auto1:\ :sd=/var/spool/lpd/lj4000-00-05-273-auto-d:\ :lf=/var/spool/lpd/lj4000-00-05-273-auto-d/log:\ :lo=/var/spool/lpd/lj4000-00-05-273-auto-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4000-00-05-273-auto-d-filter:\ :mx#0:\ :rw:\ :sh: ## lj4000 duplex Schacht 1 lj4000-00-05-273-f1-d:\ :rm=134.93.181.145:\ :rp=auto1:\ :sd=/var/spool/lpd/lj4000-00-05-273-f1-d:\ :lf=/var/spool/lpd/lj4000-00-05-273-f1-d/log:\ :lo=/var/spool/lpd/lj4000-00-05-273-f1-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4000-00-05-273-f1-d-filter:\ :mx#0:\ :rw:\ :sh: ## lj4000 duplex Schacht 2 lj4000-00-05-273-f2-d:\ :rm=134.93.181.145:\ :rp=auto1:\ :sd=/var/spool/lpd/lj4000-00-05-273-f2-d:\ :lf=/var/spool/lpd/lj4000-00-05-273-f2-d/log:\ :lo=/var/spool/lpd/lj4000-00-05-273-f2-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4000-00-05-273-f2-d-filter:\ :mx#0:\ :rw:\ :sh: ## lj4000 duplex Schacht 3 lj4000-00-05-273-f3-d:\ :rm=134.93.181.145:\ :rp=auto1:\ :sd=/var/spool/lpd/lj4000-00-05-273-f3-d:\ :lf=/var/spool/lpd/lj4000-00-05-273-f3-d/log:\ :lo=/var/spool/lpd/lj4000-00-05-273-f3-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4000-00-05-273-f3-d-filter:\ :mx#0:\ :rw:\ :sh: ## lj4000 simplex automatische Schachtwahl lj4000-00-05-273-auto-s|lj4000s:\ :rm=134.93.181.145:\ :rp=auto1:\ :sd=/var/spool/lpd/lj4000-00-05-273-auto-s:\ :lf=/var/spool/lpd/lj4000-00-05-273-auto-s/log:\ :lo=/var/spool/lpd/lj4000-00-05-273-auto-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4000-00-05-273-auto-s-filter:\ :mx#0:\ :rw:\ :sh: ## lj4000 simplex Schacht 1 lj4000-00-05-273-f1-s:\ :rm=134.93.181.145:\ :rp=auto1:\ :sd=/var/spool/lpd/lj4000-00-05-273-f1-s:\ :lf=/var/spool/lpd/lj4000-00-05-273-f1-s/log:\ :lo=/var/spool/lpd/lj4000-00-05-273-f1-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4000-00-05-273-f1-s-filter:\ :mx#0:\ :rw:\ :sh: ## lj4000 simplex Schacht 2 lj4000-00-05-273-f2-s:\ :rm=134.93.181.145:\ :rp=auto1:\ :sd=/var/spool/lpd/lj4000-00-05-273-f2-s:\ :lf=/var/spool/lpd/lj4000-00-05-273-f2-s/log:\ :lo=/var/spool/lpd/lj4000-00-05-273-f2-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4000-00-05-273-f2-s-filter:\ :mx#0:\ :rw:\ :sh: ## lj4000 simplex Schacht 3 lj4000-00-05-273-f3-s:\ :rm=134.93.181.145:\ :rp=auto1:\ :sd=/var/spool/lpd/lj4000-00-05-273-f3-s:\ :lf=/var/spool/lpd/lj4000-00-05-273-f3-s/log:\ :lo=/var/spool/lpd/lj4000-00-05-273-f3-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4000-00-05-273-f3-s-filter:\ :mx#0:\ :rw:\ :sh: ## lj4000 Windowsdrucker lj4000-00-05-273-raw|lj4000raw:\ :rm=134.93.181.145:\ :rp=auto1:\ :sd=/var/spool/lpd/lj4000-00-05-273-raw:\ :lf=/var/spool/lpd/lj4000-00-05-273-raw/log:\ :lo=/var/spool/lpd/lj4000-00-05-273-raw/lock:\ :af=/var/log/lpd-acct:\ :mx#0:\ :rw:\ :sh: ################################################################################# # # # Drucker: HP LJC4500, Raum 05 273, 5. Stock # # # ################################################################################# ## ljc4500 duplex automatische Schachtwahl lj4500-00-05-273-auto-d:\ :rm=134.93.181.145:\ :rp=auto2:\ :sd=/var/spool/lpd/lj4500-00-05-273-auto-d:\ :lf=/var/spool/lpd/lj4500-00-05-273-auto-d/log:\ :lo=/var/spool/lpd/lj4500-00-05-273-auto-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4500-00-05-273-auto-d-filter:\ :mx#0:\ :rw:\ :sh: ## ljc4500 duplex Schacht 1 lj4500-00-05-273-f1-d:\ :rm=134.93.181.145:\ :rp=auto2:\ :sd=/var/spool/lpd/lj4500-00-05-273-f1-d:\ :lf=/var/spool/lpd/lj4500-00-05-273-f1-d/log:\ :lo=/var/spool/lpd/lj4500-00-05-273-f1-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4500-00-05-273-f1-d-filter:\ :mx#0:\ :rw:\ :sh: ## ljc4500 duplex Schacht 2 lj4500-00-05-273-f2-d:\ :rm=134.93.181.145:\ :rp=auto2:\ :sd=/var/spool/lpd/lj4500-00-05-273-f2-d:\ :lf=/var/spool/lpd/lj4500-00-05-273-f2-d/log:\ :lo=/var/spool/lpd/lj4500-00-05-273-f2-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4500-00-05-273-f2-d-filter:\ :mx#0:\ :rw:\ :sh: ## ljc4500 duplex Schacht 3 lj4500-00-05-273-f3-d:\ :rm=134.93.181.145:\ :rp=auto2:\ :sd=/var/spool/lpd/lj4500-00-05-273-f3-d:\ :lf=/var/spool/lpd/lj4500-00-05-273-f3-d/log:\ :lo=/var/spool/lpd/lj4500-00-05-273-f3-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4500-00-05-273-f3-d-filter:\ :mx#0:\ :rw:\ :sh: ## ljc4500 simplex automatische Schachtwahl lj4500-00-05-273-auto-s|lj4500c:\ :rm=134.93.181.145:\ :rp=auto2:\ :sd=/var/spool/lpd/lj4500-00-05-273-auto-s:\ :lf=/var/spool/lpd/lj4500-00-05-273-auto-s/log:\ :lo=/var/spool/lpd/lj4500-00-05-273-auto-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4500-00-05-273-auto-s-filter:\ :mx#0:\ :rw:\ :sh: ## ljc4500 simplex Schacht 1 lj4500-00-05-273-f1-s:\ :rm=134.93.181.145:\ :rp=auto2:\ :sd=/var/spool/lpd/lj4500-00-05-273-f1-s:\ :lf=/var/spool/lpd/lj4500-00-05-273-f1-s/log:\ :lo=/var/spool/lpd/lj4500-00-05-273-f1-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4500-00-05-273-f1-s-filter:\ :mx#0:\ :rw:\ :sh: ## ljc4500 simplex Schacht 2 (Folie) lj4500-00-05-273-f2-s|lj4500cf:\ :rm=134.93.181.145:\ :rp=auto2:\ :sd=/var/spool/lpd/lj4500-00-05-273-f2-s:\ :lf=/var/spool/lpd/lj4500-00-05-273-f2-s/log:\ :lo=/var/spool/lpd/lj4500-00-05-273-f2-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4500-00-05-273-f2-s-filter:\ :mx#0:\ :rw:\ :sh: ## ljc4500 simplex Schacht 3 lj4500-00-05-273-f3-s:\ :rm=134.93.181.145:\ :rp=auto2:\ :sd=/var/spool/lpd/lj4500-00-05-273-f3-s:\ :lf=/var/spool/lpd/lj4500-00-05-273-f3-s/log:\ :lo=/var/spool/lpd/lj4500-00-05-273-f3-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4500-00-05-273-f3-s-filter:\ :mx#0:\ :rw:\ :sh: ## ljc4500 Windowsdrucker lj4500-00-05-273-raw|lj4500raw:\ :rm=134.93.181.145:\ :rp=auto2:\ :sd=/var/spool/lpd/lj4500-00-05-273-raw:\ :lf=/var/spool/lpd/lj4500-00-05-273-raw/log:\ :lo=/var/spool/lpd/lj4500-00-05-273-raw/lock:\ :af=/var/log/lpd-acct:\ :mx#0:\ :rw:\ :sh: ################################################################################# # # # Drucker: HP DJ1120C, A3, Raum 05 273, 5. Stock # # # ################################################################################# ## dj1120c automatik dj1120-00-05-273-auto|dj1120c:\ :rm=134.93.181.145:\ :rp=auto3:\ :sd=/var/spool/lpd/dj1120-00-05-273-auto:\ :lf=/var/spool/lpd/dj1120-00-05-273-auto/log:\ :lo=/var/spool/lpd/dj1120-00-05-273-auto/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/dj1120-00-05-273-auto-filter:\ :mx#0:\ :rw:\ :sh: ## dj1120c Windowsdrucker dj1120-00-05-273-raw|dj1120craw:\ :rm=134.93.181.145:\ :rp=auto3:\ :sd=/var/spool/lpd/dj1120-00-05-273-raw:\ :lf=/var/spool/lpd/dj1120-00-05-273-raw/log:\ :lo=/var/spool/lpd/dj1120-00-05-273-raw/lock:\ :af=/var/log/lpd-acct:\ :mx#0:\ :rw:\ :sh: ################################################################################# # # # Drucker: HP LJIII, Raum 05 131, 5. Stock, Terminalraum # # # ################################################################################# ## lj3 automatische Schachtwahl lj3-00-05-131-auto|lj3:\ :rm=134.93.180.198:\ :rp=lpt1:\ :sd=/var/spool/lpd/lj3-00-05-131-auto:\ :lf=/var/spool/lpd/lj3-00-05-131-auto/log:\ :lo=/var/spool/lpd/lj3-00-05-131-auto/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj3-00-05-131-auto-filter:\ :mx#0:\ :rw:\ :sh: ## lj3 Windowsdrucker lj3-00-05-131-raw|lj3raw:\ :rm=134.93.180.198:\ :rp=lpt1:\ :sd=/var/spool/lpd/lj3-00-05-131-raw:\ :lf=/var/spool/lpd/lj3-00-05-131-raw/log:\ :lo=/var/spool/lpd/lj3-00-05-131-raw/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj3-00-05-131-raw-filter:\ :mx#0:\ :rw:\ :sh: ################################################################################# # # # Drucker: HP LJC4600, Raum 05 162, 5. Stock # # # ################################################################################# ## ljc4600 simplex automatische Schachtwahl lj4600-00-05-162-auto-s:\ :rm=134.93.180.217:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-05-162-auto-s:\ :lf=/var/spool/lpd/lj4600-00-05-162-auto-s/log:\ :lo=/var/spool/lpd/lj4600-00-05-162-auto-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-05-162-auto-s-filter:\ :mx#0:\ :rw:\ :sh: ## ljc4600 duplex automatische Schachtwahl lp|lj4600-00-05-162-auto-d:\ :rm=134.93.180.217:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-05-162-auto-d:\ :lf=/var/spool/lpd/lj4600-00-05-162-auto-d/log:\ :lo=/var/spool/lpd/lj4600-00-05-162-auto-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-05-162-auto-d-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 Windowsdrucker lj4600-00-05-162-raw:\ :rm=134.93.180.217:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-05-162-raw:\ :lf=/var/spool/lpd/lj4600-00-05-162-raw/log:\ :lo=/var/spool/lpd/lj4600-00-05-162-raw/lock:\ :af=/var/log/lpd-acct:\ :rw:\ :mx#0:\ :sh: ## ljc4600 simplex Schacht 1 lj4600-00-05-162-f1-s:\ :rm=134.93.180.217:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-05-162-f1-s:\ :lf=/var/spool/lpd/lj4600-00-05-162-f1-s/log:\ :lo=/var/spool/lpd/lj4600-00-05-162-f1-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-05-162-f1-s-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 simplex Schacht 2 lj4600-00-05-162-f2-s:\ :rm=134.93.180.217:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-05-162-f2-s:\ :lf=/var/spool/lpd/lj4600-00-05-162-f2-s/log:\ :lo=/var/spool/lpd/lj4600-00-05-162-f2-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-05-162-f2-s-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 simplex Schacht 3 lj4600-00-05-162-f3-s:\ :rm=134.93.180.217:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-05-162-f3-s:\ :lf=/var/spool/lpd/lj4600-00-05-162-f3-s/log:\ :lo=/var/spool/lpd/lj4600-00-05-162-f3-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-05-162-f3-s-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 duplex Schacht 1 lj4600-00-05-162-f1-d:\ :rm=134.93.180.217:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-05-162-f1-d:\ :lf=/var/spool/lpd/lj4600-00-05-162-f1-d/log:\ :lo=/var/spool/lpd/lj4600-00-05-162-f1-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-05-162-f1-d-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 duplex Schacht 2 lj4600-00-05-162-f2-d:\ :rm=134.93.180.217:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-05-162-f2-d:\ :lf=/var/spool/lpd/lj4600-00-05-162-f2-d/log:\ :lo=/var/spool/lpd/lj4600-00-05-162-f2-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-05-162-f2-d-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 duplex Schacht 3 lj4600-00-05-162-f3-d:\ :rm=134.93.180.217:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-05-162-f3-d:\ :lf=/var/spool/lpd/lj4600-00-05-162-f3-d/log:\ :lo=/var/spool/lpd/lj4600-00-05-162-f3-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-05-162-f3-d-filter:\ :rw:\ :mx#0:\ :sh: ################################################################################# # # # Drucker: HP LJC4600, Raum 04 181, 4. Stock # # # ################################################################################# ## ljc4600 simplex automatische Schachtwahl lj4600-00-04-181-auto-s:\ :rm=134.93.180.160:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-04-181-auto-s:\ :lf=/var/spool/lpd/lj4600-00-04-181-auto-s/log:\ :lo=/var/spool/lpd/lj4600-00-04-181-auto-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-auto-s-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 duplex automatische Schachtwahl lj4600-00-04-181-auto-d:\ :rm=134.93.180.160:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-04-181-auto-d:\ :lf=/var/spool/lpd/lj4600-00-04-181-auto-d/log:\ :lo=/var/spool/lpd/lj4600-00-04-181-auto-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-auto-d-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 Windowsdrucker lj4600-00-04-181-raw:\ :rm=134.93.180.160:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-04-181-raw:\ :lf=/var/spool/lpd/lj4600-00-04-181-raw/log:\ :lo=/var/spool/lpd/lj4600-00-04-181-raw/lock:\ :af=/var/log/lpd-acct:\ :rw:\ :mx#0:\ :sh: ## ljc4600 duplex Schacht 1 lj4600-00-04-181-f1-d:\ :rm=134.93.180.160:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-04-181-f1-d:\ :lf=/var/spool/lpd/lj4600-00-04-181-f1-d/log:\ :lo=/var/spool/lpd/lj4600-00-04-181-f1-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f1-d-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 duplex Schacht 2 lj4600-00-04-181-f2-d:\ :rm=134.93.180.160:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-04-181-f2-d:\ :lf=/var/spool/lpd/lj4600-00-04-181-f2-d/log:\ :lo=/var/spool/lpd/lj4600-00-04-181-f2-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f2-d-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 duplex Schacht 3 lj4600-00-04-181-f3-d:\ :rm=134.93.180.160:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-04-181-f3-d:\ :lf=/var/spool/lpd/lj4600-00-04-181-f3-d/log:\ :lo=/var/spool/lpd/lj4600-00-04-181-f3-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f3-d-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 simplex Schacht 1 lj4600-00-04-181-f1-s:\ :rm=134.93.180.160:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-04-181-f1-s:\ :lf=/var/spool/lpd/lj4600-00-04-181-f1-s/log:\ :lo=/var/spool/lpd/lj4600-00-04-181-f1-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f1-s-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 simplex Schacht 2 lj4600-00-04-181-f2-s:\ :rm=134.93.180.160:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-04-181-f2-s:\ :lf=/var/spool/lpd/lj4600-00-04-181-f2-s/log:\ :lo=/var/spool/lpd/lj4600-00-04-181-f2-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f2-s-filter:\ :rw:\ :mx#0:\ :sh: ## ljc4600 simplex Schacht 3 lj4600-00-04-181-f3-s:\ :rm=134.93.180.160:\ :rp=auto:\ :sd=/var/spool/lpd/lj4600-00-04-181-f3-s:\ :lf=/var/spool/lpd/lj4600-00-04-181-f3-s/log:\ :lo=/var/spool/lpd/lj4600-00-04-181-f3-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f3-s-filter:\ :rw:\ :mx#0:\ :sh: ################################################################################# # # # Drucker: HP LJ4100, Raum 04 181, 4. Stock # # # ################################################################################# ## lj4100 duplex automatische Schachtwahl lj4100-00-04-181-auto-d|lj4100dtnd-auto:\ :rm=134.93.181.142:\ :rp=auto:\ :sd=/var/spool/lpd/lj4100-00-04-181-auto-d:\ :lf=/var/spool/lpd/lj4100-00-04-181-auto-d/log:\ :lo=/var/spool/lpd/lj4100-00-04-181-auto-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-auto-d-filter:\ :rw:\ :mx#0:\ :sh: ## lj4100 simplex automatische Schachtwahl lj4100-00-04-181-auto-s|lj4100dtns-auto:\ :rm=134.93.181.142:\ :rp=auto:\ :sd=/var/spool/lpd/lj4100-00-04-181-auto-s:\ :lf=/var/spool/lpd/lj4100-00-04-181-auto-s/log:\ :lo=/var/spool/lpd/lj4100-00-04-181-auto-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-auto-s-filter:\ :rw:\ :mx#0:\ :sh: ## lj4100 duplex Schacht 1 lj4100-00-04-181-f1-d:\ :rm=134.93.181.142:\ :rp=auto:\ :sd=/var/spool/lpd/lj4100-00-04-181-f1-d:\ :lf=/var/spool/lpd/lj4100-00-04-181-f1-d/log:\ :lo=/var/spool/lpd/lj4100-00-04-181-f1-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f1-d-filter:\ :rw:\ :mx#0:\ :sh: ## lj4100 duplex Schacht 2 lj4100-00-04-181-f2-d:\ :rm=134.93.181.142:\ :rp=auto:\ :sd=/var/spool/lpd/lj4100-00-04-181-f2-d:\ :lf=/var/spool/lpd/lj4100-00-04-181-f2-d/log:\ :lo=/var/spool/lpd/lj4100-00-04-181-f2-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f2-d-filter:\ :rw:\ :mx#0:\ :sh: ## lj4100 duplex Schacht 3 lj4100-00-04-181-f3-d:\ :rm=134.93.181.142:\ :rp=auto:\ :sd=/var/spool/lpd/lj4100-00-04-181-f3-d:\ :lf=/var/spool/lpd/lj4100-00-04-181-f3-d/log:\ :lo=/var/spool/lpd/lj4100-00-04-181-f3-d/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f3-d-filter:\ :rw:\ :mx#0:\ :sh: ## lj4100 simplex Schacht 1 lj4100-00-04-181-f1-s:\ :rm=134.93.181.142:\ :rp=auto:\ :sd=/var/spool/lpd/lj4100-00-04-181-f1-s:\ :lf=/var/spool/lpd/lj4100-00-04-181-f1-s/log:\ :lo=/var/spool/lpd/lj4100-00-04-181-f1-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f1-s-filter:\ :rw:\ :mx#0:\ :sh: ## lj4100 simplex Schacht 2 lj4100-00-04-181-f2-s:\ :rm=134.93.181.142:\ :rp=auto:\ :sd=/var/spool/lpd/lj4100-00-04-181-f2-s:\ :lf=/var/spool/lpd/lj4100-00-04-181-f2-s/log:\ :lo=/var/spool/lpd/lj4100-00-04-181-f2-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f2-s-filter:\ :rw:\ :mx#0:\ :sh: ## lj4100 simplex Schacht 3 lj4100-00-04-181-f3-s:\ :rm=134.93.181.142:\ :rp=auto:\ :sd=/var/spool/lpd/lj4100-00-04-181-f3-s:\ :lf=/var/spool/lpd/lj4100-00-04-181-f3-s/log:\ :lo=/var/spool/lpd/lj4100-00-04-181-f3-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj4600-00-04-181-f3-s-filter:\ :rw:\ :mx#0:\ :sh: ## lj4100 Windowsdrucker lj4100-00-04-181-raw|lj4100dtn-raw:\ :rm=134.93.181.142:\ :rp=auto:\ :sd=/var/spool/lpd/lj4100-00-04-181-raw:\ :lf=/var/spool/lpd/lj4100-00-04-181-raw/log:\ :lo=/var/spool/lpd/lj4100-00-04-181-raw/lock:\ :af=/var/log/lpd-acct:\ :rw:\ :mx#0:\ :sh: ################################################################################# # # # Drucker: HP LJ1100, Raum 05 233, 5. Stock # # # ################################################################################# ## lj1100 automatische Schachtwahl lj1100-00-05-233-auto-s:\ :rm=134.93.180.76:\ :rp=P1:\ :sd=/var/spool/lpd/lj1100-00-05-233-auto-s:\ :lf=/var/spool/lpd/lj1100-00-05-233-auto-s/log:\ :lo=/var/spool/lpd/lj1100-00-05-233-auto-s/lock:\ :af=/var/log/lpd-acct:\ :if=/usr/local/libexec/magicfilter.local/lj1100-00-05-233-auto-s-filter:\ :mx#0:\ :rw:\ :sh: kurz:\ :rm=134.93.180.217:\ :rp=auto:\ :sd=/var/spool/lpd/kurz:\ :lf=/var/spool/lpd/kurz/log:\ :lo=/var/spool/lpd/kurz/lock:\ :if=/usr/local/libexec/magicfilter/kurz-filter:\ :mx#0:\ :rw:\ :sh: -- MfG O. Hartmann ohartman@mail.physik.uni-mainz.de ------------------------------------------------------------------ Systemadministration des Institutes fuer Physik der Atmosphaere (IPA) ------------------------------------------------------------------ Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 13:28:30 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EE7916A4CE for ; Wed, 10 Dec 2003 13:28:30 -0800 (PST) Received: from fep01-mail.bloor.is.net.cable.rogers.com (fep01-mail.bloor.is.net.cable.rogers.com [66.185.86.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id D008143D29 for ; Wed, 10 Dec 2003 13:28:28 -0800 (PST) (envelope-from mikej@rogers.com) Received: from win2000 ([63.139.3.63]) by fep01-mail.bloor.is.net.cable.rogers.comESMTP <20031210212702.SEEX132452.fep01-mail.bloor.is.net.cable.rogers.com@win2000> for ; Wed, 10 Dec 2003 16:27:02 -0500 From: "Mike Jakubik" To: Date: Wed, 10 Dec 2003 16:29:01 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcO/ZKDmBBC8BawmS0iRp8pHMkF25Q== X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep01-mail.bloor.is.net.cable.rogers.com from [63.139.3.63] using ID at Wed, 10 Dec 2003 16:27:02 -0500 Message-Id: <20031210212702.SEEX132452.fep01-mail.bloor.is.net.cable.rogers.com@win2000> Subject: Failiure in make installworld cvsuped today. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 21:28:30 -0000 Make buildworld and kernel completes OK. Cvsuped just a few minutes ago, and cleaned /usr/obj prior to building. Here is the error. --snip-- -------------------------------------------------------------- >>> Installing everything.. -------------------------------------------------------------- cd /usr/src; make -f Makefile.inc1 install ===> share/info ===> include creating osreldate.h from newvers.sh setvar PARAMFILE /usr/src/include/../sys/sys/param.h; . /usr/src/include/../sys/conf/newvers.sh; echo "$COPYRIGHT" > osreldate.h; echo "#ifdef _KERNEL" >> osreldate.h; echo '#error "osreldate.h must not be used in the kernel, use sys/param.h"' >> osreldate.h; echo "#else" >> osreldate.h; echo \#'undef __FreeBSD_version' >> osreldate.h; echo \#'define __FreeBSD_version' $RELDATE >> osreldate.h; echo "#endif" >> osreldate.h touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 --snip-- Touch is on the system. Thanks. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 01:33:20 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89D4616A4CE for ; Thu, 11 Dec 2003 01:33:20 -0800 (PST) Received: from gx.dnepr.net (gx.dnepr.net [217.198.131.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DF6B43D2E for ; Thu, 11 Dec 2003 01:33:19 -0800 (PST) (envelope-from land@dnepr.net) Received: from land by gx.dnepr.net with local id 1AUNC9-0001VT-10 for stable@freebsd.org; Thu, 11 Dec 2003 11:33:17 +0200 Date: Thu, 11 Dec 2003 11:33:17 +0200 From: Andrey Lakhno To: stable@freebsd.org Message-ID: <20031211093317.GA5309@gx.dnepr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Subject: ipfw fwd to gif interface X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 09:33:20 -0000 Hello, I'v tried to forward all traffic incoming on the interface (tun0) to another one (gif0). And got following kernel message: gif_output: recursively called too many times(2) My configuration: # ifconfig gif0 gif0: flags=8051 mtu 1500 tunnel inet x.x.x.x --> y.y.y.y inet 10.249.1.5 --> 10.249.1.6 netmask 0xfffffffc x.x.x.x is on fxp0, y.y.y.y is on cisco router Traffic is forwarded by the following rule: # ipfw add fwd 10.249.1.6 ip from any to any out recv tun0 Packets matched by this rule, but nothing was going out gif0. -- Andrey Lakhno, land-ripe From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 07:03:05 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1167D16A4CE for ; Thu, 11 Dec 2003 07:03:05 -0800 (PST) Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50DE743D1D for ; Thu, 11 Dec 2003 07:03:02 -0800 (PST) (envelope-from dmitry@atlantis.dp.ua) Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231]) by smtp.atlantis.dp.ua (8.12.6p2/8.12.6) with ESMTP id hBBF2tjN093516 for ; Thu, 11 Dec 2003 17:02:55 +0200 (EET) (envelope-from dmitry@atlantis.dp.ua) Date: Thu, 11 Dec 2003 17:02:55 +0200 (EET) From: Dmitry Pryanishnikov To: stable@freebsd.org Message-ID: <20031211165422.D90261@atlantis.atlantis.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: ipfw fwd to gif interface X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 15:03:05 -0000 Hello! > From: Andrey Lakhno > > I'v tried to forward all traffic incoming on the interface (tun0) to another > one (gif0). And got following kernel message: > gif_output: recursively called too many times(2) > > My configuration: > > # ifconfig gif0 > gif0: flags=8051 mtu 1500 > tunnel inet x.x.x.x --> y.y.y.y > inet 10.249.1.5 --> 10.249.1.6 netmask 0xfffffffc > > x.x.x.x is on fxp0, y.y.y.y is on cisco router > > Traffic is forwarded by the following rule: > # ipfw add fwd 10.249.1.6 ip from any to any out recv tun0 > > Packets matched by this rule, but nothing was going out gif0. Of course, you've created forwarding loop. After getting encapsulated, packets travel through ipfw again, and they obviously have the same receive interface (tun0), so your rule forwarding them back to gif0. You should pass encapsulated traffic before forwarding non-encapsulated one: ipfw add 1010 pass ipencap from x.x.x.x to y.y.y.y ipfw add 1020 fwd 10.249.1.6 ip from any to any out recv tun0 You may want to replace "pass" with "skipto 1030" if you want to shape or count ipencap traffic after these rules. Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 09:28:11 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB50A16A4CE for ; Thu, 11 Dec 2003 09:28:11 -0800 (PST) Received: from queue.paperwork.com (ns.place4us.com [206.8.93.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6ECE743D2E for ; Thu, 11 Dec 2003 09:28:04 -0800 (PST) (envelope-from denon@denon.cx) Received: from ONYX.denon.cx (unknown [206.8.93.100]) by queue.paperwork.com (CCS Enterprise SMTP) with ESMTP id 3CE447527B for ; Thu, 11 Dec 2003 11:37:31 -0600 (CST) Message-Id: <6.0.1.1.2.20031211112710.05535ec0@mail.jon.com> X-Sender: denon@denon.cx (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Thu, 11 Dec 2003 11:27:59 -0600 To: freebsd-stable@freebsd.org From: denon In-Reply-To: <6.0.1.1.2.20031208152409.09cfed60@mail.jon.com> References: <6.0.1.1.2.20031207022844.066a9008@mail.jon.com> <20031207134057.Y7085@carver.gumbysoft.com> <6.0.1.1.2.20031208152409.09cfed60@mail.jon.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 17:28:12 -0000 So there are no other thoughts on this? I kinda figured people were interested in squashing 4.8 bugs left and right .. :) -d At 03:25 PM 12/8/2003, you wrote: >Responses inline: > >At 03:41 PM 12/7/2003, you wrote: >>On Sun, 7 Dec 2003, denon wrote: >> >> > We've been doing more work with VMware and FreeBSD lately. Overall it's >> > been going well, but we have a machine that's giving me grief, and I'm a >> > bit concerned. >> > >> > It's running 4.8-Release, with a single virtual SCSI drive. It's been >> > running fine for months, but as of recently, it's started locking >> up. When >> > it locks up, this is what's in the messages: >> > /kernel: (da0:bt0:0:0:0): CCB 0xca993340 - timed out >> > /kernel: bt0: btdone - Attempt to free non-active BCCB 0xca9933c0 >> >>I wonder if the vmware environment is bug-for-bug compatible with the old >>buslogic hardware :-) > >Sure seems it .. though it was stable for a long time, so I don't know .. > > >>I suspect this is a bug in vmware, where the emulated driver is suffering >>from long-term corruption. 43-day bug, perhaps? >> >>Does stopping and starting VMware clear this up? > >Nope, apparently not .. I tried and its happened again today. Seems to >happen about twice a day, but no pattern to it that I see.. > > >-d >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 14:39:28 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDC9D16A4CF for ; Thu, 11 Dec 2003 14:39:28 -0800 (PST) Received: from fep03-mail.bloor.is.net.cable.rogers.com (fep03-mail.bloor.is.net.cable.rogers.com [66.185.86.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CB7943E4C for ; Thu, 11 Dec 2003 14:21:57 -0800 (PST) (envelope-from mikej@rogers.com) Received: from win2000 ([63.139.3.63]) by fep03-mail.bloor.is.net.cable.rogers.comESMTP <20031211222143.WGBK306659.fep03-mail.bloor.is.net.cable.rogers.com@win2000> for ; Thu, 11 Dec 2003 17:21:43 -0500 From: "Mike Jakubik" To: Date: Thu, 11 Dec 2003 17:22:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <20031210212702.SEEX132452.fep01-mail.bloor.is.net.cable.rogers.com@win2000> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcO/ZKDmBBC8BawmS0iRp8pHMkF25QAz6pHg X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep03-mail.bloor.is.net.cable.rogers.com from [63.139.3.63] using ID at Thu, 11 Dec 2003 17:21:43 -0500 Message-Id: <20031211222143.WGBK306659.fep03-mail.bloor.is.net.cable.rogers.com@win2000> Subject: RE: Failiure in make installworld cvsuped today. (False Alarm) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 22:39:30 -0000 >-----Original Message----- >From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd->stable@freebsd.org] On Behalf Of Mike Jakubik >Sent: Wednesday, December 10, 2003 4:29 PM >To: stable@freebsd.org >Subject: Failiure in make installworld cvsuped today. > >Make buildworld and kernel completes OK. Cvsuped just a few minutes ago, >and >cleaned /usr/obj prior to building. Here is the error. > >--snip-- >-------------------------------------------------------------- >>>> Installing everything.. >-------------------------------------------------------------- >cd /usr/src; make -f Makefile.inc1 install >===> share/info >===> include >creating osreldate.h from newvers.sh >setvar PARAMFILE /usr/src/include/../sys/sys/param.h; . >/usr/src/include/../sys/conf/newvers.sh; echo >"$COPYRIGHT" > osreldate.h; echo "#ifdef _KERNEL" >> >osreldate.h; echo '#error "osreldate.h must not be used >in >the kernel, use sys/param.h"' >> osreldate.h; echo "#else" >> osreldate.h; >echo \#'undef __FreeBSD_version' >> osreldate.h; echo \#'define >__FreeBSD_version' $RELDATE >> osreldate.h; echo "#endif" >> osreldate.h >touch: not found >*** Error code 127 > >Stop in /usr/src/include. >*** Error code 1 Sorry guys, seems like the culprit was bad date setting (clock was set for august, 2003) Thanks. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 20:27:37 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68F2316A4CE for ; Thu, 11 Dec 2003 20:27:37 -0800 (PST) Received: from fep03-mail.bloor.is.net.cable.rogers.com (fep03-mail.bloor.is.net.cable.rogers.com [66.185.86.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13C9043D35 for ; Thu, 11 Dec 2003 20:27:33 -0800 (PST) (envelope-from mikej@rogers.com) Received: from win2000 ([63.139.3.63]) by web01-imail.rogers.com (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20031212000934.TAGY73768.web01-imail.rogers.com@win2000>; Thu, 11 Dec 2003 19:09:34 -0500 From: "Mike Jakubik" To: "'denon'" , Date: Thu, 11 Dec 2003 19:09:20 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <6.0.1.1.2.20031211112710.05535ec0@mail.jon.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcPADFQfEbqn4jPMR2CMcw8/qRHzOQAN6qeA X-Authentication-Info: Submitted using SMTP AUTH LOGIN at web01-imail.rogers.com from [63.139.3.63] using ID at Thu, 11 Dec 2003 19:09:34 -0500 Message-Id: <20031212000934.TAGY73768.web01-imail.rogers.com@win2000> Subject: RE: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 04:27:37 -0000 It seems like this list is dead, and the developers don't care anymore. Current is where it's at. -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of denon Sent: Thursday, December 11, 2003 12:28 PM To: freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare So there are no other thoughts on this? I kinda figured people were interested in squashing 4.8 bugs left and right .. :) -d At 03:25 PM 12/8/2003, you wrote: >Responses inline: > >At 03:41 PM 12/7/2003, you wrote: >>On Sun, 7 Dec 2003, denon wrote: >> >> > We've been doing more work with VMware and FreeBSD lately. Overall it's >> > been going well, but we have a machine that's giving me grief, and I'm a >> > bit concerned. >> > >> > It's running 4.8-Release, with a single virtual SCSI drive. It's been >> > running fine for months, but as of recently, it's started locking >> up. When >> > it locks up, this is what's in the messages: >> > /kernel: (da0:bt0:0:0:0): CCB 0xca993340 - timed out >> > /kernel: bt0: btdone - Attempt to free non-active BCCB 0xca9933c0 >> >>I wonder if the vmware environment is bug-for-bug compatible with the old >>buslogic hardware :-) > >Sure seems it .. though it was stable for a long time, so I don't know .. > > >>I suspect this is a bug in vmware, where the emulated driver is suffering >>from long-term corruption. 43-day bug, perhaps? >> >>Does stopping and starting VMware clear this up? > >Nope, apparently not .. I tried and its happened again today. Seems to >happen about twice a day, but no pattern to it that I see.. > > >-d >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 20:37:26 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DE1916A4CE for ; Thu, 11 Dec 2003 20:37:26 -0800 (PST) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B392143D09 for ; Thu, 11 Dec 2003 20:37:25 -0800 (PST) (envelope-from linimon@lonesome.com) Received: from lonesome.com (cs242719-195.austin.rr.com [24.27.19.195]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.soaustin.net (Postfix) with ESMTP id 098881469A; Thu, 11 Dec 2003 22:37:25 -0600 (CST) Message-ID: <3FD945F3.9000704@lonesome.com> Date: Thu, 11 Dec 2003 22:37:07 -0600 From: Mark Linimon User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030713 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jakubik References: <20031212000934.TAGY73768.web01-imail.rogers.com@win2000> In-Reply-To: <20031212000934.TAGY73768.web01-imail.rogers.com@win2000> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 04:37:26 -0000 Mike Jakubik wrote: >It seems like this list is dead, and the developers don't care anymore. >Current is where it's at. > This seems to be a pretty sweeping generalization based on lack of response to one single problem. In any case the "institutional memory" of FreeBSD with respect to problem reports is the Problem Report database. I'd suggest filing one of those before giving up entirely. Of course, you will no doubt find, in looking through the PR database, that your bug is only one of many, so set your expectations realistically. mcl From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 20:43:44 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94E6D16A4CE for ; Thu, 11 Dec 2003 20:43:44 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D7B443D2D for ; Thu, 11 Dec 2003 20:43:43 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 001D472DB5; Thu, 11 Dec 2003 20:43:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id F215272DAD; Thu, 11 Dec 2003 20:43:42 -0800 (PST) Date: Thu, 11 Dec 2003 20:43:42 -0800 (PST) From: Doug White To: Mike Jakubik In-Reply-To: <20031212000934.TAGY73768.web01-imail.rogers.com@win2000> Message-ID: <20031211203621.S45532@carver.gumbysoft.com> References: <20031212000934.TAGY73768.web01-imail.rogers.com@win2000> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org cc: 'denon' Subject: RE: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 04:43:44 -0000 On Thu, 11 Dec 2003, Mike Jakubik wrote: > It seems like this list is dead, and the developers don't care anymore. > Current is where it's at. This is patently wrong. Please don't do this. Since this is an isolated report in a hard-to-reproduce environment (vmware), its difficult to say if this is a bug in our software or a bug in vmware. Considering the bt driver hasn't been touched in over 4 years, I'm thinking that there may be issues in vmware. I'd follow up with the vmware folks. > > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of denon > Sent: Thursday, December 11, 2003 12:28 PM > To: freebsd-stable@freebsd.org > Subject: Re: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in > VMWare > > So there are no other thoughts on this? I kinda figured people were > interested in squashing 4.8 bugs left and right .. :) > > -d > > At 03:25 PM 12/8/2003, you wrote: > >Responses inline: > > > >At 03:41 PM 12/7/2003, you wrote: > >>On Sun, 7 Dec 2003, denon wrote: > >> > >> > We've been doing more work with VMware and FreeBSD lately. Overall it's > >> > been going well, but we have a machine that's giving me grief, and I'm > a > >> > bit concerned. > >> > > >> > It's running 4.8-Release, with a single virtual SCSI drive. It's been > >> > running fine for months, but as of recently, it's started locking > >> up. When > >> > it locks up, this is what's in the messages: > >> > /kernel: (da0:bt0:0:0:0): CCB 0xca993340 - timed out > >> > /kernel: bt0: btdone - Attempt to free non-active BCCB 0xca9933c0 > >> > >>I wonder if the vmware environment is bug-for-bug compatible with the old > >>buslogic hardware :-) > > > >Sure seems it .. though it was stable for a long time, so I don't know .. > > > > > >>I suspect this is a bug in vmware, where the emulated driver is suffering > >>from long-term corruption. 43-day bug, perhaps? > >> > >>Does stopping and starting VMware clear this up? > > > >Nope, apparently not .. I tried and its happened again today. Seems to > >happen about twice a day, but no pattern to it that I see.. > > > > > >-d > >_______________________________________________ > >freebsd-stable@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 21:03:05 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AD4B16A4CE for ; Thu, 11 Dec 2003 21:03:05 -0800 (PST) Received: from queue.paperwork.com (ns.place4us.com [206.8.93.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6875943D36 for ; Thu, 11 Dec 2003 21:02:59 -0800 (PST) (envelope-from denon@denon.cx) Received: from ONYX.denon.cx (unknown [206.8.93.100]) by queue.paperwork.com (CCS Enterprise SMTP) with ESMTP id 3C89E70CA0; Thu, 11 Dec 2003 23:12:25 -0600 (CST) Message-Id: <6.0.1.1.2.20031211225738.05815900@mail.jon.com> X-Sender: denon@denon.cx (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Thu, 11 Dec 2003 23:02:48 -0600 To: Doug White From: denon In-Reply-To: <20031211203621.S45532@carver.gumbysoft.com> References: <20031212000934.TAGY73768.web01-imail.rogers.com@win2000> <20031211203621.S45532@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-stable@freebsd.org Subject: RE: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 05:03:05 -0000 I agree with your analysis of the 4-year old driver, though it's funny to say it's in a difficult to reproduce environment. In all actuality, a software-based system would be one of the most controlled environments available, removing all variables of heat, flakey hardware, etc, and abstracting them from the hardware layer. VMware seems to be really robust, when the OS plays nicely. (unfortunately win2k under vmware seems to be extremely robust, even under high loads .. what luck.) This aside, I think you'll find that creating a FBSD 4.8 system in a scsi-based vmware disk will reproduce it somewhat consistently. I've spoke with several others having the same issue. You'll also take note that I'm not the guy that said this place was dead. :) Regards, -d At 10:43 PM 12/11/2003, you wrote: >On Thu, 11 Dec 2003, Mike Jakubik wrote: > > > It seems like this list is dead, and the developers don't care anymore. > > Current is where it's at. > >This is patently wrong. Please don't do this. > >Since this is an isolated report in a hard-to-reproduce environment >(vmware), its difficult to say if this is a bug in our software or a bug >in vmware. Considering the bt driver hasn't been touched in over 4 years, >I'm thinking that there may be issues in vmware. > >I'd follow up with the vmware folks. > > > > > -----Original Message----- > > From: owner-freebsd-stable@freebsd.org > > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of denon > > Sent: Thursday, December 11, 2003 12:28 PM > > To: freebsd-stable@freebsd.org > > Subject: Re: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in > > VMWare > > > > So there are no other thoughts on this? I kinda figured people were > > interested in squashing 4.8 bugs left and right .. :) > > > > -d > > > > At 03:25 PM 12/8/2003, you wrote: > > >Responses inline: > > > > > >At 03:41 PM 12/7/2003, you wrote: > > >>On Sun, 7 Dec 2003, denon wrote: > > >> > > >> > We've been doing more work with VMware and FreeBSD lately. Overall > it's > > >> > been going well, but we have a machine that's giving me grief, and I'm > > a > > >> > bit concerned. > > >> > > > >> > It's running 4.8-Release, with a single virtual SCSI drive. It's been > > >> > running fine for months, but as of recently, it's started locking > > >> up. When > > >> > it locks up, this is what's in the messages: > > >> > /kernel: (da0:bt0:0:0:0): CCB 0xca993340 - timed out > > >> > /kernel: bt0: btdone - Attempt to free non-active BCCB 0xca9933c0 > > >> > > >>I wonder if the vmware environment is bug-for-bug compatible with the old > > >>buslogic hardware :-) > > > > > >Sure seems it .. though it was stable for a long time, so I don't know .. > > > > > > > > >>I suspect this is a bug in vmware, where the emulated driver is suffering > > >>from long-term corruption. 43-day bug, perhaps? > > >> > > >>Does stopping and starting VMware clear this up? > > > > > >Nope, apparently not .. I tried and its happened again today. Seems to > > >happen about twice a day, but no pattern to it that I see.. > > > > > > > > >-d > > >_______________________________________________ > > >freebsd-stable@freebsd.org mailing list > > >http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > >-- >Doug White | FreeBSD: The Power to Serve >dwhite@gumbysoft.com | www.FreeBSD.org >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 05:01:03 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E30916A4CE for ; Fri, 12 Dec 2003 05:01:03 -0800 (PST) Received: from mail.qbrick.com (mail.qbrick.com [62.13.40.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DA7543D45 for ; Fri, 12 Dec 2003 05:01:01 -0800 (PST) (envelope-from johan@qbrick.com) Received: from localhost (localhost [127.0.0.1]) by mail.qbrick.com (Postfix) with ESMTP id 4384878057 for ; Fri, 12 Dec 2003 14:00:59 +0100 (CET) Received: from qbrick.com (unknown [62.13.40.34]) by mail.qbrick.com (Postfix) with ESMTP id 9122E78056 for ; Fri, 12 Dec 2003 14:00:57 +0100 (CET) Message-ID: <3FD9BC09.9020302@qbrick.com> Date: Fri, 12 Dec 2003 14:00:57 +0100 From: =?ISO-8859-1?Q?Johan_Bj=F6rk?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5.1) Gecko/20031202 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.82.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavis at mail.qbrick.com. Support FreeBSD Subject: nfs_getpages: error 70 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 13:01:03 -0000 Hi folks, I have problems with a NFS client. We run HelixServer (realnetwork.com) on a FreeBSD 4.9-RC. For a while now I see lots of nfs_getpages: error 70 and vm_fault: pager read error, pid xxxx in /var/log/messages. Turning Helix into debug mode says that it caught Signal 11 at the same time the kernel is reporting the error. In fstab my only options for nfs is ro,noatime,noexec. I search the nfs/nfsproto.h for 70 (did I found the right code?) nfsproto.h:#define NFSERR_STALE 70 Thats sounds like a timeout problem with the NFS server? Checked for CRC error, none. Change the ethernet cable, still errors. Is there some other option that I should use with mount_nfs? The NFS server does not log any errors. I don't use rpc.statd. (Search google.com, found nothing about error 70) What should I try to debug the problem? Any other idea? netstat -s udp: 295182895 datagrams received 0 with incomplete header 10 with bad data length field 49361 with bad checksum 3993 with no checksum 12005 dropped due to no socket 20374 broadcast/multicast datagrams dropped due to no socket 2776675 dropped due to full socket buffers 0 not for hashed pcb 292324470 delivered 916970862 datagrams output ip: 924177006 total packets received 0 bad header checksums 0 with size smaller than minimum 0 with data size < data length 0 with ip length > max ip packet size 0 with header length < data size 0 with data length < header length 0 with bad options 0 with incorrect version number 395847710 fragments received 0 fragments dropped (dup or out of space) 173 fragments dropped after timeout 65388970 packets reassembled ok 591382679 packets for this host 2335290 packets for unknown/unsupported protocol 0 packets forwarded (0 packets fast forwarded) 297 packets not forwardable 0 packets received for unknown multicast group 0 redirects sent 1426827921 packets sent from this host 0 packets sent with fabricated ip header 44620 output packets dropped due to no bufs, etc. 0 output packets discarded due to no route 165 output datagrams fragmented 352 fragments created 0 datagrams that can't be fragmented 0 tunneling packets that can't find gif 0 datagrams with bad address in header nfsstat -c Client Info: Rpc Counts: Getattr Setattr Lookup Readlink Read Write Create Remove 2098513 0 181623 2 210688645 0 0 0 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 0 0 0 0 0 952 0 5390649 Mknod Fsstat Fsinfo PathConf Commit GLease Vacate Evict 0 972 12 0 0 0 0 0 Rpc Info: TimedOut Invalid X Replies Retries Requests 0 0 1494 30680 218359803 Cache Info: Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses 31881136 5697424 7730350 181623 12737239 175415 0 0 BioRLHits Misses BioD Hits Misses DirE Hits Misses 0 2 971 951 943 0 -- Cheers Johan Björk Public PGPkey: http://www.qbrick.com/pgpkey/johan.asc From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 11:02:41 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B1C516A4CE for ; Fri, 12 Dec 2003 11:02:41 -0800 (PST) Received: from hermes.oxyd.fr (hermes.oxyd.fr [195.137.249.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB9B843D1F for ; Fri, 12 Dec 2003 11:02:39 -0800 (PST) (envelope-from pcasidy@casidy.com) Received: from [212.43.253.140] (helo=gueway.home) by hermes.oxyd.fr with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.20) id 1AUsXe-0001dT-TI for freebsd-stable@freebsd.org; Fri, 12 Dec 2003 20:01:35 +0100 Received: from casidy.com (littleoak.home [192.168.1.3]) by gueway.home (8.12.9/8.12.9) with ESMTP id hBCJ7dES076955 for ; Fri, 12 Dec 2003 20:07:44 +0100 (CET) (envelope-from pcasidy@casidy.com) Message-Id: <200312121907.hBCJ7dES076955@gueway.home> Date: Fri, 12 Dec 2003 20:02:13 +0100 (CET) From: pcasidy@casidy.com To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-auth-smtp-user: postmaster@casidy.com X-abuse-contact: abuse@oxyd.fr Subject: ucom0: init failed, IOERROR X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 19:02:41 -0000 [Feel free to point me to another mailing list if more appropriate] Hi! I am trying (as others tried to) to connect a Sony Clié (PEG-SJ33) using uvisor. I built a 4.9-Stable kernel adding the following modules: # USB com devices device ucom device uplcom device uvscom device uvisor device uftdi I have actived USB_DEBUG and get the following trace when trying the hotsync: ucom0: Sony Palm Handheld, rev 1.10/1.00, addr 2 ucom0: Sony Palm Handheld, rev 1.10/1.00, addr 2 uvisor_init: getting connection info ucom0: Number of ports: 2 ucom0: port 1, is for Generic ucom0: port 2, is for HotSync uvisor_init: getting available bytes ucom0: init failed, IOERROR uvisor_attach: ATTACH ERROR device_probe_and_attach: ucom0 attach returned 6 usbd_transfer_cb: short transfer 2<9 uhub_explore: usb_new_device failed, error=SHORT_XFER uhub0: device problem, disabling port 1 I do not know the protocol and I am trying to understand what happen but if someone could explain me what is wrong, that'd be more than welcomed ;) Thanks a lot. Phil. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 14:22:26 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F7BA16A4CE for ; Fri, 12 Dec 2003 14:22:26 -0800 (PST) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id E738143D3C for ; Fri, 12 Dec 2003 14:22:23 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 12 Dec 2003 20:54:11 +0000 (GMT) Date: Fri, 12 Dec 2003 20:54:09 +0000 From: David Malone To: Johan Bj?rk Message-ID: <20031212205409.GA5552@walton.maths.tcd.ie> References: <3FD9BC09.9020302@qbrick.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FD9BC09.9020302@qbrick.com> User-Agent: Mutt/1.5.3i Sender: dwmalone@maths.tcd.ie cc: freebsd-stable@freebsd.org Subject: Re: nfs_getpages: error 70 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 22:22:26 -0000 On Fri, Dec 12, 2003 at 02:00:57PM +0100, Johan Bj?rk wrote: > In fstab my only options for nfs is ro,noatime,noexec. I search the > nfs/nfsproto.h for 70 (did I found the right code?) > > nfsproto.h:#define NFSERR_STALE 70 Someone deleted the file the client was working on, and now the client can't read pages from that file. If this happens to an executable while it is running, then it is best to just kill the running process. David. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 15:29:11 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D66516A4CE for ; Fri, 12 Dec 2003 15:29:11 -0800 (PST) Received: from mandarin.fruitsalad.org (pc117.net160.koping.net [81.16.160.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E68643D1D for ; Fri, 12 Dec 2003 15:29:10 -0800 (PST) (envelope-from matt@fruitsalad.org) Received: from [192.168.15.54] (helo=192.168.15.54) by mandarin.fruitsalad.org with esmtp (Exim 4.14) id 1AUwia-000CqT-Q4 for stable@freebsd.org; Sat, 13 Dec 2003 00:29:08 +0100 From: Matt Douhan Organization: fruitsalad.org To: stable@freebsd.org Date: Sat, 13 Dec 2003 00:28:24 +0100 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_l8k2/kW/cycv/Ab"; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200312130028.37416.matt@fruitsalad.org> Subject: Werid message in /var/log/messages X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 23:29:11 -0000 --Boundary-02=_l8k2/kW/cycv/Ab Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline Hey I googled for this but found no reference to it, what does this message mea= n,=20 Dec 12 11:10:08 mandarin /kernel: got bad cookie vp 0xdbb08800 bp 0xcc87a6cc my machine is: 12:26am mdouhan @ [mandarin] ~ > uname -a =46reeBSD mandarin.internal.hasta.se 4.8-STABLE FreeBSD 4.8-STABLE #0: Sat = Apr =20 5 17:07:20 GMT 2003 root@mandarin.internal.hasta.se:/usr/obj/usr/src/sy= s/ MANDARIN i386 any hints would be very helpful and appreciated =2D-=20 Matt Douhan www.fruitsalad.org matt@fruitsalad.org ping elvis elvis is alive --Boundary-02=_l8k2/kW/cycv/Ab Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/2k8lJ58/+TqKmQsRApVbAJ9ty/oyocee/dVUgVO2KX4UUrdVKQCg3oUM ZE5Snvsaer2ZjEkvj1gMcSQ= =b/vQ -----END PGP SIGNATURE----- --Boundary-02=_l8k2/kW/cycv/Ab-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 19:52:52 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67C9016A4CE for ; Fri, 12 Dec 2003 19:52:52 -0800 (PST) Received: from cardinal.mail.pas.earthlink.net (cardinal.mail.pas.earthlink.net [207.217.121.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id A739543D1F for ; Fri, 12 Dec 2003 19:52:50 -0800 (PST) (envelope-from pixfbsd@earthlink.net) Received: from user153.net413.tx.sprint-hsd.net ([65.40.98.153] helo=[192.168.10.15]) by cardinal.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1AV0pe-0006pq-00; Fri, 12 Dec 2003 19:52:43 -0800 From: pixfbsd To: denon@denon.cx In-Reply-To: <6.0.1.1.2.20031211225738.05815900@mail.jon.com> References: <20031212000934.TAGY73768.web01-imail.rogers.com@win2000> <20031211203621.S45532@carver.gumbysoft.com> <6.0.1.1.2.20031211225738.05815900@mail.jon.com> Content-Type: text/plain Message-Id: <1071291244.13932.1.camel@viper.dlqj.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 12 Dec 2003 22:54:04 -0600 Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: RE: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2003 03:52:52 -0000 Pardon my missing this. So your environment is FreeBSD 4.8 machine with VMware producing your Win2000 environment? On Thu, 2003-12-11 at 23:02, denon wrote: > I agree with your analysis of the 4-year old driver, though it's funny to > say it's in a difficult to reproduce environment. In all actuality, a > software-based system would be one of the most controlled environments > available, removing all variables of heat, flakey hardware, etc, and > abstracting them from the hardware layer. VMware seems to be really robust, > when the OS plays nicely. (unfortunately win2k under vmware seems to be > extremely robust, even under high loads .. what luck.) > > This aside, I think you'll find that creating a FBSD 4.8 system in a > scsi-based vmware disk will reproduce it somewhat consistently. I've spoke > with several others having the same issue. > > You'll also take note that I'm not the guy that said this place was dead. :) > > Regards, > > -d > > > At 10:43 PM 12/11/2003, you wrote: > >On Thu, 11 Dec 2003, Mike Jakubik wrote: > > > > > It seems like this list is dead, and the developers don't care anymore. > > > Current is where it's at. > > > >This is patently wrong. Please don't do this. > > > >Since this is an isolated report in a hard-to-reproduce environment > >(vmware), its difficult to say if this is a bug in our software or a bug > >in vmware. Considering the bt driver hasn't been touched in over 4 years, > >I'm thinking that there may be issues in vmware. > > > >I'd follow up with the vmware folks. > > > > > > > > -----Original Message----- > > > From: owner-freebsd-stable@freebsd.org > > > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of denon > > > Sent: Thursday, December 11, 2003 12:28 PM > > > To: freebsd-stable@freebsd.org > > > Subject: Re: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in > > > VMWare > > > > > > So there are no other thoughts on this? I kinda figured people were > > > interested in squashing 4.8 bugs left and right .. :) > > > > > > -d > > > > > > At 03:25 PM 12/8/2003, you wrote: > > > >Responses inline: > > > > > > > >At 03:41 PM 12/7/2003, you wrote: > > > >>On Sun, 7 Dec 2003, denon wrote: > > > >> > > > >> > We've been doing more work with VMware and FreeBSD lately. Overall > > it's > > > >> > been going well, but we have a machine that's giving me grief, and I'm > > > a > > > >> > bit concerned. > > > >> > > > > >> > It's running 4.8-Release, with a single virtual SCSI drive. It's been > > > >> > running fine for months, but as of recently, it's started locking > > > >> up. When > > > >> > it locks up, this is what's in the messages: > > > >> > /kernel: (da0:bt0:0:0:0): CCB 0xca993340 - timed out > > > >> > /kernel: bt0: btdone - Attempt to free non-active BCCB 0xca9933c0 > > > >> > > > >>I wonder if the vmware environment is bug-for-bug compatible with the old > > > >>buslogic hardware :-) > > > > > > > >Sure seems it .. though it was stable for a long time, so I don't know .. > > > > > > > > > > > >>I suspect this is a bug in vmware, where the emulated driver is suffering > > > >>from long-term corruption. 43-day bug, perhaps? > > > >> > > > >>Does stopping and starting VMware clear this up? > > > > > > > >Nope, apparently not .. I tried and its happened again today. Seems to > > > >happen about twice a day, but no pattern to it that I see.. > > > > > > > > > > > >-d > > > >_______________________________________________ > > > >freebsd-stable@freebsd.org mailing list > > > >http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > > > _______________________________________________ > > > freebsd-stable@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > > > _______________________________________________ > > > freebsd-stable@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > > > >-- > >Doug White | FreeBSD: The Power to Serve > >dwhite@gumbysoft.com | www.FreeBSD.org > >_______________________________________________ > >freebsd-stable@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 00:19:10 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28B7216A4CF for ; Sat, 13 Dec 2003 00:19:10 -0800 (PST) Received: from geminix.org (gen129.n001.c02.escapebox.net [213.73.91.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09DB243D33 for ; Sat, 13 Dec 2003 00:19:09 -0800 (PST) (envelope-from gemini@geminix.org) Message-ID: <3FDACB79.8090405@geminix.org> Date: Sat, 13 Dec 2003 09:19:05 +0100 From: Uwe Doering Organization: Private UNIX Site User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org References: <200312130028.37416.matt@fruitsalad.org> In-Reply-To: <200312130028.37416.matt@fruitsalad.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Received: from gemini by geminix.org with asmtp (TLSv1:AES256-SHA:256) (Exim 3.36 #1) id 1AV4zT-000Myq-00; Sat, 13 Dec 2003 09:19:08 +0100 Subject: Re: Werid message in /var/log/messages X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2003 08:19:10 -0000 Matt Douhan wrote: > Hey > > I googled for this but found no reference to it, what does this message mean, > > Dec 12 11:10:08 mandarin /kernel: got bad cookie vp 0xdbb08800 bp 0xcc87a6cc > > my machine is: > > 12:26am mdouhan @ [mandarin] ~ > uname -a > FreeBSD mandarin.internal.hasta.se 4.8-STABLE FreeBSD 4.8-STABLE #0: Sat Apr > 5 17:07:20 GMT 2003 root@mandarin.internal.hasta.se:/usr/obj/usr/src/sys/ > MANDARIN i386 > > any hints would be very helpful and appreciated This is a notification that a directory changed on the NFS server with regard to what the kernel had in its cache. It then tries to remedy the situation by re-reading the directory, which it succeeded in if there are no further related messages in the log. Uwe -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers gemini@geminix.org | http://www.escapebox.net From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 00:55:04 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F93E16A4CE for ; Sat, 13 Dec 2003 00:55:04 -0800 (PST) Received: from web40705.mail.yahoo.com (web40705.mail.yahoo.com [66.218.78.162]) by mx1.FreeBSD.org (Postfix) with SMTP id A0CAC43D32 for ; Sat, 13 Dec 2003 00:55:03 -0800 (PST) (envelope-from seva_fwd@yahoo.com) Message-ID: <20031213085503.56723.qmail@web40705.mail.yahoo.com> Received: from [82.144.221.204] by web40705.mail.yahoo.com via HTTP; Sat, 13 Dec 2003 00:55:03 PST Date: Sat, 13 Dec 2003 00:55:03 -0800 (PST) From: Seva Fwd To: pcasidy@casidy.com In-Reply-To: <200312121318.hBCDIgES071703@gueway.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-stable@freebsd.org Subject: Re: Sony Clie on FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2003 08:55:04 -0000 I have not found a solution yet. I have some guesses. But cant fix by myself and dont know whom to contact with this. It looks like uvisor driver always uses port 1 for HotSync operation (and error message claims that error occured on port 1, that confirms said above). However some SonyClie (T675 and now seems SJ33) uses port 2 as the HotSync port. So, uvisor tries to HotSync on a wrong port. One my friend having Linux, said he had this issue too. But he found a swith in his driver that forced his driver to use exectly HotSync port for communications. I think we have the same issue with freeBSD now. And solution probably alike. BR, Seva --- pcasidy@casidy.com wrote: > Hi! > > I just found your post dated november 11th on > freebsd-stable. > Your problem was you had an error when trying to > sync: > > /kernel: ucom0: Sony Palm Handheld, rev 1.10/1.00, > addr 2 > /kernel: ucom0: Sony Palm Handheld, rev 1.10/1.00, > addr 2 > /kernel: ucom0: init failed, IOERROR > /kernel: device_probe_and_attach: ucom0 attach > returned 6 > /kernel: uhub0: port 1, set config at addr 2 failed > /kernel: uhub0: device problem, disabling port 1 > > I do have the same problem now with my Clie. Do you > manage to find out a > solution? > > Thanks > > Phil. > > ATTACHMENT part 2 application/pgp-signature __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 20:41:22 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F86B16A4CE for ; Sat, 13 Dec 2003 20:41:22 -0800 (PST) Received: from malkav.snowmoon.com (malkav.snowmoon.com [209.23.60.62]) by mx1.FreeBSD.org (Postfix) with SMTP id 83D4043D39 for ; Sat, 13 Dec 2003 20:41:18 -0800 (PST) (envelope-from jaime@snowmoon.com) Received: (qmail 39260 invoked from network); 14 Dec 2003 04:41:17 -0000 Received: from alb-24-195-202-60.nycap.rr.com (HELO snowmoon.com) (24.195.202.60) by 10.5.1.62 with SMTP; 14 Dec 2003 04:41:17 -0000 Date: Sat, 13 Dec 2003 23:40:56 -0500 Mime-Version: 1.0 (Apple Message framework v553) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Jaime To: freebsd-stable@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.553) Subject: Page faults every few days X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 04:41:22 -0000 I have a server that has been experiencing kernel panics every few weeks for months. Lately, it seems to happen anywhere from once every two weeks up to 3 times in the same week. It is always a page fault. I've replaced the drive with the swap partition on it, the RAM, the mother board, the IDE cable, the IDE controller (on that mother board), the CPU, and a few other parts in the last 12 months. I *think* that these page faults have been happening since before the most current cvsup/make-world process, but I can't be 100% certain that more than one happened. I've removed the vinum RAID-5 system that used to manage /home, but that didn't help the stability at all. (Though it made rebooting a lot quicker and less prone to failure.) I'm running out of ideas. What information I do have is listed below. Any help would be appreciated. I don't even know how to do any useful diagnostics in order to isolate the problem. Thanks in advance, Jaime zeus# uname -a FreeBSD zeus.cairodurham.org 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #9: Tue Aug 26 14:01:09 EDT 2003 jkikpole@zeus.cairodurham.org:/usr/obj/usr/src/sys/ZEUS i386 zeus# pwd /usr/local/crash zeus# whoami root zeus# ls -l total 1585106 -rw-r--r-- 1 root wheel 2 Dec 9 09:11 bounds -rw-r--r-- 1 root wheel 2324353 Nov 12 08:01 kernel.0 -rw-r--r-- 1 root wheel 2324353 Nov 12 15:05 kernel.1 -rw-r--r-- 1 root wheel 2324353 Nov 18 11:54 kernel.2 -rw-r--r-- 1 root wheel 2324353 Dec 2 10:22 kernel.3 -rw-r--r-- 1 root wheel 2324353 Dec 5 07:35 kernel.4 -rw-r--r-- 1 root wheel 2324353 Dec 9 09:11 kernel.5 -rw------- 1 root wheel 268369920 Nov 12 08:01 vmcore.0 -rw------- 1 root wheel 268369920 Nov 12 15:05 vmcore.1 -rw------- 1 root wheel 268369920 Nov 18 11:54 vmcore.2 -rw------- 1 root wheel 268369920 Dec 2 10:22 vmcore.3 -rw------- 1 root wheel 268369920 Dec 5 07:35 vmcore.4 -rw------- 1 root wheel 268369920 Dec 9 09:11 vmcore.5 zeus# gdb -k kernel.0 vmcore.0 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... IdlePTD at phsyical address 0x0036f000 initial pcb at physical address 0x002dc240 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x13 fault code = supervisor read, page not present instruction pointer = 0x8:0xc022cb68 stack pointer = 0x10:0xcca0fe48 frame pointer = 0x10:0xcca0fe50 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 = 91607 (perl5.00503) interrupt mask = none trap number = 12 panic: page fault syncing disks... 54 1 done Uptime: 2d20h1m1s dumping to dev #ad/0x20001, offset 1572992 dump ata0: resetting devices .. done 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 0xc016b1ba in dumpsys () (kgdb) quit zeus# gdb -k kernel.1 vmcore.1 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... IdlePTD at phsyical address 0x0036f000 initial pcb at physical address 0x002dc240 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x13 fault code = supervisor read, page not present instruction pointer = 0x8:0xc022cb68 stack pointer = 0x10:0xcca37e48 frame pointer = 0x10:0xcca37e50 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 = 16463 (perl5.00503) interrupt mask = none trap number = 12 panic: page fault syncing disks... 52 1 done Uptime: 7h1m56s dumping to dev #ad/0x20001, offset 1572992 dump ata0: resetting devices .. done 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 0xc016b1ba in dumpsys () (kgdb) quit zeus# gdb -k kernel.2 vmcore.2 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... IdlePTD at phsyical address 0x0036f000 initial pcb at physical address 0x002dc240 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x13 fault code = supervisor read, page not present instruction pointer = 0x8:0xc022cb68 stack pointer = 0x10:0xccef1e48 frame pointer = 0x10:0xccef1e50 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 = 67351 (perl5.00503) interrupt mask = none trap number = 12 panic: page fault syncing disks... 41 done Uptime: 5d20h45m52s dumping to dev #ad/0x20001, offset 1572992 dump ata0: resetting devices .. done 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 0xc016b1ba in dumpsys () (kgdb) quit zeus# gdb -k kernel.3 vmcore.3 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... IdlePTD at phsyical address 0x0036f000 initial pcb at physical address 0x002dc240 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xb00036 fault code = supervisor read, page not present instruction pointer = 0x8:0xc022cb68 stack pointer = 0x10:0xcc7dee48 frame pointer = 0x10:0xcc7dee50 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 = 93374 (perl5.00503) interrupt mask = none trap number = 12 panic: page fault syncing disks... 65 done Uptime: 13d22h25m47s dumping to dev #ad/0x20001, offset 1572992 dump ata0: resetting devices .. done 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 0xc016b1ba in dumpsys () (kgdb) quit zeus# gdb -k kernel.4 vmcore.4 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... IdlePTD at phsyical address 0x0036f000 initial pcb at physical address 0x002dc240 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xe4000113 fault code = supervisor read, page not present instruction pointer = 0x8:0xc022cb68 stack pointer = 0x10:0xcc9d4e48 frame pointer = 0x10:0xcc9d4e50 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 = 19861 (perl5.00503) interrupt mask = none trap number = 12 panic: page fault syncing disks... 35 4 1 done Uptime: 2d21h11m34s dumping to dev #ad/0x20001, offset 1572992 dump ata0: resetting devices .. done 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 0xc016b1ba in dumpsys () (kgdb) quit zeus# gdb -k kernel.5 vmcore.5 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... IdlePTD at phsyical address 0x0036f000 initial pcb at physical address 0x002dc240 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x13 fault code = supervisor read, page not present instruction pointer = 0x8:0xc022cb68 stack pointer = 0x10:0xccc10e48 frame pointer = 0x10:0xccc10e50 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 = 26642 (perl5.00503) interrupt mask = none trap number = 12 panic: page fault syncing disks... 55 done Uptime: 4d1h33m35s dumping to dev #ad/0x20001, offset 1572992 dump ata0: resetting devices .. done 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 0xc016b1ba in dumpsys () (kgdb) quit From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 23:18:36 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD93216A4CE for ; Sat, 13 Dec 2003 23:18:36 -0800 (PST) Received: from smtp2a.cbn.net.id (smtp2a.cbn.net.id [202.158.126.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 090A843D09 for ; Sat, 13 Dec 2003 23:18:34 -0800 (PST) (envelope-from riv@cbn.net.id) Received: from cbn.net.id (unknown [202.158.50.84]) by smtp2a.int.cbn.net.id (Postfix) with ESMTP id 2D71E15E9D for ; Sun, 14 Dec 2003 14:18:31 +0700 (WIT) Message-ID: <3FDC0EC1.7080702@cbn.net.id> Date: Sun, 14 Dec 2003 14:18:25 +0700 From: Riv Octovahriz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031203 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Vibra 128 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 07:18:36 -0000 Anyone ever successfully using SoundBlaster Vibra 128 on -STABLE ? I already tried device pcm, device sb and device sbc on my kernel config, and it still not working dmesg give me this line : pci0: (vendor=0x1102, dev=0x8938) at 13.0 irq 5 and pciconf -vl give me this output : none0@pci0:13:0: class=0x040100 card=0x59381102 chip=0x89381102 rev=0x00 hdr=0x00 vendor = 'Creative Labs' device = 'EV1938 Sound' class = multimedia subclass = audio Can anyone please help me ? Thx ~riv From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 23:57:16 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2849316A4CE for ; Sat, 13 Dec 2003 23:57:16 -0800 (PST) Received: from queue.paperwork.com (ns.place4us.com [206.8.93.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id B751A43D37 for ; Sat, 13 Dec 2003 23:57:08 -0800 (PST) (envelope-from denon@denon.cx) Received: from ONYX.denon.cx (unknown [206.8.93.100]) by queue.paperwork.com (CCS Enterprise SMTP) with ESMTP id BB2C772949; Sun, 14 Dec 2003 02:06:35 -0600 (CST) Message-Id: <6.0.1.1.2.20031214015502.01f63ec0@mail.jon.com> X-Sender: denon@denon.cx (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Sun, 14 Dec 2003 01:57:01 -0600 To: pixfbsd From: denon In-Reply-To: <1071291244.13932.1.camel@viper.dlqj.net> References: <20031212000934.TAGY73768.web01-imail.rogers.com@win2000> <20031211203621.S45532@carver.gumbysoft.com> <6.0.1.1.2.20031211225738.05815900@mail.jon.com> <1071291244.13932.1.camel@viper.dlqj.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-stable@freebsd.org Subject: RE: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 07:57:16 -0000 Nah, the host is Windows 2000 (host == OS actually running on the hardware). The guest OS is FreeBSD (running within the virtual machine). My comment, was that other guests/virtual machines running win2k were perfectly stable. I decided to give up on the buslogic drivers, and just switched the FreeBSD over to IDE. We'll see how that goes - hopefully it'll solve my problems. Much easier than playing mr bug tracker.. -d At 10:54 PM 12/12/2003, you wrote: >Pardon my missing this. So your environment is FreeBSD 4.8 machine with >VMware producing your Win2000 environment? > >On Thu, 2003-12-11 at 23:02, denon wrote: > > I agree with your analysis of the 4-year old driver, though it's funny to > > say it's in a difficult to reproduce environment. In all actuality, a > > software-based system would be one of the most controlled environments > > available, removing all variables of heat, flakey hardware, etc, and > > abstracting them from the hardware layer. VMware seems to be really > robust, > > when the OS plays nicely. (unfortunately win2k under vmware seems to be > > extremely robust, even under high loads .. what luck.) > > > > This aside, I think you'll find that creating a FBSD 4.8 system in a > > scsi-based vmware disk will reproduce it somewhat consistently. I've spoke > > with several others having the same issue. > > > > You'll also take note that I'm not the guy that said this place was > dead. :) > > > > Regards, > > > > -d > > > > > > At 10:43 PM 12/11/2003, you wrote: > > >On Thu, 11 Dec 2003, Mike Jakubik wrote: > > > > > > > It seems like this list is dead, and the developers don't care anymore. > > > > Current is where it's at. > > > > > >This is patently wrong. Please don't do this. > > > > > >Since this is an isolated report in a hard-to-reproduce environment > > >(vmware), its difficult to say if this is a bug in our software or a bug > > >in vmware. Considering the bt driver hasn't been touched in over 4 years, > > >I'm thinking that there may be issues in vmware. > > > > > >I'd follow up with the vmware folks. > > > > > > > > > > > -----Original Message----- > > > > From: owner-freebsd-stable@freebsd.org > > > > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of denon > > > > Sent: Thursday, December 11, 2003 12:28 PM > > > > To: freebsd-stable@freebsd.org > > > > Subject: Re: FreeBSD 4.8 and instabilities with Buslogic SCSI > drivers in > > > > VMWare > > > > > > > > So there are no other thoughts on this? I kinda figured people were > > > > interested in squashing 4.8 bugs left and right .. :) > > > > > > > > -d > > > > > > > > At 03:25 PM 12/8/2003, you wrote: > > > > >Responses inline: > > > > > > > > > >At 03:41 PM 12/7/2003, you wrote: > > > > >>On Sun, 7 Dec 2003, denon wrote: > > > > >> > > > > >> > We've been doing more work with VMware and FreeBSD lately. > Overall > > > it's > > > > >> > been going well, but we have a machine that's giving me grief, > and I'm > > > > a > > > > >> > bit concerned. > > > > >> > > > > > >> > It's running 4.8-Release, with a single virtual SCSI > drive. It's been > > > > >> > running fine for months, but as of recently, it's started locking > > > > >> up. When > > > > >> > it locks up, this is what's in the messages: > > > > >> > /kernel: (da0:bt0:0:0:0): CCB 0xca993340 - timed out > > > > >> > /kernel: bt0: btdone - Attempt to free non-active BCCB 0xca9933c0 > > > > >> > > > > >>I wonder if the vmware environment is bug-for-bug compatible with > the old > > > > >>buslogic hardware :-) > > > > > > > > > >Sure seems it .. though it was stable for a long time, so I don't > know .. > > > > > > > > > > > > > > >>I suspect this is a bug in vmware, where the emulated driver is > suffering > > > > >>from long-term corruption. 43-day bug, perhaps? > > > > >> > > > > >>Does stopping and starting VMware clear this up? > > > > > > > > > >Nope, apparently not .. I tried and its happened again today. Seems to > > > > >happen about twice a day, but no pattern to it that I see.. > > > > > > > > > > > > > > >-d > > > > >_______________________________________________ > > > > >freebsd-stable@freebsd.org mailing list > > > > >http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > >To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" > > > > > > > > _______________________________________________ > > > > freebsd-stable@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" > > > > > > > > _______________________________________________ > > > > freebsd-stable@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" > > > > > > > > > >-- > > >Doug White | FreeBSD: The Power to Serve > > >dwhite@gumbysoft.com | www.FreeBSD.org > > >_______________________________________________ > > >freebsd-stable@freebsd.org mailing list > > >http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"