From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 01:41:15 2006 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA68416A403; Sun, 2 Jul 2006 01:41:15 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CD25451FC; Sun, 2 Jul 2006 01:41:14 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.13.6/8.13.6/NinthNine) with ESMTP id k621fBHo076728; Sun, 2 Jul 2006 10:41:13 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Sun, 2 Jul 2006 10:41:11 +0900 From: Norikatsu Shigemura To: Alexander Leidinger Message-Id: <20060702104111.def19d47.nork@FreeBSD.org> In-Reply-To: <20060625134812.a0rm7fbd2wwg0g84@netchild.homeip.net> References: <44986777.6070601@FreeBSD.org> <20060621061437.GA53019@fit.vutbr.cz> <2265.211.18.249.19.1150871779.squirrel@mail.ninth-nine.com> <20060621121114.h6udocel5wsgg8sg@netchild.homeip.net> <2692.219.127.74.121.1150885501.squirrel@mail.ninth-nine.com> <20060621155053.d6lseiz8z4ow8wo8@netchild.homeip.net> <20060623013106.d4397e26.nork@FreeBSD.org> <20060622230416.3907a848@kan.dnsalias.net> <20060625191405.d0e78240.nork@FreeBSD.org> <20060625134812.a0rm7fbd2wwg0g84@netchild.homeip.net> X-Mailer: Sylpheed version 2.2.6 (GTK+ 2.8.19; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (sakura.ninth-nine.com [219.127.74.121]); Sun, 02 Jul 2006 10:41:13 +0900 (JST) Cc: deischen@FreeBSD.org, kabaev@gmail.com, current@FreeBSD.org Subject: Re: Linux-flashplugin7 & rtld - RFC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 01:41:15 -0000 On Sun, 25 Jun 2006 13:48:12 +0200 Alexander Leidinger wrote: > Did you try to use LD_PRELOAD=libglibcwrapper in the firefox start > script (or in the shell for testing)? The libglibcwrapper should > contain the version information and glibc symbols. Does/could/should > this work? I hope works good. But I confirmed that firefox is freeze. I re-installed firefox, but firefox's libraries don't have any symbols versioning. $ readelf -s /usr/X11R6/lib/firefox/firefox-bin | grep @ 7: 00000000 209 FUNC GLOBAL DEFAULT UND puts@FBSD_1.0 (2) 9: 00000000 49 FUNC GLOBAL DEFAULT UND fprintf@FBSD_1.0 (2) : $ readelf -s /usr/X11R6/lib/firefox/lib*.so | less (please check some functions like /\@FBSD_[enter]) I don't know why there is no symbol versioning in firefox's libraries, too. This may be a ENVIRONMENT ISSUE. After I enabled SYMVER_ENABLED=yes, I recompiled firefox, nspr and gtk/glib. It may be not enougth... From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 02:20:37 2006 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EBCC16A506; Sun, 2 Jul 2006 02:20:37 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D4274425B; Sun, 2 Jul 2006 02:00:39 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.13.6/8.13.6/NinthNine) with ESMTP id k6220bVQ077218; Sun, 2 Jul 2006 11:00:37 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Sun, 2 Jul 2006 11:00:37 +0900 From: Norikatsu Shigemura To: current@FreeBSD.org Message-Id: <20060702110037.f78ea013.nork@FreeBSD.org> In-Reply-To: <20060702104111.def19d47.nork@FreeBSD.org> References: <44986777.6070601@FreeBSD.org> <20060621061437.GA53019@fit.vutbr.cz> <2265.211.18.249.19.1150871779.squirrel@mail.ninth-nine.com> <20060621121114.h6udocel5wsgg8sg@netchild.homeip.net> <2692.219.127.74.121.1150885501.squirrel@mail.ninth-nine.com> <20060621155053.d6lseiz8z4ow8wo8@netchild.homeip.net> <20060623013106.d4397e26.nork@FreeBSD.org> <20060622230416.3907a848@kan.dnsalias.net> <20060625191405.d0e78240.nork@FreeBSD.org> <20060625134812.a0rm7fbd2wwg0g84@netchild.homeip.net> <20060702104111.def19d47.nork@FreeBSD.org> X-Mailer: Sylpheed version 2.2.6 (GTK+ 2.8.19; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (sakura.ninth-nine.com [219.127.74.121]); Sun, 02 Jul 2006 11:00:38 +0900 (JST) Cc: deischen@FreeBSD.org, Alexander@Leidinger.net, nork@FreeBSD.org, kabaev@gmail.com Subject: Re: Linux-flashplugin7 & rtld - RFC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 02:20:38 -0000 Ah, I think that version_gen.awk has a issue to migrate SYMVER_ENABLED=yes environment, like symbol non-versioning binaries -(dynamic link)->symbol versioning libraries. Almost works in current, but unstable. Because symbol non-versioning will link symbol any-versioning of the first to find. It should be order versioning information. --- share/mk/version_gen.awk.orig Fri Mar 17 00:12:26 2006 +++ share/mk/version_gen.awk Sat Jul 1 13:56:32 2006 @@ -53,6 +53,7 @@ symver = $1; versions[symver] = 1; successors[symver] = ""; + order[version_count] = symver; version_count++; } else if (/^[ \t]*} *[a-zA-Z0-9._]+ *;/) { @@ -142,17 +143,18 @@ } END { - for (v in versions) { + for (i = 0; i < version_count; i++) { + v = order[i]; printf("\n"); printf("%s {\n", v); # The version count is always one more that actual, # so the loop ranges from 1 to n-1. # - for (i = 1; i < versions[v]; i++) { - if (i == 1) + for (j = 1; j < versions[v]; j++) { + if (j == 1) printf("global:\n"); - printf("\t%s\n", symbols[v, i]); + printf("\t%s\n", symbols[v, j]); } if (successors[v] == "") { # This version succeeds no other version. From owner-freebsd-current@FreeBSD.ORG Sat Jul 1 19:08:37 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5396316A412 for ; Sat, 1 Jul 2006 19:08:37 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B34043D7E for ; Sat, 1 Jul 2006 19:08:31 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan [127.0.0.1]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k61J8SJx015476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 1 Jul 2006 15:08:28 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by aldan.algebra.com (8.13.6/8.13.6/Submit) id k61J8RIk015475; Sat, 1 Jul 2006 15:08:27 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) From: Mikhail Teterin To: Peter Jeremy Date: Sat, 1 Jul 2006 15:08:27 -0400 User-Agent: KMail/1.9.1 References: <200607010009.09231@aldan> <20060701115508.GC8447@turion.vk2pj.dyndns.org> In-Reply-To: <20060701115508.GC8447@turion.vk2pj.dyndns.org> X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" X-Mailman-Approved-At: Sun, 02 Jul 2006 03:44:03 +0000 Cc: current@freebsd.org Subject: Re: weird limitation on the system's binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jul 2006 19:08:37 -0000 On Saturday 01 July 2006 07:55, Peter Jeremy wrote: = IMHO, the FreeBSD base system should provide tools for doing native = development - anything beyond that belongs in ports. šGiven that = binutils supports quite an extensive range of targets (of the order of = 100), building them all is impractical and a waste of resources for = virtually everyone who uses FreeBSD. I would agree with this myself, except that anything in the ports would have to _duplicate_ or replace the system one. All of it -- not even just bfd -- because it is all linked statically. The overhead of even a 100 extra "bfd vectors" for all is much smaller, than the the full duplication overhead for those, who want to disassemble an "obscure" object format -- or even one from another FreeBSD platform. We support multiple human languages, each one needed by relatively few people. > My reading of contrib/binutils suggests that files for targets not > related to FreeBSD are in the exclude/delete list and aren't imported > into the FreeBSD repository. They are all here, although there are a lot fewer than 100 of them: echo /usr/src/contrib/binutils/bfd/*-* | wc -w 74 > libbdf.a is built by /usr/src/gnu/usr.bin/binutils/libbfd/Makefile. > That should be a fairly simple change to arrange for it to build and > install the .so as well. Installing both libbfd-s certainly would be a good start... As things stand, every port needing it -- including various different compilers -- builds it own version. This is, largely, explained by the GNU's stupidity of bundling a different version with each tool (gdb, compiler), but the bundled bfds are not THAT incompatible, and the system-installed version can include the compatible superset... -mi From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 00:40:33 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFEAC16A5A8 for ; Sun, 2 Jul 2006 00:40:32 +0000 (UTC) (envelope-from nobel@metafour.com) Received: from vc.metafour.com (vc.metafour.com [217.205.224.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 551CF44825 for ; Sat, 1 Jul 2006 19:41:34 +0000 (GMT) (envelope-from nobel@metafour.com) Received: from NOBEL ([172.20.1.43]) by vc.metafour.com (8.13.1/8.13.1) with SMTP id k61JfCOG004955 for ; Sat, 1 Jul 2006 20:41:12 +0100 Message-ID: <000601c69d46$4d112a80$2b0114ac@NOBEL> From: "Bhuiyan Mohammad Iklash" To: Date: Sat, 1 Jul 2006 20:41:08 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Scanned-By: MIMEDefang 2.52 on 10.2.2.11 X-Mailman-Approved-At: Sun, 02 Jul 2006 03:44:31 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Bringing up bge0 cause panic error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 00:40:33 -0000 Hi I have install FreBSD 7 (June snapshot) in my Dell LATITUDE D820 laptop. = I am facing e serious problem. whenever i want to bring up the bge0 = interface using following command nuke#ifconfig bge0 up panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia cpuid =3D 0 KDB: enter: panic [thread pid 834 tid 100078 ] Stopped at kdb_enter+0X2b: nop db> Then i can't do anything. I had install 6.1, that works fine. Then from = 6.1 i sync the current sourec and recompile system, but there was an = error during compillation. Then i have downloaded and installed the = snapshot and facing this problem. Please let me know how can i get rid of from this problem. Thanks in = advanse.. nuke#uname -a FreeBSD nuke.bloodforlife.net 7.0-CURRENT-200606 FreeBSD = 7.0-CURRENT-200606 #0: Sun Jun 4 16:51:08 UTC 2006 = root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 here is my dmesg -------------------------------------------------------------------------= --- Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 7.0-CURRENT-200606 #0: Sun Jun 4 16:51:08 UTC 2006 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Genuine Intel(R) CPU T2600 @ 2.16GHz (2161.26-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x6e8 Stepping =3D 8 Features=3D0xbfe9fbff Features2=3D0xc1a9> AMD Features=3D0x100000 Cores per package: 2 real memory =3D 1072238592 (1022 MB) avail memory =3D 1040027648 (991 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, = RF5413) acpi0: on motherboard Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 acpi_acad0: on acpi0 battery0: on acpi0 battery1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: mem = 0xdd000000-0xddffffff,0xc0000000-0xcfffffff,0xde000000-0xdeffffff irq 16 = at device 0.0 on pci1 pci0: at device 27.0 (no driver attached) pcib2: at device 28.0 on pci0 pci11: on pcib2 pcib3: at device 28.1 on pci0 pci12: on pcib3 pci12: at device 0.0 (no driver attached) pcib4: at device 28.2 on pci0 pci9: on pcib4 bge0: mem = 0xdcef0000-0xdcefffff irq 18 at device 0.0 on pci9 bge0: firmware handshake timed out miibus0: on bge0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, = 1000baseT-FDX, auto bge0: Ethernet address: 00:15:c5:0a:17:86 pcib5: at device 28.3 on pci0 pci13: on pcib5 uhci0: port 0xbf80-0xbf9f irq 20 at = device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xbf60-0xbf7f irq 21 at = device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xbf40-0xbf5f irq 22 at = device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xbf20-0xbf3f irq 23 at = device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem = 0xffa80000-0xffa803ff irq 20 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered umass0: on = uhub4 pcib6: at device 30.0 on pci0 pci3: on pcib6 cbb0: at device 1.0 on pci3 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 fwohci0: <1394 Open Host Controller Interface> mem = 0xdcbff000-0xdcbfffff,0xdcbfe800-0xdcbfefff irq 19 at device 1.4 on pci3 fwohci0: OHCI version 1.10 (ROM=3D0) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 38:4f:c0:00:04:e8:24:50 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 3a:4f:c0:e8:24:50 fwe0: Ethernet address: 3a:4f:c0:e8:24:50 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=3D0xc800ffc0, gen=3D1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <=3D 0, cable IRM =3D 0 (me) firewire0: bus manager 0 (me) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port = 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf irq 17 at device 31.2 = on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64,0x62,0x66 irq 1 on = acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model GlidePoint, device ID 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on = acpi0 sio0: type 16550A sio0: [FAST] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcffff pnpid ORM0000 on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 uhub5: = on uhub0 uhub5: 4 ports with 1 removable, self powered uhub6: = on uhub1 uhub6: 3 ports with 2 removable, bus powered ugen0: on = uhub6 Timecounters tick every 1.000 msec ad0: 76319MB at ata0-master UDMA33 acd0: DVDR at ata1-master UDMA33 SMP: AP CPU #1 Launched! da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 = device=20 da0: 40.000MB/s transfers da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) Trying to mount root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted WARNING: /home was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /usr/obj was not properly dismounted WARNING: /var was not properly dismounted /var: mount pending error: blocks 24 files 1 WARNING: /var/log was not properly dismounted WARNING: /var/mail was not properly dismounted -------------------------------------------------------------------------= --- Thanks and Regards Nobel From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 10:59:24 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C3E316A47B for ; Sun, 2 Jul 2006 10:59:24 +0000 (UTC) (envelope-from outi@bytephobia.de) Received: from dd2626.kasserver.com (dd2626.kasserver.com [81.209.184.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92F5743D73 for ; Sun, 2 Jul 2006 10:59:22 +0000 (GMT) (envelope-from outi@bytephobia.de) Received: from ax-ws170.ft.axit.de (pD9E37239.dip.t-dialin.net [217.227.114.57]) by dd2626.kasserver.com (Postfix) with ESMTP id 98585E8B02; Sun, 2 Jul 2006 12:59:20 +0200 (CEST) Date: Sun, 2 Jul 2006 12:59:17 +0200 From: Patrick Hurrelmann To: "Bhuiyan Mohammad Iklash" Message-ID: <20060702125917.0ea505ac@ax-ws170.ft.axit.de> In-Reply-To: <000601c69d46$4d112a80$2b0114ac@NOBEL> References: <000601c69d46$4d112a80$2b0114ac@NOBEL> Organization: private X-Mailer: Sylpheed-Claws 2.3.1 (GTK+ 2.8.19; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MP__NDq=1zixR3flTOduXKHYeV" Cc: freebsd-current@freebsd.org Subject: Re: Bringing up bge0 cause panic error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 10:59:24 -0000 --MP__NDq=1zixR3flTOduXKHYeV Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline On Sat, 1 Jul 2006 20:41:08 +0100 "Bhuiyan Mohammad Iklash" wrote: > Hi > > I have install FreBSD 7 (June snapshot) in my Dell LATITUDE D820 > laptop. I am facing e serious problem. whenever i want to bring up > the bge0 interface using following command nuke#ifconfig bge0 up > panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia cpuid = 0 > KDB: enter: panic > [thread pid 834 tid 100078 ] > Stopped at kdb_enter+0X2b: nop > db> > > Then i can't do anything. I had install 6.1, that works fine. Then > from 6.1 i sync the current sourec and recompile system, but there > was an error during compillation. Then i have downloaded and > installed the snapshot and facing this problem. > > Please let me know how can i get rid of from this problem. Thanks in > advanse.. nuke#uname -a > FreeBSD nuke.bloodforlife.net 7.0-CURRENT-200606 FreeBSD > 7.0-CURRENT-200606 #0: Sun Jun 4 16:51:08 UTC 2006 > root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > here is my dmesg > Hi Nobel, I'm the proud owner of a Dell Latitude D620 and I faced the same problem like you. Using 6.1 I was able to use the bge-nic but on CURRENT it panics everytime I try to use it (Set it up or assign an IP-address). The problem is probably, that the PHY of the be-nic isn't recognised and a generic PHY attaches (See your dmesg: ukphy0). Please try the attached patch. It make the Broadom-PHY attach to the card. For me it works great, although it does not solve the firmware handshake timeouts. But please note: I'm no c-programmer and the patch may be crap, but at least it works ;) Patrick -- ==================================================================== Patrick Hurrelmann | "Programming today is a race between software Mannheim, Germany | engineers striving to build bigger and better | idiot-proof programs, and the Universe trying outi@bytephobia.de | to produce bigger and better idiots. So far, www.bytephobia.de | the Universe is winning." - Rich Cook /"\ \ / ASCII Ribbon Campaign X against HTML email & vCards / \ --MP__NDq=1zixR3flTOduXKHYeV Content-Type: text/plain; name=bge_patch Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=bge_patch ZGlmZiAtcnVOIC91c3Ivc3JjL3N5cy9kZXYvbWlpL2JyZ3BoeS5jIC91c3Ivc3JjLm9sZC9zeXMv ZGV2L21paS9icmdwaHkuYw0KLS0tIC91c3Ivc3JjL3N5cy9kZXYvbWlpL2JyZ3BoeS5jCVR1ZSBN YXkgMTYgMTY6MzY6MjggMjAwNg0KKysrIC91c3Ivc3JjLm9sZC9zeXMvZGV2L21paS9icmdwaHku YwlGcmkgSnVuIDMwIDE2OjI3OjQ2IDIwMDYNCkBAIC0xNzYsNiArMTc2LDExIEBADQogCQlkZXZp Y2Vfc2V0X2Rlc2MoZGV2LCBNSUlfU1RSX3h4QlJPQURDT01fQkNNNTcwOEMpOw0KIAkJcmV0dXJu KDApOw0KIAl9DQorCWlmIChNSUlfT1VJKG1hLT5taWlfaWQxLCBtYS0+bWlpX2lkMikgPT0gTUlJ X09VSV94eEJST0FEQ09NICYmDQorCSAgICBNSUlfTU9ERUwobWEtPm1paV9pZDIpID09IE1JSV9N T0RFTF94eEJST0FEQ09NX0JDTTU3NTIpIHsNCisJCWRldmljZV9zZXRfZGVzYyhkZXYsIE1JSV9T VFJfeHhCUk9BRENPTV9CQ001NzUyKTsNCisJCXJldHVybigwKTsNCisJfQ0KIA0KIAlyZXR1cm4o RU5YSU8pOw0KIH0NCmRpZmYgLXJ1TiAvdXNyL3NyYy9zeXMvZGV2L21paS9taWlkZXZzIC91c3Iv c3JjLm9sZC9zeXMvZGV2L21paS9taWlkZXZzDQotLS0gL3Vzci9zcmMvc3lzL2Rldi9taWkvbWlp ZGV2cwlNb24gQXByIDEwIDIxOjU1OjIzIDIwMDYNCisrKyAvdXNyL3NyYy5vbGQvc3lzL2Rldi9t aWkvbWlpZGV2cwlGcmkgSnVuIDMwIDE2OjI3OjQ2IDIwMDYNCkBAIC0xMTcsNiArMTE3LDcgQEAN CiBtb2RlbCB4eEJST0FEQ09NIEJDTTU0MDAJMHgwMDA0IEJyb2FkY29tIDEwMDBiYXNlVFggUEhZ DQogbW9kZWwgeHhCUk9BRENPTSBCQ001NDAxCTB4MDAwNSBCQ001NDAxIDEwLzEwMC8xMDAwYmFz ZVRYIFBIWQ0KIG1vZGVsIHh4QlJPQURDT00gQkNNNTQxMQkweDAwMDcgQkNNNTQxMSAxMC8xMDAv MTAwMGJhc2VUWCBQSFkNCittb2RlbCB4eEJST0FEQ09NIEJDTTU3NTIJMHgwMDEwIEJDTTU3NTIg MTAvMTAwLzEwMDBiYXNlVFggUEhZDQogbW9kZWwgeHhCUk9BRENPTSBCQ001NzAxCTB4MDAxMSBC Q001NzAxIDEwLzEwMC8xMDAwYmFzZVRYIFBIWQ0KIG1vZGVsIHh4QlJPQURDT00gQkNNNTcwMwkw eDAwMTYgQkNNNTcwMyAxMC8xMDAvMTAwMGJhc2VUWCBQSFkNCiBtb2RlbCB4eEJST0FEQ09NIEJD TTU3MDQJMHgwMDE5IEJDTTU3MDQgMTAvMTAwLzEwMDBiYXNlVFggUEhZDQo= --MP__NDq=1zixR3flTOduXKHYeV-- From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 13:54:16 2006 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7356F16A40F; Sun, 2 Jul 2006 13:54:16 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id A74F243D48; Sun, 2 Jul 2006 13:54:15 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.13.6/8.13.6/NinthNine) with ESMTP id k62DsBWu095155; Sun, 2 Jul 2006 22:54:12 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Sun, 2 Jul 2006 22:54:11 +0900 From: Norikatsu Shigemura To: Daniel Eischen Message-Id: <20060702225411.4bd0e2dd.nork@FreeBSD.org> In-Reply-To: References: <44986777.6070601@FreeBSD.org> <20060621061437.GA53019@fit.vutbr.cz> <2265.211.18.249.19.1150871779.squirrel@mail.ninth-nine.com> <20060621121114.h6udocel5wsgg8sg@netchild.homeip.net> <2692.219.127.74.121.1150885501.squirrel@mail.ninth-nine.com> <20060621155053.d6lseiz8z4ow8wo8@netchild.homeip.net> <20060623013106.d4397e26.nork@FreeBSD.org> <20060622230416.3907a848@kan.dnsalias.net> <20060625191405.d0e78240.nork@FreeBSD.org> X-Mailer: Sylpheed version 2.2.6 (GTK+ 2.8.19; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (sakura.ninth-nine.com [219.127.74.121]); Sun, 02 Jul 2006 22:54:14 +0900 (JST) Cc: Alexander@Leidinger.net, current@FreeBSD.org, nork@FreeBSD.org, kabaev@gmail.com Subject: Re: Linux-flashplugin7 & rtld - RFC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 13:54:16 -0000 On Mon, 26 Jun 2006 15:06:33 -0400 (EDT) Daniel Eischen wrote: > The check for the object providing the correct version should > still be done, but it needs to be checking the correct (libmap'd) > object. Eureka!!! I understand why my approch should be integrated to libc/libm/ libpthread, and deischen's approch failuer. So I can sperate library from libc/libm/libpthread. deischen's LPW: $ readelf -Ws flash7.so | fgrep open 71: 00001760 54 FUNC LOCAL DEFAULT 11 popen 110: 000025e0 54 FUNC LOCAL DEFAULT 11 iconv_open 185: 00001520 54 FUNC LOCAL DEFAULT 11 fopen 198: 000016e0 54 FUNC LOCAL DEFAULT 11 opendir These are bad. $ readelf -Ws flash7.so | fgrep pthread_ : 27: 00000000 117 FUNC GLOBAL DEFAULT UND _pthread_mutex_init@LIBTHREAD_1_0 (13) : 70: 00000f80 94 FUNC LOCAL DEFAULT 11 pthread_mutex_init@GLIBC_2.0 : These are good. So it should be fixed like following: flash7.so: flash7.map ${FLASH7OBJ} ${CC} -shared -o $@ ${CFLAGS} ${FLASH7OBJ} \ -Wl,--version-script=flash7.map -lc -lm -lpthread -lstdc++ ~~~~ From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 14:29:32 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63A5D16A416 for ; Sun, 2 Jul 2006 14:29:32 +0000 (UTC) (envelope-from michiel@boland.org) Received: from neerbosch.nijmegen.internl.net (neerbosch.nijmegen.internl.net [217.149.193.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id B348944403 for ; Sun, 2 Jul 2006 14:29:30 +0000 (GMT) (envelope-from michiel@boland.org) Received: from brakkenstein.nijmegen.internl.net by neerbosch.nijmegen.internl.net via brakkenstein.nijmegen.internl.net [217.149.193.41] with ESMTP for id k62ETT82016170 (8.13.4/1.4); Sun, 2 Jul 2006 16:29:29 +0200 (MEST) Received: from localhost by brakkenstein.nijmegen.internl.net via mboland@localhost with ESMTP for id k62ETT4t027097 (8.13.2/2.02); Sun, 2 Jul 2006 16:29:29 +0200 (MEST) X-Authentication-Warning: brakkenstein.nijmegen.internl.net: mboland owned process doing -bs Date: Sun, 2 Jul 2006 16:29:27 +0200 (MEST) From: Michiel Boland To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: em0: watchdog timeout -- resetting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 14:29:32 -0000 Hi. I frequently get em0: watchdog timeout -- resetting messages, followed by loss of network at the most inopportune moments. It appears that it can be triggered by things like typing 'portinstall mozilla' over an SSH connection. But that is just a hunch. Any ideas how to debug this further? Hardware is a dell optiplex GX270. Kernel is -CURRENT from 29 june. Cheers Michiel From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 14:34:01 2006 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5076916A5FE; Sun, 2 Jul 2006 14:34:01 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAFB244097; Sun, 2 Jul 2006 14:03:56 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.13.6/8.13.6/NinthNine) with ESMTP id k62E3tJv095413; Sun, 2 Jul 2006 23:03:56 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Sun, 2 Jul 2006 23:03:55 +0900 From: Norikatsu Shigemura To: Alexander Kabaev Message-Id: <20060702230355.3d720352.nork@FreeBSD.org> In-Reply-To: <20060627220953.24a8e7fe@kan.dnsalias.net> References: <44986777.6070601@FreeBSD.org> <20060621061437.GA53019@fit.vutbr.cz> <2265.211.18.249.19.1150871779.squirrel@mail.ninth-nine.com> <20060621121114.h6udocel5wsgg8sg@netchild.homeip.net> <2692.219.127.74.121.1150885501.squirrel@mail.ninth-nine.com> <20060621155053.d6lseiz8z4ow8wo8@netchild.homeip.net> <20060623013106.d4397e26.nork@FreeBSD.org> <20060622230416.3907a848@kan.dnsalias.net> <20060625191405.d0e78240.nork@FreeBSD.org> <20060627220953.24a8e7fe@kan.dnsalias.net> X-Mailer: Sylpheed version 2.2.6 (GTK+ 2.8.19; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (sakura.ninth-nine.com [219.127.74.121]); Sun, 02 Jul 2006 23:03:56 +0900 (JST) Cc: deischen@FreeBSD.org, Alexander@Leidinger.net, current@FreeBSD.org Subject: Re: Linux-flashplugin7 & rtld - RFC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 14:34:01 -0000 Eureka!!!! On Tue, 27 Jun 2006 22:09:53 -0400 Alexander Kabaev wrote: > Nobody will banish anything. _Proper_ pathches to make rtld handle > libmapped libraries more completely are welcome though. No more rtld:-). I found a work around. > > 2. firefox doesn't use libc/libm/libpthread. But wrapper has > > libc/libm/libpthread all codes. > > /etc/libmap.conf ----------------------------------------------- > > [firefox-bin] > > libc.so.7 wrapper.so > > libm.so.4 wrapper.so > > libpthread.so.2 wrapper.so > > /etc/libmap.conf ----------------------------------------------- > > So I think that glibc functions are integrated to > > libc/m/pthread. But above issue will be fixed, I may think that > > separate libraries are good way. > glibc functions integrated into libc/m/pthread will never hit the tree. I understood that 2 is bad. Because wrapper.so has bad symbols as non-versioning. You can test new Userland Compat Linux Technology[TM:-)]. http://people.freebsd.org/~nork/UserlandCompatLinux-20060702.tar.bz2 /etc/libmap.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [/usr/X11R6/lib/linux-flashplugin7/libflashplayer.so] libpthread.so.0 libcompatlinux.so.0 libdl.so.2 libcompatlinux.so.0 libz.so.1 libz.so.3 libm.so.6 libcompatlinux.so.0 libc.so.6 libcompatlinux.so.0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - And set you environment value like following: FLASH_GTK_LIBRARY=/usr/X11R6/lib/libgtk-x11-2.0.so.0 And I know a issue, but I cannot fix:-(. Please change 'catalogue' line: /usr/X11R6/lib/X11/fs/config - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - catalogue = /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Please see also: readelf -Ws libcompatlinux.so.0 From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 16:01:52 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15C3816A415 for ; Sun, 2 Jul 2006 16:01:52 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from ms-smtp-02.southeast.rr.com (ms-smtp-02.southeast.rr.com [24.25.9.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98F1243D49 for ; Sun, 2 Jul 2006 16:01:51 +0000 (GMT) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (cpe-024-211-118-154.sc.res.rr.com [24.211.118.154]) by ms-smtp-02.southeast.rr.com (8.13.6/8.13.6) with ESMTP id k62G1igX027107; Sun, 2 Jul 2006 12:01:45 -0400 (EDT) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.13.6/8.13.6) with ESMTP id k62G1i1S022492; Sun, 2 Jul 2006 12:01:44 -0400 (EDT) (envelope-from morganw@chemikals.org) Date: Sun, 2 Jul 2006 12:01:43 -0400 (EDT) From: Wesley Morgan To: Michiel Boland In-Reply-To: Message-ID: <20060702115840.L12091@volatile.chemikals.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-current@freebsd.org Subject: Re: em0: watchdog timeout -- resetting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 16:01:52 -0000 On Sun, 2 Jul 2006, Michiel Boland wrote: > Hi. I frequently get > > em0: watchdog timeout -- resetting > > messages, followed by loss of network at the most inopportune moments. > > It appears that it can be triggered by things like typing 'portinstall > mozilla' over an SSH connection. But that is just a hunch. > > Any ideas how to debug this further? > > Hardware is a dell optiplex GX270. Kernel is -CURRENT from 29 june. I have the same issue on my laptop. It seems like the problem came into being a few months ago, but I've never gone any further than trying to revert to a previous version of the driver, which did not help. For me, the problem is more than just loss of network, but rather every application hanging while multiple timeouts occurr. -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 17:06:53 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05F4616A417 for ; Sun, 2 Jul 2006 17:06:53 +0000 (UTC) (envelope-from kamtha@mail.ak-labs.net) Received: from ak-labs.net (mail.ak-labs.net [71.140.59.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCE224459E for ; Sun, 2 Jul 2006 17:06:39 +0000 (GMT) (envelope-from kamtha@mail.ak-labs.net) Received: from mail.ak-labs.net (localhost [127.0.0.1]) by ak-labs.net (8.13.3/8.13.3) with ESMTP id k62H5DEo021019; Sun, 2 Jul 2006 10:05:14 -0700 (PDT) (envelope-from kamtha@mail.ak-labs.net) Received: (from kamtha@localhost) by mail.ak-labs.net (8.13.3/8.13.3/Submit) id k62H5D1V021018; Sun, 2 Jul 2006 10:05:13 -0700 (PDT) (envelope-from kamtha) Date: Sun, 2 Jul 2006 10:05:13 -0700 From: Carlos Sean Kamtha To: Michiel Boland Message-ID: <20060702170512.GA16009@ak-labs.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: em0: watchdog timeout -- resetting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 17:06:53 -0000 On Sun, Jul 02, 2006 at 04:29:27PM +0200, Michiel Boland wrote: > Hi. I frequently get > > em0: watchdog timeout -- resetting > > messages, followed by loss of network at the most inopportune moments. > > It appears that it can be triggered by things like typing 'portinstall > mozilla' over an SSH connection. But that is just a hunch. > > Any ideas how to debug this further? > > Hardware is a dell optiplex GX270. Kernel is -CURRENT from 29 june. > I suggest that this is an hardware issue. I have dealt with this problem before and fixed it by replacing the NIC. I hope this is an option for now. Carlos. From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 18:45:05 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2D8116A606 for ; Sun, 2 Jul 2006 18:45:04 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B02B43D53 for ; Sun, 2 Jul 2006 18:45:04 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1Fx6wI-00048T-Kv for freebsd-current@freebsd.org; Sun, 02 Jul 2006 20:45:02 +0200 Received: from 82-70-166-86.dsl.in-addr.zen.co.uk ([82.70.166.86]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 02 Jul 2006 20:45:02 +0200 Received: from gmane by 82-70-166-86.dsl.in-addr.zen.co.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 02 Jul 2006 20:45:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: "Steve A" Date: Sun, 2 Jul 2006 19:02:53 +0100 Lines: 34 Message-ID: X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 82-70-166-86.dsl.in-addr.zen.co.uk X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-RFC2646: Format=Flowed; Original Sender: news X-Mailman-Approved-At: Sun, 02 Jul 2006 19:00:10 +0000 Subject: FreeBSD add user script syntax X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 18:45:05 -0000 I've got Samba set up as a domain controller successfully, and am now wanting to user usrmgr.exe and svrmgr.exe to make basic user admin changes from a Windows workstation. Some stuff works, and some stuff doesn't, and I was looking for some help with the script sections listed here... What works: add user script = pw user add -n %u -g users -c "Windows User" -s /usr/bin/nologin delete user script = pw user del -n %u -r add group script = pw group add -n %g add machine script = pw user add -n %u -g winstations -c Windows_Machine -s /usr/sbin/nologin What doesn't work: delete group script = pw group del -n %g add user to group script = pw group mod -n %g -M %u set primary group script = pw user mod -n %u -g %g What I can't figure out: rename user script = delete user from group script = Does anyone have examples that work that could pinch please? Many thanks, Steve :) From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 22:20:41 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DB3116A4DD for ; Sun, 2 Jul 2006 22:20:41 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C10E844A2D for ; Sun, 2 Jul 2006 01:10:06 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1FwqTK-0006cL-AN for freebsd-current@freebsd.org; Sun, 02 Jul 2006 03:10:02 +0200 Received: from p549e2bbc.dip0.t-ipconnect.de ([84.158.43.188]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 02 Jul 2006 03:10:02 +0200 Received: from tps by p549e2bbc.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 02 Jul 2006 03:10:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Thomas Schweikle Date: Sun, 02 Jul 2006 02:39:36 +0200 Organization: Ye 'Ol Disorganized NNTPCache groupie Lines: 10 Message-ID: <1151800824.982998@hazel> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p549e2bbc.dip0.t-ipconnect.de User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8.0.4) Gecko/20060516 SeaMonkey/1.0.2 Cache-Post-Path: hazel!unknown@pine.tps X-Cache: nntpcache 3.0.2 (see http://www.nntpcache.com/) Sender: news Subject: lnc0? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 22:20:41 -0000 Hi! Trying to compile CURRENT with lnc0 enabled (device lnc) gives back only "config: error: device 'lnc' is unknown". Is this removed from current? If yes, then why? VMware does need it (except you want to use 'vxn0' --- but you do not have to expect this device working). -- Thomas From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 22:56:39 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D44916A412 for ; Sun, 2 Jul 2006 22:56:39 +0000 (UTC) (envelope-from wsalamon@computer.org) Received: from wsalamon.net (wsalamon.net [216.127.158.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BDC443D9E for ; Sun, 2 Jul 2006 22:56:36 +0000 (GMT) (envelope-from wsalamon@computer.org) Received: from [192.168.1.9] (homer.wsalamon.net [192.168.1.9]) by wsalamon.net (Postfix) with ESMTP id 0120A172B02; Sun, 2 Jul 2006 18:56:34 -0400 (EDT) In-Reply-To: <1151800824.982998@hazel> References: <1151800824.982998@hazel> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <94470B71-E30D-4DE4-8D4C-20E81E0F7348@computer.org> Content-Transfer-Encoding: 7bit From: Wayne Salamon Date: Sun, 2 Jul 2006 18:56:32 -0400 To: Thomas Schweikle X-Mailer: Apple Mail (2.752.2) Cc: freebsd-current@freebsd.org Subject: Re: lnc0? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 22:56:39 -0000 On Jul 1, 2006, at 8:39 PM, Thomas Schweikle wrote: > Trying to compile CURRENT with lnc0 enabled (device lnc) gives > back only "config: error: device 'lnc' is unknown". Is this > removed from current? If yes, then why? VMware does need it Yes, lnc device support is gone. For VMWare, use the le device, which works fine thanks to some recent changes by marius. ---------------------- Wayne Salamon wsalamon@freebsd.org From owner-freebsd-current@FreeBSD.ORG Mon Jul 3 04:16:57 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7269716A403; Mon, 3 Jul 2006 04:16:57 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECBDE43D46; Mon, 3 Jul 2006 04:16:56 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k634GtJA028957; Mon, 3 Jul 2006 00:16:55 -0400 (EDT) Date: Mon, 3 Jul 2006 00:16:55 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Norikatsu Shigemura In-Reply-To: <20060702225411.4bd0e2dd.nork@FreeBSD.org> Message-ID: References: <44986777.6070601@FreeBSD.org> <20060621061437.GA53019@fit.vutbr.cz> <2265.211.18.249.19.1150871779.squirrel@mail.ninth-nine.com> <20060621121114.h6udocel5wsgg8sg@netchild.homeip.net> <2692.219.127.74.121.1150885501.squirrel@mail.ninth-nine.com> <20060621155053.d6lseiz8z4ow8wo8@netchild.homeip.net> <20060623013106.d4397e26.nork@FreeBSD.org> <20060622230416.3907a848@kan.dnsalias.net> <20060625191405.d0e78240.nork@FreeBSD.org> <20060702225411.4bd0e2dd.nork@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: Alexander@Leidinger.net, kabaev@gmail.com, current@freebsd.org Subject: Re: Linux-flashplugin7 & rtld - RFC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 04:16:57 -0000 On Sun, 2 Jul 2006, Norikatsu Shigemura wrote: > On Mon, 26 Jun 2006 15:06:33 -0400 (EDT) > Daniel Eischen wrote: >> The check for the object providing the correct version should >> still be done, but it needs to be checking the correct (libmap'd) >> object. > > Eureka!!! > > I understand why my approch should be integrated to libc/libm/ > libpthread, and deischen's approch failuer. So I can sperate > library from libc/libm/libpthread. > > deischen's LPW: > $ readelf -Ws flash7.so | fgrep open > 71: 00001760 54 FUNC LOCAL DEFAULT 11 popen > 110: 000025e0 54 FUNC LOCAL DEFAULT 11 iconv_open > 185: 00001520 54 FUNC LOCAL DEFAULT 11 fopen > 198: 000016e0 54 FUNC LOCAL DEFAULT 11 opendir > These are bad. > > $ readelf -Ws flash7.so | fgrep pthread_ > : > 27: 00000000 117 FUNC GLOBAL DEFAULT UND _pthread_mutex_init@LIBTHREAD_1_0 (13) > : > 70: 00000f80 94 FUNC LOCAL DEFAULT 11 pthread_mutex_init@GLIBC_2.0 > : > These are good. > > So it should be fixed like following: > flash7.so: flash7.map ${FLASH7OBJ} > ${CC} -shared -o $@ ${CFLAGS} ${FLASH7OBJ} \ > -Wl,--version-script=flash7.map -lc -lm -lpthread -lstdc++ > ~~~~ Yes, I tried that also, but I couldn't get it to work. -- DE From owner-freebsd-current@FreeBSD.ORG Mon Jul 3 05:50:18 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5F9F16A417 for ; Mon, 3 Jul 2006 05:50:12 +0000 (UTC) (envelope-from frank@pinky.sax.de) Received: from pinky.frank-behrens.de (pinky.frank-behrens.de [82.139.199.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9056843D49 for ; Mon, 3 Jul 2006 05:50:07 +0000 (GMT) (envelope-from frank@pinky.sax.de) Received: from [192.168.20.32] (sun.behrens [192.168.20.32]) by pinky.frank-behrens.de (8.13.6/8.13.4) with ESMTP id k635o0VE059177; Mon, 3 Jul 2006 07:50:00 +0200 (CEST) (envelope-from frank@pinky.sax.de) Message-Id: <200607030550.k635o0VE059177@pinky.frank-behrens.de> From: "Frank Behrens" To: "M. Warner Losh" Date: Mon, 03 Jul 2006 07:49:59 +0200 MIME-Version: 1.0 Priority: normal In-reply-to: <20060630.002825.-345494538.imp@bsdimp.com> References: <200606271232.k5RCWqV4042089@pinky.frank-behrens.de> X-mailer: Pegasus Mail for Windows (4.31, DE v4.31 R1) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Cc: freebsd-current@freebsd.org Subject: Re: sio(4) should on probe return BUS_PROBE_GENERIC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 05:50:18 -0000 M. Warner Losh wrote on 30 Jun 2006 0:28: > I think you are right. A quick audit seems to indicate that while sio > sets stuff in its probe routine, it is all re-set in the attach > routine. A more complete audit might reveal something else... Thanks for your answer and committing the fix! Regards, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available. From owner-freebsd-current@FreeBSD.ORG Mon Jul 3 06:42:14 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E29C816A407 for ; Mon, 3 Jul 2006 06:42:14 +0000 (UTC) (envelope-from harikurniawan@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9903143D48 for ; Mon, 3 Jul 2006 06:42:13 +0000 (GMT) (envelope-from harikurniawan@gmail.com) Received: by nz-out-0102.google.com with SMTP id 34so384247nzf for ; Sun, 02 Jul 2006 23:42:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=cQZBrpdepbEueWIGgpc6T3/IpQJARW99n2E/bP+5DVyV9APjHSeJtyB4nCgJxGmgCZKIuYSFtckdwqV726G0i3KF/uPTE+8bsFzYJxdVXyTOJIfyoqHxn+xV3XiKnCqYEXJzdQ9TJVa5c/EYDVE9/8JPlRxJ12/Bmp4zdLoaDAU= Received: by 10.64.204.6 with SMTP id b6mr2720066qbg; Sun, 02 Jul 2006 23:42:13 -0700 (PDT) Received: by 10.64.125.19 with HTTP; Sun, 2 Jul 2006 23:42:13 -0700 (PDT) Message-ID: <4c40c4e70607022342nd815be6sf843f09ad9caec8d@mail.gmail.com> Date: Mon, 3 Jul 2006 13:42:13 +0700 From: "Angka H. K." To: freebsd-current@freebsd.org MIME-Version: 1.0 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: Compiled fail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 06:42:15 -0000 My source was updated on saturday july 1. ACPI_assus linux_emulator some arm related is not compiled even using the GENERIC kernel config. It say something about some variable defined outsite the function and mistype parameter. regards. From owner-freebsd-current@FreeBSD.ORG Mon Jul 3 12:39:35 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3577216A47B for ; Mon, 3 Jul 2006 12:39:35 +0000 (UTC) (envelope-from richardtector@thekeelecentre.com) Received: from mx0.thekeelecentre.com (mx0.thekeelecentre.com [217.206.238.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DBE743DE5 for ; Mon, 3 Jul 2006 12:39:30 +0000 (GMT) (envelope-from richardtector@thekeelecentre.com) Received: from localhost (mailfil.mx0.thekeelecentre.com [217.206.238.165]) by mx0.thekeelecentre.com (Postfix) with ESMTP id E17464109; Mon, 3 Jul 2006 13:39:29 +0100 (BST) X-Virus-Scanned: by amavisd-new at mx0.thekeelecentre.com Received: from mx0.thekeelecentre.com ([217.206.238.167]) by localhost (mailfil.mx0.thekeelecentre.com [217.206.238.165]) (amavisd-new, port 10024) with ESMTP id qtMOJ9Mfo+kZ; Mon, 3 Jul 2006 13:39:27 +0100 (BST) Received: from [217.206.238.190] (sylvester.tector.org.uk [217.206.238.190]) by mx0.thekeelecentre.com (Postfix) with ESMTP id 23E8840DE; Mon, 3 Jul 2006 13:39:27 +0100 (BST) Message-ID: <44A91000.8000202@thekeelecentre.com> Date: Mon, 03 Jul 2006 13:39:28 +0100 From: Richard Tector User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: "Angka H. K." References: <4c40c4e70607022342nd815be6sf843f09ad9caec8d@mail.gmail.com> In-Reply-To: <4c40c4e70607022342nd815be6sf843f09ad9caec8d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Compiled fail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 12:39:35 -0000 Angka H. K. wrote: > My source was updated on saturday july 1. > > ACPI_assus > linux_emulator > some arm related > > is not compiled even using the GENERIC kernel config. > > It say something about some variable defined outsite the function and > mistype parameter. This has been fixed now if you grab fresh sources. Regards, Richard From owner-freebsd-current@FreeBSD.ORG Mon Jul 3 15:00:50 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0498E16A535 for ; Mon, 3 Jul 2006 15:00:49 +0000 (UTC) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E38844087 for ; Mon, 3 Jul 2006 14:20:39 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id EEACF1A734 for ; Mon, 3 Jul 2006 16:20:36 +0200 (CEST) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 89120-03 for ; Mon, 3 Jul 2006 16:20:35 +0200 (CEST) Received: from [10.0.0.50] (sto-nat.se.tangram-group.net [212.37.5.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id CF0DE1A720 for ; Mon, 3 Jul 2006 16:20:35 +0200 (CEST) Message-ID: <44A927AC.7080807@shapeshifter.se> Date: Mon, 03 Jul 2006 16:20:28 +0200 From: Fredrik Lindberg User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="------------080500090504040201070603" X-Virus-Scanned: amavisd-new at h3q.net Subject: panic: knlist locked, but should not be X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 15:00:50 -0000 This is a multi-part message in MIME format. --------------080500090504040201070603 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I'm hitting this "knlist locked"-panic when using BPF descriptors together with kqueue/kevent. panic: knlist locked, but should not be #10 0xc051a1e3 in knlist_add (knl=0xc3b69460, kn=0xc3ad65d8, islocked=0) at /usr/src/sys/kern/kern_event.c:1571 #11 0xc059c5de in bpfkqfilter (dev=0x12, kn=0xc3ad65d8) at /usr/src/sys/net/bpf.c:1194 #12 0xc050d9e6 in giant_kqfilter (dev=0xc38f9d00, kn=0xc3ad65d8) at /usr/src/sys/kern/kern_conf.c:336 #13 0xc04e9580 in devfs_kqfilter_f (fp=0xc3ad40d8, kn=0xc3ad65d8) at /usr/src/sys/fs/devfs/devfs_vnops.c:444 #14 0xc0517e6d in filt_fileattach (kn=0x12) at file.h:305 #15 0xc0518eb0 in kqueue_register (kq=0xc3923780, kev=0xe3a67b9c, td=0xc3714a20, waitok=1) at /usr/src/sys/kern/kern_event.c:902 #16 0xc05185f4 in kern_kevent (td=0xc3714a20, fd=3, nchanges=1, nevents=0, k_ops=0xe3a67c70, timeout=0x0) at /usr/src/sys/kern/kern_event.c:640 #17 0xc0518491 in kevent (td=0xc3714a20, uap=0xe3a67d04) at /usr/src/sys/kern/kern_event.c:572 I thinks the problem is as follows, islocked is 0 which triggers the macro KNL_ASSERT_LOCK(knl, islocked); (It will only bite you if you run with INVARIANTS on) The knlist is initialized with the same mutex that protects the rest of the bpf_d structure. bpfopen(), sys/net/bpf.c:383 knlist_init(&d->bd_sel.si_note, &d->bd_mtx, NULL, NULL, NULL); In bpfkqfilter() and filt_bpfdetach() this mutex is acquired with BPFD_LOCK() before calling knlist_add()/knlist_remove() #define BPFD_LOCK(bd) mtx_lock(&(bd)->bd_mtx) Hence, the knlist lock IS locked despite being called with islocked = 0. If using the same mutex doesn't cause any additional problems, (I haven't noticed anything yet, but there could of course be issues that I've overlooked), I think knlist_add should be called with islocked = 1. A suggested patch is attached. Fredrik Lindberg --------------080500090504040201070603 Content-Type: text/plain; name="bpf.c-knlist-20060703.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="bpf.c-knlist-20060703.patch" Index: bpf.c =================================================================== RCS file: /home/ncvs/src/sys/net/bpf.c,v retrieving revision 1.168 diff -u -r1.168 bpf.c --- bpf.c 15 Jun 2006 15:39:12 -0000 1.168 +++ bpf.c 3 Jul 2006 11:36:30 -0000 @@ -1152,7 +1152,7 @@ d->bd_pid = curthread->td_proc->p_pid; kn->kn_fop = &bpfread_filtops; kn->kn_hook = d; - knlist_add(&d->bd_sel.si_note, kn, 0); + knlist_add(&d->bd_sel.si_note, kn, 1); BPFD_UNLOCK(d); return (0); @@ -1164,7 +1164,7 @@ struct bpf_d *d = (struct bpf_d *)kn->kn_hook; BPFD_LOCK(d); - knlist_remove(&d->bd_sel.si_note, kn, 0); + knlist_remove(&d->bd_sel.si_note, kn, 1); BPFD_UNLOCK(d); } --------------080500090504040201070603-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 3 18:37:21 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5209316A528; Mon, 3 Jul 2006 18:37:21 +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 42EE844B0D; Mon, 3 Jul 2006 18:14:12 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (ycmrx6ikrvo14wwc@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k63IEBri067413; Mon, 3 Jul 2006 11:14:11 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k63IE8iD067412; Mon, 3 Jul 2006 11:14:08 -0700 (PDT) (envelope-from jmg) Date: Mon, 3 Jul 2006 11:14:08 -0700 From: John-Mark Gurney To: Fredrik Lindberg Message-ID: <20060703181408.GB734@funkthat.com> Mail-Followup-To: Fredrik Lindberg , freebsd-current@freebsd.org, "Christian S. J. Peron" References: <44A927AC.7080807@shapeshifter.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44A927AC.7080807@shapeshifter.se> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 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-current@freebsd.org, "Christian S. J. Peron" Subject: Re: panic: knlist locked, but should not be X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 18:37:21 -0000 Fredrik Lindberg wrote this message on Mon, Jul 03, 2006 at 16:20 +0200: > I'm hitting this "knlist locked"-panic when using BPF descriptors > together with kqueue/kevent. > > panic: knlist locked, but should not be Yeh, csjp broke it in v1.161 by adjusting the locking w/o fixing the respective issues. > #10 0xc051a1e3 in knlist_add (knl=0xc3b69460, kn=0xc3ad65d8, islocked=0) > at /usr/src/sys/kern/kern_event.c:1571 > #11 0xc059c5de in bpfkqfilter (dev=0x12, kn=0xc3ad65d8) at > /usr/src/sys/net/bpf.c:1194 > #12 0xc050d9e6 in giant_kqfilter (dev=0xc38f9d00, kn=0xc3ad65d8) > at /usr/src/sys/kern/kern_conf.c:336 > #13 0xc04e9580 in devfs_kqfilter_f (fp=0xc3ad40d8, kn=0xc3ad65d8) > at /usr/src/sys/fs/devfs/devfs_vnops.c:444 > #14 0xc0517e6d in filt_fileattach (kn=0x12) at file.h:305 > #15 0xc0518eb0 in kqueue_register (kq=0xc3923780, kev=0xe3a67b9c, > td=0xc3714a20, waitok=1) > at /usr/src/sys/kern/kern_event.c:902 > #16 0xc05185f4 in kern_kevent (td=0xc3714a20, fd=3, nchanges=1, > nevents=0, k_ops=0xe3a67c70, > timeout=0x0) at /usr/src/sys/kern/kern_event.c:640 > #17 0xc0518491 in kevent (td=0xc3714a20, uap=0xe3a67d04) at > /usr/src/sys/kern/kern_event.c:572 > > I thinks the problem is as follows, islocked is 0 which triggers > the macro KNL_ASSERT_LOCK(knl, islocked); > (It will only bite you if you run with INVARIANTS on) > > The knlist is initialized with the same mutex that protects the > rest of the bpf_d structure. > bpfopen(), sys/net/bpf.c:383 > > knlist_init(&d->bd_sel.si_note, &d->bd_mtx, NULL, NULL, NULL); > > In bpfkqfilter() and filt_bpfdetach() this mutex is acquired with > BPFD_LOCK() before calling knlist_add()/knlist_remove() > > #define BPFD_LOCK(bd) mtx_lock(&(bd)->bd_mtx) > > Hence, the knlist lock IS locked despite being called with islocked = 0. > If using the same mutex doesn't cause any additional problems, > (I haven't noticed anything yet, but there could of course be issues > that I've overlooked), I think knlist_add should be called > with islocked = 1. A suggested patch is attached. > > > Fredrik Lindberg > Index: bpf.c > =================================================================== > RCS file: /home/ncvs/src/sys/net/bpf.c,v > retrieving revision 1.168 > diff -u -r1.168 bpf.c > --- bpf.c 15 Jun 2006 15:39:12 -0000 1.168 > +++ bpf.c 3 Jul 2006 11:36:30 -0000 > @@ -1152,7 +1152,7 @@ > d->bd_pid = curthread->td_proc->p_pid; > kn->kn_fop = &bpfread_filtops; > kn->kn_hook = d; > - knlist_add(&d->bd_sel.si_note, kn, 0); > + knlist_add(&d->bd_sel.si_note, kn, 1); > BPFD_UNLOCK(d); > > return (0); > @@ -1164,7 +1164,7 @@ > struct bpf_d *d = (struct bpf_d *)kn->kn_hook; > > BPFD_LOCK(d); > - knlist_remove(&d->bd_sel.si_note, kn, 0); > + knlist_remove(&d->bd_sel.si_note, kn, 1); > BPFD_UNLOCK(d); > } Why not drop the lock lines and keep the 0? As you said since it's the same lock, locking it a bit later won't hurt... -- 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-current@FreeBSD.ORG Mon Jul 3 18:45:30 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CD5C16A407; Mon, 3 Jul 2006 18:45:30 +0000 (UTC) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EF2243D45; Mon, 3 Jul 2006 18:45:29 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id 2B53A1A734; Mon, 3 Jul 2006 20:45:27 +0200 (CEST) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 90215-06; Mon, 3 Jul 2006 20:45:25 +0200 (CEST) Received: from [192.168.1.100] (217-208-33-252-o926.tbon.telia.com [217.208.33.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id 497D21A6B2; Mon, 3 Jul 2006 20:45:25 +0200 (CEST) Message-ID: <44A965BD.70101@shapeshifter.se> Date: Mon, 03 Jul 2006 20:45:17 +0200 From: Fredrik Lindberg User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: John-Mark Gurney References: <44A927AC.7080807@shapeshifter.se> <20060703181408.GB734@funkthat.com> In-Reply-To: <20060703181408.GB734@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at h3q.net Cc: freebsd-current@freebsd.org, "Christian S. J. Peron" Subject: Re: panic: knlist locked, but should not be X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 18:45:30 -0000 John-Mark Gurney wrote: > > Why not drop the lock lines and keep the 0? As you said since it's > the same lock, locking it a bit later won't hurt... > A yes of course the locks can be dropped from filt_bpfdetach(), that's probably better. But bpfkqfilter() will have to keep its lock because it modifies data. The lines could also be swapped (releasing the lock before calling knlist_add) but that would just be stupid as the lock would be acquired again in knlist_add. Fredrik Lindberg From owner-freebsd-current@FreeBSD.ORG Mon Jul 3 20:07:19 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DBAB16A403 for ; Mon, 3 Jul 2006 20:07:19 +0000 (UTC) (envelope-from csjp@FreeBSD.org) Received: from ems01.seccuris.com (ems01.seccuris.com [204.112.0.35]) by mx1.FreeBSD.org (Postfix) with SMTP id 5A32943D45 for ; Mon, 3 Jul 2006 20:07:18 +0000 (GMT) (envelope-from csjp@FreeBSD.org) Received: (qmail 66610 invoked by uid 86); 3 Jul 2006 20:47:36 -0000 Received: from unknown (HELO ?127.0.0.1?) (204.112.0.37) by ems01.seccuris.com with SMTP; 3 Jul 2006 20:47:36 -0000 Message-ID: <44A978F7.1010607@FreeBSD.org> Date: Mon, 03 Jul 2006 15:07:19 -0500 From: "Christian S.J. Peron" User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530) MIME-Version: 1.0 To: Fredrik Lindberg References: <44A927AC.7080807@shapeshifter.se> <20060703181408.GB734@funkthat.com> <44A965BD.70101@shapeshifter.se> In-Reply-To: <44A965BD.70101@shapeshifter.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: John-Mark Gurney , freebsd-current@freebsd.org Subject: Re: panic: knlist locked, but should not be X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 20:07:19 -0000 Fredrik Lindberg wrote: > John-Mark Gurney wrote: >> >> Why not drop the lock lines and keep the 0? As you said since it's >> the same lock, locking it a bit later won't hurt... >> > > A yes of course the locks can be dropped from filt_bpfdetach(), that's > probably better. But bpfkqfilter() will have to keep its lock because it > modifies data. The lines could also be swapped (releasing the lock > before calling knlist_add) but that would just be stupid as the lock > would be acquired again in knlist_add. > > Fredrik Lindberg > > I have committed a fix for this which should make everyone happy. However, my change 1.161 didn't actually fix what I had originally set out to fix, as there is still a race between kevent(2) and close(2). I think a possible solution here might be to extend the scope of the bpf_mtx mutex in bpfclose and pickup that lock in the kqueue operations. I need to give this a bit more thought. Sorry for the breakage, and thanks for bringing this to my attention! -- Christian S.J. Peron csjp@FreeBSD.ORG FreeBSD Committer FreeBSD Security Team From owner-freebsd-current@FreeBSD.ORG Mon Jul 3 21:18:57 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 245FE16A415 for ; Mon, 3 Jul 2006 21:18:57 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [213.238.47.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38A15449DA for ; Mon, 3 Jul 2006 21:18:55 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.7/8.13.7) with ESMTP id k63LIcZP045996 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Mon, 3 Jul 2006 23:18:48 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <20060630213259.GA20670@odin.ac.hmc.edu> References: <4498D108.90907@rogers.com> <20060621053007.GA3320@odin.ac.hmc.edu> <20060630213259.GA20670@odin.ac.hmc.edu> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <953595BB-0939-4CCB-85B7-65F99F02275E@lassitu.de> Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Mon, 3 Jul 2006 23:18:06 +0200 To: Brooks Davis X-Mailer: Apple Mail (2.752.2) Cc: Mike Jakubik , freebsd-current@freebsd.org, Garance A Drosihn , Justin Hibbits Subject: Re: ~/.hosts patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 21:18:57 -0000 Am 30.06.2006 um 23:32 schrieb Brooks Davis: > I'm very familiar with .ssh/config and it's not sufficent for at least > one server I know of. The problem is that the client must think it is > connecting to server.fully.qualified.domain and do so by name because > the name is passed to the server which misuses in in interesting ways. I'm probably just a bit too thick to really understand this, but why not teach the ssh client to pass the desired "virtual ssh host name" to the server, instead of trying to muck around with DNS or /etc/hosts? Is this "virtual host" feature part of the standard OpenSSH? It sure seems like a nice feature to hop from a bastion host directly to an internal machine... Cheers, Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-current@FreeBSD.ORG Mon Jul 3 21:55:07 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A09016A403 for ; Mon, 3 Jul 2006 21:55:06 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 848FD43D45 for ; Mon, 3 Jul 2006 21:55:06 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k63Lt5jW019251; Mon, 3 Jul 2006 14:55:05 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k63Lt4a6019250; Mon, 3 Jul 2006 14:55:04 -0700 Date: Mon, 3 Jul 2006 14:55:04 -0700 From: Brooks Davis To: Stefan Bethke Message-ID: <20060703215504.GC22556@odin.ac.hmc.edu> References: <4498D108.90907@rogers.com> <20060621053007.GA3320@odin.ac.hmc.edu> <20060630213259.GA20670@odin.ac.hmc.edu> <953595BB-0939-4CCB-85B7-65F99F02275E@lassitu.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jy6Sn24JjFx/iggw" Content-Disposition: inline In-Reply-To: <953595BB-0939-4CCB-85B7-65F99F02275E@lassitu.de> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: Mike Jakubik , freebsd-current@freebsd.org, Garance A Drosihn , Justin Hibbits Subject: Re: ~/.hosts patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 21:55:07 -0000 --jy6Sn24JjFx/iggw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 03, 2006 at 11:18:06PM +0200, Stefan Bethke wrote: > Am 30.06.2006 um 23:32 schrieb Brooks Davis: >=20 > >I'm very familiar with .ssh/config and it's not sufficent for at least > >one server I know of. The problem is that the client must think it is > >connecting to server.fully.qualified.domain and do so by name because > >the name is passed to the server which misuses in in interesting ways. >=20 > I'm probably just a bit too thick to really understand this, but why =20 > not teach the ssh client to pass the desired "virtual ssh host name" =20 > to the server, instead of trying to muck around with DNS or /etc/hosts? >=20 > Is this "virtual host" feature part of the standard OpenSSH? It sure =20 > seems like a nice feature to hop from a bastion host directly to an =20 > internal machine... The problem is that the client application using a port forwarded to localhost:port via ssh must connect to that port via the host name of the remote server or it will crash the remote server because it also passes localhost or 127.0.0.1 to the remote server over the TCP session and the server misbehaves in that case. Yes it's a bug in both the remote server and the client/server protocol, but that's really beside the point. Crappy software exists and sometimes we have to deal with it. The simple fact is that I needed a hack like this and there wasn't another solution (with possible exception of a SOCKS proxy, which wasn't an option at the time) a ~/.hosts file would have been a nice way to implement part of it rather than actually adding the entry to /etc/hosts. Please do me the favor of assuming that I have a clue and that I wouldn't have done such a think if there had been an easier solution. :) -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --jy6Sn24JjFx/iggw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEqZI3XY6L6fI4GtQRAkW+AJ96SBcZR0RgxcXHwjYwWqoMMVO3ZACfdfH9 nm3lPjmojCjg70zxZeUxrOo= =PYLx -----END PGP SIGNATURE----- --jy6Sn24JjFx/iggw-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 3 22:00:11 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA6D716A403 for ; Mon, 3 Jul 2006 22:00:11 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [213.238.47.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6A4F43D49 for ; Mon, 3 Jul 2006 22:00:08 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.7/8.13.7) with ESMTP id k63LxsjD046482 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 4 Jul 2006 00:00:04 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <20060703215504.GC22556@odin.ac.hmc.edu> References: <4498D108.90907@rogers.com> <20060621053007.GA3320@odin.ac.hmc.edu> <20060630213259.GA20670@odin.ac.hmc.edu> <953595BB-0939-4CCB-85B7-65F99F02275E@lassitu.de> <20060703215504.GC22556@odin.ac.hmc.edu> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Mon, 3 Jul 2006 23:59:22 +0200 To: Brooks Davis X-Mailer: Apple Mail (2.752.2) Cc: Mike Jakubik , freebsd-current@freebsd.org, Garance A Drosihn , Justin Hibbits Subject: Re: ~/.hosts patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 22:00:11 -0000 Am 03.07.2006 um 23:55 schrieb Brooks Davis: > On Mon, Jul 03, 2006 at 11:18:06PM +0200, Stefan Bethke wrote: >> I'm probably just a bit too thick to really understand this, ... > The problem is that the client application using a port forwarded to > localhost:port via ssh must connect to that port via the host name of > the remote server or it will crash the remote server... Sorry for the noise, I did misunderstand which clients and servers were involved. Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-current@FreeBSD.ORG Mon Jul 3 22:11:47 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D429D16A4D4 for ; Mon, 3 Jul 2006 22:11:47 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [213.238.47.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDE6643DD3 for ; Mon, 3 Jul 2006 22:09:59 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.7/8.13.7) with ESMTP id k63M9kx0046616 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 4 Jul 2006 00:09:56 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <20060630213259.GA20670@odin.ac.hmc.edu> References: <4498D108.90907@rogers.com> <20060621053007.GA3320@odin.ac.hmc.edu> <20060630213259.GA20670@odin.ac.hmc.edu> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Tue, 4 Jul 2006 00:09:14 +0200 To: Brooks Davis X-Mailer: Apple Mail (2.752.2) Cc: Mike Jakubik , freebsd-current@freebsd.org, Garance A Drosihn , Justin Hibbits Subject: Re: ~/.hosts patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 22:11:47 -0000 OK, I think I do understand the issue now, and this might or might not help in your situation... Am 30.06.2006 um 23:32 schrieb Brooks Davis: > The problem is that the client must think it is > connecting to server.fully.qualified.domain and do so by name because > the name is passed to the server which misuses in in interesting ways. At work, we're running a sort-of-VPN to a client of ours using pf and ssh with the socks proxy. On our side, pf redirects all TCP traffic to a certain set of IPs to a local process on the internal firewall (IPs identical to the customers's network, and we've copyied over their internal DNS zones). The local proxy process (www/transproxy) then uses socks to establish a TCP connection via the (permanent) ssh tunnel to the clients network. At the client's side, nothing is required except for a sshd configured to allow for dynamic port forwardings (and working internal DNS). From client software at our end, and our customer's server processes, it's virtually indistinguishable from a standard connection: the IPs are the same, the DNS names are the same, only the origin of the connection in the customer's network is the gateway machine, instead of the real client at our end. This appears to be working quite well with quite a number of standard and proprietary protocols. HTH, Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-current@FreeBSD.ORG Tue Jul 4 04:02:24 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E0F116A4DE for ; Tue, 4 Jul 2006 04:02:24 +0000 (UTC) (envelope-from harikurniawan@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0B0843D58 for ; Tue, 4 Jul 2006 04:02:23 +0000 (GMT) (envelope-from harikurniawan@gmail.com) Received: by nz-out-0102.google.com with SMTP id 34so578098nzf for ; Mon, 03 Jul 2006 21:02:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=O13z5smW5R4XWw2guh/WmAOp/VnsQiRj3sVeIEOTgp/1QKgSE6Ok767HC4OPzoXzo/P5gRp5y1QqeSqGxfsFqKvSa8IyQViYr9MsVAVgKvqqMrZ0fJG4jsQ4fkRI+4zrVz3EoEuIyodi4/xq2baEKdUjEzpRNEVJNR7KWco/MW8= Received: by 10.65.254.1 with SMTP id g1mr3778477qbs; Mon, 03 Jul 2006 21:02:23 -0700 (PDT) Received: by 10.64.125.19 with HTTP; Mon, 3 Jul 2006 21:02:23 -0700 (PDT) Message-ID: <4c40c4e70607032102h12aacbb0od9e166cece930d53@mail.gmail.com> Date: Tue, 4 Jul 2006 11:02:23 +0700 From: "Angka H. K." To: "Richard Tector" In-Reply-To: <44A91000.8000202@thekeelecentre.com> MIME-Version: 1.0 References: <4c40c4e70607022342nd815be6sf843f09ad9caec8d@mail.gmail.com> <44A91000.8000202@thekeelecentre.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 Cc: freebsd-current@freebsd.org Subject: Re: Compiled fail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 04:02:24 -0000 Oh great thanks a lot On 7/3/06, Richard Tector wrote: > > Angka H. K. wrote: > > My source was updated on saturday july 1. > > > > ACPI_assus > > linux_emulator > > some arm related > > > > is not compiled even using the GENERIC kernel config. > > > > It say something about some variable defined outsite the function and > > mistype parameter. > This has been fixed now if you grab fresh sources. > > Regards, > > Richard > From owner-freebsd-current@FreeBSD.ORG Tue Jul 4 12:12:41 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EDBE16A4DA for ; Tue, 4 Jul 2006 12:12:41 +0000 (UTC) (envelope-from b.candler@pobox.com) Received: from rune.pobox.com (rune.pobox.com [208.210.124.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA04743D6D for ; Tue, 4 Jul 2006 12:12:36 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from rune (localhost [127.0.0.1]) by rune.pobox.com (Postfix) with ESMTP id ECF5F79795; Tue, 4 Jul 2006 08:12:57 -0400 (EDT) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by rune.sasl.smtp.pobox.com (Postfix) with ESMTP id 388C31B52A; Tue, 4 Jul 2006 08:12:52 -0400 (EDT) Received: from lists by mappit.local.linnet.org with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1FxjlU-0006IJ-So; Tue, 04 Jul 2006 13:12:28 +0100 Date: Tue, 4 Jul 2006 13:12:28 +0100 From: Brian Candler To: Brooks Davis Message-ID: <20060704121228.GA24152@uk.tiscali.com> References: <4498D108.90907@rogers.com> <20060621053007.GA3320@odin.ac.hmc.edu> <20060630213259.GA20670@odin.ac.hmc.edu> <953595BB-0939-4CCB-85B7-65F99F02275E@lassitu.de> <20060703215504.GC22556@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060703215504.GC22556@odin.ac.hmc.edu> User-Agent: Mutt/1.4.2.1i Cc: Mike Jakubik , freebsd-current@freebsd.org, Garance A Drosihn , Stefan Bethke , Justin Hibbits Subject: Re: ~/.hosts patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 12:12:41 -0000 On Mon, Jul 03, 2006 at 02:55:04PM -0700, Brooks Davis wrote: > The problem is that the client application using a port forwarded to > localhost:port via ssh must connect to that port via the host name of > the remote server or it will crash the remote server because it also > passes localhost or 127.0.0.1 to the remote server over the TCP session > and the server misbehaves in that case. Yes it's a bug in both the > remote server and the client/server protocol, but that's really beside > the point. Crappy software exists and sometimes we have to deal with > it. > > The simple fact is that I needed a hack like this and there wasn't > another solution (with possible exception of a SOCKS proxy, which wasn't > an option at the time) a ~/.hosts file would have been a nice way to > implement part of it rather than actually adding the entry to /etc/hosts. Well, assuming your client calls gethostbyname() then you could write a tiny library which always returns 127.0.0.1, and use LD_PRELOAD to load it beforehand. Another solution (which doesn't require coding) would be to run the application inside a jail, and either frig /etc/hosts there, or point resolv.conf to a nameserver inside the jail, which has a '*' A record mapping everything to 127.0.0.1 Regards, Brian. From owner-freebsd-current@FreeBSD.ORG Tue Jul 4 17:30:33 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD68A16A4DA for ; Tue, 4 Jul 2006 17:30:33 +0000 (UTC) (envelope-from martin@gneto.com) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id B43DF43D5E for ; Tue, 4 Jul 2006 17:30:31 +0000 (GMT) (envelope-from martin@gneto.com) Received: from ua-83-227-181-30.cust.bredbandsbolaget.se ([83.227.181.30] [83.227.181.30]) by mxfep01.bredband.com with ESMTP id <20060704173030.VUYG440.mxfep01.bredband.com@ua-83-227-181-30.cust.bredbandsbolaget.se> for ; Tue, 4 Jul 2006 19:30:30 +0200 Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by ua-83-227-181-30.cust.bredbandsbolaget.se (Postfix) with ESMTP id F013267922 for ; Tue, 4 Jul 2006 19:30:29 +0200 (CEST) Message-ID: <44AAA5B5.2020407@gneto.com> Date: Tue, 04 Jul 2006 19:30:29 +0200 From: Martin Nilsson User-Agent: Thunderbird 1.5.0.4 (X11/20060606) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: New em PCI-id X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 17:30:33 -0000 I got the new version of intels quad port PCI-X Gbit adapter. It is not detected by 6-STABLE: FreeBSD 6.1-STABLE #0: Fri Jun 30 18:45:32 CEST 2006 pcib3: at device 1.0 on pci2 pci3: on pcib3 pci3: at device 4.0 (no driver attached) pci3: at device 4.1 (no driver attached) pci3: at device 6.0 (no driver attached) pci3: at device 6.1 (no driver attached) IntelŽ PRO/1000 GT Quad Port Server Adapter http://www.intel.com/network/connectivity/products/pro1000gt_quadport_server_adapter.htm The chip is called NH82546GB (This is the new RoHS compatible model) pciconf -lv give four of these: none2@pci3:4:0: class=0x020000 card=0x11998086 chip=0x10b58086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet Can someone familiar with the em driver please add the new id. /Martin From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 11:45:42 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80EDF16A4DA for ; Wed, 5 Jul 2006 11:45:42 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2C0A43D77 for ; Wed, 5 Jul 2006 11:45:37 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id x3so785726nzd for ; Wed, 05 Jul 2006 04:45:29 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:subject:message-id:reply-to:mime-version:content-type:content-disposition:user-agent; b=hmN3B63ZAHfkrwBCxGpjSkluObVu4X142p472+sVMlgWK3quhd3GdfHJgW5g7wGBFqW2+3VHEplwQvbOfKqzX5kM5yTLceRfUFyt7u0Qny6O0+wYahc1ohxnA8/p8xh6M7m/uLbuennWHmsImJh1xzFKzTG0//Nxq4+MQxkcWiw= Received: by 10.36.80.17 with SMTP id d17mr4475219nzb; Wed, 05 Jul 2006 04:45:29 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 17sm3716560nzo.2006.07.05.04.45.27; Wed, 05 Jul 2006 04:45:28 -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 k65Bms8v074911 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 5 Jul 2006 20:48:54 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k65BmrQr074910 for freebsd-current@freebsd.org; Wed, 5 Jul 2006 20:48:53 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 5 Jul 2006 20:48:53 +0900 From: Pyun YongHyeon To: freebsd-current@freebsd.org Message-ID: <20060705114853.GB73705@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 11:45:42 -0000 Hi, This is a ported driver from NetBSD stge(4). It supports the following GigE adapters. o Antares Microsystems Gigabit Ethernet o ASUS NX1101 Gigabit Ethernet o D-Link DL-4000 Gigabit Ethernet o IC Plus IP1000A Gigabit Ethernet o Sundance ST-2021 Gigabit Ethernet o Sundance ST-2023 Gigabit Ethernet o Sundance TC9021 Gigabit Ethernet o Tamarack TC9021 Gigabit Ethernet The IP1000A Gigabit Ethernet is also found on some motherboards (LOM) from ABIT. Due to the lack of documentation(IC Plus Inc. required a NDA) I started from NetBSD stge(4) driver and fixed several bugs in stge(4). It no longer requires promiscuous mode operation to receive packet and it now supports all hardware features( IP/UDP/TCP checksum offload, VLAN tagging/insertion and JUMBO frame) and polling(4). However JUMBO frame support seems to have several bugs and I don't know how to solve it. Sometimes it would take a very long time(30~40 seconds) to work correctly after changing MTU and sometimes it works as expected. So I guess I missed required programming steps which is not available. to me. The driver was tested on i386 only but it seems to work well on my system. I'd like to hear success/failure reports on other architectures such as sparc64/amd64. In addition, I don't have adapters that have TBI transceivers so I'd also like to know if it work on those adapters too(The patch has a generic TBI driver from NetBSD). Normally I'm more concerned with reliability than speed so please report any strange behaviors noticed. You can get the latest stge(4) driver from the following URL. http://people.freebsd.org/~yongari/stge/stge.HEAD.diff You should add "device stge" in your kernel configuration file and rebuild/reboot or build a kernel module. You need latest HEAD to apply this diffs. Thank you. -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 15:52:55 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1DFB16A4DA; Wed, 5 Jul 2006 15:52:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 525CE43D49; Wed, 5 Jul 2006 15:52:54 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k65Fqp2x000393; Wed, 5 Jul 2006 11:52:51 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 5 Jul 2006 11:39:01 -0400 User-Agent: KMail/1.9.1 References: <20060630101132.S14714@godot.imp.ch> In-Reply-To: <20060630101132.S14714@godot.imp.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607051139.02615.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 05 Jul 2006 11:52:52 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1585/Tue Jul 4 16:39:34 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Martin Blapp , mlaier@freebsd.org Subject: Re: Please help reviewing ! Got another crash because of the ttymodem() / ttyclose() race X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 15:52:56 -0000 On Friday 30 June 2006 05:09, Martin Blapp wrote: > > Hi all, > > This time its FreeBSD 5.5 RELEASE. Same code is in 6.X (which crashed on a > different server 5 days ago) and CURRENT. > > #25 0xc064f4bd in ttymodem () > #26 0xc06532bd in ptcclose () > #27 0xc05e4e14 in spec_close () > #28 0xc05e3edf in spec_vnoperate () > #29 0xc06815e0 in vn_close () > #30 0xc06825f2 in vn_closefile () > #31 0xc0601ba4 in fdrop_locked () > #32 0xc0601af1 in fdrop () > #33 0xc060015b in closef () > #34 0xc05fd5e5 in close () > #35 0xc07c5e97 in syscall () > > Can PLEASE PLEASE someone help me fix this problem > and review the patch ? > > The patch is based on Max Laiers tty.t_pgrp patch. > > http://mx.imp.ch/patch-tty.t_pgrp.diff > > Especially the part in ttyinfo() needs to be reviewed > carefully. I'm not sure that the proctree_lock should protect t_pgrp as that is part of the tty structure, not process groups or session structures. I think probably it should be protected by Giant for now until the tty subsystem is locked. Also, the ttyinfo() part will not work since it tries to acquire a mutex (PGRP_LOCK()) while holding a spin mutex (sched_lock). -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 15:53:05 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3839316A4F2 for ; Wed, 5 Jul 2006 15:53:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07C4443D5D for ; Wed, 5 Jul 2006 15:53:03 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k65Fqp31000393; Wed, 5 Jul 2006 11:52:57 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 5 Jul 2006 11:49:28 -0400 User-Agent: KMail/1.9.1 References: <000601c69d46$4d112a80$2b0114ac@NOBEL> <20060702125917.0ea505ac@ax-ws170.ft.axit.de> In-Reply-To: <20060702125917.0ea505ac@ax-ws170.ft.axit.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607051149.29086.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 05 Jul 2006 11:52:58 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1585/Tue Jul 4 16:39:34 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Patrick Hurrelmann , Bhuiyan Mohammad Iklash Subject: Re: Bringing up bge0 cause panic error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 15:53:05 -0000 On Sunday 02 July 2006 06:59, Patrick Hurrelmann wrote: > On Sat, 1 Jul 2006 20:41:08 +0100 > "Bhuiyan Mohammad Iklash" wrote: > > > Hi > > > > I have install FreBSD 7 (June snapshot) in my Dell LATITUDE D820 > > laptop. I am facing e serious problem. whenever i want to bring up > > the bge0 interface using following command nuke#ifconfig bge0 up > > panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia cpuid = 0 > > KDB: enter: panic > > [thread pid 834 tid 100078 ] > > Stopped at kdb_enter+0X2b: nop > > db> > > > > Then i can't do anything. I had install 6.1, that works fine. Then > > from 6.1 i sync the current sourec and recompile system, but there > > was an error during compillation. Then i have downloaded and > > installed the snapshot and facing this problem. > > > > Please let me know how can i get rid of from this problem. Thanks in > > advanse.. nuke#uname -a > > FreeBSD nuke.bloodforlife.net 7.0-CURRENT-200606 FreeBSD > > 7.0-CURRENT-200606 #0: Sun Jun 4 16:51:08 UTC 2006 > > root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > > > here is my dmesg > > > > > Hi Nobel, > > I'm the proud owner of a Dell Latitude D620 and I faced the same problem > like you. Using 6.1 I was able to use the bge-nic but on CURRENT it > panics everytime I try to use it (Set it up or assign an IP-address). > > The problem is probably, that the PHY of the be-nic isn't recognised > and a generic PHY attaches (See your dmesg: ukphy0). > > Please try the attached patch. It make the Broadom-PHY attach to the > card. For me it works great, although it does not solve the firmware > handshake timeouts. > But please note: I'm no c-programmer and the patch may be crap, but at > least it works ;) Can you try also making this ID upload the 5750 dsp code to see if that helps with your timeouts? Something like this: Index: brgphy.c =================================================================== RCS file: /usr/cvs/src/sys/dev/mii/brgphy.c,v retrieving revision 1.42 diff -c -r1.42 brgphy.c *** brgphy.c 16 May 2006 14:36:28 -0000 1.42 --- brgphy.c 5 Jul 2006 15:48:41 -0000 *************** *** 657,662 **** --- 657,663 ---- bcm5704_load_dspcode(sc); break; case MII_MODEL_xxBROADCOM_BCM5750: + case MII_MODEL_xxBROADCOM_BCM5752: case MII_MODEL_xxBROADCOM_BCM5714: case MII_MODEL_xxBROADCOM_BCM5780: case MII_MODEL_xxBROADCOM_BCM5706C: (This would be in addition to your current patch) -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 15:53:17 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAD1616A52B for ; Wed, 5 Jul 2006 15:53:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5F7043D5D for ; Wed, 5 Jul 2006 15:53:14 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k65Fqp30000393; Wed, 5 Jul 2006 11:52:54 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 5 Jul 2006 11:42:27 -0400 User-Agent: KMail/1.9.1 References: <200607010009.09231@aldan> <20060701115508.GC8447@turion.vk2pj.dyndns.org> <200607011508.27920@aldan> In-Reply-To: <200607011508.27920@aldan> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200607051142.28352.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 05 Jul 2006 11:52:54 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1585/Tue Jul 4 16:39:34 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Peter Jeremy , Mikhail Teterin Subject: Re: weird limitation on the system's binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 15:53:17 -0000 On Saturday 01 July 2006 15:08, Mikhail Teterin wrote: > On Saturday 01 July 2006 07:55, Peter Jeremy wrote: > =3D IMHO, the FreeBSD base system should provide tools for doing native > =3D development - anything beyond that belongs in ports. =9AGiven that > =3D binutils supports quite an extensive range of targets (of the order of > =3D 100), building them all is impractical and a waste of resources for > =3D virtually everyone who uses FreeBSD. >=20 > I would agree with this myself, except that anything in the ports would h= ave=20 > to _duplicate_ or replace the system one. All of it -- not even just bfd = =2D-=20 > because it is all linked statically. Yes, this is normal behavior for ports that install things like alternative= =20 versions of gcc. > > libbdf.a is built by /usr/src/gnu/usr.bin/binutils/libbfd/Makefile. > > That should be a fairly simple change to arrange for it to build and > > install the .so as well. >=20 > Installing both libbfd-s certainly would be a good start... As things sta= nd,=20 > every port needing it -- including various different compilers -- builds = it=20 > own version. This is, largely, explained by the GNU's stupidity of bundli= ng > a different version with each tool (gdb, compiler), but the bundled bfds = are=20 > not THAT incompatible, and the system-installed version can include the=20 > compatible superset... Actually, in the past this has proven quite difficult, hence the current=20 arrangment of various tools linking statically against their own private=20 copy. =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 15:55:19 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3817F16A4DF for ; Wed, 5 Jul 2006 15:55:19 +0000 (UTC) (envelope-from jfvogel@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 27C2843D80 for ; Wed, 5 Jul 2006 15:54:51 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id b36so2099785pyb for ; Wed, 05 Jul 2006 08:54:51 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tVnwTsVd6pJI9QVqOrw/CHE6qQBh3FyJT/euSM/zoCEMW4Edo9/2CG7vCKSFtWM+exvjddThcH7fk2fWmRTXOJxESInCsXPa1A61ST/Hz1aN2p2gjvT6jGKe2TNOZaYf7m/lxSmuE/D19tCfQ9AiO1d6DnOYG2mV5ovuo2l5UvI= Received: by 10.35.37.18 with SMTP id p18mr3393815pyj; Wed, 05 Jul 2006 08:54:51 -0700 (PDT) Received: by 10.35.105.15 with HTTP; Wed, 5 Jul 2006 08:54:51 -0700 (PDT) Message-ID: <2a41acea0607050854x7825b204k6f199dd2e9584208@mail.gmail.com> Date: Wed, 5 Jul 2006 08:54:51 -0700 From: "Jack Vogel" To: "Martin Nilsson" In-Reply-To: <44AAA5B5.2020407@gneto.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44AAA5B5.2020407@gneto.com> Cc: freebsd-current@freebsd.org Subject: Re: New em PCI-id X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 15:55:19 -0000 On 7/4/06, Martin Nilsson wrote: > I got the new version of intels quad port PCI-X Gbit adapter. > It is not detected by 6-STABLE: > > FreeBSD 6.1-STABLE #0: Fri Jun 30 18:45:32 CEST 2006 > > pcib3: at device 1.0 on pci2 > pci3: on pcib3 > pci3: at device 4.0 (no driver attached) > pci3: at device 4.1 (no driver attached) > pci3: at device 6.0 (no driver attached) > pci3: at device 6.1 (no driver attached) > > Intel(r) PRO/1000 GT Quad Port Server Adapter > http://www.intel.com/network/connectivity/products/pro1000gt_quadport_server_adapter.htm > The chip is called NH82546GB (This is the new RoHS compatible model) > > pciconf -lv give four of these: > > none2@pci3:4:0: class=0x020000 card=0x11998086 chip=0x10b58086 rev=0x03 > hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > > Can someone familiar with the em driver please add the new id. Yes, there are a number of newer cards not yet in Stable. Once I have the ability to commit changes this should be remedied, but meanwhile you can use MY driver which is on the Intel website. Go to downloads area, network connectivity, then select server adapters, at that point almost any adapter will do, you will then get an OS select menu, find FreeBSD, and then you will see version 6.0.5, download that. That driver will work with either 6.0 or 6.1, and it supports all our PCI Express adapters including the new ones . I hope to integrate the changes in our driver into STABLE before 6.2. Jack From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 16:02:56 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 477F816A4E5 for ; Wed, 5 Jul 2006 16:02:56 +0000 (UTC) (envelope-from jfvogel@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 236F843D90 for ; Wed, 5 Jul 2006 16:02:05 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id b36so2102312pyb for ; Wed, 05 Jul 2006 09:02:05 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GXnt+xJdopGwCJCQ5FdgTK7Miz22oj0r/ecz0ocpCqqp9RHdJEsJ4/m1Fn2n/WhR5i4Pw1jpUb2y9DCAHcW+pBz23vFsgI9PyMi+OmXaEBH+PBKwR/7CkRdZIes+ZRA2VLnggs3AqgaPS8jCofaWC6JV2ahoN9ecoppfJJQAPY8= Received: by 10.35.9.15 with SMTP id m15mr3458054pyi; Wed, 05 Jul 2006 09:00:19 -0700 (PDT) Received: by 10.35.105.15 with HTTP; Wed, 5 Jul 2006 09:00:19 -0700 (PDT) Message-ID: <2a41acea0607050900u10efb80drf6dc28f906ad56c5@mail.gmail.com> Date: Wed, 5 Jul 2006 09:00:19 -0700 From: "Jack Vogel" To: "Martin Nilsson" In-Reply-To: <2a41acea0607050854x7825b204k6f199dd2e9584208@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44AAA5B5.2020407@gneto.com> <2a41acea0607050854x7825b204k6f199dd2e9584208@mail.gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: New em PCI-id X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 16:02:56 -0000 On 7/5/06, Jack Vogel wrote: > On 7/4/06, Martin Nilsson wrote: > > I got the new version of intels quad port PCI-X Gbit adapter. > > It is not detected by 6-STABLE: > > > > FreeBSD 6.1-STABLE #0: Fri Jun 30 18:45:32 CEST 2006 > > > > pcib3: at device 1.0 on pci2 > > pci3: on pcib3 > > pci3: at device 4.0 (no driver attached) > > pci3: at device 4.1 (no driver attached) > > pci3: at device 6.0 (no driver attached) > > pci3: at device 6.1 (no driver attached) > > > > Intel(r) PRO/1000 GT Quad Port Server Adapter > > http://www.intel.com/network/connectivity/products/pro1000gt_quadport_server_adapter.htm > > The chip is called NH82546GB (This is the new RoHS compatible model) > > > > pciconf -lv give four of these: > > > > none2@pci3:4:0: class=0x020000 card=0x11998086 chip=0x10b58086 rev=0x03 > > hdr=0x00 > > vendor = 'Intel Corporation' > > class = network > > subclass = ethernet > > > > Can someone familiar with the em driver please add the new id. > > Yes, there are a number of newer cards not yet in Stable. > Once I have the ability to commit changes this should be > remedied, but meanwhile you can use MY driver which is > on the Intel website. Go to downloads area, network connectivity, > then select server adapters, at that point almost any adapter > will do, you will then get an OS select menu, find FreeBSD, > and then you will see version 6.0.5, download that. > > That driver will work with either 6.0 or 6.1, and it supports > all our PCI Express adapters including the new ones . > > I hope to integrate the changes in our driver into STABLE > before 6.2. > > Jack > DUH, or just use the URL you supplied, select software and you will findd the same driver :) From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 16:18:10 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 089FD16A4DF; Wed, 5 Jul 2006 16:18:10 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D95E43D49; Wed, 5 Jul 2006 16:18:09 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 3D46446CCF; Wed, 5 Jul 2006 12:18:07 -0400 (EDT) Date: Wed, 5 Jul 2006 17:18:07 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: John Baldwin In-Reply-To: <200607051142.28352.jhb@freebsd.org> Message-ID: <20060705171517.H18236@fledge.watson.org> References: <200607010009.09231@aldan> <20060701115508.GC8447@turion.vk2pj.dyndns.org> <200607011508.27920@aldan> <200607051142.28352.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Peter Jeremy , freebsd-current@freebsd.org, Mikhail Teterin Subject: Re: weird limitation on the system's binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 16:18:10 -0000 On Wed, 5 Jul 2006, John Baldwin wrote: >>> libbdf.a is built by /usr/src/gnu/usr.bin/binutils/libbfd/Makefile. That >>> should be a fairly simple change to arrange for it to build and install >>> the .so as well. >> >> Installing both libbfd-s certainly would be a good start... As things >> stand, every port needing it -- including various different compilers -- >> builds it own version. This is, largely, explained by the GNU's stupidity >> of bundling a different version with each tool (gdb, compiler), but the >> bundled bfds are not THAT incompatible, and the system-installed version >> can include the compatible superset... > > Actually, in the past this has proven quite difficult, hence the current > arrangment of various tools linking statically against their own private > copy. My recollection is that we got to where we are today precisely because the various GNU tools (gdb, gcc, etc) relied on versions of bfd "as cut" at the point where the tool revisions were released. This meant that they could not share bfd versions between tools, since tools were often released at different dates, and the versions of bfd with different tools were incompatible. The conclusion was that by statically linking the specific compatible versions into the binaries, and by not shipping a specific bfd as part of the base system, we avoided numerous compatibility issues, as well as avoided committing consumers of the system to a particular bfd revision that might be incompatible with what they want to run in the way of their own cross tools, etc. Perhaps the world has changed since that time, but those sound like pretty good reasons to me. So these are my recollections, but since I'm not an expert in our toolchain bits, I could be off in the woods somewhere. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 16:46:18 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BBF816A4E5 for ; Wed, 5 Jul 2006 16:46:18 +0000 (UTC) (envelope-from Achim_Leubner@adaptec.com) Received: from mail-gw3.adaptec.com (mail-gw3.adaptec.com [216.52.22.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF76E43D45 for ; Wed, 5 Jul 2006 16:46:17 +0000 (GMT) (envelope-from Achim_Leubner@adaptec.com) Received: from mtce2k01.adaptec.com (mtce2k01.adaptec.com [162.62.174.18]) by mail-gw3.adaptec.com (Spam Firewall) with ESMTP id AD52F6E52C for ; Wed, 5 Jul 2006 09:46:16 -0700 (PDT) content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Date: Wed, 5 Jul 2006 18:46:15 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Driver compilation for amd64 Thread-Index: AcagUof/KgpVwoOdQEOsj4zfdjYKjg== From: "Leubner, Achim" To: X-Virus-Scanned: by Barracuda Spam Firewall at adaptec.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Driver compilation for amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 16:46:18 -0000 Is it possible to cross-compile a driver on an i386 platform for amd64, and if possible, how should I do that?=20 Any help is greatly appreciated. =20 Regards, Achim Leubner =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Achim Leubner Software Engineer / RAID drivers ICP vortex GmbH / Adaptec Inc. Phone: +49-351-8718291 =20 =20 From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 16:50:56 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EC0A16A4E2 for ; Wed, 5 Jul 2006 16:50:56 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99C1F43D58 for ; Wed, 5 Jul 2006 16:50:53 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k65GobUX013965; Wed, 5 Jul 2006 10:50:43 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44ABEDD5.80701@samsco.org> Date: Wed, 05 Jul 2006 10:50:29 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Leubner, Achim" References: In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: Driver compilation for amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 16:50:56 -0000 Leubner, Achim wrote: > Is it possible to cross-compile a driver on an i386 platform for amd64, > and if possible, how should I do that? > > Any help is greatly appreciated. > > > > Regards, > > Achim Leubner > > > Are you doing this for development or for binary packaging? It's possible to create a cross-built development environment, but doing a cross build of just a kernel module is tricky. Scott From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 18:19:10 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21DE416A4E0 for ; Wed, 5 Jul 2006 18:19:10 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 320BA43D55 for ; Wed, 5 Jul 2006 18:19:01 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FyBxQ-00023h-W8 for freebsd-current@freebsd.org; Wed, 05 Jul 2006 20:18:41 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Jul 2006 20:18:40 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Jul 2006 20:18:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Wed, 05 Jul 2006 20:18:02 +0200 Lines: 10 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050921) X-Accept-Language: en-us, en In-Reply-To: Sender: news Subject: Re: Driver compilation for amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 18:19:10 -0000 Leubner, Achim wrote: > Is it possible to cross-compile a driver on an i386 platform for amd64, > and if possible, how should I do that? > > Any help is greatly appreciated. It's not exactly an answer to your questions, but you could set up a virtual machine with (for example) qemu, which supports emulating AMD64 machine on an i386. FreeBSD-AMD64 version could be installed on it, and you could compile whatever you want. From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 18:57:00 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BE9416A4E5 for ; Wed, 5 Jul 2006 18:57:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5392A43D73 for ; Wed, 5 Jul 2006 18:56:58 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k65Iup1u031530 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jul 2006 21:56:51 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k65Iup6v071393; Wed, 5 Jul 2006 21:56:51 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k65IuoAM071392; Wed, 5 Jul 2006 21:56:50 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 5 Jul 2006 21:56:50 +0300 From: Kostik Belousov To: Ivan Voras Message-ID: <20060705185650.GS37822@deviant.kiev.zoral.com.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="aNvCJ41Feu8IgPyB" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-current@freebsd.org Subject: Re: Driver compilation for amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 18:57:00 -0000 --aNvCJ41Feu8IgPyB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 05, 2006 at 08:18:02PM +0200, Ivan Voras wrote: > Leubner, Achim wrote: > >Is it possible to cross-compile a driver on an i386 platform for amd64, > >and if possible, how should I do that?=20 > > > >Any help is greatly appreciated. >=20 > It's not exactly an answer to your questions, but you could set up a=20 > virtual machine with (for example) qemu, which supports emulating AMD64= =20 > machine on an i386. FreeBSD-AMD64 version could be installed on it, and= =20 > you could compile whatever you want. Freebsd amd64 definitely does not work inside qemu, because acpi required for that architecture, but is not provided by qemu-system-x86_64. --aNvCJ41Feu8IgPyB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFErAtyC3+MBN1Mb4gRAlreAKCeUA7sMD7LUgUlVg0LgO0YY77OMQCfYGII WLX6oizQKif6KJKpoNCw+9w= =+1JA -----END PGP SIGNATURE----- --aNvCJ41Feu8IgPyB-- From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 19:06:55 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60F6716A4DF for ; Wed, 5 Jul 2006 19:06:55 +0000 (UTC) (envelope-from joseph.koshy@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAE9B43D66 for ; Wed, 5 Jul 2006 19:06:51 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by ug-out-1314.google.com with SMTP id s2so308570uge for ; Wed, 05 Jul 2006 12:06:50 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=A+2m+D7sfNRwiOrLPXi+dJbUY2v4Q1pPicH1kYtb1UZblZerGdKv4BrjuHJxV+o7+Hhdsln4tpZSyEz45IxWlNvLUVhantbtsgcMiqDnrP6VIueIq1ZljiDJqQXAJx6ABSPjx7nwmpsFo89z1TqSDVGoWcMGe2+HTtDxMPhNrHo= Received: by 10.78.170.17 with SMTP id s17mr2463879hue; Wed, 05 Jul 2006 12:06:50 -0700 (PDT) Received: by 10.78.50.15 with HTTP; Wed, 5 Jul 2006 12:06:50 -0700 (PDT) Message-ID: <84dead720607051206r384bef5gdb389ceff653af3a@mail.gmail.com> Date: Thu, 6 Jul 2006 00:36:50 +0530 From: "Joseph Koshy" To: "Leubner, Achim" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-current@freebsd.org Subject: Re: Driver compilation for amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 19:06:55 -0000 > Is it possible to cross-compile a driver on an i386 platform > for amd64, and if possible, how should I do that? You can cross-compile an entire kernel by setting the TARGET_ARCH variable appropriately. See also the description in build(7) of the TARGET_ARCH variable and the 'buildenv', 'toolchain' and 'kernel-toolchain' targets. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 19:25:51 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28F9E16A4E7 for ; Wed, 5 Jul 2006 19:25:51 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EFAC43D5D for ; Wed, 5 Jul 2006 19:25:47 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FyD0B-0004i9-3f for freebsd-current@freebsd.org; Wed, 05 Jul 2006 21:25:35 +0200 Received: from sdgate2.cvjetno.sczg.hr ([193.198.8.211]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Jul 2006 21:25:35 +0200 Received: from ivoras by sdgate2.cvjetno.sczg.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Jul 2006 21:25:35 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Wed, 05 Jul 2006 21:25:15 +0200 Lines: 10 Message-ID: References: <20060705185650.GS37822@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: sdgate2.cvjetno.sczg.hr User-Agent: Thunderbird 1.5.0.4 (X11/20060615) In-Reply-To: <20060705185650.GS37822@deviant.kiev.zoral.com.ua> Sender: news Subject: Re: Driver compilation for amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 19:25:51 -0000 Kostik Belousov wrote: > Freebsd amd64 definitely does not work inside qemu, because acpi required > for that architecture, but is not provided by qemu-system-x86_64. Don't know about that - I've just booted it to the point of sysinstall and quit :) Since it got to sysinstall, I guess it would have kept going. IIRC there was even the standard "former beastie" menu for booting with ACPI enabled/disabled. From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 19:38:28 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C735216A4E6 for ; Wed, 5 Jul 2006 19:38:28 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA36C43D73 for ; Wed, 5 Jul 2006 19:38:17 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k65JcBCv032726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jul 2006 22:38:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k65JcAht072341; Wed, 5 Jul 2006 22:38:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k65JcASK072340; Wed, 5 Jul 2006 22:38:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 5 Jul 2006 22:38:10 +0300 From: Kostik Belousov To: Ivan Voras Message-ID: <20060705193810.GT37822@deviant.kiev.zoral.com.ua> References: <20060705185650.GS37822@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="562f9N4fbIs+fPrJ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-current@freebsd.org Subject: Re: Driver compilation for amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 19:38:28 -0000 --562f9N4fbIs+fPrJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 05, 2006 at 09:25:15PM +0200, Ivan Voras wrote: > Kostik Belousov wrote: >=20 > > Freebsd amd64 definitely does not work inside qemu, because acpi requir= ed > > for that architecture, but is not provided by qemu-system-x86_64. >=20 > Don't know about that - I've just booted it to the point of sysinstall > and quit :) Since it got to sysinstall, I guess it would have kept going. >=20 > IIRC there was even the standard "former beastie" menu for booting with > ACPI enabled/disabled. Are you sure that you booted amd64 system ? Looks like it was i386 actually. I got the weeping from ata driver about unability to allocate interrupts. Moreover, colleague of mine once got to compile amd64 kernel without acpi. Booting it on the Xeon machine leads to the same errors and absence of the disks. --562f9N4fbIs+fPrJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFErBUhC3+MBN1Mb4gRAvOgAKDGpDvd5Qp58eXRGneW/CCgQPfrVwCg4/cw WnAQxW5iugLXMuyg+9V9aB8= =SRFI -----END PGP SIGNATURE----- --562f9N4fbIs+fPrJ-- From owner-freebsd-current@FreeBSD.ORG Wed Jul 5 20:04:30 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 613EA16A4DE for ; Wed, 5 Jul 2006 20:04:30 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB76943D45 for ; Wed, 5 Jul 2006 20:04:29 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FyDbi-00024r-M7 for freebsd-current@freebsd.org; Wed, 05 Jul 2006 22:04:22 +0200 Received: from sdgate2.cvjetno.sczg.hr ([193.198.8.211]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Jul 2006 22:04:22 +0200 Received: from ivoras by sdgate2.cvjetno.sczg.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Jul 2006 22:04:22 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Wed, 05 Jul 2006 22:04:03 +0200 Lines: 23 Message-ID: References: <20060705185650.GS37822@deviant.kiev.zoral.com.ua> <20060705193810.GT37822@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: sdgate2.cvjetno.sczg.hr User-Agent: Thunderbird 1.5.0.4 (X11/20060615) In-Reply-To: <20060705193810.GT37822@deviant.kiev.zoral.com.ua> Sender: news Subject: Re: Driver compilation for amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 20:04:30 -0000 Kostik Belousov wrote: >> Don't know about that - I've just booted it to the point of sysinstall >> and quit :) Since it got to sysinstall, I guess it would have kept going. > Are you sure that you booted amd64 system ? Looks like it was i386 > actually. No, I looked for 64-bit addresses in dmesg and found them, specifically because I know WinXP amd64 edition needs ACPI and refuses to boot on qemu. The "former beastie" boot menu lists boot without ACPI (default) and with ACPI (choice #2). This is from 6.1-RELEASE-amd64-bootonly.iso. > I got the weeping from ata driver about unability to allocate interrupts. I've just repeated the experiment - I can boot FreeBSD AMD64 version in qemu, it also displays messages like 'acpi0_check: pci0 attached' and 'acpi0_check: ata0 attached' just before sysinstall starts. It can see and use disks (virtual disks, files in the host file system) without problems. Maybe something got fixed in qemu? QEMU PC emulator version 0.8.1, Copyright (c) 2003-2005 Fabrice Bellard From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 03:23:16 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 017E416A4DF for ; Thu, 6 Jul 2006 03:23:16 +0000 (UTC) (envelope-from netsick@iinet.net.au) Received: from customer-domains.icp-qv1-irony6.iinet.net.au (customer-domains.icp-qv1-irony6.iinet.net.au [203.59.1.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FB1E43D49 for ; Thu, 6 Jul 2006 03:23:14 +0000 (GMT) (envelope-from netsick@iinet.net.au) Received: from per-qv1-webmail-04.iinet.net.au (HELO mail.iinet.net.au) ([203.59.3.52]) by customer-domains.icp-qv1-irony6.iinet.net.au with SMTP; 06 Jul 2006 11:23:11 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.06,211,1149436800"; d="scan'208"; a="366232583:sNHT245906116" Received: (qmail 19305 invoked by uid 33); 6 Jul 2006 03:23:10 -0000 Received: from mail-placeholder.iinet.net.au (mail-placeholder.iinet.net.au [203.59.1.180]) by mail.iinet.net.au (IMP) with HTTP for ; Thu, 6 Jul 2006 11:23:10 +0800 Message-ID: <1152156190.44ac821e66d24@mail.iinet.net.au> Date: Thu, 6 Jul 2006 11:23:10 +0800 From: netsick@iinet.net.au To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 X-Originating-IP: 203.59.1.180 Cc: eric@anholt.net Subject: OOOPs sys/pci/agp_i810.c with wrong chiptypes. Patch attached. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 03:23:16 -0000 > It looks like in the reorg of sys/pci/agp_i810.c a couple chips got the > wrong chiptype in the big table (including mine :-(). Those chips (oe > at least mine) did not properly initialize because of it. I've attached > a patch that fixes this for me - just swapping the chiptypes. > > The patch is relative to /sys. >> >>Sorry about that. Committed, plus a little fix for detecting if the >>device is disabled as well. Thanks! Hi I see you may have added a little more code to support i945 ? I rebuilt my sources to test and still no agp. Maybe one day I'll get my agpgart.. *sigh* Kris From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 06:09:23 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 029D616A4DD for ; Thu, 6 Jul 2006 06:09:23 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65CE443D4C for ; Thu, 6 Jul 2006 06:09:21 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FyN32-0005K4-Kp for freebsd-current@freebsd.org; Thu, 06 Jul 2006 08:09:12 +0200 Received: from www.creo.hu ([217.113.62.14]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Jul 2006 08:09:12 +0200 Received: from csaba-ml by www.creo.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Jul 2006 08:09:12 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Csaba Henk Date: Thu, 6 Jul 2006 06:09:04 +0000 (UTC) Lines: 9 Message-ID: References: <20060705114853.GB73705@cdnetworks.co.kr> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: www.creo.hu User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 06:09:23 -0000 On 2006-07-05, Pyun YongHyeon wrote: > This is a ported driver from NetBSD stge(4). It supports the Oh yeah, I wanted *very* much to see this happen! Thank you very much. So far it works well on my FreeBSD 6.0 box (after I added the VLAN_INPUT_TAG_NEW macro which it was lacking). Regards, Csaba From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 06:27:09 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2E7416A4E6 for ; Thu, 6 Jul 2006 06:27:09 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA3B143D68 for ; Thu, 6 Jul 2006 06:26:59 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id r28so1034487nza for ; Wed, 05 Jul 2006 23:26:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=WpV+a9o55aIRu1ivJoOyrAtJ3jZpiAKdmsXAQENJjtTAqkURDMeBVDdroTEeqwL3oO0hcqqZx03l05UDs27ivO9nAHhLQoPF65caQyGWqcDwQV+l3juiymKy6Wswl0HA/PA1o1QgVq7OkTL+GSwc+v2bImgKbkCt7WwW4gM+4uE= Received: by 10.36.33.3 with SMTP id g3mr360562nzg; Wed, 05 Jul 2006 23:26:59 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 14sm1928518nzp.2006.07.05.23.26.57; Wed, 05 Jul 2006 23:26:58 -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 k666UYEB079375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Jul 2006 15:30:34 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k666UX17079374; Thu, 6 Jul 2006 15:30:33 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 6 Jul 2006 15:30:33 +0900 From: Pyun YongHyeon To: Csaba Henk Message-ID: <20060706063033.GB76865@cdnetworks.co.kr> References: <20060705114853.GB73705@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 06:27:09 -0000 On Thu, Jul 06, 2006 at 06:09:04AM +0000, Csaba Henk wrote: > On 2006-07-05, Pyun YongHyeon wrote: > > This is a ported driver from NetBSD stge(4). It supports the > > Oh yeah, I wanted *very* much to see this happen! Thank you very much. > So far it works well on my FreeBSD 6.0 box (after I added the Great! Thanks for the report. What model/maker you've got(pciconf -lv output)? > VLAN_INPUT_TAG_NEW macro which it was lacking). > Yeah, 6.0R don't have VLAN_INPUT_TAG_NEW macro. -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 06:39:00 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E03F316A4DA for ; Thu, 6 Jul 2006 06:39:00 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8273D43D45 for ; Thu, 6 Jul 2006 06:39:00 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [IPv6:::1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k666aoHK009181; Thu, 6 Jul 2006 00:36:50 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 06 Jul 2006 00:36:55 -0600 (MDT) Message-Id: <20060706.003655.-267227242.imp@bsdimp.com> To: Achim_Leubner@adaptec.com From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Driver compilation for amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 06:39:01 -0000 In message: "Leubner, Achim" writes: : Is it possible to cross-compile a driver on an i386 platform for amd64, : and if possible, how should I do that? : : Any help is greatly appreciated. First, you must setup a cross environment: setenv TARGET amd64 setenv TARGET_ARCH amd64 setenv MAKEOBJDIRPREFIX /somewhere/obj cd /usr/src make kernel-toolchain At this point, you have two choices: (1) use the make buildkernel target and build a kernel + modules. This can be streamlined with options like NO_KERNELCLEAN, etc. We use this at work when we're developing 'base' kernel functionality for the arm port we're undertaking. (2) use the 'make buildenv' functionality. This target puts you in a proper build environment to do things by hand. You need to have done all the steps above, and each time you need to build stuff, you'll have to use the first 4 commands above followed by 'make buildenv'. You can then build your module, or whatever else you want, since cc and friends will generate code for amd64. I use both methods extensively for different types of development. They work great. I have an armenv script: cd $HOME/p4/imp_arm setenv TARGET arm setenv TARGET_ARCH arm setenv MAKEOBJDIRPREFIX $HOME/obj make buildenv which pops me into an environment I can build in. You'll need to customize it for your environment, clearly, but it should give you the main parts you need to do this sort of thing. I usually go the other way: build i386 on my fast amd64 box. Good luck Warner From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 08:54:29 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD73B16A4DD for ; Thu, 6 Jul 2006 08:54:29 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0270443D49 for ; Thu, 6 Jul 2006 08:54:28 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k668s8tT096722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Jul 2006 12:54:09 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k668rw4L096721; Thu, 6 Jul 2006 12:53:58 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 6 Jul 2006 12:53:58 +0400 From: Gleb Smirnoff To: Wesley Morgan Message-ID: <20060706085358.GA96644@FreeBSD.org> References: <20060702115840.L12091@volatile.chemikals.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20060702115840.L12091@volatile.chemikals.org> User-Agent: Mutt/1.5.6i Cc: Michiel Boland , freebsd-current@FreeBSD.org Subject: Re: em0: watchdog timeout -- resetting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 08:54:29 -0000 On Sun, Jul 02, 2006 at 12:01:43PM -0400, Wesley Morgan wrote: W> >Hi. I frequently get W> > W> >em0: watchdog timeout -- resetting W> > W> >messages, followed by loss of network at the most inopportune moments. W> > W> >It appears that it can be triggered by things like typing 'portinstall W> >mozilla' over an SSH connection. But that is just a hunch. W> > W> >Any ideas how to debug this further? W> > W> >Hardware is a dell optiplex GX270. Kernel is -CURRENT from 29 june. W> W> I have the same issue on my laptop. It seems like the problem came into W> being a few months ago, but I've never gone any further than trying to W> revert to a previous version of the driver, which did not help. In rev. 1.107 of if_em.c there was a fix that made this message printed. Before 1.107 the reset was issued, but driver was silent about this. W> For me, the problem is more than just loss of network, but rather every W> application hanging while multiple timeouts occurr. Hmm. May be you are using serial console and system lags when the console messages are printed? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 08:55:29 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A383C16A4E1; Thu, 6 Jul 2006 08:55:29 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C26EC43D49; Thu, 6 Jul 2006 08:55:26 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k668tP4d096783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Jul 2006 12:55:25 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k668tOgK096782; Thu, 6 Jul 2006 12:55:24 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 6 Jul 2006 12:55:24 +0400 From: Gleb Smirnoff To: Poul-Henning Kamp Message-ID: <20060706085524.GB96644@FreeBSD.org> References: <20060629193346.GA2548@dragon.NUXI.org> <3903.1151610672@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <3903.1151610672@critter.freebsd.dk> User-Agent: Mutt/1.5.6i Cc: freebsd-current@FreeBSD.org, obrien@FreeBSD.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 08:55:29 -0000 On Thu, Jun 29, 2006 at 07:51:12PM +0000, Poul-Henning Kamp wrote: P> >I'm still often getting calcru output. This is with P> >FreeBSD anh-thu.NUXI.org 7.0-CURRENT #44: Tue Jun 27 09:30:45 PDT 2006 amd64 P> >I'm using the default time source (ACPI). What's the latest theories of P> >the cause of this? P> P> Does this machine change the cpu clock rate ? btw, I still experience lots of these messages every time my APM notebook is put to sleep. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 10:54:54 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9260216A4E0 for ; Thu, 6 Jul 2006 10:54:54 +0000 (UTC) (envelope-from list@billxu.com) Received: from sina3-197.sina.net (sina3-197.sina.net [202.108.3.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id F332443D49 for ; Thu, 6 Jul 2006 10:54:52 +0000 (GMT) (envelope-from list@billxu.com) Received: (qmail 90716 invoked from network); 6 Jul 2006 10:54:53 -0000 Received: from unknown (HELO ?10.217.12.123?) (10.217.12.123) by 10.54.2.88 with SMTP; 6 Jul 2006 10:54:53 -0000 From: Bill Xu To: Maho Nakata In-Reply-To: <200607060038.k660cmB0087491@repoman.freebsd.org> References: <200607060038.k660cmB0087491@repoman.freebsd.org> Content-Type: text/plain; charset=UTF-8 Organization: BILLXU.COM Date: Thu, 06 Jul 2006 18:54:40 +0800 Message-Id: <1152183280.21776.13.camel@zeuux.zeuux.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-openoffice@freebsd.org, freebsd-current@freebsd.org Subject: Re: cvs commit: ports/editors/openoffice.org-2.0/files patch-i65512 ports/editors/openoffice.org-2.0-devel/files patch-i65512 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 10:54:54 -0000 Compiling editors/openoffice-2.0 still failed in the FreeBSD 7.0-CURRENT box.The following is the output, lo/MDatabaseMetaData.o ../../../unxfbsdi.pro/slo/MConnection.o ../../../unxfbsdi.pro/slo/MNSInit.o ../../../unxfbsdi.pro/slo/MQu eryHelper.o ../../../unxfbsdi.pro/slo/MDatabaseMetaDataHelper.o ../../../unxfbsdi.pro/slo/MQuery.o ../../../unxfbsdi.pro/slo/MTy peConverter.o ../../../unxfbsdi.pro/slo/MNameMapper.o ../../../unxfbsdi.pro/slo/MNSMozabProxy.o ../../../unxfbsdi.pro/slo/MNSTer minateListener.o ../../../unxfbsdi.pro/slo/MMozillaBootstrap.o ../../../unxfbsdi.pro/slo/MNSFolders.o ../../../unxfbsdi.pro/slo/ MNSProfileDiscover.o ../../../unxfbsdi.pro/slo/MNSProfileManager.o ../../../unxfbsdi.pro/slo/MNSINIParser.o ../../../unxfbsdi.pr o/slo/MNSRunnable.o ../../../unxfbsdi.pro/slo/MNSProfile.o ../../../unxfbsdi.pro/slo/MNSProfileDirServiceProvider.o ../../../unx fbsdi.pro/slo/mozabdrv2_version.o ../../../unxfbsdi.pro/slo/mozabdrv2_description.o -o ../../../unxfbsdi.pro/lib/libmozabdrv2.so -luno_cppu -luno_cppuhelpergcc3 -lvos3gcc3 -luno_sal -ldbtools680fi -lcomphelp4gcc3 -L/usr/ports/editors/openoffice.org-2.0/wor k/OOC680_m7/solver/680/unxfbsdi.pro/lib -lembed_base_s -lnspr4 -lmozreg_s -lxpcom -pthread -lm -Wl,-Bdynamic -lstlport_gcc rm -f ../../../unxfbsdi.pro/lib/check_libmozabdrv2.so mv ../../../unxfbsdi.pro/lib/libmozabdrv2.so ../../../unxfbsdi.pro/lib/check_libmozabdrv2.so /usr/ports/editors/openoffice.org-2.0/work/OOC680_m7/solenv/bin/checkdll.sh -L../../../unxfbsdi.pro/lib -L../lib -L/usr/ports/ed itors/openoffice.org-2.0/work/OOC680_m7/solenv/unxfbsdi/lib -L/usr/ports/editors/openoffice.org-2.0/work/OOC680_m7/solver/680/un xfbsdi.pro/lib -L/usr/ports/editors/openoffice.org-2.0/work/OOC680_m7/solenv/unxfbsdi/lib -L/usr/local/diablo-jdk1.5.0/lib -L/us r/local/diablo-jdk1.5.0/jre/lib/i386 -L/usr/local/diablo-jdk1.5.0/jre/lib/i386/client -L/usr/local/diablo-jdk1.5.0/jre/lib/i386/ native_threads -L/usr/X11R6/lib ../../../unxfbsdi.pro/lib/check_libmozabdrv2.so Checking DLL ../../../unxfbsdi.pro/lib/check_libmozabdrv2.so ...Fatal error 'Spinlock called when not threaded.' at line 91 in f ile /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 2) Abort trap (core dumped) dmake: Error code 1, while making '../../../unxfbsdi.pro/lib/libmozabdrv2.so' '---* tg_merge.mk *---' ERROR: Error 65280 occurred while making /usr/ports/editors/openoffice.org-2.0/work/OOC680_m7/connectivity/source/drivers/mozab dmake: Error code 1, while making 'build_instsetoo_native' '---* *---' *** Error code 255 Stop in /usr/ports/editors/openoffice.org-2.0. :( Bill 在 2006-07-06四的 00:38 +0000，Maho Nakata写道： > maho 2006-07-06 00:38:48 UTC > > FreeBSD ports repository > > Modified files: > editors/openoffice.org-2.0/files patch-i65512 > editors/openoffice.org-2.0-devel/files patch-i65512 > Log: > Build fix for 7-current. > > NAKAJI-san kindly signed to JCA for upstream, > so we accept the patch. > Please refer policy section > of http://porting.openoffice.org/freebsd > . > > PR: 99284 > Submitted by: NAKAJI Hiroyuki > > Revision Changes Path > 1.2 +18 -0 ports/editors/openoffice.org-2.0-devel/files/patch-i65512 > 1.3 +18 -0 ports/editors/openoffice.org-2.0/files/patch-i65512 > _______________________________________________ > cvs-all@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/cvs-all > To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 10:55:59 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86BCC16A4DA for ; Thu, 6 Jul 2006 10:55:59 +0000 (UTC) (envelope-from Achim_Leubner@adaptec.com) Received: from mail-gw3.adaptec.com (mail-gw3.adaptec.com [216.52.22.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 471AA43D53 for ; Thu, 6 Jul 2006 10:55:59 +0000 (GMT) (envelope-from Achim_Leubner@adaptec.com) Received: from mtce2k01.adaptec.com (mtce2k01.adaptec.com [162.62.174.18]) by mail-gw3.adaptec.com (Spam Firewall) with ESMTP id 853D8E9647; Thu, 6 Jul 2006 03:55:58 -0700 (PDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Date: Thu, 6 Jul 2006 12:55:57 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Driver compilation for amd64 Thread-Index: AcagxuHrq78vE530SEW42pCxrrGuiQAI61xA From: "Leubner, Achim" To: "M. Warner Losh" X-Virus-Scanned: by Barracuda Spam Firewall at adaptec.com Cc: freebsd-current@freebsd.org Subject: RE: Driver compilation for amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 10:55:59 -0000 Thanks for your description, it works great! Thanks, Achim -----Original Message----- From: M. Warner Losh [mailto:imp@bsdimp.com]=20 Sent: Donnerstag, 6. Juli 2006 08:37 To: Leubner, Achim Cc: freebsd-current@freebsd.org Subject: Re: Driver compilation for amd64 In message: "Leubner, Achim" writes: : Is it possible to cross-compile a driver on an i386 platform for amd64, : and if possible, how should I do that?=20 :=20 : Any help is greatly appreciated. First, you must setup a cross environment: setenv TARGET amd64 setenv TARGET_ARCH amd64 setenv MAKEOBJDIRPREFIX /somewhere/obj cd /usr/src make kernel-toolchain At this point, you have two choices: (1) use the make buildkernel target and build a kernel + modules. This can be streamlined with options like NO_KERNELCLEAN, etc. We use this at work when we're developing 'base' kernel functionality for the arm port we're undertaking. (2) use the 'make buildenv' functionality. This target puts you in a proper build environment to do things by hand. You need to have done all the steps above, and each time you need to build stuff, you'll have to use the first 4 commands above followed by 'make buildenv'. You can then build your module, or whatever else you want, since cc and friends will generate code for amd64. I use both methods extensively for different types of development. They work great. I have an armenv script: cd $HOME/p4/imp_arm setenv TARGET arm setenv TARGET_ARCH arm setenv MAKEOBJDIRPREFIX $HOME/obj make buildenv which pops me into an environment I can build in. You'll need to customize it for your environment, clearly, but it should give you the main parts you need to do this sort of thing. I usually go the other way: build i386 on my fast amd64 box. Good luck Warner From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 11:11:59 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EF8716A4DD; Thu, 6 Jul 2006 11:11:59 +0000 (UTC) (envelope-from chat95@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B71543D46; Thu, 6 Jul 2006 11:11:59 +0000 (GMT) (envelope-from chat95@mac.com) Received: from mac.com (smtpin04-en2 [10.13.10.149]) by smtpout.mac.com (Xserve/8.12.11/smtpout14/MantshX 4.0) with ESMTP id k66BBseP000995; Thu, 6 Jul 2006 04:11:54 -0700 (PDT) Received: from localhost ([133.11.172.102]) (authenticated bits=0) by mac.com (Xserve/smtpin04/MantshX 4.0) with ESMTP id k66BBmOJ024140; Thu, 6 Jul 2006 04:11:53 -0700 (PDT) Date: Thu, 06 Jul 2006 20:11:43 +0900 (JST) Message-Id: <20060706.201143.74704861.chat95@mac.com> To: list@billxu.com From: NAKATA Maho In-Reply-To: <1152183280.21776.13.camel@zeuux.zeuux.com> References: <200607060038.k660cmB0087491@repoman.freebsd.org> <1152183280.21776.13.camel@zeuux.zeuux.com> Organization: private X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: maho@freebsd.org, freebsd-openoffice@freebsd.org, freebsd-current@freebsd.org Subject: Re: cvs commit: ports/editors/openoffice.org-2.0/files patch-i65512 ports/editors/openoffice.org-2.0-devel/files patch-i65512 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 11:11:59 -0000 In Message-ID: <1152183280.21776.13.camel@zeuux.zeuux.com> Bill Xu wrote: > Compiling editors/openoffice-2.0 still failed in the FreeBSD 7.0-CURRENT > ile /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 2) as NAKAJI told at the PR, http://www.freebsd.org/cgi/query-pr.cgi?pr=99284 > I had to remove /usr/lib/libc_r.* which causes c++'s -pedantic bug. > After removing them, "portupgrade ja-openoffice.org" was successful with > this patch (I had already sent). -- NAKATA, Maho (maho@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 11:53:40 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72ED416A4DD for ; Thu, 6 Jul 2006 11:53:40 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0003043D49 for ; Thu, 6 Jul 2006 11:53:39 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FySQ5-0000Xh-2i for freebsd-current@freebsd.org; Thu, 06 Jul 2006 13:53:21 +0200 Received: from www.creo.hu ([217.113.62.14]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Jul 2006 13:53:21 +0200 Received: from csaba-ml by www.creo.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Jul 2006 13:53:21 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Csaba Henk Date: Thu, 6 Jul 2006 11:52:39 +0000 (UTC) Lines: 19 Message-ID: References: <20060705114853.GB73705@cdnetworks.co.kr> <20060706063033.GB76865@cdnetworks.co.kr> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: www.creo.hu User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 11:53:40 -0000 On 2006-07-06, Pyun YongHyeon wrote: > What model/maker you've got(pciconf -lv output)? stge0@pci0:11:0: class=0x020000 card=0x545013f0 chip=0x102113f0 rev=0x07 hdr=0x00 vendor = 'Sundance Technology Inc' class = network subclass = ethernet And this is what shows up in dmesg: Jul 6 07:50:23 leavemealone kernel: stge0: port 0xe000-0xe0ff mem 0xef000000-0xef0001ff irq 11 at device 11.0 on pci0 Jul 6 07:50:23 leavemealone kernel: stge0: phy read fail Jul 6 07:50:23 leavemealone last message repeated 31 times Jul 6 07:50:23 leavemealone kernel: miibus2: on stge0 Jul 6 07:50:23 leavemealone kernel: e1000phy0: on miibus2 Jul 6 07:50:23 leavemealone kernel: e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto Regards, Csaba From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 12:39:21 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC30916A4DA for ; Thu, 6 Jul 2006 12:39:21 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18C0C43D49 for ; Thu, 6 Jul 2006 12:39:21 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id r28so1075541nza for ; Thu, 06 Jul 2006 05:39:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=HXDtGlL+1E9GJQemDSMeWYM1mHavdJ/JeFw7HqGpb8jd8jEcXS3qCXnOsDc9cMMbieqDSdjPcXq0cNexd6AToazab5NlyUmGM7Lyzj6P33QyEgmz+8flffZ6WPDzZxXYoWuLuNcN4N9jpYcg35omztxcRO8d0luCcJ6Ky1R22As= Received: by 10.36.118.8 with SMTP id q8mr797419nzc; Thu, 06 Jul 2006 05:39:20 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id c12sm999711nzc.2006.07.06.05.39.18; Thu, 06 Jul 2006 05:39:20 -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 k66CgxSd080660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Jul 2006 21:42:59 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k66Cgwqj080659; Thu, 6 Jul 2006 21:42:58 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 6 Jul 2006 21:42:58 +0900 From: Pyun YongHyeon To: Csaba Henk Message-ID: <20060706124258.GE76865@cdnetworks.co.kr> References: <20060705114853.GB73705@cdnetworks.co.kr> <20060706063033.GB76865@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 12:39:21 -0000 On Thu, Jul 06, 2006 at 11:52:39AM +0000, Csaba Henk wrote: > On 2006-07-06, Pyun YongHyeon wrote: > > What model/maker you've got(pciconf -lv output)? > > stge0@pci0:11:0: class=0x020000 card=0x545013f0 chip=0x102113f0 rev=0x07 hdr=0x00 > vendor = 'Sundance Technology Inc' > class = network > subclass = ethernet > > And this is what shows up in dmesg: > > Jul 6 07:50:23 leavemealone kernel: stge0: port 0xe000-0xe0ff mem 0xef000000-0xef0001ff irq 11 at device 11.0 on pci0 > Jul 6 07:50:23 leavemealone kernel: stge0: phy read fail > Jul 6 07:50:23 leavemealone last message repeated 31 times > Jul 6 07:50:23 leavemealone kernel: miibus2: on stge0 > Jul 6 07:50:23 leavemealone kernel: e1000phy0: on miibus2 > Jul 6 07:50:23 leavemealone kernel: e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto > Since your NIC has a Marvell PHY and shows many "phy read fail" message I have to investigate the root cause. I don't have TC9021 NIC with Marvell PHY. So I can't sure I can fix it. Does ifconfig(8) reports correct link speed/status? Does "phy read fail" message shows only at device attach time? -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 13:24:39 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91B3616A540 for ; Thu, 6 Jul 2006 13:24:39 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18D4243D55 for ; Thu, 6 Jul 2006 13:24:38 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FyTqB-0000Si-4b for freebsd-current@freebsd.org; Thu, 06 Jul 2006 15:24:23 +0200 Received: from www.creo.hu ([217.113.62.14]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Jul 2006 15:24:23 +0200 Received: from csaba-ml by www.creo.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Jul 2006 15:24:23 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Csaba Henk Date: Thu, 6 Jul 2006 13:23:58 +0000 (UTC) Lines: 16 Message-ID: References: <20060705114853.GB73705@cdnetworks.co.kr> <20060706063033.GB76865@cdnetworks.co.kr> <20060706124258.GE76865@cdnetworks.co.kr> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: www.creo.hu User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 13:24:39 -0000 On 2006-07-06, Pyun YongHyeon wrote: > Since your NIC has a Marvell PHY and shows many "phy read fail" > message I have to investigate the root cause. I don't have > TC9021 NIC with Marvell PHY. So I can't sure I can fix it. > > Does ifconfig(8) reports correct link speed/status? Yes. > Does "phy read fail" message shows only at device attach time? Yes. After it has came up I didn't experience problems, and there were no junk or weird kernel messages. Regards, Csaba From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 13:41:56 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D56BB16A4DD; Thu, 6 Jul 2006 13:41:56 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from ms-smtp-04.southeast.rr.com (ms-smtp-04.southeast.rr.com [24.25.9.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BEFD43D70; Thu, 6 Jul 2006 13:41:53 +0000 (GMT) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (cpe-024-211-118-154.sc.res.rr.com [24.211.118.154]) by ms-smtp-04.southeast.rr.com (8.13.6/8.13.6) with ESMTP id k66DfgmJ015760; Thu, 6 Jul 2006 09:41:43 -0400 (EDT) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.13.6/8.13.6) with ESMTP id k66DfgpC004532; Thu, 6 Jul 2006 09:41:42 -0400 (EDT) (envelope-from morganw@chemikals.org) Date: Thu, 6 Jul 2006 09:41:42 -0400 (EDT) From: Wesley Morgan To: Gleb Smirnoff In-Reply-To: <20060706085358.GA96644@FreeBSD.org> Message-ID: <20060706091811.T977@volatile.chemikals.org> References: <20060702115840.L12091@volatile.chemikals.org> <20060706085358.GA96644@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Michiel Boland , freebsd-current@FreeBSD.org Subject: Re: em0: watchdog timeout -- resetting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 13:41:56 -0000 On Thu, 6 Jul 2006, Gleb Smirnoff wrote: > On Sun, Jul 02, 2006 at 12:01:43PM -0400, Wesley Morgan wrote: > W> >Hi. I frequently get > W> > > W> >em0: watchdog timeout -- resetting > W> > > W> >messages, followed by loss of network at the most inopportune moments. > W> > > W> >It appears that it can be triggered by things like typing 'portinstall > W> >mozilla' over an SSH connection. But that is just a hunch. > W> > > W> >Any ideas how to debug this further? > W> > > W> >Hardware is a dell optiplex GX270. Kernel is -CURRENT from 29 june. > W> > W> I have the same issue on my laptop. It seems like the problem came into > W> being a few months ago, but I've never gone any further than trying to > W> revert to a previous version of the driver, which did not help. > > In rev. 1.107 of if_em.c there was a fix that made this message > printed. Before 1.107 the reset was issued, but driver was silent about > this. > > W> For me, the problem is more than just loss of network, but rather every > W> application hanging while multiple timeouts occurr. > > Hmm. May be you are using serial console and system lags when the > console messages are printed? No. I didn't have this laptop until after the 1.107 commit, either. It was probably always doing the timeout, I just never used it much until more recently. -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 14:53:52 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 048D316A4DD for ; Thu, 6 Jul 2006 14:53:52 +0000 (UTC) (envelope-from bushman@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 279AE43D45 for ; Thu, 6 Jul 2006 14:53:50 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from [195.208.252.82] (stinger.cc.rsu.ru [195.208.252.82]) (authenticated bits=0) by mail.r61.net (8.13.7/8.13.6) with ESMTP id k66ErnTK072331 for ; Thu, 6 Jul 2006 18:53:49 +0400 (MSD) (envelope-from bushman@rsu.ru) Message-ID: <44AD2569.9070007@rsu.ru> Date: Thu, 06 Jul 2006 18:59:53 +0400 From: Michael Bushkov User-Agent: Thunderbird 1.5 (X11/20060228) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on asterix.r61.net X-Virus-Status: Clean Subject: nss_ldap and openldap importing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 14:53:52 -0000 Hi, I'm a FreeBSD SoC 2006 student, I work on the nsswitch/ldap/caching daemon stuff this summer. One of the tasks, that I have to do is to import nss_ldap into the source tree. I just want to check the situation with licenses. nss_ldap uses OpenLDAP library, which uses OpenLDAP license (http://www.openldap.org/software/release/license.html). OpenLDAP license seems to be BSD-compatible - so there seems to be no problems with importing it into the source tree. nss_ldap itself uses LGPL. As we use nss_ldap only as dynamic library, which is used in the "larger work" (which FreeBSD is), it can be also included into the source tree. So, we can import nss_ldap, by directly importing (with some specific changes, though) it and OpenLDAP into the source tree, can we? Just want to be sure that I understand licensing situation correctly. With best regards, Michael Bushkov From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 16:32:50 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F73816A4DE; Thu, 6 Jul 2006 16:32:50 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1368D43D45; Thu, 6 Jul 2006 16:32:49 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Thu, 06 Jul 2006 09:32:44 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id D389345047; Thu, 6 Jul 2006 09:32:43 -0700 (PDT) To: Bill Xu In-reply-to: Your message of "Thu, 06 Jul 2006 18:54:40 +0800." <1152183280.21776.13.camel@zeuux.zeuux.com> Date: Thu, 06 Jul 2006 09:32:43 -0700 From: "Kevin Oberman" Message-Id: <20060706163243.D389345047@ptavv.es.net> Cc: Maho Nakata , freebsd-openoffice@freebsd.org, freebsd-current@freebsd.org Subject: Re: cvs commit: ports/editors/openoffice.org-2.0/files patch-i65512 ports/editors/openoffice.org-2.0-devel/files patch-i65512 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 16:32:50 -0000 > From: Bill Xu > Date: Thu, 06 Jul 2006 18:54:40 +0800 > Sender: owner-freebsd-current@freebsd.org > > Compiling editors/openoffice-2.0 still failed in the FreeBSD 7.0-CURRENT > box.The following is the output, > > lo/MDatabaseMetaData.o ../../../unxfbsdi.pro/slo/MConnection.o ../../../unxfbsdi.pro/slo/MNSInit.o ../../../unxfbsdi.pro/slo/MQu > eryHelper.o ../../../unxfbsdi.pro/slo/MDatabaseMetaDataHelper.o ../../../unxfbsdi.pro/slo/MQuery.o ../../../unxfbsdi.pro/slo/MTy > peConverter.o ../../../unxfbsdi.pro/slo/MNameMapper.o ../../../unxfbsdi.pro/slo/MNSMozabProxy.o ../../../unxfbsdi.pro/slo/MNSTer > minateListener.o ../../../unxfbsdi.pro/slo/MMozillaBootstrap.o ../../../unxfbsdi.pro/slo/MNSFolders.o ../../../unxfbsdi.pro/slo/ > MNSProfileDiscover.o ../../../unxfbsdi.pro/slo/MNSProfileManager.o ../../../unxfbsdi.pro/slo/MNSINIParser.o ../../../unxfbsdi.pr > o/slo/MNSRunnable.o ../../../unxfbsdi.pro/slo/MNSProfile.o ../../../unxfbsdi.pro/slo/MNSProfileDirServiceProvider.o ../../../unx > fbsdi.pro/slo/mozabdrv2_version.o ../../../unxfbsdi.pro/slo/mozabdrv2_description.o -o ../../../unxfbsdi.pro/lib/libmozabdrv2.so > -luno_cppu -luno_cppuhelpergcc3 -lvos3gcc3 -luno_sal -ldbtools680fi > -lcomphelp4gcc3 -L/usr/ports/editors/openoffice.org-2.0/wor > k/OOC680_m7/solver/680/unxfbsdi.pro/lib -lembed_base_s -lnspr4 > -lmozreg_s -lxpcom -pthread -lm -Wl,-Bdynamic -lstlport_gcc > rm -f ../../../unxfbsdi.pro/lib/check_libmozabdrv2.so > mv ../../../unxfbsdi.pro/lib/libmozabdrv2.so ../../../unxfbsdi.pro/lib/check_libmozabdrv2.so > /usr/ports/editors/openoffice.org-2.0/work/OOC680_m7/solenv/bin/checkdll.sh -L../../../unxfbsdi.pro/lib -L../lib -L/usr/ports/ed > itors/openoffice.org-2.0/work/OOC680_m7/solenv/unxfbsdi/lib > -L/usr/ports/editors/openoffice.org-2.0/work/OOC680_m7/solver/680/un > xfbsdi.pro/lib > -L/usr/ports/editors/openoffice.org-2.0/work/OOC680_m7/solenv/unxfbsdi/lib -L/usr/local/diablo-jdk1.5.0/lib -L/us > r/local/diablo-jdk1.5.0/jre/lib/i386 > -L/usr/local/diablo-jdk1.5.0/jre/lib/i386/client > -L/usr/local/diablo-jdk1.5.0/jre/lib/i386/ > native_threads > -L/usr/X11R6/lib ../../../unxfbsdi.pro/lib/check_libmozabdrv2.so > Checking DLL ../../../unxfbsdi.pro/lib/check_libmozabdrv2.so ...Fatal > error 'Spinlock called when not threaded.' at line 91 in f > ile /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 2) > Abort trap (core dumped) > dmake: Error code 1, while making > '../../../unxfbsdi.pro/lib/libmozabdrv2.so' > '---* tg_merge.mk *---' > > ERROR: Error 65280 occurred while > making /usr/ports/editors/openoffice.org-2.0/work/OOC680_m7/connectivity/source/drivers/mozab > dmake: Error code 1, while making 'build_instsetoo_native' > '---* *---' > *** Error code 255 > > Stop in /usr/ports/editors/openoffice.org-2.0. > > > > :( If you don't need the browser in Openoffice.org, you can build successfully with -DWITHOUT_MOZILLA. BTW, Ooo 2.0.3 starts up MUCH faster than 2.0.2 or any earlier version. I don't know whet someone spotted, but my laptop (running -current) can now start and open a 5 page .doc file in just under 5 seconds. Used to take that long for the splash to appear. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 17:49:29 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF38D16A4DA for ; Thu, 6 Jul 2006 17:49:29 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 244A743D4C for ; Thu, 6 Jul 2006 17:49:28 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 8370 invoked by uid 399); 6 Jul 2006 17:49:26 -0000 Received: from localhost (HELO ?192.168.0.7?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 6 Jul 2006 17:49:26 -0000 Message-ID: <44AD4D27.3060109@FreeBSD.org> Date: Thu, 06 Jul 2006 10:49:27 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Michael Bushkov References: <44AD2569.9070007@rsu.ru> In-Reply-To: <44AD2569.9070007@rsu.ru> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: nss_ldap and openldap importing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 17:49:29 -0000 Michael Bushkov wrote: > Hi, > I'm a FreeBSD SoC 2006 student, I work on the nsswitch/ldap/caching > daemon stuff this summer. One of the tasks, that I have to do is to > import nss_ldap into the source tree. I just want to check the situation > with licenses. > > nss_ldap uses OpenLDAP library, which uses OpenLDAP license > (http://www.openldap.org/software/release/license.html). OpenLDAP > license seems to be BSD-compatible - so there seems to be no problems > with importing it into the source tree. > > nss_ldap itself uses LGPL. As we use nss_ldap only as dynamic library, > which is used in the "larger work" (which FreeBSD is), it can be also > included into the source tree. So, we can import nss_ldap, by directly > importing (with some specific changes, though) it and OpenLDAP into the > source tree, can we? Just want to be sure that I understand licensing > situation correctly. My understanding is that we are generally trying to avoid importing any new code that has any sort of GPL license. That would certainly be my (personal) preference in any case. Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 19:40:55 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50B5B16A4E2; Thu, 6 Jul 2006 19:40:55 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2A1A43D53; Thu, 6 Jul 2006 19:40:54 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 1072211446; Thu, 6 Jul 2006 15:40:19 -0400 (EDT) Message-ID: <44AD6756.4070008@rogers.com> Date: Thu, 06 Jul 2006 15:41:10 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: obrien@freebsd.org, freebsd-current@freebsd.org References: <20060629193346.GA2548@dragon.NUXI.org> In-Reply-To: <20060629193346.GA2548@dragon.NUXI.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 19:40:55 -0000 David O'Brien wrote: > I'm still often getting calcru output. This is with > FreeBSD anh-thu.NUXI.org 7.0-CURRENT #44: Tue Jun 27 09:30:45 PDT 2006 amd64 > I'm using the default time source (ACPI). What's the latest theories of > the cause of this? > "Me too" However this is on a 6.1-R machine. It does not do any clock speed changes, all power management is off in the bios. Its a Pentium D 3.2Ghz using a supermicro PDSMi motherboard. This particular example came up withe running a buildworld. --- calcru: negative runtime of -171669 usec for pid 16 (yarrow) calcru: negative runtime of -171669 usec for pid 16 (yarrow) calcru: negative runtime of -171669 usec for pid 16 (yarrow) calcru: negative runtime of -171669 usec for pid 16 (yarrow) calcru: negative runtime of -167760 usec for pid 16 (yarrow) calcru: negative runtime of -167760 usec for pid 16 (yarrow) calcru: negative runtime of -166914 usec for pid 16 (yarrow) calcru: negative runtime of -166914 usec for pid 16 (yarrow) calcru: negative runtime of -166275 usec for pid 16 (yarrow) calcru: negative runtime of -166275 usec for pid 16 (yarrow) calcru: negative runtime of -165687 usec for pid 16 (yarrow) calcru: negative runtime of -165687 usec for pid 16 (yarrow) calcru: negative runtime of -164999 usec for pid 16 (yarrow) calcru: negative runtime of -164999 usec for pid 16 (yarrow) calcru: negative runtime of -164395 usec for pid 16 (yarrow) calcru: negative runtime of -164395 usec for pid 16 (yarrow) ... From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 00:13:32 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01F7416A4E0 for ; Fri, 7 Jul 2006 00:13:32 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 760FC43D45 for ; Fri, 7 Jul 2006 00:13:30 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so1119303nzi for ; Thu, 06 Jul 2006 17:13:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=ZLbTe5GSV3LwqOp5B7Z5fgtGwCmUvTCBSWDi+Tbu1pnZ22SZHSYJ7vHDRlfgfHXGHh/t1f9Hmskz3OfvA5QY/anriJBq7jHcWcS3l8Li0YVG2ZC0R9HL9kckxok9qyHhx5pdyxf3sL8aRY0DXCrn3SxZRGBi6EBjbAhLmFD5ufY= Received: by 10.36.67.7 with SMTP id p7mr1727724nza; Thu, 06 Jul 2006 17:13:29 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id r9sm1135021nza.2006.07.06.17.13.28; Thu, 06 Jul 2006 17:13:29 -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 k670HG4g083545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 7 Jul 2006 09:17:16 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k670HFWw083544 for freebsd-current@freebsd.org; Fri, 7 Jul 2006 09:17:15 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 7 Jul 2006 09:17:15 +0900 From: Pyun YongHyeon To: freebsd-current@freebsd.org Message-ID: <20060707001715.GB82406@cdnetworks.co.kr> References: <20060705114853.GB73705@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060705114853.GB73705@cdnetworks.co.kr> User-Agent: Mutt/1.4.2.1i Subject: Re: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 00:13:32 -0000 On Wed, Jul 05, 2006 at 08:48:53PM +0900, To freebsd-current@freebsd.org wrote: > Hi, > [...] > > You can get the latest stge(4) driver from the following URL. > http://people.freebsd.org/~yongari/stge/stge.HEAD.diff > I've regenerated the patch as it has missing changes. For more broad testing I've generated a patch for RELENG_6 too. http://people.freebsd.org/~yongari/stge/stge.REL6.diff -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 01:54:59 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEFB716A4DA; Fri, 7 Jul 2006 01:54:59 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63C0143D45; Fri, 7 Jul 2006 01:54:59 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k671swON002004; Thu, 6 Jul 2006 18:54:58 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k671swwQ002003; Thu, 6 Jul 2006 18:54:58 -0700 Date: Thu, 6 Jul 2006 18:54:58 -0700 From: Brooks Davis To: Doug Barton Message-ID: <20060707015458.GC500@odin.ac.hmc.edu> References: <44AD2569.9070007@rsu.ru> <44AD4D27.3060109@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y5rl02BVI9TCfPar" Content-Disposition: inline In-Reply-To: <44AD4D27.3060109@FreeBSD.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: freebsd-current@freebsd.org, Michael Bushkov Subject: Re: nss_ldap and openldap importing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 01:54:59 -0000 --Y5rl02BVI9TCfPar Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 06, 2006 at 10:49:27AM -0700, Doug Barton wrote: > Michael Bushkov wrote: > > Hi, > > I'm a FreeBSD SoC 2006 student, I work on the nsswitch/ldap/caching > > daemon stuff this summer. One of the tasks, that I have to do is to > > import nss_ldap into the source tree. I just want to check the situation > > with licenses. > >=20 > > nss_ldap uses OpenLDAP library, which uses OpenLDAP license > > (http://www.openldap.org/software/release/license.html). OpenLDAP > > license seems to be BSD-compatible - so there seems to be no problems > > with importing it into the source tree. > >=20 > > nss_ldap itself uses LGPL. As we use nss_ldap only as dynamic library, > > which is used in the "larger work" (which FreeBSD is), it can be also > > included into the source tree. So, we can import nss_ldap, by directly > > importing (with some specific changes, though) it and OpenLDAP into the > > source tree, can we? Just want to be sure that I understand licensing > > situation correctly. >=20 > My understanding is that we are generally trying to avoid importing any n= ew > code that has any sort of GPL license. That would certainly be my (person= al) > preference in any case. Unless we have someone crediably committed to rewritting nss_ldap I think this is a good place to make an exception. We can always remove it later if an implementation exists, but we could really use better integration with ldap. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --Y5rl02BVI9TCfPar Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFErb7yXY6L6fI4GtQRArRKAKCbcuBaj4ozG2LuWfHoPwg0CEoXVgCfWtzi dyW77Hr4t9gsg5b0cDYx+44= =msM7 -----END PGP SIGNATURE----- --Y5rl02BVI9TCfPar-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 02:22:44 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18F9316A4DA for ; Fri, 7 Jul 2006 02:22:44 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FBA943D4C for ; Fri, 7 Jul 2006 02:22:41 +0000 (GMT) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id F0EA6EB108E; Fri, 7 Jul 2006 10:22:39 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id ahasJta-NXuP; Fri, 7 Jul 2006 10:22:34 +0800 (CST) Received: from [10.217.12.96] (sina152-194.staff.sina.com.cn [61.135.152.194]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 2F471EB0E39; Fri, 7 Jul 2006 10:22:32 +0800 (CST) From: Xin LI To: Michael Bushkov In-Reply-To: <44AD2569.9070007@rsu.ru> References: <44AD2569.9070007@rsu.ru> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-CtVIt26yHpWthJ6Y5E9n" Organization: The FreeBSD Project Date: Fri, 07 Jul 2006 10:22:28 +0800 Message-Id: <1152238948.951.13.camel@spirit> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 FreeBSD GNOME Team Port Cc: freebsd-current@freebsd.org Subject: Re: nss_ldap and openldap importing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 02:22:44 -0000 --=-CtVIt26yHpWthJ6Y5E9n Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =E5=9C=A8 2006-07-06=E5=9B=9B=E7=9A=84 18:59 +0400=EF=BC=8CMichael Bushkov= =E5=86=99=E9=81=93=EF=BC=9A > Hi, > I'm a FreeBSD SoC 2006 student, I work on the nsswitch/ldap/caching=20 > daemon stuff this summer. One of the tasks, that I have to do is to=20 > import nss_ldap into the source tree. I just want to check the situation=20 > with licenses. >=20 > nss_ldap uses OpenLDAP library, which uses OpenLDAP license=20 > (http://www.openldap.org/software/release/license.html). OpenLDAP=20 > license seems to be BSD-compatible - so there seems to be no problems=20 > with importing it into the source tree. I think OpenLDAP code evolves very fast and maintaining the whole library in the base system would be more or less painful at the moment. Would you please consider renaming the library to avoid collision with the ones installed with port, if we finally want to import the stuff? Cheers, --=20 Xin LI http://www.delphij.net/ --=-CtVIt26yHpWthJ6Y5E9n Content-Type: application/pgp-signature; name=signature.asc Content-Description: =?UTF-8?Q?=E8=BF=99=E6=98=AF=E4=BF=A1=E4=BB=B6=E7=9A=84=E6=95=B0?= =?UTF-8?Q?=E5=AD=97=E7=AD=BE=E5=90=8D=E9=83=A8=E5=88=86?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBErcVkhcUczkLqiksRAkpPAJ0ZgJNqa1IaXjfs/+TNIM7Zl2/fxwCg5CA7 aNZB8W1bKUI1o1Hb4wxoBug= =19aq -----END PGP SIGNATURE----- --=-CtVIt26yHpWthJ6Y5E9n-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 02:22:53 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C61916A501 for ; Fri, 7 Jul 2006 02:22:53 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11A8B43D53 for ; Fri, 7 Jul 2006 02:22:52 +0000 (GMT) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id 6BE9578C1D; Fri, 7 Jul 2006 02:22:50 +0000 (GMT) Date: Fri, 7 Jul 2006 02:22:50 +0000 From: John Birrell To: current@freebsd.org Message-ID: <20060707022250.GA52144@what-creek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: DTrace for FreeBSD - HEADS UP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 02:22:53 -0000 This is just a short note for everyone (anyone?) following the DTrace sources via cvsup10.freebsd.org. There was short period of time over the last day or so where the buildworld on i386 would have created a boot loader that was broken. I doubt that anyone would have been bitten by this because the kernel build was broken for a while too. Oops. This happened while the sun4v support was being merged into the DTrace project. Thanks to Sun Microsystems for providing an extra Sun Fire T2000 server for FreeBSD development. 32 logical cpus, 32 GB of memory, 4 gigE ports, 4 USB. Watching a make -j32 buildworld with 32 cpus all running at close to 100% is _really_ impressive! See: Expect to see DTrace built into FreeBSD/sun4v over the comming weeks. (Note: As part of the sun4v import, support for libpthread and KSE has been disabled.) -- John Birrell From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 02:01:30 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A94F16A4DA; Fri, 7 Jul 2006 02:01:30 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCBC443D4C; Fri, 7 Jul 2006 02:01:29 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 24BB7114F3; Thu, 6 Jul 2006 22:00:53 -0400 (EDT) Message-ID: <44ADC08B.8000408@rogers.com> Date: Thu, 06 Jul 2006 22:01:47 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: obrien@freebsd.org References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> In-Reply-To: <44AD6756.4070008@rogers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, AWL 0.00, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No X-Mailman-Approved-At: Fri, 07 Jul 2006 03:21:00 +0000 Cc: stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 02:01:30 -0000 I'm getting a ton of them now, and i found a way to reproduce them. Basically i run a compile session in one terminal, say make buildkernel, and run top in another. As soon as i run top, the messages appear, and they seem to be synchronized with the refresh rate of top, 2 messages per refresh. This is on a 6.1-STABLE as of today. --- calcru: negative runtime of -261273 usec for pid 12 (swi4: clock) calcru: negative runtime of -261273 usec for pid 12 (swi4: clock) calcru: negative runtime of -259691 usec for pid 12 (swi4: clock) ... From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 04:41:13 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4322916A4E7 for ; Fri, 7 Jul 2006 04:41:12 +0000 (UTC) (envelope-from davidxu@freebsd.org) Message-ID: <44ADE5EB.1090300@freebsd.org> Date: Fri, 07 Jul 2006 12:41:15 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060519 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: sysenter syscall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 04:41:13 -0000 Hi, Today I have tested sysenter sycall vs int0x80 syscall, I have done the work several monthes ago, now I have imported it into perforce, the branch name is davidxu_sysenter. Here are some benchmark results: 1. pure geteuid() syscall: x int80_syscall.txt + sysenter_syscall.txt +--------------------------------------------------------------------------+ | + | | x + | | xxx ++ | |x x xxxx + + ++++ | | |_A_| |___A_M_|| +--------------------------------------------------------------------------+ N Min Max Median Avg Stddev x 10 2390403 2562187 2525720 2508262.9 53926.058 + 10 3855570 4169162 4139662 4103079.4 95933.507 Difference at 95.0% confidence 1.59482e+06 +/- 73117.4 63.5825% +/- 2.91506% (Student's t, pooled s = 77817.9) 2. mysql super-smack: x mysql_int80.txt + mysql_sysenter.txt +--------------------------------------------------------------------------+ | x + | | x + + | | x xx + +++ | |x x xxxx x x x x + + +++++ +| | |______MA________| |___A___| | +--------------------------------------------------------------------------+ N Min Max Median Avg Stddev x 15 19212.09 19911.76 19417.23 19449.863 165.25167 + 15 20250.48 20603.26 20408.12 20411.395 76.260797 Difference at 95.0% confidence 961.531 +/- 96.2398 4.94364% +/- 0.494809% (Student's t, pooled s = 128.693) Hardware is dual-core Pentium-D. I thought sysenter is useless as I said on dragonflybsd mail list, but the fact is a little different here, so I was wrong. David Xu From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 04:53:44 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 177AF16A4DD; Fri, 7 Jul 2006 04:53:44 +0000 (UTC) In-Reply-To: <20060706124258.GE76865@cdnetworks.co.kr> from Pyun YongHyeon at "Jul 6, 2006 09:42:58 pm" To: pyunyh@gmail.com Date: Fri, 7 Jul 2006 04:53:44 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20060707045344.177AF16A4DD@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: csaba-ml@creo.hu, freebsd-current@freebsd.org Subject: Re: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 04:53:44 -0000 > On Thu, Jul 06, 2006 at 11:52:39AM +0000, Csaba Henk wrote: > > On 2006-07-06, Pyun YongHyeon wrote: > > > What model/maker you've got(pciconf -lv output)? > > > > stge0@pci0:11:0: class=0x020000 card=0x545013f0 chip=0x102113f0 rev=0x07 hdr=0x00 > > vendor = 'Sundance Technology Inc' > > class = network > > subclass = ethernet > > > > And this is what shows up in dmesg: > > > > Jul 6 07:50:23 leavemealone kernel: stge0: port 0xe000-0xe0ff mem 0xef000000-0xef0001ff irq 11 at device 11.0 on pci0 > > Jul 6 07:50:23 leavemealone kernel: stge0: phy read fail > > Jul 6 07:50:23 leavemealone last message repeated 31 times > > Jul 6 07:50:23 leavemealone kernel: miibus2: on stge0 > > Jul 6 07:50:23 leavemealone kernel: e1000phy0: on miibus2 > > Jul 6 07:50:23 leavemealone kernel: e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto > > > > Since your NIC has a Marvell PHY and shows many "phy read fail" > message I have to investigate the root cause. I don't have > TC9021 NIC with Marvell PHY. So I can't sure I can fix it. > > Does ifconfig(8) reports correct link speed/status? > Does "phy read fail" message shows only at device attach time? FYI: I don't know if you have them or not, but a long time ago I stashed away copies of the TC9020/TC9021 programming manuals. The provenance of these parts is a little murky. I first learned of them as being Sundance Technologies devices, but later I found references to them belonging to a company called Tamarack M.I. Later still, a company called ICplus ended up with them. ICplus eventually produced a single chip device combining the TC902x MAC with an integrated PHY (though I've yet to actually see a NIC that uses these anywhere). Sundance and Tamarack seem to have disappeared, but ICplus is still around (www.icplus.com.tw) and they still have the gigE MAC and PHY manuals online. They deleted the original TC902x manuals from their site, but I saved copies. :) I put all the manuals I have for these devices at http://www.freebsd.org/~wpaul/Sundance along with the original ST201 manual. Note that I didn't have to sign any NDAs to get any of these. In case you can't tell, the hardware API for the ST201 and the TC902x is copied very closely from the 3Com 3c90xB/3c90xC devices. Anyway, I'm posting these in case they help with maintaining the driver (or if anyone just wants to tinker around with the hardware). Share and enjoy! -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 05:06:19 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 838DE16A4E0 for ; Fri, 7 Jul 2006 05:06:19 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.FreeBSD.org (Postfix) with SMTP id B34BA43D46 for ; Fri, 7 Jul 2006 05:06:18 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 3840 invoked by uid 399); 7 Jul 2006 05:06:17 -0000 Received: from localhost (HELO ?192.168.0.7?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 7 Jul 2006 05:06:17 -0000 Message-ID: <44ADEBCC.70607@FreeBSD.org> Date: Thu, 06 Jul 2006 22:06:20 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Michael Bushkov References: <44AD2569.9070007@rsu.ru> In-Reply-To: <44AD2569.9070007@rsu.ru> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: nss_ldap and openldap importing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 05:06:19 -0000 Concern about licensing aside, given the other question that was raised, perhaps you can provide a little more detail in terms of answering the question, "What can having this in the base do for us that having it as a port cannot?" Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 06:07:11 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C3EC16A4DA; Fri, 7 Jul 2006 06:07:11 +0000 (UTC) (envelope-from bushman@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA76A43D45; Fri, 7 Jul 2006 06:07:10 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from carrera ([82.179.80.78]) (authenticated bits=0) by mail.r61.net (8.13.7/8.13.6) with ESMTP id k67673eh052692 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 7 Jul 2006 10:07:06 +0400 (MSD) (envelope-from bushman@rsu.ru) Message-ID: <003c01c6a18b$937cbef0$3a00a8c0@carrera> From: "Michael Bushkov" To: "Doug Barton" References: <44AD2569.9070007@rsu.ru> <44ADEBCC.70607@FreeBSD.org> Date: Fri, 7 Jul 2006 10:06:55 +0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on asterix.r61.net X-Virus-Status: Clean Cc: freebsd-current@FreeBSD.org Subject: Re: nss_ldap and openldap importing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 06:07:11 -0000 > Concern about licensing aside, given the other question that was raised, > perhaps you can provide a little more detail in terms of answering the > question, "What can having this in the base do for us that having it as a > port cannot?" 2 arguments, basically: 1. Having nss_ldap in the source gives an ability to use nss_ldap right "out of the box" and equals it in rights with such nsswitch sources as NIS and DNS. If we have NIS in the base system, I don't see any reasons not to have nss_ldap. Besides, i'm sure, having nss_ldap in the base will make users feeling more comfortable when dealing with it. 2. I guess, we'll have to rewrite nss_ldap by ourselves sooner or later (actually, I can do it), so current nss_ldap import can be viewed as the first stage of the plan. The second stage is replacing PADL's nss_ldap with our own implementation. With best regards, Michael Bushkov From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 07:47:02 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E2C416A4DF for ; Fri, 7 Jul 2006 07:47:02 +0000 (UTC) (envelope-from pyunyh@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 A986D43D6A for ; Fri, 7 Jul 2006 07:46:44 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id i75so289773pye for ; Fri, 07 Jul 2006 00:46:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=k9rZlIr5S8PQahovlb4ZHuR8R5mqZJ20sdRIyGEiEikqOtyn0Ee2aTgrsuLQdK4j1X3Y1VNG/qbQ81P8sDw+AE4CpE725gmaHJVKGQyYpjKPdzJOn2u4WoTcFiYRMDCF24GDNhsR7v9r01UIZKZe8H3cDEWpCI94mFGSpaflB8U= Received: by 10.35.84.16 with SMTP id m16mr1935131pyl; Fri, 07 Jul 2006 00:46:10 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id z80sm632550pyg.2006.07.07.00.46.07; Fri, 07 Jul 2006 00:46:09 -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 k677nwiV084859 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Jul 2006 16:49:59 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k677nv4H084858; Fri, 7 Jul 2006 16:49:57 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 7 Jul 2006 16:49:57 +0900 From: Pyun YongHyeon To: Bill Paul Message-ID: <20060707074957.GF82406@cdnetworks.co.kr> References: <20060706124258.GE76865@cdnetworks.co.kr> <20060707045344.177AF16A4DD@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060707045344.177AF16A4DD@hub.freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: csaba-ml@creo.hu, freebsd-current@FreeBSD.ORG Subject: Re: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 07:47:02 -0000 On Fri, Jul 07, 2006 at 04:53:44AM +0000, Bill Paul wrote: > > On Thu, Jul 06, 2006 at 11:52:39AM +0000, Csaba Henk wrote: > > > On 2006-07-06, Pyun YongHyeon wrote: > > > > What model/maker you've got(pciconf -lv output)? > > > > > > stge0@pci0:11:0: class=0x020000 card=0x545013f0 chip=0x102113f0 rev=0x07 hdr=0x00 > > > vendor = 'Sundance Technology Inc' > > > class = network > > > subclass = ethernet > > > > > > And this is what shows up in dmesg: > > > > > > Jul 6 07:50:23 leavemealone kernel: stge0: port 0xe000-0xe0ff mem 0xef000000-0xef0001ff irq 11 at device 11.0 on pci0 > > > Jul 6 07:50:23 leavemealone kernel: stge0: phy read fail > > > Jul 6 07:50:23 leavemealone last message repeated 31 times > > > Jul 6 07:50:23 leavemealone kernel: miibus2: on stge0 > > > Jul 6 07:50:23 leavemealone kernel: e1000phy0: on miibus2 > > > Jul 6 07:50:23 leavemealone kernel: e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto > > > > > > > Since your NIC has a Marvell PHY and shows many "phy read fail" > > message I have to investigate the root cause. I don't have > > TC9021 NIC with Marvell PHY. So I can't sure I can fix it. > > > > Does ifconfig(8) reports correct link speed/status? > > Does "phy read fail" message shows only at device attach time? > > FYI: I don't know if you have them or not, but a long time ago I > stashed away copies of the TC9020/TC9021 programming manuals. The > provenance of these parts is a little murky. I first learned of them > as being Sundance Technologies devices, but later I found references to > them belonging to a company called Tamarack M.I. Later still, a > company called ICplus ended up with them. ICplus eventually produced > a single chip device combining the TC902x MAC with an integrated PHY > (though I've yet to actually see a NIC that uses these anywhere). > ASUS NX1101 and some motherboards from ABIT have IC Plus GigE controller. > Sundance and Tamarack seem to have disappeared, but ICplus is still > around (www.icplus.com.tw) and they still have the gigE MAC and PHY > manuals online. They deleted the original TC902x manuals from their site, Yes, the online manuals are useless. > but I saved copies. :) I put all the manuals I have for these devices at > http://www.freebsd.org/~wpaul/Sundance along with the original ST201 > manual. Note that I didn't have to sign any NDAs to get any of these. > Thank you very very much. I really appreciate it. I mailed to guys working for IC Plus a couple of of times and they all requested to sign NDAs so I gave up. > In case you can't tell, the hardware API for the ST201 and the TC902x > is copied very closely from the 3Com 3c90xB/3c90xC devices. > > Anyway, I'm posting these in case they help with maintaining the driver > (or if anyone just wants to tinker around with the hardware). Share > and enjoy! > > -Bill > Thanks again. I hope I can solve JUMBO frame issues soon. -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 09:18:55 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AA2616A4DA; Fri, 7 Jul 2006 09:18:55 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE1B843D46; Fri, 7 Jul 2006 09:18:54 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail17.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k679IpHt028661 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 7 Jul 2006 19:18:52 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k679Ioqo001215; Fri, 7 Jul 2006 19:18:50 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k679Ioj4001214; Fri, 7 Jul 2006 19:18:50 +1000 (EST) (envelope-from peter) Date: Fri, 7 Jul 2006 19:18:50 +1000 From: Peter Jeremy To: Michael Bushkov Message-ID: <20060707091850.GA719@turion.vk2pj.dyndns.org> References: <44AD2569.9070007@rsu.ru> <44ADEBCC.70607@FreeBSD.org> <003c01c6a18b$937cbef0$3a00a8c0@carrera> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8" Content-Disposition: inline In-Reply-To: <003c01c6a18b$937cbef0$3a00a8c0@carrera> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: Doug Barton , freebsd-current@freebsd.org Subject: Re: nss_ldap and openldap importing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 09:18:55 -0000 --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 2006-Jul-07 10:06:55 +0400, Michael Bushkov wrote: >1. Having nss_ldap in the source gives an ability to use nss_ldap right=20 >"out of the box" and equals it in rights with such nsswitch sources as NIS= =20 >and DNS. If we have NIS in the base system, I don't see any reasons not to= =20 >have nss_ldap. Besides, i'm sure, having nss_ldap in the base will make=20 >users feeling more comfortable when dealing with it. I don't think this follows. Things like X and perl can be installed =66rom sysinstall with mininal effort. I'd prefer to make it easier to install nss_ldap as a package than have it in the base system. >2. I guess, we'll have to rewrite nss_ldap by ourselves sooner or later=20 >(actually, I can do it), so current nss_ldap import can be viewed as the= =20 >first stage of the plan. It would seem cleaner to implement our own nss_ldap from scratch rather than importing a GPL one and then replacing it. IMHO, having the GPL nss_ldap in the tree would make it harder to import another one. Once people start using nss_ldap, they are going to get very picky about a replacement being bug-for-bug compatible. --=20 Peter Jeremy --ibTvN161/egqYuK8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEribu/opHv/APuIcRAp5TAKC8P3I6LSQlocioixAwvr+DCN34hQCeLQk3 QpbaWQWI5qumUBbJk+r5V8w= =yel9 -----END PGP SIGNATURE----- --ibTvN161/egqYuK8-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 09:43:07 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9127216A4DE; Fri, 7 Jul 2006 09:43:07 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from ms-dienst.rz.rwth-aachen.de (ms-1.rz.RWTH-Aachen.DE [134.130.3.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5BC943D45; Fri, 7 Jul 2006 09:43:06 +0000 (GMT) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from circe (circe.rz.RWTH-Aachen.DE [134.130.3.36]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0J2100FBB1NRCS@ms-dienst.rz.rwth-aachen.de>; Fri, 07 Jul 2006 11:43:04 +0200 (MEST) Received: from talos.rz.RWTH-Aachen.DE ([134.130.3.22]) by circe (MailMonitor for SMTP v1.2.2 ) ; Fri, 07 Jul 2006 11:43:03 +0200 (MEST) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by smarthost.rwth-aachen.de (8.13.1/8.13.1/1) with ESMTP id k679h2YH029331; Fri, 07 Jul 2006 11:43:02 +0200 Received: from haakonia.hitnet.rwth-aachen.de ([137.226.181.92]) by bigboss.hitnet.rwth-aachen.de with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1FymrW-0007rg-Nj; Fri, 07 Jul 2006 11:43:02 +0200 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id 6C2CA3F41F; Fri, 07 Jul 2006 11:43:02 +0200 (CEST) Date: Fri, 07 Jul 2006 11:43:02 +0200 From: Christian Brueffer In-reply-to: <20060707074957.GF82406@cdnetworks.co.kr> To: Pyun YongHyeon Message-id: <20060707094302.GA1669@haakonia.hitnet.RWTH-Aachen.DE> MIME-version: 1.0 Content-type: multipart/signed; boundary="HcAYCG3uE/tztfnV"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.11 X-Operating-System: FreeBSD 6.1-STABLE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <20060706124258.GE76865@cdnetworks.co.kr> <20060707045344.177AF16A4DD@hub.freebsd.org> <20060707074957.GF82406@cdnetworks.co.kr> Cc: csaba-ml@creo.hu, Bill Paul , freebsd-current@FreeBSD.ORG Subject: Re: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 09:43:07 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 07, 2006 at 04:49:57PM +0900, Pyun YongHyeon wrote: > On Fri, Jul 07, 2006 at 04:53:44AM +0000, Bill Paul wrote: > > > On Thu, Jul 06, 2006 at 11:52:39AM +0000, Csaba Henk wrote: > > > > On 2006-07-06, Pyun YongHyeon wrote: > > > > > What model/maker you've got(pciconf -lv output)? > > > >=20 > > > > stge0@pci0:11:0: class=3D0x020000 card=3D0x545013f0 chip= =3D0x102113f0 rev=3D0x07 hdr=3D0x00 > > > > vendor =3D 'Sundance Technology Inc' > > > > class =3D network > > > > subclass =3D ethernet > > > >=20 > > > > And this is what shows up in dmesg: > > > >=20 > > > > Jul 6 07:50:23 leavemealone kernel: stge0: port 0xe000-0xe0ff mem 0xef000000-0xef0001ff irq 11 at device= 11.0 on pci0 > > > > Jul 6 07:50:23 leavemealone kernel: stge0: phy read fail > > > > Jul 6 07:50:23 leavemealone last message repeated 31 times > > > > Jul 6 07:50:23 leavemealone kernel: miibus2: on stge0 > > > > Jul 6 07:50:23 leavemealone kernel: e1000phy0: on miibus2 > > > > Jul 6 07:50:23 leavemealone kernel: e1000phy0: 10baseT, 10baseT= -FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto > > > >=20 > > >=20 > > > Since your NIC has a Marvell PHY and shows many "phy read fail" > > > message I have to investigate the root cause. I don't have > > > TC9021 NIC with Marvell PHY. So I can't sure I can fix it. > > >=20 > > > Does ifconfig(8) reports correct link speed/status? > > > Does "phy read fail" message shows only at device attach time? > >=20 > > FYI: I don't know if you have them or not, but a long time ago I > > stashed away copies of the TC9020/TC9021 programming manuals. The > > provenance of these parts is a little murky. I first learned of them > > as being Sundance Technologies devices, but later I found references to > > them belonging to a company called Tamarack M.I. Later still, a > > company called ICplus ended up with them. ICplus eventually produced > > a single chip device combining the TC902x MAC with an integrated PHY > > (though I've yet to actually see a NIC that uses these anywhere). > >=20 >=20 > ASUS NX1101 and some motherboards from ABIT have IC Plus GigE controller. >=20 > > Sundance and Tamarack seem to have disappeared, but ICplus is still > > around (www.icplus.com.tw) and they still have the gigE MAC and PHY > > manuals online. They deleted the original TC902x manuals from their si= te, >=20 > Yes, the online manuals are useless. >=20 > > but I saved copies. :) I put all the manuals I have for these devices = at > > http://www.freebsd.org/~wpaul/Sundance along with the original ST201 > > manual. Note that I didn't have to sign any NDAs to get any of these. > >=20 >=20 > Thank you very very much. I really appreciate it. I mailed to guys > working for IC Plus a couple of of times and they all requested to > sign NDAs so I gave up. >=20 > > In case you can't tell, the hardware API for the ST201 and the TC902x > > is copied very closely from the 3Com 3c90xB/3c90xC devices. > >=20 > > Anyway, I'm posting these in case they help with maintaining the driver > > (or if anyone just wants to tinker around with the hardware). Share > > and enjoy! > >=20 > > -Bill > >=20 >=20 > Thanks again. I hope I can solve JUMBO frame issues soon. >=20 There is also a BSD licensed driver for FreeBSD 4.x written by Tamarack. No idea wheather or not it is still available, so I put it up for download: http://people.freebsd.org/~brueffer/TC902X_FreeBSD.zip Maybe it can help in some way. - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEriymbHYXjKDtmC0RAmRyAKCU4H/elHwxcKJdYHDxsOkTQ6uVtgCfRD0K xQ68sRnUud1bIQqSPOH80NE= =XjRA -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 10:37:08 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC9C416A4DE for ; Fri, 7 Jul 2006 10:37:07 +0000 (UTC) (envelope-from marius.nuennerich@gmx.net) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 885A543D73 for ; Fri, 7 Jul 2006 10:37:02 +0000 (GMT) (envelope-from marius.nuennerich@gmx.net) Received: (qmail invoked by alias); 07 Jul 2006 10:37:00 -0000 Received: from dslb-084-061-193-100.pools.arcor-ip.net (EHLO sol.hackerzberg.local) [84.61.193.100] by mail.gmx.net (mp028) with SMTP; 07 Jul 2006 12:37:00 +0200 X-Authenticated: #5707313 Date: Fri, 7 Jul 2006 12:36:39 +0200 From: Marius Nuennerich To: freebsd-current@freebsd.org Message-ID: <20060707123639.68440083@sol.hackerzberg.local> In-Reply-To: <20060707094302.GA1669@haakonia.hitnet.RWTH-Aachen.DE> References: <20060706124258.GE76865@cdnetworks.co.kr> <20060707045344.177AF16A4DD@hub.freebsd.org> <20060707074957.GF82406@cdnetworks.co.kr> <20060707094302.GA1669@haakonia.hitnet.RWTH-Aachen.DE> X-Mailer: Sylpheed-Claws 2.3.1 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Mailman-Approved-At: Fri, 07 Jul 2006 11:38:58 +0000 Subject: Re: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 10:37:08 -0000 On Fri, 07 Jul 2006 11:43:02 +0200 Christian Brueffer wrote: > On Fri, Jul 07, 2006 at 04:49:57PM +0900, Pyun YongHyeon wrote: > > On Fri, Jul 07, 2006 at 04:53:44AM +0000, Bill Paul wrote: > > > > On Thu, Jul 06, 2006 at 11:52:39AM +0000, Csaba Henk wrote: > > > > > On 2006-07-06, Pyun YongHyeon wrote: > > > > > > What model/maker you've got(pciconf -lv output)? > > > > > > > > > > stge0@pci0:11:0: class=0x020000 card=0x545013f0 chip=0x102113f0 rev=0x07 hdr=0x00 > > > > > vendor = 'Sundance Technology Inc' > > > > > class = network > > > > > subclass = ethernet > > > > > > > > > > And this is what shows up in dmesg: > > > > > > > > > > Jul 6 07:50:23 leavemealone kernel: stge0: port 0xe000-0xe0ff mem 0xef000000-0xef0001ff irq 11 at device 11.0 on pci0 > > > > > Jul 6 07:50:23 leavemealone kernel: stge0: phy read fail > > > > > Jul 6 07:50:23 leavemealone last message repeated 31 times > > > > > Jul 6 07:50:23 leavemealone kernel: miibus2: on stge0 > > > > > Jul 6 07:50:23 leavemealone kernel: e1000phy0: on miibus2 > > > > > Jul 6 07:50:23 leavemealone kernel: e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto > > > > > > > > > > > > > Since your NIC has a Marvell PHY and shows many "phy read fail" > > > > message I have to investigate the root cause. I don't have > > > > TC9021 NIC with Marvell PHY. So I can't sure I can fix it. > > > > > > > > Does ifconfig(8) reports correct link speed/status? > > > > Does "phy read fail" message shows only at device attach time? > > > > > > FYI: I don't know if you have them or not, but a long time ago I > > > stashed away copies of the TC9020/TC9021 programming manuals. The > > > provenance of these parts is a little murky. I first learned of them > > > as being Sundance Technologies devices, but later I found references to > > > them belonging to a company called Tamarack M.I. Later still, a > > > company called ICplus ended up with them. ICplus eventually produced > > > a single chip device combining the TC902x MAC with an integrated PHY > > > (though I've yet to actually see a NIC that uses these anywhere). > > > > > > > ASUS NX1101 and some motherboards from ABIT have IC Plus GigE controller. > > > > > Sundance and Tamarack seem to have disappeared, but ICplus is still > > > around (www.icplus.com.tw) and they still have the gigE MAC and PHY > > > manuals online. They deleted the original TC902x manuals from their site, > > > > Yes, the online manuals are useless. > > > > > but I saved copies. :) I put all the manuals I have for these devices at > > > http://www.freebsd.org/~wpaul/Sundance along with the original ST201 > > > manual. Note that I didn't have to sign any NDAs to get any of these. > > > > > > > Thank you very very much. I really appreciate it. I mailed to guys > > working for IC Plus a couple of of times and they all requested to > > sign NDAs so I gave up. > > > > > In case you can't tell, the hardware API for the ST201 and the TC902x > > > is copied very closely from the 3Com 3c90xB/3c90xC devices. > > > > > > Anyway, I'm posting these in case they help with maintaining the driver > > > (or if anyone just wants to tinker around with the hardware). Share > > > and enjoy! > > > > > > -Bill > > > > > > > Thanks again. I hope I can solve JUMBO frame issues soon. > > > > There is also a BSD licensed driver for FreeBSD 4.x written by Tamarack. > No idea wheather or not it is still available, so I put it up for > download: > > http://people.freebsd.org/~brueffer/TC902X_FreeBSD.zip > > Maybe it can help in some way. > > - Christian And there is a driver for FreeBSD 5.1 here: http://www.icplus.com.tw/driver-pp-IP1000A.html A while ago I started to bring that one up-to-date, here is what I've got so far: http://bsdwiki.de/marius/ipg.diff I'm not sure if I remember correctly, but I think this Version compiled on 6.0. Nice someone with more clue started looking into this :) - Marius P.S. I will test stge, as soon as my testmachine is back. From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 14:13:28 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF23416A4DE for ; Fri, 7 Jul 2006 14:13:28 +0000 (UTC) (envelope-from jr@opal.com) Received: from smtp.vzavenue.net (smtp.vzavenue.net [66.171.59.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F84A43D46 for ; Fri, 7 Jul 2006 14:13:28 +0000 (GMT) (envelope-from jr@opal.com) Received: from 118.79.171.66.subscriber.vzavenue.net (HELO linwhf.opal.com) ([66.171.79.118]) by smtp.vzavenue.net with ESMTP; 07 Jul 2006 10:13:27 -0400 X-REPUTATION: -0.7 X-REMOTE-IP: 66.171.79.118 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.06,217,1149480000"; d="scan'208"; a="41900265:sNHT17632620" Received: from linwhf.opal.com (localhost [127.0.0.1]) by linwhf.opal.com (8.13.6/8.13.6) with ESMTP id k67EDRFX067281 for ; Fri, 7 Jul 2006 10:13:27 -0400 (EDT) (envelope-from jr@opal.com) Received: from 127.0.0.1 ([127.0.0.1] helo=linwhf.opal.com) by ASSP-nospam; 7 Jul 2006 10:13:27 -0400 Received: (from jr@localhost) by linwhf.opal.com (8.13.6/8.13.6/Submit) id k67EDQ9t067280 for freebsd-current@freebsd.org; Fri, 7 Jul 2006 10:13:26 -0400 (EDT) (envelope-from jr) Date: Fri, 7 Jul 2006 10:13:26 -0400 From: "J.R. Oldroyd" To: freebsd-current@freebsd.org Message-ID: <20060707141326.GG21006@linwhf.opal.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Unicode/UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 14:13:29 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Folks, In a few days' time I will submit the SWIDTH0 patches to mklocale/UTF-8.src and to hexdump/conv.c, posted here a couple of weeks ago, for committing. If anyone who's downloaded and tried them has any comments, the next day or so would be a good time to email me. I'm particularly looking for feedback that I didn't inadvertently list any non-zero-width characters as zero-width, and also that I didn't miss any that are zero-width chars. Links to those patches once more, are here: http://opal.com/freebsd/unicode.html#lcctype http://opal.com/freebsd/unicode.html#hexdump In other related news, work is progressing on updating ncurses in the base system to support wide chars, and work is also in progress on addressing some of the issues noted for nvi. -jr --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iQDVAwUBRK5sBkkkqUax7f6FAQJImAYAkE9Xx/L6DPH00FgWq9k++dJKPUKpxmPB +CnykuRNEtiVmSIk6hUtfv1SebxFO5hgbGkyngw9O6X20c+ifwcxPMj5wTZOUG8Y YPNhVKzaGCrm8Vtg6DDww5/CgKA8h93d8ft8z7+pD4gmmp8sS19B5SM2Egm28qgx SwV1Jzr9lgkeu91VsIMDo5oGaMiNO6GDpwRq8ra0RYZmW1DfsUg1Iv0FfP2DwdZq hSfea/hUW492FIbawfm1praROjSriIo8 =GX27 -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 16:17:24 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B2A916A4DA; Fri, 7 Jul 2006 16:17:24 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E6C543D58; Fri, 7 Jul 2006 16:17:24 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k67GHNe5009836; Fri, 7 Jul 2006 09:17:23 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k67GHNE6009829; Fri, 7 Jul 2006 09:17:23 -0700 Date: Fri, 7 Jul 2006 09:17:23 -0700 From: Brooks Davis To: Peter Jeremy Message-ID: <20060707161723.GA4842@odin.ac.hmc.edu> References: <44AD2569.9070007@rsu.ru> <44ADEBCC.70607@FreeBSD.org> <003c01c6a18b$937cbef0$3a00a8c0@carrera> <20060707091850.GA719@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <20060707091850.GA719@turion.vk2pj.dyndns.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: Doug Barton , freebsd-current@freebsd.org, Michael Bushkov Subject: Re: nss_ldap and openldap importing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 16:17:24 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 07, 2006 at 07:18:50PM +1000, Peter Jeremy wrote: > On Fri, 2006-Jul-07 10:06:55 +0400, Michael Bushkov wrote: > >1. Having nss_ldap in the source gives an ability to use nss_ldap right= =20 > >"out of the box" and equals it in rights with such nsswitch sources as N= IS=20 > >and DNS. If we have NIS in the base system, I don't see any reasons not = to=20 > >have nss_ldap. Besides, i'm sure, having nss_ldap in the base will make= =20 > >users feeling more comfortable when dealing with it. >=20 > I don't think this follows. Things like X and perl can be installed > from sysinstall with mininal effort. I'd prefer to make it easier > to install nss_ldap as a package than have it in the base system. IMO there's a substantial difference between something like X or perl and an authentication and authorization system in terms of the benefits of integration. Having X or perl broken because of a version mismatch or what not is annoying, but you can generally work around it particularly on a server. Having all access other than console single user broken due to breaking your login stuff is not so fixable. > >2. I guess, we'll have to rewrite nss_ldap by ourselves sooner or later= =20 > >(actually, I can do it), so current nss_ldap import can be viewed as the= =20 > >first stage of the plan. >=20 > It would seem cleaner to implement our own nss_ldap from scratch > rather than importing a GPL one and then replacing it. IMHO, having > the GPL nss_ldap in the tree would make it harder to import another > one. Once people start using nss_ldap, they are going to get very > picky about a replacement being bug-for-bug compatible. That's a valid concern. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFErokSXY6L6fI4GtQRAp8UAJ95jxmCDHLZSkreoFOgh7UeHTeC/ACgwaiC o7u2DKpI0nuiw4cXB0RIEJ8= =1fuJ -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 18:14:39 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9081516A4DD; Fri, 7 Jul 2006 18:14:39 +0000 (UTC) (envelope-from martin@gneto.com) Received: from mxfep03.bredband.com (mxfep03.bredband.com [195.54.107.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60F7943D45; Fri, 7 Jul 2006 18:14:37 +0000 (GMT) (envelope-from martin@gneto.com) Received: from ua-83-227-181-30.cust.bredbandsbolaget.se ([83.227.181.30] [83.227.181.30]) by mxfep02.bredband.com with ESMTP id <20060707041110.OSTY1253.mxfep02.bredband.com@ua-83-227-181-30.cust.bredbandsbolaget.se>; Fri, 7 Jul 2006 06:11:10 +0200 Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by ua-83-227-181-30.cust.bredbandsbolaget.se (Postfix) with ESMTP id 3AA8D67922; Fri, 7 Jul 2006 06:11:09 +0200 (CEST) Message-ID: <44ADDEE0.7080805@gneto.com> Date: Fri, 07 Jul 2006 06:11:12 +0200 From: Martin Nilsson User-Agent: Thunderbird 1.5.0.4 (X11/20060606) MIME-Version: 1.0 To: Mike Jakubik References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> In-Reply-To: <44AD6756.4070008@rogers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 18:14:39 -0000 Mike Jakubik wrote: > "Me too" However this is on a 6.1-R machine. It does not do any clock > speed changes, all power management is off in the bios. Its a Pentium D > 3.2Ghz using a supermicro PDSMi motherboard. This particular example > came up withe running a buildworld. > > --- > calcru: negative runtime of -171669 usec for pid 16 (yarrow) > calcru: negative runtime of -171669 usec for pid 16 (yarrow) > calcru: negative runtime of -171669 usec for pid 16 (yarrow) I have the same board and the same problem with 6.1. I have tested CURRENT a bit on the box and I can't remember seeing these errors there. The errors are present in both i386 and amd64 versions of FreeBSD, they are very easy to reproduce just boot and buildworld and you get at ton of these. I have lots of these boards not in production, so I'm happy to test patches if needed. /Martin From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 18:29:25 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D37316A4E7; Fri, 7 Jul 2006 18:29:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id B649943D7F; Fri, 7 Jul 2006 18:29:17 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k67ITD6k019594; Fri, 7 Jul 2006 14:29:14 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 7 Jul 2006 13:43:12 -0400 User-Agent: KMail/1.9.1 References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADC08B.8000408@rogers.com> In-Reply-To: <44ADC08B.8000408@rogers.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607071343.14205.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Fri, 07 Jul 2006 14:29:14 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1589/Fri Jul 7 10:37:51 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Mailman-Approved-At: Fri, 07 Jul 2006 18:32:07 +0000 Cc: Mike Jakubik , stable@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 18:29:25 -0000 On Thursday 06 July 2006 22:01, Mike Jakubik wrote: > I'm getting a ton of them now, and i found a way to reproduce them. > Basically i run a compile session in one terminal, say make buildkernel, > and run top in another. As soon as i run top, the messages appear, and > they seem to be synchronized with the refresh rate of top, 2 messages > per refresh. This is on a 6.1-STABLE as of today. That is partly because when you run top it queries the resource usage of the various processes via fill_kinfo_proc(). When you don't run top, no one is asking for the resource usage numbers, so the kernel doesn't waste time calculating them. > --- > calcru: negative runtime of -261273 usec for pid 12 (swi4: clock) > calcru: negative runtime of -261273 usec for pid 12 (swi4: clock) > calcru: negative runtime of -259691 usec for pid 12 (swi4: clock) > ... In both cases your errors are for a long-running kernel process that's been up since boot. What's the uptime on your box? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 18:45:05 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CE5F16A4DE; Fri, 7 Jul 2006 18:45:04 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A43E43D45; Fri, 7 Jul 2006 18:45:04 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 6291811514; Fri, 7 Jul 2006 14:44:25 -0400 (EDT) Message-ID: <44AEABC8.5010609@rogers.com> Date: Fri, 07 Jul 2006 14:45:28 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Martin Nilsson References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADDEE0.7080805@gneto.com> In-Reply-To: <44ADDEE0.7080805@gneto.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: freebsd-current@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 18:45:05 -0000 Martin Nilsson wrote: > I have the same board and the same problem with 6.1. I have tested > CURRENT a bit on the box and I can't remember seeing these errors there. > > The errors are present in both i386 and amd64 versions of FreeBSD, > they are very easy to reproduce just boot and buildworld and you get > at ton of these. I have lots of these boards not in production, so I'm > happy to test patches if needed. Oddly enough i have the same board in production, but it's using a 2.6GHz CPU, and running in amd64 mode. It does not exhibit this problem. I wonder if its a bios issue, this new board has 1.1a, the amd64 box may be a little older. Whats your bios version? From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 18:43:28 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C0E516A51A; Fri, 7 Jul 2006 18:43:28 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D13343D58; Fri, 7 Jul 2006 18:43:26 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 1807411446; Fri, 7 Jul 2006 14:42:47 -0400 (EDT) Message-ID: <44AEAB61.6000104@rogers.com> Date: Fri, 07 Jul 2006 14:43:45 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: John Baldwin References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADC08B.8000408@rogers.com> <200607071343.14205.jhb@freebsd.org> In-Reply-To: <200607071343.14205.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No X-Mailman-Approved-At: Fri, 07 Jul 2006 18:46:16 +0000 Cc: stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 18:43:28 -0000 John Baldwin wrote: > That is partly because when you run top it queries the resource usage of the > various processes via fill_kinfo_proc(). When you don't run top, no one is > asking for the resource usage numbers, so the kernel doesn't waste time > calculating them. > > Right, also running ps has the same effect. But why do these messages occur? > In both cases your errors are for a long-running kernel process that's been up > since boot. What's the uptime on your box? > > Not sure what the uptime was, this box is not in production yet so i shut it off regularly. I would guess under an hour. From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 19:55:15 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7680C16A4DF; Fri, 7 Jul 2006 19:55:15 +0000 (UTC) (envelope-from mi+mx@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6862343D64; Fri, 7 Jul 2006 19:55:14 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k67JtCBB099973 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 7 Jul 2006 15:55:13 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from [172.21.130.86] (mx-broadway [38.98.68.18]) by corbulon.video-collage.com (8.13.6/8.13.6) with ESMTP id k67Jt6n4030005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Jul 2006 15:55:06 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: Robert Watson Date: Fri, 7 Jul 2006 15:55:00 -0400 User-Agent: KMail/1.9.1 References: <200607010009.09231@aldan> <200607051142.28352.jhb@freebsd.org> <20060705171517.H18236@fledge.watson.org> In-Reply-To: <20060705171517.H18236@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200607071555.00993.mi+mx@aldan.algebra.com> X-Virus-Scanned: ClamAV 0.88/1587/Thu Jul 6 16:55:48 2006 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 X-Mailman-Approved-At: Fri, 07 Jul 2006 20:05:45 +0000 Cc: Peter Jeremy , freebsd-current@freebsd.org, Joerg Wunsch Subject: Re: weird limitation on the system's binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 19:55:15 -0000 ÓĹŇĹÄÁ 05 ĚÉĐĹÎŘ 2006 12:18, Robert Watson ÎÁĐÉÓÁ×: > Perhaps the world has changed since that time, but those sound like > pretty good reasons to me. šSo these are my recollections, but since I'm > not an expert in our toolchain bits, I could be off in the woods somewhere. Can we, perhaps start small and make the libiberty piece centrally available (and of the most recent version)? There is even a port of (devel/gnulibiberty), which its maintainer (CC-ed), I'm sure, will be glad to see obsoleted... We are currently building it four times: /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/binutils/libiberty/libiberty.a /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_tools/libiberty.a /usr/obj/usr/src/gnu/usr.bin/binutils/libiberty/libiberty.a /usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/libiberty.a And installing none... Halving that, and installing the result to be usable by ports would be a decent improvement, would not it? -mi From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 20:41:54 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D49416A4DE; Fri, 7 Jul 2006 20:41:54 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A5EC43D49; Fri, 7 Jul 2006 20:41:53 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [IPv6:::1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k67KdmlP049424; Fri, 7 Jul 2006 14:39:48 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 07 Jul 2006 14:39:53 -0600 (MDT) Message-Id: <20060707.143953.-345494968.imp@bsdimp.com> To: brooks@one-eyed-alien.net From: "M. Warner Losh" In-Reply-To: <20060707015458.GC500@odin.ac.hmc.edu> References: <44AD2569.9070007@rsu.ru> <44AD4D27.3060109@FreeBSD.org> <20060707015458.GC500@odin.ac.hmc.edu> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: dougb@freebsd.org, bushman@rsu.ru, freebsd-current@freebsd.org Subject: Re: nss_ldap and openldap importing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 20:41:54 -0000 In message: <20060707015458.GC500@odin.ac.hmc.edu> Brooks Davis writes: : On Thu, Jul 06, 2006 at 10:49:27AM -0700, Doug Barton wrote: : > Michael Bushkov wrote: : > > Hi, : > > I'm a FreeBSD SoC 2006 student, I work on the nsswitch/ldap/caching : > > daemon stuff this summer. One of the tasks, that I have to do is to : > > import nss_ldap into the source tree. I just want to check the situation : > > with licenses. : > > : > > nss_ldap uses OpenLDAP library, which uses OpenLDAP license : > > (http://www.openldap.org/software/release/license.html). OpenLDAP : > > license seems to be BSD-compatible - so there seems to be no problems : > > with importing it into the source tree. : > > : > > nss_ldap itself uses LGPL. As we use nss_ldap only as dynamic library, : > > which is used in the "larger work" (which FreeBSD is), it can be also : > > included into the source tree. So, we can import nss_ldap, by directly : > > importing (with some specific changes, though) it and OpenLDAP into the : > > source tree, can we? Just want to be sure that I understand licensing : > > situation correctly. : > : > My understanding is that we are generally trying to avoid importing any new : > code that has any sort of GPL license. That would certainly be my (personal) : > preference in any case. : : Unless we have someone crediably committed to rewritting nss_ldap I : think this is a good place to make an exception. We can always remove : it later if an implementation exists, but we could really use better : integration with ldap. Especially if this is integrated into the system such that it is easy to disable.. Warner From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 20:47:45 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6ECBD16A4DA; Fri, 7 Jul 2006 20:47:45 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0D0743D6A; Fri, 7 Jul 2006 20:47:44 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k67KlgWK028817; Fri, 7 Jul 2006 13:47:42 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k67Klg0w028816; Fri, 7 Jul 2006 13:47:42 -0700 Date: Fri, 7 Jul 2006 13:47:42 -0700 From: Brooks Davis To: "M. Warner Losh" Message-ID: <20060707204742.GA28445@odin.ac.hmc.edu> References: <44AD2569.9070007@rsu.ru> <44AD4D27.3060109@FreeBSD.org> <20060707015458.GC500@odin.ac.hmc.edu> <20060707.143953.-345494968.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline In-Reply-To: <20060707.143953.-345494968.imp@bsdimp.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: dougb@freebsd.org, bushman@rsu.ru, freebsd-current@freebsd.org Subject: Re: nss_ldap and openldap importing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 20:47:45 -0000 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 07, 2006 at 02:39:53PM -0600, M. Warner Losh wrote: > In message: <20060707015458.GC500@odin.ac.hmc.edu> > Brooks Davis writes: > : On Thu, Jul 06, 2006 at 10:49:27AM -0700, Doug Barton wrote: > : > Michael Bushkov wrote: > : > > Hi, > : > > I'm a FreeBSD SoC 2006 student, I work on the nsswitch/ldap/caching > : > > daemon stuff this summer. One of the tasks, that I have to do is to > : > > import nss_ldap into the source tree. I just want to check the situ= ation > : > > with licenses. > : > >=20 > : > > nss_ldap uses OpenLDAP library, which uses OpenLDAP license > : > > (http://www.openldap.org/software/release/license.html). OpenLDAP > : > > license seems to be BSD-compatible - so there seems to be no proble= ms > : > > with importing it into the source tree. > : > >=20 > : > > nss_ldap itself uses LGPL. As we use nss_ldap only as dynamic libra= ry, > : > > which is used in the "larger work" (which FreeBSD is), it can be al= so > : > > included into the source tree. So, we can import nss_ldap, by direc= tly > : > > importing (with some specific changes, though) it and OpenLDAP into= the > : > > source tree, can we? Just want to be sure that I understand licensi= ng > : > > situation correctly. > : >=20 > : > My understanding is that we are generally trying to avoid importing a= ny new > : > code that has any sort of GPL license. That would certainly be my (pe= rsonal) > : > preference in any case. > :=20 > : Unless we have someone crediably committed to rewritting nss_ldap I > : think this is a good place to make an exception. We can always remove > : it later if an implementation exists, but we could really use better > : integration with ldap. >=20 > Especially if this is integrated into the system such that it is easy > to disable.. It should be pretty easy to have a WITH/WITHOUT_LDAP and _NSS_LDAP options. We're only talking about two directories at this point. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFErshtXY6L6fI4GtQRAoP5AKC9EUsHEMw9CJcycEQAyDXzIVxmSgCgkLqK rXQCDi/KYIJcE0LrwjtfLYY= =uZ/q -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 21:11:29 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3525316A4DD; Fri, 7 Jul 2006 21:11:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9492043D45; Fri, 7 Jul 2006 21:11:28 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k67LB3Bo022530; Fri, 7 Jul 2006 17:11:03 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Mikhail Teterin Date: Fri, 7 Jul 2006 17:08:42 -0400 User-Agent: KMail/1.9.1 References: <200607010009.09231@aldan> <20060705171517.H18236@fledge.watson.org> <200607071555.00993.mi+mx@aldan.algebra.com> In-Reply-To: <200607071555.00993.mi+mx@aldan.algebra.com> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200607071708.43790.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Fri, 07 Jul 2006 17:11:03 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1589/Fri Jul 7 10:37:51 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Peter Jeremy , freebsd-current@freebsd.org, Robert Watson , Joerg Wunsch Subject: Re: weird limitation on the system's binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 21:11:29 -0000 On Friday 07 July 2006 15:55, Mikhail Teterin wrote: > =D3=C5=D2=C5=C4=C1 05 =CC=C9=D0=C5=CE=D8 2006 12:18, Robert Watson =CE=C1= =D0=C9=D3=C1=D7: > > Perhaps the world has changed since that time, but those sound like > > pretty good reasons to me. =9ASo these are my recollections, but since = I'm > > not an expert in our toolchain bits, I could be off in the woods=20 somewhere. >=20 > Can we, perhaps start small and make the libiberty piece centrally availa= ble=20 > (and of the most recent version)? >=20 > There is even a port of (devel/gnulibiberty), which its maintainer (CC-ed= ),=20 > I'm sure, will be glad to see obsoleted... >=20 > We are currently building it four times: >=20 > /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/binutils/libiberty/libiberty.a > /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_tools/libiberty.a > /usr/obj/usr/src/gnu/usr.bin/binutils/libiberty/libiberty.a > /usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/libiberty.a >=20 > And installing none... >=20 > Halving that, and installing the result to be usable by ports would be a= =20 > decent improvement, would not it? Only if it doesn't suffer from all the same problems as libbfd.a. =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 06:13:08 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E524516A4DA; Sat, 8 Jul 2006 06:13:08 +0000 (UTC) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (uriah.heep.sax.de [213.240.137.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id F34A243D4C; Sat, 8 Jul 2006 06:13:07 +0000 (GMT) (envelope-from j@uriah.heep.sax.de) Received: from localhost (localhost [127.0.0.1]) by uriah.heep.sax.de (Postfix) with ESMTP id 20F8284F; Sat, 8 Jul 2006 08:13:06 +0200 (MET DST) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by localhost (AvMailGate-2.0.2-10) id 28525-77D3CBC1; Sat, 08 Jul 2006 08:13:05 +0200 Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (Postfix) with ESMTP id DF11D85C; Sat, 8 Jul 2006 08:13:01 +0200 (MET DST) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (Postfix) with ESMTP; Sat, 8 Jul 2006 08:13:01 +0200 (MET DST) Received: (from j@localhost) by uriah.heep.sax.de (8.13.4/8.13.1/Submit) id k686Cx2W028521; Sat, 8 Jul 2006 08:12:59 +0200 (MET DST) (envelope-from j) Date: Sat, 8 Jul 2006 08:12:59 +0200 From: Joerg Wunsch To: John Baldwin Message-ID: <20060708061259.GD84700@uriah.heep.sax.de> Mail-Followup-To: Joerg Wunsch , John Baldwin , Mikhail Teterin , Robert Watson , freebsd-current@freebsd.org, Peter Jeremy References: <200607010009.09231@aldan> <20060705171517.H18236@fledge.watson.org> <200607071555.00993.mi+mx@aldan.algebra.com> <200607071708.43790.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200607071708.43790.jhb@freebsd.org> X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 User-Agent: Mutt/1.5.11 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on uriah.heep.sax.de X-Spam-Level: X-Spam-Status: No, score=0.0 required=6.5 tests=none autolearn=failed version=3.0.2 X-AntiVirus: checked by AntiVir MailGate (version: 2.0.2-10; AVE: 6.33.0.19; VDF: 6.33.0.62; host: uriah.heep.sax.de) Cc: Peter Jeremy , Mikhail Teterin , freebsd-current@freebsd.org, Robert Watson Subject: Re: weird limitation on the system's binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joerg Wunsch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 06:13:09 -0000 As John Baldwin wrote: > > Halving that, and installing the result to be usable by ports > > would be a decent improvement, would not it? > Only if it doesn't suffer from all the same problems as libbfd.a. What problems, btw.? Only curious. Historical note: one of my ports (devel/avarice) needs a libbfd.a, so I once made that port. As libbfd requires a GNU libiberty (it uses internal libiberty functions that are not documented, ick!), I also made that port. I don't mind seeing that one go away though. Neither of these two ports has been anything like a hobby for me. ;-) -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 06:37:04 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D21D616A4DA for ; Sat, 8 Jul 2006 06:37:04 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BA6C43D49 for ; Sat, 8 Jul 2006 06:37:04 +0000 (GMT) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id 1861278C1D; Sat, 8 Jul 2006 06:37:02 +0000 (GMT) Date: Sat, 8 Jul 2006 06:37:01 +0000 From: John Birrell To: freebsd-current@freebsd.org Message-ID: <20060708063701.GA61721@what-creek.com> References: <200607010009.09231@aldan> <20060701115508.GC8447@turion.vk2pj.dyndns.org> <200607011508.27920@aldan> <200607051142.28352.jhb@freebsd.org> <20060705171517.H18236@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060705171517.H18236@fledge.watson.org> User-Agent: Mutt/1.4.2.1i Subject: Re: weird limitation on the system's binutils X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 06:37:04 -0000 On Wed, Jul 05, 2006 at 05:18:07PM +0100, Robert Watson wrote: > My recollection is that we got to where we are today precisely because the > various GNU tools (gdb, gcc, etc) relied on versions of bfd "as cut" at the > point where the tool revisions were released. This meant that they could > not share bfd versions between tools, since tools were often released at > different dates, and the versions of bfd with different tools were > incompatible. The conclusion was that by statically linking the specific > compatible versions into the binaries, and by not shipping a specific bfd > as part of the base system, we avoided numerous compatibility issues, as > well as avoided committing consumers of the system to a particular bfd > revision that might be incompatible with what they want to run in the way > of their own cross tools, etc. Perhaps the world has changed since that > time, but those sound like pretty good reasons to me. So these are my > recollections, but since I'm not an expert in our toolchain bits, I could > be off in the woods somewhere. Historical note: I once had support for multiple architectures built into FreeBSD's GNU tools with the host architecture set as the default. I was heading for being able to build Windows programs on FreeBSD as well. It is (or at least was) possible to do, but FreeBSD has has the approach of tools built for the host machine arch or cross-built tools built for the target architecture. With support for all the architectures that the GNU tools support built in by default, FreeBSD makes a great development system for all sorts of weird (and wonderful?) architectures. I used to build MVME68K code on FreeBSD. Back in the good old days. -- John Birrell From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 06:40:43 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE3FD16A4DA; Sat, 8 Jul 2006 06:40:43 +0000 (UTC) (envelope-from mb@imp.ch) Received: from smtp.imp.ch (mx2.imp.ch [157.161.9.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 679F243D45; Sat, 8 Jul 2006 06:40:42 +0000 (GMT) (envelope-from mb@imp.ch) Received: from godot.imp.ch (godot.imp.ch [157.161.4.8]) by smtp.imp.ch (8.13.7/8.13.7/Submit) with ESMTP id k686ecSd017359; Sat, 8 Jul 2006 08:40:40 +0200 (CEST) (envelope-from mb@imp.ch) Date: Sat, 8 Jul 2006 08:40:38 +0200 (CEST) From: Martin Blapp To: freebsd-current@freebsd.org In-Reply-To: <200607072236.55319.jhb@freebsd.org> Message-ID: <20060708081419.W14714@godot.imp.ch> References: <20060708020700.A14714@godot.imp.ch> <200607072236.55319.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.57 on 157.161.9.65 Cc: Subject: Re: Please help reviewing ! Got another crash because of the ttymodem() / ttyclose() race X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 06:40:44 -0000 Hi, > Yes.. did you see my reply on the mailing list Ouch ? No I missed that ! Thanks. I just read it. > I'm not sure that the proctree_lock should protect t_pgrp as that is part > of the tty structure, not process groups or session structures. Hmm ? In /usr/src/sys/kern/tty.c:1215 we copy in ttioctl() the pointers of p->p_session and p->p_pgrp to the tty structure. 1215 tp->t_session = p->p_session; 1216 tp->t_pgrp = p->p_pgrp; 1217 SESS_LOCK(p->p_session); It looks to me that we have to protect it with the locks of the process groups or session structures since its only a copy of the pointer, and not an exact copy. Else I wouldn't had any crashes - this is the mess. Or do I understand something completly wrong ? >I think probably it should be protected by Giant for now until the tty subsystem >is locked. Also, the ttyinfo() part will not work since it tries to >acquire a mutex (PGRP_LOCK()) while holding a spin mutex (sched_lock). Ok, fixed. Does it look better now ? Btw. this version is now running for three days without any crashes on four SMP boxes. Rocking stable so far. >perhaps instead we need to expand Giant to cover it until the tty subsystem is >locked? How would you do that ? Martin From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 06:44:17 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F8C316A4DD for ; Sat, 8 Jul 2006 06:44:17 +0000 (UTC) (envelope-from mb@imp.ch) Received: from smtp.imp.ch (mx2.imp.ch [157.161.9.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9815143D45 for ; Sat, 8 Jul 2006 06:44:16 +0000 (GMT) (envelope-from mb@imp.ch) Received: from godot.imp.ch (godot.imp.ch [157.161.4.8]) by smtp.imp.ch (8.13.7/8.13.7/Submit) with ESMTP id k686iCst020415 for ; Sat, 8 Jul 2006 08:44:15 +0200 (CEST) (envelope-from mb@imp.ch) Date: Sat, 8 Jul 2006 08:44:12 +0200 (CEST) From: Martin Blapp To: freebsd-current@freebsd.org In-Reply-To: <20060708081419.W14714@godot.imp.ch> Message-ID: <20060708084356.R14714@godot.imp.ch> References: <20060708020700.A14714@godot.imp.ch> <200607072236.55319.jhb@freebsd.org> <20060708081419.W14714@godot.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.57 on 157.161.9.65 Subject: Re: Please help reviewing ! Got another crash because of the ttymodem() / ttyclose() race X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 06:44:17 -0000 > > Ok, fixed. Does it look better now ? > here's the link again. http://mx.imp.ch/patches/patch-tty.t_pgrp.diff From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 09:50:36 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56DC216A4E5 for ; Sat, 8 Jul 2006 09:50:36 +0000 (UTC) (envelope-from joel@FreeBSD.org) Received: from av7-1-sn3.vrr.skanova.net (av7-1-sn3.vrr.skanova.net [81.228.9.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84A9843D4C for ; Sat, 8 Jul 2006 09:50:35 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: by av7-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 967273814C; Sat, 8 Jul 2006 11:24:01 +0200 (CEST) Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av7-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 8851337E82; Sat, 8 Jul 2006 11:24:01 +0200 (CEST) Received: from 213-65-28-217-no21.tbcn.telia.com (213-65-28-217-no21.tbcn.telia.com [213.65.28.217]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 9284037E43; Sat, 8 Jul 2006 11:50:30 +0200 (CEST) From: Joel Dahl To: pyunyh@gmail.com In-Reply-To: <20060705114853.GB73705@cdnetworks.co.kr> References: <20060705114853.GB73705@cdnetworks.co.kr> Content-Type: text/plain Date: Sat, 08 Jul 2006 11:50:29 +0200 Message-Id: <1152352229.715.4.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Call for stge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 09:50:36 -0000 On Wed, 2006-07-05 at 20:48 +0900, Pyun YongHyeon wrote: > Hi, > > This is a ported driver from NetBSD stge(4). It supports the > following GigE adapters. I've tried your patch with RELENG_6. This is an integrated IC Plus NIC on a Abit AX8 motherboard. No problems so far... # dmesg: stge0: port 0xea00-0xeaff mem 0xdfffd000-0xdfffd0ff irq 22 at device 14.0 on pci0 stge0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xea00 miibus1: on stge0 ukphy0: on miibus1 ukphy0: OUI 0x0090c3, model 0x0008, rev. 0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto stge0: bpf attached stge0: Ethernet address: 00:50:8d:d3:54:cc ioapic0: routing intpin 22 (PCI IRQ 22) to vector 53 stge0: [MPSAFE] # pciconf -lv: stge0@pci0:14:0: class=0x020000 card=0x1416147b chip=0x102313f0 rev=0x41 hdr=0x00 vendor = 'Sundance Technology Inc' class = network subclass = ethernet -- Joel From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 15:14:26 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF63216A4DD; Sat, 8 Jul 2006 15:14:26 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 201E143D45; Sat, 8 Jul 2006 15:14:25 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.180.165] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu4) with ESMTP (Nemesis), id 0ML21M-1FzEVk1pMP-0005CA; Sat, 08 Jul 2006 17:14:24 +0200 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Sat, 8 Jul 2006 17:14:17 +0200 User-Agent: KMail/1.9.1 References: <200606252139.15862.max@love2party.net> In-Reply-To: <200606252139.15862.max@love2party.net> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2218258.qSTYUWII6N"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607081714.23266.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-current@freebsd.org Subject: Re: Call for Status Reports: 07/07 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 15:14:26 -0000 --nextPart2218258.qSTYUWII6N Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 25 June 2006 21:39, I wrote: > All, > > it's time for the Status Reports for the second quater of 2006. During t= he > last three month a lot of progress has been made. FreeBSD 6.1 and 5.5 are > released, a new round of Google's Summer of Code has been started, and a > very productive Developer Summit took place during BSDCan. On top of tha= t, > we are now running on Sun's new architecture and a lot of progress has be= en > made for the arm platform, making FreeBSD more viable in the embedded > market. > > We hope that all your projects made good progress as well and would like = to > hear about it. Please share your news and progress over the last three > month with us. Submission are due by 7 July, 2006. > > Once again, submissions are not limited to FreeBSD developers. We will > happily include non-code projects of any kind as long as it is FreeBSD > related. > > For previous reports and submission details, please see: > http://www.freebsd.org/news/status/ Last call, if you have something to submit but didn't yet, let me know *now= *=20 about it and send in the report ASAP!! We have a really good turnout already, so we won't be waiting much longer. Thanks. =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 --nextPart2218258.qSTYUWII6N Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEr8vPXyyEoT62BG0RArPWAJ9C2D8XODu2HfhfDaJJDlrLvCvjNgCcDXdI mKxe7lFfK6kGjJmR2mpLGao= =MqDA -----END PGP SIGNATURE----- --nextPart2218258.qSTYUWII6N-- From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 15:28:10 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9223016A5F2; Sat, 8 Jul 2006 15:28:04 +0000 (UTC) (envelope-from rodrigc@crodrigues.org) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.192.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F86943D55; Sat, 8 Jul 2006 15:28:04 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from c-71-233-168-2.hsd1.ma.comcast.net ([71.233.168.2]) by comcast.net (rwcrmhc13) with ESMTP id <20060708152802m1300sb44qe>; Sat, 8 Jul 2006 15:28:03 +0000 Received: from c-71-233-168-2.hsd1.ma.comcast.net (localhost [127.0.0.1]) by c-71-233-168-2.hsd1.ma.comcast.net (8.13.6/8.13.1) with ESMTP id k68FS1P9003696; Sat, 8 Jul 2006 11:28:02 -0400 (EDT) (envelope-from rodrigc@c-71-233-168-2.hsd1.ma.comcast.net) Received: (from rodrigc@localhost) by c-71-233-168-2.hsd1.ma.comcast.net (8.13.6/8.13.1/Submit) id k68FS1s2003695; Sat, 8 Jul 2006 11:28:01 -0400 (EDT) (envelope-from rodrigc) Date: Sat, 8 Jul 2006 11:28:01 -0400 From: Craig Rodrigues To: freebsd-current@freebsd.org Message-ID: <20060708152801.GA3671@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: freebsd-arch@freebsd.org Subject: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 15:28:10 -0000 Hi, One of the pet peeves I have with FreeBSD is that if I have a device with a local filesystem that I want to mount, I need to explicitly know what type of filesystem is on the device in order to mount it from the command-line. For example, mount -t cd9660 mount -t udf mount -t ext2fs mount -t msdosfs Where this is particularly annoying is if I have multiple USB thumb drives with different filesystems on them. What I usually end up doing is something like: file - < /dev/ad0s4 to figure out the filesystem type, and then mount -t [whatever] to mount it. What I would like to do is: mount /dev/ad0s4 /mnt and if I do not specify a filesystem type with -t, the mount program should "magically" figure out how to mount the disk. This is closer to how the mount program behaves on Linux for example. I've come up with a patch that does this, by interpreting an fstype of "" as: - starting with "ufs", iterate over all the local filesystem types that we know about, and try to mount the device Comments? Index: sys/kern/vfs_mount.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_mount.c,v retrieving revision 1.228 diff -u -u -r1.228 vfs_mount.c --- sys/kern/vfs_mount.c 27 Jun 2006 14:46:31 -0000 1.228 +++ sys/kern/vfs_mount.c 8 Jul 2006 14:01:52 -0000 @@ -567,6 +567,34 @@ } static int +vfs_domount_try(struct thread *td, char *fspath, int fsflags, + void *fsdata) +{ + struct vfsconf *vfsp; + int error; + printf("Mounting: %s first\n", "ufs"); + error = vfs_domount(td, "ufs", fspath, fsflags, fsdata); + if (error == 0) { + printf("successfully mounted: %s\n", "ufs"); + } + if (error != 0) { + TAILQ_FOREACH(vfsp, &vfsconf, vfc_list) { + if ((strcmp("ufs", vfsp->vfc_name) != 0) && + !(vfsp->vfc_flags & VFCF_NETWORK) && + !(vfsp->vfc_flags & VFCF_SYNTHETIC)) { + printf("Mounting: %s\n", vfsp->vfc_name); + error = vfs_domount(td, vfsp->vfc_name, fspath, fsflags, fsdata); + if (error == 0) { + printf("successfully mounted: %s\n", vfsp->vfc_name); + break; + } + } + } + } + return error; +} + +static int vfs_donmount(struct thread *td, int fsflags, struct uio *fsoptions) { struct vfsoptlist *optlist; @@ -596,7 +624,7 @@ */ fstypelen = 0; error = vfs_getopt(optlist, "fstype", (void **)&fstype, &fstypelen); - if (error || fstype[fstypelen - 1] != '\0') { + if (error || (fstypelen > 0 && fstype[fstypelen - 1] != '\0')) { error = EINVAL; if (errmsg != NULL) strncpy(errmsg, "Invalid fstype", errmsg_len); @@ -606,6 +634,7 @@ error = vfs_getopt(optlist, "fspath", (void **)&fspath, &fspathlen); if (error || fspath[fspathlen - 1] != '\0') { error = EINVAL; + printf("%s:%d EINVAL\n", __FILE__, __LINE__); if (errmsg != NULL) strncpy(errmsg, "Invalid fspath", errmsg_len); goto bail; @@ -686,7 +715,14 @@ } mtx_lock(&Giant); - error = vfs_domount(td, fstype, fspath, fsflags, optlist); + if (fstypelen > 1) { + /* fstype was specified, go directly to vfs_domount() */ + error = vfs_domount(td, fstype, fspath, fsflags, optlist); + } + else { + /* we do not know the fstype, try to probe for it */ + error = vfs_domount_try(td, fspath, fsflags, optlist); + } mtx_unlock(&Giant); bail: /* copyout the errmsg */ Index: sbin/mount/mount.c =================================================================== RCS file: /home/ncvs/src/sbin/mount/mount.c,v retrieving revision 1.87 diff -u -u -r1.87 mount.c --- sbin/mount/mount.c 10 Jun 2006 01:44:57 -0000 1.87 +++ sbin/mount/mount.c 8 Jul 2006 14:14:47 -0000 @@ -200,7 +200,7 @@ all = init_flags = 0; vfslist = NULL; - vfstype = "ufs"; + vfstype = ""; while ((ch = getopt(argc, argv, "adF:fo:prwt:uv")) != -1) switch (ch) { case 'a': Index: sbin/mount/mount_fs.c =================================================================== RCS file: /home/ncvs/src/sbin/mount/mount_fs.c,v retrieving revision 1.2 diff -u -u -r1.2 mount_fs.c --- sbin/mount/mount_fs.c 13 Nov 2005 01:27:57 -0000 1.2 +++ sbin/mount/mount_fs.c 8 Jul 2006 14:14:47 -0000 @@ -50,6 +50,7 @@ #include #include +#include #include #include @@ -82,8 +83,9 @@ int iovlen; int mntflags = 0; int ch; - char *dev, *dir, mntpath[MAXPATHLEN]; + char *dev, *dir, mntpath[MAXPATHLEN], frompath[MAXPATHLEN]; char fstype[32]; + //char errmsg[1024] = { 0 }; char *p, *val; int ret; @@ -121,15 +123,35 @@ dir = argv[1]; (void)checkpath(dir, mntpath); + if (realpath(dev, frompath) != NULL) { + dev = frompath; + } (void)rmslashes(dev, dev); build_iovec(&iov, &iovlen, "fstype", fstype, (size_t)-1); build_iovec(&iov, &iovlen, "fspath", mntpath, (size_t)-1); build_iovec(&iov, &iovlen, "from", dev, (size_t)-1); - + //build_iovec(&iov, &iovlen, "errmsg", errmsg, sizeof(errmsg)); + printf("fstype: %s, fspath: %s, from: %s\n", fstype, mntpath, dev); +retry: ret = nmount(iov, iovlen, mntflags); - if (ret < 0) - err(1, "%s", dev); + if (ret < 0 && iov[1].iov_len == 0) { + /* + * If an fstype was not specified, and nmount() failed, + * try again with an fstype of "ufs". This is for backwards + * compatibility with older kernels which do not support + * do_mount_try() with an fstype of "". + */ + iov[1].iov_base = strdup("ufs"); + iov[1].iov_len = 4; + printf("Trying again....\n"); + goto retry; + } + + if (ret < 0) { + //err(1, "%s %s", dev, errmsg); + //err(1, "%s", dev); + } return (ret); } -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 15:37:33 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92A4B16A4E5; Sat, 8 Jul 2006 15:37:33 +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 121E143D64; Sat, 8 Jul 2006 15:37:31 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id EF87A2083; Sat, 8 Jul 2006 17:37:26 +0200 (CEST) X-Spam-Tests: none X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id E276A2082; Sat, 8 Jul 2006 17:37:26 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id AD2EF33C28; Sat, 8 Jul 2006 17:37:26 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Craig Rodrigues References: <20060708152801.GA3671@crodrigues.org> Date: Sat, 08 Jul 2006 17:37:26 +0200 In-Reply-To: <20060708152801.GA3671@crodrigues.org> (Craig Rodrigues's message of "Sat, 8 Jul 2006 11:28:01 -0400") Message-ID: <86ac7krtu1.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 15:37:33 -0000 Craig Rodrigues writes: > I've come up with a patch that does this, by interpreting > an fstype of "" as: > - starting with "ufs", iterate over all the local filesystem types > that we know about, and try to mount the device What about cases where there may be several matching file systems? For instance, a clean ext3 file system is also a valid ext2 file system (and vice versa). DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 16:05:53 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B362016A4DA; Sat, 8 Jul 2006 16:05:53 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6568F43D45; Sat, 8 Jul 2006 16:05:53 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.199] ([10.0.0.199]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k68G5oV6075714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Jul 2006 09:05:51 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <44AFD7DF.8090002@errno.com> Date: Sat, 08 Jul 2006 09:05:51 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530) MIME-Version: 1.0 To: Craig Rodrigues References: <20060708152801.GA3671@crodrigues.org> In-Reply-To: <20060708152801.GA3671@crodrigues.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 16:05:53 -0000 Craig Rodrigues wrote: > Hi, > > One of the pet peeves I have with FreeBSD is that > if I have a device with a local filesystem that I want to mount, > I need to explicitly know what type of filesystem is on the > device in order to mount it from the command-line. > > For example, > > mount -t cd9660 > mount -t udf > mount -t ext2fs > mount -t msdosfs > > Where this is particularly annoying is if I have multiple > USB thumb drives with different filesystems on them. > > What I usually end up doing is something like: > file - < /dev/ad0s4 > > to figure out the filesystem type, and then mount -t [whatever] to mount it. > > What I would like to do is: > > mount /dev/ad0s4 /mnt > > and if I do not specify a filesystem type with -t, the mount > program should "magically" figure out how to mount the disk. > This is closer to how the mount program behaves on Linux for example. > > I've come up with a patch that does this, by interpreting > an fstype of "" as: > - starting with "ufs", iterate over all the local filesystem types > that we know about, and try to mount the device > > Comments? <...patch deleted...> Linux has -t auto; haven't looked at how it works. It appears you just try a series of fs types; can't you read the device to infer the filesystem? Sam From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 16:14:34 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA9F116A4DA; Sat, 8 Jul 2006 16:14:34 +0000 (UTC) (envelope-from rodrigc@crodrigues.org) Received: from rwcrmhc15.comcast.net (rwcrmhc15.comcast.net [204.127.192.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63FAE43D46; Sat, 8 Jul 2006 16:14:34 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from c-71-233-168-2.hsd1.ma.comcast.net ([71.233.168.2]) by comcast.net (rwcrmhc15) with ESMTP id <20060708160932m15004em26e>; Sat, 8 Jul 2006 16:09:32 +0000 Received: from c-71-233-168-2.hsd1.ma.comcast.net (localhost [127.0.0.1]) by c-71-233-168-2.hsd1.ma.comcast.net (8.13.6/8.13.1) with ESMTP id k68G9Vv6003907; Sat, 8 Jul 2006 12:09:31 -0400 (EDT) (envelope-from rodrigc@c-71-233-168-2.hsd1.ma.comcast.net) Received: (from rodrigc@localhost) by c-71-233-168-2.hsd1.ma.comcast.net (8.13.6/8.13.1/Submit) id k68G9VS0003906; Sat, 8 Jul 2006 12:09:31 -0400 (EDT) (envelope-from rodrigc) Date: Sat, 8 Jul 2006 12:09:31 -0400 From: Craig Rodrigues To: freebsd-current@freebsd.org Message-ID: <20060708160931.GA3871@crodrigues.org> References: <20060708152801.GA3671@crodrigues.org> <86ac7krtu1.fsf@xps.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86ac7krtu1.fsf@xps.des.no> User-Agent: Mutt/1.4.2.1i Cc: freebsd-arch@freebsd.org Subject: Re: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 16:14:35 -0000 On Sat, Jul 08, 2006 at 05:37:26PM +0200, Dag-Erling Smrgrav wrote: > What about cases where there may be several matching file systems? > For instance, a clean ext3 file system is also a valid ext2 file > system (and vice versa). Currently, FreeBSD can only mount ext2 with mount -t ext2fs. A better example would probably be udf and cd9660 filesystems. Right now the logic is to iterate over the list of known local filesystems (always starting with "ufs"), skipping over "synthetic" and "network" filesystems, i.e. similar to the list produced by lsvfs: Filesystem Refs Flags -------------------------------- ----- --------------- ufs 8 reiserfs 0 read-only nfs4 0 network ext2fs 0 ntfs 0 cd9660 0 read-only procfs 1 synthetic msdosfs 0 xfs 0 devfs 1 synthetic nfs 0 network The first matching filesystem wins....not perfect, but maybe good enough for a lot of cases. mount -t always works if you want to specify the fstype. -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 16:17:21 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2049616A4DA; Sat, 8 Jul 2006 16:17:21 +0000 (UTC) (envelope-from rodrigc@crodrigues.org) Received: from rwcrmhc15.comcast.net (rwcrmhc15.comcast.net [204.127.192.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B96243D45; Sat, 8 Jul 2006 16:17:20 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from c-71-233-168-2.hsd1.ma.comcast.net ([71.233.168.2]) by comcast.net (rwcrmhc15) with ESMTP id <20060708161719m15004h5pse>; Sat, 8 Jul 2006 16:17:19 +0000 Received: from c-71-233-168-2.hsd1.ma.comcast.net (localhost [127.0.0.1]) by c-71-233-168-2.hsd1.ma.comcast.net (8.13.6/8.13.1) with ESMTP id k68GHJtX003985; Sat, 8 Jul 2006 12:17:19 -0400 (EDT) (envelope-from rodrigc@c-71-233-168-2.hsd1.ma.comcast.net) Received: (from rodrigc@localhost) by c-71-233-168-2.hsd1.ma.comcast.net (8.13.6/8.13.1/Submit) id k68GHJwk003984; Sat, 8 Jul 2006 12:17:19 -0400 (EDT) (envelope-from rodrigc) Date: Sat, 8 Jul 2006 12:17:19 -0400 From: Craig Rodrigues To: freebsd-current@freebsd.org Message-ID: <20060708161719.GB3871@crodrigues.org> References: <20060708152801.GA3671@crodrigues.org> <44AFD7DF.8090002@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44AFD7DF.8090002@errno.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-arch@freebsd.org Subject: Re: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 16:17:21 -0000 On Sat, Jul 08, 2006 at 09:05:51AM -0700, Sam Leffler wrote: > Linux has -t auto; haven't looked at how it works. I didn't want to implement -t auto, in case that would confuse things in case someone gets around to implementing autofs for FreeBSD, so I just used -t "". > It appears you just try a series of fs types; can't you read the device > to infer the filesystem? I was thinking of doing something like that. You can basically get the same info by doing something like: file - < /dev/ad0s1e /dev/stdin: Unix Fast File system (little-endian) file - < /dev/ad0s4 /dev/stdin: SGI XFS filesystem I leaned away from this approach in mount(8) because: - I didn't want to tie mount(8) to file(1) - I didn't want to build up a table of known superblocks inside mount(8) because every time a new filesystem is added to FreeBSD, mount(8) would need to be updated If there was a way, maybe at the GEOM or filesystem level to "taste" what type of filesystem existed on a device, and/or have a filesystem advertise what type of superblock it has, then that would be a nice way to do it, but I couldn't figure out a way to easily do it. -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 16:38:35 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F407116A4E0; Sat, 8 Jul 2006 16:38:34 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BA4143D5E; Sat, 8 Jul 2006 16:38:24 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k68GcAx3034638; Sat, 8 Jul 2006 10:38:15 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44AFDF38.3030707@samsco.org> Date: Sat, 08 Jul 2006 10:37:12 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Craig Rodrigues References: <20060708152801.GA3671@crodrigues.org> <86ac7krtu1.fsf@xps.des.no> <20060708160931.GA3871@crodrigues.org> In-Reply-To: <20060708160931.GA3871@crodrigues.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 16:38:35 -0000 Craig Rodrigues wrote: > On Sat, Jul 08, 2006 at 05:37:26PM +0200, Dag-Erling Smrgrav wrote: > >>What about cases where there may be several matching file systems? >>For instance, a clean ext3 file system is also a valid ext2 file >>system (and vice versa). > > > Currently, FreeBSD can only mount ext2 with mount -t ext2fs. > > A better example would probably be udf and cd9660 filesystems. > > Right now the logic is to iterate over the list of known local > filesystems (always starting with "ufs"), skipping over "synthetic" > and "network" filesystems, > i.e. similar to the list produced by lsvfs: > > Filesystem Refs Flags > -------------------------------- ----- --------------- > ufs 8 > reiserfs 0 read-only > nfs4 0 network > ext2fs 0 > ntfs 0 > cd9660 0 read-only > procfs 1 synthetic > msdosfs 0 > xfs 0 > devfs 1 synthetic > nfs 0 network > > > > The first matching filesystem wins....not perfect, but > maybe good enough for a lot of cases. > > mount -t always works if you want to specify the fstype. > Where is udf in the list? Btw, it's not that udf and cd9660 are compatible, they aren't by any means. It's that the can co-exist on the same media, and often times a UDF filesystem has cd9660 structures available for compatibility. If you added udf to your list above with a higher priority than cd9660, everything should 'just work', and you'd still be able to override it manually. Scott From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 17:37:56 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68E5E16A4DE for ; Sat, 8 Jul 2006 17:37:56 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC96543D45 for ; Sat, 8 Jul 2006 17:37:55 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FzGkV-0005QF-Re for freebsd-current@freebsd.org; Sat, 08 Jul 2006 19:37:47 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 08 Jul 2006 19:37:47 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 08 Jul 2006 19:37:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Sat, 08 Jul 2006 19:37:08 +0200 Lines: 29 Message-ID: References: <20060708152801.GA3671@crodrigues.org> <44AFD7DF.8090002@errno.com> <20060708161719.GB3871@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050921) X-Accept-Language: en-us, en In-Reply-To: <20060708161719.GB3871@crodrigues.org> Sender: news Cc: freebsd-arch@freebsd.org Subject: Re: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 17:37:56 -0000 Craig Rodrigues wrote: > - I didn't want to build up a table of known superblocks > inside mount(8) because every time a new filesystem is > added to FreeBSD, mount(8) would need to be updated There's a similar (in the basic idea, not in details) request on freebsd-geom list - how to detect what GEOM class is set up in an arbitrary provider. That is similar to this thread because both are discussing information that is available on-disk and usable by core system utilities (mount and installer) - so maybe a new library is in order, which will enable users to detect what is on a particular device/parition/provider/etc from on the device. In case of GEOM classes, metadata is written on the last sector, and first few fields ("signature fields") are in common format for all classes, so it's easy to get what class "owns" the device without going into the details of its metadata. Something like: struct devcontentinfo* get_provider_info(char *device_name); where returned value will be an array of found "contents", with a "type" member (enum) describing what it is (GEOM class / file system / swap), a "name" member which holds the ASCII name of the found thing ("UFS", "GEOM_MIRROR"), and an additional "extended_name" which would contain details ("UFSv2", "GEOM_MIRRORv4"). For these examples instead of "extended_name" maybe a version field will be enough ("v4" for GEOM_MIRROR stands for fourth metadata layout version). From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 17:38:46 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2432716A4DF; Sat, 8 Jul 2006 17:38:46 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id C547A43D58; Sat, 8 Jul 2006 17:38:45 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k68HceAL076112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Jul 2006 10:38:41 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <44AFEDA0.7040308@errno.com> Date: Sat, 08 Jul 2006 10:38:40 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.2 (X11/20060508) MIME-Version: 1.0 To: Craig Rodrigues References: <20060708152801.GA3671@crodrigues.org> <44AFD7DF.8090002@errno.com> <20060708161719.GB3871@crodrigues.org> In-Reply-To: <20060708161719.GB3871@crodrigues.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 17:38:46 -0000 Craig Rodrigues wrote: > On Sat, Jul 08, 2006 at 09:05:51AM -0700, Sam Leffler wrote: >> Linux has -t auto; haven't looked at how it works. > > I didn't want to implement -t auto, in > case that would confuse things in case someone gets around > to implementing autofs for FreeBSD, so I just used -t "". Oh, I stupidly assumed "auto" meant something similar to what you were doing :) > >> It appears you just try a series of fs types; can't you read the device >> to infer the filesystem? > > I was thinking of doing something like that. You can basically > get the same info by doing something like: > > file - < /dev/ad0s1e > /dev/stdin: Unix Fast File system (little-endian) > > file - < /dev/ad0s4 > /dev/stdin: SGI XFS filesystem > > > I leaned away from this approach in mount(8) because: > - I didn't want to tie mount(8) to file(1) > - I didn't want to build up a table of known superblocks > inside mount(8) because every time a new filesystem is > added to FreeBSD, mount(8) would need to be updated > > If there was a way, maybe at the GEOM or filesystem level to > "taste" what type of filesystem existed on a device, and/or > have a filesystem advertise what type of superblock it has, > then that would be a nice way to do it, but I couldn't figure > out a way to easily do it. I wouldn't expect a program like mount to fork+exec file; I'd expect it to either read directly or use a kernel facility. Sounds like something is missing to do this right. Sam From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 18:58:34 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5279F16A4DD; Sat, 8 Jul 2006 18:58:34 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B75BB43D45; Sat, 8 Jul 2006 18:58:31 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k68IwIUA035170; Sat, 8 Jul 2006 12:58:23 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44B00011.9050902@samsco.org> Date: Sat, 08 Jul 2006 12:57:21 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Craig Rodrigues References: <20060708152801.GA3671@crodrigues.org> <44AFD7DF.8090002@errno.com> <20060708161719.GB3871@crodrigues.org> In-Reply-To: <20060708161719.GB3871@crodrigues.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 18:58:34 -0000 Craig Rodrigues wrote: > On Sat, Jul 08, 2006 at 09:05:51AM -0700, Sam Leffler wrote: > >>Linux has -t auto; haven't looked at how it works. > > > I didn't want to implement -t auto, in > case that would confuse things in case someone gets around > to implementing autofs for FreeBSD, so I just used -t "". > > >>It appears you just try a series of fs types; can't you read the device >>to infer the filesystem? > > > I was thinking of doing something like that. You can basically > get the same info by doing something like: > > file - < /dev/ad0s1e > /dev/stdin: Unix Fast File system (little-endian) > > file - < /dev/ad0s4 > /dev/stdin: SGI XFS filesystem > > > I leaned away from this approach in mount(8) because: > - I didn't want to tie mount(8) to file(1) > - I didn't want to build up a table of known superblocks > inside mount(8) because every time a new filesystem is > added to FreeBSD, mount(8) would need to be updated > > If there was a way, maybe at the GEOM or filesystem level to > "taste" what type of filesystem existed on a device, and/or > have a filesystem advertise what type of superblock it has, > then that would be a nice way to do it, but I couldn't figure > out a way to easily do it. > > Well, by running through a list of possible filesystems and trying each one, you are effectively 'tasting' them. In a brute force way, but still the exact same idea. But really, it's not like filesystems are sprouting up every day, so I don't see the need to spend a lot of time making this elegant and highly extensible. Scott From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 21:56:48 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2A4B16A4DD; Sat, 8 Jul 2006 21:56:47 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 604A543D55; Sat, 8 Jul 2006 21:56:41 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 1B58D51393; Sat, 8 Jul 2006 23:56:39 +0200 (CEST) Received: from localhost (dlr167.neoplus.adsl.tpnet.pl [83.24.47.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 97A2951394; Sat, 8 Jul 2006 23:56:32 +0200 (CEST) Date: Sat, 8 Jul 2006 23:53:21 +0200 From: Pawel Jakub Dawidek To: Scott Long Message-ID: <20060708215321.GJ16201@garage.freebsd.pl> References: <20060708152801.GA3671@crodrigues.org> <44AFD7DF.8090002@errno.com> <20060708161719.GB3871@crodrigues.org> <44B00011.9050902@samsco.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Swj79WlilW4BQYVz" Content-Disposition: inline In-Reply-To: <44B00011.9050902@samsco.org> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: Craig Rodrigues , freebsd-current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 21:56:48 -0000 --Swj79WlilW4BQYVz Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 08, 2006 at 12:57:21PM -0600, Scott Long wrote: > Craig Rodrigues wrote: >=20 > >On Sat, Jul 08, 2006 at 09:05:51AM -0700, Sam Leffler wrote: > >>Linux has -t auto; haven't looked at how it works. > >I didn't want to implement -t auto, in > >case that would confuse things in case someone gets around > >to implementing autofs for FreeBSD, so I just used -t "". > >>It appears you just try a series of fs types; can't you read the device > >>to infer the filesystem? > >I was thinking of doing something like that. You can basically > >get the same info by doing something like: > >file - < /dev/ad0s1e > >/dev/stdin: Unix Fast File system (little-endian) > >file - < /dev/ad0s4 > >/dev/stdin: SGI XFS filesystem > >I leaned away from this approach in mount(8) because: > >- I didn't want to tie mount(8) to file(1) > >- I didn't want to build up a table of known superblocks > > inside mount(8) because every time a new filesystem is > > added to FreeBSD, mount(8) would need to be updated > >If there was a way, maybe at the GEOM or filesystem level to > >"taste" what type of filesystem existed on a device, and/or > >have a filesystem advertise what type of superblock it has, > >then that would be a nice way to do it, but I couldn't figure > >out a way to easily do it. >=20 > Well, by running through a list of possible filesystems and trying > each one, you are effectively 'tasting' them. In a brute force way, > but still the exact same idea. [...] One thing I don't like about this idea, is that simple mount(8) command will load all file system kernel modules if we give for example device with no file system on it. Currently I think there is no way to tell from userland mount(8) that because of our call, the kernel has loaded file system module. We could load it from mount(8) instead of waiting for the kernel to do it and then unload if we don't such such file system on the given device... > [...] But really, it's not like filesystems > are sprouting up every day, so I don't see the need to spend a lot of > time making this elegant and highly extensible. What Craig was trying to do over the last few weeks/months was to remove file systems specific code out of mount(8), so this will be a step backwards, I think... --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --Swj79WlilW4BQYVz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEsClRForvXbEpPzQRAoV3AKDmDsSBmqUrx3XTAaQVPvQFdmlcNACfXCbJ smXjBDifzfy6uvxbTc+12+E= =K68X -----END PGP SIGNATURE----- --Swj79WlilW4BQYVz-- From owner-freebsd-current@FreeBSD.ORG Sat Jul 8 22:27:07 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BA9516A4DD for ; Sat, 8 Jul 2006 22:27:07 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id E71C343D45 for ; Sat, 8 Jul 2006 22:27:06 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 7212B1140B; Sat, 8 Jul 2006 18:27:37 -0400 (EDT) Message-ID: <44B0313E.6010103@rogers.com> Date: Sat, 08 Jul 2006 18:27:10 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Craig Rodrigues References: <20060708152801.GA3671@crodrigues.org> <44AFD7DF.8090002@errno.com> <20060708161719.GB3871@crodrigues.org> In-Reply-To: <20060708161719.GB3871@crodrigues.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, AWL 0.00, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: freebsd-current@freebsd.org Subject: Re: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 22:27:07 -0000 Craig Rodrigues wrote: > I was thinking of doing something like that. You can basically > get the same info by doing something like: > > file - < /dev/ad0s1e > /dev/stdin: Unix Fast File system (little-endian) > > file - < /dev/ad0s4 > /dev/stdin: SGI XFS filesystem > This does not work on my system btw. root@fbsd.home.local:~# file - < /dev/ad0 /dev/stdin: x86 boot sector root@fbsd.home.local:~# file - < /dev/ad0s1 /dev/stdin: x86 boot sector, code offset 0x3c, reserved sectors 0, Media descriptor 0x0, reserved 0x16, dos < 4.0 BootSector (0x1f), BSD disklabel root@fbsd.home.local:~# file - < /dev/ad0s1a /dev/stdin: data root@fbsd.home.local:~# file - < /dev/ad0s1b /dev/stdin: x86 boot sector, code offset 0x3c, reserved sectors 0, Media descriptor 0x0, reserved 0x16, dos < 4.0 BootSector (0x1f), BSD disklabel root@fbsd.home.local:~# file - < /dev/ad0s1c /dev/stdin: x86 boot sector, code offset 0x3c, reserved sectors 0, Media descriptor 0x0, reserved 0x16, dos < 4.0 BootSector (0x1f), BSD disklabel No mention of FS type. root@fbsd.home.local:~# df -h|grep ad0 /dev/ad0s1a 73G 12G 55G 18% /