From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 24 19:05:33 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 791B016A468 for ; Sun, 24 Jun 2007 19:05:33 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.freebsd.org (Postfix) with ESMTP id 1206E13C468 for ; Sun, 24 Jun 2007 19:05:33 +0000 (UTC) (envelope-from max@love2party.net) Received: from [88.66.59.187] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis), id 0ML2xA-1I2XCi3gkq-0003jr; Sun, 24 Jun 2007 20:52:57 +0200 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Sun, 24 Jun 2007 20:54:46 +0200 User-Agent: KMail/1.9.6 X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<%}*_BD U_or=\mOZf764&nYj=JYbR1PW0ud>|!~, , CPC.1-D$FG@0h3#'5"k{V]a~. X-Provags-ID: V01U2FsdGVkX1/hDzT82UId1tuqdX+ZIRXfdygX0y9CtIWH5A/ SmAwR08WnZzs/ltnq+MsVS1ZCdkQm+fKbYLDzGWFjRbtirEsVX EwqMNfsW/5uvB/6ccN5as9QiwW8sVAGoC4z5oGVz+I= Cc: freebsd-current@freebsd.org Subject: FreeBSD status reports due: July 7, 2007 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: monthly@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2007 19:05:33 -0000 --nextPart3409980.rt63ZT6IF6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello Everybody, it's that time again. We would like to remind everybody who has exciting=20 news to share to write a report about their project. This is a good way=20 to improve exposure of your work, receive feedback and help. As we are=20 closing in on 7.0 everybody is interested to know what's new - so please,=20 do tell! In addition we would like to gather public relations status reports as=20 well - did you run a FreeBSD conference or are you going to? Let the=20 world know how it went or why they should attend. On that note,=20 everybody remember the early bird deadline for EuroBSDCon? It's July 1=20 already! Looking forward to your reports. As always you can either use the=20 template or the generator CGI and mail the result to monthly@ by 07/07/07 http://www.freebsd.org/news/status/ http://www.freebsd.org/cgi/monthly.cgi http://www.freebsd.org/news/status/report-sample.xml =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart3409980.rt63ZT6IF6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQBGfr3+XyyEoT62BG0RAgV+AJ0ZISZzkJrT7sesnUaDS+QvRg6x6wCeLLzd s9cxE97z9G8fDPc5depTGAw= =tc4u -----END PGP SIGNATURE----- --nextPart3409980.rt63ZT6IF6-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 24 20:09:48 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7B8C216A469 for ; Sun, 24 Jun 2007 20:09:48 +0000 (UTC) (envelope-from sg@sg.org.ua) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id 3104F13C43E for ; Sun, 24 Jun 2007 20:09:48 +0000 (UTC) (envelope-from sg@sg.org.ua) Received: from [85.223.145.230] (helo=tbilisi.kiev.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1I2XdL-0009Mt-D5; Sun, 24 Jun 2007 22:20:28 +0300 Received: from rite.abacus.volia.net ([77.123.73.221] helo=[192.168.1.3]) by tbilisi.kiev.ua with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.66 (FreeBSD)) (envelope-from ) id 1I2XdL-000EAM-7p; Sun, 24 Jun 2007 22:20:27 +0300 In-Reply-To: <467CD36D.4020709@mersin.edu.tr> References: <467CD36D.4020709@mersin.edu.tr> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Alexander Mogilny Date: Sun, 24 Jun 2007 22:20:20 +0300 To: =?ISO-8859-1?Q?=D6zkan_KIRIK?= X-Mailer: Apple Mail (2.752.3) X-Scanner-Signature: 7b1a4900bea4ee3727a65c989d5962bc X-DrWeb-checked: yes X-SpamTest-Envelope-From: sg@sg.org.ua X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1169 [June 22 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {relay has no DNS name} X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 40 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release X-Mailman-Approved-At: Sun, 24 Jun 2007 20:11:53 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: 6.1 - amd64 arch. Hangs twice a day, how can i debug problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2007 20:09:48 -0000 On 23 =D0=B8=D1=8E=D0=BD=D1=8F 2007, at 11:01, =C3=96zkan KIRIK wrote: > I have a FreeBSD 6.1 - STABLE 200609 gateway have 3 up interfaces. > First one connected to 16Mbps Internet Connection, > Next onet connected to DMZ Zone (192.168.0.0/24 network) > The Last interface connected to Local network. > > this system hangs twice a day. Keyboard doesnt work, everything =20 > locks, no network reponse! > For a quick solution i wrote a crontab that reboots system at 20.00 =20= > PM & 06.00 AM. > > How can I find the problem which hangs system? Is there any method =20 > for this. > Or any known bug reports at this release ? > > a note: "if i enable hyper threading & SMP, system hangs 6 times a =20 > day" > > Waiting for your suggestions, > The first suggestion would be to cvsup RELENG_6_1 or RELENG_6_2 =20 brunch instead of using RELENG_6 brunch. The reason is that RELENG_6 brunch contains all MFCs =20= before next FreeBSD version is released and that is why you can experience yourself all =20 mid-release problems. --=20 AIM-UANIC | AIM-RIPE +-----[ FreeBSD ]-----+ Alexander Mogilny | The Power to Serve! | <> sg@sg.org.ua +---------------------+= From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 24 23:32:25 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1942516A469 for ; Sun, 24 Jun 2007 23:32:25 +0000 (UTC) (envelope-from turgeon.martin@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 894A313C4BB for ; Sun, 24 Jun 2007 23:32:24 +0000 (UTC) (envelope-from turgeon.martin@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so1501474pyb for ; Sun, 24 Jun 2007 16:32:23 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=Umea9W10ESxEMmTp3QPvMwUVAL2EEPgHy62QuBLZ+qZs3In4nmovtbKxGVshKSXUH6k8ZgKZXwaj7qmn9QHgnUdLaj8ILjGy1qDS6khoiEXFoRbcRW80iJ5VnEDTpfvDHP6/423fGoq/8/LpnadVABcYGphUX6lVJUG/gfsF3DY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=FfnD0epae2kcWwRFCc/VkiQcNL5UX52PT5ELLFXYFfMRe1MWm4Wf81vAZlr5X8o7c5heTtDoSuO0Os4PIQXjeKI6l0ZRcukCm5twcBL6/nRuxpax7HAQg38D0ZJd9wt/IEmb81psvUaAI0+iH2ayznJN6nVJ9xIYMidZo4KcoAo= Received: by 10.35.121.12 with SMTP id y12mr1000060pym.1182727943855; Sun, 24 Jun 2007 16:32:23 -0700 (PDT) Received: from ?192.168.3.200? ( [69.70.75.162]) by mx.google.com with ESMTP id f45sm8281478pyh.2007.06.24.16.32.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 24 Jun 2007 16:32:23 -0700 (PDT) Message-ID: <467EFF06.6020902@gmail.com> Date: Sun, 24 Jun 2007 19:32:22 -0400 From: Martin Turgeon User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2007 23:32:25 -0000 Hi, I recently installed AMD64 6.2 Release on 2 PowerEdge servers, both with dual core Xeon (3070 and 5110). I noticed when I was updating the sources that it was compiling as an Athlonxp by default. I was wondering if I should change the CPUTYPE in make.conf to something else. I read at some places that it is not recommended because it could cause problems but I thought it would be interesting to start the debate here. Please note that I would prefer not to go with the -STABLE or -CURRENT branch because these a going to be essential productions servers. Thank you for your opinions, Martin From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 02:28:00 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8138316A400 for ; Mon, 25 Jun 2007 02:28:00 +0000 (UTC) (envelope-from angus@aggyb.org) Received: from aggyb.org (87-194-8-28.bethere.co.uk [87.194.8.28]) by mx1.freebsd.org (Postfix) with ESMTP id EB75D13C43E for ; Mon, 25 Jun 2007 02:27:59 +0000 (UTC) (envelope-from angus@aggyb.org) Received: from localhost (localhost.org [127.0.0.1]) by aggyb.org (Postfix) with ESMTP id 21E3D3D183D for ; Mon, 25 Jun 2007 03:31:06 +0100 (BST) X-Virus-Scanned: amavisd-new at aggyb.org Received: from aggyb.org ([127.0.0.1]) by localhost (aggyb.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KWGZuv+aHlsI for ; Mon, 25 Jun 2007 03:31:00 +0100 (BST) Received: from [192.168.1.10] (agb.studnet [192.168.1.10]) by aggyb.org (Postfix) with ESMTP id 38D9A3D1835 for ; Mon, 25 Jun 2007 03:31:00 +0100 (BST) Message-ID: <467F2411.7070709@aggyb.org> Date: Mon, 25 Jun 2007 03:10:25 +0100 From: Angus Barrow User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: multipart/mixed; boundary="------------020502060506000100030004" Subject: libelf question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 02:28:00 -0000 This is a multi-part message in MIME format. --------------020502060506000100030004 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi there, I'm trying to develop a BSD licensed version of the ar utility using the new libelf library as this seems to be listed on the project ideas page but doesn't seem to be being worked on. I've started off simply trying to get a toc printed for the archive but for some reason the time-stamp seems to be coming back wrong for the contents of the archives. The code in question uses libelf to fetch a struct for each entry in an archive and it prints out the data as a table: ... Elf_Arhdr *arh; while ((object = elf_begin(fd, ELF_C_READ, archive)) != NULL) { if ((arh = elf_getarhdr(object)) == NULL) errx(EX_SOFTWARE, "elf_getarhdr() failed: %s.", elf_errmsg(-1)); ... char timestring[20]; time_t timet=arh->ar_date; strftime(timestring, sizeof(timestring), "%b %e %H:%M %Y", gmtime(&timet)); The time shown in arh->ar_date (this is the struct that the libelf library provides for each entry in the ar archive) seems to have a negative value (using the GNU ar the date is Jun 3 13:09 2007, I've loaded the program in gdb also and this seems to suggest the problem is with the library: 30 time_t timet=arh->ar_date; (gdb) n 31 strftime(timestring, sizeof(timestring), "%b %e %H:%M %Y", gmtime(&timet)); (gdb) n ... (gdb) print timet $1 = -1515870811 (gdb) print timestring $2 = "Dec 19 04:46 1921\000\000" My question is, should I log a PR about this or is there something obvious that I'm doing wrong here. I'm totally new to writing anything serious in C as all my uni courses use Java and VB.net etc. Please find the program attached in full. Thanks for any advice. Angus Barrow --------------020502060506000100030004 Content-Type: text/plain; name="print.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="print.c" #include #include #include #include #include #include void prettyMode(int, char*); int printToc(int fd, Elf *archive, int argc, char *argv, int VERBOSE_FLAG) { Elf *object; printf("(DBG)\tprint.c:printToc(Elf, char) - argc=%d verb=%d\n",argc, VERBOSE_FLAG); Elf_Kind type = elf_kind(archive); if(type!=ELF_K_AR) errx(EX_DATAERR, "Type of object is not ELF_K_AR\n"); Elf_Arhdr *arh; while ((object = elf_begin(fd, ELF_C_READ, archive)) != NULL) { if ((arh = elf_getarhdr(object)) == NULL) errx(EX_SOFTWARE, "elf_getarhdr() failed: %s.", elf_errmsg(-1)); if(VERBOSE_FLAG!=1) { printf("%s\n", arh->ar_name); } else { char timestring[20]; time_t timet=arh->ar_date; strftime(timestring, sizeof(timestring), "%b %e %H:%M %Y", gmtime(&timet)); char perms[10]="---------\0"; prettyMode(arh->ar_mode, perms); printf("%s %u/%u %8u %s %s\n", perms, arh->ar_uid, arh->ar_gid, arh->ar_size, timestring, arh->ar_name); } elf_next(object); elf_end(object); } elf_end(archive); return 0; } void prettyMode(int mode, char *string) { /* There must be a better way or a library for this!*/ if(strlen(string)<9) { printf("Urgh, that is not good!\nGive me a longer array!"); return; } if((mode & 0400)==0400) string[0]='r'; if((mode & 0200)==0200) string[1]='w'; if((mode & 0100)==0100) string[2]='x'; if((mode & 040)==040) string[3]='r'; if((mode & 020)==020) string[4]='w'; if((mode & 010)==010) string[5]='x'; if((mode & 04)==04) string[6]='r'; if((mode & 02)==02) string[7]='w'; if((mode & 01)==01) string[8]='x'; } --------------020502060506000100030004 Content-Type: text/plain; name="ar.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ar.c" /*- * Copyright (c) 2007 Angus Barrow * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice unmodified, this list of conditions, and the following * disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. * IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. */ #include #include #include #include #include #include #include #include static int VERBOSE_FLAG; int tflag; /* * This is a BSD licenced attempt at the ar program as in POSIX 1003.1. * It makes use of the Elf and GElf API's in FreeBSD 7-CURRENT. */ int main(int argc, char *argv[]) { int ch; /* Decide how we've been invoked and try to decide what to do! */ VERBOSE_FLAG=-1; while ((ch = getopt(argc, argv, "htv")) != -1) switch (ch) { case 't': tflag = 1; break; case 'v': VERBOSE_FLAG=1; printf("(DBG)\tVerbose flag set\n"); break; case 'h': printf("(DBG)\tDisplay help\n"); /* FLOWS THROUGH */ default: usage(); /* NOTREACHED */ } argc-=optind; argv+=optind; printf("(DBG)\tFile to open is: %s\n", *argv); /* Open file */ int fd; if ((fd = open(*argv, O_RDONLY, 0)) < 0) err(EX_NOINPUT, "open \%s\" failed", *argv); /* Open library */ if (elf_version(EV_CURRENT) == EV_NONE) errx(EX_SOFTWARE, "ELF library initialization failed: %s", elf_errmsg(-1)); /* Open elf object/archive */ Elf *elf; if ((elf = elf_begin(fd, ELF_C_READ, NULL)) == NULL) errx(EX_SOFTWARE, "elf_begin() failed: %s.", elf_errmsg(-1)); if(tflag==1) { printToc(fd, elf, argc, argv, VERBOSE_FLAG); } close(fd); return 0; } int usage() { printf("Options are:\nh\t-\tDisplay this help!\nt\t-\tDisplay TOC\nv\t-\tEnable verbose mode\n"); exit(0); } --------------020502060506000100030004-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 03:41:02 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E9EFF16A400; Mon, 25 Jun 2007 03:41:02 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.freebsd.org (Postfix) with ESMTP id C84E713C45B; Mon, 25 Jun 2007 03:41:02 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l5P3f250028707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 24 Jun 2007 20:41:02 -0700 X-Auth-Received: from [192.168.10.45] (c-24-10-12-194.hsd1.ca.comcast.net [24.10.12.194]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l5P3esnZ016456 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 24 Jun 2007 20:41:01 -0700 Message-ID: <467F3946.6020703@u.washington.edu> Date: Sun, 24 Jun 2007 20:40:54 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.4 (X11/20070621) MIME-Version: 1.0 To: Martin Turgeon References: <467EFF06.6020902@gmail.com> In-Reply-To: <467EFF06.6020902@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.24.202333 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 03:41:03 -0000 Martin Turgeon wrote: > Hi, > > I recently installed AMD64 6.2 Release on 2 PowerEdge servers, both with > dual core Xeon (3070 and 5110). I noticed when I was updating the > sources that it was compiling as an Athlonxp by default. I was wondering > if I should change the CPUTYPE in make.conf to something else. I read at > some places that it is not recommended because it could cause problems > but I thought it would be interesting to start the debate here. Please > note that I would prefer not to go with the -STABLE or -CURRENT branch > because these a going to be essential productions servers. > > Thank you for your opinions, > > Martin It's preferred to be nocona for 64-bit support (EMT-64 support to be exact) and prescott for 32-bit only support. There should be a core2duo CPUTYPE rolling around the corner in the near future IIRC, but that will most likely be in gcc 4.3, which I believe it slated for being stable 1~1.5 years from now. -Garrett From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 05:01:17 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ABBDC16A400 for ; Mon, 25 Jun 2007 05:01:17 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 2808B13C483 for ; Mon, 25 Jun 2007 05:01:17 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l5P4PZH7061456; Sun, 24 Jun 2007 21:25:35 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <467F43BF.5050900@freebsd.org> Date: Sun, 24 Jun 2007 21:25:35 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Angus Barrow References: <467F2411.7070709@aggyb.org> In-Reply-To: <467F2411.7070709@aggyb.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: libelf question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 05:01:17 -0000 Angus Barrow wrote: > I'm trying to develop a BSD licensed version of the ar utility using > the new libelf library ... > > The time shown in arh->ar_date (this is the struct that the libelf > library provides for each entry in the ar archive) seems to have a negative > value (using the GNU ar the date is Jun 3 13:09 2007.... Kai Wang recently added 'ar' support to libarchive/bsdtar; what does 'tar -tv' say? Note: You'll need a recent 7-CURRENT system for this or you can install libarchive/bsdtar from the most recent development snapshot on http://people.freebsd.org/~kientzle/ Tim Kientzle From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 05:08:10 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D974B16A469 for ; Mon, 25 Jun 2007 05:08:10 +0000 (UTC) (envelope-from lstewart@room52.net) Received: from swin.edu.au (gpo5.cc.swin.edu.au [136.186.1.225]) by mx1.freebsd.org (Postfix) with ESMTP id 71FBE13C483 for ; Mon, 25 Jun 2007 05:08:10 +0000 (UTC) (envelope-from lstewart@room52.net) Received: from [136.186.229.95] (lstewart.caia.swin.edu.au [136.186.229.95]) by swin.edu.au (8.13.6.20060614/8.13.1) with ESMTP id l5P57vWb030701; Mon, 25 Jun 2007 15:07:58 +1000 Message-ID: <467F4DE5.3020001@room52.net> Date: Mon, 25 Jun 2007 15:08:53 +1000 From: Lawrence Stewart User-Agent: Thunderbird 1.5.0.9 (X11/20070123) MIME-Version: 1.0 To: Ivan Voras References: <4649349D.4060101@room52.net> <200705150847.38838.marc.loerner@hob.de> <46499491.2010205@room52.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.1.9 X-Spam-Checker-Version: SpamAssassin 3.1.9 (2007-02-13) on gpo5.cc.swin.edu.au Cc: James Healy , freebsd-hackers@freebsd.org Subject: Re: Writing a plain text file to disk from kernel space X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 05:08:10 -0000 Ivan Voras wrote: > Lawrence Stewart wrote: > >> I'll have a play around and report back to the list what I find for >> archival purposes. > > Please do, and also consider writing a short and instructive tutorial > on it! Many people have asked this same question without a > to-the-point answer. Hi all, Finally managed to wrap up the code and documentation for the little module I've been working on at work. We've released the SIFTR (Statistical Information For TCP Research) code under a BSD licence, and hope some of you may find it useful. It's a tool mostly aimed at the TCP research community, but perhaps someone out there might find another use for all or part of the code. We've also made a prototype module (named filewriter) available that specifically demonstrates file writing from within the kernel. It should hopefully provide a useful reference implementation for anyone wanting to write files from within the kernel. As promised, we've also made a technical report available that documents what we learnt whilst transitioning from noob kernel hackers to guys that have a (partial) clue. The report is certainly a useful reference for us and people working at our research centre. We hope it will also be a useful reference for the community to point people at who are new to kernel hacking. The report's title is "An Introduction to FreeBSD 6 Kernel Hacking" and has been released as Centre for Advanced Internet Architectures Technical Report 070622A. The code distributions and technical report can be grabbed from http://caia.swin.edu.au/urp/newtcp/ under the "Tools" and "Papers" sections respectively. Many thanks to all of you who helped us make it to the finishing post with your invaluable information and insights. If you find a use for the code or any bugs in the code/documentation, we'd be very happy to hear from you. Cheers, Lawrence PS Is there anywhere else other than hackers@, net@, fs@ and doc@ that might be interested in this information? From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 05:40:13 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F17F216A41F for ; Mon, 25 Jun 2007 05:40:13 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.247]) by mx1.freebsd.org (Postfix) with ESMTP id AF61A13C468 for ; Mon, 25 Jun 2007 05:40:13 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so336774anc for ; Sun, 24 Jun 2007 22:40:13 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ApOiWv9bF3QTXD1m8sho/6pW6l+3AdReFNLHTB/F0VJBQPFDMwz+1D4pS4SFoZ+JUYi7TzOQzFxHAX7ctedbnY0O4kLuuoPH9FwNret12cAHOpbBsCKrY/d+GJ6JUo5C94vYf1pI7CJae60EDfTG+zJYF37JDwW0MxFJlVqzXWY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=E+tP/vsAIewVIRkTslv0pWrrKcWfQACXZZXEn1LZL9ASNGtWzbGVKtMtErfWhhXZ6TonvIsv2eMBmpbqNt47Vrpbh3mCGb/gDLJ+KLAFjy3gZWKdHhjhbtFnW3oJADfVXlVfZ0SBBN29ozMG+DuqWj5wQrFGo4wzgSdmS6kRWRM= Received: by 10.100.91.6 with SMTP id o6mr2939935anb.1182750012626; Sun, 24 Jun 2007 22:40:12 -0700 (PDT) Received: by 10.100.9.14 with HTTP; Sun, 24 Jun 2007 22:40:12 -0700 (PDT) Message-ID: <499c70c0706242240n1c5f3177q7645ae97387db701@mail.gmail.com> Date: Mon, 25 Jun 2007 08:40:12 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "Martin Turgeon" In-Reply-To: <467EFF06.6020902@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <467EFF06.6020902@gmail.com> Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 05:40:14 -0000 On 6/25/07, Martin Turgeon wrote: > Hi, > > I recently installed AMD64 6.2 Release on 2 PowerEdge servers, both with > dual core Xeon (3070 and 5110). I noticed when I was updating the > sources that it was compiling as an Athlonxp by default. I was wondering > if I should change the CPUTYPE in make.conf to something else. I read at > some places that it is not recommended because it could cause problems > but I thought it would be interesting to start the debate here. Please > note that I would prefer not to go with the -STABLE or -CURRENT branch > because these a going to be essential productions servers. > > Thank you for your opinions, > > Martin Since I use FreeBSD 7.0 AMD64 which is stable now and it's frozen for making RELENG_7 I didn't set the CPUTYPE in the make.conf , so I wonder how come you got athlon-xp cpu arch and I didn't see GCC 4.2 doing it in my server. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 06:20:02 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E55ED16A41F; Mon, 25 Jun 2007 06:20:02 +0000 (UTC) (envelope-from yuri@darklight.org.ru) Received: from darklight.org.ru (darklight.org.ru [194.186.18.14]) by mx1.freebsd.org (Postfix) with ESMTP id 3687C13C448; Mon, 25 Jun 2007 06:19:14 +0000 (UTC) (envelope-from yuri@darklight.org.ru) Received: from darklight.org.ru (yuri@darklight.org.ru [127.0.0.1]) by darklight.org.ru (8.14.1/8.14.1) with ESMTP id l5P66sdg059767; Mon, 25 Jun 2007 10:06:55 +0400 (MSD) (envelope-from yuri@darklight.org.ru) Received: (from yuri@localhost) by darklight.org.ru (8.14.1/8.14.1/Submit) id l5P66m2a059589; Mon, 25 Jun 2007 10:06:48 +0400 (MSD) (envelope-from yuri@darklight.org.ru) Date: Mon, 25 Jun 2007 10:06:48 +0400 From: Yuri Pankov To: Abdullah Ibn Hamad Al-Marri Message-ID: <20070625060648.GB1109@darklight.org.ru> References: <467EFF06.6020902@gmail.com> <499c70c0706242240n1c5f3177q7645ae97387db701@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=SHA1; protocol="application/pgp-signature"; boundary="H+4ONPRPur6+Ovig" Content-Disposition: inline In-Reply-To: <499c70c0706242240n1c5f3177q7645ae97387db701@mail.gmail.com> User-Agent: Mutt/1.5.15 (2007-04-06) X-Greylist: Sender is SPF-compliant, not delayed by milter-greylist-3.0 (darklight.org.ru [127.0.0.1]); Mon, 25 Jun 2007 10:06:55 +0400 (MSD) Cc: freebsd-hackers@freebsd.org, Martin Turgeon , freebsd-amd64@freebsd.org Subject: Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 06:20:03 -0000 --H+4ONPRPur6+Ovig Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 25, 2007 at 08:40:12AM +0300, Abdullah Ibn Hamad Al-Marri wrote: > On 6/25/07, Martin Turgeon wrote: > > Hi, > > > > I recently installed AMD64 6.2 Release on 2 PowerEdge servers, both with > > dual core Xeon (3070 and 5110). I noticed when I was updating the > > sources that it was compiling as an Athlonxp by default. I was wondering > > if I should change the CPUTYPE in make.conf to something else. I read at > > some places that it is not recommended because it could cause problems > > but I thought it would be interesting to start the debate here. Please > > note that I would prefer not to go with the -STABLE or -CURRENT branch > > because these a going to be essential productions servers. > > > > Thank you for your opinions, > > > > Martin >=20 > Since I use FreeBSD 7.0 AMD64 which is stable now and it's frozen for > making RELENG_7 I didn't set the CPUTYPE in the make.conf , so I > wonder how come you got athlon-xp cpu arch and I didn't see GCC 4.2 > doing it in my server. >=20 >=20 > --=20 > Regards, >=20 > -Abdullah Ibn Hamad Al-Marri > Arab Portal > http://www.WeArab.Net/ Used when compiling lib32 shim libraries, I guess. Yuri --H+4ONPRPur6+Ovig Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGf1t4eoAklVFrLdgRAgrdAKCPhYIw03q6N+NThAh+klXgDgxA/wCfYfHK he40o9boa4j+gECYza7F8hA= =7V3T -----END PGP SIGNATURE----- --H+4ONPRPur6+Ovig-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 09:11:23 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA65916A469 for ; Mon, 25 Jun 2007 09:11:23 +0000 (UTC) (envelope-from bkoenig@alpha-tierchen.de) Received: from mail.liberty-hosting.de (mail.smartterra.de [195.225.132.203]) by mx1.freebsd.org (Postfix) with ESMTP id 64E1313C4B8 for ; Mon, 25 Jun 2007 09:11:23 +0000 (UTC) (envelope-from bkoenig@alpha-tierchen.de) Received: from mail.liberty-hosting.de ([195.225.132.203]) by localhost (liberty-mail [195.225.132.203]) (amavisd-new, port 10024) with ESMTP id 47601-06 for ; Mon, 25 Jun 2007 10:56:41 +0200 (CEST) Received: from home.alpha-tierchen.de (port-212-202-42-120.dynamic.qsc.de [212.202.42.120]) by mail.liberty-hosting.de (Postfix) with ESMTP id 95AFB3E96E7 for ; Mon, 25 Jun 2007 10:56:41 +0200 (CEST) Received: from webmail.alpha-tierchen.de (localhost [127.0.0.1]) by home.alpha-tierchen.de (Postfix) with ESMTP id 58FA445046 for ; Mon, 25 Jun 2007 10:54:06 +0200 (CEST) Received: from 192.168.1.2 (SquirrelMail authenticated user bkoenig) by webmail.alpha-tierchen.de with HTTP; Mon, 25 Jun 2007 10:54:06 +0200 (CEST) Message-ID: <1500.192.168.1.2.1182761646.squirrel@webmail.alpha-tierchen.de> Date: Mon, 25 Jun 2007 10:54:06 +0200 (CEST) From: =?iso-8859-1?Q?Bj=F6rn_K=F6nig?= To: hackers@freebsd.org User-Agent: SquirrelMail/1.4.10a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at mail.smartterra.de Cc: Subject: end, edata, etext issues X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 09:11:23 -0000 Hello, I'm playing with FreeBSD on ARM. I noticed that sbrk(2) doesn't work properly on this architecture. I still don't understand the whole process of the initialisation of end, edata and etext. There are some oddities that confuse me even more. Let me make an example: 1 #include 2 extern end; 3 extern edata; 4 int main() { 5 printf("edata: %08x\n", edata); 6 printf("end: %08x\n", end); 7 printf("sbrk(0): %08x\n", sbrk(0)); 8 return (0); 9 } > cc test.c && ./a.out edata: 00000000 end: 00000000 sbrk(0): ffffffff This is obviously not correct and the reason why program that rely sbrk(2) are broken. I added the following code: 1 .data 2 .globl curbrk 3 curbrk: 4 .word end and compiled the whole thing again: > cc test.c curbrk.S && ./a.out edata: 00000000 end: 0001070c sbrk(0): 00100000 and it seems to work. Another strange thing is that if I don't access "edata", e.g. leave printf("edata: %08x\n", edata); away, then sbrk still works, but "end" is zero. In case I don't access "edata" or "end" at all I'll get a bus error. Is there somebody who can tell me how end depends on the presence curbrk and edata in this example? Regards Björn From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 10:17:13 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2CDFB16A400 for ; Mon, 25 Jun 2007 10:17:13 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id 093C713C489 for ; Mon, 25 Jun 2007 10:17:13 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: by wa-out-1112.google.com with SMTP id j37so1810711waf for ; Mon, 25 Jun 2007 03:17:12 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iYflukfhB7Mc5YGSkd7wuMIAx3nu1y0+XuSHAPeM+ruRCn4fFsw1ef1knrGIdKFQGToLoxcJh5GviMdLCNozyewv70UY+CGhspc4mHgvoEhQtXSQ253xJmqCIQcpu/WlWLCumo4Vo2CzuGt2YVQMbqUQX+IHa1FI/iq0B8O8lkU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=p+eqXCLVXKEdwQKrh515zUXN6mPOsOWes9OhCMLKNgyrlUal/Du3Q5wiPi36iuKaGVYfRjJHsH4t6N1Em1NVS+WNg5VKEHBdea/Am1MOObHs4djPCk6GgvVUUw6E6HA28H2D9E9M20r9Dwo/OJTEtZjo3J61YPlxdLyBBp4LauU= Received: by 10.114.209.1 with SMTP id h1mr5266757wag.1182765000929; Mon, 25 Jun 2007 02:50:00 -0700 (PDT) Received: by 10.114.75.5 with HTTP; Mon, 25 Jun 2007 02:50:00 -0700 (PDT) Message-ID: Date: Mon, 25 Jun 2007 02:50:00 -0700 From: "Jack L." To: "Martin Turgeon" In-Reply-To: <467EF0C1.1010609@optiksecurite.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <467EF0C1.1010609@optiksecurite.com> X-Mailman-Approved-At: Mon, 25 Jun 2007 11:33:16 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 10:17:13 -0000 On 6/24/07, Martin Turgeon wrote: > Hi, > > I recently installed AMD64 6.2 Release on 2 PowerEdge servers, both with > dual core Xeon (3070 and 5110). I noticed when I was updating the > sources that it was compiling as an Athlonxp by default. I was wondering > if I should change the CPUTYPE in make.conf to something else. I read at > some places that it is not recommended because it could cause problems > but I thought it would be interesting to start the debate here. Please > note that I would prefer not to go with the -STABLE or -CURRENT branch > because these a going to be essential productions servers. > > Thank you for your opinions, > > Martin I use nocona. That should be the correct one. From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 12:24:11 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B057316A41F; Mon, 25 Jun 2007 12:24:11 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 55C4A13C45D; Mon, 25 Jun 2007 12:24:11 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1I2nbz-000Nqm-Sv; Mon, 25 Jun 2007 15:24:07 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-current@FreeBSD.ORG In-reply-to: Your message of Mon, 25 Jun 2007 14:49:29 +0300 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Jun 2007 15:24:07 +0300 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org Subject: KSE was Re: open/close/ioctl api change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 12:24:11 -0000 > actually it's the struct thread *tp where my problems are, > this code works fine under 6.2, and did work till some days ago under current. > > static int > iscsi_open(struct cdev *dev, int flags, int otype, struct thread *td) > { > ... > debug(3, "td->td_proc=%p", td->td_proc); > debug(3, "td->td_proc->p_pid=%d pid=%d", > td->td_proc->p_pid, curproc->p_pid); > ... > > the first debug prints out td->td_proc=0 and the next one panics. found the problem, 'option KSE' which is defined now in DEFAULTS, and i'm compiling a module! which does not include DEFAULTS! danny From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 12:28:16 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ABB2A16A468 for ; Mon, 25 Jun 2007 12:28:16 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6A68D13C484 for ; Mon, 25 Jun 2007 12:28:16 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1I2n4U-000LwJ-Uo; Mon, 25 Jun 2007 14:49:30 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Jun 2007 14:49:29 +0300 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org, Scott Long Subject: open/close/ioctl api change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 12:28:16 -0000 actually it's the struct thread *tp where my problems are, this code works fine under 6.2, and did work till some days ago under current. static int iscsi_open(struct cdev *dev, int flags, int otype, struct thread *td) { ... debug(3, "td->td_proc=%p", td->td_proc); debug(3, "td->td_proc->p_pid=%d pid=%d", td->td_proc->p_pid, curproc->p_pid); ... the first debug prints out td->td_proc=0 and the next one panics. danny From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 15:19:46 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6709C16A41F for ; Mon, 25 Jun 2007 15:19:46 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 2AC0B13C48A for ; Mon, 25 Jun 2007 15:19:46 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id CA51620AF; Mon, 25 Jun 2007 17:19:41 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id BD60E20AB; Mon, 25 Jun 2007 17:19:41 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id 8814E5C77; Mon, 25 Jun 2007 17:19:41 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Angus Barrow References: <467F2411.7070709@aggyb.org> Date: Mon, 25 Jun 2007 17:19:41 +0200 In-Reply-To: <467F2411.7070709@aggyb.org> (Angus Barrow's message of "Mon\, 25 Jun 2007 03\:10\:25 +0100") Message-ID: <867ipsnjsi.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: libelf question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 15:19:46 -0000 Angus Barrow writes: > 30 time_t timet=3Darh->ar_date; > (gdb) n > 31 strftime(timestring, sizeof(timestring), "%b %e %H:%M %Y", > gmtime(&timet)); > (gdb) n > ... > (gdb) print timet > $1 =3D -1515870811 (gdb) p/x -1515870811 $1 =3D 0xa5a5a5a5 from malloc(3): J Each byte of new memory allocated by malloc(), realloc() or reallocf() will be initialized to 0xa5. All memory returned by free(), realloc() or reallocf() will be initialized to 0x5a. This is intended for debugging and will impact performance neg= a- tively. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 16:58:25 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D20D216A421 for ; Mon, 25 Jun 2007 16:58:25 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outB.internet-mail-service.net (outB.internet-mail-service.net [216.240.47.225]) by mx1.freebsd.org (Postfix) with ESMTP id C068313C46C for ; Mon, 25 Jun 2007 16:58:25 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 25 Jun 2007 09:58:25 -0700 Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 059C7125B43; Mon, 25 Jun 2007 09:58:24 -0700 (PDT) Message-ID: <467FF435.6050108@elischer.org> Date: Mon, 25 Jun 2007 09:58:29 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: KSE was Re: open/close/ioctl api change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 16:58:25 -0000 Danny Braniss wrote: >> actually it's the struct thread *tp where my problems are, >> this code works fine under 6.2, and did work till some days ago under current. >> >> static int >> iscsi_open(struct cdev *dev, int flags, int otype, struct thread *td) >> { >> ... >> debug(3, "td->td_proc=%p", td->td_proc); >> debug(3, "td->td_proc->p_pid=%d pid=%d", >> td->td_proc->p_pid, curproc->p_pid); >> ... >> >> the first debug prints out td->td_proc=0 and the next one panics. > > found the problem, 'option KSE' which is defined now in DEFAULTS, > and i'm compiling a module! which does not include DEFAULTS! > even so it shouldnt' happen.. > danny > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 17:45:39 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F3E2116A46F for ; Mon, 25 Jun 2007 17:45:38 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu (math.missouri.edu [128.206.184.200]) by mx1.freebsd.org (Postfix) with ESMTP id C800E13C44B for ; Mon, 25 Jun 2007 17:45:38 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from [128.206.184.213] (cauchy.math.missouri.edu [128.206.184.213]) by math.missouri.edu (8.13.1/8.13.1) with ESMTP id l5PHjcDb084849 for ; Mon, 25 Jun 2007 12:45:38 -0500 (CDT) (envelope-from stephen@math.missouri.edu) Message-ID: <467FFF41.10204@math.missouri.edu> Date: Mon, 25 Jun 2007 12:45:37 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.4) Gecko/20070623 SeaMonkey/1.1.2 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <467EF0C1.1010609@optiksecurite.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88/3523/Mon Jun 25 09:30:33 2007 on math.missouri.edu X-Virus-Status: Clean Subject: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 17:45:39 -0000 Jack L. wrote: > On 6/24/07, Martin Turgeon wrote: >> Hi, >> >> I recently installed AMD64 6.2 Release on 2 PowerEdge servers, both with >> dual core Xeon (3070 and 5110). I noticed when I was updating the >> sources that it was compiling as an Athlonxp by default. I was wondering >> if I should change the CPUTYPE in make.conf to something else. I read at >> some places that it is not recommended because it could cause problems >> but I thought it would be interesting to start the debate here. Please >> note that I would prefer not to go with the -STABLE or -CURRENT branch >> because these a going to be essential productions servers. >> >> Thank you for your opinions, >> >> Martin > I use nocona. That should be the correct one. I know I am hijacking the thread a bit - but: In general, how does one decide which CPUTYPE to use? The connection between the options for CPUTYPE and the output of dmesg is not so obvious to me. I looked at the features advertised by dmesg (which in my case included SSE3) and then reverse engineered bsd.cpu.mk to figure out I should be using "prescott," but I am hoping I figured it out the hard way. Also, does setting CPUTYPE make a lot of difference to performance? Right now I have no CPUTYPE set at all. Thanks, Stephen From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 18:21:29 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D8D0B16A400 for ; Mon, 25 Jun 2007 18:21:29 +0000 (UTC) (envelope-from stsp@stsp.name) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by mx1.freebsd.org (Postfix) with ESMTP id 6A88B13C45D for ; Mon, 25 Jun 2007 18:21:29 +0000 (UTC) (envelope-from stsp@stsp.name) X-Envelope-From: stsp@stsp.name X-Envelope-To: Received: from stsp.lan (stsp.in-vpn.de [217.197.85.96]) (authenticated bits=128) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id l5PILQfQ001568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 25 Jun 2007 20:21:27 +0200 Received: from ted.stsp.lan (localhost [127.0.0.1]) by stsp.lan (8.13.8/8.13.8) with ESMTP id l5PIIIU9038846 for ; Mon, 25 Jun 2007 20:18:18 +0200 (CEST) (envelope-from stsp@stsp.name) Received: (from stsp@localhost) by ted.stsp.lan (8.13.8/8.13.8/Submit) id l5PIIHOa038845 for freebsd-hackers@freebsd.org; Mon, 25 Jun 2007 20:18:17 +0200 (CEST) (envelope-from stsp@stsp.name) X-Authentication-Warning: ted.stsp.lan: stsp set sender to stsp@stsp.name using -f Date: Mon, 25 Jun 2007 20:18:16 +0200 From: Stefan Sperling To: freebsd-hackers@freebsd.org Message-ID: <20070625181816.GC25719@ted.stsp.lan> Mail-Followup-To: freebsd-hackers@freebsd.org References: <467EF0C1.1010609@optiksecurite.com> <467FFF41.10204@math.missouri.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eHhjakXzOLJAF9wJ" Content-Disposition: inline In-Reply-To: <467FFF41.10204@math.missouri.edu> User-Agent: Mutt/1.5.15 (2007-04-06) X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 Subject: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 18:21:29 -0000 --eHhjakXzOLJAF9wJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 25, 2007 at 12:45:37PM -0500, Stephen Montgomery-Smith wrote: > Also, does setting CPUTYPE make a lot of difference to performance? I don't notice any difference in performance on my Athlon xp 2400 box if I set CPUTYPE=3Dathlon-xp vs. leaving it alone. YMMV though, ask the gentoo people :) > Right now I have no CPUTYPE set at all. Also leaving CPUTYPE unset means I can plug the system disc into any other old x86 box without hitting illegal instructions. In case my motherboard fries itself again some time like the old one did a few weeks ago I'll be glad I can do this. --=20 stefan http://stsp.name PGP Key: 0xF59D25F0 --eHhjakXzOLJAF9wJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGgAbo5dMCc/WdJfARAl/xAJ0XEXw0D37haxLpi9mNjc4cW2xyrwCfVf2o //77oK5kMQxQV13kI4hwP9U= =15kJ -----END PGP SIGNATURE----- --eHhjakXzOLJAF9wJ-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 19:12:07 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 37E6C16A468; Mon, 25 Jun 2007 19:12:07 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id E3C7E13C44C; Mon, 25 Jun 2007 19:12:06 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1I2tym-000DGS-50; Mon, 25 Jun 2007 22:12:04 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Julian Elischer In-reply-to: <467FF435.6050108@elischer.org> References: <467FF435.6050108@elischer.org> Comments: In-reply-to Julian Elischer message dated "Mon, 25 Jun 2007 09:58:29 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Jun 2007 22:12:04 +0300 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: KSE was Re: open/close/ioctl api change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 19:12:07 -0000 > Danny Braniss wrote: > >> actually it's the struct thread *tp where my problems are, > >> this code works fine under 6.2, and did work till some days ago under current. > >> > >> static int > >> iscsi_open(struct cdev *dev, int flags, int otype, struct thread *td) > >> { > >> ... > >> debug(3, "td->td_proc=%p", td->td_proc); > >> debug(3, "td->td_proc->p_pid=%d pid=%d", > >> td->td_proc->p_pid, curproc->p_pid); > >> ... > >> > >> the first debug prints out td->td_proc=0 and the next one panics. > > > > found the problem, 'option KSE' which is defined now in DEFAULTS, > > and i'm compiling a module! which does not include DEFAULTS! > > > > even so it shouldnt' happen.. > why? I'm compiling outside the source tree. I agree that it shouldn't, specially, since it took me a long time to find the problem :-), but I can't see how config options can be exported. Unless, the make file is made aware of the KERNCONF file. danny From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 19:20:01 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D835716A46E for ; Mon, 25 Jun 2007 19:20:01 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outF.internet-mail-service.net (outF.internet-mail-service.net [216.240.47.229]) by mx1.freebsd.org (Postfix) with ESMTP id BF83013C46C for ; Mon, 25 Jun 2007 19:20:01 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 25 Jun 2007 12:20:01 -0700 Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id F25EA125A23; Mon, 25 Jun 2007 12:20:00 -0700 (PDT) Message-ID: <46801566.2080706@elischer.org> Date: Mon, 25 Jun 2007 12:20:06 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Danny Braniss References: <467FF435.6050108@elischer.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: KSE was Re: open/close/ioctl api change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 19:20:02 -0000 Danny Braniss wrote: >> Danny Braniss wrote: >>>> actually it's the struct thread *tp where my problems are, >>>> this code works fine under 6.2, and did work till some days ago under current. >>>> >>>> static int >>>> iscsi_open(struct cdev *dev, int flags, int otype, struct thread *td) >>>> { >>>> ... >>>> debug(3, "td->td_proc=%p", td->td_proc); >>>> debug(3, "td->td_proc->p_pid=%d pid=%d", >>>> td->td_proc->p_pid, curproc->p_pid); >>>> ... >>>> >>>> the first debug prints out td->td_proc=0 and the next one panics. >>> found the problem, 'option KSE' which is defined now in DEFAULTS, >>> and i'm compiling a module! which does not include DEFAULTS! >>> >> even so it shouldnt' happen.. >> > why? I'm compiling outside the source tree. > I agree that it shouldn't, specially, since it took me a long > time to find the problem :-), but I can't see how config options > can be exported. Unless, the make file is made aware of the KERNCONF file. there should be no place in the source at any time where a thread that is not on the free list could have a td_proc of NULL. it doesn't matter about where a module came from etc.. the fact that it happened is a bug somewhere. > > danny > From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 19:23:14 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9889816A47D for ; Mon, 25 Jun 2007 19:23:14 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (vlk.vlakno.cz [62.168.28.247]) by mx1.freebsd.org (Postfix) with ESMTP id 4D66813C448 for ; Mon, 25 Jun 2007 19:23:13 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 567CA8BE983; Mon, 25 Jun 2007 21:23:10 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (vlk.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0f6WFqVDzHeF; Mon, 25 Jun 2007 21:23:09 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 3862D8BE922; Mon, 25 Jun 2007 21:23:09 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.13.8/8.13.8/Submit) id l5PJN8ZK014597; Mon, 25 Jun 2007 21:23:08 +0200 (CEST) (envelope-from rdivacky) Date: Mon, 25 Jun 2007 21:23:08 +0200 From: Roman Divacky To: Stephen Montgomery-Smith Message-ID: <20070625192308.GA14544@freebsd.org> References: <467EF0C1.1010609@optiksecurite.com> <467FFF41.10204@math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <467FFF41.10204@math.missouri.edu> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org Subject: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 19:23:14 -0000 > In general, how does one decide which CPUTYPE to use? The connection > between the options for CPUTYPE and the output of dmesg is not so > obvious to me. I looked at the features advertised by dmesg (which in > my case included SSE3) and then reverse engineered bsd.cpu.mk to figure > out I should be using "prescott," but I am hoping I figured it out the I would not judge only by instructions like SSE etc. ins scheduling etc. plays key role as well. you should know what cpu you bought, or just use cpuid (found in ports) and determine what cpu you have. on -current you can set _native_ or native (dont remember) and gcc will choose itself... ;) roman From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 19:31:49 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CED4D16A47B; Mon, 25 Jun 2007 19:31:49 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 8126B13C44B; Mon, 25 Jun 2007 19:31:49 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1I2uHq-000DkP-E7; Mon, 25 Jun 2007 22:31:46 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Julian Elischer In-reply-to: Your message of Mon, 25 Jun 2007 12:20:06 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Jun 2007 22:31:46 +0300 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: KSE was Re: open/close/ioctl api change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 19:31:50 -0000 > Danny Braniss wrote: > >> Danny Braniss wrote: > >>>> actually it's the struct thread *tp where my problems are, > >>>> this code works fine under 6.2, and did work till some days ago under current. > >>>> > >>>> static int > >>>> iscsi_open(struct cdev *dev, int flags, int otype, struct thread *td) > >>>> { > >>>> ... > >>>> debug(3, "td->td_proc=%p", td->td_proc); > >>>> debug(3, "td->td_proc->p_pid=%d pid=%d", > >>>> td->td_proc->p_pid, curproc->p_pid); > >>>> ... > >>>> > >>>> the first debug prints out td->td_proc=0 and the next one panics. > >>> found the problem, 'option KSE' which is defined now in DEFAULTS, > >>> and i'm compiling a module! which does not include DEFAULTS! > >>> > >> even so it shouldnt' happen.. > >> > > why? I'm compiling outside the source tree. > > I agree that it shouldn't, specially, since it took me a long > > time to find the problem :-), but I can't see how config options > > can be exported. Unless, the make file is made aware of the KERNCONF file. > > there should be no place in the source at any time where a thread > that is not on the free list could have a td_proc of NULL. > it doesn't matter about where a module came from etc.. the fact that > it happened is a bug somewhere. Julian, I compiled the kernel, and DEFAULT contains option KSE then I compiled the loadable module, outside the source tree, where KSE is not defined, the thread structure has #ifdef KSE ... #endif so my module sees a different thread structure. The real arguable issue is that the #ifdef KSE is below the *td_proc, So td->proc should not be affected by the ifdef. BTW, it was NULL when compiled for i386, garbage for amd64. danny From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 21:11:05 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 558CF16A480 for ; Mon, 25 Jun 2007 21:11:05 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id E8CDA13C483 for ; Mon, 25 Jun 2007 21:11:04 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 11255 invoked by uid 1001); 25 Jun 2007 21:09:21 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Mon, 25 Jun 2007 17:09:20 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18048.12032.316862.338084@bhuda.mired.org> Date: Mon, 25 Jun 2007 17:09:20 -0400 To: Roman Divacky In-Reply-To: <20070625192308.GA14544@freebsd.org> References: <467EF0C1.1010609@optiksecurite.com> <467FFF41.10204@math.missouri.edu> <20070625192308.GA14544@freebsd.org> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 21:11:05 -0000 In <20070625192308.GA14544@freebsd.org>, Roman Divacky typed: > you should know what cpu you bought, or just use cpuid (found in ports) > and determine what cpu you have. Knowing what CPU you bought doesn't help a lot for the case asked about of "nocona" vs. "prescott". Those are the names of P4 and Xeon cores, not CPUs - and not the last cores used in either line. cpuid will tell you what features your CPU supports, but not the name of the core. So it only helps if you know what you're looking for. P4 and Xeon are just marketing names, and the features available vary quite a bit across the lines. Even knowing the core names doesn't help, as some prescott cored P4s have all the gcc "nocona" features. Assuming the gcc man page is correct, use cpuid to check the feature sets of your CPU. If you don't have SSE2, then you should be using something prior to pentium 4. If you have SSE2 but not SSE3, then you want pentium-m, pentium4 or pentium4m. If you have SSE3, then you should be using either nocona or prescott. If you have 64 bit support, you want nocona, otherwise prescott. For the record, I believe the nocona cores are: pentium 4/some prescott, prescott 2m, cedar mill pentium D/all core 2 duo/all All xeons with sse3 except the sossaman cored Xeon LV. The prescott cores are: pentium 4/some prescott xeon lv (sossaman core) core solo core duo http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 25 21:29:16 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E541916A400 for ; Mon, 25 Jun 2007 21:29:16 +0000 (UTC) (envelope-from turgeon.martin@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.freebsd.org (Postfix) with ESMTP id 9E8E913C447 for ; Mon, 25 Jun 2007 21:29:16 +0000 (UTC) (envelope-from turgeon.martin@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so2111877pyb for ; Mon, 25 Jun 2007 14:29:16 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Mkd1lpPhMxblm0YLMkume5Qfcl7mXQhFCOD+ebPUdjaJTU5limwS+pcJrP59aEIzT2UhvqagLFYejTOPrk2qnVihmf9jVyo/H7pDbwqbaXfEjAKMlPglhaQszC6oSTLO6NyMvU43UuCSfCs29Bz8cW93H8zwhZ/b9KcfFgSJaLk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=qdA1AF9Ba4Ne8WmMn0ESpyv4FKfAwFlyCvaItpzfgxJlsBUxzspkAhl2zozYqUmzRSqxXC3kBH+MpVLtFOfHteOFNjSm3/UJP2aQKVeBtis43zGZvOccqszrTQSIgsRZNTxRL00lh+J+nkuGUpYEDy+LGZU6aWR2qjUUktme2po= Received: by 10.35.106.15 with SMTP id i15mr2703117pym.1182806955703; Mon, 25 Jun 2007 14:29:15 -0700 (PDT) Received: from ?192.168.3.200? ( [69.70.75.162]) by mx.google.com with ESMTP id 7sm7516497nzn.2007.06.25.14.29.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 25 Jun 2007 14:29:14 -0700 (PDT) Message-ID: <468033A8.8060103@gmail.com> Date: Mon, 25 Jun 2007 17:29:12 -0400 From: Martin Turgeon User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Mike Meyer References: <467EF0C1.1010609@optiksecurite.com> <467FFF41.10204@math.missouri.edu> <20070625192308.GA14544@freebsd.org> <18048.12032.316862.338084@bhuda.mired.org> In-Reply-To: <18048.12032.316862.338084@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, Roman Divacky Subject: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 21:29:17 -0000 Mike Meyer a écrit : > In <20070625192308.GA14544@freebsd.org>, Roman Divacky typed: > >> you should know what cpu you bought, or just use cpuid (found in ports) >> and determine what cpu you have. >> > > Knowing what CPU you bought doesn't help a lot for the case asked > about of "nocona" vs. "prescott". Those are the names of P4 and Xeon > cores, not CPUs - and not the last cores used in either line. cpuid > will tell you what features your CPU supports, but not the name of the > core. So it only helps if you know what you're looking for. P4 and > Xeon are just marketing names, and the features available vary quite a > bit across the lines. Even knowing the core names doesn't help, as > some prescott cored P4s have all the gcc "nocona" features. > > Assuming the gcc man page is correct, use cpuid to check the feature > sets of your CPU. If you don't have SSE2, then you should be using > something prior to pentium 4. If you have SSE2 but not SSE3, then you > want pentium-m, pentium4 or pentium4m. If you have SSE3, then you > should be using either nocona or prescott. If you have 64 bit support, > you want nocona, otherwise prescott. > > For the record, I believe the nocona cores are: > pentium 4/some prescott, prescott 2m, cedar mill > pentium D/all > core 2 duo/all > All xeons with sse3 except the sossaman cored Xeon LV. > > The prescott cores are: > pentium 4/some prescott > xeon lv (sossaman core) > core solo > core duo > > Thanks a lot for the precision, I will use nocona for my dual core Xeon. Martin From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 03:34:51 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8D48516A468; Tue, 26 Jun 2007 03:34:51 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.freebsd.org (Postfix) with ESMTP id 62F5413C465; Tue, 26 Jun 2007 03:34:51 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9] (may be forged)) by mxout5.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l5Q3YokC000993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 25 Jun 2007 20:34:50 -0700 X-Auth-Received: from [192.168.10.45] (c-24-10-12-194.hsd1.ca.comcast.net [24.10.12.194]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l5Q3Ynie004905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 25 Jun 2007 20:34:50 -0700 Message-ID: <4680895A.5060700@u.washington.edu> Date: Mon, 25 Jun 2007 20:34:50 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Martin Turgeon References: <467EF0C1.1010609@optiksecurite.com> <467FFF41.10204@math.missouri.edu> <20070625192308.GA14544@freebsd.org> <18048.12032.316862.338084@bhuda.mired.org> <468033A8.8060103@gmail.com> In-Reply-To: <468033A8.8060103@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.25.201734 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Cc: freebsd-hackers@freebsd.org, Roman Divacky , Mike Meyer Subject: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 03:34:51 -0000 Martin Turgeon wrote: > Mike Meyer a écrit : >> In <20070625192308.GA14544@freebsd.org>, Roman Divacky >> typed: >> >>> you should know what cpu you bought, or just use cpuid (found in ports) >>> and determine what cpu you have. >>> >> >> Knowing what CPU you bought doesn't help a lot for the case asked >> about of "nocona" vs. "prescott". Those are the names of P4 and Xeon >> cores, not CPUs - and not the last cores used in either line. cpuid >> will tell you what features your CPU supports, but not the name of the >> core. So it only helps if you know what you're looking for. P4 and >> Xeon are just marketing names, and the features available vary quite a >> bit across the lines. Even knowing the core names doesn't help, as >> some prescott cored P4s have all the gcc "nocona" features. >> >> Assuming the gcc man page is correct, use cpuid to check the feature >> sets of your CPU. If you don't have SSE2, then you should be using >> something prior to pentium 4. If you have SSE2 but not SSE3, then you >> want pentium-m, pentium4 or pentium4m. If you have SSE3, then you >> should be using either nocona or prescott. If you have 64 bit support, >> you want nocona, otherwise prescott. >> >> For the record, I believe the nocona cores are: >> pentium 4/some prescott, prescott 2m, cedar mill >> pentium D/all >> core 2 duo/all >> All xeons with sse3 except the sossaman cored Xeon LV. >> >> The prescott cores are: >> pentium 4/some prescott >> xeon lv (sossaman core) >> core solo >> core duo >> > > Thanks a lot for the precision, I will use nocona for my dual core Xeon. > > Martin Sorry for not having a reference but it came from an Intel internal site. Here are the highlights for some of the past players: Cedar Mill: Last P4 processor. Followup to Prescott. Conroe: Desktop version of the Core2Duo processor. Mobile equivalent is Merom. Dothan: 2nd gen. Pentium M CPU. Nocona: Xeon server processor code name -- first CPU with EMT64 (amd64) compatibility [and hence first non-IA64 bit Xeon processor to feature 64-bit compatibility; not sure if it was the first non-IA64 64-bit designed Intel processor]. Prescott: Single-core processor with HTT. Base CPU for [later generation] P4 processors, and the dual core Pentium D [basically the larger cousin of the Northwood CPUs]. Prescott was compacted into Cedar Mill -- from a 90nm (?) process to 65nm. Sossaman: Dual-core Xeon processor, based off of Yonah. Woodcrest: Server version of Conroe/Merom. Yonah: First Duo/Solo processor. Based off of Dothan. Some people have claimed that pentium-m is better for Core * based processors because of the shorter pipelines and lower frequency (found via a google discussion about gcc and -march, but I can't be sure of its validity), but pentium-m is a 32-bit CPU, thus it's not an option for 64-bit computing. Intel suggests using -march=prescott (32-bit) and -march=nocona (64-bit) with gcc on Core2Duo processors and equivalent Xeons. You can also find your CPU's type by going to this page: http://www.intel.com/products/server/processors/index.htm?iid=serv_body+proc, and searching for the appropriate model number. Your frequency and model should be reported in your BIOS, if not the first couple lines of dmesg in FreeBSD. Cheers, -Garrett From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 05:06:28 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2492816A41F for ; Tue, 26 Jun 2007 05:06:28 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id C58EF13C43E for ; Tue, 26 Jun 2007 05:06:27 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 16297 invoked by uid 1001); 26 Jun 2007 05:04:44 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Tue, 26 Jun 2007 01:04:44 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <18048.40555.876785.219568@bhuda.mired.org> Date: Tue, 26 Jun 2007 01:04:43 -0400 To: Garrett Cooper In-Reply-To: <4680895A.5060700@u.washington.edu> References: <467EF0C1.1010609@optiksecurite.com> <467FFF41.10204@math.missouri.edu> <20070625192308.GA14544@freebsd.org> <18048.12032.316862.338084@bhuda.mired.org> <468033A8.8060103@gmail.com> <4680895A.5060700@u.washington.edu> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Cc: freebsd-hackers@freebsd.org, Martin Turgeon , Roman Divacky Subject: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 05:06:28 -0000 In <4680895A.5060700@u.washington.edu>, Garrett Cooper typed: > Martin Turgeon wrote: > > Mike Meyer a =E9crit : > >> In <20070625192308.GA14544@freebsd.org>, Roman Divacky=20 > >> typed: > >> For the record, I believe the nocona cores are: > >> pentium 4/some prescott, prescott 2m, cedar mill > >> pentium D/all > >> core 2 duo/all > >> All xeons with sse3 except the sossaman cored Xeon LV. > >> > >> The prescott cores are: > >> pentium 4/some prescott > >> xeon lv (sossaman core) > >> core solo > >> core duo > > Thanks a lot for the precision, I will use nocona for my dual core = Xeon. > Cedar Mill: Last P4 processor. Followup to Prescott. > Nocona: Xeon server processor code name -- first CPU with EMT64 (amd6= 4)=20 > compatibility [and hence first non-IA64 bit Xeon processor to feature= =20 > 64-bit compatibility; not sure if it was the first non-IA64 64-bit=20= > designed Intel processor]. > Prescott: Single-core processor with HTT. Base CPU for [later=20 > generation] P4 processors, and the dual core Pentium D [basically the= =20 > larger cousin of the Northwood CPUs]. Prescott was compacted into Ced= ar=20 > Mill -- from a 90nm (=3F) process to 65nm. >From what I can tell, the Prescott went through a number of iterations; the first of them didn't have HTT, or had it but it was disabled. Later versions added that, EMT64, virtualization, and other things. If my information is correct, the nocona was the first version of the prescott core with em64t, and only used in Xeons. And yes, I believe prescott and following were 90nm until Cedar Mill. > Intel suggests using -march=3Dprescott (32-bit) and -march=3Dnoco= na=20 > (64-bit) with gcc on Core2Duo processors and equivalent Xeons. Note that /usr/share/mk/sys.mk includes bsd.mk.cpu, which overrides CPUTYPE if it's set to prescott or nocona. It turns nocona into prescott if you're building for i386 and prescott into nocona if you're building for amd64. So the correct answer to the question "Do I set CPUTYPE to nocona or prescott in /etc/make.conf=3F" would seem to b= e "It doesn't matter." > You can also find your CPU's type by going to this page:=20 > http://www.intel.com/products/server/processors/index.htm=3Fiid=3Dser= v=5Fbody+proc,=20 > and searching for the appropriate model number. Your frequency and mo= del=20 > should be reported in your BIOS, if not the first couple lines of dme= sg=20 > in FreeBSD. I've never seen those report core names. Possibly you're referring specifically to the Xeon cpu model numbers=3F =09thanks, =09=09=09http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more informatio= n. From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 11:00:51 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A976416A400; Tue, 26 Jun 2007 11:00:51 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.freebsd.org (Postfix) with ESMTP id 82F8513C469; Tue, 26 Jun 2007 11:00:51 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9] (may be forged)) by mxout2.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l5QB0ojb005863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 26 Jun 2007 04:00:51 -0700 X-Auth-Received: from [192.168.10.45] (c-24-10-12-194.hsd1.ca.comcast.net [24.10.12.194]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l5QB0oJt023521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Jun 2007 04:00:50 -0700 Message-ID: <4680F1E3.1010306@u.washington.edu> Date: Tue, 26 Jun 2007 04:00:51 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Mike Meyer References: <467EF0C1.1010609@optiksecurite.com> <467FFF41.10204@math.missouri.edu> <20070625192308.GA14544@freebsd.org> <18048.12032.316862.338084@bhuda.mired.org> <468033A8.8060103@gmail.com> <4680895A.5060700@u.washington.edu> <18048.40555.876785.219568@bhuda.mired.org> In-Reply-To: <18048.40555.876785.219568@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.26.33934 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Cc: freebsd-hackers@freebsd.org, Martin Turgeon , Roman Divacky Subject: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 11:00:51 -0000 Mike Meyer wrote: > In <4680895A.5060700@u.washington.edu>, Garrett Cooper typed: > >> Martin Turgeon wrote: >> >>> Mike Meyer a écrit : >>> >>>> In <20070625192308.GA14544@freebsd.org>, Roman Divacky >>>> typed: >>>> For the record, I believe the nocona cores are: >>>> pentium 4/some prescott, prescott 2m, cedar mill >>>> pentium D/all >>>> core 2 duo/all >>>> All xeons with sse3 except the sossaman cored Xeon LV. >>>> >>>> The prescott cores are: >>>> pentium 4/some prescott >>>> xeon lv (sossaman core) >>>> core solo >>>> core duo >>>> >>> Thanks a lot for the precision, I will use nocona for my dual core Xeon. >>> > > >> Cedar Mill: Last P4 processor. Followup to Prescott. >> Nocona: Xeon server processor code name -- first CPU with EMT64 (amd64) >> compatibility [and hence first non-IA64 bit Xeon processor to feature >> 64-bit compatibility; not sure if it was the first non-IA64 64-bit >> designed Intel processor]. >> Prescott: Single-core processor with HTT. Base CPU for [later >> generation] P4 processors, and the dual core Pentium D [basically the >> larger cousin of the Northwood CPUs]. Prescott was compacted into Cedar >> Mill -- from a 90nm (?) process to 65nm. >> > > From what I can tell, the Prescott went through a number of > iterations; the first of them didn't have HTT, or had it but it was > disabled. Later versions added that, EMT64, virtualization, and other > things. If my information is correct, the nocona was the first version > of the prescott core with em64t, and only used in Xeons. > There was a big difference between the Prescott CPU core and the Nocona core though, in terms of technology (Pentium 4 vs Core/Core2). Apparently the pipelines for the CPU were similar for the desktop CPU though, some have claimed. I haven't looked at the RTL though, so I can't be sure for myself whether or not that's the case. > And yes, I believe prescott and following were 90nm until Cedar Mill. > Ok, that's what I thought (since fab screen size goes by 15nm each time nowadays). >> Intel suggests using -march=prescott (32-bit) and -march=nocona >> (64-bit) with gcc on Core2Duo processors and equivalent Xeons. >> > > Note that /usr/share/mk/sys.mk includes bsd.mk.cpu, which overrides > CPUTYPE if it's set to prescott or nocona. It turns nocona into > prescott if you're building for i386 and prescott into nocona if > you're building for amd64. So the correct answer to the question "Do I > set CPUTYPE to nocona or prescott in /etc/make.conf?" would seem to be > "It doesn't matter." Hmmm... interesting.. Seems like a bit ambitious for bsd.mk.cpu, if the user knows what they're doing. >> You can also find your CPU's type by going to this page: >> http://www.intel.com/products/server/processors/index.htm?iid=serv_body+proc, >> and searching for the appropriate model number. Your frequency and model >> should be reported in your BIOS, if not the first couple lines of dmesg >> in FreeBSD. >> > > I've never seen those report core names. Possibly you're referring > specifically to the Xeon cpu model numbers? > Yeah, that's exactly what I meant. -Garrett From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 12:45:39 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 69FE616A41F for ; Tue, 26 Jun 2007 12:45:39 +0000 (UTC) (envelope-from egypcio@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.233]) by mx1.freebsd.org (Postfix) with ESMTP id 0CCC013C46E for ; Tue, 26 Jun 2007 12:45:38 +0000 (UTC) (envelope-from egypcio@gmail.com) Received: by nz-out-0506.google.com with SMTP id 34so791823nzf for ; Tue, 26 Jun 2007 05:45:38 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=n2dQHbslo2Gv6UVh95lZLvfMpy/2QCY7VnsCKYOEnSVjO012+RSq+XZNOhkBW6zNWPG2HU0tepKS7aE6ZfbQSPelyJz1B3vbelPCvF4wZZPk1RfYs7hsvn2rAT1jShmTXRGZs/6BlfcKv6CpLnPKu1gDVVgcGy/PIOEvUMrqWZI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ncyHzH2dGlvuXGqVu3fMYgtJU3ZcWExHItD/Xx12kUI2pWpGpJk5xrd0FdWlDGwGUHGT3fKK2onBrLW0zo1DoE3ALWN6mo+5w61m+EisZnVlJfHEfTfuxrTwU48kE7KZ0cnUgGMGBE3Zs6k19ecZxJNertbdo8q++gTkMp9Kn9Q= Received: by 10.114.177.1 with SMTP id z1mr6397314wae.1182861938094; Tue, 26 Jun 2007 05:45:38 -0700 (PDT) Received: by 10.115.15.16 with HTTP; Tue, 26 Jun 2007 05:45:38 -0700 (PDT) Message-ID: <8b5ad0e10706260545u6ad0b0c6w209548293809e993@mail.gmail.com> Date: Tue, 26 Jun 2007 08:45:38 -0400 From: "=?ISO-8859-1?Q?Zavam,_Vin=EDcius?=" To: freebsd-hackers@freebsd.org In-Reply-To: <4680F1E3.1010306@u.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <467EF0C1.1010609@optiksecurite.com> <467FFF41.10204@math.missouri.edu> <20070625192308.GA14544@freebsd.org> <18048.12032.316862.338084@bhuda.mired.org> <468033A8.8060103@gmail.com> <4680895A.5060700@u.washington.edu> <18048.40555.876785.219568@bhuda.mired.org> <4680F1E3.1010306@u.washington.edu> Subject: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 12:45:39 -0000 2007/6/26, Garrett Cooper : > Mike Meyer wrote: > > In <4680895A.5060700@u.washington.edu>, Garrett Cooper typed: > > > >> Martin Turgeon wrote: > >> > >>> Mike Meyer a =E9crit : > >>> > >>>> In <20070625192308.GA14544@freebsd.org>, Roman Divacky > >>>> typed: > >>>> For the record, I believe the nocona cores are: > >>>> pentium 4/some prescott, prescott 2m, cedar mill > >>>> pentium D/all > >>>> core 2 duo/all > >>>> All xeons with sse3 except the sossaman cored Xeon LV. > >>>> > >>>> The prescott cores are: > >>>> pentium 4/some prescott > >>>> xeon lv (sossaman core) > >>>> core solo > >>>> core duo > >>>> > >>> Thanks a lot for the precision, I will use nocona for my dual core Xe= on. > >>> > > > > > >> Cedar Mill: Last P4 processor. Followup to Prescott. > >> Nocona: Xeon server processor code name -- first CPU with EMT64 (amd64= ) > >> compatibility [and hence first non-IA64 bit Xeon processor to feature > >> 64-bit compatibility; not sure if it was the first non-IA64 64-bit > >> designed Intel processor]. > >> Prescott: Single-core processor with HTT. Base CPU for [later > >> generation] P4 processors, and the dual core Pentium D [basically the > >> larger cousin of the Northwood CPUs]. Prescott was compacted into Ceda= r > >> Mill -- from a 90nm (?) process to 65nm. > >> > > > > From what I can tell, the Prescott went through a number of > > iterations; the first of them didn't have HTT, or had it but it was > > disabled. Later versions added that, EMT64, virtualization, and other > > things. If my information is correct, the nocona was the first version > > of the prescott core with em64t, and only used in Xeons. > > > There was a big difference between the Prescott CPU core and the Nocona > core though, in terms of technology (Pentium 4 vs Core/Core2). > Apparently the pipelines for the CPU were similar for the desktop CPU > though, some have claimed. I haven't looked at the RTL though, so I > can't be sure for myself whether or not that's the case. > > And yes, I believe prescott and following were 90nm until Cedar Mill. > > > Ok, that's what I thought (since fab screen size goes by 15nm each time > nowadays). > >> Intel suggests using -march=3Dprescott (32-bit) and -march=3Dnocon= a > >> (64-bit) with gcc on Core2Duo processors and equivalent Xeons. > >> > > > > Note that /usr/share/mk/sys.mk includes bsd.mk.cpu, which overrides > > CPUTYPE if it's set to prescott or nocona. It turns nocona into > > prescott if you're building for i386 and prescott into nocona if > > you're building for amd64. So the correct answer to the question "Do I > > set CPUTYPE to nocona or prescott in /etc/make.conf?" would seem to be > > "It doesn't matter." > Hmmm... interesting.. Seems like a bit ambitious for bsd.mk.cpu, if the u= ser knows what they're doing. > > >> You can also find your CPU's type by going to this page: > >> http://www.intel.com/products/server/processors/index.htm?iid=3Dserv_b= ody+proc, > >> and searching for the appropriate model number. Your frequency and mod= el > >> should be reported in your BIOS, if not the first couple lines of dmes= g > >> in FreeBSD. > >> > > > > I've never seen those report core names. Possibly you're referring > > specifically to the Xeon cpu model numbers? > > > Yeah, that's exactly what I meant. > -Garrett please correct me if I'm wrong, but gcc(1) can help us a bit also; http://www.freebsd.org/cgi/man.cgi?query=3Dgcc&sektion=3D1&format=3Dhtml z.B.: " (...) prescott Improved version of Intel Pentium4 CPU with MMX, SSE, SSE2 and SSE3 instruction set support. nocona Improved version of Intel Pentium4 CPU with 64-bit extensions, MMX, SSE, SSE2 and SSE3 instruction set support. (...) athlon-4, athlon-xp, athlon-mp Improved AMD Athlon CPU with MMX, 3dNOW!, enhanced 3dNOW! and full SSE instruction set support. k8, opteron, athlon64, athlon-fx AMD K8 core based CPUs with x86-64 instruction set support. (This supersets MMX, SSE, SSE2, 3dNOW!, enhanced 3dNOW! and 64-bit instruction set extensions.) (...) " --=20 Zavam, Vin=EDcius From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 13:23:18 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3939816A4FA for ; Tue, 26 Jun 2007 13:23:18 +0000 (UTC) (envelope-from n.cormier@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.freebsd.org (Postfix) with ESMTP id C11D813C44C for ; Tue, 26 Jun 2007 13:23:17 +0000 (UTC) (envelope-from n.cormier@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so2492219pyb for ; Tue, 26 Jun 2007 06:23:17 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=iGnNdhCNRfOurO7VxgRHrFDVfB1NCO6X6JP94qMUZt1mROvsMWlA+CKVFdDkQJe3tybWdV8iwCyk5KOme4H9/7D5+RewfWyiBKwsnPCOpDMYPiJXWiNaD7sFQahgSRc8nd1zHJ7025PmgUqu+0DLp2CFogFkVU7tVILuyno1dWY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=CcatGi34OW2E5DLq9222E9VmjAgFNbpP+Rw6rF8F3hZvFVLNLj7lruMjj6uiXPpiTQkQ6QVowtx8Y1tt5qzGbGiOCdsFASO/sTsQuS2NumQbNqoIeMFNRaBGCKplTpTtvuUhdeGqY+Uei1M6zQVeVIgsKuPjAvsvIUl7dhitMxU= Received: by 10.35.96.6 with SMTP id y6mr5925594pyl.1182864197024; Tue, 26 Jun 2007 06:23:17 -0700 (PDT) Received: by 10.35.40.11 with HTTP; Tue, 26 Jun 2007 06:23:16 -0700 (PDT) Message-ID: Date: Tue, 26 Jun 2007 15:23:16 +0200 From: "Nicolas Cormier" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Play with the VM X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 13:23:18 -0000 Hi, I have some questions about virtual memory and the freebsd implementation. I am trying to map in userland (with a syscall like mmap) some anonymous data (from sockets, files ...). What's the best way to do this ? There are callbacks in the VM when a user process tries to access a specific address ? Thanks in advance -- Nicolas Cormier From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 14:04:06 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ADA4416A400 for ; Tue, 26 Jun 2007 14:04:06 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 4849113C45E for ; Tue, 26 Jun 2007 14:04:05 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 21199 invoked by uid 1001); 26 Jun 2007 14:02:23 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Tue, 26 Jun 2007 10:02:23 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <18049.7278.769858.788831@bhuda.mired.org> Date: Tue, 26 Jun 2007 10:02:22 -0400 To: "=?ISO-8859-1?Q?Zavam,_Vin=EDcius?=" In-Reply-To: <8b5ad0e10706260545u6ad0b0c6w209548293809e993@mail.gmail.com> References: <467EF0C1.1010609@optiksecurite.com> <467FFF41.10204@math.missouri.edu> <20070625192308.GA14544@freebsd.org> <18048.12032.316862.338084@bhuda.mired.org> <468033A8.8060103@gmail.com> <4680895A.5060700@u.washington.edu> <18048.40555.876785.219568@bhuda.mired.org> <4680F1E3.1010306@u.washington.edu> <8b5ad0e10706260545u6ad0b0c6w209548293809e993@mail.gmail.com> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 14:04:06 -0000 In <8b5ad0e10706260545u6ad0b0c6w209548293809e993@mail.gmail.com>, Zavam= , Vin=EDcius typed: > 2007/6/26, Garrett Cooper : > > Mike Meyer wrote: > > nowadays). > > >> Intel suggests using -march=3Dprescott (32-bit) and -march=3D= nocona > > >> (64-bit) with gcc on Core2Duo processors and equivalent Xeons. > > >> > > > > > > Note that /usr/share/mk/sys.mk includes bsd.mk.cpu, which overrid= es > > > CPUTYPE if it's set to prescott or nocona. It turns nocona into > > > prescott if you're building for i386 and prescott into nocona if > > > you're building for amd64. So the correct answer to the question = "Do I > > > set CPUTYPE to nocona or prescott in /etc/make.conf=3F" would see= m to be > > > "It doesn't matter." > > Hmmm... interesting.. Seems like a bit ambitious for bsd.mk.cpu, if= the user knows what they're doing. > please correct me if I'm wrong, but gcc(1) can help us a bit also; > http://www.freebsd.org/cgi/man.cgi=3Fquery=3Dgcc&sektion=3D1&format=3D= html Right. We actually discussed this, then wondered into the history of the CPU cores. You start with misc/cpuid to get a list of features your CPU has, then use the gcc man page to figure out which cputype will use the most features of your CPU without trying to use features which your CPU doesn't have. > z.B.: > " > (...) > prescott > Improved version of Intel Pentium4 CPU with MMX, SSE, SSE2 and= > SSE3 instruction set support. >=20 > nocona > Improved version of Intel Pentium4 CPU with 64-bit extensions,= > MMX, SSE, SSE2 and SSE3 instruction set support. >=20 > (...) > athlon-4, athlon-xp, athlon-mp > Improved AMD Athlon CPU with MMX, 3dNOW!, enhanced 3dNOW! and > full SSE instruction set support. >=20 > k8, opteron, athlon64, athlon-fx > AMD K8 core based CPUs with x86-64 instruction set support. > (This supersets MMX, SSE, SSE2, 3dNOW!, enhanced 3dNOW! and > 64-bit instruction set extensions.) > (...) > " =09=09=09http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more informatio= n. From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 15:28:30 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8936C16A469 for ; Tue, 26 Jun 2007 15:28:30 +0000 (UTC) (envelope-from xride@x12.dk) Received: from swip.net (mailfe03.tele2.dk [212.247.154.67]) by mx1.freebsd.org (Postfix) with ESMTP id 2640513C4BE for ; Tue, 26 Jun 2007 15:28:29 +0000 (UTC) (envelope-from xride@x12.dk) X-Cloudmark-Score: 0.000000 [] Received: from x12.dk (account mu12272@get2net.dk [83.72.97.231] verified) by mailfe03.swip.net (CommuniGate Pro SMTP 5.1.10) with ESMTPA id 536990135 for freebsd-hackers@freebsd.org; Tue, 26 Jun 2007 17:28:28 +0200 Received: by x12.dk (Postfix, from userid 666) id E488950845; Tue, 26 Jun 2007 17:28:27 +0200 (CEST) Date: Tue, 26 Jun 2007 17:28:27 +0200 From: Soeren Straarup To: freebsd-hackers@freebsd.org Message-ID: <20070626152827.GH96848@x12.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Subject: strange wi driver things. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 15:28:30 -0000 Hi.. Last kernel was build at Wed Jun 20 23:20:34 CEST 2007 from head. At first glance: 1) Channel number is +1. 2) Getting alot of wi0: record read mismatch, rid=fd44, got=8000 Where the got part changes randomly. 3) wi0: xmit failed 4) 'ifconfig wi0 list scan' returns nothing at first run, then on second go it looks right. http://people.freebsd.org/~xride/wi.txt There is some logs there. /Soeren -- Soeren Straarup | aka OZ2DAK aka Xride FreeBSD committer | FreeBSD since 2.2.6-R If a program is not working right, then send a patch From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 18:40:32 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D6BE616A473 for ; Tue, 26 Jun 2007 18:40:32 +0000 (UTC) (envelope-from eksffa@freebsdbrasil.com.br) Received: from capeta.freebsdbrasil.com.br (vrrp.freebsdbrasil.com.br [200.210.70.30]) by mx1.freebsd.org (Postfix) with SMTP id AED2213C465 for ; Tue, 26 Jun 2007 18:40:31 +0000 (UTC) (envelope-from eksffa@freebsdbrasil.com.br) Received: (qmail 41398 invoked from network); 26 Jun 2007 15:40:54 -0300 Received: by simscan 1.1.0 ppid: 41388, pid: 41389, t: 1.1416s scanners: clamav: 0.90.2/m:43/d:3087 spam: 3.1.1 X-Spam-Checker-Version: SpamAssassin: -last, FreeBSD Brasil LTDA rulesets: Yes X-Spam-Status: No, hits=0.1 required=3.7 Received: from unknown (HELO claire.freebsdbrasil.com.br) (201.58.72.108) by capeta.freebsdbrasil.com.br with SMTP; 26 Jun 2007 15:40:53 -0300 Message-ID: <46815D9A.6090903@freebsdbrasil.com.br> Date: Tue, 26 Jun 2007 15:40:26 -0300 From: Patrick Tracanelli Organization: FreeBSD Brasil LTDA User-Agent: Thunderbird 2.0.0.0 (X11/20070612) MIME-Version: 1.0 To: Maxim Konovalov References: <467C343C.60707@freebsdbrasil.com.br> <20070626221207.R410@mp2.macomnet.net> In-Reply-To: <20070626221207.R410@mp2.macomnet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: hackers@freebsd.org Subject: Re: UPEK/TouchChip Biometric Device problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 18:40:32 -0000 Maxim Konovalov wrote: > On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote: > >> Hello all, >> >> I have used the mentioned devices on FreeBSD 5.4 in the past, and >> they worked just fine, but now I get problems with the same device, >> on top of 6.2-STABLE and also 7.0-CURRENT. >> > [...] > > Just for the record: the above mentioned device works fine on lenovo > x60s and 6.2-STABLE. > Is it 0×0483 vendor and 0×2016 device? Which revision? Can you please send the relevant output from usbdevs -v and the ugen device from /var/run/dmesg.boot? -- Patrick Tracanelli From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 18:43:12 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 934CC16A421 for ; Tue, 26 Jun 2007 18:43:12 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.freebsd.org (Postfix) with ESMTP id 1A65D13C469 for ; Tue, 26 Jun 2007 18:43:11 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.8) with ESMTP id l5QIhASg050241; Tue, 26 Jun 2007 22:43:10 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Tue, 26 Jun 2007 22:43:10 +0400 (MSD) From: Maxim Konovalov To: Patrick Tracanelli In-Reply-To: <46815D9A.6090903@freebsdbrasil.com.br> Message-ID: <20070626224201.S50072@mp2.macomnet.net> References: <467C343C.60707@freebsdbrasil.com.br> <20070626221207.R410@mp2.macomnet.net> <46815D9A.6090903@freebsdbrasil.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: hackers@freebsd.org Subject: Re: UPEK/TouchChip Biometric Device problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 18:43:12 -0000 On Tue, 26 Jun 2007, 15:40-0300, Patrick Tracanelli wrote: > Maxim Konovalov wrote: > > On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote: > > > > > Hello all, > > > > > > I have used the mentioned devices on FreeBSD 5.4 in the past, and > > > they worked just fine, but now I get problems with the same device, > > > on top of 6.2-STABLE and also 7.0-CURRENT. > > > > > [...] > > > > Just for the record: the above mentioned device works fine on lenovo > > x60s and 6.2-STABLE. > > > > Is it 0?0483 vendor and 0?2016 device? Which revision? Can you > please send the relevant output from usbdevs -v and the ugen device > from /var/run/dmesg.boot? > port 2 addr 2: full speed, power 100 mA, config 1, Biometric Coprocessor(0x2016), STMicroelectronics(0x0483), rev 0.01 Controller /dev/usb4: ugen0: STMicroelectronics Biometric Coprocessor, rev 1.00/0.01, addr 2 -- Maxim Konovalov From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 18:51:23 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4FFE016A400 for ; Tue, 26 Jun 2007 18:51:23 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.freebsd.org (Postfix) with ESMTP id B2B7C13C4AD for ; Tue, 26 Jun 2007 18:51:22 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.8) with ESMTP id l5QIDRiI049203; Tue, 26 Jun 2007 22:13:28 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Tue, 26 Jun 2007 22:13:26 +0400 (MSD) From: Maxim Konovalov To: Patrick Tracanelli In-Reply-To: <467C343C.60707@freebsdbrasil.com.br> Message-ID: <20070626221207.R410@mp2.macomnet.net> References: <467C343C.60707@freebsdbrasil.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: hackers@freebsd.org Subject: Re: UPEK/TouchChip Biometric Device problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 18:51:23 -0000 On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote: > Hello all, > > I have used the mentioned devices on FreeBSD 5.4 in the past, and > they worked just fine, but now I get problems with the same device, > on top of 6.2-STABLE and also 7.0-CURRENT. > [...] Just for the record: the above mentioned device works fine on lenovo x60s and 6.2-STABLE. -- Maxim Konovalov From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 18:59:44 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D182516A468 for ; Tue, 26 Jun 2007 18:59:44 +0000 (UTC) (envelope-from eksffa@freebsdbrasil.com.br) Received: from capeta.freebsdbrasil.com.br (vrrp.freebsdbrasil.com.br [200.210.70.30]) by mx1.freebsd.org (Postfix) with SMTP id DCE5413C483 for ; Tue, 26 Jun 2007 18:59:43 +0000 (UTC) (envelope-from eksffa@freebsdbrasil.com.br) Received: (qmail 45921 invoked from network); 26 Jun 2007 16:00:07 -0300 Received: by simscan 1.1.0 ppid: 45450, pid: 45453, t: 54.1305s scanners: clamav: 0.90.2/m:43/d:3087 spam: 3.1.1 X-Spam-Checker-Version: SpamAssassin: -last, FreeBSD Brasil LTDA rulesets: Yes X-Spam-Status: No, hits=-2.2 required=3.7 Received: from unknown (HELO claire.freebsdbrasil.com.br) (201.58.72.108) by capeta.freebsdbrasil.com.br with SMTP; 26 Jun 2007 15:59:13 -0300 Message-ID: <468161E6.8030403@freebsdbrasil.com.br> Date: Tue, 26 Jun 2007 15:58:46 -0300 From: Patrick Tracanelli Organization: FreeBSD Brasil LTDA User-Agent: Thunderbird 2.0.0.0 (X11/20070612) MIME-Version: 1.0 To: Maxim Konovalov References: <467C343C.60707@freebsdbrasil.com.br> <20070626221207.R410@mp2.macomnet.net> <46815D9A.6090903@freebsdbrasil.com.br> <20070626224201.S50072@mp2.macomnet.net> In-Reply-To: <20070626224201.S50072@mp2.macomnet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: UPEK/TouchChip Biometric Device problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 18:59:44 -0000 Maxim Konovalov wrote: > On Tue, 26 Jun 2007, 15:40-0300, Patrick Tracanelli wrote: > >> Maxim Konovalov wrote: >>> On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote: >>> >>>> Hello all, >>>> >>>> I have used the mentioned devices on FreeBSD 5.4 in the past, and >>>> they worked just fine, but now I get problems with the same device, >>>> on top of 6.2-STABLE and also 7.0-CURRENT. >>>> >>> [...] >>> >>> Just for the record: the above mentioned device works fine on lenovo >>> x60s and 6.2-STABLE. >>> >> Is it 0?0483 vendor and 0?2016 device? Which revision? Can you >> please send the relevant output from usbdevs -v and the ugen device >> from /var/run/dmesg.boot? >> > port 2 addr 2: full speed, power 100 mA, config 1, Biometric > Coprocessor(0x2016), STMicroelectronics(0x0483), rev 0.01 > Controller /dev/usb4: > > ugen0: STMicroelectronics Biometric Coprocessor, rev 1.00/0.01, addr 2 > Exactly the same. Did you do anything different from using securyt/bioapi, securiy/bsp_upektfmess and security/pam_bsdbioapi and creating birdb.conf? -- Patrick Tracanelli From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 19:06:09 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D0DC016A400 for ; Tue, 26 Jun 2007 19:06:09 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.freebsd.org (Postfix) with ESMTP id 4156713C468 for ; Tue, 26 Jun 2007 19:06:09 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.8) with ESMTP id l5QJ67mN050760; Tue, 26 Jun 2007 23:06:08 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Tue, 26 Jun 2007 23:06:07 +0400 (MSD) From: Maxim Konovalov To: Patrick Tracanelli In-Reply-To: <468161E6.8030403@freebsdbrasil.com.br> Message-ID: <20070626230516.S50072@mp2.macomnet.net> References: <467C343C.60707@freebsdbrasil.com.br> <20070626221207.R410@mp2.macomnet.net> <46815D9A.6090903@freebsdbrasil.com.br> <20070626224201.S50072@mp2.macomnet.net> <468161E6.8030403@freebsdbrasil.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: hackers@freebsd.org Subject: Re: UPEK/TouchChip Biometric Device problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 19:06:10 -0000 [...] > Exactly the same. Did you do anything different from using > securyt/bioapi, securiy/bsp_upektfmess and security/pam_bsdbioapi > and creating birdb.conf? > No, I didn't. It works out of the box. -- Maxim Konovalov From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 19:10:39 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C061816A469 for ; Tue, 26 Jun 2007 19:10:39 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id 1C0F913C489 for ; Tue, 26 Jun 2007 19:10:38 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l5QJAYWo003647; Wed, 27 Jun 2007 05:10:34 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l5QJAWQb003646; Wed, 27 Jun 2007 05:10:32 +1000 (EST) (envelope-from peter) Date: Wed, 27 Jun 2007 05:10:32 +1000 From: Peter Jeremy To: =?iso-8859-1?Q?=D6zkan?= KIRIK Message-ID: <20070626191032.GZ3397@turion.vk2pj.dyndns.org> References: <467CD36D.4020709@mersin.edu.tr> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: <467CD36D.4020709@mersin.edu.tr> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.15 (2007-04-06) Cc: freebsd-hackers@freebsd.org Subject: Re: 6.1 - amd64 arch. Hangs twice a day, how can i debug problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 19:10:39 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Jun-23 11:01:49 +0300, zkan KIRIK wrote: > I have a FreeBSD 6.1 - STABLE 200609 gateway have 3 up interfaces. > First one connected to 16Mbps Internet Connection, > Next onet connected to DMZ Zone (192.168.0.0/24 network) > The Last interface connected to Local network. > > this system hangs twice a day. Keyboard doesnt work, everything locks, no= =20 > network reponse! > For a quick solution i wrote a crontab that reboots system at 20.00 PM &= =20 > 06.00 AM. > > How can I find the problem which hangs system? Is there any method for th= is. This sort of thing is very difficult to debug. My suggestions would be: - Check for flaky hardware - maybe run memtest86 overnight. - Run one of the following: while sleep 5; do date; vmstat -m; done while sleep 5; do date; netstat -m; done top systat -v 2 on a VTY or a serial console and see when it's dying and what was happening shortly before. - Check if anything unusual (cron jobs or unusual external activity) happens at the time it dies. - You may be able to debug a frozen system via firewire > Or any known bug reports at this release ? I don't recall this particuar problem being reported. That said, you appear to be running a 9 month old -stable - have you considered updating to either 6.2 or a more recent -stable? --=20 Peter Jeremy --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGgWSo/opHv/APuIcRAjTKAJ9FR2JWTm9/KDcmyg78xu6KzTfe2gCcCxYv 8Jn7wE5zQMBNp+Tj2HhL8EM= =z7iV -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 20:25:29 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D5AE916A41F; Tue, 26 Jun 2007 20:25:29 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id 65DB913C46A; Tue, 26 Jun 2007 20:25:29 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by koef.zs64.net (8.14.1/8.14.1) with ESMTP id l5QJoVYE029859; Tue, 26 Jun 2007 21:50:31 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.1/8.14.1/Submit) id l5QJoVSB029858; Tue, 26 Jun 2007 15:50:31 -0400 (EDT) (envelope-from cracauer) Date: Tue, 26 Jun 2007 15:50:31 -0400 From: Martin Cracauer To: Martin Turgeon Message-ID: <20070626195031.GA29545@cons.org> References: <467EFF06.6020902@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <467EFF06.6020902@gmail.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 20:25:29 -0000 Martin Turgeon wrote on Sun, Jun 24, 2007 at 07:32:22PM -0400: > Hi, > > I recently installed AMD64 6.2 Release on 2 PowerEdge servers, both with > dual core Xeon (3070 and 5110). I extensively benchmarked different compiler options on Xeon 5160 (3.0 GHz Core2) with gcc-4.1.2 and gcc-4.2. Apart from very minor differences the best was plain "-O3 -finline-limit=xxx" where xxx was different by code, some code ran faster with 400 and other code with 750 (both beating the 600 default). The inline limit made a bigger difference than most of the other options and I actually ended up compiling parts of my code with a differen inline-limit than others. The result was within a percent of all highly tuned CPU-specific options like -march=k8 -msse3 -mfpmath=sse -ffast-math, and I went through most iterations. This means that locking your code to one x86_64 implementation and locking out either AMD or Intel is not worth the trouble. Testing was done on gcc-4.2.1 and later partially verified with gcc-4.2. Gcc-4.2 was a little slower overall but the same options were about the same speed. I also tested with Intel's icc 9.0 which didn't even come close to either gcc, even if you were willing to wait 10 times as long for compilation to finish (for inter-object file optimizations). No inlining limit would bring Intel's icc code size down to close what gcc had and subsequently performance was bad. gcc-3.4 was blown out of the water by gcc-4, too. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 23:14:00 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 71E0B16A473 for ; Tue, 26 Jun 2007 23:14:00 +0000 (UTC) (envelope-from stef@memberwebs.com) Received: from mx.npubs.com (mail.wsfamily.com [209.66.100.224]) by mx1.freebsd.org (Postfix) with ESMTP id 623A013C483 for ; Tue, 26 Jun 2007 23:14:00 +0000 (UTC) (envelope-from stef@memberwebs.com) Received: from mx.npubs.com (avhost [209.66.100.194]) by mx.npubs.com (Postfix) with ESMTP id 4A5B1D4C17 for ; Tue, 26 Jun 2007 22:43:38 +0000 (UTC) Received: from northstar-srv2 (unknown [172.27.2.11]) by mx.npubs.com (Postfix) with ESMTP id A6E25D4C0D for ; Tue, 26 Jun 2007 22:43:37 +0000 (UTC) From: Stef Walter User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20070626224337.A6E25D4C0D@mx.npubs.com> X-Virus-Scanned: ClamAV using ClamSMTP Date: Tue, 26 Jun 2007 22:43:38 +0000 (UTC) X-Mailman-Approved-At: Tue, 26 Jun 2007 23:16:12 +0000 Subject: devfs symlink over device doesn't work X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 23:14:00 -0000 After deleting a device in devfs, any symlink placed over it results in ENOENT. # cd /dev # rm console # touch /var/log/console # ln -s /var/log/console console # ls -l console ls: console: No such file or directory I'd like to fix this behavior. Or is there a reason for it that I'm not seeing? Reasoning: I'm using devfs in jails, and I'd like anything written (by user space programs, syslogd, etc...) to /dev/console to go to a file in the jail. So at jail startup I'd like to put a symlink over /dev/console to a normal file. Cheers, Stef Walter From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 27 00:52:55 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5833D16A41F for ; Wed, 27 Jun 2007 00:52:55 +0000 (UTC) (envelope-from george@mail.reprise.com) Received: from reprise.com (69-30-97-91.dv1mn.easystreet.com [69.30.97.91]) by mx1.freebsd.org (Postfix) with ESMTP id 1683D13C44B for ; Wed, 27 Jun 2007 00:52:55 +0000 (UTC) (envelope-from george@mail.reprise.com) Received: from mail.reprise.com (localhost [127.0.0.1]) by reprise.com (8.13.8/8.13.8) with ESMTP id l5R0XkoR084993 for ; Tue, 26 Jun 2007 17:33:46 -0700 (PDT) Received: (from george@localhost) by mail.reprise.com (8.13.8/8.13.8/Submit) id l5R0Xkf9084990; Tue, 26 Jun 2007 17:33:46 -0700 (PDT) (envelope-from george) Date: Tue, 26 Jun 2007 17:33:46 -0700 (PDT) Message-Id: <200706270033.l5R0Xkf9084990@mail.reprise.com> From: george+freebsd@m5p.com To: freebsd-hackers@freebsd.org X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.57 on 69.30.97.91 Subject: Gigabit Ethernet w/Jumbo Frames X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 00:52:55 -0000 I'm having poor luck trying to use NFS over a gigabit ethernet using jumbo frames. By all indications, my switch (Netgear GS608) forwards jumbo frames with no difficulty, but my Realtek 8169-based cards seem unreceptive to the idea, giving many watchdog timeouts and other obscure log messages. One server is amd64 and my clients are i386, but I think I've ruled that out as the problem because I see errors evern with an i386 server. So I strongly suspect my network cards at the moment. What gigabit ethernet cards do you use for reliable performance with jumbo frames? -- George Mitchell From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 26 23:25:47 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A1FD716A400 for ; Tue, 26 Jun 2007 23:25:47 +0000 (UTC) (envelope-from stef@memberwebs.com) Received: from mx.npubs.com (mail.writemehere.com [209.66.100.224]) by mx1.freebsd.org (Postfix) with ESMTP id 91B9513C45E for ; Tue, 26 Jun 2007 23:25:47 +0000 (UTC) (envelope-from stef@memberwebs.com) Received: from mx.npubs.com (avhost [209.66.100.194]) by mx.npubs.com (Postfix) with ESMTP id 52D08D4C38 for ; Tue, 26 Jun 2007 23:25:47 +0000 (UTC) Received: from northstar-srv2 (unknown [172.27.2.11]) by mx.npubs.com (Postfix) with ESMTP id C4EE1D4C37 for ; Tue, 26 Jun 2007 23:25:46 +0000 (UTC) From: Stef Walter User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <4681849F.3050308@memberwebs.com> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20070626232546.C4EE1D4C37@mx.npubs.com> X-Virus-Scanned: ClamAV using ClamSMTP Date: Tue, 26 Jun 2007 23:25:47 +0000 (UTC) X-Mailman-Approved-At: Wed, 27 Jun 2007 00:57:59 +0000 Subject: Re: devfs symlink over device doesn't work X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 23:25:47 -0000 Stef Walter wrote: > After deleting a device in devfs, any symlink placed over it results in > ENOENT. > > I'd like to fix this behavior. Or is there a reason for it that I'm not > seeing? Filed a bug report with a patch that solves the issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=114057 Cheers, Stef Walter From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 27 01:36:30 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8F4E916A400 for ; Wed, 27 Jun 2007 01:36:30 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 6E2E013C44B for ; Wed, 27 Jun 2007 01:36:30 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.1/8.13.8) with ESMTP id l5R1aHkR017352; Tue, 26 Jun 2007 18:36:17 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.1/8.13.8/Submit) id l5R1aCoD017351; Tue, 26 Jun 2007 18:36:12 -0700 (PDT) (envelope-from sgk) Date: Tue, 26 Jun 2007 18:36:12 -0700 From: Steve Kargl To: george+freebsd@m5p.com Message-ID: <20070627013612.GA17267@troutmask.apl.washington.edu> References: <200706270033.l5R0Xkf9084990@mail.reprise.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706270033.l5R0Xkf9084990@mail.reprise.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org Subject: Re: Gigabit Ethernet w/Jumbo Frames X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 01:36:30 -0000 On Tue, Jun 26, 2007 at 05:33:46PM -0700, george+freebsd@m5p.com wrote: > I'm having poor luck trying to use NFS over a gigabit ethernet using > jumbo frames. By all indications, my switch (Netgear GS608) forwards > jumbo frames with no difficulty, but my Realtek 8169-based cards seem > unreceptive to the idea, giving many watchdog timeouts and other > obscure log messages. One server is amd64 and my clients are i386, > but I think I've ruled that out as the problem because I see errors > evern with an i386 server. So I strongly suspect my network cards at > the moment. What gigabit ethernet cards do you use for reliable > performance with jumbo frames? -- George Mitchell > Are you setting any sysctl tunables? There have been recent reports of watchdog timeout problems with xl, bge, and em devices. I've manage to work around the timeout on bge with net.inet.tcp.sendspace=131072 net.inet.tcp.recvspace=131072 net.inet.tcp.path_mtu_discovery=0 net.inet.udp.recvspace=65536 net.inet.raw.recvspace=16384 hw.pci.enable_msix=0 hw.pci.enable_msi=0 kern.ipc.nmbclusters=50000 kern.timecounter.hardware=ACPI-fast -- Steve From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 27 03:02:41 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E595816A41F for ; Wed, 27 Jun 2007 03:02:41 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.236]) by mx1.freebsd.org (Postfix) with ESMTP id 895F713C455 for ; Wed, 27 Jun 2007 03:02:41 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by nz-out-0506.google.com with SMTP id 34so28035nzf for ; Tue, 26 Jun 2007 20:02:40 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=rr5wU7HMmYKZ12suLnNCKgc8VS4ZDG2/ftfb6pbsZXRwCtnzZ8m6mmUupoX4SZ6/oj4uPblIfiGtNvlefTwhPUQvLBO4SN+7oW1ENp02YpOwdpNYJQ9c6Z0X2d2jApO7CLRFQg2jsdB6GAZrEgn5D7F+UnsRPJDJqrLp68P+LGI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=j1cZbi2D7MrHCK7/0kRoRBrs/CX2nVO1Is+s9DB0kHEBKq9Aw777hRY95TI7znhZRktJNUwrpSig8B50xJfn5MB5urr7jIHirE31myLMPqrLMRP371GYxCVyPfj/JjuyLh48mymwqYTJvVbIL/HOCgA2h+NlP1cTe38b7E8py9U= Received: by 10.115.75.1 with SMTP id c1mr36602wal.1182911606804; Tue, 26 Jun 2007 19:33:26 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id m5sm9697875wag.2007.06.26.19.33.23 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Jun 2007 19:33:25 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l5R2XKkD045537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jun 2007 11:33:20 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l5R2XJSb045536; Wed, 27 Jun 2007 11:33:19 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 27 Jun 2007 11:33:17 +0900 From: Pyun YongHyeon To: george+freebsd@m5p.com Message-ID: <20070627023317.GA45303@cdnetworks.co.kr> References: <200706270033.l5R0Xkf9084990@mail.reprise.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706270033.l5R0Xkf9084990@mail.reprise.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: Gigabit Ethernet w/Jumbo Frames X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 03:02:42 -0000 On Tue, Jun 26, 2007 at 05:33:46PM -0700, george+freebsd@m5p.com wrote: > I'm having poor luck trying to use NFS over a gigabit ethernet using > jumbo frames. By all indications, my switch (Netgear GS608) forwards > jumbo frames with no difficulty, but my Realtek 8169-based cards seem > unreceptive to the idea, giving many watchdog timeouts and other > obscure log messages. One server is amd64 and my clients are i386, > but I think I've ruled that out as the problem because I see errors > evern with an i386 server. So I strongly suspect my network cards at > the moment. What gigabit ethernet cards do you use for reliable > performance with jumbo frames? -- George Mitchell > See http://lists.freebsd.org/pipermail/freebsd-current/2007-May/072845.html -- Regards, Pyun YongHyeon From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 27 06:22:26 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E2BF216A469 for ; Wed, 27 Jun 2007 06:22:26 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.freebsd.org (Postfix) with ESMTP id B197A13C447 for ; Wed, 27 Jun 2007 06:22:26 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (84rvcwo2lhs7qfhf@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id l5R6COTQ015967; Tue, 26 Jun 2007 23:12:24 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id l5R6CNgw015966; Tue, 26 Jun 2007 23:12:23 -0700 (PDT) (envelope-from jmg) Date: Tue, 26 Jun 2007 23:12:23 -0700 From: John-Mark Gurney To: george+freebsd@m5p.com Message-ID: <20070627061223.GE1221@funkthat.com> Mail-Followup-To: george+freebsd@m5p.com, freebsd-hackers@freebsd.org References: <200706270033.l5R0Xkf9084990@mail.reprise.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706270033.l5R0Xkf9084990@mail.reprise.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-hackers@freebsd.org Subject: Re: Gigabit Ethernet w/Jumbo Frames X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 06:22:27 -0000 george+freebsd@m5p.com wrote this message on Tue, Jun 26, 2007 at 17:33 -0700: > I'm having poor luck trying to use NFS over a gigabit ethernet using > jumbo frames. By all indications, my switch (Netgear GS608) forwards > jumbo frames with no difficulty, but my Realtek 8169-based cards seem Are you sure? I just tried w/ my GS608 again, and it still doesn't pass jumbo frames... I specifically bought a second switch, an SMC 8508T so that I could work on jumbo frame support... I took my MBP to the SMC and verified that I could ping 5k packets w/o fragmentation between the two (MBP and a FreeBSD-current box w/ an em card) boxes, and then took my MBP to the Netgear, and the remote box would not see the large pings... I just checked Netgear's website, and they do list Jumbo Frame support.. Either I have an old switch and newer ones support it, or they depend upon that most people can't figure out to make jumbo frames work reliabily and depend upon people just using 1500 byte frames... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 27 08:22:27 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5AD2416A400 for ; Wed, 27 Jun 2007 08:22:27 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.227]) by mx1.freebsd.org (Postfix) with ESMTP id 000E513C45A for ; Wed, 27 Jun 2007 08:22:26 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by nz-out-0506.google.com with SMTP id 34so83579nzf for ; Wed, 27 Jun 2007 01:22:26 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=oNAVYH2G9KXZDEwvdJYZS+0CHVhiun3VMTdOHGxveo3X9d7U25z8djsZ+dPAMNZk9jkvRkGYFP+VXaMbIW5/iBR/et4NdwrG+pT/bb6gw/g4XKRzFQ6AxN03dJMZpgYOWtaVk/R63BDceVX4qgT7ccyi1ezKgHWs0Cc1mULQnlA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=cbRNVba08/Mo355G7uvM9ePKv0408SAJcq6dBXK9I0UtcFUohmVwwmZT3Y5EgqWcqMd5ph62qSpOGswq91mxRgO7m/uVCi3R3O2V6fURutqUXp1NziG5115lU6IXwCDijBhZWMej0ov+Y6IXgv2wa8BW9qIX278XwtcQdjJegHw= Received: by 10.114.199.1 with SMTP id w1mr288571waf.1182932545880; Wed, 27 Jun 2007 01:22:25 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id v35sm3744898wah.2007.06.27.01.22.23 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Jun 2007 01:22:25 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l5R8MHA2046384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jun 2007 17:22:17 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l5R8MG6i046383; Wed, 27 Jun 2007 17:22:16 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 27 Jun 2007 17:22:16 +0900 From: Pyun YongHyeon To: george+freebsd@m5p.com, freebsd-hackers@freebsd.org Message-ID: <20070627082216.GB45303@cdnetworks.co.kr> References: <200706270033.l5R0Xkf9084990@mail.reprise.com> <20070627061223.GE1221@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070627061223.GE1221@funkthat.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: Gigabit Ethernet w/Jumbo Frames X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 08:22:27 -0000 On Tue, Jun 26, 2007 at 11:12:23PM -0700, John-Mark Gurney wrote: > george+freebsd@m5p.com wrote this message on Tue, Jun 26, 2007 at 17:33 -0700: > > I'm having poor luck trying to use NFS over a gigabit ethernet using > > jumbo frames. By all indications, my switch (Netgear GS608) forwards > > jumbo frames with no difficulty, but my Realtek 8169-based cards seem > > Are you sure? I just tried w/ my GS608 again, and it still doesn't > pass jumbo frames... I specifically bought a second switch, an SMC > 8508T so that I could work on jumbo frame support... I took my MBP > to the SMC and verified that I could ping 5k packets w/o fragmentation > between the two (MBP and a FreeBSD-current box w/ an em card) boxes, > and then took my MBP to the Netgear, and the remote box would not see > the large pings... > > I just checked Netgear's website, and they do list Jumbo Frame support.. > Either I have an old switch and newer ones support it, or they depend > upon that most people can't figure out to make jumbo frames work > reliabily and depend upon people just using 1500 byte frames... > I guess re(4) should not generate watchdog errors even if intermediate switches drop/fragment jumbo frames. -- Regards, Pyun YongHyeon From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 27 08:28:06 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 376DA16A421 for ; Wed, 27 Jun 2007 08:28:06 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp02.sth.basefarm.net (ch-smtp02.sth.basefarm.net [80.76.149.213]) by mx1.freebsd.org (Postfix) with ESMTP id B940113C43E for ; Wed, 27 Jun 2007 08:28:05 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-10-135.bredband.comhem.se ([83.253.10.135]:51035 helo=falcon.midgard.homeip.net) by ch-smtp02.sth.basefarm.net with smtp (Exim 4.66) (envelope-from ) id 1I3Sdu-0001L2-6o for freebsd-hackers@freebsd.org; Wed, 27 Jun 2007 10:12:50 +0200 Received: (qmail 80665 invoked from network); 27 Jun 2007 10:12:47 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with SMTP; 27 Jun 2007 10:12:47 +0200 Received: (qmail 30909 invoked by uid 1001); 27 Jun 2007 10:12:47 +0200 Date: Wed, 27 Jun 2007 10:12:47 +0200 From: Erik Trulsson To: george+freebsd@m5p.com, freebsd-hackers@freebsd.org Message-ID: <20070627081247.GA30818@owl.midgard.homeip.net> Mail-Followup-To: george+freebsd@m5p.com, freebsd-hackers@freebsd.org References: <200706270033.l5R0Xkf9084990@mail.reprise.com> <20070627061223.GE1221@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070627061223.GE1221@funkthat.com> User-Agent: Mutt/1.5.14 (2007-02-12) X-Originating-IP: 83.253.10.135 X-ACL-Warn: Too high rate of unknown addresses received from you X-Scan-Result: No virus found in message 1I3Sdu-0001L2-6o. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1I3Sdu-0001L2-6o f2e0edbb78f1deaf8c095b3e495f8fe5 Cc: Subject: Re: Gigabit Ethernet w/Jumbo Frames X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 08:28:06 -0000 On Tue, Jun 26, 2007 at 11:12:23PM -0700, John-Mark Gurney wrote: > george+freebsd@m5p.com wrote this message on Tue, Jun 26, 2007 at 17:33 -0700: > > I'm having poor luck trying to use NFS over a gigabit ethernet using > > jumbo frames. By all indications, my switch (Netgear GS608) forwards > > jumbo frames with no difficulty, but my Realtek 8169-based cards seem > > Are you sure? I just tried w/ my GS608 again, and it still doesn't > pass jumbo frames... I specifically bought a second switch, an SMC > 8508T so that I could work on jumbo frame support... I took my MBP > to the SMC and verified that I could ping 5k packets w/o fragmentation > between the two (MBP and a FreeBSD-current box w/ an em card) boxes, > and then took my MBP to the Netgear, and the remote box would not see > the large pings... > > I just checked Netgear's website, and they do list Jumbo Frame support.. > Either I have an old switch and newer ones support it, or they depend > upon that most people can't figure out to make jumbo frames work > reliabily and depend upon people just using 1500 byte frames... There are (at least) two different versions of the Netgear GS608 (and some other Netgear switches.) The older ones do not support Jumbo Frames, while the newer ones are supposed to do it. See http://kbserver.netgear.com/inquira/default.asp?ui_mode=answer&prior_transaction_id=5016326&action_code=5&highlight_info=16778279,200,201&turl=http%3A%2F%2Fkbserver.netgear.com%2Fkb_web_files%2Fn101624.asp&answer_id=6141591#__highlight for some more information on the different versions of some Netgear switches. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 27 09:23:29 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AC69D16A41F for ; Wed, 27 Jun 2007 09:23:29 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.freebsd.org (Postfix) with ESMTP id 698BC13C4D1 for ; Wed, 27 Jun 2007 09:23:29 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (ho57g3knsi3rv3bd@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id l5R9NS87018846; Wed, 27 Jun 2007 02:23:28 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id l5R9NSb3018845; Wed, 27 Jun 2007 02:23:28 -0700 (PDT) (envelope-from jmg) Date: Wed, 27 Jun 2007 02:23:28 -0700 From: John-Mark Gurney To: george+freebsd@m5p.com, freebsd-hackers@freebsd.org Message-ID: <20070627092327.GF1221@funkthat.com> Mail-Followup-To: george+freebsd@m5p.com, freebsd-hackers@freebsd.org References: <200706270033.l5R0Xkf9084990@mail.reprise.com> <20070627061223.GE1221@funkthat.com> <20070627081247.GA30818@owl.midgard.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070627081247.GA30818@owl.midgard.homeip.net> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: Subject: Re: Gigabit Ethernet w/Jumbo Frames X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 09:23:29 -0000 Erik Trulsson wrote this message on Wed, Jun 27, 2007 at 10:12 +0200: > On Tue, Jun 26, 2007 at 11:12:23PM -0700, John-Mark Gurney wrote: > > george+freebsd@m5p.com wrote this message on Tue, Jun 26, 2007 at 17:33 -0700: > > > I'm having poor luck trying to use NFS over a gigabit ethernet using > > > jumbo frames. By all indications, my switch (Netgear GS608) forwards > > > jumbo frames with no difficulty, but my Realtek 8169-based cards seem > > > > Are you sure? I just tried w/ my GS608 again, and it still doesn't > > pass jumbo frames... I specifically bought a second switch, an SMC > > 8508T so that I could work on jumbo frame support... I took my MBP > > to the SMC and verified that I could ping 5k packets w/o fragmentation > > between the two (MBP and a FreeBSD-current box w/ an em card) boxes, > > and then took my MBP to the Netgear, and the remote box would not see > > the large pings... > > > > I just checked Netgear's website, and they do list Jumbo Frame support.. > > Either I have an old switch and newer ones support it, or they depend > > upon that most people can't figure out to make jumbo frames work > > reliabily and depend upon people just using 1500 byte frames... > > There are (at least) two different versions of the Netgear GS608 (and some > other Netgear switches.) The older ones do not support Jumbo Frames, while > the newer ones are supposed to do it. See > > http://kbserver.netgear.com/inquira/default.asp?ui_mode=answer&prior_transaction_id=5016326&action_code=5&highlight_info=16778279,200,201&turl=http%3A%2F%2Fkbserver.netgear.com%2Fkb_web_files%2Fn101624.asp&answer_id=6141591#__highlight > > for some more information on the different versions of some Netgear > switches. My serial number isn't listed there... It starts w/ GS21146, but it's around 2 years old so it's probably v1... Thanks for the link. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 27 13:24:07 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A654716A468 for ; Wed, 27 Jun 2007 13:24:07 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 4DA0913C455 for ; Wed, 27 Jun 2007 13:24:07 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 45293 invoked by uid 1001); 27 Jun 2007 13:22:26 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Wed, 27 Jun 2007 09:22:25 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18050.25745.401646.292347@bhuda.mired.org> Date: Wed, 27 Jun 2007 09:22:25 -0400 To: Martin Cracauer In-Reply-To: <20070626195031.GA29545@cons.org> References: <467EFF06.6020902@gmail.com> <20070626195031.GA29545@cons.org> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Cc: freebsd-hackers@freebsd.org, Martin Turgeon , freebsd-amd64@freebsd.org Subject: Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 13:24:07 -0000 In <20070626195031.GA29545@cons.org>, Martin Cracauer typed: > Martin Turgeon wrote on Sun, Jun 24, 2007 at 07:32:22PM -0400: > > Hi, > > > > I recently installed AMD64 6.2 Release on 2 PowerEdge servers, both with > > dual core Xeon (3070 and 5110). > I extensively benchmarked different compiler options on Xeon 5160 (3.0 > GHz Core2) with gcc-4.1.2 and gcc-4.2. Using what benchmark? That makes a *lot* of difference. > The result was within a percent of all highly tuned CPU-specific > options like -march=k8 -msse3 -mfpmath=sse -ffast-math, and I went > through most iterations. This means that locking your code to one > x86_64 implementation and locking out either AMD or Intel is not worth > the trouble. I don't think you've reached the correct conclusions. In particular, note that doing -mtune instead of -march won't lock you to a specific CPU, but will instead choose instructions/sequences optimized for your CPU. So it's a minor win with no downside. With the x86_64bit architecture, you have three choices: unset (x86 + MMX/SSE/SSE2), nocona (intel, with SSE3) and athlon64 (amd, with 3dNOW!). So changing your Xeon to nocona will just enablie SSE3. The SSE3 extensions are mostly things for doing "horizontal" computations inside the SSE register file. So unless your benchmark was doing lots of work on arrays of floats, it's unlikely you actually tested the SSE3 extensions, in which case all you did was test -mtune. Without testing the extra instructions, we don't know whether using them is worth the trouble or not, and you didn't say what your test was. 3dNOW! is an alternative, instead of an extension, to SSE/SSE2 (and maybe SSE3). People who hack such things tell me it's much spiffier than the SSE instructions, so possibly enabling it would cause those instructions to be used instead of the SSE instructions the compiler currently uses. But you didn't test this case, so we don't know how much difference it would make, and hence whether or not it's worth locking your code to AMD to get it. Thanks, http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 27 13:31:17 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 18A2316A46D for ; Wed, 27 Jun 2007 13:31:17 +0000 (UTC) (envelope-from george@mail.reprise.com) Received: from reprise.com (69-30-97-91.dv1mn.easystreet.com [69.30.97.91]) by mx1.freebsd.org (Postfix) with ESMTP id CC69113C489 for ; Wed, 27 Jun 2007 13:31:16 +0000 (UTC) (envelope-from george@mail.reprise.com) Received: from mail.reprise.com (localhost [127.0.0.1]) by reprise.com (8.13.8/8.13.8) with ESMTP id l5RDVEOJ099565 for ; Wed, 27 Jun 2007 06:31:14 -0700 (PDT) Received: (from george@localhost) by mail.reprise.com (8.13.8/8.13.8/Submit) id l5RDVEAF099562; Wed, 27 Jun 2007 06:31:14 -0700 (PDT) (envelope-from george) Date: Wed, 27 Jun 2007 06:31:14 -0700 (PDT) Message-Id: <200706271331.l5RDVEAF099562@mail.reprise.com> From: george+freebsd@m5p.com To: freebsd-hackers@freebsd.org X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.57 on 69.30.97.91 Subject: Re: Gigabit Ethernet w/Jumbo Frames X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 13:31:17 -0000 Thanks to all for your suggestions! As soon as I have a chance to follow up on them (might not be for a couple of days), I'll let you known how it came out. -- George Mitchell From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 27 15:27:25 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2EC4216A468; Wed, 27 Jun 2007 15:27:25 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id B9DD213C45D; Wed, 27 Jun 2007 15:27:24 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by koef.zs64.net (8.14.1/8.14.1) with ESMTP id l5RFRNVl005378; Wed, 27 Jun 2007 17:27:23 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.1/8.14.1/Submit) id l5RFRMFW005376; Wed, 27 Jun 2007 11:27:22 -0400 (EDT) (envelope-from cracauer) Date: Wed, 27 Jun 2007 11:27:22 -0400 From: Martin Cracauer To: Mike Meyer Message-ID: <20070627152722.GA5217@cons.org> References: <467EFF06.6020902@gmail.com> <20070626195031.GA29545@cons.org> <18050.25745.401646.292347@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18050.25745.401646.292347@bhuda.mired.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org, Martin Cracauer , Martin Turgeon , freebsd-amd64@freebsd.org Subject: Re: Which CPUTYPE for a dualcore Xeon on AMD64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 15:27:25 -0000 Mike Meyer wrote on Wed, Jun 27, 2007 at 09:22:25AM -0400: > In <20070626195031.GA29545@cons.org>, Martin Cracauer typed: > > Martin Turgeon wrote on Sun, Jun 24, 2007 at 07:32:22PM -0400: > > > Hi, > > > > > > I recently installed AMD64 6.2 Release on 2 PowerEdge servers, both with > > > dual core Xeon (3070 and 5110). > > I extensively benchmarked different compiler options on Xeon 5160 (3.0 > > GHz Core2) with gcc-4.1.2 and gcc-4.2. > > Using what benchmark? That makes a *lot* of difference. A proprietory application. I should have mentioned it does almost no floating point, so the assumption to drop sse might not be valid. However, the differences in compiler flags were generally huge and and the simpler ones came out on or near the top. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 27 15:26:44 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2202516A46D for ; Wed, 27 Jun 2007 15:26:44 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32707.mail.mud.yahoo.com (web32707.mail.mud.yahoo.com [68.142.207.251]) by mx1.freebsd.org (Postfix) with SMTP id C7D1F13C448 for ; Wed, 27 Jun 2007 15:26:43 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 15434 invoked by uid 60001); 27 Jun 2007 15:00:02 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=nOjd7TGJVwTbIRDDiENPHwf2a32xQes7BqxcNsXMTdwM2IqvpSheVfa2buVuP7fY+RuCaaITjv7xlUkcmeEdQdtfhKUVamLr8SeKZshUCugigWJ50HJ/FwFN8OOiS/8LQZ5BITnEU3jZ15pjE1QmRly0kqpSuq55CM0RLd065bg=; X-YMail-OSG: 8dGFdEIVM1k_cMAa6s4YhgRz8_QEuy050Fu7BQ.80Qe.1.xn8aDycqC3oKCqxseA.RhPz0AZ0iusdqTsEtxgERl_05dpuexQQL3H7dBNIQ81CMT4wYy0vhP79ortSw-- Received: from [69.79.129.102] by web32707.mail.mud.yahoo.com via HTTP; Wed, 27 Jun 2007 17:00:02 CEST Date: Wed, 27 Jun 2007 17:00:02 +0200 (CEST) From: To: freebsd-hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <722528.14010.qm@web32707.mail.mud.yahoo.com> X-Mailman-Approved-At: Wed, 27 Jun 2007 15:44:04 +0000 Cc: Subject: MS Vista vs FreeBSD's bootloader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 15:26:44 -0000 Hi; FWIW, if you just got your new computer with Windows Vista installed and were hoping to dual boot FreeBSD on it, let me tell you that FreeBSD's bootloader will screw things up. Microsoft basically declared the war on alternative OSs so it seems vista doesn't like: - bootloaders different than the one used by Vista. - Making a non Vista partition active. I did what I used to do with XP: I resized the Windows partition with a liveCD and QTparted, Installed FreeBSD with booteasy.. and surprise... Windows Vista won't run again. I then rescued the Vista installation with the install CD (good thing they included that this time, and not only the preinstalled OS!), and looked on the -net for something called EasyBCD, which looks like it will solve the problem by reconfiguring the Vista bootloader. cheers, Pedro. ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 28 02:08:31 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8064516A469 for ; Thu, 28 Jun 2007 02:08:31 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.freebsd.org (Postfix) with ESMTP id 5026F13C46A for ; Thu, 28 Jun 2007 02:08:31 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9] (may be forged)) by mxout4.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l5S28Ufg017551 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 27 Jun 2007 19:08:30 -0700 X-Auth-Received: from [192.168.10.45] (c-24-10-12-194.hsd1.ca.comcast.net [24.10.12.194]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l5S28UBl026111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 27 Jun 2007 19:08:30 -0700 Message-ID: <46831822.4090600@u.washington.edu> Date: Wed, 27 Jun 2007 19:08:34 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: pfgshield-freebsd@yahoo.com References: <722528.14010.qm@web32707.mail.mud.yahoo.com> In-Reply-To: <722528.14010.qm@web32707.mail.mud.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.3.2.304607, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.27.184633 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Cc: freebsd-hackers@FreeBSD.org Subject: Re: MS Vista vs FreeBSD's bootloader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 02:08:31 -0000 pfgshield-freebsd@yahoo.com wrote: > Hi; > > FWIW, if you just got your new computer with Windows Vista installed and were > hoping to dual boot FreeBSD on it, let me tell you that FreeBSD's bootloader > will screw things up. > > Microsoft basically declared the war on alternative OSs so it seems vista > doesn't like: > - bootloaders different than the one used by Vista. > - Making a non Vista partition active. > > I did what I used to do with XP: I resized the Windows partition with a liveCD > and QTparted, Installed FreeBSD with booteasy.. and surprise... Windows Vista > won't run again. > > I then rescued the Vista installation with the install CD (good thing they > included that this time, and not only the preinstalled OS!), and looked on the > -net for something called EasyBCD, which looks like it will solve the problem > by reconfiguring the Vista bootloader. > > cheers, > > Pedro. > Their excuse is probably to keep (some of the less intelligent) users out there from booting using their own media or alternate means. M$ really must have something important in their bootloader... -Garrett From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 28 03:38:33 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 01E8D16A400 for ; Thu, 28 Jun 2007 03:38:33 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from ls405.t-com.hr (ls405.t-com.hr [195.29.150.135]) by mx1.freebsd.org (Postfix) with ESMTP id 7F84A13C48C for ; Thu, 28 Jun 2007 03:38:32 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from ls248.t-com.hr (ls248.t-com.hr [195.29.150.237]) by ls405.t-com.hr (Postfix) with ESMTP id C1770144C61 for ; Thu, 28 Jun 2007 05:04:56 +0200 (CEST) Received: from ls248.t-com.hr (localhost.localdomain [127.0.0.1]) by ls248.t-com.hr (Qmlai) with ESMTP id BDB1CD5004A for ; Thu, 28 Jun 2007 05:04:56 +0200 (CEST) Received: from ls248.t-com.hr (localhost.localdomain [127.0.0.1]) by ls248.t-com.hr (Qmlai) with ESMTP id A7F59D50047 for ; Thu, 28 Jun 2007 05:04:56 +0200 (CEST) X-Envelope-Sender-Info: g5URFa92gX9K/Rg9VFA/rABUxmEcZAn2X0vuLcPq36Y6StkSH1j7CT0zJW9WjWDV X-Envelope-Sender: ivoras@fer.hr Received: from [10.0.0.100] (78-1-114-244.adsl.net.t-com.hr [78.1.114.244]) by ls248.t-com.hr (Qmali) with ESMTP id 7EC3E5E001A for ; Thu, 28 Jun 2007 05:04:56 +0200 (CEST) Message-ID: <46832557.8080902@fer.hr> Date: Thu, 28 Jun 2007 05:04:55 +0200 From: Ivan Voras User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org References: <722528.14010.qm@web32707.mail.mud.yahoo.com> In-Reply-To: <722528.14010.qm@web32707.mail.mud.yahoo.com> X-Enigmail-Version: 0.94.3.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig70820A6AD0C46340EADA31E5" Cc: Subject: Re: MS Vista vs FreeBSD's bootloader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 03:38:33 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig70820A6AD0C46340EADA31E5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable pfgshield-freebsd@yahoo.com wrote: > > Hi; > > > > FWIW, if you just got your new computer with Windows Vista installed and were > > hoping to dual boot FreeBSD on it, let me tell you that FreeBSD's bootloader > > will screw things up. > > > > Microsoft basically declared the war on alternative OSs so it seems vista > > doesn't like: > > - bootloaders different than the one used by Vista. > > - Making a non Vista partition active. I can confirm this - messing with the boot sector will make Vista unbootable, but it can be repaired with the installer (of course, you lose FreeBSD at that point). It seems Vista uses registry or some other binary format to store boot info (as opposed to WinXP which uses a text file...) and it protects the boot loader for "DRM" reasons. --------------enig70820A6AD0C46340EADA31E5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGgyVXldnAQVacBcgRAvkdAJ4yQVmHyS4ELmtHQnuhckDST2d8SwCg7lvM QZRtV+vAJNM83Auf7Snsg2Q= =0Vrh -----END PGP SIGNATURE----- --------------enig70820A6AD0C46340EADA31E5-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 28 09:21:55 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5DB9E16A46D for ; Thu, 28 Jun 2007 09:21:55 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp804.mail.ird.yahoo.com (smtp804.mail.ird.yahoo.com [217.146.188.64]) by mx1.freebsd.org (Postfix) with SMTP id C771B13C45A for ; Thu, 28 Jun 2007 09:21:54 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 4442 invoked from network); 28 Jun 2007 08:55:13 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=Qd7lCXvscBmNeoYtUqfgHXyBAZ3SXNxW6yGk1jjsTKFxoG5JVNzHx+75rlYLHrBjNqTfo8pb8xS5++8QILhLkCgifI8hCSNc29xLu5klLdrSePFYwIXSOXLQtnZko4f0omvyKbxOGySJGFcDLWl8i6FtXfpM9zWdOWHRKlPfinY= ; Received: from unknown (HELO w2fzz0vc03.aah-go-on.com) (thomas.sparrevohn@btinternet.com@81.156.175.229 with login) by smtp804.mail.ird.yahoo.com with SMTP; 28 Jun 2007 08:55:13 -0000 X-YMail-OSG: SPCqPDQVM1nmEgkJhPma75FqWeIZ0GWOajzousmnEQaxTsqjuTRWlzvo4EsoDmlv.TROz7Oldw-- From: Thomas Sparrevohn To: freebsd-hackers@freebsd.org Date: Thu, 28 Jun 2007 09:55:11 +0100 User-Agent: KMail/1.9.6 References: <722528.14010.qm@web32707.mail.mud.yahoo.com> <46831822.4090600@u.washington.edu> In-Reply-To: <46831822.4090600@u.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706280955.11311.Thomas.Sparrevohn@btinternet.com> Cc: Garrett Cooper , pfgshield-freebsd@yahoo.com Subject: Re: MS Vista vs FreeBSD's bootloader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 09:21:55 -0000 On Thursday 28 June 2007 03:08:34 Garrett Cooper wrote: > pfgshield-freebsd@yahoo.com wrote: > > Hi; > > > > FWIW, if you just got your new computer with Windows Vista installed and were > > hoping to dual boot FreeBSD on it, let me tell you that FreeBSD's bootloader > > will screw things up. > > > > Microsoft basically declared the war on alternative OSs so it seems vista > > doesn't like: > > - bootloaders different than the one used by Vista. > > - Making a non Vista partition active. > > > > I did what I used to do with XP: I resized the Windows partition with a liveCD > > and QTparted, Installed FreeBSD with booteasy.. and surprise... Windows Vista > > won't run again. > > > > I then rescued the Vista installation with the install CD (good thing they > > included that this time, and not only the preinstalled OS!), and looked on the > > -net for something called EasyBCD, which looks like it will solve the problem > > by reconfiguring the Vista bootloader. > > > > cheers, > > > > Pedro. > > > Their excuse is probably to keep (some of the less intelligent) users > out there from booting using their own media or alternate means. M$ > really must have something important in their bootloader... > -Garrett I have Vista Home edition ruinning any FreeBSD without any problems and without having to do anything special - That is on CURRENT From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 28 10:34:17 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9314C16A485 for ; Thu, 28 Jun 2007 10:34:17 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.freebsd.org (Postfix) with ESMTP id 1E68A13C469 for ; Thu, 28 Jun 2007 10:34:14 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A5639.dip.t-dialin.net [84.154.86.57]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id l5SAXkt6060409; Thu, 28 Jun 2007 12:33:47 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.6/8.13.6) with ESMTP id l5SAXdpa094661; Thu, 28 Jun 2007 12:33:39 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id l5SAXdll095785; Thu, 28 Jun 2007 12:33:39 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200706281033.l5SAXdll095785@fire.js.berklix.net> To: Thomas Sparrevohn In-reply-to: <200706280955.11311.Thomas.Sparrevohn@btinternet.com> References: <722528.14010.qm@web32707.mail.mud.yahoo.com> <46831822.4090600@u.washington.edu> <200706280955.11311.Thomas.Sparrevohn@btinternet.com> Comments: In-reply-to Thomas Sparrevohn message dated "Thu, 28 Jun 2007 09:55:11 +0100." Date: Thu, 28 Jun 2007 12:33:39 +0200 From: "Julian H. Stacey" Cc: freebsd-hackers@freebsd.org, Garrett Cooper , pfgshield-freebsd@yahoo.com Subject: Re: MS Vista vs FreeBSD's bootloader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 10:34:17 -0000 > I have Vista Home edition ruinning any FreeBSD without any problems and > without having to do anything special - That is on CURRENT ruinning: No such word ruining: Wrecking, destroying running: Working acceptably - I guess you probably mean this ? -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com HTML mail unseen. Ihr Rauch=mein allergischer Kopfschmerz. Dump cigs 4 snuff. From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 28 10:40:38 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4ACD216A53B for ; Thu, 28 Jun 2007 10:40:38 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.freebsd.org (Postfix) with ESMTP id C2D1413C48A for ; Thu, 28 Jun 2007 10:40:32 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A5639.dip.t-dialin.net [84.154.86.57]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id l5SAeQUt061037; Thu, 28 Jun 2007 12:40:31 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.6/8.13.6) with ESMTP id l5SAeKlP094698; Thu, 28 Jun 2007 12:40:20 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id l5SAeKhn095833; Thu, 28 Jun 2007 12:40:20 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200706281040.l5SAeKhn095833@fire.js.berklix.net> To: pfgshield-freebsd@yahoo.com In-reply-to: <722528.14010.qm@web32707.mail.mud.yahoo.com> References: <722528.14010.qm@web32707.mail.mud.yahoo.com> Comments: In-reply-to message dated "Wed, 27 Jun 2007 17:00:02 +0200." Date: Thu, 28 Jun 2007 12:40:20 +0200 From: "Julian H. Stacey" Cc: freebsd-hackers@freebsd.org Subject: Re: MS Vista vs FreeBSD's bootloader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 10:40:38 -0000 pfgshield-freebsd@yahoo.com wrote: > Hi; > > FWIW, if you just got your new computer with Windows Vista installed and were > hoping to dual boot FreeBSD on it, let me tell you that FreeBSD's bootloader > will screw things up. > > Microsoft basically declared the war on alternative OSs so it seems vista > doesn't like: ... Actually, NetBSD can criple FreeBSD MBR too ! Detail http://www.berklix.com/~jhs/hardware/laptops/#netbsd (I tried Net in desperation as FreeBSD-6.2 useless w. 16 bit pcmcia & PLIP) (I reported MBR to users@netbsd.org & got just 1 response, not a solution). So many OS' cripple other OS's MBR - Sigh ! -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com HTML mail unseen. Ihr Rauch=mein allergischer Kopfschmerz. Dump cigs 4 snuff. From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 28 06:05:49 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D15D016A400 for ; Thu, 28 Jun 2007 06:05:49 +0000 (UTC) (envelope-from phi@evilphi.com) Received: from mail.twinthornes.com (mail.twinthornes.com [65.75.198.147]) by mx1.freebsd.org (Postfix) with ESMTP id B033113C465 for ; Thu, 28 Jun 2007 06:05:49 +0000 (UTC) (envelope-from phi@evilphi.com) Received: from [10.9.70.101] (pool-72-90-106-233.ptldor.fios.verizon.net [72.90.106.233]) by mail.twinthornes.com (Postfix) with ESMTP id E6071658; Wed, 27 Jun 2007 22:41:05 -0700 (PDT) Message-ID: <468349CD.1020302@evilphi.com> Date: Wed, 27 Jun 2007 22:40:29 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Ivan Voras References: <722528.14010.qm@web32707.mail.mud.yahoo.com> <46832557.8080902@fer.hr> In-Reply-To: <46832557.8080902@fer.hr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 28 Jun 2007 11:32:10 +0000 Cc: freebsd-hackers@FreeBSD.org Subject: Re: MS Vista vs FreeBSD's bootloader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 06:05:49 -0000 Ivan Voras wrote: > pfgshield-freebsd@yahoo.com wrote: >> >> FWIW, if you just got your new computer with Windows Vista >> installed and were hoping to dual boot FreeBSD on it, let me tell >> you that FreeBSD's bootloader will screw things up. >> >> vista doesn't like: >> - bootloaders different than the one used by Vista. >> - Making a non Vista partition active. > > I can confirm this - messing with the boot sector will make Vista > unbootable, but it can be repaired with the installer (of course, you > lose FreeBSD at that point). It seems Vista uses registry or some > other binary format to store boot info (as opposed to WinXP which > uses a text file...) and it protects the boot loader for "DRM" > reasons. This has been SOP at Microsoft for almost a decade. If you want to dual-boot Windows, the solution is to use the established methods for adding additional boot options to the built-in Windows boot-loader. For Vista, this means using the BCDEdit command-line tool to manipulate the Boot Configuration Data in the system registry rather than Notepad to edit boot.ini. BCDEdit and its options are detailed on MSDN: http://msdn2.microsoft.com/en-us/library/aa468636.aspx A slightly more useful discussion of BCDedit on bsdforums.org: http://www.bsdforums.org/forums/showthread.php?t=48405 It specifies Linux, but this is a tutorial for adding a non-Windows boot option to the Vista Boot Manager: http://port25.technet.com/archive/2006/10/13/Using-Vista_2700_s-Boot-Manager-to-Boot-Linux-and-Dual-Booting-with-BitLocker-Protection-with-TPM-Support.aspx -- Darren Pilgrim From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 28 12:29:11 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D476716A4BF for ; Thu, 28 Jun 2007 12:29:11 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp811.mail.ird.yahoo.com (smtp811.mail.ird.yahoo.com [217.146.188.71]) by mx1.freebsd.org (Postfix) with SMTP id 3118813C45B for ; Thu, 28 Jun 2007 12:29:10 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 11602 invoked from network); 28 Jun 2007 12:29:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=IMdYKO7sqeqUyddolMg3MNRHKIRUapPdhKoaFc3ciT7VEpXiZ8t9E3coeRFmAQOHOnthg8DPf3LUBf4mZe4cXIHPpN4ZFrMjNZvNwq8bzZ8clcDQ+I3Y/CqJxnkaR+wEj1wa+yUmWf+b9usncNImh3Rw/3PxbTDUM4u0jcdn7Wo= ; Received: from unknown (HELO w2fzz0vc03.aah-go-on.com) (thomas.sparrevohn@btinternet.com@81.156.175.229 with login) by smtp811.mail.ird.yahoo.com with SMTP; 28 Jun 2007 12:29:09 -0000 X-YMail-OSG: gAzjGdkVM1lvUYCTilhPI6wz.l4GWGQrRp5CFj4C87.mZRZol9jWtr_kFz7_kGEfO_aD72QniA-- From: Thomas Sparrevohn To: "Julian H. Stacey" Date: Thu, 28 Jun 2007 13:29:06 +0100 User-Agent: KMail/1.9.6 References: <722528.14010.qm@web32707.mail.mud.yahoo.com> <200706280955.11311.Thomas.Sparrevohn@btinternet.com> <200706281033.l5SAXdll095785@fire.js.berklix.net> In-Reply-To: <200706281033.l5SAXdll095785@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706281329.07139.Thomas.Sparrevohn@btinternet.com> Cc: freebsd-hackers@freebsd.org, Garrett Cooper , pfgshield-freebsd@yahoo.com Subject: Re: MS Vista vs FreeBSD's bootloader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 12:29:11 -0000 On Thursday 28 June 2007 11:33:39 Julian H. Stacey wrote: > > I have Vista Home edition ruinning any FreeBSD without any problems and > > without having to do anything special - That is on CURRENT > > ruinning: No such word > ruining: Wrecking, destroying > running: Working acceptably - I guess you probably mean this ? > LOL - Yes the last - From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 28 13:44:06 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B5A1916A421 for ; Thu, 28 Jun 2007 13:44:06 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32714.mail.mud.yahoo.com (web32714.mail.mud.yahoo.com [68.142.206.27]) by mx1.freebsd.org (Postfix) with SMTP id 65CAF13C48A for ; Thu, 28 Jun 2007 13:44:06 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 53100 invoked by uid 60001); 28 Jun 2007 13:44:05 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=0BOv9E92XCCwmVsPC83fxuH71CP69LyLeN8S3f6f5188yPtzzX1ZaQPxd3omNmc5u/I9nHP/ak1pWpDzB8Jo4Qfh40LI2Kwp4b6/u9ap+pBS247EUKjEaxUq5zclWPWxf6uIKmXBKrW33s8oXSvR2t+40FyniH/9ibOSKU9fLlY=; X-YMail-OSG: auBcRYwVM1kCwpwXylBumdwNfLkLXJLhT2581hOdQEBzx6VIYejdHFYEIfWaewfnD7SVtEgOaS_u0iM8W5hDdeNqngfR.yeG4vFj9OaZp9STGHn2ISMHhzDthA2bRg-- Received: from [200.118.214.193] by web32714.mail.mud.yahoo.com via HTTP; Thu, 28 Jun 2007 15:44:05 CEST Date: Thu, 28 Jun 2007 15:44:05 +0200 (CEST) From: To: Thomas Sparrevohn In-Reply-To: <200706280955.11311.Thomas.Sparrevohn@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <758783.52560.qm@web32714.mail.mud.yahoo.com> X-Mailman-Approved-At: Thu, 28 Jun 2007 13:53:32 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: MS Vista vs FreeBSD's bootloader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 13:44:06 -0000 --- Thomas Sparrevohn ha scritto: ... > > I have Vista Home edition ruinning any FreeBSD without any problems and > without having to do anything special - That is on CURRENT > > Hmm... Installation order is important, perhaps you already had FreeBSD before installing Vista? In my case Vista Premium came preinstalled, there was also a FAT partition (with diagnostic stuff) and an NTFS for rescue purposes. Of course getting the new computer without Vista was not really an option :(, but MS went too far this time, they removed postcript type1 font support and they crippled OpenGL enough that major CAD packages don't work easily or have something like 85% performance penalty. Pedro. ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 28 16:07:52 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8FACA16A421 for ; Thu, 28 Jun 2007 16:07:52 +0000 (UTC) (envelope-from pb@ludd.ltu.se) Received: from mother.ludd.ltu.se (mother.ludd.ltu.se [130.240.16.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2222013C487 for ; Thu, 28 Jun 2007 16:07:51 +0000 (UTC) (envelope-from pb@ludd.ltu.se) Received: from brother.ludd.ltu.se (root@brother.ludd.ltu.se [130.240.16.78]) by mother.ludd.ltu.se (8.13.6+Sun/8.12.10) with ESMTP id l5SFpm0a023007 for ; Thu, 28 Jun 2007 17:51:48 +0200 (MEST) Received: from brother.ludd.ltu.se (pb@localhost [127.0.0.1]) by brother.ludd.ltu.se (8.13.6+Sun/8.12.2) with ESMTP id l5SFpm07005600 for ; Thu, 28 Jun 2007 17:51:48 +0200 (MEST) Received: (from pb@localhost) by brother.ludd.ltu.se (8.13.6+Sun/8.13.6/Submit) id l5SFpleb005598 for freebsd-hackers@freebsd.org; Thu, 28 Jun 2007 17:51:47 +0200 (MEST) From: Peter B Message-Id: <200706281551.l5SFpleb005598@brother.ludd.ltu.se> To: freebsd-hackers@freebsd.org Date: Thu, 28 Jun 2007 17:51:47 +0200 (MEST) X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 28 Jun 2007 16:24:36 +0000 Subject: SII3512 rev0 ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 16:07:52 -0000 In /usr/src/sys/dev/ata/ata-chipset.c the table (ata_sii_ident) for Silicon Image chips: pcirev { ATA_SII3512, 0x02, SIIMEMIO, 0, ATA_SA150, "SiI 3512" }, { ATA_SII3512, 0x00, SIIMEMIO, SIIBUG, ATA_SA150, "SiI 3512" }, Indicate there is a revision 0 of the chip SII3512. I wonder if there exist such chip, or if this is just an assumption from the problems with SII3112 rev0 ..? http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/ata-chipset.c#rev1.62 Any input on the reliability of SII3512 is also welcomed. /P From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 28 19:09:04 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1B34C16A468 for ; Thu, 28 Jun 2007 19:09:04 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp810.mail.ird.yahoo.com (smtp810.mail.ird.yahoo.com [217.146.188.70]) by mx1.freebsd.org (Postfix) with SMTP id 85AD913C44B for ; Thu, 28 Jun 2007 19:09:03 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 57323 invoked from network); 28 Jun 2007 19:09:02 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=g41i0WvLYhFnSwR0HMSp2ChNMOWDP4LPNYogk+lZdd16Z/FiyehGWIoO9DMqe4B822e/mZ8v0v31z3pe1GfwBqiZEM2jUBJUkIkl3q/oCydLtd18L6BXwB7EwMLfgjDtMnlCgomx61bamXwfM2e2KWfkRWeMD37DlC4DoL8SBCw= ; Received: from unknown (HELO w2fzz0vc03.aah-go-on.com) (thomas.sparrevohn@btinternet.com@81.156.175.229 with login) by smtp810.mail.ird.yahoo.com with SMTP; 28 Jun 2007 19:09:01 -0000 X-YMail-OSG: vxBbtw0VM1nZLr8WkGKa3wLAM4v1gPt1TMOkr88y5VDCySl_Yyb0ZAQrbYRrWuUEYGSccyHl7ZZQHQstWtuL6xqpu2vX14jmG5yYVPm_pvSYEAHSYvKVLN2ifWw- From: Thomas Sparrevohn To: pfgshield-freebsd@yahoo.com Date: Thu, 28 Jun 2007 20:09:00 +0100 User-Agent: KMail/1.9.6 References: <758783.52560.qm@web32714.mail.mud.yahoo.com> In-Reply-To: <758783.52560.qm@web32714.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706282009.00938.Thomas.Sparrevohn@btinternet.com> Cc: freebsd-hackers@freebsd.org Subject: Re: MS Vista vs FreeBSD's bootloader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 19:09:04 -0000 On Thursday 28 June 2007 14:44:05 pfgshield-freebsd@yahoo.com wrote: > > --- Thomas Sparrevohn ha scritto: > ... > > > > > I have Vista Home edition ruinning any FreeBSD without any problems and > > without having to do anything special - That is on CURRENT > > > > > Hmm... > > Installation order is important, perhaps you already had FreeBSD before > installing Vista? In my case Vista Premium came preinstalled, there was also a > FAT partition (with diagnostic stuff) and an NTFS for rescue purposes. > No - The originally came with XP - I nuked that and installed FreeBSD - However I did nuke the XP totally before upgrading to Vista - It does overwrite the FreeBSD MBR - I just rebooted using a CD and added the mbr again > Of course getting the new computer without Vista was not really an option :(, > but MS went too far this time, they removed postcript type1 font support and > they crippled OpenGL enough that major CAD packages don't work easily or have > something like 85% performance penalty. > > Pedro. > > > ___________________________________ > L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html > From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 29 06:46:14 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C04B16A469 for ; Fri, 29 Jun 2007 06:46:14 +0000 (UTC) (envelope-from tim1timau@yahoo.com) Received: from web50302.mail.re2.yahoo.com (web50302.mail.re2.yahoo.com [206.190.38.56]) by mx1.freebsd.org (Postfix) with SMTP id B8C3213C484 for ; Fri, 29 Jun 2007 06:46:13 +0000 (UTC) (envelope-from tim1timau@yahoo.com) Received: (qmail 41053 invoked by uid 60001); 29 Jun 2007 06:19:32 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=a9ttW3C8AsdbbKS9pqbZi+Y9v+EuwNBEGmZ8B5vDqNhfxGKIzRZzGymavVky6DtEckejAiJZdbZRekEA4yxuqteUP98oWfIozrzu/UIJg+586b1XI4YDMmRd8+NBFCphMkKzjqPkX0I4MBknrEnI7YMAEWQyffrbJLsfLoY/5K8=; X-YMail-OSG: hbvjHM4VM1mhDH99D02UjQOANal8KXV6dsp.fjsEbGZE0x_E2arqHG5AQHgoLbfcyA-- Received: from [210.50.6.166] by web50302.mail.re2.yahoo.com via HTTP; Thu, 28 Jun 2007 23:19:32 PDT Date: Thu, 28 Jun 2007 23:19:32 -0700 (PDT) From: Tim Clewlow To: freebsd-hackers@freebsd.org In-Reply-To: <200706282009.00938.Thomas.Sparrevohn@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <235027.40865.qm@web50302.mail.re2.yahoo.com> Subject: Re: MS Vista vs FreeBSD's bootloader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2007 06:46:14 -0000 --- Thomas Sparrevohn wrote: > On Thursday 28 June 2007 14:44:05 pfgshield-freebsd@yahoo.com wrote: > > > > --- Thomas Sparrevohn ha scritto: > > ... > > > > > > > > I have Vista Home edition ruinning any FreeBSD without any problems and > > > without having to do anything special - That is on CURRENT > > > > > > > > Hmm... > > > > Installation order is important, perhaps you already had FreeBSD before > > installing Vista? In my case Vista Premium came preinstalled, there was > also a > > FAT partition (with diagnostic stuff) and an NTFS for rescue purposes. > > > > No - The originally came with XP - I nuked that and installed FreeBSD - > However > I did nuke the XP totally before upgrading to Vista - It does overwrite the > FreeBSD > MBR - I just rebooted using a CD and added the mbr again > > > Of course getting the new computer without Vista was not really an option > :(, > > but MS went too far this time, they removed postcript type1 font support > and > > they crippled OpenGL enough that major CAD packages don't work easily or > have > > something like 85% performance penalty. > > > > Pedro. > > ----------------------- Hi, this may not be the correct place to ask - but it is related. Has anyone been able to get Vista running on qemu? Cheers, Tim. ____________________________________________________________________________________ Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545469 From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 29 07:32:17 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AA1DF16A400 for ; Fri, 29 Jun 2007 07:32:17 +0000 (UTC) (envelope-from pb@ludd.ltu.se) Received: from mother.ludd.ltu.se (mother.ludd.ltu.se [130.240.16.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3BDEF13C448 for ; Fri, 29 Jun 2007 07:32:16 +0000 (UTC) (envelope-from pb@ludd.ltu.se) Received: from brother.ludd.ltu.se (root@brother.ludd.ltu.se [130.240.16.78]) by mother.ludd.ltu.se (8.13.6+Sun/8.12.10) with ESMTP id l5T7W9KM013155; Fri, 29 Jun 2007 09:32:09 +0200 (MEST) Received: from brother.ludd.ltu.se (pb@localhost [127.0.0.1]) by brother.ludd.ltu.se (8.13.6+Sun/8.12.2) with ESMTP id l5T7W9cv006816; Fri, 29 Jun 2007 09:32:09 +0200 (MEST) Received: (from pb@localhost) by brother.ludd.ltu.se (8.13.6+Sun/8.13.6/Submit) id l5T7W4oG006813; Fri, 29 Jun 2007 09:32:04 +0200 (MEST) From: Peter B Message-Id: <200706290732.l5T7W4oG006813@brother.ludd.ltu.se> To: didier@aida.org (didier derny) Date: Fri, 29 Jun 2007 09:32:04 +0200 (MEST) In-Reply-To: <4684A495.8030701@aida.org> from "didier derny" at Jun 29, 2007 08:20:05 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Fri, 29 Jun 2007 11:37:06 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: SII3512 rev0 ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2007 07:32:17 -0000 >Peter B a écrit : >> In /usr/src/sys/dev/ata/ata-chipset.c the table (ata_sii_ident) for >> Silicon Image chips: >> >> pcirev >> { ATA_SII3512, 0x02, SIIMEMIO, 0, ATA_SA150, "SiI 3512" }, >> { ATA_SII3512, 0x00, SIIMEMIO, SIIBUG, ATA_SA150, "SiI 3512" }, >> >> Indicate there is a revision 0 of the chip SII3512. I wonder if there exist >> such chip, or if this is just an assumption from the problems with >> SII3112 rev0 ..? >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/ata-chipset.c#rev1.62 >> >> Any input on the reliability of SII3512 is also welcomed. didier derny wrote: > >I recently added a sata board with a SiI 3512 to my computer to bypass >a problem with the VT8732a of the What was the problem with VIA VT8732a..? >mother board, but if FreeBSD 6.2 booted from this controller it was >totally unstable, crashing as soon as the >disk activity became high (occuring in less than 10mn after boot) Can you check which pci revision it has? (scanpci -v or pciconf -l) Look for 'REVISION' or 'rev=' I have the suspicion that despite possible fixes after the SII3112A v1.1 (rev1) chip. Silicon Image still lacks in engineering reliable equipment. As they infact have failed before with the famous CMD640 chip bug. However it's hard to evade the sii chips as Sweex, Lycom, ST Labs, InnoDV, Belkin, Sunix, Adaptec/1210SA all use their chips. >I replaced this board by a Sata Controller with a SiI 3114 and now >FreeBSD is extremely stable >no crashes at all in 2 days What was the tradename for your SII 3114 equiped card .. ? Regards /Peter From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 29 12:54:22 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 13F2716A473 for ; Fri, 29 Jun 2007 12:54:22 +0000 (UTC) (envelope-from pb@ludd.ltu.se) Received: from mother.ludd.ltu.se (mother.ludd.ltu.se [130.240.16.3]) by mx1.freebsd.org (Postfix) with ESMTP id A581913C4AE for ; Fri, 29 Jun 2007 12:54:21 +0000 (UTC) (envelope-from pb@ludd.ltu.se) Received: from brother.ludd.ltu.se (root@brother.ludd.ltu.se [130.240.16.78]) by mother.ludd.ltu.se (8.13.6+Sun/8.12.10) with ESMTP id l5TCsI5m004211; Fri, 29 Jun 2007 14:54:18 +0200 (MEST) Received: from brother.ludd.ltu.se (pb@localhost [127.0.0.1]) by brother.ludd.ltu.se (8.13.6+Sun/8.12.2) with ESMTP id l5TCsH22007129; Fri, 29 Jun 2007 14:54:17 +0200 (MEST) Received: (from pb@localhost) by brother.ludd.ltu.se (8.13.6+Sun/8.13.6/Submit) id l5TCsH3e007127; Fri, 29 Jun 2007 14:54:17 +0200 (MEST) From: Peter B Message-Id: <200706291254.l5TCsH3e007127@brother.ludd.ltu.se> To: didier@aida.org (Didier Derny) Date: Fri, 29 Jun 2007 14:54:17 +0200 (MEST) In-Reply-To: <200706291105.02431.didier@aida.org> from "Didier Derny" at Jun 29, 2007 11:05:02 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 29 Jun 2007 13:15:29 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: SII3512 rev0 ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2007 12:54:22 -0000 Conclusion as for SATA Freebsd6: Good: SII 3114 r2 Bad: SII 3512 r1, VIA 8237A r128 Question is then about 'SII 3512 r2' .. For ms-xp, linux debian4: SII3512 r1 working. The SII 3112A datasheet specifies: "revision 01H is defined for SiI3112A rev 1.1 and revision 02H is defined for SiI3112A rev 1.21." Guess I have to do the reliable thing and use 3ware, Promise, Highpoint etc.. Any recommendation on this? (connectland 4P sata sii3114 is not easily available from here it seems) >This is a connectland 4 ports serial ata, equiped with a Sil 3114 >with this card, FreeBSD works just fine and is really stable >atapci0@pci0:11:0: class=0x010400 card=0x61141095 chip=0x31141095 rev=0x02 >hdr=0x00 > vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' > device = 'Sil 3114 SATALink/SATARaid Controller' > class = mass storage > subclass = RAID >atapci0: port >0xc400-0xc407,0xc080-0xc083,0xc000-0xc007,0xbc00-0xbc03,0xb880-0xb88f mem >0xff6ff000-0xff6ff3ff irq 19 at device 11.0 on pci0 >ata2: on atapci0 >ata3: on atapci0 >ata4: on atapci0 >ata5: on atapci0 >ad8: 117246MB at ata4-master SATA150 Guess it's one of these? http://www.connectland.net/fiche-629-pci_card_combo_sata_150_et_ide_p_ata.html http://www.connectland.net/fiche-130-serial_a150.html >I'm not sure but I think this board was also connectland >this card with a 3512 works just fine with windows xp and linux debian 4 >but makes FreeBSD really unstable (crashing every about 10 minutes) >atapci1@pci0:12:0: class=0x010400 card=0x65121095 chip=0x35121095 rev=0x01>hdr=0x00 > vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' > device = 'Sil 3512 SATALink/SATARaid Controller' > class = mass storage > subclass = RAID >atapci1: port >0xd400-0xd407,0xcc00-0xcc03,0xc880-0xc887,0xc800-0xc803,0xc480-0xc48f mem >0xff6ff400-0xff6ff5ff irq 16 at device 12.0 on pci0 >ata6: on atapci1 >ata7: on atapci1 >ad12: 152627MB at ata6-master SATA150 Seems the freebsd driver is to blame for this card then. Or m$/lin just hides the errors ;) (iow SII3512 + freebsd6 = bad) >Sata controller on my 4coredual-vsta motherboard, FreeBSD at best just >"see" the hard disks and crashes at the first attempt to access it >atapci2@pci0:15:0: class=0x01018f card=0x05911849 chip=0x05911106 rev=0x80 >hdr=0x00 > vendor = 'VIA Technologies Inc' > class = mass storage > subclass = ATA >atapci2: port >0xe000-0xe007,0xdc00-0xdc03,0xd880-0xd887,0xd800-0xd803,0xd480-0xd48f,0xd000-0xd0ff >irq 21 at device 15.0 on pci0 >ata8: on atapci2 >ata9: on atapci2 >ad16: 117246MB at ata8-master SATA150 > >Ide controller on the same motherboard, FreeBSD seems to be able to use it >but I'm not really confident about it's reliability >atapci3@pci0:15:1: class=0x01018a card=0x05711849 chip=0x05711106 rev=0x07 >hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT82xxxx EIDE Controller (All VIA Chipsets)' > class = mass storage > subclass = ATA >atapci3: port >0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0 >ata0: on atapci3 >ata1: on atapci3 >acd0: DVDR at ata1-master UDMA33 PATA? Anyway VIA had some serious blunders before, just like CMD Tech - Siliconimage. >This is confusing but I had many problems with FreeBSD, Windows, Linux debian >(debian refusing to boot if it was not alone on a controller, and bsd refusing>to work wih some controllers) From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 30 15:53:06 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C8BE816A41F for ; Sat, 30 Jun 2007 15:53:06 +0000 (UTC) (envelope-from erenerdemli@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.freebsd.org (Postfix) with ESMTP id 88F1413C455 for ; Sat, 30 Jun 2007 15:53:06 +0000 (UTC) (envelope-from erenerdemli@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so1946639pyb for ; Sat, 30 Jun 2007 08:53:06 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=CNjLfa4ibtKw3OE9Nd1hhsXapCpY/oglB2FUVrRmaQftwMnzEdT1v3b7vVuXtnIzGc1GzFftssMwPAl7u24T9LZ95objv6I6gxsiV1cswoUskHSnBZjs8Moytm76/D/FYOwGCqmydbpUHGHyUXxRofWskwPjGazsR6cunV+wAtc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=as+LwJU0ghKgcegdbVkxKdEkCQULXWTUnsthMqE6rYwNr2KXNjNItUH/iJQX3IZkyCwjbwAzjsEi39DctCVKWg9D5HGmNE8V3ldXlMlj6yDr8H1+VZIBJFuWIZbult3Sg9OJSvsuB+TYm78laMq8LefKv/IWrceGOUhrSAXdnTQ= Received: by 10.65.212.3 with SMTP id o3mr6848105qbq.1183217057615; Sat, 30 Jun 2007 08:24:17 -0700 (PDT) Received: by 10.64.193.7 with HTTP; Sat, 30 Jun 2007 08:24:17 -0700 (PDT) Message-ID: Date: Sat, 30 Jun 2007 15:24:17 +0000 From: "Eren Erdemli" To: freebsd-hackers@freebsd.org In-Reply-To: <20070629171137.GG1221@funkthat.com> MIME-Version: 1.0 References: <20070629171137.GG1221@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: getCWD in kernel space X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jun 2007 15:53:06 -0000 Hello hackers, Sorry to disturb you's but I have a question and would like to know if you can assist me. I am new to freebsd programing and I am trying to get the current working directory of the curthread. I have hook on to the sys calls and redirected the mkdir my_mkdir(struct thread *p, (void*) uap) { mkdir_args = ..................... ........ getCWD()??????????? } the given path in the args is relative to the current path if not supplied fully. So who would I get the path of file. Your help is truly appreciated as I I have been trying it for few days now. no result apart from kernel panics. Thanks in advance Eren From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 30 17:13:00 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 59BD616A469 for ; Sat, 30 Jun 2007 17:13:00 +0000 (UTC) (envelope-from patrick_dkt@yahoo.com.hk) Received: from web54305.mail.re2.yahoo.com (web54305.mail.re2.yahoo.com [206.190.49.115]) by mx1.freebsd.org (Postfix) with SMTP id EE49D13C44B for ; Sat, 30 Jun 2007 17:12:59 +0000 (UTC) (envelope-from patrick_dkt@yahoo.com.hk) Received: (qmail 23800 invoked by uid 60001); 30 Jun 2007 17:12:59 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.hk; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ogTufG70NCmHkdKw6ey8gkrzwvRex3NFuOKO90S52OPNRu+90Yirvpr18uKbqkR030qkmB4w30FG2aazVarN4Fc1Ud08m/G7Me228aiXdHDzuc4+xx7VULuwUrfm7Hkz8AuIdFAtfsaH9nqVTQY5tiLBx0OxJcoSfCZE1eu0BrM=; X-YMail-OSG: S3p.h2wVM1kAH5M7xs1_zDX2Kg0BhTJ_C103FRKLhkX6oKhKGVUIMNpA8zsDWn7R_hQ6vgh20i1W1e4BCBhEQ10Oaf8qY6uQlSmtp0KHq2WblpwgUCeg7fd67cE63g-- Received: from [61.15.61.52] by web54305.mail.re2.yahoo.com via HTTP; Sat, 30 Jun 2007 10:12:59 PDT Date: Sat, 30 Jun 2007 10:12:59 -0700 (PDT) From: Patrick Dung To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <105872.23286.qm@web54305.mail.re2.yahoo.com> X-Mailman-Approved-At: Sat, 30 Jun 2007 17:31:10 +0000 Cc: freebsd-hackers@freebsd.org Subject: password againg and other policy enforcement X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jun 2007 17:13:00 -0000 I have some question about password policy in FreeBSD: 1. Administrator can enforce password expire in /etc/login.conf Is there any tool that can check when the password will expire for the users? 2. Any good way to enforce minimum password length and other restriction(like password need at least 2 numbers, 2 special char)? 3. Any ways to prevent user reuse old password? Regards Patrick ____________________________________________________________________________________ Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. http://autos.yahoo.com/green_center/ From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 30 18:13:17 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5584216A46D for ; Sat, 30 Jun 2007 18:13:17 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (vlk.vlakno.cz [62.168.28.247]) by mx1.freebsd.org (Postfix) with ESMTP id 0E6C113C4AE for ; Sat, 30 Jun 2007 18:13:16 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 716F58BF127; Sat, 30 Jun 2007 20:13:15 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (vlk.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tgy9hila8euK; Sat, 30 Jun 2007 20:13:14 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 28E708BF0C3; Sat, 30 Jun 2007 20:13:14 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.13.8/8.13.8/Submit) id l5UIDDEe063285; Sat, 30 Jun 2007 20:13:13 +0200 (CEST) (envelope-from rdivacky) Date: Sat, 30 Jun 2007 20:13:13 +0200 From: Roman Divacky To: Eren Erdemli Message-ID: <20070630181313.GA63208@freebsd.org> References: <20070629171137.GG1221@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org Subject: Re: getCWD in kernel space X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jun 2007 18:13:17 -0000 On Sat, Jun 30, 2007 at 03:24:17PM +0000, Eren Erdemli wrote: > Hello hackers, > > Sorry to disturb you's but I have a question and would like to know if you > can assist me. > > I am new to freebsd programing and I am trying to get the current working > directory of the curthread. > > I have hook on to the sys calls and redirected the mkdir > > my_mkdir(struct thread *p, (void*) uap) > { > mkdir_args = ..................... > ........ > getCWD()??????????? > } curthread->td_proc->p_fd->fd_cdir is a vnode of cwd From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 30 19:59:57 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A05EB16A46D for ; Sat, 30 Jun 2007 19:59:57 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 5625713C46E for ; Sat, 30 Jun 2007 19:59:57 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=H/kB4swZhgbEGOejwZ0nPHkxnrX63W94j+FWK34bkweNTS3tLUuQH7XHhuASE6O9mz3oHAmjE+0R5yUglquGwagplc03+TB65iA2DAk+sk3TM8Bi0uHzzFo57xQSYlkbt7H46mktNk+XMeWuQ/B73DTvxRM+tGvBufJ8MQt1/Wk=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1I4j6n-000Az2-RA; Sat, 30 Jun 2007 23:59:53 +0400 Date: Sat, 30 Jun 2007 23:59:49 +0400 From: Eygene Ryabinkin To: Patrick Dung Message-ID: <20070630195949.GA1240@void.codelabs.ru> References: <105872.23286.qm@web54305.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <105872.23286.qm@web54305.mail.re2.yahoo.com> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_00 Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: password againg and other policy enforcement X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jun 2007 19:59:57 -0000 Patrick, good day. Sat, Jun 30, 2007 at 10:12:59AM -0700, Patrick Dung wrote: > 1. Administrator can enforce password expire in /etc/login.conf In the /etc/master.passwd. login.conf has the fields, but does not implement the functionality, if the manpage is right: ===== RESERVED CAPABILITIES The following capabilities are reserved for the purposes indicated and may be supported by third-party software. They are not implemented in the base system. Name Type Notes Description <...> expireperiod time Time for expiry allocation. graceexpire time Grace days for expired account. ===== But the following fields are working: > Is there any tool that can check when the password will expire for the > users? Yep, ===== $ LANG=C date -r `pw showuser | cut -d: -f 6` Tue Jan 20 00:00:00 MSK 2009 $ LANG=C date -r `pw showuser | cut -d: -f 7` Sat Feb 28 00:00:00 MSK 2009 ==== > 2. Any good way to enforce minimum password length and other > restriction(like password need at least 2 numbers, 2 special char)? > > 3. Any ways to prevent user reuse old password? man pam_passwdqc, search for the 'match' and 'similar'. But for the '3.': user still can change his password to something and immediately bounce back to the old password. The longer password history changes the chain length, but does not solve the problem completely. The complete password history can help, but it is out of the passwdqc's scope: it just checks against the current password. -- Eygene From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 30 20:17:51 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9076016A469; Sat, 30 Jun 2007 20:17:51 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 4337513C447; Sat, 30 Jun 2007 20:17:51 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=F9fVrei+UQ9jb6gQU0vNa7ChTCrRDXBNQEfft1PSbOdMoAHerNCO2E6J3Flx6ZMMuzUNpzwQBLXBUCAOKmEPRFdth8n+lsNEnSVIxBhZ8/kTcOZ8i9gfRof/Q/9TWUDwDvaOaU/PAbG11zKNALdO8Ga1joAJ002IWiuJH1/SvJU=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1I4jOA-000B3t-CW; Sun, 01 Jul 2007 00:17:50 +0400 Date: Sun, 1 Jul 2007 00:17:46 +0400 From: Eygene Ryabinkin To: Patrick Dung Message-ID: <20070630201745.GB1240@void.codelabs.ru> References: <105872.23286.qm@web54305.mail.re2.yahoo.com> <20070630195949.GA1240@void.codelabs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20070630195949.GA1240@void.codelabs.ru> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_00 Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: password againg and other policy enforcement X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jun 2007 20:17:51 -0000 Me again. Forgot to finish the sentence, sorry. Sat, Jun 30, 2007 at 11:59:49PM +0400, Eygene Ryabinkin wrote: > > 1. Administrator can enforce password expire in /etc/login.conf > > In the /etc/master.passwd. login.conf has the fields, but does > not implement the functionality, if the manpage is right: > ===== > RESERVED CAPABILITIES > The following capabilities are reserved for the purposes indicated and > may be supported by third-party software. They are not implemented in > the base system. > > Name Type Notes Description > <...> > expireperiod time Time for expiry allocation. > graceexpire time Grace days for expired account. > ===== > But the following fields are working: ===== warnexpire time Advance notice for pending account expiry. warnpassword time Advance notice for pending password expiry. ===== So this can provide some warnings to the user when it logs in. -- Eygene