From owner-freebsd-hackers Sun Nov 11 0:34:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 7CED437B422; Sun, 11 Nov 2001 00:33:58 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.3) id fAB8Xun88149; Sun, 11 Nov 2001 09:33:56 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200111110833.fAB8Xun88149@freebsd.dk> Subject: Re: HPT370 RAID or Vinum? In-Reply-To: <200111102227.fAAMRQV01034@mass.dis.org> To: Mike Smith Date: Sun, 11 Nov 2001 09:33:56 +0100 (CET) Cc: Greg Lehey , john_wilson100@excite.com, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Mike Smith wrote: > > Agreed. I don't think the RAIDs will have the same parameters. Most > > of these cheap controllers have fairly simplistic algorithms. Note > > that I said "guess", though. In my language, that means "don't know > > for sure". I'd really like to see some objective benchmarks. > > Er. > > These "cheap controllers" don't have any algorithms at all to speak of; > they're just ATA controllers with BIOS code that supposedly understands > striping/mirroring. There is no algorithm to speak of involved with striping, and just a little more in mirroring in the error case, but anyways.. > The "algorithms" are in the 'ar' driver, which should really just be a > vinum shim. Well, the way vinum is implemented that wont work unfortunately. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 1:39:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 50B9C37B41A for ; Sun, 11 Nov 2001 01:39:49 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fAB9dmU45444; Sun, 11 Nov 2001 01:39:48 -0800 (PST) (envelope-from dillon) Date: Sun, 11 Nov 2001 01:39:48 -0800 (PST) From: Matthew Dillon Message-Id: <200111110939.fAB9dmU45444@apollo.backplane.com> To: David Xu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Found some unnecessary code References: <20011111075324.72482.qmail@web20906.mail.yahoo.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Found some unnecessary code in FreeBSD 4.4-stable VM. : :File vm_page.c, in function vm_page_startup(), vm_page :bucket is :zeroed two times, this is unnecessary. : :--- vm_page.c Sun Nov 11 15:34:41 2001 :+++ vm_page.c.orig Sun Nov 11 15:34:21 2001 :@@ -265,6 +265,11 @@ : vaddr = round_page(vaddr); : bzero((caddr_t) mapped, vaddr - mapped); : :+ for (i = 0; i < vm_page_bucket_count; i++) { :+ *bucket = NULL; :+ bucket++; :+ } :+ Hmm. That code has been through a lot. The buckets were originally a doubly-linked list requiring initialization, but I turned them into a singly-linked list in early 1999. It's somewhat of a fluke that the bzero even covers the proper area, because 'mapped' just happens to be equal to 'vaddr' due to the fact that vaddr has already been rounded up. But it isn't explicit. We could probably cleanup the code but we'd have to make the mapped/vaddr matchup explicit to really be able to depend on the bzero() (or some programmer might come along later and break it). : * Compute the number of pages of memory that will :be available for : * use (taking into account the overhead of a page :structure per : : : :File vm_object.c, function vm_object_backing_scan() :calling :vm_page_deactivate() is unnecessary, this is already :done in :vm_page_rename(). : : :--- vm_object.c.orig Sun Nov 11 15:35:22 2001 :+++ vm_object.c Sun Nov 11 15:35:42 2001 :@@ -1159,9 +1159,6 @@ : * If the page was mapped to a process, it can :remain : * mapped through the rename. : */ :- if ((p->queue - p->pc) == PQ_CACHE) :- vm_page_deactivate(p); :- : vm_page_rename(p, object, new_pindex); : /* page automatically made dirty by rename */ : } : :-- :David Xu This looks reasonable. This is also left-over cruft from older versions of the code. A bunch of stuff was collapsed into vm_page_rename(). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 3: 6:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sydney.worldwide.lemis.com (dhcp243.rocks.bsdconeurope.org [195.40.100.243]) by hub.freebsd.org (Postfix) with ESMTP id 3282837B405; Sun, 11 Nov 2001 03:06:03 -0800 (PST) Received: (from grog@localhost) by sydney.worldwide.lemis.com (8.11.6/8.9.3) id fABB5iE32153; Sun, 11 Nov 2001 11:05:44 GMT (envelope-from grog) Date: Sun, 11 Nov 2001 11:05:43 +0000 From: Greg Lehey To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: Mike Smith , john_wilson100@excite.com, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: HPT370 RAID or Vinum? Message-ID: <20011111110543.F31680@sydney.worldwide.lemis.com> References: <200111102227.fAAMRQV01034@mass.dis.org> <200111110833.fAB8Xun88149@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200111110833.fAB8Xun88149@freebsd.dk>; from sos@freebsd.dk on Sun, Nov 11, 2001 at 09:33:56AM +0100 Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, 11 November 2001 at 9:33:56 +0100, Søren Schmidt wrote: > It seems Mike Smith wrote: >>> Agreed. I don't think the RAIDs will have the same parameters. Most >>> of these cheap controllers have fairly simplistic algorithms. Note >>> that I said "guess", though. In my language, that means "don't know >>> for sure". I'd really like to see some objective benchmarks. >> >> Er. >> >> These "cheap controllers" don't have any algorithms at all to speak of; >> they're just ATA controllers with BIOS code that supposedly understands >> striping/mirroring. > > There is no algorithm to speak of involved with striping, and just > a little more in mirroring in the error case, but anyways.. Well, there are questions of stripe size and whether you read entire stripes or just the part you want. >> The "algorithms" are in the 'ar' driver, which should really just be a >> vinum shim. > > Well, the way vinum is implemented that wont work unfortunately. Details? Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 3:23: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 21C9437B41C; Sun, 11 Nov 2001 03:22:54 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.3) id fABBMqv25712; Sun, 11 Nov 2001 12:22:52 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200111111122.fABBMqv25712@freebsd.dk> Subject: Re: HPT370 RAID or Vinum? In-Reply-To: <20011111110543.F31680@sydney.worldwide.lemis.com> To: Greg Lehey Date: Sun, 11 Nov 2001 12:22:52 +0100 (CET) Cc: Mike Smith , john_wilson100@excite.com, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Greg Lehey wrote: > >> These "cheap controllers" don't have any algorithms at all to speak of; > >> they're just ATA controllers with BIOS code that supposedly understands > >> striping/mirroring. > > > > There is no algorithm to speak of involved with striping, and just > > a little more in mirroring in the error case, but anyways.. > > Well, there are questions of stripe size and whether you read entire > stripes or just the part you want. Sure, stripe size is not changeable to other sizes than the BIOS supports on the ATA RAID's or you wont be able to boot, and insofar as we normally dont do readahead, we only read the part we want.. > > >> The "algorithms" are in the 'ar' driver, which should really just be a > >> vinum shim. > > > > Well, the way vinum is implemented that wont work unfortunately. > > Details? Vinun monopolises the disk by putting varius data in areas of the disk, that wont play ball with native RAID's if the disks needs to be bootable and shareable with other OS's. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 8: 9:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from D00015.dialonly.kemerovo.su (www2.svzserv.kemerovo.su [213.184.65.86]) by hub.freebsd.org (Postfix) with ESMTP id 438E837B41B; Sun, 11 Nov 2001 08:09:15 -0800 (PST) Received: (from eugen@localhost) by D00015.dialonly.kemerovo.su (8.11.6/8.11.4) id fABG8Hw02428; Sun, 11 Nov 2001 23:08:17 +0700 (KRAT) (envelope-from eugen) Date: Sun, 11 Nov 2001 23:08:17 +0700 From: Eugene Grosbein To: stable@freebsd.org Cc: hackers@freebsd.org Subject: kern.vm.kmem.size Message-ID: <20011111230817.A2325@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I'm trying to test and tune speed of freebsd's filesystem in many aspects. I run recent FreeBSD 4.4-STABLE with new dirprefs code, read tuning(7), newfs'd my FS, turned softupdates on, have UFS_DIRHASH kernel option. Also, I've read DIRHASH kernel code source. It seems that efficiency of DIRHASH greatly depends of kernel memory size (and some experiments approve this). loader(8) describes tunnable parameter kern.vm.kmem.size which overrides default size of kernel memory. Increasing this helps DIRHASH not to fall back to linear search. But how can I see exact amount of used kernel memory? Default 12M does not seem to be suitable for my tasks and I would like to increase this but cannot estimate right value. Perhaps, sysctl vm.zone might help but I do not know how to interpret its output. All that I need is a % of used kernel memory. Eugene Grosbein P.S. Please CC: me when replying. Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 11:16: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail7.wlv.netzero.net (mail7.wlv.netzero.net [209.247.163.57]) by hub.freebsd.org (Postfix) with SMTP id A342C37B405 for ; Sun, 11 Nov 2001 11:16:00 -0800 (PST) Received: (qmail 8093 invoked from network); 11 Nov 2001 19:15:59 -0000 Received: from dialup-166.90.236.51.dial1.detroit1.level3.net (HELO computer) (166.90.236.51) by mail7.wlv.netzero.net with SMTP; 11 Nov 2001 19:15:59 -0000 Message-ID: <000801c16afe$7787a3e0$33ec5aa6@computer> From: "sureshkg1" To: Subject: Request for membership Date: Sun, 11 Nov 2001 14:16:08 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C16ABB.683F6BE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C16ABB.683F6BE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Please add my id in freebsd mailing list. Thank you. Regards, SURESH. ------=_NextPart_000_0005_01C16ABB.683F6BE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Please add my id in freebsd mailing=20 list.
 
Thank you.
 
Regards,
SURESH.
------=_NextPart_000_0005_01C16ABB.683F6BE0-- ---------------------------------------------------- Sign Up for NetZero Platinum Today Only $9.95 per month! http://my.netzero.net/s/signup?r=platinum&refcd=PT97 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 11:20:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id E70FC37B428; Sun, 11 Nov 2001 11:20:09 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA89909; Sun, 11 Nov 2001 11:11:50 -0800 (PST) Date: Sun, 11 Nov 2001 11:11:48 -0800 (PST) From: Julian Elischer To: hackers@freebsd.org Cc: phk@freebsd.org Subject: HP deskjet 940 (color) and FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone have success in getting one of these (or similar) printing color from USB? using Ghostscript 6.52 it does ok with graphics and text in B/W I can get gimp to produce colour and in apsfilter I can select the gimp output drivers and get rather 'crude' colour, but if I select the hp drivers in ghostscript (even the pcl3 of hpdj) I just get Black and white testpages from apsfilter. (I get a cruddy colour one if I select gimp drivers) Rumour has it that the pcl3 or hpdj drivers in ghostscript are supposed to be very good (writtenby HP?) but what's the secret to making them do colour? Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 12:23:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id EDCCB37B419; Sun, 11 Nov 2001 12:23:33 -0800 (PST) Received: from colt.ncptiddische.net (ppp-165.wobline.de [212.68.69.173]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fABKNSr06196; Sun, 11 Nov 2001 21:23:29 +0100 Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fABKNkV10415; Sun, 11 Nov 2001 21:23:46 +0100 (CET) (envelope-from nils@tisys.org) Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by jodie.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fABKO5K04937; Sun, 11 Nov 2001 21:24:05 +0100 (CET) (envelope-from nils@tisys.org) Date: Sun, 11 Nov 2001 21:24:05 +0100 (CET) From: Nils Holland To: Julian Elischer Cc: hackers@FreeBSD.ORG, Subject: Re: HP deskjet 940 (color) and FreeBSD In-Reply-To: Message-ID: <20011111212120.C4935-100000@jodie.ncptiddische.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 11 Nov 2001, Julian Elischer wrote: > Does anyone have success in getting one of these > (or similar) printing color from USB? > > using Ghostscript 6.52 it does ok with graphics > and text in B/W > > I can get gimp to produce colour > and in apsfilter I can select the gimp output drivers and get > rather 'crude' colour, but if I select the hp drivers in ghostscript > (even the pcl3 of hpdj) I just get Black and white testpages > from apsfilter. (I get a cruddy colour one if I select gimp drivers) I guess this should have been asked on -questions, but anyway: I guess that you will probably get your printer to produce some good color output using ghostscript's "djc970" driver. It works really great with the DeskJet 970 (in case anyone wondered where its name comes from), as well with the DekJet 930C, as I have learned recently after buying that printer. I guess that the djc970 would probably work well with any DeskJet from the 900 line, so you should probably try it out! Greetings Nils Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 12:29:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from robin.mail.pas.earthlink.net (robin.mail.pas.earthlink.net [207.217.120.65]) by hub.freebsd.org (Postfix) with ESMTP id 30E0937B405; Sun, 11 Nov 2001 12:29:14 -0800 (PST) Received: from fire (1Cust63.tnt1.pasadena.ca.da.uu.net [63.28.226.63]) by robin.mail.pas.earthlink.net (8.11.5/8.9.3) with SMTP id fABKTBX27078; Sun, 11 Nov 2001 12:29:12 -0800 (PST) Message-ID: <003301c16aee$ea58bf90$6503c23f@XGforce.com> Reply-To: "matt" From: "matt" To: Cc: Subject: wake up on lan driver support Date: Sun, 11 Nov 2001 12:24:48 -0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, guys, is there any wake up on lan driver support available in the NIC driver tree? or if any one have any pointers on this? Is also any support in the src tree support poweroff when shutting down FreeBSD? Many thanks ====================================== WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. ====================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 12:56:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 8EB9437B417 for ; Sun, 11 Nov 2001 12:56:14 -0800 (PST) Received: (qmail 55353 invoked by uid 1000); 11 Nov 2001 20:56:12 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 11 Nov 2001 20:56:12 -0000 Date: Sun, 11 Nov 2001 14:56:12 -0600 (CST) From: Mike Silbersack To: John Kozubik Cc: Subject: Re: CPU Temp and Fan speed as entropy? In-Reply-To: Message-ID: <20011111145324.W55153-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 10 Nov 2001, John Kozubik wrote: > > CPU temp and fan speed may or may not be truly random - regardless, I > would be wary of using them as random seeds. First, I suspect that the > range of values is quite small - how much does your temp and fan speed > actually fluctuate over time ? > > Second, I don't have a bios like this in front of me to examine, but I > doubt the granularity is greater than one decimal place. Comments ? > > Due to the small range that these numbers will fall in, I would think the > effectiveness of these values as a random seed are directly related to the > number of places to the right of the decimal these values are measured in. > > ----- > John Kozubik - john@kozubik.com - http://www.kozubik.com I tried running one of the monitoring programs after I sent that message, and found what you guessed above; the accuracy is not early good enough for entropy use. The granularity seems to be about 4 degrees, and the temperature seems to just bounce between two values once every few seconds or so. Oh well. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 13: 3:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id AE1B437B419; Sun, 11 Nov 2001 13:03:27 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fABL54801504; Sun, 11 Nov 2001 13:05:04 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200111112105.fABL54801504@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: sos@freebsd.dk Cc: Mike Smith , Greg Lehey , john_wilson100@excite.com, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: HPT370 RAID or Vinum? In-reply-to: Your message of "Sun, 11 Nov 2001 09:33:56 +0100." <200111110833.fAB8Xun88149@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Sun, 11 Nov 2001 13:05:04 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > These "cheap controllers" don't have any algorithms at all to speak o= f; = > > they're just ATA controllers with BIOS code that supposedly understan= ds = > > striping/mirroring. > = > There is no algorithm to speak of involved with striping, and just = > a little more in mirroring in the error case, but anyways.. Unless you've fixed it, the error case handling in mirror mode is busted = as well. > > The "algorithms" are in the 'ar' driver, which should really just be = a = > > vinum shim. > = > Well, the way vinum is implemented that wont work unfortunately. There's no reason that 'ar' and Vinum couldn't be fixed to play together.= Or at least, no technical reason. -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 13:38:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpzilla3.xs4all.nl (smtpzilla3.xs4all.nl [194.109.127.139]) by hub.freebsd.org (Postfix) with ESMTP id D118337B418; Sun, 11 Nov 2001 13:38:05 -0800 (PST) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtpzilla3.xs4all.nl (8.12.0/8.12.0) with ESMTP id fABLbxcb006422; Sun, 11 Nov 2001 22:38:00 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.11.6/8.9.3) with ESMTP id fABLbwj09918; Sun, 11 Nov 2001 22:37:58 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <200111112137.fABLbwj09918@trantor.xs4all.nl> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Mike Smith Cc: sos@freebsd.dk, Greg Lehey , john_wilson100@excite.com, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG, paulz@trantor.xs4all.nl Subject: Re: HPT370 RAID or Vinum? In-Reply-To: Message from Mike Smith of "Sun, 11 Nov 2001 13:05:04 PST." <200111112105.fABL54801504@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Nov 2001 22:37:58 +0100 From: Paul van der Zwan Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200111112105.fABL54801504@mass.dis.org>, Mike Smith wrote: >> > These "cheap controllers" don't have any algorithms at all to speak of; >> > they're just ATA controllers with BIOS code that supposedly understands >> > striping/mirroring. >> >> There is no algorithm to speak of involved with striping, and just >> a little more in mirroring in the error case, but anyways.. > >Unless you've fixed it, the error case handling in mirror mode is busted >as well. > >> > The "algorithms" are in the 'ar' driver, which should really just be a >> > vinum shim. >> >> Well, the way vinum is implemented that wont work unfortunately. > >There's no reason that 'ar' and Vinum couldn't be fixed to play together. > >Or at least, no technical reason. Well, currently there are some minor glitches. I just installed a vinum slice on /dev/ar0s1 and unless I do a 'vinum read /dev/ar0s1' vinum will not find the volumes. This causes the boot of my box ( -current btw) to fail at the mount of my filesystems. Is there a way to tell vinum to also look on /dev/ar* for its config ?? Paul -- Klein bottle for rent -- inquire within. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 13:39:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 6E33737B417; Sun, 11 Nov 2001 13:39:39 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.3) id fABLdcM76782; Sun, 11 Nov 2001 22:39:38 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200111112139.fABLdcM76782@freebsd.dk> Subject: Re: HPT370 RAID or Vinum? In-Reply-To: <200111112105.fABL54801504@mass.dis.org> To: Mike Smith Date: Sun, 11 Nov 2001 22:39:38 +0100 (CET) Cc: Greg Lehey , john_wilson100@excite.com, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Mike Smith wrote: > > > These "cheap controllers" don't have any algorithms at all to speak of; > > > they're just ATA controllers with BIOS code that supposedly understands > > > striping/mirroring. > > > > There is no algorithm to speak of involved with striping, and just > > a little more in mirroring in the error case, but anyways.. > > Unless you've fixed it, the error case handling in mirror mode is busted > as well. I know, too little time... > > > The "algorithms" are in the 'ar' driver, which should really just be a > > > vinum shim. > > > > Well, the way vinum is implemented that wont work unfortunately. > > There's no reason that 'ar' and Vinum couldn't be fixed to play together. > > Or at least, no technical reason. Might be, but it involves some pretty radical changes to the way vinum stores its config info on the disks, and I have not had the time nor energy to fight those through. Another thing is how to setup/config those RAID's, the info put on the disks *must* be exactly what the BIOS's wants, or they wont pick up an array. So its not as simple as to just "fix" vinum and ar, its goes far beyond that... But I'll say this much, if you find sponsors for the time, I'll happily make this work they way it should :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 13:42:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id AC4CE37B419; Sun, 11 Nov 2001 13:42:24 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.3) id fABLgHW77454; Sun, 11 Nov 2001 22:42:17 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200111112142.fABLgHW77454@freebsd.dk> Subject: Re: HPT370 RAID or Vinum? In-Reply-To: <200111112137.fABLbwj09918@trantor.xs4all.nl> To: Paul van der Zwan Date: Sun, 11 Nov 2001 22:42:17 +0100 (CET) Cc: Mike Smith , Greg Lehey , john_wilson100@excite.com, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Paul van der Zwan wrote: > Well, currently there are some minor glitches. I just installed a vinum slice > on /dev/ar0s1 and unless I do a 'vinum read /dev/ar0s1' vinum will not > find the volumes. This causes the boot of my box ( -current btw) to fail > at the mount of my filesystems. You dont need to mix ar and vinum devices, why do you want to run a SW RAID ontop of a SW RAID ? > Is there a way to tell vinum to also look on /dev/ar* for its config ?? Nope, not yet, and it will only solve part of your problem... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 13:48: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpzilla1.xs4all.nl (smtpzilla1.xs4all.nl [194.109.127.137]) by hub.freebsd.org (Postfix) with ESMTP id A0DDC37B419; Sun, 11 Nov 2001 13:47:53 -0800 (PST) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtpzilla1.xs4all.nl (8.12.0/8.12.0) with ESMTP id fABLlh4e089397; Sun, 11 Nov 2001 22:47:43 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.11.6/8.9.3) with ESMTP id fABLlgj10123; Sun, 11 Nov 2001 22:47:42 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <200111112147.fABLlgj10123@trantor.xs4all.nl> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: sos@freebsd.dk Cc: Paul van der Zwan , Mike Smith , Greg Lehey , john_wilson100@excite.com, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG, paulz@trantor.xs4all.nl Subject: Re: HPT370 RAID or Vinum? In-Reply-To: Message from S ren Schmidt of "Sun, 11 Nov 2001 22:42:17 +0100." <200111112142.fABLgHW77454@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sun, 11 Nov 2001 22:47:42 +0100 From: Paul van der Zwan Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200111112142.fABLgHW77454@freebsd.dk>, S ren Schmidt wrote: >It seems Paul van der Zwan wrote: >> Well, currently there are some minor glitches. I just installed a vinu= m slic >e >> on /dev/ar0s1 and unless I do a 'vinum read /dev/ar0s1' vinum will not= >> find the volumes. This causes the boot of my box ( -current btw) to fa= il >> at the mount of my filesystems. = > >You dont need to mix ar and vinum devices, why do you want to run a >SW RAID ontop of a SW RAID ? I bought the mobo with a promise controller to get some extra IDE channel= s but unfortunately I cannot get it to just pass on the channels. I need to= make a raid volume to make the box continue booting past the BIOS. But I don't want a big 80 gig slice, I want to use vinum to create a numb= er of smaller volumes , possibly more than disklabel will allow and at least ea= sier and possibly safer than relabeling a disk with data on it. So I just want= = volumes consisting of a single plex nothing fancy, no raid 0, 1 or 5. > >> Is there a way to tell vinum to also look on /dev/ar* for its config ?= ? > >Nope, not yet, and it will only solve part of your problem... What problem have I not noticed yet ?? The not reading the config is the = only = one I have found sofar. Paul -- = Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 14: 0:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id AAB9437B41C; Sun, 11 Nov 2001 14:00:29 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA90448; Sun, 11 Nov 2001 13:44:06 -0800 (PST) Date: Sun, 11 Nov 2001 13:44:05 -0800 (PST) From: Julian Elischer To: Nils Holland Cc: hackers@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: HP deskjet 940 (color) and FreeBSD In-Reply-To: <20011111212120.C4935-100000@jodie.ncptiddische.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well it prints in b/w really well, Just not in colour.... however I just found the apsfilter entry for cjd880 and that seems to work a treat. I don't understand.. there seem to be a plethora of device drivers for hp and yet there is little info on which is best... oh well, I'm happy now at least.. thanks for your information... I'll try the djc970 driver again some time.. On Sun, 11 Nov 2001, Nils Holland wrote: > On Sun, 11 Nov 2001, Julian Elischer wrote: > > > Does anyone have success in getting one of these > > (or similar) printing color from USB? > > > > using Ghostscript 6.52 it does ok with graphics > > and text in B/W > > > > I can get gimp to produce colour > > and in apsfilter I can select the gimp output drivers and get > > rather 'crude' colour, but if I select the hp drivers in ghostscript > > (even the pcl3 of hpdj) I just get Black and white testpages > > from apsfilter. (I get a cruddy colour one if I select gimp drivers) > > I guess this should have been asked on -questions, but anyway: I guess > that you will probably get your printer to produce some good color output > using ghostscript's "djc970" driver. It works really great with the > DeskJet 970 (in case anyone wondered where its name comes from), as well > with the DekJet 930C, as I have learned recently after buying that > printer. I guess that the djc970 would probably work well with any DeskJet > from the 900 line, so you should probably try it out! > > Greetings > Nils > > Nils Holland > Ti Systems - FreeBSD in Tiddische, Germany > http://www.tisys.org * nils@tisys.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 14: 0:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 31EB937B416; Sun, 11 Nov 2001 14:00:25 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA90457; Sun, 11 Nov 2001 13:45:17 -0800 (PST) Date: Sun, 11 Nov 2001 13:45:16 -0800 (PST) From: Julian Elischer To: matt Cc: current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: wake up on lan driver support In-Reply-To: <003301c16aee$ea58bf90$6503c23f@XGforce.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 11 Nov 2001, matt wrote: > Hi, guys, is there any wake up on lan driver support > available in the NIC driver tree? or if any one have any > pointers on this? > > Is also any support in the src tree support poweroff > when shutting down FreeBSD? A least in -current, halt -p powers off the machine It may rely on the acpi support or soemthing... > > Many thanks > > > > ====================================== > WWW.XGFORCE.COM > The Next Generation Load Balance and > Fail Safe Server Clustering Software > for the Internet. > ====================================== > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 14:11:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 63F2537B41F for ; Sun, 11 Nov 2001 14:11:21 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fABMAML01692; Sun, 11 Nov 2001 23:10:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: hackers@freebsd.org Subject: Re: HP deskjet 940 (color) and FreeBSD In-Reply-To: Your message of "Sun, 11 Nov 2001 11:11:48 PST." Date: Sun, 11 Nov 2001 23:10:22 +0100 Message-ID: <1690.1005516622@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Julian Elischer writes: >Rumour has it that the pcl3 or hpdj drivers in ghostscript are supposed >to be very good (writtenby HP?) but >what's the secret to making them do colour? You want the HP developed hpijs driver. This is what I use for my HP 1220 printer, you may need to change the DeviceName: /usr/local/bin/gs -dSAFER -dNOPAUSE -q \ -sDEVICE=DJ9xx \ -dPrintMode=1 -r300 \ -sOutputFile=- - | dd obs=64k 2>/dev/null && exit 0 The dd(1) trick is because it outputs ridiculous small write(2) requests and the USB path does no buffering. I think there is little reason for ultp(4) to not buffer aggressively. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 14:30:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id DC5EA37B41B for ; Sun, 11 Nov 2001 14:30:35 -0800 (PST) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.6/8.11.6) with ESMTP id fABMUVE39695; Sun, 11 Nov 2001 17:30:31 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200111112230.fABMUVE39695@whizzo.transsys.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Poul-Henning Kamp Cc: Julian Elischer , hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: HP deskjet 940 (color) and FreeBSD References: <1690.1005516622@critter.freebsd.dk> In-reply-to: Your message of "Sun, 11 Nov 2001 23:10:22 +0100." <1690.1005516622@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Nov 2001 17:30:31 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > In message , Julian Elischer writes: > > >Rumour has it that the pcl3 or hpdj drivers in ghostscript are supposed > >to be very good (writtenby HP?) but > >what's the secret to making them do colour? > > You want the HP developed hpijs driver. This is what I use for my > HP 1220 printer, you may need to change the DeviceName: > > /usr/local/bin/gs -dSAFER -dNOPAUSE -q \ > -sDEVICE=DJ9xx \ > -dPrintMode=1 -r300 \ > -sOutputFile=- - | dd obs=64k 2>/dev/null && exit 0 Will the hpijs driver work with the PCL printers? When I looked at the docs, I was left with the impression that the driver supported the "Windows" printers. The docs didn't mention the hp870 printer that I had. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 14:56: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.dyndns.org (adsl-208-191-149-232.dsl.hstntx.swbell.net [208.191.149.232]) by hub.freebsd.org (Postfix) with ESMTP id 7F76437B422 for ; Sun, 11 Nov 2001 14:56:00 -0800 (PST) Received: (from chris@localhost) by holly.dyndns.org (8.11.6/8.9.3) id fABMsjM55257; Sun, 11 Nov 2001 16:54:45 -0600 (CST) (envelope-from chris) Date: Sun, 11 Nov 2001 16:54:44 -0600 From: Chris Costello To: "Louis A. Mamakos" Cc: hackers@FreeBSD.org Subject: Re: HP deskjet 940 (color) and FreeBSD Message-ID: <20011111165444.B51056@holly.calldei.com> Reply-To: chris@FreeBSD.org References: <1690.1005516622@critter.freebsd.dk> <200111112230.fABMUVE39695@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111112230.fABMUVE39695@whizzo.transsys.com>; from louie@TransSys.COM on Sun, Nov 11, 2001 at 05:30:31PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, November 11, 2001, Louis A. Mamakos wrote: > Will the hpijs driver work with the PCL printers? When I looked at > the docs, I was left with the impression that the driver supported > the "Windows" printers. The docs didn't mention the hp870 printer > that I had. Absolutely! Works with my 882C pretty well. -- +-------------------+-------------------------------------+ | Chris Costello | Every program in development at MIT | | chris@FreeBSD.org | expands until it can read mail. | +-------------------+-------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 15:34: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id E64E637B405 for ; Sun, 11 Nov 2001 15:33:58 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fABNWxL02887; Mon, 12 Nov 2001 00:33:00 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Louis A. Mamakos" Cc: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: HP deskjet 940 (color) and FreeBSD In-Reply-To: Your message of "Sun, 11 Nov 2001 17:30:31 EST." <200111112230.fABMUVE39695@whizzo.transsys.com> Date: Mon, 12 Nov 2001 00:32:59 +0100 Message-ID: <2885.1005521579@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200111112230.fABMUVE39695@whizzo.transsys.com>, "Louis A. Mamakos" writes: >> In message , Julian Elischer writes: >> >> >Rumour has it that the pcl3 or hpdj drivers in ghostscript are supposed >> >to be very good (writtenby HP?) but >> >what's the secret to making them do colour? >> >> You want the HP developed hpijs driver. This is what I use for my >> HP 1220 printer, you may need to change the DeviceName: >> >> /usr/local/bin/gs -dSAFER -dNOPAUSE -q \ >> -sDEVICE=DJ9xx \ >> -dPrintMode=1 -r300 \ >> -sOutputFile=- - | dd obs=64k 2>/dev/null && exit 0 > >Will the hpijs driver work with the PCL printers? When I looked at >the docs, I was left with the impression that the driver supported >the "Windows" printers. The docs didn't mention the hp870 printer >that I had. There is a webpage here: http://hpinkjet.sourceforge.net/ Basically, for the supported printers, you get the full quality of the printer with ghostscript. No other ghostscript drivers contain the HP magic color dithering code... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 16: 7:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 20B9337B425; Sun, 11 Nov 2001 16:07:15 -0800 (PST) Received: from cain.gsoft.com.au (root@localhost [127.0.0.1]) by cain.gsoft.com.au (8.11.6/8.11.6) with ESMTP id fAC06pS44832; Mon, 12 Nov 2001 10:36:52 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <003301c16aee$ea58bf90$6503c23f@XGforce.com> Date: Mon, 12 Nov 2001 10:36:51 +1030 (CST) From: "Daniel O'Connor" To: matt Subject: RE: wake up on lan driver support Cc: freebsd-hackers@freebsd.org, current@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 11-Nov-2001 matt wrote: > Hi, guys, is there any wake up on lan driver support > available in the NIC driver tree? or if any one have any > pointers on this? I didn't think this was a driver issue? ie the main part is the crafting of the magic packet to wake the card up. (But I've never used WOL so take with a grain of salt :) > Is also any support in the src tree support poweroff > when shutting down FreeBSD? Plenty :) If you enable APM you can add the -p flat to shutdown and/or halt to power the machine off. (If APM is off then -p behaves like -h) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 16:43:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id CB91837B417; Sun, 11 Nov 2001 16:43:34 -0800 (PST) Received: from 1cust179.tnt1.pasadena.ca.da.uu.net ([63.28.226.179] helo=fire) by pintail.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1635C7-00037G-00; Sun, 11 Nov 2001 16:43:24 -0800 Message-ID: <000d01c16b12$6cc333c0$6503c23f@XGforce.com> Reply-To: "matt" From: "matt" To: "Daniel O'Connor" Cc: , References: Subject: Re: wake up on lan driver support Date: Sun, 11 Nov 2001 16:38:50 -0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG any clue to find the tech doc regarding the format of the packet. I'd code such thing. It's a very good feature for FreeBSD. ====================================== WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. ====================================== ----- Original Message ----- From: "Daniel O'Connor" To: "matt" Cc: ; Sent: Sunday, November 11, 2001 4:06 PM Subject: RE: wake up on lan driver support > > On 11-Nov-2001 matt wrote: > > Hi, guys, is there any wake up on lan driver support > > available in the NIC driver tree? or if any one have any > > pointers on this? > > I didn't think this was a driver issue? > ie the main part is the crafting of the magic packet to wake the card up. > > (But I've never used WOL so take with a grain of salt :) > > > Is also any support in the src tree support poweroff > > when shutting down FreeBSD? > > Plenty :) > If you enable APM you can add the -p flat to shutdown and/or halt to power the > machine off. > > (If APM is off then -p behaves like -h) > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 16:59:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 7D35537B405; Sun, 11 Nov 2001 16:59:34 -0800 (PST) Received: from cain.gsoft.com.au (root@localhost [127.0.0.1]) by cain.gsoft.com.au (8.11.6/8.11.6) with ESMTP id fAC0xFS45556; Mon, 12 Nov 2001 11:29:15 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <000d01c16b12$6cc333c0$6503c23f@XGforce.com> Date: Mon, 12 Nov 2001 11:29:13 +1030 (CST) From: "Daniel O'Connor" To: matt Subject: Re: wake up on lan driver support Cc: current@freebsd.org, freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 12-Nov-2001 matt wrote: > any clue to find the tech doc regarding the format of > the packet. I'd code such thing. It's a very good > feature for FreeBSD. I just did a quick web search.. http://gsd.di.uminho.pt/jpo/software/wakeonlan/mini-howto/wol-mini-howto-3.html --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 17: 2: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail25.sdc1.sfba.home.com (femail25.sdc1.sfba.home.com [24.254.60.15]) by hub.freebsd.org (Postfix) with ESMTP id C89F937B416; Sun, 11 Nov 2001 17:01:59 -0800 (PST) Received: from lightnin ([65.11.111.111]) by femail25.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011112010159.CLUP7421.femail25.sdc1.sfba.home.com@lightnin>; Sun, 11 Nov 2001 17:01:59 -0800 Date: Sun, 11 Nov 2001 17:01:59 -0800 Subject: Re: wake up on lan driver support Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v472) From: justin@mac.com To: freebsd-hackers@freebsd.org, current@freebsd.org Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.472) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, November 11, 2001, at 04:06 , Daniel O'Connor wrote: > > On 11-Nov-2001 matt wrote: >> Hi, guys, is there any wake up on lan driver support >> available in the NIC driver tree? or if any one have any >> pointers on this? > > I didn't think this was a driver issue? > ie the main part is the crafting of the magic packet to wake the card > up. The technology is explained on a number of websites; here's one I found just now: http://www.networking.ibm.com/eji/ejiwake.html I think it requires device driver support because it has to be enabled (at least, that's what the devices I know about require). Regards, Justin --- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Men are from Earth. | Women are from Earth. | Deal with it. *--------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 11 17:29:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id B43EE37B416; Sun, 11 Nov 2001 17:29:31 -0800 (PST) Received: from v-ger.we.lc.ehu.es (lxpx199.lx.ehu.es [158.227.26.99]) by polaris.we.lc.ehu.es (8.11.6/8.11.6) with ESMTP id fAC1TRj05878; Mon, 12 Nov 2001 02:29:28 +0100 (MET) Received: (from jose@localhost) by v-ger.we.lc.ehu.es (8.11.6/8.11.6) id fAC1Tbx01742; Mon, 12 Nov 2001 02:29:37 +0100 (CET) (envelope-from jose) Date: Mon, 12 Nov 2001 02:29:37 +0100 From: "Jose M. Alcaide" To: Julian Elischer Cc: hackers@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: HP deskjet 940 (color) and FreeBSD Message-ID: <20011112022937.C827@v-ger.we.lc.ehu.es> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Sun, Nov 11, 2001 at 11:11:48AM -0800 X-Operating-System: FreeBSD 4.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Nov 11, 2001 at 11:11:48AM -0800, Julian Elischer wrote: > I can get gimp to produce colour > and in apsfilter I can select the gimp output drivers and get > rather 'crude' colour, but if I select the hp drivers in ghostscript > (even the pcl3 of hpdj) I just get Black and white testpages > from apsfilter. (I get a cruddy colour one if I select gimp drivers) Apsfilter does not use the options of hpdj and pcl3 drivers correctly. I have a patch for this problem (sent attached). The patch also fix a bug with the handling of duplex/tumble options. I reported these problems to the apsfilter developers, and they acknowledged them. OTOH, hpijs is the best driver for HP inkjet printers. Unfortunately, apsfilter does not support this driver yet. Regards, JMA -- ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="apsfilter.patch" --- apsfilter.orig Tue Oct 2 01:42:43 2001 +++ apsfilter Wed Oct 3 18:04:59 2001 @@ -1077,35 +1077,11 @@ ps_set_tumble() { - local tumble - if [ "$BINDING" = short ]; then - tumble=true + psset -n -q -t else - tumble=false + psset -n -q -d fi - - # this code was taken from the psset command (a2ps 4.13b) - awk "{ print } /^%%EndProlog/ { print \"\ -countdictstack\n\ -/psset_mark\n\ -{\n\ -%%BeginFeature: *Duplex true\n\ - (<<) cvx exec /Duplex (true) cvx exec (>>) cvx exec\n\ - systemdict /setpagedevice get exec\n\ -%%EndFeature\n\ -%%BeginFeature: *Tumble $tumble\n\ - (<<) cvx exec /Tumble ($tumble) cvx exec (>>) cvx exec\n\ - systemdict /setpagedevice get exec\n\ -%%EndFeature\n\ -} stopped\n\ -{ /psset_mark eq { exit } if } loop\n\ -countdictstack exch sub dup 0 gt\n\ -{\n\ - { end } repeat\n\ -}{\n\ - pop\n\ -} ifelse\" }" } duplex_notification() @@ -1742,13 +1718,13 @@ GS_MODEL="$option" ;; 500c|550c|560c|850c|855c) GS_MODEL="${option%c}C" ;; - mono) GS_FEATURES="$GS_FEATURES -sColorMode=mono" ;; + mono) GS_FEATURES="$GS_FEATURES -sColourModel=Gray" ;; cmy) COLOR=color - GS_FEATURES="$GS_FEATURES -sColorMode=CMY" ;; + GS_FEATURES="$GS_FEATURES -sColourModel=CMY" ;; cmy+k) COLOR=color - GS_FEATURES="$GS_FEATURES -sColorMode=CMY+K" ;; + GS_FEATURES="$GS_FEATURES -sColourModel=CMY+K" ;; cmyk) COLOR=color - GS_FEATURES="$GS_FEATURES -sColorMode=CMYK" ;; + GS_FEATURES="$GS_FEATURES -sColourModel=CMYK" ;; draft) GS_FEATURES="$GS_FEATURES -sPrintQuality=draft" ;; norm*) GS_FEATURES="$GS_FEATURES -sPrintQuality=normal" ;; pres*) GS_FEATURES="$GS_FEATURES -sPrintQuality=presentation";; --bp/iNruPH9dso1Pn-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 1:10:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 432F737B405; Mon, 12 Nov 2001 01:10:34 -0800 (PST) Received: from colt.ncptiddische.net (ppp-196.wobline.de [212.68.69.207]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fAC9AMr09987; Mon, 12 Nov 2001 10:10:23 +0100 Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fAC9AhV12792; Mon, 12 Nov 2001 10:10:43 +0100 (CET) (envelope-from nils@tisys.org) Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by jodie.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fAC9AvV01024; Mon, 12 Nov 2001 10:10:57 +0100 (CET) (envelope-from nils@tisys.org) Date: Mon, 12 Nov 2001 10:10:57 +0100 (CET) From: Nils Holland To: Julian Elischer Cc: hackers@FreeBSD.ORG, Subject: Re: HP deskjet 940 (color) and FreeBSD In-Reply-To: Message-ID: <20011112100903.N922-100000@jodie.ncptiddische.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 11 Nov 2001, Julian Elischer wrote: > Well it prints in b/w really well, Just not in colour.... > however I just found the apsfilter entry for cjd880 > and that seems to work a treat. Well, many different drivers seem to do the job on any HP printer. Last week, when I got my new DJ 930C, I really sat here and let it print a test page with all the HP/PCL3 drivers supported by my ghostscript. The cdj970 worked best, but if you have found that the cdj880 does what you want, there's not really a reason to try something else. You may want to do it for fun, but generally, if it ain't broken, don't fix it. Greetings Nils Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 2:36:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 06AA637B417 for ; Mon, 12 Nov 2001 02:36:51 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fACAaiv75199; Mon, 12 Nov 2001 02:36:44 -0800 (PST) (envelope-from dillon) Date: Mon, 12 Nov 2001 02:36:44 -0800 (PST) From: Matthew Dillon Message-Id: <200111121036.fACAaiv75199@apollo.backplane.com> To: "Jason Mawdsley" Cc: , Subject: Re: mmap/madvise References: <200111081947.fA8JlAe03457@web.cs.ndsu.nodak.edu> <02ae01c16891$4c1f4970$2a64a8c0@macadamian.com> <3BEB0A57.3C510C49@mindspring.com> <019401c16959$4e64a8b0$2a64a8c0@macadamian.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : : :The man pages state that the fd must be -1 for MAP_ANON. :an open() /dev/zero will return an valid file descriptor. So how would I :mmap using /dev/zero? : :> Too bad there isn't an "Advance UNIX programming for Windows :> Programmers" book. 8-(. : :Sounds like their could be a good market for one ;-) : :Jason : :Jason Mawdsley ~ jason@macadamian.com With /dev/zero you open() /dev/zero and do a MAP_PRIVATE mapping of the descriptor. I recommend you use MAP_ANON on systems that support it. /dev/zero might be slightly more portable but I learned the hard way (while writing Diablo) that it isn't guarenteed to work as you might expect across all platforms either. The big problem with /dev/zero is that there is no easy way to tell whether a platform supports anonymous memory allocation via /dev/zero without actually running code to find out, and then there is no easy way to tell what the fork() characteristics are again without actually running code to find out. Ick. If #ifdef MAP_ANON is true then you at least know that MAP_ANON is supported and you should use it. If it isn't true then you can fall back to using a small temporary file, or /dev/zero. In Diablo I finally gave up entirely on /dev/zero and just had three methods: MAP_ANON, the mmap-a-temporary-file trick, and a standard malloc(). The small-temporary-file trick is simple: create a small temporary file, get a file descriptor to it, remove() the file, then ftruncate() the descriptor to the amount of space you need, mmap() it MAP_PRIVATE, and close the descriptor. Since it is a private map no actual space is allocated for the file, only an inode. You can leave the descriptor open if you need to 'allocate' more space using additional calls to mmap(). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 3:51:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ash25.adelaide.on.net (mail.internode.on.net [203.16.214.248]) by hub.freebsd.org (Postfix) with ESMTP id C57C737B416 for ; Mon, 12 Nov 2001 03:51:14 -0800 (PST) Received: from slick ([150.101.145.219]) by internode.on.net (PMDF V6.0-24 #37831) with SMTP id <01KAMS370VDI001QWO@internode.on.net> for hackers@freebsd.org; Mon, 12 Nov 2001 22:18:05 +1030 Date: Mon, 12 Nov 2001 22:21:53 +1030 From: Alex Subject: Fw: ufs:/dev/md0 To: hackers@freebsd.org Message-id: <002e01c16b70$6caab300$26906596@slick> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Content-type: multipart/alternative; boundary="----=_NextPart_000_002B_01C16BC8.6EC96C50" X-Priority: 3 X-MSMail-priority: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_002B_01C16BC8.6EC96C50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Howdy Crew, I have an issue regarding an installation of FreeBSD4.4-Release from = cdrom. When I boot from the cdrom to install, the computer freezes at this = point: acd0:CDROM at ata1-master using PI03 mounting root from ufs:/dev/md0c At this point the computer is comletley frozen and I have to manually = reset. I haven't yet tryed an alternate way of booting, because I would like to = understand what is going on. Would anyone have an idea of what is causing the freeze? Thanks=20 - Alex ------=_NextPart_000_002B_01C16BC8.6EC96C50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

 
Howdy Crew,
 
I have an issue regarding an = installation of=20 FreeBSD4.4-Release from cdrom.
 
When I boot from the cdrom to install, = the computer=20 freezes at this point:
 
      = acd0:CDROM=20 <MATSHITA CR-583> at ata1-master using PI03
      mounting = root from=20 ufs:/dev/md0c
 
At this point the computer is comletley = frozen and=20 I have to manually reset.
 
I haven't yet tryed an alternate way of = booting,=20 because I would like to understand what is
going on.
 
Would anyone have an idea of what is = causing the=20 freeze?
 
 Thanks
 
 - Alex
 
 
------=_NextPart_000_002B_01C16BC8.6EC96C50-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 4:34: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay3-gui.server.ntli.net (relay3-gui.server.ntli.net [194.168.4.200]) by hub.freebsd.org (Postfix) with ESMTP id B14EC37B419 for ; Mon, 12 Nov 2001 04:33:55 -0800 (PST) Received: from pc3-card3-0-cust122.cdf.cable.ntl.com ([62.254.251.122] helo=rhadamanth.private.submonkey.net ident=exim) by relay3-gui.server.ntli.net with esmtp (Exim 3.03 #2) id 163GHf-0006iW-00; Mon, 12 Nov 2001 12:33:52 +0000 Received: from setantae by rhadamanth.private.submonkey.net with local (Exim 3.33 #1) id 163GHY-000L00-00; Mon, 12 Nov 2001 12:33:44 +0000 Date: Mon, 12 Nov 2001 12:33:44 +0000 From: setantae To: Alex Cc: hackers@FreeBSD.org Subject: Re: Fw: ufs:/dev/md0 Message-ID: <20011112123344.GA80642@rhadamanth> Reply-To: questions@FreeBSD.org References: <002e01c16b70$6caab300$26906596@slick> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002e01c16b70$6caab300$26906596@slick> User-Agent: Mutt/1.3.23.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Nov 12, 2001 at 10:21:53PM +1030, Alex wrote: This should have gone to questions (follow up set). > I have an issue regarding an installation of FreeBSD4.4-Release from cdrom. > > When I boot from the cdrom to install, the computer freezes at this point: > > acd0:CDROM at ata1-master using PI03 > mounting root from ufs:/dev/md0c From http://www.FreeBSD.org/cgi/query-pr.cgi?pr=i386/30860 : ``4.4-RELEASE installation requires enabling of 'Assign IRQ for USB' option in AWARD BIOS.'' Ceri -- keep a mild groove on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 5:19:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id D12D137B405 for ; Mon, 12 Nov 2001 05:19:29 -0800 (PST) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 Nov 2001 14:19:26 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FDA08F@l04.research.kpn.com> From: "Koster, K.J." To: "FreeBSD Hackers mailing list (E-mail)" Cc: "Bruin, M.L. de" Subject: FreeBSD on vmware Date: Mon, 12 Nov 2001 14:19:25 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear All, We have a rather beafy server here and we're experimenting with putting a number of vmware sessions on it. To avoid Windows and Linux becoming the only OS'es here in the lab I've volunteered to help out and install FreeBSD. :) I have tried installing on a few configurations; SCSI and IDE, with and without LAN. First: FreeBSD gets a SCSI disk and LAN. The bt0 driver picks up on the disk and proceeds to panic the vmware environment. The main error message is: VMWare GSX Server Panic BUG F(562): 1703 bugnr=4935. Second: FreeBSD gets an IDE disk and LAN. The FreeBSD kernel panics right after detecting the keyboard. The panic is (typed from screen): Fatal trap 12: page fault in vm86 mode fault vir. addr. = 0x1000 code = user read, page not present instr. ptr. = 0x0:0xa03 stack ptr = 0x0:0xffe frame ptr = 0x0:0x0 code seg. = base 0x0, lim 0x0, type 0x0 dpl 0, pres 0, def32 0, gran 0 cpu efl = interrupt enabled, vm86, iopl=0 currproc = 0 (swapper) int mask = net tty bio cam trap = 12 The same panic occurs when I boot up without LAN. This was using FreeBSD version 4.4 from the (ATAPI) cdrom. Detailed logs are available on request and I'm willing to try any experiments you may suggest. Anyone have any suggestions as to what I could try? Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 5:29:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 8DB4237B416; Mon, 12 Nov 2001 05:28:52 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id PAA16421; Mon, 12 Nov 2001 15:28:49 +0200 (EET) (envelope-from max@vega.com) Received: from vega.vega.com (h178.229.dialup.iptcom.net [212.9.229.178]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id PAA40190; Mon, 12 Nov 2001 15:28:47 +0200 (EET) (envelope-from max@vega.com) Received: (from max@localhost) by vega.vega.com (8.11.6/8.11.3) id fACDSGt04364; Mon, 12 Nov 2001 15:28:16 +0200 (EET) (envelope-from sobomax@FreeBSD.org) From: Maxim Sobolev Message-Id: <200111121328.fACDSGt04364@vega.vega.com> Subject: kqueue(2) doesn't deliver EV_EOF on pipes [patch] To: jlemon@FreeBSD.org Date: Mon, 12 Nov 2001 15:28:15 +0200 (EET) Cc: current@FreeBSD.org, hackers@FreeBSD.org X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="%--multipart-mixed-boundary-1.4281.1005571695--%" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --%--multipart-mixed-boundary-1.4281.1005571695--% Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I've noticed that kqueue(2) doesn't notify reader about EV_EOF condition on pipe. Attached simple test program highlights the problem (confirmed both on 5-CURRENT and 4-STABLE). Also attached is the simple fix. -Maxim --%--multipart-mixed-boundary-1.4281.1005571695--% Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Description: ASCII C program text Content-Disposition: attachment; filename="sys_pipe.c.diff" Index: sys/kern/sys_pipe.c =================================================================== RCS file: /home/ncvs/src/sys/kern/sys_pipe.c,v retrieving revision 1.86 diff -d -u -r1.86 sys_pipe.c --- sys/kern/sys_pipe.c 2001/09/21 22:46:53 1.86 +++ sys/kern/sys_pipe.c 2001/11/12 13:28:05 @@ -1221,6 +1221,7 @@ ppipe->pipe_state |= PIPE_EOF; wakeup(ppipe); + KNOTE(&ppipe->pipe_sel.si_note, 0); ppipe->pipe_peer = NULL; } /* --%--multipart-mixed-boundary-1.4281.1005571695--% Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Description: ASCII C program text Content-Disposition: attachment; filename="testpipe.c" #include #include #include #include #include #include #include void testpassed(int sig) { printf("Test passed\n"); exit(0); } int main(int argc, char **argv) { int kq, pid, ppid, nevents; struct kevent changelist[1]; struct kevent eventlist[1]; int pp[2]; pipe(pp); ppid = getpid(); pid = fork(); switch (pid) { case -1: /* Error */ err(1, "can't fork()"); /* NOTREACHED */ case 0: /* Child */ close(pp[1]); kq = kqueue(); EV_SET(changelist, pp[0], EVFILT_READ, EV_ADD | EV_ENABLE | EV_EOF, \ 0, 0, NULL); kevent(kq, changelist, 1, NULL, 0, NULL); for (;;) { nevents = kevent(kq, NULL, 0, eventlist, 1, NULL); if (nevents > 0 || (eventlist[0].flags & EV_EOF) != 0) { kill(ppid, SIGTERM); exit(0); } } break; default: /* Sever */ close(pp[0]); break; } signal(SIGTERM, testpassed); /* Give child some time to initialise kqueue(2) */ sleep(1); close(pp[1]); /* Give child some time to receive EV_EOF and kill us */ sleep(1); kill(pid, SIGTERM); printf("Test failed\n"); exit(1); } --%--multipart-mixed-boundary-1.4281.1005571695--%-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 5:50:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 883A837B405; Mon, 12 Nov 2001 05:50:30 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id PAA30792; Mon, 12 Nov 2001 15:50:27 +0200 (EET) (envelope-from max@vega.com) Received: from vega.vega.com (h156.228.dialup.iptcom.net [212.9.228.156]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id PAA49060; Mon, 12 Nov 2001 15:50:25 +0200 (EET) (envelope-from max@vega.com) Received: (from max@localhost) by vega.vega.com (8.11.6/8.11.3) id fACDnfT04437; Mon, 12 Nov 2001 15:49:41 +0200 (EET) (envelope-from sobomax@FreeBSD.org) From: Maxim Sobolev Message-Id: <200111121349.fACDnfT04437@vega.vega.com> Subject: Re: kqueue(2) doesn't deliver EV_EOF on pipes [patch] To: sobomax@FreeBSD.ORG (Maxim Sobolev) Date: Mon, 12 Nov 2001 15:48:39 +0200 (EET) Cc: jlemon@FreeBSD.ORG, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Maxim Sobolev" at Nov 12, 2001 03:28:15 PM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > if (nevents > 0 || (eventlist[0].flags & EV_EOF) != 0) { ^^ OOPS, last minute bug. Should be `&&' instead, but it doesn't affect outcome of the test. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 5:57:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id 647C637B419 for ; Mon, 12 Nov 2001 05:57:48 -0800 (PST) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 Nov 2001 14:57:47 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FDA091@l04.research.kpn.com> From: "Koster, K.J." To: 'Rohit Grover' Cc: "FreeBSD Hackers mailing list (E-mail)" , "Bruin, M.L. de" Subject: RE: FreeBSD on vmware Date: Mon, 12 Nov 2001 14:57:45 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear Rohit, Thanks for the response and your suggestion. > > > Fatal trap 12: page fault in vm86 mode > > The following change helped me get rid of a similar panic. > > - device atkbd0 at atkbdc? irq 1 > + device atkbd0 at atkbdc? irq 1 flags 0x1 > When I look at the keyboard in the visual kernel configuration this flag is already set. Just out of curiousity, are there any people who actually have FreeBSD running inside a vmware VM? Evidence from the mailing list archives seems to suggest that it worked up to FreeBSD 3.2 and then stopped, never to work again. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 6:25:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 069BE37B416 for ; Mon, 12 Nov 2001 06:25:24 -0800 (PST) Received: from nycmny1-013-179.elnk.dsl.gtei.net ([4.60.13.179] helo=raff.ElectroCity.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 163I1F-00023c-00; Mon, 12 Nov 2001 06:25:01 -0800 Message-Id: <5.1.0.14.0.20011112091938.052a8600@pop.earthlink.net> X-Sender: astralflash@earthlink.net@pop.earthlink.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 12 Nov 2001 09:24:57 -0500 To: "Koster, K.J." From: Michael Raff Subject: RE: FreeBSD on vmware Cc: "FreeBSD Hackers mailing list (E-mail)" In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FDA091@l04.research.kpn. com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yes, I am running FreeBSD 4.3 in a win2k vmware will everything working including the network (to outside world). No special configurations were required other than the obvious. At 08:57 AM 11/12/2001, Koster, K.J. wrote: >Just out of curiousity, are there any people who actually have FreeBSD >running inside a vmware VM? Evidence from the mailing list archives seems to >suggest that it worked up to FreeBSD 3.2 and then stopped, never to work >again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 6:59:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elisa.utopianet.net (elisa.utopianet.net [212.210.231.2]) by hub.freebsd.org (Postfix) with ESMTP id A72DB37B418 for ; Mon, 12 Nov 2001 06:59:11 -0800 (PST) Received: from LORENZO (cl1.sintesi.net [212.210.231.22]) by elisa.utopianet.net (8.9.1a/8.9.1) with SMTP id PAA17942 for ; Mon, 12 Nov 2001 15:59:01 +0100 (CET) Message-ID: <014e01c16b8a$bdb4b4c0$0500000a@LORENZO> From: "Lorenzo Iania" To: References: <59063B5B4D98D311BC0D0001FA7E452205FDA08F@l04.research.kpn.com> Subject: Re: FreeBSD on vmware Date: Mon, 12 Nov 2001 16:00:11 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am running FreeBSD 4.4 in a win2k vmware. Everything seems to work without any perticoular configurations. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 7:12:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from castle.jp.freebsd.org (castle.jp.FreeBSD.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 9719B37B417 for ; Mon, 12 Nov 2001 07:12:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id AAA90010 for ; Tue, 13 Nov 2001 00:12:46 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <5.1.0.14.0.20011112091938.052a8600@pop.earthlink.net> References: <59063B5B4D98D311BC0D0001FA7E452205FDA091@l04.research.kpn. com> <5.1.0.14.0.20011112091938.052a8600@pop.earthlink.net> X-User-Agent: Mew/1.94.2 XEmacs/21.5 (alfalfa) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 10 From: Makoto Matsushita To: hackers@FreeBSD.ORG Subject: RE: FreeBSD on vmware Date: Tue, 13 Nov 2001 00:12:44 +0900 Message-Id: <20011113001244H.matusita@jp.FreeBSD.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG raff> Yes, I am running FreeBSD 4.3 in a win2k vmware will everything raff> working including the network (to outside world). No special raff> configurations were required other than the obvious. FreeBSD 5-current guest also works fine here (W2k host). I'm happy with ports/emulators/vmware-tools :-) -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 7:36:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta10.onebox.com (mta10.onebox.com [64.68.76.184]) by hub.freebsd.org (Postfix) with ESMTP id EDEF437B418 for ; Mon, 12 Nov 2001 07:36:10 -0800 (PST) Received: from onebox.com ([10.1.111.8]) by mta10.onebox.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20011112153610.CROT27419.mta10.onebox.com@onebox.com>; Mon, 12 Nov 2001 07:36:10 -0800 Received: from [63.49.217.164] by onebox.com with HTTP; Mon, 12 Nov 2001 07:36:10 -0800 Date: Mon, 12 Nov 2001 07:36:10 -0800 Subject: RE: FreeBSD on vmware From: "Glenn Gombert" To: Michael Raff Cc: "Koster, K.J." , "FreeBSD Hackers mailing list (E-mail)" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Message-Id: <20011112153610.CROT27419.mta10.onebox.com@onebox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am running VMware on my Dell 5000e LapTop using Win2k right now and 4.3 seems to work fine....I 'hang' badly when trying to run 'Current' however ...and I am still trying to sort out why that is .... Glenn G. -- Glenn Gombert glenngombert@onebox.com - email (513) 587-2643 x2263 - voicemail/fax ---- Michael Raff wrote: > Yes, I am running FreeBSD 4.3 in a win2k vmware will everything working > > including the network (to outside world). No special configurations > were > required other than the obvious. > > At 08:57 AM 11/12/2001, Koster, K.J. wrote: > > >Just out of curiousity, are there any people who actually have FreeBSD > >running inside a vmware VM? Evidence from the mailing list archives > seems to > >suggest that it worked up to FreeBSD 3.2 and then stopped, never to > work > >again. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 7:58:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id D1F1C37B405 for ; Mon, 12 Nov 2001 07:58:41 -0800 (PST) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Mon, 12 Nov 2001 15:56:28 +0000 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 163JQd-0002X6-00; Mon, 12 Nov 2001 15:55:19 +0000 Date: Mon, 12 Nov 2001 15:55:19 +0000 (GMT) From: Jan Grant X-X-Sender: To: "Koster, K.J." Cc: 'Rohit Grover' , "FreeBSD Hackers mailing list (E-mail)" , "Bruin, M.L. de" Subject: RE: FreeBSD on vmware In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FDA091@l04.research.kpn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 12 Nov 2001, Koster, K.J. wrote: > Just out of curiousity, are there any people who actually have FreeBSD > running inside a vmware VM? Evidence from the mailing list archives seems to > suggest that it worked up to FreeBSD 3.2 and then stopped, never to work > again. Yep; 4-stable with nary a hitch (I use it for testing remote hands-off upgrades and for hacking around with bits and pieces like rc.d jiggery-pokery). I've had -current running on it in the past, but not looked at this recently due to a CFT suddenly being less C. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk Axioms speak louder than words. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 8: 6:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.teledis.be (mail.teledis.be [217.117.32.52]) by hub.freebsd.org (Postfix) with ESMTP id C474437B405 for ; Mon, 12 Nov 2001 08:06:46 -0800 (PST) Received: from 217-117-54-102.teledisnet.be ([217.117.54.102]) by mail.teledis.be (Netscape Messaging Server 4.15) with ESMTP id GMP3FD01.EU4 for ; Mon, 12 Nov 2001 17:06:49 +0100 Subject: Hijack lpt_intr() from lpt driver From: Sansonetti Laurent To: freebsd-hackers@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 12 Nov 2001 17:06:32 +0000 Message-Id: <1005584796.830.6.camel@teneriel.teledisnet.be> Mime-Version: 1.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi hackers, I have to hijack lpt_intr() from lpt device driver (/sys/dev/ppbus/lpt.c) to measure latency. Is this right = BUS_TEARDOWN_INTR(old interrupt handler); BUS_SETUP_INTR(new interrupt handler); ? In fact I could not get resource structure and the cookie from lpt driver, so before doing bad things I would want to know if this is the right way to hijack a hardware interrupt handler. Thanks in advance, -- Sansonetti Laurent - http://lrz.linuxbe.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 8:29:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id DDF9B37B405 for ; Mon, 12 Nov 2001 08:29:08 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fACGSFL20834; Mon, 12 Nov 2001 17:28:15 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Sansonetti Laurent Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Hijack lpt_intr() from lpt driver In-Reply-To: Your message of "12 Nov 2001 17:06:32 GMT." <1005584796.830.6.camel@teneriel.teledisnet.be> Date: Mon, 12 Nov 2001 17:28:15 +0100 Message-ID: <20832.1005582495@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <1005584796.830.6.camel@teneriel.teledisnet.be>, Sansonetti Laurent writes: >Hi hackers, > >I have to hijack lpt_intr() from lpt device driver >(/sys/dev/ppbus/lpt.c) to measure latency. Uhm, why don't you simply use the pps driver ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 8:54:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 5A10737B405; Mon, 12 Nov 2001 08:54:07 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id fACGrse00533; Mon, 12 Nov 2001 08:53:54 -0800 Date: Mon, 12 Nov 2001 08:53:54 -0800 From: Brooks Davis To: matt Cc: "Daniel O'Connor" , freebsd-hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: wake up on lan driver support Message-ID: <20011112085354.A29887@Odin.AC.HMC.Edu> References: <000d01c16b12$6cc333c0$6503c23f@XGforce.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000d01c16b12$6cc333c0$6503c23f@XGforce.com>; from matt-l@pacbell.net on Sun, Nov 11, 2001 at 04:38:50PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 11, 2001 at 04:38:50PM -0800, matt wrote: > any clue to find the tech doc regarding the format of > the packet. I'd code such thing. It's a very good > feature for FreeBSD. ports/net/wakeonlan I'd really like to see some driver support for WOL for support of dynamic power control on clusters. Suspend/Resume is going to be faster then a boot cycle unless someone ports the loader to the LinuxBIOS framework. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE77/6hXY6L6fI4GtQRAjsGAKC0fVLYY3gGGRssz+BHj6RDgW5VqQCgkoOr af1VLq6jSnpaboPLaFZYz+w= =/izp -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 9: 0:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 80DC037B405 for ; Mon, 12 Nov 2001 09:00:28 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id IAA94066; Mon, 12 Nov 2001 08:42:38 -0800 (PST) Date: Mon, 12 Nov 2001 08:42:38 -0800 (PST) From: Julian Elischer To: "Koster, K.J." Cc: "'Rohit Grover'" , "FreeBSD Hackers mailing list (E-mail)" , "Bruin, M.L. de" Subject: RE: FreeBSD on vmware In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FDA091@l04.research.kpn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG oh yeah there was a period where the lnc driver caused a crash of vmware. leave it out and try again.... On Mon, 12 Nov 2001, Koster, K.J. wrote: > Dear Rohit, > > Thanks for the response and your suggestion. > > > > > > Fatal trap 12: page fault in vm86 mode > > > > The following change helped me get rid of a similar panic. > > > > - device atkbd0 at atkbdc? irq 1 > > + device atkbd0 at atkbdc? irq 1 flags 0x1 > > > When I look at the keyboard in the visual kernel configuration this flag is > already set. > > Just out of curiousity, are there any people who actually have FreeBSD > running inside a vmware VM? Evidence from the mailing list archives seems to > suggest that it worked up to FreeBSD 3.2 and then stopped, never to work > again. > > Kees Jan > > ================================================ > You are only young once, > but you can stay immature all your life. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 9: 0:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 2542A37B41A for ; Mon, 12 Nov 2001 09:00:33 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id IAA94064; Mon, 12 Nov 2001 08:41:24 -0800 (PST) Date: Mon, 12 Nov 2001 08:41:22 -0800 (PST) From: Julian Elischer To: "Koster, K.J." Cc: "'Rohit Grover'" , "FreeBSD Hackers mailing list (E-mail)" , "Bruin, M.L. de" Subject: RE: FreeBSD on vmware In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FDA091@l04.research.kpn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have been running -current under vmware 2.x up until about August.. (it didn't stop working, but I vmware stopped running on -current due to KSE changes (patches now available I believe)).. i.e I was running -current under -current On Mon, 12 Nov 2001, Koster, K.J. wrote: > Dear Rohit, > > Thanks for the response and your suggestion. > > > > > > Fatal trap 12: page fault in vm86 mode > > > > The following change helped me get rid of a similar panic. > > > > - device atkbd0 at atkbdc? irq 1 > > + device atkbd0 at atkbdc? irq 1 flags 0x1 > > > When I look at the keyboard in the visual kernel configuration this flag is > already set. > > Just out of curiousity, are there any people who actually have FreeBSD > running inside a vmware VM? Evidence from the mailing list archives seems to > suggest that it worked up to FreeBSD 3.2 and then stopped, never to work > again. > > Kees Jan > > ================================================ > You are only young once, > but you can stay immature all your life. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 9:17:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.teledis.be (mail.teledis.be [217.117.32.52]) by hub.freebsd.org (Postfix) with ESMTP id 5263837B405 for ; Mon, 12 Nov 2001 09:17:27 -0800 (PST) Received: from 217-117-54-102.teledisnet.be ([217.117.54.102]) by mail.teledis.be (Netscape Messaging Server 4.15) with ESMTP id GMP6P500.OTK; Mon, 12 Nov 2001 18:17:29 +0100 Subject: Re: Hijack lpt_intr() from lpt driver From: Sansonetti Laurent To: Poul-Henning Kamp Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <20832.1005582495@critter.freebsd.dk> References: <20832.1005582495@critter.freebsd.dk> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 12 Nov 2001 18:17:13 +0000 Message-Id: <1005589037.830.10.camel@teneriel.teledisnet.be> Mime-Version: 1.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 2001-11-12 at 16:28, Poul-Henning Kamp wrote: > > Uhm, why don't you simply use the pps driver ? > Yes, why not.. but I have the same problem : how to hijack current interrupt handler ? I don't want to patch the kernel.. Thanks in advance, -- Sansonetti Laurent - http://lrz.linuxbe.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 10:10:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 88AB537B405 for ; Mon, 12 Nov 2001 10:10:14 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fACIC0n01123; Mon, 12 Nov 2001 10:12:01 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200111121812.fACIC0n01123@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Sansonetti Laurent Cc: freebsd-hackers@freebsd.org Subject: Re: Hijack lpt_intr() from lpt driver In-reply-to: Your message of "12 Nov 2001 17:06:32 GMT." <1005584796.830.6.camel@teneriel.teledisnet.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Nov 2001 10:12:00 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Don't do this; write your own ppbus driver and just claim the ppbus directly when you are 'active'. > Hi hackers, > > I have to hijack lpt_intr() from lpt device driver > (/sys/dev/ppbus/lpt.c) to measure latency. > > Is this right = > > BUS_TEARDOWN_INTR(old interrupt handler); > BUS_SETUP_INTR(new interrupt handler); > > ? > > In fact I could not get resource structure and the cookie from lpt > driver, so before doing bad things I would want to know if this is the > right way to hijack a hardware interrupt handler. > > Thanks in advance, > > > -- > Sansonetti Laurent - http://lrz.linuxbe.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 10:11:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id F0A5C37B417 for ; Mon, 12 Nov 2001 10:11:35 -0800 (PST) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 Nov 2001 19:11:34 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FDA095@l04.research.kpn.com> From: "Koster, K.J." To: "FreeBSD Hackers mailing list (E-mail)" Cc: "Bruin, M.L. de" Subject: RE: FreeBSD on vmware Date: Mon, 12 Nov 2001 19:11:33 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [ Picking any one to reply to... ] > > I have been running -current under vmware 2.x up until about August.. > (it didn't stop working, but I vmware stopped running on -current > due to KSE changes (patches now available I believe)).. > > i.e I was running -current under -current > Thanks to all who responded. The fact that it works for some reassures me that it might work for me too. :-) I'm still at a loss what to do about the vmware and kernel panics. The vmware tools port is not a big help, since I have no FreeBSD to install it into. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 10:14:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 7DC5337B416 for ; Mon, 12 Nov 2001 10:14:24 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fACIDUL22413; Mon, 12 Nov 2001 19:13:30 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Sansonetti Laurent Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Hijack lpt_intr() from lpt driver In-Reply-To: Your message of "12 Nov 2001 18:17:13 GMT." <1005589037.830.10.camel@teneriel.teledisnet.be> Date: Mon, 12 Nov 2001 19:13:30 +0100 Message-ID: <22411.1005588810@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <1005589037.830.10.camel@teneriel.teledisnet.be>, Sansonetti Laurent writes: >On Mon, 2001-11-12 at 16:28, Poul-Henning Kamp wrote: >> >> Uhm, why don't you simply use the pps driver ? >> > >Yes, why not.. but I have the same problem : how to hijack current >interrupt handler ? I don't want to patch the kernel.. Uhm, the pps driver implements the RFC 2783 PPS-API which does exactly timestamping of external events, and which include facilities to measure the delay, jitter and dispersion. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 12:22:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from seven.Alameda.net (seven.Alameda.net [64.81.63.137]) by hub.freebsd.org (Postfix) with ESMTP id BBF6D37B417 for ; Mon, 12 Nov 2001 12:22:16 -0800 (PST) Received: by seven.Alameda.net (Postfix, from userid 1000) id 7C0743A248; Mon, 12 Nov 2001 12:22:16 -0800 (PST) Date: Mon, 12 Nov 2001 12:22:16 -0800 From: Ulf Zimmermann To: hackers@freebsd.org Subject: Skeleton pseudo device driver for 4.4-STABLE ? Message-ID: <20011112122216.E8046@seven.alameda.net> Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 4.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I looked at /usr/share/examples/drivers/make_pseudo_driver.sh but it seems to be a bit out of date. Running it, it creates a file "files." in /usr/src/sys/i386/conf, where "files" doesn't exists there anymore. It also adds "device-driver" at the end of line which is obsolete as far I can tell. Anyone wanna give me a pointer at what to look at for a skeleton driver ? I got finaly an Digi Etherlite unit and want to see if I can port the linux driver. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 12:50:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id 2136E37B418 for ; Mon, 12 Nov 2001 12:50:53 -0800 (PST) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 Nov 2001 21:50:51 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FDA09A@l04.research.kpn.com> From: "Koster, K.J." To: freebsd-hackers@FreeBSD.ORG Subject: Please commit this port: ports/31188: New port: www/orion-current Date: Mon, 12 Nov 2001 21:50:51 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear All, Guys, please. Is there noone with a tiny bit of time on their hands and -ports commit privs? I've been bugging -java -ports and now -hackers and get no reaction at all. What happened to the close-a-PR drive? Kees Jan ================================================ You are only young once, but you can stay immature all your life. > -----Original Message----- > From: Kees Jan Koster [mailto:kjkoster@kjkoster.org] > Sent: vrijdag 9 november 2001 22:45 > To: freebsd-hackers@FreeBSD.ORG > Subject: Re: ports/31188: New port: www/orion-current > > > Dear All, > > I've tried to get someone to commit this port over on -ports, but > I got no response. Is there someone who could commit this port, > please? > > Thanks in advance. > > Yours, > Kees Jan > > ------------------------------------------------------- > Kees Jan Koster e-mail: kjkoster "at" kjkoster.org > www: http://www.kjkoster.org/ > ------------------------------------------------------- > File not found. Should I fake it? [Y/N] > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 12:55: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from coffee.q9media.com (coffee.q9media.com [216.94.229.19]) by hub.freebsd.org (Postfix) with ESMTP id 576A137B405 for ; Mon, 12 Nov 2001 12:54:59 -0800 (PST) Received: (from mike@localhost) by coffee.q9media.com (8.11.6/8.11.6) id fACL1JH54084; Mon, 12 Nov 2001 16:01:19 -0500 (EST) (envelope-from mike) Date: Mon, 12 Nov 2001 16:01:19 -0500 From: Mike Barcroft To: "Koster, K.J." Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Please commit this port: ports/31188: New port: www/orion-current Message-ID: <20011112160118.A54042@coffee.q9media.com> References: <59063B5B4D98D311BC0D0001FA7E452205FDA09A@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FDA09A@l04.research.kpn.com>; from K.J.Koster@kpn.com on Mon, Nov 12, 2001 at 09:50:51PM +0100 Organization: The FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Koster, K.J. writes: > Guys, please. Is there noone with a tiny bit of time on their hands and > -ports commit privs? I've been bugging -java -ports and now -hackers and get > no reaction at all. What happened to the close-a-PR drive? This is inappropriate discussion for -hackers so you're unlikely to find a response here. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 12:59:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id 708D037B418; Mon, 12 Nov 2001 12:59:55 -0800 (PST) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 Nov 2001 21:59:54 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FDA09B@l04.research.kpn.com> From: "Koster, K.J." To: 'Mike Barcroft' Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: Please commit this port: ports/31188: New port: www/orion-cur rent Date: Mon, 12 Nov 2001 21:59:53 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear Mike, > > > Guys, please. Is there noone with a tiny bit of time on > their hands and > > -ports commit privs? I've been bugging -java -ports and now > -hackers and get > > no reaction at all. What happened to the close-a-PR drive? > > This is inappropriate discussion for -hackers so you're unlikely to > find a response here. > I am fully aware that -hackers is not the right forum for this discussion, and I apologise for the noise. I tried the appropriate mailing lists first and got ignored. You are the second person to respond to two mails to -ports, one to -java and one to -hackers. I'm open to other ideas on how to get this port committed. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 13:10: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from coffee.q9media.com (coffee.q9media.com [216.94.229.19]) by hub.freebsd.org (Postfix) with ESMTP id C9A0137B417 for ; Mon, 12 Nov 2001 13:09:56 -0800 (PST) Received: (from mike@localhost) by coffee.q9media.com (8.11.6/8.11.6) id fACLGa054151; Mon, 12 Nov 2001 16:16:36 -0500 (EST) (envelope-from mike) Date: Mon, 12 Nov 2001 16:16:36 -0500 From: Mike Barcroft To: "Koster, K.J." Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Please commit this port: ports/31188: New port: www/orion-cur rent Message-ID: <20011112161636.A54135@coffee.q9media.com> References: <59063B5B4D98D311BC0D0001FA7E452205FDA09B@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FDA09B@l04.research.kpn.com>; from K.J.Koster@kpn.com on Mon, Nov 12, 2001 at 09:59:53PM +0100 Organization: The FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Koster, K.J. writes: > I am fully aware that -hackers is not the right forum for this discussion, > and I apologise for the noise. I tried the appropriate mailing lists first > and got ignored. You are the second person to respond to two mails to > -ports, one to -java and one to -hackers. > > I'm open to other ideas on how to get this port committed. The best advice I can give is to just be patient. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 13:18:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id 9E11437B405; Mon, 12 Nov 2001 13:18:54 -0800 (PST) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 Nov 2001 22:18:53 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FDA09D@l04.research.kpn.com> From: "Koster, K.J." To: 'Mike Barcroft' Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: Please commit this port: ports/31188: New port: www/orion-cur rent Date: Mon, 12 Nov 2001 22:18:52 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear Mike, > > > I am fully aware that -hackers is not the right forum for > this discussion, > > and I apologise for the noise. I tried the appropriate > mailing lists first > > and got ignored. You are the second person to respond to > two mails to > > -ports, one to -java and one to -hackers. > > > > I'm open to other ideas on how to get this port committed. > > The best advice I can give is to just be patient. > Thanks for your advice. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 13:40:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 97BE637B417 for ; Mon, 12 Nov 2001 13:40:14 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA95006; Mon, 12 Nov 2001 13:36:16 -0800 (PST) Date: Mon, 12 Nov 2001 13:36:16 -0800 (PST) From: Julian Elischer To: Ulf Zimmermann Cc: hackers@freebsd.org Subject: Re: Skeleton pseudo device driver for 4.4-STABLE ? In-Reply-To: <20011112122216.E8046@seven.alameda.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Try the one from -current.. If it works maybe it should be MFC'd julian On Mon, 12 Nov 2001, Ulf Zimmermann wrote: > I looked at /usr/share/examples/drivers/make_pseudo_driver.sh but it > seems to be a bit out of date. Running it, it creates a file > "files." in /usr/src/sys/i386/conf, where "files" doesn't > exists there anymore. It also adds "device-driver" at the end of > line which is obsolete as far I can tell. > > Anyone wanna give me a pointer at what to look at for a skeleton > driver ? I got finaly an Digi Etherlite unit and want to see if > I can port the linux driver. > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 14:12:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from seven.Alameda.net (seven.Alameda.net [64.81.63.137]) by hub.freebsd.org (Postfix) with ESMTP id D8B1737B405 for ; Mon, 12 Nov 2001 14:12:28 -0800 (PST) Received: by seven.Alameda.net (Postfix, from userid 1000) id 813303A23B; Mon, 12 Nov 2001 14:12:28 -0800 (PST) Date: Mon, 12 Nov 2001 14:12:28 -0800 From: Ulf Zimmermann To: Julian Elischer Cc: Ulf Zimmermann , hackers@freebsd.org Subject: Re: Skeleton pseudo device driver for 4.4-STABLE ? Message-ID: <20011112141228.G8046@seven.alameda.net> Reply-To: ulf@Alameda.net References: <20011112122216.E8046@seven.alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Mon, Nov 12, 2001 at 01:36:16PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 4.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Nov 12, 2001 at 01:36:16PM -0800, Julian Elischer wrote: > Try the one from -current.. > If it works maybe it should be MFC'd Nope, more or less same stuff: On 4.4-STABLE: # \$FreeBSD: src/share/examples/drivers/make_pseudo_driver.sh,v 1.5.2.1 2001/07/25 15:56:09 dd Exp $" From a fresh cvsuped -current: # \$FreeBSD: src/share/examples/drivers/make_pseudo_driver.sh,v 1.6 2001/05/01 09:14:45 schweikh Exp $" Last modification on -current is longer ago then on -STABLE. Both have the same symtons: playtoy root examples/drivers # sh make_pseudo_driver.sh els files.ELS: `device-driver' flag obsolete. make: don't know how to make depend. Stop make: don't know how to make els.o. Stop make: no target to make. Files created by the script: /usr/src/sys/i386/conf/ELS /usr/src/sys/i386/conf/files.ELS Diff of ELS to GENERIC: 1,3d0 < # Configuration file for kernel type: ELS < ident ELS < # $FreeBSD: src/share/examples/drivers/make_pseudo_driver.sh,v 1.6 2001/05/01 09:14:45 schweikh Exp $" 4a2 > # GENERIC -- Generic kernel configuration file for FreeBSD/i386 19a18 > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.35 2001/09/27 17:43:06 alfred Exp $ 25a25 > ident GENERIC 251,253d250 < # trust me, you'll need this < options DDB < device els 4 # might as well allow 4 of them Contents of files.ELS: dev/els.c optional els device-driver > > julian > > On Mon, 12 Nov 2001, Ulf Zimmermann wrote: > > > I looked at /usr/share/examples/drivers/make_pseudo_driver.sh but it > > seems to be a bit out of date. Running it, it creates a file > > "files." in /usr/src/sys/i386/conf, where "files" doesn't > > exists there anymore. It also adds "device-driver" at the end of > > line which is obsolete as far I can tell. > > > > Anyone wanna give me a pointer at what to look at for a skeleton > > driver ? I got finaly an Digi Etherlite unit and want to see if > > I can port the linux driver. > > > > -- > > Regards, Ulf. > > > > --------------------------------------------------------------------- > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 14:53:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from raven.mail.pas.earthlink.net (raven.mail.pas.earthlink.net [207.217.120.39]) by hub.freebsd.org (Postfix) with ESMTP id 24DAB37B417 for ; Mon, 12 Nov 2001 14:53:39 -0800 (PST) Received: from dialup-209.245.136.188.dial1.sanjose1.level3.net ([209.245.136.188] helo=mindspring.com) by raven.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 163Pww-0005jt-00; Mon, 12 Nov 2001 14:53:06 -0800 Message-ID: <3BF05303.FEC66C7A@mindspring.com> Date: Mon, 12 Nov 2001 14:53:55 -0800 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Jason Mawdsley , freebsd-hackers@FreeBSD.ORG Subject: Re: mmap/madvise References: <200111081947.fA8JlAe03457@web.cs.ndsu.nodak.edu> <02ae01c16891$4c1f4970$2a64a8c0@macadamian.com> <3BEB0A57.3C510C49@mindspring.com> <019401c16959$4e64a8b0$2a64a8c0@macadamian.com> <200111121036.fACAaiv75199@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > The small-temporary-file trick is simple: create a small temporary > file, get a file descriptor to it, remove() the file, then ftruncate() > the descriptor to the amount of space you need, mmap() it > MAP_PRIVATE, and close the descriptor. Since it is a private map no > actual space is allocated for the file, only an inode. You can > leave the descriptor open if you need to 'allocate' more space using > additional calls to mmap(). One of his original issues was avoiding overcommit. In the file backed region case, as I suggested in my original response, to get this behaviour, he would have to touch each of the blocks in the file following the truncation, to make sure he didn't fall into an overcommit based failure later. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 15: 0:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 6711437B416 for ; Mon, 12 Nov 2001 15:00:21 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA95237; Mon, 12 Nov 2001 14:54:27 -0800 (PST) Date: Mon, 12 Nov 2001 14:54:26 -0800 (PST) From: Julian Elischer To: Ulf Zimmermann Cc: hackers@freebsd.org Subject: Re: Skeleton pseudo device driver for 4.4-STABLE ? In-Reply-To: <20011112141228.G8046@seven.alameda.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG errr try the 'device driver' you are making a real device driver, not a pseudo driver.. (the pseudo driver should go away I think...) On Mon, 12 Nov 2001, Ulf Zimmermann wrote: > On Mon, Nov 12, 2001 at 01:36:16PM -0800, Julian Elischer wrote: > > Try the one from -current.. > > If it works maybe it should be MFC'd > > Nope, more or less same stuff: > > On 4.4-STABLE: > > # \$FreeBSD: src/share/examples/drivers/make_pseudo_driver.sh,v 1.5.2.1 2001/07/25 15:56:09 dd Exp $" > > From a fresh cvsuped -current: > > # \$FreeBSD: src/share/examples/drivers/make_pseudo_driver.sh,v 1.6 2001/05/01 09:14:45 schweikh Exp $" > > Last modification on -current is longer ago then on -STABLE. Both have the same symtons: > > playtoy root examples/drivers # sh make_pseudo_driver.sh els > files.ELS: `device-driver' flag obsolete. > make: don't know how to make depend. Stop > make: don't know how to make els.o. Stop > make: no target to make. > > Files created by the script: > > /usr/src/sys/i386/conf/ELS > /usr/src/sys/i386/conf/files.ELS > > Diff of ELS to GENERIC: > > 1,3d0 > < # Configuration file for kernel type: ELS > < ident ELS > < # $FreeBSD: src/share/examples/drivers/make_pseudo_driver.sh,v 1.6 2001/05/01 09:14:45 schweikh Exp $" > 4a2 > > # GENERIC -- Generic kernel configuration file for FreeBSD/i386 > 19a18 > > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.35 2001/09/27 17:43:06 alfred Exp $ > 25a25 > > ident GENERIC > 251,253d250 > < # trust me, you'll need this > < options DDB > < device els 4 # might as well allow 4 of them > > Contents of files.ELS: > > dev/els.c optional els device-driver > > > > > julian > > > > On Mon, 12 Nov 2001, Ulf Zimmermann wrote: > > > > > I looked at /usr/share/examples/drivers/make_pseudo_driver.sh but it > > > seems to be a bit out of date. Running it, it creates a file > > > "files." in /usr/src/sys/i386/conf, where "files" doesn't > > > exists there anymore. It also adds "device-driver" at the end of > > > line which is obsolete as far I can tell. > > > > > > Anyone wanna give me a pointer at what to look at for a skeleton > > > driver ? I got finaly an Digi Etherlite unit and want to see if > > > I can port the linux driver. > > > > > > -- > > > Regards, Ulf. > > > > > > --------------------------------------------------------------------- > > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 15: 2:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4449337B417 for ; Mon, 12 Nov 2001 15:02:13 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fACN2C306926; Mon, 12 Nov 2001 15:02:12 -0800 (PST) (envelope-from dillon) Date: Mon, 12 Nov 2001 15:02:12 -0800 (PST) From: Matthew Dillon Message-Id: <200111122302.fACN2C306926@apollo.backplane.com> To: Terry Lambert Cc: Jason Mawdsley , freebsd-hackers@FreeBSD.ORG Subject: Re: mmap/madvise References: <200111081947.fA8JlAe03457@web.cs.ndsu.nodak.edu> <02ae01c16891$4c1f4970$2a64a8c0@macadamian.com> <3BEB0A57.3C510C49@mindspring.com> <019401c16959$4e64a8b0$2a64a8c0@macadamian.com> <200111121036.fACAaiv75199@apollo.backplane.com> <3BF05303.FEC66C7A@mindspring.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Matthew Dillon wrote: :> The small-temporary-file trick is simple: create a small temporary :> file, get a file descriptor to it, remove() the file, then ftruncate() :> the descriptor to the amount of space you need, mmap() it :> MAP_PRIVATE, and close the descriptor. Since it is a private map no :> actual space is allocated for the file, only an inode. You can :> leave the descriptor open if you need to 'allocate' more space using :> additional calls to mmap(). : :One of his original issues was avoiding overcommit. In the file :backed region case, as I suggested in my original response, to :get this behaviour, he would have to touch each of the blocks in :the file following the truncation, to make sure he didn't fall :into an overcommit based failure later. : :-- Terry This example was for anonymous memory, not file-backed memory. mmap()ing the dummy file MAP_PRIVATE means that none of the I/O ever gets to the filesystem or the file, so no blocks are ever allocated (or ever have to be). The only responsible, reasonable, and dependable way to avoid overcommit is to outfit the system according to the type of load you want to place on it, and for the programs being run to be told how far they are allowed to go and to govern themselves using that information. This is going to be true whether you are backing your storage with anonymous memory (swap/phys backed), or whether you are backing it with a pre-written file. Simply using a pre-written file does not really guarentee anything... after all, you can run out of space on the filesystem as easily as you can run out of VM, and if you store other things, like configuration data, in the same filesystem, you are just as vulnerable to bad programming in the event of a write() filesystem-full failure as you are vulnerable to overcomitting the VM system to the point where it starts killing processes. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 15:21:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 77F8337B419 for ; Mon, 12 Nov 2001 15:21:30 -0800 (PST) Received: from dialup-209.245.136.188.dial1.sanjose1.level3.net ([209.245.136.188] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 163QOM-0006kG-00; Mon, 12 Nov 2001 15:21:26 -0800 Message-ID: <3BF059A7.12FA60F3@mindspring.com> Date: Mon, 12 Nov 2001 15:22:15 -0800 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Jason Mawdsley , freebsd-hackers@FreeBSD.ORG Subject: Re: mmap/madvise References: <200111081947.fA8JlAe03457@web.cs.ndsu.nodak.edu> <02ae01c16891$4c1f4970$2a64a8c0@macadamian.com> <3BEB0A57.3C510C49@mindspring.com> <019401c16959$4e64a8b0$2a64a8c0@macadamian.com> <200111121036.fACAaiv75199@apollo.backplane.com> <3BF05303.FEC66C7A@mindspring.com> <200111122302.fACN2C306926@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: He was writing a virtual memory manger of his own that resembled the Windows version of one he wrote, in order to port software to UNIX (most likely Linux and not FreeBSD, if you were to look at the web site for his company). > Simply using a pre-written file does not really guarentee > anything... after all, you can run out of space on the > filesystem as easily as you can run out of VM, and if you > store other things, like configuration data, in the same > filesystem, you are just as vulnerable to bad programming > in the event of a write() filesystem-full failure as you > are vulnerable to overcomitting the VM system to the point > where it starts killing processes. If you precommit the disk space, then it is impossible for you to run out later. The answer to the "if you store other things" arguement is "precommit *all* contendable resources". I think he wants to avoid failure testing out the ying-yang in his fast path, which is a reasonable thing to want. I know you like overcommit, and trusting the system to do the right thing, but this is not FreeBSD specific code he is writing here, so bending his code around the FreeBSD implementation would be bad. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 18:42:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by hub.freebsd.org (Postfix) with ESMTP id 4778137B405 for ; Mon, 12 Nov 2001 18:42:21 -0800 (PST) Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id B42442B3F; Mon, 12 Nov 2001 19:42:20 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.cos.agilent.com (Postfix) with ESMTP id E6F3930D; Mon, 12 Nov 2001 19:42:19 -0700 (MST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_22672)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id SAA16894; Mon, 12 Nov 2001 18:42:19 -0800 (PST) Message-Id: <200111130242.SAA16894@mina.soco.agilent.com> To: justin@mac.com Cc: freebsd-hackers@freebsd.org Subject: Re: wake up on lan driver support Reply-To: Darryl Okahata In-Reply-To: Your message of "Sun, 11 Nov 2001 17:01:59 PST." Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Mon, 12 Nov 2001 18:42:18 -0800 From: Darryl Okahata Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG justin@mac.com wrote: > I think it requires device driver support because it has to be enabled > (at least, that's what the devices I know about require). No, it does not (at least, not for WOL -- you do need APM in order to use "halt -p" to turn off the system, though). It does not require any special driver support on the machine to be woken up, or from the machine that sends the special wake-on-lan packets. I've been using WOL since FreeBSD 4.2/4.3 (well, for a short while, at least, until I did an impressively stupid boneheaded unmentionable that burned out my motherboard's WOL support ;-(). WOL only requires a few things of the machine to be woken up: 1. The motherboard must support WOL. 2. The LAN card must support WOL. 3. You must have connected the special WOL cable between the LAN card and the motherboard. 4. You must have enabled WOL on the motherboard. That's it. Now, you only have to send the special WOL packets to the system to be woken up (someone's already mentioned the software, in another posting, which also does not require any special driver support). I've used both FreeBSD and Windows to send the packets. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 19: 9:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail29.sdc1.sfba.home.com (femail29.sdc1.sfba.home.com [24.254.60.19]) by hub.freebsd.org (Postfix) with ESMTP id 9FD2237B416 for ; Mon, 12 Nov 2001 19:09:50 -0800 (PST) Received: from lightnin ([65.11.111.111]) by femail29.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011113030945.QGIL26177.femail29.sdc1.sfba.home.com@lightnin> for ; Mon, 12 Nov 2001 19:09:45 -0800 Date: Mon, 12 Nov 2001 19:09:55 -0800 Subject: Re: wake up on lan driver support Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v472) From: justin@mac.com To: freebsd-hackers@FreeBSD.ORG Content-Transfer-Encoding: 7bit In-Reply-To: <200111130242.SAA16894@mina.soco.agilent.com> Message-Id: X-Mailer: Apple Mail (2.472) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG That's cool. I must have recalled incorrectly. Thanks for the clarification. Regards, Justin On Monday, November 12, 2001, at 06:42 , Darryl Okahata wrote: > justin@mac.com wrote: > >> I think it requires device driver support because it has to be enabled >> (at least, that's what the devices I know about require). > > No, it does not (at least, not for WOL -- you do need APM in order > to use "halt -p" to turn off the system, though). It does not require > any special driver support on the machine to be woken up, or from the > machine that sends the special wake-on-lan packets. I've been using WOL > since FreeBSD 4.2/4.3 (well, for a short while, at least, until I did an > impressively stupid boneheaded unmentionable that burned out my > motherboard's WOL support ;-(). > > WOL only requires a few things of the machine to be woken up: > > 1. The motherboard must support WOL. > > 2. The LAN card must support WOL. > > 3. You must have connected the special WOL cable between the LAN card > and the motherboard. > > 4. You must have enabled WOL on the motherboard. > > That's it. > > Now, you only have to send the special WOL packets to the system to > be woken up (someone's already mentioned the software, in another > posting, which also does not require any special driver support). I've > used both FreeBSD and Windows to send the packets. > > -- > Darryl Okahata > darrylo@soco.agilent.com > > DISCLAIMER: this message is the author's personal opinion and does not > constitute the support, opinion, or policy of Agilent Technologies, or > of the little green men that have been following him all day. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > --- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Men are from Earth. | Women are from Earth. | Deal with it. *--------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 21:31:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail5.sh163.net (mail5.sh163.net [202.96.194.136]) by hub.freebsd.org (Postfix) with SMTP id 6980E37B41A for ; Mon, 12 Nov 2001 21:31:00 -0800 (PST) Received: (Rockmail 5083 invoked from network); 13 Nov 2001 05:17:10 -0000 Received: from unknown (HELO sh163.net) ([61.165.121.147]) (envelope-sender ) by mail5.sh163.net (Rockmail) with SMTP for ; 13 Nov 2001 05:17:10 -0000 Message-ID: <4120011121352012840@sh163.net> X-EM-Version: 5, 0, 0, 11 X-EM-Registration: #S1dI500R1AX60C0Rb100 X-Priority: 3 Reply-To: zmzl@sh163.net From: "zhongmaoexpo" Subject: ÖйúʯÓͺÍʯÓÍ»¯¹€É豞¹€ÒµÐ­»á Date: Tue, 13 Nov 2001 13:20:12 +0800 MIME-Version: 1.0 Content-Type: text/html; charset=GB2312_CHARSET To: undisclosed-recipients:; Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG »¶ Ó­ ²Î ¹Û 2001Öйú£šÉϺ££©¹úŒÊʯÓÍŒ°Ê¯»¯ŒŒÊõÉ豞չÀÀ»á ͬÆڟٰ죺2001ÉϺ£¹úŒÊ»¯¹€ŒŒÊõÉ豞չÀÀ»áŒ°2001ÉϺ£¹úŒÊÆøÌ匌ÊõÉ豞չÀÀ»á ÓÉÖйúʯÓͺÍʯÓÍ»¯¹€É豞¹€ÒµÐ­»á¡¢ÉϺ£Êлúе¹€³Ìѧ»áŒ°ÉϺ£ÖÐóչÀÀ·þÎñÓÐ ÏÞ¹«ËŸµÈµ¥Î»¹²Í¬ŸÙ°ìµÄ"2001Öйú£šÉϺ££©¹úŒÊʯÓÍŒ°Ê¯»¯ŒŒÊõÉ豞չÀÀ»á"œ«ÓÚ2001 Äê11ÔÂ29ÈÕ-12ÔÂ1ÈÕÔÚÉϺ£¹âŽó»áÕ¹ÖÐÐÄ¡Ö؟ٰ졣±ŸŽÎÕ¹»áÎüÒýÁËÀŽ×Ô¹úÄÚÍâ250ŒÒ³ §É̲ÎÕ¹£¬»ãŸÛÖÚ¶à¹úÄÚÍâÖøÃû³§É̵Ä×îÐÂŒŒÊõÓëÉ豞¡£²¢ŸÙ°ìÏà¹Ø±šžæ»áŒ°ŒŒÊõœ»Á÷» á¡£ ÎÒÃdzÏÑûÄãœìʱ¹âÁÙÕ¹»á²Î¹Û¡¢œ»Á÷¡£ ÏêÇéÇë²éѯ£ºÉϺ£ÖÐóչÀÀ·þÎñÓÐÏÞ¹«ËŸ ÉϺ£ÊÐäîϪ·251Ū5ºÅÂ¥20F µç »°£º021-54641713 54641743 Ž« Õ棺021-64942305 E-mail:zmzl@sh163.net ²¿·ÖÕ¹ÉÌÃûµ¥ Ó¢¹úººÄ·ÎÖ˹°×ÁŠÊË-ÄŠºàÓÐÏÞ¹«ËŸ µÂ¹úÈü¶àÀû˹ÓÐÏÞ¹«ËŸ Louisiana Chemical Equipment Co L.L.C. Î÷ÃÅ×ÓÕæ¿Õ±ÃѹËõ»úÓÐÏÞ¹«ËŸ °¢Ä·Ë¹×³.ÔÆ·œÚÄÜÉ豞ÓÐÏÞ¹«ËŸ ºŒÖݲŒÀʵÍÎÂÉ豞ÓÐÏÞ¹«ËŸ ÒËÐËÌšÐË»·±£ÓÐÏÞ¹«ËŸ ºŒÖÝ£š»ðŸæ£©Î÷¶·ÃÅÄ€¹€ÒµÓÐÏÞ¹«ËŸ º«¹ú£šÖ꣩ÐÅÓѵç×Ó ÉϺ£¿ÆŽïʵҵÓÐÏÞ¹«ËŸ ÉϺ£Â¡Ç¿Œì²âÒÇÆ÷É豞ÓÐÏÞ¹«ËŸ ÌšÍåÊËÆôÓÐÏÞ¹«ËŸ ÄÏÑô·À±¬Œ¯ÍÅÓÐÏÞ¹«ËŸ ÉýÑôÆóÒµ£š¹É·Ý£©¹«ËŸ ž£ÖÝ·§ÃÅ×ܳ§ ÎÂÖÝÊÐÀûÆÕ×Ô¿ØÉ豞ÓÐÏÞ¹«ËŸ ÉϺ£Ž¬±õÖÆÒ©·ÛËéÉ豞³§ ÄÏ͚ɜœ£Ê¯Ä«É豞ÓÐÏÞ¹«ËŸ ÉϺ£°Í°²Ë®ŽŠÀí¹€³ÌÓÐÏÞ¹«ËŸ ÷ÌØÀÕ-ÍÐÀû¶à³£ÖݺâÆ÷ÓÐÏÞ¹«ËŸ ÀïÆäÀÖóÒ×£šÉϺ££©ÓÐÏÞ¹«ËŸ ÉœÎ÷ÐË°²»¯Ñ§¹€Òµ£šŒ¯ÍÅ£©ÓÐÏÞ¹«ËŸ Î✭ÊйÌÁŠÕ͹ÜÆ÷ÓÐÏÞ¹«ËŸ ÉϺ£Éê·œÈÈÄÜ»úеÉ豞ÓÐÏÞ¹«ËŸ Õ㜭ʡÎÂÁëÊÐÉñ¹âÈÈÄÜÉ豞ÓÐÏÞ¹«ËŸ ÉϺ£·çžùѹËõ»úÓÐÏÞ¹«ËŸ Ììœò±ÃÒµ»úеŒ¯ÍÅÓÐÏÞ¹«ËŸ ÉϺ£¿É¹ó¹Ì̬Àë×ÓµŒÌ幫˟ Äþ²šÌìÉúÃÜ·âŒþÓÐÏÞ¹«ËŸ ŽÈϪºãÁŠÍ¬²œŽøÂÖÓÐÏÞ¹«ËŸ ºŒÖÝÐËÔŽ¹ýÂË»úÓÐÏÞ¹«ËŸ ºÓÄÏ¿ÆԎʯÓÍŒŒÊõ¿ª·¢¹«ËŸ ËÄŽšÑÇÁªÉúÎﻯ¹€ÑП¿Ëù Óª¿ÚÊй܌þ¹€Òµ¹«ËŸ °°ÉœÊпƳÏ×Ô¶¯»¯ÏµÍ³ÓÐÏÞ¹«ËŸ ¹ãÖÝÊв©Ê¿Âü»úµçÓÐÏÞ¹«ËŸ ±±Ÿ©¶«·œÊ¥Â¡Žï¿ÆóÓÐÏÞ¹«ËŸ Î✭ÝÚæÚʯÓÍ»¯¹€³§ ËÕÖÝÅŠÍþ»úеÓÐÏÞ¹«ËŸ ÉϺ£œðÄɲš¿ÆŒŒ·¢Õ¹ÓÐÏÞ¹«ËŸ ÉϺ£·ÉºÍ»úеÓÐÏÞ¹«ËŸ ÉϺ£Äá¿ÉÄá±ÃÒµÓÐÏÞ¹«ËŸ Õ㜭·á»ªÇá»ú·§Ãų§ Éœ¶«Ê¡Î«·»Éúœš»úе³§£šŒ¯ÍÅ£© œ­ËÕÊ¡œ­ÒõÊÐʯÓÍ»¯¹€É豞ÓÐÏÞ¹«ËŸ ÎÂÖÝÊзúËÜÉ豞ÖÆÔ쳧 Õ㜭ÓÓÀû¹€³ÌËÜÁϹܵÀ×ܳ§ ÉîÛÚÊÐÌØ°²µç×ÓÓÐÏÞ¹«ËŸ ²ý»Ý£šÌìœò£©¹úŒÊóÒ×ÓÐÏÞ¹«ËŸ Õ㜭ʡÁÙº£ÊлúÉž³§ ÉϺ£ÁøÓª»úе³§ ÂÞŽïÀ³¿Ë˹·§ÃÅ£šÉϺ££©ÓÐÏÞ¹«ËŸ ±±Ÿ©ŸÓ°²È𺫿ƌŒ·¢Õ¹ÓÐÏÞ¹«ËŸ ºŒÖÝÄÏ·œÌØÖֱó§ ³É¶Œ°²¿ÉÐŵç×ÓÓÐÏÞ¹«ËŸ ¹þ¶û±õÁëÄϹܵÀÁ¬œÓÆ÷ÓÐÏÞ¹«ËŸ ±±Ÿ©Ô󻪿µÒ«ŒŒÊõ·¢Õ¹ÓÐÏÞ¹«ËŸ ÆœºþÊг¿ÈËÈŒÆøÉ豞ÓÐÏÞ¹«ËŸ °²»ÕÖпÆÖÇÄܞߌŒÊõÓÐÏÞÔðÈι«ËŸ Õ㜭ŽºêÍŒ¯ÍÅÓÐÏÞ¹«ËŸ µÂžßœàÇåœàÉ豞ÓÐÏÞ¹«ËŸ ±±Ÿ©žñÁÖ²©ÄÉÉÌóÓÐÏÞ¹«ËŸ Õ㜭ʡÓÀ¿µÊÐÐÂÁúÒDZíÓÐÏÞ¹«ËŸ ÎÞÎýÊÐÇ®ÊÏ¿ÆŒŒ¿ª·¢ÓÐÏÞ¹«ËŸ ³É¶ŒºÀ˹µç×ÓÌœ²âŒŒÊõÓÐÏÞ¹«ËŸ žÛ»ª»ÔÐŹ€³ÌËÜÁÏ£šÖÐÉœ£©ÓÐÏÞ¹«ËŸ ʯŒÒׯÊкàŽïîѹýÂËÆ÷²ÄÓÐÏÞ¹«ËŸ ÉϺ£¹ÚÁú·§ÃÅÓÐÏÞ¹«ËŸ ¹ãÎ÷ÄÏÄþÐÂÄÜ¿ÆŒŒ¿ª·¢ÓÐÏÞ¹«ËŸ ±±Ÿ©º«ŽóÔªÉÌóÓÐÏÞ¹«ËŸ ÎÞÎýÎ÷Ä·À³Ë¹Ê¯ÓÍךÓùÜÖÆÔ칫˟ ÉòÑôÊÐÈ«Íš·§ÃŹ܌þÖÆÔìÓÐÏÞ¹«ËŸ ÀŒÖÝʯÓÍ»¯¹€»úÆ÷×ܳ§ °Í¿ËÐîÄÜÆ÷£šÌìœò£©ÓÐÏÞ¹«ËŸ ÉϺ£¿ÆŽŽÉ«Æ×ÒÇÆ÷ÓÐÏÞ¹«ËŸ Õ㜭ÀÖ¶Š²šÎƹÜÓÐÏÞ¹«ËŸ ÉϺ£¹þµÏÍþ²»ÐâžÖÓÐÏÞ¹«ËŸ ÉϺ£ÊæÈðÆÕʵҵÓÐÏÞ¹«ËŸ ²ŒµÂ³˹Èȹ€ŒŒÊõÓÐÏÞ¹«ËŸ ž»Ë¹Žó¹ø¯ ÃÀ¹úÀïÆæ¹€Ÿß¹«ËŸ À׵ϣšÖйú£©ÓÐÏÞ¹«ËŸ Õ㜭̚ÖÝŽóÑóҺѹÕ͹ÜÉ豞ÖÆÔì×ܳ§ ÉϺ£·îÌ©µç×ÓµçÆ÷ÔªŒþ³§ÓÐÏÞ¹«ËŸ ʯÓÍŽóѧ¿ÂÁÖÈð¶û¿ÆŒŒÓÐÏÞÔðÈι«ËŸ Äþ²šÊÐÓµçÆ÷¹«ËŸ Õ㜭ÓÀÒ»·§Ãų§ œ­ËÕ»ªÑôœðÊô¹ÜŒþÓÐÏÞ¹«ËŸ ÉϺ£Åµ²©»úеÉ豞ÓÐÏÞ¹«ËŸ ÌìœòÊÐÈðµÂÂݞ˱ÃÖÆÔ쌌ÊõÓÐÏÞ¹«ËŸ œ­ÒõÊÐœ­ÄÏžßѹ¹ÜŒþ³§ ÉϺ£èªÍþ»úµçÉ豞ÓÐÏÞ¹«ËŸ Î÷°²¶«·œžÖÌú³§ ÀÈ·»¿ª·¢Çø¹ÜµÀÈË»úеÉ豞ÓÐÏÞ¹«ËŸ ÎýÉœÊÐÐÂÒµ·À±¬µçÆøÓÐÏÞ¹«ËŸ Íþº£»¯¹€Æ÷еÓÐÏÞ¹«ËŸ ÉϺ£Ò×Ì©»¯¹€É豞ÖÆÔìÓÐÏÞ¹«ËŸ ÖÐÍâºÏ×Ê»ÍÊ¢¹ÜÒµÓÐÏÞ¹«ËŸÉϺ£°ì ÉϺ£ÖÐÒâʯÓÍÉ豞ÖÆÔìÓÐÏÞ¹«ËŸ ÉϺ£°×º×»ªÐÂÀö»ªÌØÊâžÖÖÆÆ·ÓÐÏÞ¹« œ­ÒõÊÐÆø»¯»úе³§ ÀŒÖÝʯÓÍ»úеÑП¿Ëù ÉϺ£Ÿ«Î¢·ÛÈÜ»úеÉ豞ÓÐÏÞ¹«ËŸ ÉϺ£Žó¡»úÆ÷³§ ±±Ÿ©žñÈðÍض¯ÁŠÉ豞ÓÐÏÞ¹«ËŸ ÉϺ£œàÁع€Ã³ÓÐÏÞ¹«ËŸ Öйú±±·œ¹€ÒµŒ¯ÍŹ«ËŸ ¹þ¶û±õËĺ£Êý¿Ø¿ÆŒŒ¹É·ÝÓÐÏÞ¹«ËŸ ¹úÓªŸ®žÔÉœÒÇ±í³§ ¹óÖÝ¿­ÐÇÒºÁŠŽ«¶¯»úеÓÐÏÞ¹«ËŸ ÄÏÑôʯÓÍ»úе³§ ÉœÎ÷ÓÀŒÃµç»ú³§ ¹ã¶«ÓîÃ÷¿ÆŒŒÓÐÏÞ¹«ËŸ ÕŌҞÛÊж«ºœµçÈȵçÆ÷³§ ÉϺ£ŒÎ¶Ù»·±£¿ÆŒŒÓÐÏÞ¹«ËŸ ÉϺ£º£Ë÷ÒÇÆ÷ÒDZíÓÐÏÞ¹«ËŸ Éœ¶«Ê¡À³ÖÝÊаÔÁŠÊ¯ÓÍ»úеÓÐÏÞ¹«ËŸ ÉϺ£ŒÑ÷ë±Ã·§ÓÐÏÞ¹«ËŸ ÉϺ£ÄÏ»ª»»ÈÈÆ÷ÖÆÔìÓÐÏÞ¹«ËŸ œ­ÒõÊÐʯÓÍ»úе³§ Ê€ÀûʯÓ͹ÜÀíŸÖ¶¯ÁŠ»úе³§ ÉϺ£ÉгŒ¿ÆŒŒÓÐÏÞ¹«ËŸ ÕŌҞÛÊлªêÉŸ»»¯É豞ÓÐÏÞ¹«ËŸ ÉϺ£º£Ì©žÖ¹ÜÓÐÏÞ¹«ËŸ Ö麣Êк£·òʵҵ·¢Õ¹ÓÐÏÞ¹«ËŸ ïÃûʯ»¯»úе³§ ÎýÉœÊл·Óî×Ô¶¯»¯ÒDZíÓÐÏÞ¹«ËŸ ºÏ·ÊÀŒ²©µçÁŠ»úŸßŒŒÊõÓÐÏÞÔðÈι«ËŸ ŽóÇìʯÓ͹ÜÀíŸÖµÚ¶þ»úе³§ ÉϺ£ÑÇÌ«ŒÆËã»úÐÅϢϵͳÓÐÏÞ¹«ËŸ Î÷°²¶š»ªµç×ÓÓÐÏÞÔðÈι«ËŸ ±±Ÿ©ÍþÓ¢ÖÇÍš¿ÆŒŒÓÐÏÞ¹«ËŸ ŒÃÄÏÊÔœðŒ¯ÍÅÓÐÏÞ¹«ËŸ ŒÃÄÏÊÔÑé»ú³§ ÖйúºœÌì¿ÆŒŒŒ¯ÍŹ«ËŸËÄÔºËÄʮһËù ÉϺ£¹€Òµ×Ô¶¯»¯ÒDZíÑП¿Ëù ¿šÂÞ¿ËÃܷ⌌ÊõÓÐÏÞ¹«ËŸ ¹þ¶û±õÐŲý·Àž¯·§ÃÅÖÆÔìÓÐÏÞ¹«ËŸ ÉϺ£»·ÌìʵҵÓÐÏÞ¹«ËŸ ¡¶µÍÎÂÓëÌØÆø¡· Öйú²»ÐâžÖÊÐÔÓÖŸÉç ÑÌÌšÀŒµÂÍøÂçÓÐÏÞÔðÈι«ËŸ »¯¹€É豞Óë¹ÜµÀ Öйú»¯¹€ÐÅÏ¢Íø ž»ÑôÊÐÊ¢Žó»úµçÖÆÔìÓÐÏÞ¹«ËŸ ÎÂÖÝÊÐÓÀÖÐÓÀ¡»úе³§ ÎÞÎýŽŽÃ÷Ž«¶¯¹€³ÌÓÐÏÞ¹«ËŸ ×Ͳ©Õæ¿ÕÉ豞³§ÓÐÏÞ¹«ËŸ ÎÂÖÝÊж«·œ·Àž¯É豞ÓÐÏÞ¹«ËŸ ÎÂÖÝÌØÒ»·§Ãų§ ÇÇÖηÑЪ¶û¹«ËŸ ³àÊ¿¶Ü/°¬ÖŸ»úе Õ㜭º£ÃÅÊÔѹ±Ã³§ ÄÏŸ©°¢¶û·¢ÒÇÆ÷ÒDZíÓÐÏÞ¹«ËŸ Äþ²šÕýÒ»±Ã·§ÓÐÏÞ¹«ËŸ Õ㜭ʡÓÀÉϲ»ÐâžÖ²úÒµÓÐÏÞ¹«ËŸ ÉϺ£Ê¯ÓÍ»¯¹€É豞ÓÐÏÞ¹«ËŸ Ì«ÆœÑóÌìÈ»ÄÜÔŽ/»ªËŒ°²ÆøÌå¹ËÎÊ Ô¶¶«£šÄþ²š£©ËÜœºœðÊô¹€ÒµÓÐÏÞ¹«ËŸ œ­ËÕºãÍšµçÆøÒDZíÓÐÏÞ¹«ËŸ Æô¶«·À±¬µçÆø ±±Ÿ©ÖÐÓÍÁªºÏÐÅÏ¢ŒŒÊõÓÐÏÞ¹«ËŸ œÝÄÜŽïµçÆøÓÐÏÞ¹«ËŸ ³£ÖÝ×ÛÑÐŒÓÈȯÓÐÏÞ¹«ËŸ ÎÂÖÝ¿ÆÓî·§ÃÅÓÐÏÞ¹«ËŸ ÌìœòÊÐŽóžÛÇøÌ©ŽïʯÓÍÉ豞ÓÐÏÞ¹«ËŸ »ªÄÜÎÞÎýµçÈÈÆ÷²ÄÓÐÏÞ¹«ËŸ ÄÏŸ©°ÂÌصçÆøÓÐÏÞ¹«ËŸ ÁÉÄþÇìÑô»¯Ñ§¹€ÒµŒ¯ÍŹ«ËŸ ÉœÎ÷·çÀ×»úе³§ ÐÂœ®ÁÇÔ­»úÆ÷³§Ì©°²Éä¿×µ¯³§ ¹þ¶û±õœš³É»úе³§ ÉœÎ÷œúÎ÷¹€ÒµŒ¯ÍÅÓÐÏÞÔðÈι«ËŸ ÁÉÄþœõ»ª»úе³§ ºÚÁúœ­»ª°²¹€Òµ£šŒ¯ÍÅ£©¹«ËŸ Î÷°²œüŽú»¯Ñ§ÑП¿Ëù Éœ¶«»úÆ÷³§ ÉÂÎ÷ÓŠÓÃÎïÀí»¯Ñ§ÑП¿Ëù ±øÆ÷¹€ÒµµÚ213ÑП¿Ëù ÉϺ£åŸÑÇÎåœðÖÆÆ·ÓÐÏÞ¹«ËŸ ÖйúÈËÃñœâ·ÅŸüµÚ5719¹€³§·§ÃÅÎ峧 ÎÞÎýÎýÄÜŒÓÈȯÓÐÏÞ¹«ËŸ Õ㜭œðÖÞŒ¯ÍŹɷÝÓÐÏÞ¹«ËŸ ŽóÁ¬ÁŠµÏÁ÷Ìå¿ØÖÆŒŒÊõÓÐÏÞ¹«ËŸ ±±Ÿ©ËÉÌï³Ì¿ÆŒŒÓÐÏÞ¹«ËŸ ³£ÖÝÅÉÀ³ž£ÔöÇ¿ËÜÁÏÓÐÏÞ¹«ËŸ ÉϺ£·Ñ²š×Ô¿ØŒŒÊõÓÐÏÞ¹«ËŸ Õ㜭ÓàÒŠÊÐÐÂŽóËÜÁϹܲÄÓÐÏÞ¹«ËŸ ž»ÑôÊÐÓÀÊ¢ÒDZíÓÐÏÞ¹«ËŸ ÎÂÖÝÊСŽóËÜÒµÓÐÏÞ¹«ËŸ ÉϺ£µÂ±Š»úµçÉ豞ÓÐÏÞ¹«ËŸ ÖÐŽ¬Öع€Œ¯ÍŹ«ËŸÆßÔºÆß°ËÑП¿Ëù ÌìœòÊÐÇ°œøÒÇÆ÷ÒÇ±í³§ ÉîÛÚÊО»ÈÀµç×ÓÓÐÏÞ¹«ËŸ Éœ¶«Ê¡ÁÙÒÊÊа²ž£µç×ÓÓÐÏÞ¹«ËŸ Çൺ¶«¹â¹ø¯ÖÆÔìÓÐÏÞ¹«ËŸ ÉϺ£ÐÇ¿Õ×Ô¶¯»¯ÒDZíÓÐÏÞ¹«ËŸ Öйúʯ»¯³ö°æÉç ÖйúʯÓÍ»¯¹€ÐÅÏ¢Íø Öйú»¯¹€ÔÚ œ­ÄÏŽóѧ·ÖÀë¹€³ÌÑП¿Ëù ³É¶Œ»ªÎ÷»¯¹€¿ÆŒŒ¹É·ÝÓÐÏÞ¹«ËŸ ÉϺ£ÒàÂíÍšÓûúеÓÐÏÞ¹«ËŸ ÉϺ£Ê¯ÓÍ»¯¹€É豞ÓÐÏÞ¹«ËŸÅäŒþ³§ ÉϺ£ÊÐʯÓÍ»¯¹€»úеŒŒÊõÑП¿Ëù ºÓ±±Ê¡Ÿ°ÏØŸ°œòѹÂË»ú³§ £šÆª·ùÓÐÏÞÎŽÄÜŸ¡ÂŒ£© ---------------------------------------------------------------------------- ---------------------------------------------------- ŒŒÊõŒ°±šžæ»á Ö÷ Ì⣺ÐýÁ÷·ÖÀ댌ÊõÔÚʯÓÍ¡¢»¯¹€¹€ÒµÖеÄÓŠÓà ±šžæÈË£ºœÌÓý²¿œ­ÄÏŽóѧ·ÖÀë¹€³ÌÑП¿Ëù Ô¬»ÝÐÂœÌÊÚ Ê± Œä£º2001Äê11ÔÂ29ÈÕÉÏÎç10£º30-11£º30 µØ µã£ºÉϺ£¹âŽó»áÕ¹ÖÐÐÄÎ÷¹ÝÈýºÅ»áÒéÊÒ Ö÷ Ì⣺¹ØÓÚÎÒ¹úʯÓÍ×ê²ÉŒŒÊõ×°±ž·¢Õ¹µÄÈôžÉ¶Ô²ß ±šžæÈË£ºÊ¯ÓÍŽóѧ ÕÅËÃΰœÌÊÚ Ê± Œä£º2001Äê11ÔÂ29ÈÕÏÂÎç13£º30-15£º30 µØ µã£ºÉϺ£¹âŽó»áÕ¹ÖÐÐÄÎ÷¹ÝÈýºÅ»áÒéÊÒ Ö÷ Ì⣺"Ê®Îå"ÆÚŒäʯ»¯¹€ÒµµÄ·¢Õ¹Œ°Æä¶Ô×°±žµÄÐèÇó ±šžæÈË£ºÖйúʯÓÍ»¯¹€Œ¯ÍŹ«ËŸ×Éѯ¹«ËŸ ³ÂÔÊÖÐœÌÊÚŒ¶žß¹€ ʱ Œä£º2001Äê11ÔÂ30ÈÕÉÏÎç10£º00-12£º00 µØ µã£ºÉϺ£¹âŽó»áÕ¹ÖÐÐÄÎ÷¹ÝÈýºÅ»áÒéÊÒ Ö÷ Ì⣺ȫÇò¹€ÒµÆøÌåÊг¡µÄ·¢Õ¹Ç÷Ïò ʱ Œä£º2001Äê11ÔÂ30ÈÕÉÏÎç10£º00-11£º30 µØ µã£ºÉϺ£¹âŽó»áÕ¹ÖÐÐÄÎ÷¹ÝËĺŻáÒéÊÒ ±šžæÈË£ºJohn Racquet ÏÈÉú Ö÷ Ì⣺¹€ÒµŽ¿Ë® ³¬Ž¿Ë®ÖÆÔì ʱ Œä£º2001Äê11ÔÂ30ÈÕÏÂÎç13£º30-15£º00 µØ µã£ºÉϺ£¹âŽó»áÕ¹ÖÐÐÄÎ÷¹ÝËĺŻáÒéÊÒ ±šžæÈË£ººŒÖÝ£š»ðŸæ£©Î÷¶·ÃÅÄ€¹€ÒµÓÐÏÞ¹«ËŸ ÐìÈÙ°²×ÜŸ­Àí ²Î¹ÛµÇŒÇ»ØÖŽ ÐÕ Ãû£º Ö° Îñ£º µ¥Î»Ãû³Æ£º µØ Ö·£º µç »°£º Ž« Õ棺 ÓÊ ±à£º ÒµÎñ·¶Î§£º £šÄã¿ÉÆŸ±Ÿ»ØÖŽÔÚÕ¹¹ÝÈë¿Ú»»È¡×šÒµ¹ÛÖÚÖ€£© To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 12 23:28:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpzilla3.xs4all.nl (smtpzilla3.xs4all.nl [194.109.127.139]) by hub.freebsd.org (Postfix) with ESMTP id 0ED2037B405 for ; Mon, 12 Nov 2001 23:28:57 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtpzilla3.xs4all.nl (8.12.0/8.12.0) with ESMTP id fAD7So1f034947; Tue, 13 Nov 2001 08:28:55 +0100 (CET) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fAD7Smk35675; Tue, 13 Nov 2001 08:28:48 +0100 (CET) (envelope-from wkb) Date: Tue, 13 Nov 2001 08:28:48 +0100 From: Wilko Bulte To: Darryl Okahata Cc: justin@mac.com, freebsd-hackers@FreeBSD.ORG Subject: Re: wake up on lan driver support Message-ID: <20011113082848.A35646@freebie.xs4all.nl> References: <200111130242.SAA16894@mina.soco.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111130242.SAA16894@mina.soco.agilent.com>; from darrylo@soco.agilent.com on Mon, Nov 12, 2001 at 06:42:18PM -0800 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Nov 12, 2001 at 06:42:18PM -0800, Darryl Okahata wrote: > justin@mac.com wrote: > > > I think it requires device driver support because it has to be enabled > > (at least, that's what the devices I know about require). > > No, it does not (at least, not for WOL -- you do need APM in order > to use "halt -p" to turn off the system, though). It does not require > any special driver support on the machine to be woken up, or from the > machine that sends the special wake-on-lan packets. I've been using WOL > since FreeBSD 4.2/4.3 (well, for a short while, at least, until I did an > impressively stupid boneheaded unmentionable that burned out my > motherboard's WOL support ;-(). > > WOL only requires a few things of the machine to be woken up: > > 1. The motherboard must support WOL. > > 2. The LAN card must support WOL. > > 3. You must have connected the special WOL cable between the LAN card > and the motherboard. > > 4. You must have enabled WOL on the motherboard. 5. You must have a power supply that supplies sufficient power on the standby power rail to satisfy the needs of the lan card. Not all PSUs seem to do that. -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 0:19:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id CDD0537B405; Tue, 13 Nov 2001 00:19:49 -0800 (PST) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.32 #1) id 163YnM-0004lV-00; Tue, 13 Nov 2001 10:19:48 +0200 Received: from localhost ([127.0.0.1] helo=pampa.cs.huji.ac.il ident=danny) by pampa.cs.huji.ac.il with esmtp (Exim 3.22 #2) id 163YnM-0005vh-00; Tue, 13 Nov 2001 10:19:48 +0200 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: gx driver MFC Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Nov 2001 10:19:48 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG will th gx driver be MFC'ed any time soon? I have a box and a card sitting around, and was wondering ... thanks, danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 0:22:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 1682837B416 for ; Tue, 13 Nov 2001 00:22:35 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id B1E5081D05; Tue, 13 Nov 2001 02:22:29 -0600 (CST) Date: Tue, 13 Nov 2001 02:22:29 -0600 From: Alfred Perlstein To: Danny Braniss Cc: hackers@FreeBSD.org Subject: Re: gx driver MFC Message-ID: <20011113022229.H13393@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from danny@cs.huji.ac.il on Tue, Nov 13, 2001 at 10:19:48AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Danny Braniss [011113 02:20] wrote: > will th gx driver be MFC'ed any time soon? I have a box and a card > sitting around, and was wondering ... *rolls eyes* Stop wondering, start hacking. It should be nearly trivial to do. :) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 1: 5:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from clueless.redbus.aaisp.net (clueless.redbus.aaisp.net [213.161.73.195]) by hub.freebsd.org (Postfix) with SMTP id 3FA4637B416 for ; Tue, 13 Nov 2001 01:05:30 -0800 (PST) Received: from zebedee.innovision-group.com([217.169.2.11] HELO:garfield.innovisiongroup.com) by clueless.redbus.aaisp.net for freebsd-hackers@FreeBSD.ORG; Tue, 13 Nov 2001 09:05:29 +0000 From: "Jonathan Belson" To: "Vladimir Kushnir" , "Jonathan Belson" Cc: Subject: RE: Screen saver module Date: Tue, 13 Nov 2001 09:10:53 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20011109013949.G73861-100000@kushnir1.kiev.ua> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hi, > > On Thu, 8 Nov 2001, Jonathan Belson wrote: > > > I've written a screen saver module for syscons which uses > > VESA modes (where available) for higher resolutions. > > > > It runs quite happily on my GeForce 2 but I found it > > crashes almost straight away on a Matrox Millenium > > when I try to run it in M_VESA_CG800x600 - I changed > > the code to use 640x480 and it seemed fine. > > > It runs just as happily on Vanta here (FreeBSD-CURRENT). Thanks Jonathan. Cheers for the report. The code in its current state has now been tested on five different graphics cards with no problems...it runs fine on this machine (Matrox G400) at 800x600, so maybe it's just the Millenium that has the problem with M_VESA_CG800x600. > > The source is at http://www.witchspace.com//kix.tgz > > Extract it in /usr/src/sys/modules/syscons, cd to > > 'kix' and type 'make && make install'. > > Would somebody commit it (with some warning message, perhaps)? If they could, that would be great. Cheers, --Jon http://www.witchspace.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 1:32:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id AE10C37B416 for ; Tue, 13 Nov 2001 01:32:40 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1000) id 7426C81D05; Tue, 13 Nov 2001 03:32:35 -0600 (CST) Date: Tue, 13 Nov 2001 01:32:35 -0800 From: Paul Saab To: Alfred Perlstein Cc: Danny Braniss , hackers@FreeBSD.org Subject: Re: gx driver MFC Message-ID: <20011113013235.A35077@elvis.mu.org> References: <20011113022229.H13393@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011113022229.H13393@elvis.mu.org>; from bright@mu.org on Tue, Nov 13, 2001 at 02:22:29AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I believe the driver in -current will compile under stable. Alfred Perlstein (bright@mu.org) wrote: > * Danny Braniss [011113 02:20] wrote: > > will th gx driver be MFC'ed any time soon? I have a box and a card > > sitting around, and was wondering ... > > *rolls eyes* > Stop wondering, start hacking. It should be nearly trivial to do. > > :) > > -- > -Alfred Perlstein [alfred@freebsd.org] > 'Instead of asking why a piece of software is using "1970s technology," > start asking why software is ignoring 30 years of accumulated wisdom.' > http://www.morons.org/rants/gpl-harmful.php3 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Paul Saab Technical Yahoo ps@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 2:16:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bubo.vslib.cz (bubo.vslib.cz [147.230.16.1]) by hub.freebsd.org (Postfix) with ESMTP id D9B1737B405 for ; Tue, 13 Nov 2001 02:16:07 -0800 (PST) Received: from 127.0.0.1 (bubo.vslib.cz [127.0.0.1]) by bubo.vslib.cz (Postfix) with SMTP id AF9F78345 for ; Tue, 13 Nov 2001 11:16:06 +0100 (CET) Received: from A411A (a410a.kolej.vslib.cz [147.230.152.17]) by bubo.vslib.cz (Postfix) with SMTP id 02C7B8036 for ; Tue, 13 Nov 2001 11:16:05 +0100 (CET) Message-ID: <002801c16c2c$36014be0$1198e693@kolej.vslib.cz> From: "Martin Vana" To: Subject: cipe under freebsd Date: Tue, 13 Nov 2001 11:16:08 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, I need to set up a packet tunnel for two win boxes connected to the same localnetwork which is terorized by firewall. Someone recommends me cipe is there something like it for freebsd? How could I tell the two win boxes to send all their traffic to bsdbox? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 2:26:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 4717437B419 for ; Tue, 13 Nov 2001 02:26:16 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 239CD81D05; Tue, 13 Nov 2001 04:26:16 -0600 (CST) Date: Tue, 13 Nov 2001 04:26:16 -0600 From: Alfred Perlstein To: Paul Saab Cc: Danny Braniss , hackers@FreeBSD.org Subject: Re: gx driver MFC Message-ID: <20011113042616.J13393@elvis.mu.org> References: <20011113022229.H13393@elvis.mu.org> <20011113013235.A35077@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011113013235.A35077@elvis.mu.org>; from ps@mu.org on Tue, Nov 13, 2001 at 01:32:35AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Paul Saab [011113 03:32] wrote: > I believe the driver in -current will compile under stable. It requires some minor hacking which I haven't tested, this basically disables the hardware checksum offloading because I'm too tired to figure out the difference at (what the hell time is it anyhow.. AAARGH!!) ohboy.. It also may misbehave if vlan packets arrive, it may even make your dog go bald so no promises. Just take the -current src/sys/modules/gx put it into a -stable in the same location then do the same thing for src/sys/dev/gx/ and apply the following patch. Let me know if it works. --- /usr/src/sys/dev/gx/if_gx.c Wed Oct 24 00:20:45 2001 +++ if_gx.c Tue Nov 13 02:25:30 2001 @@ -349,10 +349,12 @@ ifp->if_snd.ifq_maxlen = GX_TX_RING_CNT - 1; /* see if we can enable hardware checksumming */ +#if 0 /* HAS_IFCAP */ if (gx->gx_vflags & GXF_CSUM) { ifp->if_capabilities = IFCAP_HWCSUM; ifp->if_capenable = ifp->if_capabilities; } +#endif /* figure out transciever type */ if (gx->gx_vflags & GXF_FORCE_TBI || @@ -469,6 +471,7 @@ ctrl |= GX_RXC_LONG_PKT_ENABLE; /* setup receive checksum control */ +#if 0 /* HAS_IFCAP */ if (ifp->if_capenable & IFCAP_RXCSUM) CSR_WRITE_4(gx, GX_RX_CSUM_CONTROL, GX_CSUM_TCP/* | GX_CSUM_IP*/); @@ -476,6 +479,7 @@ /* setup transmit checksum control */ if (ifp->if_capenable & IFCAP_TXCSUM) ifp->if_hwassist = GX_CSUM_FEATURES; +#endif ctrl |= GX_RXC_STRIP_ETHERCRC; /* not on 82542? */ CSR_WRITE_4(gx, GX_RX_CONTROL, ctrl); @@ -958,6 +962,7 @@ error = ifmedia_ioctl(ifp, ifr, &gx->gx_media, command); } break; +#if 0 /* HAS_IFCAP */ case SIOCSIFCAP: mask = ifr->ifr_reqcap ^ ifp->if_capenable; if (mask & IFCAP_HWCSUM) { @@ -969,6 +974,7 @@ gx_init(gx); } break; +#endif default: error = EINVAL; break; @@ -1294,6 +1300,7 @@ #define IP_CSMASK (GX_RXSTAT_IGNORE_CSUM | GX_RXSTAT_HAS_IP_CSUM) #define TCP_CSMASK \ (GX_RXSTAT_IGNORE_CSUM | GX_RXSTAT_HAS_TCP_CSUM | GX_RXERR_TCP_CSUM) +#if 0 /* HAS_IFCAP */ if (ifp->if_capenable & IFCAP_RXCSUM) { #if 0 /* @@ -1313,12 +1320,17 @@ m->m_pkthdr.csum_data = 0xffff; } } +#endif /* * If we received a packet with a vlan tag, pass it * to vlan_input() instead of ether_input(). */ if (staterr & GX_RXSTAT_VLAN_PKT) { +#if 0 + m_freem(m); +#else VLAN_INPUT_TAG(ifp, eh, m, rx->rx_special); +#endif continue; } ether_input(ifp, eh, m); > > Alfred Perlstein (bright@mu.org) wrote: > > * Danny Braniss [011113 02:20] wrote: > > > will th gx driver be MFC'ed any time soon? I have a box and a card > > > sitting around, and was wondering ... > > > > *rolls eyes* > > Stop wondering, start hacking. It should be nearly trivial to do. > > > > :) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 3:38:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 7B54C37B405 for ; Tue, 13 Nov 2001 03:38:15 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.3) id fADBcBw36497; Tue, 13 Nov 2001 12:38:11 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200111131138.fADBcBw36497@freebsd.dk> Subject: Re: VIA 82231 South Bridge In-Reply-To: <200111102338.CAA04062@aaz.links.ru> To: .@babolo.ru Date: Tue, 13 Nov 2001 12:38:11 +0100 (CET) Cc: hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems .@babolo.ru wrote: > > > Are there any planes to support > > > VIA 82231 south bridge > > > for UDMA33/66/100 ? OK, support has been added to -current, MFC will follow later... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 7:13:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 286AB37B405; Tue, 13 Nov 2001 07:13:34 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 13 Nov 2001 15:13:33 +0000 (GMT) Date: Tue, 13 Nov 2001 15:13:29 +0000 From: David Malone To: Eugene Grosbein Cc: stable@freebsd.org, hackers@freebsd.org Subject: Re: kern.vm.kmem.size Message-ID: <20011113151329.A44837@walton.maths.tcd.ie> References: <20011111230817.A2325@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011111230817.A2325@grosbein.pp.ru>; from eugen@grosbein.pp.ru on Sun, Nov 11, 2001 at 11:08:17PM +0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Nov 11, 2001 at 11:08:17PM +0700, Eugene Grosbein wrote: > I'm trying to test and tune speed of freebsd's filesystem in many aspects. > I run recent FreeBSD 4.4-STABLE with new dirprefs code, read tuning(7), > newfs'd my FS, turned softupdates on, have UFS_DIRHASH kernel option. > Also, I've read DIRHASH kernel code source. It seems that efficiency of > DIRHASH greatly depends of kernel memory size (and some experiments > approve this). You should be able to control how much memory is used by dirhash with the vfs.ufs.dirhash_maxmem sysctl. By default it uses up to 2MB and it should be possible to raise it significantly, providing you have enough physical memory. (By default there is about 1GB of kernel address space, so you are unlikely to be running into this limit - I don't think changing kern.vm.kmem.size will help you). Remember - raising it will only help you if your working set of oversized directories is larger that what fits into the memory allocated for dirhash. I'd suggest that you watch how much memory dirhash is using "vmstat -m" and examinign the dirhash line. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 7:17:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id DB3F337B405; Tue, 13 Nov 2001 07:17:51 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 13 Nov 2001 15:17:51 +0000 (GMT) Date: Tue, 13 Nov 2001 15:17:50 +0000 From: David Malone To: Danny Braniss Cc: developers@FreeBSD.org, hackers@FreeBSD.org Subject: Re: gx driver MFC Message-ID: <20011113151750.B44837@walton.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from danny@cs.huji.ac.il on Tue, Nov 13, 2001 at 10:19:48AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 13, 2001 at 10:19:48AM +0200, Danny Braniss wrote: > will th gx driver be MFC'ed any time soon? I have a box and a card > sitting around, and was wondering ... You could use the wx driver (which is in -stable and should work) until the gx driver is merged. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 7:51:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from D00015.dialonly.kemerovo.su (www2.svzserv.kemerovo.su [213.184.65.86]) by hub.freebsd.org (Postfix) with ESMTP id 3FFD637B418; Tue, 13 Nov 2001 07:51:31 -0800 (PST) Received: (from eugen@localhost) by D00015.dialonly.kemerovo.su (8.11.6/8.11.4) id fADFlUT00911; Tue, 13 Nov 2001 22:47:30 +0700 (KRAT) (envelope-from eugen) Date: Tue, 13 Nov 2001 22:47:30 +0700 From: Eugene Grosbein To: David Malone Cc: stable@freebsd.org, hackers@freebsd.org Subject: Re: kern.vm.kmem.size Message-ID: <20011113224730.A864@grosbein.pp.ru> References: <20011111230817.A2325@grosbein.pp.ru> <20011113151329.A44837@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011113151329.A44837@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Tue, Nov 13, 2001 at 03:13:29PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 13, 2001 at 03:13:29PM +0000, David Malone wrote: > > I'm trying to test and tune speed of freebsd's filesystem in many aspects. > > I run recent FreeBSD 4.4-STABLE with new dirprefs code, read tuning(7), > > newfs'd my FS, turned softupdates on, have UFS_DIRHASH kernel option. > > Also, I've read DIRHASH kernel code source. It seems that efficiency of > > DIRHASH greatly depends of kernel memory size (and some experiments > > approve this). > > You should be able to control how much memory is used by dirhash > with the vfs.ufs.dirhash_maxmem sysctl. By default it uses up to > 2MB and it should be possible to raise it significantly, providing > you have enough physical memory. (By default there is about 1GB of > kernel address space, so you are unlikely to be running into this > limit - I don't think changing kern.vm.kmem.size will help you). Are you shure? From LINT: # Tune the kernel malloc area parameters. VM_KMEM_SIZE represents the # minimum, in bytes, and is typically (12*1024*1024) (12MB). # VM_KMEM_SIZE_MAX represents the maximum, typically 200 megabytes. # VM_KMEM_SIZE_SCALE can be set to adjust the auto-tuning factor, which # typically defaults to 4 (kernel malloc area size is physical memory # divided by the scale factor). # options VM_KMEM_SIZE="(10*1024*1024)" options VM_KMEM_SIZE_MAX="(100*1024*1024)" options VM_KMEM_SIZE_SCALE="4" It seems DIRHASH is limited with free space in the kernel malloc area. It even cannot utilize default 2M of vfs.ufs.dirhash_maxmem when I do not increase kern.vm.kmem.size. I think it's because of kernel malloc area exhaustion. However, when I increase kern.vm.kmem.size upto 64M and vfs.ufs.dirhash_maxmem upto 8M, it starts using more than 2M of dirhash memory and speed of my tests greatly improves. So, how can I estimate needed value of kern.vm.kmem.size? Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 9:26:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by hub.freebsd.org (Postfix) with ESMTP id 2046437B418 for ; Tue, 13 Nov 2001 09:26:21 -0800 (PST) Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id 7BE0B2D41; Tue, 13 Nov 2001 10:26:20 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.cos.agilent.com (Postfix) with ESMTP id C8A70187; Tue, 13 Nov 2001 10:26:19 -0700 (MST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_22672)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id JAA21758; Tue, 13 Nov 2001 09:26:19 -0800 (PST) Message-Id: <200111131726.JAA21758@mina.soco.agilent.com> To: Wilko Bulte Cc: justin@mac.com, freebsd-hackers@FreeBSD.ORG Subject: Re: wake up on lan driver support Reply-To: Darryl Okahata In-Reply-To: Your message of "Tue, 13 Nov 2001 08:28:48 +0100." <20011113082848.A35646@freebie.xs4all.nl> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Tue, 13 Nov 2001 09:26:18 -0800 From: Darryl Okahata Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > WOL only requires a few things of the machine to be woken up: > > > > 1. The motherboard must support WOL. > > > > 2. The LAN card must support WOL. > > > > 3. You must have connected the special WOL cable between the LAN card > > and the motherboard. > > > > 4. You must have enabled WOL on the motherboard. > > 5. You must have a power supply that supplies sufficient power on the > standby power rail to satisfy the needs of the lan card. Not all PSUs > seem to do that. Yes, definitely (thanks for the addition!). Many older power supplies cannot supply enough current on the +5VSB rail to support WOL. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 9:45:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 9377E37B41C; Tue, 13 Nov 2001 09:44:44 -0800 (PST) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id fADHiOT78961; Tue, 13 Nov 2001 09:44:24 -0800 (PST) (envelope-from mjacob@feral.com) Date: Tue, 13 Nov 2001 09:44:24 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: David Malone Cc: Danny Braniss , developers@FreeBSD.org, hackers@FreeBSD.org Subject: Re: gx driver MFC In-Reply-To: <20011113151750.B44837@walton.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Not if he requires Cordoba support. On Tue, 13 Nov 2001, David Malone wrote: > On Tue, Nov 13, 2001 at 10:19:48AM +0200, Danny Braniss wrote: > > will th gx driver be MFC'ed any time soon? I have a box and a card > > sitting around, and was wondering ... > > You could use the wx driver (which is in -stable and should work) > until the gx driver is merged. > > David. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 10:58: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout06.sul.t-online.de (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id C4E3837B405 for ; Tue, 13 Nov 2001 10:57:55 -0800 (PST) Received: from fwd03.sul.t-online.de by mailout06.sul.t-online.de with smtp id 163iei-0001Me-0b; Tue, 13 Nov 2001 19:51:32 +0100 Received: from ernie.kts.org (520021727764-0001@[217.80.9.23]) by fmrl03.sul.t-online.com with esmtp id 163ieb-0L4iPIC; Tue, 13 Nov 2001 19:51:25 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id E93D04C95C; Tue, 13 Nov 2001 19:51:24 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id 89B09F9C4; Tue, 13 Nov 2001 19:51:25 +0100 (CET) Subject: Re: wake up on lan driver support In-Reply-To: <200111131726.JAA21758@mina.soco.agilent.com> To: Darryl Okahata Date: Tue, 13 Nov 2001 19:51:25 +0100 (CET) Cc: Wilko Bulte , justin@mac.com, freebsd-hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20011113185125.89B09F9C4@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) X-Sender: 520021727764-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Darryl Okahata wrote: > > > WOL only requires a few things of the machine to be woken up: > > > > > > 1. The motherboard must support WOL. > > > > > > 2. The LAN card must support WOL. > > > > > > 3. You must have connected the special WOL cable between the LAN card > > > and the motherboard. > > > > > > 4. You must have enabled WOL on the motherboard. > > > > 5. You must have a power supply that supplies sufficient power on the > > standby power rail to satisfy the needs of the lan card. Not all PSUs > > seem to do that. > > Yes, definitely (thanks for the addition!). Many older power > supplies cannot supply enough current on the +5VSB rail to support WOL. 6. The LAN card driver must support waking up of the card and/or the LAN card driver must not disable waking up of the card. I have some experience with an fxp0: LAN card under current: this card has some on-board firmware, press CTRL-S on bootup and configure the card as to (some of the options) what does it wake up. Some months ago it was possible to let the machine fall to sleep and when a packet arrived, it woke up (which was exactly what i wanted) the machine (which is my home workstation under current, which then slept over the day but i was able to wake it up to access it from remote). When this did not function anymore (APM->ACPI && fxp driver changes), i tried to get docs from Intel on the chip but failed completely. This feature seems to be documented for the 3Com chips in their docs, but i found not the time to work on it. There are AFAIK three types of packets which are able to wake up a LAN card, any packet, a "magic packet" as defined by AMD, and a user defined packet. Each method has to be supported and enabled in the driver and having this functionality in FreeBSD would be really GREAT! I hoped i perhaps get this functionality with ACPI "for free" but it still did not materialize ;-) hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 11:50:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [128.29.154.90]) by hub.freebsd.org (Postfix) with ESMTP id 5A1E737B405 for ; Tue, 13 Nov 2001 11:50:46 -0800 (PST) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id fADJoi120787 for ; Tue, 13 Nov 2001 14:50:44 -0500 (EST) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id fADJohs01452 for ; Tue, 13 Nov 2001 14:50:43 -0500 (EST) Received: from dhcp-48-37.mitre.org (128.29.48.37) by mailhub2.mitre.org with SMTP id 8348314; Tue, 13 Nov 2001 14:50:17 -0500 Message-ID: <3BF179CA.14EC4554@mitre.org> Date: Tue, 13 Nov 2001 14:51:38 -0500 From: "PSI, Mike Smith" Organization: The MITRE Corporation X-Mailer: Mozilla 4.76 [en]C-20010313M (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: C++ and ISO sockets Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Have a tricky problem. I am developing code to transfer data over AF_ISO family sockets. Standard stuff, socket, bind, etc. Nothing tricky. Being a good little boy I am using C++ (gpp delivered with OS) for transportability (read make sure everyone else faces the same stupid problems I did). Alas, when it works it works like a champ. But every 2nd, 3rd, execution, the system freezes or crashes (when I've actually gotten feedback it seems to be a page fault in kernel). This happens before I even get to my first line of code (I've put in a "program running" to stdout WITH A FLUSH at the start of my code). The only non-standard library I'm using is -liso. Has anyone ever encountered something like this...don't like user programs crashing the kernel. I hope someone can help because I am really trying to avoid the kernel debugger. I'm convinced it is in the C++ initialization, but why would this only affect subsequent running of the same program? Is there possibly something in -liso that is causing problems? Something that C++ would call on it's own during it's initialization (can't imagine what). I am using FreeBSD 3.2 (no comments please - I've given plenty of "comments" to the powers that be without results). I am currently rewriting it in C to determine if C++ may be the problem. Any clues?? Mike Smith (not THE Mike Smith) mlsmith@mitre.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 11:57: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id EB77837B417 for ; Tue, 13 Nov 2001 11:56:56 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 00E9481D0B; Tue, 13 Nov 2001 13:56:56 -0600 (CST) Date: Tue, 13 Nov 2001 13:56:56 -0600 From: Alfred Perlstein To: "PSI, Mike Smith" Cc: hackers@freebsd.org Subject: Re: C++ and ISO sockets Message-ID: <20011113135656.M13393@elvis.mu.org> References: <3BF179CA.14EC4554@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BF179CA.14EC4554@mitre.org>; from mlsmith@mitre.org on Tue, Nov 13, 2001 at 02:51:38PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * PSI, Mike Smith [011113 13:51] wrote: > Have a tricky problem. I am developing code to transfer data over AF_ISO > family sockets. Standard stuff, socket, bind, etc. Nothing tricky. Being > a good little boy I am using C++ (gpp delivered with OS) for > transportability (read make sure everyone else faces the same stupid > problems I did). [snip] > Any clues?? Not without sample code dude. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 12:15:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [128.29.154.90]) by hub.freebsd.org (Postfix) with ESMTP id 38A1337B41B for ; Tue, 13 Nov 2001 12:15:18 -0800 (PST) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id fADKFC124968 for ; Tue, 13 Nov 2001 15:15:16 -0500 (EST) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id fADKFBs04536 for ; Tue, 13 Nov 2001 15:15:11 -0500 (EST) Received: from dhcp-48-37.mitre.org (128.29.48.37) by mailhub2.mitre.org with SMTP id 8348921; Tue, 13 Nov 2001 15:15:09 -0500 Message-ID: <3BF17F9F.5B9FA@mitre.org> Date: Tue, 13 Nov 2001 15:16:31 -0500 From: "PSI, Mike Smith" Organization: The MITRE Corporation X-Mailer: Mozilla 4.76 [en]C-20010313M (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Mea Culpa on C++ and ISO Sockets Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry - I'm not looking for someone to debug my code (I am actually a fairly experienced C++ programmer on *gasp* SVR4 which means I create errors only God can figure out). I apologize if my earlier request appeared that way (got a few choice comments from some hackers). All I want to know is if anyone else has had problems using C++ (in general) crashing the kernel during subsequent "initialization" of the same program or specifically with AF_ISO family (-liso) sockets. Nothing more than that. Thanks again, Mike Smith (again, not THE Mike Smith) mlsmith@mitre.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 12:46:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 37D5B37B416 for ; Tue, 13 Nov 2001 12:46:26 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fADKjKx03019; Tue, 13 Nov 2001 12:45:25 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200111132045.fADKjKx03019@mass.dis.org> To: "PSI, Mike Smith" Cc: hackers@freebsd.org Subject: Re: Mea Culpa on C++ and ISO Sockets In-Reply-To: Message from "PSI, Mike Smith" of "Tue, 13 Nov 2001 15:16:31 EST." <3BF17F9F.5B9FA@mitre.org> Date: Tue, 13 Nov 2001 12:45:20 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > All I want to know is if anyone else has had problems using C++ (in > general) crashing the kernel during subsequent "initialization" of the > same program or specifically with AF_ISO family (-liso) sockets. Nothing > more than that. I suspect that the ISO socket code is woefully under-tested, and may in fact demonstrate never-really-worked-the-first-time syndrome. > Mike Smith (again, not THE Mike Smith) You're no more or less "Mike Smith" than I am, dude. 8) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 12:56:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id 05A4037B419 for ; Tue, 13 Nov 2001 12:56:29 -0800 (PST) Received: (from bob@localhost) by luke.immure.com (8.11.6/8.11.6) id fADKuSG56197 for freebsd-hackers@freebsd.org; Tue, 13 Nov 2001 14:56:28 -0600 (CST) (envelope-from bob) Date: Tue, 13 Nov 2001 14:56:28 -0600 From: Bob Willcox To: hackers list Subject: Statically linked version of cvs...how to make it? Message-ID: <20011113145627.B13547@luke.immure.com> Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi All, I need to build a statically-linked version of cvs so that I can run it in a jail. I was hoping someone out there could describe the steps necessary to build cvs static on 4.4-stable. Thanks, Bob -- Bob Willcox Boucher's Observation: bob@vieo.com He who blows his own horn always plays the music Austin, TX several octaves higher than originally written. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 13: 4: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by hub.freebsd.org (Postfix) with ESMTP id B274537B417 for ; Tue, 13 Nov 2001 13:04:03 -0800 (PST) Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id 1A5CA1E54; Tue, 13 Nov 2001 14:04:03 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.cos.agilent.com (Postfix) with ESMTP id A2FA4593; Tue, 13 Nov 2001 14:04:02 -0700 (MST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_22672)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id NAA25071; Tue, 13 Nov 2001 13:04:02 -0800 (PST) Message-Id: <200111132104.NAA25071@mina.soco.agilent.com> To: hm@kts.org Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: wake up on lan driver support Reply-To: Darryl Okahata In-Reply-To: Your message of "Tue, 13 Nov 2001 19:51:25 +0100." <20011113185125.89B09F9C4@bert.kts.org> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Tue, 13 Nov 2001 13:04:01 -0800 From: Darryl Okahata Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hm@kts.org (Hellmuth Michaelis) wrote: > 6. The LAN card driver must support waking up of the card and/or the > LAN card driver must not disable waking up of the card. [ I think we're in violent agreement here, and that we're now quibbling over subtle differences in the English language. ] I don't think you need *support* in the driver. What you do need is for the driver/ACPI *bugs* to be fixed (any existing BIOS-configured settings like WOL need to be preserved and not destroyed by the driver). -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 13:16:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 31CA337B405 for ; Tue, 13 Nov 2001 13:16:50 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.6/8.11.6) id fADLGkk33309; Tue, 13 Nov 2001 15:16:46 -0600 (CST) (envelope-from dan) Date: Tue, 13 Nov 2001 15:16:46 -0600 From: Dan Nelson To: Bob Willcox Cc: hackers list Subject: Re: Statically linked version of cvs...how to make it? Message-ID: <20011113211646.GA90270@dan.emsphone.com> References: <20011113145627.B13547@luke.immure.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011113145627.B13547@luke.immure.com> User-Agent: Mutt/1.3.23.2i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Nov 13), Bob Willcox said: > I need to build a statically-linked version of cvs so that I can run > it in a jail. I was hoping someone out there could describe the steps > necessary to build cvs static on 4.4-stable. Add "NOSHARED=YES" to the top of /usr/src/gnu/usr.bin/cvs/Makefile , make obj && make depend && make && make install. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 13:29:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id 0C9C637B41A for ; Tue, 13 Nov 2001 13:29:10 -0800 (PST) Received: (from bob@localhost) by luke.immure.com (8.11.6/8.11.6) id fADLT8X60404; Tue, 13 Nov 2001 15:29:08 -0600 (CST) (envelope-from bob) Date: Tue, 13 Nov 2001 15:29:08 -0600 From: Bob Willcox To: Dan Nelson Cc: hackers list Subject: Re: Statically linked version of cvs...how to make it? Message-ID: <20011113152908.A58402@luke.immure.com> Reply-To: Bob Willcox References: <20011113145627.B13547@luke.immure.com> <20011113211646.GA90270@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011113211646.GA90270@dan.emsphone.com>; from dnelson@allantgroup.com on Tue, Nov 13, 2001 at 03:16:46PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks for the reply, Dan. For some reason adding NOSHARED=YES to the Makefile didn't seem to work. I wound up explicitly adding: LDFLAGS+= -static to the Makefile and that did it. This is strange because from the looks of it the bsd.prog.mk file should have done this with NOSHARED=YES. Oh, well, thanks anyway as your reply got me on the track. Bob On Tue, Nov 13, 2001 at 03:16:46PM -0600, Dan Nelson wrote: > In the last episode (Nov 13), Bob Willcox said: > > I need to build a statically-linked version of cvs so that I can run > > it in a jail. I was hoping someone out there could describe the steps > > necessary to build cvs static on 4.4-stable. > > Add "NOSHARED=YES" to the top of /usr/src/gnu/usr.bin/cvs/Makefile , > make obj && make depend && make && make install. > > -- > Dan Nelson > dnelson@allantgroup.com -- Bob Willcox Boucher's Observation: bob@vieo.com He who blows his own horn always plays the music Austin, TX several octaves higher than originally written. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 13:56:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ve6kik.bohica.net (h24-65-50-126.ed.shawcable.net [24.65.50.126]) by hub.freebsd.org (Postfix) with ESMTP id ED47937B419; Tue, 13 Nov 2001 13:56:25 -0800 (PST) Received: (from kirk@localhost) by ve6kik.bohica.net (8.11.6/8.11.3) id fADLuO517143; Tue, 13 Nov 2001 14:56:24 -0700 (MST) (envelope-from kirk) From: Kirk Davis Message-Id: <200111132156.fADLuO517143@ve6kik.bohica.net> Subject: porting OpenSSH to 2.2.8 To: hackers@freebsd.org, freebsd-security@freebsd.org Date: Tue, 13 Nov 2001 14:56:24 -0700 (MST) X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have a number of older FreeBSD boxes (running 2.2.8-STABLE) and I am not able to upgrade beyond 2.2.8 due to some custom software. Has anyone managed to get a newer version of OpenSSH running on a 2.2.8 box? I'm not a C programer but I have ported some programs in the past. I'm not having a lot of luck and was hoping that someone out there had already invented the wheel. --- Kirk kirk@bohica.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 14: 0:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 8E9F337B425 for ; Tue, 13 Nov 2001 14:00:43 -0800 (PST) Received: from fledge.pr.watson.org (ak82hjs7hex92j@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with ESMTP id fADM0OB54479; Tue, 13 Nov 2001 17:00:25 -0500 (EST) (envelope-from rwatson@FreeBSD.org) Date: Tue, 13 Nov 2001 17:00:24 -0500 (EST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Makoto Matsushita Cc: hackers@FreeBSD.org Subject: RE: FreeBSD on vmware In-Reply-To: <20011113001244H.matusita@jp.FreeBSD.org> Message-ID: <20011113165944.G52323-100000@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've had -STABLE run fine, but of late have had a lot of trouble with -current. Userland processes during the boot sequence seem to spend a lot of time just spinning -- it's not clear to me what the cause is, and I haven't had time to debug. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Tue, 13 Nov 2001, Makoto Matsushita wrote: > > raff> Yes, I am running FreeBSD 4.3 in a win2k vmware will everything > raff> working including the network (to outside world). No special > raff> configurations were required other than the obvious. > > FreeBSD 5-current guest also works fine here (W2k host). I'm happy > with ports/emulators/vmware-tools :-) > > -- - > Makoto `MAR' Matsushita > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 14: 6: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id EFE9C37B416 for ; Tue, 13 Nov 2001 14:05:58 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id fADM5kj72005; Tue, 13 Nov 2001 14:05:46 -0800 (PST) (envelope-from obrien) Date: Tue, 13 Nov 2001 14:05:46 -0800 From: "David O'Brien" To: "Koster, K.J." , freebsd-hackers@FreeBSD.ORG Subject: Re: Please commit this port: ports/31188: New port: www/orion-cur rent Message-ID: <20011113140546.A71967@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <59063B5B4D98D311BC0D0001FA7E452205FDA09B@l04.research.kpn.com> <20011112161636.A54135@coffee.q9media.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011112161636.A54135@coffee.q9media.com>; from mike@FreeBSD.ORG on Mon, Nov 12, 2001 at 04:16:36PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Nov 12, 2001 at 04:16:36PM -0500, Mike Barcroft wrote: > Koster, K.J. writes: > > I am fully aware that -hackers is not the right forum for this discussion, > > and I apologise for the noise. I tried the appropriate mailing lists first > > and got ignored. You are the second person to respond to two mails to > > -ports, one to -java and one to -hackers. > > > > I'm open to other ideas on how to get this port committed. > > The best advice I can give is to just be patient. Or to request to become a port committer. :-) -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 14: 8: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 1836437B416 for ; Tue, 13 Nov 2001 14:08:01 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id CE59981D0A; Tue, 13 Nov 2001 16:07:55 -0600 (CST) Date: Tue, 13 Nov 2001 16:07:55 -0600 From: Alfred Perlstein To: Kirk Davis Cc: hackers@freebsd.org Subject: Re: porting OpenSSH to 2.2.8 Message-ID: <20011113160755.O13393@elvis.mu.org> References: <200111132156.fADLuO517143@ve6kik.bohica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111132156.fADLuO517143@ve6kik.bohica.net>; from kirk@bohica.net on Tue, Nov 13, 2001 at 02:56:24PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Kirk Davis [011113 15:58] wrote: > Hi, > I have a number of older FreeBSD boxes (running 2.2.8-STABLE) and > I am not able to upgrade beyond 2.2.8 due to some custom software. > > Has anyone managed to get a newer version of OpenSSH running on > a 2.2.8 box? I'm not a C programer but I have ported some programs in > the past. I'm not having a lot of luck and was hoping that someone out > there had already invented the wheel. Please don't cross post! I did a bunch of work trying to get it working in the ports tree, but that was months and months ago. Have you tried the port? Have you tried the "portable" version of openssh? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 14:25:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id A4E3737B416 for ; Tue, 13 Nov 2001 14:25:46 -0800 (PST) Received: from dialup-209.245.141.251.dial1.sanjose1.level3.net ([209.245.141.251] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 163lzy-0005qO-00; Tue, 13 Nov 2001 14:25:42 -0800 Message-ID: <3BF19E14.C6105E35@mindspring.com> Date: Tue, 13 Nov 2001 14:26:28 -0800 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "PSI, Mike Smith" Cc: hackers@freebsd.org Subject: Re: C++ and ISO sockets References: <3BF179CA.14EC4554@mitre.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "PSI, Mike Smith" wrote: > I am using FreeBSD 3.2 (no comments please - I've given plenty of > "comments" to the powers that be without results). I am currently > rewriting it in C to determine if C++ may be the problem. > > Any clues?? The GCC in FreeBSD 3.2 does not support per thread exception stacks; this is most likely your problem. Jeremy Allison (of SAMBA) may still have a copy of the patch that he and I did to fix this for that version of C++. Alternately, you will need to install the latest version of GCC, in particular, to get the crt0.o stuff that does the per thread exception stack registration. Note that if you do this, you will need to work to add the patchs to the installed new C++ header files if you are using BSD .mk files to build your code, since it overrides the paths with the system paths (this is abug in FreeBSD's .mk file system) if DESTDIR is set. This is required to support RTTI, among other things needed for reasonable exception handling. You will have to hack the compiler definition line in your Makefile to put the explicit path first for the includes and the library paths (ugly; but it works around the FreeBSD .mk file bug). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 14:38: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ve6kik.bohica.net (h24-65-50-126.ed.shawcable.net [24.65.50.126]) by hub.freebsd.org (Postfix) with ESMTP id D67D437B416 for ; Tue, 13 Nov 2001 14:37:57 -0800 (PST) Received: (from kirk@localhost) by ve6kik.bohica.net (8.11.6/8.11.3) id fADMbuO17557; Tue, 13 Nov 2001 15:37:56 -0700 (MST) (envelope-from kirk) From: Kirk Davis Message-Id: <200111132237.fADMbuO17557@ve6kik.bohica.net> Subject: Re: porting OpenSSH to 2.2.8 To: bright@mu.org (Alfred Perlstein) Date: Tue, 13 Nov 2001 15:37:56 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <20011113160755.O13393@elvis.mu.org> from "Alfred Perlstein" at Nov 13, 2001 04:07:55 PM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > * Kirk Davis [011113 15:58] wrote: > > Hi, > > I have a number of older FreeBSD boxes (running 2.2.8-STABLE) and > > I am not able to upgrade beyond 2.2.8 due to some custom software. > > > > Has anyone managed to get a newer version of OpenSSH running on > > a 2.2.8 box? I'm not a C programer but I have ported some programs in > > the past. I'm not having a lot of luck and was hoping that someone out > > there had already invented the wheel. > > Please don't cross post! Sorry about that. I didn't know if it was more a hackers or security thing. > I did a bunch of work trying to get it working in the ports tree, > but that was months and months ago. Have you tried the port? > > Have you tried the "portable" version of openssh? I haven't tried the portable version yet. I started from the source and then after I ran into some problems I tried the port. I took the port from 4.4 and tried it but since the ports moved to the common BSD ports tree... I had more problems. OpenSSH was in the 3.x tree before the move to the common ports but it's only 2.1.1 and still has some known security problems. I'm starting to get the idea it gust might be easier to try and get the other custom software modified to run in 4.4 :-) ---- Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 15:25:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta10.onebox.com (mta10.onebox.com [64.68.76.184]) by hub.freebsd.org (Postfix) with ESMTP id 3A23337B405 for ; Tue, 13 Nov 2001 15:25:36 -0800 (PST) Received: from onebox.com ([10.1.111.7]) by mta10.onebox.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20011113232535.OQZU27419.mta10.onebox.com@onebox.com> for ; Tue, 13 Nov 2001 15:25:35 -0800 Received: from [66.32.40.52] by onebox.com with HTTP; Tue, 13 Nov 2001 15:25:35 -0800 Date: Tue, 13 Nov 2001 15:25:35 -0800 Subject: RE: FreeBSD on vmware From: "Glenn Gombert" To: hackers@FreeBSD.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Message-Id: <20011113232535.OQZU27419.mta10.onebox.com@onebox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I now have 4.3 running under VMware on my laptop and main desktop machine (Asus CVU4X-D) system....I am trying to recompile current on my desktop system now (Current hangs badly on my laptop)....I will try and investigate the cause of this a little later tonight .... -- Glenn Gombert glenngombert@onebox.com - email (513) 587-2643 x2263 - voicemail/fax ---- Robert Watson wrote: > I've had -STABLE run fine, but of late have had a lot of trouble with > -current. Userland processes during the boot sequence seem to spend > a lot > of time just spinning -- it's not clear to me what the cause is, and > I > haven't had time to debug. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > On Tue, 13 Nov 2001, Makoto Matsushita wrote: > > > > > raff> Yes, I am running FreeBSD 4.3 in a win2k vmware will everything > > raff> working including the network (to outside world). No special > > raff> configurations were required other than the obvious. > > > > FreeBSD 5-current guest also works fine here (W2k host). I'm happy > > with ports/emulators/vmware-tools :-) > > > > -- - > > Makoto `MAR' Matsushita > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 15:39:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 0747F37B416; Tue, 13 Nov 2001 15:39:45 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 13 Nov 2001 23:39:44 +0000 (GMT) To: Robert Watson Cc: Makoto Matsushita , hackers@FreeBSD.org Subject: Re: FreeBSD on vmware In-Reply-To: Your message of "Tue, 13 Nov 2001 17:00:24 EST." <20011113165944.G52323-100000@fledge.watson.org> Date: Tue, 13 Nov 2001 23:39:43 +0000 From: Ian Dowse Message-ID: <200111132339.aa29506@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011113165944.G52323-100000@fledge.watson.org>, Robert Watson writ es: >I've had -STABLE run fine, but of late have had a lot of trouble with >-current. Userland processes during the boot sequence seem to spend a lot >of time just spinning -- it's not clear to me what the cause is, and I >haven't had time to debug. Someone mentioned on a list somewhere that vmware takes forever to emulate the cmpxchg instruction, and that using the I386_CPU version of atomic_cmpset_int() helps a lot. I noticed a major vmware slowdown with -current sometime in September, so I tried avoiding the cmpxchg's and things got much faster. Below is the patch I use (using this outside vmware on SMP hardware is a bad idea :-). Ian Index: atomic.h =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/i386/include/atomic.h,v retrieving revision 1.21 diff -u -r1.21 atomic.h --- atomic.h 2001/10/08 20:58:24 1.21 +++ atomic.h 2001/10/09 18:35:25 @@ -111,7 +111,7 @@ * Returns 0 on failure, non-zero on success */ -#if defined(I386_CPU) +#if defined(I386_CPU) || 1 static __inline int atomic_cmpset_int(volatile u_int *dst, u_int exp, u_int src) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 16: 3:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hayai.de (potwin.de [217.115.141.118]) by hub.freebsd.org (Postfix) with ESMTP id AF7E737B418 for ; Tue, 13 Nov 2001 16:03:53 -0800 (PST) Received: (from marco@localhost) by hayai.de (8.11.2/8.11.2) id fAE03kc31269; Wed, 14 Nov 2001 01:03:46 +0100 Date: Wed, 14 Nov 2001 01:03:46 +0100 From: Marco Wertejuk To: Martin Vana Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: cipe under freebsd Message-ID: <20011114010346.A31238@localhost.com> References: <002801c16c2c$36014be0$1198e693@kolej.vslib.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002801c16c2c$36014be0$1198e693@kolej.vslib.cz> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, On Tue, Nov 13, 2001 at 11:16:08AM +0100, Martin Vana wrote: | hi, | I need to set up a packet tunnel for | two win boxes connected to the same | localnetwork which is terorized by | firewall. | Someone recommends me cipe | is there something like it for freebsd? tunneling and ipsec are basically supported within latest freebsd versions (and even before 4.4-release) | How could I tell the two win boxes | to send all their traffic to bsdbox? Although it does not belong to this list, you should enable packet forwarding on your freebsd box (gateway_enable="yes" in rc.conf, see documentation) and then tell your windows pc's to use the freebsd box as default gateway. -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Computer/Internet/Security-Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 16:35:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id 4383B37B416; Tue, 13 Nov 2001 16:35:55 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id fAE0NMR63124; Wed, 14 Nov 2001 00:23:22 GMT (envelope-from nik) Date: Wed, 14 Nov 2001 00:23:22 +0000 From: Nik Clayton To: Mike Smith Cc: "PSI, Mike Smith" , hackers@freebsd.org Subject: Re: Mea Culpa on C++ and ISO Sockets Message-ID: <20011114002322.B94326@clan.nothing-going-on.org> Reply-To: chat@freebsd.org References: <200111132045.fADKjKx03019@mass.dis.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="qcHopEYAB45HaUaB" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111132045.fADKjKx03019@mass.dis.org>; from msmith@freebsd.org on Tue, Nov 13, 2001 at 12:45:20PM -0800 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --qcHopEYAB45HaUaB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [ Note reply-to ] On Tue, Nov 13, 2001 at 12:45:20PM -0800, Mike Smith wrote: > > All I want to know is if anyone else has had problems using C++ (in > > general) crashing the kernel during subsequent "initialization" of the > > same program or specifically with AF_ISO family (-liso) sockets. Nothing > > more than that. >=20 > I suspect that the ISO socket code is woefully under-tested, and may > in fact demonstrate never-really-worked-the-first-time syndrome. >=20 > > Mike Smith (again, not THE Mike Smith) >=20 > You're no more or less "Mike Smith" than I am, dude. 8) In some sense I suspect that we all, in fact, may be Mike Smith. Nik "Mike Smith" Clayton --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --qcHopEYAB45HaUaB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjvxuXoACgkQk6gHZCw343U1sgCcDigiKaczTEuZS/uY4P/jjZuo iJ0AnjnpcMbE/hb/hFXaJ7Zd/blD8Ysy =rUSR -----END PGP SIGNATURE----- --qcHopEYAB45HaUaB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 16:38:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id 264CD37B417; Tue, 13 Nov 2001 16:38:32 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 65BD0786E3; Wed, 14 Nov 2001 11:08:28 +1030 (CST) Date: Wed, 14 Nov 2001 11:08:28 +1030 From: Greg Lehey To: Paul van der Zwan Cc: Mike Smith , sos@freebsd.dk, john_wilson100@excite.com, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: HPT370 RAID or Vinum? Message-ID: <20011114110828.A42750@monorchid.lemis.com> References: <200111112105.fABL54801504@mass.dis.org> <200111112137.fABLbwj09918@trantor.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200111112137.fABLbwj09918@trantor.xs4all.nl> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, 11 November 2001 at 22:37:58 +0100, Paul van der Zwan wrote: > In message <200111112105.fABL54801504@mass.dis.org>, Mike Smith wrote: >>>> These "cheap controllers" don't have any algorithms at all to speak of; >>>> they're just ATA controllers with BIOS code that supposedly understands >>>> striping/mirroring. >>> >>> There is no algorithm to speak of involved with striping, and just >>> a little more in mirroring in the error case, but anyways.. >> >> Unless you've fixed it, the error case handling in mirror mode is busted >> as well. >> >>>> The "algorithms" are in the 'ar' driver, which should really just be a >>>> vinum shim. >>> >>> Well, the way vinum is implemented that wont work unfortunately. >> >> There's no reason that 'ar' and Vinum couldn't be fixed to play together. >> >> Or at least, no technical reason. Indeed. It works. > Well, currently there are some minor glitches. I just installed a > vinum slice on /dev/ar0s1 and unless I do a 'vinum read /dev/ar0s1' > vinum will not find the volumes. This causes the boot of my box ( > -current btw) to fail at the mount of my filesystems. Is there a > way to tell vinum to also look on /dev/ar* for its config?? This may be because ar doesn't have a devstat interface (my assumption). Currently Vinum looks in the devstat structures to find mass storage devices, but this will change when the root file system support gets rewritten (hopefully Real Soon Now). Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 13 18:23:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by hub.freebsd.org (Postfix) with ESMTP id 9354537B405; Tue, 13 Nov 2001 18:23:42 -0800 (PST) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.11.6/8.11.6) id fAE2N3i77869; Wed, 14 Nov 2001 09:23:03 +0700 (KRAT) (envelope-from eugen) Date: Wed, 14 Nov 2001 09:23:03 +0700 From: Eugene Grosbein To: Kirk Davis Cc: hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: porting OpenSSH to 2.2.8 Message-ID: <20011114092303.A77520@svzserv.kemerovo.su> References: <200111132156.fADLuO517143@ve6kik.bohica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111132156.fADLuO517143@ve6kik.bohica.net>; from kirk@bohica.net on Tue, Nov 13, 2001 at 02:56:24PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 13, 2001 at 02:56:24PM -0700, Kirk Davis wrote: > I have a number of older FreeBSD boxes (running 2.2.8-STABLE) and > I am not able to upgrade beyond 2.2.8 due to some custom software. > Has anyone managed to get a newer version of OpenSSH running on > a 2.2.8 box? I'm not a C programer but I have ported some programs in > the past. I'm not having a lot of luck and was hoping that someone out > there had already invented the wheel. I had installed OpenSSH to 2.2.5 a couple of months ago. All that you need is: 1. Only if you do not have perl5 installed. Take distfile and patches from current ports tree for perl5. You can build and install it manually with no problems. 2. Take distfile and patches from current ports tree for openssl. You can build and install it manually with no problems, too. 3. The same with openssh-portable from ports. Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 14 0: 5:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpzilla3.xs4all.nl (smtpzilla3.xs4all.nl [194.109.127.139]) by hub.freebsd.org (Postfix) with ESMTP id 1EEF237B417; Wed, 14 Nov 2001 00:05:31 -0800 (PST) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtpzilla3.xs4all.nl (8.12.0/8.12.0) with ESMTP id fAE85KcO011407; Wed, 14 Nov 2001 09:05:20 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.11.6/8.9.3) with ESMTP id fAE85JT34436; Wed, 14 Nov 2001 09:05:19 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <200111140805.fAE85JT34436@trantor.xs4all.nl> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Greg Lehey Cc: Paul van der Zwan , Mike Smith , sos@freebsd.dk, john_wilson100@excite.com, freebsd-hackers@FreeBSD.org, sos@FreeBSD.org, paulz@trantor.xs4all.nl Subject: Re: HPT370 RAID or Vinum? In-Reply-To: Message from Greg Lehey of "Wed, 14 Nov 2001 11:08:28 +1030." <20011114110828.A42750@monorchid.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Nov 2001 09:05:19 +0100 From: Paul van der Zwan Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011114110828.A42750@monorchid.lemis.com>, Greg Lehey wrote: >On Sunday, 11 November 2001 at 22:37:58 +0100, Paul van der Zwan wrote: >> In message <200111112105.fABL54801504@mass.dis.org>, Mike Smith wrote: >>>>> These "cheap controllers" don't have any algorithms at all to speak of; >>>>> they're just ATA controllers with BIOS code that supposedly understands >>>>> striping/mirroring. >>>> >>>> There is no algorithm to speak of involved with striping, and just >>>> a little more in mirroring in the error case, but anyways.. >>> >>> Unless you've fixed it, the error case handling in mirror mode is busted >>> as well. >>> >>>>> The "algorithms" are in the 'ar' driver, which should really just be a >>>>> vinum shim. >>>> >>>> Well, the way vinum is implemented that wont work unfortunately. >>> >>> There's no reason that 'ar' and Vinum couldn't be fixed to play together. >>> >>> Or at least, no technical reason. > >Indeed. It works. > >> Well, currently there are some minor glitches. I just installed a >> vinum slice on /dev/ar0s1 and unless I do a 'vinum read /dev/ar0s1' >> vinum will not find the volumes. This causes the boot of my box ( >> -current btw) to fail at the mount of my filesystems. Is there a >> way to tell vinum to also look on /dev/ar* for its config?? > >This may be because ar doesn't have a devstat interface (my >assumption). Currently Vinum looks in the devstat structures to find >mass storage devices, but this will change when the root file system >support gets rewritten (hopefully Real Soon Now). Well for the moment I 'fixed' it by marking them as noauto in /etc/fstab and having the following in /etc/rc.local: vinum read /dev/ar0s1 mount /usr/source mount /usr/obj Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 14 7:30:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4559D37B418; Wed, 14 Nov 2001 07:30:33 -0800 (PST) Received: from lanczos.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Nov 2001 15:30:32 +0000 (GMT) Date: Wed, 14 Nov 2001 15:30:31 +0000 From: David Malone To: Eugene Grosbein Cc: stable@freebsd.org, hackers@freebsd.org Subject: Re: kern.vm.kmem.size Message-ID: <20011114153031.A16886@lanczos.maths.tcd.ie> References: <20011111230817.A2325@grosbein.pp.ru> <20011113151329.A44837@walton.maths.tcd.ie> <20011113224730.A864@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011113224730.A864@grosbein.pp.ru>; from eugen@grosbein.pp.ru on Tue, Nov 13, 2001 at 10:47:30PM +0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 13, 2001 at 10:47:30PM +0700, Eugene Grosbein wrote: > > you have enough physical memory. (By default there is about 1GB of > > kernel address space, so you are unlikely to be running into this > > limit - I don't think changing kern.vm.kmem.size will help you). > > Are you shure? From LINT: You're right - it is much smaller (I was thinking of something else). However it is bigger than 12MB on most systems - I think it will turn out to be 1/3 physical memory or 200MB, whichever is less. > It seems DIRHASH is limited with free space in the kernel malloc area. > It even cannot utilize default 2M of vfs.ufs.dirhash_maxmem when I do not > increase kern.vm.kmem.size. > > So, how can I estimate needed value of kern.vm.kmem.size? How much ram do you have in the machine? On a 4.4-RC1 machine with 128MB of ram we don't have any problems getting dirhash to use almost all of it's 2MB: vfs.ufs.dirhash_maxmem: 2097152 vfs.ufs.dirhash_mem: 2085797 This is with the devault value for kern.vm.kmem.size. Maybe you could print the value your system is getting with: echo print vm_kmem_size | gdb -k /kernel /dev/mem David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 14 7:45:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shumai.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id 153AA37B416 for ; Wed, 14 Nov 2001 07:45:10 -0800 (PST) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.6/8.11.6) with ESMTP id fAEFjAB03326 for ; Wed, 14 Nov 2001 10:45:10 -0500 (EST) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Wed, 14 Nov 2001 10:45:10 -0500 (EST) From: Joe Clarke To: freebsd-hackers@freebsd.org Subject: Possible pthread bug Message-ID: <20011114103543.D3241-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been trying to track down some kernel errors I've been seeing on my -stable box for a while now with no luck. Admittedly, I don't know much about the internals of threads. I'm hoping someone can point me in the right direction. I have a few applications that are generating SIGABRTs in uthread_kern.c with the message: Thread has returned from sigreturn or longjmp This is a direct result of sigreturn() failing(?) to set eflags in machdep.c at line 950. I know this because everytime I see the SIGABRT and the uthread_kern message, I also see: sigreturn: eflags = 0x280 Where the eflags value is different each time. Now, if I comment out the return(EINVAL); in sigreturn(), things work. That is, I don't get the crash, but I do get the eflags kernel message. I know this is a terrible fix, but I just don't know where to go from here. It seems to me that what's going on here is a previous thread's context is trying to be restored after returning from a signal. That's failing because eflags can't be set. This doesn't seem like an application bug to me, but I could be wrong. I'm running -stable: FreeBSD shumai.marcuscom.com 4.4-STABLE FreeBSD 4.4-STABLE #0: Wed Nov 14 02:21:53 EST 2001 marcus@shumai.marcuscom.com:/usr/src/sys/compile/SHUMAI i386 and the apps in question are nautilus and balse. However, I've walked through the failing apps, and can't find anything amiss. Core dumps and gdb aren't very helpful. I've asked a similar question on -stable, but only got some comiseration. I'd really appreciate any help or insight someone could give. Thanks. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 14 10:51:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from SRDMAIL.SINP.MSU.RU (bigking.sinp.msu.ru [213.131.9.130]) by hub.freebsd.org (Postfix) with ESMTP id 5E9FD37B416 for ; Wed, 14 Nov 2001 10:51:35 -0800 (PST) Received: from tere.sinp.msu.ru ([213.131.9.140] helo=tere) by SRDMAIL.SINP.MSU.RU with smtp (Exim 3.33 #3) id 16456q-000GDl-00 for freebsd-hackers@freebsd.org; Wed, 14 Nov 2001 21:50:04 +0300 Message-ID: <026401c16d3d$2d528560$8c0983d5@sinp.msu.ru> From: "Dmitry A. Mottl" To: Subject: kernel messages Date: Wed, 14 Nov 2001 21:50:06 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, All I got following error, while I say 'reboot'. Please, help me with description, what's going on Why 'pagein' failed? What is error 22? ---- Nov 14 18:07:00 spectre /kernel: swap_pager: I/O error - pageout failed; blkno 1552,size 16384, error 22 Nov 14 18:08:03 spectre /kernel: swap_pager: I/O error - pagein failed; blkno 336,size 4096, error 22 Nov 14 18:08:03 spectre /kernel: vm_fault: pager read error, pid 707 (sshd) Nov 14 18:08:03 spectre /kernel: swap_pager: I/O error - pagein failed; blkno 760,size 4096, error 22 Nov 14 18:08:03 spectre /kernel: vm_fault: pager read error, pid 707 (sshd) Nov 14 18:08:03 spectre /kernel: pid 707 (sshd), uid 0: exited on signal 11 Nov 14 18:10:47 spectre reboot: rebooted by dima Nov 14 18:10:48 spectre syslogd: exiting on signal 15 ---- Thank you -- best regards, Dmitry Mottl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 14 12:46:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157]) by hub.freebsd.org (Postfix) with ESMTP id 9AA1F37B405 for ; Wed, 14 Nov 2001 12:46:09 -0800 (PST) Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56]) by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fAEKjNS08591 for ; Wed, 14 Nov 2001 15:45:23 -0500 (EST) Received: from zcard00m.ca.nortel.com by zcars04e.ca.nortel.com; Wed, 14 Nov 2001 15:45:57 -0500 Received: from zcard0ka.ca.nortel.com ([47.129.242.162]) by zcard00m.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id WNFSCLRJ; Wed, 14 Nov 2001 15:45:06 -0500 Received: from hcarp00g (hcarp00g.ca.nortel.com [47.196.31.114]) by zcard0ka.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id PX30TGT0; Wed, 14 Nov 2001 15:45:05 -0500 Date: Wed, 14 Nov 2001 15:47:32 -0500 (EST) X-Sybari-Space: 00000000 00000000 00000000 From: "Andrew Atrens" X-X-Sender: atrens@hcarp00g.ca.nortel.com To: hackers@freebsd.org Subject: linux JVMs not handling SEGV well. Message-ID: <20011114152822.G3841-100000@hcarp00g.ca.nortel.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Orig: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG All, I'm using 4.x-stable, linux-base-6.x, and am encountering a lot of turbulence with both Sun's jdk1.3.x HotSpot JVM and IBM's linux jdk1.3.x JVM. I have a buggy 3rdparty java app that occasionally causes a null pointer exception to be thrown. While not fatal for the app (the exception is correctly caught), it's most often fatal for the JVM. The SUN jvm SEGV's ( doesn't correctly catch the SIGNAL ), while the IBM jvm seems to get locked in kernel mode - only responding to SIGKILL and chewing up tons of 'system' cpu time. The common denominator here is that both JITs utilize linux threads. When I use a non-threaded JIT, the problem doesn't occur. The problem is readily reproducible, but I'm not sure how to debug it. I've played with truss and ktrace, but I think it's time to begin thinking about using the kernel debugger. Anyone have suggestions on the best way to proceed ? Andrew. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 14 16:51:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id BAAE537B405 for ; Wed, 14 Nov 2001 16:51:55 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id LAA08804 for ; Thu, 15 Nov 2001 11:51:53 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01KAQD2R8ECGVFJFEC@cim.alcatel.com.au> for freebsd-hackers@freebsd.org; Thu, 15 Nov 2001 11:51:46 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id fAF0pde43424 for freebsd-hackers@freebsd.org; Thu, 15 Nov 2001 11:51:39 +1100 Content-return: prohibited Date: Thu, 15 Nov 2001 11:51:39 +1100 From: Peter Jeremy Subject: opiekeys, opieinfo and opiepasswd permissions To: freebsd-hackers@freebsd.org Message-id: <20011115115139.S94635@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm looking at moving to OPIE and have bumped into a couple of areas which don't seem to be clear: 1) What should the permissions on /etc/opiekeys be? This file isn't created by installworld or mergemaster under -stable, and I can't find anything looking through the -current Makefile's. None of the code in libopie has O_CREAT set. The original OPIE Makefile creates the file during "make install" with mode 0644. 2) Why is opieinfo(1) setuid root in -current? The relevant commitlog entry (src/usr.bin/opieinfo/Makefile v1.7) talks about messing with /etc/opiekeys but opieinfo only reads it. Does this mean opiekeys should be mode 0600? 3) Is there a particular reason why opiepasswd(1) isn't setuid root in -stable? opiepasswd does need to update /etc/opiekeys and so it currently doesn't work in -stable. Is this just a lack of round tuit's for MFC's, or is there some other reason? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 14 17:30:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.viasoft.com.cn (unknown [61.153.1.177]) by hub.freebsd.org (Postfix) with ESMTP id 8481937B417 for ; Wed, 14 Nov 2001 17:30:18 -0800 (PST) Received: from davidwnt (davidwnt.viasoft.com.cn [192.168.1.239]) by mail.viasoft.com.cn (8.9.3/8.9.3) with SMTP id JAA01412 for ; Thu, 15 Nov 2001 09:37:04 +0800 Message-ID: <005a01c16d74$9e0c88a0$ef01a8c0@davidwnt> From: "David Xu" To: Subject: vm_map_protect() Date: Thu, 15 Nov 2001 09:26:56 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In FreeBSD 4.4-stable file /sys/vm/vm_map.c, function vm_map_protect() will leave and have an entry splitted when first pass fails. here is the patch to avoid such issue. %diff -u vm_map.c.orig vm_map.c --- vm_map.c.orig Thu Nov 15 08:27:19 2001 +++ vm_map.c Thu Nov 15 09:08:47 2001 @@ -999,13 +999,14 @@ { vm_map_entry_t current; vm_map_entry_t entry; + int clip_start =3D 0; vm_map_lock(map); VM_MAP_RANGE_CHECK(map, start, end); if (vm_map_lookup_entry(map, start, &entry)) { - vm_map_clip_start(map, entry, start); + clip_start =3D 1; } else { entry =3D entry->next; } @@ -1026,6 +1027,8 @@ } current =3D current->next; } + if (clip_start) + vm_map_clip_start(map, entry, start); /* * Go back and fix up protections. [Note that clipping is not -- David Xu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 14 19:32:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 9D19E37B405; Wed, 14 Nov 2001 19:32:43 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id fAF3VVK75687; Wed, 14 Nov 2001 21:31:31 -0600 (CST) (envelope-from jlemon) Date: Wed, 14 Nov 2001 21:31:31 -0600 From: Jonathan Lemon To: Danny Braniss Cc: developers@FreeBSD.org, hackers@FreeBSD.org Subject: Re: gx driver MFC Message-ID: <20011114213131.C74189@prism.flugsvamp.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just MFC'd it. -- Jonathan On Tue, Nov 13, 2001 at 10:19:48AM +0200, Danny Braniss wrote: > will th gx driver be MFC'ed any time soon? I have a box and a card > sitting around, and was wondering ... > > thanks, > > danny > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 14 21:41:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6D5B737B416 for ; Wed, 14 Nov 2001 21:41:42 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fAF5fbs18850; Wed, 14 Nov 2001 21:41:37 -0800 (PST) (envelope-from dillon) Date: Wed, 14 Nov 2001 21:41:37 -0800 (PST) From: Matthew Dillon Message-Id: <200111150541.fAF5fbs18850@apollo.backplane.com> To: "David Xu" Cc: Subject: Re: vm_map_protect() References: <005a01c16d74$9e0c88a0$ef01a8c0@davidwnt> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :In FreeBSD 4.4-stable file /sys/vm/vm_map.c, function vm_map_protect() :will leave and have an entry splitted when first pass fails. :here is the patch to avoid such issue. Hmm... don't you want to vm_map_simplify_entry() at the end instead of vm_map_clip_start()? -Matt Matthew Dillon :%diff -u vm_map.c.orig vm_map.c :--- vm_map.c.orig Thu Nov 15 08:27:19 2001 :+++ vm_map.c Thu Nov 15 09:08:47 2001 :@@ -999,13 +999,14 @@ : { : vm_map_entry_t current; : vm_map_entry_t entry; :+ int clip_start = 0; : : vm_map_lock(map); : : VM_MAP_RANGE_CHECK(map, start, end); : : if (vm_map_lookup_entry(map, start, &entry)) { :- vm_map_clip_start(map, entry, start); :+ clip_start = 1; : } else { : entry = entry->next; : } :@@ -1026,6 +1027,8 @@ : } : current = current->next; : } :+ if (clip_start) :+ vm_map_clip_start(map, entry, start); : : /* : * Go back and fix up protections. [Note that clipping is not : :-- :David Xu : : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 14 23: 2:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sherline.net (216-203-226-2.customer.algx.net [216.203.226.2]) by hub.freebsd.org (Postfix) with SMTP id 0B97337B417 for ; Wed, 14 Nov 2001 23:02:15 -0800 (PST) Received: (qmail 29927 invoked from network); 15 Nov 2001 07:02:10 -0000 Received: from cx443070-a.vista1.sdca.home.com (HELO cx443070b) (24.4.93.90) by sherline.net with SMTP; 15 Nov 2001 07:02:10 -0000 Message-ID: <002701c16da3$806dc960$a700a8c0@cx443070b> From: "Jeremiah Gowdy" To: , Subject: OT: AMD Mobile CPUs Date: Wed, 14 Nov 2001 23:02:34 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Guys, I hate to make such an OT post, so I'll try to make it short. I'm a FreeBSD admin writing on behalf of owners of the very very flawed Sony Vaio FX210 and FX215 laptops. We're trying to resolve some of the problems with our laptops by replacing the mobile Duron CPU. Basically what we're looking for is a source where we can purchase AMD Athlon and Duron mobile CPUs. (a) Yes, we are sure other Socket A mobile CPUs will work. We have tested a couple including the newest Athlon 4 mobiles. (b) Yes, we've already contacted Sony and AMD. If you know someone involved with laptops, AMD, or any other source that might be able to aquire perhaps 20 mobile cpus, we would really appreciate any contacts you might have. We currently have Mobile Durons with the Spitfire core, which has no PowerNow! support, the source of one of our problems. We have solved every possible issue in making one of the new CPUs work in our laptops. The only problem we are having is trying to aquire them. The tests we've done were all supplied with CPUs from other AMD laptop owners. Thanks for any help you can provide. Please email me directly with your responses, and don't CC the list since this *is* OT. I apologize in advance for the chat/hackers crosspost. We're trying to recover some value from a very recent $1700 investment. And of course my laptop runs FreeBSD. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 14 23:24:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.viasoft.com.cn (unknown [61.153.1.177]) by hub.freebsd.org (Postfix) with ESMTP id BA59837B418 for ; Wed, 14 Nov 2001 23:24:28 -0800 (PST) Received: from davidwnt (davidwnt.viasoft.com.cn [192.168.1.239]) by mail.viasoft.com.cn (8.9.3/8.9.3) with SMTP id PAA02740; Thu, 15 Nov 2001 15:31:12 +0800 Message-ID: <001101c16da6$1834d980$ef01a8c0@davidwnt> From: "David Xu" To: "Matthew Dillon" Cc: References: <005a01c16d74$9e0c88a0$ef01a8c0@davidwnt> <200111150541.fAF5fbs18850@apollo.backplane.com> Subject: Re: vm_map_protect() Date: Thu, 15 Nov 2001 15:21:07 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I like fast code. I want to avoid all object and entry=20 splitting and merging cost. besides, I think the code=20 is still very clear. -- David Xu ----- Original Message -----=20 From: "Matthew Dillon" To: "David Xu" Cc: Sent: Thursday, November 15, 2001 1:41 PM Subject: Re: vm_map_protect() > :In FreeBSD 4.4-stable file /sys/vm/vm_map.c, function = vm_map_protect() > :will leave and have an entry splitted when first pass fails. > :here is the patch to avoid such issue. >=20 > Hmm... don't you want to vm_map_simplify_entry() at the end = instead > of vm_map_clip_start()? >=20 > -Matt > Matthew Dillon=20 > >=20 > :%diff -u vm_map.c.orig vm_map.c > :--- vm_map.c.orig Thu Nov 15 08:27:19 2001 > :+++ vm_map.c Thu Nov 15 09:08:47 2001 > :@@ -999,13 +999,14 @@ > : { > : vm_map_entry_t current; > : vm_map_entry_t entry; > :+ int clip_start =3D 0; > : > : vm_map_lock(map); > : > : VM_MAP_RANGE_CHECK(map, start, end); > : > : if (vm_map_lookup_entry(map, start, &entry)) { > :- vm_map_clip_start(map, entry, start); > :+ clip_start =3D 1; > : } else { > : entry =3D entry->next; > : } > :@@ -1026,6 +1027,8 @@ > : } > : current =3D current->next; > : } > :+ if (clip_start) > :+ vm_map_clip_start(map, entry, start); > : > : /* > : * Go back and fix up protections. [Note that clipping is not > : > :-- > :David Xu > : > : > : > :To Unsubscribe: send mail to majordomo@FreeBSD.org > :with "unsubscribe freebsd-hackers" in the body of the message > : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 3:19:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from excalibur.skynet.be (excalibur.skynet.be [195.238.3.135]) by hub.freebsd.org (Postfix) with ESMTP id C9E6337B416 for ; Thu, 15 Nov 2001 03:19:18 -0800 (PST) Received: from relay.skynet.be (adsl-50999.turboline.skynet.be [217.136.71.55]) by excalibur.skynet.be (8.11.6/8.11.6/Skynet-OUT-2.16) with SMTP id fAFBJ1p29262; Thu, 15 Nov 2001 12:19:06 +0100 (MET) (envelope-from ) Date: Thu, 15 Nov 2001 12:19:06 +0100 (MET) Message-Id: <200111151119.fAFBJ1p29262@excalibur.skynet.be> From: Vande Walle Daniel SUBJECT: M.D. , sise 572 chaussée X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Outlook Express 5.00.2014.211 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_004D_01BE0CA9.BF0CA9F0" Content-Transfer-Encoding: 7bit To: undisclosed-recipients:; Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_004D_01BE0CA9.BF0CA9F0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit V.A. = 445.029.367 et R.C.B. = 551489 ). Mois de juillet 2001 Total = 1.980 F.B. T.V.A.= 416 F.B. Total T.V.A.C. = 2.396 F.B. Vande Walle Daniel Avenue de l’Araucaria , 55 1020 Bruxelles n compte financier = 310.0161610.94 T.V.A. = BE 564.663.526 R.C.B. = 620514 Ainsi fait à Bruxelles , le 31 juillet 2001 Vande Walle Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 3:59:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta11.onebox.com (mta11.onebox.com [64.68.76.121]) by hub.freebsd.org (Postfix) with ESMTP id 0718C37B405 for ; Thu, 15 Nov 2001 03:59:22 -0800 (PST) Received: from onebox.com ([10.1.111.10]) by mta11.onebox.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20011115115921.LISE29441.mta11.onebox.com@onebox.com>; Thu, 15 Nov 2001 03:59:21 -0800 Received: from [165.121.193.174] by onebox.com with HTTP; Thu, 15 Nov 2001 03:59:21 -0800 Date: Thu, 15 Nov 2001 03:59:21 -0800 Subject: Re: FreeBSD on vmware From: "Glenn Gombert" To: Ian Dowse Cc: hackers@FreeBSD.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Message-Id: <20011115115921.LISE29441.mta11.onebox.com@onebox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks for the tip Ian ...this works great! I have applied this patch to my desktop system ...and the FreeBSD Current kernel with this patch applied boots right up now...anyone else running Current under FreeBSD would fine it helpful to do as well.... Glenn G. ---- Ian Dowse wrote: > In message <20011113165944.G52323-100000@fledge.watson.org>, Robert > Watson writ > es: > >I've had -STABLE run fine, but of late have had a lot of trouble with > >-current. Userland processes during the boot sequence seem to spend > a lot > >of time just spinning -- it's not clear to me what the cause is, and > I > >haven't had time to debug. > > Someone mentioned on a list somewhere that vmware takes forever to > emulate the cmpxchg instruction, and that using the I386_CPU version > of atomic_cmpset_int() helps a lot. I noticed a major vmware slowdown > with -current sometime in September, so I tried avoiding the > cmpxchg's and things got much faster. Below is the patch I use > (using this outside vmware on SMP hardware is a bad idea :-). > > Ian > > Index: atomic.h > =================================================================== > RCS file: /dump/FreeBSD-CVS/src/sys/i386/include/atomic.h,v > retrieving revision 1.21 > diff -u -r1.21 atomic.h > --- atomic.h 2001/10/08 20:58:24 1.21 > +++ atomic.h 2001/10/09 18:35:25 > @@ -111,7 +111,7 @@ > * Returns 0 on failure, non-zero on success > */ > > -#if defined(I386_CPU) > +#if defined(I386_CPU) || 1 > static __inline int > atomic_cmpset_int(volatile u_int *dst, u_int exp, u_int src) > { > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 4:16:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cc-gw.1anetworks.net (cc-gw.1anetworks.net [193.243.179.83]) by hub.freebsd.org (Postfix) with SMTP id 3BCF137B41A; Thu, 15 Nov 2001 04:16:50 -0800 (PST) Received: from brian (brian.1anetworks.net [212.36.98.200]) by parma.1anetworks.net (8.9.3+Sun/8.9.3) with SMTP id MAA28522; Thu, 15 Nov 2001 12:16:46 GMT From: "Bri" To: , Subject: problems with 3Com 900TPO network card Date: Thu, 15 Nov 2001 12:35:02 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20011115135826.W25119-100000@sp.gilan.uar.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi I have the 3com card that I listed above and I have a problem with the network card light going off on the hub and the card it self basically crashing for some reason which leaves the machine in an unstable state and then prepares to reboot itself. this happens after 4 days of usage normally all though if you down and up the interface every 2 days you can get 13 days out of the machine. When it crashes it gives a crash dump from the driver which I'll try and take down next time it happens and maybe one of you guys will know why this is happening to me. thanks Bri, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 4:35:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from yellow.csi.cam.ac.uk (yellow.csi.cam.ac.uk [131.111.8.67]) by hub.freebsd.org (Postfix) with ESMTP id 8B14037B416; Thu, 15 Nov 2001 04:35:14 -0800 (PST) Received: from dr263.sel.cam.ac.uk ([131.111.129.153] helo=there ident=dr) by yellow.csi.cam.ac.uk with smtp (Exim 3.22 #1) id 164LjZ-0000sL-00; Thu, 15 Nov 2001 12:35:09 +0000 Content-Type: text/plain; charset="iso-8859-1" From: David Rufino To: freebsd-hackers@freebsd.org Subject: -STABLE NVidia drivers Date: Thu, 15 Nov 2001 12:35:14 +0000 X-Mailer: KMail [version 1.3.1] Cc: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Just thought I would mention my -STABLE NVidia drivers have been working for the past week, as far as 2D and XVideo goes. Available on CVS at http://sourceforge.net/projects/nv-bsd. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 6: 8:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id 0FD1437B416; Thu, 15 Nov 2001 06:08:13 -0800 (PST) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Thu, 15 Nov 2001 15:08:11 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FDA0B0@l04.research.kpn.com> From: "Koster, K.J." To: 'Andrew Atrens' , "FreeBSD Java mailing list (E-mail)" Cc: hackers@FreeBSD.ORG Subject: RE: linux JVMs not handling SEGV well. Date: Thu, 15 Nov 2001 15:08:07 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [ CC'd to freebsd-java, please followup there too ] Dear Andrew, This question is better asked on -java, so I forwarded you question. There are many hardcore JVM hackers on that list. > > I'm using 4.x-stable, linux-base-6.x, and am encountering a lot of > turbulence with both Sun's jdk1.3.x HotSpot JVM and IBM's > linux jdk1.3.x JVM. > Well, considering that technically we don't actually have any Java VM post 1.1.8... :-) > > I have a buggy 3rdparty java app that occasionally causes a > null pointer > exception to be thrown. While not fatal for the app (the exception is > correctly caught), it's most often fatal for the JVM. The SUN > jvm SEGV's ( > doesn't correctly catch the SIGNAL ), while the IBM jvm seems to get > locked in kernel mode - only responding to SIGKILL and > chewing up tons of > 'system' cpu time. The common denominator here is that both > JITs utilize > linux threads. When I use a non-threaded JIT, the problem > doesn't occur. > > The problem is readily reproducible, but I'm not sure how to debug it. > I've played with truss and ktrace, but I think it's time to > begin thinking > about using the kernel debugger. > Could you perhaps provide a simple code sample that allows us to reproduce the problem? Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 7:35:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 48FBA37B405 for ; Thu, 15 Nov 2001 07:35:19 -0800 (PST) Received: (qmail 26895 invoked from network); 15 Nov 2001 15:35:18 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Nov 2001 15:35:18 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20011115115921.LISE29441.mta11.onebox.com@onebox.com> Date: Thu, 15 Nov 2001 07:35:18 -0800 (PST) From: John Baldwin To: Glenn Gombert Subject: Re: FreeBSD on vmware Cc: hackers@FreeBSD.org, Ian Dowse Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15-Nov-01 Glenn Gombert wrote: > > Thanks for the tip Ian ...this works great! I have applied this patch > to my desktop system ...and the FreeBSD Current kernel with this patch > applied boots right up now...anyone else running Current under FreeBSD > would fine it helpful to do as well.... Perhaps we need an 'options VMWARE' that this could be triggered off of. > Glenn G. > > > ---- Ian Dowse wrote: >> In message <20011113165944.G52323-100000@fledge.watson.org>, Robert >> Watson writ >> es: >> >I've had -STABLE run fine, but of late have had a lot of trouble with >> >-current. Userland processes during the boot sequence seem to spend >> a lot >> >of time just spinning -- it's not clear to me what the cause is, and >> I >> >haven't had time to debug. >> >> Someone mentioned on a list somewhere that vmware takes forever to >> emulate the cmpxchg instruction, and that using the I386_CPU version >> of atomic_cmpset_int() helps a lot. I noticed a major vmware slowdown >> with -current sometime in September, so I tried avoiding the >> cmpxchg's and things got much faster. Below is the patch I use >> (using this outside vmware on SMP hardware is a bad idea :-). >> >> Ian >> >> Index: atomic.h >> =================================================================== >> RCS file: /dump/FreeBSD-CVS/src/sys/i386/include/atomic.h,v >> retrieving revision 1.21 >> diff -u -r1.21 atomic.h >> --- atomic.h 2001/10/08 20:58:24 1.21 >> +++ atomic.h 2001/10/09 18:35:25 >> @@ -111,7 +111,7 @@ >> * Returns 0 on failure, non-zero on success >> */ >> >> -#if defined(I386_CPU) >> +#if defined(I386_CPU) || 1 >> static __inline int >> atomic_cmpset_int(volatile u_int *dst, u_int exp, u_int src) >> { >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message >> > > __________________________________________________ > FREE voicemail, email, and fax...all in one place. > Sign Up Now! http://www.onebox.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 8:10:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from spitfire.velocet.net (spitfire.velocet.net [216.138.223.227]) by hub.freebsd.org (Postfix) with ESMTP id 7851B37B41C for ; Thu, 15 Nov 2001 08:09:54 -0800 (PST) Received: from office.tor.velocet.net (trooper.velocet.net [216.138.242.2]) by spitfire.velocet.net (Postfix) with ESMTP id 0B8EB44AAD0; Thu, 15 Nov 2001 16:09:51 +0000 (GMT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.11.4/8.9.3) id fAFG9nI37647; Thu, 15 Nov 2001 11:09:49 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15347.59596.755128.156049@trooper.velocet.net> Date: Thu, 15 Nov 2001 11:09:48 -0500 To: hm@kts.org Cc: Darryl Okahata , Wilko Bulte , justin@mac.com, freebsd-hackers@FreeBSD.ORG Subject: [hackers] Re: wake up on lan driver support In-Reply-To: <20011113185125.89B09F9C4@bert.kts.org> References: <200111131726.JAA21758@mina.soco.agilent.com> <20011113185125.89B09F9C4@bert.kts.org> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "Hellmuth" == Hellmuth Michaelis writes: >> Yes, definitely (thanks for the addition!). Many older power >> supplies cannot supply enough current on the +5VSB rail to support >> WOL. Hellmuth> I have some experience with an fxp0: Ethernet> LAN card under current: this card has some Hellmuth> on-board firmware, press CTRL-S on bootup and configure the Hellmuth> card as to (some of the options) what does it wake up. Hellmuth> Some months ago it was possible to let the machine fall to Hellmuth> sleep and when a packet arrived, it woke up (which was Hellmuth> exactly what i wanted) the machine (which is my home Hellmuth> workstation under current, which then slept over the day but Hellmuth> i was able to wake it up to access it from remote). Hellmuth> When this did not function anymore (APM->ACPI && fxp driver Hellmuth> changes), i tried to get docs from Intel on the chip but Hellmuth> failed completely. My laptop has the fxp chipset onboard (a Fujitsu E6575) appears to work flawlessly with wake-on-lan enabled in the bios. I might add as an aside that FreeBSD running on the Fujitsu E series is very sweet at this point. APM, in particular suspend/unsuspend work perfectly as does DVD and sound support. Only the included modem doesn't appear to work. I should also comment that XFree86-3 doesn't support the display where XFree86-4.1 does. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 8:46: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 81A6B37B405; Thu, 15 Nov 2001 08:46:03 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id fAFGk0n67268; Thu, 15 Nov 2001 11:46:00 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Thu, 15 Nov 2001 11:45:58 -0500 To: John Baldwin , Glenn Gombert From: Garance A Drosihn Subject: Re: FreeBSD on vmware Cc: hackers@FreeBSD.ORG, Ian Dowse Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 7:35 AM -0800 11/15/01, John Baldwin wrote: >On 15-Nov-01 Glenn Gombert wrote: >> >> Thanks for the tip Ian ...this works great! I have applied this patch >> to my desktop system ...and the FreeBSD Current kernel with this patch >> applied boots right up now...anyone else running Current under FreeBSD >> would fine it helpful to do as well.... > >Perhaps we need an 'options VMWARE' that this could be triggered off of. Sounds like a good idea. But call it something like 'VMWARE_GUEST', so it is less likely to be used by someone who wants to *run* vmware on freebsd. (and if we need some other kernel options for running vmware on freebsd, those could be called 'VMWARE_HOST', or something). -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 8:51:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from D00015.dialonly.kemerovo.su (www2.svzserv.kemerovo.su [213.184.65.86]) by hub.freebsd.org (Postfix) with ESMTP id D835C37B41A; Thu, 15 Nov 2001 08:51:17 -0800 (PST) Received: from svzserv.kemerovo.su (localhost.dialonly.kemerovo.su [127.0.0.1]) by D00015.dialonly.kemerovo.su (8.11.6/8.11.4) with ESMTP id fAFGEn600438; Thu, 15 Nov 2001 23:14:49 +0700 (KRAT) (envelope-from eugen@svzserv.kemerovo.su) Message-ID: <3BF3E9F8.38004D42@svzserv.kemerovo.su> Date: Thu, 15 Nov 2001 23:14:48 +0700 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.76 [ru] (X11; U; FreeBSD 4.4-STABLE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: David Malone Cc: Eugene Grosbein , stable@freebsd.org, hackers@freebsd.org Subject: Re: kern.vm.kmem.size References: <20011111230817.A2325@grosbein.pp.ru> <20011113151329.A44837@walton.maths.tcd.ie> <20011113224730.A864@grosbein.pp.ru> <20011114153031.A16886@lanczos.maths.tcd.ie> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > So, how can I estimate needed value of kern.vm.kmem.size? > > How much ram do you have in the machine? On a 4.4-RC1 machine I have 320M here. > with 128MB of ram we don't have any problems getting dirhash > to use almost all of it's 2MB: > > vfs.ufs.dirhash_maxmem: 2097152 > vfs.ufs.dirhash_mem: 2085797 > > This is with the devault value for kern.vm.kmem.size. Maybe > you could print the value your system is getting with: > > echo print vm_kmem_size | gdb -k /kernel /dev/mem You are absolutely right, it's using about 1/3 of RAM here (108875776 when I do not tune kern.vm.kmem.size). Hmm, my test seems to be incorrect somehow. How can I see used amount of kernel malloc area? Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 9: 0:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from green.bikeshed.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8557537B418 for ; Thu, 15 Nov 2001 09:00:05 -0800 (PST) Received: from localhost (green@localhost) by green.bikeshed.org (8.11.4/8.11.1) with ESMTP id fAFH03l69797 for ; Thu, 15 Nov 2001 12:00:04 -0500 (EST) (envelope-from green@green.bikeshed.org) Message-Id: <200111151700.fAFH03l69797@green.bikeshed.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: hackers@FreeBSD.org Subject: removing lockmgr from sys/vm From: Brian Fundakowski Feldman Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Nov 2001 12:00:03 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've taken a few shots at getting lockmgr removed from sys/vm to replace it with much simpler sx lock semantics, and now I'm at a point that I really feel I've done as much as I can to be sure that I'm going about this the right way, and would like feedback from others on what could be wrong. The major obstacle is the very vague set of assurances that vm gives you as to what locks are held when, and what may be okay or not okay to hold. According to WITNESS, however, I've been able to avoid now all warnings except for one that occurs in zalloc() because it locks kernel_map, and another vm_map may already be locked by the process. A second issue is that of deadlocks; I believe I may have removed a deadlock in vm_fault1() which would occur because a shared lock is never actually dropped when trying to upgrade for an exclusive lock on the map. In practice, this may be hard to reproduce unintentionally, but I think that two RFMEM processes could probably do it. Here are my diffs; I'd appreciate any insight into what I may have gotten wrong. Index: vm_fault.c =================================================================== RCS file: /home/freebsd/ncvs/src/sys/vm/vm_fault.c,v retrieving revision 1.126 diff -u -r1.126 vm_fault.c --- vm_fault.c 2001/10/26 00:08:05 1.126 +++ vm_fault.c 2001/11/15 16:42:58 @@ -128,6 +128,8 @@ unlock_map(struct faultstate *fs) { if (fs->lookup_still_valid) { + if (fs->lookup_still_valid == 2) + vm_map_lock_downgrade(fs->map); vm_map_lookup_done(fs->map, fs->entry); fs->lookup_still_valid = FALSE; } @@ -280,7 +282,7 @@ fs.first_pindex, fs.first_pindex + 1); } - fs.lookup_still_valid = TRUE; + fs.lookup_still_valid = 1; if (wired) fault_type = prot; @@ -666,10 +668,10 @@ * grab the lock if we need to */ (fs.lookup_still_valid || - lockmgr(&fs.map->lock, LK_EXCLUSIVE|LK_NOWAIT, (void *)0, curthread) == 0) + vm_map_try_lock(fs.map) == 0) ) { - - fs.lookup_still_valid = 1; + if (fs.lookup_still_valid == 0) + fs.lookup_still_valid = 2; /* * get rid of the unnecessary page */ @@ -778,7 +780,7 @@ unlock_and_deallocate(&fs); return (result); } - fs.lookup_still_valid = TRUE; + fs.lookup_still_valid = 1; if ((retry_object != fs.first_object) || (retry_pindex != fs.first_pindex)) { Index: vm_glue.c =================================================================== RCS file: /home/freebsd/ncvs/src/sys/vm/vm_glue.c,v retrieving revision 1.120 diff -u -r1.120 vm_glue.c --- vm_glue.c 2001/10/10 23:06:54 1.120 +++ vm_glue.c 2001/11/15 16:42:58 @@ -576,9 +576,7 @@ * data structures there is a * possible deadlock. */ - if (lockmgr(&vm->vm_map.lock, - LK_EXCLUSIVE | LK_NOWAIT, - NULL, curthread)) { + if (vm_map_try_lock(&vm->vm_map)) { vmspace_free(vm); PROC_UNLOCK(p); goto nextproc; Index: vm_map.c =================================================================== RCS file: /home/freebsd/ncvs/src/sys/vm/vm_map.c,v retrieving revision 1.211 diff -u -r1.211 vm_map.c --- vm_map.c 2001/10/31 03:06:32 1.211 +++ vm_map.c 2001/11/15 16:42:58 @@ -264,75 +264,63 @@ } void -vm_map_lock(vm_map_t map) +_vm_map_lock(vm_map_t map, const char *file, int line) { vm_map_printf("locking map LK_EXCLUSIVE: %p\n", map); - if (lockmgr(&map->lock, LK_EXCLUSIVE, NULL, curthread) != 0) - panic("vm_map_lock: failed to get lock"); + _sx_xlock(&map->lock, file, line); map->timestamp++; } +int +_vm_map_try_lock(vm_map_t map, const char *file, int line) +{ + vm_map_printf("trying to lock map LK_EXCLUSIVE: %p\n", map); + if (_sx_try_xlock(&map->lock, file, line)) { + map->timestamp++; + return (0); + } + return (EWOULDBLOCK); +} + void -vm_map_unlock(vm_map_t map) +_vm_map_unlock(vm_map_t map, const char *file, int line) { vm_map_printf("locking map LK_RELEASE: %p\n", map); - lockmgr(&(map)->lock, LK_RELEASE, NULL, curthread); + _sx_xunlock(&map->lock, file, line); } void -vm_map_lock_read(vm_map_t map) +_vm_map_lock_read(vm_map_t map, const char *file, int line) { vm_map_printf("locking map LK_SHARED: %p\n", map); - lockmgr(&(map)->lock, LK_SHARED, NULL, curthread); + _sx_slock(&map->lock, file, line); } void -vm_map_unlock_read(vm_map_t map) +_vm_map_unlock_read(vm_map_t map, const char *file, int line) { vm_map_printf("locking map LK_RELEASE: %p\n", map); - lockmgr(&(map)->lock, LK_RELEASE, NULL, curthread); + _sx_sunlock(&map->lock, file, line); } -static __inline__ int -_vm_map_lock_upgrade(vm_map_t map, struct thread *td) { - int error; - - vm_map_printf("locking map LK_EXCLUPGRADE: %p\n", map); - error = lockmgr(&map->lock, LK_EXCLUPGRADE, NULL, td); - if (error == 0) - map->timestamp++; - return error; -} - int -vm_map_lock_upgrade(vm_map_t map) +_vm_map_lock_upgrade(vm_map_t map, const char *file, int line) { - return(_vm_map_lock_upgrade(map, curthread)); + vm_map_printf("locking map LK_EXCLUPGRADE: %p\n", map); + if (_sx_try_upgrade(&map->lock, file, line)) { + map->timestamp++; + return (0); + } + return (EWOULDBLOCK); } void -vm_map_lock_downgrade(vm_map_t map) +_vm_map_lock_downgrade(vm_map_t map, const char *file, int line) { vm_map_printf("locking map LK_DOWNGRADE: %p\n", map); - lockmgr(&map->lock, LK_DOWNGRADE, NULL, curthread); -} - -void -vm_map_set_recursive(vm_map_t map) -{ - mtx_lock((map)->lock.lk_interlock); - map->lock.lk_flags |= LK_CANRECURSE; - mtx_unlock((map)->lock.lk_interlock); + _sx_downgrade(&map->lock, file, line); } -void -vm_map_clear_recursive(vm_map_t map) -{ - mtx_lock((map)->lock.lk_interlock); - map->lock.lk_flags &= ~LK_CANRECURSE; - mtx_unlock((map)->lock.lk_interlock); -} - vm_offset_t vm_map_min(vm_map_t map) { @@ -404,7 +392,7 @@ map->first_free = &map->header; map->hint = &map->header; map->timestamp = 0; - lockinit(&map->lock, PVM, "thrd_sleep", 0, LK_NOPAUSE); + sx_init(&map->lock, "thrd_sleep"); } void @@ -412,7 +400,7 @@ struct vm_map *map; { GIANT_REQUIRED; - lockdestroy(&map->lock); + sx_destroy(&map->lock); } /* @@ -1493,17 +1481,13 @@ eend = entry->end; /* First we need to allow map modifications */ - vm_map_set_recursive(map); - vm_map_lock_downgrade(map); map->timestamp++; rv = vm_fault_user_wire(map, entry->start, entry->end); if (rv) { - + vm_map_lock(map); entry->wired_count--; entry->eflags &= ~MAP_ENTRY_USER_WIRED; - - vm_map_clear_recursive(map); vm_map_unlock(map); /* @@ -1517,8 +1501,14 @@ return rv; } - vm_map_clear_recursive(map); - if (vm_map_lock_upgrade(map)) { + /* + * XXX- This is only okay because we have the + * Giant lock. If the VM system were to be + * reentrant, we'd know that we really can't + * do this. Still, this behavior is no worse + * than the old recursion... + */ + if (vm_map_try_lock(map)) { vm_map_lock(map); if (vm_map_lookup_entry(map, estart, &entry) == FALSE) { @@ -1760,13 +1750,13 @@ entry = entry->next; } - if (vm_map_pmap(map) == kernel_pmap) { - vm_map_lock(map); - } if (rv) { - vm_map_unlock(map); + if (vm_map_pmap(map) != kernel_pmap) + vm_map_unlock_read(map); (void) vm_map_pageable(map, start, failed, TRUE); return (rv); + } else if (vm_map_pmap(map) == kernel_pmap) { + vm_map_lock(map); } /* * An exclusive lock on the map is needed in order to call @@ -1775,6 +1765,7 @@ */ if (vm_map_pmap(map) != kernel_pmap && vm_map_lock_upgrade(map)) { + vm_map_unlock_read(map); vm_map_lock(map); if (vm_map_lookup_entry(map, start, &start_entry) == FALSE) { @@ -2551,8 +2542,10 @@ * might have intended by limiting the stack size. */ if (grow_amount > stack_entry->start - end) { - if (vm_map_lock_upgrade(map)) + if (vm_map_lock_upgrade(map)) { + vm_map_unlock_read(map); goto Retry; + } stack_entry->avail_ssize = stack_entry->start - end; @@ -2582,8 +2575,10 @@ ctob(vm->vm_ssize); } - if (vm_map_lock_upgrade(map)) + if (vm_map_lock_upgrade(map)) { + vm_map_unlock_read(map); goto Retry; + } /* Get the preliminary new entry start value */ addr = stack_entry->start - grow_amount; @@ -2818,8 +2813,10 @@ * object. */ - if (vm_map_lock_upgrade(map)) + if (vm_map_lock_upgrade(map)) { + vm_map_unlock_read(map); goto RetryLookup; + } vm_object_shadow( &entry->object.vm_object, @@ -2843,8 +2840,10 @@ */ if (entry->object.vm_object == NULL && !map->system_map) { - if (vm_map_lock_upgrade(map)) + if (vm_map_lock_upgrade(map)) { + vm_map_unlock_read(map); goto RetryLookup; + } entry->object.vm_object = vm_object_allocate(OBJT_DEFAULT, atop(entry->end - entry->start)); @@ -3082,7 +3081,10 @@ pmap_remove (map->pmap, uaddr, tend); vm_object_pmap_copy_1 (srcobject, oindex, oindex + osize); - vm_map_lock_upgrade(map); + if (vm_map_lock_upgrade(map)) { + vm_map_unlock_read(map); + vm_map_lock(map); + } if (entry == &map->header) { map->first_free = &map->header; Index: vm_map.h =================================================================== RCS file: /home/freebsd/ncvs/src/sys/vm/vm_map.h,v retrieving revision 1.68 diff -u -r1.68 vm_map.h --- vm_map.h 2001/10/31 03:06:32 1.68 +++ vm_map.h 2001/11/15 16:42:58 @@ -71,7 +71,8 @@ #ifndef _VM_MAP_ #define _VM_MAP_ -#include +#include +#include #ifdef MAP_LOCK_DIAGNOSTIC #include @@ -154,7 +155,7 @@ */ struct vm_map { struct vm_map_entry header; /* List of entries */ - struct lock lock; /* Lock for map data */ + struct sx lock; /* Lock for map data */ int nentries; /* Number of entries */ vm_size_t size; /* virtual size */ u_char system_map; /* Am I a system map? */ @@ -215,14 +216,23 @@ } while(0) #endif -void vm_map_lock(vm_map_t map); -void vm_map_unlock(vm_map_t map); -void vm_map_lock_read(vm_map_t map); -void vm_map_unlock_read(vm_map_t map); -int vm_map_lock_upgrade(vm_map_t map); -void vm_map_lock_downgrade(vm_map_t map); -void vm_map_set_recursive(vm_map_t map); -void vm_map_clear_recursive(vm_map_t map); +void _vm_map_lock(vm_map_t map, const char *file, int line); +int _vm_map_try_lock(vm_map_t map, const char *file, int line); +void _vm_map_unlock(vm_map_t map, const char *file, int line); +void _vm_map_lock_read(vm_map_t map, const char *file, int line); +void _vm_map_unlock_read(vm_map_t map, const char *file, int line); +int _vm_map_lock_upgrade(vm_map_t map, const char *file, int line); +void _vm_map_lock_downgrade(vm_map_t map, const char *file, int line); + +#define vm_map_lock(map) _vm_map_lock(map, LOCK_FILE, LOCK_LINE) +#define vm_map_try_lock(map) _vm_map_try_lock(map, LOCK_FILE, LOCK_LINE) +#define vm_map_unlock(map) _vm_map_unlock(map, LOCK_FILE, LOCK_LINE) +#define vm_map_lock_read(map) _vm_map_lock_read(map, LOCK_FILE, LOCK_LINE) +#define vm_map_unlock_read(map) _vm_map_unlock_read(map, LOCK_FILE, LOCK_LINE) +#define vm_map_lock_upgrade(map) _vm_map_lock_upgrade(map, LOCK_FILE, LOCK_LINE) +#define vm_map_lock_downgrade(map) _vm_map_lock_downgrade(map, LOCK_FILE, \ + LOCK_LINE) + vm_offset_t vm_map_min(vm_map_t map); vm_offset_t vm_map_max(vm_map_t map); struct pmap *vm_map_pmap(vm_map_t map); Index: vm_pageout.c =================================================================== RCS file: /home/freebsd/ncvs/src/sys/vm/vm_pageout.c,v retrieving revision 1.185 diff -u -r1.185 vm_pageout.c --- vm_pageout.c 2001/10/21 06:12:06 1.185 +++ vm_pageout.c 2001/11/15 16:42:58 @@ -547,9 +547,8 @@ int nothingwired; GIANT_REQUIRED; - if (lockmgr(&map->lock, LK_EXCLUSIVE | LK_NOWAIT, (void *)0, curthread)) { + if (vm_map_try_lock(map)) return; - } bigobj = NULL; nothingwired = TRUE; Index: vm_zone.c =================================================================== RCS file: /home/freebsd/ncvs/src/sys/vm/vm_zone.c,v retrieving revision 1.48 diff -u -r1.48 vm_zone.c --- vm_zone.c 2001/08/05 03:55:02 1.48 +++ vm_zone.c 2001/11/15 16:42:58 @@ -409,14 +409,14 @@ * map. */ mtx_unlock(&z->zmtx); - if (lockstatus(&kernel_map->lock, NULL)) { - item = (void *) kmem_malloc(kmem_map, nbytes, M_WAITOK); - if (item != NULL) - atomic_add_int(&zone_kmem_pages, z->zalloc); + item = (void *)kmem_alloc(kernel_map, nbytes); + if (item != NULL) { + atomic_add_int(&zone_kern_pages, z->zalloc); } else { - item = (void *) kmem_alloc(kernel_map, nbytes); + item = (void *)kmem_malloc(kmem_map, nbytes, + M_WAITOK); if (item != NULL) - atomic_add_int(&zone_kern_pages, z->zalloc); + atomic_add_int(&zone_kmem_pages, z->zalloc); } if (item != NULL) { bzero(item, nbytes); -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 11:31:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [128.29.154.90]) by hub.freebsd.org (Postfix) with ESMTP id E296437B41A for ; Thu, 15 Nov 2001 11:31:12 -0800 (PST) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id fAFJVBc03582 for ; Thu, 15 Nov 2001 14:31:11 -0500 (EST) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id fAFJVAa27678 for ; Thu, 15 Nov 2001 14:31:10 -0500 (EST) Received: from dhcp-48-37.mitre.org (128.29.48.37) by mailhub2.mitre.org with SMTP id 8378179; Thu, 15 Nov 2001 14:31:08 -0500 Message-ID: <3BF4185B.35A8B872@mitre.org> Date: Thu, 15 Nov 2001 14:32:43 -0500 From: "PSI, Mike Smith" Organization: The MITRE Corporation X-Mailer: Mozilla 4.76 [en]C-20010313M (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: _init execs in middle of code Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone know exactly what _init is? An "nm" of my executable lists: 080486a8 ? _init It is the lowest numeric address (before _start and main) so I would assume it is some sort of program initialization code. But when trying to determine the cause of a kernel freeze (caused by my user app), I found that _init is being "called" after quite a bit of code has been executed. I scanned every library known to man and of course all of my objects. I cannot find any symbol reference to _init anywhere so I can only guess it is set up by the linker. HELP! My kernel freezes (every 2nd/3rd execution of the program) so I can't run the debugger on the kernel. However, the freeze condition is very repeatable (happens what appears to be the same point in the execution WHEN it happens) so if I can figure out what _init is, I may have a chance to solve this. Also if _init isn't supposed to be called during a program running, can anyone give a clue as to what stupid programming error could cause this to happen? Thanks Mike Smith (not THE Mike Smith) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 11:41:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 28EBF37B416 for ; Thu, 15 Nov 2001 11:41:43 -0800 (PST) Received: (qmail 856 invoked from network); 15 Nov 2001 19:41:12 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Nov 2001 19:41:12 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3BF4185B.35A8B872@mitre.org> Date: Thu, 15 Nov 2001 11:41:41 -0800 (PST) From: John Baldwin To: "PSI, Mike Smith" Subject: RE: _init execs in middle of code Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15-Nov-01 PSI, Mike Smith wrote: > Does anyone know exactly what _init is? An "nm" of my executable lists: > > 080486a8 ? _init > > It is the lowest numeric address (before _start and main) so I would > assume it is some sort of program initialization code. But when trying > to determine the cause of a kernel freeze (caused by my user app), I > found that _init is being "called" after quite a bit of code has been > executed. > > I scanned every library known to man and of course all of my objects. I > cannot find any symbol reference to _init anywhere so I can only guess > it is set up by the linker. HELP! My kernel freezes (every 2nd/3rd > execution of the program) so I can't run the debugger on the kernel. > > However, the freeze condition is very repeatable (happens what appears > to be the same point in the execution WHEN it happens) so if I can > figure out what _init is, I may have a chance to solve this. > > Also if _init isn't supposed to be called during a program running, can > anyone give a clue as to what stupid programming error could cause this > to happen? IIRC, _init is when constructors for global variables are called (and _fini is when destructors are called.) It is magic behind the scenes generated by the compiler and linker. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 11:57:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shumai.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id 4DBDA37B422; Thu, 15 Nov 2001 11:56:28 -0800 (PST) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.6/8.11.6) with ESMTP id fAFJuVJ10134; Thu, 15 Nov 2001 14:56:31 -0500 (EST) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Thu, 15 Nov 2001 14:56:31 -0500 (EST) From: Joe Clarke To: Maxim Sobolev Cc: freebsd-ports@FreeBSD.org, , Subject: Re: sigreturn: eflags creash (fixed!) In-Reply-To: <3BF41BE2.BD7D8EAA@FreeBSD.org> Message-ID: <20011115145029.G47613-200000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2136882512-1005854191=:47613" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-2136882512-1005854191=:47613 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 15 Nov 2001, Maxim Sobolev wrote: > Joe Clarke wrote: > > > > Sorry for the wide distribution, but I have sent email to both lists > > regarding this problem in the past. It seems that while doing intensive > > threaded operations in Gnome applications, crashes occur with the > > following kernel message: > > > > sigreturn: eflags 0x280 > > > > And, in .gnomerc-errors: > > > > Fatal error 'Thread has returned from sigreturn or longjump' > > > > The problem as I have found it is with libpng. libpng uses MMX > > optimizations by default on FreeBSD. If you apply the attached patch to > > patch-aa in /usr/ports/graphics/png, the problem goes away. You only need > > to recompile and install libpng. Reinstalling Gnome isn't necessary. It > > seems the MMX optimizations are corrupting eflags, and when a thread tries > > to restore context after a signal, things go really wrong. > > > > The true fix will probably come in analyzing the MMX code in libpng. > > Unfortunately, I don't know enough about x86 assembly to be of much use > > here. Hopefully this will help other experiencing the same problem. > > Very interesting, and weird if true. I'll test this tomorrow. In the > meantime, could some CPU guru confirm or reject theoretical > possibility of MMX user-level code causing problems to the kernel? I learned about this by reading through some of the -hackers archives. One person complained of similar errors trying to get xine to work on FreeBSD. Removing the MMX detection code fixed it. I remembered libpng also used MMX, so I removed the pnggccrd.c source, and voila! Based on core dumps, strace output, and a lot of code surfing, this makes sense to me. Basically, any png-dependent app's thread that runs longer than what ITIMER_PROF is set to gets hit with a SIGPROF. When that happens, things context switch. eflags must have been corrupted by the MMX code, thus sigreturn() bombs out, and causes uthread_kern to die as well. Here's what strace looks like when balsa tries to read a 33 MB mailbox: ... 74202 --- SIGPROF (Profiling timer expired) --- 74202 --- SIGPROF (Profiling timer expired) --- 74202 gettimeofday({1005789324, 257513}, NULL) = 0 74202 sigprocmask(SIG_SETMASK, [], NULL) = 0 74202 sigaltstack({ss_sp=0x811b000, ss_flags=0, ss_size=40960}, NULL) = 0 74202 poll([{fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11, events=POLLIN|POLLPRI}, {fd=13, events=POLLIN}, {fd=12, events=POLLIN}], 6, 0) = 0 74202 sigreturn(0x81f2c64 When this happens, strace politely dies with a bus error. Thanks for testing this, Maxim. Hopefully someone can find the problem and fix it for good. Joe P.S. my original patch sucks I was in a hurry. The one attached is better. > > -Maxim > > --0-2136882512-1005854191=:47613 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="patch-aa.diff" Content-Transfer-Encoding: BASE64 Content-ID: <20011115145631.X47613@shumai.marcuscom.com> Content-Description: Content-Disposition: attachment; filename="patch-aa.diff" LS0tIHBhdGNoLWFhLm9yaWcJVGh1IE5vdiAxNSAxNDo1NTo0MyAyMDAxDQor KysgcGF0Y2gtYWEJVGh1IE5vdiAxNSAxNDo1NTo1NyAyMDAxDQpAQCAtNDMs OCArNDMsOCBAQA0KICANCiAtYWxsOiBsaWJwbmcuYSBwbmd0ZXN0DQogKy5p ZiAoJHtBUkNIfSA9PSAiaTM4NiIpDQotK0NGTEFHUys9LURQTkdfVVNFX1BO R0dDQ1JEDQotK09CSlMrPXBuZ2djY3JkLm8NCisrI0NGTEFHUys9LURQTkdf VVNFX1BOR0dDQ1JEDQorKyNPQkpTKz1wbmdnY2NyZC5vDQogKy5lbmRpZg0K ICsNCiArLlNVRkZJWEVTOiAuYyAuc28gLm8NCkBAIC05MSw1ICs5MSw1IEBA DQogIHBuZ3d0cmFuLm86IHBuZy5oIHBuZ2NvbmYuaA0KICBwbmd3dXRpbC5v OiBwbmcuaCBwbmdjb25mLmgNCiAgcG5ncHJlYWQubzogcG5nLmggcG5nY29u Zi5oDQotK3BuZ2djY3JkLm86IHBuZy5oIHBuZ2NvbmYuaCBwbmdhc21yZC5o DQorKyNwbmdnY2NyZC5vOiBwbmcuaCBwbmdjb25mLmggcG5nYXNtcmQuaA0K ICANCg== --0-2136882512-1005854191=:47613-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 12:17:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 20D1937B427 for ; Thu, 15 Nov 2001 12:16:43 -0800 (PST) Received: from dialup-209.245.139.20.dial1.sanjose1.level3.net ([209.245.139.20] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 164SvT-0001cO-00; Thu, 15 Nov 2001 12:15:56 -0800 Message-ID: <3BF422AC.CE9806E@mindspring.com> Date: Thu, 15 Nov 2001 12:16:44 -0800 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "PSI, Mike Smith" Cc: hackers@freebsd.org Subject: Re: _init execs in middle of code References: <3BF4185B.35A8B872@mitre.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "PSI, Mike Smith" wrote: > > Does anyone know exactly what _init is? An "nm" of my executable lists: > > 080486a8 ? _init > > It is the lowest numeric address (before _start and main) so I would > assume it is some sort of program initialization code. But when trying > to determine the cause of a kernel freeze (caused by my user app), I > found that _init is being "called" after quite a bit of code has been > executed. > > I scanned every library known to man and of course all of my objects. I > cannot find any symbol reference to _init anywhere so I can only guess > it is set up by the linker. HELP! My kernel freezes (every 2nd/3rd > execution of the program) so I can't run the debugger on the kernel. > > However, the freeze condition is very repeatable (happens what appears > to be the same point in the execution WHEN it happens) so if I can > figure out what _init is, I may have a chance to solve this. > > Also if _init isn't supposed to be called during a program running, can > anyone give a clue as to what stupid programming error could cause this > to happen? _init is called by crt0.o. It is used to, among other things, initialize per thread exception stacks and instance statically or globally declared classes, template base classes, and set up pur virtual base classes for use. It also executes anything else in the ".entry" code segment linker set list (which is where this stuff is done). See "dumpobj". If you want to run this in the debugger, then you should set a breakpoint on _main (or just _init), and then single step the machine instructions from there. See the GCC web site for more detailed information. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 12:43: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.macomnet.ru (relay1.macomnet.ru [195.128.64.10]) by hub.freebsd.org (Postfix) with ESMTP id 2487F37B405 for ; Thu, 15 Nov 2001 12:42:59 -0800 (PST) Received: from news1.macomnet.ru (maxim@news1.macomnet.ru [195.128.64.14]) by relay1.macomnet.ru (8.11.3/8.11.3) with ESMTP id fAFKgp7131797 for ; Thu, 15 Nov 2001 23:42:51 +0300 (MSK) Date: Thu, 15 Nov 2001 23:42:50 +0300 (MSK) From: Maxim Konovalov To: hackers@freebsd.org Subject: has 'options LOCKF_DEBUG' ever worked? (w/ patch) (fwd) Message-ID: <20011115233840.T38246-100000@news1.macomnet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [ forward to -hackers because of silence in -current ] ---------- Forwarded message ---------- Date: Thu, 8 Nov 2001 17:35:17 +0300 (MSK) From: Maxim Konovalov To: current@freebsd.org Subject: has 'options LOCKF_DEBUG' ever worked? (w/ patch) Hello, Seems 'options LOCKF_DEBUG' does not work at all. How to repeat: echo 'options LOCKF_DEBUG' >> KERNELCONF, recompile the kernel, install it, reboot, # sysctl -w debug.lockf_debug=1 $ lockf -k /etc/passwd sleep 1 .. and got the panic: Script started on Wed Nov 7 14:03:14 2001 miss# gdb -k /usr/obj/usr/src/sys/MISS/kernel.debug vmcore.4 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 3858432 initial pcb at 303b40 panicstr: bdwrite: buffer is not busy panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1d fault code = supervisor read, page not present instruction pointer = 0x8:0xc018f581 stack pointer = 0x10:0xc66ebb40 frame pointer = 0x10:0xc66ebb50 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 = 416 (lockf) trap number = 12 panic: page fault syncing disks... panic: bdwrite: buffer is not busy Uptime: 6m54s dumping to dev ad0s1b, offset 393600 dump ata0: resetting devices .. done 63 62 61 [CTRL-C to abort] 60 59 [CTRL-C to abort] 58 [CTRL-C to abort] 57 [CTRL-C to abort] 56 [CTRL-C to abort] 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 0xc0197d7e in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:476 476 } (kgdb) bt #0 0xc0197d7e in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:476 #1 0xc0df244c in ?? () #2 0xc0197b6b in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:334 #3 0xc0197f9d in panic (fmt=0xc0299721 "bdwrite: buffer is not busy") at /usr/src/sys/kern/kern_shutdown.c:632 #4 0xc01c93e3 in bdwrite (bp=0xc213a91c) at /usr/src/sys/kern/vfs_bio.c:841 #5 0xc02286ad in ffs_update (vp=0xc65cb380, waitfor=0) at /usr/src/sys/ufs/ffs/ffs_inode.c:119 #6 0xc023539a in ffs_fsync (ap=0xc66eb9f4) at /usr/src/sys/ufs/ffs/ffs_vnops.c:292 #7 0xc02339aa in ffs_sync (mp=0xc0de5e00, waitfor=2, cred=0xc05ade00, td=0xc031a8e4) at vnode_if.h:441 #8 0xc01d59c5 in sync (td=0xc031a8e4, uap=0x0) at /usr/src/sys/kern/vfs_syscalls.c:662 #9 0xc0197770 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:244 #10 0xc0197f9d in panic (fmt=0xc02b129e "%s") at /usr/src/sys/kern/kern_shutdown.c:632 #11 0xc02747e3 in trap_fatal (frame=0xc66ebb00, eva=29) at /usr/src/sys/i386/i386/trap.c:939 #12 0xc0274525 in trap_pfault (frame=0xc66ebb00, usermode=0, eva=29) at /usr/src/sys/i386/i386/trap.c:851 #13 0xc0273f37 in trap (frame={tf_fs = -1071841256, tf_es = -965869552, tf_ds = 16, tf_edi = 0, tf_esi = 0, tf_ebp = -965821616, tf_isp = -965821652, tf_ebx = -1058144640, tf_edx = -1071033256, tf_ecx = -1069469696, tf_eax = 1, tf_trapno = 12, tf_err = 0, tf_eip = -1072106111, tf_cs = 8, tf_eflags = 66118, tf_esp = -1071033241, tf_ss = 0}) at /usr/src/sys/i386/i386/trap.c:403 #14 0xc0266488 in alltraps_with_regs_pushed () #15 0xc018ea2a in lf_setlock (lock=0xc0edfe80) at /usr/src/sys/kern/kern_lockf.c:211 #16 0xc018e9c3 in lf_advlock (ap=0xc66ebc04, head=0xc0edd93c, size=0) at /usr/src/sys/kern/kern_lockf.c:176 #17 0xc023d30e in ufs_advlock (ap=0xc66ebc04) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2190 #18 0xc023d7f9 in ufs_vnoperate (ap=0xc66ebc04) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2658 #19 0xc01d64e3 in open (td=0xc6691e04, uap=0xc66ebd20) at vnode_if.h:843 #20 0xc0274c64 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1, tf_esi = -1077938004, tf_ebp = -1077938176, tf_isp = -965821068, tf_ebx = -1077937786, tf_edx = -1077938012, tf_ecx = 672100864, tf_eax = 5, tf_trapno = 12, tf_err = 2, tf_eip = 671764168, tf_cs = 31, tf_eflags = 663, tf_esp = -1077938220, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1127 #21 0xc02664bd in syscall_with_err_pushed () #22 0x8048ae2 in ?? () #23 0x80488f1 in ?? () (kgdb) quit    p   quit miss# exit exit Script done on Wed Nov 7 14:04:38 2001 It panics because of if_inode is not initiliazed: /sys/kern/kern_lockf.c:1.25:153 /* lock->lf_inode = ip; */ /* XXX JH */ I have no idea what ``JH'' means, the comment appeared in 1.10. The patch against kern_lockf.c:1.38 Index: kern_lockf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_lockf.c,v retrieving revision 1.38 diff -u -r1.38 kern_lockf.c --- kern_lockf.c 12 Sep 2001 08:37:44 -0000 1.38 +++ kern_lockf.c 7 Nov 2001 10:59:04 -0000 @@ -163,7 +163,7 @@ lock->lf_start = start; lock->lf_end = end; lock->lf_id = ap->a_id; -/* lock->lf_inode = ip; */ /* XXX JH */ + lock->lf_inode = VTOI(ap->a_vp); lock->lf_type = fl->l_type; lock->lf_head = head; lock->lf_next = (struct lockf *)0; Works for me on yesterday -current. - -maxim -- Maxim Konovalov, MAcomnet, Internet-Intranet Dept., system engineer phone: +7 (095) 796-9079, mailto: maxim@macomnet.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 13:22: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.sitaranetworks.com (apollo.sitaranetworks.com [199.103.141.105]) by hub.freebsd.org (Postfix) with ESMTP id 6DF1337B418 for ; Thu, 15 Nov 2001 13:22:04 -0800 (PST) Received: from rios.sitaranetworks.com (rios.sitaranetworks.com [199.103.141.78]) by apollo.sitaranetworks.com (8.10.2+Sun/8.9.3) with ESMTP id fAFLLd513035 for ; Thu, 15 Nov 2001 16:21:39 -0500 (EST) Received: by rios.sitaranetworks.com with Internet Mail Service (5.5.2653.19) id ; Thu, 15 Nov 2001 16:21:55 -0500 Message-ID: <31269226357BD211979E00A0C9866DAB02BB9745@rios.sitaranetworks.com> From: Chris Ptacek To: "'freebsd-hackers@freebsd.org'" Subject: kernel malloc questions... Date: Thu, 15 Nov 2001 16:21:51 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey all, I have a couple questions about kernel mallocs. I am trying to malloc a large amount of memory for a KLD during load and the malloc keeps failing. I am trying to malloc 64-128MB for a memory pool for a project I am working on. My system has 196MB of memory and the KLD is loaded at startup so I am relativly sure that I have enough memory to satisfy the request. I guess the questions are: Is there a limit to the amount of memory the kernel (including modules) can malloc? If there is how do I change this amount? I am currently using M_NOWAIT, would using M_WAITOK be better? Would this end up hanging my system in this case? Would I be better off mallocing many smaller buffers into a memory pool (64 1MB buffers)? I don't have access to the mailing lists at the moment and would appreciate it if you could CC me with any replies. Thanks, Chris cptacek@sitaranetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 13:32:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 1803D37B418 for ; Thu, 15 Nov 2001 13:32:45 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id D3C8C81D08; Thu, 15 Nov 2001 15:32:39 -0600 (CST) Date: Thu, 15 Nov 2001 15:32:39 -0600 From: Alfred Perlstein To: Maxim Konovalov Cc: hackers@freebsd.org Subject: Re: has 'options LOCKF_DEBUG' ever worked? (w/ patch) (fwd) Message-ID: <20011115153239.T13393@elvis.mu.org> References: <20011115233840.T38246-100000@news1.macomnet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011115233840.T38246-100000@news1.macomnet.ru>; from maxim@macomnet.ru on Thu, Nov 15, 2001 at 11:42:50PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yes I saw this, I have no idea what 'JH' stands for either that's why I left it as is. The problem is that VTOI is ufs specific, this "fix" will break LOCKF_DEBUG for all other FS's other than UFS because it casts the vnode->data ptr to struct inode *. So your "fix" is broken. Please just fix lf_print to not deref the inode ptr in the struct. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 13:34:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id BA55937B405 for ; Thu, 15 Nov 2001 13:34:20 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id AE25C81D0A; Thu, 15 Nov 2001 15:34:20 -0600 (CST) Date: Thu, 15 Nov 2001 15:34:20 -0600 From: Alfred Perlstein To: Chris Ptacek Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: kernel malloc questions... Message-ID: <20011115153420.U13393@elvis.mu.org> References: <31269226357BD211979E00A0C9866DAB02BB9745@rios.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <31269226357BD211979E00A0C9866DAB02BB9745@rios.sitaranetworks.com>; from cptacek@sitaranetworks.com on Thu, Nov 15, 2001 at 04:21:51PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Chris Ptacek [011115 15:22] wrote: > Hey all, I have a couple questions about kernel mallocs. > > I am trying to malloc a large amount of memory for a KLD during load and the > malloc keeps failing. I am trying to malloc 64-128MB for a memory pool for > a project I am working on. My system has 196MB of memory and the KLD is > loaded at startup so I am relativly sure that I have enough memory to > satisfy the request. You're probably incorrect. I know malloc looks easy, but what you want to use is the underlying mechanisms that malloc uses, vm_alloc or whatnot. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 13:44:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id A82D137B41A for ; Thu, 15 Nov 2001 13:44:06 -0800 (PST) Received: (qmail 2761 invoked from network); 15 Nov 2001 21:44:05 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Nov 2001 21:44:05 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20011115233840.T38246-100000@news1.macomnet.ru> Date: Thu, 15 Nov 2001 13:44:05 -0800 (PST) From: John Baldwin To: Maxim Konovalov Subject: RE: has 'options LOCKF_DEBUG' ever worked? (w/ patch) (fwd) Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15-Nov-01 Maxim Konovalov wrote: > It panics because of if_inode is not initiliazed: > > /sys/kern/kern_lockf.c:1.25:153 > > /* lock->lf_inode = ip; */ /* XXX JH */ > > I have no idea what ``JH'' means, the comment appeared in 1.10. revision 1.10 date: 1997/02/10 02:09:36; author: dyson; state: Exp; lines: +53 -68 This is the kernel Lite/2 commit. There are some requisite userland changes, so don't expect to be able to run the kernel as-is (very well) without the appropriate Lite/2 userland changes. The system boots and can mount UFS filesystems. Untested: ext2fs, msdosfs, NFS Known problems: Incorrect Berkeley ID strings in some files. Mount_std mounts will not work until the getfsent library routine is changed. Reviewed by: various people Submitted by: Jeffery Hsu Obviously the 'JH' seems to refer to hsu@FreeBSD.org. He might have more details on why this change was made. It seems that it has been broken for 4.75 years at this point. :) I have no objections to the patch except that the concept of an inode is not valid on all file systems, which is why that may be commented out in the first place. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 13:56:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 92D9837B405; Thu, 15 Nov 2001 13:56:32 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id XAA67156; Thu, 15 Nov 2001 23:56:25 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from notebook.vega.com (h30.229.dialup.iptcom.net [212.9.229.30]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id XAA79972; Thu, 15 Nov 2001 23:56:21 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-Id: <200111152156.XAA79972@ipcard.iptcom.net> To: marcus@marcuscom.com Cc: freebsd-ports@FreeBSD.org, hackers@FreeBSD.org From: Maxim Sobolev Subject: Using bit 21 of EFLAGS in user-mode [was: Re: sigreturn: eflags creash (fixed!)] X-Mailer: Pygmy (v0.5.13) Date: Thu, 15 Nov 2001 23:56:13 EET In-Reply-To: <20011115145029.G47613-200000@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="192.168.1.100.0.992.1005861375.631.10189" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --192.168.1.100.0.992.1005861375.631.10189 Content-Type: text/plain On Thu, 15 Nov 2001 14:56:31 -0500 (EST), Joe Clarke wrote: > > I learned about this by reading through some of the -hackers archives. > One person complained of similar errors trying to get xine to work on > FreeBSD. Removing the MMX detection code fixed it. I remembered libpng > also used MMX, so I removed the pnggccrd.c source, and voila! > > Based on core dumps, strace output, and a lot of code surfing, this makes > sense to me. Basically, any png-dependent app's thread that runs longer > than what ITIMER_PROF is set to gets hit with a SIGPROF. When that > happens, things context switch. eflags must have been corrupted by the > MMX code, thus sigreturn() bombs out, and causes uthread_kern to die as > well. Here's what strace looks like when balsa tries to read a 33 MB > mailbox: > > 74202 sigreturn(0x81f2c64 > > When this happens, strace politely dies with a bus error. > > Thanks for testing this, Maxim. Hopefully someone can find the problem > and fix it for good. That explains... After a quick glance at png code I found that the only place where EFLAGS is altered is CPUID code, where the library flips bit 21 of EFLAGS in order to ensure that the CPUID instruction is supported (otherwise it will get SIGILL on older processors). Unfortunately, for some reason FreeBSB kernel considers bit 21 of EFLAGS as one that should not be altered in the user mode, thus making it illegal to use standard user-mode processor-detection routines based around that bit. AFAIK, it is a bug in FreeBSD, because there is actually nothing wrong with altering bit 21 in the user mode - it doesn't have any side effects and pretty much any of the currently available on the i386 OSes allows it. Therefore, I would like to ask you to test attached patch and if it works and there are no other objections I would like to commit it shortly. To test the patch, you need to recompile kernel with patch applied, reboot, recompile/reinstall png with MXX support turned on and try to run Nautilus. Please let me know if it helped or not. Thanks! -Maxim --192.168.1.100.0.992.1005861375.631.10189 Content-Type: application/octet-stream; name="psl.h.diff" Content-Transfer-Encoding: base64 SW5kZXg6IHN5cy9pMzg2L2luY2x1ZGUvcHNsLmgKPT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTogL2hvbWUv bmN2cy9zcmMvc3lzL2kzODYvaW5jbHVkZS9wc2wuaCx2CnJldHJpZXZpbmcgcmV2aXNpb24gMS4x MApkaWZmIC1kIC11IC1yMS4xMCBwc2wuaAotLS0gc3lzL2kzODYvaW5jbHVkZS9wc2wuaAkyOCBB dWcgMTk5OSAwMDo0NDoyMiAtMDAwMAkxLjEwCisrKyBzeXMvaTM4Ni9pbmNsdWRlL3BzbC5oCTE1 IE5vdiAyMDAxIDIxOjI1OjAyIC0wMDAwCkBAIC04Myw2ICs4Myw2IEBACiAgKiAzODYncy4KICAq LwogI2RlZmluZQlQU0xfVVNFUkNIQU5HRSAoUFNMX0MgfCBQU0xfUEYgfCBQU0xfQUYgfCBQU0xf WiB8IFBTTF9OIHwgUFNMX1QgXAotCQkJfCBQU0xfRCB8IFBTTF9WIHwgUFNMX05UIHwgUFNMX0FD KQorCQkJfCBQU0xfRCB8IFBTTF9WIHwgUFNMX05UIHwgUFNMX0FDIHwgUFNMX0lEKQogCiAjZW5k aWYgLyogIV9NQUNISU5FX1BTTF9IXyAqLwo= --192.168.1.100.0.992.1005861375.631.10189-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 14:12:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id A2FF937B417 for ; Thu, 15 Nov 2001 14:12:34 -0800 (PST) Received: (qmail 14733 invoked from network); 15 Nov 2001 22:12:04 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Nov 2001 22:12:04 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200111152156.XAA79972@ipcard.iptcom.net> Date: Thu, 15 Nov 2001 14:12:32 -0800 (PST) From: John Baldwin To: Maxim Sobolev Subject: RE: Using bit 21 of EFLAGS in user-mode [was: Re: sigreturn: efl Cc: hackers@FreeBSD.org, freebsd-ports@FreeBSD.org, marcus@marcuscom.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15-Nov-01 Maxim Sobolev wrote: > That explains... After a quick glance at png code I found that > the only place where EFLAGS is altered is CPUID code, where > the library flips bit 21 of EFLAGS in order to ensure that the > CPUID instruction is supported (otherwise it will get SIGILL > on older processors). Unfortunately, for some reason FreeBSB > kernel considers bit 21 of EFLAGS as one that should not be > altered in the user mode, thus making it illegal to use standard > user-mode processor-detection routines based around that bit. > AFAIK, it is a bug in FreeBSD, because there is actually nothing > wrong with altering bit 21 in the user mode - it doesn't have > any side effects and pretty much any of the currently available > on the i386 OSes allows it. Agreed, patch looks good to me. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 14:36:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shumai.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id 247CF37B419; Thu, 15 Nov 2001 14:36:36 -0800 (PST) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.6/8.11.6) with ESMTP id fAFMadn10807; Thu, 15 Nov 2001 17:36:39 -0500 (EST) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Thu, 15 Nov 2001 17:36:39 -0500 (EST) From: Joe Clarke To: Maxim Sobolev Cc: freebsd-ports@FreeBSD.org, Subject: Re: Using bit 21 of EFLAGS in user-mode [was: Re: sigreturn: eflags creash (fixed!)] In-Reply-To: <200111152156.XAA79972@ipcard.iptcom.net> Message-ID: <20011115173550.W47613-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 15 Nov 2001, Maxim Sobolev wrote: > On Thu, 15 Nov 2001 14:56:31 -0500 (EST), Joe Clarke wrote: > > > > I learned about this by reading through some of the -hackers archives. > > One person complained of similar errors trying to get xine to work on > > FreeBSD. Removing the MMX detection code fixed it. I remembered libpng > > also used MMX, so I removed the pnggccrd.c source, and voila! > > > > Based on core dumps, strace output, and a lot of code surfing, this makes > > sense to me. Basically, any png-dependent app's thread that runs longer > > than what ITIMER_PROF is set to gets hit with a SIGPROF. When that > > happens, things context switch. eflags must have been corrupted by the > > MMX code, thus sigreturn() bombs out, and causes uthread_kern to die as > > well. Here's what strace looks like when balsa tries to read a 33 MB > > mailbox: > > > > 74202 sigreturn(0x81f2c64 > > > > When this happens, strace politely dies with a bus error. > > > > Thanks for testing this, Maxim. Hopefully someone can find the problem > > and fix it for good. > > That explains... After a quick glance at png code I found that > the only place where EFLAGS is altered is CPUID code, where > the library flips bit 21 of EFLAGS in order to ensure that the > CPUID instruction is supported (otherwise it will get SIGILL > on older processors). Unfortunately, for some reason FreeBSB > kernel considers bit 21 of EFLAGS as one that should not be > altered in the user mode, thus making it illegal to use standard > user-mode processor-detection routines based around that bit. > AFAIK, it is a bug in FreeBSD, because there is actually nothing > wrong with altering bit 21 in the user mode - it doesn't have > any side effects and pretty much any of the currently available > on the i386 OSes allows it. > > Therefore, I would like to ask you to test attached patch and > if it works and there are no other objections I would like to > commit it shortly. To test the patch, you need to recompile > kernel with patch applied, reboot, recompile/reinstall png with > MXX support turned on and try to run Nautilus. Please let me know > if it helped or not. Works like a champ! Thanks a lot for taking this to the next step. It's really good to have full Gnome functionality. Joe > > Thanks! > > -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 14:42:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 04EE737B416; Thu, 15 Nov 2001 14:42:43 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.12.1/8.12.1) id fAFMfWZa011587; Thu, 15 Nov 2001 17:41:32 -0500 (EST) Date: Thu, 15 Nov 2001 17:41:32 -0500 (EST) From: Daniel Eischen To: Maxim Sobolev Cc: marcus@marcuscom.com, freebsd-ports@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Using bit 21 of EFLAGS in user-mode [was: Re: sigreturn: eflags creash (fixed!)] In-Reply-To: <200111152156.XAA79972@ipcard.iptcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 15 Nov 2001, Maxim Sobolev wrote: > On Thu, 15 Nov 2001 14:56:31 -0500 (EST), Joe Clarke wrote: > > > > I learned about this by reading through some of the -hackers archives. > > One person complained of similar errors trying to get xine to work on > > FreeBSD. Removing the MMX detection code fixed it. I remembered libpng > > also used MMX, so I removed the pnggccrd.c source, and voila! > > > > Based on core dumps, strace output, and a lot of code surfing, this makes > > sense to me. Basically, any png-dependent app's thread that runs longer > > than what ITIMER_PROF is set to gets hit with a SIGPROF. When that > > happens, things context switch. eflags must have been corrupted by the > > MMX code, thus sigreturn() bombs out, and causes uthread_kern to die as > > well. Here's what strace looks like when balsa tries to read a 33 MB > > mailbox: > > > > 74202 sigreturn(0x81f2c64 > > > > When this happens, strace politely dies with a bus error. > > > > Thanks for testing this, Maxim. Hopefully someone can find the problem > > and fix it for good. > > That explains... After a quick glance at png code I found that > the only place where EFLAGS is altered is CPUID code, where > the library flips bit 21 of EFLAGS in order to ensure that the > CPUID instruction is supported (otherwise it will get SIGILL > on older processors). Unfortunately, for some reason FreeBSB Does it need to keep bit 21 of EFLAGS flipped, or can libpng set it back and keep knowledge that CPUID is supported? Or does that bit need to remain set for CPUID to work? > kernel considers bit 21 of EFLAGS as one that should not be > altered in the user mode, thus making it illegal to use standard > user-mode processor-detection routines based around that bit. > AFAIK, it is a bug in FreeBSD, because there is actually nothing > wrong with altering bit 21 in the user mode - it doesn't have > any side effects and pretty much any of the currently available > on the i386 OSes allows it. > > Therefore, I would like to ask you to test attached patch and > if it works and there are no other objections I would like to > commit it shortly. To test the patch, you need to recompile > kernel with patch applied, reboot, recompile/reinstall png with > MXX support turned on and try to run Nautilus. Please let me know > if it helped or not. If at all possible, a fix should be committed that wouldn't necessitate a new kernel be built for -stable. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 14:48:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 7746B37B405 for ; Thu, 15 Nov 2001 14:48:05 -0800 (PST) Received: from dialup-209.245.139.20.dial1.sanjose1.level3.net ([209.245.139.20] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 164VIf-0000l3-00; Thu, 15 Nov 2001 14:48:02 -0800 Message-ID: <3BF44651.2583430C@mindspring.com> Date: Thu, 15 Nov 2001 14:48:49 -0800 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Chris Ptacek Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: kernel malloc questions... References: <31269226357BD211979E00A0C9866DAB02BB9745@rios.sitaranetworks.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chris Ptacek wrote: > I am trying to malloc a large amount of memory for a KLD during load and the > malloc keeps failing. I am trying to malloc 64-128MB for a memory pool for > a project I am working on. My system has 196MB of memory and the KLD is > loaded at startup so I am relativly sure that I have enough memory to > satisfy the request. > > I guess the questions are: > > Is there a limit to the amount of memory the kernel (including > modules) can malloc? Yes. There are two limits. One is based on the amount of mappings available, which limits your total swap plus physical memory that you can allocate. The second one is 1G, because that the size of the KernelVirtual Address space. > If there is how do I change this amount? The kernel virtual address space can be increased. The handbook give almost all (but not quite) the information needed. See the -current list archives. > I am currently using M_NOWAIT, would using M_WAITOK be better? M_NOWAIT means that you are not permitting it to sleep; this means that you are willing to accept a failure, rather than have the process on whose behalf the call is being made put to sleep. You say it's a KLD, but fail to tell us if it is a device driver in the module. I'll assume that it is. Then the answer is that you can't sleep unless you create a kernel process to use as a sleep context. > Would this end up hanging my system in this case? It depends on your usage; see above. M_WAITOK is supposed to wait until the memory is available; but in fact, it does not wait forever, like you would want. If it fails after a number of retries, it gives up. This is a semantic change that came in early in the 4.x branch, It was never really justified to my satisfaction, other than someone had a wait case that failed once in a while, and didn't want to understand the code fully enough to fix it. So no matter how you call it, you have to be prepared for a failure. Knowing why it fails would probably help you: the failure can only occur if it traverses the map looking for a large enough space and can't find it. > Would I be better off mallocing many smaller buffers into a > memory pool (64 1MB buffers)? It depends on your usage. If the memory is necessary to be contiguous, then you could do worse than to follow Alfred's advice. In any case, if you can do it as smaller chunks, you will get better utilization of the kernel memory map, and will be more likely to not need a large contiguous region. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 15: 6: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id DD96A37B418 for ; Thu, 15 Nov 2001 15:05:51 -0800 (PST) Received: (qmail 2551 invoked from network); 15 Nov 2001 23:05:50 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Nov 2001 23:05:50 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 15 Nov 2001 15:05:49 -0800 (PST) From: John Baldwin To: Daniel Eischen Subject: Re: Using bit 21 of EFLAGS in user-mode [was: Re: sigreturn: efl Cc: hackers@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG, marcus@marcuscom.com, Maxim Sobolev Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15-Nov-01 Daniel Eischen wrote: > On Thu, 15 Nov 2001, Maxim Sobolev wrote: >> On Thu, 15 Nov 2001 14:56:31 -0500 (EST), Joe Clarke wrote: >> > >> > I learned about this by reading through some of the -hackers archives. >> > One person complained of similar errors trying to get xine to work on >> > FreeBSD. Removing the MMX detection code fixed it. I remembered libpng >> > also used MMX, so I removed the pnggccrd.c source, and voila! >> > >> > Based on core dumps, strace output, and a lot of code surfing, this makes >> > sense to me. Basically, any png-dependent app's thread that runs longer >> > than what ITIMER_PROF is set to gets hit with a SIGPROF. When that >> > happens, things context switch. eflags must have been corrupted by the >> > MMX code, thus sigreturn() bombs out, and causes uthread_kern to die as >> > well. Here's what strace looks like when balsa tries to read a 33 MB >> > mailbox: >> > >> > 74202 sigreturn(0x81f2c64 >> > >> > When this happens, strace politely dies with a bus error. >> > >> > Thanks for testing this, Maxim. Hopefully someone can find the problem >> > and fix it for good. >> >> That explains... After a quick glance at png code I found that >> the only place where EFLAGS is altered is CPUID code, where >> the library flips bit 21 of EFLAGS in order to ensure that the >> CPUID instruction is supported (otherwise it will get SIGILL >> on older processors). Unfortunately, for some reason FreeBSB > > Does it need to keep bit 21 of EFLAGS flipped, or can libpng > set it back and keep knowledge that CPUID is supported? Or > does that bit need to remain set for CPUID to work? It needs to be able to change it. If you can change the value of the bit (done by pushf ; pop %eax ; mov %eax,%ebx ; xor $PSL_ID,%eax ; push %eax ; popf ; pushf ; pop %eax ; compare bit PSL_ID of eax ebx to see if they match). The problem is if a signal comes in during the middle of that bit toggling due to a profiling timer. I think the problem may be that it uses a sequence that leaves the bit set, thus the kernel freaks out thinking that the user has changed a kernel only flag. The solution is Maxim's patch to make the kernel not care about the flag (which it shouldn't since cpuid is not a privileged instruction). > If at all possible, a fix should be committed that wouldn't > necessitate a new kernel be built for -stable. Perhaps if you patched libpng to block all signals and changed the code to add a pushf/popf around the entire sequence to preserve the PSL_ID flag. You would need to do this for xien and other apps that attempt to use cpuid as well. Fixing the kernel is much easier as Maxim's patch shows. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 16:10:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 812C837B416; Thu, 15 Nov 2001 16:10:15 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id CAA08165; Fri, 16 Nov 2001 02:10:12 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from notebook.vega.com (h141.227.dialup.iptcom.net [212.9.227.141]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id CAA15164; Fri, 16 Nov 2001 02:10:08 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-Id: <200111160010.CAA15164@ipcard.iptcom.net> To: eischen@pcnet1.pcnet.com Cc: marcus@marcuscom.com, freebsd-ports@FreeBSD.org, hackers@FreeBSD.org From: Maxim Sobolev Subject: Re: Using bit 21 of EFLAGS in user-mode [was: Re: sigreturn: eflags creash (fixed!)] X-Mailer: Pygmy (v0.5.13) Date: Fri, 16 Nov 2001 02:10:01 EET In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 15 Nov 2001 17:41:32 -0500 (EST), Daniel Eischen wrote: > On Thu, 15 Nov 2001, Maxim Sobolev wrote: > > On Thu, 15 Nov 2001 14:56:31 -0500 (EST), Joe Clarke wrote: > > > > > > I learned about this by reading through some of the -hackers archives. > > > One person complained of similar errors trying to get xine to work on > > > FreeBSD. Removing the MMX detection code fixed it. I remembered libpng > > > also used MMX, so I removed the pnggccrd.c source, and voila! > > > > > > Based on core dumps, strace output, and a lot of code surfing, this makes > > > sense to me. Basically, any png-dependent app's thread that runs longer > > > than what ITIMER_PROF is set to gets hit with a SIGPROF. When that > > > happens, things context switch. eflags must have been corrupted by the > > > MMX code, thus sigreturn() bombs out, and causes uthread_kern to die as > > > well. Here's what strace looks like when balsa tries to read a 33 MB > > > mailbox: > > > > > > 74202 sigreturn(0x81f2c64 > > > > > > When this happens, strace politely dies with a bus error. > > > > > > Thanks for testing this, Maxim. Hopefully someone can find the problem > > > and fix it for good. > > > > That explains... After a quick glance at png code I found that > > the only place where EFLAGS is altered is CPUID code, where > > the library flips bit 21 of EFLAGS in order to ensure that the > > CPUID instruction is supported (otherwise it will get SIGILL > > on older processors). Unfortunately, for some reason FreeBSB > > Does it need to keep bit 21 of EFLAGS flipped, or can libpng > set it back and keep knowledge that CPUID is supported? Or > does that bit need to remain set for CPUID to work? No it doesn't need it to be in any specific state. The only knowelege a program gains from the bit 21 is that its state could be changed, which means that CPUID instruction is supported. Unfortunately original libpng doesn't bother to set the state of the bit back, which exposed this problem. > If at all possible, a fix should be committed that wouldn't > necessitate a new kernel be built for -stable. Yes, I was also thinking about that. I've committed a patch, which restores state of the bit 21 as soon as possible. There is still a chance that the program will get a signal during that time, but this change is rather slim. The "unsafe" piece of code in question looks like: popfl <-load eflags with bit 21 flipped pushfl <-save resulting eflags + popl %%eax <-load resulting eflags into eax + pushl %%ecx <-save original eflags popfl <-restore original eflags Of course, it is possible to either mask all signals during detection period, or rip out detection code based around eflags and replace it with SIGILL handler, but this will cannibalize on speed improvement from MMX optimisations because of the additonal overhead associated with doing syscall necessary to set-up signal handler or signal mask. In any case, tomorrow I will test this workaround extensively, and if it appears that it is not sufficient to prevent `sigreturn: eflags...' errors, then I'll just disable MMX code in the libpng. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 16:10:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id BF61C37B416; Thu, 15 Nov 2001 16:10:46 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.12.1/8.12.1) id fAG09etu025898; Thu, 15 Nov 2001 19:09:40 -0500 (EST) Date: Thu, 15 Nov 2001 19:09:40 -0500 (EST) From: Daniel Eischen To: John Baldwin Cc: hackers@FreeBSD.org, freebsd-ports@FreeBSD.org, marcus@marcuscom.com, Maxim Sobolev Subject: Re: Using bit 21 of EFLAGS in user-mode [was: Re: sigreturn: efl In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 15 Nov 2001, John Baldwin wrote: > On 15-Nov-01 Daniel Eischen wrote: > > On Thu, 15 Nov 2001, Maxim Sobolev wrote: > >> On Thu, 15 Nov 2001 14:56:31 -0500 (EST), Joe Clarke wrote: > >> > > >> > I learned about this by reading through some of the -hackers archives. > >> > One person complained of similar errors trying to get xine to work on > >> > FreeBSD. Removing the MMX detection code fixed it. I remembered libpng > >> > also used MMX, so I removed the pnggccrd.c source, and voila! > >> > > >> > Based on core dumps, strace output, and a lot of code surfing, this makes > >> > sense to me. Basically, any png-dependent app's thread that runs longer > >> > than what ITIMER_PROF is set to gets hit with a SIGPROF. When that > >> > happens, things context switch. eflags must have been corrupted by the > >> > MMX code, thus sigreturn() bombs out, and causes uthread_kern to die as > >> > well. Here's what strace looks like when balsa tries to read a 33 MB > >> > mailbox: > >> > > >> > 74202 sigreturn(0x81f2c64 > >> > > >> > When this happens, strace politely dies with a bus error. > >> > > >> > Thanks for testing this, Maxim. Hopefully someone can find the problem > >> > and fix it for good. > >> > >> That explains... After a quick glance at png code I found that > >> the only place where EFLAGS is altered is CPUID code, where > >> the library flips bit 21 of EFLAGS in order to ensure that the > >> CPUID instruction is supported (otherwise it will get SIGILL > >> on older processors). Unfortunately, for some reason FreeBSB > > > > Does it need to keep bit 21 of EFLAGS flipped, or can libpng > > set it back and keep knowledge that CPUID is supported? Or > > does that bit need to remain set for CPUID to work? > > It needs to be able to change it. If you can change the value of the bit (done > by pushf ; pop %eax ; mov %eax,%ebx ; xor $PSL_ID,%eax ; push %eax ; popf ; > pushf ; pop %eax ; compare bit PSL_ID of eax ebx to see if they match). > The problem is if a signal comes in during the middle of that bit toggling due > to a profiling timer. I think the problem may be that it uses a sequence that > leaves the bit set, thus the kernel freaks out thinking that the user has > changed a kernel only flag. The solution is Maxim's patch to make the kernel > not care about the flag (which it shouldn't since cpuid is not a privileged > instruction). I just thought perhaps libpng could do something like: static int init_done = 0; static int cpuid_supported = 0; ... if (init_done == 0) { block_all_sigs(); cpuid_supported = check_cpuid(); init_done = 1; unblock_sigs(); } But if it always needs to change the bit, I guess the above doesn't help. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 16:54:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 0F70337B41B for ; Thu, 15 Nov 2001 16:54:30 -0800 (PST) Received: (qmail 28277 invoked from network); 16 Nov 2001 00:54:28 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 16 Nov 2001 00:54:28 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 15 Nov 2001 16:54:27 -0800 (PST) From: John Baldwin To: Daniel Eischen Subject: Re: Using bit 21 of EFLAGS in user-mode [was: Re: sigreturn: efl Cc: Maxim Sobolev , marcus@marcuscom.com, freebsd-ports@FreeBSD.org, hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 16-Nov-01 Daniel Eischen wrote: > On Thu, 15 Nov 2001, John Baldwin wrote: >> On 15-Nov-01 Daniel Eischen wrote: >> > On Thu, 15 Nov 2001, Maxim Sobolev wrote: >> >> On Thu, 15 Nov 2001 14:56:31 -0500 (EST), Joe Clarke wrote: >> >> > >> >> > I learned about this by reading through some of the -hackers archives. >> >> > One person complained of similar errors trying to get xine to work on >> >> > FreeBSD. Removing the MMX detection code fixed it. I remembered >> >> > libpng >> >> > also used MMX, so I removed the pnggccrd.c source, and voila! >> >> > >> >> > Based on core dumps, strace output, and a lot of code surfing, this >> >> > makes >> >> > sense to me. Basically, any png-dependent app's thread that runs >> >> > longer >> >> > than what ITIMER_PROF is set to gets hit with a SIGPROF. When that >> >> > happens, things context switch. eflags must have been corrupted by the >> >> > MMX code, thus sigreturn() bombs out, and causes uthread_kern to die as >> >> > well. Here's what strace looks like when balsa tries to read a 33 MB >> >> > mailbox: >> >> > >> >> > 74202 sigreturn(0x81f2c64 >> >> > >> >> > When this happens, strace politely dies with a bus error. >> >> > >> >> > Thanks for testing this, Maxim. Hopefully someone can find the problem >> >> > and fix it for good. >> >> >> >> That explains... After a quick glance at png code I found that >> >> the only place where EFLAGS is altered is CPUID code, where >> >> the library flips bit 21 of EFLAGS in order to ensure that the >> >> CPUID instruction is supported (otherwise it will get SIGILL >> >> on older processors). Unfortunately, for some reason FreeBSB >> > >> > Does it need to keep bit 21 of EFLAGS flipped, or can libpng >> > set it back and keep knowledge that CPUID is supported? Or >> > does that bit need to remain set for CPUID to work? >> >> It needs to be able to change it. If you can change the value of the bit >> (done >> by pushf ; pop %eax ; mov %eax,%ebx ; xor $PSL_ID,%eax ; push %eax ; popf ; >> pushf ; pop %eax ; compare bit PSL_ID of eax ebx to see if they match). >> The problem is if a signal comes in during the middle of that bit toggling >> due >> to a profiling timer. I think the problem may be that it uses a sequence >> that >> leaves the bit set, thus the kernel freaks out thinking that the user has >> changed a kernel only flag. The solution is Maxim's patch to make the >> kernel >> not care about the flag (which it shouldn't since cpuid is not a privileged >> instruction). > > I just thought perhaps libpng could do something like: > > static int init_done = 0; > static int cpuid_supported = 0; > > ... > > if (init_done == 0) { > block_all_sigs(); > cpuid_supported = check_cpuid(); > init_done = 1; > unblock_sigs(); > } > > But if it always needs to change the bit, I guess the above doesn't help. No, that's correct. The problem is the check_cpuid() function left the state of the PSL_ID flag bit changed. :) So you need to change the check_cpuid() to include a wrapper to save/restore the flags. Maxim just committed a change to do this. I'm not sure if he included the signal blocking though. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 18:51:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id CA47937B405; Thu, 15 Nov 2001 18:51:30 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fAG2pTa48188; Thu, 15 Nov 2001 19:51:29 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fAG2pS719339; Thu, 15 Nov 2001 19:51:28 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200111160251.fAG2pS719339@harmony.village.org> To: Daniel Eischen Subject: Re: Using bit 21 of EFLAGS in user-mode [was: Re: sigreturn: efl Cc: John Baldwin , hackers@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG, marcus@marcuscom.com, Maxim Sobolev In-reply-to: Your message of "Thu, 15 Nov 2001 19:09:40 EST." References: Date: Thu, 15 Nov 2001 19:51:28 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm also seeing this in my X server... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 20:47:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail5.sh163.net (mail5.sh163.net [202.96.194.136]) by hub.freebsd.org (Postfix) with SMTP id 3DF2837B405 for ; Thu, 15 Nov 2001 20:47:41 -0800 (PST) Received: (Rockmail 7411 invoked from network); 16 Nov 2001 04:47:33 -0000 Received: from unknown (HELO sh163.net) ([61.165.120.136]) (envelope-sender ) by mail5.sh163.net (Rockmail) with SMTP for ; 16 Nov 2001 04:47:33 -0000 Message-ID: <4120011151645038800@sh163.net> X-EM-Version: 5, 0, 0, 11 X-EM-Registration: #S1dI500R1AX60C0Rb100 X-Priority: 3 Reply-To: zmzl@sh163.net From: "ÖÐó" Subject: ÖйúʯÓͺÍʯÓÍ»¯¹€É豞¹€ÒµÐ­»á Date: Fri, 16 Nov 2001 12:50:38 +0800 MIME-Version: 1.0 Content-type: text/plain; charset=GB2312_CHARSET To: undisclosed-recipients:; Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG »¶ Ó­ ²Î ¹Û 2001Öйú£šÉϺ££©¹úŒÊʯÓÍŒ°Ê¯»¯ŒŒÊõÉ豞չÀÀ»á ͬÆڟٰ죺2001ÉϺ£¹úŒÊ»¯¹€ŒŒÊõÉ豞չÀÀ»á 2001ÉϺ£¹úŒÊÆøÌ匌ÊõÉ豞չÀÀ»á ÓÉÖйúʯÓͺÍʯÓÍ»¯¹€É豞¹€ÒµÐ­»á¡¢ÉϺ£Êлúе¹€³Ìѧ»áŒ°ÉϺ£ÖÐóչÀÀ ·þÎñÓÐÏÞ¹«ËŸµÈµ¥Î»¹²Í¬ŸÙ°ìµÄ"2001 Öйú£šÉϺ££©¹úŒÊʯÓÍŒ°Ê¯»¯ŒŒÊõÉ豞չ ÀÀ»á"œ«ÓÚ2001Äê11ÔÂ29ÈÕ-12ÔÂ1ÈÕÔÚÉϺ£¹âŽó»áÕ¹ÖÐÐÄ¡Ö؟ٰ졣 ±ŸŽÎÕ¹»áÎü ÒýÁËÀŽ×Ô¹úÄÚÍâ250ŒÒ³§É̲ÎÕ¹£¬ »ãŸÛÖÚ¶à¹úÄÚÍâÖøÃû³§É̵Ä×îÐÂŒŒÊõÓëÉ豞 ¡£ ²¢ŸÙ°ìÏà¹Ø±šžæ»áŒ°ŒŒÊõœ»Á÷»á¡£ ÎÒÃdzÏÑûÄãœìʱ¹âÁÙÕ¹»á²Î¹Û¡¢œ»Á÷¡£ ÏêÇéÇë²éѯ£ºÉϺ£ÖÐóչÀÀ·þÎñÓÐÏÞ¹«ËŸ ÉϺ£ÊÐäîϪ·251Ū5ºÅÂ¥20F µç »°£º021-54641713 54641743 Ž« Õ棺021-64942305 E-mail:zmzl@sh163.net http:www.zhongmao.com.cn ŒŒÊõœ»Á÷Ó뱚žæ»á Ö÷ Ì⣺ÐýÁ÷·ÖÀ댌ÊõÔÚʯÓÍ¡¢»¯¹€¹€ÒµÖеÄÓŠÓà ±šžæÈË£ºœÌÓý²¿œ­ÄÏŽóѧ·ÖÀë¹€³ÌÑП¿Ëù Ô¬»ÝÐÂœÌÊÚ Ê± Œä£º2001Äê11ÔÂ29ÈÕÉÏÎç10£º30-11£º30 µØ µã£ºÉϺ£¹âŽó»áÕ¹ÖÐÐÄÎ÷¹Ý¶þºÅ»áÒéÊÒ Ö÷ Ì⣺¹ØÓÚÎÒ¹úʯÓÍ×ê²ÉŒŒÊõ×°±ž·¢Õ¹µÄÈôžÉ¶Ô²ß ±šžæÈË£ºÊ¯ÓÍŽóѧ ÕÅËÃΰœÌÊÚ Ê± Œä£º2001Äê11ÔÂ29ÈÕÏÂÎç13£º30-15£º30 µØ µã£ºÉϺ£¹âŽó»áÕ¹ÖÐÐÄÎ÷¹Ý¶þºÅ»áÒéÊÒ Ö÷ Ì⣺"Ê®Îå"ÆÚŒäʯ»¯¹€ÒµµÄ·¢Õ¹Œ°Æä¶Ô×°±žµÄÐèÇó ±šžæÈË£ºÖйúʯÓÍ»¯¹€Œ¯ÍŹ«ËŸ×Éѯ¹«ËŸ ³ÂÔÊÖÐœÌÊÚŒ¶žß¹€ ʱ Œä£º2001Äê11ÔÂ30ÈÕÉÏÎç10£º00-12£º00 µØ µã£ºÉϺ£¹âŽó»áÕ¹ÖÐÐÄÎ÷¹Ý¶þºÅ»áÒéÊÒ Ö÷ Ì⣺ȫÇò¹€ÒµÆøÌåÊг¡µÄ·¢Õ¹Ç÷Ïò ʱ Œä£º2001Äê11ÔÂ30ÈÕÉÏÎç10£º00-11£º30 µØ µã£ºÉϺ£¹âŽó»áÕ¹ÖÐÐÄÎ÷¹ÝËĺŻáÒéÊÒ ±šžæÈË£ºJohn Racquet ÏÈÉú Ö÷ Ì⣺¹€ÒµŽ¿Ë® ³¬Ž¿Ë®ÖÆÔì ʱ Œä£º2001Äê11ÔÂ30ÈÕÏÂÎç13£º30-15£º00 µØ µã£ºÉϺ£¹âŽó»áÕ¹ÖÐÐÄÎ÷¹ÝËĺŻáÒéÊÒ ±šžæÈË£ººŒÖÝ£š»ðŸæ£©Î÷¶·ÃÅÄ€¹€ÒµÓÐÏÞ¹«ËŸ ÐìÈÙ°²×ÜŸ­Àí ²¿·ÖÕ¹ÉÌÃûµ¥ Ó¢¹úººÄ·ÎÖ˹°×ÁŠÊË-ÄŠºà¹«ËŸ µÂ¹úÈü¶àÀû˹ÓÐÏÞ¹«ËŸ Louisiana Chemical Equipment Co L.L.C Î÷ÃÅ×ÓÕæ¿Õ±ÃѹËõ»úÓÐÏÞ¹«ËŸ °¢Ä·Ë¹×³.ÔÆ·œÚÄÜÉ豞ÓÐÏÞ¹«ËŸ ºŒÖݲŒÀʵÍÎÂÉ豞ÓÐÏÞ¹«ËŸ ÒËÐËÌšÐË»·±£ÓÐÏÞ¹«ËŸ ºŒÖÝ£š»ðŸæ£©Î÷¶·ÃÅÄ€¹€Òµ¹«ËŸ º«¹ú£šÖ꣩ÐÅÓѵç×Ó ÉϺ£¿ÆŽïʵҵÓÐÏÞ¹«ËŸ ÉϺ£Â¡Ç¿Œì²âÒÇÆ÷É豞ÓÐÏÞ¹«ËŸ ÌšÍåÊËÆôÓÐÏÞ¹«ËŸ ÄÏÑô·À±¬Œ¯ÍÅÓÐÏÞ¹«ËŸ ÉýÑôÆóÒµ£š¹É·Ý£©¹«ËŸ ž£ÖÝ·§ÃÅ×ܳ§ ÎÂÖÝÊÐÀûÆÕ×Ô¿ØÉ豞ÓÐÏÞ¹«ËŸ ÉϺ£Ž¬±õÖÆÒ©·ÛËéÉ豞³§ ÄÏ͚ɜœ£Ê¯Ä«É豞ÓÐÏÞ¹«ËŸ ÉϺ£°Í°²Ë®ŽŠÀí¹€³ÌÓÐÏÞ¹«ËŸ ÷ÌØÀÕ-ÍÐÀû¶à³£ÖݺâÆ÷¹«ËŸ ÀïÆäÀÖóÒ×£šÉϺ££©ÓÐÏÞ¹«ËŸ ÉœÎ÷ÐË°²»¯Ñ§¹€Òµ£šŒ¯ÍÅ£©¹«ËŸ Î✭ÊйÌÁŠÕ͹ÜÆ÷ÓÐÏÞ¹«ËŸ ÉϺ£Éê·œÈÈÄÜ»úеÉ豞ÓÐÏÞ¹«ËŸ Õ㜭ʡÎÂÁëÊÐÉñ¹âÈÈÄÜÉ豞ÓÐÏÞ¹«ËŸ ÉϺ£·çžùѹËõ»úÓÐÏÞ¹«ËŸ Ììœò±ÃÒµ»úеŒ¯ÍÅÓÐÏÞ¹«ËŸ ÉϺ£¿É¹ó¹Ì̬Àë×ÓµŒÌ幫˟ Äþ²šÌìÉúÃÜ·âŒþÓÐÏÞ¹«ËŸ ŽÈϪºãÁŠÍ¬²œŽøÂÖÓÐÏÞ¹«ËŸ ºŒÖÝÐËÔŽ¹ýÂË»úÓÐÏÞ¹«ËŸ ºÓÄÏ¿ÆԎʯÓÍŒŒÊõ¿ª·¢¹«ËŸ ËÄŽšÑÇÁªÉúÎﻯ¹€ÑП¿Ëù Óª¿ÚÊй܌þ¹€Òµ¹«ËŸ °°ÉœÊпƳÏ×Ô¶¯»¯ÏµÍ³ÓÐÏÞ¹«ËŸ ¹ãÖÝÊв©Ê¿Âü»úµçÓÐÏÞ¹«ËŸ ±±Ÿ©¶«·œÊ¥Â¡Žï¿ÆóÓÐÏÞ¹«ËŸ Î✭ÝÚæÚʯÓÍ»¯¹€³§ ËÕÖÝÅŠÍþ»úеÓÐÏÞ¹«ËŸ ÉϺ£œðÄɲš¿ÆŒŒ·¢Õ¹ÓÐÏÞ¹«ËŸ ÉϺ£·ÉºÍ»úеÓÐÏÞ¹«ËŸ ÉϺ£Äá¿ÉÄá±ÃÒµÓÐÏÞ¹«ËŸ Õ㜭·á»ªÇá»ú·§Ãų§ Éœ¶«Ê¡Î«·»Éúœš»úе³§£šŒ¯ÍÅ£© œ­ËÕÊ¡œ­ÒõÊÐʯÓÍ»¯¹€É豞ÓÐÏÞ¹«ËŸ ÎÂÖÝÊзúËÜÉ豞ÖÆÔ쳧 Õ㜭ÓÓÀû¹€³ÌËÜÁϹܵÀ×ܳ§ ÉîÛÚÊÐÌØ°²µç×ÓÓÐÏÞ¹«ËŸ ²ý»Ý£šÌìœò£©¹úŒÊóÒ×ÓÐÏÞ¹«ËŸ Õ㜭ʡÁÙº£ÊлúÉž³§ ÉϺ£ÁøÓª»úе³§ ÂÞŽïÀ³¿Ë˹·§ÃÅ£šÉϺ££©ÓÐÏÞ¹«ËŸ ±±Ÿ©ŸÓ°²È𺫿ƌŒ·¢Õ¹ÓÐÏÞ¹«ËŸ ºŒÖÝÄÏ·œÌØÖֱó§ ³É¶Œ°²¿ÉÐŵç×ÓÓÐÏÞ¹«ËŸ ¹þ¶û±õÁëÄϹܵÀÁ¬œÓÆ÷ÓÐÏÞ¹«ËŸ ±±Ÿ©Ô󻪿µÒ«ŒŒÊõ·¢Õ¹ÓÐÏÞ¹«ËŸ ÆœºþÊг¿ÈËÈŒÆøÉ豞ÓÐÏÞ¹«ËŸ °²»ÕÖпÆÖÇÄܞߌŒÊõÓÐÏÞÔðÈι«ËŸ Õ㜭ŽºêÍŒ¯ÍÅÓÐÏÞ¹«ËŸ µÂžßœàÇåœàÉ豞ÓÐÏÞ¹«ËŸ ±±Ÿ©žñÁÖ²©ÄÉÉÌóÓÐÏÞ¹«ËŸ Õ㜭ʡÓÀ¿µÊÐÐÂÁúÒDZíÓÐÏÞ¹«ËŸ ÎÞÎýÊÐÇ®ÊÏ¿ÆŒŒ¿ª·¢ÓÐÏÞ¹«ËŸ ³É¶ŒºÀ˹µç×ÓÌœ²âŒŒÊõÓÐÏÞ¹«ËŸ žÛ»ª»ÔÐŹ€³ÌËÜÁÏ£šÖÐÉœ£©¹«ËŸ ʯŒÒׯÊкàŽïîѹýÂËÆ÷²ÄÓÐÏÞ¹«ËŸ ÉϺ£¹ÚÁú·§ÃÅÓÐÏÞ¹«ËŸ ¹ãÎ÷ÄÏÄþÐÂÄÜ¿ÆŒŒ¿ª·¢ÓÐÏÞ¹«ËŸ ±±Ÿ©º«ŽóÔªÉÌóÓÐÏÞ¹«ËŸ ÎÞÎýÎ÷Ä·À³Ë¹Ê¯ÓÍךÓùÜÖÆÔ칫˟ ÉòÑôÊÐÈ«Íš·§ÃŹ܌þÖÆÔ칫˟ ÀŒÖÝʯÓÍ»¯¹€»úÆ÷×ܳ§ °Í¿ËÐîÄÜÆ÷£šÌìœò£©ÓÐÏÞ¹«ËŸ ÉϺ£¿ÆŽŽÉ«Æ×ÒÇÆ÷ÓÐÏÞ¹«ËŸ Õ㜭ÀÖ¶Š²šÎƹÜÓÐÏÞ¹«ËŸ ÉϺ£¹þµÏÍþ²»ÐâžÖÓÐÏÞ¹«ËŸ ÉϺ£ÊæÈðÆÕʵҵÓÐÏÞ¹«ËŸ ²ŒµÂ³˹Èȹ€ŒŒÊõÓÐÏÞ¹«ËŸ ž»Ë¹Žó¹ø¯ ÃÀ¹úÀïÆæ¹€Ÿß¹«ËŸ À׵ϣšÖйú£©ÓÐÏÞ¹«ËŸ Õ㜭̚ÖÝŽóÑóҺѹÕ͹ÜÉ豞ÖÆÔì×ܳ§ ÉϺ£·îÌ©µç×ÓµçÆ÷ÔªŒþ³§ÓÐÏÞ¹«ËŸ ʯÓÍŽóѧ¿ÂÁÖÈð¶û¿ÆŒŒÓÐÏÞÔðÈι«ËŸ Äþ²šÊÐÓµçÆ÷¹«ËŸ Õ㜭ÓÀÒ»·§Ãų§ œ­ËÕ»ªÑôœðÊô¹ÜŒþÓÐÏÞ¹«ËŸ ÉϺ£Åµ²©»úеÉ豞ÓÐÏÞ¹«ËŸ ÌìœòÊÐÈðµÂÂݞ˱ÃÖÆÔ쌌Êõ¹«ËŸ œ­ÒõÊÐœ­ÄÏžßѹ¹ÜŒþ³§ ÉϺ£èªÍþ»úµçÉ豞ÓÐÏÞ¹«ËŸ Î÷°²¶«·œžÖÌú³§ ÀÈ·»¿ª·¢Çø¹ÜµÀÈË»úеÉ豞¹«ËŸ ÎýÉœÊÐÐÂÒµ·À±¬µçÆøÓÐÏÞ¹«ËŸ Íþº£»¯¹€Æ÷еÓÐÏÞ¹«ËŸ ÉϺ£Ò×Ì©»¯¹€É豞ÖÆÔìÓÐÏÞ¹«ËŸ ÖÐÍâºÏ×Ê»ÍÊ¢¹ÜÒµÓÐÏÞ¹«ËŸÉϺ£°ì ÉϺ£ÖÐÒâʯÓÍÉ豞ÖÆÔìÓÐÏÞ¹«ËŸ ÉϺ£°×º×»ªÐÂÀö»ªÌØÊâžÖÖÆÆ· œ­ÒõÊÐÆø»¯»úе³§ ÀŒÖÝʯÓÍ»úеÑП¿Ëù ÉϺ£Ÿ«Î¢·ÛÈÜ»úеÉ豞ÓÐÏÞ¹«ËŸ ÉϺ£Žó¡»úÆ÷³§ ±±Ÿ©žñÈðÍض¯ÁŠÉ豞ÓÐÏÞ¹«ËŸ ÉϺ£œàÁع€Ã³ÓÐÏÞ¹«ËŸ Öйú±±·œ¹€ÒµŒ¯ÍŹ«ËŸ ¹þ¶û±õËĺ£Êý¿Ø¿ÆŒŒ¹É·ÝÓÐÏÞ¹«ËŸ ¹úÓªŸ®žÔÉœÒÇ±í³§ ¹óÖÝ¿­ÐÇÒºÁŠŽ«¶¯»úеÓÐÏÞ¹«ËŸ ÄÏÑôʯÓÍ»úе³§ ÉœÎ÷ÓÀŒÃµç»ú³§ ¹ã¶«ÓîÃ÷¿ÆŒŒÓÐÏÞ¹«ËŸ ÕŌҞÛÊж«ºœµçÈȵçÆ÷³§ ÉϺ£ŒÎ¶Ù»·±£¿ÆŒŒÓÐÏÞ¹«ËŸ ÉϺ£º£Ë÷ÒÇÆ÷ÒDZíÓÐÏÞ¹«ËŸ Éœ¶«Ê¡À³ÖÝÊаÔÁŠÊ¯ÓÍ»úеÓÐÏÞ¹«ËŸ ÉϺ£ŒÑ÷ë±Ã·§ÓÐÏÞ¹«ËŸ ÉϺ£ÄÏ»ª»»ÈÈÆ÷ÖÆÔìÓÐÏÞ¹«ËŸ œ­ÒõÊÐʯÓÍ»úе³§ Ê€ÀûʯÓ͹ÜÀíŸÖ¶¯ÁŠ»úе³§ ÉϺ£ÉгŒ¿ÆŒŒÓÐÏÞ¹«ËŸ ÕŌҞÛÊлªêÉŸ»»¯É豞ÓÐÏÞ¹«ËŸ ÉϺ£º£Ì©žÖ¹ÜÓÐÏÞ¹«ËŸ Ö麣Êк£·òʵҵ·¢Õ¹ÓÐÏÞ¹«ËŸ ïÃûʯ»¯»úе³§ ÎýÉœÊл·Óî×Ô¶¯»¯ÒDZíÓÐÏÞ¹«ËŸ ºÏ·ÊÀŒ²©µçÁŠ»úŸßŒŒÊõ¹«ËŸ ŽóÇìʯÓ͹ÜÀíŸÖµÚ¶þ»úе³§ ÉϺ£ÑÇÌ«ŒÆËã»úÐÅϢϵͳ¹«ËŸ Î÷°²¶š»ªµç×ÓÓÐÏÞÔðÈι«ËŸ ±±Ÿ©ÍþÓ¢ÖÇÍš¿ÆŒŒÓÐÏÞ¹«ËŸ ŒÃÄÏÊÔœðŒ¯ÍÅÓÐÏÞ¹«ËŸ ŒÃÄÏÊÔÑé»ú³§ ÖйúºœÌì¿ÆŒŒŒ¯ÍŹ«ËŸËÄÔºËÄʮһËù ÉϺ£¹€Òµ×Ô¶¯»¯ÒDZíÑП¿Ëù ¿šÂÞ¿ËÃܷ⌌ÊõÓÐÏÞ¹«ËŸ ¹þ¶û±õÐŲý·Àž¯·§ÃÅÖÆÔ칫˟ ÉϺ£»·ÌìʵҵÓÐÏÞ¹«ËŸ ¡¶µÍÎÂÓëÌØÆø¡· Öйú²»ÐâžÖÊÐÔÓÖŸÉç ÑÌÌšÀŒµÂÍøÂçÓÐÏÞÔðÈι«ËŸ »¯¹€É豞Óë¹ÜµÀ Öйú»¯¹€ÐÅÏ¢Íø ž»ÑôÊÐÊ¢Žó»úµçÖÆÔìÓÐÏÞ¹«ËŸ ÎÂÖÝÊÐÓÀÖÐÓÀ¡»úе³§ ÎÞÎýŽŽÃ÷Ž«¶¯¹€³ÌÓÐÏÞ¹«ËŸ ×ÍÕæ¿ÕÉ豞³§ÓÐÏÞ¹«ËŸ ÎÂÖÝÊж«·œ·Àž¯É豞ÓÐÏÞ¹«ËŸ ÎÂÖÝÌØÒ»·§Ãų§ ÇÇÖηÑЪ¶û¹«ËŸ ³àÊ¿¶Ü/°¬ÖŸ»úе Õ㜭º£ÃÅÊÔѹ±Ã³§ ÄÏŸ©°¢¶û·¢ÒÇÆ÷ÒDZíÓÐÏÞ¹«ËŸ Äþ²šÕýÒ»±Ã·§ÓÐÏÞ¹«ËŸ Õ㜭ʡÓÀÉϲ»ÐâžÖ²úÒµÓÐÏÞ¹«ËŸ ÉϺ£Ê¯ÓÍ»¯¹€É豞ÓÐÏÞ¹«ËŸ Ì«ÆœÑóÌìÈ»ÄÜÔŽ/»ªËŒ°²ÆøÌå¹ËÎÊ Ô¶¶«£šÄþ²š£©ËÜœºœðÊô¹€ÒµÓÐÏÞ¹«ËŸ œ­ËÕºãÍšµçÆøÒDZíÓÐÏÞ¹«ËŸ Æô¶«·À±¬µçÆø ±±Ÿ©ÖÐÓÍÁªºÏÐÅÏ¢ŒŒÊõÓÐÏÞ¹«ËŸ œÝÄÜŽïµçÆøÓÐÏÞ¹«ËŸ ³£ÖÝ×ÛÑÐŒÓÈȯÓÐÏÞ¹«ËŸ ÎÂÖÝ¿ÆÓî·§ÃÅÓÐÏÞ¹«ËŸ ÌìœòÊÐŽóžÛÇøÌ©ŽïʯÓÍÉ豞¹«ËŸ »ªÄÜÎÞÎýµçÈÈÆ÷²ÄÓÐÏÞ¹«ËŸ ÄÏŸ©°ÂÌصçÆøÓÐÏÞ¹«ËŸ ÁÉÄþÇìÑô»¯Ñ§¹€ÒµŒ¯ÍŹ«ËŸ ÉœÎ÷·çÀ×»úе³§ ÐÂœ®ÁÇÔ­»úÆ÷³§Ì©°²Éä¿×µ¯³§ ¹þ¶û±õœš³É»úе³§ ÉœÎ÷œúÎ÷¹€ÒµŒ¯ÍÅÓÐÏÞÔðÈι«ËŸ ÁÉÄþœõ»ª»úе³§ ºÚÁúœ­»ª°²¹€Òµ£šŒ¯ÍÅ£©¹«ËŸ Î÷°²œüŽú»¯Ñ§ÑП¿Ëù Éœ¶«»úÆ÷³§ ÉÂÎ÷ÓŠÓÃÎïÀí»¯Ñ§ÑП¿Ëù ±øÆ÷¹€ÒµµÚ213ÑП¿Ëù ÉϺ£åŸÑÇÎåœðÖÆÆ·ÓÐÏÞ¹«ËŸ ÖйúÈËÃñœâ·ÅŸüµÚ5719¹€³§·§ÃÅÎ峧 ÎÞÎýÎýÄÜŒÓÈȯÓÐÏÞ¹«ËŸ Õ㜭œðÖÞŒ¯ÍŹɷÝÓÐÏÞ¹«ËŸ ŽóÁ¬ÁŠµÏÁ÷Ìå¿ØÖÆŒŒÊõÓÐÏÞ¹«ËŸ ±±Ÿ©ËÉÌï³Ì¿ÆŒŒÓÐÏÞ¹«ËŸ ³£ÖÝÅÉÀ³ž£ÔöÇ¿ËÜÁÏÓÐÏÞ¹«ËŸ ÉϺ£·Ñ²š×Ô¿ØŒŒÊõÓÐÏÞ¹«ËŸ Õ㜭ÓàÒŠÊÐÐÂŽóËÜÁϹܲÄÓÐÏÞ¹«ËŸ ž»ÑôÊÐÓÀÊ¢ÒDZíÓÐÏÞ¹«ËŸ ÎÂÖÝÊСŽóËÜÒµÓÐÏÞ¹«ËŸ ÉϺ£µÂ±Š»úµçÉ豞ÓÐÏÞ¹«ËŸ ÖÐŽ¬Öع€Œ¯ÍŹ«ËŸÆßÔºÆß°ËÑП¿Ëù ÌìœòÊÐÇ°œøÒÇÆ÷ÒÇ±í³§ ÉîÛÚÊО»ÈÀµç×ÓÓÐÏÞ¹«ËŸ Éœ¶«Ê¡ÁÙÒÊÊа²ž£µç×ÓÓÐÏÞ¹«ËŸ Çൺ¶«¹â¹ø¯ÖÆÔìÓÐÏÞ¹«ËŸ ÉϺ£ÐÇ¿Õ×Ô¶¯»¯ÒDZíÓÐÏÞ¹«ËŸ Öйúʯ»¯³ö°æÉç ÖйúʯÓÍ»¯¹€ÐÅÏ¢Íø Öйú»¯¹€ÔÚ œ­ÄÏŽóѧ·ÖÀë¹€³ÌÑП¿Ëù ³É¶Œ»ªÎ÷»¯¹€¿ÆŒŒ¹É·ÝÓÐÏÞ¹«ËŸ ÉϺ£ÒàÂíÍšÓûúеÓÐÏÞ¹«ËŸ ÉϺ£Ê¯ÓÍ»¯¹€É豞ÓÐÏÞ¹«ËŸÅäŒþ³§ ÉϺ£ÊÐʯÓÍ»¯¹€»úеŒŒÊõÑП¿Ëù ºÓ±±Ê¡Ÿ°ÏØŸ°œòѹÂË»ú³§ £šÆª·ùÓÐÏÞÎŽÄÜŸ¡ÂŒ£© --------------------------------------------------------------------------- ²Î¹ÛµÇŒÇ»ØÖŽ ÐÕ Ãû£º Ö° Îñ£º µ¥Î»Ãû³Æ£º µØ Ö·£º µç »°£º Ž« Õ棺 ÓÊ ±à£º ÒµÎñ·¶Î§£º £šÄã¿ÉÆŸ±Ÿ»ØÖŽÔÚÕ¹¹ÝÈë¿Ú»»È¡×šÒµ¹ÛÖÚÖ€»òƟךҵÃûƬÁìÈ¡£© To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 15 23:34:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id CAC2637B41B for ; Thu, 15 Nov 2001 23:34:27 -0800 (PST) Received: (qmail 26429 invoked from network); 16 Nov 2001 07:33:58 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 16 Nov 2001 07:33:58 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200111160251.fAG2pS719339@harmony.village.org> Date: Thu, 15 Nov 2001 23:34:26 -0800 (PST) From: John Baldwin To: Warner Losh Subject: Re: Using bit 21 of EFLAGS in user-mode [was: Re: sigreturn: efl Cc: Maxim Sobolev , marcus@marcuscom.com, freebsd-ports@FreeBSD.ORG, hackers@FreeBSD.ORG, Daniel Eischen Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 16-Nov-01 Warner Losh wrote: > I'm also seeing this in my X server... Maxim has fixed the kernel, so it should work fine now. > Warner -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 2:12:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from piggy.rz.tu-ilmenau.de (piggy.rz.tu-ilmenau.de [141.24.4.8]) by hub.freebsd.org (Postfix) with ESMTP id 79C4D37B405 for ; Fri, 16 Nov 2001 02:12:46 -0800 (PST) Received: from gtw.hh59.local (pD9508BE7.dip.t-dialin.net [217.80.139.231]) (authenticated (0 bits)) by piggy.rz.tu-ilmenau.de (8.11.1/8.11.1) with ESMTP id fAGACg511227 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO) Fri, 16 Nov 2001 11:12:44 +0100 (MET) Received: from walnut.hh59.local (walnut.hh59.local [192.168.2.10]) by gtw.hh59.local (8.11.3/8.11.3) with ESMTP id fAGALdK04908 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified FAIL) for ; Fri, 16 Nov 2001 11:21:40 +0100 (CET) Received: (qmail 14233 invoked by uid 1000); 16 Nov 2001 10:13:06 -0000 Date: Fri, 16 Nov 2001 11:13:06 +0100 From: Martin Kaeske To: freebsd-hackers@freebsd.org Subject: BSD buffer management Message-ID: <20011116111306.A14218@walnut.hh59.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello Because i want to learn more about the BSD-kernel i bought the book "The Design and Implementation of the 4.4BSD Operating System" [McKusick, et.al.]. Now i come across the topic "Buffer Management" and i have a question: Is it possible that a call to bread() can result in a buffer covering more than one disk-block? If this is true how does the kernel ensures that there are no disk-blocks in more than one buffer (as the kernel does when files are shortened or removed)? Is it possible that its the callers (caller of bread()) task to keep track of overlapping buffers? And breads size argument is 'just' for flexibility and the caller has to ensure integrity. Martin -- The instructions said to use Windows 98 or better, so I installed FreeBSD. -- Jim Levie in comp.unix.bsd.freebsd.misc -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 3:57:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.macomnet.ru (relay1.macomnet.ru [195.128.64.10]) by hub.freebsd.org (Postfix) with ESMTP id BEDAE37B405; Fri, 16 Nov 2001 03:57:03 -0800 (PST) Received: from news1.macomnet.ru (maxim@news1.macomnet.ru [195.128.64.14]) by relay1.macomnet.ru (8.11.3/8.11.3) with ESMTP id fAGBux7180343; Fri, 16 Nov 2001 14:56:59 +0300 (MSK) Date: Fri, 16 Nov 2001 14:56:59 +0300 (MSK) From: Maxim Konovalov To: Alfred Perlstein Cc: John Baldwin , Subject: Re: has 'options LOCKF_DEBUG' ever worked? (w/ patch) (fwd) In-Reply-To: <20011115153239.T13393@elvis.mu.org> Message-ID: <20011116113214.S13973-100000@news1.macomnet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, On Thu, 15 Nov 2001, Alfred Perlstein wrote: > Yes I saw this, I have no idea what 'JH' stands for either that's why > I left it as is. > > The problem is that VTOI is ufs specific, this "fix" will break > LOCKF_DEBUG for all other FS's other than UFS because it casts > the vnode->data ptr to struct inode *. > > So your "fix" is broken. Alfred, John, thanks you very much for your answers. I expected something similar. Btw are there any smart ways to find out does underlying FS support inode concept or not? Yes, I know about vnode.v_tag, but comparing it with VT_UFS/VT_NFS/VT_MFS etc does not look OK for me. > Please just fix lf_print to not deref the inode ptr in the struct. Here it is. I put you comment, Alfred, above lf_inode assignment. Index: kern_lockf.c =================================================================== RCS file: /vol0/cvs/ncvs/src/sys/kern/kern_lockf.c,v retrieving revision 1.38 diff -u -r1.38 kern_lockf.c --- kern_lockf.c 2001/09/12 08:37:44 1.38 +++ kern_lockf.c 2001/11/16 11:49:42 @@ -163,7 +163,13 @@ lock->lf_start = start; lock->lf_end = end; lock->lf_id = ap->a_id; -/* lock->lf_inode = ip; */ /* XXX JH */ + /* + * XXX The problem is that VTOI is ufs specific, so it will + * break LOCKF_DEBUG for all other FS's other than UFS because + * it casts the vnode->data ptr to struct inode *. + */ +/* lock->lf_inode = VTOI(ap->a_vp); */ + lock->lf_inode = (struct inode *)0; lock->lf_type = fl->l_type; lock->lf_head = head; lock->lf_next = (struct lockf *)0; @@ -768,15 +774,22 @@ printf("proc %ld", (long)((struct proc *)lock->lf_id)->p_pid); else printf("id %p", (void *)lock->lf_id); - /* XXX no %qd in kernel. Truncate. */ - printf(" in ino %lu on dev <%d, %d>, %s, start %ld, end %ld", - (u_long)lock->lf_inode->i_number, - major(lock->lf_inode->i_dev), - minor(lock->lf_inode->i_dev), - lock->lf_type == F_RDLCK ? "shared" : - lock->lf_type == F_WRLCK ? "exclusive" : - lock->lf_type == F_UNLCK ? "unlock" : - "unknown", (long)lock->lf_start, (long)lock->lf_end); + if (lock->lf_inode != (struct inode *)0) + /* XXX no %qd in kernel. Truncate. */ + printf(" in ino %lu on dev <%d, %d>, %s, start %ld, end %ld", + (u_long)lock->lf_inode->i_number, + major(lock->lf_inode->i_dev), + minor(lock->lf_inode->i_dev), + lock->lf_type == F_RDLCK ? "shared" : + lock->lf_type == F_WRLCK ? "exclusive" : + lock->lf_type == F_UNLCK ? "unlock" : + "unknown", (long)lock->lf_start, (long)lock->lf_end); + else + printf(" %s, start %ld, end %ld", + lock->lf_type == F_RDLCK ? "shared" : + lock->lf_type == F_WRLCK ? "exclusive" : + lock->lf_type == F_UNLCK ? "unlock" : + "unknown", (long)lock->lf_start, (long)lock->lf_end); if (!TAILQ_EMPTY(&lock->lf_blkhd)) printf(" block %p\n", (void *)TAILQ_FIRST(&lock->lf_blkhd)); else @@ -789,6 +802,9 @@ struct lockf *lock; { register struct lockf *lf, *blk; + + if (lock->lf_inode == (struct inode *)0) + return; printf("%s: Lock list for ino %lu on dev <%d, %d>:\n", tag, (u_long)lock->lf_inode->i_number, > -Alfred tested on -stable. - -maxim -- Maxim Konovalov, MAcomnet, Internet-Intranet Dept., system engineer phone: +7 (095) 796-9079, mailto: maxim@macomnet.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 7:40:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from SRDMAIL.SINP.MSU.RU (bigking.sinp.msu.ru [213.131.9.130]) by hub.freebsd.org (Postfix) with ESMTP id F33FF37B418 for ; Fri, 16 Nov 2001 07:40:29 -0800 (PST) Received: from [194.220.213.239] (helo=sinp.msu.ru) by SRDMAIL.SINP.MSU.RU with esmtp (Exim 3.33 #3) id 164l4p-000MkR-00 for freebsd-hackers@freebsd.org; Fri, 16 Nov 2001 18:38:47 +0300 Message-ID: <3BF5335E.5080506@sinp.msu.ru> Date: Fri, 16 Nov 2001 18:40:14 +0300 From: Dmitry Mottl Organization: SINP MSU User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.4) Gecko/20011004 X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: kernel error messages Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, All I got following error, while I say 'reboot'. Please, help me with description, what's going on Why 'pagein' and 'pageout' failed? What is error 22? ---- Nov 14 18:07:00 spectre /kernel: swap_pager: I/O error - pageout failed; blkno 1552,size 16384, error 22 Nov 14 18:08:03 spectre /kernel: swap_pager: I/O error - pagein failed; blkno 336,size 4096, error 22 Nov 14 18:08:03 spectre /kernel: vm_fault: pager read error, pid 707 (sshd) Nov 14 18:08:03 spectre /kernel: swap_pager: I/O error - pagein failed; blkno 760,size 4096, error 22 Nov 14 18:08:03 spectre /kernel: vm_fault: pager read error, pid 707 (sshd) Nov 14 18:08:03 spectre /kernel: pid 707 (sshd), uid 0: exited on signal 11 Nov 14 18:10:47 spectre reboot: rebooted by dima Nov 14 18:10:48 spectre syslogd: exiting on signal 15 ---- Thank you -- best regards, Dmitry Mottl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 7:49: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (d211.dhcp212-26.cybercable.fr [212.198.26.211]) by hub.freebsd.org (Postfix) with ESMTP id C3C7437B419 for ; Fri, 16 Nov 2001 07:48:53 -0800 (PST) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id RAA47818; Fri, 16 Nov 2001 17:19:33 +0100 (CET) (envelope-from thierry@herbelot.com) Message-ID: <3BF5355E.84617BB2@herbelot.com> Date: Fri, 16 Nov 2001 16:48:46 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Dmitry Mottl Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: kernel error messages References: <3BF5335E.5080506@sinp.msu.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, this may be due to a bad block on your hard disk, in the swap partition (matt ?) TfH PS : anyway, the "error 22" comes from some code (happy RTFS'ing !) Dmitry Mottl wrote: > > Hi, All > > I got following error, while I say 'reboot'. > Please, help me with description, what's going on > Why 'pagein' and 'pageout' failed? > What is error 22? > > ---- > Nov 14 18:07:00 spectre /kernel: swap_pager: I/O error - pageout failed; > blkno 1552,size 16384, error 22 > Nov 14 18:08:03 spectre /kernel: swap_pager: I/O error - pagein failed; > blkno 336,size 4096, error 22 > Nov 14 18:08:03 spectre /kernel: vm_fault: pager read error, pid 707 (sshd) > Nov 14 18:08:03 spectre /kernel: swap_pager: I/O error - pagein failed; > blkno 760,size 4096, error 22 > Nov 14 18:08:03 spectre /kernel: vm_fault: pager read error, pid 707 (sshd) > Nov 14 18:08:03 spectre /kernel: pid 707 (sshd), uid 0: exited on signal 11 > Nov 14 18:10:47 spectre reboot: rebooted by dima > Nov 14 18:10:48 spectre syslogd: exiting on signal 15 > ---- > > Thank you > > -- > best regards, > Dmitry Mottl > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 8: 5:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by hub.freebsd.org (Postfix) with SMTP id 3FA8D37B405 for ; Fri, 16 Nov 2001 08:05:21 -0800 (PST) Received: from scummy.research.bell-labs.com ([135.104.2.10]) by dirty; Fri Nov 16 11:04:15 EST 2001 Received: from aura.research.bell-labs.com (aura.research.bell-labs.com [135.104.46.10]) by scummy.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id fAGG3UO82552 for ; Fri, 16 Nov 2001 11:03:31 -0500 (EST) Received: (from sandeepj@localhost) by aura.research.bell-labs.com (8.9.1/8.9.1) id LAA09239 for hackers@freebsd.org; Fri, 16 Nov 2001 11:03:30 -0500 (EST) Date: Fri, 16 Nov 2001 11:03:30 -0500 (EST) Message-Id: <200111161603.LAA09239@aura.research.bell-labs.com> From: sandeepj@research.bell-labs.com (Sandeep Joshi) To: hackers@freebsd.org Subject: Tracking down "BTX halted" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I changed the disklabels on a few SCSI disks and now I keep getting these "BTX halted" messages every time I reboot. They dont occur if I disconnect those disks. They occur even after I rewrite those labels. Its not dedicated mode or whatever now.. I am currently running 4.4-REL. I am willing to post the entire system configuration but it would be really nice if instead someone could tell me _HOW_ to determine the problem. A colleague tells me its possible to track the problem from the registers(cs,es,..) in the message dump. thanks -Sandeep To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 9:54:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id C7C4837B418 for ; Fri, 16 Nov 2001 09:54:22 -0800 (PST) Received: (qmail 9857 invoked from network); 16 Nov 2001 17:53:53 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 16 Nov 2001 17:53:53 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200111161603.LAA09239@aura.research.bell-labs.com> Date: Fri, 16 Nov 2001 09:54:21 -0800 (PST) From: John Baldwin To: (Sandeep Joshi) Subject: RE: Tracking down "BTX halted" Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 16-Nov-01 Sandeep Joshi wrote: > I changed the disklabels on a few SCSI disks and now > I keep getting these "BTX halted" messages every time > I reboot. > > They dont occur if I disconnect those disks. They occur > even after I rewrite those labels. Its not dedicated mode > or whatever now.. > > I am currently running 4.4-REL. > > I am willing to post the entire system configuration > but it would be really nice if instead someone could > tell me _HOW_ to determine the problem. > > A colleague tells me its possible to track the problem > from the registers(cs,es,..) in the message dump. Yes, especially if you provide that info in the e-mail. :) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 10:30:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 2A24737B418 for ; Fri, 16 Nov 2001 10:30:05 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fAGIWFo01305; Fri, 16 Nov 2001 10:32:16 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200111161832.fAGIWFo01305@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: sandeepj@research.bell-labs.com (Sandeep Joshi) Cc: hackers@freebsd.org Subject: Re: Tracking down "BTX halted" In-reply-to: Your message of "Fri, 16 Nov 2001 11:03:30 EST." <200111161603.LAA09239@aura.research.bell-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Nov 2001 10:32:15 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I changed the disklabels on a few SCSI disks and now > I keep getting these "BTX halted" messages every time > I reboot. The most likely cause of this is that you're messing up the disks to the point that your BIOS (probably your SCSI controller BIOS) is crashing when it tries to read them. > They dont occur if I disconnect those disks. They occur > even after I rewrite those labels. Its not dedicated mode > or whatever now.. You must have missed something. 8) > I am willing to post the entire system configuration > but it would be really nice if instead someone could > tell me _HOW_ to determine the problem. If the above guess is correct, you're looking at a BIOS bug. You might try updating your SCSI controller/motherboard BIOS, but there's no guarantee that'll fix the problem. The only real solution is to hot-plug the disks, camcontrol rescan, then dd zeroes over the heads of the disks and then re-lable them safely. > A colleague tells me its possible to track the problem > from the registers(cs,es,..) in the message dump. That would tell you where, exactly, the crash is occuring, and would make it possible to absolutely finger the culprit. What's the value of the cs register? If it's above 0xa000, then the BIOS is at fault. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 11: 7:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 11DF637B416 for ; Fri, 16 Nov 2001 11:07:20 -0800 (PST) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id WAA24126; Fri, 16 Nov 2001 22:13:17 +0300 (MSK) Message-Id: <200111161913.WAA24126@aaz.links.ru> Subject: Re: VIA 82231 South Bridge In-Reply-To: <200111131138.fADBcBw36497@freebsd.dk> from "Søren Schmidt" at "Nov 13, 1 12:38:11 pm" X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R To: sos@freebsd.dk Date: Fri, 16 Nov 2001 22:13:17 +0300 (MSK) Cc: hackers@FreeBSD.ORG From: "."@babolo.ru MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry for my error, the exact name of south bridge is VT8231 (from the manual I have in hands now) Søren Schmidt writes: [Charset ISO-8859-1 unsupported, filtering to ASCII...] > It seems .@babolo.ru wrote: > > > > Are there any planes to support > > > > VIA 82231 south bridge > > > > for UDMA33/66/100 ? > OK, support has been added to -current, MFC will follow later... I extracted patch --- sys/dev/ata/ata-dma.c Wed Nov 14 19:41:00 2001 +++ sys/dev/ata/ata-dma.c Wed Nov 14 20:03:34 2001 @@ -413,6 +413,7 @@ case 0x05711106: /* VIA 82C571, 82C586, 82C596, 82C686 */ if (ata_find_dev(parent, 0x06861106, 0x40) || + ata_find_dev(parent, 0x82311106, 0) || ata_find_dev(parent, 0x30741106, 0)) { /* 82C686b */ if (udmamode >= 5) { error = ata_command(scp, device, ATA_C_SETFEATURES, 0, 0, 0, --- sys/dev/ata/ata-all.c Tue Nov 13 20:36:33 2001 +++ sys/dev/ata/ata-all.c Thu Nov 15 21:05:57 2001 @@ -290,6 +290,7 @@ if (ata_find_dev(dev, 0x05961106, 0)) return "VIA 82C596 ATA33 controller"; if (ata_find_dev(dev, 0x06861106, 0x40) || + ata_find_dev(dev, 0x82311106, 0) || ata_find_dev(dev, 0x30741106, 0)) return "VIA 82C686 ATA100 controller"; if (ata_find_dev(dev, 0x06861106, 0)) from your changes for: 0test~/patch(12)>uname -a FreeBSD test.duty.ru 4.4-STABLE FreeBSD 4.4-STABLE #0: Mon Oct 29 20:08:36 MSK 2001 babolo@test.duty.ru:/tmp/babolo/usr/src/sys/garkin i386 and drives are 0test~/patch(13)>dmesg | grep ata [.....] ata0-master: success setting WDMA2 on VIA chip ad0: ATA-6 disk at ata0-master ad0: 78167MB [158816/16/63] at ata0-master WDMA2 ata1-master: success setting WDMA2 on VIA chip ad2: ATA-5 disk at ata1-master ad2: 73308MB [148945/16/63] at ata1-master tagged WDMA2 Both drives tested as UDMA in anoter system. Am I wrong? -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 11:34:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 040A437B416 for ; Fri, 16 Nov 2001 11:34:18 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id fAGJYVg44791; Fri, 16 Nov 2001 11:34:31 -0800 (PST) Date: Fri, 16 Nov 2001 11:34:31 -0800 (PST) From: Doug White To: Sandeep Joshi Cc: Subject: Re: Tracking down "BTX halted" In-Reply-To: <200111161603.LAA09239@aura.research.bell-labs.com> Message-ID: X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 16 Nov 2001, Sandeep Joshi wrote: > I changed the disklabels on a few SCSI disks and now > I keep getting these "BTX halted" messages every time > I reboot. Lemme guess, you're running them in 'dangerously dedicated' mode. There is a bug in Adaptec BIOSen that they will not tolerate DD disks. Put proper partition tables on them and they should behave. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 11:56: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net [209.226.175.25]) by hub.freebsd.org (Postfix) with ESMTP id 7F07737B417 for ; Fri, 16 Nov 2001 11:55:56 -0800 (PST) Received: from xena.gsicomp.on.ca ([199.243.144.157]) by tomts5-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011116195555.UQHI7882.tomts5-srv.bellnexxia.net@xena.gsicomp.on.ca>; Fri, 16 Nov 2001 14:55:55 -0500 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.1) with SMTP id fAGJlgW20175; Fri, 16 Nov 2001 14:47:42 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <015c01c16ed8$b357c6b0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Doug White" , "Sandeep Joshi" Cc: References: Subject: Re: Tracking down "BTX halted" Date: Fri, 16 Nov 2001 14:55:52 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Doug Write wrote: > > On Fri, 16 Nov 2001, Sandeep Joshi wrote: > > > I changed the disklabels on a few SCSI disks and now > > I keep getting these "BTX halted" messages every time > > I reboot. > > Lemme guess, you're running them in 'dangerously dedicated' mode. > > There is a bug in Adaptec BIOSen that they will not tolerate DD disks. Which controllers have this bug? I've got a whole bunch of 7880 and 79xx controllers with disks running in DD mode and never have had this problem. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 12:15: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id DECF637B405 for ; Fri, 16 Nov 2001 12:15:04 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.3) id fAGKEsX94905; Fri, 16 Nov 2001 21:14:54 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200111162014.fAGKEsX94905@freebsd.dk> Subject: Re: VIA 82231 South Bridge In-Reply-To: <200111161913.WAA24126@aaz.links.ru> To: "."@babolo.ru Date: Fri, 16 Nov 2001 21:14:54 +0100 (CET) Cc: hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems "."@babolo.ru wrote: > > It seems .@babolo.ru wrote: > > > > > Are there any planes to support > > > > > VIA 82231 south bridge > > > > > for UDMA33/66/100 ? > > OK, support has been added to -current, MFC will follow later... > I extracted patch > > --- sys/dev/ata/ata-dma.c Wed Nov 14 19:41:00 2001 > +++ sys/dev/ata/ata-dma.c Wed Nov 14 20:03:34 2001 > @@ -413,6 +413,7 @@ > > case 0x05711106: /* VIA 82C571, 82C586, 82C596, 82C686 */ > if (ata_find_dev(parent, 0x06861106, 0x40) || > + ata_find_dev(parent, 0x82311106, 0) || > ata_find_dev(parent, 0x30741106, 0)) { /* 82C686b */ > if (udmamode >= 5) { > error = ata_command(scp, device, ATA_C_SETFEATURES, 0, 0, 0, > --- sys/dev/ata/ata-all.c Tue Nov 13 20:36:33 2001 > +++ sys/dev/ata/ata-all.c Thu Nov 15 21:05:57 2001 > @@ -290,6 +290,7 @@ > if (ata_find_dev(dev, 0x05961106, 0)) > return "VIA 82C596 ATA33 controller"; > if (ata_find_dev(dev, 0x06861106, 0x40) || > + ata_find_dev(dev, 0x82311106, 0) || > ata_find_dev(dev, 0x30741106, 0)) > return "VIA 82C686 ATA100 controller"; > if (ata_find_dev(dev, 0x06861106, 0)) > > from your changes for: > 0test~/patch(12)>uname -a > FreeBSD test.duty.ru 4.4-STABLE FreeBSD 4.4-STABLE #0: Mon Oct 29 20:08:36 MSK 2001 babolo@test.duty.ru:/tmp/babolo/usr/src/sys/garkin i386 Uhm from that it seems the kernel is from Oct 29 which cannot be correct. Also I need the atapci? line from the dmesg to tell if it works... Are you sure you have recompiled your kernel, and installed it ? What does a ls -l /kernel say ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 16 12:41:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by hub.freebsd.org (Postfix) with SMTP id 93A2E37B416 for ; Fri, 16 Nov 2001 12:41:17 -0800 (PST) Received: from scummy.research.bell-labs.com ([135.104.2.10]) by dirty; Fri Nov 16 15:40:43 EST 2001 Received: from aura.research.bell-labs.com (aura.research.bell-labs.com [135.104.46.10]) by scummy.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id fAGKdwO05913 for ; Fri, 16 Nov 2001 15:39:58 -0500 (EST) Received: from research.bell-labs.com (IDENT:sandeepj@sandeepj-pcmh.research.bell-labs.com [135.104.47.90]) by aura.research.bell-labs.com (8.9.1/8.9.1) with ESMTP id PAA01845 for ; Fri, 16 Nov 2001 15:39:58 -0500 (EST) Message-ID: <3BF5799E.1DBCB8A0@research.bell-labs.com> Date: Fri, 16 Nov 2001 15:39:58 -0500 From: Sandeep Joshi X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: Tracking down "BTX halted" References: <200111161832.fAGIWFo01305@mass.dis.org> Content-Type: multipart/mixed; boundary="------------449EFD473C47C3D663301B3D" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------449EFD473C47C3D663301B3D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mike, Mike Smith wrote: > The only real solution is to hot-plug > the disks, camcontrol rescan, then dd zeroes over the heads of the disks > and then re-lable them safely. Yep, that method works for now. I was hoping its easy enough to crack this myself (with some online tips & references) but John Baldwin convinced me otherwise :-) So here's the entire configuration attached.. SUMMARY: The boot disk (ad0 in attachment) is not the problem. There are two other IBM SCSI disks attached to two Adaptec cards. Its these other two SCSI disks-da0,da1 which are empty and whose disklabels I played with. These cause a BTX error if they are plugged in during a boot. TIA, -Sandeep --------------449EFD473C47C3D663301B3D Content-Type: text/plain; charset=us-ascii; name="btx" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="btx" ----------------------------------------------------------- Error message when the SCSI disk is attached to the AIC-7896 SCSI BIOS v2.20s1B1 int=00000000 err=00000000 efl=00030246 eip=00001d29 eax=00000000 ebx=00000386 ecx=00000000 edx=00000000 esi=00009e3e edi=00001c09 ebp=0000038e esp=00000382 cs=c800 ds=0040 ed=9e3e fs=0000 gs=0000 ss=9e3e cs:eip=f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff ss:esp=00 00 3f 00 00 00 00 00-00 00 02 00 22 0a 00 c8 ----------------------------------------------------------- Error message when the SCSI disk is attached to the AHA2940U2W SCSI BIOS v2.20 : int=00000000 err=00000000 efl=00030246 eip=00001d29 eax=00000000 ebx=0000038e ecx=00000000 edx=00000000 esi=00009e3e edi=00001a3e ebp=00000396 esp=0000038a cs=cd80 ds=0040 ed=9e3e fs=0000 gs=0000 ss=9e3e cs:eip=f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff ss:esp=00 00 3f 00 00 00 00 00-00 00 02 00 df 09 80 cd ----------------------------------------------------------- Dmesg: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-RELEASE #2: Mon Nov 12 13:12:46 EST 2001 root@nstg7.research.bell-labs.com:/usr/src/sys/compile/NSTG7.SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (696.41-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x387fbff real memory = 805240832 (786368K bytes) avail memory = 778305536 (760064K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0535000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 12 entries at 0xc00fdf00 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard IOAPIC #0 intpin 19 -> irq 2 IOAPIC #0 intpin 21 -> irq 5 IOAPIC #0 intpin 16 -> irq 9 pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pcib3: at device 15.0 on pci1 IOAPIC #0 intpin 20 -> irq 10 pci2: on pcib3 pci2: (vendor=0x12ae, dev=0x0001) at 4.0 irq 10 ahc0: port 0x2000-0x20ff mem 0xf4100000-0xf4100fff irq 2 at device 12.0 on pci0 aic7896/97: Ultra2 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0x2400-0x24ff mem 0xf4101000-0xf4101fff irq 2 at device 12.1 on pci0 aic7896/97: Ultra2 Wide Channel B, SCSI Id=4, 32/255 SCBs fxp0: port 0x2c00-0x2c3f mem 0xf4000000-0xf40fffff,0xf4102000-0xf4102fff irq 5 at device 14.0 on pci0 fxp0: Ethernet address 00:90:27:e0:18:5d inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc2: port 0x2800-0x28ff mem 0xf4103000-0xf4103fff irq 9 at device 16.0 on pci0 aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/255 SCBs isab0: at device 18.0 on pci0 isa0: on isab0 atapci0: port 0x2c60-0x2c6f at device 18.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x2c40-0x2c5f irq 5 at device 18.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x1040-0x104f at device 18.3 on pci0 pci0: at 20.0 pcib1: on motherboard pci3: on pcib1 orm0: